openstack team mailing list archive

[Sam Morrison <sorrison@xxxxxxxxx>]

We have been using this patch in testing for a few months now. It works pretty well with launching instances etc.
It is feature incomplete at the moment though.

We have developed syncing of security groups and private keys down do child cells. Also done the live migration add ons for cells.

It would be good to get this in master as soon as Folsom gets branched off as we'd like to contribute these back.


Cheers,
Sam





On 16/09/2012, at 5:07 PM, balaji patnala <patnala003@xxxxxxxxx> wrote:

> Atleast we should have continued with "ZONES" until CELLS were part  of up-stream releases. I was waiting for this feature eagerly to explore more on this. 
> 
> Can we try with the patch listed below. Only one concern with patches are we dont get much help from stack users/testers..!!!!
> 
> This is little disappointing...
> 
> On Fri, Sep 14, 2012 at 10:35 PM, Joshua Harlow <harlowja@xxxxxxxxxxxxx> wrote:
> Ya, is there a session on it at the summit.
> 
> I'd at least like to talk about it and what it could be in the end.
> 
> Or maybe we can 'freestyle' that session :-P
> 
> On 9/14/12 8:36 AM, "Russell Bryant" <rbryant@xxxxxxxxxx> wrote:
> 
> >On 09/14/2012 11:08 AM, Joe Topjian wrote:
> >>     > We didnt find any information related to CELLS [which is planned
> >>to
> >>     > replace ZONES] in the latest Folsom pre-release.
> >>     >
> >>     > Can any body give us information on this.
> >>
> >>     Unfortunately, cells was unable to make feature freeze.  It should
> >>be in
> >>     Grizzly.  Sorry for the delay :/
> >>
> >>
> >> This is very disappointing. I was looking forward to cells as well.
> >>
> >> When was this decided and was the decision announced somewhere else? I'd
> >> like to know so I can monitor for other announcements like this.
> >
> >The patch is here:
> >
> >    https://review.openstack.org/#/c/10707/
> >
> >It was proposed for inclusion on August 2nd, which was just a couple of
> >weeks before the feature freeze.  There were enough significant things
> >that came up in discussion that it just wasn't going to make it in for
> >Folsom.  In addition to working through the technical details, it also
> >desperately needs some documentation (ideally both architectural, as
> >well as how to use it).
> >
> >It seems like we should be able to get this all wrapped up for Grizzly,
> >though.
> >
> >--
> >Russell Bryant
> >
> >_______________________________________________
> >Mailing list: https://launchpad.net/~openstack
> >Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> >Unsubscribe : https://launchpad.net/~openstack
> >More help   : https://help.launchpad.net/ListHelp
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp