20:03:32 <harlowja> #startmeeting openstack-state-management
20:03:33 <openstack> Meeting started Thu Mar  6 20:03:32 2014 UTC and is due to finish in 60 minutes.  The chair is harlowja. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:03:34 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
20:03:36 <harlowja> hmmm, is meeting bot dead :-/
20:03:37 <openstack> The meeting name has been set to 'openstack_state_management'
20:04:10 <changbl> hi
20:04:11 <openstack> harlowja: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.
20:04:12 <iv_m_> hi hi
20:04:15 <harlowja> hey, think i got disconnected, or something
20:04:15 <akarpinska-home> hi
20:04:16 <harlowja> or freenode is back under DOS :-/
20:04:17 <harlowja> not sure
20:04:19 <iv_m_> network problems
20:04:20 <harlowja> could be
20:04:51 <harlowja> k, guess its going already, anyway
20:05:06 <harlowja> #topic last-agenda
20:05:06 <harlowja> http://eavesdrop.openstack.org/meetings/openstack_state_management/2014/openstack_state_management.2014-02-27-20.00.html
20:05:23 <harlowja> i'm still working on mine, been busy with a little other stuff this week :)
20:05:43 <harlowja> busy mainly cause hosting https://etherpad.openstack.org/p/tripleo-icehouse-sprint :)
20:06:32 <harlowja> #action harlowja draft ML post for workers and jobboard
20:06:43 <harlowja> #action harlowja report back on oslo!
20:06:49 <harlowja> akarpinska-home did u do your action item?
20:06:51 <harlowja> ;)
20:07:24 <akarpinska-home> yes, if you tell about the vacation
20:07:48 <harlowja> ya
20:07:49 <harlowja> :)
20:08:29 <akarpinska-home> 100% completed
20:08:31 <harlowja> lol
20:08:37 <harlowja> +2
20:09:13 <harlowja> #topic reviews-for-0.2
20:09:13 <iv_m_> now we see who's working)
20:09:24 <harlowja> lol
20:09:48 <harlowja> so afaik, akarpinska-home has the bulk of reviews, around the retry controller work
20:09:57 <harlowja> seems like thats almost all ready to go
20:10:42 <akarpinska-home> iv_m?
20:10:42 <harlowja> and then other various small cleanup ones that would be good also, and iv_m_ work on the URI adjustments
20:10:53 <iv_m_> ya, one last loooong look from me left, and i hope i will not find anything wrong
20:11:17 <harlowja> k, akarpinska-home are u ok with that for 0.2, or do u want to do any other further stuff?
20:11:54 <akarpinska-home> I'm ok
20:11:59 <akarpinska-home> docs left
20:12:33 <harlowja> k
20:12:38 <harlowja> sounds great
20:13:07 <harlowja> anything else i am missing, stans work would be great, but doesn't seem critical (and he's working on it also)
20:14:12 <akarpinska-home> he found problems with some transfers
20:14:33 <harlowja> akarpinska-home those are fixed in the cleanup reviews?
20:14:43 <harlowja> *if u know
20:14:43 <akarpinska-home> no
20:15:25 <harlowja> hmmm, do u recall what the transfer problem was?
20:16:02 <akarpinska-home> I don't know, he told he was working on it
20:16:39 <harlowja> kk
20:16:39 <harlowja> np
20:16:41 <harlowja> thats fine
20:16:47 <akarpinska-home> he tested different protocols that kombu supports
20:17:04 <akarpinska-home> some of them don't work
20:17:20 <iv_m_> *for some of them his code does not work
20:17:31 <akarpinska-home> yes
20:17:58 <harlowja> kk, guess lets wait a little and maybe he can drop on IRC (or i guess he's working on it currently anyway)
20:18:12 <iv_m_> we were talking about it today, i think we'll have partial solution for 0.2 and we'll see what we can do next
20:18:15 <harlowja> not releasing today anyway, but would be interested in the issue he had
20:18:24 <harlowja> k
20:18:56 <iv_m_> if u interested i can try to elaborate on that later, on open-discuss or after meeting
20:19:11 <harlowja> np
20:19:14 <harlowja> sounds good
20:19:59 <harlowja> next topic then :) keep up the reviewing! ;)
20:20:10 <harlowja> #topic integration progress
20:20:28 <harlowja> so didn't work out getting a meeting early this week, but guess we can do a short one
20:21:20 <harlowja> akarpinska-home for icehouse cinder has the refactored code work correct? still pretty basic usage of taskflow though
20:21:57 <harlowja> i believe also glance has there tasks api (not using taskflow, although afaik they want to)
20:22:09 <akarpinska-home> I'm in progress, get a timeout to finish taskflow stuff
20:22:13 <harlowja> np
20:22:20 <harlowja> thinking we can all jump in and help :)
20:22:31 <harlowja> changbl glance might be a nice integration point and good one to do also
20:22:56 <harlowja> and i can help out with akarpinska-home and cinder
20:23:17 <changbl> harlowja, sounds good
20:23:24 <harlowja> although everyone i believe is in FF right now, which is ok, its good time to start discussing anyway
20:23:34 <changbl> FF?
20:23:46 <iv_m_> feature freeze
20:23:50 <changbl> k
20:24:07 <harlowja> changbl i believe https://wiki.openstack.org/wiki/Glance-tasks-api is up to date, but nikhil___ and others might be able to be contacted and see whats there in icehouse (i haven't checked recently)
20:24:33 <harlowja> can start all that fun around seeing what is lacking in taskflow, how glance could use it and all
20:25:00 <harlowja> iv_m_ do u want to do that with changbl, might be useful also if u have time?
20:25:25 <harlowja> nova i think is still a little early to figure out yet (and alex is still working there on seeing what he can get accomplished, likely not in icehouse)
20:25:48 <iv_m_> if there anything i can help with, i'll be glad to
20:25:55 <harlowja> cool
20:26:16 <nikhil___> harlowja: we are in the glance meeting right now, however would like to provide with any information that is needed
20:26:23 <harlowja> nikhil___ great, thx!
20:26:45 <harlowja> nikhil___ just was discussing how we should start discussing with the glance folks about tasks and stuff, and seeing how to integrate (and when and all that)
20:26:51 <nikhil___> harlowja: we do need task flow like support sometime in the future however, not in i-3
20:26:58 <harlowja> nikhil___ of course :)
20:27:10 <harlowja> sounds great nikhil___
20:27:15 <nikhil___> harlowja: absolutely, we should target this for j-1/2
20:27:19 <nikhil___> cool
20:27:23 <harlowja> thx!
20:28:03 <harlowja> akarpinska-home ok with u, can split both of our times trying to continue working with the cinder folks, seems like a good way to do it (since both of us have worked with them)
20:28:17 <harlowja> continue keeping the momenutm and stuff there
20:28:26 <akarpinska-home> ok
20:28:55 <harlowja> cool
20:29:12 <akarpinska-home> now cinder flows are in different files, we can work together
20:29:13 <harlowja> think a good target maybe for next week is to just get some initial etherpads flowing between both teams
20:29:37 <harlowja> with something like, what exists currently, what taskflow can offer, maybe a basic idea of how
20:29:39 <harlowja> that seem reasonable?
20:30:42 <harlowja> (if not this week, maybe the next few weeks, peoples time depending)
20:31:19 <akarpinska-home> are you about cinder or about taskflow?
20:31:26 <harlowja> both :)
20:31:56 <akarpinska-home> our ideas what to do and what is done?
20:32:01 <harlowja> just sorta thinking etherpads with some cinder/glance plans (maybe even heat, although that one might be more heat folks dependent)
20:32:12 <harlowja> akarpinska-home right, with some involvement with the glance/cidner teams also :)
20:32:25 <akarpinska-home> ok
20:32:46 <harlowja> cool
20:33:18 <harlowja> sound ok iv_m_ changbl ?
20:33:51 <changbl> harlowja, so the glance team agreed to use taskflow right?
20:34:46 <harlowja> changbl i think they are fine with that, in using it
20:35:08 <harlowja> it will though involve working together to make sure its all fine and goes smoothly
20:35:19 <harlowja> and so-on
20:35:30 <changbl> any API for us to start with?
20:35:33 <changbl> glance API
20:36:05 <harlowja> likely, that will be part of the investigation period i think, nikhil___  and markwash would likely know (although i think they are in there irc meeting in -alt right now)
20:37:04 <changbl> ok, wonder what I should in detail. Go to implement an example API and see the response?
20:38:43 <harlowja> i think to start it can be more of just figuring out whats there (discussing with the glance folks), maybe seeing it in action (setting up glance for icehouse), checking out the docs, and thinking and writing up where taskflow can fit in the glance picture,
20:39:26 <nikhil___> harlowja: can we please discuss the use cases a bit on Monday?
20:39:41 <harlowja> thats fine with me :)
20:39:51 <nikhil___> we have a sync up meeting tomorrow when we will know the remaning pieces to target and get a clear picture
20:39:55 <harlowja> k
20:40:20 <harlowja> changbl seem ok?
20:40:36 <changbl> sure, let me know the time for monday meeting. maybe i can join
20:40:41 <iv_m_> nikhil___, harlowja are u talking about some meeting on monday, or just #openstack-state-management?
20:41:07 <harlowja> could be, seems undecided yet iv_m_
20:41:14 <harlowja> could be in #openstack-glance ?
20:42:34 <harlowja> lets figure that out afterwards i think, shouldn't be a problem
20:42:54 <harlowja> #topic documentation
20:42:58 <harlowja> so iv_m_  all yours :)
20:43:09 <iv_m_> ya, i'll try to be quick
20:43:10 <iv_m_> so
20:43:20 <iv_m_> #link we have docs at http://docs.openstack.org/developer/taskflow/ which are generated via sphinx
20:43:23 <iv_m_> #link and bp for improving them https://blueprints.launchpad.net/taskflow/+spec/sphinx-docs
20:43:26 <iv_m_> #link and docs on wiki https://wiki.openstack.org/wiki/TaskFlow
20:43:29 <iv_m_> the question is, what should go to wiki and what should go to shpinx
20:43:51 <iv_m_> imo, wiki is for general concepts, tips and tricks and general design explanations, while things that are needed for reference should go to sphinx doc
20:44:29 <harlowja> iv_m_ i agree, so examples would be the main movers right? engine types and backend descriptions and such would also move?
20:46:03 <iv_m_> we may want to have e.g some high-level desciription of engine types still on wiki, and sphinx should provide list of configuration parameters and such things
20:46:09 <harlowja> k
20:46:26 <harlowja> that seems fine with me
20:46:42 <iv_m_> i also thought we should movet things like https://wiki.openstack.org/wiki/TaskFlow/States_of_Task_and_Flow, but akarpinska-home said we should not
20:46:55 <iv_m_> *that's why i raised the question here basically
20:47:11 <harlowja> hmmm
20:47:32 <iv_m_> for things like states of tasks  i have additional concern: every time code changes we should update the page describing states
20:47:36 <iv_m_> wiki page effectively becomes a changelog, while sphinx docs can be easily kept in sync with code
20:47:40 <harlowja> ya, i'm sort of leaning to that being developer docs
20:47:46 <harlowja> akarpinska-home yt
20:48:06 <harlowja> since its really more of an internal detail that would be nicer to just keep in sync with code (automatically if we can)
20:48:50 <iv_m_> i've seen sphinx has graphvis plugin...
20:48:54 <harlowja> ah, nice
20:49:22 <akarpinska-home> I thought that we should describe states on wiki because it is visible for user
20:50:00 <iv_m_> and i said that our users are developers, so they look at developers docs, too
20:50:02 <harlowja> sure, but seems like most developers would be the target readers of it?
20:50:04 <akarpinska-home> maybe we should leave a brief description on wiki, but move graphs to dev docs
20:50:49 <iv_m_> ya, brief description and more words on why states are important and what they may be used for
20:51:00 <harlowja> k, that seems fair
20:51:03 <iv_m_> and that note on 3-d party states
20:51:36 <harlowja> k, lets try that, sound ok?
20:51:51 <harlowja> move anything we think is more developer centric to developer docs
20:51:53 <iv_m_> k, that seems solved, and we can move to next agenda item)
20:51:57 <harlowja> kk
20:52:09 <harlowja> #topic volunteer for oslo security team
20:52:27 <harlowja> so chatting with doug, he'd appreciate if someone from taskflow was on the oslo security team
20:52:34 <harlowja> *some core from taskflow
20:52:40 <harlowja> for potentially any security issues
20:52:49 <harlowja> in general or possibly just releated to taskflow
20:52:50 <harlowja> https://wiki.openstack.org/wiki/Security/How_To_Contribute
20:53:45 <iv_m_> interesting
20:54:02 <harlowja> dhellmann yt
20:54:09 <dhellmann> hi
20:54:11 <harlowja> hey
20:54:19 <harlowja> so discussing the security volunteer stuffs :)
20:54:58 <harlowja> so i was thinking that someone could desire to do this, if not i can (but thought it'd be nice to see if anyone else would want to also)
20:55:18 <dhellmann> yeah, 1-2 is fine, but I need at least 1
20:55:50 <dhellmann> we don't want a huge list, keep in mind this is just the "initial contact" and others can be pulled in as needed
20:55:56 <harlowja> sure
20:56:02 <dhellmann> and it's not like you're on call or something -- no pagers :-)
20:56:07 <harlowja> dhellmann phew, lol
20:56:29 <iv_m_> i could do that too, if noone else really wants, and if it does not mean attending oslo meetings on firday is not mandatory
20:56:50 <dhellmann> no, I don't think it will mean attending any regular meetings
20:57:02 <dhellmann> certainly not for oslo itself
20:57:21 <dhellmann> if we have any issues to deal with, I would expect to coordinate closely, but on a case by case basis
20:57:25 <harlowja> iv_m_ i'm ok with doign it also, just thinking someone might be interested thats all :)
20:58:26 <harlowja> iv_m_ do u want to try it out then, see how it goes (if not ok, thats fine, i can do it also)
20:58:56 <iv_m_> k, if noone objects, write me as volonteer, and we'll see how it goes
20:59:13 <harlowja> i'm fine with that :)
20:59:49 <harlowja> dhellmann sound ok with u, iv_m_ a smart guy and all
20:59:49 <harlowja> :)
21:00:21 <dhellmann> sure, just send me the launchpad ids so I can add you to the contact team
21:00:30 <harlowja> k, sounds good
21:00:32 <harlowja> and time up
21:00:32 <harlowja> ack
21:00:45 <harlowja> more in #openstack-state-management, to be continued next time!
21:00:59 <harlowja> sorry folks, cutting short
21:00:59 <harlowja> #endmeeting