I'd like to reiterate what we discussed during the "Core Awareness" topic at yesterday's Glance weekly meeting for those who weren't able to attend or read through the meeting logs yet.
Three Ocata priorities have already been determined: (1) image import refactor (2) community images (including image 'visibility' enhancements) (3) rolling upgrades, specifically the database strategy for zero-downtime upgrades There's a sub-team working on image import (weekly sync in #openstack-glance at 14:00 UTC). Any cores not working on image import, please direct your attention to community images: - https://review.openstack.org/369110 - https://review.openstack.org/366354 - https://review.openstack.org/379852 With timely reviews, we may be able to land this before the summit. Additionally, it's important to have the code merged so for the sub-team working on rolling upgrades, so they can demonstrate how the strategy will work on a real-life migration. As far as rolling upgrades reviews go, there are a lot of comments on the database strategy spec, but not many of these are from Glance cores. It would be good to take a look to sanity check the strategy being proposed: - https://review.openstack.org/#/c/331740/ Additionally, there's a patch for moving db migrations from SQLAlchemy-migrate to Alembic: - https://review.openstack.org/#/c/374278/ And a patch up to make the switch to Alembic: - https://review.openstack.org/#/c/382958/ Please take the time to look these over. If you have reservations about the move to Alembic, now's the time to make them heard. So, those are the Glance priorities for the next two weeks. cheers, brian __________________________________________________________________________ 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
