19:59:18 #startmeeting state-management 19:59:19 Meeting started Thu Aug 29 19:59:18 2013 UTC and is due to finish in 60 minutes. The chair is harlowja. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:59:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:59:23 The meeting name has been set to 'state_management' 19:59:38 oops, 30 seconds to early, lol 20:00:07 hallooooooo 20:00:17 #link https://wiki.openstack.org/wiki/Meetings/StateManagement 20:01:02 hmmm, if nobody around then its a quick meeting, ha 20:01:25 quick one? :) 20:01:42 sweet, hi changbl 20:01:50 hey man 20:01:52 hey 20:02:05 might just be me and u, ha 20:02:15 oops... what happened? 20:02:22 vacation? 20:02:44 or busy, jessica i think is busy, i guess ivan to 20:03:21 let me see if we had any action items from last time 20:03:25 #topic previous-items 20:03:35 #link http://eavesdrop.openstack.org/meetings/openstack_state_management/2013/openstack_state_management.2013-08-22-20.00.html 20:03:41 so i did find a sock puppet app for iphone/ipad 20:03:54 #link https://itunes.apple.com/us/app/sock-puppets/id394504903 20:04:02 so i might mess around with that, haha 20:04:24 and i did go through the twiki and added a few more use-cases, cleaned up a few sections 20:04:35 #link https://wiki.openstack.org/wiki/TaskFlow#Further_use-cases 20:04:48 those are other things i think taskflow can help out with 20:05:18 hello. 20:05:31 at first glance, we will use taskflow to stop/upgrade/restart openstack services? 20:06:02 hmmm, not really, i think that taskflow can help those service actions not behave so badly 20:06:20 kebray hii 20:06:49 changbl let me see if i can readjust that, the description there was more about how the problem exists and how taskflow can help make it better 20:06:51 all right, sounds like a good idea, not sure of the acceptance by others 20:07:45 changbl sure, i'll adjust that to make that more obvious 20:07:53 harlowja, did you throw this idea into the mailing list to see what others think? 20:08:23 not yet, i always thought it was an inherent thing that taskflow offers, but might be worth a mailing list post 20:08:40 ok 20:09:02 changbl when u stop say nova-compute, i guess the question is how does that work for u, does it sometimes leave hypervisors half-way completed? 20:09:36 did not encounter this problem before ... 20:09:45 seems smooth for me 20:10:10 hmmm, interesting, ok 20:10:36 seems like in general projects if they are forced to stop, when they are in the process of doing actions don't exactly handle that so well 20:10:47 and u typically force them to stop when doing an upgrade, when the hardware fails... 20:11:08 anyways 20:11:19 ah, I see... never stop nova-compute when it was performing actions... 20:11:27 lol 20:11:45 guess i have not had that much experience with openstack in production 20:11:48 so ya, thats not exactly something i personally believe is acceptable software design ;) 20:12:02 it should always be stoppable 20:12:10 and it should recover 20:12:17 make sense to me 20:12:37 i'll update the wiki there to make that more obvious 20:12:45 sounds good 20:13:02 cool 20:13:20 #topic status 20:13:51 i see a lot of commits from Ivan 20:13:55 yup 20:13:57 he's been busy, ha 20:14:05 with taskflow? or others? 20:14:11 taskflow afaik 20:14:29 talking to him i think we can start getting some of those in next week 20:14:35 and see how that goes 20:14:48 i took a rough look at the code 20:14:58 will need more time to review carefully 20:15:02 agreed, same here 20:15:10 i think thats his prototype review also (so its not finished) 20:15:23 he just wanted to get it out there so that we could start thinking about it 20:16:33 as for me, i've just been working on the persistance of flows and experimenting with how we can save tasks and flows to the backiing logbook changes done recently 20:16:40 and not just save them, but restore them 20:16:58 https://review.openstack.org/#/c/43814/ isn't up to date, but its a WIP 20:17:34 it gets complicated when u have arbitarily complex flows/tasks, which is why it will be interesting to see how ivan/anastasia will handle it 20:18:01 yes, saw your recent changes, will keep an eye on it 20:18:10 cool :) 20:18:11 thx changbl 20:18:20 what is this file "askflow/persistence/backends/sqlalchemy/alembic/versions/21da24117e42_add_task_and_flow_ty.py"? 20:18:46 ah, alembic migration 20:19:03 instead of 002_blah_db.py like in sqlalchemy-migrate 20:19:13 alembic uses this other way, so not 002 20:19:33 the naming i don't really like, ha 20:19:38 but it automatically creates those 20:19:39 seems a very alien file to me... 20:20:08 ya 20:20:26 https://github.com/openstack/ceilometer/tree/master/ceilometer/storage/sqlalchemy/alembic/versions 20:20:33 i guess openstack is moving toward that alembic for migrations 20:20:41 so u'll see similar stuff more often i think 20:21:05 *for better or worse* 20:21:11 ah, i see.... gonna learn yet another library 20:21:15 ya 20:21:21 i learned quite some libraries these days 20:21:23 :) 20:22:17 btw, how is the distributed task queue/celery work? 20:22:29 kebray do u have any update there, i guess jessica is out today 20:23:44 what are you gonna remove threaded flow ? 20:24:00 whattt 20:24:03 ha 20:24:25 ekarlso- not afaik, it might change a little with ivans work, but i don't think it will affect u at this moment 20:24:57 so no worries ekarlso- ! 20:25:02 we got u covered 20:25:04 :/ 20:25:08 harlowja, anyway, i put some comments there on jessica's commit, will wait for her to respond. 20:25:14 changbl agreed 20:25:50 cool, so let me jump into a vote that ivan wanted 20:25:50 harlowja sorry, got distracted. 20:25:56 ah 20:25:57 np 20:26:12 Yeah, school is back in session, so jlucci's schedule is sort of sporadic for a bit. 20:26:24 understood 20:26:37 Is she a student ? :) 20:26:41 She's still just plugging along at Trove.. I know she had a meeting w/Trove developers last week. They got very excited. 20:26:49 They liked what TaskFlow had to offer. 20:26:56 sweet 20:27:19 changbl She is currently attending university. 20:27:30 kebray, part-time I guess? 20:27:47 So, I don't anticipate much push back on the work she will be doing in Trove... but, we'll keep monitoring that to make sure it goes smooth. 20:28:18 full-time work, full-time school... but, she loads most of her classes on Tues/Thur. 20:28:32 busy bee, woah 20:28:32 lol 20:28:37 double full-time, wow! 20:28:40 technically part-time work... but, she manages to put in quite a few hours. 20:28:50 i see... 20:28:53 anyway. 20:29:08 kebray do u think we should see if anyone wants to jump on the distributed stuff to help out 20:29:15 i'm not sure who that might be, but i can look around, ha 20:29:49 that would be great... I"m resource constrained. 20:29:58 k, let me see what i can do 20:30:42 My hope is she can finish up Trove work soon, and then let those devs carry on with that... and, put her back on Distributed with intentions of figuring out how to work things into Heat in a way that the community will find valuable, through collaboration with them of course. 20:30:51 agreed 20:31:02 its the same with me and cinder i guess 20:31:04 So, it might make sense if someone wants to help her with the Trove stuff first :-) 20:31:13 inspire them to see it, then hope that they can run with some of it 20:31:39 hmmm, so much to tackle 20:31:41 ha 20:32:29 changbl is anyone in your area interested the distributed pieces? 20:32:42 if not at this moment, thats fine also 20:32:43 not as far as I know... 20:32:48 k 20:33:15 let me jump topics into the glance meeting that happened 20:33:19 #topic glance-meeting 20:33:29 so there was a meeting on monday morning with the glance folks 20:33:51 i think they are interested in using it for some of there task work, the meeting was more of a what is this, what are u trying to accomplish and all of that 20:34:02 so i think there is shared interest in making it work in someway inside glance 20:34:21 harlowja, sounds great 20:34:27 the meeting was in #openstack-glance so it wasn't logged (sadly) 20:34:35 but i think positive involvement there 20:34:49 overall we just need to keep in touch with them, help them explore i think 20:34:56 and then we can be in glance (maybe in H, unsure) 20:35:04 kebray that means cough cough 2 core projects btw ;) 20:35:10 :-) 20:35:42 I'm meeting internally with John G. soon too, btw. to talk more about nova integration. 20:36:20 so i'm going to try to continue working with them, if i can get some time to make that happen and help them see how much of taskflow they want/can use, which i think does align with there future goals of having a little task engine in glance to do import/export/convert (of images) 20:36:26 thx kebray that sounds great, let me know if u need me 20:36:36 +1 kebray 20:36:56 will definitely let you know harlowja. 20:37:24 great, thx kebray 20:37:51 nikhil yt 20:38:14 nikhil i think is the main person thats doing some of the glance -task work 20:38:40 ok, will chat with him later i think 20:39:04 kebray when u get a chance, would u check over https://wiki.openstack.org/wiki/TaskFlow#Further_use-cases also, let me know if they don't make sense 20:39:25 i think i have one modification to do there to make the 'Service stop/upgrade/restart' make more sense 20:39:31 adrian_otto might be interested also 20:39:47 was reading that a minute ago... I'm not an expert on nova services (e.g. I don't have experience running openstack myself too much)... but, the use-case seemed good. 20:40:13 on a call. Will read scrollback later. 20:40:18 ok, its not really nova specific 20:40:30 its just generic openstack specific really 20:40:43 maybe i shouldn't mention individual services 20:41:08 I did the read _very_ quickly. 20:41:11 np 20:41:12 :) 20:42:13 ok that covers my topics i think, ekarlso- i think has been working with billingstack and has been in touch also, so +1 there 20:42:15 thx ekarlso- :) 20:42:27 #topic open-discuss 20:42:42 and the vote that ivan wanted, which might not be much of a controversy, ha 20:43:16 harlowja, do you know when speaking submissions get accepted/rejected? 20:43:25 hmmm, kebray not sure 20:43:47 that would be useful to know i think, ha 20:43:54 I'm looking for it. 20:44:08 #startvote change __call__() for tasks -> execute()? Yes, No, Maybe 20:44:09 Begin voting on: change __call__() for tasks -> execute()? Valid vote options are Yes, No, Maybe. 20:44:10 Vote using '#vote OPTION'. Only your last vote counts. 20:44:17 ^ https://review.openstack.org/#/c/44008/ 20:44:18 harlowja: Error: "https://review.openstack.org/#/c/44008/" is not a valid command. 20:44:24 #link https://review.openstack.org/#/c/44008/ 20:44:30 #vote Maybe 20:44:35 i am fine with either... 20:44:37 #vote Yes 20:44:55 since i'm fine with seeing how it works, and i think __call__ might have to much inherent meaning 20:45:06 aloo right 20:45:11 s/aloo/all/ 20:45:28 ya, i know ivan wants it, don't think it will be to harmful :) 20:45:35 agreed 20:45:41 i have some issues with execute_with and revert_with though 20:45:50 remote "_with"? 20:45:55 s/remote/remove/ 20:46:12 hmmm 20:46:28 possibly 20:46:36 that way specifying a task will need less typing :) 20:46:54 sure, and i guess when u do execute=blah, its inherent that the '=' means with 20:47:02 hmmmm 20:47:06 right... kind of obvious 20:47:24 and less typing, ha 20:47:29 exactly 20:47:38 seems like that makes sense to me 20:47:46 anyone else wanna vote, ha :-P 20:47:54 haha, vote again 20:48:05 harlowja: Speaking submission notification will happen by email in mid-September. 20:48:09 i can make a patch later, if people are not against it 20:48:10 thx kebray 20:48:18 #endvote 20:48:19 Voted on "change __call__() for tasks -> execute()?" Results are 20:48:20 Maybe (1): changbl 20:48:21 Yes (1): harlowja 20:48:33 :) 20:48:37 harlowja: kebray: if you don't already, some of you folks might want to sit in on our trove meetings. we're talking a lot about scheduled tasks lately 20:48:57 #startvote remove '_with'? Yes, No, Maybe 20:48:58 Begin voting on: remove '_with'? Valid vote options are Yes, No, Maybe. 20:48:59 Vote using '#vote OPTION'. Only your last vote counts. 20:49:01 kevinconway when are those meetings? 20:49:03 kevinconway sure 20:49:12 #link https://wiki.openstack.org/wiki/Meetings/TroveMeeting 20:49:15 #vote Yes 20:49:16 #vote Yes 20:49:22 lol 20:49:26 thx kevinconway 20:49:31 ^_^ 20:49:32 changbl: Error: "_^" is not a valid command. 20:49:40 i'll see if i can make sure i attend kevinconway 20:49:57 scheduled tasks is an interseting area, still unsure if taskflow should get into that yet 20:50:07 or should something be built ontop of taskflow to do the scheduling 20:50:11 harlowja: it's still in the design phase for tasks 20:50:23 sure sure 20:50:29 ok, any more voters?? 20:50:32 but it would be another opportunity to mention taskflow 20:50:37 agreed 20:50:59 #endvote 20:51:00 Voted on "remove '_with'?" Results are 20:51:01 Yes (2): harlowja, changbl 20:51:06 changbl there u go, ha 20:51:07 cool! 20:51:18 * harlowja we need more voters, ha 20:51:22 #action harlowja find more voters 20:51:28 lol 20:51:43 The trove meeting is Wednesdays at 1pm Pacfic time? that can't be... that's the same time as the Heat meeting. 20:51:57 * kebray maybe has his timezone conversations all confused again. 20:52:11 :) 20:52:11 kebray: we meet in #openstack-meeting-alt 20:52:21 20:00 is when this one is, so it would be yesterday 20:52:33 20:00 is also when glances is (right now in #openstack-meeting-alt) 20:52:36 ah, well, then that's the problem for me... I attend the Heat meeting... will have to work on my multitasking skills :-) 20:52:41 everyone choose like 2000 i think 20:53:38 anyways, any more things to chat about? if not then #openstack-state-management 20:54:23 nothing more from me. 20:54:27 ditto 20:54:32 cool, thx kebray changbl :) 20:54:35 till next time! 20:54:47 #endmeeting