Tuesday, 2014-02-11

*** sarob_ has joined #openstack-meeting-alt00:01
*** sarob_ has quit IRC00:01
*** sarob has quit IRC00:04
*** michael-yu has quit IRC00:05
*** Ranjitha has quit IRC00:05
*** mtreinish has quit IRC00:05
*** carl_baldwin has quit IRC00:07
*** flaper87 is now known as flaper87|afk00:07
*** amcrn_ has joined #openstack-meeting-alt00:08
*** michael-yu has joined #openstack-meeting-alt00:09
*** amcrn has quit IRC00:09
*** jrist has joined #openstack-meeting-alt00:09
*** amcrn_ is now known as amcrn00:09
*** mtreinish has joined #openstack-meeting-alt00:10
*** bdpayne has joined #openstack-meeting-alt00:11
*** Ranjitha has joined #openstack-meeting-alt00:12
*** mwagner_lap has quit IRC00:15
*** mwagner_lap has joined #openstack-meeting-alt00:15
*** mwagner_lap has quit IRC00:16
*** pdmars has quit IRC00:17
*** ijw_ has quit IRC00:19
*** ijw has joined #openstack-meeting-alt00:20
*** jmontemayor has quit IRC00:26
*** nati_ueno has joined #openstack-meeting-alt00:32
*** david-lyle has quit IRC00:37
*** Ranjitha has quit IRC00:41
*** baoli has joined #openstack-meeting-alt00:41
*** baoli has quit IRC00:43
*** baoli has joined #openstack-meeting-alt00:43
*** baoli has quit IRC00:47
*** RajeshMohan has quit IRC00:48
*** baoli has joined #openstack-meeting-alt00:48
*** richm has quit IRC00:52
*** matrohon has quit IRC00:55
*** matrohon has joined #openstack-meeting-alt00:55
*** RajeshMohan has joined #openstack-meeting-alt00:56
*** nati_ueno has quit IRC00:56
*** jmaron has quit IRC00:58
*** gokrokve has quit IRC01:00
*** gokrokve has joined #openstack-meeting-alt01:00
*** RajeshMohan has quit IRC01:01
*** gokrokve has quit IRC01:05
*** RajeshMohan has joined #openstack-meeting-alt01:06
*** atiwari has quit IRC01:07
*** tchaypo has joined #openstack-meeting-alt01:14
*** gokrokve has joined #openstack-meeting-alt01:17
*** Barker has joined #openstack-meeting-alt01:20
*** IlyaE has quit IRC01:20
*** RajeshMohan has quit IRC01:24
*** gokrokve has quit IRC01:25
*** IlyaE has joined #openstack-meeting-alt01:33
*** RajeshMohan has joined #openstack-meeting-alt01:35
*** vkmc has quit IRC01:39
*** xuhanp has joined #openstack-meeting-alt01:41
*** michael-yu has quit IRC01:42
*** michael-yu has joined #openstack-meeting-alt01:46
*** bdpayne has quit IRC01:48
*** Barker has quit IRC01:49
*** michael-yu has quit IRC01:51
*** RajeshMohan has quit IRC01:52
*** RajeshMohan has joined #openstack-meeting-alt01:53
*** RajeshMohan has quit IRC01:58
*** RajeshMohan has joined #openstack-meeting-alt01:58
*** Duane_ has joined #openstack-meeting-alt02:00
*** RajeshMohan has quit IRC02:05
*** RajeshMohan has joined #openstack-meeting-alt02:05
*** Duane__ has joined #openstack-meeting-alt02:10
*** mattgriffin has quit IRC02:10
*** lisaclark1 has joined #openstack-meeting-alt02:11
*** Duane_ has quit IRC02:13
*** mattgriffin has joined #openstack-meeting-alt02:13
*** gokrokve has joined #openstack-meeting-alt02:14
*** lisaclark1 has quit IRC02:15
*** lisaclark1 has joined #openstack-meeting-alt02:15
*** yamahata has quit IRC02:16
*** banix has joined #openstack-meeting-alt02:16
*** flwang has quit IRC02:17
*** baoli has quit IRC02:19
*** amrith has quit IRC02:19
*** amrith has joined #openstack-meeting-alt02:19
*** sarob has joined #openstack-meeting-alt02:22
*** markvoelker1 has joined #openstack-meeting-alt02:25
*** sankarshan is now known as sankarshan_away02:34
*** sarob has quit IRC02:34
*** Barker has joined #openstack-meeting-alt02:34
*** sarob has joined #openstack-meeting-alt02:34
*** sarob has quit IRC02:39
*** Duane__ has quit IRC02:40
*** IlyaE has quit IRC02:40
*** sarob has joined #openstack-meeting-alt02:41
*** johnthetubaguy has joined #openstack-meeting-alt02:42
*** chandan_kumar has joined #openstack-meeting-alt02:48
*** flwang has joined #openstack-meeting-alt02:53
*** chandan_kumar has quit IRC02:54
*** esker has joined #openstack-meeting-alt02:55
*** chandan_kumar has joined #openstack-meeting-alt02:56
*** bdpayne has joined #openstack-meeting-alt02:59
*** flwang has quit IRC02:59
*** flwang has joined #openstack-meeting-alt03:00
*** mikal has quit IRC03:02
*** bdpayne has quit IRC03:02
*** ZangMingJie has quit IRC03:02
*** mikal has joined #openstack-meeting-alt03:03
*** ZangMingJie has joined #openstack-meeting-alt03:03
*** troytoman has quit IRC03:04
*** chandan_kumar has quit IRC03:04
*** troytoman has joined #openstack-meeting-alt03:07
*** ZangMingJie has quit IRC03:08
*** ZangMingJie has joined #openstack-meeting-alt03:09
*** lisaclark1 has quit IRC03:09
*** sankarshan_away is now known as sankarshan03:11
*** troytoman is now known as troytoman-away03:15
*** sarob has quit IRC03:16
*** sarob has joined #openstack-meeting-alt03:16
*** yamahata has joined #openstack-meeting-alt03:16
tchaypono, not moving03:17
*** sarob has quit IRC03:20
*** yamahata has quit IRC03:21
*** jecarey has quit IRC03:24
*** baoli has joined #openstack-meeting-alt03:25
*** michael-yu has joined #openstack-meeting-alt03:26
*** michael-yu has quit IRC03:28
*** chandan_kumar has joined #openstack-meeting-alt03:29
*** Haiying has joined #openstack-meeting-alt03:35
*** baoli has quit IRC03:35
*** michael-yu has joined #openstack-meeting-alt03:35
*** doug_shelley66 has quit IRC03:37
*** amrith has quit IRC03:43
*** sarob has joined #openstack-meeting-alt03:43
*** bdpayne has joined #openstack-meeting-alt03:44
*** sarob_ has joined #openstack-meeting-alt03:49
*** sarob has quit IRC03:50
*** balajiiyer has joined #openstack-meeting-alt03:50
*** arnaud has quit IRC03:53
*** arnaud__ has quit IRC03:54
*** RajeshMohan has quit IRC03:58
*** michael-yu has quit IRC03:58
*** RajeshMohan has joined #openstack-meeting-alt03:59
*** sbalukoff has quit IRC04:02
*** gokrokve has quit IRC04:05
*** gokrokve has joined #openstack-meeting-alt04:05
*** bdpayne has quit IRC04:06
*** gokrokve has quit IRC04:10
*** Haiying has quit IRC04:10
*** michael-yu has joined #openstack-meeting-alt04:11
*** bdpayne has joined #openstack-meeting-alt04:14
*** michael-yu has quit IRC04:14
*** yamahata has joined #openstack-meeting-alt04:19
*** Barker has quit IRC04:19
*** harlowja is now known as harlowja_away04:22
*** yamahata has quit IRC04:23
*** ijw has quit IRC04:23
*** ijw has joined #openstack-meeting-alt04:24
*** gokrokve has joined #openstack-meeting-alt04:25
*** SushilKM has joined #openstack-meeting-alt04:27
*** ijw has quit IRC04:28
*** harlowja_away is now known as harlowja04:30
SushilKMhey hub_cap04:31
SushilKMcan we proceed for https://review.openstack.org/#/c/69383/04:31
SushilKMu have -2d it for i304:31
*** SushilKM has left #openstack-meeting-alt04:32
*** IlyaE has joined #openstack-meeting-alt04:32
*** igor_ has joined #openstack-meeting-alt04:35
*** balajiiyer has left #openstack-meeting-alt04:35
*** johnthetubaguy has quit IRC04:42
*** Haiying has joined #openstack-meeting-alt04:44
*** yamahata has joined #openstack-meeting-alt04:45
*** johnthetubaguy has joined #openstack-meeting-alt04:49
*** bdpayne has quit IRC04:59
*** eharney has quit IRC05:02
*** michael-yu has joined #openstack-meeting-alt05:05
*** sarob_ has quit IRC05:06
*** sarob has joined #openstack-meeting-alt05:07
*** bdpayne has joined #openstack-meeting-alt05:07
*** sarob_ has joined #openstack-meeting-alt05:08
*** sarob_ has quit IRC05:09
*** IlyaE has quit IRC05:09
*** sarob_ has joined #openstack-meeting-alt05:09
*** sarob has quit IRC05:11
*** sarob_ has quit IRC05:13
*** Haiying has quit IRC05:13
*** chandan_kumar has quit IRC05:15
*** chandan_kumar has joined #openstack-meeting-alt05:16
*** banix has quit IRC05:18
*** jecarey has joined #openstack-meeting-alt05:18
*** IlyaE has joined #openstack-meeting-alt05:18
*** michael-yu has quit IRC05:20
*** bdpayne has quit IRC05:22
*** IlyaE has quit IRC05:23
*** michael-yu has joined #openstack-meeting-alt05:24
*** michael-yu has quit IRC05:26
*** IlyaE has joined #openstack-meeting-alt05:27
*** garyk has quit IRC05:30
*** IlyaE has quit IRC05:31
*** bdpayne has joined #openstack-meeting-alt05:32
*** doug_shelley66 has joined #openstack-meeting-alt05:34
*** sarob has joined #openstack-meeting-alt05:34
*** amcrn has quit IRC05:36
*** doug_shelley66 has quit IRC05:38
*** SushilKM has joined #openstack-meeting-alt05:50
*** michael-yu has joined #openstack-meeting-alt05:53
*** michael-yu has quit IRC05:54
*** gokrokve has quit IRC05:54
*** johnthetubaguy has quit IRC05:54
*** jecarey has quit IRC05:56
*** gokrokve has joined #openstack-meeting-alt05:57
*** sarob_ has joined #openstack-meeting-alt06:05
*** IlyaE has joined #openstack-meeting-alt06:05
*** michael-yu has joined #openstack-meeting-alt06:06
*** rwsu has quit IRC06:07
*** rwsu has joined #openstack-meeting-alt06:07
*** michael-yu has quit IRC06:07
*** sarob has quit IRC06:08
*** sarob_ has quit IRC06:12
*** amcrn has joined #openstack-meeting-alt06:15
*** amcrn_ has joined #openstack-meeting-alt06:16
*** bdpayne has quit IRC06:17
*** amcrn has quit IRC06:20
*** RajeshMohan has quit IRC06:21
*** RajeshMohan has joined #openstack-meeting-alt06:23
*** rwsu has quit IRC06:25
*** amcrn_ is now known as amcrn06:28
*** aignatov_ is now known as aignatov06:28
*** DinaBelova_ is now known as DinaBelova06:31
*** harlowja is now known as harlowja_away06:33
*** IlyaE has quit IRC06:35
*** denis_makogon has joined #openstack-meeting-alt06:36
*** michael-yu has joined #openstack-meeting-alt06:36
*** rwsu has joined #openstack-meeting-alt06:38
*** saju_m has joined #openstack-meeting-alt06:38
*** coolsvap has joined #openstack-meeting-alt06:40
*** saju_m has quit IRC06:43
*** saju_m has joined #openstack-meeting-alt06:50
*** saju_m has quit IRC06:51
*** _nadya_ has joined #openstack-meeting-alt06:52
*** garyk has joined #openstack-meeting-alt06:53
*** _nadya_ has quit IRC07:01
*** sarob has joined #openstack-meeting-alt07:05
*** SushilKM has quit IRC07:07
*** aignatov is now known as aignatov_07:09
*** michael-yu has quit IRC07:14
*** michael-yu has joined #openstack-meeting-alt07:15
*** yamahata has quit IRC07:15
*** michael-yu has quit IRC07:17
*** gyee has quit IRC07:18
*** yamahata has joined #openstack-meeting-alt07:19
*** SushilKM has joined #openstack-meeting-alt07:22
*** DinaBelova is now known as DinaBelova_07:30
*** sarob has quit IRC07:33
*** saju_m has joined #openstack-meeting-alt07:37
*** markvoelker1 has quit IRC07:37
*** d0ugal has joined #openstack-meeting-alt07:41
*** d0ugal has quit IRC07:41
*** d0ugal has joined #openstack-meeting-alt07:41
*** saju_m has quit IRC07:52
*** denis_makogon has quit IRC08:04
*** flaper87|afk is now known as flaper8708:04
*** sarob has joined #openstack-meeting-alt08:05
*** michael-yu has joined #openstack-meeting-alt08:06
*** sarob has quit IRC08:10
*** jasonb365 has joined #openstack-meeting-alt08:15
*** jtomasek has joined #openstack-meeting-alt08:28
*** DinaBelova_ is now known as DinaBelova08:32
*** aignatov_ is now known as aignatov08:41
*** aignatov is now known as aignatov_08:42
*** nacim has joined #openstack-meeting-alt08:44
*** aignatov_ is now known as aignatov08:45
*** safchain has joined #openstack-meeting-alt08:49
*** saju_m has joined #openstack-meeting-alt08:51
*** flwang has quit IRC08:52
*** gokrokve has quit IRC08:57
*** sergmelikyan has joined #openstack-meeting-alt09:00
*** jasonb365 has quit IRC09:03
*** SushilKM has quit IRC09:04
*** sarob has joined #openstack-meeting-alt09:05
*** yamahata has quit IRC09:06
*** yamahata has joined #openstack-meeting-alt09:07
*** sarob has quit IRC09:10
*** jcoufal has joined #openstack-meeting-alt09:12
*** DinaBelova is now known as DinaBelova_09:13
*** DinaBelova_ is now known as DinaBelova09:24
*** rsblendido has joined #openstack-meeting-alt09:24
*** rossella_s has joined #openstack-meeting-alt09:24
*** flwang has joined #openstack-meeting-alt09:30
*** mozawa has joined #openstack-meeting-alt09:30
*** gokrokve has joined #openstack-meeting-alt09:33
*** gokrokve_ has joined #openstack-meeting-alt09:35
*** coolsvap has quit IRC09:36
*** boris-42_ has quit IRC09:36
*** gokrokve has quit IRC09:38
*** gokrokve_ has quit IRC09:39
*** sbalukoff has joined #openstack-meeting-alt10:02
*** DinaBelova is now known as DinaBelova_10:03
*** sarob has joined #openstack-meeting-alt10:05
*** michael-yu has quit IRC10:07
*** sarob has quit IRC10:10
*** jjmb1 has quit IRC10:11
*** xuhanp has quit IRC10:12
*** tnovacik has joined #openstack-meeting-alt10:12
*** DinaBelova_ is now known as DinaBelova10:19
*** dmakogon_ is now known as denis_makogon10:21
*** saju_m has quit IRC10:25
*** saju_m has joined #openstack-meeting-alt10:26
*** jasonb365 has joined #openstack-meeting-alt10:28
*** jrist has quit IRC10:30
*** gokrokve has joined #openstack-meeting-alt10:34
*** aignatov is now known as aignatov_10:34
*** gokrokve has quit IRC10:39
*** jrist has joined #openstack-meeting-alt10:42
*** aignatov_ is now known as aignatov10:50
*** sarob has joined #openstack-meeting-alt11:05
*** jasonb365 has quit IRC11:07
*** sarob has quit IRC11:10
*** boris-42_ has joined #openstack-meeting-alt11:16
*** RajeshMohan has quit IRC11:27
*** RajeshMohan has joined #openstack-meeting-alt11:28
*** sankarshan is now known as sankarshan_away11:29
*** gokrokve has joined #openstack-meeting-alt11:34
*** DinaBelova has quit IRC11:39
*** gokrokve has quit IRC11:39
*** DinaBelova has joined #openstack-meeting-alt11:39
*** amrith has joined #openstack-meeting-alt11:39
*** vkmc has joined #openstack-meeting-alt11:49
*** vkmc has joined #openstack-meeting-alt11:49
*** aignatov has quit IRC11:50
*** NikitaKonovalov_ has quit IRC11:50
*** SergeyLukjanov has quit IRC11:51
*** NikitaKonovalov_ has joined #openstack-meeting-alt11:54
*** aignatov has joined #openstack-meeting-alt11:54
*** NikitaKonovalov_ is now known as NikitaKonovalov11:54
*** SergeyLukjanov has joined #openstack-meeting-alt11:55
*** yamahata has quit IRC12:02
*** d0ugal has quit IRC12:03
*** d0ugal has joined #openstack-meeting-alt12:04
*** d0ugal has quit IRC12:04
*** d0ugal has joined #openstack-meeting-alt12:04
*** sarob has joined #openstack-meeting-alt12:05
*** doug_shelley66 has joined #openstack-meeting-alt12:07
*** sarob has quit IRC12:10
*** eanxgeek|log is now known as eanxgeek12:10
*** akuznetsov has joined #openstack-meeting-alt12:30
*** gokrokve has joined #openstack-meeting-alt12:34
*** ttx has quit IRC12:35
*** gokrokve has quit IRC12:39
*** venkatesh has joined #openstack-meeting-alt12:41
*** yamahata has joined #openstack-meeting-alt12:48
*** banix has joined #openstack-meeting-alt12:53
*** yamahata has quit IRC12:54
*** banix has quit IRC12:54
*** irenab has joined #openstack-meeting-alt12:54
*** baoli has joined #openstack-meeting-alt12:56
*** rkukura has joined #openstack-meeting-alt12:59
irenabhi13:02
rkukurahi13:02
*** sadasu has joined #openstack-meeting-alt13:02
irenabrkukura: looked at your patch and posted few questions13:03
baoli#startmeeting PCI Passthrough13:03
openstackMeeting started Tue Feb 11 13:03:32 2014 UTC and is due to finish in 60 minutes.  The chair is baoli. Information about MeetBot at http://wiki.debian.org/MeetBot.13:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:03
*** openstack changes topic to " (Meeting topic: PCI Passthrough)"13:03
irenabDid you have a chance to look at vnic_type patch?13:03
openstackThe meeting name has been set to 'pci_passthrough'13:03
*** tnovacik has quit IRC13:03
baoliHi13:03
irenabI need to rework it a bit, but want to see if in general it what you have in mind13:03
irenabbaoli: hi13:04
*** heyongli has joined #openstack-meeting-alt13:04
rkukurairenab: I have not had a chance to review it closely yet, but will do that this morning.13:05
irenabrkukra: thanks, wating for your inputs before rework13:05
sadasuirenab: I am fine with whatever you have in your patch so far13:05
*** sarob has joined #openstack-meeting-alt13:05
irenabsadasu: thanks a lot for reviewing13:05
heyongliwhat can we do more for nova side blue print?13:05
baoliIrenab, I briefly looked at it, and it looks good. I will take a close look at it later.13:06
irenabbaoli: thanks.13:06
baoliheyongli, welcome back13:06
*** jjmb has joined #openstack-meeting-alt13:06
irenabsomehow all 3rd party tests are broken, but I handle it once have rkukura comments13:07
rkukurairenab: That's my top priority this AM13:07
heyonglibaoli, yeah, after one week13:07
irenabbaoli: Can represent the nova side?13:07
rkukurairenab: I see your questions regarding the vif-details patch and can respond their and/or discuss here.13:07
baolirkukura, I looked at your patch briefly. One question I had is how the MD add their field, say the profileid or vlan field13:08
irenabLet's do it shortly now?13:08
rkukurabaoli: In general, MDs supply the binding:vif_detail value when they call PortContext.set_binding() from within MechanismDriver.bind_port()13:09
*** pdmars has joined #openstack-meeting-alt13:10
*** sarob has quit IRC13:10
*** sgordon has joined #openstack-meeting-alt13:10
rkukuraSo previously, for agent-based MDs using AgentMechanismDriverBase, the base class would alway make this call, passing binding:vif_type setup during __init__().13:11
rkukura/alway/always/13:11
irenabrkukura: why its done via _init__?13:11
rkukuraNow, the driver can supply both binding:vif_type and binding:vif_details in the __init__() call, or pass None for these13:12
rkukuraIf they pass pass None for bindig:vif_type, then the base class no longer calls PortContext.set_binding() when the driver's bind_port() returns True.13:13
irenabwhy its based on vif_type and not vif_details being None?13:13
rkukuraInstead, the driver itself needs to call set_binding() from within check_segment_for_agent()13:13
rkukuraThis approach makes it easy for drivers whose vif_type and vif_details will always be the same, but lets them set them dynamically if needed13:14
sadasurkukura: this is for non-agent based MDs ?13:15
irenabI just think it should be possible to Agent based MDs to set VIF Details even when vif_type is always the same. vif_details may still be changed13:16
rkukurasadasu: All the way AgentMechanismDriverBase deals with getting vif_type and vif_details from the derived class only applies for agent-based MDs13:16
sadasurkukura: ok13:17
rkukurairenab: The derived class can definitely use a static vif_type when it calls set_binding()13:17
irenabsadasu: I think you are first who adds MD that capable to bind port and does not have agent13:17
sadasuirenab: thats right!13:18
rkukurasadasu: All MDs that can bind ports need to call PortContext.set_binding() from within their bind_port() method. The agent base class just provides some structure for this.13:18
rkukurasadasu: I think the ODL MD that's in review also binds ports without an agent.13:19
sadasurkukura: ok13:19
irenabrkukura: OK, so for Agent based MD that need to modify vif_details, it is required to override the base bind_port method?13:19
sadasurkukura: will take a look at this MD...but I understand your explanation13:19
*** yamahata has joined #openstack-meeting-alt13:20
rkukurairenab: They can ovveride bind_port(), but that kind of defeats the purpose of the base class. Instead, they can call PortContext.set_binding() themselves from within check_segment_for_agent().13:20
rkukuraI'll try to clarify things a bit in the review. I also need to do the DB migration so the tempest tests will run.13:21
rkukuraShould have an updated patch later today, and maybe an initial patch for binding:profile.13:21
irenabrkukura: Ok, I think I got it. So PortContext.set_binding() will override the vif_details in __init__?13:21
irenabrkukura: great13:21
rkukurairenab: If vif_details are static (don't depend on anything else) then thats fine.13:22
*** venkatesh has quit IRC13:22
irenabthey may depend on network details, like vlan id13:22
rkukurairenab: But if you need to put the VLAN tag in vif_details, you'll need to call PortContext.set_binding() from within check_segment_for_agent() instead.13:22
irenabrkukra: Is there any flow chart for the ML2 port-create?13:23
irenabif not, I'll definitely do one13:24
rkukurairenab: Not that I'm aware of. Note that the internal handling of this by the plugin will be changing significantly. See http://lists.openstack.org/pipermail/openstack-dev/2014-February/026344.html13:24
irenabrkukura: is this item already under development?13:25
sadasuirenab: my thoughts exactly about the flow chart!13:26
*** jdob has joined #openstack-meeting-alt13:26
rkukuraCoding hasn't started yet. That's next after binding:profile. This is to address two bugs, not a new BP, so feature freeze doesn't apply.13:26
irenabrkukura: so it is also on your table?13:26
rkukuraBut since MDs are impacted, and feature freeze does apply to them, it needs to get done ASAP.13:26
rkukuraIt flowed off my plate onto my table;-)13:27
irenabrkukura: :-)13:28
*** aignatov is now known as aignatov_13:28
irenabto cover the nova part for vif_details changes13:28
baolirkukura, I need more time to look at your patch. But another question, any time set_binding is called, the values will be overwritten (not updated), is that right?13:28
rkukurabaoli: correct13:28
baolirkukura, so each port is associated with a single MD, right?13:29
*** mozawa has quit IRC13:29
irenabbaoli: bound by one MD, I think is more correct to say13:29
*** aignatov_ is now known as aignatov13:29
baoliOk, so a port can only be bound to a single MD.13:30
sadasurkukura: set_binding() is always invoked only by the MD or is there some ML2 internal logic that can trigger set_binding() at other times?13:30
rkukurabaoli: Right now, a single MD is involved in the binding, but all MDs have their create/update/delete precommit and postcommit() calls made, so they can observe things13:30
rkukuralong term, we may want to do some sort of composite bindings that involve MDs at the vswitch, ToR switch, core switch layers, or something13:31
baolithat sounds interesting. In that case, the overwritting behavior would be an issue?13:31
rkukurabaoli: Maybe, but since vif_details is really specifically intended for the VIF driver, it probably only should come from the lowest level part of the composite binding13:32
irenabI suggest to solve the short term first ;-) Its already complicated enough13:32
*** sankarshan_away is now known as sankarshan13:33
rkukurairenab: good point!13:33
baoliagreed13:33
irenabcoming back to nova, I saw that baoli suggests to cover vif_details and profile as part of his changes13:34
irenabI think that vif_details are also required for port security13:34
*** gokrokve has joined #openstack-meeting-alt13:34
rkukurairenab: I was chatting with markmclain prior to the neutron team IRC meeting, and asked about the "blocked" status on your BP. I think this was due to it potentially needing the binding:profile BP implemented first. That's not the case, so I think it can be unblocked.13:34
*** mozawa has joined #openstack-meeting-alt13:35
baoliI posted a patch https://review.openstack.org/#/c/67500/13:35
irenabrkukura: Now I see Mark already unblocked it13:35
*** gokrokve_ has joined #openstack-meeting-alt13:36
baoliIrenab, are you talking about adding vif_details and profile into the VIF object as a separate BP?13:36
irenabbaoli: getting physicla_netowrk for netowrk is added as bug fix I raised yesteday, and we need it for current Mlnx support too, it will be pushed later today by Itzik13:37
baoliirenab, that's good, will take a look. But what's your concern with vif_details and profile on the nova side?13:37
irenabI think it will be small enough and easy for nova cores to review, so you can assume you will get the method to get provider_net info13:38
*** amrith has quit IRC13:38
irenabwill send the link to review once pushed13:38
rkukurabaoli: I'll review that today too.13:38
baolirkukura, great13:39
*** gokrokve has quit IRC13:39
irenabbaoli: I started to look, will poss comments later today13:39
baoliirenab, thanks.13:39
irenab^post13:39
irenabheyongli: any updates on your patches?13:40
heyongliyunhong get some work done, i still work on that, will soon refresh it i think13:40
*** gokrokve_ has quit IRC13:41
irenabbaoli: for vif_details, it changed the portbonding attribute, so I am  ot sure if it breaks the nova code13:41
baoliheyongli, I posted some comments the other day on your patches. Please also take a look at my patch and look for the APIs that it calls into the generic PCI modules.13:42
rkukurairenab: Do you mean the old binding:capabilities attribute?13:42
heyonglibaoli: sure13:42
irenabrkukura: yes13:42
rkukurairenab: It seems all reference to binding:capabilities had been removed from nova early in icehouse.13:43
irenabrkukura: Ok, so then it should not affect the current code13:43
irenabbaoli: maybe yu just need to push support as small patches on same bp, to make nova cores comfortable with review13:44
baoliIrenab, if it becomes big, I would think about doing that. So far, it's not that bad13:45
irenabbaoli: fair enough13:46
rkukurairenab, baoli: I was hoping to push a small nova patch that simply included the binding:vif_details dictionary in the VIF object. The idea was for this to be used for the SR-IOV and for the VIF security work.13:46
irenabso we need to decide on contnt/format for binding:profile and binding:vif_details for SRIOV ports13:47
baoliSo regarding vif_details and profile, we'd create two fields in VIF object, something like VIF.vif_details, VIF.port_profile?13:47
irenabbaoli: agree13:47
rkukuraI'm not clear on why VIF.port_profile is needed. Will nova be setting this, looking at this, or both?13:48
sadasurkukura: nova will look at this13:48
baolirkukrua, information in VIF.port_profile will be needed by the vif driver13:48
*** BrianB_ has joined #openstack-meeting-alt13:48
irenabrkukura: we need to propagate to neutron the SRIOV device details13:48
rkukuraSounds like it both sets and looks at it13:49
sadasuVIF.port_profile is purely from neutron to nova13:49
rkukuraSo are we saying that if it already exists, it will get stuffed into VIF.port_profile, then modified and updated on the port, then used by the VIF driver?13:50
baolirkukura, VIF.port_profile will be set while creating/updating a port. Later the port will be queried and VIF created13:50
irenaband by L2 agent if exists13:50
sadasumy MD creates a port_profile, has to pass it to nova via VIF.port_profile and will be used by the genericVifDriver13:50
baoliI should have said, port.binding.profile will be set while creating/updateing a port13:50
rkukurasadasu: I think you need to use binding:vif_details to pass data from neutron to nova.13:51
baolirkukura, with port query from nova, port.binding.profile will be returned to nova13:51
rkukurabaoli: I'm fine with storing binding:profile in the VIF object if that's needed13:52
sadasurkukura: yes....its the vif_details....port_profile is in the nova->neutron direction correct?13:52
baolirkukrua, ok13:52
rkukurasadasu: right13:52
*** noslzzp has joined #openstack-meeting-alt13:52
rkukurabut of course nova or any client can read the binding:profile value too13:52
irenabso if binding:profile exists it vill be set in binding:vif_details.profile ?13:52
baolirkukura, from neutron side, you can enforce that rule. But from nova side, both are available from the port object13:53
baoliirenab, not really13:53
rkukurabaoli: Correct, but any attempt to modify binding:vif_type or binding:vif_details via the API will fail13:53
baolirkukura, that's right. But nova wouldn't try to do that13:54
irenabI am trying to undestand rkukura suggestion for neutron->nova flow13:54
sadasurkukura: nova doesn't have to modify those fields13:54
irenabwith regards to binding:profile content that need to be passed to VIFDriver13:54
rkukuraI think we all are clear on the directions of flow at this point!13:55
*** dteselkin_ is now known as dteselkin13:55
rkukuraI've got another meeting in 5 minutes13:55
sadasuyes...just the same names are re(used) in a diff context13:55
irenabrkukura: so you are ok with baoli suggestion ?13:56
rkukuraThe suggestion to store binding:vif_details and binding:profile dicts in VIF object?13:56
sadasuactually I am ok with vif_details...can we talk about VIF.port_profile?13:56
rkukuraI'm fine with that13:56
sadasurather binding:profile...13:57
sadasuwhat would be the contents?13:57
baoliWe need to decide the fields in binding:profile13:57
*** julim has joined #openstack-meeting-alt13:57
irenabbaoli: agree13:57
baoliBut let's wrap it up today. Let's do that first thing tomorrow morning13:57
rkukuraOne field in binding:profile we've discussed is the chosen physical_network to which the SR-IOV device is attached, right?13:58
irenabaccording to the google doc, we have vendor_id, product_id and slot addres13:58
sadasurkukura: correct13:58
sadasuirenab: your MD needs it?13:58
irenabrkukura: not sure why its on profile and not vif_details13:58
sadasuvif_details is neutron->nova13:59
irenabsadasu: the device ID, yes13:59
baoliI need to attend to another meeting too. So can we resume tomorrow morning?13:59
baoliWe can also exchange emails.13:59
rkukuraI would think any SR-IOV MD would use this in bind_port() to pick the right network segment when binding13:59
irenabbaoli: sure, let's try via email too13:59
rkukuraOK, email, IRC, ...14:00
baoli#endmeeting14:00
rkukuraand gerrit14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Tue Feb 11 14:00:07 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-02-11-13.03.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-02-11-13.03.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-02-11-13.03.log.html14:00
*** heyongli has quit IRC14:00
*** Randy has joined #openstack-meeting-alt14:00
*** Randy has left #openstack-meeting-alt14:01
*** lblanchard has joined #openstack-meeting-alt14:01
*** dprince has joined #openstack-meeting-alt14:02
*** jjmb has quit IRC14:03
*** eankutse has joined #openstack-meeting-alt14:03
*** sarob has joined #openstack-meeting-alt14:05
*** dane_ has joined #openstack-meeting-alt14:07
*** sarob has quit IRC14:10
*** jjmb has joined #openstack-meeting-alt14:11
*** Haiying has joined #openstack-meeting-alt14:12
*** jmaron has joined #openstack-meeting-alt14:19
*** jjmb has quit IRC14:26
*** saju_m has quit IRC14:27
*** esker has quit IRC14:28
*** esker has joined #openstack-meeting-alt14:29
*** saju_m has joined #openstack-meeting-alt14:29
*** julienvey has joined #openstack-meeting-alt14:32
*** igor___ has joined #openstack-meeting-alt14:33
*** esker has quit IRC14:34
*** igor_ has quit IRC14:34
*** banix has joined #openstack-meeting-alt14:34
*** gokrokve has joined #openstack-meeting-alt14:34
*** lisaclark1 has joined #openstack-meeting-alt14:34
*** jecarey has joined #openstack-meeting-alt14:36
*** Barker has joined #openstack-meeting-alt14:38
*** gokrokve has quit IRC14:39
*** Haiying has quit IRC14:49
*** lisaclark1 has quit IRC14:51
*** kevinconway has joined #openstack-meeting-alt14:52
*** sadasu has quit IRC14:53
*** lisaclark1 has joined #openstack-meeting-alt14:56
*** rkukura has left #openstack-meeting-alt14:56
*** lisaclark1 has quit IRC14:56
*** nacim has quit IRC14:56
*** Barker has quit IRC14:58
*** alcabrera has joined #openstack-meeting-alt14:58
*** balajiiyer has joined #openstack-meeting-alt14:58
*** jrist has quit IRC14:59
*** malini has joined #openstack-meeting-alt14:59
*** balajiiyer has quit IRC15:00
alcabrerao/15:00
*** balajiiyer has joined #openstack-meeting-alt15:00
malinio/15:00
flwang\o/15:00
balajiiyero/15:00
flaper87o/15:00
flaper87so so so15:00
*** amitgandhi has joined #openstack-meeting-alt15:00
flaper87Kurt doesn't seem to be around15:00
flaper87kg15:00
flaper87ops15:00
alcabrerayup15:01
flaper87#startmeeting Marconi15:01
openstackMeeting started Tue Feb 11 15:01:01 2014 UTC and is due to finish in 60 minutes.  The chair is flaper87. 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: Marconi)"15:01
openstackThe meeting name has been set to 'marconi'15:01
flaper87alcabrera: do you have the agenda?15:01
flaper87:D15:01
alcabrerayes I do. :)15:01
*** amrith has joined #openstack-meeting-alt15:01
alcabrera#link https://wiki.openstack.org/wiki/Meetings/Marconi#Agenda15:01
alcabreravery packed - we'll have much discussion today15:01
flaper87#info flaper87 could get fuel out of his coffee... It's soooo deeply dark15:01
alcabreralol15:02
alcabrerathat will be the highlight of today's meeting15:02
flaper87lets get started15:02
flaper87#topic summit15:02
*** openstack changes topic to "summit (Meeting topic: Marconi)"15:02
maliniyayyy ATL15:02
alcabreraso, let's submit a talk(s)15:02
flaper87so, the idea would be to do a joint talk for the summit as we did last year15:02
alcabrera#link https://etherpad.openstack.org/p/marconi-icehouse-talk15:02
flaper87we've this week to submit the proposal15:02
flaper87the idea would be not to do an introductory talk because we expect folks to be already familiar with Marconi15:03
flaper87(at least those attending to the summit)15:03
flwangflaper87: +115:03
alcabrera+115:03
flaper87what we would like to do is present Marconi for realz15:03
flaper87Real examples, deployments and code. That is.15:03
alcabreraWe've got great titles so far15:03
flwanghow about the best practice in Rackspace ?15:03
maliniwhat abt a demo which wud replace some other queue used in OS with Marconi?15:03
maliniWithout raising controversioes of course15:04
*** Barker has joined #openstack-meeting-alt15:04
flaper87malini: good idea but I'd avoid that :(15:04
flaper87I think there's no way to do it without having people saying "YOU'RE REPLACING MY DEAR RABBIT"15:04
maliniyeah..will create too much heated discussions15:04
alcabreraflwang: I heard that oz_akan from Rackspace might be presenting on deploying Marconi (best practices, too)15:04
* flaper87 would happily eat that rabbit at lunch15:04
flwangalcabrera: cool, I will join15:05
* flaper87 hopefully didn't offend any vegan nor vegetarian in this channel15:05
flaper87so, there's an ehterpad that alcabrera already linked15:05
alcabrerabattle of the queues might be an event held elsewhere. :)15:05
flaper87lets all contribute there15:05
*** sarob has joined #openstack-meeting-alt15:05
flaper87We should agree on something by EOD15:05
flaper87and submit the proposal today / tomorrow15:05
flwangmay I get another Marconi T-shirt this time :)?15:06
maliniwhere's the etherpad? sorry I am so out of touch with tempest going on15:06
amitgandhihttps://etherpad.openstack.org/p/marconi-icehouse-talk15:06
flwanghttps://etherpad.openstack.org/p/marconi-icehouse-talk15:06
flaper87flwang: just if you put yourself in the queue15:06
flaper87:D15:06
*** nacim has joined #openstack-meeting-alt15:06
flaper87#link https://etherpad.openstack.org/p/marconi-icehouse-talk15:06
flaper87malini: ^15:06
flwangflaper87: coool, pls put me in the queue, amen15:06
alcabrera+1 about submitting by tomorrow EOD15:06
*** dane_ has quit IRC15:06
flaper87queue.post(flwang)15:07
malinithanks you for the link!15:07
alcabrerawho wants to write the proposal for the joint talk?15:07
* flaper87 is burried in stuff15:07
alcabreraI'm happy to volunteer.15:07
flaper87alcabrera: it's yours15:07
alcabreracool15:07
alcabreraaction-ize me flaper8715:07
flaper87#action alcabrera to write the talk proposal15:07
balajiiyer+1 on contributing for the talk15:07
balajiiyeralcabrera: I will chip in15:07
flaper87any other comment?15:07
*** Barker has quit IRC15:07
alcabreraalright, and there's15:08
alcabreraerr, one more15:08
alcabreraI'll see if oz_akan wants to submit an ops-marconi proposal15:08
alcabreraaction-ize me on that, too.15:08
flaper87alcabrera: that would be awesome15:08
flaper87#action alcabrera to force oz_akan to submit an ops-marconi talk proposal. Use brute force if necessary15:08
balajiiyerthinking out loud - can oz 's talk be a workshop?15:09
alcabrera#info contribute towards a great marconi proposal https://etherpad.openstack.org/p/marconi-icehouse-talk15:09
alcabreralol flaper8715:09
alcabrerahmm15:09
flaper87balajiiyer: it could, not sure how much he hast to say about it15:09
alcabreraI wonder...15:09
flaper87workshops are normally >1h15:09
maliniwe shud let oz decide how he wants to do it (A)15:09
alcabrera+1 malini15:09
balajiiyerwe will ask him to do it real sloooooow15:10
balajiiyer;)15:10
alcabreraalright :D15:10
flaper87t h i s  i s  m a r c o n i15:10
alcabreraI'd say we're ready to move on15:10
flaper87like that?15:10
flaper87ok, moving on15:10
flaper87#topic sqlalchemy15:10
alcabrerasqlalchemy ->15:10
*** openstack changes topic to "sqlalchemy (Meeting topic: Marconi)"15:10
*** sarob has quit IRC15:10
alcabreraw00t15:10
flaper87alcabrera: SO haskelized15:10
flaper87alcabrera: floor is yours15:10
alcabreralol15:10
alcabreramap (review) patches15:10
alcabreraanyway15:10
alcabrera:D15:11
alcabrerawe've got some lovely patches sitting in the review queue for sqlalchemy15:11
alcabrera#link https://review.openstack.org/#/c/70202/15:11
*** richm has joined #openstack-meeting-alt15:11
flaper87alcabrera: +115:11
flaper87thanks for the effort there15:11
alcabrera#link https://review.openstack.org/#/c/70946/15:11
alcabrera#link https://review.openstack.org/#/c/71335/15:11
alcabreraand...15:12
alcabrera#link https://review.openstack.org/#/c/70947/15:12
malinihttps://review.openstack.org/#/q/status:open+project:openstack/marconi+branch:master+topic:bp/sql-storage-driver,n,z15:12
alcabreramalini: even better!15:12
malinihope tht has all of it15:12
flaper87#link https://review.openstack.org/#/c/72677/15:12
flaper87so, I went ahead and worked on the message controller15:12
alcabrerathat's all 5 of them15:12
flaper87it should be complete now but it depends on the queue controller and the claim one (which we don't have yet)15:12
alcabrerasweet15:13
flaper87so, that review is likely to fail but we could start putting some eyes there15:13
alcabrerathanks, flaper87!15:13
flaper87on the other hand we should all work on reviewing alcabrera patches15:13
alcabrera#info flaper87 made great progress on message controller15:13
flaper87those are independent and ready to be merged15:13
alcabrera+115:13
flaper87well,ready to be reviewed15:13
flaper87:D15:13
flaper87we'll see alcabrera, we'll see15:13
flaper87:P15:13
alcabrera#info shard driver ready for review15:13
alcabreralol15:13
alcabreraso, schedule-wise...15:14
flaper87also, alcabrera patches have some things I'd love to base mine (and the queue's controller) on15:14
*** eankutse has quit IRC15:14
flaper87so, lets focus on those reviews and start testing the driver15:14
alcabrerawe're doing alright15:14
alcabreraI'll finish the catalogue driver by tomorrow EOD15:14
flaper87alcabrera: agreed, we'll make it15:14
alcabreraand then we're all caught up15:14
alcabrera+1 flaper8715:14
alcabrera#info sqlalchemy on schedule15:15
alcabreramalini: any thoughts on testing?15:15
maliniI will start working on adding the gating jobs today15:15
*** cpallares has joined #openstack-meeting-alt15:15
flaper87malini: AWESOME!15:15
alcabrerathanks! That'd be awesome. :)15:15
flaper87cpallares: welcome :)15:15
malinifirst one will be for mongo - since we already have everything in place for tht15:15
cpallareso/15:15
flaper87malini: sounds good15:16
flaper87is there anything blocking you?15:16
malinino..just me :)15:16
malinitht can be easily unblocked15:16
flaper87#action malini to unblock herself15:16
maliniI have been focussing on getting the tempest stuff merged15:16
maliniSo havent been able to spend time on the gating jobs yet15:17
flaper87malini: once we complete the work on sqlalchemy, we could help you out if there are still pending things15:17
*** ruhe_ has joined #openstack-meeting-alt15:17
malinicool  :)15:17
alcabrerasweet15:17
flaper87any other comment?15:18
alcabreraI'm good.15:18
alcabreraNext up is another hot topic15:18
flaper87#topic API v1.115:18
*** openstack changes topic to "API v1.1 (Meeting topic: Marconi)"15:18
alcabrerakgriffs is missing out. :(15:18
*** esker has joined #openstack-meeting-alt15:18
malinijust a quick tempest update before tht?15:18
flaper87#action to beat kgriffs for not being around15:18
alcabrerasure thing, malini15:18
flaper87#topic tempest update15:18
*** openstack changes topic to "tempest update (Meeting topic: Marconi)"15:18
*** esker has quit IRC15:18
maliniI think I am really close - but keeps moving an inch away each time15:19
malini:|15:19
maliniI submitted another patch y'day for devstack https://review.openstack.org/#/c/72412/15:19
*** esker has joined #openstack-meeting-alt15:19
alcabrera#link https://review.openstack.org/#/c/63449/15:19
alcabrera#link https://review.openstack.org/#/c/72412/15:19
alcabreragetting close15:19
maliniHave two +2s , so might get merged soon - but it needs another patch to be merged before 72412 can be merged15:20
flaper87not sure why there are to +2s and no approve15:20
alcabrera#info malini making good progress on marconi/temptest integration15:20
flaper87malini: feel free to ping them on irc15:20
*** AlanClark has joined #openstack-meeting-alt15:20
maliniflaper87: I already am15:20
flaper87malini: awesome15:20
malinihttps://review.openstack.org/#/c/69497/ might end up as a blocker for us15:20
*** yanndegat has joined #openstack-meeting-alt15:20
alcabrerahmmm15:21
alcabrerarefactoring patch!15:21
maliniyeah..15:21
maliniBut I'll keep pinging folks so we can get tempest merged15:21
alcabrerawell, hopefully that comes along quickly15:21
alcabrerawe'll see15:21
flaper87malini: +115:21
malinitht's it for tempest update15:21
flaper87malini: thanks a lot for the update and the hard work there15:22
malinias far as grad req go15:22
maliniwe need to have a 'basic devstack gate job in place'15:22
flaper87ok15:22
maliniSo hopefully we'll be covered with the basic tempest patch merged15:22
flaper87malini: awesome! That would cover API v115:23
flaper87right?15:23
flaper87Do you think moving to API v1.1 will be hard ?15:23
maliniright now all we have is a basic create queue15:23
maliniflaper87: moving to 1.1 wont be hard15:23
flaper87cool15:23
maliniis 1.1 needed to graduate?15:23
flaper87that makes me happy15:23
alcabreramalini: no15:23
flaper87no but it is for icehouse15:23
flaper87I mean, it would be nice to release 1.1 as part of icehouse15:24
flaper87hence, we need to test it15:24
alcabrera#info extending tempest test suite to include v1.1 not expected to be difficult15:24
*** jmaron has quit IRC15:24
malinitht shud be do-able15:24
flaper87cool beans15:24
*** michael-yu has joined #openstack-meeting-alt15:24
* flaper87 doesn't know where "cool beans" comes from but he learned that from kgriffs15:24
malini:D15:24
alcabreralol15:25
flaper87anyway, moving on15:25
alcabrerayup15:25
flaper87#topic API v1.115:25
*** openstack changes topic to "API v1.1 (Meeting topic: Marconi)"15:25
alcabreraback to api v1.115:25
flaper87#link https://wiki.openstack.org/wiki/Marconi/specs/api/v1.115:25
flaper87that's the spec15:25
flaper87I imagine you know it all15:25
alcabrerahahaha15:25
alcabreraon good days, yes15:25
flaper87:P15:25
alcabreraI added sharding to that document last week15:26
flaper87so, I took a quick look and it seems to be in good shape15:26
alcabreraso we're offering quite a jump in power15:26
alcabreragoing from 1.0 -> 1.115:26
alcabreraI agree that it looks good15:26
flaper87Something that makes me happy is that we're not doing any change to the schema in the database15:27
alcabrerathat's often a good sign - we have a good foundation15:27
flaper87for the record, we're going to basically copy v1 into v1.1 and change it15:27
alcabrera+115:27
flaper87that's not what we want to do in the long run but it's the best we can do now15:27
* alcabrera forsees much refactoring15:27
flaper87during June, I'd like us to dedicate some time figuring out a better way to do that15:28
flaper87hopefully the experiment cpallares is working on will be of great help there15:28
alcabreraoh yes15:28
cpallares\o/15:28
flaper87AFAIK, cpallares said it's all done and she's been using it for a couple of weeks already15:28
flaper87OOOOOOOOPSSSSSSSSSSS15:28
flaper87she's here15:28
alcabreralol15:28
cpallareslol15:29
cpallaresit needs tweaking15:29
flaper87so, does anyone have comments w.r.t the API spec ?15:29
alcabreranot I15:29
flaper87Lets make sure we make those comments NOW15:29
alcabreraoh15:29
alcabreraone thing15:29
flaper87and by now I mean before implementing it15:29
flaper87:P15:29
flaper87alcabrera: gp15:29
flaper87go15:29
alcabrerareturning an empty default body things like GET messages is great15:30
alcabrerainstead of 20415:30
maliniha sit already been emailed out to openstack-dev ML ?15:30
malinihas it *15:30
alcabrerait simplifies the handling a bit15:30
alcabreradefault reprs are a nifty idea we should do more of in the future15:30
alcabrerathat's it15:30
alcabreramalini: I'm not sure... flaper87?15:30
flaper87it hasn't been sent to the m-l yet15:31
alcabrerawe should action-ize that - who wants to write email? :D15:31
flaper87alcabrera: +1 for empty default bodies15:31
* alcabrera looks at ghostly kgriffs15:31
flaper87#action send the v1.1 spec to the mailing list15:31
*** ttx has joined #openstack-meeting-alt15:31
alcabrerahehe15:31
*** ttx has quit IRC15:31
*** ttx has joined #openstack-meeting-alt15:31
alcabreraalright, so let's move on to specific v1.1 items15:31
flaper87comments?15:32
*** david-lyle has joined #openstack-meeting-alt15:32
flaper87#topic health endpoint15:32
*** openstack changes topic to "health endpoint (Meeting topic: Marconi)"15:32
flaper87flwang: alcabrera floor is yours15:32
alcabreraflwang: regarding v1.1 /health, it seems like the way to go is to start a v1_1 directory and implement it there15:32
*** jmaron has joined #openstack-meeting-alt15:32
flwangalcabrera: ok15:33
alcabreraso what we have now is marconi.queues.transport.wsgi. We need is marconi.queues.transport.wsgi.v1 and marconi.queues.transport.wsgi.v1_115:33
alcabrerathoughts?15:33
alcabreradoes this align with our v1.1 strategy alright?15:33
flaper87alcabrera: that sounds like a plan15:33
alcabreracool15:33
alcabreraso that15:33
alcabrera's two steps15:33
*** jcoufal_ has joined #openstack-meeting-alt15:33
flaper87I can do pacakage moving thing if you guys want15:34
alcabrera1. separate our current API into v115:34
alcabrera2. implement health in v1_115:34
alcabreraflaper87: that'd be awesome!15:34
alcabrerayes, please15:34
alcabrera:D15:34
*** gokrokve has joined #openstack-meeting-alt15:34
flwangalcabrera: agree and we may need to implement the /ping first15:34
flaper87#action flaper87 to put the wsgi transport under the v1 version and clone it to v1_115:34
alcabreracool15:34
alcabrera#action flwang to continue work on /health and /ping for v1.115:35
alcabreraany other thoughts?15:35
flaper87not from me15:35
flwangalcabrera: cool15:35
alcabrerasweet15:35
alcabreraflaper87: grace not required - the floor is yours15:35
alcabrera:D15:35
flwangI will implement the /ping endpoint first15:35
flaper87#topic Grace not required15:35
*** openstack changes topic to "Grace not required (Meeting topic: Marconi)"15:35
flaper87SOOOOO15:36
*** boris-42_ has quit IRC15:36
malinitht is disgraceful15:36
*** jcoufal has quit IRC15:36
flaper87I found out today (and don't laugh at me) that we require grace15:36
alcabrerait gets me every time, hehe15:36
flaper87I don't think that makes much sense TBH15:36
malini:D15:36
alcabreraagreed15:36
flaper87first impression from a user stand point is: WTF?15:36
flaper87the second is: What should I use?15:36
*** noslzzp has quit IRC15:36
alcabreraand all under the covers15:37
flaper87the third is: I'll put whatever comes to my mind in 3 2 1 ...15:37
alcabrerattl = ttl + grace15:37
alcabrerathe magic secret15:37
alcabrerawhich is confusing15:37
flaper87exactly15:37
flaper87so, we should accept it but not require it15:37
alcabrera+115:37
alcabreraI'd even go so far as suggesting we remove it from the public API for v1.1 or v2.015:37
alcabrerait's an implementation detail15:37
*** eanxgeek is now known as eanxgeek|log15:37
alcabrerawe can offer wiggle room internally15:37
alcabreraconfigurable and all15:37
flaper87mmh15:38
alcabrerabut users should only need to care about TTL15:38
flaper87so, the change I was proposing was for v1.115:38
flaper87but if we think removing it makes more sense then fine15:38
maliniso have a default grace value, but use config value if provided?15:38
*** SushilKM has joined #openstack-meeting-alt15:38
flaper87although, removing it requires a major release15:38
flaper87maybe15:38
alcabreraI'm advocating: mark as deprecated in public API v1.1, remove in v2.015:38
flaper87alcabrera: +115:38
flaper87sounds like a plan15:38
flaper87lets see what kgriffs thinks15:39
alcabrerayup15:39
alcabrerato address malini15:39
alcabrera's question15:39
*** gokrokve has quit IRC15:39
alcabreraFor now, users have to provide it. The plan is to make it optional, and use a deployment-time/config option to replace it. The operator decides the wiigle grace.15:39
alcabrera*wiggle15:39
flaper87I don't quite remember why we thought that requiring it makes sense15:40
malinialcabrera: thanks!! that makes sense15:40
flaper87I'm pretty sure there's a reason15:40
*** noslzzp has joined #openstack-meeting-alt15:40
alcabrerawe'll find out from kgriffs later. ;)15:40
flaper87but it doesn't make sense to me now15:40
flaper87alcabrera: yeha15:40
flaper87yeah15:40
alcabreraso let me info this and let's move on. :D15:41
*** michael-yu has quit IRC15:41
alcabrera#info /claims grace to be deprecated in v1.1 and removed in v2.015:41
flaper87awesome, thanks15:41
flaper87moving on15:41
alcabreralet's talk about gacks and pops, flaper8715:41
flaper87#topic Add gack and/or pop15:41
*** openstack changes topic to "Add gack and/or pop (Meeting topic: Marconi)"15:41
flaper87#topic Add gack and/or pop to API v1.115:42
*** openstack changes topic to "Add gack and/or pop to API v1.1 (Meeting topic: Marconi)"15:42
flaper87:D15:42
*** jrist has joined #openstack-meeting-alt15:42
alcabreracould you elaborate on these two ideas, flaper87?15:42
flaper87First, let me explain what gack and pop are15:42
*** coolsvap has joined #openstack-meeting-alt15:42
flaper87Gack (not exacly the best name) is basically get and ack15:42
flaper87the idea behind it is to be able to get a message and make sure *no one else will*15:42
flaper87when getting a message and then claiming it it is possible that some other client would try to do the same15:43
flaper87this means that a message could be delivered more than once15:43
alcabreradoesn't /claim already fetch the message(s) for you?15:43
flaper87and the jobs executed twice15:43
flaper87mmh, does it ?15:43
flaper87:D15:43
alcabreraI thought so. :P15:43
* alcabrera checksa15:43
alcabrera#link https://wiki.openstack.org/wiki/Marconi/specs/api/v1.1#Claim_Messages15:44
flaper87If it does then that covers gack which is awesome15:44
alcabrerayes, it does15:44
flaper87I bet it is a mix of claim + limit15:44
flaper87ah ok, v1.115:44
flaper87ok ok15:44
alcabreraso gack == claim?limit=115:44
flaper87yeah15:44
flaper87I'd say we don't need it then.15:44
alcabrera#info gack is already provided as /claim?limit=115:44
flaper87folks can claim 1 message15:44
flaper87next one, and alcabrera I'm sure as hell we don't have it, is pop15:45
flaper87:D15:45
*** saju_m has quit IRC15:45
flaper87this is basically get-and-delete15:45
alcabreraheh15:45
alcabreraso atomic get-and-delete15:45
flaper87yeah15:45
flaper87this is pretty useful for things like kombu15:45
*** sarob has joined #openstack-meeting-alt15:45
*** eanxgeek|log is now known as eanxgeek15:46
flaper87where you want to get a message out of the queue and you don't want to make another call to delete it15:46
alcabrerahmmm15:46
*** saju_m has joined #openstack-meeting-alt15:46
flaper87Avoiding those 2 calls we would make the client life easier and Marconi's server load lower15:46
alcabrerathere's a tricky point there I worry about, having used marconi extensively recently15:46
flaper87shoot15:46
alcabreraSo, a worker claims a message15:47
alcabrerathat worker maybe does somethings15:47
alcabrerathen crashes before deleting the message after doing those things15:47
*** jrist has quit IRC15:47
* alcabrera tries to think this through more clearly15:47
alcabreraThe gist of it: I'm worried that -15:47
malinialcabrera: tht is exactly what I am thinking too15:48
maliniI cannot think of an use case15:48
flaper87so, if the worker uses pop, it doesn't have to delete the message from the queue. The message will be deleted when it gets the message15:48
alcabreraif claim-and-delete is used, the task might never really get processed if a worker crashes15:48
alcabrera*get-and-delete15:48
maliniit sounds like a claim with delete built in15:48
flaper87alcabrera: ah yeah but that's up to the implementation15:48
flaper87I mean, we can't protect the client from that15:48
alcabrerahmmm15:48
flaper87that's up to the client15:48
alcabreratrue15:48
alcabreraso15:48
alcabreragiven that15:48
alcabreraI'm in favor of this pop behavior15:48
flaper87what we can is give it an easier way to do claim->delete15:48
alcabreragiven that clients can still manually do things if they want to separate the claim from the delete15:49
flaper87indeed15:49
alcabreracool15:49
alcabrerawhat do you think, malini?15:49
flaper87I mean, a client could also do: claim->delete and then crash15:49
*** muralia has joined #openstack-meeting-alt15:49
flaper87so, we won't ever be able to protect them from that15:49
flaper87we can make it easier for them to shoot their own feet though15:49
flaper87:P15:49
alcabreraheh15:50
maliniif it crashes after processing, we are ok15:50
alcabrerakk15:50
malinithe message is not lost in tht case15:50
*** sarob has quit IRC15:50
*** lisaclark1 has joined #openstack-meeting-alt15:50
*** jjmb has joined #openstack-meeting-alt15:50
*** paulmo has joined #openstack-meeting-alt15:50
flaper87Thing is that get-and-delete is a common pattern and doing claim->delete will be expensive for both the client and marconi15:51
*** DinaBelova is now known as DinaBelova_15:51
flaper87#info pop seems to be a good idea. It needs further discussion and it may make sense to have it for v1.115:51
alcabreraI'm in favor of pop as an optimization, since alternate operations are still available15:51
alcabrera+115:51
alcabrerathat's the info I would've given. :D15:52
flaper87any other comment?15:52
maliniflaper87: agreed abt more ops being expensive..will do some homework on kombu to understand an use case15:52
alcabreranone form me15:52
*** jjmb has quit IRC15:52
alcabrera*form15:52
alcabrera...15:52
alcabrera*from15:52
alcabreranext15:52
flaper87#topic Open Discussion15:52
*** openstack changes topic to "Open Discussion (Meeting topic: Marconi)"15:52
alcabrerayup - +1 for open discussion15:52
alcabrerawe don't have much time left to review BPs/bugs15:52
flaper87So, at the next summit, kgriffs said he wants to offer beers, food and whatever we want15:53
flaper87he told me to share this with y'all15:53
alcabreralol15:53
malini:D15:53
alcabrerathis kgriffs fellow is very generous15:53
alcabrera<315:53
*** jjmb has joined #openstack-meeting-alt15:53
flaper87#action Everyone to thank kgriffs for being so nice and paying for whatever we need at the next summit15:53
alcabrerayaaay15:53
alcabrera#info this kgriffs fellow is very generous15:53
alcabrerabetter15:53
flaper87so, I've been burried in stuff lately15:53
alcabreraah15:53
maliniwe are getting buried in snow ;)15:54
cpallareslol15:54
flaper87but I'd ask everyone to do an extra efford and review the sqlalchemy patches15:54
flaper87give them some priorities over other things15:54
flaper87not sure why I said "some priorities" but anyway, you got my point15:54
flaper87malini: it hasn't snowed much here this winter :(15:55
*** lisaclark1 has quit IRC15:55
alcabreratwo non-sqlalchemy patches want review love, too15:55
alcabrera#link https://review.openstack.org/#/c/68267/15:55
alcabrera^^ guard against bad URI in shard registration15:55
alcabreraand...15:55
*** gokrokve has joined #openstack-meeting-alt15:55
alcabrera#link https://review.openstack.org/#/c/70463/15:55
alcabreracleanup limit configs - great refactoring15:55
flaper87alcabrera: dude, stop coding, you're burrying us all with reviews15:55
alcabreralol15:55
alcabrera;D15:55
*** devkulkarni has joined #openstack-meeting-alt15:56
flaper87so, any other comment ?15:56
*** gokrokve_ has joined #openstack-meeting-alt15:56
flaper87any cat that needs to be rescued ?15:56
alcabrerayaks need shaving?15:56
alcabrera*needing15:56
flaper87ok, that's all folks!15:56
alcabreraI think we're good.15:56
alcabrerathanks for joining!15:57
flaper87thanks everyone and see you in #openstack-marconi15:57
flaper87#endmeeting15:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:57
openstackMeeting ended Tue Feb 11 15:57:07 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-02-11-15.01.html15:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-02-11-15.01.txt15:57
openstackLog:            http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-02-11-15.01.log.html15:57
alcabreraI15:57
alcabrera'll grab those minutes. :)15:57
*** paulczar has joined #openstack-meeting-alt15:57
*** noorul has joined #openstack-meeting-alt15:58
*** jjmb has quit IRC15:58
*** gokrokve has quit IRC15:59
*** adrian_otto has joined #openstack-meeting-alt16:00
adrian_otto#startmeeting Solum Team Meeting16:00
openstackMeeting started Tue Feb 11 16:00:58 2014 UTC and is due to finish in 60 minutes.  The chair is adrian_otto. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: Solum Team Meeting)"16:01
openstackThe meeting name has been set to 'solum_team_meeting'16:01
*** cpallares has left #openstack-meeting-alt16:01
*** amitgandhi has left #openstack-meeting-alt16:01
*** Barker has joined #openstack-meeting-alt16:01
*** rajdeep has joined #openstack-meeting-alt16:01
adrian_otto#link https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2014-02-11_1600_UTC Our Agenda16:01
adrian_otto#topic Roll Call16:02
*** openstack changes topic to "Roll Call (Meeting topic: Solum Team Meeting)"16:02
adrian_ottoAdrian Otto16:02
paulmoPaul Montgomery16:02
muraliamurali allada16:02
stanniePierre Padrixe16:02
paulczarPaul Czarkowski16:02
julienveyJulien Vey16:02
nmarchenkoNikita Marchenko, Mirantis16:02
devkulkarniDevdatta16:02
rajdeepRajdeep Dua16:02
*** sarob has joined #openstack-meeting-alt16:02
noorulNoorul Islam16:02
*** jrist has joined #openstack-meeting-alt16:02
coolsvapSwapnil16:02
*** aratim has joined #openstack-meeting-alt16:03
adrian_ottohello everyone16:03
*** alcabrera has left #openstack-meeting-alt16:03
adrian_ottofeel free to chime in at any time to record your attendance if you have not already16:04
adrian_otto#topic Announcements16:04
*** openstack changes topic to "Announcements (Meeting topic: Solum Team Meeting)"16:04
adrian_ottowe have selected a date for our upcoming for Solum Summit16:04
adrian_ottotwo dates, actually16:04
adrian_ottoTuesday, March 25, 201416:04
adrian_ottoWednesday, March 26, 201416:04
*** sarob_ has joined #openstack-meeting-alt16:05
adrian_ottoRed Hat has offered to host us in North Carolina16:05
*** lisaclark1 has joined #openstack-meeting-alt16:05
adrian_ottowe will get you additional details on the specifics soon16:05
adrian_ottoso that you can plan your travel arrangements.16:05
*** isviridov has joined #openstack-meeting-alt16:06
adrian_ottofor those of you planning to attend remotely, please earmark your time on these dates to ensure your availability16:06
adrian_ottonext up, I created a bunch of new blueprints for the various API resources16:06
*** jrist has quit IRC16:06
*** atiwari has joined #openstack-meeting-alt16:06
adrian_ottothey don't have details in them. If you are interested, links to them are in the agenda16:06
*** yanndegat has quit IRC16:07
*** sarob has quit IRC16:07
devkulkarniadrian_otto: thanks for creating these!!16:07
nooruladrian_otto: Good :)16:07
adrian_ottoYou can thank me once I've put the grinding hours into fleshing each one out ;-)16:07
*** yanndegat has joined #openstack-meeting-alt16:07
adrian_ottothe good news is that we actually have code for all of these already16:07
adrian_ottoso this is not a lift from zero.16:07
devkulkarnitrue.16:08
*** eankutse has joined #openstack-meeting-alt16:08
*** eankutse has quit IRC16:08
adrian_ottobut this gives us a place to focus design work in a place with more narrow scope16:08
*** jjmb has joined #openstack-meeting-alt16:08
*** eankutse has joined #openstack-meeting-alt16:08
adrian_ottook, next topic16:08
adrian_otto#topic Review Action Items16:08
*** openstack changes topic to "Review Action Items (Meeting topic: Solum Team Meeting)"16:08
adrian_ottoACTION adrian_otto to hold a vote for next F2F location16:08
adrian_ottoStatus: Completed16:09
adrian_ottoACTION adrian_otto remove https://blueprints.launchpad.net/solum/+spec/solum-zuul-integration Solum integration with Zuul (devdatta-kulkarni) from recurring agenda, to be combined with https://blueprints.launchpad.net/solum/+spec/solum-git-pull16:09
adrian_ottoStatus: Completed16:09
adrian_ottoalthough I have a question about this16:09
devkulkarniyes..16:09
adrian_ottokraman owned the second16:09
adrian_ottoand devkulkarni owned the first16:09
adrian_ottowho should I ask for the updates for the combination of the two?16:09
*** aignatov is now known as aignatov_16:09
devkulkarniadrian_otto: I think anyone of us can give updates. we are working together on this.16:10
adrian_ottook16:10
adrian_ottoand our last action item16:10
adrian_ottoACTION kraman to submit zuul work into Gerrit as WIP for review. Tests to be added as they are created.16:10
devkulkarniI think kraman is out today. I can give an update on this.16:10
adrian_ottook16:11
devkulkarniI am going to work with kraman today/tomorrow to start submitting WIPs for review. I have more updates which I can give now or when we go to BP status discussion.16:11
*** SushilKM has quit IRC16:11
adrian_ottook, so I should resubmit this as an open action for this week, correct?16:12
*** jrist has joined #openstack-meeting-alt16:12
devkulkarniyes, that makes sense16:12
adrian_ottoshould I keep it assigned to kraman, or assign it to devkulkarni?16:12
devkulkarnifor now I would say lets keep it assigned to kraman..16:12
adrian_otto#action kraman to submit zuul work into Gerrit as WIP for review. Tests to be added as they are created.16:12
*** balajiiyer has quit IRC16:12
devkulkarniI will check with him if we want to reassign it16:12
adrian_ottook, so I will revisit that next week for status.16:12
devkulkarnisounds good.16:13
*** jrist has quit IRC16:13
*** balajiiyer has joined #openstack-meeting-alt16:13
adrian_ottoready to begin Blueprint updates?16:13
adrian_otto#topic Review Blueprints: https://launchpad.net/solum/+milestone/milestone-116:13
*** openstack changes topic to "Review Blueprints: https://launchpad.net/solum/+milestone/milestone-1 (Meeting topic: Solum Team Meeting)"16:13
*** RaymondWong has quit IRC16:13
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/api Solum API (aotto)16:13
*** RaymondWong has joined #openstack-meeting-alt16:13
adrian_ottothere has been a lot of progress on this. Many reviews were posted over the past two weeks to add methods to the api, and wire them to the db layer16:13
adrian_ottoI also created 7 new blueprints for the API16:14
*** denis_makogon has quit IRC16:14
adrian_ottowhich I will report status on at this position in the agenda.16:14
adrian_ottofeel free to claim those blueprints if you have open reviews against them16:14
adrian_ottoalso, please resubmit your commit messages to reference these blueprints16:14
devkulkarniabout that..16:14
adrian_ottodevananda: yes?16:15
*** denis_makogon has joined #openstack-meeting-alt16:15
adrian_ottodevkulkarni: yes?16:15
devkulkarnihas anyone figured out why blueprint links in the commit message do not go to solum project?16:15
adrian_ottosorry devananda16:15
*** eankutse1 has joined #openstack-meeting-alt16:15
*** jcoufal_ is now known as jcoufal16:15
adrian_ottoYes!16:15
adrian_ottothat happens because the blueprint slug does not start with the word solum16:15
adrian_ottoso they are not necessarily unique16:16
adrian_ottoall of the ones I create are properly named, so that should work properly for you16:16
noorulI thought it is because solum is not yet part of openstack16:16
adrian_ottoalso, I have been renaming them as I approve them to prevent this from continuing with new ones16:16
*** eankutse has quit IRC16:16
adrian_ottono, it's a quirk about the way that Gerrit links to Launchpad16:16
nooruladrian_otto: That seems to be incorrect, See https://review.openstack.org/#/c/71923/16:17
*** jrist has joined #openstack-meeting-alt16:17
*** lisaclark1 has quit IRC16:17
adrian_ottonoorul: oh, I see.16:17
*** jmontemayor has joined #openstack-meeting-alt16:17
noorulI remember asking this question initially to infra and they said it is because we are not part of openstack yet16:18
adrian_ottook, so that should work at such time that this project enters an incubation phase16:18
adrian_ottook, sorry for the misinformation before16:18
*** jmontemayor has quit IRC16:18
adrian_ottoso I still want to have the references in the commit messages16:19
*** jmontemayor has joined #openstack-meeting-alt16:19
devkulkarniso in the interim, do we put direct links in the commit message? I think gokrokve_ did that for some of his patches16:19
adrian_ottoeven if the links do what they do now16:19
adrian_ottowe can put both in16:19
adrian_ottoanother option is to put a comment in as you submit the patch that has the full link16:19
adrian_ottothat way you won't run into the caracter maximum for a line in the commit message16:20
adrian_ottos/caracter/character/16:20
*** gokrokve_ has quit IRC16:20
*** tomblank has joined #openstack-meeting-alt16:20
*** balajiiyer has left #openstack-meeting-alt16:20
devkulkarniokay. that would work.16:20
adrian_ottomore thoughts on the API work?16:20
adrian_ottoI will mention...16:20
noorulAre all these APIs required for M1?16:21
adrian_ottomuralia has stepped up to help with fleshing out the API for the enablement of the CLI tool16:21
adrian_ottonot all capabilities of all resources are required for M116:21
adrian_ottoI will make it clear in the blueprint descriptions wich parts are essential16:21
adrian_ottowe need to be able to create/modify/delete plans and assemblies16:21
adrian_ottoand list assemblies16:22
noorulI think it is right time we come up with the list of items we should concentrate for M116:22
adrian_ottothat should be enough to start16:22
*** lisaclark1 has joined #openstack-meeting-alt16:22
devkulkarniadrian_otto: noorul has shown the way of how to do this, muralia is taking it from there. (btw, that is the update for the next bp)16:22
adrian_ottonoorul: I agree completely. We ahve an agenda item for that16:22
adrian_ottofor today16:22
adrian_ottonice segway devkulkarni16:22
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/solum-minimal-cli Command Line Interface for Solum (devdatta-kulkarni)16:22
*** gokrokve has joined #openstack-meeting-alt16:23
noorulsubmitted around 6 patches last week16:23
devkulkarni:) thanks noorul. thanks muralia16:23
muraliasure16:23
devkulkarninoorul: awesome stuff!!16:23
noorulThanks16:23
noorulI was thinking whether we should add functional tests16:24
adrian_ottonoorul: +1 Thanks!16:24
adrian_ottoon the subject of the functional tests...16:24
devkulkarninoorul: what do other projects do?16:24
noorulThey have it in tempest, but some read only operations alone16:25
adrian_ottoother projects really don't test much, as the tests for the CLI are relatively low value16:25
adrian_ottoTrove for example just runs the cli script to cause it to emit the API version16:25
adrian_ottoand does a string check against that to be sure it's the expected string value16:25
devkulkarniwhat do recent projects like Heat do?16:25
adrian_ottoand that's the extent of the test16:25
noorullet us not add it now16:26
noorulI have another question16:26
noorulhttps://etherpad.openstack.org/p/MinimalCLI16:26
adrian_ottoI think it's a pretty low value test, so we should focus on features16:26
noorulIt just talks about assembly and app16:26
*** Leonr has joined #openstack-meeting-alt16:26
noorulWhat about other resources?16:26
adrian_ottothose are the two essential to basic operation16:27
noorulAm I missing something?16:27
adrian_ottoapp = plan16:27
adrian_ottoso if we have plans and assemblies working, we can demonstrate simple end-to-end functionality16:27
*** Barker has quit IRC16:27
noorulHow can I define component, lang pack ,etc?16:27
adrian_ottogood question...16:27
adrian_ottocomponents get defined by Solum when interpreting the plan16:28
adrian_ottoand the first language pack can be pre-loaded in the base distribution16:28
muraliaWe should take a second look and see if this etherpad has everything required for M1. I can do that and update it in the next few days as I start work on the CLI16:28
*** _nadya_ has joined #openstack-meeting-alt16:29
noorulI see16:29
adrian_ottomuralia: are you willing to take that as an action item?16:29
muraliayes16:29
adrian_ottoI would love your help with that16:29
muraliasure. I'll do that16:29
noorulIt will be great if you can provide an example16:30
adrian_otto#action muralia to review https://etherpad.openstack.org/p/MinimalCLI to verify that everything for M1 is tracked, and placed into the appropriate blueprints.16:30
*** demorris has joined #openstack-meeting-alt16:30
noorulHow user will invoke assembly create with all those data?16:30
adrian_otto#action adrian_otto to support muralia for review of https://etherpad.openstack.org/p/MinimalCLI 16:30
muralianoorul: sure. i'll provide examples16:31
adrian_ottonoorul: what data are you concerned about?16:31
*** bnemec has quit IRC16:31
noorulmuralia: ok thanks16:31
nooruladrian_otto: How do we pass all these info in command line16:31
adrian_ottothe info placed into the plan file is what we use as input16:31
*** eankutse1 has quit IRC16:32
nooruladrian_otto: Oh I se16:32
nooruladrian_otto: got it16:32
adrian_ottothat goes into the plan, and is subsequently given to the assembly16:32
adrian_ottook, good16:32
*** eankutse has joined #openstack-meeting-alt16:32
adrian_ottoany mote on this topic?16:32
adrian_ottomore16:32
noorulI am good16:32
adrian_ottoNext is two blueprints combined as a single update subject16:33
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/solum-git-pull Pull integration of Solum from an external Git repo (kraman)16:33
adrian_otto                #link https://blueprints.launchpad.net/solum/+spec/solum-zuul-integration Solum integration with Zuul (devdatta-kulkarni)16:33
devkulkarniI have following updates:16:33
*** RajeshMohan has quit IRC16:33
*** gyee has joined #openstack-meeting-alt16:33
*** RajeshMohan has joined #openstack-meeting-alt16:33
*** claytonc has joined #openstack-meeting-alt16:33
*** RajeshMohan has quit IRC16:33
*** RajeshMohan has joined #openstack-meeting-alt16:33
devkulkarni1) For Solum specific changes we had to modify Zuul's scheduler. I have added tests to those.16:34
*** bnemec has joined #openstack-meeting-alt16:34
devkulkarni2) I am working with kraman to split the code and tests into patches to be submitted to Zuul repo16:34
adrian_ottoclaytonc: wlecome. devkulkarni is giving us the update on Git pull and Zuul16:34
claytoncsorry about the delay16:34
devkulkarni3) We still need tests to be added for the changes to the layout in Zuul. Will be working with coolsvap to get those in16:35
devkulkarni4) We discussed about an 'interim service'.16:35
devkulkarniThere is not a concrete plan yet about how to build it, but..16:35
*** markwash has joined #openstack-meeting-alt16:35
claytoncdevkulkarni: correct me if i'm wrong but we hypothesized not needing an interim service because we could fill that role via the hooks16:36
devkulkarniyesterday asalkeld seemed to be thinking along those lines as well and he said he will create a wiki page with his thoughts/ideas etc. I am planning to get this to tomorrow's git-integration meeting16:36
claytoncwill take that to the meeting tomorrow though16:36
devkulkarniclaytonc: cool. we can discuss more then.16:36
devkulkarniadrian_otto: that is all.16:37
adrian_ottook, let's get that wiki linked as the design to the "https://blueprints.launchpad.net/solum/+spec/solum-git-pull/+edit" of the blueprint16:37
devkulkarnisure.16:37
adrian_ottook, also, I'd like to have you add the link to the breakout meetings into our agenda here16:37
adrian_ottoI think that will help us follow along16:37
devkulkarniokay. can do that from next time16:38
adrian_ottoso as soon as you generate the chat log.minutes, please add them to https://wiki.openstack.org/wiki/Meetings/Solum16:38
adrian_ottothat way I can link to them in the subsequent team meeting so they become more visible to the wider audience16:38
devkulkarnisounds good.16:38
adrian_ottoI think we are already recording those on the breakout meeting wiki page, right?16:38
adrian_ottoif not, we should get back into that habbit16:39
devkulkarniI will have to double check..16:39
claytonci'm pretty sure they are16:39
claytoncbut we missed one meeting and rescheduled another16:39
adrian_ottonot critically important, but it would be nice for the full history to be linked there16:39
claytoncwill follow up16:39
adrian_otto#action claytonc t make sure that https://wiki.openstack.org/wiki/Solum/BreakoutMeetings links to all logs and minutes from breakout meetings we have held16:40
adrian_ottothanks claytonc16:40
adrian_ottomore on this topic?16:40
*** jjmb has quit IRC16:41
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/specify-lang-pack Specify the language pack to be used for app deploy (devdatta-kulkarni)16:41
devkulkarniHere are the updates on this:16:41
devkulkarniaratim has been making great progress on the data model definition, which was the remaining part of this work.16:41
*** julienvey has left #openstack-meeting-alt16:42
devkulkarnibtw, thanks claytonc for discussions the other day about the data model16:42
devkulkarnianother thing is.. we need to start including the plan work either in this bp or discuss it as part of some other bp.16:42
*** garyk has quit IRC16:42
*** ruhe_ has quit IRC16:43
claytoncdevkulkarni: agreed16:43
*** sarob_ has quit IRC16:43
adrian_ottowhich plan work do you mean, devkulkarni?16:43
devkulkarnithe title of the bp is 'specify-lang-pack'. what aratim is part of the story — 'get the list of available lang-packs'.16:43
*** DinaBelova_ is now known as DinaBelova16:43
devkulkarniadrian_otto: the work that asalkeld has done on the plan API.16:43
*** sarob has joined #openstack-meeting-alt16:43
devkulkarni*aratim's work is part of the story of this bp16:44
aratimI am currently working on connecting the lang pack API to the DB16:44
devkulkarniwe could rename this bp to something like 'get-lang-pack' and then it should be fine16:45
devkulkarnisince there is already a bp for plans16:45
adrian_ottodevkulkarni: perhaps we could land that on https://blueprints.launchpad.net/solum/+spec/solum-api-plan16:45
aratim+1 devkulkarni16:45
adrian_ottowait16:45
*** hockeynut has joined #openstack-meeting-alt16:46
adrian_ottolet's not rename a bp that we have linked to in prior meeting minutes16:46
devkulkarnioh right!!16:46
adrian_ottoif we need another BP, we can make a new one16:46
devkulkarniI can create a new bp and link it to the specify-lang-pack bp.16:46
*** gokrokve has quit IRC16:47
adrian_ottosounds like it would be one that depends on the current blueprint16:47
claytoncscope of this BP - defining how plans change as language packs generate DU's, and how plans are used to create templates?16:47
*** gokrokve has joined #openstack-meeting-alt16:47
*** hockeynut has quit IRC16:48
adrian_otto#action devkulkarni to make a new blueprint for language pack selection that would have a dependency link relation with specify-lang-pack16:48
devkulkarniclaytonc: actually, no. I was referring to a BP that will capture the work that aratim is doing.16:48
*** sarob has quit IRC16:48
claytoncah16:48
adrian_ottook, ready to advance to the next item in the agenda?16:48
devkulkarniadrian_otto: that is all16:49
*** hockeynut has joined #openstack-meeting-alt16:49
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/logging Logging Architecture (paulmo)16:49
paulmoAfter much discussion and design, I created a new pull request for logging/trace: https://review.openstack.org/#/c/71970/16:49
paulmoIf folks like Angus, kgriffs, gokrokve and anyone else interested could take a look at it and give feedback, I would appreciate it.16:49
adrian_ottothanks for putting that together, paulmo!16:50
adrian_ottoquestions on that item?16:50
paulmotrace_test.py can be run to see an example with lots of comments inline.16:50
adrian_ottothanks paulmo.16:50
adrian_otto#topic M1 Completion16:50
*** openstack changes topic to "M1 Completion (Meeting topic: Solum Team Meeting)"16:50
adrian_ottoDo we have all gaps addressed?16:50
devkulkarniadrian_otto: Deployment workflow bp is missing in the list of BP updates.16:51
adrian_ottoRoshan is working on a new wiki page that further describes the ideal end-to-end user experience16:51
*** Barker has joined #openstack-meeting-alt16:51
*** gokrokve has quit IRC16:51
adrian_ottodevkulkarni: yes, let's get that in there now16:51
adrian_ottoactually, running low on time16:52
*** boris-42_ has joined #openstack-meeting-alt16:52
adrian_ottoI will take an action16:52
devkulkarniI can give brief update on it. asalkeld is progressing on it..16:52
adrian_otto#action adrian_otto to add Deployment workflow bp to our subsequent agenda for review updates16:52
adrian_ottodevkulkarni: yes, please16:52
*** gokrokve has joined #openstack-meeting-alt16:52
devkulkarni^^16:52
adrian_ottook, so back to M1 completion16:53
adrian_ottoany other gaps that need our focus?16:53
devkulkarniare we good on devstack setup?16:53
devkulkarnihow would someone try out solum end-to-end?16:53
adrian_ottotop priorities are getting minimal implementaitons of the CLI and Git integration working with a simple plan and have Solum create an Assembly16:53
*** hockeynut has left #openstack-meeting-alt16:54
adrian_ottopaulczar: what do you think on the devstack question?16:54
noorulwhom are we targetting M1 with?16:54
*** igormarnat_ has joined #openstack-meeting-alt16:55
*** IYozhikov_away is now known as IgorYozhikov16:55
adrian_ottonoorul: M1 should be suitable for a public demo16:55
paulczarthere are scripts in contrib for the hookup to devstack16:55
noorulM1 requires to run keystone and glance16:55
adrian_ottoto illustrate the concept of Solum16:55
paulczaras long as we keep those up to date as we build on solum we should be okay with devstack integration16:55
adrian_ottowe might also have a dependency on swift16:56
*** xwizard__ has joined #openstack-meeting-alt16:56
noorulI think it is always easy to use devstack if we have multiple services to run16:56
paulczarthe vagrantfile in the solum-dev repo on rackerlabs does the hookup when it starts devstack16:56
adrian_ottonoorul: agreed16:56
devkulkarniwe will also have dependency on heat (and may be zuul)16:56
*** SushilKM has joined #openstack-meeting-alt16:56
adrian_otto#topic Open Discussion16:57
*** openstack changes topic to "Open Discussion (Meeting topic: Solum Team Meeting)"16:57
noorulso zuul is independent of devstack16:57
*** SushilKM has quit IRC16:57
*** ativelkov has joined #openstack-meeting-alt16:57
adrian_ottowe have a few minutes remaining, so we can continue on this, or bring up any other topics16:57
noorulI have one question16:57
*** jmcbride has joined #openstack-meeting-alt16:57
*** xwizard__ is now known as tnurlygayanov___16:57
devkulkarninoorul: if someone want to try end-to-end, they would need zuul setup. I was thinking it can be made part of devstack, like other services16:57
adrian_ottonoorul: proceed16:57
noorulHow early can we start applying for incubation?16:58
*** amytron has joined #openstack-meeting-alt16:58
adrian_ottonoorul: good question.16:58
*** jmontemayor_ has joined #openstack-meeting-alt16:58
adrian_ottoI suppose that if we want to pursue incubation, it's never too early to publicly state that as an intent of ours16:58
adrian_ottoand when we all feel we are ready to apply, in terms of functionality… then we can do that16:59
adrian_ottoanyone have objections to stating an intent to file for incubation?16:59
paulczardevkulkarni: correct,  I think we would need to add scripts in contrib/devstack/lib/solum  to install/start external tools such as zuul16:59
noorulpaulczar: So that needs a bp17:00
adrian_ottonoorul: we could adjust that part of our Wiki to make that intent more clear.17:00
*** stanlagun has joined #openstack-meeting-alt17:00
nooruladrian_otto: ok17:00
adrian_ottoanyone agree?17:00
nooruladrian_otto: Should we ask M?17:00
noorulML?17:00
adrian_ottolet;s put it on next weeks agenda17:00
adrian_ottoso we can ave a good discussion about it17:00
*** Barker has quit IRC17:00
nooruladrian_otto: ok, thank you!17:01
devkulkarninoorul: good point about bp17:01
*** IlyaE has joined #openstack-meeting-alt17:01
*** jmontema_ has joined #openstack-meeting-alt17:01
adrian_otto#action adrian_otto to add incubation discussion to next agenda17:01
adrian_ottothanks everyone!17:01
adrian_otto#endmeeting17:01
*** gokrokve has quit IRC17:01
*** jmontema_ has quit IRC17:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:01
openstackMeeting ended Tue Feb 11 17:01:23 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/solum_team_meeting/2014/solum_team_meeting.2014-02-11-16.00.html17:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/solum_team_meeting/2014/solum_team_meeting.2014-02-11-16.00.txt17:01
openstackLog:            http://eavesdrop.openstack.org/meetings/solum_team_meeting/2014/solum_team_meeting.2014-02-11-16.00.log.html17:01
*** devkulkarni has left #openstack-meeting-alt17:01
*** paulczar has left #openstack-meeting-alt17:01
*** paulmo has left #openstack-meeting-alt17:01
*** jmontemayor has quit IRC17:01
*** jmontemayor_ has quit IRC17:02
*** jmontema_ has joined #openstack-meeting-alt17:02
ativelkov#startmeeting murano17:02
openstackMeeting started Tue Feb 11 17:02:12 2014 UTC and is due to finish in 60 minutes.  The chair is ativelkov. Information about MeetBot at http://wiki.debian.org/MeetBot.17:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:02
*** openstack changes topic to " (Meeting topic: murano)"17:02
openstackThe meeting name has been set to 'murano'17:02
ativelkovHi folks17:02
*** noorul has left #openstack-meeting-alt17:02
dteselkinHi17:02
*** Barker has joined #openstack-meeting-alt17:02
*** claytonc has left #openstack-meeting-alt17:02
ativelkov#link This is our agenda for today: https://wiki.openstack.org/wiki/Meetings/MuranoAgenda17:03
ativelkov#topic AI review17:04
*** openstack changes topic to "AI review (Meeting topic: murano)"17:04
*** aratim has left #openstack-meeting-alt17:04
ativelkovSo, let's start17:04
*** muralia has left #openstack-meeting-alt17:05
ativelkovativelkov and gokrokve to submit more BPs to Glance17:05
*** noslzzp has quit IRC17:05
*** rajdeep has quit IRC17:05
*** tomblank has quit IRC17:05
ativelkovWe've started doing that and submitted several BPs17:05
ativelkovmore remain to be done17:05
*** katyafervent2 has joined #openstack-meeting-alt17:06
ativelkovThe main work which is still in progress is to create a draft for the API17:06
ativelkovit is on me currently17:06
*** tomblank has joined #openstack-meeting-alt17:07
ativelkovativelkov to update project roadmap to reflect the metadata17:07
ativelkov    repository req's17:07
ativelkovNot done yet: I had too much presentation activities last week, didn't get to that17:08
ativelkov#action ativelkov to update project roadmap to reflect the metadata repository req's17:08
ativelkovSo this remains to be done17:08
ativelkovAnd the last one on me create more MVP-releated blueprints17:08
ativelkovThis one was actually done by katyafervent, thanks to her :)17:09
*** katyafervent2 has quit IRC17:09
*** bdpayne has joined #openstack-meeting-alt17:09
*** tomblank has left #openstack-meeting-alt17:09
*** katyafervent2 has joined #openstack-meeting-alt17:09
ativelkovkatyafervent to comment the blueprint on dynamic service description17:10
ativelkovAny comments here?17:10
*** jjmb has joined #openstack-meeting-alt17:10
sergmelikyanativelkov, not done yet,  katyafervent planned to work on this item tomorrow17:10
katyafervent2Yes, I have no time due to release postponed17:11
*** akuznetsov has quit IRC17:11
ativelkovok, let's have it for the next week as well17:11
ativelkov#action katyafervent to comment the blueprint on dynamic service descriptions17:11
katyafervent2Ok17:12
ativelkovnext one: stanlagun to update the DSL description according to the implemented POC17:12
sergmelikyanativelkov, AFAIK it is done: http://bit.ly/1bJ7jjh17:13
stanlagunI've written DSL description. It is on googledocs now. I'm going to publish it on wiki after initial feedback and approval17:13
*** katyafervent2 has quit IRC17:13
*** jmcbride1 has joined #openstack-meeting-alt17:13
ativelkovYes, let's publish it and get the feedback from the community.17:14
*** nacim has quit IRC17:14
*** jmcbride has quit IRC17:14
ativelkovwe'll also need some abstract and quick examples17:14
*** katyafervent2 has joined #openstack-meeting-alt17:14
*** sarob has joined #openstack-meeting-alt17:14
ativelkovlast ai: tnurlygayanov to help stanlagun with DSL Engine & YAML workflow unit tests17:15
ativelkovany prohress on testing?17:15
tnurlygayanov___no, we just read the code17:16
katyafervent2We decide to choose anybody else to help with this action item17:16
katyafervent2No?17:16
stanlagunI just starting with testing. The first thing that need to be done is make it testable. Need to throw correct exceptions, to pass exception call stack across green threads etc17:16
stanlagunAlso need to write some simple testing framework that would contain all needed mocks and class injection mechanics17:17
*** akuznetsov has joined #openstack-meeting-alt17:17
*** jcoufal has quit IRC17:17
sergmelikyanI would like to mention that improving unit-tests coverage may be much proficient during actual development, not on PoC17:18
*** katyafervent2 has quit IRC17:18
ativelkovyes, sure17:18
*** katyafervent2 has joined #openstack-meeting-alt17:18
ativelkovSo, let's agree that the testing framework is needed indeed, but actual tests should be done only hen adding this functionality to Murano itself17:18
ativelkovAny objections?17:19
*** garyk has joined #openstack-meeting-alt17:19
*** garyk has quit IRC17:19
sergmelikyantesting framework should also be developed during development phase ) What reason behind framework without tests?17:19
*** garyk has joined #openstack-meeting-alt17:19
stanlagunTests already needed so that i wouldn't brake one part of DSL while adding features to another17:20
ativelkovbecause it is the part of the engine17:20
*** katyafervent2 has quit IRC17:20
sergmelikyanI think mentioned framework will be efficiently written when will be needed by actual tests17:20
*** katyafervent2 has joined #openstack-meeting-alt17:20
ativelkovOk17:21
sergmelikyanstanlagun, I think there is no reason to invest time on PoC development. We need feedback and integration in main project17:21
*** yanndegat has quit IRC17:21
*** amytron_ has joined #openstack-meeting-alt17:22
ativelkovit turns out we are already on our next agenda topic :)17:22
ativelkov#topic New DSL status17:22
*** openstack changes topic to "New DSL status (Meeting topic: murano)"17:22
*** bdpayne_ has joined #openstack-meeting-alt17:22
*** joel_c has joined #openstack-meeting-alt17:23
ativelkovWe've already received some feedback on the new language17:23
ativelkovthe general idea is that we need to simplify it as much as possible, to reduce the adoption time for the new developers17:23
*** amytron has quit IRC17:23
*** amytron_ is now known as amytron17:23
sergmelikyanativelkov, I think we need to publish docs written by Stan as soon as possible, and discuss feature by feature features17:24
*** bdpayne has quit IRC17:24
ativelkovYes, but first we need a short abstract17:25
sergmelikyanativelkov, sure17:25
ativelkovSome draft of this abstract may be seen here: https://etherpad.openstack.org/p/v5rce77Rpt17:27
ativelkov#link https://etherpad.openstack.org/p/v5rce77Rpt17:27
ativelkovBut it has to be finalized first17:27
*** lisaclark1 has quit IRC17:28
ativelkov#action tivelkov, stanlagun to complete the short abstract for the new DSL and then publish a complete description of Wiki17:28
*** _nadya_ has quit IRC17:28
ativelkovmeawhile, it is suggested not to use the term "DSL" at all17:28
ativelkovThis thing may have features and power of a full-fledged programming language but it should not look like it- unless absolutely needed17:29
ativelkovOur users/develeopers should think of them as about the configuration files17:30
*** katyafervent2 has quit IRC17:30
*** katyafervent2 has joined #openstack-meeting-alt17:30
*** katyafervent2 has quit IRC17:30
ativelkovHerman Narkaytis has even proposed an analogue with the make-file17:31
ativelkovBut it may also look overcomplicated17:32
*** sankarshan is now known as sankarshan_away17:33
ativelkovAnything else on this topic17:33
ativelkov?17:33
*** jjmb has quit IRC17:33
ativelkovthen, let's move on17:34
ativelkov#topic Oslo.messaging status17:34
*** openstack changes topic to "Oslo.messaging status (Meeting topic: murano)"17:34
ativelkovsergmelikyan: could you please share an update here?17:34
*** RajeshMohan has quit IRC17:35
*** RajeshMohan has joined #openstack-meeting-alt17:36
sergmelikyanI had published email to the mailing list with results of my research. In short - we can migrate to oslo.messaging17:38
*** lisaclark1 has joined #openstack-meeting-alt17:39
sergmelikyanETA: around a week17:40
*** sarob has quit IRC17:40
ativelkovOK, is it doable as part of 0.5?17:40
sergmelikyanSure17:40
ativelkovgood17:40
*** sarob has joined #openstack-meeting-alt17:40
ativelkov#info migration to oslo.messaging to be done as part of 0.517:41
*** rwmjones has joined #openstack-meeting-alt17:41
*** melodous has joined #openstack-meeting-alt17:41
ativelkov#link the ML thread here: http://lists.openstack.org/pipermail/openstack-dev/2014-February/026843.html17:42
*** eankutse1 has joined #openstack-meeting-alt17:42
ativelkovok, the last item in agenda17:42
ativelkov#topic Repository Reorganization17:43
*** openstack changes topic to "Repository Reorganization (Meeting topic: murano)"17:43
ativelkovThat's what we didn't complete discussiong last time17:43
ativelkovThere was a message to ML from sergmelikyan17:44
ativelkov#link http://lists.openstack.org/pipermail/openstack-dev/2014-February/026526.html17:44
ativelkovI wanted other Muranoers to express some opinions as well17:44
*** eankutse has quit IRC17:44
ativelkovEither here or in a mailing list17:44
ativelkovWe have to make decisions on that before we start the actual coding of 0.517:45
*** _nadya_ has joined #openstack-meeting-alt17:45
*** sarob has quit IRC17:45
*** _dim has joined #openstack-meeting-alt17:45
*** gokrokve has joined #openstack-meeting-alt17:45
ativelkovNo opinions? :)17:46
sergmelikyan:)17:47
*** pballand has joined #openstack-meeting-alt17:47
*** amcrn has quit IRC17:48
*** amrith has quit IRC17:48
ativelkovoh, well. Guys, this needs to be done. Let's schedule the discussion on some other time then, when everybody are ready17:48
*** Barker has quit IRC17:48
*** mwagner_lap has joined #openstack-meeting-alt17:48
*** ijw has joined #openstack-meeting-alt17:49
*** gokrokve has quit IRC17:49
ativelkov#topic Open Discussion17:49
*** openstack changes topic to "Open Discussion (Meeting topic: murano)"17:49
*** jmontema_ has quit IRC17:49
*** gokrokve has joined #openstack-meeting-alt17:49
ativelkovAnything else to discuss?17:49
ativelkovWell, lets wrap up then17:50
ativelkovThanks for joining17:51
ativelkov#endmeeting17:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:51
openstackMeeting ended Tue Feb 11 17:51:07 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/murano/2014/murano.2014-02-11-17.02.html17:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/murano/2014/murano.2014-02-11-17.02.txt17:51
openstackLog:            http://eavesdrop.openstack.org/meetings/murano/2014/murano.2014-02-11-17.02.log.html17:51
*** devlaps has joined #openstack-meeting-alt17:51
*** noslzzp has joined #openstack-meeting-alt17:52
*** gokrokve has quit IRC17:54
*** gokrokve has joined #openstack-meeting-alt17:54
*** thinrichs has joined #openstack-meeting-alt17:57
*** rajdeep has joined #openstack-meeting-alt17:58
pballandhello18:00
thinrichsHi all18:01
*** gokrokve has quit IRC18:01
rajdeephi18:01
*** gokrokve has joined #openstack-meeting-alt18:01
pballand#startmeeting CongressTeamMeeting18:01
openstackMeeting started Tue Feb 11 18:01:41 2014 UTC and is due to finish in 60 minutes.  The chair is pballand. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: CongressTeamMeeting)"18:01
openstackThe meeting name has been set to 'congressteammeeting'18:01
pballandSo I didn't update the agenda, but there are a couple things18:02
pballand1) change meeting time18:02
pballand2) discuss design doc18:02
pballand3) open discussion18:02
pballand#topic meeting time18:02
*** openstack changes topic to "meeting time (Meeting topic: CongressTeamMeeting)"18:02
pballandwe have heard from a few people that the meeting time doesn't work for them18:03
rajdeepyeah too late for my time zone in india18:03
pballandI think a PST time would be better for thinrichs and I18:03
pballandwould 1 or 2 hours earlier help rajdeep?18:04
rajdeep1 hour early would be better18:04
rajdeepi attend solum meeting 2 hours earlier than this meeting18:04
pballandif we can fine a room available, that would work18:04
pballandthere is #openstack-meeting-3 now18:05
*** gokrokve has quit IRC18:06
pballandso 1700 UTC on ever other Tues?18:06
pballandanyone?18:07
rajdeepyes that will be better18:07
thinrichsWorks for me18:07
pballand#agreed meeting will be changed to #openstack-meeting-3 at 1700UTC18:07
*** mshindo_ has joined #openstack-meeting-alt18:07
*** aignatov_ is now known as aignatov18:07
pballandI will make the changes on the wiki18:07
pballand#topic Congress design doc18:07
*** openstack changes topic to "Congress design doc (Meeting topic: CongressTeamMeeting)"18:08
pballandthinrichs has been working on the design doc18:08
pballanddo you mind talking a bit about what you have and what should be done next?18:08
thinrichs#link https://docs.google.com/a/vmware.com/document/d/1f2xokl9Tc47aV67KEua0PBRz4jsdSDLXth7dYe-jz6Q/edit#18:08
thinrichsWe've got the basic structure and there's plenty of text describing the basic design.18:09
*** balajiiyer has joined #openstack-meeting-alt18:09
thinrichsThere are a number of holes highlighted in yellow that need to be filled in.18:09
thinrichsSome of the holes are conceptual details and some are API details.18:10
*** rossella_s has quit IRC18:10
thinrichsProbably the most useful thing at this point is for everyone to scan it and make high-level comments.18:11
*** rsblendido has quit IRC18:11
thinrichsAre we missing important design issues?  Do we agree with the things that are there?  Are there things we're missing?18:11
*** joel_c has left #openstack-meeting-alt18:11
rajdeepis the doc editable?18:11
pballandNot publicly18:12
pballand(as of now)18:12
*** safchain has quit IRC18:12
pballandI can add you (or anyone else who wants to contribute)18:12
rajdeepsure, i was planning to start documenting existing implementation18:13
rajdeephow are API server and the lexer parser linked in the current design18:13
*** BrianB_ has quit IRC18:13
pballandthey aren't :-)18:13
rajdeepok :)18:13
rajdeepi was not able to figure out..i am assuming they have to be linked18:14
pballandactually, there are 2 different entry points18:14
pballandone just runs the parser, the other launches the API in an eventlet loop, with some policy engine integration18:14
pballandbut I have some uncommitted code on this that I have to clean up and get in18:14
rajdeepok..18:14
rajdeepso people create their policies offline18:15
rajdeepand hook into policy engine18:15
thinrichsThere are a bunch of things we're planning to do over the next month to get the prototype ready for others to use/understand.18:15
pballandcurrently, yes, but the plan is that they can set/update policies via the API18:15
thinrichsHere's the list.  Let's add to it/modify it.18:15
rajdeepexactly18:15
thinrichs- Hook up Congress to Nova/Neutron data sources (ideally in a way that makes it easy to hook up other data sources so that if customers have a use case with another data source then we/they can add it in short order)18:16
rajdeepone entry point for everything18:16
thinrichs- Hook up Congress to Nova/Neutron actions (so that we can actually correct violations after they occur)18:16
thinrichs- Do some scaling tests/minor performance improvements.  Don't want to hand them something that only works with 10 hosts.18:16
thinrichs- Add some error handling.18:16
thinrichs- Some basic user docs18:16
*** amcrn has joined #openstack-meeting-alt18:16
rajdeepare you planning to use nova / neutron python clients18:16
rajdeepor REST directly18:17
pballandI was thinking REST so they are more loosely coupled18:17
pballandbut performance could be an issue...18:17
rajdeepok...18:17
rajdeepany plans to integrate congress into devstack18:18
rajdeep?18:18
pballandthat's probably the best way for integration testing18:18
pballandbut it isn't on my short-list18:18
*** gokrokve has joined #openstack-meeting-alt18:18
pballandit would be great if someone can tackle this18:19
pballand#topic open discussion18:20
*** openstack changes topic to "open discussion (Meeting topic: CongressTeamMeeting)"18:20
*** rajdeep_ has joined #openstack-meeting-alt18:20
*** stanlagun has left #openstack-meeting-alt18:20
rajdeep_let us get the nova/neutron integration first18:21
rajdeep_devstack comes into picture after that18:21
pballandthat sounds reasonable to me18:21
pballandI'll try to get some of my old commits cleaned up and pushed18:21
rajdeep_where will congress pickup uses/ groups from18:21
pballandand documenting a simple workflow with API is high priority18:21
rajdeep_users*18:21
pballandI did a simple hack for Active Directory18:22
*** rajdeep has quit IRC18:22
rajdeep_ok,18:22
pballandbut we should also support keystone18:22
rajdeep_for devstack keystone would be default18:23
pballandyup18:23
thinrichsThe goal, though, is for these to be examples of where users could be imported.18:23
rajdeep_and why are we using ovs in the current implementation18:23
rajdeep_saw some imports18:23
*** dane_ has joined #openstack-meeting-alt18:23
*** gokrokve has quit IRC18:23
*** jjmb has joined #openstack-meeting-alt18:23
pballandbecause that was an easy way for demonizing Python :)18:23
pballandI should use oslo18:24
pballandbut was in a hurry and used what I knew18:24
rajdeep_yeah..i got confused18:24
rajdeep_looking at ovw18:24
rajdeep_ovs18:24
pballandyeah, it's just the ova-python utility routines18:25
*** rajdeep_ is now known as rajdeep18:25
rajdeepah ok..18:26
pballandanything else to discuss today?18:26
thinrichsHow about next steps for each of us?18:26
rajdeepi will go through the doc and ask questions if required18:26
thinrichsFrom the list above, I was planning on ...18:26
rajdeepwhat is the best way of communication : mailing list18:27
thinrichs- Add some error handling and do overall cleanup of the policy engine18:27
pballandyes, openstack-dev is probably the best place18:27
*** esker has quit IRC18:27
rajdeepi will explore keystone integration18:27
*** aignatov is now known as aignatov_18:28
pballandok, great18:28
*** esker has joined #openstack-meeting-alt18:28
*** yogesh has joined #openstack-meeting-alt18:28
*** resker has joined #openstack-meeting-alt18:28
pballandso Feb 25, at 1700UTC is the next meeting18:29
pballanduntil then, questions on the mailing list18:29
rajdeepok,18:29
pballandthanks everyone18:30
pballand#endmeeting18:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:30
openstackMeeting ended Tue Feb 11 18:30:21 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-02-11-18.01.html18:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-02-11-18.01.txt18:30
openstackLog:            http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-02-11-18.01.log.html18:30
*** rajdeep has quit IRC18:30
*** thinrichs has quit IRC18:30
*** gokrokve has joined #openstack-meeting-alt18:31
*** mshindo_ has left #openstack-meeting-alt18:31
*** arnaud has joined #openstack-meeting-alt18:31
*** arnaud__ has joined #openstack-meeting-alt18:31
*** pballand has quit IRC18:31
*** michael-yu has joined #openstack-meeting-alt18:31
*** jjmb has quit IRC18:32
*** jjmb has joined #openstack-meeting-alt18:33
*** esker has quit IRC18:33
*** resker has quit IRC18:33
*** pballand has joined #openstack-meeting-alt18:34
*** amytron has quit IRC18:34
*** chandan_kumar has quit IRC18:34
*** dane_ has quit IRC18:35
*** balajiiyer has quit IRC18:35
*** malini has left #openstack-meeting-alt18:36
*** balajiiyer has joined #openstack-meeting-alt18:36
*** balajiiyer has left #openstack-meeting-alt18:38
*** _dim has quit IRC18:40
*** dane_ has joined #openstack-meeting-alt18:40
*** _dim has joined #openstack-meeting-alt18:45
*** Ranjitha has joined #openstack-meeting-alt18:45
*** ccrouch has joined #openstack-meeting-alt18:46
*** amrith has joined #openstack-meeting-alt18:49
*** demorris_ has joined #openstack-meeting-alt18:52
*** amrith has quit IRC18:52
*** pino|work has joined #openstack-meeting-alt18:52
*** greghaynes has joined #openstack-meeting-alt18:54
*** demorris has quit IRC18:54
*** demorris_ is now known as demorris18:54
*** matty_dubs has joined #openstack-meeting-alt18:57
*** jcoufal has joined #openstack-meeting-alt18:59
*** pblaho has joined #openstack-meeting-alt18:59
*** gokrokve has quit IRC18:59
*** rpodolyaka1 has joined #openstack-meeting-alt18:59
*** Ranjitha has quit IRC18:59
*** gokrokve has joined #openstack-meeting-alt19:00
*** jistr has joined #openstack-meeting-alt19:01
matty_dubsTripleO meeting time?19:01
jcoufalprobably...19:01
jistro/19:01
jcoufal\o19:01
shadowerhola19:01
*** jog0 has joined #openstack-meeting-alt19:01
jomarahi19:01
rpodolyaka1o/19:02
dkehnhi19:02
matty_dubs\o\19:02
bnemec/o/19:02
SpamapSaye...19:02
slaglehi19:02
dprincehowdy19:02
* pino|work greets19:02
greghaynesO/19:03
lsmolahello19:03
pblaho\o19:03
pleia2o/19:04
*** SushilKM has joined #openstack-meeting-alt19:04
*** cadenzajon has joined #openstack-meeting-alt19:05
lsmolaSpamapS: so, still doesn't work with new devtest https://bugs.launchpad.net/tripleo/+bug/127901119:05
*** SushilKM has left #openstack-meeting-alt19:05
SpamapS#startmeeting tripleo19:05
openstackMeeting started Tue Feb 11 19:05:58 2014 UTC and is due to finish in 60 minutes.  The chair is SpamapS. Information about MeetBot at http://wiki.debian.org/MeetBot.19:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:06
*** openstack changes topic to " (Meeting topic: tripleo)"19:06
openstackThe meeting name has been set to 'tripleo'19:06
SpamapSAhoy there!19:06
lsmolaSpamapS: but works with slagle 's undercloud-live as rlandy tried19:06
lsmola_o/19:06
SpamapSlsmola: wait one moment while we get to the bugs topic :)19:06
SpamapS#topic bugs19:06
*** openstack changes topic to "bugs (Meeting topic: tripleo)"19:06
lsmolaSpamapS: I am a skipper :-)19:06
lsmolahehe that was fast :-D19:07
SpamapSoh I forgot19:07
SpamapS#link https://wiki.openstack.org/wiki/Meetings/TripleO19:07
SpamapS#link https://bugs.launchpad.net/tripleo/19:07
SpamapS#link https://bugs.launchpad.net/diskimage-builder/19:07
SpamapS#link https://bugs.launchpad.net/os-refresh-config19:07
SpamapS#link https://bugs.launchpad.net/os-apply-config19:07
SpamapS#link https://bugs.launchpad.net/os-collect-config19:07
SpamapS#link https://bugs.launchpad.net/tuskar19:07
SpamapS#link https://bugs.launchpad.net/tuskar-ui19:07
SpamapS#link https://bugs.launchpad.net/python-tuskarclient19:07
slaglehttps://bugs.launchpad.net/tripleo/+bug/1279011 needs triage19:08
slaglelsmola: i assume the heat syack-update in the description is just a typo in the bug?19:08
SpamapSslagle: it is assigned a High importance, it just isn't known to be reproducible.. :)19:09
lsmolaslagle: yes sorry19:09
slagleSpamapS: it should still be set to Triaged though? or no?19:09
SpamapSslagle: Well I see New as a signal to developers to try and clarify the bug... Triaged would just put it on the stack of things to fix.19:10
lsmolaslagle: set19:10
lsmolaSpamapS: unset? :-)19:10
*** dguitarbite has joined #openstack-meeting-alt19:10
*** dguitarbite has left #openstack-meeting-alt19:10
SpamapSlsmola: if you think devs can work it then Triaged is appropriate. If you'd like to see if more users experience the problem, New.19:11
SpamapSI'm fine either way.19:11
SpamapSTriaged is really such a weird status name.19:11
*** sarob has joined #openstack-meeting-alt19:11
lsmolaSpamapS: ok, I vote for more users19:11
SpamapS:) ok19:11
lsmolaso anybody else experienced it?19:11
SpamapSso https://bugs.launchpad.net/tripleo/+bug/1271344 has been hitting us on the cd-undercloud lately19:11
*** baoli has quit IRC19:12
SpamapSbut I think we _also_ have some machines in our rack that don't work well19:12
SpamapSI've been working on isolating those so we can open tickets and get them fixed19:12
SpamapSAlso I totally forgot releases last week so the fix committed bugs can all go to fix released soon19:13
jistrall check-tripleo-undercloud-precise Jenkins jobs fail on this: https://bugs.launchpad.net/tripleo/+bug/127886119:13
jistrthere is workaround available if running locally, so i set it to high19:13
SpamapSI think this bug needs some interaction https://bugs.launchpad.net/tuskar/+bug/1278976 ... the poster gives no justification for why /etc is a bad place for t-h-t19:14
jistrbut i wonder if it should be critical because it breaks Jenkins19:14
*** eanxgeek is now known as eanxgeek|log19:14
SpamapSjistr: I think so.. the bar for me is the amount of affect it has on users.. and jenkins not working is indeed a large effect!19:14
*** jprovazn has joined #openstack-meeting-alt19:15
SpamapSAny other bugs?19:15
jistrSpamapS: ok, done19:15
*** Ranjitha has joined #openstack-meeting-alt19:16
SpamapS#topic reviews19:16
*** openstack changes topic to "reviews (Meeting topic: tripleo)"19:16
SpamapS#link http://russellbryant.net/openstack-stats/tripleo-openreviews.html19:16
*** coolsvap has quit IRC19:17
SpamapSseems we've been leaving things sitting a bit more this past week19:17
SpamapSConsider this a reminder that we need to keep up with the in-flow.19:17
SpamapSI don't think we have a team shortage.. it seems like we've done less reviews is all.19:17
*** tzumainn has joined #openstack-meeting-alt19:18
*** esker has joined #openstack-meeting-alt19:19
SpamapS#topic Projects needing releases19:19
*** openstack changes topic to "Projects needing releases (Meeting topic: tripleo)"19:19
SpamapSshadower: I think you wanted to do the release process?19:19
*** morazi has joined #openstack-meeting-alt19:19
shadowerSpamapS: yup19:19
SpamapSrpodolyaka1: perhaps you can assist shadower ?19:19
rpodolyaka1SpamapS: shadower: sure19:19
SpamapSrpodolyaka1: (and welcome back from vacation :)19:19
shadowerany docs you can point me at?19:19
rpodolyaka1SpamapS:  thanks :)19:19
ccrouchtripleo-heat-templates, tripleo-image-elements and diskimage-builder have a bunch of changes and don't look like they have had a release in ~3wks19:20
rpodolyaka1shadower: just ping me, if you need any help with releases19:20
shadowerrpodolyaka1: will do, thanks19:20
*** jrist has quit IRC19:20
rpodolyaka1shadower: np19:20
SpamapSThe process is basically "make a signed tag. Push that tag to gerrit. Close bugs"19:21
SpamapSNot sure if we have an automated thing for "Close bugs"19:21
rpodolyaka1yeah, we have a script19:21
SpamapSrpodolyaka1: sweet19:21
SpamapS#topic CD Cloud status19:21
*** openstack changes topic to "CD Cloud status (Meeting topic: tripleo)"19:21
shadowersweet19:22
SpamapStripleo-cd is failing always now because of a combination of hardware issues and the neutron bug I cited earlier19:22
SpamapSI believe I'm close to isolating _12_ "bad" machines.19:22
SpamapSbut it could be some of them are just victims of the neutron bug so I am going to be disabling them all and then enabling each one to see if it can deploy.19:23
tchaypoWhat does bad mean in this case?19:23
SpamapStchaypo: won't pxe boot or fail somewhere between pxe boot and running.19:23
SpamapSremotely debugging them via ilo can be tedious because of the 8 minute POST windows where the console shows nothing. :-P19:24
tchaypoSo possibly a variety of causes, but all we care about is that they aren't useable right now19:24
SpamapStchaypo: right, we want to just make sure we stop trying to deploy to the bad ones.19:24
lsmolahave to leave early today, see you guys tomorrow19:25
SpamapSand that we get our NOC to fix them19:25
tchaypoAt least you can enjoy a coffee while waiting for the ILO. Tends to be frowned on if you're physically in front of the machine19:25
*** IlyaE has quit IRC19:25
SpamapShah true19:26
SpamapSok so that is where it is at. Hopefully will recover and regain our 50% uptime rating this week. :-P19:27
SpamapS#topic CI virtualized testing status19:27
*** openstack changes topic to "CI virtualized testing status (Meeting topic: tripleo)"19:27
SpamapSIt seems like they're deep in discussion about tripleo things in the infra meeting..19:27
SpamapSso lets skip and come back19:27
SpamapS#topic open discussion19:28
*** openstack changes topic to "open discussion (Meeting topic: tripleo)"19:28
* pino|work has a topic19:28
* matty_dubs as well19:28
SpamapSlifeless: when you're done in infra meeting.. ping back here for the CI virtualized testing stuff19:28
SpamapSpleia2: you too19:28
SpamapSdprince: you three19:28
SpamapSpino|work: fire away19:28
pino|workit is something that has been proposed few times in the past19:28
SpamapSPuppies for everyone?19:29
SpamapSI told you, the shipping costs...19:29
SpamapSoh ;)19:29
pino|workie basically making use of the guestfs tools (virt-builder, virt-sysprep, guestfish, etc) to handle the generation and edit of images19:29
*** igor___ has quit IRC19:29
SpamapSpino|work: I think we'd all be open to other tools. We have a _lot_ invested in tripleo elements. But diskimage-builder's guts are pretty light weight.19:30
pino|work... instead of disk-image-builder (which, at least to my looks earlier today, seemed a bit... fragile and possibly insecure)19:30
lifelessSpamapS: aiieee19:30
*** tanisdl has joined #openstack-meeting-alt19:30
*** jmontemayor has joined #openstack-meeting-alt19:30
pino|worksince rwmjones and me are starting to head toward a new 1.26 release in a month or two, it would be a great time for asking feedback from you guys and have this reflected in our tools19:31
SpamapSpino|work: spin up a VM.. run dib in it.. tear down VM. Not sure where the insecurity is.19:31
pino|workthat's what our tools do as well19:32
jistrpino|work: is it clear how to make the guestfs tools use tripleo-image-elements? or is it something that needs to be worked out?19:32
SpamapSpino|work: I would be willing to bet that you could change dib to work via other tools than the current chroot based solution.19:32
pino|workSpamapS: i remember about the chroot, it was not totally clear it was spawned within a vm19:32
*** MarkAtwood has joined #openstack-meeting-alt19:32
lifelessSpamapS: so am here19:33
lifelessquestion was?19:33
jprovaznI agreee that DIB elements should might work with virt-builder19:33
SpamapSpino|work: it is not, but it could be with relative ease19:33
SpamapSlifeless: CI virtualized testing progress19:33
jprovaznand AFAIK virt-builder supports building of windows images19:33
SpamapSlifeless: but let's address pino's issue first19:33
SpamapSOk this is TripleO...19:33
*** sarob has quit IRC19:33
SpamapSwe're not running pieces of OpenStack on Windows. :)19:33
lifelesspino|work: whats insecure about dib? Note that if you say 'the image you unpack might be hostile' - note that if the image is hostile, the code in it certainly is, and that code is going to be your /cloud/.19:33
rwmjonesguestfs does the "spinning up in a VM" already (and uses things like sVirt and containers too)19:34
pino|worklifeless: handling tools like kpartx, losetup, etc as root19:34
jprovaznso it would be great to consider virt-builder before guys working on DIB for windows go too far19:34
slaglefyi, i wrote a thing a while back to apply elements not using a chroot. virt-builder could use that with relative ease i suspect, since it can run arbitrary scripts19:34
SpamapSjprovazn: definitely19:34
lifelesspino|work: right, this debate is all based around the argument that you're unpacking random images that might be hostile.19:34
SpamapSslagle: indeed!19:34
*** Barker has joined #openstack-meeting-alt19:35
SpamapSslagle: the dib element interface is well documented and _relatively_ stable.19:35
lifelesspino|work: Which is a scenario Nova has, but we don't.19:35
pino|workjprovazn: exactly, i was told about the windows support, which at least we should have at some degree (of course, we're open to improvements)19:35
SpamapSso if there is a concern over dib, I'd like to see a clear write up of the concerns as a blueprint, and an open discussion on the ML where the concerns can be articulated.19:35
SpamapSblueprint or bugs or both actually :)19:35
lifelesswell19:35
lifelesslets start with a bug19:35
lifelessblueprints are timeline coordination tools19:36
pino|workregarding the elements: i looked at the current elements, and most of the features done with them are currently doable with virt-builder/virt-sysprep/guestfish19:36
lifelessa bug/etherpad/mailing list discussion.19:36
jistrpino|work: is it possible to build images with guestfs tools without having sudo rights?19:36
lifelesspino|work: so, I'm still unclear: whats the problem statement.19:37
lifelesspino|work: and what are the benefits/tradeoffs. Technical ability to do the thing comes second IMO.19:37
pino|workjistr: noting that we don't do installations from scratch/kickstart/d-i/etc, the rest is done with no need for sudo/root19:37
rwmjonesjistr: yes, no sudo or root needed at all for anything libguestfs related19:38
pino|worklifeless: benefits: image manipulation doable without root rights at all, in an isolated vm19:38
rwmjonesjistr: except if you have an image which is owned by root and -rw------ but I guess that goes without saying ..19:38
*** _dim has quit IRC19:39
jistrrwmjones, pino|work: sounds good19:39
SpamapSpino|work: we can do that, just by running dib.. in an isolated vm.. :p19:39
lifelesspino|work: as SpamapS says, we have that.19:39
lifelesspino|work: sdake put a heat template together for it.19:39
pino|worklifeless: userbase very-well tested, also in production, and with easier user handling than shell scripts19:39
SpamapSpino|work: if you could automate just doing that.. that might be attractive. :)19:39
lifelesspino|work: what do you mean by 'easier user handling than shell scripts'?19:39
slagledib could still destroy the vm it's in due to it's chroot bind mounting19:41
pino|worklifeless: easier way to do operations than using chunks of shell code19:41
SpamapSslagle: I doubt we'd shed a tear for said VM. ;)19:41
*** ruhe_ has joined #openstack-meeting-alt19:41
slagleSpamapS: sure, it's just a very unfriendly thing19:41
slagleand hard(ish) to debug19:42
lifelesspino|work: uhm19:42
lifelesspino|work: I still don't understand 'easier than shell code'19:42
pino|worklifeless: for example, virt-builder can handle users creation/passwords, package installation, file editing and more during the image building phase19:42
SpamapSslagle: we destroyed /dev on everybody's laptop and, while mildly inconvenient, we didn't stop using it or start using it in vms the next day ;)19:42
lifelesspino|work: since the whole point of dib is to run shell code.19:42
SpamapSpino|work: that is complecting19:42
slagleSpamapS: indeed, but i'm not thinking about "us"19:43
pino|work"complecting"?19:43
SpamapSpino|work: dib runs elements. It is simple and does one thing well. I don't want dib to know how to make users.19:43
matty_dubsIn any case, is this the place to sort it out? Or should this be taken to a bug/mailing list discussion?19:43
ccrouchhttp://www.thefreedictionary.com/complecting19:43
rwmjonesI think "complicating"19:43
slagleSpamapS: more so a cloud admin/operator19:43
matty_dubsI feel like this conversation could go on for several hours19:43
bnemecmatty_dubs: +119:44
rwmjonescrumbs, that is a real word :-)19:44
jprovaznSpamapS, I remember that vaporized /dev on my laptop was beautiful welcome message when I was starting :)19:44
SpamapSRight I'm suggesting that this is something that needs an articulated document and some thought that a 59 minute meeting will not allow.19:44
lifelessagreed19:44
lifelessso look, in principle I'm not against dib dying a beautiful death as patches to something else.19:44
lifelessBut19:44
SpamapSjprovazn: welcome to Seattle, you didn't need /dev anyway19:44
pino|worksure, i was generally trying to restart a discussion about it19:44
jprovaznhehe19:45
lifelessWe've a -very- tight timeline for delivery of key things for multiple vendors19:45
lifelessand dib is finished.19:45
lifelessIt works, it meets all our current use cases.19:45
lifelessSo I have approximately 0 interest in fixing it for fixing sake at the moment.19:45
pino|worki was told you need windows support... which means kind of rewriting it19:45
SpamapSwe do not19:45
rwmjoneswell we're going to work on some stuff to make virt-builder do everything that dib can do, so suggestions are welcome19:45
lifelesspino|work: There's a vendor that wants a window image building thing analagous to dib.19:46
SpamapSOpenStack on OpenStack has no need to deploy workloads on Windows AFAIK.19:46
lifelesspino|work: We'll point them at virt-builder and see if it meets their use case.19:46
jprovaznpino|work, not rewriting but creating another "dib windows" project19:46
*** dguitarbite_ has joined #openstack-meeting-alt19:46
SpamapSwe may _deploy_ windows images.. but that is way different than needing windows for TripleO.19:46
lifelesspino|work: if it doesn't, they might offer patches, or do something new.19:46
lifelesspino|work: dunno yet. How mature is virt-builders windows support ?19:46
lifelessrwmjones: ok, cool!19:47
rwmjonesit can create a windows image, but not install software or firstboot scripts yet19:47
*** doug_shelley66 has quit IRC19:47
rwmjonesresize supports works at the moment19:47
lifelessrwmjones: ok, so the interesting bit is installing stuff :)19:47
rwmjonescertainly, but we'll get that soon19:47
*** doug_shelley66 has joined #openstack-meeting-alt19:47
lifelessrwmjones: on making virt-builder do what dib can do: - key features for me:19:47
lifeless - run simple shell scripts19:47
rwmjones(done!)19:47
lifeless - access resources outside the image being built19:48
pino|worklifeless: i was not trying to said "kill dib now", just that we could use your feedback in making our tools have the functionalities you need right now with dib (as to eveventually switch to them in some future)19:48
rwmjonesdone!19:48
dprincerwmjones: the only hangup for me is installing RPMs (without using a firstboot script)19:48
rwmjones(you can attach disks, or grab stuff off the network)19:48
lifeless - let users interactively poke around within the thing, to debug things that failed.19:48
rwmjonesyou can install RPMs19:48
lifelessrwmjones: ah, so neither of attach disks or grabb off network are what I mean19:48
rwmjoneslifeless: that's a good point, our debug support isn't great19:48
lifelessrwmjones: I mean 'I have a local file <here>' and I want it <there> in the image.19:49
*** saju_m has quit IRC19:49
rwmjoneslifeless: oh right, yes you can do that now, using --upload option19:49
*** igormarnat_ has quit IRC19:49
lifelessrwmjones: so that e.g. RPM can share its cache with the host os.19:49
pino|work(or the upload command in guestfish, for example)19:49
rwmjonesbut only files, we could/should let you upload more substantial stuff19:49
lifelessrwmjones: which --upload doesn't deliver.19:49
rwmjoneslike directories19:49
lifelessrwmjones: and uploading the whole cache to pull out what files are needed sounds expensive.19:49
*** dguitarbite has joined #openstack-meeting-alt19:49
rwmjoneswell we could do it with 9pfs, which libguestfs supports but virt-builder doesn't use right now19:50
lifelessrwmjones: ah, ok.19:50
rwmjonesok, all good ideas anyway, thanks19:50
lifelessrwmjones: so anyhow - teh debug support we have is also limited today but it is super useful19:50
lifelessrwmjones: the bind mounting stuff is super useful19:50
SpamapSthe use case is that we will run dib on a machine that already has git trees checked out and ready to use..19:50
*** ruhe_ has quit IRC19:50
lifelessrwmjones: dib itself has a few minor os specific abstractions, I'm sure virt-builder has them too19:51
SpamapSamong other things19:51
rwmjonesok I'm off now, but thanks -- will read the IRC log when it is posted19:51
pino|workwe have guestmount to mount images on your host using fuse19:51
slaglelike well populated yum caches :)19:51
lifelesspino|work: we don't do that19:51
lifelesspino|work: we start with tarballs - when we download a qcow2 or something, the first thing we do is unpack it into a tarball19:51
*** saju_m has joined #openstack-meeting-alt19:51
*** Ranjitha has quit IRC19:51
matty_dubsMay I humbly submit that this feels quite off-topic and has taken about a good chunk of the meeting?19:51
SpamapSagreed19:51
lifelessagreed19:51
rwmjonesagreed19:51
SpamapSand matty_dubs has another topic19:51
matty_dubsOh, right! Mine is probably far less-interesting, though.19:52
SpamapSYOU want puppies too? ;)19:52
matty_dubsWas just curious about the meetup. Is there a venue set?19:52
matty_dubsHotel recommendation?19:52
*** pballand has quit IRC19:52
matty_dubsAnd, will there be puppies handed out at the meeting?19:52
* jcoufal shares the same question19:52
tchaypoWhat's all this about puppies? I was promised ponies!19:52
*** IlyaE has joined #openstack-meeting-alt19:52
shadowermatty_dubs: what a bore!19:52
SpamapSmatty_dubs: City: yes, Venue: may shift.19:53
SpamapSHotel is something we should have "shortly" with a group rate.19:53
matty_dubsOh, and are we meeting Friday, or is it a travel day? I had conflicting information. (Either's A-OK with me.)19:53
SpamapSI believe the venue will be open and some will stay through Friday19:53
SpamapSI am leaving Friday morning.19:53
*** gokrokve has quit IRC19:53
*** gokrokve has joined #openstack-meeting-alt19:54
matty_dubsAh, okay, so either will work then19:54
matty_dubsSo we should book flights to be there Monday-Friday, but not everyone will be there Friday, and we shouldn't book a hotel until we hear about a group rate.19:55
matty_dubs^ apt summary?19:55
*** gokrokve_ has joined #openstack-meeting-alt19:55
*** ruhe- has joined #openstack-meeting-alt19:55
SpamapSmatty_dubs: I believe so yes19:56
matty_dubsAwesome, thanks.19:56
SpamapSNot sure why the hotel is taking so long.19:56
SpamapSThought we'd have that by now.19:56
SpamapSwith that I believe we will come to a close.19:56
SpamapSwatch the ML for more details about the meetup.19:56
*** ruhe- has quit IRC19:56
SpamapSthanks everyone!19:57
jomarathanks SpamapS19:57
SpamapS#endmeeting19:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:57
openstackMeeting ended Tue Feb 11 19:57:15 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:57
pino|workthanks, and sorry for taking too much time :)19:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tripleo/2014/tripleo.2014-02-11-19.05.html19:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tripleo/2014/tripleo.2014-02-11-19.05.txt19:57
openstackLog:            http://eavesdrop.openstack.org/meetings/tripleo/2014/tripleo.2014-02-11-19.05.log.html19:57
*** eankutse1 has quit IRC19:57
SpamapSpino|work: It is most appreciated, nothing ot be sorry for :)19:57
*** ruhe has quit IRC19:57
matty_dubsHehe, yeah, it's an interesting conversation to have.19:57
*** jprovazn is now known as jprovazn_afk19:57
rpodolyaka1night all!19:58
jistrthanks all, bye :)19:58
matty_dubsDidn't mean to shut it down, as much as suggest that it move to the list, since it didn't look like it was going to be resolved here.19:58
*** gyee has quit IRC19:58
matty_dubsAdios!19:58
*** rpodolyaka1 has left #openstack-meeting-alt19:58
*** greghaynes has left #openstack-meeting-alt19:58
pino|workjistr: o/ :)19:58
*** Duane_ has joined #openstack-meeting-alt19:58
*** eankutse has joined #openstack-meeting-alt19:58
*** gokrokve has quit IRC19:58
*** ruhe has joined #openstack-meeting-alt19:58
lifelessmatty_dubs: its a meeting day19:59
*** lisaclark1 has quit IRC19:59
lifelessmatty_dubs: but some folk are leaving early for family/etc19:59
*** lisaclark1 has joined #openstack-meeting-alt19:59
*** pblaho has quit IRC19:59
*** lisaclark1 has quit IRC19:59
*** gokrokve_ has quit IRC19:59
matty_dubsAh, okay, so I'll plan on being there for Friday.19:59
matty_dubstzumainn: ^20:00
jcoufalthanks guys20:00
*** gokrokve has joined #openstack-meeting-alt20:00
*** tanisdl has quit IRC20:00
*** gokrokve_ has joined #openstack-meeting-alt20:01
*** matty_dubs has left #openstack-meeting-alt20:01
*** jistr has quit IRC20:02
*** Ranjitha has joined #openstack-meeting-alt20:02
*** Barker has quit IRC20:03
*** saju_m has quit IRC20:04
*** gokrokve has quit IRC20:04
*** tchaypo has left #openstack-meeting-alt20:05
*** saju_m has joined #openstack-meeting-alt20:05
*** _nadya_ has quit IRC20:05
*** jmcbride1 has left #openstack-meeting-alt20:06
*** lisaclark1 has joined #openstack-meeting-alt20:07
*** _nadya_ has joined #openstack-meeting-alt20:09
*** ijw has quit IRC20:09
*** ijw has joined #openstack-meeting-alt20:10
*** eankutse has quit IRC20:12
*** eankutse has joined #openstack-meeting-alt20:13
*** eankutse1 has joined #openstack-meeting-alt20:13
*** eankutse has quit IRC20:13
*** ijw has quit IRC20:14
*** dguitarbite_ has left #openstack-meeting-alt20:15
*** gokrokve_ has quit IRC20:16
*** cadenzajon has quit IRC20:16
*** gokrokve has joined #openstack-meeting-alt20:16
*** cadenzajon has joined #openstack-meeting-alt20:17
*** pino|work has quit IRC20:18
*** jcoufal has quit IRC20:19
*** yogesh has quit IRC20:20
*** gokrokve has quit IRC20:21
*** _nadya_ has quit IRC20:21
*** yogesh has joined #openstack-meeting-alt20:23
*** harlowja_away is now known as harlowja20:24
*** jcoufal has joined #openstack-meeting-alt20:25
*** denis_makogon_ has joined #openstack-meeting-alt20:26
*** dguitarbite has quit IRC20:27
*** tnurlygayanov___ has quit IRC20:30
*** jcoufal has quit IRC20:31
*** saju_m has quit IRC20:32
*** jjmb has quit IRC20:33
*** Barker has joined #openstack-meeting-alt20:34
*** sarob has joined #openstack-meeting-alt20:35
*** Ranjitha has quit IRC20:37
*** RajeshMohan has quit IRC20:40
*** sarob has quit IRC20:40
*** RajeshMohan has joined #openstack-meeting-alt20:41
*** balajiiyer has joined #openstack-meeting-alt20:44
*** denis_makogon has quit IRC20:45
*** denis_makogon_ is now known as denis_makogon20:45
*** dmakogon_ has joined #openstack-meeting-alt20:46
*** DinaBelova is now known as DinaBelova_20:47
*** igormarnat_ has joined #openstack-meeting-alt20:47
*** zzelle has joined #openstack-meeting-alt20:51
*** _nadya_ has joined #openstack-meeting-alt20:52
*** dane_ has quit IRC20:52
*** jprovazn_afk has quit IRC20:55
*** aignatov_ is now known as aignatov20:55
*** Barker has quit IRC20:59
*** lisaclark1 has quit IRC21:00
*** dane_ has joined #openstack-meeting-alt21:00
*** amcrn has quit IRC21:00
*** Barker has joined #openstack-meeting-alt21:00
*** _nadya_ has quit IRC21:00
*** amcrn has joined #openstack-meeting-alt21:01
*** jdob_ has joined #openstack-meeting-alt21:01
*** ccrouch has quit IRC21:02
*** eankutse1 has quit IRC21:03
*** eankutse has joined #openstack-meeting-alt21:03
*** lisaclark1 has joined #openstack-meeting-alt21:04
*** pballand has joined #openstack-meeting-alt21:08
*** sarob has joined #openstack-meeting-alt21:10
*** jdob_ has quit IRC21:15
*** Ranjitha has joined #openstack-meeting-alt21:18
*** baoli has joined #openstack-meeting-alt21:20
*** baoli has quit IRC21:20
*** baoli has joined #openstack-meeting-alt21:21
*** sarob_ has joined #openstack-meeting-alt21:22
*** Barker has joined #openstack-meeting-alt21:22
*** Duane_ has quit IRC21:24
*** sarob has quit IRC21:24
*** irenab has quit IRC21:25
*** ccrouch has joined #openstack-meeting-alt21:28
*** michael-yu has quit IRC21:30
*** Ranjitha has quit IRC21:30
*** ijw has joined #openstack-meeting-alt21:31
*** balajiiyer has quit IRC21:31
*** Barker has quit IRC21:33
*** michael-yu has joined #openstack-meeting-alt21:34
*** amcrn has quit IRC21:34
*** Ranjitha has joined #openstack-meeting-alt21:35
*** gokrokve has joined #openstack-meeting-alt21:36
*** sarob_ has quit IRC21:39
*** amcrn has joined #openstack-meeting-alt21:41
*** tanisdl has joined #openstack-meeting-alt21:49
*** Duane_ has joined #openstack-meeting-alt21:55
*** Barker has joined #openstack-meeting-alt21:56
*** chadlung has joined #openstack-meeting-alt21:57
*** Duane_ has quit IRC21:57
*** balajiiyer has joined #openstack-meeting-alt21:57
*** Barker has quit IRC21:59
*** lisaclark1 has quit IRC21:59
*** sarob has joined #openstack-meeting-alt21:59
*** sarob has quit IRC22:00
*** sarob has joined #openstack-meeting-alt22:01
*** RajeshMohan has quit IRC22:02
*** ijw_ has joined #openstack-meeting-alt22:03
*** harlowja has quit IRC22:03
*** RajeshMohan has joined #openstack-meeting-alt22:03
*** sarob has quit IRC22:06
*** ijw has quit IRC22:06
*** ErikB has joined #openstack-meeting-alt22:09
*** balajiiyer has left #openstack-meeting-alt22:11
*** jecarey has quit IRC22:12
*** lblanchard has quit IRC22:13
*** boris-42_ has quit IRC22:13
*** NearlyFunctional has quit IRC22:18
*** kmak has joined #openstack-meeting-alt22:19
*** pdmars has quit IRC22:20
*** ErikB has quit IRC22:20
*** ErikB has joined #openstack-meeting-alt22:21
*** demorris has quit IRC22:22
*** sgordon has quit IRC22:23
*** demorris has joined #openstack-meeting-alt22:23
*** noslzzp has quit IRC22:24
*** jecarey has joined #openstack-meeting-alt22:25
*** aignatov is now known as aignatov_22:26
*** jtomasek has quit IRC22:26
*** jrist has joined #openstack-meeting-alt22:26
*** flwang has quit IRC22:27
*** jog0 has left #openstack-meeting-alt22:27
*** dprince has quit IRC22:28
*** lisaclark1 has joined #openstack-meeting-alt22:31
*** MarkAtwood has quit IRC22:31
*** noslzzp has joined #openstack-meeting-alt22:31
*** NearlyFunctional has joined #openstack-meeting-alt22:35
*** lisaclark1 has quit IRC22:35
*** igormarnat_ has quit IRC22:38
*** Barker has joined #openstack-meeting-alt22:38
*** balajiiyer has joined #openstack-meeting-alt22:42
*** noslzzp has quit IRC22:42
*** balajiiyer has quit IRC22:46
*** noslzzp has joined #openstack-meeting-alt22:47
*** eankutse has quit IRC22:51
*** mwagner_lap has quit IRC22:52
*** jmontemayor has quit IRC22:53
*** noslzzp has quit IRC22:54
*** gokrokve has quit IRC22:58
*** demorris has quit IRC22:58
*** igormarnat_ has joined #openstack-meeting-alt23:00
*** gokrokve has joined #openstack-meeting-alt23:00
*** sarob has joined #openstack-meeting-alt23:02
*** flwang has joined #openstack-meeting-alt23:02
*** gokrokve has quit IRC23:02
*** gokrokve has joined #openstack-meeting-alt23:02
*** banix has quit IRC23:03
*** gokrokve has quit IRC23:03
*** zzelle has quit IRC23:04
*** sarob has quit IRC23:07
*** noslzzp has joined #openstack-meeting-alt23:09
*** harlowja has joined #openstack-meeting-alt23:09
*** dane_ has quit IRC23:10
*** kevinconway_ has joined #openstack-meeting-alt23:11
*** sarob has joined #openstack-meeting-alt23:12
*** kevinconway has quit IRC23:14
*** kevinconway_ is now known as kevinconway23:14
*** noslzzp has quit IRC23:16
*** sarob has quit IRC23:16
*** cadenzajon has quit IRC23:17
*** esker has quit IRC23:18
*** krtaylor has quit IRC23:22
*** noslzzp has joined #openstack-meeting-alt23:25
*** RaymondWong has quit IRC23:26
*** baoli has quit IRC23:29
*** baoli has joined #openstack-meeting-alt23:30
*** Leonr has quit IRC23:31
*** baoli has quit IRC23:31
*** dhellmann is now known as dhellmann_23:32
*** pballand has quit IRC23:36
*** pballand has joined #openstack-meeting-alt23:36
*** markwash has quit IRC23:36
*** jdob has quit IRC23:40
*** chadlung has quit IRC23:40
*** julim has quit IRC23:40
*** denis_makogon has quit IRC23:41
*** mozawa has quit IRC23:42
*** balajiiyer1 has joined #openstack-meeting-alt23:42
*** balajiiyer1 has quit IRC23:47
*** noslzzp has quit IRC23:47
*** vkmc has quit IRC23:47
*** yogesh has quit IRC23:49
*** yogesh has joined #openstack-meeting-alt23:49
*** noslzzp has joined #openstack-meeting-alt23:51
*** tanisdl has quit IRC23:53
*** yogesh has quit IRC23:54
*** tanisdl has joined #openstack-meeting-alt23:57
*** noslzzp has quit IRC23:57
*** pballand has quit IRC23:58

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