Thursday, 2013-08-01

*** IlyaE has joined #openstack-meeting-alt00:11
*** demorris has quit IRC00:16
*** pcm_ has quit IRC00:17
*** IlyaE has quit IRC00:21
*** Riddhi has joined #openstack-meeting-alt00:27
*** IlyaE has joined #openstack-meeting-alt00:39
*** IlyaE has quit IRC00:50
*** bdpayne has quit IRC00:50
*** dina_belova has joined #openstack-meeting-alt00:50
*** NikitaKonovalov has joined #openstack-meeting-alt00:54
*** dina_belova has quit IRC00:55
*** IlyaE has joined #openstack-meeting-alt00:57
*** demorris has joined #openstack-meeting-alt00:58
*** NikitaKonovalov has quit IRC00:58
*** IlyaE has quit IRC01:05
*** pdmars has quit IRC01:08
*** demorris has quit IRC01:13
*** vipul is now known as vipul-away01:26
*** ErikB has quit IRC01:43
*** esp1 has joined #openstack-meeting-alt01:43
*** esp1 has quit IRC01:49
*** dina_belova has joined #openstack-meeting-alt01:52
*** NikitaKonovalov has joined #openstack-meeting-alt01:55
*** dina_belova has quit IRC01:56
*** tanisdl has quit IRC01:57
*** NikitaKonovalov has quit IRC01:59
*** colinmcnamara has joined #openstack-meeting-alt02:02
*** anteaya has quit IRC02:26
*** ErikB has joined #openstack-meeting-alt02:29
*** HenryG has joined #openstack-meeting-alt02:34
*** vipul-away is now known as vipul02:35
*** HenryG has quit IRC02:42
*** SergeyLukjanov has joined #openstack-meeting-alt02:50
*** dina_belova has joined #openstack-meeting-alt02:51
*** ErikB has quit IRC02:54
*** NikitaKonovalov has joined #openstack-meeting-alt02:56
*** NikitaKonovalov has quit IRC03:00
*** SergeyLukjanov has quit IRC03:05
*** dina_belova has quit IRC03:15
*** bdpayne has joined #openstack-meeting-alt03:50
*** bdpayne has quit IRC03:51
*** IlyaE has joined #openstack-meeting-alt03:54
*** NikitaKonovalov has joined #openstack-meeting-alt03:56
*** NikitaKonovalov has quit IRC04:01
*** IlyaE has quit IRC04:15
*** IlyaE has joined #openstack-meeting-alt04:19
*** markmcclain has quit IRC04:36
*** basha has joined #openstack-meeting-alt04:39
*** basha has quit IRC04:46
*** basha has joined #openstack-meeting-alt04:48
*** NikitaKonovalov has joined #openstack-meeting-alt04:57
*** NikitaKonovalov has quit IRC05:01
*** dina_belova has joined #openstack-meeting-alt05:15
*** IlyaE has quit IRC05:15
*** dina_belova has quit IRC05:16
*** lastidiot has quit IRC05:20
*** basha has quit IRC05:24
*** dina_belova has joined #openstack-meeting-alt05:25
*** basha has joined #openstack-meeting-alt05:30
*** IlyaE has joined #openstack-meeting-alt05:37
*** dina_belova has quit IRC05:52
*** basha has quit IRC06:00
*** aignatov has quit IRC06:04
*** aignatov has joined #openstack-meeting-alt06:04
*** NikitaKonovalov has joined #openstack-meeting-alt06:11
*** saurabhs has quit IRC06:15
*** dina_belova has joined #openstack-meeting-alt06:20
*** dina_belova has quit IRC06:25
*** salv-orlando has joined #openstack-meeting-alt06:25
*** mestery_ has joined #openstack-meeting-alt06:34
*** mestery has quit IRC06:36
*** stanlagun has quit IRC06:36
*** stanlagun has joined #openstack-meeting-alt06:44
*** dina_belova has joined #openstack-meeting-alt06:44
*** dina_belova has quit IRC06:50
*** salv-orlando has quit IRC06:50
*** NikitaKonovalov has quit IRC06:53
*** enikanorov-w has quit IRC06:54
*** basha has joined #openstack-meeting-alt06:54
*** enikanorov-w has joined #openstack-meeting-alt06:54
*** dina_belova has joined #openstack-meeting-alt06:55
*** IlyaE has quit IRC06:58
*** NikitaKonovalov has joined #openstack-meeting-alt07:04
*** basha has quit IRC07:07
*** dina_belova has quit IRC07:08
*** aignatov has quit IRC07:09
*** IlyaE has joined #openstack-meeting-alt07:09
*** aignatov has joined #openstack-meeting-alt07:10
*** IlyaE has quit IRC07:14
*** User199 has joined #openstack-meeting-alt07:14
*** User199 has quit IRC07:15
*** Tien has joined #openstack-meeting-alt07:15
*** sergmelikyan has quit IRC07:17
*** Tien has quit IRC07:19
*** Riddhi has quit IRC07:22
*** NikitaKonovalov has quit IRC07:28
*** colinmcnamara has quit IRC07:37
*** NikitaKonovalov has joined #openstack-meeting-alt07:47
*** dina_belova has joined #openstack-meeting-alt07:59
*** SergeyLukjanov has joined #openstack-meeting-alt07:59
*** NikitaKo_ has joined #openstack-meeting-alt08:02
*** NikitaKonovalov has quit IRC08:04
*** NikitaKo_ has quit IRC08:04
*** NikitaKonovalov has joined #openstack-meeting-alt08:04
*** dina_belova has quit IRC08:10
*** dina_belova has joined #openstack-meeting-alt08:28
*** sreshetnyak has joined #openstack-meeting-alt08:40
*** ruhe has joined #openstack-meeting-alt08:44
*** basha has joined #openstack-meeting-alt08:54
*** basha has quit IRC09:01
*** salv-orlando has joined #openstack-meeting-alt09:07
*** salv-orlando has quit IRC09:21
*** NikitaKonovalov has quit IRC09:33
*** NikitaKonovalov has joined #openstack-meeting-alt09:36
*** NikitaKonovalov has quit IRC09:42
*** dina_belova has quit IRC09:57
*** salv-orlando has joined #openstack-meeting-alt10:01
*** ruhe has quit IRC10:04
*** basha has joined #openstack-meeting-alt10:25
*** SergeyLukjanov has quit IRC10:41
*** NikitaKonovalov has joined #openstack-meeting-alt10:42
*** ruhe has joined #openstack-meeting-alt10:45
*** NikitaKonovalov has quit IRC10:46
*** dina_belova has joined #openstack-meeting-alt10:58
*** dina_belova has quit IRC11:02
*** mugsie has left #openstack-meeting-alt11:06
*** NikitaKonovalov has joined #openstack-meeting-alt11:10
*** dina_belova has joined #openstack-meeting-alt11:11
*** SergeyLukjanov has joined #openstack-meeting-alt11:11
*** sergmelikyan has joined #openstack-meeting-alt11:40
*** pcm_ has joined #openstack-meeting-alt11:52
*** HenryG has joined #openstack-meeting-alt11:58
*** pdmars has joined #openstack-meeting-alt12:22
*** ruhe has quit IRC12:32
*** NikitaKonovalov has quit IRC12:43
*** NikitaKonovalov has joined #openstack-meeting-alt12:47
*** ruhe has joined #openstack-meeting-alt12:54
*** ruhe has quit IRC12:59
*** basha has quit IRC13:14
*** basha has joined #openstack-meeting-alt13:21
*** pcm_ has quit IRC13:24
*** pcm_ has joined #openstack-meeting-alt13:25
*** flwang has joined #openstack-meeting-alt13:41
*** Riddhi has joined #openstack-meeting-alt13:48
*** djohnstone has joined #openstack-meeting-alt13:51
*** NikitaKonovalov has quit IRC13:53
*** anteaya has joined #openstack-meeting-alt13:53
*** dhellmann_ is now known as dhellmann13:57
*** markwash has joined #openstack-meeting-alt13:59
*** Riddhi has quit IRC13:59
*** jbresnah has joined #openstack-meeting-alt13:59
markwash#startmeeting glance14:00
*** zhiyan has joined #openstack-meeting-alt14:00
openstackMeeting started Thu Aug  1 14:00:13 2013 UTC and is due to finish in 60 minutes.  The chair is markwash. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: glance)"14:00
openstackThe meeting name has been set to 'glance'14:00
brianrhi mark14:00
markwashbrianr: o/14:00
flwango/14:01
iccha\o14:01
zhiyanops, time changed?14:01
*** SergeyLukjanov has quit IRC14:01
jbresnaho/14:01
nikhilo/14:01
*** NikitaKonovalov has joined #openstack-meeting-alt14:02
flwangmarkwash: what's the agenda today?14:02
markwashgood question!14:02
markwash#topic agenda14:02
*** openstack changes topic to "agenda (Meeting topic: glance)"14:02
markwashI meant to talk about documentation stuff some last week but forgot14:03
*** hemanth_ has joined #openstack-meeting-alt14:03
flwangyep, good topic14:03
flwangthe homework assigned to you :)14:03
markwashand I'd like to review any blueprint progress we've made, give people a chance to highlight reviews14:03
zhiyangood point14:04
markwashso, from me *blueprint progress and *docs14:04
markwashany other items folks want to talk about that aren't covered under bp progress?14:04
*** esheffield has joined #openstack-meeting-alt14:05
markwashokay, maybe we'll think of something along the way14:05
markwash#topic docs14:06
*** openstack changes topic to "docs (Meeting topic: glance)"14:06
markwashso I did finally contact annegentle14:06
jbresnahperhaps a review day/bug squash day14:06
icchamarkwash: and?14:06
markwashand I got a great response, main items were14:07
markwashglance/doc/source should contain stuff for contributors, which is probably a good catchall for design, relevant history, and api spec plans14:07
markwashand openstack/image-api should contain our spec documentation14:07
markwashalso openstack/api-site/ is for api reference, but I'm not really sure what that means apart from the spec. . .14:08
markwashI haven't taken the chance to determine what kind of state those various places are in14:08
flwangmarkwash: i think the api-site is update to date, just need recheck14:08
icchayeah the different between image-api and api-site?14:08
flwangiccha: +1 what's the image-api mean here?14:09
markwashone final thing, before I forget, is openstack/openstack-manuals for installation / administration info, there might be some elements of that we want to contribute to as developers14:10
markwashiccha: I'm as confused as anyone about the distinction14:10
icchai feel like we need a doc day or something, or atleast split the effort. the current document is in different states from some info being incorrect, inconsistent to some latest details being there14:11
*** markmcclain has joined #openstack-meeting-alt14:11
icchadont know if thats stretching it14:11
*** markmcclain has quit IRC14:12
markwashsomething to that tune would make a lot of sense14:12
*** markmcclain has joined #openstack-meeting-alt14:12
markwashit also looks like there's a divide in the image-api repo14:13
flwangso until now, we mentioned: 1.  openstack/doc/source  2. api-site   3. installation/admin doc14:13
markwashwith v1 in docbooks, and v2 in markdown14:13
brianrapi-site looks like a split from openstack-manuals, it's got the quickstart guides in it14:14
brianri wish they would stop moving stuff, it is very confusing14:14
zhiyanbrianr: +114:15
markwashI'm stuggling for a strategy, how we can have the most impact before H is released14:15
*** NikitaKonovalov has quit IRC14:15
icchamarkwash: maybe we should start with the doc/source becuase thats something as devs we can start working on right away14:15
flwangiccha: +114:16
markwashI buy that14:16
icchaand then if we have the meat information, it can be ported to other places14:16
icchathe installation guide may require some additional work tho14:16
brianri will get info into the "operator docs" (which you haven't mentioned!)14:16
flwangI can recheck the api-site14:16
markwashsorry, slightly distracted, cats attacking each other14:17
brianrflwang: +1 , that needs to be updated for the current glanceclient14:17
markwashbrianr: which operator docs?14:17
flwangoperator guide?14:18
brianr https://github.com/openstack/openstack-manuals14:18
brianrit's where the common images properties went for grizzly14:18
markwashokay gotcha14:18
brianrit's where some config info for protected props should go14:18
markwashit might also make sense as a first effort for people to go through and submit patches to remove the out-of-date or incorrect portions of whatever is out there14:18
icchaso apart from the 3 points flwang listed there is a 4. operator docs?14:18
markwashI'm not sure there is a lot of that, but there might be some14:19
markwashoh and, FWIW we're not necessarily on the hook for all of these14:19
markwashhence, starting with the one in our source tree does make a lot of sense14:19
flwangyep14:19
markwashso it sounds like we have some volunteers to look into and assess the ones on our list?14:20
brianryep14:20
flwangflwang:   api-site,     brianr:  operators doc14:20
icchamarkwash: +1 there must be some sort of split up so we dont step on notes. an etherpad or soem sort of communication so we all know whose looking into what14:20
*** boris-42 has joined #openstack-meeting-alt14:21
icchaeven if its just docs in glance repo14:21
boris-42Hi all14:21
boris-42=)14:21
icchahey boris-4214:21
flwangiccha: can you help create a etherpad link to track this?14:21
icchahttps://etherpad.openstack.org/glance_documentation_efforts14:21
flwangthen we can update our status on that and everyone know each other's focus to avoid overlap14:21
flwangcool14:22
flwangthanks14:22
*** lastidiot has joined #openstack-meeting-alt14:22
markwashso did we agree the first step is essentially review?14:23
markwashor is that already done to some extent elsewhere?14:24
flwangmarkwash: i agree the first item we need to do is figuring out the out-of-date stuff14:24
brianri think iccha and eddie already did a review14:25
brianrit's on an etherpad somewhere14:25
markwashah, lord, apparently I'm just completely behind on this issue :-/14:25
icchamarkwash: i think it could be done simelatanesouly. while some ppl identity the purpose/state of soem resources. we need to identify a central source of truth where we start contributing14:25
brianrwe should probably file documentation bugs14:25
icchahttps://etherpad.openstack.org/glance_etherpad_list - etherpad of all glance etherpads . the stuff esheffield and me worked on is like api related14:26
brianrthat way, we won't step on each otehr14:26
markwashbrianr, iccha: +114:26
markwashbrianr: are those like  bugs to a specific project? or just glance bugs with some docs tag?14:27
brianrmarkwash: it's kind of complicated, like take a look at this one:https://bugs.launchpad.net/openstack-manuals/+bug/119547314:28
brianrso it's a bug for openstack-manuals, and it's linked back to glance14:28
*** basha has quit IRC14:28
markwashgotcha, that makes sense14:29
brianri think if we are going to write doc, we do something like that14:29
brianrif we just want to alert the doc people, we put the doc impact tag in the regular bug14:29
icchahmm ok so here is the thing. if we make it too complicated it might deter ppl from going into quick update glance docs mode. so either we need one person owning maintaining this docs bugs and make sure they get tagged and etc or ppl being able to just enter what they re doing and jump onto it.14:29
brianriccha: you are right, it is a PITA14:30
brianrhow about i follow up with Anne and get better instructions about how/where we should file stuff14:30
icchabrianr: sounds good and if meanwhile ppl feel like updating glance/doc/source they are welcome to file a bug and do it?14:30
icchathanks for taking the onerous task brianr :)14:31
markwashokay, we have *some* action items here14:32
brianryes, i think we own glance/doc/source, so we do whatever we want there14:32
icchaso maybe action item is brianr will give us a step by step how to file glance doc bugs and which projects to associate it with?14:32
icchabrianr: +1 on us gettign started with this if we want and keep contributing to glance/doc/source but remembering to file a bug for it before14:33
markwashand flwang, you had said you were going to look into api-site somewhat?14:33
flwangmarkwash: yep, will check if it's update to date and update it14:33
flwangmake sense?14:34
markwashgood14:34
*** lastidiot has quit IRC14:34
markwashlet's move on to blueprints, any objections?14:34
brianrno objections!14:34
icchago for it!14:34
markwash#topic current blueprint progress14:34
*** openstack changes topic to "current blueprint progress (Meeting topic: glance)"14:34
markwashiccha: brianr indicated you would most likely begin work on api protected properties this week14:35
markwashdid that come to pass?14:35
icchamarkwash: some intial work has started https://github.com/isethi/glance/tree/protected_p14:35
markwashtimeline for H-3 still feels reasonable?14:36
markwashiccha: ^^14:36
icchamarkwash: yes def doable14:36
markwashcool14:37
brianranyone interested in protected properties, please take a look at https://wiki.openstack.org/wiki/Glance-property-protections-product and put questions on the FAQ if you have 'em14:37
markwashhow about async work, there are a number of people interested in that. . any progress?14:37
markwashflwang: brianr ^^ ?14:37
brianrflwang and nikhil have been working on an etherpad14:37
icchawhats the link ? :p  need to add it to https://etherpad.openstack.org/glance_etherpad_list14:38
brianri think anyone interested should take a look, and let's meet today or tomorrow?14:38
flwangIhttps://etherpad.openstack.org/havana-glance-requirements14:38
markwashsketching out code design, basically?14:38
brianrhttps://etherpad.openstack.org/havana-glance-requirements14:38
brianrand some use cases to provoke design14:38
nikhilmarkwash: code design, rearch, more use cases(corner cases) etc14:38
nikhilbasically, a careful one to implement so it seems14:39
*** dina_belova has quit IRC14:39
nikhiladded some comments based on convo last night14:39
flwangnikhil: did you touch the task api part?14:39
icchai remember markwash had some poc work on async workers14:39
markwashbrianr: meeting tomorrow could be great14:39
iccha+114:39
nikhilpeople state adding in your names there14:40
flwangiccha: yep, I know that. I'm going to implement it based on markwash's work14:40
brianrflwang: what time zone are you in?14:40
nikhilflwang: brianr markwash iccha we need to divide tasks14:40
flwangBeijing, China14:40
nikhilflwang: he means wrt UTC14:40
flwangso I think UTC+8:0014:40
markwashI'd like to attend as well14:41
brianrwould this time work?14:41
markwashprobably14:42
nikhilbrianr: may be a doodle?14:42
nikhilin UTC :)14:42
flwangbrianr: you can plan it on my night, it's ok14:42
brianrso 14:00 UTC, i think?14:42
markwashFriday night glance party!14:43
flwangthe tomorrow, the same time?14:43
markwashbyob14:43
jbresnahheh14:43
brianretherpad party!14:43
flwangbrianr: it works for me14:43
markwashlet's sort this out after the meeting if we aren't already settled14:43
markwashzhiyan: got any reviews to highlight for us for your various bps?14:44
zhiyanhttps://review.openstack.org/#/c/37222/314:44
zhiyanprobable need flaper87 input: https://review.openstack.org/#/c/37421/114:44
markwashah yes, that second one looks a little stuck14:44
markwashI tried to wrap my head around the issues, and couldn't quite figure it out14:45
markwashbut I know jerdfelt is a smart guy, so I'm a little worried14:45
markwashzhiyan: maybe sometime we can track that down on irc with flaper87 and jerdfelt14:46
markwashtoday or tomorrow. . I think he's in my timezone14:46
*** NikitaKonovalov has joined #openstack-meeting-alt14:46
markwashzhiyan: does that cover it for now?14:46
zhiyanand for Scrubber-refactoring, i'm working on it, as our discussed, but from tomorrow to next Tuesday i need attend a meetings in office, will spend some time on that..14:46
markwashgotcha14:46
markwashjbresnah: any work on super simple quotas?14:46
zhiyanmarkwash: so, sorry, seems i'm not available tomorrow...14:47
markwash(which I forgot to add to the H-3 list, but will fix immediately)14:47
markwashzhiyan: I'll ask flaper about it next I see him then14:47
jbresnahmarkwash: yeah i have a patch out there14:47
jbresnahhttps://review.openstack.org/#/c/3799314:47
jbresnahzhiyan: left some comments that i am addressing, but the general idea is there14:47
jbresnahi also have a nova patch, but that is OT here14:48
jbresnahbut it relates to direct-url work14:48
markwashcool14:48
markwashboris-42: your group has a number of db-related patches out for the oslo db blueprints14:49
*** megan_w has joined #openstack-meeting-alt14:49
markwashcare to mention them or other concerns here?14:49
boris-42markwash not so much=)14:49
boris-42markwash so we are working in whole openstack, we would like to use common DB code in all projects14:49
zhiyanjbresnah: btw, as i mentioned, seems nfs-driver patch maybe drop some challenge in for your 'metadata' idea (which based on file-store) ...14:49
boris-42nova, neutron, cinder, ironic already use this code14:50
boris-42and there is no problems with it14:50
markwashyeah, it looks like there are a number of good fixes in the patches14:50
icchai do know that this will offer some benefits like tpooling and softdelete code. but i am not sure if it has anything missing which glance needs14:50
markwashI'm a little meh on the timestamp mixins. . not sure that DRY really goes that far I guess14:51
boris-42markwash It will14:51
boris-42markwash but it requires migrations14:51
jbresnahzhiyan: perhaps, but there are other filesystem stores besides nfs14:51
zhiyaniccha: +1 ,also interested in that part.14:51
jbresnahand other storage systems besides file, etc14:52
boris-42markwash using oslo db code is just start point14:52
boris-42markwash of global DB cleanup14:52
boris-42markwash such as soft_delete + unique constraints, alembic instead of sqlaclhemy-migrate14:52
*** jmontemayor has joined #openstack-meeting-alt14:52
boris-42markwash and so on14:53
zhiyanseems cool14:53
markwashboris-42: out of curiousity, have you or your team thought much about non-sql based backends?14:53
boris-42we would like to use non-sql, to allow easier way to make now downtime updates14:54
boris-42but it will be soooo hard to put it in OpenStack=)14:54
icchamarkwash: was it you or someone else who was mentioning some sort of db abtraction so its database indepedent14:54
boris-42in nova, cinder we have db.api14:54
boris-42iccha ^14:54
markwashiccha: I have some work in that direction, but not a lot of push from anyone internally to push it further14:54
boris-42it allows us to isolate and implement different backends14:55
*** NikitaKonovalov has quit IRC14:55
boris-42But this thing is connected with unit tests14:55
boris-42and unit tests should be run also with different backends14:55
flwangmarkwash: did you mean we are interested in using no-sql as the db backend? such as mongo? Hbase?14:55
markwashflwang: yes14:55
flwanggreat, I love it14:56
markwashmostly I'm interested in redefining the db abstraction layer so that it doesn't implicitly put business logic in the db drivers14:56
boris-42markwash flwang first of all we should make our tests independent from sqlalchemy14:56
markwashboris-42: I think we have that to a fair degree in glance14:56
markwashanyway, I'd be interested in your perspective on what we do have there14:56
markwashboris-42: any reviews you want to highlight here? I know we can find them as well, so maybe that is enough14:57
nikhilmarkwash: +1 interested in db abstraction (a lot)14:57
boris-42markwash about db abstraction14:57
flwangwe can take some reference from ceilometer14:57
*** ruhe has joined #openstack-meeting-alt14:57
esheffield+1 likewise - I was actually giving some thought to non-sql approaches this morning14:57
boris-42markwash I am not sure that full isolation of logic and DB is good poing14:57
flwangI will do some investigation14:57
markwash#topic open discussion14:57
*** openstack changes topic to "open discussion (Meeting topic: glance)"14:57
boris-42markwash it is clear14:58
markwash(seems like that's what we're doing)14:58
markwashboris-42: there are some definite risks14:58
brianrquick tasks question: so we have asynchronous image tasks, s'pose someone starts an export and then deletes the image, do we:14:58
brianr1 - end task with error, they were stupid14:58
brianr2 - "lock" the image somehow until the task is completed14:58
brianrthis will be a problem for cloning since the glance-to-glance coordination may take some time, you originate task request in region T but the image is in region S, someone else working in your account in image S doesn't know about the clone request, and could delete image before it gets cloned14:58
brianri'm wondering whether something like the task_state that nova has on instances might be needed here?14:58
jbresnahbrianr: there are many issues regarding the asycn task work like that which concern me actually14:58
*** SergeyLukjanov has joined #openstack-meeting-alt14:59
boris-42markwash hmm I have some thoughts about DB code and tests in glance14:59
icchajbresnah: do u see any overlap with staccato?14:59
boris-42markwash as we should make baby steps14:59
bourkewill throw this out, have added a blueprint for porting Swift's ratelimiting to Glance.  Is this something people would be interested in?14:59
markwashbrianr: also, 3 - use reference counts for deletes. . . task would hold a temporary reference. . that might be very strained14:59
flwangbrianr: we need some "lock" just like Nova does14:59
brianrguess we r out of time, should we discuss on mailing list?14:59
flwangor the glance irc channel?15:00
jbresnahiccha: good questions, in some areas yes15:00
boris-42markwash probably it will be best solution to implement db.api as in Nova (it is pretty easy), and remove dependency from sqla in tests?)15:00
jbresnahiccha: but i worry about going to far down the road into becoming a generic job scheduler15:00
brianrflwang: maybe after async worker meeting tomorrow?15:00
nikhilflwang: not on irc15:00
nikhilseems like many poepl are interested15:00
ameade_time15:00
ameade_lol15:00
nikhiland don't want to miss on input15:00
brianrok, i will send out my question to mailing list15:01
flwangnikhil: ok, got15:01
jbresnahbrianr: i think you would need tpo reference count the image15:01
nikhilthanks15:01
nikhilwe need atomicity15:01
flwangit's time to run15:01
markwash#endmeeting15:01
*** openstack changes topic to "OpenStack meetings (alternate)"15:01
openstackMeeting ended Thu Aug  1 15:01:33 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-08-01-14.00.html15:01
nikhiland seems like db is the best/convinient place to do so15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-08-01-14.00.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-08-01-14.00.log.html15:01
*** cp16net is now known as cp16net|away15:02
*** markwash has quit IRC15:04
*** cp16net|away is now known as cp16net15:07
*** lastidiot has joined #openstack-meeting-alt15:09
*** boris-42 has quit IRC15:11
*** NikitaKonovalov has joined #openstack-meeting-alt15:16
*** dina_belova has joined #openstack-meeting-alt15:19
*** zhiyan has left #openstack-meeting-alt15:20
*** tanisdl has joined #openstack-meeting-alt15:25
*** basha has joined #openstack-meeting-alt15:36
*** rnirmal has joined #openstack-meeting-alt15:37
*** markwash has joined #openstack-meeting-alt15:38
*** markwash_ has joined #openstack-meeting-alt15:43
*** markwash has quit IRC15:45
*** markwash_ is now known as markwash15:45
*** dina_belova has quit IRC15:47
*** SergeyLukjanov has quit IRC15:48
*** NikitaKonovalov has quit IRC15:50
*** sarob has joined #openstack-meeting-alt16:01
*** IlyaE has joined #openstack-meeting-alt16:01
*** ruhe has quit IRC16:01
*** tmckayrh has joined #openstack-meeting-alt16:04
*** Riddhi has joined #openstack-meeting-alt16:07
*** jmontemayor has quit IRC16:10
*** jmontemayor has joined #openstack-meeting-alt16:13
*** dina_belova has joined #openstack-meeting-alt16:20
*** basha has quit IRC16:22
*** saurabhs has joined #openstack-meeting-alt16:22
*** SergeyLukjanov has joined #openstack-meeting-alt16:25
*** saurabhs has left #openstack-meeting-alt16:28
*** jmontemayor has quit IRC16:32
*** jmontemayor has joined #openstack-meeting-alt16:35
*** ruhe has joined #openstack-meeting-alt16:39
*** esp has joined #openstack-meeting-alt16:39
*** cp16net is now known as cp16net|away16:44
*** NikitaKonovalov has joined #openstack-meeting-alt16:46
*** sarob has quit IRC16:49
*** sarob has joined #openstack-meeting-alt16:49
*** NikitaKonovalov has quit IRC16:51
*** bourke has quit IRC16:51
*** jmontemayor has quit IRC16:52
*** pdmars has quit IRC16:53
*** sarob has quit IRC16:54
*** ruhe has quit IRC16:56
*** esp has left #openstack-meeting-alt16:58
*** ben_duyujie has joined #openstack-meeting-alt17:03
*** boris-42 has joined #openstack-meeting-alt17:05
*** NikitaKonovalov has joined #openstack-meeting-alt17:13
*** sarob has joined #openstack-meeting-alt17:20
*** vipul is now known as vipul-away17:21
*** sarob has quit IRC17:25
*** vipul-away is now known as vipul17:31
*** ben_duyujie has quit IRC17:31
*** ben_duyujie has joined #openstack-meeting-alt17:33
*** dina_belova has quit IRC17:43
*** mattf has joined #openstack-meeting-alt17:44
*** IlyaE has quit IRC17:45
*** sarob has joined #openstack-meeting-alt17:51
*** Nadya has joined #openstack-meeting-alt17:52
*** IvanBerezovskiy has joined #openstack-meeting-alt17:54
*** sarob has quit IRC17:56
SergeyLukjanovsavanna meeting will be here in 7 minutes17:57
*** vipul is now known as vipul-away17:58
*** dmitryme has joined #openstack-meeting-alt17:58
*** _crobertsrh has joined #openstack-meeting-alt17:58
*** NikitaKonovalov has quit IRC18:02
*** aignatov_ has joined #openstack-meeting-alt18:02
*** NikitaKonovalov has joined #openstack-meeting-alt18:03
*** vipul-away is now known as vipul18:03
*** ErikB has joined #openstack-meeting-alt18:04
*** benl_ has joined #openstack-meeting-alt18:05
*** Nadya_ has joined #openstack-meeting-alt18:05
*** pdmars has joined #openstack-meeting-alt18:05
*** akuznetsov has joined #openstack-meeting-alt18:05
*** Nadya has quit IRC18:06
SergeyLukjanovhowdy folks, I think we can start the meeting18:06
aignatov_hi18:06
SergeyLukjanov#startmeeting savanna18:06
openstackMeeting started Thu Aug  1 18:06:59 2013 UTC and is due to finish in 60 minutes.  The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot.18:07
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:07
*** openstack changes topic to " (Meeting topic: savanna)"18:07
openstackThe meeting name has been set to 'savanna'18:07
SergeyLukjanov#topic Agenda18:07
SergeyLukjanov#info News / updates18:07
SergeyLukjanov#info Action items from the last meeting18:07
SergeyLukjanov#info General discussion18:07
*** openstack changes topic to "Agenda (Meeting topic: savanna)"18:07
SergeyLukjanov#topic News / updates18:07
*** openstack changes topic to "News / updates (Meeting topic: savanna)"18:07
aignatov_whos around beside me and Sergey? ;)18:07
*** IlyaE has joined #openstack-meeting-alt18:07
mattfi am18:08
tmckayrhme too18:08
SergeyLukjanov#info Savanna 0.2.1 released has been released with bunch of bug fixes and improvements18:08
dmitrymeme here18:08
aignatov_cool18:08
SergeyLukjanov#link http://lists.openstack.org/pipermail/openstack-dev/2013-July/012747.html18:08
*** ben_duyujie has quit IRC18:08
SergeyLukjanov^^ announcement of 0.2.1 release with details18:08
SergeyLukjanov#link https://wiki.openstack.org/wiki/Savanna/ReleaseNotes/0.2.118:08
SergeyLukjanov^^ release notes18:08
mattfcongrats on getting it out!18:08
SergeyLukjanovHDP plugin has been postponed to be polished and released in 0.2.2 version18:09
SergeyLukjanovI mean HDP plugin release18:09
SergeyLukjanov#info active work started on both EDP and scaling component18:10
SergeyLukjanov#info we are working now on implementing conductor abstraction18:10
*** benl__ has joined #openstack-meeting-alt18:11
SergeyLukjanovaignatov_, akuznetsov, are there any updates on EDP side?18:11
aignatov_ok, my updates about EDP. I mostly worked this week on Oozie service integration into vanilla Plugin18:11
SergeyLukjanovand Nadya too, sorry18:11
aignatov_it's done i think18:11
akuznetsovfirst version of REST API for EDP was merged to trunk18:11
*** cp16net|away is now known as cp16net18:12
aignatov_Oozie integration code is already merged18:12
*** benl_ has quit IRC18:12
aignatov_also I put dib elements of oozie installation18:12
Nadya_on this week I worked on workflow.xml helper. Initial version will be on review tomorrow18:12
aignatov_#link https://review.openstack.org/#/c/39671/18:12
akuznetsovalso we plan to interact with cluster via Oozie and created a simple REST client for Oozie18:13
aignatov_got reasonable comment frrom matt already))18:13
akuznetsovit also merged to the trunk18:13
aignatov_mattf, thx, I will do wget and tar installation18:13
aignatov_waiting also Ivan's comments18:13
mattfyeah, minor stuff. you should plow forward.18:13
aignatov_also I upload compiled oozie.tar.gz library to our CDN18:14
SergeyLukjanovtmckayrh, do you have any updates?18:14
Nadya_there are some differences in workflow.xml between hive, pig and mapreduce jobs so I think it would be useful to write helpers for all this things18:14
*** jbresnah has left #openstack-meeting-alt18:15
aignatov_its here18:15
aignatov_#link http://a8e0dce84b3f00ed7910-a5806ff0396addabb148d230fde09b7b.r31.cf1.rackcdn.com/oozie-3.3.2.tar.gz18:15
tmckayrhI am working on learning SqlAlchemy/Flask usage in savanna as a precursor to supporting Swift in the Job Source component18:15
tmckayrhI added some notes to the Savanna EDP api draft etherpad yesterday.18:15
tmckayrhThere may be a mistake in the sequence diagrams having to do with job code retrieval18:16
aignatov_could someone post a link here to etherpad?)18:16
tmckayrhAlso, I wonder if we should change terminology slighly18:16
SergeyLukjanovtmckayrh, we are now working on rewriting db-related code to make it more consistent, btw we'll help to port changes if you'll have questions18:16
tmckayrhyes, hold on...18:16
tmckayrh#link https://etherpad.openstack.org/savanna_API_draft_EDP_extensions18:16
aignatov_tmckayrh, thx18:17
_crobertsrhI'm working on the UI for Job Sources.  commenting out the actual api calls until they are ready to go.  Seems to be going well so far, but I have yet to bring anything very "dynamic" to the UI yet.18:17
Nadya_tmckayrh, if you have questions about swift integration please post your question in irc. I dealt with swift in savanna18:18
SergeyLukjanovtmckayrh, _crobertsrh, folks, I remember that you have several concerns yesterday?18:18
tmckayrhmy terminology question is as follows:  "Job Source" means a storage facility for jobs.  But "source" often means "code" as well.  So "job source" could be ambiguous.18:18
benl__I have a little question about that draft. I hope im not missing anytihng. You create a job execution by specifying a cluster ID. why doesnt the GET method doesnt specify the used cluster?18:19
*** ruhe has joined #openstack-meeting-alt18:19
SergeyLukjanovabout Job Source naming and scm18:19
akuznetsovfor pig and hive source and code will be the same18:19
*** mestery_ is now known as mestery18:20
tmckayrhSo this is where it starts to get confusing :)   Suppose we have Pig and Hive jobs stored in a git repository18:20
tmckayrhThe "Job Source" is the git, as I see it.  The Job Source component manages information about the git repository and how to access it.18:21
tmckayrhFiles in the git are "job source code"18:21
SergeyLukjanovbenl__, am I understand you correctly that we need to have cluster_id in job?18:21
benl__I meant job execution18:22
SergeyLukjanovbenl__, thx, it's a good point18:22
*** sarob has joined #openstack-meeting-alt18:22
benl__:)18:22
tmckayrhSo for example, maybe "Job Source Component" could be "Job Depot Component" or similar.18:22
akuznetsovI added the cluster_id to the job execution object18:22
SergeyLukjanovakuznetsov, thx18:23
aignatov_thx18:23
*** sreshetnyak has quit IRC18:24
tmckayrhSergeyLukjanov, the other issue we chatted about is that the draft API had "Hive" as a type in the Job Source Object example, but I changed it to "Swift".  It seems to me that "type" for that object should be git, svn, mercurial, swift, hdfs, internal (for the savanna db), etc.18:24
SergeyLukjanovwhat are you think about "Job Origin"?18:24
tmckayrhtype is describes the storage facility, not what is stored there18:24
*** sreshetnyak has joined #openstack-meeting-alt18:24
tmckayrhI like Job Origin18:24
_crobertsrhJob Origin works for me18:24
SergeyLukjanovakuznetsov, aignatov_, Nadya_?18:25
SergeyLukjanov#vote Rename "Job Source" to "Job Origin"18:25
SergeyLukjanovit's not working O_O18:25
SergeyLukjanov#startvote Rename "Job Source" to "Job Origin"18:26
openstackUnable to parse vote topic and options.18:26
tmckayrhSo would we rename "Job Source Component" to "Job Origin Component" as well as the classes defined there?18:26
akuznetsovtmckayrh possible we should have a two types in Job Source components one of type there job is stored and second is the type of job like HIve, Pig etc.18:26
tmckayrhakuznetsov, could be.  A single repo could store multiple types, though, so maybe a list?  My git can contain anything :)18:27
SergeyLukjanov#startvote Rename "Job Source" to …? "Job Depot", "Job Origin"18:27
openstackBegin voting on: Rename "Job Source" to …? Valid vote options are , Job, Depot, Job, Origin, .18:27
openstackVote using '#vote OPTION'. Only your last vote counts.18:27
*** sarob has quit IRC18:27
tmckayrhI'm thinking the facility type is helpful for finding plugins, etc.18:27
SergeyLukjanovoooops18:27
SergeyLukjanov#undo18:27
openstackRemoving item from minutes: <ircmeeting.items.Link object at 0x22d9110>18:27
SergeyLukjanov#endvote18:27
openstackVoted on "Rename "Job Source" to …?" Results are18:27
SergeyLukjanovlet's not use voting :)18:28
Nadya_what about Job Home?18:28
* tmckayrh laughs18:28
tmckayrhHome is also good.18:28
SergeyLukjanov#startvote Rename "Job Source" to …? JobDepot, JobOrigin, JobHome18:28
openstackBegin voting on: Rename "Job Source" to …? Valid vote options are JobDepot, JobOrigin, JobHome.18:28
openstackVote using '#vote OPTION'. Only your last vote counts.18:28
ruheso, there are two things here "Job Source" where the actual code resides. And Job Storage where we'll compiled jar files, Pig scripts, etc, etc18:28
dmitrymeto me, origin is better18:28
SergeyLukjanovlooks like it's working good18:28
ruhe*we'll keep compiled18:28
dmitryme#vote JobOrigin18:28
_crobertsrh#vote JobOrigin18:29
NikitaKonovalov#vote JobOrigin18:29
SergeyLukjanov#vote JobOrigin18:29
Nadya_#vote JobHome18:29
ruhe#vote JobStorage18:29
openstackruhe: JobStorage is not a valid option. Valid options are JobDepot, JobOrigin, JobHome.18:29
*** sarob has joined #openstack-meeting-alt18:29
aignatov_ruhe, I'm just thinking about the same question)18:29
tmckayrh#vote JobOrigin18:29
akuznetsovI removed type from Job Source object and two fields storage_type and job_type18:29
aignatov_#vote JobHome18:29
akuznetsov#vote JobDepot18:29
*** sarob has quit IRC18:30
SergeyLukjanov#endvote18:30
openstackVoted on "Rename "Job Source" to …?" Results are18:30
openstackJobDepot (1): akuznetsov18:30
openstackJobOrigin (5): tmckayrh, NikitaKonovalov, dmitryme, _crobertsrh, SergeyLukjanov18:30
openstackJobHome (2): Nadya_, aignatov_18:30
SergeyLukjanov+ JobStorage: ruhe18:30
aignatov_ok, let it be JobOrigin)18:30
SergeyLukjanovlooks like we name it Job Origin :)18:30
*** sarob has joined #openstack-meeting-alt18:31
SergeyLukjanovtmckayrh, what about SCM?18:31
tmckayrhso please check my understanding.  based on ^^, the Job Origin Component will manage the registration of Job Origins.  We can define Job Origins there.  It can also interact with plugins for particular origin types so that raw, executable job script code can be retrieved from a particular Job Origin (which may be an scm storing jobs of multiple types like Pig, Hive, jar, oozie, etc)18:31
aignatov_belt__, do akuznetsov's changes resolve your question about cluster_id in job execution?18:32
benl__yeah, looks good now :)18:33
ruheshold JobOrigin manage different storages for the jobs, like Swift, Gluster, HDSF etc?18:33
tmckayrhSergeyLukjanov, I was wondering yesterday if we define each supported SCM as it's own job origin type.  So, rather than have a single type "SCM" we would have "git, mercurial, etc" as distinct job origin types.18:34
tmckayrhruhe, I thought that was the intention.18:34
dmitrymetmckayrh: +118:35
_crobertsrhI think that would make it easier UI-wise to know which fields need to be displayed for a given type.  +118:35
dmitrymeI would prefer different types18:35
SergeyLukjanovdmitryme, tmckayrh, +1 for have different types18:35
*** ruhe_ has joined #openstack-meeting-alt18:36
ruhe_the second question: should it also support different build systems: mvn, gradle, ant, make … ?18:37
SergeyLukjanovruhe_, lein...18:37
tmckayrhI should update the sequence diagram to reflect this thinking, that the Job Manager on execute() pass "job id" and "job origin id" to the Job Origin component, which then handles interacting with plugins to retrieve the actual code.  Agreed?18:37
*** ruhe has quit IRC18:37
ruhe_tmckayrh, agree18:38
akuznetsovruhe_ I think this support is valuable, but this not for this development phase18:38
aignatov_+118:38
tmckayrhruhe_, how does the Job Origin component interact with build?18:38
Nadya_tmckayrh, we will process all pig, hive, jar through oozie, right?18:39
tmckayrhNadya_, yes, we seemed to have consensus on that.  I think it's a great idea.18:39
tmckayrhNadya_, hmm, that brings up a good question....18:40
akuznetsovruhe_ Job Origin can download a job code for execution form build server18:40
Nadya_tmckayrh, yes, great:) just to clarify18:40
tmckayrhIf we autowrap scripts in Oozie, does that happen before the job is stored, or after we retrieve it but before it is submitted to the cluster for execution?18:40
tmckayrhMaybe it's better to wrap on the fly, so that a Hive job can still be a Hive job in case external storage is used by something other than savanna18:41
tmckayrhin other words, wrap it late, just before submission18:41
Nadya_tmckayrh, I'm working on this now. for each job we will create it's own workflow.xml18:41
aignatov_i agree with this idea18:41
akuznetsovtmckayrh it will happen after downloading job code and before job execution18:41
aignatov_on the fly I mean18:41
Nadya_tmckayrh, on the fly, yes18:41
tmckayrh+118:41
ruhe_tmckayrh, akuznetsov, just to clarify. JobOrigin doesn't deal with java source code, or any other type of source code. it just works compiled binaries. right?18:42
tmckayrhI don't know the answer to that :)18:42
akuznetsovin this case end use will not need to know the oozie18:42
tmckayrhI was thinking of it as uncompiled code, I admit18:43
Nadya_ruhe_, +118:43
*** dina_belova has joined #openstack-meeting-alt18:43
akuznetsovruhe_ yes, not  now in this phase, possible in feature we add this functionality18:43
ruhe_compilation from source code is a nice feature, but it should be dealt with by another component18:44
aignatov_ruhe_, i also agree with you, it's complex to build code in this stage of EDP develompment18:44
Nadya_I think it should be separate component for jos sources (binaries I mean)18:44
* tmckayrh has been writing Python too long18:44
*** _crobertsrh has quit IRC18:45
benl__So the user must compile against machines similar to the ones in the cluster?18:45
akuznetsovruhe_, also in case of pig and hive we don't need a compilation18:45
*** vipul is now known as vipul-away18:45
aignatov_i think we can create job compilation and building on top of well-created JobOrigin - the component whish stores binaries, pig scripts, not code right now18:45
SergeyLukjanovbenl__, jars are not OS-dependent18:46
ruhe_akuznetsov, sometimes we need, actually in most cases people are using UDFs for Pig script. UDF is written in java and compiled to jar18:46
dmitrymebut that is true in case of C jobs18:46
benl__Yeah I was refering C jobs18:47
aignatov_yes, benl, also pig and hive scripts are also translated to hadoop job with known structures18:47
Nadya_benl_, SerjeyLukjanov, what about java version?18:47
akuznetsovbenl__ in most cases user need to compile a java and it is cross platform language, so it is not a problem to build jar on windows when run on linux18:47
ruhe_dmitryme, benl__, why would someone write jobs in C? just wondering18:47
dmitrymeNadya_: I think with Java it is simpler: you just need to find JDK of the given version18:48
akuznetsovbenl__ dmitryme this is a not typical use case for Hadoop18:48
dmitrymeruhe_: I don't know, but there is Hadoop Pipes for some reason here18:48
benl__I was thinking of "streaming" jobs18:48
SergeyLukjanovlet's start from the pre-compiled jobs18:48
dmitrymeI guess for faster execution18:48
*** dina_belova has quit IRC18:49
SergeyLukjanovit's ok for the 0.3 version to postpone sources compilation and etc.18:49
akuznetsovbenl_ for streaming API users often use a scripting language like python and perl18:49
benl__Okay, thanks18:50
SergeyLukjanovare there any other questions to discuss or concerns around the EDP topic?18:51
tmckayrhokay, so Job Origins will only store "binary" jobs which can be wrapped in Oozie for now (not that I really need to care about that, I think, in implementing the API)18:51
SergeyLukjanovtmckayrh, I think it'll be ok for now18:52
tmckayrhokay, thanks.  Very helpful meeting for me!18:52
aignatov_+1 tmckayrh18:52
Nadya_agreed18:52
SergeyLukjanovwe should design "source" jobs management in future18:52
ruhe_do we have a BP for EDP dashboard?18:53
tmckayrhmaybe we should add a blueprint for "source" management, too18:53
SergeyLukjanovI think nope18:53
akuznetsovruhe_ you means horizon?18:53
SergeyLukjanov(to ruhe)18:53
ruhe_yes18:53
aignatov_tmckayrh, please create the new one18:54
akuznetsovnot yet18:54
SergeyLukjanovtmckayrh, yes, it'll be good to create bp for it18:54
ruhe__crobertsrh, would you do that?18:54
tmckayrhokay18:54
*** dina_belova has joined #openstack-meeting-alt18:54
tmckayrh#action tmckayrh will make a blueprint for an uncompiled source code management component18:54
ruhe_#action _crobertsrh create blueprint for EDP Horizon dashboard (since Robert is working on UI part)18:55
tmckayrhI think we lost crobertsrh but we can assign it18:55
ruhe_sorry (*Chad)18:55
SergeyLukjanovI think that's all areund EDP18:56
SergeyLukjanovaround*18:56
SergeyLukjanov#topic Action items from the last meeting18:56
*** openstack changes topic to "Action items from the last meeting (Meeting topic: savanna)"18:56
SergeyLukjanovthere are two action items18:56
SergeyLukjanovSergey to create an issue to cover image creation for HDP plugin18:56
SergeyLukjanovaignatov to create a blueprint for ubuntu packaging18:56
aignatov_done18:56
SergeyLukjanov#link https://bugs.launchpad.net/savanna/+bug/120624918:56
SergeyLukjanov#link https://blueprints.launchpad.net/savanna/+spec/savanna-in-ubuntu18:56
SergeyLukjanovand we have several minutes before the end of meeting :)18:57
SergeyLukjanov#topic General discussion18:57
*** openstack changes topic to "General discussion (Meeting topic: savanna)"18:57
tmckayrhcan I add actions still?18:57
aignatov_sure18:57
SergeyLukjanovyep, sure18:57
tmckayrh#action tmckayrh will update sequence diagrams and etherpad to show proper flow and the rename of Job Source Component to Job Origin Component18:58
tmckayrhI suppose the blueprint name needs to change too?18:58
tmckayrhIs that easy to do?18:58
ruhe_it's easy18:58
ruhe_but you might not have permissions. i'm not sure18:59
tmckayrhthat's what I was wondering.18:59
SergeyLukjanovtmckayrh, just ping me if you will have any questions18:59
benl__If its alright with everyone I'd like to have a go at the PKI bp. I assume you expect it to be used as a middleware in the same way its done in Swift?18:59
akuznetsovtmckayrh I have a permissions you can assign this action to me18:59
tmckayrhokay19:00
tmckayrh#action akuznetsov will rename the Job Source Component to Job Origin Component19:00
tmckayrhthanks!19:00
SergeyLukjanovbenl__, PKI tokens are not working now with Savanna now19:00
tmckayrhoops, I meant in the blueprint19:00
SergeyLukjanovbenl__, we doesn't dig into it19:00
SergeyLukjanovbenl__, feel free to investigate/fix it19:01
SergeyLukjanovwe out of time for today...19:01
benl__Alright19:01
SergeyLukjanovlet's move to the #savanna channel19:01
SergeyLukjanovthanks folks!19:01
SergeyLukjanov#info JFYI you can always use openstack-dev@lists.openstack.org mailing lists and #savanna irc channel to find us and ask your questions19:02
SergeyLukjanov#endmeeting19:02
*** openstack changes topic to "OpenStack meetings (alternate)"19:02
openstackMeeting ended Thu Aug  1 19:02:08 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-08-01-18.06.html19:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-08-01-18.06.txt19:02
openstackLog:            http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-08-01-18.06.log.html19:02
*** tmckayrh is now known as tmckay_latelunch19:04
*** IvanBerezovskiy has left #openstack-meeting-alt19:04
*** mattf has left #openstack-meeting-alt19:04
*** sarob has quit IRC19:09
*** aignatov_ has quit IRC19:11
*** tmckay_latelunch is now known as tmckay19:17
*** tmckay is now known as tmckayrh19:17
*** NikitaKonovalov has quit IRC19:18
*** vipul-away is now known as vipul19:18
*** boris-42 has quit IRC19:19
*** boris-42 has joined #openstack-meeting-alt19:20
*** NikitaKonovalov has joined #openstack-meeting-alt19:21
*** akuznetsov has quit IRC19:22
*** benl__ has quit IRC19:24
*** dina_belova has quit IRC19:29
*** benl_ has joined #openstack-meeting-alt19:31
*** NikitaKonovalov has quit IRC19:35
*** NikitaKonovalov has joined #openstack-meeting-alt19:36
*** rnirmal has quit IRC19:36
*** benl__ has joined #openstack-meeting-alt19:38
*** benl_ has quit IRC19:42
*** dina_belova has joined #openstack-meeting-alt19:44
*** ruhe_ has quit IRC19:45
*** benl__ has quit IRC19:52
*** sreshetnyak has quit IRC20:01
*** cp16net is now known as cp16net|away20:06
*** dina_belova has quit IRC20:06
*** benl_ has joined #openstack-meeting-alt20:07
*** dina_belova has joined #openstack-meeting-alt20:08
*** cp16net|away is now known as cp16net20:12
*** Nadya_ has quit IRC20:13
*** dina_belova has quit IRC20:18
*** rnirmal has joined #openstack-meeting-alt20:19
*** jmontemayor has joined #openstack-meeting-alt20:22
*** pcm_ has quit IRC20:29
*** HenryG has quit IRC20:30
*** Riddhi has quit IRC20:30
*** IlyaE has quit IRC20:33
*** boris-42 has quit IRC20:38
*** cp16net is now known as cp16net|away20:43
*** jmontemayor has quit IRC20:46
*** jmontemayor has joined #openstack-meeting-alt20:47
*** cp16net|away is now known as cp16net20:48
*** IlyaE has joined #openstack-meeting-alt20:50
*** vipul is now known as vipul-away20:52
*** jmontemayor has quit IRC20:54
*** megan_w has quit IRC21:00
*** enikanorov has quit IRC21:00
*** SergeyLukjanov has quit IRC21:00
*** benl_ has quit IRC21:01
*** enikanorov has joined #openstack-meeting-alt21:05
*** vipul-away is now known as vipul21:05
*** IlyaE has quit IRC21:06
*** benl_ has joined #openstack-meeting-alt21:06
*** enikanorov_ has joined #openstack-meeting-alt21:07
*** enikanorov has quit IRC21:09
*** demorris has joined #openstack-meeting-alt21:11
*** NikitaKonovalov has quit IRC21:12
*** venkatesh has joined #openstack-meeting-alt21:14
*** djohnstone has quit IRC21:16
*** dmitryme has quit IRC21:21
*** dina_belova has joined #openstack-meeting-alt21:29
*** dina_belova has quit IRC21:33
*** venkatesh has quit IRC21:37
*** zane has joined #openstack-meeting-alt21:37
*** zane has quit IRC21:37
*** zane has joined #openstack-meeting-alt21:37
*** zane has quit IRC21:44
*** ben_duyujie has joined #openstack-meeting-alt21:47
*** tmckayrh has left #openstack-meeting-alt21:53
*** pcm_ has joined #openstack-meeting-alt21:55
*** pcm_ has quit IRC21:56
*** pcm_ has joined #openstack-meeting-alt21:57
*** NikitaKonovalov has joined #openstack-meeting-alt22:13
*** rnirmal has quit IRC22:15
*** NikitaKonovalov has quit IRC22:17
*** lastidiot has quit IRC22:21
*** aignatov has quit IRC22:25
*** aignatov has joined #openstack-meeting-alt22:26
*** nmakhotkin has quit IRC22:28
*** plomakin has quit IRC22:29
*** plomakin has joined #openstack-meeting-alt22:29
*** demorris has quit IRC22:32
*** benl_ has quit IRC22:32
*** benl_ has joined #openstack-meeting-alt22:32
*** Riddhi has joined #openstack-meeting-alt22:38
*** nmakhotkin has joined #openstack-meeting-alt22:42
*** IlyaE has joined #openstack-meeting-alt22:45
*** IlyaE has quit IRC22:52
*** IlyaE has joined #openstack-meeting-alt22:53
*** IlyaE has quit IRC22:55
*** benl_ has quit IRC22:55
*** salv-orlando has quit IRC23:02
*** NikitaKonovalov has joined #openstack-meeting-alt23:13
*** NikitaKonovalov has quit IRC23:18
*** benl_ has joined #openstack-meeting-alt23:26
*** benl_ has quit IRC23:33
*** pdmars has quit IRC23:36
*** lastidiot has joined #openstack-meeting-alt23:52

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!