Thursday, 2015-06-04

*** padkrish_ has joined #openstack-meeting-400:00
*** padkrish has quit IRC00:00
*** vinkman has joined #openstack-meeting-400:01
*** vinkman has left #openstack-meeting-400:02
*** alexpilotti has quit IRC00:03
*** Swami has quit IRC00:07
*** Swami has joined #openstack-meeting-400:08
*** fallenpegasus has quit IRC00:10
*** banix has quit IRC00:14
*** banix has joined #openstack-meeting-400:19
*** asselin_ has joined #openstack-meeting-400:23
*** puranamr has quit IRC00:27
*** sarob has quit IRC00:35
*** bknudson has joined #openstack-meeting-400:43
*** xingchao has joined #openstack-meeting-400:48
*** xingchao has quit IRC00:49
*** watanabe_isao has joined #openstack-meeting-400:49
*** Sukhdev has quit IRC00:59
*** armax has quit IRC01:00
*** akwasnie has quit IRC01:02
*** padkrish_ has quit IRC01:04
*** CheKoLyN has joined #openstack-meeting-401:10
*** jmcbride has quit IRC01:10
*** jmcbride has joined #openstack-meeting-401:10
*** openstack has joined #openstack-meeting-401:21
*** jmcbride has quit IRC01:22
*** pdb_ has joined #openstack-meeting-401:22
*** galstrom_zzz is now known as galstrom01:22
*** ChanServ sets mode: +o openstack01:22
*** CheKoLyN has joined #openstack-meeting-401:22
*** openstack has joined #openstack-meeting-401:36
*** ChanServ sets mode: +o openstack01:36
*** s3wong has quit IRC01:40
*** yamahata has quit IRC01:46
*** openstack has quit IRC01:52
*** openstack has joined #openstack-meeting-401:53
*** asselin_ has quit IRC01:54
*** ChanServ sets mode: +o openstack01:54
*** jmcbride has joined #openstack-meeting-401:59
*** jmcbride has quit IRC01:59
*** eghobo_ has quit IRC02:04
*** bharath has quit IRC02:12
*** galstrom is now known as galstrom_zzz02:18
*** kobis has joined #openstack-meeting-402:28
*** KunalGan_ has joined #openstack-meeting-402:33
*** kenhui has joined #openstack-meeting-402:35
*** KunalGandhi has quit IRC02:37
*** KunalGan_ has quit IRC02:38
*** bknudson has quit IRC02:39
*** ivar-lazzaro has quit IRC02:44
*** asselin_ has joined #openstack-meeting-402:44
*** ivar-lazzaro has joined #openstack-meeting-402:44
*** kobis has quit IRC02:54
*** ajmiller has joined #openstack-meeting-402:59
*** yamahata has joined #openstack-meeting-403:00
*** dims_ has quit IRC03:07
*** ivar-laz_ has joined #openstack-meeting-403:15
*** ivar-lazzaro has quit IRC03:15
*** ivar-laz_ has quit IRC03:16
*** asselin_ has quit IRC03:16
*** ivar-lazzaro has joined #openstack-meeting-403:17
*** sbalukoff has quit IRC03:19
*** markvoelker has quit IRC03:23
*** Swami has quit IRC03:24
*** Swami_ has joined #openstack-meeting-403:25
*** rfolco has quit IRC03:30
*** zehicle_IRL has quit IRC03:32
*** zehicle_IRL has joined #openstack-meeting-403:35
*** CheKoLyN has quit IRC03:40
*** dannywilson has quit IRC03:46
*** watanabe_isao has quit IRC03:46
*** galstrom_zzz is now known as galstrom03:49
*** tobe has joined #openstack-meeting-403:51
*** watanabe_isao has joined #openstack-meeting-403:52
*** asselin_ has joined #openstack-meeting-403:53
*** EmilienM|off has quit IRC03:55
*** EmilienM has joined #openstack-meeting-404:01
*** sdake has joined #openstack-meeting-404:05
*** dims_ has joined #openstack-meeting-404:07
*** eghobo has joined #openstack-meeting-404:11
*** dims_ has quit IRC04:13
*** markvoelker has joined #openstack-meeting-404:23
*** markvoelker has quit IRC04:28
*** irenab has quit IRC04:31
*** Swami_ has quit IRC04:34
*** sbalukoff has joined #openstack-meeting-404:34
*** sdake has quit IRC04:34
*** galstrom is now known as galstrom_zzz04:43
*** marcusvrn has joined #openstack-meeting-404:43
*** kenhui has quit IRC05:00
*** banix has quit IRC05:10
*** tobe has quit IRC05:22
*** numan has joined #openstack-meeting-405:28
*** irenab has joined #openstack-meeting-405:35
*** armax has joined #openstack-meeting-405:36
*** tobe has joined #openstack-meeting-405:40
*** marcusvrn has quit IRC05:45
*** fallenpegasus has joined #openstack-meeting-405:46
*** ajayaa has joined #openstack-meeting-405:47
*** saneax has joined #openstack-meeting-405:51
*** belmoreira has joined #openstack-meeting-405:56
*** fallenpegasus has quit IRC06:10
*** saneax has quit IRC06:12
*** markvoelker has joined #openstack-meeting-406:13
*** markvoelker has quit IRC06:18
*** tobe has quit IRC06:18
*** ivar-lazzaro has quit IRC06:20
*** eghobo has quit IRC06:22
*** radek_ has joined #openstack-meeting-406:23
*** fallenpegasus has joined #openstack-meeting-406:26
*** ajayaa has quit IRC06:28
*** flaper87 has quit IRC06:33
*** flaper87 has joined #openstack-meeting-406:33
*** ajayaa has joined #openstack-meeting-406:34
*** KunalGandhi has joined #openstack-meeting-406:36
*** kobis has joined #openstack-meeting-406:42
*** saneax has joined #openstack-meeting-406:50
*** vikram has joined #openstack-meeting-406:54
*** tobe has joined #openstack-meeting-406:57
*** irenab has quit IRC07:06
*** paramite has joined #openstack-meeting-407:09
*** wojdev has joined #openstack-meeting-407:10
*** irenab has joined #openstack-meeting-407:12
*** markvoelker has joined #openstack-meeting-407:13
*** matrohon has joined #openstack-meeting-407:16
*** markvoelker has quit IRC07:18
*** Kiall has quit IRC07:24
*** Kiall has joined #openstack-meeting-407:25
*** GB21 has joined #openstack-meeting-407:28
*** KunalGandhi has quit IRC07:32
*** wojdev has quit IRC07:33
*** dims_ has joined #openstack-meeting-407:44
*** matrohon has quit IRC07:46
*** dims_ has quit IRC07:49
*** bharath has joined #openstack-meeting-408:01
*** circ-user-JzesN has joined #openstack-meeting-408:06
*** armax has quit IRC08:11
*** yamahata has quit IRC08:14
*** matrohon has joined #openstack-meeting-408:20
*** fallenpegasus has quit IRC08:21
*** wojdev has joined #openstack-meeting-408:21
*** wojdev has quit IRC08:35
*** daneyon has joined #openstack-meeting-408:38
*** tobe has quit IRC08:39
*** tobe has joined #openstack-meeting-408:39
*** daneyon has quit IRC08:43
*** GeetikaBatra__ has joined #openstack-meeting-408:50
*** wojdev has joined #openstack-meeting-408:52
*** GB21 has quit IRC08:52
*** matrohon has quit IRC08:55
*** sbalukoff has quit IRC08:57
*** GeetikaBatra__ is now known as GB2108:59
*** matrohon has joined #openstack-meeting-409:00
*** markvoelker has joined #openstack-meeting-409:02
*** mstachow has joined #openstack-meeting-409:03
*** wojdev has quit IRC09:07
*** markvoelker has quit IRC09:07
*** salv-orlando has quit IRC09:08
*** watanabe_isao has quit IRC09:09
*** matrohon has quit IRC09:13
*** matrohon has joined #openstack-meeting-409:19
*** wojdev has joined #openstack-meeting-409:20
*** matrohon has quit IRC09:24
*** GB21 has quit IRC09:27
*** tobe has quit IRC09:33
*** paramite is now known as paramite|afk09:39
*** ajayaa has quit IRC09:40
*** dims_ has joined #openstack-meeting-409:45
*** dims_ has quit IRC09:51
*** matrohon has joined #openstack-meeting-409:52
*** GB21 has joined #openstack-meeting-409:53
*** tobe has joined #openstack-meeting-409:53
*** ajayaa has joined #openstack-meeting-409:57
*** dims_ has joined #openstack-meeting-410:03
*** salv-orlando has joined #openstack-meeting-410:09
*** salv-orlando has quit IRC10:17
*** markvoelker has joined #openstack-meeting-410:18
*** salv-orlando has joined #openstack-meeting-410:20
*** salv-orlando has quit IRC10:21
*** markvoelker has quit IRC10:22
*** salv-orlando has joined #openstack-meeting-410:23
*** daneyon has joined #openstack-meeting-410:27
*** daneyon has quit IRC10:32
*** bharath has quit IRC10:37
*** rods has joined #openstack-meeting-410:45
*** markvoelker has joined #openstack-meeting-410:46
*** IlyaG has quit IRC10:59
*** GB21 has quit IRC11:21
*** paramite|afk is now known as paramite11:40
*** mstachow has quit IRC11:50
*** paramite has quit IRC11:58
*** paramite has joined #openstack-meeting-411:58
*** tobe has quit IRC12:06
*** daneyon has joined #openstack-meeting-412:16
*** irenab has quit IRC12:17
*** irenab has joined #openstack-meeting-412:17
*** GB21 has joined #openstack-meeting-412:20
*** daneyon has quit IRC12:21
*** GB21 has quit IRC12:25
*** ajmiller has quit IRC12:26
*** ajayaa has quit IRC12:29
*** bknudson has joined #openstack-meeting-412:43
*** lakshmiS has joined #openstack-meeting-412:56
*** delatte has joined #openstack-meeting-412:58
*** delattec has quit IRC12:59
*** delattec has joined #openstack-meeting-413:00
*** IlyaG has joined #openstack-meeting-413:01
*** delatte has quit IRC13:02
*** IlyaG has quit IRC13:05
*** banix has joined #openstack-meeting-413:11
*** irenab has quit IRC13:18
*** singlethink has joined #openstack-meeting-413:21
*** banix has quit IRC13:24
*** jmcbride has joined #openstack-meeting-413:28
*** puranamr has joined #openstack-meeting-413:33
*** VW has joined #openstack-meeting-413:33
*** ajayaa has joined #openstack-meeting-413:38
*** puranamr has quit IRC13:40
*** puranamr has joined #openstack-meeting-413:41
*** jmcbride has quit IRC13:43
*** saneax has quit IRC13:43
*** rods has quit IRC13:45
*** bpoulos has joined #openstack-meeting-413:48
*** puranamr has quit IRC13:50
*** puranamr has joined #openstack-meeting-413:50
*** jmcbride has joined #openstack-meeting-413:52
*** rods has joined #openstack-meeting-413:54
*** sigmavirus24_awa is now known as sigmavirus2413:55
*** rods1 has joined #openstack-meeting-413:56
*** rods1 has quit IRC13:56
*** rods1 has joined #openstack-meeting-413:56
*** TravT has joined #openstack-meeting-413:57
*** rods1 has quit IRC13:57
*** rods1 has joined #openstack-meeting-413:57
*** rods1 has left #openstack-meeting-413:58
*** rods has quit IRC13:59
nikhil_kCourtesy meeting reminder: ativelkov, cpallares, esheffield, flaper87, flwang1, hemanthm, ivasilevskaya, jokke_, kragniz, lakshmiS, mclaren, mfedosin, nikhil_k, Nikolay_St, Olena, pennerc, rosmaita, sigmavirus24, sabari, TravT, zhiyan, pkoniszewski, krykowski, ajayaa, GB21, bpoulos14:00
nikhil_k#startmeeting Glance14:00
sigmavirus24Thanks nikhil_k :D14:00
openstackMeeting started Thu Jun  4 14:00:17 2015 UTC and is due to finish in 60 minutes.  The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
sigmavirus24o/14:00
*** openstack changes topic to " (Meeting topic: Glance)"14:00
*** ativelkov has joined #openstack-meeting-414:00
openstackThe meeting name has been set to 'glance'14:00
nikhil_ksigmavirus24: :)14:00
ativelkovo/14:00
*** jmcbride has left #openstack-meeting-414:00
ajayaao/14:00
mfedosino/14:00
flaper87o/14:00
TravTo/14:00
*** ivasilevskaya1 has joined #openstack-meeting-414:00
*** kobis has quit IRC14:01
nikhil_kLet's give folks a couple more mins14:01
bpouloso/14:02
lakshmiSo/14:02
nikhil_kWelcome everyone!14:02
kragnizo/14:02
*** rosmaita has joined #openstack-meeting-414:02
nikhil_kLooks like we've a decent turnout. Let's get started.14:03
rosmaitao/14:03
nikhil_k#topic Mid-cycle meetup14:03
*** openstack changes topic to "Mid-cycle meetup (Meeting topic: Glance)"14:03
*** kenhui has joined #openstack-meeting-414:03
nikhil_kA informal conversation on irc led us to pursue the co-location with other teams.14:03
nikhil_kWe are currently looking to co-host the event with Horizon and SearchLight teams however, are open to options if more are willing to join14:04
flaper87I'd really beg to make it earlier in July and somewhere in the east coast14:04
nikhil_kNova one is a bit later14:04
flaper87not that I hate the west one but going there just for 2 days is.... painful14:04
flaper87:D14:04
* flaper87 stops crying14:04
nikhil_kThanks for the feedback flaper87 .14:05
nikhil_kWe shall welcome some more on the collab link:14:05
nikhil_k#action everyone: Please review and suggest a location, date for mid-cycle meetup https://docs.google.com/spreadsheets/d/1w0eI6SPCA2IrOyHiEYC2uDO3fbYGzahZRUQSva0UD3Y/edit#gid=014:05
*** daneyon has joined #openstack-meeting-414:05
* ativelkov is smiling, thinking about painfull travels for 2 days14:05
TravTscroll down to the bottom.14:05
* mfedosin agrees with Flavio14:05
flaper87ativelkov: lol14:06
nikhil_kThanks to those who already gave feedback there. If anyone has more apprehensions feel free to send me email.14:06
nikhil_kAny more comments?14:07
flaper87looking forward to it14:07
flaper87:)14:07
nikhil_k#topic APIWG process update14:07
*** openstack changes topic to "APIWG process update (Meeting topic: Glance)"14:07
*** mclaren has joined #openstack-meeting-414:07
nikhil_kTrying to get this out there for some cross project process awareness14:08
nikhil_k#link https://review.openstack.org/#/c/186836/14:08
rosmaitamfedosin: sorry, i edited your row by mistake14:08
mfedosinrosmaita, np14:08
*** vikram has quit IRC14:09
nikhil_kelmiko reached out the other day and would be a decent point of contact. I think we also have our very own sigmavirus24 for any intial comments and concerns.. :-)14:09
*** sdake has joined #openstack-meeting-414:09
*** puranamr has quit IRC14:09
nikhil_k#topic Domain model and related refactor14:09
*** openstack changes topic to "Domain model and related refactor (Meeting topic: Glance)"14:09
nikhil_kflaper87: all yours14:09
flaper87o/14:09
nikhil_kone thing before..14:10
flaper87so, I did some research, as promissed14:10
nikhil_k#link https://etherpad.openstack.org/p/liberty-glance-domain-model14:10
flaper87nikhil_k: ++14:10
flaper87Most of my findings were around status updates14:10
*** daneyon has quit IRC14:10
flaper87I know ativelkov had some other places14:10
flaper87and in the etherpad I didn't put task status updates14:10
flaper87anyway14:10
flaper87that said, I think, in the lihgt of the upcoming artifacts work, that we should fix this cases with atomic updates in the domain model14:11
*** sdake_ has joined #openstack-meeting-414:11
flaper87and let the artifact code remove the domain model entirely14:11
flaper87Assuming that's something we want14:11
flaper87This will allow us to fix these races and still work on a major refactor if we want14:11
mfedosinNext week I'm going to start working on new architecture for v314:11
*** ramaj has joined #openstack-meeting-414:12
flaper87The fix shouldn't be invassive, it should be enough to fix the status setter14:12
mfedosinwithout dm14:12
nikhil_k#link https://review.openstack.org/#/c/132898/14:12
ativelkovyup, I agree with that, given that it does not delay us: I'd prefer to land the remaining part of artifacts as it is now (it uses domain concept) and get rid of it with further commits14:12
flaper87same for tasks14:12
flaper87and with those small fixes, we should be able to cover those races14:12
flaper87I wrote some drawbacks in the etherpad14:12
flaper87if you think I missed something please, do tell14:12
*** ramaj has quit IRC14:12
nikhil_kWhat is the proposal though for the pattern without the DM?14:12
flaper87ativelkov: and I had a small chat yday about some strategies14:12
nikhil_kI agree that it makes a ton of sense for tasks to remove it14:13
flaper87nikhil_k: I don't have a proposal for that, I'll defer it to ativelkov14:13
flaper87I'm more concerned about the races now than the DM14:13
nikhil_kPlease do share ativelkov14:13
*** aventerav has joined #openstack-meeting-414:13
flaper87That's a side convo that came out of these findings14:13
ativelkovI want to make sure that the same transaction is used for the whole duration of each request14:14
nikhil_kI don't mind if we start collaborating about removing such logic on the etherpad. We had concerns for v2 refactor given our priority is stability. So, +1 on fixing races and not refactoring there yet.14:14
ativelkovwith optional "for update" locks and a decorator to repeat the transaction in case of dead-lock exception in DB14:14
*** sdake has quit IRC14:15
nikhil_kativelkov: you mean a DB session?14:15
ativelkovYup14:15
nikhil_kBasically what't the scope for transaction would be good to know. Does that make sense for long running tasks?14:15
*** praveens has joined #openstack-meeting-414:15
nikhil_kThose may be Glance Tasks or uploads/downloads too14:15
nikhil_knot so much on downloads, uploads may be affected with open sessions14:16
nikhil_k(yet)14:16
ativelkovThen the DB updates should be transactional anyway14:16
*** IlyaG has joined #openstack-meeting-414:17
ativelkovNow we have a situation when a DB record is read with one transaction, serialized to a "domain object", then somehow transformed and then the object is put back to the DB14:17
ativelkovThis is racy14:17
nikhil_kYeah14:18
mfedosinwe have a solution on that matter btw14:18
nikhil_kDoes this conflict with the oslo.versionedobjects proposal?14:18
nikhil_kWe need the records serialized in that case14:18
ativelkovNot sure yet14:19
nikhil_k(I am just putting some food for thought out there as this is a big change)14:19
flaper87I don't think it conflicts but I'd need to double check14:19
flaper87wasn't the previous artifact version out of the DM ?14:19
flaper87then you guys made it work with DM14:19
nikhil_kIt is14:19
flaper87ah ok14:19
nikhil_kOh wait, no. It's all in coherence with DM..14:20
mfedosinno, it originally was with dm14:20
ivasilevskaya1flaper87, DM model was always there14:20
nikhil_k#link https://review.openstack.org/#/c/132898/14:20
flaper87thanks14:20
nikhil_kShould we move on and let ativelkov, mfedosin &/or flaper87 propose us a plan / etherpad ?14:21
flaper87nikhil_k: for a non-DM glance? yes14:21
nikhil_kThanks14:21
flaper87I don't expect us to figure that out now14:21
nikhil_k#topic Discuss adopting Core Reviewer Hierarchy akin to Neutron's14:21
*** openstack changes topic to "Discuss adopting Core Reviewer Hierarchy akin to Neutron's (Meeting topic: Glance)"14:21
flaper87but I'd like to have an agreement on fixing the races now14:21
flaper87nikhil_k: ^14:21
flaper87(on the DM)14:21
*** IlyaG has quit IRC14:22
nikhil_kThanks. ethadpad discussion good with you?14:22
nikhil_kflaper87: ^14:22
flaper87nikhil_k: kk14:22
nikhil_kLet me revert the topic then14:22
sigmavirus24lol14:22
flaper87nikhil_k: you know there's an undo command ?14:23
flaper87:)14:23
sigmavirus24flaper87: there is?14:23
flaper87there is14:23
sigmavirus24huh14:23
flaper87anyway, feel free to move on14:23
nikhil_kflaper87: sure :) more of silent question14:23
nikhil_k#topic racy status updates in v214:23
*** openstack changes topic to "racy status updates in v2 (Meeting topic: Glance)"14:24
nikhil_kflaper87: earlier was on DM14:24
nikhil_k#link https://github.com/openstack/glance/blob/master/glance/domain/__init__.py#L25014:24
flaper87The thing I'd like us to agree on now is on fixing those races in the actual code14:24
nikhil_k#link  https://github.com/openstack/glance/blob/master/glance/api/v2/images.py#L254-L30614:24
nikhil_kmore on #link https://etherpad.openstack.org/p/liberty-glance-domain-model14:24
flaper87instead of waiting 'til the discussion of whether to use DM or not ends14:24
sigmavirus24flaper87: I doubt anyone disagrees that we need to fix that up14:25
*** sdake has joined #openstack-meeting-414:25
nikhil_k== sigmavirus2414:25
flaper87sigmavirus24: logged or it isn't true14:25
flaper87:P14:25
flaper87ok, that's it14:25
nikhil_kha14:25
sigmavirus24lol14:25
flaper87that's all I wanted :)14:25
* flaper87 stfu now14:25
sigmavirus24flaper87: you know that #openstack-glance is logged now rigth?14:25
sigmavirus24=P14:25
*** matrohon has quit IRC14:25
sigmavirus24Also you can make a spec and have it logged via votes =P14:25
jokke_++ for working around it for now and taking the time to plan future properly14:25
flaper87sigmavirus24: yup but this makes it feel "official"14:25
flaper87sigmavirus24: stfu14:26
nikhil_ktest and set (yes please for status updates)14:26
flaper87:P14:26
sigmavirus24++ for having jokke_ around14:26
flaper87sigmavirus24: bug>spec14:26
* flaper87 hides from everyone's kciks14:26
flaper87or kicks14:26
flaper87ok, enough jokes14:26
flaper87nikhil_k: lets move on14:26
nikhil_kThanks14:27
flaper87thanks for the feedback14:27
nikhil_k#topic Discuss adopting Core Reviewer Hierarchy akin to Neutron's14:27
*** openstack changes topic to "Discuss adopting Core Reviewer Hierarchy akin to Neutron's (Meeting topic: Glance)"14:27
nikhil_k    #link http://git.openstack.org/cgit/openstack/neutron/tree/doc/source/policies/core-reviewers.rst#n3314:27
nikhil_ksigmavirus24: all yours14:27
sigmavirus24So14:27
*** matrohon has joined #openstack-meeting-414:27
sigmavirus24There's been a discussion of this on the mailing list and there was a summit discussion of it14:27
sigmavirus24At this point there are probably 3 sub-teams in glance: metadefs, images, artifacts14:27
sigmavirus24I think in order of attention they get it's: images, artifacts, metadefs14:28
sigmavirus24And it's very unfair to both artifacts and metadefs14:28
*** sdake_ has quit IRC14:28
nikhil_kMay be this overlaps with Fast track stuff (next topic) ?14:29
sigmavirus24It makes sense to me if we adopt the hierarchy/sub-team model since glance has grown to have these specialty teams14:29
* sigmavirus24 missed the fast track stuff14:29
sigmavirus24This is a bit more broad though, especially since there are a bunch of metadefs reviews lying around that no one has reviewed14:29
sigmavirus24Also, we agreed at the summit to keep Metadefs around so we need to give it proper attention14:30
nikhil_ksigmavirus24: Actually, I got one email about image members too14:30
mclarenI'll put my hand up for some metadef reviews14:30
* nikhil_k wonders if anyone is using image sharing in real world besides Rackspace?14:30
sigmavirus24Yeah, I can imagine there are several specialty parts of the codebase. Sub-teams just makes sense and would allow us to maybe scale14:31
*** armax has joined #openstack-meeting-414:31
sigmavirus24We could even adopt something like the Security Doc team that has to have one +2 from doc team core and one +2 from sec core14:31
mclarennikhil_k: yes14:31
nikhil_kok14:31
sigmavirus24Again, most of this is up on the Mailing List but that's all discussion around Rally at the moment14:31
sigmavirus24Neutron and the Security docs projects seem to be doing well with the sub-team model and I think we'd benefit from it and I'd love to hear other opinions telling me I'm wrong =P14:32
jokke_I'm just not convinced that we're big enough project to justify this, but it might be just me14:33
kragnizsigmavirus24: I think it's worth trying14:33
ativelkovWell, neutron is really big and diverse14:33
kragnizparticularly with metadefs14:33
ativelkovDe-facto we already have "sub-teams"14:34
sigmavirus24^ ++14:34
jokke_I think neutron has pretty much their own repos for the subteams which makes the real life separation easier14:34
*** praveens has quit IRC14:34
sigmavirus24jokke_: to a degree but they also have that flow in neutron itself if I understand correctly14:34
kragnizjokke_: thye have sub teams in the core neutron as well14:34
ivasilevskaya1hm.. sorry, I don't get it - who is supposed to review sub-teams?14:34
ativelkovHowever I'm not sure if we need any formal rules on this14:34
mfedosinwhat's the benefit to have it de-jure then?14:34
nikhil_kI am with sigmavirus24 on this one. I think this makes a ton of sense at least for metadefs to begin with. For artifacts, we have fast track proposal coming out and the entire team should get to know it given we will go with all artifacts v3 API. However, I agree that we are too small and don't have enough reviewers to begin with.14:35
sigmavirus24well at the moment, none of the metadef subteam members are core14:35
mclarenIt's worth remembering that a metadef change can still impact (break) image functionality, they're not completely orthogonal.14:35
sigmavirus24mclaren: agreed14:35
sigmavirus24Which is why I pointed out teh security doc team workflow14:35
sigmavirus24at least one +2 from metadefs subteam and at least one from other glance core before workflowing it14:35
jokke_mclaren: =+14:36
nikhil_kI doubt if a email mechanism works for everyone esp for reviews14:36
sigmavirus24We can try whatever, but we need to try something =P14:36
nikhil_k+114:36
jokke_sigmavirus24: I think the fact that we have no core from metadefs group is the issue we need to solve instead of trying to make things more complicated14:36
sigmavirus24And we all need to commit to it14:36
mclarenI think currently there's just a small # of metadef reviews which we should be able to get through14:36
mclaren[until metadefs need to be ported to v3 :-)]14:37
sigmavirus24mclaren: are you just looking at /glance or also python-glanceclient14:37
kragnizmclaren: D:14:37
flaper87also, note that in the future images+artifacts will be one thing14:37
sigmavirus24flaper87: right, in the future ;)14:37
TravTi believe wayne is out of office this week, but i would like to mention that multiple times he mentioned that he was stuck in getting reviews this last release.14:37
TravTon metadefs14:37
flaper87sigmavirus24: right but lets not forget about that14:37
*** praveens has joined #openstack-meeting-414:37
mclarenTravT: yeah, he spoke to me at the summit, I said I'll try to help14:38
TravTand wayne and lakshmiS know metadefs code better than anybody else, i believe.14:38
mclarenthat's true for sure14:38
nikhil_kIn that case, we need some committee that will drive & draft/document the proposal. I would prefer more than two company and at least one repr from each of the sub teams to be proposed if we are even considering this.14:38
*** fallenpegasus has joined #openstack-meeting-414:39
jokke_TravT & all: if stuck with reviews ... yell out for help ... it might not happen on the same day, but keeping same reviews week after week in the meeting agenda seems to give them some traction ;)14:39
mclarenTravT: we don't expect too many more metadef patches once the current ones are merged?14:39
nikhil_kYeah, holler for help should be great. However, I think the diverse focus is making this difficult.14:39
nikhil_kmclaren: I think we may need more as SL becomes more mature14:40
sigmavirus24jokke_: I know that wayne hollered at me for help a bunch of times last cycle and I did my best14:40
TravTmclaren, i have been talking to wayne about some concerns I have about current API14:40
TravTit requires too many calls and can be optimized14:40
sigmavirus24But yeah, we just need some way to make sure wayne, lakshmi, and everyone else's valuable contributions don't get lost14:40
sigmavirus24I don't know if that way of prioritizing them is an etherpad or trello or something else that we'll all stop using after a couple weeks14:41
TravTi was talking to wayne about how we can change a few things so that we can go from 13 calls from horizon to 3 to get them.14:41
sigmavirus24^ mclaren, i.e., it's not just these few reviews and then we're done14:41
TravTwhich actually was part of our original API, but at the juno mid-cycle was voted out.14:42
TravTbecause of time14:42
lakshmiSalso when the cruch time comes, metadef changes takes a lower priority even with all the good intentions from the reviewers14:42
jokke_I don't think having the metadef stuff on flight brought up in the meeting (and opened up a bit why something needs to happen) would hurt14:42
jokke_Personally I'm true believer the more we understand what's going on, the easier it is to review and keep moving14:43
nikhil_kOne thing though.. we need people reviewing stuff and maintain the core-reviewership based off reviews. If that's to be changed then we need to consider input from CPL/TC meeting.14:43
mclarencan metadefs become standard artifacts in v3? Around the 'u' timeframe :-)14:43
TravTthere is also a localization spec wayne (primarily) and I have been talking about.14:43
nikhil_kha14:44
*** kenhui has quit IRC14:44
nikhil_kU -- would be still call artifacts artifacts then or have a fancy new name?14:44
TravTmclaren, i have concerns about that as well but should be discussed14:44
ativelkovmclaren: I don't think so14:44
*** vikram___ has joined #openstack-meeting-414:44
ativelkovMetadefs are dynamic schemas of things14:44
mfedosinmclaren, they will be part of v3 along with artifacts and tasks14:45
ativelkovartifacts are things themselves.14:45
TravTmy thoughts are a little too much for this meeting, so i can send out a ML on it if desired.14:45
nikhil_kumm?14:45
nikhil_kOk, we are short of time.14:45
mclarenativelkov: they're not immutable you mean?14:45
ativelkovmclaren: yes, that's one of the differences14:46
TravTi think this is a good discussion to have... i'll start an ML on it later today.14:46
nikhil_kLet's put some thought and share them on ML. We seem to be having some such discussions there atm..14:46
nikhil_kI think metadefs are conceptually different from artifacts/images.14:46
mclarenativelkov: hmm, ok. (I wonder if we could fake something with versioning...)14:47
nikhil_ksigmavirus24: you mind creating a thread with your comprehensive thoughts on this topic?14:47
sigmavirus24I dont' mind14:47
nikhil_kThanks14:47
mfedosinbut you can always make a metadef-plugin for artifacts if you need it :)14:47
ativelkovnikhil_k: +114:47
nikhil_k#topic Merging remaining artifacts commits with FastTrack14:48
*** openstack changes topic to "Merging remaining artifacts commits with FastTrack (Meeting topic: Glance)"14:48
nikhil_kativelkov: or mfedosin ?14:48
ativelkovme14:48
nikhil_kplease :)14:48
ativelkovWell, just wanted to let you know that we have two changesets ready. They are all the same as we had in April, just changed from v0.1 to v3 and put back into main glance-api process14:49
*** praveens has quit IRC14:49
ativelkov#link https://review.openstack.org/#/c/132898/14:49
ativelkovand14:49
ativelkov#link https://review.openstack.org/#/c/136629/14:49
*** kobis has joined #openstack-meeting-414:49
flaper87ativelkov: I'm happy to be the glance-core that sanity checks those patches14:49
flaper87I think I raised my hand at the summit14:49
* flaper87 keeps doing that14:50
ativelkovI'd prefer to merge them using our newly-approved "fast-track" procedure )14:50
mfedosinand also there is a spec https://review.openstack.org/#/c/177397/14:50
ativelkovthanks flaper87! )14:50
nikhil_kcool!14:50
flaper87ativelkov: I'll take a look and go for fast-track14:50
mfedosinflaper87, thank you!14:50
ativelkovThanks!14:50
flaper87should we tag fast-track reviews in the commit message?14:50
*** GB21 has joined #openstack-meeting-414:50
nikhil_kativelkov: please do send an email to ML when that is about to merge14:50
flaper87A FastTrack tag doesn't hurt14:50
mfedosinflaper87, I think yes14:50
ativelkovSo, I want to merge them first, and then initiate a discussion with API-WG about improvements into API14:50
nikhil_kflaper87: I think that should help ^14:51
nikhil_kativelkov: ok14:51
jokke_I'd like the idea to have operational artifacts sooner than later now when we have been going around the topic for 2 releases ;P14:51
nikhil_ktag works then14:51
sigmavirus24ativelkov: iirc there's a meeting this morning for the WG14:51
jokke_merged I mean14:51
sigmavirus24(er, in a couple hours)14:51
sigmavirus24(morning for me =P)14:51
nikhil_k:)14:51
flaper87jokke_: stop bringing the 2 releases thing up14:51
mfedosinI will update those CMs right after this meeting14:52
ativelkovI'd like to summarize my question into the email first and then discuss them14:52
ativelkovI have some questions on my mind, inlucing that one about /v3/artifacts/something vs /v2/something - and some more about type versioning14:52
nikhil_ksounds great14:52
ativelkov /v3/something*14:52
mclarenat least you didn't mis-type v4 :-)14:53
flaper87mfedosin: ativelkov feel free to ping me on irc14:53
mfedosinlet's leave /v3/artifacts/something for now14:53
nikhil_k+114:54
nikhil_kI like that for future too14:54
sigmavirus24mfedosin: +114:54
mfedosinif we have tasks and metadefs along with artifacts then it's the best solution I think14:54
nikhil_kativelkov: mfedosin : please tag cores for reviews if stuck. I think people won't mind giving a quick look..14:54
* sigmavirus24 has those two reviews open to look at14:55
ativelkovThanks!14:55
ativelkovThat's all from my side14:55
nikhil_kthanks14:55
nikhil_kmoving on..14:55
mfedosinthanks :)14:55
nikhil_k#topic Making use_user_token param False by default14:55
*** openstack changes topic to "Making use_user_token param False by default (Meeting topic: Glance)"14:55
nikhil_kmfedosin: yours14:55
mfedosinyeah14:55
mfedosinI wrote a message to Openstack dev where I had a couple of questions14:56
mfedosinWe have situations during image creation where our token may expire, which leads to unsuccessful operation.14:56
mfedosinand one of them in connection between glance-api and glance-registry14:57
mfedosinIn this case we have a solution (https://review.openstack.org/#/c/29967/) - use_user_token parameter in glance-api.conf, but it is True by default.14:57
*** fallenpegasus has quit IRC14:57
mfedosinIf it's changed to False then glance-api will use its own credentials to authorize in glance-registry and it prevents many possible issues with user token expiration.14:57
mfedosinSo, I'm interested if there are some performance degradations if we change use_user_token to False and what are the reasons against making it the default value.14:58
mclarenis http://en.wikipedia.org/wiki/Principle_of_least_privilege relevant here?14:58
*** krotscheck has joined #openstack-meeting-414:58
*** VW has quit IRC14:58
nikhil_kyep, I think admin calls are a bit messy (in openstack lingo)14:58
sigmavirus24didn't ayoung suggest trusts as a (messy) way of doing this?14:59
mclarenmfedosin: you're thinking about trusts for the backend - would it make sense ... bah there goes sigmavirus2414:59
jokke_also I don't think this affect gate so perhaps making documentation change rather than changing the default behavior14:59
ativelkovsigmavirus24: yeah, that is one of the options14:59
flaper87fwiw, we've been walking around this issue waiting for the right solution to happen14:59
*** VW has joined #openstack-meeting-414:59
*** VW has quit IRC14:59
*** carl_baldwin has joined #openstack-meeting-414:59
flaper87sigmavirus24: ayoung did mention that14:59
*** fallenpegasus has joined #openstack-meeting-414:59
sigmavirus24flaper87: is correct14:59
sigmavirus24This was an open issue for months14:59
sigmavirus24The old solution was to bump the keystone token expiration time limit15:00
nikhil_kno registry, trusted auth are some other deployment (non-software) opetions15:00
*** VW has joined #openstack-meeting-415:00
jokke_I personally like the trusts approach for long term fix15:00
sigmavirus24& time15:00
nikhil_kyep15:00
sigmavirus24don't want to encroach on searchlight =P15:00
nikhil_kIf there's nothing urgent, let's continue on the ML..15:00
*** sdake has quit IRC15:00
mfedosinokay thank you for suggestions :)15:00
ativelkovYeah, any input is welcome to that thread15:01
nikhil_kThanks all!15:01
nikhil_k#endmeeting15:01
flaper87o/15:01
*** openstack changes topic to "(Meeting topic: sc)"15:01
openstackMeeting ended Thu Jun  4 15:01:08 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-06-04-14.00.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-06-04-14.00.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-06-04-14.00.log.html15:01
*** ivasilevskaya1 has left #openstack-meeting-415:01
*** bpoulos has left #openstack-meeting-415:01
TravT#startmeeting openstack search15:01
openstackMeeting started Thu Jun  4 15:01:21 2015 UTC and is due to finish in 60 minutes.  The chair is TravT. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: openstack search)"15:01
openstackThe meeting name has been set to 'openstack_search'15:01
nikhil_kO/15:01
ativelkovo/15:01
kragnizo/15:01
lakshmiSo/15:01
rosmaitao/15:01
TravTlong time no see :)15:01
nikhil_k:)15:01
david-lyleo/15:01
sigmavirus24o/15:02
*** wko has joined #openstack-meeting-415:02
TravTok, so our agenda is here: #link https://etherpad.openstack.org/p/search-team-meeting-agenda15:02
TravTplease add to it as you see fit...15:02
TravTi seem to be having some issues with staying connected to etherpad today15:02
*** eghobo has joined #openstack-meeting-415:03
nikhil_kI do sometimes on chrome/chromium/yandex. Firefox works better15:03
sigmavirus24TravT: blame infra ;)15:03
TravTsounds like a good plan. ;)15:03
TravT#topic governance repo submission15:03
*** openstack changes topic to "governance repo submission (Meeting topic: openstack search)"15:03
TravTas we discussed last week and as you saw, i put up the patch15:04
TravT#link https://review.openstack.org/#/c/188014/15:04
TravTalso sent out a short ML announcement.15:04
mclareno/15:04
TravTso far it has been all positive!15:04
TravTi think need to add a few other TC members as reviewers to try to get their votes.15:05
*** belmoreira has quit IRC15:05
*** fallenpegasus has quit IRC15:05
mclarenany idea is there a particular number of TC votes required?15:05
mclaren(just curious)15:05
david-lyleTravT: what day did you post?15:05
TravTbased on history, it looks like Thierry waits for most the members to weigh in and then he'll do a final approval.15:05
mclarenk15:05
TravTjust yesterday morning.15:05
TravTso, hasn't been there long.15:05
sigmavirus24mclaren: we must be mentally linked, I was thinking the same15:06
david-lyle8 days before TC meeting to vote15:06
david-lylewait that may be the old rules15:06
TravTttx maybe can answer that if he's around?15:06
nikhil_k#link http://comments.gmane.org/gmane.comp.cloud.openstack.devel/5519615:06
TravTi see him in the room list15:06
ttxTravT: In that case it needs to be discussed in a TC meeting15:07
ttxthen we collect TC members votes and I approve when more than half members agree15:07
ttxthat would be 715:07
TravTok.  so, is there a meeting every week or every other week?15:08
ttxthen we have more rules for corner cases -- see http://governance.openstack.org/reference/charter.html15:08
ttxevery week15:08
ttxIt's likely that we would try to cover it next week15:08
TravTwould you mind adding to the agenda or do I need to do that?15:08
ttxI'll pick it up tomorrow morning as I build the final agenda15:08
TravTgreat, thanks!15:08
TravTdo you have a link for the meeting, so everybody here knows when it is?15:09
nikhil_k#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee15:09
*** GB21 is now known as GB21-brb15:10
TravTthanks nikhil_k:15:10
*** vikram___ has left #openstack-meeting-415:10
TravTok, so we'll try to get a few more votes and attend that meeting.15:11
TravTanything else on this, or can we move on?15:11
TravT#topic Glance code breakout update (Steve, lakshmi)15:12
*** openstack changes topic to "Glance code breakout update (Steve, lakshmi) (Meeting topic: openstack search)"15:12
*** kobis has quit IRC15:12
TravTsjmc7 sent me a message a bit ago that he's in transit15:12
TravThe said he's got the metadef plugin pull request up, but needs a tiny bit of tweaking.15:12
TravTdhellmann also said he'd help us out with repo.15:13
nikhil_k\o/15:13
kragnizTravT: with what part of the repo?15:13
kragnizimporting it?15:13
nikhil_kpackaging in general I think15:13
TravTi think so, need to follow up with him (unless he's on here)?15:13
lakshmiSi dont know if dhellmann knows that we already extracted the code from glance15:13
TravTyeah, wanted to cover that with him.15:14
nikhil_kwe need to be mindful about the requirements, release style and sync on global etc15:14
TravTbut we will need help going from our glance extract to an openstack governed repo.15:14
TravTnikhil_k, anything there to share?15:14
*** GB21-brb has quit IRC15:15
nikhil_kIt would be nice to get some glance cores (may 2) to review the removal so that we do not leave a trail behind15:15
nikhil_kI can be one of those15:15
lakshmiS+115:15
* TravT looking at nikhil_k, sigmavirus24, mclaren, kragniz15:15
mclarenme too15:15
TravTgreat!15:15
kragnizwhen do we plan on doing the removal?15:15
kragnizbefore l1, or sooner?15:16
wkoDo I need to remove glance-search from devstack?15:16
nikhil_knext week of so should be great15:16
nikhil_kdepending on when the review is approved15:16
TravTnikhil_k, should wait until this new project is actually accepted?15:16
*** daneyon has joined #openstack-meeting-415:16
nikhil_k:)15:16
lakshmiSyes :)15:16
sigmavirus24I'm in15:16
*** kobis has joined #openstack-meeting-415:17
*** singleth_ has joined #openstack-meeting-415:17
TravTif for some odd reason the project gets rejected, i'd rather not get stranded. :)15:17
nikhil_kTravT: yes, sorry I meant the project acceptance by review15:17
TravT:)15:17
TravTwko: re: devstack, probably same thing.15:17
nikhil_kbasically, we should try to switch the repos is what I was getting at15:18
nikhil_kvs. keeping it in two places near L115:18
wkoTravT: ok will wait15:18
TravTbut that said, did you get a chance to talk with sdague at the summit?15:18
*** wojdev has quit IRC15:18
TravThe is working on (maybe landed now) a new way for projects to deliver their code via plugins to devstack15:19
kragnizTravT: devstack plugins15:19
kragnizthey're pretty cool15:19
TravTbasically, it is a new task in the devstack scripts that allows you to do something like enable foo foo-url15:19
*** zehicle_IRL has quit IRC15:19
kragnizand let us keep most of the devstack code in our tree15:19
wkoTravT: no didn't talk to  him. Will ping him on how to deliver searchlight when available...15:19
TravTit will then reach out to foo-url and executes a script that has known lifecycle points15:19
*** Bjoern__ has joined #openstack-meeting-415:19
*** singlethink has quit IRC15:20
wkook...that sounds pretty cool.15:20
TravTso, project can much more easily install into devstack by keeping in their tree (like kragniz said)15:20
*** Bjoern__ is now known as BjoernT15:20
kragnizTravT: it's the maintaining that gets easier15:20
*** dannywilson has joined #openstack-meeting-415:21
wkowas there a session on it at vancouver?15:21
kragnizso we don't need to wait for devstack people to approve our changes15:21
TravTno, i just talked with him for awhile after the session on the Bit Tent model.15:21
TravTs/Bit/Big15:21
wkoTravT: ok15:21
* sigmavirus24 likes bit tent better15:22
TravTlol15:22
nikhil_k== singleth_15:22
nikhil_k:)15:22
kragnizTravT: have a look at how zaqar does it15:22
kragnizhttps://github.com/openstack/zaqar/tree/master/devstack15:22
nikhil_ksigmavirus24: I was thinking the same. We shall have a bit tent and then a byte tent :P15:22
TravTand the release is called the megabyte15:22
sigmavirus24bit tent will be each repo and byte tent will be openstack/15:22
sigmavirus24;)15:22
sigmavirus24TravT: skipping one sir15:23
sigmavirus24kilobyte ;)15:23
nikhil_klol15:23
sigmavirus24okay15:23
sigmavirus24we're getting wayyyy off topic15:23
kragnizthen libertybyte?15:23
* sigmavirus24 apologizes15:23
TravTlol15:23
nikhil_kI was thiking byte tent == program. bit tent == repo/sub team15:23
wkokragniz: Thx!15:23
sigmavirus24nikhil_k: ah15:23
TravT #action mclaren review extract15:23
TravT#action nikhil_k review extract15:23
TravTso next up:15:24
mclarenTravT: send on the link in case I miss it15:24
TravT#topic Brainstorming session15:24
*** openstack changes topic to "Brainstorming session (Meeting topic: openstack search)"15:24
nikhil_klakshmiS: please ping me near your extraction plan (that sounds a bit fishy/james bond like)15:24
TravTBasically, i'd like to have a session where we can all do some brainstorming on where we go with this project.15:25
lakshmiS:) sure15:25
nikhil_k+1 TravT15:25
david-lyle+115:25
TravTi've started on etherpad (will share in a second).15:25
* nikhil_k looks for like button. forgets irc and fb are different15:25
TravTThe idea is to talk about what we need to do.15:26
TravTwhat we should do15:26
TravTwhat we want to do15:26
TravTand what we DON'T want to do.15:26
TravTAnd the bubble that up into some plans for what we WILL do in the liberty time frame15:26
TravTOn the initial etherpad, people can just freeform add to those topics15:27
TravTbut then I think we need to have some discussion in a rich environment.15:27
nikhil_k++15:27
TravTso was hoping we could do a video conference (or two) next week.15:27
lakshmiSalso discuss on the scope of what areas searchlight can be used in openstack15:27
sigmavirus24I think what we want to do is focus on the defcore projects for liberty and ignore the others unless someone else adds it15:27
*** ajmiller has joined #openstack-meeting-415:28
nikhil_klakshmiS: exactly what I was thinking too.15:28
sigmavirus24by focusing on defcore and indexing defcore projects (or the ones that make sense) I think we'll have a bit more legitimacy on top of what we already have for being so freaking awesome15:28
*** sjmc7 has joined #openstack-meeting-415:28
TravTsigmavirus24: that's generally my thoughts too15:28
nikhil_ksigmavirus24: good point. Do we know the new DefCore plan yet or they are going with same old same old?15:29
TravTi'm not sharing the link just yet15:29
TravTso please have some open discussion here15:29
nikhil_kI have heard that HEAT might benefit from this a bit besides other discussions people have had15:30
nikhil_kIt seems a good fit for autoscale that needs to be extra aware of resource contraints/updates15:30
TravTinteresting.15:30
mclarenobviously getting it done for nova would win mindshare amount the community15:30
lakshmiSapp catalog can use some searching from searchlight15:30
mclaren*amoung15:30
TravTok, i'll go ahead and drop the etherpad link.15:31
rosmaita+1 for defcore projects first, beginning with nova15:31
nikhil_klakshmiS: app catalog == https://github.com/stackforge/apps-catalog ?15:31
TravT#https://etherpad.openstack.org/p/liberty-searchlight-brainstorming15:31
TravT#link https://etherpad.openstack.org/p/liberty-searchlight-brainstorming15:31
sjmc7hi all15:31
nikhil_khi!15:32
lakshmiSnikhil_k: yes15:32
sigmavirus24TravT: we can start with the existing defcore projects and expand as necessary15:32
sjmc7on the subject of other projects, designate bug me regularly about getting a plugin15:32
sigmavirus24at the very least we'll be one cycle behind to start with15:32
david-lyledefcore includes keystone15:32
sigmavirus24sjmc7: if they want to write it ;)15:32
nikhil_ksjmc7: lakshmiS and you are going to work on extraction plan ;) is what I heard15:32
david-lylewhat's the plan around keystone15:32
david-lyle?15:32
TravTdavid-lyle: we don't have one.  do you want to own coming up one?15:33
*** IlyaG has joined #openstack-meeting-415:33
david-lyleindex identity constructs as well? or just use keystone for authZ15:33
*** paramite has quit IRC15:33
lakshmiSnikhil_k: https://github.com/lakshmisampath/searchlight has the extracted code which is getting fine tuned15:33
TravTi was wondering about how keystone would work for when keystone is hooked up to ldap... keystone doesn't pass notification everytime an ldap user is added, right?15:33
david-lyleit get messy once you're trying to index keystone, I would put that part on hold for now, but I will think about it more15:33
nikhil_kthis coule potentially replace keystone-middleware calls that don't work well15:33
*** galstrom_zzz is now known as galstrom15:33
nikhil_klakshmiS: thanks15:34
nikhil_kAlso, they have support for nosql DB now is what we heard15:34
david-lyleTravT: I believe that is correct15:34
nikhil_kso may not benefit as much as other projects would15:35
*** kobis has quit IRC15:35
nikhil_kI would like to focus on Nova myself as I know rackspace heat can use this better15:35
nikhil_k(not air conditioning)15:36
mclarenI'd be interested in swift (if I get permission from the powers that be)15:36
TravTyeah you and rosmaita probably would be good on nova15:36
*** eghobo has quit IRC15:37
*** blahRus has joined #openstack-meeting-415:37
*** IlyaG has quit IRC15:37
TravTso, my suggestion is to start adding things to the etherpad and putting your name by it if you want to be the primary person on it.15:37
TravTbut, on the etherpad, i'd like us to also think about other conceps as well.15:37
TravTsuch as technology decisions and direction.15:38
TravTfor example sigmavirus24 was mentioning twisted the other day15:38
mclarennailing down some pluses and minuses of different approaches sounds like a good idea15:38
TravT+1 mclaren15:39
TravTalso, if people are able to go off and look at what it would mean to index different services, we could come back together and compare notes to help drive framework decisions15:40
sigmavirus24twisted is just really good for async work and has great methods of testing interleaved tasks15:40
sigmavirus24(just my quick 2 cents)15:41
kragnizsigmavirus24: do any other openstack services use it currently?15:41
sigmavirus24no =(15:41
TravTso, we are running low on time...15:41
sigmavirus24no other openstack services use elasticsearch either though =P15:41
* sigmavirus24 shuts up15:41
wkosigmavirus24: ceilometer?15:42
* TravT trying to remember how to setup vote15:42
sigmavirus24\#vote question options15:42
sigmavirus24e.g. #vote Do you think this shed should be red? yes, no15:42
TravT#startvote (are we okay with doing a video conference vs IRC for a brainstorming session) ? yes, no15:43
openstackBegin voting on: (are we okay with doing a video conference vs IRC for a brainstorming session) ? Valid vote options are yes, no.15:43
*** puranamr has joined #openstack-meeting-415:43
openstackVote using '#vote OPTION'. Only your last vote counts.15:43
sigmavirus24#vote yes15:43
*** dims_ has quit IRC15:43
nikhil_kI like that however I feel like we can do that first up for M-1. For L if we can get it working along lines of codes and designs other projects like nova, glance use then it would be decently stable. We can get more feedback too at the summit.15:43
TravT#vote yes15:43
nikhil_k#vote yes15:43
lakshmiS#vote yes15:43
mclaren#vote yes15:44
david-lyle#vote yes15:44
wko#vote yes15:44
TravTsmc7?15:44
kragniz#vote yes15:44
TravTrosmaita?15:44
sjmc7#vote yes15:44
TravT#endvote15:44
openstackVoted on "(are we okay with doing a video conference vs IRC for a brainstorming session) ?" Results are15:44
openstackyes (9): wko, lakshmiS, mclaren, sjmc7, sigmavirus24, nikhil_k, TravT, david-lyle, kragniz15:44
TravTok, so then we basically have vidyo (rackspace) or hangouts15:45
rosmaitasorry, saw something shiny ... yes!15:45
david-lyleso many shiny things15:45
TravTi think vidyo works a little bit better, so could one of your rackers set one up?15:45
mclarenhangout is better from behind firewall?15:45
nikhil_ksure, I can take that15:45
*** galstrom has left #openstack-meeting-415:45
TravToh right, i did have some vidyo problems when in office.15:46
kragnizI'd rather have hangouts, unless we have too many people for that15:46
nikhil_kas long as we have <10 people joining15:46
sigmavirus24^15:46
TravTok, we could start with a hangouts and go to vidyo as backup?15:47
kragnizTravT: that sounds reasonable15:47
TravTSo on days...15:47
*** singlethink has joined #openstack-meeting-415:47
TravTwould either Tuesday or Wednesday next week at 14:00 UTC for 2 hours work for you?15:48
nikhil_kSometime after TC meeting?15:48
nikhil_kthat is on Tuesdays15:48
david-lylenot Tuesday pleas15:48
david-lylee15:48
nikhil_k+1 on Wednesdays (in general)15:49
rosmaitawednesday is better, but i may have to disappear for 1/2 hour in the middle15:49
TravTlakshmiS, i know this is late for you.  How late are you able to attend?15:50
*** singleth_ has quit IRC15:50
nikhil_kI may disaapear for 10-15 mins15:50
lakshmiS9:00 PM IST15:50
nikhil_kthat's 15.30UTC15:50
TravTokay #startvote will this time work for everybody to do a video meetup http://everytimezone.com/#2015-6-10,150,cn3 ? yes, no15:51
TravThmm,, didn't like that15:51
nikhil_k# needs to be first for this command15:51
sigmavirus24TravT: leave off the "okay"15:51
TravT#startvote (will this time work for everybody to do a video meetup http://everytimezone.com/#2015-6-10,150,cn3) ? yes, no15:52
openstackBegin voting on: (will this time work for everybody to do a video meetup http://everytimezone.com/#2015-6-10,150,cn3) ? Valid vote options are yes, no.15:52
openstackVote using '#vote OPTION'. Only your last vote counts.15:52
sjmc7#vote yes15:52
sigmavirus24#vote yes15:52
david-lyle#vote yes15:52
sigmavirus24but I'll probably bail early15:52
TravTsigmavirus24, we could start 30 min earlier15:52
nikhil_kTravT: for 2 hours from then?15:52
*** prometheanfire has joined #openstack-meeting-415:53
TravTyes15:53
kragniz#vote yes15:53
*** zehicle_IRL has joined #openstack-meeting-415:53
sigmavirus24TravT: the start time doesn't matter =P15:53
lakshmiSTravT: is it just for next week?15:53
nikhil_kok15:53
TravTjust next week15:53
nikhil_k#vote yes15:53
*** numan has quit IRC15:53
rosmaita#vote yes15:53
nikhil_kI may leave early too15:53
lakshmiS#vote yes15:53
TravTi'm trying to help get things kicked off15:53
wko#vote yes15:53
TravT#endvote15:53
openstackVoted on "(will this time work for everybody to do a video meetup http://everytimezone.com/#2015-6-10,150,cn3) ?" Results are15:53
openstackyes (8): wko, lakshmiS, sjmc7, sigmavirus24, nikhil_k, david-lyle, kragniz, rosmaita15:53
TravTokay, we'll go with that time15:54
TravTso please add ideas to etherpad and be prepared to discuss them15:54
TravTthank you!15:54
lakshmiSTravT: whats the etherpad link?15:54
nikhil_kyeah, I think I missed it15:55
nikhil_ktoo15:55
TravT#link https://etherpad.openstack.org/p/liberty-searchlight-brainstorming15:55
lakshmiSthx15:55
TravT#topic mid cycle meetup15:55
*** openstack changes topic to "mid cycle meetup (Meeting topic: openstack search)"15:55
*** b3rnard0 has joined #openstack-meeting-415:55
TravTi think everybody has already heard about it in glance or horizon meetings.15:55
*** stevelle has joined #openstack-meeting-415:56
TravTbut please add your availability to the voting section on the bottom of this page15:56
*** rromans has joined #openstack-meeting-415:56
TravT#https://docs.google.com/spreadsheets/d/1w0eI6SPCA2IrOyHiEYC2uDO3fbYGzahZRUQSva0UD3Y/edit#gid=015:56
TravT#link https://docs.google.com/spreadsheets/d/1w0eI6SPCA2IrOyHiEYC2uDO3fbYGzahZRUQSva0UD3Y/edit#gid=015:56
*** s3wong has joined #openstack-meeting-415:56
david-lyleI seem to be the only one not in the know, what is meant by "No preference"15:56
TravTwe have crossover between projects, so trying to get them colocated if possible.15:56
ekarlsoello guys :)15:56
david-lyledon't care?15:56
TravTnikhil_k: ^ "no preference"15:56
TravThi ekarlso15:56
rosmaitadavid-lyle: i interpreted it as "don't care either way"15:56
TravTi'd kinda lika "not preferred, but will do it"15:57
nikhil_kgot disconnected sorry15:57
lakshmiShmm. i thought it meant "didnt care"15:57
TravTnikhil_k: david-lyle wants a definition for no preference15:57
nikhil_kdavid-lyle: no is strong no, no preference is okay but not preffered kinda ono15:58
TravTok.15:58
david-lyleok, just wasn't clear, thanks!15:58
TravTi'm going to skip the launchpad topic... we'll come back to that after brainstorming15:58
nikhil_kI will update legend15:58
*** cloudnull has joined #openstack-meeting-415:58
TravTkragniz, should we push the searchlightclient to next week / brainstorming?15:59
kragnizlet's skip client stuff, too15:59
TravTok.15:59
kragnizyeah, we're too short on tome15:59
kragniztime15:59
TravTWell thanks, everybody!15:59
kragnizthanks!15:59
nikhil_kThanks16:00
TravTI think we are just about ready to really start running!16:00
ekarlsohey guys16:00
rosmaitabye!16:00
* nikhil_k finds his running shoes :)16:00
TravTout of time for now.  try to jump in on #openstack-searchlight16:00
TravT#endmeeting16:00
ekarlsook..16:00
*** openstack changes topic to "(Meeting topic: sc)"16:00
openstackMeeting ended Thu Jun  4 16:00:29 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-06-04-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-06-04-15.01.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-06-04-15.01.log.html16:00
*** rosmaita has left #openstack-meeting-416:00
*** sjmc7 has left #openstack-meeting-416:00
*** galstrom has joined #openstack-meeting-416:01
*** VW has quit IRC16:01
*** sdake has joined #openstack-meeting-416:02
*** Sam-I-Am has joined #openstack-meeting-416:02
cloudnullHello  !16:03
*** lakshmiS has left #openstack-meeting-416:03
Sam-I-Amhowdy16:03
dstanekhi16:03
rromans\o16:03
galstromo/16:03
cloudnull#startmeeting OpenStack Ansible Meeting16:03
openstackMeeting started Thu Jun  4 16:03:30 2015 UTC and is due to finish in 60 minutes.  The chair is cloudnull. Information about MeetBot at http://wiki.debian.org/MeetBot.16:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:03
*** openstack changes topic to " (Meeting topic: OpenStack Ansible Meeting)"16:03
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:03
galstromo/16:03
cloudnull#topic Agenda & rollcall16:03
*** openstack changes topic to "Agenda & rollcall (Meeting topic: OpenStack Ansible Meeting)"16:03
rromans.16:03
sigmavirus24o/16:04
stevelleo/16:04
prometheanfire\o16:04
dstaneko/16:04
cloudnullso lets get started.16:07
cloudnull#Blueprints16:07
cloudnull#topic Blueprints16:07
*** openstack changes topic to "Blueprints (Meeting topic: OpenStack Ansible Meeting)"16:07
cloudnull#link https://review.openstack.org/#/q/status:open+project:stackforge/os-ansible-deployment-specs,n,z16:08
*** VW has joined #openstack-meeting-416:08
cloudnullthis spec needs to be re-reviewed https://review.openstack.org/#/c/184726/16:09
cloudnullJaveria Khan has revised the spec16:09
*** erikmwilson has joined #openstack-meeting-416:10
cloudnulland will focus on only making the 'In tree' neutron code functional.16:10
*** praveens has joined #openstack-meeting-416:10
Sam-I-Ammmkay16:11
* Sam-I-Am tap tap is this thing on?16:13
cloudnullnext #link https://review.openstack.org/#/c/181544/16:13
Sam-I-Amyeah16:14
cloudnullit would be great to get some more people to chime in on this.16:14
Sam-I-Ammaybe we need a config linter?16:14
*** GB21 has joined #openstack-meeting-416:14
cloudnullthis is probably something that we should look into16:15
sigmavirus24Sam-I-Am: you write the spec, I'll write the linter16:15
sigmavirus24It's already 90% done anyway16:15
cloudnulli think sigmavirus24 did that16:15
cloudnull++16:15
cloudnull:)16:15
sigmavirus24github.com/sigmavirus24/schema-validator16:15
sigmavirus24#link https://github.com/sigmavirus24/schema-validator16:15
Sam-I-Amoh, well there you go16:15
sigmavirus24needs osad integration though16:15
sigmavirus24=P16:15
Sam-I-Amso now whats this thing about a config scheme?16:15
Sam-I-Amschema16:15
sigmavirus24and someone to maintain things16:15
Sam-I-Amhughs comment16:16
cloudnullso i think we can expand upon that and make part of our process.16:16
*** kobis has joined #openstack-meeting-416:16
cloudnulli dont think OSAD needs to carry the repo, those bits can live on PyPi and and OSAD can consume them16:16
Sam-I-Amthis works16:16
hughsaunderssigmavirus24++16:17
Sam-I-Amhughsaunders: there you are16:17
sigmavirus24cloudnull: yep, that was my understanding of how it would work too16:17
stevelleeven better, we get free lifetime support if we import it from Pypi16:17
Sam-I-Amhaha16:18
Sam-I-Amsigmavirus24: are you core on that?16:18
Sam-I-Amhughsaunders: so does this linter address your comment?16:19
Sam-I-Ami can update the spec to include the linter16:19
cloudnulli agree with others that the linter process should be a spec on its own.16:20
hughsaundersSam-I-Am: if sigmavirus24 has figured out how to do a linter/validator in a DRY & maintainable way16:20
hughsaundersyep16:20
Sam-I-Amwe cant have a wet linter?16:20
sigmavirus24hughsaunders: but wet linters are faster16:20
Sam-I-Amdoes my spec become dependent on the linter spec?16:20
cloudnullyes16:20
sigmavirus24hughsaunders: and yeah, schema-validator just needs a schema to validate against16:20
cloudnullimo16:20
sigmavirus24hughsaunders: in other words, someone needs to maintain a schema so that the validator knows what belongs in the config file and what does16:21
sigmavirus24it can be simple exclusion/inclusion or it can be more16:21
sigmavirus24because jsonschema is powerful that way16:22
sigmavirus24we can shave that yak when Sam-I-Am writes that spec16:22
cloudnullkk16:22
cloudnullnext16:22
cloudnull#LINK https://review.openstack.org/#/c/168976/16:22
cloudnullcan we kill this one off.16:23
cloudnullor is it something that people are wantng to still do / see?16:23
*** puranamr has quit IRC16:23
*** zehicle_IRL has quit IRC16:23
*** kobis has quit IRC16:24
Sam-I-Amhmmm16:24
Sam-I-Amis there still value for it?16:24
Sam-I-Amhaving a standard way to tune things is better than a bunch of one-offs?16:24
Sam-I-Ammaybe the linter is helpful here too16:25
cloudnullmaybe16:26
cloudnullso im abandoning that spec. unless someone gives me a reason not to16:26
Sam-I-Amthere is no jesse here16:26
cloudnullsilence is acceptance. . .16:26
cloudnulllastly https://review.openstack.org/#/c/181955/16:27
cloudnull#link https://review.openstack.org/#/c/181955/16:27
prometheanfireI wanted to ask about providing a generic os support spec16:27
cloudnullshoot16:28
prometheanfirewhat methods do you think would work best for adding that (as a parrent spec)?16:28
prometheanfirehttps://github.com/openstack-infra/bindep/ might help16:28
Sam-I-Amyep, bindep16:28
*** puranamr has joined #openstack-meeting-416:28
cloudnulljust write the spec and update the gentoo specific one to be a dependent .16:28
cloudnullthen in LP you'll have to associate the two.16:28
prometheanfireI don't think ansible has a generic package install function, just ones specific to distro (families)16:29
prometheanfirecloudnull: got that part, it's implimentation details I wonder about :D16:29
cloudnullthis is correct.16:29
prometheanfirethink they have specifically avoided that16:29
cloudnullso there will be conditional includes/vars16:30
cloudnullbased on facts16:30
prometheanfirewant to avoid that as much as possible is all16:30
prometheanfiregeneric package spec would help16:30
prometheanfires/spec/functino16:30
cloudnulli dont think theres a way to generically proxy commands to a ansible module. however that would be an interesting module upstream to write16:31
prometheanfireit's something I'll look into16:31
prometheanfirewon't have the spec ready next week (gone), but will for the week after16:31
cloudnullthe truth is the package names themself will be different across distros which16:31
cloudnullwill intail optional includes.16:31
prometheanfirecloudnull: use bindep for that16:32
prometheanfireto source the package lists16:32
cloudnullbindep produceses a flat requirement file with package lists.16:32
cloudnullso there will be some additional logic that goes into making that work16:32
cloudnullbut yes bindep is key to multi distro16:32
prometheanfirethought it provided mapping from generic package name to distro package name16:33
*** matrohon has quit IRC16:33
cloudnullso lets move on.16:33
cloudnull#topic Bugs16:33
prometheanfireya16:33
*** openstack changes topic to "Bugs (Meeting topic: OpenStack Ansible Meeting)"16:33
cloudnulldo we have any bugs that we need to call out or otherwise need people on ?16:34
*** kobis has joined #openstack-meeting-416:34
cloudnullwe have the following high priority items that we should be looking at crushing https://bugs.launchpad.net/openstack-ansible/+bugs?search=Search&field.importance=High&field.status=New&field.status=Incomplete&field.status=Confirmed&field.status=Triaged&field.status=In+Progress&field.status=Fix+Committed16:34
cloudnull#LINK https://bugs.launchpad.net/openstack-ansible/+bugs?search=Search&field.importance=High&field.status=New&field.status=Incomplete&field.status=Confirmed&field.status=Triaged&field.status=In+Progress&field.status=Fix+Committed16:34
cloudnullif we could just get a few more eyes on those it would be great!16:35
cloudnull#topic Open discussion16:36
*** openstack changes topic to "Open discussion (Meeting topic: OpenStack Ansible Meeting)"16:36
cloudnullanything else we want to talk about  ?16:36
cloudnullwith so few of us here i think we can wrap up if there's nothing us.16:36
cloudnull*else16:36
*** yamahata has joined #openstack-meeting-416:36
cloudnullit seems that people couldn't be bothered to come to the meeting today and or participate so i think we're done here.16:37
*** sarob has joined #openstack-meeting-416:37
cloudnullthanks everyone that showed up16:37
cloudnull#endmeeting16:37
*** openstack changes topic to "(Meeting topic: sc)"16:37
openstackMeeting ended Thu Jun  4 16:37:44 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-06-04-16.03.html16:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-06-04-16.03.txt16:37
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-06-04-16.03.log.html16:37
*** eghobo has joined #openstack-meeting-416:37
*** prometheanfire has left #openstack-meeting-416:38
Sam-I-Amthanks y'all16:38
*** Sam-I-Am has left #openstack-meeting-416:38
*** TravT has left #openstack-meeting-416:38
*** dims_ has joined #openstack-meeting-416:39
*** praveens has quit IRC16:45
*** galstrom has left #openstack-meeting-416:45
*** kobis has quit IRC16:46
*** sdake_ has joined #openstack-meeting-416:48
*** IlyaG has joined #openstack-meeting-416:49
*** asselin_ has quit IRC16:49
*** Swami has joined #openstack-meeting-416:50
*** aduarte has joined #openstack-meeting-416:50
*** fitoduarte has joined #openstack-meeting-416:50
*** fitoduarte has quit IRC16:50
*** aduarte has quit IRC16:50
*** sdake has quit IRC16:52
*** banix has joined #openstack-meeting-416:52
*** ajmiller has quit IRC16:52
*** KunalGandhi has joined #openstack-meeting-416:52
*** fitoduarte has joined #openstack-meeting-416:52
*** IlyaG has quit IRC16:53
*** Cathy_ has joined #openstack-meeting-416:56
Cathy_#startmeeting16:59
openstackCathy_: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'16:59
Cathy_#startmeeting service chaining16:59
openstackMeeting started Thu Jun  4 16:59:58 2015 UTC and is due to finish in 60 minutes.  The chair is Cathy_. Information about MeetBot at http://wiki.debian.org/MeetBot.16:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: service chaining)"17:00
openstackThe meeting name has been set to 'service_chaining'17:00
*** VW has quit IRC17:00
*** stevelle has left #openstack-meeting-417:00
SwamiCathy_:hi17:00
*** LouisF has joined #openstack-meeting-417:00
Cathy_Swami: hi17:00
Cathy_hi louis17:00
LouisFSwami: hi17:00
*** vikram has joined #openstack-meeting-417:00
SwamiLouisF: hi17:00
Cathy_let's wait for a few minutes for more people to join17:00
Cathy_hi Vikram17:01
*** nikhil_k is now known as nikhil-afk17:01
*** stevelle has joined #openstack-meeting-417:01
*** nbouthors has joined #openstack-meeting-417:02
*** nbouthors has quit IRC17:03
*** VW has joined #openstack-meeting-417:03
*** nbouthors has joined #openstack-meeting-417:03
*** ajmiller has joined #openstack-meeting-417:04
*** fitoduarte has quit IRC17:04
*** fitoduarte has joined #openstack-meeting-417:04
*** adduarte has joined #openstack-meeting-417:04
Cathy_I think we can start17:04
*** fitoduarte has quit IRC17:04
*** adduarte has quit IRC17:04
nbouthorsCathy_: hello17:05
*** fitoduarte has joined #openstack-meeting-417:05
Swamiyes please, we can start17:05
Cathy_I am thinking about discussing the use case and the components for supporting the service chain.17:05
*** stevelle has left #openstack-meeting-417:05
*** erikmwilson has left #openstack-meeting-417:05
Cathy_nbouthors: hi17:05
*** fitoduarte has quit IRC17:05
Cathy_is that OK with everyone. Any other suggestion?17:05
*** fitoduarte has joined #openstack-meeting-417:06
SwamiCathy_: fine17:06
Swami#Agenda Use Case discussion17:06
*** fitoduarte is now known as duartea17:06
Cathy_here is a link to the use case and the components for supporting service chaining in Neutron17:06
s3wongSwami: #topic would be more appropriate :-)17:06
Swamis3wong: yes makes sense17:07
*** duartea is now known as adduarte17:07
Cathy_Swami: would you like to post the link to the slides we prepared for the discussion?17:08
*** adduarte is now known as fitoduarte17:08
Swamisure17:08
Cathy_#topic use case and components discussion17:08
*** openstack changes topic to "use case and components discussion (Meeting topic: service chaining)"17:08
Swami#link https://docs.google.com/presentation/d/1SpVyLBCMRFBpMh7BsHmpENbSY6qh1s5NRsAS68ykd_0/edit?usp=sharing17:09
Cathy_the neutron service chain API is used for the case that the user wants to use OpenStack Neutron and OVS to support service chaining. Any comments on this?17:10
Cathy_By Neutron service chain API, I mean the port chain API which was presented at the OpenStack Summit17:11
LouisFThis basic api is needed to support chaining of vnfs17:12
nbouthorsIs this an abstract description of the chain ?17:12
Cathy_let's go through slide by slide.17:12
*** salv-orlando has quit IRC17:12
Cathy_the port chain is not the Intent abstraction level API17:13
*** s3wong has quit IRC17:13
Cathy_It is a specification of the logical chain API17:13
Cathy_the abstraction level matches existing Neutron abstraction level17:13
SwamiCathy_: I think what you are trying to say is inorder for the intent based port chaining to occur here are the high level actions items that has to be taken in neutron.17:14
LouisFnbouthors: it is a specification of the chain in terms of neutron port-pairs17:14
Cathy_LouisF: yes17:14
LouisFnbouthors: each port-pair represents a VNF17:14
Cathy_Swami: yes17:14
nbouthorsLouisF: A VNF instance17:15
LouisFnbouthors: correct17:15
Cathy_The high level intent Infra can map the high level intent abstraction API to this Neutron level port chain API if it wants to leverage the Neutron module functionality17:15
Cathy_But in this project, we will not cover the Intent Engine. We will concentrate on implementing the Neutron port chain API and the related service chain plugin to support this API17:16
nbouthorsSo a lot of work has been done prior to using the Neutron Port Chain API, in term of resource identification and location.17:16
*** nikhil-afk is now known as nikhil_k17:17
LouisFnbouthors: what resources do you mean?17:17
Cathy_nbouthors: yes in terms of the service function resource and location17:17
nbouthorsLouisF: for example which VNF instance exists, what are the locators which can be used to send traffic to them.17:18
Cathy_So the user needs to first create the service function (like FW) and gets the port of the FW before using this port chain API.17:18
*** bradjones is now known as bradjones_away17:19
LouisFnbouthors: correct, it is expected that the VNF instance resources will already be set up17:19
nbouthorsCathy_: OK, what about SFFs addresses ?17:19
Cathy_Any question on the use case? and architecture diagram in slide 2?17:20
LouisFnbouthors: the steering to SFFs will be handled by the drivers17:20
nbouthorsCathy_: yes17:20
Cathy_nbouthors: SFF addresses are not specified at the API level and will be automatically decided at the Service chain Plugin and driver level17:21
nbouthorsLouisF: OK, so we suppose that from a VM info the driver can find the associated responsible SFF. It could work.17:21
LouisFnbouthors: that is the idea17:21
nbouthorsCathy_: I am checking that it fits  the ODL SFC data model.17:22
Cathy_nbouthors: OK. thanks.17:23
nbouthorsCathy_: I am ok with slides 2 and 317:24
Cathy_for the case the SDN Controller is plugined into the Neutron, then the SDN Controller will decide the SFF based on the SF locator information. For the case that OVS is plugined into the Neutron, the OVS driver will do that.17:25
Cathy_nbouthors: good17:25
*** daneyon_ has joined #openstack-meeting-417:26
Cathy_let's go back to slide 417:26
Cathy_go to slide 417:26
Cathy_slide 4 lists the breakdown of the work we need to deliver for supporting the port chain functionality.17:27
LouisFin slide 3 should there be a SDNC driver like the OVS driver?17:27
*** ajmiller_ has joined #openstack-meeting-417:28
Cathy_LouisF: yes, there should be one inside the neutron server17:28
SwamiLouisF: Can you elaborate on the SDNC driver17:28
*** daneyon has quit IRC17:29
Cathy_LouisF: we can update the slide to reflect it. Actually if you refer to the service chain presentation slides in the OpenStack Summit, it has that driver17:29
*** AlanClark has joined #openstack-meeting-417:29
Cathy_Hi Alan17:29
LouisFSwami: there would be a common sfc driver api with various different datapath driver below it, eg OVS driver, SDNC driver17:30
SwamiCathy_: Are you talking about the "Network Controller Service Chain Driver" that you mentioned in your slide deck in the summit.17:30
Cathy_yes17:30
Cathy_Swami: yes17:30
Cathy_Swami: are you OK with that?17:31
*** ajmiller has quit IRC17:31
Swamiyes17:31
Cathy_#action update the diagram to reflect the Network Controller driver17:32
Cathy_now let's go to slide 4. Is it a complete list of the tasks for supporting this service chain functionality in openStack?17:32
Cathy_any addition or modification?17:33
SwamiThis should be good to start with. We can add or remove as we go.17:34
LouisFthat looks like a complete list17:34
Cathy_sounds good.17:34
Cathy_#topic tasks assignment17:34
*** openstack changes topic to "tasks assignment (Meeting topic: service chaining)"17:34
nbouthorsLouisF: Is this something like an ML2 driver structure, where a set of ports are managed by a specific driver, with a plugin mechanism to keep the specific driver out of the main ce tree?17:34
*** delattec has quit IRC17:34
*** cdelatte has joined #openstack-meeting-417:34
Cathy_Now let's see who would like to lead the development/design of which part?17:35
*** tidwellr has joined #openstack-meeting-417:35
LouisFnbouthors: yes that would be the way to go17:35
*** puranamr has quit IRC17:35
nbouthorsLouisF: ok17:35
Cathy_Anyone like to lead the CLI/ Horizon/Heat part work?17:36
SwamiCathy_: LouisF: I still have a question on the Network Controller Service Chain driver - what would be the functionality of this driver.17:36
Cathy_back up a little bit.17:36
Cathy_let's start from the beginning17:36
LouisFSwami: it would be translate the port chain abstraction into a form used by the SDNC17:37
SwamiBut should that logic reside in neutron.17:37
SwamiIt can be the responsibility of the North bound interface in the SDN controller where neutron feeds in.17:38
LouisFSwami: correct but is a specific sdnc driver which would sit below the common sfc drriver api17:38
SwamiLouisF: this is basically from your block diagram, what I am asking will it be neutron's responsibility to provide that abstraction or can we leave it to the SDN controllers to handle it.17:39
SwamiWhat are the pros and cons.17:39
*** cdelatte has quit IRC17:39
*** fallenpegasus has joined #openstack-meeting-417:40
*** salv-orlando has joined #openstack-meeting-417:40
Cathy_Swami: basically different service chain driver (OVS driver or some vendor's network controller driver) will do their own translation from the common service chain driver API to their specific SFC API. Yes the translation should be handler by the network Controller17:40
*** dims_ has quit IRC17:40
*** puranamr has joined #openstack-meeting-417:41
Cathy_Swami: OK with you?17:41
*** numan has joined #openstack-meeting-417:41
SwamiCathy_: I still have a confusion on that aspect, but I don't want to slow your progress, for now let us focus on the OVS Driver for the first release and move on. I can chat with you later to understand it in more detail.17:42
Cathy_Swami: are you there?17:42
Cathy_Swami: sure. let's focus on the OVS part17:42
Cathy_now let's go through the task assignment on slide 4.17:43
Cathy_1. repo creation. Shall we create it in Stackforge? Is Stackforge doing away?17:44
Cathy_I mean is Stackforge going away?17:44
Swamiarmax: can you comment on the repo17:44
Cathy_Anyone knows whether there is a new type of repo for new projects of the Big Tent?17:45
armaxhi17:45
Cathy_What is the new rule?17:45
armaxsorry I thought the meeting was at 11am PST17:45
armax:(17:45
armaxlet me backtrack17:45
Cathy_armax: :-) np. Great you are here17:46
armaxCathy_: not sure what first steps were decided17:46
*** VW_ has joined #openstack-meeting-417:46
*** VW has quit IRC17:47
armaxI imagine that setting up a repo where we start iterating on is one of the first steps17:47
*** wko has quit IRC17:47
armaxCathy_: we could use the same repo to hold the API document where the discussion can take place17:47
*** IlyaG has joined #openstack-meeting-417:47
Cathy_armax: could you clarify what you mean? We are wondering whether there is a new repo for new project targeted at Big Tent or Neutron Tent? Or shall we use Stackforge? We would like to do this right to avoid moving the repo.17:48
*** s3wong has joined #openstack-meeting-417:48
armaxCathy_: did you follow up with openstack-infra? I don’t think we’re quite ready to accept projects under the openstack namespace17:48
*** BjoernT has quit IRC17:48
armaxCathy_: and renaming isn’t a big deal either17:48
Cathy_armax: could you clarify "we could use the same repo to hold the API document where the discussion can take place"? Which repo is that? Shall we develop code in that repo?17:49
*** SumitNaiksatam has joined #openstack-meeting-417:49
Cathy_Sorry I have not followed up with openstack-infra. I will do that17:49
armaxCathy_: I think we agreed that it makes sense to have this SFC initiative take place the same way other initiatives have taken place, for instance networking-l2gw17:49
armaxCathy_: in that case, we created a repo, and we used to hold the API spec too17:50
Cathy_#action: Cathy follow up with openstack-infra about repo space for this project17:50
armaxCathy_: if SFC is its own initiative, there’s no need to track the spec within the neutron-specs repo17:50
armaxCathy_: as we won’t have rights to ‘merge’ it if we have reached a consensus on what the API should look like17:51
*** singlethink has quit IRC17:51
armaxCathy_: rather than creating two repos: one for specs and one for code17:51
Cathy_armax: Ok, I will do contact openstack-infra and maybe contact you off line to get this sorted out and the repo created.17:51
armaxCathy_: we could just trailblaze the new RFE process where effectively we go straight from RFE to documentation of what the API needs to look like17:52
armaxand that can happen directly in the repo where the code exists17:52
armaxCathy_: sounds good17:52
LouisFarmax: so you are proposing we use stackforge as the repo?17:53
armaxCathy_: my suggestion is: let’s create the repo and move over on the existing related SFC documents to be devref docs in the newly created repo17:53
armaxLouisF: yes17:53
armaxwell17:53
armaxas namespace17:53
*** mwang2 has joined #openstack-meeting-417:53
armaxthe repo might be something like networking-sfc17:53
armaxor neutron-sfc17:53
armaxwhichever we end up settling on in terms on naming17:53
LouisFarmax: neutron-sfc17:53
armaxLouisF: it’s not up to us to decide17:54
LouisFarmax: ok17:54
Swamiarmax: who decides on the repo name17:54
armaxLouisF: in the past some folks pushed back on using neutron as prefix, but things might have changed17:54
*** sbalukoff has joined #openstack-meeting-417:54
Cathy_armax: I needs to digest all your points:-) I will investigate and create the repo offline instead of stuck at this repo point. Now let's move on17:54
vikramhi17:55
*** yamahata has quit IRC17:55
LouisFvikram: hi17:55
armaxCathy_: I can help you with that17:55
vikramSorry to be late17:55
*** yamahata has joined #openstack-meeting-417:55
Cathy_Integration with CLI, Horizon, Heat. Who would like to lead this? Vikram, are you there?17:55
vikramMeeting is from 18:00 UTC17:55
*** igordcard_ has joined #openstack-meeting-417:55
Cathy_armax: thanks!17:55
armaxthe sooner we move past this the quicker we can start iterating on what the API needs to look like on all the various levels and what type of use case we want to achieve by the end of Liberty17:55
vikramI will take care17:56
*** singlethink has joined #openstack-meeting-417:56
*** igordcard_ has quit IRC17:56
armaxCathy_: I think we need to be extremily diligent during the process becasuse the timeline is very aggessive17:56
Cathy_armax: sure. Will do this as the first priority17:56
armaxand we can’t afford to boil the ocean17:56
armaxotherwise by the end of Liberty we’ll have nothing to show for17:56
Cathy_armax: yes, will appreciate your help on this!17:56
armaxand who wants that? :)17:56
*** igordcard_ has joined #openstack-meeting-417:56
*** ajmiller_ has quit IRC17:57
Cathy_armax: 100% agree with you that we can not afford to boil the ocean17:57
*** ajmiller_ has joined #openstack-meeting-417:57
Cathy_vikram: can you take that? I am always here to help if any issue.17:57
armaxvikram: ah, so I wasn’t the only one confused about the time of the meeting!17:58
LouisFvikram: I will help on that also17:58
vikramOk.. Np17:58
*** jwarendt has joined #openstack-meeting-417:58
numanHi17:58
igordcard_hi - the time is now right?17:59
vikramCathy_, LouisF: Thanks17:59
*** nbouthors has quit IRC17:59
*** singleth_ has joined #openstack-meeting-417:59
s3wong1800 utc now18:00
Cathy_I am sorry about the time. BTW, two developer who have expressed in interest in joining the code development can not join today due to holiday in their country and conflict with another meeting.18:00
* armax confused18:00
Cathy_igordcard_: yes18:00
armaxare we at time now, or are going for another hour? If so, it may make sense rebooting this conversation18:00
igordcard_Cathy_: I have a conflict with another meeting, but I will be glancing upon this one as well18:00
Cathy_let's stop here and we cna resume the discussion in next IRC meeting.18:01
*** johnsom has joined #openstack-meeting-418:01
Cathy_igordcard_: sure. np.18:01
Swamisure18:01
Cathy_I will work on the meeting time and send to everyone.18:01
*** barra204 has joined #openstack-meeting-418:01
Cathy_bye everyone, see you in next IRC meeting18:02
armaxCathy_: one suggestion is not to send private emails alongside the dev list18:02
armaxCathy_: otherwise people subscribed to the list will receive emails twice for no good reason18:02
igordcard_Cathy_: but is the meeting ending or starting?18:02
vikrambye18:02
Cathy_armax: sure. I always send to openstack-dev18:02
pcarverI thought the service chaining meeting was at 1800. Is it 1700?18:02
Cathy_or CC openstack-dev18:02
fitoduarteservice chain meeting?18:02
armaxCathy_: just address openstack-dev18:03
johnsomYeah, also just joined for service chaining meeting18:03
Cathy_fitoduarte: it just ends.18:03
armaxpcarver, igordcard_: ye\s18:03
*** mmedvede has quit IRC18:03
armaxpcarver, igordcard_ there’s been a misunderstanding18:03
vikramyes I also thought it's 18:00 .. It's mentioned over the meeting page18:03
xgerman+118:03
pcarverIs this a recurring meeting at 1700 weekly?18:03
*** singlethink has quit IRC18:03
fitoduarteI have it at 1800 as well.. so it changed to 1700 utc?18:03
Cathy_johnsom: sorry about the mess-up on the meeting time. Is 1800 UTC 10am pacific time, right? Am I wrong on the meeting conversion time?18:03
fitoduarte1800 utc is 11:00 am pacifict time.18:04
armaxpcarver, igordcard_ the meeting was supposed to start now but it started an hour before, I suppose we’ll read the log on eavesdrop to catch up what happened, and next week we’ll get it right! 18UTC == 11am for the PST folks18:04
pcarverUTC doesn't do daylight savings18:04
Cathy_pcarver: it is a recurring meeting18:04
johnsomCathy_ 11am pacific18:04
armaxCathy_: https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=18+UTC converts the time in the local timezone18:04
Cathy_fitoduarte: really. I checked the google and it says 10am pacific time. Let me double check this. Sorry folks!18:04
xgermanyep, Outlook has it as a timezone — that ’s how I keep track of it18:04
pcarvermake sure you distinguish between PST and PDT18:05
fitoduarteright now it is is 1800 utc no matter where in the world you are :)18:05
armaxwe overrun, we should get out of this channel18:05
fitoduartelates18:05
Cathy_pcarver: Oh, yeh, let's me check again. Sorry again. I guess we need to go now and I will modify the meeting time and send it out to everyone.18:06
armaxlet’s endmeeting, please18:06
Cathy_by now18:06
Cathy_#endmeeting18:06
*** openstack changes topic to "(Meeting topic: sc)"18:06
openstackMeeting ended Thu Jun  4 18:06:27 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:06
openstackMinutes:        http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-06-04-16.59.html18:06
johnsomarmax This is the meeting time18:06
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-06-04-16.59.txt18:06
openstackLog:            http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-06-04-16.59.log.html18:06
armaxjohnsom: I am afraid there’s been a bit of a clusterconfusion18:06
*** barra204 has quit IRC18:07
johnsomThe timeslot that was just used was neutron L2 gateway18:07
johnsomOh, different day, nevermind18:07
armaxjohnsom: right18:07
armaxjohnsom: let’s read the minutes, it’s the most sane thing to do at this point :)18:08
*** Cathy_ has quit IRC18:08
*** dims_ has joined #openstack-meeting-418:08
*** ivar-lazzaro has joined #openstack-meeting-418:09
xgermanyep18:09
dougwigheh.18:09
*** mmedvede has joined #openstack-meeting-418:09
*** johnsom has left #openstack-meeting-418:15
*** sballe has joined #openstack-meeting-418:17
*** bharath has joined #openstack-meeting-418:21
*** Sukhdev has joined #openstack-meeting-418:22
*** eghobo_ has joined #openstack-meeting-418:25
*** singlethink has joined #openstack-meeting-418:27
*** eghobo has quit IRC18:27
*** singlet__ has joined #openstack-meeting-418:28
*** bradjones_away is now known as bradjones18:29
*** singleth_ has quit IRC18:30
*** padkrish has joined #openstack-meeting-418:32
*** singlethink has quit IRC18:32
*** tidwellr has left #openstack-meeting-418:33
*** numan has quit IRC18:34
*** aventerav has quit IRC18:34
*** vikram has left #openstack-meeting-418:35
*** padkrish has quit IRC18:37
*** openstackstatus has joined #openstack-meeting-418:39
*** ChanServ sets mode: +v openstackstatus18:39
*** bradjones is now known as bradjones_away18:40
-openstackstatus- NOTICE: Gerrit has been restarted to clear an issue with its event stream. Any change events between 17:25 and 18:38 UTC should be rechecked or have their approvals reapplied to initiate testing.18:42
*** LouisF has quit IRC18:43
*** VW_ has quit IRC18:44
*** ajayaa has quit IRC18:45
*** ajo has quit IRC18:47
*** VW has joined #openstack-meeting-418:49
*** padkrish has joined #openstack-meeting-418:49
*** aventerav has joined #openstack-meeting-418:52
*** krtaylor has quit IRC18:59
*** dannywilson has quit IRC19:01
*** dannywilson has joined #openstack-meeting-419:03
*** vishwana_ has joined #openstack-meeting-419:04
*** puranamr has quit IRC19:05
*** vishwanathj has quit IRC19:06
*** barclaac|2 has joined #openstack-meeting-419:11
*** barclaac has quit IRC19:11
*** b3rnard0 has left #openstack-meeting-419:11
*** puranamr has joined #openstack-meeting-419:14
*** salv-orlando has quit IRC19:15
*** krtaylor has joined #openstack-meeting-419:23
*** salv-orlando has joined #openstack-meeting-419:23
*** puranamr has quit IRC19:28
*** puranamr has joined #openstack-meeting-419:37
*** puranamr has quit IRC19:38
*** matrohon has joined #openstack-meeting-419:42
*** zehicle_IRL has joined #openstack-meeting-419:44
*** VW has quit IRC19:49
*** VW has joined #openstack-meeting-419:49
*** dannywilson has quit IRC19:49
*** dannywilson has joined #openstack-meeting-419:50
*** sarob has quit IRC19:50
*** puranamr has joined #openstack-meeting-419:52
*** puranamr has quit IRC19:54
*** VW has quit IRC19:54
*** puranamr has joined #openstack-meeting-419:56
*** VW has joined #openstack-meeting-420:00
*** sarob has joined #openstack-meeting-420:00
*** singlethink has joined #openstack-meeting-420:01
*** dannywilson has quit IRC20:02
*** dannywilson has joined #openstack-meeting-420:04
*** singlet__ has quit IRC20:05
*** SumitNaiksatam has quit IRC20:15
*** SumitNaiksatam has joined #openstack-meeting-420:16
*** GB21 has quit IRC20:16
*** jpeeler has quit IRC20:19
*** VW has quit IRC20:20
*** Sukhdev has quit IRC20:22
*** sarob has quit IRC20:22
*** bradjones_away has quit IRC20:26
*** bradjones has joined #openstack-meeting-420:32
*** sarob has joined #openstack-meeting-420:33
*** markvoelker has quit IRC20:41
*** sarob has quit IRC20:41
*** sarob has joined #openstack-meeting-420:42
*** jpeeler has joined #openstack-meeting-420:42
*** igordcard_ has quit IRC20:45
*** IlyaG has quit IRC20:54
*** fnaval has joined #openstack-meeting-420:55
*** kenhui has joined #openstack-meeting-421:00
*** padkrish has quit IRC21:01
*** padkrish has joined #openstack-meeting-421:02
*** kenhui has quit IRC21:04
*** padkrish has quit IRC21:05
*** padkrish_ has joined #openstack-meeting-421:05
*** s3wong_ has joined #openstack-meeting-421:16
*** s3wong_ has quit IRC21:17
*** IlyaG has joined #openstack-meeting-421:17
*** s3wong_ has joined #openstack-meeting-421:17
*** s3wong_ has quit IRC21:18
*** s3wong has quit IRC21:20
*** s3wong has joined #openstack-meeting-421:21
*** ajmiller_ has quit IRC21:31
*** ajmiller_ has joined #openstack-meeting-421:32
*** ivar-laz_ has joined #openstack-meeting-421:35
*** salv-orlando has quit IRC21:35
*** sarob has quit IRC21:35
*** ivar-laz_ has quit IRC21:35
*** ivar-laz_ has joined #openstack-meeting-421:36
*** ivar-lazzaro has quit IRC21:38
*** salv-orlando has joined #openstack-meeting-421:41
*** markvoelker has joined #openstack-meeting-421:41
*** markvoelker has quit IRC21:46
*** mandre has left #openstack-meeting-421:46
*** ajmiller_ has quit IRC21:47
*** ajmiller has joined #openstack-meeting-421:47
*** matrohon has quit IRC21:49
*** ivar-laz_ has quit IRC21:51
*** ivar-lazzaro has joined #openstack-meeting-421:52
*** krtaylor has quit IRC21:56
*** padkrish_ has quit IRC21:57
*** padkrish has joined #openstack-meeting-421:57
*** padkrish has quit IRC22:02
*** wojdev has joined #openstack-meeting-422:03
*** padkrish has joined #openstack-meeting-422:04
*** puranamr has quit IRC22:04
*** banix has quit IRC22:08
*** ivar-lazzaro has quit IRC22:09
*** dannywil_ has joined #openstack-meeting-422:10
*** padkrish has quit IRC22:11
*** padkrish has joined #openstack-meeting-422:11
*** puranamr has joined #openstack-meeting-422:13
*** sigmavirus24 is now known as sigmavirus24_awa22:13
*** dannywilson has quit IRC22:14
*** dannywil_ has quit IRC22:15
*** padkrish has quit IRC22:16
*** SumitNaiksatam has quit IRC22:17
*** jwarendt has quit IRC22:20
*** eghobo_ has quit IRC22:22
*** sarob has joined #openstack-meeting-422:23
*** padkrish has joined #openstack-meeting-422:23
*** IlyaG has quit IRC22:25
*** krtaylor has joined #openstack-meeting-422:27
*** bknudson has quit IRC22:28
*** Sukhdev has joined #openstack-meeting-422:29
*** blahRus has quit IRC22:29
*** blahRus has joined #openstack-meeting-422:30
*** pdb_ has quit IRC22:33
*** pdb_ has joined #openstack-meeting-422:34
*** csd has quit IRC22:34
*** csd has joined #openstack-meeting-422:35
*** wojdev has quit IRC22:37
*** markvoelker has joined #openstack-meeting-422:42
*** markvoelker has quit IRC22:47
*** wojdev has joined #openstack-meeting-422:48
*** singlethink has quit IRC22:50
*** aventerav has quit IRC22:53
*** fnaval has quit IRC22:53
*** fallenpegasus has quit IRC22:55
*** sarob has quit IRC22:59
*** saneax has joined #openstack-meeting-423:04
*** wojdev has quit IRC23:05
*** carl_baldwin has quit IRC23:05
*** wojdev has joined #openstack-meeting-423:06
*** radek_ has quit IRC23:09
*** sarob has joined #openstack-meeting-423:09
*** GB21 has joined #openstack-meeting-423:12
*** padkrish has quit IRC23:14
*** padkrish has joined #openstack-meeting-423:15
*** ivar-lazzaro has joined #openstack-meeting-423:16
*** GB21 has quit IRC23:19
*** blahRus has quit IRC23:19
*** xingchao has joined #openstack-meeting-423:19
*** sarob has quit IRC23:21
*** puranamr has quit IRC23:25
*** puranamr has joined #openstack-meeting-423:28
*** fitoduarte has quit IRC23:29
*** padkrish has quit IRC23:33
*** ivar-lazzaro has quit IRC23:36
*** bradjones has quit IRC23:36
*** ivar-lazzaro has joined #openstack-meeting-423:36
*** xingchao has quit IRC23:38
*** bradjones has joined #openstack-meeting-423:39
*** puranamr has quit IRC23:40
*** eghobo has joined #openstack-meeting-423:41
*** eghobo_ has joined #openstack-meeting-423:43
*** sdake_ is now known as sdake23:44
*** padkrish has joined #openstack-meeting-423:46
*** eghobo has quit IRC23:46
*** VW has joined #openstack-meeting-423:51
*** puranamr has joined #openstack-meeting-423:51
*** padkrish has quit IRC23:51
*** xingchao has joined #openstack-meeting-423:53
*** padkrish has joined #openstack-meeting-423:53
*** salv-orlando has quit IRC23:53
*** xingchao has quit IRC23:54
*** ajmiller has quit IRC23:59

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