[openstack-dev] Rolling upgrades in icehouse

Meghal Gosalia meghal at yahoo-inc.com
Mon Mar 24 21:39:55 UTC 2014

Thanks a lot Dan for your reply.
This is definitely a good first step to move out nova-compute from the services to be upgraded atomically.

Looking forward to your blog post.


On Mar 24, 2014, at 12:14 PM, Dan Smith <dms at danplanet.com> wrote:

> Signed PGP part
> > Where can I obtain more information about this feature?
> - From the blog post that I've yet to write :D
> > Does above imply that database is upgraded along with control
> > service update as well?
> Yes, but only for the services that interact directly with the
> database. The services that do *not* need to be upgraded atomically
> with the schema are: nova-compute and nova-network.
> > One more question - is there an initiative to make icehouse
> > database schema work with havana based control services ?
> It depends on what you mean by "control services". For icehouse, the
> incremental step that we're making is that all the controller services
> must be upgraded atomically with the database schema. That means api,
> scheduler, conductor, etc. A havana compute node is sufficiently
> isolated from the data schema that it will continue to work with an
> icehouse conductor, allowing you to upgrade compute nodes
> independently after the controller services are updated.
> This was just our first step at providing some capability for this. We
> hope to continue to increase the capabilities (and decrease the amount
> that must be done atomically) going forward.
> Hope that helps!
> - --Dan
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140324/c1587543/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140324/c1587543/attachment.pgp>

More information about the OpenStack-dev mailing list