On 31/01/14 11:33 +0100, Alan Pevec wrote:
Hi all,
I'm opening the thread to discuss proposed exceptions for the stable/havana, either breaking the freeze or breaking the backport rules. I've two for now:
* https://review.openstack.org/69884 - Keystone: significant performance improvement, includes db migrations which are verboten in general, so my first reaaction was -2. But upon closer look, I think this is acceptable since even without running migration code will work after upgrade. Migrations are sequential to last in havana (034) so 035-036 could be treated like "reserved for Havana backports" like Nova did in https://github.com/openstack/nova/commit/ab2c467da951071a8aac4eb6ca032371c69... Of course that means no more db migrations in Keystone Havana!
* https://review.openstack.org/70016 - Horizon: session data type change - I'm not a Django expert, so I'd like input for Horizon team to verify Kieran's claims that it won't break existing sessions.
I'd like to request an exception for[0]. This is an important - quite invasive - cinder fix. The issue raises when the driver is not initialized correctly - or goes down - which makes volumes operations on that node fail without updating the volume status correctly. I hesitated a bit before proposing it for stable/havana but I believe that it can be a show stopper in some cases and most importantly it causes a lot of frustrations to the final users. Several bug reports have been filed because of this. After talking to John, Eric and Huang, we agreed it is a good backport. [0] https://review.openstack.org/#/c/67097/
Cheers, Alan
_______________________________________________ Openstack-stable-maint mailing list Openstack-stable-maint@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint
-- @flaper87 Flavio Percoco