Quantum Grizzly Upgrade Paths
-
Upload
salvorlando -
Category
Technology
-
view
443 -
download
0
description
Transcript of Quantum Grizzly Upgrade Paths
![Page 1: Quantum Grizzly Upgrade Paths](https://reader036.fdocuments.in/reader036/viewer/2022082809/556f5edfd8b42a916b8b5165/html5/thumbnails/1.jpg)
Openstack Grizzly Summit
Quantum Upgrade Paths
San Diego, CaliforniaTuesday, October 16th
![Page 2: Quantum Grizzly Upgrade Paths](https://reader036.fdocuments.in/reader036/viewer/2022082809/556f5edfd8b42a916b8b5165/html5/thumbnails/2.jpg)
Summary
• Problem statement:THERE IS NO WAY TO PERFORM ANY KIND OF UPGRADE ON QUANTUM
• Goal:MAKE SURE THAT FOR GRIZZLY QUANTUM HAS AN UPGRADE STORY
![Page 3: Quantum Grizzly Upgrade Paths](https://reader036.fdocuments.in/reader036/viewer/2022082809/556f5edfd8b42a916b8b5165/html5/thumbnails/3.jpg)
Upgrade Path 1:
• From Quantum X to Quantum Y• DB Upgrade procedure– SQL alchemy migrations– For extension too
• Handle properly plugin-specific extensions
• Plugin specific upgrade operations– If needed, can be performed with plugin-specific
procedure after db upgrade• MUST target Grizzly– possibly milestone #1 or #2
![Page 4: Quantum Grizzly Upgrade Paths](https://reader036.fdocuments.in/reader036/viewer/2022082809/556f5edfd8b42a916b8b5165/html5/thumbnails/4.jpg)
Upgrade Path 2
• From Nova-network to Quantum– Extract information from nova DB– Create Quantum logical model– Rebuild networks (fairly hard according to
requirements)• Need to exactly scope what we want to achieve when
migrating from nova-network
• It would be awesome to have something for it in Grizzly!
![Page 5: Quantum Grizzly Upgrade Paths](https://reader036.fdocuments.in/reader036/viewer/2022082809/556f5edfd8b42a916b8b5165/html5/thumbnails/5.jpg)
Upgrade Path 3
• From Quantum Plugin A to Quantum Plugin B– Do we have a use case for this?– If yes, Should it be plugin-specific?
• If a use case is agreed for it, can be implemented post Grizzly