Open Stack

I'm happy to be corrected on this as I'm basing it on reading a diff, not an actual test.
It looks like glance migration 19 could introduce a non backwards compatible change
to the glance database. In principle, how should such an upgrade be managed?

A 'rolling' upgrade would be an ideal way to minimize disruptive updates.
It looks like there would need to be a bounce upgrade (stop the service on all nodes;
upgrade sw; start service) as old and new db clients don't look like they will co-exist.

thanks,
Tom

---

Tomas Hancock, HP Cloud Services, Hewlett Packard, Galway. Ireland +353-91-754765

Postal Address   : Hewlett Packard Galway Limited, European Software Centre, Ballybrit Business Park, Galway, Ireland
Registered Office: Hewlett Packard Galway Limited, 63-74 Sir John Rogerson's Quay, Dublin 2 Registered Number: 361933

The contents of this message and any attachments to it are confidential and may be legally privileged. If you have received this message in error you should delete it from your system immediately and advise the sender. To any recipient of this message within HP, unless otherwise stated, you should consider this message and attachments as "HP CONFIDENTIAL".

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130311/ac07eb1d/attachment.html>