20:00:13 #startmeeting state-management 20:00:14 Meeting started Thu Oct 24 20:00:13 2013 UTC and is due to finish in 60 minutes. The chair is harlowja. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:00:17 The meeting name has been set to 'state_management' 20:00:20 hi folks 20:00:27 hi there 20:00:30 hi hi 20:01:23 lets see who shows up, ha 20:02:02 i just noticed these, i think we can close them, as they don't need to be in nova anymore :-P 20:02:12 https://blueprints.launchpad.net/nova/+spec/structured-state-management-core-library 20:02:17 forgot i even made those, ha 20:02:37 guess we'll have a micro-meeting today then :) 20:02:53 #link https://wiki.openstack.org/wiki/Meetings/StateManagement 20:03:21 think a good think just to discuss https://blueprints.launchpad.net/taskflow 20:03:28 #link https://blueprints.launchpad.net/taskflow 20:04:23 was thinking checkpointing, a basic distributed engine, book-retention, and zk-logbook from changbl 20:04:38 and maybe a basic job-reference-impl 20:04:49 so those 5 things (if we can) 20:05:00 i think i've got some kind of plan for reversion strategies 20:05:10 k 20:05:26 * iv_m is prepearing design doce with colorful pictures of graphs) 20:05:29 ha 20:05:33 ponies included? 20:06:05 no, i thought we agreed ponies are out of scope of taskflow 20:06:08 damn it 20:06:12 :( 20:06:57 k, so checkpointing (which might include basic retention?), distributed engine (basic), reversion-strategies, zk-logbook 20:07:08 and of course integration into openstack 20:07:15 *cinder, glance, nova 20:07:22 *more integration that is 20:07:30 hey guys, 20:07:35 hi changbl ! 20:07:40 sorry i am late 20:07:42 hi 20:07:43 np 20:07:58 also btw, 0.1 tag is almost made, there is some problem with gerrit that i am working with them on 20:08:07 something about permissions not being assigned correctly 20:08:15 cool 20:08:25 we were just talking about what to try to do for 0.2 20:08:26 look forward to 0.1 20:08:34 thinking so checkpointing (which might include basic retention?), distributed engine (basic), reversion-strategies, zk-logbook 20:08:39 and of course high priority on integration 20:08:41 i see, i am scrolling back the log 20:08:43 np 20:09:11 those don't seem like to much (more priority on integration of 0.1 i think) 20:09:37 and if we can, DuncanT has a FSM we can try to work with him on 20:09:42 *or is working on* 20:09:59 #link https://etherpad.openstack.org/p/CinderTaskFlowFSM 20:10:14 the FSM would be a nice to have 20:11:06 seems reasonable? 20:11:28 sure 20:11:32 did not read it into detail, but i like the idea of associating each entity with a state machine 20:11:52 changbl ya, its still a WIP, so i think we can help make it appear, although what it is yet is TBD :) 20:12:02 sure 20:12:59 i am hoping we dive the FSM into that at the summit (or maybe an unconference) with some cinder folks (and other interested parties) 20:13:20 #action harlowja talk to DuncanT about unconference (or similar) 20:13:31 sigh, too bad i won't be there :( 20:13:36 :( 20:13:47 i will channel your good will 20:13:54 :) 20:14:17 cool 20:14:24 #topic integration 20:14:37 i think this deserves a whole little session, just to share proposals/ideas 20:14:48 #link https://etherpad.openstack.org/p/TaskflowIcehouseWhoWhatWhereWhy 20:15:27 so i think we have a few cinder sessions, and i think anastasia (and i) want to continue doing work there (and others) 20:15:36 so cinder i feel is going good 20:16:12 glance, i've talked with markwash and explained taskflow ideas and such 20:16:21 and i think there will be some talks at the summit, http://summit.openstack.org/cfp/details/120 (and others) 20:16:34 i think good progress going there 20:17:19 nova i have a joint session with john garbutt and am forming some blueprints for nova to try to get some traction there 20:17:23 You can cover not just import\export but image migration feature too. 20:17:50 I saw some BP in glance about more smart image management and distribution. 20:17:52 gokrokve sure, i'm hoping the glance folks do the integration :) 20:18:00 * markwash is listening 20:18:11 markwash ^ 20:18:35 harlowja: review help would be nice of course 20:18:36 some summit talks and unconference and stuff i think are going well for glance 20:18:40 of course markwash :) 20:19:00 never fear! we are here , ha 20:19:53 so nova 'front', i am hoping will have some stuff going there for icehouse, thinking harlowja and iv_m can see what we can do there :) 20:20:10 i'd be happy with basics :) 20:20:23 and then heat, http://summit.openstack.org/cfp/details/121 20:20:31 i think that will just be more information sharing and discussion 20:20:57 #action harlowja gotta work with zaneb on that 20:21:11 * harlowja damn i'm doing alot of sessions 20:21:11 What do you think about nova using taskflow for VM instantiation. Potetnially user can extend workflow to add more actions during the creation of VM without rewriting nova code. 20:21:44 gokrokve so about a 9 months ago, taskflow version 0.00001 NTT and y! actually did that 20:21:55 and we showed it at the conference as a prototype 20:22:21 i think we have to take it a little slower though (for better or worse) 20:22:22 That's cool. Why it still not in nova? 20:22:50 :) 20:23:11 so i think partially because me and others believed this is better as a library, so diverted path for a short period to build that library 20:23:23 and i think it was also to big of a change for nova at the time 20:23:48 got it. Still it is valuable extension for nova. 20:23:50 totally agreed 20:24:18 and i hope we can get some traction there in icehouse 20:25:14 gokrokve make more sense now :) 20:25:23 * make more sense now? 20:25:29 yes 20:25:55 oslo integration also, http://summit.openstack.org/cfp/details/118 20:26:11 i think that one will maybe be about what taskflow is, where does it fit in oslo (does it?) 20:26:49 is it just a naming association (taskflow is in oslo, when its still a library) 20:26:51 I am not sure how it is related to oslo. 20:27:15 well oslo is a set of common libraries for openstack right? 20:27:28 set = [rpc, log, config] 20:27:39 set += [taskflow] ? 20:27:56 Yep. Makes sense. 20:28:03 oslo.taskflow 20:28:11 possibly, idk 20:28:18 to me thats just 'branding' in a way 20:28:21 *which has its uses 20:28:32 taskflow still exists no matter 20:28:43 with our without 'oslo.' prefix :) 20:28:46 *or 20:28:57 anyways, so thats oslo integration 20:29:06 Yes. It looks like that being adopted by multiple projects is a requirement. 20:29:22 but is sqlalchemy part of oslo? 20:29:33 its used everywhere 20:29:41 No. And it looks like because oslo is an API library 20:30:05 what libraries aren't API libraries? 20:30:06 :) 20:30:17 I am probably confused with REAST API. 20:30:24 k, gotcha 20:30:45 ya, so i'm unsure what oslo buys us (besides sponsorship) so we'll see what happens in that session 20:30:48 The API should be generally useful and a "good fit" - e.g. it shouldn't encode any assumptions specific to the project it originated from, it should follow a style consistent with other Oslo APIs and should fit generally in a theme like error handling, configuration options, time and date, notifications, WSGI, etc 20:31:17 They actually also mix REST API (WSGI) and probably other API's like library interfaces 20:31:18 sounds like any library i've worked with :-P 20:31:50 ya, so we'll see what happens at summit related to that 20:32:33 so thats all the integration talks that i'll be pushing around :) 20:32:41 anyone else have any? 20:32:46 oh, and of course mistral 20:32:51 which is WIP :) 20:33:14 working with gokrokve and others for mistral 20:33:51 Do you have time slot in taskflow sessions for Mistral? 20:34:09 We can prepare etherpads with design proposals and other stuff to discuss. 20:34:23 I believe we already did something in this direction. 20:34:38 gokrokve the only one i see partially releated to mistral is the heat one 20:34:50 #link http://summit.openstack.org/cfp/details/121 20:35:04 otherwise i think it will have to be unconference like (not official session) 20:35:19 ok 20:35:50 for the speaker session i am doing (not design session) i have a slide for mistral :) 20:36:30 * harlowja can't find the link off hand for that 20:36:44 if u guys want to see a prototype (version 3.5) of those slides, email me (or ask later) 20:36:57 rather not publize them until earlier to the summt 20:37:04 *when i'll drop them on slideshare 20:37:54 hopefully the deck will be useful :) 20:38:16 ok. I will ask Ruslan to prepare some data for you and then we can discuss this slide. 20:38:47 k 20:39:38 gokrokve do u want to give a little summary of your current thoughts for mistral (or should we wait?) 20:39:41 #topic mistral 20:41:16 We are working on two major documents: 1) use cases with detailed description of how Mistral can be used 20:41:39 2) Q&A documents with answers for most common questions 20:42:17 Also we are preparing initial etherpad page for Mistral design 20:42:43 awesome :) 20:42:52 looks like good progress, making sure the foundation is solid 20:43:46 Also I see an invite for tomorrow for hangout meeting with taskflow team. But frankly, I don't see anyone from your team in this invitation. 20:43:52 i'm there :) 20:43:59 iv_m if he wants to be 20:44:10 at least i think i'm there, ha 20:44:48 *and if anyone else wants, please join 20:45:04 Probably. My calendar shows only mirantis folks, though 20:45:10 hmmm 20:45:21 i'll double check 20:46:09 #action harlowja make sure hangout in 20:46:45 thx gokrokve , i'll make sure i'm there 20:46:59 #topic open-discuss 20:47:09 anything else for people to discuss? if not we can end early 20:48:00 goiiing once 20:48:43 goiiing twice 20:48:56 sold! 20:49:07 k, keep up the good work folks, and thanks for coming :) 20:49:18 more fun times of course in #openstack-state-management 20:49:30 questions, answers and more goodness there 20:49:46 #endmeeting