Open Stack

> -----Original Message-----
> From: John Garbutt [mailto:john at johngarbutt.com]
> Sent: Tuesday, May 21, 2013 10:20 PM
> To: OpenStack Development Mailing List
> Subject: Re: [openstack-dev] [State-Management] Meeting minutes.
> 
> OK, we should have a chat to help co-ordinate our efforts.
> I have started work the nova live-migrate refactoring to use the task
> library here:
> https://blueprints.launchpad.net/nova/+spec/live-migration-to-conductor
> 
> I sadly can't make that meeting time during (UK) school term time due
> to a clash, but I can email status updates around the list, if that
> helps.
> 
> In terms of using TaskFlow, I am just starting to take a look at the code.

So are you planning to use this TaskFlow (https://github.com/yahoo/TaskFlow) library
to implement the blueprint or just unify the code paths with conductor?

> John
> 
> On 21 May 2013 17:14, Karajgi, Rohit <Rohit.Karajgi at nttdata.com> wrote:
> > Good progress indeed. We're continuing our efforts towards this goal by
> > implementing
> >
> > Live migration API using the taskflow library, and will have an update soon.
> >
> >
> >
> > -Rohit
> >
> > NTT Data
> >
> >
> >
> > From: Joshua Harlow [mailto:harlowja at yahoo-inc.com]
> > Sent: Friday, May 17, 2013 11:38 PM
> > To: OpenStack Development Mailing List
> > Subject: [openstack-dev] [State-Management] Meeting minutes.
> >
> >
> >
> > Great progress is one word I would choose to describe this so far :-)
> >
> >
> >
> > Logs @
> >
> http://eavesdrop.openstack.org/meetings/state_management/2013/state_
> management.2013-05-16-20.00.html
> >
> >
> >
> > TLDR:
> >
> >
> >
> > - Went over progress of taskflow library and discussed in-progress move to
> > stackforge (thx jlucci)
> >
> > - Showed potential example of how library could be used and what it
> enables
> > @ http://paste.openstack.org/show/37363/
> >
> > - Discussed about some of the patterns being created (linear, graph
> oriented
> > and distributed flows) that will allow users of the library to avoid
> > recreating common flows.
> >
> > - Discussed work being done (or work to be done) for hooking in a
> database
> > backend, a ZK backend and so-on.
> >
> >   - Interest from ipersky, changbl, jlucci on working on some of the above
> > (thx guys/gals!)
> >
> > - Agreement that we should target initial integration with cinder for H2 (H1
> > seems to close to be realistic).
> >
> > - Large desire to be able to get other openstack projects onboard (with a
> > similar timeline?).
> >
> >
> >
> > Feel free to jump on #openstack-state-management if you want to ask
> > questions or get involved :-)
> >
> > Feel free to experiment with the library and give any feedback also. New
> use
> > cases for other projects always welcome!
> >
> >
> >
> > -Josh
> >
> >
> >
> __________________________________________________________
> ____________
> > Disclaimer:This email and any attachments are sent in strictest confidence
> > for the sole use of the addressee and may contain legally privileged,
> > confidential, and proprietary data. If you are not the intended recipient,
> > please advise the sender by replying promptly to this email and then delete
> > and destroy this email and any attachments without any further use,
> copying
> > or forwarding
> >
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

______________________________________________________________________
Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data.  If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding