Assuming my understanding is correct, 2 things make you sad in the upgrade process.
1. must reconfig the 'upgrade_levels' in the config file during post-upgrade. 2. must restart the service in order to make the option 'upgrade_level' work. I think the configuration management tools (e.g. chef, pupput) can solve the #1. We can change the 'upgrade_level' option in config file after upgrading and sync it to all the hosts conveniently. #2 is more complex, fortunately there are some works to try to solve it, [1] [2]. If all the OpenStack services can support SIGHUP, I think we just need to trigger a SIGHUP to make the services reload the config file. Correct me If I'm wrong, thanks. [1]: https://blueprints.launchpad.net/glance/+spec/sighup-conf-reload [2]: https://bugs.launchpad.net/oslo-incubator/+bug/1276694 2015-05-07 16:09 GMT+08:00 Guo, Ruijing <ruijing....@intel.com>: > Hi, All, > > > > In existing design, we need to reconfig nova.conf and restart nova > service during post-upgrade cleanup > > As https://www.rdoproject.org/Upgrading_RDO_To_Icehouse: > > > > I propose to send RPC message to remove RPC API version pin. > > > > > > 1. Stop services (same with existing) > > 2. Upgrade packages (same with existing) > > 3. Upgrade DB schema (same with existint) > > 4. Start service with upgrade (add upgrade parameter so that nova > will use old version of RPC API. We may add more parameter for other > purpose including query upgrade progress) > > 5. Send RPC message to remove RPC API version pin. (we don’t need > to reconfig nova.conf and restart nova service) > > > > What do you think? > > > > Thanks, > > -Ruijing > > > > > > __________________________________________________________________________ > 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 > >
__________________________________________________________________________ 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