> The current DB online data upgrade model feels *very opaque* to > ops. They didn't realize the current model Nova was using, and didn't > feel like it was documented anywhere.
> ACTION: document the DB data lifecycle better for operators This is on me, so I'll take it. I've just thrown together something that I think will help a little bit: https://review.openstack.org/373361 Which, instead of a blank screen and a return code, gives you something like this: +---------------------------+--------------+-----------+ | Migration | Total Needed | Completed | +---------------------------+--------------+-----------+ | migrate_aggregates | 5 | 4 | | migrate_instance_keypairs | 6 | 6 | +---------------------------+--------------+-----------+ I'll also see about writing up some docs about the expected workflow here. Presumably that needs to go in some fancy docs and not into the devref, right? Can anyone point me to where that should go? --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
