Thursday, 2015-02-19

cyeohhey all :-)00:00
etoewshere we go00:00
etoews#startmeeting api wg00:00
openstackMeeting started Thu Feb 19 00:00:18 2015 UTC and is due to finish in 60 minutes.  The chair is etoews. Information about MeetBot at http://wiki.debian.org/MeetBot.00:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.00:00
*** openstack changes topic to " (Meeting topic: api wg)"00:00
openstackThe meeting name has been set to 'api_wg'00:00
etoews#link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda00:00
etoews#topic mission statement00:00
*** openstack changes topic to "mission statement (Meeting topic: api wg)"00:00
etoews#link https://review.openstack.org/#/c/155911/00:01
etoewsthe discussion is going well00:01
etoewsnot really much to say00:01
etoewsexcept...00:01
ryansbMight we be ready for a vote?00:02
etoewsrosmaita has a question..."My question is: what is the sense of "pragmatic" in this sentence?"00:02
etoewswhich ties into our next topic00:02
rosmaitawe can kill 2 birds with one stone!00:02
etoewsdeath to birds00:02
* sigmavirus24 is suddenly feeling uncomfortable here as a bird with arms00:03
miguelgrinbergthese are big birds though, we need a bigger stone :)00:03
etoewsrosmaita do you have a preference on which aspect you want to tackle this from?00:03
sigmavirus24I know, we'll use miguelgrinberg as the stone =P00:03
rosmaitanot really00:03
rosmaitamaybe concrete first, though00:03
etoewsdiscuss the abstract "pragmatic" or concrete review first00:03
etoewsreview it is00:04
*** yamamoto has joined #openstack-meeting-300:04
etoews#topic Glance and functional API00:04
*** openstack changes topic to "Glance and functional API (Meeting topic: api wg)"00:04
etoews#link http://lists.openstack.org/pipermail/openstack-dev/2015-February/056968.html00:04
etoews#link https://etherpad.openstack.org/p/glance-adding-functional-operations-to-api00:04
etoews#link https://review.openstack.org/#/c/13512200:04
etoewsthoughts and feels?00:05
rosmaitai was trying to explain the discussion to some glance devs this afternoon00:06
rosmaitathey feel like we have a simple use case, disable an image00:06
elmikoi like jay's idea, but i think i prefer option C00:06
rosmaitait seems like a lot of extra overhead to create a resource00:06
etoewsrosmaita the "heavyweight"00:07
miguelgrinbergrosmaita: I agree about the overhead00:07
cyeohso I think Jay's is fine where have async calls00:07
elmikocyeoh: yea, makes a ton of sense there00:07
cyeohbut it does seem heavy to me too for sync calls if the caller can know straight away if it succeded/failed00:07
elmikoagreed, i think that's why i prefer C in this case00:07
cyeohso although this specific case only handles sync, will it ever expand with other actions which may be async?00:09
nikhil_ko/00:09
rosmaitacyeoh: no, we have actual tasks for that00:09
*** dttocs has quit IRC00:09
rosmaita(already)00:09
sigmavirus24nikhil_k: o/00:10
* nikhil_k hi5s sigmavirus24 00:10
cyeohrosmaita: ok00:10
sigmavirus24etoews: fwiw, the other "heavyweight" is using the existing /tasks endpoint for this00:10
nikhil_kGlance tasks are supposed to be user centric00:10
nikhil_kand this operations is admin/oper specific00:10
nikhil_kthese*00:11
nikhil_kare*00:11
rosmaitaplus tasks come with a framework to make them easy to implemenet00:11
etoewsto me (c) sounds like a controller that operates on a resource as per "RESTful Web Services Cookbook"00:12
etoews(section 2.6)00:12
etoewsrosmaita nikhil_k do either of you know if that was the intention?00:12
* jaypipes likes jay's idea as well00:13
rosmaitahi jay!00:13
jaypipesheh, hi :)00:13
* sigmavirus24 likes jaypipes and his idea00:13
*** Yi has quit IRC00:14
nikhil_ketoews: am looking into that section00:15
nikhil_ketoews: reading through half way seems to indicate that it was the intent (or one of the main ones)00:17
rosmaitai concur00:17
*** eghobo has joined #openstack-meeting-300:17
nikhil_kActaually, I was reading some blogs this afternoon which pointed me to retrospect of the same things00:18
etoewsi'm starting to lean towards (c)00:19
*** markvoelker has quit IRC00:19
rosmaitai think it is a pragmatic and respectable solution00:20
etoews(d) seems to veer away from the stated intent of that api (async calls)00:20
etoewsif the task resource wasn't dedicated to async, it would be a different story i think.00:21
etoewsjaypipes miguelgrinberg thoughts?00:22
sigmavirus24Yeah, I stopped having strong feelings either way a while ago, so while I like jaypipes's idea, I just want this discussion to finish up00:22
etoewssigmavirus24 +100:22
miguelgrinbergas I said in the ML, in my view none of the options currently in the table are the best, but of all I like jaypipes best00:22
nikhil_kjaypipes: hi00:23
etoewslet me throw this out there00:23
nikhil_kjaypipes: I wanted to ask why your felt so strongly for task vs action ?00:23
etoewshow would people feel about (c) being used in other apis?00:23
etoewsor put another way, is what we come up with this decision to be a guideline going forward?00:24
miguelgrinbergI will never +1 such a guideline, sorry00:24
sigmavirus24I think it shouldn't be a guideline00:24
rosmaitai am ok with other apis doing this where appropriate00:24
nikhil_k== rosmaita00:24
*** shamail has quit IRC00:25
elmikoi'm withi rosmaita, i'd be ok with it where it makes sense00:25
sigmavirus24It seems to me that the people who already implemented this elsewhere regret it already so that should be a reason to avoid this (or maybe I'm thinking of a separate conversation)00:25
elmikoi also think there is an important distinction between sync/async00:25
rosmaitai think people who mixed sync and async in the same resource are the ones with regrets00:26
* nikhil_k wonders if perfect ontology exists for scalable, maintainable, portable large scale computational systems00:26
cyeohyea, for sync calls I think (C) is good, when it can be async then tasks are appropriate00:26
rosmaitacyeoh: +100:26
elmikocyeoh: +100:26
cyeohif it is a resource that could have sync or async depending on the operation, then I'd prefer (d) as a recommendation00:27
*** fischerw has quit IRC00:27
elmikothat makes sense to me00:27
*** sarob has quit IRC00:27
cyeohbut then I guess this part of "pragmatism" ;-)00:27
elmikohehe00:27
rosmaitacyeoh: you brought us full circle!00:27
cyeoh:-)00:28
etoewssunrise sunet00:28
etoewss/sunet/sunset/00:28
sigmavirus24I like sunet better00:28
*** Yi has joined #openstack-meeting-300:29
etoewsi think jaypipes got distracted (i know he has another meeting at this time)00:30
etoewsi'm not sure what else to do besides put it to a vote.00:30
sigmavirus24Yeah jaypipes has disappeared00:30
rosmaitaif it's a tie we can call him back00:31
nikhil_kWe also had flavio vote for option C on the ML00:32
etoewsphrasing....00:33
*** melwitt has quit IRC00:33
*** stevelle has joined #openstack-meeting-300:34
etoews#startvote should glance use POST /images/{image_id}/actions/[deactivate|activate] (aka (c)) to put images into a deactive or active state?00:34
openstackBegin voting on: should glance use POST /images/{image_id}/actions/[deactivate|activate] (aka (c)) to put images into a deactive or active state? Valid vote options are Yes, No.00:34
openstackVote using '#vote OPTION'. Only your last vote counts.00:34
rosmaita#vote Yes00:35
elmiko#vote Yes00:35
elmiko(gotta say this feels a little weird voting on what glance should do)00:35
ryansbwell it's voting on the wg's recommendation00:36
etoewsgood point00:36
sigmavirus24(they asked for our input)00:36
ryansb#vote yes00:36
ryansb#vote Yes00:36
elmikoryansb: yea, exactly00:36
etoewsryansb uses words good00:36
cyeohyea, when passing it on should probably clarify that its just a recommendation. We can't make them do anything00:36
elmikolol00:36
nikhil_k#vote Yes00:36
cyeoh#vote yes00:36
rosmaitacyeoh: +100:36
elmikoright, vote on what we recommend they do. i guess that's implied.00:37
etoewsmy bad phrasing00:37
elmikono worries00:37
etoewsthe point is well taken00:37
etoews#vote Yes00:37
etoewssigmavirus24 miguelgrinberg ?00:37
* sigmavirus24 is abstaining purposefully =P00:38
etoewsimo a No vote is perfectly respectable.00:38
sigmavirus24I don't feel strongly either way at this point00:38
elmikoetoews: +100:38
etoewsbut abstaining is okay too00:38
miguelgrinbergthere's nothing that I find interesting, so I'm not voting00:38
etoewsokay00:38
etoews#showvote00:39
sigmavirus24I think it's #endvote, no?00:39
etoewsmeetbot y u no #showvote00:39
sigmavirus24Even so it doesn't work =P00:39
etoewssupposedly there's a #showvote00:39
etoewsforget it00:39
etoews#endvote00:39
openstackVoted on "should glance use POST /images/{image_id}/actions/[deactivate|activate] (aka (c)) to put images into a deactive or active state?" Results are00:39
stevelleI'm pretty sure I have a sticky with a lead on that voting bug00:39
sigmavirus24endvote is supposed to show the results but doesn't00:39
sigmavirus24stevelle: /me assigns it to you00:40
elmikohmm, that endvote bug really stings lol00:40
etoews#agreed the api wg recommends that glance use POST /images/{image_id}/actions/[deactivate|activate] (aka (c)) to put images into a deactive or active state00:41
*** david-lyle is now known as david-lyle_afk00:41
sigmavirus24elmiko: 99% sure no one voted No ;)00:41
sigmavirus24Besides jaypipes in spirit00:42
etoewswell that wasn't an easy discussion but i do want to thank rosmaita and nikhil_k for reaching out to us.00:42
elmikosigmavirus24: yea, that was softball00:42
* nikhil_k thanks everyone for their valuable input and background knowledge00:42
*** eghobo has quit IRC00:42
rosmaitaso it looks like "pragmatic" means there's some reasonable prior art, like for example the controller pattern in the web svcs cookbook?00:42
nikhil_kelmiko: thanks to you for that reference in the cookbook!00:43
nikhil_ketoews: ^00:43
elmiko?00:43
sigmavirus24one of you e* people ;)00:43
nikhil_kelmiko: sorry, bad day00:43
elmiko=)00:43
elmikonikhil_k: hope it gets better tomorrow00:43
nikhil_k:)00:44
* nikhil_k still trying to digest the winter storm warning00:44
elmikooh man... that could be serious depending your locale00:45
nikhil_kno kidding00:46
sigmavirus24I'm not sure why everyone's complaining. It's -15 with windchill here00:46
sigmavirus24You don't hear me complaining00:46
sigmavirus24(-15F)00:46
etoewsrosmaita ya. to me "pragmatic" means taking into account the wider context.00:46
cyeoh35C over here :)00:46
rosmaitaetoews: that seems reasonable00:47
sigmavirus24etoews: pretty sure that's convergence more than pragmatism00:47
elmikosigmavirus24: about the same here, a tad warmer00:47
nikhil_ksigmavirus24: :) because MSP is always prepared for long and chilly winters!00:47
sigmavirus24we have an existing well designed API practice, let's converge on that00:47
sigmavirus24nikhil_k: heh, I'm only in this general region for ~2 years now though so, I wasn't last year00:47
cyeohsigmavirus24: If the practice is clearly wrong, I think we can recommend what best practice is though (presumably has some advantages) and then expect over time that the older projects will converge to that00:48
nikhil_k:)00:48
sigmavirus24cyeoh: correct00:49
cyeoheventually ally the projects are going to have to tackle backwards incompatible changes (and probably in a way that allows them to do it over time rather than big version bumps.00:49
sigmavirus24pragmatism I think means "without over-architecting an one aspect of an API" IMO00:49
etoews"pragmatic" is a mighty squishy term.00:50
nikhil_k== etoews00:50
sigmavirus24perhaps we should squash it from the mission statement then00:50
elmikoagreed about squishy-ness, but sometimes squishy is called for00:50
etoewselmiko that's why i left it in there00:51
etoewsit's a very subjective term00:51
sigmavirus24"deferring to best current practice when one is available"00:51
elmikomy understanding is that we are using "pragmatic" to indicate that we will attempt to create guidelines that pay respects to best practices in the field as well as attempting to honor the existing choices that have been made. then making decisions that have the greatest gain with the least pain =)00:52
nikhil_khow feasible is it to apply webservices semantics to infrastructure system resources?00:52
*** markvoelker has joined #openstack-meeting-300:52
etoewselmiko i like that take on it00:53
sigmavirus24nikhil_k: I think that's better asked "how feasible is it to expose infrastructure system resources through web services?"00:53
nikhil_ksigmavirus24: heh, abs. I think we need to un-cloud stuff now ;)00:53
* sigmavirus24 wants his almost 3 year old nephews to use requests to make clouds go soon ;)00:53
* nikhil_k finds his magic wand00:54
sigmavirus24heh00:54
etoewsif anyone feels strongly about the word pragmatic please comment on the mission statement review.00:54
*** alexsyip has quit IRC00:54
rosmaitai like what elmiko said above00:54
etoews#topic previous meeting action items00:55
* nikhil_k like=then making decisions that have the greatest gain with the least pain00:55
*** openstack changes topic to "previous meeting action items (Meeting topic: api wg)"00:55
etoews#link http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-02-12-16.00.html00:55
*** nelsnelson has joined #openstack-meeting-300:56
etoews*desparately wants to discuss versioning but knows we don't have enough time*00:56
cyeohetoews: microversioning of apis?00:56
*** GavinPratt_ has quit IRC00:57
*** GavinPratt has quit IRC00:57
etoewsimo we need to say _something_ about versioning00:57
etoewsit's always the second question we get.00:57
*** bknudson has quit IRC00:58
etoewshow do we go from x to y?00:58
cyeohyea, projects should at least think about it early on before it gets even more expensive to do00:58
etoewsexactly00:58
cyeohthe nova microversions will probably be enabled next wed00:58
elmikocould we develop some sort of checklist that might help for projects considering a version change?00:59
cyeohand from what little I've seen of it, the ironic one looks very similar (at least from the user point of view)00:59
*** markvoelker has quit IRC00:59
etoewswe'll need a survey of the current designs.00:59
sigmavirus24And time01:00
sigmavirus24at which point I'm going to grab dinner01:00
sigmavirus24good night all01:00
*** stevelle has left #openstack-meeting-301:00
etoews#endmeeting01:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"01:00
openstackMeeting ended Thu Feb 19 01:00:23 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)01:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-02-19-00.00.html01:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-02-19-00.00.txt01:00
openstackLog:            http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-02-19-00.00.log.html01:00
etoewscya. thanks all.01:00
cyeohcya!01:00
rosmaitabye01:00
*** ryansb has left #openstack-meeting-301:01
*** sigmavirus24 is now known as sigmavirus24_awa01:02
elmikolater, etoews thanks!01:03
rosmaitayes, thanks etoews01:03
*** rosmaita has left #openstack-meeting-301:03
*** elmiko has left #openstack-meeting-301:03
*** banix has joined #openstack-meeting-301:04
*** yamamoto has quit IRC01:05
*** etoews has quit IRC01:06
*** vishy has quit IRC01:07
*** vishy has joined #openstack-meeting-301:08
*** krotscheck has quit IRC01:18
*** MarkAtwood has joined #openstack-meeting-301:19
*** ivar-laz_ has quit IRC01:25
*** ivar-lazzaro has joined #openstack-meeting-301:26
*** ivar-lazzaro has quit IRC01:28
*** markvoelker has joined #openstack-meeting-301:29
*** ivar-lazzaro has joined #openstack-meeting-301:29
*** nelsnelson has quit IRC01:29
*** banix has quit IRC01:30
*** ivar-lazzaro has quit IRC01:40
*** ivar-lazzaro has joined #openstack-meeting-301:41
*** mattgriffin has joined #openstack-meeting-301:43
*** s3wong has quit IRC01:50
*** absubram has quit IRC01:54
*** devlaps has quit IRC01:55
*** krotscheck has joined #openstack-meeting-302:03
*** clu_ has quit IRC02:08
*** krotscheck has quit IRC02:12
*** krotscheck has joined #openstack-meeting-302:13
*** banix has joined #openstack-meeting-302:16
*** etoews has joined #openstack-meeting-302:17
*** stevenldt has quit IRC02:21
*** killer_prince is now known as lazy_prince02:21
*** FallenPegasus has joined #openstack-meeting-302:23
*** MarkAtwood has quit IRC02:25
*** FallenPegasus is now known as MarkAtwood02:25
*** SridharRamaswam1 has quit IRC02:25
*** mattgriffin has quit IRC02:27
*** seizadi has joined #openstack-meeting-302:28
*** seizadi has quit IRC02:29
*** armax has quit IRC02:30
*** salv-orlando has quit IRC02:40
*** banix has quit IRC02:44
*** Piet has quit IRC02:45
*** banix has joined #openstack-meeting-302:52
*** bpokorny has quit IRC03:01
*** etoews has quit IRC03:03
*** mattgriffin has joined #openstack-meeting-303:08
*** seizadi has joined #openstack-meeting-303:09
*** megm_ has joined #openstack-meeting-303:10
*** megm has quit IRC03:11
*** marg7175 has quit IRC03:21
*** nelsnelson has joined #openstack-meeting-303:36
*** salv-orlando has joined #openstack-meeting-303:41
*** banix has quit IRC03:41
*** yamamoto has joined #openstack-meeting-303:48
*** yamahata has quit IRC03:54
*** seizadi has quit IRC03:54
*** seizadi has joined #openstack-meeting-303:55
*** jckasper has joined #openstack-meeting-303:56
*** jckasper has quit IRC03:56
*** jckasper has joined #openstack-meeting-303:56
*** mwang2 has quit IRC03:57
*** badveli has quit IRC03:58
*** seizadi has quit IRC03:59
*** seizadi has joined #openstack-meeting-303:59
*** amotoki has joined #openstack-meeting-304:04
*** seizadi has quit IRC04:04
*** seizadi has joined #openstack-meeting-304:04
*** lazy_prince is now known as killer_prince04:05
*** sandr8 has joined #openstack-meeting-304:07
*** seizadi1 has joined #openstack-meeting-304:08
*** seizadi has quit IRC04:08
*** Yi has quit IRC04:12
*** seizadi1 has quit IRC04:13
*** SridarK has quit IRC04:16
*** yamamoto has quit IRC04:20
*** marg7175 has joined #openstack-meeting-304:22
*** marg7175 has joined #openstack-meeting-304:23
*** mwang2 has joined #openstack-meeting-304:24
*** ivar-laz_ has joined #openstack-meeting-304:25
*** coolsvap_ is now known as coolsvap04:28
*** ivar-lazzaro has quit IRC04:29
*** nelsnelson has quit IRC04:30
*** ivar-laz_ has quit IRC04:30
*** salv-orlando has quit IRC04:31
*** marg7175 has quit IRC04:34
*** etoews has joined #openstack-meeting-304:38
*** markvoelker has quit IRC04:42
*** markvoelker has joined #openstack-meeting-304:42
*** etoews has quit IRC04:43
*** markvoelker has quit IRC04:46
*** Yi has joined #openstack-meeting-305:01
*** Yi has quit IRC05:01
*** Yi has joined #openstack-meeting-305:01
*** coolsvap is now known as coolsvap_05:05
*** yamamoto has joined #openstack-meeting-305:07
*** markvoelker has joined #openstack-meeting-305:13
*** coolsvap_ is now known as coolsvap05:15
*** markvoelker has quit IRC05:17
*** Sukhdev has joined #openstack-meeting-305:19
*** VW_ has joined #openstack-meeting-305:19
*** yamahata has joined #openstack-meeting-305:19
*** VW_ has quit IRC05:21
*** VW_ has joined #openstack-meeting-305:22
*** Yi has quit IRC05:24
*** mattgriffin has quit IRC05:28
*** mwang2 has quit IRC05:34
*** mwang2 has joined #openstack-meeting-305:37
*** killer_prince is now known as lazy_prince05:38
*** etoews has joined #openstack-meeting-305:39
*** mattgriffin has joined #openstack-meeting-305:43
*** etoews has quit IRC05:43
*** amotoki_ has joined #openstack-meeting-305:44
*** mwang2_ has joined #openstack-meeting-305:45
*** mwang2 has quit IRC05:47
*** amotoki has quit IRC05:47
*** mwang2_ has quit IRC05:51
*** mattgriffin has quit IRC05:53
*** mwang2 has joined #openstack-meeting-305:54
*** zigo has quit IRC05:54
*** zigo has joined #openstack-meeting-305:55
*** absubram has joined #openstack-meeting-306:01
*** absubram has quit IRC06:02
*** mwang2 has quit IRC06:02
*** absubram has joined #openstack-meeting-306:03
*** Sukhdev has quit IRC06:12
*** markvoelker has joined #openstack-meeting-306:13
*** salv-orlando has joined #openstack-meeting-306:15
*** SridharRamaswamy has joined #openstack-meeting-306:16
*** seizadi has joined #openstack-meeting-306:17
*** markvoelker has quit IRC06:18
*** Sukhdev has joined #openstack-meeting-306:21
*** SridharRamaswam1 has joined #openstack-meeting-306:21
*** SridharRamaswamy has quit IRC06:22
*** Yi has joined #openstack-meeting-306:24
*** belmoreira has joined #openstack-meeting-306:26
*** VW_ has quit IRC06:28
*** Yi has quit IRC06:29
*** absubram has quit IRC06:31
*** seizadi1 has joined #openstack-meeting-306:32
*** seizadi has quit IRC06:32
*** seizadi1 has quit IRC06:37
*** seizadi has joined #openstack-meeting-306:37
*** etoews has joined #openstack-meeting-306:40
*** SridharRamaswam1 has quit IRC06:40
*** seizadi1 has joined #openstack-meeting-306:41
*** seizadi has quit IRC06:41
*** etoews has quit IRC06:44
*** seizadi1 has quit IRC06:45
*** seizadi has joined #openstack-meeting-306:46
*** seizadi has quit IRC06:47
*** devvesa has joined #openstack-meeting-306:50
*** yamahata has quit IRC06:51
*** yamahata has joined #openstack-meeting-306:52
*** mrunge has joined #openstack-meeting-307:03
*** mrunge has quit IRC07:03
*** mrunge has joined #openstack-meeting-307:03
*** Sukhdev has quit IRC07:04
*** mrmartin has joined #openstack-meeting-307:06
*** megm has joined #openstack-meeting-307:12
*** megm_ has quit IRC07:13
*** markvoelker has joined #openstack-meeting-307:14
*** Godfath3r has joined #openstack-meeting-307:15
*** Sukhdev has joined #openstack-meeting-307:16
*** pkoniszewski has joined #openstack-meeting-307:19
*** markvoelker has quit IRC07:19
*** MarkAtwood has quit IRC07:20
*** MarkAtwood has joined #openstack-meeting-307:21
*** Godfath3r has quit IRC07:22
*** salv-orlando has quit IRC07:26
*** VW_ has joined #openstack-meeting-307:27
*** VW_ has quit IRC07:27
*** VW__ has joined #openstack-meeting-307:28
*** sahid has joined #openstack-meeting-307:31
*** Sukhdev has quit IRC07:34
*** stanzgy has joined #openstack-meeting-307:57
*** sergef has joined #openstack-meeting-308:00
*** markvoelker has joined #openstack-meeting-308:15
*** markvoelker has quit IRC08:20
*** scheuran has joined #openstack-meeting-308:23
*** yamamoto has quit IRC08:24
*** jcoufal has joined #openstack-meeting-308:25
*** salv-orlando has joined #openstack-meeting-308:25
*** evgenyf has joined #openstack-meeting-308:37
*** MaxV has joined #openstack-meeting-308:50
*** salv-orlando has quit IRC08:52
*** salv-orlando has joined #openstack-meeting-308:52
*** etoews has joined #openstack-meeting-308:58
*** zz_johnthetubagu is now known as johnthetubaguy09:00
*** etoews has quit IRC09:03
*** jcoufal_ has joined #openstack-meeting-309:05
*** egallen has joined #openstack-meeting-309:06
*** jcoufal has quit IRC09:08
*** egallen has quit IRC09:13
*** matrohon has joined #openstack-meeting-309:14
*** stanzgy has quit IRC09:16
*** markvoelker has joined #openstack-meeting-309:16
*** markvoelker has quit IRC09:21
*** salv-orlando has quit IRC09:29
*** yamamoto has joined #openstack-meeting-309:31
*** salv-orlando has joined #openstack-meeting-309:33
*** VW__ has quit IRC09:34
*** egallen has joined #openstack-meeting-309:36
*** yamahata has quit IRC09:39
*** VW_ has joined #openstack-meeting-309:39
*** VW_ has quit IRC09:48
*** VW_ has joined #openstack-meeting-309:49
*** yamamoto has quit IRC09:50
*** etoews has joined #openstack-meeting-310:00
*** yamamoto has joined #openstack-meeting-310:00
*** Yi has joined #openstack-meeting-310:03
*** etoews has quit IRC10:04
*** jtomasek_ has joined #openstack-meeting-310:07
*** Yi has quit IRC10:08
*** pkoniszewski has quit IRC10:08
*** yamamoto has quit IRC10:10
*** amotoki_ has quit IRC10:14
*** markvoelker has joined #openstack-meeting-310:17
*** stanzgy has joined #openstack-meeting-310:18
*** amotoki has joined #openstack-meeting-310:18
*** ihrachyshka has joined #openstack-meeting-310:21
*** yamamoto has joined #openstack-meeting-310:21
*** markvoelker has quit IRC10:22
*** yamamoto has quit IRC10:31
*** sergef has quit IRC10:39
*** VW_ has quit IRC10:39
*** yamamoto has joined #openstack-meeting-310:39
*** jcoufal_ has quit IRC10:45
*** jcoufal has joined #openstack-meeting-310:46
*** yamamoto has quit IRC10:47
*** pkoniszewski has joined #openstack-meeting-310:50
*** egallen has quit IRC10:52
*** etoews has joined #openstack-meeting-311:00
*** etoews has quit IRC11:05
*** VW_ has joined #openstack-meeting-311:07
*** salv-orlando has quit IRC11:11
*** salv-orlando has joined #openstack-meeting-311:12
*** megm_ has joined #openstack-meeting-311:14
*** megm has quit IRC11:15
*** markvoelker has joined #openstack-meeting-311:18
*** markvoelker has quit IRC11:23
*** VW_ has quit IRC11:25
*** VW_ has joined #openstack-meeting-311:27
*** VW_ has quit IRC11:27
*** VW_ has joined #openstack-meeting-311:28
*** salv-orlando has quit IRC11:31
*** salv-orlando has joined #openstack-meeting-311:31
*** johnthetubaguy is now known as zz_johnthetubagu11:35
*** pkoniszewski has quit IRC11:47
*** yamamoto has joined #openstack-meeting-311:50
*** alexpilotti has joined #openstack-meeting-311:51
*** yamamoto has quit IRC11:55
*** mwang2 has joined #openstack-meeting-311:59
*** egallen has joined #openstack-meeting-312:01
*** mwang2 has quit IRC12:03
*** wojdev has joined #openstack-meeting-312:03
*** wojdev has quit IRC12:03
*** mwagner_lap has quit IRC12:10
*** banix has joined #openstack-meeting-312:16
*** ihrachyshka has quit IRC12:16
*** yamamoto has joined #openstack-meeting-312:16
*** banix has quit IRC12:19
*** markvoelker has joined #openstack-meeting-312:19
*** markvoelker has quit IRC12:24
*** VW_ has quit IRC12:29
*** VW_ has joined #openstack-meeting-312:30
*** salv-orlando has quit IRC12:31
*** salv-orlando has joined #openstack-meeting-312:31
*** SridharRamaswamy has joined #openstack-meeting-312:38
*** salv-orlando has quit IRC12:40
*** salv-orlando has joined #openstack-meeting-312:41
*** stanzgy has quit IRC12:42
*** SridharRamaswamy has quit IRC12:42
*** amotoki has quit IRC12:43
*** VW_ has quit IRC12:47
*** salv-orlando has quit IRC12:49
*** zz_johnthetubagu is now known as johnthetubaguy12:52
*** pkoniszewski has joined #openstack-meeting-312:52
*** etoews has joined #openstack-meeting-313:00
*** Yi has joined #openstack-meeting-313:00
*** markvoelker has joined #openstack-meeting-313:02
*** etoews has quit IRC13:03
*** alexpilotti has quit IRC13:05
*** etoews has joined #openstack-meeting-313:05
*** Yi has quit IRC13:13
*** Yi has joined #openstack-meeting-313:29
*** Yi has quit IRC13:33
*** markvoelker_ has joined #openstack-meeting-313:42
*** markvoelker has quit IRC13:42
*** Yi has joined #openstack-meeting-313:46
*** stanzgy has joined #openstack-meeting-313:47
*** salv-orlando has joined #openstack-meeting-313:50
*** yamamoto has quit IRC13:51
*** sigmavirus24_awa is now known as sigmavirus2413:52
*** ihrachyshka has joined #openstack-meeting-313:52
*** jtomasek_ has quit IRC13:52
*** jtomasek has joined #openstack-meeting-313:53
*** sergef has joined #openstack-meeting-313:55
*** crobertsrh has joined #openstack-meeting-314:00
*** stevelle has joined #openstack-meeting-314:03
*** beagles is now known as beagles_brb14:11
*** amuller has joined #openstack-meeting-314:14
*** VW_ has joined #openstack-meeting-314:22
*** banix has joined #openstack-meeting-314:23
*** VW_ has quit IRC14:26
*** gulic has joined #openstack-meeting-314:27
*** banix has quit IRC14:30
*** banix has joined #openstack-meeting-314:32
*** VW_ has joined #openstack-meeting-314:33
*** lblanchard has joined #openstack-meeting-314:34
*** markvoelker_ has quit IRC14:38
*** salv-orlando has quit IRC14:39
*** markvoelker has joined #openstack-meeting-314:39
*** mattgriffin has joined #openstack-meeting-314:39
*** salv-orlando has joined #openstack-meeting-314:40
*** pavel_bondar has joined #openstack-meeting-314:47
*** MaxV has quit IRC14:51
*** mrsmith has joined #openstack-meeting-314:53
*** mwagner_lap has joined #openstack-meeting-314:55
*** tidwellr1 has joined #openstack-meeting-314:57
*** carl_baldwin has joined #openstack-meeting-314:57
*** yamahata has joined #openstack-meeting-314:57
*** mrsmith has quit IRC14:59
*** pc_m has joined #openstack-meeting-315:00
*** mlavalle has joined #openstack-meeting-315:00
carl_baldwinhi all15:00
mlavallehi15:00
pc_mhi15:00
*** mrsmith has joined #openstack-meeting-315:00
tidwellr1hi15:00
pavel_bondarhi15:00
carl_baldwin#startmeeting neutron_l315:00
openstackMeeting started Thu Feb 19 15:00:53 2015 UTC and is due to finish in 60 minutes.  The chair is carl_baldwin. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
amullerheya15:00
*** stevelle has left #openstack-meeting-315:00
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:00
openstackThe meeting name has been set to 'neutron_l3'15:00
salv-orlandoaloha15:01
carl_baldwin#topic Announcements15:01
*** jpomero has joined #openstack-meeting-315:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:01
mrsmithG'day15:01
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam15:01
carl_baldwinkilo-3 is four weeks away.  That isn’t much time at all.15:01
carl_baldwinVoting for summit talks is open this week and will close soon.  I’m not sure when.15:02
pc_m23rd I think...15:03
amulleryeah15:03
carl_baldwinThat sounds right.  I’ve already voted.15:04
carl_baldwinAny other announcements?15:04
carl_baldwin#topic Bugs15:04
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:04
*** lazy_prince is now known as killer_prince15:05
carl_baldwinI don’t have any bugs to bring up now.  Are there any bugs to bring to our attention?15:05
*** absubram has joined #openstack-meeting-315:06
salv-orlandonot from me. I am not aware of serious issues with l3 agent or dvr15:06
salv-orlandobut this does not mean that there aren't issues - it's just that I'm not aware of them!15:06
carl_baldwin#topic L3 agent restructuring.15:07
*** openstack changes topic to "L3 agent restructuring. (Meeting topic: neutron_l3)"15:07
carl_baldwinWe’re winding down this effort but still trying to get patches merged15:07
carl_baldwin#link https://review.openstack.org/#/q/topic:bp/restructure-l3-agent+status:open,n,z15:07
carl_baldwinIf you remove the status:open from the query, you can see just how much has already been merged.  We’re really on the tail end here.15:08
carl_baldwinAnything to discuss here?15:08
carl_baldwinWe’ll just keep moving forward then.15:10
carl_baldwin#topic neutron-ipam15:10
*** openstack changes topic to "neutron-ipam (Meeting topic: neutron_l3)"15:10
carl_baldwinHow are we doing here?15:10
tidwellr1new patch here https://review.openstack.org/#/c/148698/15:11
tidwellr1*patch set15:11
salv-orlandoaloha15:11
carl_baldwintidwellr1: Thanks.15:11
salv-orlandoso I have two topics which I'd like to bring to your attention15:12
carl_baldwintidwellr1: I will be sure to review it today.15:12
pavel_bondarNew version of db_base re-factor, still WIP, https://review.openstack.org/#/c/153236/15:12
salv-orlando1)  non blocking IP Allocation algorithms 2) what we can reasonably merge in Kilo15:12
salv-orlandoI might become quite chatty - so if you want me to move this discussions to the mailing list I'll do that15:13
carl_baldwinpavel_bondar: Thanks.  I will review it today.  Hopefully others here can too.15:13
carl_baldwinsalv-orlando: No worries.  Let’s see what we can discuss here.15:13
*** nelsnelson has joined #openstack-meeting-315:13
salv-orlandoIp allocation: https://github.com/salv-orlando/ip_allocation_poc15:13
salv-orlandoI've tested 2 non-locking algorithms (that don't do lock for update)15:13
*** nelsnelson has quit IRC15:14
salv-orlandoand compared them with lock for update.  executing a lock for update scales a lot better. Were you expecting that?15:14
salv-orlandoI kind of was expecting this - since approaches based on retries are conceptually similar to active waits15:14
*** MaxV has joined #openstack-meeting-315:15
carl_baldwinsalv-orlando: That kind of makes sense.15:15
*** nelsnelson has joined #openstack-meeting-315:15
salv-orlandohowever the issue is that lock for update queries suffer of dataset validation issues in active/active clusters like galera15:15
salv-orlandoso we need an alternative15:15
carl_baldwinAre both found in db.py in your link?15:15
salv-orlandocarl_baldwin: the algorithms package15:15
carl_baldwinsalv-orlando: Thanks, I glanced right over that sub-package.15:16
salv-orlandocarl_baldwin: that github repo is kind of ok - I just need to add some documentation to explain the algorithms15:16
*** amuller has quit IRC15:16
*** megm has joined #openstack-meeting-315:17
salv-orlandoI devised two - one based on primary keys. It's rather slow, and also I found out that in active active cluster also primary key violations trigger data set validation failures and hence db deadlocks15:17
salv-orlandoso that approach is baddish as well.15:17
*** megm_ has quit IRC15:17
salv-orlandothe third one instead is a three-step approach which leverages compare-and-swap and also uses the same technique as the bully election to uniquely determine a winner15:17
carl_baldwinsalv-orlando: I’m not I understand yet the data set validation failures with primary key violations.15:18
*** amuller has joined #openstack-meeting-315:19
salv-orlandocarl_baldwin: basically if you add two records with the same pkey on two nodes you won't know about the violation until the data sets are synchronized, and this will be signalled with a DBDeadlock error15:19
salv-orlandoapparently dealing with these errors is quite expensive15:19
salv-orlandoI say apparently because I do not have numbers to support a quantitative judgment. But somebody from Galera came to the ML to explain how things work.15:19
*** seizadi has joined #openstack-meeting-315:20
carl_baldwinsalv-orlando: I see.  It seems there is much I don’t know about the active/active clusters.  I wouldn’t have expected such a delay.15:20
carl_baldwinsalv-orlando: Do you have a link to that ML thread?15:20
salv-orlandocarl_baldwin: gimme one minute to find it.15:20
salv-orlandocarl_baldwin: I think the issue lies in the fact that the rollback upon a data set validation error is a lot more expensive that a rollback which can be triggered before a local commit (local == your local node)15:21
* salv-orlando finding ML threads... please wait15:22
salv-orlandocarl_baldwin: this is one thread -> http://lists.openstack.org/pipermail/openstack-dev/2014-May/035264.html15:22
salv-orlandocarl_baldwin: and this is the second one -> http://lists.openstack.org/pipermail/openstack-dev/2015-February/056007.html15:23
salv-orlandosummarizing - I will post later on today a detailed analysis15:23
salv-orlandobut my opinion is: give users a chance to choose the algorithms that better suits their needs. a query which does lock for update works in most cases.15:24
carl_baldwinsalv-orlando: Thank you.  This will take some time to review.15:24
salv-orlandoAnd also provide support for DBDeadlock failures when doing LOCK...FOR UPDATE15:24
salv-orlandoBut then also offer an alternative which scales decently for people using ACTIVE/ACTIVE clusters15:24
salv-orlandofinally, there are two more options to consider from an architectural perspective:15:24
* carl_baldwin on the edge of his seat15:25
salv-orlando- distributed locking at the application layer. We have avoided it so far not because "it does not scale" (as I've heard several times) but because it is a process which is intrinsecally error prone. So if we can avoid distributed coordination, it's better15:25
salv-orlandoBut if are better off with some distributed coordination, we should use it15:25
amullersalv-orlando: like dogpile?15:26
carl_baldwinRight, up to now, we’ve limited all distributed coordination to what we can accomplish with the db.15:26
salv-orlando- then we can also think of having a centralized IPAM server even when there multiple API workers. This conductor-like solution will greatly simplify the architecture and the implementation of IP Allocation strategies, at the expenses of reducing the level of concurrency supported by the IPAM service15:27
*** beagles_brb is now known as beagles15:27
salv-orlandoamuller: dogpile but even memcached15:27
salv-orlandoamuller: and if you want to find the best way to make your like more complicated, use zookeeper15:27
salv-orlandoor even better, implement your own system!15:27
amullerusing dogpile or memcache to retain 'select for update' "like" behavior but making Galera happy seems like such a braindead simple solution to me15:28
salv-orlandothis is all for the first part I wanted to discuss (IP allocation)15:28
amullermuch easier than shifting our entire locking paradigm throughout the code15:29
*** yamamoto has joined #openstack-meeting-315:29
salv-orlandoamuller: while I am sure that adding a distributed lock among workers is kind of easy, I am not sure what do you about shifting the entire locking paradigm throughout the code. Anyway, we have plenty of time for in-depth technical discussions, because I think that for Kilo we should be happy to just have an IPAM driver which does IPAM as it's done todya.15:30
carl_baldwinWe need to look in to it further.  I’ve had it in the back of my mind that distributed coordination or a separate service will be the answer.15:30
*** Rajeev has joined #openstack-meeting-315:31
salv-orlandonot because it's difficult to code, but simply because we are an opinionated community and reviews can lead to the most unexpected and spectacular results.15:31
salv-orlandoanyway this lead me to the second point which is what we can merge on kilo.15:31
salv-orlandofor kilo, sorry15:31
carl_baldwinsalv-orlando: Right, we’ll have to look at this for Liberty.  We need to discuss now what we can do for Kilo.15:31
salv-orlandocarl_baldwin: to cut a long story short I think 1) db_base refactoring that enables optional usage of ipam driver; 2) reference ipam driver 3) other drivers - but I'm not sure if we want to have them in openstack/neutron15:32
*** yushiro has joined #openstack-meeting-315:32
salv-orlandoPlease do not hate me but I reckon it might be better to move subnet pools out to Liberty. I'm not sure we can get enough review cycles there and the necessary API changes in.15:32
carl_baldwinsalv-orlando: So far, that matches what I was thinking.15:33
carl_baldwinsalv-orlando: Are you aware that the API changes are up for review?15:33
salv-orlandocarl_baldwin: yes I am. But you know how it is with APIs ;)15:33
salv-orlandoI have to leave because I have another meeting now - but I want just to mention that I think I'll have the IPAM driver ready by next weds15:34
salv-orlandoand then I can move one to help with Pavel's patch review and ensure it gets merged in time.15:35
salv-orlandoAs with anything that touches the db_base_plugin class that might raise some eybrows15:35
pavel_bondarthanks, sounds good to me15:35
*** seizadi1 has joined #openstack-meeting-315:35
carl_baldwinsalv-orlando: Thanks. Would you mind doing a review of the API changes before making any judgement?15:35
salv-orlandocarl_baldwin: I will. But I sense that you are then still confident to get the subnet pools merged in Kilo ;)15:36
*** seizadi has quit IRC15:36
carl_baldwinsalv-orlando: I’m not ready to concede defeat, no.15:37
carl_baldwin:)15:37
*** yamamoto has quit IRC15:37
salv-orlandocarl_baldwin: In my opinion the API change is fine as long as it's backward compatible, but I'm not the only reviewer around!15:37
*** cbader has joined #openstack-meeting-315:37
salv-orlandoanyway, I'll review these patches and provide a detailed update on IP allocation15:37
carl_baldwinsalv-orlando: Who else should I get to review it?15:37
carl_baldwinsalv-orlando: Thank you.15:38
salv-orlandocarl_baldwin: markmcclain in the past took interest in all the IPAM stuff15:38
carl_baldwinsalv-orlando: I will talk to him.15:38
salv-orlandoit might be worth to also get armax's and mestery's perspective on the release impact15:38
carl_baldwinsalv-orlando: I will15:38
*** yamamoto has joined #openstack-meeting-315:39
*** seizadi has joined #openstack-meeting-315:39
carl_baldwin#action carl_baldwin will talk to Mark about subnet API.15:39
salv-orlandocarl_baldwin: cool. Enjoy the rest of the meeting guys!15:39
carl_baldwin#action carl_baldwin will talk to mestery and armax about release impact.15:39
carl_baldwinsalv-orlando: bye.15:39
carl_baldwinAnything more on ipam?15:39
*** seizadi1 has quit IRC15:40
*** banix has quit IRC15:41
carl_baldwinLet’s get some review attention on the patchs the remainder of this week.   I will be sure they can all be easily found from the L3 meeting page.15:42
carl_baldwin#action carl_baldwin will update meeting page to easily find ipam patches.15:42
carl_baldwin#topic neutron-ovs-dvr15:42
*** openstack changes topic to "neutron-ovs-dvr (Meeting topic: neutron_l3)"15:42
carl_baldwinmrsmith: Rajeev: Swami: you around?15:43
carl_baldwinAnything to discuss?15:43
carl_baldwinviveknarasimhan alse15:43
carl_baldwins/alse/also/15:43
mrsmithI am just getting back up to speed from holiday15:43
Rajeevcarl_baldwin: resuming work on HA15:44
*** Sukhdev has joined #openstack-meeting-315:44
Rajeevand some other patches that were pending but nothing to discuss here for me.15:44
*** mrunge has quit IRC15:47
*** mattgriffin has quit IRC15:48
carl_baldwinThanks, I see that Swami’s patch merged.  Is anyone keeping an eye on the dvr job failures?15:48
carl_baldwinI don’t see any significant improvement yet.15:49
Rajeevcarl_baldwin: I think armax's graph will be the indicator15:49
mrsmithSlight drop ya15:49
*** stanzgy has quit IRC15:49
mrsmithLast I checked15:49
carl_baldwinI think it needs a little more time.15:50
Rajeevcarl_baldwin: agreed15:51
*** jaypipes has quit IRC15:51
*** mattgriffin has joined #openstack-meeting-315:51
*** yamamoto has quit IRC15:51
Rajeevwe do have couple of talks submitted, please do vote15:52
carl_baldwinRajeev: I did see them.  Best of luck.15:53
*** thangp has joined #openstack-meeting-315:53
Rajeevcarl_baldwin: Thanks.15:54
carl_baldwinWell, I think we’re about ready to wrap up.15:54
carl_baldwin#topic Open Discussion15:54
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)"15:54
carl_baldwinAnyone have good talk abstracts to plug?  ;)15:54
*** killer_prince is now known as lazy_prince15:55
pc_mcarl_baldwin: Do think we're at a point where we can refactor the VPN device driver to access new router object, vs use VPN_service and agent?15:56
*** peristeri has joined #openstack-meeting-315:56
carl_baldwinpc_m: Yes, I think we can get started on that.15:56
pc_mcurrent device driver -> vpn service -> agent -> router15:56
carl_baldwinJohn submitted a talk on IPAM15:57
carl_baldwin#link https://www.openstack.org/vote-vancouver/presentation/subnet-pools-and-pluggable-external-ip-management-in-openstack-kilo15:57
pc_mdevice driver has router_id, should we use that to get the router object and then move the methods into the driver?15:57
carl_baldwinrossella_s submitted a talk on L2/L3 agent improvements15:57
carl_baldwin#link https://www.openstack.org/vote-vancouver/presentation/neutron-l2-and-l3-agents-how-they-work-and-how-kilo-improves-them15:57
*** kozhukalov has joined #openstack-meeting-315:57
*** Sukhdev has quit IRC15:58
carl_baldwinsc68cal and I submitted one on IPv6 and L315:58
carl_baldwin#link https://www.openstack.org/vote-vancouver/presentation/whats-coming-for-ipv6-and-l3-in-neutron15:58
pc_mcarl_baldwin: driver needs to add/delete nat rules. Are there existing methods in the router class that can be used?15:58
carl_baldwinpc_m: Some of that might still be unmerged in the patch chain.15:59
pc_mcarl_baldwin: OK. Will ping you off line to discuss15:59
carl_baldwinpc_m: It just occurred to me that (obviously) the advanced services can’t have patches that depend on unmerged patches in Neutron.15:59
carl_baldwinpc_m: Okay.15:59
carl_baldwinOkay, we’re out of time.16:00
carl_baldwin#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Thu Feb 19 16:00:11 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
pc_mcarl_baldwin: Yeah, just need to see if I should wait more, and if ready, how we proceed.16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-02-19-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-02-19-15.00.txt16:00
pc_mbye16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-02-19-15.00.log.html16:00
*** pc_m has left #openstack-meeting-316:00
carl_baldwinThanks, all for your great work.16:00
carl_baldwinWe’ve made a lot of progress in all of these areas.16:00
*** jaypipes has joined #openstack-meeting-316:01
*** mlavalle has left #openstack-meeting-316:01
*** armax has joined #openstack-meeting-316:02
*** mrsmith has quit IRC16:04
*** annegentle has joined #openstack-meeting-316:04
*** david-lyle_afk is now known as david-lyle16:04
*** seizadi1 has joined #openstack-meeting-316:05
VW_any meeting officially scheduled to start right now?16:05
VW_need to sort out a meeting room conflict16:06
*** seizadi has quit IRC16:06
*** bpokorny has joined #openstack-meeting-316:08
*** seizadi1 has quit IRC16:09
*** seizadi has joined #openstack-meeting-316:09
*** marun has joined #openstack-meeting-316:12
sigmavirus24VW_: is https://wiki.openstack.org/wiki/Meetings#Openstack_Operators_Team_Meeting you?16:12
VW_no, it's the Large Deployments Team (a subset of the above)16:13
VW_we are admittedly behind on wiki stuff16:13
VW_completely not the ansible group's fault16:13
VW_I'll clean it all up and find us another spot16:13
*** seizadi1 has joined #openstack-meeting-316:14
*** tidwellr1 has left #openstack-meeting-316:14
*** seizadi has quit IRC16:14
*** devvesa has quit IRC16:18
*** seizadi1 has quit IRC16:21
*** seizadi has joined #openstack-meeting-316:21
*** yushiro is now known as yushiro_afk16:24
*** Yi has quit IRC16:25
*** Piet has joined #openstack-meeting-316:26
*** seizadi1 has joined #openstack-meeting-316:29
*** seizadi has quit IRC16:30
*** seizadi1 has quit IRC16:33
*** seizadi has joined #openstack-meeting-316:33
*** seizadi has quit IRC16:37
*** seizadi1 has joined #openstack-meeting-316:37
*** annegentle has quit IRC16:39
*** yamahata has quit IRC16:39
*** annegentle has joined #openstack-meeting-316:40
*** Yi has joined #openstack-meeting-316:42
*** vgridnev_ has joined #openstack-meeting-316:49
*** lazy_prince is now known as killer_prince16:49
*** mestery has quit IRC16:49
*** salv-orlando has quit IRC16:52
*** seizadi1 has quit IRC16:52
*** yamamoto has joined #openstack-meeting-316:52
*** scheuran has quit IRC16:52
*** killer_prince is now known as lazy_prince16:55
*** seizadi has joined #openstack-meeting-316:56
*** yamamoto has quit IRC16:57
*** coolsvap is now known as coolsvap_16:57
*** jtomasek has quit IRC17:01
*** annegentle has quit IRC17:01
*** seizadi has quit IRC17:01
*** carl_baldwin has quit IRC17:02
*** ihrachyshka has quit IRC17:03
*** Yi_ has joined #openstack-meeting-317:09
*** yamahata has joined #openstack-meeting-317:10
*** pkoniszewski has quit IRC17:12
*** Yi has quit IRC17:12
*** crobertsrh has left #openstack-meeting-317:17
*** alexsyip has joined #openstack-meeting-317:19
*** jcoufal has quit IRC17:25
*** bknudson has joined #openstack-meeting-317:26
*** SridharRamaswamy has joined #openstack-meeting-317:27
*** MaxV has quit IRC17:30
*** dansmith has quit IRC17:30
*** dansmith has joined #openstack-meeting-317:30
*** gduan has quit IRC17:32
*** garyduan has joined #openstack-meeting-317:32
*** banix has joined #openstack-meeting-317:34
*** krotscheck has quit IRC17:36
*** SridharRamaswamy has quit IRC17:36
*** krotscheck has joined #openstack-meeting-317:39
*** banix has quit IRC17:39
*** yapeng has joined #openstack-meeting-317:40
*** matrohon has quit IRC17:42
*** carl_baldwin has joined #openstack-meeting-317:42
*** amuller has left #openstack-meeting-317:48
*** mattgriffin has quit IRC17:48
*** seizadi has joined #openstack-meeting-317:49
*** seizadi has quit IRC17:50
*** seizadi has joined #openstack-meeting-317:50
*** mageshgv has joined #openstack-meeting-317:51
*** salv-orlando has joined #openstack-meeting-317:52
*** SumitNaiksatam has joined #openstack-meeting-317:55
*** yapeng has left #openstack-meeting-317:58
*** bpokorny_ has joined #openstack-meeting-317:58
*** yapeng has joined #openstack-meeting-317:58
*** yushiro_afk is now known as yushiro17:59
*** sreshetnyak has joined #openstack-meeting-317:59
*** rkukura has joined #openstack-meeting-317:59
SumitNaiksatamyapeng: mageshgv: hi17:59
SumitNaiksatamYi_: hi18:00
rkukurahi18:00
SumitNaiksatamrkukura: hi18:00
mageshgvSumitNaiksatam:hi18:00
*** s3wong has joined #openstack-meeting-318:00
SumitNaiksatams3wong: hi18:00
yapengHi18:00
SumitNaiksatamlets get started18:00
SumitNaiksatam#startmeeting networking_policy18:00
openstackMeeting started Thu Feb 19 18:00:33 2015 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: networking_policy)"18:00
openstackThe meeting name has been set to 'networking_policy'18:00
s3wonghello18:00
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy#Feb_19th.2C_12th.2C_201518:00
SumitNaiksatam#info kilo-1 was released on Feb 16th18:01
*** bpokorny has quit IRC18:01
SumitNaiksatam#link http://lists.openstack.org/pipermail/openstack-dev/2015-February/057115.html18:01
SumitNaiksatamour next milestone is March 16th18:02
SumitNaiksatamanything else anyone would like to share?18:02
*** elmiko has joined #openstack-meeting-318:02
*** Youcef has joined #openstack-meeting-318:03
rkukuraSumitNaiksatam: Is there a plan to release stable-juno?18:03
Yi_SumitNaiksatam: Hi18:03
*** ivar-lazzaro has joined #openstack-meeting-318:03
SumitNaiksatamrkukura: i think we have a bunch of juno-backport potentials which have to be either backported or are waiting to be fixed18:04
SumitNaiksatammy hope was to get as many of those in before doing the next stable/juno18:04
rkukuraSumitNaiksatam: Right. Was wondering if there is a target date.18:04
SumitNaiksatamhowever if you think it makes sense to do the stable/juno now, i dont have any objections18:04
rkukuraLets see after we discuss bugs whether there are backportable fixes coming soon.18:05
SumitNaiksatamrkukura: i personally dont have a date in mind, though i was kind of considering this as an asap activity18:05
*** elmiko has left #openstack-meeting-318:06
SumitNaiksatamrkukura: good point to bring up, perhaps fixing a date will speed up the backport acitivity18:06
SumitNaiksatam#topic Bugs18:06
*** openstack changes topic to "Bugs (Meeting topic: networking_policy)"18:06
SumitNaiksatamwe touched on a number of bugs in the last couple of meetings18:06
*** mattgriffin has joined #openstack-meeting-318:06
SumitNaiksatamanyone wants to report any updates on those18:07
SumitNaiksatama few fixes were merged18:07
SumitNaiksatambut there is still a bunch that we need to close on18:07
rkukuraI’ve added followup questions on a couple that were assigned to me, but haven’t seen responses yet.18:07
SumitNaiksatamrkukura: which ones?18:07
rkukurahttps://bugs.launchpad.net/group-based-policy/+bug/1417206/comments/118:08
openstackLaunchpad bug 1417206 in Group Based Policy "GBP: PTG delete at times not cleaning neutron resources" [Undecided,New] - Assigned to Robert Kukura (rkukura)18:08
*** etoews has quit IRC18:08
rkukurahttps://bugs.launchpad.net/group-based-policy/+bug/1416527/comments/418:08
openstackLaunchpad bug 1416527 in Group Based Policy "GBP: PTG delete errors out" [Undecided,New]18:08
SumitNaiksatamrkukura: okay let me follow up on those two18:09
rkukuraSumitNaiksatam: thanks18:09
SumitNaiksatamhopefully i can get jishnu to join the meetings in the future, so that he can participate directly rather me being a proxy18:09
rkukuraI should be able to knock off https://bugs.launchpad.net/group-based-policy/+bug/1417724 soon.18:09
openstackLaunchpad bug 1417724 in Group Based Policy "GBP: Changing L3P of a in-use L2P, does not reflect in change in subnet of PTG" [High,Confirmed] - Assigned to Robert Kukura (rkukura)18:09
SumitNaiksatamrkukura: nice!18:10
SumitNaiksatam#action SumitNaiksatam to follow up with jishnub on 1416527 and 141720618:10
SumitNaiksatamKrishnaK updated offline that he is working on the bug in his plate, and he should be done soon18:11
*** belmoreira has quit IRC18:11
SumitNaiksatamwe dont have enough time in this meeting to a complete bug scrub, but if our bug count grows or we are not able to clean up the current ones, we will need to schedule one separately18:12
SumitNaiksatammy request to everyone is to look at the bugs assigned to them and target them for the appropriage milestone18:12
SumitNaiksatamright now i have targeted mostly everything for K-218:13
SumitNaiksatamwhich may be actually be the case, but if its not please target appropriately18:13
*** etoews has joined #openstack-meeting-318:14
SumitNaiksatami think we have a “future” milestone as well for anything that cannot be immediately fixed in kilo18:14
SumitNaiksatamor is not considered immediately relevant18:14
SumitNaiksatamany other blockers on the bugs18:14
SumitNaiksatami dont see any new criticals so thats good18:14
SumitNaiksatambtw, i noticed some issues in the CLI as well especially when pointing to “neutron” resources18:15
rkukuraI’d actually like to see more bugs being reported - evidence that the code is being used18:15
SumitNaiksatamrkukura: agree, but too many criticals would mean we are not doing a good job reviewing :-)18:16
SumitNaiksatamon the CLI issue, so if you try to creat a group, and point to a pre-created subnet, the CLI will fail18:16
SumitNaiksatamjust in case if it anyone tries this18:16
SumitNaiksatamthis is because we try to do a validation of the neutron resource in the CLI and the reference to the neutron client is not correct18:17
SumitNaiksatami will check if there is a bug for this, else i will file one18:17
*** mwang2 has joined #openstack-meeting-318:17
*** LouisF has joined #openstack-meeting-318:17
SumitNaiksatamanything else to discuss in bugs today?18:17
SumitNaiksatamanyone blocked on anything?18:17
SumitNaiksatamLouisF: hi18:18
LouisFhi18:18
SumitNaiksatamok moving on18:18
SumitNaiksatam#topic Re-factor Group Based Policy with Neutron RESTful APIs18:18
*** openstack changes topic to "Re-factor Group Based Policy with Neutron RESTful APIs (Meeting topic: networking_policy)"18:18
SumitNaiksatam#link https://review.openstack.org/#/c/15312618:18
SumitNaiksatamdid folks get a chance to review this spec?18:18
SumitNaiksatamthe Yi_ yapeng team is in full force there today18:19
rkukuraI read through it again, and will file a couple minor comments18:19
SumitNaiksatamrkukura: okay18:19
rkukuraI’ll try to do that by the end of today18:19
Yi_rkukura: thanks!18:19
SumitNaiksatami am really hoping that at least at a spec level we close on this by enf of today18:19
SumitNaiksatam*end18:19
ivar-lazzaroSumitNaiksatam: +118:19
*** absubram has quit IRC18:19
SumitNaiksatamivar-lazzaro: okay18:19
yapengrkukura, thanks, I updated the spec based on previous comments.18:19
SumitNaiksatameverybody else think thats doable?18:20
rkukura+118:20
LouisF+118:20
SumitNaiksatamwe can always give comments on the implementation, but i think the spec has been waiting for a long time18:20
SumitNaiksatamrkukura: LouisF: ok thanks18:20
SumitNaiksatamYi_: yapeng: lets work on this today close the spec, based on any outstanding review comments18:21
SumitNaiksatammageshgv: did you get a chance to read?18:21
*** egallen has quit IRC18:21
yapengSumitNaiksatam: sure18:21
SumitNaiksatam*read/review18:21
Yi_SumitNaiksatam: sounds great!18:21
mageshgvSumitNaiksatam: Yes, looks ok18:21
SumitNaiksatamok good, so we have some loose consensus here18:21
SumitNaiksatamthanks yapeng and Yi_ for your patience on this!18:22
SumitNaiksatamoh, and Yi_ you posted a WIP patch: #link https://review.openstack.org/#/c/156856/18:22
SumitNaiksatamthanks18:22
Yi_as well as https://review.openstack.org/#/c/156776/18:23
SumitNaiksatamah sorry, i missed that18:23
Yi_Yapeng and I also did some manual testing on this18:23
SumitNaiksatamYi_: sweet18:24
Yi_following the devstack example18:24
Yi_for the base cases, we were able to do it18:24
SumitNaiksatamYi_ yapeng: are there any blockers for you at this point (apart from the reviews)18:24
SumitNaiksatamanything that you would like to get resolved within the team?18:24
Yi_SumitNaiksatam: so far so good18:24
yapengnot right now.18:24
SumitNaiksatami know you had questions on the external connectivity18:24
SumitNaiksatamok18:24
rkukuraI’ve got a question on the client library18:25
Yi_yes, if we can have clear instruction to test external connectivity, it would be great18:25
SumitNaiksatamrkukura: please18:25
SumitNaiksatamgo ahead18:25
rkukuraWill this mean all our current unit tests for the mapping_driver (and maybe others) will depend on a running neutron server?18:26
Yi_rkukura: I don't think the client code should introduce any new dependency, but I miss something?18:27
SumitNaiksatamrkukura: good question18:27
SumitNaiksatamrkukura: the usual approach would be to mock, right?18:27
yapengrkukura, depends, UT can mock some data18:27
SumitNaiksatamyapeng: yeah18:27
rkukuraRight now our “unit” tests depend pretty heavily on the direct calls into the neutron core plugin actually functioning.18:28
rkukuraWe obviously need to break this dependency, and this BP may be when we need to do it.18:28
Yi_rkukura: I see your concern18:28
SumitNaiksatamrkukura: correct, i think you are also referring to some of the functional tests which are masquerading as “unit” tests :-)18:28
rkukuraSumitNaiksatam: That’s why I quoted “unit”18:28
SumitNaiksatamthose tests are very helpful though18:29
rkukuraI’m not really clear on how neutron defines “functional test”, but could our functional tests depend on a running neutron-server?18:29
SumitNaiksatami would have hoped that we dont lose the validation provided those tests when do this mock (meaning we actually trigger functional tests separately)18:29
SumitNaiksatamrkukura: this again goes to the tempest lib usage per project, right?18:30
rkukuraSumitNaiksatam: Right, I’m thinking we’d move/copy the existing “unit” tests to be functional tests.18:30
rkukuraNot really sure if tempest comes into play for this.18:30
SumitNaiksatamrkukura: and run the neutron server for those?18:30
rkukuraright18:31
yapengare these tests belong to tempest instead of UT?18:31
rkukurayapeng: I don’t think these specific tests really require tempest and a full deployment, but they could be done that way.18:32
SumitNaiksatamyapeng: i think the guidance is to move to a model of using a tempest lib, and putting the tests in each project18:32
rkukuraRight now, these tests call the GBP API and then use neutron APIs to verify the resources were mapped correctly.18:32
SumitNaiksatamthough i am not completely clear on the specifics of that18:32
rkukuraWe could do that with just the gbp-server and neutron-server, and not a full devstack/tempest setup.18:33
Yi_SumitNaiksatam rkukura: shouldn't we have a seperated project/BP to tract such a movement?18:33
SumitNaiksatamYi_: agreed18:33
SumitNaiksatamrkukura: any chance that you can investigate this?18:33
rkukuraYi_: I agree for the new server, but I’m concern about this BP breaking the existing test strategy18:34
rkukuraI don’t think neutron will actually accept client HTTP connections when run in unit tests.18:34
rkukuraBut I could be wrong18:34
*** Piet has quit IRC18:34
rkukuraIf it does work in the current UT setup, then there is no immediate issue18:35
SumitNaiksatamrkukura:  so if i understand your suggestion, as part of this refactoring, and before we actually move to a different service, your suggestion is move these tests to a “funcationa” test directory18:35
rkukuraSumitNaiksatam: Maybe - if needed18:35
SumitNaiksatamrkukura: and not use the client lib18:35
SumitNaiksatamjust keep the tests the way they are18:35
SumitNaiksatami think i like that as an interim solution18:35
rkukuraBut the rmd is going to be using the client lib18:35
rkukuraThe question is whether mocking at the client lib level makes sense with the existing tests18:36
rkukuraOr if those tests should become function tests where neutron-server does access client connections18:36
rkukuras/access/accept/18:36
*** yapeng has quit IRC18:37
*** yapeng_ has joined #openstack-meeting-318:37
SumitNaiksatamrkukura: in the cases where you are using the direct neutron calls to validate the neutron resources, mocking would not make sense, right?18:37
rkukuraI’ll include this test impact in a comment on the BP18:37
rkukuraon the spec I mean18:37
rkukuraSumitNaiksatam: Right, I think the tests would have to change drastically18:38
rkukuraAnd I kind of agree these tests really should be functional rather than unit tests18:38
rkukuraSo maybe we should do proper mock-based unit tests for RMD.18:38
*** pkoniszewski has joined #openstack-meeting-318:38
yapeng_was disconnected. I will check the spec comments.18:38
SumitNaiksatamrkukura: Yi_ yapeng_, if you guys dont mind can we meet sometime today in #openstack-gbp to close on this?18:38
*** SridharRamaswamy has joined #openstack-meeting-318:39
rkukuraSumitNaiksatam: sure18:39
yapeng_sure18:39
Yi_SumitNaiksatam: sure18:39
SumitNaiksatamgreat18:39
SumitNaiksatami think we need rkukura to provide guidance on this since he has mostly written the RMD tests18:39
SumitNaiksatamivar-lazzaro: if you have time, please do join as well, but no pressure18:40
rkukuraI’ll need to look over thest current tests to refresh my memory18:40
SumitNaiksatammageshgv: i know it will be late for you, so you are excused ;-)18:40
ivar-lazzaroSumitNaiksatam: sure18:40
SumitNaiksatamrkukura: yes, lets not meet right after this, i will communicate offline with you guys18:40
rkukuraok18:40
SumitNaiksatamokay lets move on for now18:40
Yi_ok.18:40
SumitNaiksatam#topic Floating IP support18:41
*** bpokorny has joined #openstack-meeting-318:41
*** openstack changes topic to "Floating IP support (Meeting topic: networking_policy)"18:41
SumitNaiksatam#link https://review.openstack.org/15729818:41
SumitNaiksatammageshgv: thanks for posting the spec18:41
SumitNaiksatamdid anyone get a chance to review?18:41
SumitNaiksatami did a quick read before the meeting18:41
rkukuraI have not yet18:42
SumitNaiksatambut did not get a chance to post coments18:42
*** melwitt has joined #openstack-meeting-318:43
SumitNaiksatammageshgv: per ivar-lazzaro’s comment from last week, i think we need to clarify how the “nat_pool” resource relates to all this18:43
mageshgvSumitNaiksatam: It will be good to discuss here. Last week we did not reach a consensus in the meeting18:43
SumitNaiksatamokay18:43
mageshgvSumitNaiksatam: Right, I feel that nat_pool is not useful unless gbp does the natting by itself18:44
*** bpokorny_ has quit IRC18:44
*** stanzgy has joined #openstack-meeting-318:45
ivar-lazzaromageshgv: NAT pool should be the Neutron equivalent of a FIP pool18:45
ivar-lazzaromageshgv: scoped per external segment18:45
ivar-lazzaroIn Neutron, a FIP pool today is a portion of the external subnet, is that correct?18:46
*** johnthetubaguy is now known as zz_johnthetubagu18:46
SumitNaiksatamivar-lazzaro: i believe so18:46
mageshgvivar-lazzaro: Ah, I get what you mean, but is the nat_pool originally intended to be used this way ? I still really get its use case as it is not used today18:46
*** Sukhdev has joined #openstack-meeting-318:47
rkukuraIs this for SNAT or DNAT?18:47
SumitNaiksatamrkukura: good question18:47
ivar-lazzaromageshgv: it's not used today, but that was exactly the intention18:47
*** evgenyf has quit IRC18:47
ivar-lazzarorkukura: it's for Floating IPs, so SNAT18:47
rkukuraIs’nt that DNAT ivar-lazzaro ?18:48
ivar-lazzarorkukura: DNAT is activated by the "PAT" attribute on the segment18:48
SumitNaiksatamivar-lazzaro: thats DNAT, right?18:48
mageshgvivar-lazzaro: thanks for the clarification18:48
SumitNaiksatamivar-lazzaro: PAT is for SNAT (going from inside to the outside)18:48
SumitNaiksatamper the neutron model, doing the PAT one does not necessarily have to use the floating ip (or at least that was my understanding)18:49
ivar-lazzaroSumitNaiksatam: PAT is Dynamic NAT18:49
ivar-lazzaroSumitNaiksatam: or port address translation18:49
SumitNaiksatamivar-lazzaro: yes18:49
ivar-lazzaroSumitNaiksatam: FIP are 1:1 addresses18:49
*** peristeri has quit IRC18:49
Yi_ivar-lazzaro: that's right18:49
ivar-lazzaroSumitNaiksatam: so Static NAT18:49
SumitNaiksatamwhen we say DNAT here, it means destination NAT, not dynamic NAT18:49
*** stanzgy has quit IRC18:50
ivar-lazzarooh18:50
SumitNaiksatamSNAT is static NAT18:50
rkukuraFIP is DNAT since the destination is modified as packets enter18:50
*** MaxV has joined #openstack-meeting-318:50
SumitNaiksatamrkukura: yes, thats the terminology i am familiar with as well18:50
ivar-lazzaroDNAT for me means dynamic NAT, but thanks for clarifying18:50
*** etoews has quit IRC18:50
SumitNaiksatamok that aside, i think the nat_pool will still tie into the current spec, right?18:51
ivar-lazzarook that's the thing, the NAT pool is the pool from which you retrieve addresses for 1:1 mapping18:51
SumitNaiksatami think the current spec is talking in terms of using the entire subnet from the external subnet18:51
ivar-lazzaro1:1 means that the SRC address gets modified for outgoing packets18:51
*** etoews has joined #openstack-meeting-318:51
SumitNaiksatamwhereas nat_pool provides a way to restrict it18:51
ivar-lazzaroand DST address modified for incoming packets18:51
SumitNaiksatamivar-lazzaro: is it necessary to do the 1:1 for the outgoing packets (even when a floating IP is assigned)?18:53
ivar-lazzarothe PAT flag, on the other hand, is like the one we have on traditional IPv4 networks at home. N internal addresses are translated on the outgoing traffic into M (with M < N tipically)18:53
ivar-lazzaroand the translation is done by port number18:53
SumitNaiksatamivar-lazzaro: yes, PAT can be independent of the floating ip association18:53
Yi_SumitNaiksatam: if it is NOT FIP, 1:1 is not required18:53
ivar-lazzaroSumitNaiksatam: not sure how Neutron does today18:53
SumitNaiksatamivar-lazzaro: my understanding was that, for outgoing, neutron does a PAT18:54
ivar-lazzaroSumitNaiksatam: but I would guess that a VM with a FIP reaching the outside world will have that FIP as source address18:54
SumitNaiksatamand if floating IP is defined, then it does a SNAT based on the floating IP for incoming18:54
SumitNaiksatamso i think we are discussing two points here:18:55
ivar-lazzaroSumitNaiksatam: and outgoing IMHO. but that's an implementation detail isn't it?18:55
SumitNaiksatam1. how/whether to use the “nat_pool” currently defined in the model18:55
SumitNaiksatam2. how do we achieve outgoing address translation when a floating IP is defined for a port18:56
*** sahid has quit IRC18:56
SumitNaiksatami think for the later we will have to follow the neutron model (whichever way its implemented)18:56
SumitNaiksatamso we should investigate that and document it in the spec18:57
ivar-lazzaroSumitNaiksatam: note that the NAT pool may not restrict the external segment subnet! It may be a completely different set of addresses.18:57
SumitNaiksatamivar-lazzaro: okay18:57
*** salv-orlando has quit IRC18:57
SumitNaiksatamand for (1), instead of using the external subnet, use the “nat_pool” for drawing the floating_ips18:57
SumitNaiksatamivar-lazzaro: mageshgv: does that sound, right?18:57
ivar-lazzaroSumitNaiksatam: that sounds like the initial intent for that model :)18:58
SumitNaiksatamivar-lazzaro: which model?18:58
mageshgvsumitNaiksatam: sounds good18:58
ivar-lazzaroSumitNaiksatam: the "nat_pool" object18:58
Yi_SumitNaiksatam, mageshgv: the current nat-pool in neutron is related wirh LBaas, is that right?18:59
SumitNaiksatamivar-lazzaro: okay, is it documented somewhere, that way mageshgv make use of that reference18:59
SumitNaiksatamYi_: no, not really18:59
SumitNaiksatamYi_: the current “nat_pool” is a place holder, its not used18:59
SumitNaiksatamhence the confusion18:59
ivar-lazzaroSumitNaiksatam: the External connectivity spec should do the trick IIRC18:59
*** kozhukalov has quit IRC19:00
*** clu_ has joined #openstack-meeting-319:00
*** Piet has joined #openstack-meeting-319:00
*** sreshetnyak has quit IRC19:01
SumitNaiksatamivar-lazzaro: the spec says this: “Nat Policy A pool of IP addresses (range/cidr) that will be used by the drivers to implement NAT capabilities when needed. How and whether the Nat Policy will be used by the reference implementation is out of scope of this blueprint.”19:01
SumitNaiksatamwe are in a minute over19:01
SumitNaiksatamgood discussion19:01
SumitNaiksatammageshgv: do you think you have enough information now to wrap up the spec?19:01
*** SridharRamaswamy has quit IRC19:02
mageshgvI think we can continue tomorrow on IRC19:02
SumitNaiksatammageshgv: okay sure, perhaps you can factor the current discussion into the spec and the rest of the team can review based on that, and we take it from there19:02
SumitNaiksatammageshgv: thanks for working on this19:02
SumitNaiksatam#topic Open Discussion19:02
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"19:02
*** SridharRamaswamy has joined #openstack-meeting-319:02
SumitNaiksatamwe skipped the taskflow discussion and the update on packaging19:03
*** vgridnev_ has quit IRC19:03
ivar-lazzaroI would like to bring up a couple of Vancouver talks we are proposing19:03
SumitNaiksatamivar-lazzaro: yes, we have a bunch of talks around GBP19:03
ivar-lazzaro#link https://www.openstack.org/vote-vanvouver/presentation/taking-security-groups-to-ludicrous-speed-with-open-vswitch19:04
SumitNaiksatamlet post the talks on the wiki page19:04
ivar-lazzaro(not really GBP related that one, but still interesting)19:04
SumitNaiksatamso that everyone can see them19:04
ivar-lazzaroOk good idea19:04
ivar-lazzarowe also are proposing a Lab session19:04
*** SridharRamaswamy has quit IRC19:05
s3wongcool19:05
SumitNaiksatamall please check the wiki page by end of today for the talks19:05
SumitNaiksatamand please vote :-)19:05
SumitNaiksatamthanks all19:05
SumitNaiksatambye19:05
yushirothank you19:05
ivar-lazzaroMe and rkukura are driving this, but it would be great to have at least one more core with deep experience on GBP's SC19:05
Yi_bye19:05
ivar-lazzaroso let me know if you are interested :) byw!19:05
SumitNaiksatamivar-lazzaro: needless to say, i will be participating as well19:06
rkukurabye19:06
mageshgvbye19:06
SumitNaiksatam#endmeeting19:06
s3wongivar-lazzaro: assuming it is voted in :-)19:06
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:06
openstackMeeting ended Thu Feb 19 19:06:14 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:06
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-02-19-18.00.html19:06
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-02-19-18.00.txt19:06
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-02-19-18.00.log.html19:06
ivar-lazzaroSumitNaiksatam: ofc :D19:06
*** yushiro has quit IRC19:07
*** mageshgv has quit IRC19:07
*** rkukura has left #openstack-meeting-319:07
*** s3wong has quit IRC19:10
*** mestery has joined #openstack-meeting-319:12
*** MarkAtwood has quit IRC19:18
*** Yi has joined #openstack-meeting-319:18
*** bpokorny_ has joined #openstack-meeting-319:18
*** megm_ has joined #openstack-meeting-319:18
*** megm has quit IRC19:19
*** sarob has joined #openstack-meeting-319:19
*** bpokorny has quit IRC19:21
*** Yi has left #openstack-meeting-319:21
*** Yi_ has quit IRC19:21
*** Godfath3r has joined #openstack-meeting-319:21
*** VW_ has quit IRC19:22
*** MaxV has quit IRC19:23
*** SridharRamaswamy has joined #openstack-meeting-319:24
*** seizadi has quit IRC19:31
*** bpokorny has joined #openstack-meeting-319:31
*** salv-orlando has joined #openstack-meeting-319:32
*** SridharRamaswamy has quit IRC19:33
*** bpokorny_ has quit IRC19:34
*** SridharRamaswamy has joined #openstack-meeting-319:36
*** mrunge has joined #openstack-meeting-319:41
*** mestery has quit IRC19:44
*** LouisF has quit IRC19:44
*** yapeng_ has quit IRC19:52
*** sandr8 has quit IRC19:54
*** SridharRamaswamy has quit IRC19:54
*** yamamoto has joined #openstack-meeting-319:55
*** sandr8 has joined #openstack-meeting-319:55
*** yamamoto has quit IRC19:59
*** bpokorny_ has joined #openstack-meeting-320:03
*** peristeri has joined #openstack-meeting-320:04
*** bpokorny has quit IRC20:06
*** SridharRamaswamy has joined #openstack-meeting-320:08
*** MaxV has joined #openstack-meeting-320:09
*** VW_ has joined #openstack-meeting-320:12
*** mestery has joined #openstack-meeting-320:13
*** VW_ has quit IRC20:18
*** clu_ has quit IRC20:19
*** VW_ has joined #openstack-meeting-320:19
*** clu_ has joined #openstack-meeting-320:21
*** VW_ has quit IRC20:31
*** Youcef has quit IRC20:31
*** Youcef has joined #openstack-meeting-320:37
*** MaxV has quit IRC20:37
*** Piet has quit IRC20:46
*** Sukhdev has quit IRC20:46
*** arosen has quit IRC20:50
*** Yi_ has joined #openstack-meeting-320:50
*** yamahata has quit IRC20:51
*** mwang2 has quit IRC20:51
*** bpokorny has joined #openstack-meeting-320:54
*** bpokorny_ has quit IRC20:57
*** Sam-I-Am has joined #openstack-meeting-320:57
*** Godfath3r has quit IRC20:58
mattgriffinhello HA Guide team!21:00
megm_Hi, Matt!21:00
mattgriffinhey megm_21:00
*** nickchase has joined #openstack-meeting-321:01
mattgriffinhello nickchase21:01
Sam-I-Amhello21:01
megm_While you're waiting, the start of the outline is at https://wiki.openstack.org/wiki/HAGuideImprovements/TOC21:01
nickchasehey, all21:01
mattgriffinmegm_, great... going to officially start the meeting :)21:01
Sam-I-Ammegm_: ah, i was going to suggest an etherpad for those21:01
megm_Hey, Nick et alia21:01
mattgriffin#startmeeting HA Guide Update21:01
openstackMeeting started Thu Feb 19 21:01:47 2015 UTC and is due to finish in 60 minutes.  The chair is mattgriffin. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: HA Guide Update)"21:01
openstackThe meeting name has been set to 'ha_guide_update'21:01
mattgriffinwelcome megm_, nickchase21:02
nickchaseSam-I-Am we already had one in the wiki, actually21:02
nickchasefrom a while back21:02
nickchaseI've talked to our HA people21:03
nickchaseand they went through what we had and vetted it21:03
nickchasewhat's there is what they feel will give us good results.21:03
Sam-I-Amcool21:03
mattgriffin#info today's agenda: https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update#Next_Meeting21:03
nickchasewe can discuss, of course21:03
nickchaseok so I have a hard stop on the half hour, actually21:04
nickchaseI apologize for that21:04
mattgriffinnickchase, cool21:04
mattgriffinnp21:04
nickchaseapparently nobody knows how to read a calendar :(21:04
mattgriffinhaha21:04
Sam-I-Amtime is overrated21:05
mattgriffinfor the benefit of others, megm_, nickchase, sriram, and I had a Hangout on last Tues21:05
megm_Can't you multitask?  ;-)21:05
* Sam-I-Am is looking over the TOC. didnt know about the link until now :/21:05
mattgriffinNotes added here: https://etherpad.openstack.org/p/openstack-basic-install-steps21:05
nickchase:)  I can to some extent21:05
mattgriffin#link https://etherpad.openstack.org/p/openstack-basic-install-steps21:05
* nickchase had forgotten about it until he asked Meg to see if there was already a blueprint (which there was).21:06
megm_We also have a blueprint that targets this for Kilo.21:06
mattgriffinwe made some decisions on where we think the structure of the HA Guide should go in the future21:06
mattgriffinSam-I-Am, sorry... should have sent around in a mailing list email21:07
*** fischerw has joined #openstack-meeting-321:07
mattgriffin#link https://wiki.openstack.org/wiki/HAGuideImprovements/TOC21:07
nickchaseWell, let's just make sure we do that in the minutes today.21:07
Sam-I-Amis there a separate ha mailing list, or is it just a tag on the docs list?21:07
nickchasetag: [ha-guide] I think21:08
mattgriffinnickchase, great stuff so far21:08
nickchasewell, megm_ did the starting point and I handed it off to the SMEs so i can't take credit. :)21:09
mattgriffinnickchase, TOC still in progress?21:09
mattgriffinmegm_, +1 :)21:09
nickchasethe SME's have had at it from a content standpoint21:09
Sam-I-Amso there's still some pacemaker stuff in here21:09
nickchasewe should look at it from a writing standpoint and see if there's some stuff we need to look at21:09
nickchasethey do use pacemaker.  if ...21:09
megm_Nick, I just added a couple more sections and some details21:09
Sam-I-Amalso dont see memcached (which doesnt really HA, but oslo supports hash synchronization among services)21:09
nickchaseyou feel it doesn't belong, let's talk about what you think it should be instead and we'll go back to them to see what the story is.21:10
nickchasethat's why we're having this conversation.  if you feel something is missing or out of place let's figure that out21:10
* mattgriffin reads21:10
Sam-I-Ami'm going to add some memcached stuff21:11
nickchaseok, please do.21:12
nickchaseif you could add some context on why you think it should be there that'd be great too21:12
mattgriffini think that's essentially homework for all - review the ToC21:12
mattgriffinnickchase, do these sections correspond with Install Guide sections?21:13
mattgriffinor mostly map to them?21:13
megm_The Install Guide outline had memcached mentioned for Horizon21:13
Sam-I-Amfor the most part21:13
mattgriffinlooks like it to me21:13
mattgriffinok21:13
Sam-I-Ammegm_: theres a lot of places where memcached makes sense for performance reasons21:14
megm_Yes, I basically structured this based on the etherpad that had the Install Guide structure21:14
Sam-I-Amalso, apache on top of keystone21:14
Sam-I-Amits sort of performance-related, but also apache handled redundancy a little better imho21:14
megm_then I annotated for HA based on the old HA guide, etc21:14
nickchaseOK, so in the interest of time, what are our next steps?21:16
*** mwang2 has joined #openstack-meeting-321:16
mattgriffinreview the ToC and update for next week21:16
nickchasegreat.21:16
megm_Can we identify pieces of the old HA Guide that are worth preserving?21:16
megm_Then set up the RST files and put those in?21:17
mattgriffinhopefully we can find some old Guide content to retain in the new structure21:18
Sam-I-Amthere's probabably some stuff21:18
nickchase+121:18
Sam-I-Amshould one person or all of us take that action item?21:18
nickchasebut is it in docbook or rst?21:18
nickchasedocbook, Iw ould think21:18
mattgriffinthat can be homework too for next week.21:18
Sam-I-Amand make notes in the ToC as necessary21:18
*** markmcclain has quit IRC21:18
megm_Yes, although maybe not a lot...21:18
Sam-I-Amnickchase: its docbook now, but we could converterate it21:18
megm_Are we missing any "big" topics in the TOC?  That should be a review priority.21:19
nickchasewe should but can I request we postpone converterating it until we work the bugs out of converterating the Networking guide?21:20
nickchase(though I hope to have that fixed shortly)21:20
nickchase(see, I DO multitask. :))21:20
*** seizadi has joined #openstack-meeting-321:20
megm_The old etherpad has links to specific HA Guide sections for each topic.  We could use that to mark each section as Keep or Replace21:20
Sam-I-Amnickchase: luckily there's not much to do for the networking guide21:20
nickchase+1 on both21:21
Sam-I-Ammegm_: TOC first, things we can convert second?21:21
mattgriffinmegm_, which pad?21:21
megm_Okay, but I'm thinking all new writing should be done in RST so we don't have more to convert21:21
megm_https://etherpad.openstack.org/p/openstack-basic-install-steps21:21
mattgriffinmegm_, yes... TOC first then convert second if needed21:21
nickchaseremember that etherpad is NOT the TOC for htis book21:22
nickchaseit's only about the install guide21:22
mattgriffinyes. that was just a catalog of main steps at a high level21:22
megm_I could move the links to the appropriate TOC sections here -- would that be too muddy?21:22
mattgriffinmegm_, i think that would be helpful21:23
megm_Perhaps in each section, just add an item like "Keep <link>" or "Replace <link>"?21:23
*** etoews_ has joined #openstack-meeting-321:23
megm_Are we writing for Juno or Kilo or both?21:25
mattgriffinmegm_, as we discussed on Tues, the sections of the HA Guide will handoff to the Install Guide (or other guides) sections so I don't think it would hurt to get started on adding those URLs21:25
Sam-I-Ammegm_: kilo makes sense, especially in light of DVR/L3HA21:25
*** sergef has quit IRC21:25
megm_Matt, I was referring to links to the old HA Guide here21:25
nickchase(my 430 got moved to 445 so I have another 15 minutes.)21:25
mattgriffinmegm_, ah... gotcha. then i think starting on the keep/replace links is good21:26
*** etoews has quit IRC21:26
megm_But yes, adding specific Install Guide links is also good.  What is the URL I should use?21:26
*** mrmartin has quit IRC21:26
Sam-I-Aminterestingly enough, wikis do not handle multiple editors :)21:27
megm_Sam, you mean simultaneously, right?  Can you edit the wiki if noone else is in it?21:27
mattgriffinmegm_, for the Install Guide, the "basic-install-steps" pad has links to each section for the different services21:28
megm_Be sure you're logged in -- it logs me out very quickly...21:28
Sam-I-Ammegm_: you can, but sometimes changes get squished21:28
megm_Ah, I see -- okay, I'll add those plus links to HA Guide21:29
*** Piet has joined #openstack-meeting-321:29
mattgriffinso the action item(s) for next week are to review and update the TOC. megm_ will start to add links to the TOC for content to keep/replace and links to the related areas in the Install Guide.21:29
mattgriffinlet's wait on converting until the TOC is done-ish21:30
megm_+1 on Matt's statement21:30
nickchase+121:30
* Sam-I-Am is matt too lol21:30
Sam-I-Amjust call me sam, everyone else does21:30
mattgriffinhehe21:30
Sam-I-Ameven at work21:30
megm_Thanks, Sam -- I wondered about that...21:31
mattgriffin:)21:31
mattgriffinany other topics to discuss for this week?21:31
*** MaxV has joined #openstack-meeting-321:31
nickchaseI got nothing21:31
mattgriffincool... ending meeting21:31
Sam-I-Amdo the toc!21:31
mattgriffin:)21:31
mattgriffin#endmeeting21:31
megm_Does anyone know of any specs, etc that we should be looking at?21:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:31
openstackMeeting ended Thu Feb 19 21:31:55 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ha_guide_update/2015/ha_guide_update.2015-02-19-21.01.html21:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ha_guide_update/2015/ha_guide_update.2015-02-19-21.01.txt21:31
openstackLog:            http://eavesdrop.openstack.org/meetings/ha_guide_update/2015/ha_guide_update.2015-02-19-21.01.log.html21:32
nickchaseok, guys, I'm out21:32
Sam-I-Amthanks everyone, things are looking good21:32
Sam-I-Amnickchase: see you tomorrow21:32
mattgriffinthanks all... later21:32
nickchaseyep. :)21:32
nickchaselater!21:32
nickchasebye21:32
megm_Bye21:32
*** Sam-I-Am has left #openstack-meeting-321:32
*** nickchase has quit IRC21:32
*** seizadi1 has joined #openstack-meeting-321:37
*** seizadi has quit IRC21:37
*** yapeng has joined #openstack-meeting-321:39
*** lazy_prince is now known as killer_prince21:39
*** ivar-laz_ has joined #openstack-meeting-321:41
*** seizadi has joined #openstack-meeting-321:41
*** seizadi1 has quit IRC21:41
*** ivar-lazzaro has quit IRC21:43
*** ivar-laz_ has quit IRC21:46
*** ivar-lazzaro has joined #openstack-meeting-321:46
*** sarob has quit IRC21:46
etoews_heh. me too.21:47
*** ivar-lazzaro has quit IRC21:47
*** seizadi has quit IRC21:47
*** ivar-lazzaro has joined #openstack-meeting-321:48
*** jaypipes has quit IRC21:53
*** seizadi has joined #openstack-meeting-321:54
*** bpokorny has quit IRC22:01
*** MaxV has quit IRC22:03
*** SridharRamaswamy has quit IRC22:04
*** marun has quit IRC22:04
*** carl_baldwin has quit IRC22:07
*** carl_baldwin has joined #openstack-meeting-322:09
*** SridharRamaswamy has joined #openstack-meeting-322:10
*** mrunge has quit IRC22:13
*** openstackstatus has joined #openstack-meeting-322:15
*** ChanServ sets mode: +v openstackstatus22:15
*** bpokorny has joined #openstack-meeting-322:21
*** bpokorny has quit IRC22:22
*** bpokorny has joined #openstack-meeting-322:22
*** lblanchard has quit IRC22:23
*** cbader has quit IRC22:26
*** seizadi has quit IRC22:27
*** seizadi has joined #openstack-meeting-322:29
*** SridharRamaswamy has quit IRC22:29
*** thangp has quit IRC22:33
*** SridharRamaswamy has joined #openstack-meeting-322:36
*** seizadi has quit IRC22:43
*** seizadi has joined #openstack-meeting-322:46
*** VW_ has joined #openstack-meeting-322:46
*** MarkAtwood has joined #openstack-meeting-322:47
*** seizadi has quit IRC22:51
*** seizadi has joined #openstack-meeting-322:52
*** jgrimm is now known as zz_jgrimm22:55
*** matrohon has joined #openstack-meeting-322:56
*** yamamoto has joined #openstack-meeting-322:57
*** pkoniszewski has quit IRC22:58
*** seizadi1 has joined #openstack-meeting-322:59
*** seizadi has quit IRC22:59
*** marun has joined #openstack-meeting-323:01
*** yamamoto has quit IRC23:02
*** seizadi1 has quit IRC23:04
*** seizadi has joined #openstack-meeting-323:04
*** Yi_ has quit IRC23:05
*** marun has quit IRC23:06
*** sarob has joined #openstack-meeting-323:07
*** yapeng has quit IRC23:08
*** Youcef has quit IRC23:09
*** MarkAtwood has quit IRC23:11
*** MarkAtwood has joined #openstack-meeting-323:12
*** egallen has joined #openstack-meeting-323:12
*** yamamoto has joined #openstack-meeting-323:15
*** bpokorny has quit IRC23:17
*** megm has joined #openstack-meeting-323:21
*** megm_ has quit IRC23:21
*** carl_baldwin has quit IRC23:22
*** seizadi1 has joined #openstack-meeting-323:23
*** yamamoto has quit IRC23:24
*** seizadi has quit IRC23:25
*** bpokorny has joined #openstack-meeting-323:28
*** seizadi has joined #openstack-meeting-323:29
*** seizadi1 has quit IRC23:30
*** yamamoto has joined #openstack-meeting-323:32
*** seizadi has quit IRC23:33
*** seizadi has joined #openstack-meeting-323:34
*** bpokorny has quit IRC23:36
*** salv-orlando has quit IRC23:39
*** seizadi1 has joined #openstack-meeting-323:39
*** seizadi has quit IRC23:40
*** salv-orlando has joined #openstack-meeting-323:40
*** carl_baldwin has joined #openstack-meeting-323:43
*** carl_baldwin has quit IRC23:45
*** markvoelker has quit IRC23:49
*** yamamoto has quit IRC23:53
*** bknudson has quit IRC23:53
*** wojdev has joined #openstack-meeting-323:54
*** seizadi1 has quit IRC23:54
*** matrohon has quit IRC23:56
*** seizadi has joined #openstack-meeting-323:57

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