Thanks Gary for doing this, will chip in with the reviews.

I guess 
https://review.openstack.org/#**/c/19079<https://review.openstack.org/#/c/19079>
is
now https://review.openstack.org/#/c/19090/

Thanks,
~Sumit.

On Mon, Jan 7, 2013 at 3:01 AM, Gary Kotton <gkot...@redhat.com> wrote:

> Hi,
> I have done a OSLO update and to be honest it was quite a challenge. This
> is due to the fact that the CFG interface has changed a bit. Now CLI
> commands have to be registered - this is a tough one as it is no longer
> backward compatible. Bummer.
> Can you please take a look at 
> https://review.openstack.org/#**/c/19079<https://review.openstack.org/#/c/19079>
> I have tested this with devstack and it looks OK. A few additional eyes on
> this one will be good.
>
> Regarding the stable branch we have the follows:
>     In stable review:
>         
> https://review.openstack.org/#**/c/19079/<https://review.openstack.org/#/c/19079/>-
>  validity checks for gateway on subnet
>         
> https://review.openstack.org/#**/c/19051/<https://review.openstack.org/#/c/19051/>-
>  exception cleanup
>         
> https://review.openstack.org/#**/c/18818/<https://review.openstack.org/#/c/18818/>-
>  ensure allocation pools are deleted
>         
> https://review.openstack.org/#**/c/18819/<https://review.openstack.org/#/c/18819/>-
>  fix exception output (I need to write a test case on master - i do not
> think this should prevent it)
>         
> https://review.openstack.org/#**/c/18651/<https://review.openstack.org/#/c/18651/>-
>  atomic access to databases
>     Upstream review:
>         
> https://review.openstack.org/**19039<https://review.openstack.org/19039>- 
> quotas refactoring (required to perform upgrades in the future)
>         
> https://review.openstack.org/#**/c/18871/<https://review.openstack.org/#/c/18871/>-
>  invalid exceptions
>         
> https://review.openstack.org/**18758<https://review.openstack.org/18758>- 
> additional support to ovs cleanup utility
>
>     Pending upstream fix:
>         
> https://bugs.launchpad.net/**quantum/+bug/1056437<https://bugs.launchpad.net/quantum/+bug/1056437>-
>  provider network support (grizzly 3)
>         
> https://bugs.launchpad.net/**quantum/+bug/1089773<https://bugs.launchpad.net/quantum/+bug/1089773>-
>  notification level support
>
>     Pending back port:
>         
> https://review.openstack.org/#**/c/18653/<https://review.openstack.org/#/c/18653/>-
>  better to wait for the exception patch above first (bulk/quotas)
>         
> https://review.openstack.org/#**/c/18854/<https://review.openstack.org/#/c/18854/>-
>  enable to tenants to set-non-owned netwrok... (i'll do this soon)
>
> Open Issues:
>     I think that at some stage or another we should discuss backporting of
> specific plugin updates. For example, do we want to move the NVP provider
> network support to folsom stable?
>
> Thanks
> Gary
>
> --
> Mailing list: 
> https://launchpad.net/~**quantum-core<https://launchpad.net/~quantum-core>
> Post to     : 
> quantum-core@lists.launchpad.**net<quantum-core@lists.launchpad.net>
> Unsubscribe : 
> https://launchpad.net/~**quantum-core<https://launchpad.net/~quantum-core>
> More help   : 
> https://help.launchpad.net/**ListHelp<https://help.launchpad.net/ListHelp>
>
-- 
Mailing list: https://launchpad.net/~quantum-core
Post to     : quantum-core@lists.launchpad.net
Unsubscribe : https://launchpad.net/~quantum-core
More help   : https://help.launchpad.net/ListHelp

Reply via email to