Thursday, 2015-02-12

*** emagana has quit IRC00:02
*** markvoelker has quit IRC00:03
*** baoli has quit IRC00:08
*** emagana has joined #openstack-meeting-300:08
*** sambetts has quit IRC00:08
*** VW_ has joined #openstack-meeting-300:11
*** stevedoll has quit IRC00:11
*** emagana has quit IRC00:12
*** stevedoll has joined #openstack-meeting-300:13
*** MarkAtwood has quit IRC00:14
*** SridharRamaswamy has joined #openstack-meeting-300:14
*** emagana has joined #openstack-meeting-300:26
*** banix has quit IRC00:27
*** Longgeek has quit IRC00:30
*** VW_ has quit IRC00:30
*** stevedoll has quit IRC00:31
*** banix has joined #openstack-meeting-300:35
*** stevedoll has joined #openstack-meeting-300:40
*** mattgriffin has joined #openstack-meeting-300:40
*** markvoelker has joined #openstack-meeting-300:52
*** banix has quit IRC00:55
*** VW_ has joined #openstack-meeting-300:55
*** markvoelker has quit IRC00:57
*** markvoelker has joined #openstack-meeting-300:59
*** banix has joined #openstack-meeting-301:01
*** ChuckC has quit IRC01:02
*** ChuckC has joined #openstack-meeting-301:03
*** markvoelker has quit IRC01:04
*** megm has joined #openstack-meeting-301:14
*** megm_ has quit IRC01:15
*** stevedoll has quit IRC01:25
*** banix has quit IRC01:25
*** amotoki has joined #openstack-meeting-301:27
*** amotoki has quit IRC01:28
*** banix has joined #openstack-meeting-301:31
*** banix has quit IRC01:32
*** TravT has quit IRC01:32
*** sarob has quit IRC01:36
*** sarob has joined #openstack-meeting-301:38
*** markvoelker has joined #openstack-meeting-301:40
*** sarob has quit IRC01:43
*** sigmavirus24 is now known as sigmavirus24_awa01:43
*** clu_ has quit IRC01:44
*** stanzgy has joined #openstack-meeting-301:46
*** ChuckC_ has joined #openstack-meeting-301:46
*** watanabe_isao has quit IRC01:47
*** ChuckC has quit IRC01:49
*** TheJulia has quit IRC01:54
*** mwang2_ has quit IRC01:55
*** SridharRamaswamy has quit IRC02:00
*** VW_ has quit IRC02:01
*** melwitt has quit IRC02:06
*** melwitt has joined #openstack-meeting-302:06
*** watanabe_isao has joined #openstack-meeting-302:07
*** VW_ has joined #openstack-meeting-302:08
*** nelsnelson has joined #openstack-meeting-302:10
*** etoews has joined #openstack-meeting-302:12
*** Longgeek has joined #openstack-meeting-302:15
*** salv-orlando has quit IRC02:15
*** banix has joined #openstack-meeting-302:19
*** VW_ has quit IRC02:23
*** sambetts has joined #openstack-meeting-302:29
*** armax has quit IRC02:29
*** sarob has joined #openstack-meeting-302:39
*** obondarev_ has joined #openstack-meeting-302:43
*** sarob has quit IRC02:44
*** bpokorny has quit IRC02:45
*** asahlin_ has joined #openstack-meeting-302:46
*** cgoncalv1s has joined #openstack-meeting-302:47
*** Longgeek has quit IRC02:48
*** shakamunyi has joined #openstack-meeting-302:49
*** vgridnev has quit IRC02:52
*** asahlin has quit IRC02:52
*** obondarev has quit IRC02:52
*** cgoncalves has quit IRC02:52
*** emagana has quit IRC02:53
*** emagana has joined #openstack-meeting-302:54
*** Longgeek has joined #openstack-meeting-302:55
*** vgridnev has joined #openstack-meeting-302:56
*** etoews has quit IRC02:56
*** jckasper has joined #openstack-meeting-302:57
*** emagana has quit IRC02:58
*** david-lyle is now known as david-lyle_afk02:59
*** yamahata has quit IRC03:06
*** murkk has quit IRC03:08
*** MarkAtwood has joined #openstack-meeting-303:13
*** MarkAtwood has quit IRC03:14
*** salv-orlando has joined #openstack-meeting-303:16
*** VW_ has joined #openstack-meeting-303:17
*** salv-orlando has quit IRC03:21
*** lazy_prince is now known as killer_prince03:21
*** nelsnelson has quit IRC03:22
*** melwitt has quit IRC03:22
*** Piet has quit IRC03:22
*** nelsnelson has joined #openstack-meeting-303:25
*** sarob has joined #openstack-meeting-303:29
*** evgenyf has joined #openstack-meeting-303:30
*** Piet has joined #openstack-meeting-303:32
*** evgenyf has quit IRC03:34
*** salv-orlando has joined #openstack-meeting-303:36
*** melwitt has joined #openstack-meeting-303:39
*** salv-orlando has quit IRC03:40
*** salv-orlando has joined #openstack-meeting-303:41
*** melwitt has quit IRC03:51
*** yamahata has joined #openstack-meeting-303:53
*** etoews has joined #openstack-meeting-303:53
*** salv-orlando has quit IRC03:57
*** etoews has quit IRC03:57
*** nelsnelson has quit IRC04:00
*** salv-orlando has joined #openstack-meeting-304:01
*** armax has joined #openstack-meeting-304:04
*** salv-orlando has quit IRC04:05
*** VW_ has quit IRC04:06
*** VW_ has joined #openstack-meeting-304:08
*** Longgeek has quit IRC04:10
*** killer_prince is now known as lazy_prince04:19
*** Longgeek has joined #openstack-meeting-304:25
*** Longgeek has quit IRC04:26
*** lazy_prince has quit IRC04:34
*** barra204 has joined #openstack-meeting-304:35
*** salv-orlando has joined #openstack-meeting-304:37
*** ivar-lazzaro has quit IRC04:38
*** shakamunyi has quit IRC04:39
*** salv-orlando has quit IRC04:41
*** lazy_prif has joined #openstack-meeting-304:42
*** lazy_prif is now known as lazy_prince04:42
*** marg7175 has quit IRC04:52
*** barra204 has quit IRC04:53
*** salv-orlando has joined #openstack-meeting-304:59
*** salv-orlando has quit IRC05:02
*** salv-orlando has joined #openstack-meeting-305:05
*** barra204 has joined #openstack-meeting-305:07
*** VW_ has quit IRC05:08
*** sarob has quit IRC05:09
*** salv-orlando has quit IRC05:12
*** banix has quit IRC05:15
*** salv-orlando has joined #openstack-meeting-305:15
*** megm_ has joined #openstack-meeting-305:16
*** megm has quit IRC05:17
*** mwagner_lap has quit IRC05:19
*** coolsvap has joined #openstack-meeting-305:19
*** coolsvap has quit IRC05:21
*** coolsvap has joined #openstack-meeting-305:23
*** r1chardj0n3s is now known as r1chardj0n3s_afk05:24
*** amotoki has joined #openstack-meeting-305:25
*** VW_ has joined #openstack-meeting-305:27
*** sarob has joined #openstack-meeting-305:28
*** salv-orlando has quit IRC05:30
*** mattgriffin has quit IRC05:31
*** sarob has quit IRC05:32
*** VW_ has quit IRC05:39
*** salv-orlando has joined #openstack-meeting-305:40
*** carl_baldwin has joined #openstack-meeting-305:46
*** salv-orlando has quit IRC05:52
*** etoews has joined #openstack-meeting-305:53
*** etoews has quit IRC05:58
*** carl_baldwin has quit IRC06:04
*** Longgeek has joined #openstack-meeting-306:07
*** salv-orlando has joined #openstack-meeting-306:08
*** salv-orlando has quit IRC06:15
*** salv-orlando has joined #openstack-meeting-306:16
*** salv-orlando has quit IRC06:18
*** salv-orlando has joined #openstack-meeting-306:21
*** salv-orlando has quit IRC06:25
*** barra204 has quit IRC06:36
*** radek has joined #openstack-meeting-306:40
*** mwagner_lap has joined #openstack-meeting-306:42
*** salv-orlando has joined #openstack-meeting-306:49
*** marios has joined #openstack-meeting-306:50
*** mrunge has joined #openstack-meeting-306:53
*** etoews has joined #openstack-meeting-306:54
*** yamamoto_ has joined #openstack-meeting-306:56
*** salv-orlando has quit IRC06:56
*** lazy_prince has quit IRC06:57
*** thomasem has quit IRC06:57
*** killer_prince has joined #openstack-meeting-306:57
*** killer_prince is now known as lazy_prince06:57
*** pkoniszewski has joined #openstack-meeting-307:01
*** thomasem has joined #openstack-meeting-307:02
*** etoews has quit IRC07:03
*** scheuran has joined #openstack-meeting-307:12
*** burgobianco has quit IRC07:12
*** sarob has joined #openstack-meeting-307:30
*** sarob has quit IRC07:34
*** jcoufal has joined #openstack-meeting-307:35
*** burgobianco has joined #openstack-meeting-307:40
*** flaper87 has quit IRC07:41
*** flaper87 has joined #openstack-meeting-307:41
*** killer_prince has joined #openstack-meeting-307:42
*** lazy_prince has quit IRC07:43
*** killer_prince is now known as lazy_prince07:43
*** vkmc has quit IRC07:43
*** vkmc has joined #openstack-meeting-307:43
*** sergef has joined #openstack-meeting-307:44
*** sahid has joined #openstack-meeting-307:45
*** coolsvap has quit IRC07:48
*** coolsvap has joined #openstack-meeting-307:48
*** pkoniszewski has quit IRC07:49
*** pkoniszewski has joined #openstack-meeting-307:49
*** scheuran has quit IRC07:49
*** scheuran has joined #openstack-meeting-307:49
*** jcoufal has quit IRC07:49
*** jcoufal has joined #openstack-meeting-307:49
*** Longgeek has quit IRC07:53
*** Longgeek has joined #openstack-meeting-307:53
*** Longgeek has quit IRC07:53
*** mrmartin has joined #openstack-meeting-308:05
*** salv-orlando has joined #openstack-meeting-308:11
*** lsmola has joined #openstack-meeting-308:12
*** wojdev has joined #openstack-meeting-308:17
*** watanabe_isao has quit IRC08:43
*** iovadia has joined #openstack-meeting-308:45
*** devvesa has joined #openstack-meeting-308:46
*** yamamoto_ has quit IRC08:46
*** matrohon has joined #openstack-meeting-308:46
*** JeanBriceCombebi has joined #openstack-meeting-308:47
*** iovadia has quit IRC08:50
*** jtomasek has joined #openstack-meeting-308:51
*** Longgeek has joined #openstack-meeting-308:54
*** MaxV has joined #openstack-meeting-308:55
*** evgenyf has joined #openstack-meeting-309:00
*** etoews has joined #openstack-meeting-309:01
*** safchain has joined #openstack-meeting-309:02
*** iovadia has joined #openstack-meeting-309:03
*** zz_ttrifonov is now known as ttrifonov09:04
*** etoews has quit IRC09:05
*** Longgeek has quit IRC09:07
*** JeanBriceCombebi has quit IRC09:09
*** megm has joined #openstack-meeting-309:18
*** enikanorov_ has quit IRC09:19
*** megm_ has quit IRC09:19
*** enikanorov_ has joined #openstack-meeting-309:20
*** jtomasek has quit IRC09:20
*** stanzgy has quit IRC09:21
*** jckasper has quit IRC09:22
*** yamamoto has joined #openstack-meeting-309:22
*** amotoki has quit IRC09:23
*** yamamoto has quit IRC09:27
*** mwang2 has joined #openstack-meeting-309:27
*** amotoki has joined #openstack-meeting-309:28
*** tmazur has joined #openstack-meeting-309:30
*** scheuran_ has joined #openstack-meeting-309:31
*** mwang2 has quit IRC09:32
*** scheuran has quit IRC09:32
*** yamamoto has joined #openstack-meeting-309:33
*** armax has quit IRC09:33
*** jtomasek has joined #openstack-meeting-309:34
*** zz_johnthetubagu is now known as johnthetubaguy09:35
*** jtomasek has quit IRC09:37
*** jtomasek has joined #openstack-meeting-309:37
*** yamamoto has quit IRC09:46
*** wojdev has quit IRC09:51
*** enikanorov_ has quit IRC09:51
*** wojdev has joined #openstack-meeting-309:51
*** enikanorov_ has joined #openstack-meeting-309:51
*** enikanorov__ has joined #openstack-meeting-309:56
*** enikanorov_ has quit IRC09:57
*** yamamoto has joined #openstack-meeting-310:00
*** JeanBriceCombebi has joined #openstack-meeting-310:03
*** Longgeek has joined #openstack-meeting-310:04
*** yamamoto has quit IRC10:21
*** Longgeek has quit IRC10:38
*** Longgeek has joined #openstack-meeting-310:44
*** marios has quit IRC10:46
*** mattgriffin has joined #openstack-meeting-310:50
*** salv-orlando has quit IRC10:53
*** marios has joined #openstack-meeting-310:56
*** yamahata has quit IRC10:59
*** etoews has joined #openstack-meeting-311:02
*** etoews has quit IRC11:07
*** sambetts has left #openstack-meeting-311:08
*** mattgriffin has quit IRC11:09
*** JeanBriceCombebi has quit IRC11:16
*** JeanBriceCombebi has joined #openstack-meeting-311:17
*** dobson has quit IRC11:27
*** salv-orlando has joined #openstack-meeting-311:27
*** dobson has joined #openstack-meeting-311:34
*** markvoelker has quit IRC11:34
*** absubram has quit IRC11:52
*** JeanBriceCombebi has quit IRC11:59
*** amotoki has quit IRC11:59
*** etoews has joined #openstack-meeting-312:03
*** etoews has quit IRC12:07
*** JeanBriceCombebi has joined #openstack-meeting-312:20
*** pavel_bondar has joined #openstack-meeting-312:22
*** wojdev has quit IRC12:28
*** salv-orlando has quit IRC12:29
*** markvoelker has joined #openstack-meeting-312:35
*** tellesnobrega_ has joined #openstack-meeting-312:36
*** markvoelker has quit IRC12:40
*** tellesnobrega_ has quit IRC12:58
*** markvoelker has joined #openstack-meeting-312:59
*** jckasper has joined #openstack-meeting-313:02
*** baoli has joined #openstack-meeting-313:03
*** salv-orlando has joined #openstack-meeting-313:03
*** etoews has joined #openstack-meeting-313:04
*** markvoelker has quit IRC13:05
*** lazy_prince is now known as killer_prince13:07
*** killer_prince is now known as lazy_prince13:08
*** etoews has quit IRC13:08
*** alexpilotti has joined #openstack-meeting-313:09
*** jckasper has quit IRC13:10
*** jckasper has joined #openstack-meeting-313:10
*** mwagner_lap has quit IRC13:11
*** jcoufal_ has joined #openstack-meeting-313:17
*** jcoufal has quit IRC13:20
*** megm_ has joined #openstack-meeting-313:21
*** megm has quit IRC13:21
*** scheuran_ has quit IRC13:33
*** wojdev has joined #openstack-meeting-313:34
*** tellesnobrega has joined #openstack-meeting-313:37
*** wojdev has quit IRC13:44
*** amotoki has joined #openstack-meeting-313:48
*** weiting has joined #openstack-meeting-313:52
*** zhidong has joined #openstack-meeting-313:53
*** elmiko has joined #openstack-meeting-313:53
*** mattf has joined #openstack-meeting-313:54
*** Nikolay_St has joined #openstack-meeting-313:54
*** _crobertsrh has joined #openstack-meeting-313:57
*** sahid has quit IRC13:58
*** mwagner_lap has joined #openstack-meeting-313:58
*** sahid has joined #openstack-meeting-313:59
*** huichun has joined #openstack-meeting-313:59
SergeyLukjanovhey sahara folks!13:59
*** tosky has joined #openstack-meeting-314:00
*** amotoki_ has joined #openstack-meeting-314:00
SergeyLukjanov#startmeeting sahara14:00
openstackMeeting started Thu Feb 12 14:00:47 2015 UTC and is due to finish in 60 minutes.  The chair is SergeyLukjanov. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: sahara)"14:00
openstackThe meeting name has been set to 'sahara'14:00
*** sigmavirus24_awa is now known as sigmavirus2414:01
*** egafford has joined #openstack-meeting-314:01
SergeyLukjanov#topic sahara@horizon status (crobertsrh, NikitaKonovalov)14:01
*** openstack changes topic to "sahara@horizon status (crobertsrh, NikitaKonovalov) (Meeting topic: sahara)"14:01
*** cgoncalv1s is now known as cgoncalves14:01
*** amotoki__ has joined #openstack-meeting-314:02
*** jcoufal_ has quit IRC14:02
*** jcoufal has joined #openstack-meeting-314:02
NikitaKonovalovok, so we've got things moving a bit14:02
*** amotoki has quit IRC14:02
*** amotok___ has joined #openstack-meeting-314:02
SergeyLukjanov_crobertsrh, do you probably have a list of things to promote?14:02
NikitaKonovalovthe change for job execution table has finally got targeted for kilo-314:03
_crobertsrhHere's the current list:
*** _crobertsrh is now known as crobertsrh14:03
NikitaKonovalovand that's a good sign for getting it reviewed14:03
NikitaKonovalovbtw, we need to make sure that all patches on review have a target milestone14:04
SergeyLukjanovNikitaKonovalov, nice14:04
crobertsrhI don't think we can set that, can we?14:04
SergeyLukjanovcrobertsrh, oh, yeah, i see it updated :)14:04
NikitaKonovalovcrobertsrh: we can't14:04
SergeyLukjanovcrobertsrh, we could prepare a list of the important stuff to promote and ask david-lyle to set milestone for tham14:05
NikitaKonovalovbut horizon cores can14:05
*** JeanBriceCombebi has quit IRC14:05
*** JeanBriceCombebi has joined #openstack-meeting-314:05
*** amotoki_ has quit IRC14:05
*** kchen has joined #openstack-meeting-314:05
NikitaKonovalovcrobertsrh: I think the top section in etherpad is the one to be promoted14:05
crobertsrhYeah.  Feel free to re-order those items if necessary.14:06
*** amotoki__ has quit IRC14:06
SergeyLukjanovcrobertsrh, thanks for keeping it uptodate14:06
NikitaKonovalovcrobertsrh: ok14:06
*** Piet has quit IRC14:06
SergeyLukjanov#topic News / updates14:06
*** openstack changes topic to "News / updates (Meeting topic: sahara)"14:06
*** tmckay has joined #openstack-meeting-314:07
SergeyLukjanovI've proposed new members to stable main team -
elmikosecurity doc is finally up for review14:07
elmikoand i've got an idea for a barbican integration spec14:08
tmckayworking on solution for hbase jobs, should have a spec today, a few things left to investigate with Oozie14:08
Nikolay_Stsahara logging spec is up for discussion/review14:08
*** salv-orlando has quit IRC14:08
sreshetnyaki'm working on new integration tests and bug fixing14:08
*** salv-orlando has joined #openstack-meeting-314:08
vgridnevuploaded new spec to add timeouts for polling processes in sahara14:09
*** huichun_ has joined #openstack-meeting-314:09
weitingstill working on key store value integration test for cdh plugin, I got one issue about the memory size is too small since our test case provide more services.14:09
egaffordThanks SergeyLukjanov (re: stable maint.) Working with TripleO guys on Sahara integration; commits are pending the arrival of some hardware to field a dev environment.14:10
*** VW_ has joined #openstack-meeting-314:10
huichun_tmckay: thank you Mckay14:10
SergeyLukjanovegafford, are you probably going to the tripleo meetup?14:10
tmckayhuichun_, np, did you see my email?14:11
egaffordSergeyLukjanov: Do you mean meeting (IRC) or meetup (in-person)?14:11
tmckayhuichun_, question is the best way to handle sharelib.  We might want to use oozie admin and a tarball, still investigating ...14:11
huichun_tmckay: Trevor. I have read the email already14:11
tmckayhuichun_, I hope to have the spec up for comments today14:12
SergeyLukjanovegafford, meetup14:12
huichun_tmckay: ok, i will follow up you14:12
*** salv-orlando has quit IRC14:13
egaffordSergeyLukjanov: I am not going to an in-person meetup. I am primarily assigned to (and interested in!) Sahara; I've just been assigned to a lot of installer integration projects thus far.14:13
SergeyLukjanovegafford, oh, ok14:14
SergeyLukjanovegafford, /me great to here that you're full time assigned to our awesome project :)14:14
SergeyLukjanovany other news?14:14
SergeyLukjanovI'd like to release client after the meeting14:14
SergeyLukjanovany objections?14:14
tmckaySergeyLukjanov, I have to drop.  elmiko and I had a question about "recheck" best practices and docs (if any?) for open discussion.  I am happy to be on the stable team.  No other updates beyond oozie hbase stuff14:15
elmikono objection here14:15
Nikolay_Sttry to resolve this bug #link
openstackLaunchpad bug 1396214 in Sahara "Sahara image builder should execute 'yum update' during the build image" [High,Confirmed] - Assigned to Nikolay Starodubtsev (starodubcevna)14:15
tmckaynone here14:15
SergeyLukjanov#topic Open discussion14:15
*** openstack changes topic to "Open discussion (Meeting topic: sahara)"14:15
SergeyLukjanovtmckay, elmiko, what kind of best practices for recheck?14:16
*** wojdev has joined #openstack-meeting-314:16
elmikois there any official documentation about how recheck works?14:16
SergeyLukjanovsahara-ci-recheck could recheck only sahara ci, "recheck" rechecks all CIs14:16
elmikoi've seen recheck, sahara-ci-recheck, recheck-ci, etc...14:16
elmikois it documented somewhere though?14:17
SergeyLukjanovany CI should recheck if comments starts with "recheck"14:17
mattfmy personal fav: recheck sahara-ci14:17
elmikoseriously, it's some regex check?14:17
kchenhi all, I just have a patch merged, to have cdh 5.3.0 tagged image in image-element. but I am not sure when there will be a corresponding 5.3.0 tagged image registry in ci system?14:17
SergeyLukjanovmattf, it rechecks all CI systems14:17
huichun_tmckay: Hi Trevor, if we want to add new feature for edp jobs, need to modify the horizon page, so who should we contact?14:17
mattfSergeyLukjanov, yeah, kinda bums me out14:17
kchenwe need such a image registry to do our cdh 5.3 test cases...14:17
elmikohuichun_: probably want to start by talking with crobertsrh and NikitaKonovalov14:18
elmikohuichun_: they've done much work with horizon14:18
SergeyLukjanovokay, I've found regex links14:18
SergeyLukjanovhere is for the sahara ci -
elmikoSergeyLukjanov: thanks!14:18
SergeyLukjanovand for the main jenkins -
crobertsrhYes, huichun.  I can probably help.  If there is a spec, you can probably put my name in there for dashboard stuff.14:19
huichun_crobertsrh: thx crobertsrh14:19
SergeyLukjanovwe should ask degorenko to add CDH 5.3 image and jobs to sahara-ci and disable 5.014:20
huichun_tmckay: you will have some horizon page modification in your specs, right?14:21
kchenSergey, we can keep both 5.0 and 5.3 tags. so that we can use it for both test.14:21
*** tmckay has quit IRC14:22
huichun_tmckay: btw, i have replied your email, that hbase classpath is not platform specific, i have tested14:22
SergeyLukjanovkchen, I mean we'll have CDH tests in sahara-ci only for the latest version14:23
huichun_elmiko: thx elmiko14:23
kchenSergeyLukjanov: if we only test latest version, need we preserve other versions in cdh plugin?14:24
weitingsergey: why sahara-ci only test for the latest one?14:24
*** david-lyle_afk is now known as david-lyle14:25
SergeyLukjanovkchen, weiting, it's just a question about lack of the resource to test all configurations14:25
weitingsergey: could we remove 5.0 for cdh?14:26
SergeyLukjanovwas it released as part of the Juno release/14:28
SergeyLukjanovif yes we could deprecate it in kilo and remove in liberty14:28
*** alexpilotti has quit IRC14:28
*** alexpilotti has joined #openstack-meeting-314:29
*** peristeri has joined #openstack-meeting-314:30
*** jtomasek has quit IRC14:31
*** DenisEgorenko has joined #openstack-meeting-314:31
SergeyLukjanovanything else to discuss folks?14:32
elmiko <--- please review =)14:32
*** jcoufal has quit IRC14:33
*** jcoufal_ has joined #openstack-meeting-314:33
*** JeanBriceCombebi has quit IRC14:34
*** JeanBriceCombebi has joined #openstack-meeting-314:34
*** thangp has joined #openstack-meeting-314:34
crobertsrhNothing from me14:34
SergeyLukjanovokay, thank you folks14:35
*** lblanchard has joined #openstack-meeting-314:36
*** openstack changes topic to "OpenStack Meetings ||"14:36
openstackMeeting ended Thu Feb 12 14:36:03 2015 UTC.  Information about MeetBot at . (v 0.1.4)14:36
openstackMinutes (text):
*** mattf has left #openstack-meeting-314:38
*** tosky has left #openstack-meeting-314:39
*** huichun has quit IRC14:40
*** banix has joined #openstack-meeting-314:40
*** huichun_ has quit IRC14:40
*** jtomasek has joined #openstack-meeting-314:44
*** jpomero has joined #openstack-meeting-314:48
*** egafford has left #openstack-meeting-314:50
*** tellesnobrega has quit IRC14:51
*** tidwellr has joined #openstack-meeting-314:52
*** mbgalt has joined #openstack-meeting-314:52
*** tellesnobrega_ has joined #openstack-meeting-314:54
*** amuller has joined #openstack-meeting-314:55
*** tellesnobrega_ has quit IRC14:55
*** kchen has quit IRC14:56
*** carl_baldwin has joined #openstack-meeting-314:57
*** johnbelamaric has joined #openstack-meeting-314:58
*** qwebirc68886 has joined #openstack-meeting-314:58
*** etoews has joined #openstack-meeting-314:58
carl_baldwinhi all14:59
*** pc_m has joined #openstack-meeting-314:59
*** mlavalle has joined #openstack-meeting-315:00
carl_baldwin#startmeeting neutron_l315:00
openstackMeeting started Thu Feb 12 15:00:55 2015 UTC and is due to finish in 60 minutes.  The chair is carl_baldwin. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:00
openstackThe meeting name has been set to 'neutron_l3'15:00
carl_baldwin#topic Announcements15:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:01
*** weiting has quit IRC15:01
carl_baldwinAny announcements for today?  I don’t think I have any.15:01
carl_baldwinLooking at the meeting page, I need to update it.15:01
carl_baldwinI’ve heard the name of the L release will be Liberty.  Is that right?15:02
*** qwebirc68886 has quit IRC15:02
carl_baldwinAlso, keep a close eye on the kilo release schedule.15:02
carl_baldwinMarch 19th will come very soon.  If history is a good indicator, the gate will get crazy and it will be difficult to get stuff in the last week or son.15:03
pc_mcarl_baldwin: Yes Liberty15:03
carl_baldwinAny other announcements?15:03
carl_baldwin#topic Bugs15:03
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:03
carl_baldwinAny bugs that we should be aware of?15:04
carl_baldwinI’m not aware of any new ones.15:04
carl_baldwinAny discussion needed here?15:04
carl_baldwin#topic L3 Agent Restructuring15:05
*** openstack changes topic to "L3 Agent Restructuring (Meeting topic: neutron_l3)"15:05
carl_baldwinThis is going well.  Once I can finish my latest patch, I think pretty much all of the router logic will be moved to the router classes.15:05
carl_baldwinThanks to all of you who have pitched in with patches and reviews.15:07
carl_baldwinAnything else to discuss about restructuring?15:07
carl_baldwin#topic neutron-ipam15:08
*** openstack changes topic to "neutron-ipam (Meeting topic: neutron_l3)"15:08
carl_baldwinjohnbelamaric: pavel_bondar: salv-orlando: ping15:08
johnbelamariccarl_baldwin: pong15:08
*** dboik has joined #openstack-meeting-315:08
carl_baldwintidwellr too15:09
tidwellrcarl_baldwin: pong15:09
*** zhidong has quit IRC15:09
carl_baldwinI think we’ve got one open issue with the interface.15:09
carl_baldwinThat is how to update IPAM with changes in the subnet.15:10
johnbelamaricyes - also i want to verify that the subnet request will contain a pre-generated subnet_id, even though it has not yet been allocated15:10
johnbelamaricat least, that's what the interface is implying now15:11
*** pkoniszewski has quit IRC15:11
*** JeanBriceCombebi has quit IRC15:11
carl_baldwinjohnbelamaric: That is what I was thinking.  Do you think that will work?15:11
*** marun has joined #openstack-meeting-315:12
johnbelamariccarl_baldwin: sure, that should be fine. one sec let me go back and read the comments15:12
*** lazy_prince is now known as killer_prince15:13
*** JeanBriceCombebi has joined #openstack-meeting-315:13
johnbelamariccarl_baldwin: ok, so the discussion on PS 18 line 22115:14
*** salv-orlando has joined #openstack-meeting-315:14
carl_baldwinjohnbelamaric: What about a SubnetUpdateRequest.  Very much like SpecificSubnetRequest.15:15
* carl_baldwin just thinking out loud here.15:16
johnbelamariccarl_baldwin: the subnet_id resolves the issue from line 85. but line 221 is talking about the sequencing and where/when the DB object is created and saved and who has that responsibility15:16
johnbelamariccarl_baldwin: sure, that's possible. but why not just pass the subnet object to the driver and let it decide what to do with it?15:16
*** tmckay has joined #openstack-meeting-315:16
johnbelamariccarl_baldwin: to me, the idea of the request was that we would be allocating based on various criteria. The update isn't to the CIDR, it's just to the name or other meta-data, isn't it?15:17
*** salv-orlando has quit IRC15:17
carl_baldwinjohnbelamaric: Right.15:17
johnbelamariccarl_baldwin: i guess allocation pools - can the driver reject a change to allocation pool? i would think it would need to be able to15:18
*** tmckay has left #openstack-meeting-315:18
carl_baldwinjohnbelamaric: I think the driver could reject such a change.  The current implementation doesn’t but I think it should be able to.15:18
carl_baldwinjohnbelamaric: I’ll look at it today.  Will you be around in case I want to ping you in openstack-neutron?15:19
johnbelamariccarl_baldwin: yes, i should be unless i am in a meeting or something. i do have to leave for a memorial service at 5pm eastern today, though :(15:19
*** JeanBriceCombebi has quit IRC15:20
carl_baldwinjohnbelamaric: I’ll plan to get to it well before that then.15:20
carl_baldwintidwellr: How is the subnet allocation coming?15:20
johnbelamariccarl_baldwin: ok. I am not sure for the need of a special "update request" object - do you see just passing the subnet object as enough?15:20
*** Yi has joined #openstack-meeting-315:21
tidwellrlooking to post a review that is not WIP tonight15:21
carl_baldwinjohnbelamaric: It might be.  I’m going to give it some thought and get back with you.15:22
carl_baldwintidwellr: Great.15:22
tidwellrjust working through some unit tests15:22
carl_baldwintidwellr: What parts will this patch cover in all?15:22
carl_baldwintidwellr: I guess all of the CRUD on the pool resource, right?  Probably doesn’t touch on allocation of subnets yet.15:23
tidwellrcarl_baldwin: it will cover CRUD on subnet pools and everything that goes with that15:23
tidwellrcarl_baldwin: no allocation yet15:23
carl_baldwintidwellr: Do we need to get tempest tests going for this?15:24
*** jgrimm is now known as zz_jgrimm15:24
tidwellrcarl_baldwin: for the allocation component? I would say yes, this is where the rubber meets the road15:24
johnbelamarictidwellr, carl_baldwin: actual allocation will be part of the driver, no? so creation of the pools would be enough, then the driver uses the pool info to do allocations15:25
tidwellrjohnbelamaric: when a subnet is requested, the driver still needs to be invoked15:26
carl_baldwinjohnbelamaric: Yes, I believe so.  We may need to be a bit creative since this and the drivers are being developed simultaneously.15:26
johnbelamarictidwellr: sure. ok - i will go look at the code and see how it will fit together15:27
carl_baldwintidwellr: I think even the subnet pool CRUD should be covered by tempest.  I’ll admit I’ve not written a full tempest test before.15:27
carl_baldwintidwellr: I wonder if we can find someone who would be willing to help us get started with the tempest tests.15:27
carl_baldwinDoes anyone here have any suggestions for who we might go to for help?15:28
*** dboik_ has joined #openstack-meeting-315:28
*** dboik_ has quit IRC15:28
carl_baldwin#action carl_baldwin will look in to getting tempest tests started.15:29
*** dboik_ has joined #openstack-meeting-315:29
*** dtroyer has joined #openstack-meeting-315:29
mlavallecarl_baldwin: talk to mtreinish15:29
carl_baldwinmlavalle: Thanks.  That is a good idea.15:29
mlavallecarl_baldwin: I might be of some small help. I just don't want to over commit. As you know, I am quite busy with the l3 agent restructuring15:30
carl_baldwinmlavalle: Thanks, we’ll take that in to consideration.15:30
carl_baldwinI feel the same way.15:31
*** dboik has quit IRC15:31
tidwellrcarl_baldwin: once I get a review up tonight and I could start looking into it15:31
tidwellrtempest sounds like a ramp for most of us here anyway15:31
carl_baldwintidwellr: I think there are some things that others could pitch in on so that you can start looking to allocation.15:32
tidwellrok, I'm fine with that, offer still stands though......15:32
carl_baldwintidwellr: great, thanks.15:32
*** JeanBriceCombebi has joined #openstack-meeting-315:32
carl_baldwinAnything else to discuss regarding ipam?15:32
pavel_bondarI will upload new version of re-factoring db_base patch for review aftr meeting15:33
carl_baldwinpavel_bondar: Great.  ping me when you do.15:33
pavel_bondarit will be still WIP, but the approach can be reviewed15:33
pavel_bondarcarl_baldwin: ok, sure15:34
carl_baldwin#topic neutron-ovs-dvr15:34
*** openstack changes topic to "neutron-ovs-dvr (Meeting topic: neutron_l3)"15:34
carl_baldwinAny dvr folks around today?15:34
*** baoli has quit IRC15:34
carl_baldwinI couldn’t make the dvr meeting yesterday but will read through the notes.15:34
carl_baldwin#action carl_baldwin will catch up on dvr meeting.15:34
carl_baldwinI found that the dvr check job (non-voting) had been failing on the stable branch.  I uploaded a backport to fix it.15:35
*** baoli_ has joined #openstack-meeting-315:35
*** crobertsrh has left #openstack-meeting-315:36
carl_baldwinThat is all I have.15:36
carl_baldwin#topic Open Discussion15:36
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)"15:36
carl_baldwinAnything else to discuss?15:37
amuller is generally ready for review15:38
carl_baldwinamuller: Thanks, I’ve actually been watching for an update on that one.15:39
*** Piet has joined #openstack-meeting-315:39
carl_baldwinWe’ll make it a short meeting then.  Thanks everyone.  I’ve seen great progress.  Keep up the great work.15:39
carl_baldwinI’ve got to be offline to ride in to the office but then I plan to be around the rest of the day.15:40
johnbelamaricok, bye all15:40
*** openstack changes topic to "OpenStack Meetings ||"15:40
openstackMeeting ended Thu Feb 12 15:40:38 2015 UTC.  Information about MeetBot at . (v 0.1.4)15:40
*** tmazur has quit IRC15:40
openstackMinutes (text):
*** amuller has left #openstack-meeting-315:41
*** marg7175 has joined #openstack-meeting-315:41
*** tidwellr has left #openstack-meeting-315:41
*** johnbelamaric has left #openstack-meeting-315:41
*** opsvision has joined #openstack-meeting-315:41
*** Networkn3rd has joined #openstack-meeting-315:42
*** pc_m has left #openstack-meeting-315:43
*** Rajeev has joined #openstack-meeting-315:46
*** amotok___ has quit IRC15:48
*** salv-orlando has joined #openstack-meeting-315:54
*** kaufer has joined #openstack-meeting-315:58
*** rosmaita has joined #openstack-meeting-315:59
*** ryansb has joined #openstack-meeting-316:00
rosmaitaanyone here for API-WG, or am i in wrong channel?16:00
ryansbrosmaita: I am16:00
*** mlavalle has left #openstack-meeting-316:00
sigmavirus24#startmeeting api wg16:00
openstackMeeting started Thu Feb 12 16:00:47 2015 UTC and is due to finish in 60 minutes.  The chair is sigmavirus24. Information about MeetBot at
dtroyerYou are in the right place16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: api wg)"16:00
openstackThe meeting name has been set to 'api_wg'16:00
*** clu_ has joined #openstack-meeting-316:00
sigmavirus24Hey everyone16:01
*** Nikolay_St has quit IRC16:01
sigmavirus24Seems etoews can't make it today so I volunteered to take over the hard hard work of chairing today ;)16:01
*** cdent has joined #openstack-meeting-316:01
sigmavirus24#topic agenda16:02
*** openstack changes topic to "agenda (Meeting topic: api wg)"16:02
kauferhey all16:02
rosmaitadid we have an etherpad with the various mission statements?16:02
sigmavirus24#topic mission statement16:02
*** openstack changes topic to "mission statement (Meeting topic: api wg)"16:02
elmikoi don't think it was updated from last time though16:02
* sigmavirus24 was going to find that :)16:02
*** stevedoll has joined #openstack-meeting-316:03
sigmavirus24unless someone else has it16:03
sigmavirus24#info mailing list thread
sigmavirus24Thanks elmiko16:03
ryansboop, too slow16:03
sigmavirus24and ryansb :)16:03
rosmaitaso my impression of the ML discussion is that stefano's is the favorite?16:04
sigmavirus24Or something along those lines, yes16:04
sigmavirus24(I think etoews had a few changes he wanted to make to it)16:05
ryansbIn essence, yes. I (only just posted) that I like how "API user" sounds, but even without that tweak +1 to stefano's16:05
elmikoyea, stefano's is nice16:05
cdentI prefer user to consumer as well, despite the weird connotations of both.16:05
*** zz_jgrimm is now known as jgrimm16:05
edleafe+1 to stefano's, even with the excessively long last sentence. :)16:05
sigmavirus24cdent: yeah, why can't we just make up words to avoid overriding syntax in OpenStack?16:05
cdentAPI flimflam with the frobnitz16:06
sigmavirus24cdent: +A16:06
ryansbaaaand openstack-ese was born16:06
sigmavirus24We want to discuss this further or should we move on? (I'm not really sure what etoews had wanted to say about this)16:07
cdentmove on16:07
sigmavirus24#action etoews to wrap up conversation on the mailing list and disseminate our mission statement16:07
dtroyerI think stefano's paragraph is a nice explanation/expansion, I still strongly prefer short and concise.  but will not hold things up, we spend too much time on this already16:07
sigmavirus24#topic Glance and functional API16:07
*** openstack changes topic to "Glance and functional API (Meeting topic: api wg)"16:07
sigmavirus24rosmaita: want to take this one?16:08
elmikodtroyer: i thought the idea was to have a long version, and a short tweetable version?16:08
*** salv-orlando has quit IRC16:08
dtroyerelmiko: tha's cool too16:08
rosmaitanot much to say, overall issue is "is there a place in openstack API for functional calls, and if so what should they look like?"16:08
rosmaitathe idea is that the current RESTful paradigm is extremely document-centric16:09
rosmaitaand not everything fits naturally into that paradigm16:10
rosmaitastuff can be forced into the paradigm if that's what's really wanted16:10
rosmaitaso the proposal is to introduce16:10
rosmaitaPOST /v2/images/{image_uuid}/action/deactivate16:11
rosmaitaeven though there's no "action"resource16:11
rosmaita(and similar POST to reactivate)16:11
elmikodoes there need to be an "action" in the uri?16:11
ryansbI like the idea of tasks as a resource foo/{}/action/frobozzle is ok without an action resource IMO since it acts as a namespace16:11
sigmavirus24I think it's also important to note (since I've been involved in this discussion a lot) that the contention is that Glance may do more than just change a status field on the image so this is meant to hide implementation details ideally (taken for granted that the spec in question does nothing other than change the status field iirc)16:12
sigmavirus24Also jaypipes had feedback on this coming from Nova but I'm not sure they're around16:12
rosmaitasigmavirus24: that's basically correct16:13
cdentwhat about POST /v2/images/{image_uuid}?deactivate or /v2/images{image_uuid};deactivate ? Your resources is still the image, you're just changing its state16:13
rosmaitacdent: well, the key thing is that you are not changing the state, the state machine is under complete control of glance16:13
*** wojdev has quit IRC16:13
rosmaitawe don't want anyone to have the impression that it's ok to monkey with state16:13
rosmaitaboth users and future devs16:14
*** salv-orlando has joined #openstack-meeting-316:14
ryansbthat's why tasks as a resource ae (IMO) better since you are manipulating a *request* not the resource state16:14
rosmaitayeah, except we already have tasks as actual entities16:14
rosmaitathis seems a different kind of thing16:14
rosmaitawe're requesting a function16:15
cdenthow is active or not active not part of the image's state? From the spec being "on hold" sounds exactly like state16:15
elmikocdent: i would think for a controller-ish action wouldn't it be better to have /v2/images/{id}/deactivate , or is that some sort of badness?16:15
rosmaitaelmiko: the actions part was in there jsut to group these things together16:15
rosmaitadon't necessarily have to have it16:16
rosmaitabut could keep things neat for later16:16
edleafeelmiko: that looks like 'deactivate' is a resource16:16
elmikorosmaita: right, except that like you said there is no "action" resource16:16
ryansb+1 on grouping16:16
rosmaitaelmiko: correct, no action resource, it's a function16:16
cdentelmiko I prefer to put the resource and nothing else in the path part of the URI to preserve the sense to which it is an identifier16:16
elmikoedleafe: i thought these type of endpoints were ok for exposing controller type actions?16:16
elmikocdent: got it16:16
rosmaitawe could replace "action" with "function" ... would that be more clear?16:17
edleafecdent: I like your idea, but with this tweak: POST /v2/images/{image_uuid}?action=deactivate16:17
rosmaita"action" is overloaded in openstack16:17
cdentyeah, that's fine edleafe16:17
cdentevery word is overload in openstack! :)16:17
elmiko"action" seems fine to me, i was more responding to the idea that /action wasn't a resource16:18
ryansbcdent: not the word "overloaded"...yet16:18
dtroyerdoes moving the action=<foo> to the query string change the rationale for using POST over PUT?16:18
edleaferosmaita: replace 'action' with 'task' or 'job' or 'function' or ...16:18
rosmaitawell, can't do 'task', it's taken!16:18
edleafedtroyer: good point16:18
cdentdtroyer: it would need to be POST, for PUT you're supposed to PUT the whole resoruce again16:18
sigmavirus24cdent: except the POST body here is empty16:18
sigmavirus24(according to the spec)16:19
* cdent struggles to type well16:19
cdentsigmavirus24: yeah, that's okay16:19
rosmaitai'm with cdent on not using PUT16:19
salv-orlandofwiw I too think POST is the appropriate verb here.16:19
cdentPUT has very specific semantics whereas POST is just sort of "aw hell, nothing else fits"16:20
cdentso in this case we are saying "I want to deactivate this image"16:20
cdentthat's a server-side state changing operation so thus is POST16:20
cdentwhether it has a body or not is not relevant16:20
dtroyerok…was just reading the rationale, the POST==catch-all bit helps me…move along…16:20
salv-orlandoIn my understanding POST semantics pretty much means "I instruct you, server, to do this for me"16:21
rosmaitaok, let's stick with POST, then?  everyone OK with that?16:21
sigmavirus24Seems that way16:21
sigmavirus24Also we're nearing on 15 minutes on this ;)16:21
rosmaitanext thing would be dtroyer's suggestion of query string instead of resource look16:21
rosmaita(really want to get this settled)16:22
*** jckasper_ has joined #openstack-meeting-316:22
cdentI'm +1 on query string16:22
rosmaitawe discussed & rejected in atlanta, but i can't remember whhy16:22
sigmavirus24cdent: why?16:23
rosmaitamay have rejected query string because it confuses things for rate limiting and the controller, maybe?16:23
cdentbecause it keeps the image being the resource, not some other thing that isn't actually a resource16:23
edleafecd +116:23
edleafecdent: +116:23
* edleafe curses his fat fingers16:24
*** jckasper has quit IRC16:24
dtroyerit also fits with the notion of instructing the server to do something…we do the same with sort, which changes the servers behaviour16:24
* sigmavirus24 wasn't against it, just trying to help everyone understand the reasoning for being +1 on it ;)16:26
elmikoi'm a little confused about the notion of having endpoints that are not resources. my main expose is the o'reilly book on rest design, but they specify that endpoints for actions are ok under some circumstances, is this generally bad rest practice?16:26
*** yamahata has joined #openstack-meeting-316:26
rosmaitaelmiko: depends on who you ask!16:27
elmikoexactly... lol16:27
cdentelmiko in my experience its okay to have a resource which is an action: for example /differ which takes to args16:27
sigmavirus24elmiko: so much of this is subjective IMO16:27
cdentas query parameters16:27
*** bpokorny has joined #openstack-meeting-316:27
cdentbut if you've already got a resource adding an action on it as a yet another resource is a bit funky16:27
sigmavirus24Somethings are more widely agreed upon than others though so you have overlapping opinions16:27
elmikocdent: ok, that clears up the difference16:28
rosmaitai really don't like the query parameter approach, but i can't think of a good argument16:28
elmikoi get it about the opinions, i was just missing the issue about adding on to a resource16:28
sigmavirus24#startvote Is the API WG's recommendation to use POST with a query parameter, e.g., /images/{id}?action=deactivate, instead of a functional API, e.g., /images/{id}/action/deactivate?16:29
openstackBegin voting on: Is the API WG's recommendation to use POST with a query parameter, e.g., /images/{id}?action=deactivate, instead of a functional API, e.g., /images/{id}/action/deactivate? Valid vote options are Yes, No.16:29
openstackVote using '#vote OPTION'. Only your last vote counts.16:29
cdentrosmaita: have you considerd a PATCH with a body of '{"active": false}'16:29
sigmavirus24cdent: yes and that was shot down16:29
ryansbwhy was PATCH downvoted?16:30
ryansbSeems like a fit to me16:30
rosmaitacdent: doesn't really fit the PATCH semantics16:30
rosmaitawell, the key thing is that you can make it look like a PATCH, but it really isn't16:30
dtroyerrosmaita: but does the api caller care?16:31
rosmaitano, but we are thinking of developers here16:31
dtroyerthat's who I am talking about16:31
rosmaitathe problem is that people come and go on projects16:31
sigmavirus24#endvote since we threw a monkey wrench into the discussion16:31
openstackVoted on "Is the API WG's recommendation to use POST with a query parameter, e.g., /images/{id}?action=deactivate, instead of a functional API, e.g., /images/{id}/action/deactivate?" Results are16:31
cdentsorry sigmavirus2416:32
*** carl_baldwin has quit IRC16:32
sigmavirus24No need to apologize cdent. i started it too early ;)16:32
sigmavirus24rosmaita: not to sound like a jerk but, isn't that what specs are for? To document this for future developers on the project?16:32
rosmaitadtroyer: i mean the glance developers ourselves16:32
dtroyerI don't understand why that influences the api design?16:32
edleafePATCH is simply a partial PUT. It really doesn't fit what we're talking about.16:33
dtroyerit seems to me to be exactly what we are talking about…an api caller things this is a simple state change, internally it is totally something else evidently16:33
cdentedleafe: how so? a patch is what you want to do when you want to change part of a resource rather than replace it16:33
cdentwe want to change the resource from active to not active, yes?16:34
dtroyerI suppose my PUT question earlier should have been PATCH…16:34
edleafecdent: exactly. PUT is when you want to replace it16:34
edleafecdent: it's more than just changing one thing on a resource, no?16:35
* edleafe isn't too familiar with glance internals16:35
miguelgrinbergsorry to arrive late to the party, but is the discussion now centered on POST vs. PUT vs. PATCH alone? Are we giving up on RESTfulness?16:35
rosmaitadtroyer: not sure this makes sense, but there are some things glance should be in complete charge of.  i am afraid that if we make it look like you can change image state, someone will put in a change making that happen16:35
*** marios has quit IRC16:36
edleafemiguelgrinberg: quite the opposite16:36
dtroyerbut that is exactly what you are doing…an admin who deactivates an image is overriding glance16:36
sigmavirus24rosmaita: so the thing is that cores will ideally be familiar with the idea that this shouldn't be allowed and block that particular patch16:36
miguelgrinbergedleafe: good, reading now16:36
rosmaitasigmavirus24: one would think so, but i've seen some pretty weird stuff get in16:36
*** marg7175 has quit IRC16:37
rosmaitadtroyer: you're not really overriding glance, you are asking glance to make something happen if possible16:37
cdentrosmaita: how does the structure of the url have any bearing on whether or not people will try to use the functionality?16:37
*** marg7175 has joined #openstack-meeting-316:37
rosmaitacdent: i mean people maintaining the API16:37
dtroyerrosmaita: I simply do not see how deactivating an image is not a state change,16:38
cdentpresumably whatever code path that handles deactivation will be guarded by admin checks that are suitably visible that some subsequent dev will notice?16:38
dtroyerit is called that on line 2816:38
*** tellesnobrega_ has joined #openstack-meeting-316:39
*** tellesnobrega_ has quit IRC16:39
cdentif glance doesn't want to do it, it responds with a 40x (probalby 3)16:39
salv-orlandodtroyer: it is a state change indeed. But such change is triggered by executed action, rather than by processing the request sent to the server.16:39
*** JeanBriceCombebi has quit IRC16:39
salv-orlandoIs this correct?16:40
rosmaitayeah, i guess it's just an intuition i have.  it just seems different to me16:40
rosmaitasalv-orlando: yes16:40
rosmaitathat's a nice way to put it16:40
* jaypipes really despises the /resources/{id}/actions stuff.16:40
*** sarob has joined #openstack-meeting-316:40
dtroyersalv-orlando: right, I don't see much difference though, in the semantic game of not saying state change in the api16:41
elmikojaypipes: what's your feeling on /resources/{id}?actions ?16:41
cdentI think we need vote or punt or we'll be on this the entire meeting.16:41
rosmaitacdent: +116:41
sigmavirus24cdent: agreed but wanted rosmaita to not feel like we were trying to delay this more16:42
jaypipeselmiko: I don't like that either :)16:42
elmikojaypipes: ha!16:42
elmikojaypipes: how to expose controller type actions then?16:42
dtroyerI'd suggest a deferment and clarify the points at question16:42
jaypipeselmiko: I prefer POST /resources/{id}/tasks with a payload describing the task.16:42
sigmavirus24dtroyer: seems fair16:42
elmikojaypipes: got it16:42
miguelgrinbergjaypipes: sorry, but that's still an action, don't like that either16:42
cdentjaypipes-- :)16:43
*** JeanBriceCombebi has joined #openstack-meeting-316:43
sigmavirus24So we should definitely move this to the Mailing LIst16:43
sigmavirus24Can we all be more mindful about responding this time?16:43
sigmavirus24I know rosmaita brought it up there before but got almost no responses16:43
miguelgrinbergeither define a resource that represents that action happening or not and edit that resource, or add state to the main resource to indicate if that action needs to occur (i.e. a change of state in the resource)16:43
sigmavirus24Moving on16:43
sigmavirus24#topic versioning16:44
ryansbyeah, though can folks make sure to use the [API] tag? I missed the mission statement thread for a while because it lacked it16:44
*** openstack changes topic to "versioning (Meeting topic: api wg)"16:44
*** stevedoll has quit IRC16:44
sigmavirus24Did someone other than etoews add this?16:44
jaypipesmiguelgrinberg: a task is an object. an action is an action.16:45
*** sarob has quit IRC16:45
rosmaitajaypipes: +116:45
miguelgrinbergjaypipes: we can agree to disagree16:45
sigmavirus24#action sigmavirus24 to carry this topic forward to next week16:45
jaypipes:) sure16:45
*** yamahata has quit IRC16:45
sigmavirus24#topic previous meeting action items16:46
*** openstack changes topic to "previous meeting action items (Meeting topic: api wg)"16:46
*** yamahata has joined #openstack-meeting-316:46
sigmavirus24Seems all of the previous action items were taken care of.16:46
sigmavirus24#topic guidelines16:47
*** openstack changes topic to "guidelines (Meeting topic: api wg)"16:47
sigmavirus24I think we need jaypipes or someone else to abandon
sigmavirus24We should also try to get more cross-project attention on
jaypipessigmavirus24: done.16:48
sigmavirus24Thanks jaypipes16:48
sigmavirus24kaufer: are you around?16:48
sigmavirus24Mind if I assign you to grab more eyes on that?16:48
kauferI'd like to get jaypipes thoughts on
sigmavirus24#action kaufer to get some more input from other project members on
miguelgrinbergkaufer: I would just add that this is necessary only when getting the count can be seen as affecting performance. If not, then APIs are free to always return the count.16:49
jaypipeskaufer: reviewed.16:49
*** JeanBriceCombebi has quit IRC16:50
sigmavirus24Anything else from,n,z we want to discuss?16:50
miguelgrinbergso there is a discussion on tags in the Heat channel, I'm thinking in expanding the metadata guideline to include also tags16:51
*** ChuckC_ has quit IRC16:51
*** JeanBriceCombebi has joined #openstack-meeting-316:51
miguelgrinbergor would you guys prefer a separate doc?16:51
sigmavirus24miguelgrinberg: perhaps it'd be better to make that dependent since metadata guidelines are already seemingly controversial16:51
sigmavirus24#info metadata guideline
*** ChuckC_ has joined #openstack-meeting-316:51
*** ChuckC_ is now known as ChuckC16:51
jaypipesmiguelgrinberg: would be great to include the server tagging API (from Nova, based heavily on Glance's) in that discussion16:51
cdentmiguelgrinberg: I'd choose separate16:51
miguelgrinbergjaypipes: that's what we were looking at for heat, yes16:52
*** tellesnobrega_ has joined #openstack-meeting-316:52
jaypipesrock on.16:52
miguelgrinbergokay, I'll do a separate doc on tagging then16:52
sigmavirus24#action miguelgrinberg to make a guideline for tagging16:53
sigmavirus24Other guidelines we want to discuss or should we move on to APIImpact?16:53
ryansbmiguelgrinberg: if you'd like a hand I'm happy to help w/ that16:53
miguelgrinbergryansb: sure, I'll find you when I have a first draft16:53
*** MaxV has quit IRC16:54
sigmavirus24No one seems to object to moving on, so16:54
sigmavirus24#topic APIImpact16:54
*** openstack changes topic to "APIImpact (Meeting topic: api wg)"16:54
sigmavirus24Anything anyone wants to point out here?16:55
*** evgenyf has quit IRC16:55
cdentguess not?16:57
*** bpokorny_ has joined #openstack-meeting-316:58
ryansbno, looks like most of those are being well-handled by the project team16:59
miguelgrinbergthe heat tags spec is missing, just added a note for the author to add the flag16:59
ryansbgood catch16:59
*** bpokorny has quit IRC17:00
*** baoli_ has quit IRC17:00
sigmavirus24And we're over time17:02
cdenttimes up?17:02
sigmavirus24Sorry about that17:02
sigmavirus24Got distracted17:02
*** openstack changes topic to "OpenStack Meetings ||"17:02
openstackMeeting ended Thu Feb 12 17:02:13 2015 UTC.  Information about MeetBot at . (v 0.1.4)17:02
openstackMinutes (text):
sigmavirus24Thanks everyone17:02
elmikothanks sigmavirus2417:02
sigmavirus24Sorry to the next meeting17:02
*** ryansb has left #openstack-meeting-317:02
*** elmiko has left #openstack-meeting-317:04
*** mbgalt has quit IRC17:04
*** cdent has left #openstack-meeting-317:05
*** dtroyer has left #openstack-meeting-317:05
*** Nikolay_St has joined #openstack-meeting-317:06
*** jcoufal_ has quit IRC17:07
*** SridharRamaswamy has joined #openstack-meeting-317:10
*** opsvision has quit IRC17:11
*** coolsvap is now known as coolsvap_17:12
*** fischerw has joined #openstack-meeting-317:13
*** SridharRamaswam1 has joined #openstack-meeting-317:13
*** bpokorny_ has quit IRC17:13
*** SridharRamaswamy has quit IRC17:14
*** carl_baldwin has joined #openstack-meeting-317:15
*** opsvision has joined #openstack-meeting-317:15
*** iovadia has quit IRC17:19
*** stevedoll has joined #openstack-meeting-317:22
*** megm has joined #openstack-meeting-317:22
*** megm_ has quit IRC17:23
*** banix has quit IRC17:25
*** Nikolay_St has quit IRC17:26
*** salv-orlando has quit IRC17:29
*** armax has joined #openstack-meeting-317:29
*** salv-orlando has joined #openstack-meeting-317:29
*** devvesa has quit IRC17:30
*** clu_ has quit IRC17:36
*** matrohon has quit IRC17:38
*** ChuckC has quit IRC17:42
*** emagana has joined #openstack-meeting-317:42
*** ChuckC has joined #openstack-meeting-317:42
*** bknudson has quit IRC17:47
*** alexsyip has joined #openstack-meeting-317:47
*** Nikolay_St has joined #openstack-meeting-317:48
*** safchain has quit IRC17:50
*** sahid has quit IRC17:51
*** SumitNaiksatam has joined #openstack-meeting-317:52
*** marun has quit IRC17:52
*** baoli has joined #openstack-meeting-317:53
*** rkukura has joined #openstack-meeting-317:53
*** melwitt has joined #openstack-meeting-317:53
*** tellesnobrega_ has quit IRC17:53
*** banix has joined #openstack-meeting-317:54
*** Nikolay_St has quit IRC17:55
*** coolsvap_ is now known as coolsvap17:55
*** mageshgv has joined #openstack-meeting-317:56
*** Nikolay_St has joined #openstack-meeting-317:56
*** cbader has joined #openstack-meeting-317:57
*** baoli has quit IRC17:57
*** tellesnobrega_ has joined #openstack-meeting-317:58
*** mwang2 has joined #openstack-meeting-317:59
SumitNaiksatamrkukura: banix mageshgv: hi18:00
YiHi Sumit18:00
*** Youcef has joined #openstack-meeting-318:00
mageshgvSumitNaiksatam: hi18:00
SumitNaiksatamYi: hi good to see you18:00
SumitNaiksatamlets get started18:00
SumitNaiksatam#startmeeting networking_policy18:01
openstackMeeting started Thu Feb 12 18:01:04 2015 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: networking_policy)"18:01
openstackThe meeting name has been set to 'networking_policy'18:01
SumitNaiksatam#info agenda
SumitNaiksatam#info Kilo-1 for GBP is Feb 16th18:02
*** KrishnaK has joined #openstack-meeting-318:02
SumitNaiksatamKrishnaK: banix: hi18:02
SumitNaiksatam#topic Bugs18:02
*** openstack changes topic to "Bugs (Meeting topic: networking_policy)"18:02
*** kaufer has left #openstack-meeting-318:02
KrishnaKhi SumitNaiksatam, banix18:02
SumitNaiksatamper last meeting, i have posted links to the k-1 bugs18:03
SumitNaiksatamwe still have quite a few pending (and some new ones are showing up)18:03
SumitNaiksatamlast week we took some time to discuss: #link
openstackLaunchpad bug 1414139 in Group Based Policy "RMD assumes implicit driver running" [Medium,New] - Assigned to Ivar Lazzaro (mmaleckk)18:03
SumitNaiksatamnice, bot runs now ;-)18:04
SumitNaiksatami believe Ivar is not here18:04
*** lsmola has quit IRC18:04
SumitNaiksatami am not sure if he had a chance to make progress on this18:04
SumitNaiksatami know he was focussed on fixing some issues in the external connectivity model18:05
SumitNaiksatamany other bugs that we want to discuss here? any blockers?18:05
*** ivar-lazzaro has joined #openstack-meeting-318:06
SumitNaiksatamrkukura: you were mentioning that you had some sqlalchemy issues?18:06
*** Nikolay_St has quit IRC18:06
rkukuraSumitNaiksatam: is high and for k-1, but my comment recommends postponing until later18:06
openstackLaunchpad bug 1383947 in Group Based Policy "subnet mapping broken with overlapping ips" [High,Confirmed] - Assigned to Robert Kukura (rkukura)18:06
SumitNaiksatamrkukura: yes, can you change the milestone to the relevant one?18:06
SumitNaiksatamivar-lazzaro: hi18:07
*** Nikolay_St has joined #openstack-meeting-318:07
rkukuraSumitNaiksatam: OK18:07
SumitNaiksatamivar-lazzaro: we just went past the “"RMD assumes implicit driver running" bug18:07
*** ivar-lazzaro has quit IRC18:07
SumitNaiksatamivar-lazzaro: anything to report on that?18:07
SumitNaiksatamoops, seems to have lost him18:07
*** ivar-lazzaro has joined #openstack-meeting-318:08
*** sergef has quit IRC18:08
ivar-lazzaroSumitNaiksatam: do'h18:08
SumitNaiksatamivar-lazzaro: were you able to see the backscroll?18:09
SumitNaiksatamwas just checking if you wanted to dicuss "RMD assumes implicit driver running" bug?18:10
*** susaant has joined #openstack-meeting-318:10
*** salv-orlando has quit IRC18:10
ivar-lazzaroSumitNaiksatam: I have no progress on that side, I was wondering if we should adopt the "validator" phase solution or if we should wait after the refactor instead18:10
*** salv-orlando has joined #openstack-meeting-318:10
SumitNaiksatamivar-lazzaro: can quickly summarize “validator phase” solution?18:11
ivar-lazzaroSumitNaiksatam: of course if we plan on keeping the current ML2 architecture as is the order really doesn't matter18:11
SumitNaiksatamivar-lazzaro: i would say it depends on how critical this issue is18:12
SumitNaiksatamcurrently its marked as medium18:12
*** salv-orl_ has joined #openstack-meeting-318:12
SumitNaiksatamif so we can potentially wait18:12
*** salv-orl_ has quit IRC18:12
SumitNaiksatambut if its actually higher priority, we should fix the issue before refactor (and bump up the priority of this bug)18:12
*** salv-orl_ has joined #openstack-meeting-318:13
SumitNaiksatami dont anticipate the first phase of the refactor to do away with current ML2-like arch18:13
*** bknudson has joined #openstack-meeting-318:13
*** dboik_ has quit IRC18:13
SumitNaiksatami think we will need more discussion on that, and its not preferable to hold up the other refactor effort for that discussion18:13
rkukuraIs there a requirement to run without IPD?18:14
rkukuraI mean a short-term requirement. I agree we shouid fix this eventually.18:14
SumitNaiksatamrkukura: i believe the suggestion is that the RMD should be self contained18:14
SumitNaiksatamrkukura: in that it doesnt assume resource dependencies exist18:15
SumitNaiksatamrkukura: i am not aware of the immediate short term requirement, perhaps ivar-lazzaro has run into an issue on account of this?18:15
*** mwagner_lap has quit IRC18:16
*** pkoniszewski has joined #openstack-meeting-318:16
*** s3wong has joined #openstack-meeting-318:16
s3wongsorry, late18:16
SumitNaiksatamnot sure if ivar-lazzaro is still around or dropped off18:16
SumitNaiksatams3wong: hi, np18:17
SumitNaiksatamas I mentioned earlier we are also catching some issues during the external connectivity testing18:17
SumitNaiksatamthe issues have not been filed yet, but will do so soon18:17
SumitNaiksatamsome of them might be backports (fyi - in case you are planning to use the external connectivity model)18:18
*** Nikolay_St has quit IRC18:18
*** sergef has joined #openstack-meeting-318:18
SumitNaiksatammageshgv: any service-chain related bugs you need to discuss here?18:18
*** baoli has joined #openstack-meeting-318:18
SumitNaiksatamoh, i find a few and have filed them, and have a fix for some of them18:19
*** johnthetubaguy is now known as zz_johnthetubagu18:19
mageshgvSumitNaiksatam: No. I havent made much progress on the current bugs, saw a few new ones and working on those at present18:19
*** Nikolay_St has joined #openstack-meeting-318:19
SumitNaiksatami was having issues with the one-convergence tests18:19
SumitNaiksatammageshgv: i will sync with you offline18:19
mageshgvSumitNaiksatam: Fine, we can discuss offline18:19
SumitNaiksatammageshgv: thanks18:20
ivar-lazzarowe can add a pre-processing phase (or validator) *before* the DB transaction starts18:20
*** salv-orlando has quit IRC18:20
SumitNaiksatamjust a reminder folks, K-1 is feb-16th18:20
ivar-lazzarotherefore before the pre-commit18:20
ivar-lazzaroin which the implicit mapping can do the object creation18:20
ivar-lazzaroso that the pre-commit phase will already be seeing the full chain of objects produced by a given call18:20
ivar-lazzaroand can validate properly18:20
ivar-lazzaroThe issue has a workaround (always run the Implicit Policy Driver)18:20
ivar-lazzaroI think that's fair18:20
*** dboik has joined #openstack-meeting-318:20
*** dboik has quit IRC18:20
*** dboik has joined #openstack-meeting-318:20
SumitNaiksatamivar-lazzaro: okay18:20
*** clu_ has joined #openstack-meeting-318:21
ivar-lazzarook I got back after a pretty bad connection time :)18:21
SumitNaiksatamregarding the deadline - if an issue is assigned to you and is targeted for k-1, please respond to that launchpad with an update18:21
SumitNaiksatamKrishnaK: thanks for fixing the bug in your plate, it it merged now?18:21
KrishnaKSumitNaiksatam: Not yet merged. Need review of this bug:
*** baoli has quit IRC18:22
SumitNaiksatamKrishnaK: hi cores, can you please take a look at ^^^ #link
SumitNaiksatampretty straightforward18:23
rkukuraI’ll review that today18:23
SumitNaiksatamKrishnaK: you had another one in your plate i believe?18:24
*** rosmaita has left #openstack-meeting-318:24
*** SridharRamaswam1 has quit IRC18:24
KrishnaKrkukura. Thx.18:24
*** DenisEgorenko has left #openstack-meeting-318:24
KrishnaKSumitNaiksatam: yes. I'll look at other bug soon.18:24
SumitNaiksatamKrishnaK: thanks18:24
SumitNaiksatamin general, if anyone has a pending review and is not getting reviewer attention please yell! :-)18:24
SumitNaiksatamor get in touch with me18:25
SumitNaiksatamwe also have the #openstack-gbp channel18:25
SumitNaiksatamand a bunch of the cores are there on that channel18:25
KrishnaKSumitNaiksatam: Thx for that info.18:25
SumitNaiksatam(i would request all cores to log in whenever convenient)18:25
SumitNaiksatamKrishnaK: not specifically target at you, i know you have been trying your best to get attention :-)18:26
*** Nikolay_St has quit IRC18:26
SumitNaiksatamokay if nothing else on the pending bugs, lets move on18:26
SumitNaiksatam#topic “Re-factor Group Based Policy with Neutron RESTful APIs”18:26
*** openstack changes topic to "“Re-factor Group Based Policy with Neutron RESTful APIs” (Meeting topic: networking_policy)"18:26
*** Nikolay_St has joined #openstack-meeting-318:26
SumitNaiksatami believe Yi  is here18:26
Yiyes, I am here18:26
YiI was able to use the RESTful API to create network18:27
SumitNaiksatami responded to the spec yesterday (had some very minor comments, mostly in response to Yi’s offline questions)18:27
SumitNaiksatamYi: thats nice progress!18:27
SumitNaiksatamanyone else got a chance to look at the above spec18:27
SumitNaiksatamits really pretty small, so i would appreciate if cores can take a look at it at the earliest18:28
SumitNaiksatamlast week we had an action to provide immediate review comments on this one18:28
SumitNaiksatami believe Yi and yapeng are kind of waiting on a “thumbs-up" for this18:28
ivar-lazzarowill do today18:28
SumitNaiksatamivar-lazzaro: thanks!18:29
Yiwe appreciate it!18:29
*** emagana has quit IRC18:29
SumitNaiksatamYi: its good you have the implementation going18:29
YiThat's what I was trying to do.18:29
SumitNaiksatamYi: please dont hesitate to bug the team if you run into any issues18:29
*** emagana has joined #openstack-meeting-318:29
Yiand I need to poll your opinion actually18:30
SumitNaiksatamas i mentioned before #openstack-gbp can also be a good resource to get immediate attention (and emails will also work)18:30
*** emagana has quit IRC18:30
SumitNaiksatamYi: yes please18:30
Yiregarding the location of the module18:30
SumitNaiksatamah okay18:30
*** emagana has joined #openstack-meeting-318:30
SumitNaiksatammy suggestion was to use the way nova does it18:31
Yiwhich would be gbpservice/network/neutronv218:31
SumitNaiksatamyeah in our case18:31
*** tellesnobrega_ has quit IRC18:31
SumitNaiksatamif others have differing opinion please comment on the review at the earliest18:31
SumitNaiksatamand/or here18:31
*** annegent_ has joined #openstack-meeting-318:32
*** dboik has quit IRC18:32
SumitNaiksatamokay silence is golden - Yi so you can use this module path for now :-)18:32
SumitNaiksatami dont hear objections18:33
Yigood :-)18:33
SumitNaiksatamYi: any other issues you wanted to discuss?18:33
SumitNaiksatami also mentioned about the neutron client version18:33
SumitNaiksatamin the review18:33
YiI will check it out18:33
SumitNaiksatamour other gbp projects are using 2.3.918:33
SumitNaiksatamwhereas the latest in 2.3.1018:34
SumitNaiksatamuntil we move the other projects to 2.3.10, we should use 2.3.9 here as well18:34
SumitNaiksatamthe move to 2.3.10 has been targeted for k-218:34
SumitNaiksatamso go with 2.3.918:34
SumitNaiksatami believe you will have to add this to the requirements file18:34
Yimake sense18:34
Yiwill do18:35
SumitNaiksatamYi: thanks18:35
*** jpomero has quit IRC18:35
SumitNaiksatamYi: anything else on this?18:35
SumitNaiksatamyapeng not around today?18:35
YiOne thing I do notice is we have dependency on plugin context18:35
*** tellesnobrega_ has joined #openstack-meeting-318:35
*** jaypipes has quit IRC18:36
Yiyapeng is in China this week, I believe18:36
SumitNaiksatamYi: ah18:36
SumitNaiksatamYi: what about the plugin context, is that creating an issue?18:36
Yinot an issue right now, as I can use plugin context directly18:36
Yibut I'd assume later when we have gbp independent, we should not reply on the plugin context?18:37
SumitNaiksatamYi: i am not fully understanding, but lets take that offline18:37
Yii.e., to keep the auth_token and other attributes in the context instead of plugin context?18:37
Yisure, let's discuss it offline18:38
SumitNaiksatamrkukura: can i request you to provide Yi some guidance on this if required?18:38
*** dboik has joined #openstack-meeting-318:38
rkukuraYi: I’d think we’d replace the neutron plugin context with something similar. Sure.18:38
SumitNaiksatamrkukura: thanks!18:38
Yirkukura: I think that will be fine in the future18:39
SumitNaiksatamYi: thanks for the update18:39
SumitNaiksatamwant to give some time to the next topic18:39
SumitNaiksatam#topic “Floating IP Support”18:39
*** openstack changes topic to "“Floating IP Support” (Meeting topic: networking_policy)"18:39
SumitNaiksatammageshgv: over to you18:40
*** baoli has joined #openstack-meeting-318:40
SumitNaiksatami believe you have made some progress?18:40
*** Nikolay_St has quit IRC18:40
mageshgvSumitNaiksatam: Yes, I am stuck somewhere now though. Will expand on this design18:40
*** Nikolay_St has joined #openstack-meeting-318:41
mageshgvFrom an api perspective, the idea was to use Network service policy with type ip_pool and value external_subnet to indicate all PTs should get a FIP.18:41
SumitNaiksatammageshgv: okay :-)18:41
mageshgvAnother alternative user friendly api option is to extend PTG with a parameter to indicate that all PTs on this PTG should get a floating IP associated.18:41
SumitNaiksatammageshgv: yes, as i recalled from prior discussions in the original GBP spec18:41
SumitNaiksatami meant yes for the earlie alternative18:42
rkukuramageshgv: Can we just infer based on the policies whether a PTG needs FIPs?18:42
SumitNaiksatamrkukura: that was idea in encoding that in the Network Service Policy18:42
rkukuraI don’t think FIPs should be part of the “intent”.18:42
mageshgvrkukura: right, that is why we were thinking to use Network Service Policy18:43
SumitNaiksatamrkukura: i think i agree with that18:43
rkukuraI’m not sure how we represent external networks, but if there is a policy allowing incoming connections, a FIP is needed. If not, it isn’t.18:43
SumitNaiksatammageshgv: perhaps the alternatives should be captured in the design (in the alternative section)18:43
mageshgvSumitNaiksatam: okay, will add that too18:43
rkukura“external” here could also mean a different L3P from the same tenant or a different tenant, as well as outside-the-cloud18:43
ivar-lazzaromageshgv, SumitNaiksatam, rkukura: what about the nat-pool object?18:44
ivar-lazzarowhich already exists from the external connectivity blueprint18:44
rkukuraivar-lazzaro: I need to re-read that BP (and code)18:45
SumitNaiksatammageshgv: perhaps good to post the spec at the earliest18:46
SumitNaiksatamso that people can relate to different parts of the model18:46
ivar-lazzarothe idea of the NAT pool was to provide a pool of FIPs that all the PT from a given external-segment would be assigned with18:46
mageshgvivar-lazzaro: you are correct, we have to use the nat pool to achieve this, but I havent modelled a proper relation with this nat pool yet18:46
*** bpokorny has joined #openstack-meeting-318:47
ivar-lazzaromageshgv: keep in mind that the nat pool is not used today by any driver. So feel free to remove/change it if you think of a better solution18:47
SumitNaiksatamivar-lazzaro: my understanding is that the trigger comes from the Network Service Policy (whether to configure FIP or not)18:47
rkukuraivar-lazzaro: I also agree a NAT pool is needed by the PTG, but just was thinking whether to allocate a FIP could be inferred.18:47
ivar-lazzaroSumitNaiksatam: why from NSP? This should be a property of the L3Policy IMHO18:48
mageshgvrkukura: We need some way of way of expressing this floating ip policy and also like it to a nat pool18:48
SumitNaiksatamthere are two steps, first whether to use the FIP or not (which can be characterized as the “intent”), and the second is where to pull the FIPs from, if used18:48
ivar-lazzaroSumitNaiksatam: (therefore a property of the external segment)18:49
*** SridharRamaswamy has joined #openstack-meeting-318:49
rkukuraSumitNaiksatam: makes sense, ivar-lazzaro: L3P seems to make sense18:49
SumitNaiksatamivar-lazzaro: because, FIP is achieved using NAT, which can be thought of as a service18:50
ivar-lazzaroOriginally the simple idea was: Any PT created on a EPG which external connectivity (see external-segment) will be granted a FIP from the nat pool18:50
SumitNaiksatamand allows the choice of explicit versus implicit NAT services to achieve it18:50
ivar-lazzaroSumitNaiksatam: FIP could just be a routable address, not necessarily implemented using NAT18:51
SumitNaiksatamivar-lazzaro: why should that be the case?18:51
*** Longgeek has quit IRC18:51
ivar-lazzaroSumitNaiksatam:  (see IPv6)18:51
SumitNaiksatamivar-lazzaro: yeah, but it could also be a NAT, which it commonly is in IPv418:51
Yiivar-lazzaro: I agree with rkukura, NAT pool and FIP pool may not necessarily by related18:51
ivar-lazzaroSumitNaiksatam: true, but we have to catch the intent18:52
*** Longgeek has joined #openstack-meeting-318:52
SumitNaiksatamivar-lazzaro: external connectivity is for going from the inside to the outside18:52
mageshgvivar-lazzaro: If I understand it correctly, in the current model, external segment by itself represents a PTG. Is that not the case ?18:52
ivar-lazzarowe don't really care wether it's a service or not18:52
SumitNaiksatamso does not necessarily need a FIP18:52
rkukuraIdeally, intent would not be different for IPv4 vs. IPv618:52
SumitNaiksatamivar-lazzaro: it needs a NAT pool, not a FIP18:52
SumitNaiksatamivar-lazzaro: a FIP can also be assigned from that pool18:52
ivar-lazzaromageshgv: no, external policy is a PTG. External Segment is an extension of the L3P basically18:53
SumitNaiksatamrkukura: true18:53
ivar-lazzarorkukura: exactly18:53
mageshgvivar-lazzaro: my bad got mixed up with the two resources18:53
SumitNaiksatamrkukura: hence the NSP model which tries to generalize that18:53
ivar-lazzaromaybe nat-pool is not the best choice in term of naming18:53
ivar-lazzaromageshgv: ES describes how a L3P can reach the external world18:53
SumitNaiksatamokay, we have 6 mins remaining, and at least one more item to cover18:54
*** dboik has quit IRC18:54
SumitNaiksatami belive we need to see the spec and comment in the review18:54
SumitNaiksatammageshgv: what is your estimate for posting the spec18:55
mageshgvI should be able to post it by this weekend18:55
*** dboik has joined #openstack-meeting-318:55
SumitNaiksatammageshgv: ok thanks, the earlier the better :-)18:55
*** Piet has quit IRC18:55
mageshgvSumitNaiksatam: sure18:55
ivar-lazzaroThe point is to understand if we want to assign FIPs per L3Policy or per PTG18:55
SumitNaiksatamsince this is currently targeted for K-1 :-)18:55
ivar-lazzarowe could also use labels eventually for a greater granularity18:55
SumitNaiksatammageshgv: thanks for the update18:56
SumitNaiksatam#topic Taskflow investigation18:56
*** openstack changes topic to "Taskflow investigation (Meeting topic: networking_policy)"18:56
SumitNaiksatamrkukura: over to you18:56
*** Longgeek has quit IRC18:56
rkukuraSumitNaiksatam: I started looking at, which the start of a PoC for incorporating TaskFlow into ML2.18:57
rkukuraBut it needs a ton more work to really make any sense.18:57
*** coolsvap is now known as coolsvap_18:57
SumitNaiksatamrkukura: okay, so this patch is not complete?18:57
rkukuraI’d like to also look at how other projects are using TaskFlow.18:57
rkukuraSumitNaiksatam: Its a WiP of a PoC18:58
SumitNaiksatamrkukura: okay18:58
SumitNaiksatamrkukura: so is taskflow targeted in Neutron for Kilo?18:58
rkukuraI’d like to see how we really should combine the concepts of driver and task18:58
rkukuraSumitNaiksatam: No, the ML2 TaskFlow is investigation going into Liberty planning18:59
SumitNaiksatamrkukura: ah ok18:59
rkukuraNo decisions have been made about it. Just working towards a BP.18:59
rkukuraThat’s all I have right now, but will continue.18:59
SumitNaiksatamso perhaps that tells that the scope is large19:00
SumitNaiksatamrkukura: thanks for that update19:00
SumitNaiksatam#topic Open Discussion19:00
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"19:00
SumitNaiksatamwe are at the hour19:00
SumitNaiksatamany parting comments, or anything that we missed?19:00
SumitNaiksatamelse over to #openstack-gbp19:00
rkukuraOne note - The RDO GBP instructions at have been updated.19:00
SumitNaiksatamrkukura: awesome!19:01
SumitNaiksatamwe skipped the packaging standing item19:01
SumitNaiksatamall right, thanks everyone19:01
*** openstack changes topic to "OpenStack Meetings ||"19:01
openstackMeeting ended Thu Feb 12 19:01:33 2015 UTC.  Information about MeetBot at . (v 0.1.4)19:01
openstackMinutes (text):
rkukuraI’d really encourage others to try the RDO packages on Fedora, RHEL, or CentOS19:01
*** susaant has quit IRC19:01
*** mageshgv has quit IRC19:01
*** rkukura has left #openstack-meeting-319:02
*** wojdev has joined #openstack-meeting-319:02
*** Yi has left #openstack-meeting-319:02
*** Godfath3r has joined #openstack-meeting-319:02
*** dboik has quit IRC19:05
*** dboik has joined #openstack-meeting-319:06
*** KrishnaK has quit IRC19:09
*** alexpilotti has quit IRC19:11
*** banix has quit IRC19:12
*** banix has joined #openstack-meeting-319:14
*** baoli has quit IRC19:15
*** mwagner_lap has joined #openstack-meeting-319:18
*** emagana has quit IRC19:26
*** emagana has joined #openstack-meeting-319:26
*** GavinPratt has joined #openstack-meeting-319:27
*** emagana has quit IRC19:31
*** ttrifonov is now known as zz_ttrifonov19:33
*** Sukhdev has joined #openstack-meeting-319:37
*** stevedoll has quit IRC19:39
*** emagana has joined #openstack-meeting-319:44
*** sarob has joined #openstack-meeting-319:46
*** JeanBriceCombebi has quit IRC19:46
*** emagana has quit IRC19:49
*** emagana has joined #openstack-meeting-319:49
*** Longgeek has joined #openstack-meeting-319:53
*** emagana has quit IRC19:54
*** egallen has quit IRC19:54
*** wojdev has quit IRC19:54
*** thangp has quit IRC19:58
*** Longgeek has quit IRC20:02
*** jrist has quit IRC20:02
*** Godfath3r has quit IRC20:04
*** briancurtin has quit IRC20:07
*** zhiyan has quit IRC20:08
*** ctracey has quit IRC20:08
*** jraim has quit IRC20:09
*** victor_lowther has quit IRC20:09
*** emagana has joined #openstack-meeting-320:09
*** ameade has quit IRC20:10
*** radek has quit IRC20:12
*** s3wong has quit IRC20:12
*** Youcef has quit IRC20:13
*** s3wong has joined #openstack-meeting-320:14
*** jraim has joined #openstack-meeting-320:15
*** jrist has joined #openstack-meeting-320:15
*** ctracey has joined #openstack-meeting-320:16
*** victor_lowther has joined #openstack-meeting-320:17
*** briancurtin has joined #openstack-meeting-320:17
*** zhiyan has joined #openstack-meeting-320:18
*** ameade has joined #openstack-meeting-320:18
*** mwang2 has quit IRC20:22
*** r1chardj0n3s_afk is now known as r1chardj0n3s20:22
*** r1chardj0n3s has left #openstack-meeting-320:23
*** jrist has quit IRC20:24
*** VW_ has quit IRC20:29
*** annegent_ has quit IRC20:32
*** jtomasek has quit IRC20:35
*** jrist has joined #openstack-meeting-320:37
*** salv-orlando has joined #openstack-meeting-320:38
*** tellesnobrega_ has quit IRC20:41
*** Yi has joined #openstack-meeting-320:41
*** salv-orl_ has quit IRC20:41
*** markvoelker has joined #openstack-meeting-320:41
*** qwebirc46669 has joined #openstack-meeting-320:44
*** qwebirc46669 has quit IRC20:44
*** sarob_ has joined #openstack-meeting-320:44
*** sarob_ has quit IRC20:45
*** yamahata has quit IRC20:46
*** qwebirc51741 has joined #openstack-meeting-320:49
*** s3wong has quit IRC20:49
*** qwebirc51741 has quit IRC20:50
*** s3wong has joined #openstack-meeting-320:53
*** alexsyip has quit IRC20:57
*** alexsyip_ has joined #openstack-meeting-320:57
*** annegent_ has joined #openstack-meeting-320:58
*** clu_ has quit IRC20:59
*** mwang2 has joined #openstack-meeting-320:59
*** Shamail has joined #openstack-meeting-321:00
*** clouddon has joined #openstack-meeting-321:02
*** jckasper has joined #openstack-meeting-321:02
clouddonHello, anyone around for HA guide updates?21:03
Shamailhi clouddon21:03
megmHi all21:03
clouddonhi there! Matt just pinged that he can't get on IRC21:04
*** lblanchard has quit IRC21:04
clouddonone of us needs to lead.21:04
ShamailAll yours :)21:04
clouddonthanks :)21:04
*** jckasper_ has quit IRC21:05
clouddonany status updates from last week? Matt shared his first cut on install steps :
*** baoli has joined #openstack-meeting-321:06
ShamailNo status updates on my action item (review ops guide for recovery from failure information)21:07
ShamailI was distracted by talk submissions but I should have an update by next week21:07
*** jckasper has quit IRC21:07
clouddonno problem.21:07
*** jckasper has joined #openstack-meeting-321:07
clouddonNick/ Meg - do you have any updates?21:08
megmI'm looking at Matt's etherpad for the first time -- so is this the Install Guide or HA specific?21:08
megmI have no updates -- I don't know where Nick is21:08
ShamailIt seems to be the location of the install guides21:08
openstackclouddon: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'21:09
clouddon#startmeeting ha-guide21:09
openstackMeeting started Thu Feb 12 21:09:17 2015 UTC and is due to finish in 60 minutes.  The chair is clouddon. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:09
ShamailMatt's AI was to review them to see if there were any steps mentioned in the install guides that might conflict or support HA21:09
*** openstack changes topic to " (Meeting topic: ha-guide)"21:09
openstackThe meeting name has been set to 'ha_guide'21:09
clouddonsorry for missing that command.21:09
*** jckasper_ has joined #openstack-meeting-321:09
Shamaile.g. areas where we might be able to recommend HA guidelines or areas where the install guide would prevent the setup of HA in the future21:09
ShamailDoes the etherpad make sense in that context?21:10
clouddonfor meeting note purposes, here is the link again:
ShamailIt looks as though he has started, but still a WIP21:10
megmYes, the HA ramifications are not clear to me21:11
clouddonyes,thats what he mentioned. First pass21:11
*** baoli has quit IRC21:11
megmBut a good working base on which to do that analysis21:11
*** baoli has joined #openstack-meeting-321:11
clouddonit appears that we are not on same page regarding this. If I remember correctly, we were planning on getting together to hash this out21:12
*** jckasper has quit IRC21:12
clouddonMeg, can you take an action to schedule a hangout please?21:12
megmSure, I can schedule a hangout -- what is a good time?21:13
megmAre participants all in US?21:14
ShamailI believe so21:14
clouddonI'm at PST, Shamail in EST. I believe Matt in CST?21:14
megmI'm in PST, Nick is in EST21:15
clouddonok. all in the US then. 10 am PST?21:15
ShamailWhich day?21:16
megmDoes uesday the 17th work?21:17
*** banix has quit IRC21:17
ShamailThat should work for me21:18
clouddonworks. If this doesn't seem a good one or we can't confirm in the 2 mnts, Meg, can you please send a doodle request to all of us and pick from there. Matt is also not online, so can't really talk for him21:18
megmOkay -- I need to learn how to do all these things -- I'll get instructions from Nick21:19
*** mwang2_ has joined #openstack-meeting-321:19
megmWhat about the existing HA Guide?  How about if I analyze that and match it to what is in the Install Guide?21:19
clouddonAs of now, Tuesday 10 am PST looks for Shamail, Sriram and Meg. Rt? Nick is not online now?21:20
megmIt's a small start21:20
megmNick isn't responding on Skype or email -- I'll get with him later21:20
ShamailI think that's a good idea megm, this way we will know at least some starting state of the install, HA, and ops guides21:21
clouddon#action megm to schedule Google Hangout to hashout HA Guide/ Install Guide21:21
Shamailfrom a HA enablement perspective21:21
clouddonok.can we move to next item?21:22
*** mwang2 has quit IRC21:22
clouddon#info Shamail, Gerd and Sriram submitted a summit talk on HA best practices/ Use case example21:23
*** banix has joined #openstack-meeting-321:23
clouddoni don't have anything else. Does anyone have anything else?21:24
Shamailclouddon: nothing at the moment, I hope to have an update on the ops guide by next meeting.21:24
*** megm_ has joined #openstack-meeting-321:25
clouddonthanks everyone.21:25
Shamailalright, take care all!21:25
*** megm has quit IRC21:25
*** openstack changes topic to "OpenStack Meetings ||"21:25
openstackMeeting ended Thu Feb 12 21:25:51 2015 UTC.  Information about MeetBot at . (v 0.1.4)21:25
openstackMinutes (text):
*** Shamail has quit IRC21:26
*** clu_ has joined #openstack-meeting-321:28
*** clouddon has quit IRC21:29
*** emagana has quit IRC21:30
*** emagana has joined #openstack-meeting-321:31
*** emagana has quit IRC21:34
*** emagana has joined #openstack-meeting-321:35
*** baoli has quit IRC21:37
*** Sukhdev has quit IRC21:37
*** baoli has joined #openstack-meeting-321:37
*** Piet has joined #openstack-meeting-321:42
*** jrist has quit IRC21:44
*** Yi has quit IRC21:46
*** Yi has joined #openstack-meeting-321:46
*** bpokorny_ has joined #openstack-meeting-321:46
*** Longgeek has joined #openstack-meeting-321:47
*** sergef has quit IRC21:49
*** bpokorny has quit IRC21:49
*** jaypipes has joined #openstack-meeting-321:49
*** Piet has quit IRC21:49
*** sigmavirus24 is now known as sigmavirus24_awa21:55
*** banix has quit IRC21:56
*** jrist has joined #openstack-meeting-321:57
*** melwitt has left #openstack-meeting-321:59
*** emagana has quit IRC22:01
*** pkoniszewski has quit IRC22:01
*** s3wong has quit IRC22:02
*** s3wong has joined #openstack-meeting-322:08
*** emagana has joined #openstack-meeting-322:12
*** annegent_ has quit IRC22:13
*** annegent_ has joined #openstack-meeting-322:15
*** VW_ has joined #openstack-meeting-322:15
*** salv-orlando has quit IRC22:19
*** s3wong has quit IRC22:19
*** s3wong has joined #openstack-meeting-322:19
*** salv-orlando has joined #openstack-meeting-322:19
*** Longgeek has quit IRC22:19
*** VW_ has quit IRC22:20
*** yamahata has joined #openstack-meeting-322:26
*** mrmartin has quit IRC22:28
*** banix has joined #openstack-meeting-322:32
*** Yi has quit IRC22:35
*** jrist has quit IRC22:36
*** tellesnobrega_ has joined #openstack-meeting-322:39
*** carl_baldwin has quit IRC22:40
*** peristeri has quit IRC22:43
*** VW_ has joined #openstack-meeting-322:43
*** Sandra_ has joined #openstack-meeting-322:44
*** Networkn3rd has quit IRC22:47
*** annegent_ has quit IRC22:49
*** Sandra_ has quit IRC22:50
*** GavinPratt has quit IRC22:57
*** jrist has joined #openstack-meeting-323:00
*** jrist has quit IRC23:00
*** jrist has joined #openstack-meeting-323:00
*** Yi has joined #openstack-meeting-323:02
*** jgrimm is now known as zz_jgrimm23:06
*** jrist has quit IRC23:08
*** dboik_ has joined #openstack-meeting-323:09
*** dboik has quit IRC23:13
*** dboik_ has quit IRC23:14
*** y-oguchi has joined #openstack-meeting-323:18
*** y-oguchi has quit IRC23:19
*** Yi has quit IRC23:19
*** cbader has quit IRC23:19
*** watanabe_isao has joined #openstack-meeting-323:27
*** watanabe_isao has quit IRC23:28
*** watanabe_isao has joined #openstack-meeting-323:32
*** jrist has joined #openstack-meeting-323:36
*** jrist has quit IRC23:36
*** jrist has joined #openstack-meeting-323:36
*** yamahata has quit IRC23:39
*** tellesnobrega_ has quit IRC23:39
*** openstack has joined #openstack-meeting-323:40
*** ChanServ sets mode: +o openstack23:40
*** baoli has quit IRC23:42
*** bknudson has quit IRC23:42
*** baoli has joined #openstack-meeting-323:42
*** VW_ has quit IRC23:49
*** jrist has quit IRC23:53
*** carl_baldwin has joined #openstack-meeting-323:54
*** salv-orlando has quit IRC23:54
*** annegent_ has joined #openstack-meeting-323:59

Generated by 2.14.0 by Marius Gedminas - find it at!