Thursday, 2015-03-05

sigmavirus24#startmeeting api wg00:00
openstackMeeting started Thu Mar  5 00:00:44 2015 UTC and is due to finish in 60 minutes.  The chair is sigmavirus24. 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
cyeoho/00:00
sigmavirus24o/00:00
elmikoo/00:01
sigmavirus24etoews: asked me to run the meeting again00:01
etoewso/ i'll be here for only 10-15 min00:01
sigmavirus24I apologize in advance =P00:01
miguelgrinberghi00:01
elmikolol00:01
sigmavirus24#topic agenda00:01
*** openstack changes topic to "agenda (Meeting topic: api wg)"00:01
sigmavirus24#link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda00:01
sigmavirus24#topic versioning00:01
*** openstack changes topic to "versioning (Meeting topic: api wg)"00:01
sigmavirus24etoews: ?00:01
etoewssorry for being so vague with that one00:02
*** Brainspackle has quit IRC00:02
etoewsnow that we have the mission statement done. it seems the next most asked question is "how to i take my api from current state to following your guidelines?"00:03
sigmavirus24oh I was supposed to write a strawman for that00:03
etoewsit would be helpful to have a reasoned response00:03
*** claired has joined #openstack-meeting-300:03
etoewsbut i'm not proposing we solve api versioning in the next 10 min00:03
elmikoand.. go!00:03
*** baoli has quit IRC00:04
etoews:D00:04
cyeohyep, we should make sure that ironic and nova versioning are compatible from the rest api point of view (which I think they are even if the implementation may be a bit different in places)00:04
elmikoi think starting with some sort of high-level workflow type thingie would be useful00:04
elmikoeven if it's just bullet points for now00:04
etoews+100:05
etoewssigmavirus24: what form was that strawman to take?00:05
sigmavirus24A guideline proposing a strategy for migrating to our guidelines00:05
etoewssgtm00:06
elmikonice, kinda meta too ;)00:06
sigmavirus24I think we had discussed it last year00:06
miguelgrinbergmeta-guideline00:06
etoewsi remember the email thread you kicked off00:06
sigmavirus24Should we have guidelines to help write meta-guidelines? /kidding00:06
sigmavirus24etoews: yes00:06
etoews*feels bad for not responding to that thread*00:06
elmikosigmavirus24: LOL00:06
sigmavirus24etoews: people did, just not a lot00:06
etoewssigmavirus24: remember to include the CPLs on the review00:07
sigmavirus24okay00:07
*** Brainspackle has joined #openstack-meeting-300:07
sigmavirus24etoews: will do00:07
sigmavirus24#action sigmavirus24 to write versioning/migration guideline00:07
sigmavirus24#topic #openstack-api channel00:07
*** openstack changes topic to "#openstack-api channel (Meeting topic: api wg)"00:07
*** Rockyg has quit IRC00:07
*** markvoelker has quit IRC00:07
sigmavirus24So after the last meeting a few of us discussed the idea of #openstack-api and after a quick check with etoews today I went ahead and made it figuring it was better to ask for forgiveness00:08
elmiko\o/00:08
sigmavirus24I sent a message to the mailing list but in case you missed it here area the relevant Changes00:08
sigmavirus24#link https://review.openstack.org/#/c/161330/00:08
sigmavirus24 #link https://review.openstack.org/#/c/161337/00:08
sigmavirus24One adds logging the other adds notifications from openstack/api-wg00:08
sigmavirus24Please weigh in either on the ML or those changes or both00:08
sigmavirus24If anyone wants to discuss it quickly we can, but I'd like to keep that short00:09
cyeohsounds good to me00:09
elmikono complaints here00:09
sigmavirus24#topic merge the mission?00:09
*** openstack changes topic to "merge the mission? (Meeting topic: api wg)"00:09
sigmavirus24#link https://review.openstack.org/#/c/155911/00:09
sigmavirus24etoews: ?00:10
miguelgrinberg+100:10
*** Yi has quit IRC00:10
sigmavirus24+1 from me00:10
etoewsi think it passes the api wg merge rules at this point.00:10
cyeohyea that has more than enough votes and no negative00:10
etoewscyeoh: care to merge the mission statement?00:10
cyeohsure!00:11
etoewsthanks! i know that was a somewhat painful exercise but i appreciate everyone's patience00:11
sigmavirus24You did good etoews00:11
etoewshopefully it will make for a smoother path00:11
elmikoyea, etoews++00:12
etoews#action update the wiki page with the mission statement00:12
sigmavirus24#topic previous meeting action items00:13
*** openstack changes topic to "previous meeting action items (Meeting topic: api wg)"00:13
sigmavirus24#link http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-02-26-16.00.html00:13
sigmavirus24(There were none from 19 Feb 2015 so I dropped that link)00:13
sigmavirus24kaufer doesn't seem to be around00:13
etoewsalright. i need to duck out now. ciao.00:13
elmikolater00:14
sigmavirus24bye etoews00:14
sigmavirus24miguelgrinberg: I don't recall seeing messages from you on the ML00:14
miguelgrinberghmm, completely forgot about mine, will do this week00:14
sigmavirus24#action kaufer to gather more API-WG consensus on https://review.openstack.org/#/c/147684/5 before bringing it to the ML00:14
sigmavirus24#action miguelgrinberg to get ML feedback on https://review.openstack.org/#/c/141229/00:14
sigmavirus24#action miguelgrinberg to bring tagging guideline to the ML https://review.openstack.org/#/c/155620/00:14
sigmavirus24e0ne and yuriy who aren't even members got their item done ;00:14
sigmavirus24*;)00:14
elmikonice00:15
sigmavirus24I think that'll come up in the next section00:15
sigmavirus24I'll ping kaufer when I see him about his action item tomorrow00:15
sigmavirus24#topic guidelines00:15
*** openstack changes topic to "guidelines (Meeting topic: api wg)"00:15
*** s3wong_ has joined #openstack-meeting-300:15
sigmavirus24     #link https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z00:15
*** s3wong has quit IRC00:15
sigmavirus24#link https://review.openstack.org/15989200:16
sigmavirus24^ That is Yuriy's guideline00:16
sigmavirus24I personally think it needs some help from one of our more experienced guideline authors00:16
sigmavirus24#link https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z00:16
*** Tcs has quit IRC00:16
sigmavirus24(In case meetbot doesn't strip leading whitespace)00:16
*** carl_baldwin_ has joined #openstack-meeting-300:17
sigmavirus24Further I think the guideline should recommend a format for the datetime to be serialized to when returned via the api00:17
elmikoagreed00:17
miguelgrinbergdo you all like UTC vs something like the ISO date format which can support any TZ?00:17
sigmavirus24something like calling datetime_instance.iso8601() would be preferable00:17
*** s3wong__ has joined #openstack-meeting-300:18
sigmavirus24miguelgrinberg: so this is particularly talking about timezone where as the format itself is not defined there00:18
*** s3wong_ has quit IRC00:18
elmikoi like the use of UTC, but having a strong opinion on formatting is nice as well00:18
sigmavirus24That said, I think it's best if all datetimes are returned as the same timezone00:18
miguelgrinbergwell, if everybody speaks ISO then it does not matter00:18
sigmavirus24Right00:18
elmikotrue00:18
*** carl_baldwin has quit IRC00:19
*** carl_baldwin_ is now known as carl_baldwin00:19
miguelgrinbergcan javascript parse ISO dates? I think it can, but not sure00:19
sigmavirus24But still, people using plain old datetime will have trouble00:19
cyeohI think there was some cleanup work around this in Nova last year, but I can't remember what was settled on.00:19
miguelgrinbergmoment.js surely can00:19
sigmavirus24miguelgrinberg: google's closure tools can00:19
sigmavirus24cyeoh: could you research that and comment on the spec?00:19
*** wojdev has quit IRC00:19
cyeohyep, will do00:19
sigmavirus24#action cyeoh to look into how nova handled datetimes and comment on Yuriy's guideline00:20
*** s3wong__ has quit IRC00:20
*** s3wong__ has joined #openstack-meeting-300:20
sigmavirus24Anyone else have guidelines in progress they want to call out?00:21
sigmavirus24miguelgrinberg: elmiko cyeoh ?00:21
elmikonothing as of yet00:21
cyeohnothing from me00:21
miguelgrinbergshould we merge https://review.openstack.org/#/c/131320/?00:22
miguelgrinbergit's been out there for ages00:22
sigmavirus24It doesn't have any -1s00:22
elmikolgtm00:22
cyeohI'd like to get to the point where we can do it, but I know for Nova it will be a while00:23
miguelgrinbergI managed to sneak an implementation of this into Heat :)00:23
cyeohbecause of the requirement to return a list of valid methods00:23
sigmavirus24miguelgrinberg: I recall :D00:23
*** annegentle has joined #openstack-meeting-300:24
*** s3wong__ has quit IRC00:24
sigmavirus24cyeoh: yeah, I expect that'll be v4 of nova (since I'm guessing y'all won't be reusing v3 ;))00:24
*** s3wong has joined #openstack-meeting-300:24
cyeohv3 name is cursed ;-)00:24
miguelgrinbergcyeoh: you say because it is hard to compute the methods associated with a URL?00:24
sigmavirus24What happens if you look in the mirror and say "v3" 3 times?00:24
elmikolol00:25
*** Piet has joined #openstack-meeting-300:25
*** xuhanp has joined #openstack-meeting-300:25
cyeohmiguelgrinberg: yes and I suspect it got even a bit harder with microversions because the response has to reflect the version of the api requested as well00:25
miguelgrinbergcyeoh: okay00:26
cyeohsigmavirus24: mirrors have been known to shatter :-)00:27
*** watanabe_isao has joined #openstack-meeting-300:27
sigmavirus24I'd really like more people to read https://review.openstack.org/#/c/141229/ and discuss it there, so don't feel pressed to read it now and respond00:28
sigmavirus24#link I'd really like more people to read https://review.openstack.org/#/c/141229/00:28
sigmavirus24ugh00:28
miguelgrinbergI was thinking that to support swift's URLs I can stick the /metadata as a prefix, not a suffix. What do you guys think?00:29
miguelgrinbergso it will be recommended as a suffix, but allowed as a prefix as well00:29
elmikosuffix as an option, or just for swift?00:29
elmikoer prefix00:29
miguelgrinbergit would be a prefix when the URL has variable components with slashes, so file system type URLs00:30
elmikoright, makes sense00:30
miguelgrinbergI'll add that and advertise on the ML00:30
sigmavirus24We should probably ask swift to write a guideline on dealing with URLs that have variable components like filenames00:30
miguelgrinbergthey have that, they use HTTP headers00:31
sigmavirus24#action miguelgrinberg to update the metadata guideline and advertise it on the ML00:31
sigmavirus24miguelgrinberg: it just seems like they already feel alienated from the group. so this would be a way of having them feel like their input is wanted00:31
sigmavirus24I'm pretty sure my RFC citing was antagonistic, but hindsight is 20/2000:31
*** edleafe has quit IRC00:32
miguelgrinbergand aws does the same thing, btw00:32
*** edleafe- has joined #openstack-meeting-300:32
elmikoa good move towards inclusion00:32
sigmavirus24We have plenty of time left, should we continue with guidelines or move onto APIImpact?00:33
* sigmavirus24 realizes there's an analogy between heat and himself orchestrating this meeting00:33
*** SridharRamaswamy has quit IRC00:34
sigmavirus24:crickets:00:34
*** carl_baldwin has quit IRC00:34
elmikowe've almost gone through all the guidelines, maybe just finish them out?00:35
sigmavirus24WFm00:35
sigmavirus24https://review.openstack.org/147684 seems to be overall fairly positively received00:36
sigmavirus24#link https://review.openstack.org/14768400:36
elmikovery non-controversial00:36
sigmavirus24it's also been around for a while00:36
*** annegentle has quit IRC00:36
cyeohyea the only issue I had a round it was defining true/false00:38
cyeohbut that can wait till later00:38
elmikoaside from the whole true/false issue, is it ready for merging?00:38
sigmavirus24+100:39
cyeoh+100:39
* sigmavirus24 thinks true/false will be far more controversial00:39
elmikocould be00:39
elmikoi'm +1 for merge too00:39
*** shwetaap has quit IRC00:40
miguelgrinberg+100:40
cyeohok we have enough votes so I'll merge it00:40
sigmavirus24a consensus of 400:40
sigmavirus24;)00:40
sigmavirus24#link https://review.openstack.org/15562000:41
sigmavirus24That's miguelgrinberg's tagging guideline00:41
*** devlaps has quit IRC00:41
sigmavirus24(And the last two are from Sam Harwell when the group started way back when)00:41
elmikoi haven't checked this one out yet00:42
*** david-lyle has quit IRC00:43
cyeohinstance tags is just going through nova queue at the moment. So I'd want to double check consistency00:46
miguelgrinbergcyeoh: it's close, but not identical00:46
*** SridharRamaswamy has joined #openstack-meeting-300:47
miguelgrinbergcyeoh: one thing nova does not have is negative filtering of tags00:47
cyeohok. also I think we'll need to make some statement around naming beyond what we have - eg length, unicode, etc to avoid issues we've had in the past where we break because some unicode characters aren't supported by mysql00:47
elmikolooks pretty solid on a first readthrough, i can already see that the swift folks probably wouldn't like the .../tags endpoint00:47
miguelgrinbergelmiko: same as with /metadata, yeah00:48
elmikoi wonder if between this and the metadata there is room to expand on the whole prefix/suffix endpoint thing and make it a more general guideline?00:48
sigmavirus24elmiko: right and their opinions should be heard, but they seem to have checked out already00:48
sigmavirus24elmiko: I was thinking the same thing00:49
elmikosigmavirus24: total agreement about hearing their opinions00:49
miguelgrinbergmaybe a guideline on how to work with dynamic/variable-length resource URLs00:49
elmikoright00:49
elmikothen we could avoid having that language in the metdata and tag guidelines00:49
miguelgrinbergcan we ask them to kick that off?00:50
elmikoif they're amenable to the idea, sure00:50
miguelgrinbergthey are the experts00:50
elmikowe might have to build some bridges back into the swift community though :/00:50
*** lhcheng has left #openstack-meeting-300:50
elmikoor at the least mend them00:51
*** fischerw has quit IRC00:51
sigmavirus24yep00:51
miguelgrinbergno permanent damage has been done, we haven't merged anything they dislike00:51
elmikocool00:51
miguelgrinbergyet00:52
elmikohehe ;)00:52
miguelgrinberg:)00:52
sigmavirus24Oh shoot00:52
sigmavirus248 minutes left00:52
sigmavirus24APIImpact?00:52
miguelgrinbergshould we discuss versions?00:52
miguelgrinbergor do we leave that for another day?00:52
miguelgrinbergI mean versions for services behind proxies00:52
elmikocan we cover it in the remaining time?00:53
*** Brainspackle has left #openstack-meeting-300:53
miguelgrinbergnot sure, have you guys seen sigmavirus24's email on the ML?00:53
sigmavirus24miguelgrinberg: heh00:53
* notmyname will be happy to talk about swift things00:53
notmynameI haven't commented because I haven't seen things00:54
sigmavirus24Hi notmyname !00:54
elmikomiguelgrinberg: not sure, what was it tagged under?00:54
sigmavirus24elmiko: lots of tags including [glance] and [all]00:54
sigmavirus24It's less ofa question for us though I think00:54
miguelgrinbergelmiko: [api] I think, it's about reporting base URLs when the service is behind a proxy00:54
* sigmavirus24 is more interested in talking to notmyname 00:54
elmikoi don't think i've read it00:54
elmikosigmavirus24: yea, that might be more productive at this point00:55
miguelgrinbergyes00:55
*** claired has quit IRC00:55
notmynamesigmavirus24: I just got back online for a little while, and it looks like your meeting time is almost up. what irc channel do the api wg people lurk in?00:55
sigmavirus24#openstack-api00:55
sigmavirus24We just made it today00:55
*** Yi has joined #openstack-meeting-300:55
sigmavirus24So tl;dr on miguelgrinberg's topic: if a service is behind a proxy it reports the wrong version urls00:57
miguelgrinbergit should report the proxy's root URL, not its own00:58
*** chuckC_ has quit IRC00:58
sigmavirus24Correct00:58
sigmavirus24There's an RFC that was published recently defining de jure headers to be sent by proxies00:59
sigmavirus24But the de facto ones are the ones we'll likely see and want to standardize around for now00:59
sigmavirus24(While also supporting proxies that are RFC compliant)00:59
sigmavirus24(Also hattip to miguelgrinberg for finding that RFC)00:59
miguelgrinbergI have an awesome teacher :)00:59
sigmavirus24tl;dr, Glance found it first and I'm going to write a better fix00:59
sigmavirus245 s00:59
sigmavirus24#endmeeting01:00
*** openstack changes topic to "Zuul check queue stuck due to reboot maintenance window at one of our cloud providers - no need to recheck changes at the moment, they won't move forward."01:00
openstackMeeting ended Thu Mar  5 01:00:00 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-03-05-00.00.html01:00
sigmavirus24ON THE NOSE01:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-03-05-00.00.txt01:00
openstackLog:            http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-03-05-00.00.log.html01:00
sigmavirus24\o/01:00
* sigmavirus24 shouldn't be so proud01:00
sigmavirus24Thanks everyone01:00
elmikosigmavirus24: thanks!01:00
cyeoh cya!01:00
sigmavirus24bye01:01
sigmavirus24you're welcome elmiko01:01
*** elmiko has left #openstack-meeting-301:02
*** yamamoto has quit IRC01:04
*** carl_baldwin has joined #openstack-meeting-301:07
*** markvoelker has joined #openstack-meeting-301:08
*** SumitNaiksatam has quit IRC01:11
*** markvoelker has quit IRC01:13
*** annegentle has joined #openstack-meeting-301:15
*** markvoelker has joined #openstack-meeting-301:15
*** salv-orlando has quit IRC01:16
*** annegentle has quit IRC01:16
*** s3wong has quit IRC01:16
*** annegentle has joined #openstack-meeting-301:16
*** tqtran has joined #openstack-meeting-301:20
*** markvoelker has quit IRC01:20
*** tqtran has left #openstack-meeting-301:20
*** hareeshp has joined #openstack-meeting-301:22
*** carl_baldwin has quit IRC01:27
*** hareeshp has quit IRC01:27
*** annegentle has quit IRC01:27
*** amotoki has joined #openstack-meeting-301:35
*** stanzgy has joined #openstack-meeting-301:35
*** stanzgy_ has joined #openstack-meeting-301:35
*** Yi has quit IRC01:59
*** mwang2__ has quit IRC02:06
*** Networkn3rd has joined #openstack-meeting-302:06
*** vishwana_ has joined #openstack-meeting-302:16
*** enikanorov_ has joined #openstack-meeting-302:16
*** Longgeek has joined #openstack-meeting-302:16
*** obondarev_ has joined #openstack-meeting-302:16
*** markvoelker has joined #openstack-meeting-302:16
*** bpokorny_ has joined #openstack-meeting-302:17
*** jgrimmn has joined #openstack-meeting-302:20
*** abramley_ has joined #openstack-meeting-302:20
*** bpokorny has quit IRC02:20
*** fesp has joined #openstack-meeting-302:20
*** flaper87 has quit IRC02:21
*** abramley has quit IRC02:21
*** zz_jgrimm has quit IRC02:21
*** vishwanathj has quit IRC02:21
*** reed has quit IRC02:21
*** obondarev has quit IRC02:21
*** enikanorov__ has quit IRC02:21
*** jgrimmn has quit IRC02:21
*** jgrimmn has joined #openstack-meeting-302:21
*** fesp has quit IRC02:21
*** fesp has joined #openstack-meeting-302:21
*** abramley_ is now known as abramley02:21
*** fesp is now known as flaper8702:21
*** markvoelker has quit IRC02:21
*** coolsvap_ is now known as coolsvap02:22
*** Longgeek has quit IRC02:22
*** hareeshp has joined #openstack-meeting-302:23
*** Longgeek has joined #openstack-meeting-302:24
*** Longgeek has quit IRC02:25
*** Longgeek has joined #openstack-meeting-302:25
*** SridharRamaswamy has quit IRC02:25
*** ChuckC has joined #openstack-meeting-302:26
*** VW_ has joined #openstack-meeting-302:30
*** reed has joined #openstack-meeting-302:32
*** david-lyle has joined #openstack-meeting-302:33
*** bpokorny has joined #openstack-meeting-302:35
*** reed has quit IRC02:36
*** reed has joined #openstack-meeting-302:37
*** bpokorny_ has quit IRC02:38
*** coolsvap is now known as coolsvap_02:41
*** bpokorny has quit IRC02:42
*** sarob has joined #openstack-meeting-302:42
*** bpokorny has joined #openstack-meeting-302:43
*** VW_ has quit IRC02:44
*** bpokorny has quit IRC02:47
*** sarob has quit IRC02:47
*** shwetaap has joined #openstack-meeting-302:49
*** Yi has joined #openstack-meeting-302:52
*** Yi has quit IRC02:59
*** yamahata has quit IRC03:00
*** ChuckC has quit IRC03:01
*** ChuckC has joined #openstack-meeting-303:06
*** david-lyle has quit IRC03:07
*** eghobo has quit IRC03:08
*** markvoelker has joined #openstack-meeting-303:17
*** markvoelker has quit IRC03:22
*** badveli has quit IRC03:27
*** yamamoto has joined #openstack-meeting-303:28
*** SumitNaiksatam has joined #openstack-meeting-303:32
*** watanabe_isao has quit IRC03:35
*** SumitNaiksatam has quit IRC03:38
*** yamamoto has quit IRC03:41
*** Networkn_ has joined #openstack-meeting-303:42
*** Networkn3rd has quit IRC03:44
*** sigmavirus24 is now known as sigmavirus24_awa03:47
*** VW_ has joined #openstack-meeting-303:52
*** watanabe_isao has joined #openstack-meeting-303:52
*** VW_ has quit IRC03:52
*** VW_ has joined #openstack-meeting-303:53
*** yamamoto has joined #openstack-meeting-303:54
*** Yi has joined #openstack-meeting-304:00
*** shwetaap has quit IRC04:04
*** Yi has quit IRC04:04
*** shwetaap has joined #openstack-meeting-304:05
*** SumitNaiksatam has joined #openstack-meeting-304:08
*** alexsyip has joined #openstack-meeting-304:13
*** alexsyip has quit IRC04:14
*** reed has quit IRC04:15
*** alexsyip has joined #openstack-meeting-304:15
*** alexsyip has quit IRC04:16
*** salv-orlando has joined #openstack-meeting-304:16
*** yamamoto has quit IRC04:17
*** markvoelker has joined #openstack-meeting-304:19
*** salv-orlando has quit IRC04:21
*** yamahata has joined #openstack-meeting-304:22
*** markvoelker has quit IRC04:23
*** ivar-lazzaro has joined #openstack-meeting-304:24
*** ivar-laz_ has quit IRC04:27
*** ivar-lazzaro has quit IRC04:29
*** yamamoto has joined #openstack-meeting-304:30
*** sulo has quit IRC04:33
*** yamamoto_ has joined #openstack-meeting-304:43
*** yamamoto has quit IRC04:43
*** sulo has joined #openstack-meeting-304:43
*** sarob has joined #openstack-meeting-304:44
*** vishy has quit IRC04:47
*** yamamoto_ has quit IRC04:48
*** sarob has quit IRC04:49
*** VW_ has quit IRC04:52
*** shwetaap has quit IRC04:54
*** eghobo has joined #openstack-meeting-304:57
*** melwitt has quit IRC04:59
*** shwetaap has joined #openstack-meeting-304:59
*** Yi has joined #openstack-meeting-305:01
*** Yi has quit IRC05:07
*** carl_baldwin has joined #openstack-meeting-305:08
*** carl_baldwin has quit IRC05:08
*** shwetaap has quit IRC05:10
*** stendulker has joined #openstack-meeting-305:13
*** yamamoto has joined #openstack-meeting-305:17
*** yalie1 has quit IRC05:19
*** markvoelker has joined #openstack-meeting-305:20
*** markmcclain has quit IRC05:20
*** markmcclain has joined #openstack-meeting-305:22
*** markvoelker has quit IRC05:25
*** vishwana_ has quit IRC05:35
*** eghobo has quit IRC05:39
*** eghobo has joined #openstack-meeting-305:39
*** eghobo_ has joined #openstack-meeting-305:47
*** eghobo has quit IRC05:51
*** alexsyip has joined #openstack-meeting-305:57
*** yalie has joined #openstack-meeting-306:01
*** stendulker_ has joined #openstack-meeting-306:04
*** stendulker has quit IRC06:06
*** ttx has quit IRC06:07
*** lazy_prince has quit IRC06:08
*** killer_prince has joined #openstack-meeting-306:08
*** killer_prince is now known as lazy_prince06:08
*** ttx has joined #openstack-meeting-306:19
*** stendulker has joined #openstack-meeting-306:19
*** hareeshp has quit IRC06:19
*** markvoelker has joined #openstack-meeting-306:22
*** stendulker_ has quit IRC06:23
*** markvoelker has quit IRC06:27
*** kun_huang has joined #openstack-meeting-306:36
*** e0ne has joined #openstack-meeting-306:36
*** e0ne has quit IRC06:38
*** e0ne has joined #openstack-meeting-306:42
*** e0ne has quit IRC06:43
*** Yi has joined #openstack-meeting-306:51
*** Yi has quit IRC06:58
*** nkrinner has joined #openstack-meeting-307:07
*** zz_ttrifonov is now known as ttrifonov07:12
*** salv-orlando has joined #openstack-meeting-307:14
*** gcb has joined #openstack-meeting-307:16
*** salv-orlando has quit IRC07:19
*** markvoelker has joined #openstack-meeting-307:22
*** evgenyf has joined #openstack-meeting-307:24
*** salv-orlando has joined #openstack-meeting-307:27
*** markvoelker has quit IRC07:28
*** pkoniszewski has joined #openstack-meeting-307:34
*** mrmartin has joined #openstack-meeting-307:35
*** killer_prince has joined #openstack-meeting-307:37
*** lazy_prince has quit IRC07:38
*** killer_prince is now known as lazy_prince07:38
*** mrmartin has quit IRC07:39
*** sarob has joined #openstack-meeting-307:47
*** ttrifonov is now known as zz_ttrifonov07:50
*** sarob has quit IRC07:53
*** scheuran has joined #openstack-meeting-307:56
*** eghobo_ has quit IRC07:58
*** mwang2 has joined #openstack-meeting-308:02
*** mwang2 has quit IRC08:07
*** matrohon has joined #openstack-meeting-308:08
*** sergef has joined #openstack-meeting-308:09
*** wojdev has joined #openstack-meeting-308:09
*** gcb has quit IRC08:10
*** sandr8 has joined #openstack-meeting-308:14
*** jtomasek has joined #openstack-meeting-308:15
*** wojdev has quit IRC08:20
*** markvoelker has joined #openstack-meeting-308:25
*** sahid has joined #openstack-meeting-308:26
*** markvoelker has quit IRC08:29
*** takadayuiko has joined #openstack-meeting-308:31
*** alexsyip has quit IRC08:32
*** salv-orlando has quit IRC08:33
*** ttx has quit IRC08:34
*** ttx has joined #openstack-meeting-308:34
*** MaxV has joined #openstack-meeting-308:35
*** zz_ttrifonov is now known as ttrifonov08:38
*** wojdev has joined #openstack-meeting-308:40
*** Yi has joined #openstack-meeting-308:42
*** sbalukoff has quit IRC08:43
*** gulic has joined #openstack-meeting-308:45
*** Yi has quit IRC08:47
*** cyeoh has quit IRC08:49
*** JeanBriceCombebi has joined #openstack-meeting-308:52
*** jcoufal has joined #openstack-meeting-308:54
*** sbalukoff has joined #openstack-meeting-308:55
*** salv-orlando has joined #openstack-meeting-309:05
*** JeanBriceCombebi has quit IRC09:06
*** yamahata has quit IRC09:07
*** watanabe_isao has quit IRC09:15
*** wojdev has quit IRC09:24
*** markvoelker has joined #openstack-meeting-309:26
*** wojdev has joined #openstack-meeting-309:28
*** markvoelker has quit IRC09:31
*** stanzgy_ has quit IRC09:40
*** stanzgy has quit IRC09:40
*** stendulker has quit IRC09:44
*** igordcard has joined #openstack-meeting-309:49
*** sarob has joined #openstack-meeting-309:50
*** sahid has quit IRC09:53
*** sahid has joined #openstack-meeting-309:53
*** sahid has quit IRC09:53
*** sahid has joined #openstack-meeting-309:54
*** sarob has quit IRC09:54
*** salv-orlando has quit IRC09:59
*** safchain has joined #openstack-meeting-310:00
*** wendar has quit IRC10:06
*** yapeng has quit IRC10:09
*** yushiro has joined #openstack-meeting-310:12
*** wendar has joined #openstack-meeting-310:16
*** markmcclain has quit IRC10:22
*** markmcclain has joined #openstack-meeting-310:26
*** e0ne has joined #openstack-meeting-310:26
*** e0ne is now known as e0ne_10:26
*** markvoelker has joined #openstack-meeting-310:27
*** e0ne_ has quit IRC10:27
*** e0ne has joined #openstack-meeting-310:27
*** markvoelker has quit IRC10:31
*** takadayuiko has quit IRC10:32
*** Yi has joined #openstack-meeting-310:33
*** dstanek has quit IRC10:33
*** leifz has quit IRC10:34
*** alexpilotti has joined #openstack-meeting-310:34
*** Yi has quit IRC10:38
*** wojdev has quit IRC10:44
*** wojdev has joined #openstack-meeting-310:46
*** yushiro has quit IRC10:49
*** egallen has joined #openstack-meeting-310:55
*** lazy_prince is now known as killer_prince10:57
*** salv-orlando has joined #openstack-meeting-311:00
*** e0ne is now known as e0ne_11:00
*** xuhanp has quit IRC11:04
*** e0ne_ has quit IRC11:11
*** e0ne has joined #openstack-meeting-311:14
*** mrunge has joined #openstack-meeting-311:26
*** markvoelker has joined #openstack-meeting-311:28
*** wojdev has quit IRC11:32
*** markvoelker has quit IRC11:32
*** salv-orlando has quit IRC11:42
*** Yi has joined #openstack-meeting-311:50
*** Yi has quit IRC11:56
*** Yi has joined #openstack-meeting-312:13
*** egallen has quit IRC12:16
*** e0ne is now known as e0ne_12:20
*** evgenyf has quit IRC12:21
*** mwagner_lap has quit IRC12:26
*** evgenyf has joined #openstack-meeting-312:26
*** markvoelker has joined #openstack-meeting-312:29
*** e0ne_ has quit IRC12:30
*** MaxV has quit IRC12:31
*** evgenyf has quit IRC12:31
*** markvoelker has quit IRC12:34
*** jcoufal_ has joined #openstack-meeting-312:34
*** evgenyf has joined #openstack-meeting-312:37
*** jcoufal has quit IRC12:37
*** markvoelker has joined #openstack-meeting-312:38
*** coolsvap_ has quit IRC12:38
*** Yi has quit IRC12:42
*** coolsvap_ has joined #openstack-meeting-312:46
*** wojdev has joined #openstack-meeting-312:50
*** sarob has joined #openstack-meeting-312:53
*** salv-orlando has joined #openstack-meeting-312:56
*** baoli has joined #openstack-meeting-312:57
*** banix has joined #openstack-meeting-312:57
*** baoli has quit IRC12:57
*** sarob has quit IRC12:57
*** mwagner_lap has joined #openstack-meeting-313:01
*** baoli has joined #openstack-meeting-313:06
*** jckasper has quit IRC13:08
*** yamamoto has quit IRC13:13
*** sahid has quit IRC13:15
*** sahid has joined #openstack-meeting-313:15
*** amotoki has quit IRC13:21
*** [1]evgenyf has joined #openstack-meeting-313:22
*** evgenyf has quit IRC13:25
*** [1]evgenyf is now known as evgenyf13:25
*** e0ne has joined #openstack-meeting-313:29
*** banix has quit IRC13:31
*** egallen has joined #openstack-meeting-313:34
*** Yi has joined #openstack-meeting-313:37
*** yamamoto has joined #openstack-meeting-313:37
*** Yi has quit IRC13:43
*** _crobertsrh has quit IRC13:45
*** crobertsrh has joined #openstack-meeting-313:45
*** dstanek has joined #openstack-meeting-313:46
*** crobertsrh has quit IRC13:46
*** erikmwilson has joined #openstack-meeting-313:47
*** jckasper has joined #openstack-meeting-314:01
*** edleafe- is now known as edleafe14:04
*** shwetaap has joined #openstack-meeting-314:08
*** cbader has joined #openstack-meeting-314:09
*** Yi has joined #openstack-meeting-314:10
*** sahid has quit IRC14:10
*** wojdev has quit IRC14:10
*** banix has joined #openstack-meeting-314:11
*** sahid has joined #openstack-meeting-314:15
*** peristeri has joined #openstack-meeting-314:17
*** lblanchard has joined #openstack-meeting-314:18
*** amotoki has joined #openstack-meeting-314:23
*** mrmartin has joined #openstack-meeting-314:24
*** wojdev has joined #openstack-meeting-314:27
*** VW_ has joined #openstack-meeting-314:28
*** shwetaap1 has joined #openstack-meeting-314:28
*** shwetaap has quit IRC14:31
*** mattfarina has joined #openstack-meeting-314:35
*** jgrimmn has quit IRC14:38
*** maurosr has quit IRC14:38
*** pkoniszewski has quit IRC14:39
*** absubram has joined #openstack-meeting-314:39
*** jgrimm has joined #openstack-meeting-314:39
*** annegentle has joined #openstack-meeting-314:39
*** maurosr has joined #openstack-meeting-314:41
*** leifz has joined #openstack-meeting-314:41
*** thangp has joined #openstack-meeting-314:41
*** jgrimm has quit IRC14:44
*** maurosr has quit IRC14:44
*** jgrimm has joined #openstack-meeting-314:45
*** wojdev has quit IRC14:46
*** maurosr has joined #openstack-meeting-314:46
*** chuckC_ has joined #openstack-meeting-314:46
*** e0ne is now known as e0ne_14:47
*** chuckC_ has quit IRC14:48
*** thomasem has joined #openstack-meeting-314:50
*** ttrifonov is now known as zz_ttrifonov14:50
*** thomasem has quit IRC14:51
*** sahid has quit IRC14:51
*** sahid has joined #openstack-meeting-314:53
*** sahid has quit IRC14:53
*** yamamoto has quit IRC14:53
*** sahid has joined #openstack-meeting-314:53
*** thomasem has joined #openstack-meeting-314:55
*** johnbelamaric has joined #openstack-meeting-314:55
*** mrsmith has joined #openstack-meeting-314:57
*** jckasper has quit IRC14:57
*** carl_baldwin has joined #openstack-meeting-314:57
*** tidwellr has joined #openstack-meeting-314:58
*** mlavalle has joined #openstack-meeting-314:59
*** sigmavirus24_awa is now known as sigmavirus2414:59
*** yamamoto has joined #openstack-meeting-314:59
carl_baldwinhi15:00
mlavallehi15:00
yamamotohi15:00
pavel_bondarhi15:00
mrsmithhiya15:00
johnbelamarichello15:00
tidwellrhi15:00
salv-orlandoaloha15:00
*** pc_m has joined #openstack-meeting-315:00
*** jckasper has joined #openstack-meeting-315:00
pc_mhi15:00
carl_baldwin#startmeeting neutron_l315:01
openstackMeeting started Thu Mar  5 15:01:15 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:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:01
openstackThe meeting name has been set to 'neutron_l3'15:01
carl_baldwin#topic Announcements15:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:01
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam15:01
carl_baldwinJust two weeks until Kilo-3.  It is flying by isn’t it?15:01
carl_baldwin#topic Bugs15:02
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:02
carl_baldwinAny new bugs to be aware of?15:02
*** dboik has joined #openstack-meeting-315:02
*** erikmwilson has quit IRC15:02
haleybhttps://bugs.launchpad.net/neutron/+bug/1428305 :)15:03
openstackLaunchpad bug 1428305 in neutron "Floating IP namespace not created when DVR enabled" [Undecided,New] - Assigned to Brian Haley (brian-haley)15:03
haleybbut i've identified two patches that fix it15:03
carl_baldwinhaleyb: Good progress.  Are the patches up?15:04
haleybthey're cisco's ipv6 patches15:04
carl_baldwinhaleyb: You confirmed that it is only with ipv6 enabled?15:05
carl_baldwinhaleyb: How much work will it be to write tests for the issue?15:05
haleybyes, with ipv6 and dvr, so it needs multiple things turned-on15:05
*** baoli has quit IRC15:05
haleybi know nothing about the dvr job, but perhaps we should enable ipv6 with it eventually15:06
salv-orlandocarl_baldwin, haleyb: that should be a test executed as part of the dvr job. But I wonder if we isolate the failure mode correctly, would it be possible to add a functional test for this?15:06
salv-orlandoI don't think we explicitly need to enable ipv6 on a job. We need to add an ipv6-specific test.15:07
HenryGhaleyb: note the ipv6 patches are community work, not cisco's :)15:07
*** e0ne_ is now known as e0ne15:08
salv-orlandohaleyb: from the bug report it pretty much seems dvr is totally broken when using ipv6?15:08
carl_baldwinsalv-orlando: Good point.  I think even having ipv6 enabled in the job might’ve caught this.15:08
*** banix has quit IRC15:08
haleybsalv-orlando: floating ip's are what's broken as the fip- namespace is never created, for ipv6 to work we need all those "community" patches :)15:09
*** jschwarz has joined #openstack-meeting-315:09
haleybwe can probably create a functional test to add two subnets and see if the namespace is created15:09
*** baoli__ has joined #openstack-meeting-315:10
salv-orlandohaleyb: that sounds reasonable. But in order to repro the issue all you have to do is to attach a v4 floating IP on a DVR linking it to a V6 internal address?15:10
HenryGI think sc68cal is working towards making 4+6 the default in devstack (and hence all jobs)15:10
sc68calyup15:11
salv-orlandosc68cal: basically by making the "private" network v6?15:11
haleybsalv-orlando: the VM is dual-stack, problem is the l3-agent doesn't deal with multiple subnets on the gateway port properly15:11
sc68calsalv-orlando: the private network will have an RFC1918 IPv4 subnet associated, and an IPv6 subnet from the ULA prefix15:12
carl_baldwinsalv-orlando: IOW, I don’t think we even need ipv6 addresses involved to break ipv4.  Just enabling it for the stack breaks it.15:12
sc68calhttps://bugs.launchpad.net/neutron/+bug/140172815:12
openstackLaunchpad bug 1401728 in neutron "Routing updates lost when multiple IPs attached to router" [Medium,In progress] - Assigned to Sean M. Collins (scollins)15:12
salv-orlandocarl_baldwin: I am a bit lost about what do you mean for "enabling it for the stack"15:12
*** nelsnelson has joined #openstack-meeting-315:13
salv-orlandothanks sc68cal, that's a really good thing to do15:13
carl_baldwinsalv-orlando: Just turning on ipv6 in devstack.15:13
carl_baldwinhaleyb: Correct me if I’m wrong.15:13
sc68calWhat happens is the code in the L3 agent gets bad data from the DB layer, we have some code in the db layer to skip ports that have more than one subnet associated with the port15:13
sc68caland it ends up not creating a key in the dictionary the L3 agent accesses, and the whole thing goes kablooowey15:14
salv-orlandocarl_baldwin: ok, I did not recall we needed to explicitly enable it for devstack. I'm trying to understand if this issue affects not only IPv6 users, but also users which build external ipv4 networks using multiple non-contiguous ranges as subnets15:14
sc68calsalv-orlando: it's possbile it does15:15
sc68cal*does affect15:15
carl_baldwinsalv-orlando: Interesting.  My thinking is that it would not because multiple subnets are handled with a different structure, not multiple addresses on each port.15:15
haleybcarl_baldwin: do you mean enabling ipv6 but not on that network?  i think sc68cal has it right wrt multiple subnets15:15
sc68calwhoops carl_baldwin is right, it's multiple addresses15:16
salv-orlandocarl_baldwin: good point.15:16
carl_baldwinsalv-orlando: There is an “extra_subnets” field (or something liket that)15:16
carl_baldwinTo summarize, we need to turn attention to these ipv6 patches mentioned in the bug report.  We also need to work out details for how to test this and/or turn attention to sc68cal ’s effort to enable ipv6 in devstack.15:17
carl_baldwinAnyway, good work haleyb and others on this bug.15:18
carl_baldwinAny other bugs?15:18
*** pkoniszewski has joined #openstack-meeting-315:18
*** ChuckC has quit IRC15:19
carl_baldwin#topic L3 Agent Restructuring15:19
*** openstack changes topic to "L3 Agent Restructuring (Meeting topic: neutron_l3)"15:19
carl_baldwinmlavalle: We got yours merged.15:19
mlavallecarl_baldwin: yeap, I saw that.... thanks for the help :-)15:20
carl_baldwinI’ve got a couple of small patches lined up next and then a couple of medium sized ones.15:20
*** yamahata has joined #openstack-meeting-315:20
pc_mPlease review https://review.openstack.org/#/c/160983/, which fixes VPN UTs as a result of 147744 merged.15:20
carl_baldwinBut, we’re getting to the end of the line.  I looked yesterday and saw just under 40 non-abandoned patches on this topic.  Most have merged.15:21
mlavallecarl_baldwin: I am also adding a funtional test for the namespaces manager. I will push it tonight or tomorrow15:21
carl_baldwin#action carl_baldwin will be sure to review https://review.openstack.org/#/c/160983/ today for pc_m15:21
carl_baldwin^ Encourage others to review too.15:21
pc_mAlso, I have https://review.openstack.org/#/c/160179/ to separate VPN device driver from L3 agent, too.15:21
carl_baldwinpc_m: Ready to go now?15:22
pc_mcarl_baldwin: Thanks, need review of both of these.15:22
pc_mcarl_baldwin: Yes, in fact, I did part 2 changes as well so this is the whole thing.15:22
carl_baldwinpc_m: Thanks.15:22
pc_mI made it dependent on the bug fix, so should pass Jenkins.15:22
pc_m160179 depends on 160983, which was waiting on 147741... whew!15:23
carl_baldwinpc_m: :)15:23
carl_baldwinamuller do you have anything?15:23
*** banix has joined #openstack-meeting-315:24
carl_baldwin#topic neutron-ipam15:25
*** openstack changes topic to "neutron-ipam (Meeting topic: neutron_l3)"15:25
carl_baldwinI can’t believe that we have only 2 weeks left.15:25
*** marun has joined #openstack-meeting-315:26
carl_baldwinsalv-orlando: pavel_bondar: johnbelamaric: tidwellr:  How are things going?15:26
salv-orlandomaking progress, even if not as fast as I'd like15:26
tidwellrsame for me15:26
salv-orlandoI've addressed all comments, and completed the subnet allocation part. I need to finish the address pool allocation bits.15:27
salv-orlandoAnd then unit tests - and this bit is done.15:27
salv-orlandoThen we'll have to add functional tests15:27
johnbelamaricpavel_bondar: what remains on the db base refactor?15:27
salv-orlandobut before the functional tests we'll need to integrate the reference driver with pavel_bondar refactoring15:28
pavel_bondarI am no longer marking re-factored db_base as not WIP, so feel free to review #link https://review.openstack.org/#/c/153236/ , however there some amount of work in todo list still15:28
pavel_bondarIt would be nice if we could start integration testing soon15:28
pavel_bondarright now, I have only minor things left to do, improve tests, add rollback for delete_subnet, probably missed something else15:29
*** JeanBriceCombebi has joined #openstack-meeting-315:29
*** amuller has joined #openstack-meeting-315:29
carl_baldwinsalv-orlando: pavel_bondar:  Sounds like we need a plan of attack for integration and testing.15:30
salv-orlandofor testing, the strategy is to have a non-voting job, similar to dvr15:31
carl_baldwinWould it help to meet at another time to discuss this in more depth?15:31
salv-orlandocarl_baldwin: as long as it's IRC it's fine forme.15:31
carl_baldwinWe can also discuss here, didn’t mean to imply that is not an option.15:31
carl_baldwinIRC is fine for me either way.15:31
pavel_bondarok for me too15:32
pavel_bondaronce reference driver is ready, I can rebase on it and turn new IPAM by default, so we will see how many tests are broken in jenkins15:33
salv-orlandocarl_baldwin: it was just because IRC allows me to have meetings also very late in the night. As I don't have to speak I won't wake up anybody15:33
carl_baldwinpavel_bondar: That sounds like a reasonable way to start.15:33
*** armax has quit IRC15:33
*** armax has joined #openstack-meeting-315:34
carl_baldwinsalv-orlando: We’ll strive to be considerate of your time.15:34
carl_baldwinI’m inclined to let salv-orlando stay focused on the remaining address pool allocation bits and set up another time to discuss our testing strategy maybe next week sometime.15:35
salv-orlandoeven monday will work for me15:35
carl_baldwinsalv-orlando: That could work.  I’ll have to check to be sure.15:35
carl_baldwin#action carl_baldwin will find a time we can meet next week about a testing IPAM15:36
carl_baldwintidwellr: Anything to discuss on subnet allocation?15:38
carl_baldwinWe have a good start on tempest tests15:38
carl_baldwin#link https://review.openstack.org/15964415:39
tidwellrsome thoughts on the semantics of updates to the prefix of a pool would be appreciated15:39
carl_baldwinAlso, on python-neutronclient15:39
carl_baldwin#link https://review.openstack.org/15961815:39
tidwellryes, I've seen those15:39
carl_baldwintidwellr: Do you want those thoughts in the review?15:40
tidwellrreview, ML, "offline" in IRC works as well15:40
tidwellrquotas is something I'm starting to worry about a little15:41
tidwellrin the spec it was mentioned that the built-in quota mechanism might not be sufficient for subnet pools15:42
salv-orlandoare quotas the thing that we had so much fun about back in Utah?15:42
carl_baldwintidwellr: Wow, quotas.  I have managed not to think about quotas much at all.15:42
carl_baldwinsalv-orlando: Yes, we had some fun with that.15:42
tidwellryeah, la la la, what quotas? :)15:42
carl_baldwintidwellr: Well, first things first.  Let’s talk about updating the pool a bit.15:43
salv-orlandodo we really want to do that? management-wise is difficult, we know that15:44
salv-orlandobut is there a use case that justifies adding this complexity?15:44
carl_baldwintidwellr: I’m fine if updating a pool completely ignored current allocations.  What do others think?15:44
salv-orlandoI think pools can be extended over time15:44
salv-orlandoso that can be a use case...15:44
tidwellrcarl_baldwin: I was going to propose we not support updates at this time, too complex15:44
*** Yi has quit IRC15:45
carl_baldwintidwellr: What is the complexity?15:45
salv-orlandoin principle I am fine with detaching current allocations from the prefix. But on the other hand how should we handle the situation where one adds a prefix to a pool for which allocations exist in another pool?15:45
carl_baldwintidwellr: Would it be simpler to support only updates that extend the pool but do not take away from it at first?15:46
tidwellrcarl_baldwin: I suppose adding prefixes is not really a problem. Removing prefixes, dealing with existing allocations, compacting the prefix list, that gets messy15:47
carl_baldwinsalv-orlando: That is an interesting thought.15:47
tidwellrsalv-orlando carl_baldwin: prefixes don't have to be unique across pools, is that even a problem?15:48
carl_baldwinsalv-orlando: at one point, I was thinking that — at least initially — we’d only allow one pool per address scope.  So, if two pools overlapped, it would be assumed that the addresses are in different scopes and that would be okay.15:48
tidwellr+115:49
*** stendulker has joined #openstack-meeting-315:49
salv-orlandocarl_baldwin, tidwellr: I reckon in the design it unicity of addresses across pool was configurable.15:49
carl_baldwinsalv-orlando: tidwellr: With ipv4, yes.  With ipv6 they *should* be unique globally.  However, I wasn’t thinking that we would deal with enforcing it.15:49
salv-orlandocarl_baldwin: but perhaps we don't even need it do it now15:50
carl_baldwinsalv-orlando: The configurability was for addresses *within* one pool.15:50
salv-orlandocarl_baldwin: ok15:50
*** sahid has quit IRC15:50
carl_baldwinsalv-orlando: You know how current Neutron allows overlap all over the place.  :)15:50
tidwellrcarl_baldwin: we can easily support extending the prefix pool, so I'll go that route15:51
salv-orlandook let's say one pool for address scope?15:51
carl_baldwinsalv-orlando: Yes.15:51
tidwellrsalv-orlando: yes15:51
carl_baldwinI think the most important use case to support will be extending the pool.  tidwellr: does that make it any easier?15:52
*** egallen has quit IRC15:52
tidwellryes, I had a patch set earlier that supported this15:52
tidwellrwe can chat later about quotas, I don't want to take any more time15:53
carl_baldwintidwellr: Could you be sure to note any restrictions in the commit message so that we and document writers can easily figure out how to present all of this?15:54
carl_baldwintidwellr: Fair enough.  Though we may not want to wait until next week to talk about quotas.15:55
tidwellrI meant today or tomorrow :)15:55
tidwellrbetter commit message coming15:55
carl_baldwintidwellr: Thanks.15:55
carl_baldwinAnything else on IPAM?15:56
carl_baldwin#topic Open Discussion15:57
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)"15:57
*** kozhukalov has joined #openstack-meeting-315:57
mrsmithI have a fip ns delay patch that may help with some of the intermittent failures of the dvr job15:58
mrsmithhttps://review.openstack.org/#/c/151758/15:58
mrsmithits still a WIP15:58
mrsmithbut anyone who wants to take a look and let me know if I am going in the right or wrong direction would be appreciated15:59
mrsmithit tries to delay the deletion of the fip ns and ports to reduce the churn that is seen on the dvr job15:59
mrsmithalso - Rajeev's lock patch may help as well - https://review.openstack.org/#/c/153422/15:59
carl_baldwinmrsmith: Thanks.16:00
carl_baldwin#endmeeting16:00
*** openstack changes topic to "Zuul check queue stuck due to reboot maintenance window at one of our cloud providers - no need to recheck changes at the moment, they won't move forward."16:00
openstackMeeting ended Thu Mar  5 16:00:53 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-03-05-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-03-05-15.01.txt16:00
carl_baldwinThanks everyone.16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-03-05-15.01.log.html16:00
yamamotobye16:01
mlavallehave a nice day all16:01
johnbelamaricbye16:01
*** baoli__ has quit IRC16:01
*** MarkAtwood has joined #openstack-meeting-316:01
*** pc_m has left #openstack-meeting-316:02
*** sahid has joined #openstack-meeting-316:02
*** baoli has joined #openstack-meeting-316:02
*** mrsmith has quit IRC16:02
*** fischerw has joined #openstack-meeting-316:03
*** pkoniszewski has quit IRC16:03
*** amuller has left #openstack-meeting-316:04
*** dboik has quit IRC16:05
*** sahid has quit IRC16:05
*** shwetaap1 has quit IRC16:05
*** sahid has joined #openstack-meeting-316:06
*** carl_baldwin has quit IRC16:08
*** ChuckC has joined #openstack-meeting-316:17
*** MaxV has joined #openstack-meeting-316:17
*** ChuckC has quit IRC16:18
*** ChuckC has joined #openstack-meeting-316:18
*** mrmartin has quit IRC16:19
*** shwetaap has joined #openstack-meeting-316:21
*** stendulker has quit IRC16:23
*** evgenyf has quit IRC16:28
*** salv-orlando has quit IRC16:29
*** chuckC_ has joined #openstack-meeting-316:29
*** chuckC_ has quit IRC16:29
*** david-lyle has joined #openstack-meeting-316:30
*** tidwellr has left #openstack-meeting-316:31
*** jschwarz has quit IRC16:35
*** obondarev_ is now known as obondarev16:36
*** salv-orlando has joined #openstack-meeting-316:39
*** scheuran has quit IRC16:40
*** baoli has quit IRC16:42
*** carl_baldwin has joined #openstack-meeting-316:45
*** Yi has joined #openstack-meeting-316:45
*** yamahata has quit IRC16:50
*** Yi has quit IRC16:50
*** baoli has joined #openstack-meeting-316:51
*** amotoki has quit IRC16:53
*** JeanBriceCombebi has quit IRC17:01
*** JeanBriceCombebi has joined #openstack-meeting-317:02
*** yamamoto has quit IRC17:04
*** vishwanathj has joined #openstack-meeting-317:06
*** vishwanathj has quit IRC17:06
*** baoli has quit IRC17:08
*** bpokorny has joined #openstack-meeting-317:08
*** baoli has joined #openstack-meeting-317:09
*** jaypipes has joined #openstack-meeting-317:09
*** alexsyip has joined #openstack-meeting-317:10
*** yamahata has joined #openstack-meeting-317:12
*** bpokorny has quit IRC17:16
*** bpokorny has joined #openstack-meeting-317:18
*** yamahata has quit IRC17:18
*** yamahata has joined #openstack-meeting-317:19
*** igordcard has quit IRC17:20
*** Longgeek has quit IRC17:22
*** nkrinner has quit IRC17:22
*** gulic has quit IRC17:25
*** vishwanathj has joined #openstack-meeting-317:26
*** absubram has left #openstack-meeting-317:28
*** annegentle has quit IRC17:29
*** matrohon has quit IRC17:34
*** JeanBriceCombebi has quit IRC17:34
*** carl_baldwin_ has joined #openstack-meeting-317:38
*** carl_baldwin has quit IRC17:40
*** carl_baldwin has joined #openstack-meeting-317:42
*** carl_baldwin_ has quit IRC17:43
*** mlavalle has quit IRC17:43
*** safchain has quit IRC17:44
*** Yi has joined #openstack-meeting-317:46
*** sahid has quit IRC17:46
*** mrunge has quit IRC17:47
*** baoli has quit IRC17:49
*** mageshgv has joined #openstack-meeting-317:54
*** ivar-lazzaro has joined #openstack-meeting-317:59
*** lazy_prif has joined #openstack-meeting-317:59
*** lazy_prif is now known as lazy_prince17:59
*** ivar-lazzaro has quit IRC17:59
*** rkukura has joined #openstack-meeting-317:59
*** killer_prince has quit IRC17:59
*** sreshetn1ak has joined #openstack-meeting-317:59
*** ivar-lazzaro has joined #openstack-meeting-317:59
*** songole has joined #openstack-meeting-318:00
*** elmiko has joined #openstack-meeting-318:00
SumitNaiksatamrkukura: ivar-lazzaro songole mageshgv Yi: hi18:01
rkukurahi18:01
mageshgvhi18:01
songoleSumitNaiksatam: hello18:01
ivar-lazzaroSumitNaiksatam: hi18:01
SumitNaiksatamseems like the team is here, lets get started18:01
SumitNaiksatam#startmeeting networking_policy18:01
openstackMeeting started Thu Mar  5 18:01:51 2015 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: networking_policy)"18:01
openstackThe meeting name has been set to 'networking_policy'18:01
*** mwang2 has joined #openstack-meeting-318:01
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/GroupBasedPolicy#March_5th.2C_Feb_26th.2C_19th.2C_12th.2C_201518:02
SumitNaiksatamno announcements from me18:02
SumitNaiksatamanyone like to share anything up front?18:02
SumitNaiksatam#topic Bugs18:03
*** openstack changes topic to "Bugs (Meeting topic: networking_policy)"18:03
SumitNaiksatamso as planned, we had the bug squashing day on Tuesday (March 2nd)18:03
SumitNaiksatam#link https://wiki.openstack.org/wiki/GroupBasedPolicy/kilo-bug-squash#Pending_bugs_on_master_.28and_require_backport.2918:03
SumitNaiksatamas you can see we fixed most of what we had planned to and managed to back port as well18:03
SumitNaiksatamBIG thanks to everyone for participating18:04
SumitNaiksatamthere was an issue with the gate starting that evening18:04
*** elmiko has left #openstack-meeting-318:04
SumitNaiksatamand at one point mageshgv and I noticed that at least our stable branch patches we kicked out of the zuul queue18:04
*** baoli has joined #openstack-meeting-318:05
SumitNaiksatamso if you are noticing that your patch has not been voted on for a long time by Jenkins, always check status.openstack.org/zuul18:05
SumitNaiksatamto see if its in the queue18:05
*** baoli has quit IRC18:06
SumitNaiksatamif not, you can retrigger it by putting “recheck” on the patch18:06
*** sbalukoff has quit IRC18:06
SumitNaiksatamalso one of the patches was in the merge queue and got bumped out18:06
SumitNaiksatamso I had to do a +A again to get it back into the merge queue18:06
SumitNaiksatamrecheck was not enough18:07
*** yapeng has joined #openstack-meeting-318:07
rkukurareverify?18:07
*** alexsyip has quit IRC18:07
*** baoli has joined #openstack-meeting-318:07
SumitNaiksatamrkukura: i dont think reverify is supported anymore, at least i did not find it on the wiki page (but i might not be looking at the right place)18:07
*** LouisF has joined #openstack-meeting-318:08
SumitNaiksatamrkukura: i think, reverify and recheck probably mean the same thing now, but i dont want to misinform folks here18:08
*** eghobo has joined #openstack-meeting-318:08
*** baoli_ has joined #openstack-meeting-318:08
SumitNaiksatamlastly, if your patch is in the zuul queue, it might take a long time for you to get back the jenkins vote, since the queue has been pretty deep18:08
SumitNaiksatamin general, on the proccess, please feel free to check on #openstack-gbp any time you run into issues like these (or you can directly ask on #openstack-infra)18:09
SumitNaiksatamthe list of bugs that we fixed on the bug squash is prioritized subset of the pending buga18:09
SumitNaiksatam*bugs18:09
SumitNaiksatamwe still need to take of the other pending bugs18:10
rkukuraI expect to have a patch for the last remaining bug squash bug, https://bugs.launchpad.net/group-based-policy/+bug/1416177, today18:10
openstackLaunchpad bug 1416177 in Group Based Policy " ptg wrongly created with null subnet, cannot be deleted either" [Medium,In progress] - Assigned to Robert Kukura (rkukura)18:10
*** KrishnaK has joined #openstack-meeting-318:10
SumitNaiksatamrkukura: sweet!18:10
SumitNaiksatamper rkukura’s suggestion last week, if we are able to get most of the prioritized bugs fixed and backported, we will do a new stable/juno release end of this weekend18:11
SumitNaiksatamany comments/questions on the above?18:11
*** baoli has quit IRC18:11
SumitNaiksatamis jishnu here?18:12
rkukurahe’s logging in now18:12
SumitNaiksatamrkukura: ah okay18:12
*** jtomasek has quit IRC18:12
SumitNaiksatamso jishnu has a uploaded a scenario testing library to pypi for running GBP tests18:13
SumitNaiksatamthis is an interim step while we enable these tests via the upstream gate18:13
SumitNaiksatami was hoping jishnu would have been able to summarize how to use this library18:13
*** jishnu has joined #openstack-meeting-318:14
SumitNaiksatamah right on cue18:14
jishnuhi18:14
SumitNaiksatamjishnu: hi, we were just discussing about your pypi lib18:14
SumitNaiksatamjishnu: can you summarize for the team here how to use it?18:14
jishnuSure18:14
jishnuThe are the steps:18:15
jishnupip install noirogbptests18:15
*** e0ne has quit IRC18:15
*** SridharRamaswamy has joined #openstack-meeting-318:15
SumitNaiksatamjishnu: still there?18:16
jishnupkg will wil be installed at18:16
jishnu /usr/lib/python2.7/site-packages/noirogbptests/ (for RHEL)18:16
SumitNaiksatamok18:17
jishnuhi18:17
jishnuLooks like my previous msgs did not appear18:17
jishnuLet me repeat again .. sorry folks18:18
*** songole has quit IRC18:18
jishnupip install noirogbptests18:18
*** jcoufal_ has quit IRC18:18
jishnupkg will be installed in:18:18
jishnu /usr/lib/python2.7/site-packages/noirogbptests/ (for RHEL)18:18
jishnu /usr/local/lib/python2.7/dist-packages/noirogbptests/ (for Ubuntu)18:18
jishnu# Usage: User can run each test-script or entire test-suite(suite_run.py) in any of two ways: #        1. If the default location of the package is appended to the $PATH #           then executable files can be run rom anywhere #        2. The executable can be run from the default location # # Test Report: Depending on the location from where the suite is run, a file "test_reports.txt" #              get created in that18:19
SumitNaiksatamjishnu: ok good, perhaps its a good idea to post these instructions on a wiki page, and point from the main GBP wiki page18:19
jishnuyes .. i shall put it there18:20
SumitNaiksatamjishnu: thanks, sorry to put you on the spot ;-)18:20
jishnufolks: it takes 5 mins 10-12 secs to finish 52 functonal testcases18:20
SumitNaiksatamjishnu: ok good to know18:21
SumitNaiksatamthese are end to end tempest scenario like tests18:21
SumitNaiksatamjishnu: so the requirement is that devstack be installed before running these, right?18:21
ivar-lazzaroare the testcase defined on the library itself?18:21
ivar-lazzaroshould we include them upstream instead?18:22
jishnuyes.. devstack needs to be installed first18:22
banixcould these become part of the tree?18:22
banixis that the plan eventually?18:22
SumitNaiksatambanix: yes18:22
jishnuAs Sumit mentioned, I will put the instructions clearly in the Wiki..18:22
SumitNaiksatamivar-lazzaro: yes, we should upstream this18:22
SumitNaiksatamso banix ivar-lazzaro on that -18:22
SumitNaiksatami have started the process of triggering an upstream gate job to run GBP functional tests18:23
SumitNaiksatamhave posted two patches:18:23
SumitNaiksatam#link https://review.openstack.org/#/c/161511/18:23
SumitNaiksatamthat one is in infra18:23
SumitNaiksatamand: #link https://review.openstack.org/#/c/161532/18:23
SumitNaiksatamin GBP18:23
*** SumitNaiksatam has quit IRC18:24
banixnice18:24
ivar-lazzarogood!18:24
ivar-lazzarojust wondering, do they give you the ability to define arbitrary topologies? Or is it all single node testing?18:25
yapenggreat, how to run the functional test, is there any instruction?18:26
jishnuits is topology agnostic..18:26
*** SumitNaiksatam has joined #openstack-meeting-318:28
SumitNaiksatamsorry i got disconnected18:28
SumitNaiksatamany other bugs we need to discuss in this meeting?18:29
SumitNaiksatam #topic Re-factor Group Based Policy with Neutron RESTful APIs18:29
SumitNaiksatamYi: yapeng: over to you18:29
SumitNaiksatamhow is this coming along?18:29
Yialmost done..18:30
Yithe client and api are ready18:30
jishnuAs the datapath testcases are getting developed, the approach taken is: presence of two end-points agnostic of their location(so that you can run the same set of tests in two nodes or single node)18:30
SumitNaiksatamYi: wow! :-)18:30
SumitNaiksatamjishnu: ok good to know18:30
Yiwe are working on the refactoring the RMD and UT cade18:30
*** annegentle has joined #openstack-meeting-318:31
SumitNaiksatamYi: you ran into some issues with the latest merged patches?18:31
Yiit was done. -- As some new test cases were introduced in recent bug fixes, we are working on patching them18:31
SumitNaiksatamYi: ok18:32
SumitNaiksatamso in terms of review, we are discussing the following chaing of patches:18:32
SumitNaiksatam#link https://review.openstack.org/#/c/15972518:32
SumitNaiksatam#link https://review.openstack.org/#/c/156776/18:32
SumitNaiksatam#link https://review.openstack.org/#/c/156856/18:32
YiSumitNaiksatam: correct18:33
SumitNaiksatami did one pass of quick reviews over the former two patches18:33
yapengthe first link is ready for review.18:33
Yithe first two are ready18:33
SumitNaiksatamyapeng: ah good to know18:33
Yithe last one is almost...18:33
SumitNaiksatamyapeng: yi, apart from the UTs, have you tested this in a devstack setup?18:33
Yiyes, we did.18:34
SumitNaiksatamYi: sweet!!18:34
yapengyes, last week I did test against devstack18:34
SumitNaiksatamyapeng: nice!18:34
YiI have not got a chance to test the external segment in devstack18:34
Yibut otherwise, it seems fine18:34
*** MarkAtwood has quit IRC18:35
SumitNaiksatamYi: okay, ivar-lazzaro and I can help you with that18:35
YiSumitNaiksatam: ivar-lazzaro: Thanks!18:35
SumitNaiksatamwould really appreciate if the rest of the team can help review these patches18:35
rkukuraSumitNaiksatam: will do18:35
SumitNaiksatamYi: and yapeng have been working pretty hard on this, and we owe them some good feedback at the earliest18:35
SumitNaiksatamrkukura: great, thanks!18:35
YiWill do one more round test in devstack once we finish pacthing the RMD and UT.18:36
mageshgvSumitNaiksatam: sure, will review these18:36
SumitNaiksatammageshgv: thanks18:36
SumitNaiksatamyapeng: Yi: do you have any blockers at this point?18:36
Yirkukura: mageshgv: Thanks!18:36
YiSumitNaiksatam: So far so good18:36
yapengSumitNaiksatam: not at this moment18:36
SumitNaiksatamYi: yapeng: great to hear that, so lets focus our attention on reviewing and testing these18:37
SumitNaiksatamany other questions for Yi and yapeng at this point?18:37
yapengSumitNaiksatam: ok18:37
Yigreat!18:37
SumitNaiksatamyapeng: yi: thanks much for your work on this!18:38
SumitNaiksatam#topic Floating IP support18:38
*** openstack changes topic to "Floating IP support (Meeting topic: networking_policy)"18:38
SumitNaiksatamthere were lots of good discussions on this since rkukura is in town, and some of us were meeting18:39
SumitNaiksatammost of the discussions were sparked by rkukura’s comments on the latest patch set:18:40
SumitNaiksatam#link https://review.openstack.org/#/c/157298/2/specs/kilo/gbp-floating-ip-support.rst18:40
SumitNaiksatamat this point i think most of us are on the same page in terms of understanding where we want to be in terms of trying to capture the user intent18:41
SumitNaiksatamand I think that the current spec puts us on a patch towards that, although might not entirely be the case (the explicilt use of the network service policy is a sticky point)18:42
*** mrmartin has joined #openstack-meeting-318:42
SumitNaiksatamthat said, our current plan is to use this spec as a basis for the first iteration of implementation18:42
SumitNaiksatamwe will no doubt learn with that, and we can revise accordingly18:42
SumitNaiksatamthat said, over to you mageshgv18:43
*** SumitNaiksatam has quit IRC18:43
mageshgvSumitNaiksatam: True, Capturing the intent exactly is the important aspect here18:43
mageshgvIt might help in getting a clear picture when we can try out a patch for this functionlity18:44
YiSumitNaiksatam: mageshgv: regarding the intent, I do think in the case of FIP, it's to allow an endpoint to be accessed from external environment18:45
Yii.e., the external users could be the initiator of the session18:46
mageshgvYi: Yes, that is indeed the usecase for this feature18:46
*** SumitNaiksatam_ has joined #openstack-meeting-318:46
*** jrist has joined #openstack-meeting-318:47
Yiwhile the intent, for the non-FIP NAT case, is to allow endpoint to access external ...18:47
Yithe difference is "who is the initiator"...18:47
*** SumitNaiksatam has joined #openstack-meeting-318:48
mageshgvYi: are you referring to nat_pool when you mean non-FIP NT case ?18:48
Yimageshgv: yes..18:48
SumitNaiksatamsorry, folks having problems with my client again18:49
mageshgvActually I too wanted to discuss this with ivar-lazzaro and SumitNaiksatam18:50
SumitNaiksatammageshgv: my apologies, i was typing not realizing that what i was typing was not geting relayed18:51
*** sambetts has quit IRC18:51
SumitNaiksatamand i missed some of the context here too18:51
SumitNaiksatami will go back and check the logs once the meeting is done18:51
SumitNaiksatam#chair rkukura mageshgv ivar-lazzaro18:51
openstackCurrent chairs: SumitNaiksatam ivar-lazzaro mageshgv rkukura18:51
SumitNaiksatamin case i drop off again18:51
Yimageshgv: do we want to discuss here?18:52
SumitNaiksatammageshgv: are we at a logical point in this discussion where we can take this offline?18:52
ivar-lazzaroYi, mageshgv: nat pool is intended for FIP cases18:52
*** carl_baldwin_ has joined #openstack-meeting-318:52
SumitNaiksatami mean onto #openstack-gbp18:52
ivar-lazzaroYi, mageshgv: non-FIP cases are in the PAT domain imp18:52
*** sambetts has joined #openstack-meeting-318:52
ivar-lazzaros/imp/IMO18:52
mageshgvSumitNaiksatam: ok, that will be fine18:52
SumitNaiksatami want to take a few minutes to discuss the GBP project in the open discussion18:53
SumitNaiksatammageshgv: thanks18:53
Yiivar-lazzaro: I would agree, but there seems some inconsistency about terms used in openstack regard nat/pat/FIP/snat/dnat18:53
*** carl_baldwin has quit IRC18:53
*** carl_baldwin_ is now known as carl_baldwin18:53
SumitNaiksatammageshgv: to Yi’s point perhaps we can clarify in the spec18:54
ivar-lazzaroYi: well, PAT only mean one thing I think. And NAT pool could be renamed if we need to18:54
Yiivar-lazzaro: that's why I tried to avoid using nat-pool previously. Instead, using FIP/non-FIP.18:54
SumitNaiksatamYi: that said, we are not reinventing the floating IP (or NAT) definition, we intend to use it exactly as neutron uses it18:54
*** wojdev has joined #openstack-meeting-318:54
SumitNaiksatam#topic Open Discussion18:55
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"18:55
YiSumitNaiksatam: I agree. but we need to make sure all of us on the same page.:-)18:55
SumitNaiksatamYi: absolutely18:55
SumitNaiksatami had one item i wanted to bring up - as a team it seems that we are in agreement that we want to take the step towards openstack “projectification” per the new “big tent” policy18:56
SumitNaiksatam*governance policy18:56
SumitNaiksatameverybody mostly in agreement on this?18:57
ivar-lazzaro+118:57
yapeng+118:57
mageshgv+118:57
SumitNaiksatamivar-lazzaro: yapeng mageshgv: great18:57
banix+118:57
SumitNaiksatambanix: great18:57
Yi+118:58
LouisF+118:58
SumitNaiksatamtowards that end - here is the proposed mission statement for the project:18:58
SumitNaiksatam“To provide a policy framework consisting of declarative, intent-based abstractions for cloud infrastructure coupled with an enforcement engine designed to enable scalable automation.”18:59
SumitNaiksatamsound okay to everyone?18:59
banixsounds reasonable18:59
SumitNaiksatambanix: okay18:59
Yi+118:59
SumitNaiksatamthis is of course in no way set in stone18:59
SumitNaiksatamprojects keep evolving, so can be adjusted as we go along19:00
SumitNaiksatamanyway, let me know if you have further thoughts on any of this19:00
SumitNaiksatamand we have the #openstack-gbp channel to discuss as well19:00
SumitNaiksatamwe are at the hour19:00
SumitNaiksatamthanks all!19:00
Yithanks, SumitNaiksatam!19:01
SumitNaiksatamreminder - kilo-2 deadline for us is March 16th19:01
SumitNaiksatambye!19:01
Yibye19:01
banixthaks. bye19:01
mageshgvbye19:01
SumitNaiksatam#endmeeting19:01
*** openstack changes topic to "Zuul check queue stuck due to reboot maintenance window at one of our cloud providers - no need to recheck changes at the moment, they won't move forward."19:01
openstackMeeting ended Thu Mar  5 19:01:38 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-03-05-18.01.html19:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-03-05-18.01.txt19:01
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-03-05-18.01.log.html19:01
yapengbye19:01
*** mageshgv has quit IRC19:01
*** SumitNaiksatam_ has quit IRC19:04
*** ivar-lazzaro has quit IRC19:05
*** SumitNaiksatam has quit IRC19:06
*** egallen has joined #openstack-meeting-319:07
*** SumitNaiksatam has joined #openstack-meeting-319:08
*** wojdev has quit IRC19:09
*** kozhukalov has quit IRC19:10
*** carl_baldwin_ has joined #openstack-meeting-319:11
*** jishnu has quit IRC19:13
*** baoli_ has quit IRC19:13
*** carl_baldwin has quit IRC19:13
*** carl_baldwin_ is now known as carl_baldwin19:13
*** egallen has quit IRC19:13
*** sreshetn1ak has quit IRC19:14
*** sbalukoff has joined #openstack-meeting-319:17
*** wojdev has joined #openstack-meeting-319:17
*** egallen has joined #openstack-meeting-319:20
*** e0ne has joined #openstack-meeting-319:24
*** ivar-lazzaro has joined #openstack-meeting-319:28
*** david-lyle has quit IRC19:29
*** annegentle has quit IRC19:35
*** annegentle has joined #openstack-meeting-319:35
*** mrmartin has quit IRC19:40
*** alexsyip has joined #openstack-meeting-319:42
*** wojdev has quit IRC19:43
*** jckasper has quit IRC19:44
*** jckasper has joined #openstack-meeting-319:45
*** wojdev has joined #openstack-meeting-319:48
*** vishwanathj has quit IRC19:48
*** Sukhdev has joined #openstack-meeting-319:53
*** thangp has quit IRC19:55
*** melwitt has joined #openstack-meeting-319:55
*** sarob has joined #openstack-meeting-319:56
*** sarob has quit IRC19:57
*** sarob has joined #openstack-meeting-319:58
*** wojdev has quit IRC19:58
*** rkukura has quit IRC19:58
*** MarkAtwood has joined #openstack-meeting-319:59
*** sarob has quit IRC20:00
*** MaxV has quit IRC20:00
*** sarob has joined #openstack-meeting-320:01
*** bpokorny_ has joined #openstack-meeting-320:02
*** MarkAtwood has quit IRC20:03
*** vishwanathj has joined #openstack-meeting-320:03
*** wojdev has joined #openstack-meeting-320:03
*** LouisF has quit IRC20:05
*** bpokorny has quit IRC20:06
*** bpokorny has joined #openstack-meeting-320:08
*** Yi has quit IRC20:10
*** bpokorny_ has quit IRC20:11
*** MarkAtwood has joined #openstack-meeting-320:17
*** MarkAtwood has quit IRC20:18
*** wojdev has quit IRC20:22
*** Longgeek has joined #openstack-meeting-320:23
*** coolsvap_ is now known as coolsvap20:24
*** mattgriffin has joined #openstack-meeting-320:24
*** rkukura has joined #openstack-meeting-320:27
*** Longgeek has quit IRC20:27
*** thangp has joined #openstack-meeting-320:34
*** carl_baldwin_ has joined #openstack-meeting-320:36
*** carl_baldwin has quit IRC20:38
*** carl_baldwin_ is now known as carl_baldwin20:38
*** ivar-laz_ has joined #openstack-meeting-320:38
*** MarkAtwood has joined #openstack-meeting-320:38
*** ivar-lazzaro has quit IRC20:41
*** matrohon has joined #openstack-meeting-320:44
*** david-lyle_afk has joined #openstack-meeting-320:45
*** david-lyle_afk has quit IRC20:47
*** david-lyle_afk has joined #openstack-meeting-320:47
megmhi all -- I may be a couple minutes late20:49
*** MaxV has joined #openstack-meeting-320:51
*** coolsvap is now known as coolsvap_20:52
*** rkukura has quit IRC20:53
*** rkukura has joined #openstack-meeting-320:55
*** rkukura has left #openstack-meeting-320:55
mattgriffinmegm, np20:56
mattgriffinHA Guide meeting getting started in a few min20:56
*** Sam-I-Am has joined #openstack-meeting-320:58
*** ivar-laz_ has quit IRC20:58
*** ivar-lazzaro has joined #openstack-meeting-320:59
*** salv-orlando is now known as ihate-salv-orlan20:59
*** ivar-lazzaro has quit IRC21:00
mattgriffinhi Sam-I-Am21:00
*** ivar-lazzaro has joined #openstack-meeting-321:00
Sam-I-Amhowdy21:00
*** ihate-salv-orlan is now known as salv-orlando21:00
*** nickchase has joined #openstack-meeting-321:01
mattgriffin#startmeeting HA-Guide-Update21:01
openstackMeeting started Thu Mar  5 21:01:04 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
mattgriffinhi nickchase21:01
mattgriffin#topic last week's meeting21:01
*** openstack changes topic to "last week's meeting (Meeting topic: HA-Guide-Update)"21:01
*** egallen has quit IRC21:01
nickchasehi all21:01
mattgriffinnickchase, can you give an update on last week's meeting?21:02
mattgriffinmegm, said she was going to be a bit late21:02
nickchasesure, if you give me a minute21:02
nickchaseI can't remember that far back. :)21:02
mattgriffinheh21:02
Sam-I-Amhi nick21:02
megmHi all21:03
nickchasehey, all21:03
mattgriffinmegm, hello21:03
*** david-lyle_afk is now known as david-lyle21:03
nickchaseI sent the minutes to the list21:03
nickchasebut I'm trying to find them21:03
mattgriffinhere's what i thought we might cover today21:03
mattgriffin#link https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update#Next_Meeting21:03
mattgriffinnickchase, cool21:03
nickchasefound them:21:03
nickchaseShort meeting today.  TOC is still being reviewed, and Meg is adding links to existing material.  We agreed on the following:21:03
nickchaseWe need to add strategy information to the TOC. (nickchase, 21:17:11)21:03
nickchaseWe don't want to duplicate existing docs (ie, for Galera) (nickchase, 21:18:57)21:03
nickchaseWe'll take the discussion of RST vs Docbook to the mailing list. (nickchase, 21:26:02)21:03
nickchaseAction items:21:03
nickchase    nickchase21:03
nickchase        nickchase Add structure for HA strategy.21:03
nickchase        nickchase Create wiki pages for the install guide and ops guide notes and link them from the main HA guide page.21:03
nickchase    Sam-I-Am21:03
nickchase        Sam-I-Am Review the install guide for any references that are relevant to HA.21:03
nickchase    Shamail21:03
nickchase        Shamail Review the ops guide for any references that are relevant to HA.21:03
nickchaseFull minutes:  http://eavesdrop.openstack.org/meetings/ha_guide/2015/ha_guide.2015-02-26-21.11.html21:03
nickchasewhoa,s orry about that!!!21:04
Sam-I-Amheh21:04
mattgriffin:)21:04
Sam-I-Amyou need to irc better :)21:04
nickchasehey, been out of IRC except for these meetings for about a decade and a half.21:04
nickchaseglad I remember how to /join :)21:04
Sam-I-Amwe'll eventually fix that21:04
mattgriffinshould we consider these action items for the next meeting as well. wondering about progess21:05
nickchaseI apologize I just realized I completely spaced on my action items.21:05
mattgriffinquestion for Sam-I-Am, nickchase, and megm ^21:05
mattgriffinnickchase, np21:06
nickchaseI'm all for considering them for next meeting (for reasons just stated)21:06
megmI'm still not quite done with the outline but most of it is there.21:06
mattgriffinmegm, what was that link again?21:06
megmI think there is enough to start discussing content structure21:06
megmhttps://wiki.openstack.org/wiki/HAGuideImprovements/TOC21:06
Sam-I-Amyeah, we're getting closer on structure21:06
Sam-I-Ami also reviewed the install guide21:07
mattgriffinexcellent. this is great stuff21:07
megmsam-i-am, are things in the right order in the outline?21:08
nickchaseSo the internal Mirantis team is supposed to be letting us know which topics they're going to tackle first.21:08
Sam-I-Ammegm: not 100%21:08
nickchaseI'll bug Evgeniy to see where that is21:08
Sam-I-Amsort of need to weed things out first, imho21:08
megmwe also need to identify when one does what is in the install guide and then does the ha steps, versus replacing the install guide steps21:08
Sam-I-Amthen it sort of makes sense to start with the most system-wide things, like databases... then keystone, etc.21:08
mattgriffinnickchase, cool. i can start to see what database parts Percona can take too21:09
Sam-I-Amnothing in the install guide does HA, except one part of swift, but thats only because its required minimum config21:09
mattgriffinack21:09
Sam-I-Amit wasnt supposed to handle redundancy because its often "too much" for first-timers21:10
nickchaseright21:10
Sam-I-Amredundancy is the second step though21:10
megmAgreed about install guide not covering ha.21:10
Sam-I-Amand secueity21:10
Sam-I-Amsecurity21:10
megmBut, for instance, do I do the Keystone install/config that is in the Install Guide, then do the "special" stuff that is in HA Guide.21:10
mattgriffinso for next meeting, review this TOC page and ensure it's on the mark?21:11
megmOr do we just use the Keystone concepts from the install guide, and handle all config in HA guide21:11
Sam-I-Ammegm: where possible, we should reference the install guide's basic config.21:11
*** zz_ttrifonov is now known as ttrifonov21:11
*** Yi has joined #openstack-meeting-321:11
Sam-I-Amthere may be some services that require complete reconfiguration to do HA21:11
megmI agree -- where do we get the definition of "where possible"?21:11
megmDo I go through and modify keystone.conf for install guide, then throw that away when I do HA?21:12
nickchaseBasically if you can do the install steps and then do special for HA, then we reuse it.21:12
nickchaseIf you do something different from start, then it's not possible.21:12
megmIt needs definition, probably for each component/topic21:12
nickchaseagreed.21:12
Sam-I-Amin some cases its "roughly duplicate this config, with minor changes for X Y Z"21:12
megmI think we agreed on the strategy/component a few weeks ago -- the specifics are what concerns me21:13
Sam-I-Ammost of the APIs are that way21:13
*** KrishnaK has quit IRC21:13
megmSam, did you do the "Configure networking on each node" piece?  Very nice!21:13
Sam-I-Amfor databases, question is do we want to take a one-node sql database to redundancy, or start from scratch with redundancy?21:13
megmNick, do the networking guide people agree?21:13
*** shwetaap has quit IRC21:13
nickchaseagree about thwat?21:14
nickchasesorry, not following.21:14
Sam-I-Ammegm: which "configure networking on each node" ? (which doc)21:14
*** mwagner_lap has quit IRC21:14
mattgriffinSam-I-Am, i think start with redundancy - i.e., galera-based21:14
Sam-I-Amthe question is, do we think most people will start out with the install guide architecture and then add onto it? or will they want to deploy from scratch with redundancy.21:14
megmhttps://wiki.openstack.org/wiki/HAGuideImprovements/TOC -- first header after "Prerequisites"21:14
mattgriffinSam-I-Am, hmm... maybe for the DB we could include a general upgrade procedure from single node to galera21:15
Sam-I-Ammegm: oh yeah that was me21:15
*** shwetaap has joined #openstack-meeting-321:15
Sam-I-Ammegm: that makes sense21:15
Sam-I-Amerrr mattgriffin21:16
mattgriffin:)21:16
*** Yi has quit IRC21:16
Sam-I-Amthe thing about the install guide is we have a known-good architecture to base off21:16
megmsam-i-am, that is an excellent question.21:16
Sam-I-Amthe install guide was written to make it easy to add more nodes of things21:16
mattgriffinSam-I-Am, i think just add that to the Prerequisites section - general DB upgrade step21:16
nickchaseI think that ...21:16
megmMy guess is that people will do a "play" set-up with the Install Guide but, when they are ready to deploy their production system, they will start over21:17
nickchasewe have an assumption that if someone is doing HA, they are NOT a beginner.  I think that...21:17
nickchaseti's perfactly acceptable to say, "INstall keystone. (see install guide if you need details)".  Now do this."21:18
nickchase(darn, my text disappeared :()21:18
megm+1 nick...  And we can include links to Install Guide (like for Keystone concepts) to help those who aren't experts at some piece or other21:18
nickchase(there it is (facepalm))21:18
Sam-I-Amyeah.21:18
Sam-I-Amagreed.21:18
mattgriffin+121:18
nickchasegreat.21:18
Sam-I-Amon the topic of audience, we're not going to handhold basic system things in the HA guide21:18
Sam-I-Amlike "here's how you edit a file"21:18
megmFor Keystone example, maybe it should be what you say, but "but modify keystone.conf like this rather than what is in Install GUide"21:18
nickchaseagreed.21:19
Sam-I-Ammegm: probably a blanket statement that says "we start with the basic config in the install guide... and then add this stuff. your base keystone config might contain more stuff"21:19
Sam-I-Amthats how the network guide is doing it21:19
nickchase+121:19
mattgriffini like it21:19
Sam-I-Am"we assume you know about all this other crap you have to configure, here's how to make DVR work"21:20
megmSounds good.  I just don't want the HA guide to routinely tell people to undo something they did in Install Guide...21:20
nickchaseright21:20
nickchasewe said from the beginning that the first thing we were going to do...21:21
Sam-I-Amif there's a case of that, we'll figure it out21:21
megmIs the outline in the correct order?  How do we determine that?21:21
nickchasewas tell people, "Look, here's the basic install procedure, and here are the steps that will be different for HA.  Now let's get into the details."21:21
nickchasemegm:  we do it.21:21
Sam-I-Ammegm: let me look over it again here21:21
nickchasewe'll have an overview to start.  and if there isn't one in the TOC, please add one while you're looking, Sam-I-Am21:22
Sam-I-Ammegm: ntp probably comes right around host networking, but its pretty simple (in fact, people should probably know how to do this)21:22
megmsam-i-am, you can always email me directly at meg.mcroberts@yahoo.com21:23
Sam-I-Amother than that, it mostly makes sense. start with host stuff, then system services, then openstack services.21:23
Sam-I-Amthe openstack services should probably go in the order of most-common to least-common21:23
Sam-I-Amand also based on dependencies21:23
Sam-I-Amlike... if you HA keystone, you're going to have to change all these other services.21:23
megm+1 sam21:23
*** carl_baldwin_ has joined #openstack-meeting-321:23
Sam-I-Amkeystone -> glance -> nova -> neutron -> cinder -> swift -> trove -> ??? -> ceilometer21:24
*** carl_baldwin has quit IRC21:24
*** carl_baldwin_ is now known as carl_baldwin21:24
Sam-I-Amand i think we do ceilometer last because it requires installing more agents for a bunch of other services21:24
Sam-I-Amin other words, ceilometer redundancy itself isnt the hard part21:25
Sam-I-Amits as you add more nodes and make other services redundant, you have to deploy more agents21:25
Sam-I-Amor for each service that has special ceilometer steps, we could say "do these steps if you run ceilometer"21:25
megmThe "Prerequisites" list needs to be looked at critically -- should NTP be there?21:26
mattgriffinmegm, i think it should be there from the install guide21:27
megmYes, NTP is from Install Guide but at what point?  It may be required earlier for HA, right?21:28
mattgriffinmegm, http://docs.openstack.org/havana/install-guide/install/yum/content/basics-ntp.html21:28
Sam-I-Amso, with NTP... the only real suggestion would be running servers on each controller node, then configuring each other hosts to use all of the controllers for sync. we can doc it, but its not complex.21:28
mattgriffinhmm... maybe21:28
Sam-I-Ammattgriffin: aaaaaa dont look at the guide that old :/21:28
Sam-I-Amit hurtses me21:28
mattgriffinhaha... oops21:28
megmInstructions are not complex, but order might be wrong in current outline.21:29
Sam-I-Amits a system level thing that is good practice for any server21:29
Sam-I-Ammegm: yes21:29
mattgriffingoogle likes havana21:29
Sam-I-Amit'll be easy to doc i think21:29
Sam-I-Ammattgriffin: tell me about it21:29
megmoutline has link to current ntp instructions21:29
megmThis is just a question of order -- I'm thinking that they should install O/S on all nodes then configure NTP before going further21:29
Sam-I-Amyeah, in the most basic case, ntp needs to at least run on every node.21:30
Sam-I-Ammegm: i'd say yes21:30
Sam-I-Amntp comes early21:30
Sam-I-Ambad time screws up all sorts of things21:30
mattgriffinok. 0 min left. document action items for next week?21:30
megmOkay, I'll move it.  But that's one example of a bad ordering in current outline21:30
megmMeg and Sam finish outline?21:31
megmNick get Mirantis owners for some pieces21:31
Sam-I-Amyeah, i can poke at it. i'll be at mid-cycle ops next week though.21:31
mattgriffin#action Meg and Sam finish outline21:31
Sam-I-Amso hopefully i can get to it tomorrow, or in any spare time before next thursday's meeting21:31
mattgriffin#action Nick get Mirantis owners for some pieces21:31
nickchaseand also my action items from last week21:31
mattgriffinnickchase, :)21:31
Sam-I-Ami'm also going to ask ops about their HA at the ops meetup21:32
Sam-I-Amthat was something someone asked me to do21:32
Sam-I-Amand i'll be there21:32
mattgriffin#action matt check with percona on where we can help more21:32
Sam-I-Amso chances are there will be some TOC updates post-ops21:32
mattgriffinSam-I-Am, good idea21:32
Sam-I-Amno reason to document things no one uses21:32
*** baoli has joined #openstack-meeting-321:32
megmAre we targeting Kilo or Juno?  Blueprint says Kilo21:32
nickchaseI would think Kilo.21:33
Sam-I-Amkilo, although thats kind of soon at this point21:33
Sam-I-Ami'm pretty tied up with the install guide and network guide21:33
mattgriffinshould we write something up for the rest of the Docs community with our plans. make sure they're +1. i can start a pad and share it with you guys.21:34
megmSounds good21:34
mattgriffin#action matt start an HA Guide update for the Docs list21:34
mattgriffinanything else?21:34
Sam-I-Amif we get enough writers, this might go quicker21:34
mattgriffinaye21:34
Sam-I-Ambut right now its... not many.21:34
Sam-I-Amthe networking guide was a juno thing :)21:35
Sam-I-Amand now kilo21:35
Sam-I-Amand...21:35
mattgriffin:)21:35
Sam-I-Amturns out, this stuff is a lot of work and requires some specialized people21:35
mattgriffinshocking21:35
Sam-I-Am(and those people need time to write)21:35
*** baoli has quit IRC21:36
mattgriffinok. i'm going to end the meeting then. thanks all!!! have a great rest of your week21:36
Sam-I-Amthanks21:36
mattgriffin#endmeeting21:36
*** openstack changes topic to "Zuul check queue stuck due to reboot maintenance window at one of our cloud providers - no need to recheck changes at the moment, they won't move forward."21:36
openstackMeeting ended Thu Mar  5 21:36:15 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ha_guide_update/2015/ha_guide_update.2015-03-05-21.01.html21:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ha_guide_update/2015/ha_guide_update.2015-03-05-21.01.txt21:36
openstackLog:            http://eavesdrop.openstack.org/meetings/ha_guide_update/2015/ha_guide_update.2015-03-05-21.01.log.html21:36
*** baoli has joined #openstack-meeting-321:36
*** Sam-I-Am has left #openstack-meeting-321:40
*** sergef has quit IRC21:40
*** MarkAtwood has quit IRC21:40
*** MarkAtwood has joined #openstack-meeting-321:41
*** SumitNaiksatam has quit IRC21:48
*** baoli has quit IRC21:48
*** mrmartin has joined #openstack-meeting-321:48
*** MaxV has quit IRC21:49
*** SumitNaiksatam has joined #openstack-meeting-321:50
*** alexsyip has quit IRC21:52
*** Sukhdev has quit IRC21:53
*** ivar-lazzaro has quit IRC21:53
*** wojdev has joined #openstack-meeting-321:55
*** baoli has joined #openstack-meeting-321:56
*** ivar-lazzaro has joined #openstack-meeting-321:57
*** ttrifonov is now known as zz_ttrifonov21:59
*** dtroyer has joined #openstack-meeting-321:59
*** wojdev has quit IRC22:00
*** ivar-lazzaro has quit IRC22:01
*** bpokorny_ has joined #openstack-meeting-322:02
*** clu_ has joined #openstack-meeting-322:03
*** Yi has joined #openstack-meeting-322:05
*** bpokorny has quit IRC22:05
*** jaypipes has quit IRC22:08
*** dtroyer has left #openstack-meeting-322:09
*** lblanchard has quit IRC22:10
*** Sukhdev has joined #openstack-meeting-322:13
*** wojdev has joined #openstack-meeting-322:14
*** ivar-lazzaro has joined #openstack-meeting-322:24
*** ivar-lazzaro has quit IRC22:32
*** eghobo has quit IRC22:33
*** wojdev has quit IRC22:34
*** mrmartin has quit IRC22:40
*** wojdev has joined #openstack-meeting-322:43
*** e0ne has quit IRC22:44
*** annegentle has quit IRC22:53
*** banix has quit IRC22:56
*** peristeri has quit IRC22:56
*** jaypipes has joined #openstack-meeting-322:57
*** mattfarina has quit IRC23:02
*** shwetaap has quit IRC23:03
*** jckasper has quit IRC23:04
*** nelsnelson has quit IRC23:15
*** ChuckC is now known as ChuckC_23:19
*** VW_ has quit IRC23:21
*** marun has quit IRC23:25
*** VW_ has joined #openstack-meeting-323:25
*** ChuckC_ is now known as ChuckC23:26
*** clu_ has quit IRC23:26
*** jaypipes has quit IRC23:28
*** etoews has quit IRC23:29
*** sigmavirus24 is now known as sigmavirus24_awa23:32
*** claired has joined #openstack-meeting-323:34
*** claired has quit IRC23:35
*** matrohon has quit IRC23:40
*** thomasem has quit IRC23:41
*** SumitNaiksatam has quit IRC23:41
*** cyeoh has joined #openstack-meeting-323:41
*** SumitNaiksatam has joined #openstack-meeting-323:43
*** thangp has quit IRC23:45
*** clu_ has joined #openstack-meeting-323:46
*** SumitNaiksatam has quit IRC23:47
*** wojdev has quit IRC23:49
*** SumitNaiksatam has joined #openstack-meeting-323:50
*** VW_ has quit IRC23:51
*** openstack has joined #openstack-meeting-323:52
-sendak.freenode.net- [freenode-info] channel trolls and no channel staff around to help? please check with freenode support: http://freenode.net/faq.shtml#gettinghelp23:52
*** ChanServ sets mode: +o openstack23:52
*** baoli has quit IRC23:57
*** ivar-lazzaro has joined #openstack-meeting-323:57

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