On 8/17/2015 10:19 AM, Dan Smith wrote:
Is this documented somewhere?
I did a bit of digging and couldn't find anywhere that explicitly
required that for the J->K upgrade. Certainly it was documented for the
I->J upgrade.
It's our model, so I don't think we need to document it for each cycle
since we don't expect it to change. We may need more general coverage
for this topic, but I don't expect the release notes to always mention it.
This isn't formal documentation, but it's relevant:
http://www.danplanet.com/blog/2015/06/26/upgrading-nova-to-kilo-with-minimal-downtime/
--Dan
__________________________________________________________________________
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
We have some very loose upgrade docs in the devref [1]. Under the
"Process" section, steps 4 and 5 talk about upgrading services in order
and says conductor (implied controller) first. Granted we need to clean
up this page and merge with Dan's more specific blog post, but there is
*something* in tree docs.
[1] http://docs.openstack.org/developer/nova/upgrade.html
--
Thanks,
Matt Riedemann
__________________________________________________________________________
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
