Hi devs,
With online schema changes/No downtime DB upgrades things would be much lot
easier for OpenStack deployments.
Big kudos to Johannes who initiated this feature. But as a service provider,
I'm curious to understand what is the development process of adding new
features to Kilo and future releases once the online schema changes is in.
1. Will the committer be responsible of adding new procedures of
upgrading db with minimal or zero downtime? or the online schema changes
framework itself will detect whatever db changes are required on its own and
the decision to apply db changes online or offline will be left solely with the
service provider?
2. Is it possible to predict how much time it would take to upgrade db
(expand/migrate/contract phases) for adding a new column, constraint.
For example, adding a new column with NULL constraint would
take less time than adding a default value.
Please let us know your valuable opinions for the same.
Thank you,
Abhishek Kekane
______________________________________________________________________
Disclaimer: This email and any attachments are sent in strictest confidence
for the sole use of the addressee and may contain legally privileged,
confidential, and proprietary data. If you are not the intended recipient,
please advise the sender by replying promptly to this email and then delete
and destroy this email and any attachments without any further use, copying
or forwarding.__________________________________________________________________________
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
