2. 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
3. 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
4. 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!
5. 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