Hi, I am upgrading from Juno to Kilo and from that to Liberty.
I understand I need to nova-manage db migrate_flavor_data before upgrading from Kilo to Liberty to let VMs that were spawned while the system was in Juno to flavor migrate to Kilo. Depending on the number of computes, complete upgrade can potentially be spanned for longer duration, days if not months. While migrate_flavor_data seem to flavor migrate meta data of the VMs that were spawned before upgrade procedure, it doesn't seem to flavor migrate for the VMs that were spawned during the upgrade procedure more specifically after openstack controller upgrade and before compute upgrade. Am I missing something here or is it by intention? Since, the compute upgrade procedure could last for days, would it be practical to block spawning work load VMs for that long duration? Otherwise, next upgrade will fail right? thanks Suresh
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
