Tuesday, 2015-12-08

*** avarner has quit IRC00:00
*** salv-orl_ has quit IRC00:03
*** salv-orlando has joined #openstack-meeting-400:09
*** May-meimei has quit IRC00:18
*** mbound_ has quit IRC00:18
*** sdake has joined #openstack-meeting-400:20
*** May-meimei has joined #openstack-meeting-400:20
*** yamamoto has joined #openstack-meeting-400:26
*** yamamoto_ has joined #openstack-meeting-400:29
*** yamamoto has quit IRC00:32
*** yamamot__ has joined #openstack-meeting-400:32
*** ashtokolov has quit IRC00:32
*** aglarendil has quit IRC00:32
*** patrickeast has quit IRC00:32
*** milo_raofei__ has quit IRC00:32
*** raofei has quit IRC00:32
*** yamamoto_ has quit IRC00:34
*** dougwig has quit IRC00:35
*** dougwig has joined #openstack-meeting-400:36
*** stanchan has quit IRC00:36
*** yamamot__ has quit IRC00:37
*** banix has joined #openstack-meeting-400:37
*** Swami has quit IRC00:37
*** u_kozat has joined #openstack-meeting-400:41
*** u_kozat has quit IRC00:45
*** Sukhdev has joined #openstack-meeting-400:56
*** Sukhdev has quit IRC00:57
*** sdake has quit IRC01:10
*** armax has quit IRC01:17
*** aglarendil has joined #openstack-meeting-401:18
*** ashtokolov has joined #openstack-meeting-401:18
*** mbound_ has joined #openstack-meeting-401:19
*** coolsvap has quit IRC01:23
*** nikhil_k has joined #openstack-meeting-401:23
*** mbound_ has quit IRC01:24
*** gchamoul has quit IRC01:24
*** nikhil has quit IRC01:25
*** salv-orlando has quit IRC01:25
*** gchamoul has joined #openstack-meeting-401:25
*** coolsvap has joined #openstack-meeting-401:25
*** Sukhdev has joined #openstack-meeting-401:28
*** Prithiv has quit IRC01:34
*** baoli has joined #openstack-meeting-401:36
*** Prithiv has joined #openstack-meeting-401:38
*** patrickeast has joined #openstack-meeting-401:39
*** Prithiv has quit IRC01:48
*** raofei has joined #openstack-meeting-401:55
*** milo_raofei__ has joined #openstack-meeting-401:55
*** sridhar_ram has quit IRC02:06
*** Sukhdev has quit IRC02:11
*** bobh has joined #openstack-meeting-402:12
*** prashantD has quit IRC02:19
*** s3wong has quit IRC02:23
*** tfukushima has joined #openstack-meeting-402:26
*** itisha has quit IRC02:26
*** bobh has quit IRC02:40
*** May-meimei has quit IRC02:50
*** iyamahat has quit IRC02:51
*** yamahata has quit IRC02:51
*** bpokorny_ has joined #openstack-meeting-402:52
*** baoli has quit IRC02:55
*** jgjhgsonchn88523 has joined #openstack-meeting-402:56
*** bpokorny has quit IRC02:56
*** bpokorny_ has quit IRC02:57
*** bobh has joined #openstack-meeting-403:17
*** shuquan has joined #openstack-meeting-403:23
*** julim has quit IRC03:25
*** shuquan has quit IRC03:28
*** yamamoto has joined #openstack-meeting-403:29
*** salv-orlando has joined #openstack-meeting-403:29
*** shuquan has joined #openstack-meeting-403:31
*** salv-orlando has quit IRC03:34
*** jgjhgsonchn88523 has quit IRC03:49
*** bobh has quit IRC03:50
*** bobh has joined #openstack-meeting-403:50
*** bpokorny has joined #openstack-meeting-403:52
*** bpokorny has quit IRC03:52
*** iyamahat has joined #openstack-meeting-403:52
*** bpokorny has joined #openstack-meeting-403:52
*** jgjhgsonchn88523 has joined #openstack-meeting-403:57
*** baoli has joined #openstack-meeting-404:01
*** bobh has quit IRC04:02
*** jgjhgsonchn88523 has quit IRC04:04
*** darrenc is now known as darrenc_afk04:06
*** tfukushima has quit IRC04:11
*** tfukushima has joined #openstack-meeting-404:14
*** tfukushima has quit IRC04:20
*** shuquan has quit IRC04:25
*** shuquan has joined #openstack-meeting-404:26
*** cfarquhar has quit IRC04:34
*** baoli has quit IRC04:37
*** iyamahat has quit IRC04:38
*** banix has quit IRC04:39
*** darrenc_afk is now known as darrenc04:42
*** shuquan has quit IRC04:50
*** ozstacker_ has quit IRC04:50
*** yamahata has joined #openstack-meeting-404:54
*** cfarquhar has joined #openstack-meeting-404:54
*** cfarquhar has quit IRC04:54
*** cfarquhar has joined #openstack-meeting-404:54
*** numans has joined #openstack-meeting-404:59
*** numans has quit IRC05:04
*** numans has joined #openstack-meeting-405:05
*** numans has quit IRC05:09
*** MarkAtwood has joined #openstack-meeting-405:10
*** fawadkhaliq has joined #openstack-meeting-405:12
*** tfukushima has joined #openstack-meeting-405:20
*** amotoki has joined #openstack-meeting-405:20
*** Sukhdev has joined #openstack-meeting-405:26
*** shuquan has joined #openstack-meeting-405:30
*** numans has joined #openstack-meeting-405:39
*** gsagie has left #openstack-meeting-405:40
*** shuquan has quit IRC05:46
*** shuquan has joined #openstack-meeting-405:47
*** amotoki has quit IRC05:48
*** numans has quit IRC05:50
*** numans has joined #openstack-meeting-405:51
*** sdake has joined #openstack-meeting-405:51
*** bpokorny has quit IRC05:56
*** dims has quit IRC05:57
*** yamahata has quit IRC05:58
*** yamahata has joined #openstack-meeting-405:59
*** yamahata has quit IRC06:04
*** moshele_1 has joined #openstack-meeting-406:07
*** moshele_1 has quit IRC06:08
*** kebray has quit IRC06:08
*** iyamahat has joined #openstack-meeting-406:08
*** yamahata has joined #openstack-meeting-406:09
*** iyamahat has quit IRC06:13
*** shuquan has quit IRC06:15
*** Sukhdev has quit IRC06:20
*** dims has joined #openstack-meeting-406:20
*** javeriak has joined #openstack-meeting-406:30
*** amotoki has joined #openstack-meeting-406:30
*** tfukushima has quit IRC06:31
*** stanchan has joined #openstack-meeting-406:31
*** tfukushima has joined #openstack-meeting-406:31
*** shuquan has joined #openstack-meeting-406:38
*** salv-orlando has joined #openstack-meeting-406:49
*** partner has quit IRC06:52
*** partner has joined #openstack-meeting-406:53
*** salv-orlando has quit IRC06:54
*** EvgenyF has joined #openstack-meeting-406:57
*** [1]evgenyf has joined #openstack-meeting-406:57
*** [2]evgenyf has joined #openstack-meeting-407:02
*** javeriak has quit IRC07:03
*** javeriak has joined #openstack-meeting-407:04
*** [1]evgenyf has quit IRC07:04
*** dims has quit IRC07:11
*** sambetts-afk has quit IRC07:13
*** MarkAtwood has quit IRC07:19
*** sambetts has joined #openstack-meeting-407:19
*** MarkAtwood has joined #openstack-meeting-407:19
*** shuquan has quit IRC07:22
*** nkrinner has joined #openstack-meeting-407:22
*** shuquan has joined #openstack-meeting-407:25
*** dims has joined #openstack-meeting-407:31
*** javeriak has quit IRC07:36
*** javeriak has joined #openstack-meeting-407:37
*** javeriak has quit IRC07:37
*** fawadkhaliq has quit IRC07:41
*** javeriak has joined #openstack-meeting-407:41
*** fawadkhaliq has joined #openstack-meeting-407:42
*** dims has quit IRC07:52
*** shuquan has quit IRC07:53
*** shuquan has joined #openstack-meeting-407:54
*** May-meimei has joined #openstack-meeting-408:01
*** stanchan has quit IRC08:01
*** stanchan has joined #openstack-meeting-408:02
*** stanchan has quit IRC08:03
*** sridhar_ram has joined #openstack-meeting-408:04
*** matrohon has joined #openstack-meeting-408:07
*** sridhar_ram has quit IRC08:08
*** javeriak has quit IRC08:14
*** sdake has quit IRC08:15
*** MarkAtwood has quit IRC08:34
*** zeih has joined #openstack-meeting-408:36
*** FallenPegasus has joined #openstack-meeting-408:36
*** yamahata has quit IRC08:43
*** Prithiv has joined #openstack-meeting-408:47
*** paul-carlton2 has joined #openstack-meeting-408:58
*** javeriak has joined #openstack-meeting-409:06
*** mbound_ has joined #openstack-meeting-409:10
*** javeriak_ has joined #openstack-meeting-409:12
*** javeriak has quit IRC09:12
*** shakamunyi has joined #openstack-meeting-409:13
*** shuquan has quit IRC09:20
*** shakamunyi has quit IRC09:23
*** purp has quit IRC09:23
*** shuquan has joined #openstack-meeting-409:23
*** Prithiv has quit IRC09:24
*** purp has joined #openstack-meeting-409:26
*** macsz has quit IRC09:39
*** macsz has joined #openstack-meeting-409:46
*** Prithiv has joined #openstack-meeting-409:57
*** macsz has quit IRC10:00
*** macsz has joined #openstack-meeting-410:01
*** tfukushima has quit IRC10:10
*** tfukushima has joined #openstack-meeting-410:11
*** tfukushima has quit IRC10:14
*** fawadkhaliq has quit IRC10:21
*** fawadkhaliq has joined #openstack-meeting-410:21
*** salv-orlando has joined #openstack-meeting-410:25
*** salv-orlando has quit IRC10:30
*** yamamoto has quit IRC10:48
*** shuquan has quit IRC10:51
*** masterbound has joined #openstack-meeting-411:02
*** mbound_ has quit IRC11:05
*** salv-orlando has joined #openstack-meeting-411:06
*** amotoki has quit IRC11:07
*** paul-carlton2 has quit IRC11:11
*** salv-orlando has quit IRC11:14
*** paul-carlton2 has joined #openstack-meeting-411:25
*** masterbound has quit IRC11:29
*** javeriak has joined #openstack-meeting-411:29
*** mbound_ has joined #openstack-meeting-411:29
*** javeriak_ has quit IRC11:30
*** javeriak_ has joined #openstack-meeting-411:33
*** javeriak has quit IRC11:34
*** yamamoto has joined #openstack-meeting-411:36
*** yamamoto has quit IRC11:41
*** yamamoto has joined #openstack-meeting-411:44
*** yamamoto has quit IRC11:44
*** sdake has joined #openstack-meeting-411:50
*** yamamoto has joined #openstack-meeting-411:53
*** yamamoto has quit IRC11:53
*** dshakhray has joined #openstack-meeting-412:00
*** masterbound has joined #openstack-meeting-412:05
*** mbound_ has quit IRC12:08
*** javeriak_ has quit IRC12:09
*** javeriak has joined #openstack-meeting-412:10
*** zeih has quit IRC12:10
*** zeih has joined #openstack-meeting-412:11
*** Kevin_Zheng has joined #openstack-meeting-412:13
*** fawadkhaliq has quit IRC12:14
*** shuquan has joined #openstack-meeting-412:36
*** fawadkhaliq has joined #openstack-meeting-412:37
*** fawadkhaliq has quit IRC12:40
*** fawadkhaliq has joined #openstack-meeting-412:40
*** shuquan has quit IRC12:41
*** yamamoto has joined #openstack-meeting-412:51
*** bobh has joined #openstack-meeting-413:11
*** amotoki has joined #openstack-meeting-413:15
*** dims has joined #openstack-meeting-413:16
*** sdake has quit IRC13:17
*** klamath has joined #openstack-meeting-413:18
*** klamath has joined #openstack-meeting-413:19
*** baoli has joined #openstack-meeting-413:22
*** baoli_ has joined #openstack-meeting-413:25
*** bobh has quit IRC13:27
*** baoli has quit IRC13:28
*** javeriak_ has joined #openstack-meeting-413:29
*** baoli_ has quit IRC13:31
*** baoli has joined #openstack-meeting-413:32
*** javeriak has quit IRC13:33
*** itisha has joined #openstack-meeting-413:33
*** baoli has quit IRC13:37
*** baoli has joined #openstack-meeting-413:37
*** yamamoto has quit IRC13:40
*** baoli has quit IRC13:42
*** bunting has joined #openstack-meeting-413:46
*** igordcard has joined #openstack-meeting-413:46
*** yamamoto has joined #openstack-meeting-413:46
*** mhayden has quit IRC13:53
*** mhayden has joined #openstack-meeting-413:53
*** woodard has joined #openstack-meeting-413:55
*** julim has joined #openstack-meeting-413:55
flaper87#startmeeting Glance Drivers14:00
openstackMeeting started Tue Dec  8 14:00:34 2015 UTC and is due to finish in 60 minutes.  The chair is flaper87. 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 Drivers)"14:00
openstackThe meeting name has been set to 'glance_drivers'14:00
rosmaitao/14:00
flaper87#topic Agenda14:00
*** openstack changes topic to "Agenda (Meeting topic: Glance Drivers)"14:00
ativelkovo/14:00
flaper87yoooooo!14:00
jokke_o/14:00
*** mclaren_ has joined #openstack-meeting-414:00
flaper87#link https://etherpad.openstack.org/p/glance-drivers-meeting-agenda14:00
flaper87Courtesy Glance Drivers' meeting reminder: nikhil_k, flaper87, sigmavirus24, rosmaita, mclaren, dhellmann, jokke_14:01
*** dandruta has joined #openstack-meeting-414:01
*** yamamoto has quit IRC14:01
flaper87just like last week, I have quite some lag in my connection today so, I'm sorry if it takes me a bit to reply14:01
flaper87that said, we have a packed agenda for tody14:01
flaper87let's get to it14:01
flaper87#topic https://review.openstack.org/#/c/249950/4 This could do with some eyes on it (bunting)14:01
*** openstack changes topic to "https://review.openstack.org/#/c/249950/4 This could do with some eyes on it (bunting) (Meeting topic: Glance Drivers)"14:01
*** yamamoto has joined #openstack-meeting-414:02
flaper87#link https://review.openstack.org/#/c/249950/414:02
* flaper87 should have fixed the topic title14:02
flaper87sorry14:02
flaper87:D14:02
buntingI also emailed the mailing list about that, telling nova about it.14:02
flaper87yeah, I think I took a look at it already, not sure if my comments synced14:02
flaper87Have other drivers read through it already?14:02
mclaren_I have14:03
rosmaitanot yet14:03
flaper87mclaren_: cool, comments?14:03
mclaren_It would be nice to get someone from nova to have a quick look, although that needn't be a blocker14:03
flaper87ok, what about we get those comments and sync back next week14:03
mclaren_I think it's good. Needs buy in from other services for it to be put to use14:04
flaper87that way rosmaita and nikhil_k can take a look at it14:04
rosmaitaok14:04
flaper87btw, as ageneral rule, it'd be awesome if all drivers could go through the agenda before the meeting so that we have already some knowledge about the specs we'll discuss14:04
flaper87this is not a complain, btw14:04
rosmaitait is a good suggestion though14:05
flaper87just something I normally do for this and other meetings and it's worked well for me14:05
flaper87ok, moving on14:05
nikhil_khey, sorry I am a bit late. I was out and met some friends on way back.14:05
flaper87#topic Swift driver re-authentication spec: https://review.openstack.org/#/c/24868114:05
*** openstack changes topic to "Swift driver re-authentication spec: https://review.openstack.org/#/c/248681 (Meeting topic: Glance Drivers)"14:05
*** nikhil_k is now known as nikhil14:05
flaper87I assume that's you, mfedosin14:05
*** pmesserli has joined #openstack-meeting-414:05
flaper87that's the second part of the trusts spec14:06
flaper87or better, that's the glance-store part of it14:06
ativelkovmfedosin is on PTO today, he'll be back next week14:06
flaper87ativelkov: ah right, he mentioned that. Thanks for the reminder14:06
*** javeriak_ has quit IRC14:06
flaper87I know we're heads down on image process but these specs won't take much time to review and provide feedback too14:07
flaper87to*14:07
jokke_so if we have trust we cannot use that towards swift?14:07
flaper87I think this spec would be nice to have as it's a follow-up on the trusts one14:07
flaper87jokke_: we can and that's the plan, AFAIK14:08
*** chem has joined #openstack-meeting-414:08
flaper87we just asked to split this into 2 specs because this part belongs to glance-store14:08
flaper87and it depends on the glance one14:08
flaper87I'll create a list of specs prio so we can focus on reviewing those14:09
flaper87of course , you can contribute to that list14:09
flaper87:D14:09
jokke_would be great if spec actually mentioned that :P14:09
flaper87I've seen more specs coming up now and we need to start focusing on few of them14:09
nikhilagreed14:09
flaper87jokke_: it does, it mentions the trust id in several parts14:09
nikhilit's quite unclear on what the eventual goal is14:09
flaper87jokke_: oh, you mean the dependency14:09
flaper87yeah14:10
flaper87lets comment on the spec :D14:10
jokke_++14:10
flaper87The glance one mentioned there would be a specific spec for glance_sotre14:10
flaper87this one doesn't have the reverse reference14:10
nikhilhmm, I did not find in the problem statement. trusts seems to be mentioned in other places14:10
nikhilit does have a ref14:11
nikhillook at line 21814:11
flaper87right but I meant the reference in the problem statement mentioning why this spec is needed and how it depends /elates to the one in glance14:11
flaper87ok, lets put all this on that spec14:12
nikhilagreed, that's needed14:12
flaper87I'm sure mike will address all this comments as soon as he is back14:12
flaper87and if he does it during his PTO, I'll take his place wherever he is and let him take mine as being on PTO would be super cool now :P14:12
flaper87anyway, let's move on14:12
flaper87#topic mage import refactor: https://review.openstack.org/#/c/232371/14:12
*** openstack changes topic to "mage import refactor: https://review.openstack.org/#/c/232371/ (Meeting topic: Glance Drivers)"14:13
flaper87There have been updates but14:13
flaper87today, I believe what we want to discuss is the /v2/bikeshed and /ve/images/{id}/bikeshed thing14:13
flaper87s/ve/v2/14:13
flaper87I expressed my opinion on the spec14:13
flaper87and Stuart has donde the same14:13
mclaren_can I say one thing?14:13
flaper87done*14:13
flaper87mclaren_: NO!14:14
* flaper87 ducks14:14
flaper87mclaren_: of course14:14
mclaren_heh14:14
mclaren_Right now I don't really have a solid proposal for an API for the non-integrated-with-image case14:14
mclaren_More just some thoughts and observations14:14
mclaren_that's it really14:15
mclaren_I do agree with Brian14:15
flaper87ok, so the /v2/bikeshed is a brainstorm14:15
mclaren_well it achieves a specific end14:16
mclaren_that I am interested in14:16
mclaren_I'm going to cut and paste ...14:16
mclaren_Divide your application into distinct features with as little overlap in functionality as possible. The important factor is minimization of interaction points to achieve high cohesion and low coupling.14:16
mclaren_I think doing that has practical benefits14:16
*** banix has joined #openstack-meeting-414:16
flaper87my current opinion is that we shouldn't have it as a separate resource as I mentioned on the spec. In the worst case scenario, we can just add it later rather than doing it now14:17
mclaren_I agree with Brian that we can make a start on other things, eg the Swift case, and let this percolate for a while14:17
nikhilyeah, agree14:17
nikhilif we(glance) are at this point where the resource is a problem14:17
flaper87I do agree with that statement but I disagree on the bikshed being a separate functionality. This is where, I believe, our POV differ w.r.t the bikeshed thing14:18
*** bobh has joined #openstack-meeting-414:18
nikhilI am of opinion that we should leave things be and add a discovery API instead14:18
rosmaitai think the key issue is, is there any reason why an end-user should manipulate the bikeshed?14:18
rosmaitaif not, no need to expose it14:18
jokke_rosmaita: ++14:18
rosmaitabut i think we can get separation of concerns behind the scenes14:18
flaper87right, my opinion is that users shouldn't14:18
flaper87exactly my point14:19
nikhilrosmaita: not right away14:19
jokke_while it might make our job initially easier but is it right tihng to do for user?14:19
nikhiljokke_: ditto14:19
rosmaitanikhil: elaborate?14:19
nikhilrosmaita: I assume that we are all of opinion at this point14:20
mclaren_are we saying that the bikeshed isn't visible to the user at all?14:20
*** paul-carlton2 has left #openstack-meeting-414:20
*** iurygregory has joined #openstack-meeting-414:20
nikhilthat the bikeshed won't be used to store immutable entities14:20
nikhilbasically the input to bikeshed can be changed later14:20
flaper87mclaren_: not as a resource. The endpoint under images is so that data can be uploaded to it14:20
rosmaitanikhil: +1 no immutable entities in bikeshed14:21
flaper87++14:21
nikhilfrom a user experience POV it would help to overwrite on the bikeshed to make multiple failed attempts successful14:21
nikhilso, that is a distributed transation issue14:21
nikhileither we way 1 bikeshed per image record14:21
flaper87I just don't want to have yet another public resource being added t oglance in Mitaka14:21
nikhilor a "single phase" write to bikeshed to enable import14:21
flaper87and I don't think we need it for now14:21
mclaren_can I be honest?14:22
rosmaitaquick question: doug indicated on an earlier patch set that there's no prob requiring a user to delete the Image record upon failure14:22
jokke_nikhil: I see no reason why we couldn't allow user to PUT again to /v2/images/{ID}/bikeshed before calling the import (either initially when noticing failed upload or after first import try has failed)14:22
rosmaitaso no need for retries14:22
flaper87mclaren_: you always are :D14:22
flaper87jokke_: that's one of the goals, yes14:22
*** sdake has joined #openstack-meeting-414:22
rosmaitajokke_: that's what i'm asking, do we want to allow that or just keep it simple?14:22
flaper87at least I remember us talking about this14:22
jokke_rosmaita: for our users it would be the right thing to do14:23
nikhilmclaren_: was saying something14:23
nikhil?14:23
flaper87I think he's writing14:23
flaper87waaaaaaaaaaaaaaaaaaaaaaaaiiiiit for it14:23
jokke_I don't know if it's viable goal initially when we are doing this, but I think we should keep it in mind when we desing this14:23
flaper87:P14:23
rosmaitajokke_: i wonder, because the "hard part" for auser is creating the import call14:24
mclaren_nope, trying to figure out how honest I should be :-)14:24
nikhil:D14:24
nikhilawesome14:24
flaper87hahahaha14:24
flaper87ok14:24
rosmaitamclaren_: +1 for honesty14:24
flaper87mclaren_: just be blunt14:24
flaper87shoot14:24
flaper87we can take it14:24
rosmaita(depending on what you say)14:24
*** yamamoto has quit IRC14:24
jokke_mclaren_: totally ... there's never too big toes to step on14:24
mclaren_tbh, I need to think about the bikeshed not being visible to users, I hadn't expected that14:24
flaper87mclaren_: what do you mean by "not visible" ?14:25
jokke_rosmaita: why would it be the hard part?14:25
nikhilrosmaita: rofl14:25
rosmaitajokke_: most of the configuration is in there14:25
flaper87we've 5mins left and other items on the agenda14:26
nikhilmclaren_: some more elaboration would be awesome14:26
flaper87Can I count on you guys going through them?14:26
nikhilI am liking this direction14:26
flaper87:)14:26
mclaren_flaper87: you can't 'see' it (it's size/checksum) as a user14:26
jokke_which bring's my next question about this spec ... do we want separate spec for our client changes? I've not seen a single word around that yet14:26
nikhilflaper87: ack14:26
mclaren_(I think that's what you meant above)14:26
flaper87mclaren_: mmh, not sure I follow, tbh14:26
rosmaitaok, i will put up a new patch set, i want to get examples of vhd upload resulting in OVA in Glance (as done at rackspace) and also ova -> qcow2 as outlined on the ova conversion spec14:27
nikhilflaper87: etherpad of trello of specs that require earlier feedback14:27
*** yamamoto has joined #openstack-meeting-414:27
nikhilor*14:27
flaper87the bikeshed was never meant to be an external resource for users to consume14:27
flaper87nikhil: working on that as we speak14:27
mclaren_flaper87: so as you envision it a user only knows about an uploaded bikeshed through what - image state?14:27
flaper87rosmaita: wait for my next comment, I'm creating the requied bugs to break this down and start working on the spec14:27
rosmaitaflaper87: ok14:27
nikhilrosmaita: "want to get examples of vhd upload resulting in OVA in Glance"<-like14:28
rosmaitamclaren_: right, image state14:28
rosmaitaall communication via the Image object14:28
flaper87mclaren_: how did you envision this? As far as I know, this is what we've been discussing since before the summit14:28
rosmaitamclaren_: the swift-local would allow "sort of" bikeshed visibility14:28
flaper87honest question14:28
rosmaitasince the blob is in the user's object store account14:29
flaper87just want to makes ure we're on the same page14:29
flaper87make sure*14:29
flaper87ok, 1min left14:29
flaper87lets move to our channel and or comment on the spec14:29
mclaren_we can discuss after the meeting? What do folks think of making a start on the Swift case?14:29
flaper87thanks folks!14:29
flaper87mclaren_: thanks for being critical on the proposal. It's super useful14:30
rosmaitamclaren_: let's discuss in glance channel14:30
flaper87#endmeeting14:30
*** openstack changes topic to "Q&A (Meeting topic: openstack-vahana)"14:30
rosmaitaflaper87: +!14:30
openstackMeeting ended Tue Dec  8 14:30:11 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance_drivers/2015/glance_drivers.2015-12-08-14.00.html14:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance_drivers/2015/glance_drivers.2015-12-08-14.00.txt14:30
openstackLog:            http://eavesdrop.openstack.org/meetings/glance_drivers/2015/glance_drivers.2015-12-08-14.00.log.html14:30
*** fawadkhaliq has quit IRC14:45
*** fawadkhaliq has joined #openstack-meeting-414:46
*** zeih has quit IRC14:47
*** neelashah has joined #openstack-meeting-414:48
*** armax has joined #openstack-meeting-414:50
*** njohnston has joined #openstack-meeting-414:51
*** richm has joined #openstack-meeting-414:52
*** dims_ has joined #openstack-meeting-414:52
*** mdorman has joined #openstack-meeting-414:55
*** dims has quit IRC14:55
*** xarses has joined #openstack-meeting-414:56
*** baoli has joined #openstack-meeting-414:58
*** sbog has joined #openstack-meeting-414:58
*** degorenko has joined #openstack-meeting-414:59
*** Vinsh has joined #openstack-meeting-414:59
*** mkarpin has joined #openstack-meeting-414:59
*** _ody has joined #openstack-meeting-415:00
*** mwhahaha has joined #openstack-meeting-415:00
EmilienM#startmeeting puppet-openstack15:00
openstackMeeting started Tue Dec  8 15:00:12 2015 UTC and is due to finish in 60 minutes.  The chair is EmilienM. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: puppet-openstack)"15:00
openstackThe meeting name has been set to 'puppet_openstack'15:00
mfischhola15:00
mwhahahahi2u15:00
EmilienM#link agenda: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-2015120815:00
iurygregoryhello o/15:00
*** skolekonov_ has joined #openstack-meeting-415:00
EmilienMo/15:00
*** masterbound has quit IRC15:00
degorenkohey o/15:00
skolekonov_o/15:00
Vinsh0_o15:00
claytono/15:00
mkarpino/15:00
chemo/15:00
mentato/15:01
_odyo/15:01
_ody(yawn)15:01
EmilienMlet's start by a couple of announcements!15:01
iurygregory\o/15:01
EmilienM#topic announcements15:01
*** openstack changes topic to "announcements (Meeting topic: puppet-openstack)"15:01
EmilienMthis blueprint has been accepted: Enhance inifile option deprecations15:01
EmilienM#link http://specs.openstack.org/openstack/puppet-openstack-specs/specs/mitaka/config-deprecation-for-inifile-provider.html15:01
richmhello15:01
EmilienMclayton: thanks for this work!15:01
EmilienManother good news for the group, Sofer is now part of puppet-keystone core team! Well done :-)15:02
claytonCongrats :)15:02
xarseso/15:02
chemthanks :)15:02
iurygregorycongrats chem15:02
jasondotstaro/15:02
EmilienMlet's move15:02
EmilienM#topic using reno for release note management15:03
*** openstack changes topic to "using reno for release note management (Meeting topic: puppet-openstack)"15:03
EmilienMI created this topic for discussion15:03
EmilienMthere is a project in OpenStack that is called "reno" and becomes the official way to write release notes"15:03
richmchem: ++15:03
iurygregorynice15:03
richmRNaaS?15:04
EmilienMI spent some time looking at it15:04
EmilienMrichm: lol15:04
iurygregoryhasuhasuahsu15:04
EmilienMI see is 3 possibilities15:04
EmilienM1/ we use reno and enforce each contributions (bugfix, feature, etc) to also edit a release note YAML file15:04
EmilienM2/ we use reno and the release note YAML file can be updated later (by the contributor or someone else)15:05
EmilienM3/ we don't use reno and continue to manually write release notes15:05
EmilienMthe #1 will implies a lot of -1 at the beginning because people would not know they have to do it15:05
*** sigmavirus24_awa is now known as sigmavirus2415:06
EmilienMthe 3/ is not really what is doing other OpenStack projects15:06
claytonI'd vote for 1, with 2 as needed to fix things15:06
EmilienMI propose we go to 2/ with good documentation so people can start contributing themselves15:06
EmilienMclayton: if we go for 1/, I thought some people would get frustrated to have -1 for something they did not have to care before15:06
richm+115:06
iurygregoryi ike 1 but 2 is good15:06
*** numans has quit IRC15:07
claytonEmilienM: I'm also ok with starting with 2 and the goal being 1 over time15:07
xarses2 seems good15:07
EmilienMnote: using reno is an heavy work too, and the automation is not magic, we need to write ONE yaml per bug, per feature, per useful thing in release note.15:07
EmilienMdhellmann: iiuc ^15:07
claytonI think it will probably take some practice to know what really needs release notes.  Not every change will15:07
mwhahahathat sounds awful15:07
EmilienMclayton: yeah, the goal would be 1/15:08
EmilienMmwhahaha: what is awful?15:08
mwhahahathe yaml thing15:08
xarsesI haven't looked at reno, but it seems like it should pull some of this out automatically out of well made commit messages15:08
claytonif you work on puppet and you're not comfortable with yaml, you may have other issues :)15:08
EmilienMexample: https://github.com/openstack/nova/tree/master/releasenotes/notes15:08
mwhahahano the fact you have to create one for every bug, etc15:08
claytonxarses the goal with reno was to have it be outside of commit messages, so that they can change later15:08
mwhahahanot yaml itself15:08
*** baoli has quit IRC15:08
mwhahahai'd assume it'd also be per puppet module as well15:09
xarsesclayton: thats, fine but maybe it should start there. some commit hook or something15:09
mwhahahaso our updates of all the modules would result in a similar number of yamls15:09
EmilienMI think, and that's my proposal: we should start looking in Mitaka for using it in one or two modules15:09
claytonbut that if you cherry-pick a change that includes a release note, that gets backported also15:09
EmilienMdoing 2/ method15:09
EmilienMand see15:09
claytonEmilienM: I think doing it for a limited number of modules is probably a good way to start15:09
*** ntpttr has joined #openstack-meeting-415:09
mwhahahai don't think release notes should be part of the change itself, it would be better to parse the git log and add it after the fact15:09
_odywow really a new yaml file for every commit.  That is indeed horrible.15:09
iurygregoryit will be hard but we can do o/15:10
claytonif we have good success there, we can move to #115:10
*** mbound_ has joined #openstack-meeting-415:10
EmilienM_ody: hence the "heavy work" I was saying15:10
iurygregoryagree with clayton for a limited number of modules15:10
clayton_ody: no, one file for anything that needs to be in release notes15:10
EmilienM_ody: BTW, when I prepared stable/liberty, I spent 3 days reading commit messages15:10
mfischdo other projects do a note on every commit?15:10
claytonlots of changes won't be mentioned in release notes.15:10
EmilienMmfisch: look the example on nova15:10
claytonthe idea is that this is supposed to be a summary, not a copy of the commit log.15:10
mwhahahawould it be better to start enforcing a must have a bug/blueprint per change?15:10
EmilienMit's very new so I think the adoption is not 100% here15:11
_odyEmilienM: Which is why I prefer 1 over 2.  Spread the load.15:11
ntpttrCinder is just starting to adopt it15:11
mwhahahaso we could parse that out to create the release notes15:11
*** IvanBerezovskiy1 has joined #openstack-meeting-415:11
EmilienM_ody: 1/ is the final goal, sure. But we don't want to frustrate our contributors. We need a smooth transition15:11
_odyclayton: How do we judge what is and isn't worthy of a release note? Just guess until we get the hang of it?15:12
mfischup to reviewers?15:12
EmilienMyes15:12
clayton_ody: I think so, we'll just have to develop an eye for it, and I suspect before releases we'd have a patch (or several) to fix the release notes where they don't make sense15:12
EmilienMwe are developpers, we know when we fix a bug or add a feature, isn't?15:12
claytonbut that's still better than spending 3 days reading lots and then still missing things15:12
claytons/lots/logs/15:12
EmilienMclayton: ++15:13
EmilienMso I see we have different opinions here15:13
iurygregory+115:13
EmilienMI would follow-up on the mailing-list15:13
EmilienMand involve Doug who is not here I guess ( dhellmann )15:13
EmilienMmaybe he has some thoughts15:13
EmilienMI'll summarize thoughts here15:14
EmilienMfeel free to participate to the thread :-)15:14
EmilienMwe definitly need to find a way to maintain release notes15:14
EmilienMthat's a lot of time15:14
_odyany chance the reno project provides a commit hook?15:15
EmilienMand automation will help us to scale the number of our modules15:15
xarses_ody: +115:15
xarsesI was asking that too15:15
EmilienM_ody: to do what?15:15
xarsesTo me, thats the only way to make it bearable15:15
xarsespopulate both the commit message and the yaml at the same time15:15
_odySeems pretty straight forward to write the yaml on commit just like "git review" does with change-id.15:16
claytonI do not think the commit message and the release note should have the same content.  they have different audiences.15:16
EmilienMclayton is right15:16
degorenko+115:16
*** fawadkhaliq has quit IRC15:16
EmilienMrelease notes are read by users/operators also15:16
claytonkeep in mind here that the alternative right now is emilien continuing to do all of it.15:16
xarsesyes, but they can be writen at the same time15:16
claytonthere is nothing stopping you from doing them at the same time, in fact that's the preferred workflow15:17
claytonthat the release note yaml file be in the same commit that it describes15:17
EmilienMthe content of the commit message & the release note can be different, that's the point of clayton iiuc15:17
ntpttras someone who recently started contributing, I don't mind writing release notes for patches that would need them tbh15:17
EmilienMntpttr: good feedback15:18
mfischI think most changes would need a release note15:18
EmilienMso if you don't mind, I'll follow a discussion on our mailing list, with a summary of our meeting thoughts15:18
mfischnew fields, deprecations, removals15:18
EmilienMprobably using cross project tag15:19
EmilienM[all] I mean15:19
mfischgood idea15:19
EmilienMI feel like we're not alone in this case15:19
EmilienMbefore I end the topic, anyone has more thoughts?15:19
EmilienMoki15:20
EmilienM#topic open discussion / bugs-review triage15:20
*** openstack changes topic to "open discussion / bugs-review triage (Meeting topic: puppet-openstack)"15:20
EmilienMlike usual, feel free to ask for reviews15:20
EmilienMor raise an outstanding request/bug15:20
EmilienMwe will be happy to help15:20
mfischI'd like to discuss my ML topic from yesterday15:20
chemI have three long standing review15:20
mfischopenstackclient15:20
chemon keystone15:20
mfischchem: you go 1st15:20
chemmfisch: thanks15:21
chemit's about specific domain conf15:21
chemthey add feature, so no backward change15:21
EmilienM#action EmilienM to follow-up on mailing-list about reno15:21
chemhttps://review.openstack.org/#/c/202689/, https://review.openstack.org/#/c/219289/, https://review.openstack.org/#/c/238164/15:21
EmilienMchem: where is release note? (joke)15:21
iurygregorylol15:22
chemthey have been +1/+2 serveral time and rebase countless times15:22
* _ody should have beaker bug fixes in soon15:22
_odyThey passed CI15:22
chemrelease what ?15:22
chemhehe15:22
chem_ody: a long time ago :)15:22
mfischarg no commas in URLs even at the expense of grammar15:22
claytonmfisch you need a better irc client :)15:22
_odychem: I meant my patches. ;)15:23
EmilienMmfisch: stop using windows!15:23
*** blahRus has joined #openstack-meeting-415:23
iurygregorykkkkkk15:23
xarsesEmilienM:  +115:23
EmilienMchem: thanks for adding the patches in our radar15:23
chemthat's it for me :) please help me to get rid of thoses rebases15:23
EmilienMthat's a lot of LOC, I guess it needs more time to review it :-)15:23
iurygregoryi'll try to review chem o/15:24
chemthanks15:24
ntpttrI wouldn't mind getting some eyes on this multiple store configuration in Glance once I go and fix the merge conflict - https://review.openstack.org/#/c/242718/ some feedback on if this is the correct way to deprecate these options while moving them to api.pp would be appreciated15:24
ntpttrI can go ahead and fix the merge conflict after this meeting15:24
EmilienMmfisch: IMHO, we should just use ensure_resource everywhere for this case15:25
EmilienMso the resource can be multiple times in the catalog15:25
claytonEmilienM: what if I want to set package_ensure to something other than the default?  I have to set it everywhere?15:26
mfischI think ensure_packages() in openstackclient class and everyone else just includes it15:26
claytonthat works for me.15:26
EmilienMclayton: in that case we need the conditional and use ::openstacklib15:26
iurygregory+115:26
EmilienMyeah, +115:26
*** bunting has left #openstack-meeting-415:26
mfischconditionally include it like keystone does now?15:27
claytonI don't think we should be managing the resource in 25 different places15:27
EmilienMclayton: did you have time to start a PoC of your blueprint?15:27
claytonthey should just include ::openstacklib::openstackclient15:27
EmilienMclayton: yes, +1 with that15:27
mfischso the vote is to conditionally include it like https://github.com/openstack/puppet-keystone/blob/master/manifests/client.pp#L20-L2615:27
mfischor just include it bare15:27
claytonNo, I've been too busy with docker, docker, docker.15:27
claytonmfisch: bare15:28
claytonno conditional15:28
*** javeriak has joined #openstack-meeting-415:28
mfischlol ok I agree15:28
EmilienMbare looks fine15:28
mfischhah15:28
EmilienMI haven't found time to start looking at multi node jobs15:28
mfischbare means that everyone will need to use hiera to control openstack client15:28
mfischbut its cleaner15:29
EmilienMdegorenko: what is the status of having Fuel CI gating our modules?15:29
degorenkoEmilienM, it is already implemented :)15:29
claytonmfisch: I'm +1 on that for now15:29
mfischclayton: oh sorry, I misunderstood you when you said "no conditional" I read it as "no, conditional"...  I will add it bare15:30
EmilienMdegorenko: I mean, having Fuel jobs in our CI15:30
claytonwe can talk about other approaches later if we actually run into problems with that approach15:30
degorenkoEmilienM, oh, for our modules15:30
mfischneed a review on the main fix: https://review.openstack.org/#/c/254502/15:30
degorenkoi think it's not started yet15:30
EmilienMdegorenko: ok15:30
xarsesEmilienM:  I'll add a topic to the Fuel IRC meeting for it15:31
EmilienMI need review on https://review.openstack.org/252562 and final +A on https://review.openstack.org/252026 https://review.openstack.org/25200315:31
degorenkoEmilienM, i will raise this question in our fuel weekly meeting15:31
EmilienMdegorenko, xarses: thx guys15:31
degorenkoxarses, go 1st :)15:31
EmilienMclayton: is it good time to discuss about keystone/eventlet drop ?15:31
claytonsure15:31
EmilienMI think the first question to me is:15:32
claytonthat's related to work I started yesterday :)15:32
EmilienMshould we still allow people to deploy eventlet in our mitaka cycle?15:32
degorenkowe have one old patch: can you guys review it please: https://review.openstack.org/#/c/220224/15:32
EmilienMor follow keystone and drop it15:32
claytonI don't think that's actually the right question15:32
claytonEmilienM: what you're calling "eventlet" is actually "the way the distro packaged it"15:32
claytonwhich may or may not be eventlet, especially if eventlet is dropped15:32
claytonrunning service keystone start might start it under uwsgi, or nginx, or something completely different15:33
*** neelashah1 has joined #openstack-meeting-415:33
*** neelashah has quit IRC15:33
*** javeriak has quit IRC15:34
*** javeriak has joined #openstack-meeting-415:34
EmilienMclayton: ok15:34
EmilienMclayton: so I guess we don't have much to change then15:34
claytonI'd be willing to rework the existing "eventlet" and apache support to both run under the hooks model I did for designate, heat and nova (under review)15:35
EmilienMclayton: nice15:36
EmilienManything else for today?15:36
mfischwe should consider canceling the meeting xmas week15:37
EmilienMok15:37
EmilienMmfisch: or invite santa claus15:37
mfischand even the week after perhaps15:37
EmilienMsanta cloud?15:37
degorenko:D15:37
EmilienMI'll not cancel it but rather invite Santa Cloud15:37
mfischsanta is still working on keystone v315:38
iurygregoryhsaushaush good idea15:38
claytonaction, emilien to dress up as santa and give out presents?15:38
EmilienMjoking, ok let's cancel it15:38
EmilienMclayton: YEAH !15:38
*** javeriak_ has joined #openstack-meeting-415:38
EmilienM#action EmilienM to dress in Santa Claus for Christmas15:38
EmilienMhave a good day folks!15:38
EmilienM#endmeeting15:38
*** openstack changes topic to "Q&A (Meeting topic: openstack-vahana)"15:38
openstackMeeting ended Tue Dec  8 15:38:34 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:38
openstackMinutes:        http://eavesdrop.openstack.org/meetings/puppet_openstack/2015/puppet_openstack.2015-12-08-15.00.html15:38
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/puppet_openstack/2015/puppet_openstack.2015-12-08-15.00.txt15:38
openstackLog:            http://eavesdrop.openstack.org/meetings/puppet_openstack/2015/puppet_openstack.2015-12-08-15.00.log.html15:38
*** xarses has left #openstack-meeting-415:38
ntpttrthanks!15:38
*** mwhahaha has left #openstack-meeting-415:38
*** ntpttr has left #openstack-meeting-415:38
*** skolekonov_ has left #openstack-meeting-415:38
*** IvanBerezovskiy1 has left #openstack-meeting-415:38
*** javeriak has quit IRC15:39
*** milo_raofei__ has quit IRC15:40
*** raofei has quit IRC15:40
*** raofei_ has joined #openstack-meeting-415:40
*** milo_raofei___ has joined #openstack-meeting-415:40
*** njohnston has quit IRC15:45
*** _ody has left #openstack-meeting-415:45
*** bharathm has joined #openstack-meeting-415:45
*** njohnston has joined #openstack-meeting-415:48
*** njohnston has quit IRC15:48
*** njohnston has joined #openstack-meeting-415:49
*** nkrinner has quit IRC15:53
*** [2]evgenyf has quit IRC15:54
*** EvgenyF has quit IRC15:54
*** johnsom has joined #openstack-meeting-415:55
*** jbratton has joined #openstack-meeting-415:55
*** njohnsto_ has joined #openstack-meeting-415:58
*** codebauss has joined #openstack-meeting-415:58
*** njohnston has quit IRC15:59
mugsie#startmeeting Kosmos16:00
openstackMeeting started Tue Dec  8 16:00:43 2015 UTC and is due to finish in 60 minutes.  The chair is mugsie. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: Kosmos)"16:00
*** sridhar_ram has joined #openstack-meeting-416:00
openstackThe meeting name has been set to 'kosmos'16:00
johnsomo/16:00
*** Bjoern_ has joined #openstack-meeting-416:00
mugsie#topic roll call16:00
*** openstack changes topic to "roll call (Meeting topic: Kosmos)"16:00
johnsomI always jump in too quick...16:01
mugsiexgerman: dougwig courtesy ping16:01
*** richm has left #openstack-meeting-416:01
mugsiejohnsom: isnt that how I ended up as ptl ?16:01
mugsie:D16:01
xgermanyoh16:01
bharathmO/16:01
johnsomCould be....16:02
dougwigo/16:02
jokke_:P16:02
dougwigi think it's that his pubs have better beer.16:02
mugsie#topic Open Discussion16:02
*** openstack changes topic to "Open Discussion (Meeting topic: Kosmos)"16:02
mugsiedougwig: very definitly16:02
mugsiewow, I can not the english today16:02
johnsomYeah, for these meetings I'm on coffee16:02
dougwigeta on some initial code? or suggestions on something that wouldn't step on your initial commit?16:02
mugsieeta  - this week16:03
mugsieI was in meeting rooms the entire week last week16:03
mugsie:(16:03
johnsomI have been watching for it16:03
*** avarner has joined #openstack-meeting-416:03
*** salv-orlando has joined #openstack-meeting-416:03
johnsommeeting rooms == pubs16:03
*** salv-orlando has quit IRC16:03
mugsiemy boss was in town, and that was a massive time suck16:03
mugsiewell, that too :)16:03
*** salv-orlando has joined #openstack-meeting-416:03
mugsiebut - intial albemic stuff would not go amiss16:04
mugsieI am not 100% up to date on that stuiff (we use sqla-migrate)16:04
*** mbound_ has quit IRC16:04
*** yamamoto has quit IRC16:04
mugsieI might dump up the objects as a separate review today16:04
johnsomI have done some stuff with alembic, so if you want to ping me I might be able to help16:06
*** mbound_ has joined #openstack-meeting-416:06
mugsieI ended up going down a rabbithole with the objects (getting oslo.versionedobjects to validate UUIDs is a bigger problem than I thought)16:06
mugsieit turns out nova has things likle "fake_uuid" in their tests16:07
mugsieso turning on UUID validation breaks nova16:07
*** mkarpin has left #openstack-meeting-416:07
mugsiejohnsom: cool, I will ping you in the next day or so16:08
mugsieany other topics ? I am just getting confirmation of which room I am getting in Seatte before sending out the email for the mid cycle16:08
mugsieunfortunatly my boss is jet lagged / ignoring me (both are possible)16:09
dougwigjohnsom, mugsie: i can also do the alembic bit.  which of us is less over-subscribed?  :)16:09
mugsiewell, it ain't me :)16:09
*** yamamoto has joined #openstack-meeting-416:09
johnsomProbably you dougwig16:10
johnsomgrin16:10
mugsiesure johnsom and xgerman have loads of people on their team :)16:11
* mugsie ducks before xgerman throws anything16:11
xgermannot true16:11
dougwigi'll do it.16:11
mugsiecool16:11
* johnsom throws HOS systems at mugsie16:11
mugsieI will split the objects out now, and add them as a single commit16:11
mugsiejohnsom: sweet -  I have been looking for one of these16:11
johnsomSadly me too16:12
xgermannah, Kiall has one…16:12
xgermanI hope you bring that with you to Seattle ;-)16:12
*** fawadkhaliq has joined #openstack-meeting-416:12
mugsieOK, so any more topics before we let the pacific wake up fully?16:12
johnsomAnyway, so code this week.  Two patches, alembic/db might need some help16:12
mugsie++16:12
johnsomSounds good.  Do we have a plan of goals for the mid-cycle?16:13
xgermando we have an ether pad?16:13
mugsienope.https://etherpad.openstack.org/p/kosmos_2016_winter_midcycle_meetup16:14
johnsomgrin16:14
johnsomI got in fast enough to know you just created that.16:14
xgermangreat!!16:14
mugsiejohnsom: ssshhh :P16:14
* mugsie may have edited the URL of the designate one just in time16:15
mugsieideas in there please. Will send offical invite to the ML asap16:15
mugsiejust waiting on barclac16:15
mugsieare we done?16:16
mugsielast chance16:16
xgermanwell, you can always meet at the pub across the street — just saying...16:16
xgermanso send it out...16:16
mugsietrue :)16:16
mugsieok16:17
mugsie#endmeeting16:17
*** openstack changes topic to "Q&A (Meeting topic: openstack-vahana)"16:17
openstackMeeting ended Tue Dec  8 16:17:32 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:17
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kosmos/2015/kosmos.2015-12-08-16.00.html16:17
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kosmos/2015/kosmos.2015-12-08-16.00.txt16:17
openstackLog:            http://eavesdrop.openstack.org/meetings/kosmos/2015/kosmos.2015-12-08-16.00.log.html16:17
mugsietalk to ya'll later16:17
*** johnsom has left #openstack-meeting-416:17
xgermanl8ter16:17
*** jbratton has left #openstack-meeting-416:21
*** baoli has joined #openstack-meeting-416:23
*** galstrom_zzz is now known as galstrom16:23
*** dshakhray has quit IRC16:24
*** salv-orl_ has joined #openstack-meeting-416:26
*** salv-orlando has quit IRC16:29
*** __snake__ has joined #openstack-meeting-416:35
*** yamamoto has quit IRC16:37
*** bpokorny has joined #openstack-meeting-416:38
*** armax has quit IRC16:44
*** sripriya has joined #openstack-meeting-416:45
*** chem has quit IRC16:50
*** armax has joined #openstack-meeting-416:51
*** u_kozat has joined #openstack-meeting-416:51
*** degorenko is now known as _degorenko|afk16:53
*** pbourke has quit IRC16:56
*** pbourke has joined #openstack-meeting-416:56
*** yamahata has joined #openstack-meeting-416:58
*** chem has joined #openstack-meeting-416:58
*** vishwanathj has joined #openstack-meeting-417:01
sridhar_ram#startmeeting tacker17:01
openstackMeeting started Tue Dec  8 17:01:07 2015 UTC and is due to finish in 60 minutes.  The chair is sridhar_ram. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: tacker)"17:01
openstackThe meeting name has been set to 'tacker'17:01
sridhar_ram#topic Roll Call17:01
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"17:01
bobho/17:01
*** brucet has joined #openstack-meeting-417:01
sridhar_ramHi Tackers -- who is here ?17:01
sridhar_rambobh: hi there!17:01
brucetbrucet17:01
vishwanathjo/17:01
*** mdorman has left #openstack-meeting-417:01
sripriyahi17:01
sridhar_ramlets start then...17:02
u_kozatI am here also17:02
*** tbh has joined #openstack-meeting-417:02
sridhar_rammorning everyone!17:02
sridhar_ram... noon, or evening (depending on tz)17:03
tbhmorning sridhar_ram17:03
sridhar_ram#topic Agenda17:03
*** openstack changes topic to "Agenda (Meeting topic: tacker)"17:03
sridhar_ram#link https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_Dec_8.2C_201517:03
*** brucet has quit IRC17:03
sridhar_ram#topic Announcements17:03
*** openstack changes topic to "Announcements (Meeting topic: tacker)"17:03
*** brucet has joined #openstack-meeting-417:03
sridhar_ramWe now have tacker packages in pypi...17:04
vishwanathjcool17:04
sridhar_ram#link  https://pypi.python.org/pypi/tacker/0.1.017:04
*** dandruta has quit IRC17:04
sripriyanice17:04
sridhar_ram#link https://pypi.python.org/pypi/tacker-horizon/0.1.017:04
sridhar_ram#link https://pypi.python.org/pypi/python-tackerclient/0.1.017:04
sridhar_ramthis is based of kilo release17:05
sridhar_ramwe finally got everything in place to make releases..17:05
*** s3wong has joined #openstack-meeting-417:05
*** kebray has joined #openstack-meeting-417:05
s3wonghello17:06
sridhar_ramWill make a liberty release as well sometime soon..17:06
sripriyasridhar_ram:will this be reflected in the tacker launch page also?17:06
sridhar_ram.. we can decide on a time, perhaps mid-Dec ?17:06
*** kebray has quit IRC17:06
sridhar_ramsripriya: not sure, if launchpad will pick up automatically...need to check17:07
*** kebray has joined #openstack-meeting-417:07
sripriyasridhar_ram: ok thanks17:07
sridhar_ramFolks - if you've any pending cherry picks to stable/liberty please do it now!17:07
*** natarajk has joined #openstack-meeting-417:08
sridhar_ramwe should decide on our release strategy ..17:08
*** afveitch has joined #openstack-meeting-417:08
*** natarajk has quit IRC17:09
sridhar_ramour devstack installers can potentially use pypi based tackerclient and tacker-horizon for dependencies moving forward..17:09
*** natarajk has joined #openstack-meeting-417:10
*** santoshk has joined #openstack-meeting-417:10
sridhar_ramany thoughts / suggestions on pypi / pkg releases ?17:10
vishwanathjwhat do other projects do? like monasca, sfc17:10
s3wongnetworking-sfc hasn't been released yet17:11
sridhar_ramvishwanathj: some projects, particularly library projects like tosca-parser, make continuous releases .. every 5-6 weeks17:11
vishwanathjtrying to see if we there is a precedent and can follow best practices17:11
natarajksridhar_ram: I thought pypi jobs can be scheduled automatically along with releases17:11
sridhar_ram"client" projects should also make regular releases...17:11
s3wongbut once you are tagged release: independent, you can release whenever and under whatever frequency as you want17:12
sridhar_ramnatarajk: we are not yet in governance, so release team won't do it for us.. we are on our own17:12
sridhar_rams3wong: we can do the same for us...17:13
s3wongsridhar_ram: yep17:13
sridhar_rambottomline ... we need to move to regular client & horizon releases and tacker repo need to pull them using requirements.txt17:13
s3wongwe are NOT bounded by the half-year release cycle; even if we make it to big tent, as long as we are release:independent17:14
sridhar_rams3wong: true17:14
*** amotoki has quit IRC17:14
sridhar_ramversioning wise 0.1.0 == kilo, 0.2.0 == liberty, 0.3.0 == mitaka ..17:14
sridhar_ram.. for liberty we might do follow 0.2.1 with things like sfc17:15
sridhar_ram*follow-on17:15
*** Swami has joined #openstack-meeting-417:15
sridhar_ramlets move on.. we can talk more on release in future mtgs17:15
sridhar_ram#topic Mitaka Midcycle Plans17:15
*** openstack changes topic to "Mitaka Midcycle Plans (Meeting topic: tacker)"17:15
*** salv-orl_ has quit IRC17:16
sridhar_ramwith many big ticket items in flight - like sfc, enhanced vnf placement, tosca-parser, auto-resource - I thought we shd consider meeting face 2 face17:16
sridhar_ramfor a quick poll - how many of you would be interested in attending ?17:16
santoshksridhar_ram +117:17
natarajk+117:17
sripriya+117:17
bobh+117:17
u_kozat+117:17
vishwanathj+117:17
s3wong+117:17
tbh+117:17
brucet+117:17
sridhar_ramnice ...17:17
sridhar_ramI'll send a doodle pool for some possible dates ..17:18
sridhar_ram.. tentatively, would mid- to- 2nd half of Jan work for most of you ?17:18
*** dshakhray has joined #openstack-meeting-417:19
bobhyes17:19
sripriyasridhar_ram: fine with me17:19
santoshk+117:19
s3wongsounds fine --- at least for now :-)17:19
sridhar_ramwe can take this to finalize in an ML thread..17:19
tbhsridhar_ram, yes17:19
u_kozatI will be traveling Jan 9-1617:20
bobh+117:20
sridhar_ramwe need to find a way for remote attendance, without hampering the benefit of a F2F...17:20
sridhar_ramtbh: you would need a remote dial-in ... ?17:21
tbhsridhar_ram, yeah17:21
*** brucet_ has joined #openstack-meeting-417:21
tbhsridhar_ram, I need some way to connect17:21
*** brucet has quit IRC17:21
sridhar_ramalright.. we can decide the date/time/logistics outside this mtg.17:22
sridhar_ramlets move on...17:22
sridhar_ram#topic Mitaka Blueprint Updates17:22
*** openstack changes topic to "Mitaka Blueprint Updates (Meeting topic: tacker)"17:22
sridhar_ram#topic Enhanced VNF Placement (EVP)17:22
*** openstack changes topic to "Enhanced VNF Placement (EVP) (Meeting topic: tacker)"17:22
sridhar_ramvishwanathj: and gongysh from China has come forward to get this going. I know tbh is also interested in contributing..17:23
sridhar_ramI'm planning to host a one time adhoc / china / india friendly irc meeting on this topic..17:24
tbhsridhar_ram, yes I want to be part of this BP17:24
sridhar_ramit is 1am in Beijing :(17:24
sridhar_ramtbh: sure17:24
*** matrohon has quit IRC17:25
tbhsridhar_ram, is it possible to  have alternate timings each week17:25
tbhlike most of the other openstack projects follow to accommodate all contributors?17:25
sridhar_ramtbh: absolutely.. lets starts with few adhoc meetings and see how it goes17:26
tbhsridhar_ram, sure17:26
sridhar_ramanyone here interested to discuss further on EVP ?17:26
sridhar_rambtw EVP == numa topology awareness + cpu-pinning + pci-passthry + sr-iov...17:27
sridhar_ramplease watchout for a mtg invite and plan to attend..17:28
sridhar_ramlets move on...17:28
brucet_OK. brucet +117:28
sridhar_rambrucet_: sure, bruce17:28
sridhar_ram#topic TOSCA parser updates17:28
*** openstack changes topic to "TOSCA parser updates (Meeting topic: tacker)"17:28
*** mhayden has quit IRC17:28
sridhar_rambobh: any quick updates from your side ?17:28
*** prashantD has joined #openstack-meeting-417:29
bobhI submitted a WIP patchset for the tosca-parser changes and created the BPs for heat-translator and tacker (I think - need to check that one)17:29
*** sdake has quit IRC17:29
bobhThe next big hurdle is the object mappings from TOSCA NFV -> Heat in heat-translator17:29
sridhar_rambobh: link ?17:29
bobhsridhar_ram: checking17:30
*** pmesserl_ has joined #openstack-meeting-417:30
bobh#link https://blueprints.launchpad.net/tacker/+spec/tosca-parser-integration17:30
bobh#link https://blueprints.launchpad.net/heat-translator/+spec/tosca-nfv-support17:31
bobh#link https://review.openstack.org/#/c/253689/17:31
sridhar_rambobh: cool.. this actually big deal, this is probably the first and only implementation of tosca-nfv profile (AFAIK)17:32
bobhThere needs to be some discussion around the specific object mappings to I'll start that conversation this week - maybe an etherpad is the best place for that17:32
bobhsridhar_ram: probably - it's not completely implementable in it's current form17:32
sridhar_rambobh: etherpad is a good idea..17:32
bobhLooking at the NFV spec has raised some questions in my mind about the Simple TOSCA spec17:33
sridhar_rambobh: understood, we have some mindful folks in tosca-nfv stds group (that's includes me) to incorporate our findings17:33
*** pmesserli has quit IRC17:33
bobhlike why the basic Network object has IP addresses in it17:33
bobhso it might end up triggering additional changes in the base spec if we do it right17:33
sridhar_rambobh:  I see..17:34
sridhar_rambobh: one thing, you might already know .. tosca-nfv profile is not a standalone spec as it stands. It build on top of tosca-simple profile namespace17:34
*** brucet has joined #openstack-meeting-417:34
bobhwe can discuss in the etherpad and find the right solution - for now anyway17:34
bobhright - but for example they define the "VirtualLink" as derived from Root not derived from tosca.nodes.network.Network17:35
sridhar_ramsure, please send a ML email when you get the etherpad to going17:35
*** yasui_ has quit IRC17:35
bobhwill do17:35
sridhar_rambobh: that VL reference is weird.. will take a look17:35
sridhar_ramlets move on...17:36
*** sambetts is now known as sambetts-afk17:36
sridhar_ram#topic Multi-Site17:36
*** openstack changes topic to "Multi-Site (Meeting topic: tacker)"17:36
sridhar_ramsripriya: please take over..17:36
vishwanathjare multi-site and multi-vim synonymous ?17:37
sripriyasridhar_ram: sure, multisite vim support v2 is out for review https://review.openstack.org/#/c/249085/17:37
sripriyavishwanathj: IMHO no17:37
*** brucet_ has quit IRC17:38
sridhar_ramvishwanathj: there was bit of confusion, as multi-vim for some folks means different types of VIMs like openstack, vmware, aws17:38
vishwanathjok, my understanding as well was that they were not the same17:38
sripriyavishwanathj: multi-VIM refers to types of VIMs (OpenStack, VMware, AWS, etc) where as multi-site ( multiple installations of same VIM) as i understand17:38
sripriyasridhar_ram: one thing i wanted to discuss here was about the auto network creation in case of multisite scenario17:39
vishwanathjsridhar_ram, sripriya, thanks for the explanation17:39
brucetOK. Since this is multi site, did you see my comments about the potential use of Heat multi cloud?17:39
brucetfor this feature?17:39
*** mbound_ has quit IRC17:39
*** Prithiv has quit IRC17:40
sridhar_rambrucet: my understand is that feature is still under development ?17:40
sripriyabrucet: heat mutlicloud is still a WIP right?17:41
sripriya*multi17:41
brucetThe point is that you could incorporate a prive version of it into Tacker17:41
*** yasui_ has joined #openstack-meeting-417:41
brucetIt assumes a standalone version of Heat17:41
brucetSo you could incorporate that standalone versiojn of Heat in Tacker17:41
brucetWhen the feature is fully released, you could use the public version.17:42
sridhar_rambrucet: that puts a dependency for operators to use this bleeding edge openstack feature before someone can use Tacker's multi-site17:42
brucetMuch easier than developing something new17:42
brucetNope17:43
brucetThe feature is extremely simple17:43
*** mhayden has joined #openstack-meeting-417:44
sridhar_rambrucet: the scope of this spec is even basic than that..17:44
sripriyabrucet: i don't see any spec for the blueprint or i may be missing it. moreover it uses keystone federation (as the bp states) which needs some real effort to get it right17:44
sridhar_rambrucet: see https://answers.launchpad.net/tacker/+question/27671717:44
brucetIf you find bugs in the feature, you can fix them in your standalone version of Heat and fold them into the version under development17:44
sridhar_rambrucet: we need to support Tacker, sometime even on existing / operational OpenStack instances17:45
brucetStandalone Heat in Tacker17:45
sridhar_rambrucet: we CANNOT ask the operators to re-work their deployment at this point17:45
brucetWorks with existing OpenStack deployments17:45
sridhar_rambrucet: have said that, we shd consider this (multi-cloud) and perhaps other things like keystone federation in follow on iterations of multi-site17:46
sridhar_rambrucet: but it is not available now.. lets start with something that is available now and iterate17:46
brucetBut you understand my point about standalone Heat?17:46
brucetI think a beta version is available now.17:47
*** natarajk1 has joined #openstack-meeting-417:47
sridhar_rambrucet: can you explainn further on that ?17:47
brucetHeat can be deployed as a standalone subsystem17:47
brucetThe multi cloud feature works with a stand alone Heat deployment17:48
*** Johnny_ has joined #openstack-meeting-417:48
brucetYou use the standalone Heat to instantiate stacks in other OpenStack clouds17:48
brucetThe standalone Heat variant could be incorporated in Tacker17:48
sripriyabrucet: this is the multi-region heat feature right?17:49
brucetSeparate from Heat in OpenStack that Tacker is running on17:49
brucetActually multi cloud17:49
*** natarajk has quit IRC17:49
brucetI sent a link to the blueprint in my comment17:49
sripriyawhere standalone heat can instantiate stacks in remote stacks and a single identity service is running across all sites17:50
brucetSeems extremely simple17:50
sridhar_rambrucet: I see. Standalone Heat talks to remote heat-engines ? or does it talk directly to remote nova/neutron ?17:50
brucetRemote heat engines17:50
brucetRemote heat engines instaniate stacks on remote OpenStack instances.17:50
brucetThe new multi cloud feature is based on multi region17:51
sridhar_rambrucet: so you propose tacker --> standalone-heat --- > { remote-heat-engine-1, remote-heat-engine-2, .. }17:51
sripriyabrucet: with the requirement of keystone federation17:51
brucetsridar: yes17:52
brucetI think the new multi cloud fearture does not require keystone federation17:53
*** Bjoern_ has left #openstack-meeting-417:53
brucetIn any case, I think its worth looking into17:53
sridhar_rambrucet: yes, that is an interesting feature..17:54
sridhar_rambrucet: however lets keep in mind.  that higher order tacker user facing requirement here is .. target VIMs need to be exposed to NFV / VNF Orchestrators.17:54
sridhar_rambrucet: .. apart from mult-site support17:54
sridhar_ramlets continue the discussion in the spec..17:54
brucetOK17:55
sripriyabrucet: not sure,as the BP says "Extend our existing multi-region remote stacks to multi-cloud, so that a remote stack can be created on a separate cloud with its own Keystone, provided that Keystone federation is supported between clouds."17:55
sridhar_ramtbh: can give a quick update from your side ?17:55
* sridhar_ram 5 mins mark17:55
sridhar_ram#topic Automatic Resource Creation17:55
*** openstack changes topic to "Automatic Resource Creation (Meeting topic: tacker)"17:55
tbhsridhar_ram, yeah, we have decided to create network resources on vnf-create tim17:55
tbhsridhar_ram,  but I need some clarity on declaration of image details in TOSCA template17:56
tbhsridhar_ram, if we use artifacts syntax, you mentioned in the comments17:56
sripriyatbh: on the create network part, it will be good to understand its requirement in multisite use case17:56
tbhthen are we not going to support vm_image ?17:57
*** chem has quit IRC17:57
tbhsripriya, sure, I will look into that direction17:57
sridhar_ramtbh: no, we should support both for time being..17:57
sridhar_ramtbh: leave your question in your spec.. I'll respond17:58
sripriyatbh: thanks, you can provide your suggestions on the multisite spec as well17:58
tbhsridhar_ram, but have concerns with artifacts syantax17:58
sridhar_ramtacker team - pllease review https://review.openstack.org/#/c/250291/17:58
sridhar_ramwe need to land this, if possible, earlier in the Mitaka cycle17:59
tbhsridhar_ram,  sure will update in the comments17:59
sridhar_ramtbh: unfortunately we are out of time for today...17:59
*** zz_ja is now known as zz_zz_ja17:59
sridhar_ramlets continue in the gerrit17:59
sridhar_ram#topic Open Discussion17:59
*** openstack changes topic to "Open Discussion (Meeting topic: tacker)"17:59
sridhar_ramfolks - watch out for an email on EVP mtg and plan to attend!18:00
sridhar_ramthat's it for today...18:00
*** kebray has quit IRC18:00
sridhar_rambye18:00
s3wongbye18:00
vishwanathjbye18:00
*** natarajk1 has left #openstack-meeting-418:00
sripriyathanks bye18:00
sridhar_ram#endmeeting18:00
brucetbye18:00
*** openstack changes topic to "Q&A (Meeting topic: openstack-vahana)"18:00
openstackMeeting ended Tue Dec  8 18:00:33 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2015/tacker.2015-12-08-17.01.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2015/tacker.2015-12-08-17.01.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2015/tacker.2015-12-08-17.01.log.html18:00
*** vishwanathj has quit IRC18:00
*** kebray has joined #openstack-meeting-418:03
*** Johnny_ has left #openstack-meeting-418:03
*** s3wong has quit IRC18:05
*** santoshk has quit IRC18:05
*** brucet has quit IRC18:08
*** brucet has joined #openstack-meeting-418:17
*** salv-orlando has joined #openstack-meeting-418:17
*** __snake__ has quit IRC18:20
*** salv-orlando has quit IRC18:21
*** kebray has quit IRC18:22
*** sripriya has quit IRC18:25
*** shakamunyi has joined #openstack-meeting-418:25
*** s3wong has joined #openstack-meeting-418:26
*** dims_ has quit IRC18:30
*** brucet has quit IRC18:32
*** tbh has left #openstack-meeting-418:32
*** brucet has joined #openstack-meeting-418:45
*** brucet has quit IRC18:46
*** david-ly_ has joined #openstack-meeting-418:50
*** david-ly_ is now known as david-lyle_18:52
*** david-lyle has quit IRC18:54
*** neelashah1 has quit IRC19:00
*** sripriya has joined #openstack-meeting-419:02
*** bpokorny_ has joined #openstack-meeting-419:02
*** bpokorny_ has quit IRC19:03
*** neelashah has joined #openstack-meeting-419:03
*** bpokorny_ has joined #openstack-meeting-419:04
*** salv-orlando has joined #openstack-meeting-419:04
*** pmesserli has joined #openstack-meeting-419:05
*** bpokorny_ has quit IRC19:05
*** bpokorny has quit IRC19:05
*** bpokorny has joined #openstack-meeting-419:06
*** avarner has quit IRC19:07
*** avarner has joined #openstack-meeting-419:07
*** pmesserl_ has quit IRC19:08
*** pmesserli has quit IRC19:09
*** pmesserli has joined #openstack-meeting-419:10
*** salv-orlando has quit IRC19:11
*** prashantD has quit IRC19:11
*** kebray has joined #openstack-meeting-419:11
*** david-lyle_ is now known as david-lyle19:14
*** sripriya has left #openstack-meeting-419:14
*** prashantD has joined #openstack-meeting-419:15
*** neelashah has quit IRC19:15
*** neelashah has joined #openstack-meeting-419:15
*** bpokorny has quit IRC19:16
*** bpokorny has joined #openstack-meeting-419:17
*** sridhar_ram has quit IRC19:17
*** mestery has quit IRC19:28
*** mestery has joined #openstack-meeting-419:28
*** kebray has quit IRC19:38
*** irenab has quit IRC19:42
*** neelashah has quit IRC19:51
*** u_kozat has quit IRC19:55
*** prashantD has quit IRC20:00
*** prashantD has joined #openstack-meeting-420:03
*** neelashah has joined #openstack-meeting-420:05
*** kebray has joined #openstack-meeting-420:06
*** kebray_ has joined #openstack-meeting-420:07
*** kebray has quit IRC20:07
*** prashantD has quit IRC20:08
*** neelashah has quit IRC20:14
*** neelashah has joined #openstack-meeting-420:16
*** prashantD has joined #openstack-meeting-420:18
*** kebray_ has quit IRC20:18
*** neelashah has quit IRC20:19
*** galstrom is now known as galstrom_zzz20:22
*** sridhar_ram has joined #openstack-meeting-420:29
*** neelashah has joined #openstack-meeting-420:32
*** kebray has joined #openstack-meeting-420:38
*** igordcard has quit IRC20:52
*** avarner has quit IRC20:53
*** javeriak_ has quit IRC20:54
*** fawadkhaliq has quit IRC20:55
*** afveitch has quit IRC20:55
*** u_kozat has joined #openstack-meeting-420:56
*** kebray has quit IRC21:01
*** u_kozat has quit IRC21:01
*** neelashah has quit IRC21:19
*** cdelatte has quit IRC21:23
*** dims has joined #openstack-meeting-421:31
*** vishwanathj has joined #openstack-meeting-421:32
*** neelashah has joined #openstack-meeting-421:47
*** cdelatte has joined #openstack-meeting-421:49
*** salv-orlando has joined #openstack-meeting-421:50
*** salv-orlando has quit IRC21:55
*** bobh has quit IRC21:56
*** sridhar_ram has quit IRC21:58
*** dims has quit IRC21:59
*** salv-orlando has joined #openstack-meeting-422:05
*** sridhar_ram has joined #openstack-meeting-422:05
*** dshakhray has quit IRC22:08
*** david-ly_ has joined #openstack-meeting-422:10
*** woodard has quit IRC22:12
*** david-lyle has quit IRC22:13
*** david-ly_ is now known as david-lyle22:13
*** Prithiv has joined #openstack-meeting-422:18
*** belmoreira has joined #openstack-meeting-422:19
*** julim has quit IRC22:21
*** kebray has joined #openstack-meeting-422:26
*** Swami_ has joined #openstack-meeting-422:27
*** Swami has quit IRC22:27
*** SimonChung has joined #openstack-meeting-422:30
*** kebray has quit IRC22:31
*** sridhar_ram has quit IRC22:32
*** Prithiv has quit IRC22:34
*** sridhar_ram has joined #openstack-meeting-422:34
*** EricLajoie has joined #openstack-meeting-422:40
*** banix has quit IRC22:40
*** prashantD has quit IRC22:40
*** njohnsto_ has quit IRC22:41
*** prashantD has joined #openstack-meeting-422:45
*** salv-orlando has quit IRC22:53
*** salv-orlando has joined #openstack-meeting-422:54
*** sigmavirus24 is now known as sigmavirus24_awa22:56
*** devananda has quit IRC22:57
*** u_kozat has joined #openstack-meeting-422:59
*** u_kozat has quit IRC23:04
*** sridhar_ram has quit IRC23:04
*** EricLajoie has quit IRC23:04
*** EricLajoie has joined #openstack-meeting-423:04
*** EricLajoie has quit IRC23:05
*** EricLajoie has joined #openstack-meeting-423:05
*** neelashah has quit IRC23:06
*** sridhar_ram has joined #openstack-meeting-423:08
*** klamath has quit IRC23:11
*** SimonChung has quit IRC23:13
*** FallenPegasus has joined #openstack-meeting-423:15
*** baoli has quit IRC23:18
*** yamamoto has joined #openstack-meeting-423:23
*** sdake has joined #openstack-meeting-423:24
*** EricLajoie has quit IRC23:31
*** baoli has joined #openstack-meeting-423:32
*** baoli has quit IRC23:35
*** baoli has joined #openstack-meeting-423:36
*** blahRus has quit IRC23:40
*** yamamoto has quit IRC23:40
*** mbound_ has joined #openstack-meeting-423:42
*** baoli has quit IRC23:54

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