Thursday, 2015-01-08

etoewshi00:00
elmikoyo00:00
miguelgrinberghello, and happy 2015!00:00
etoews#startmeeting api wg00:00
openstackMeeting started Thu Jan  8 00:00:36 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
etoewsa happy new year to all. :D00:00
elmiko+100:01
etoewsi get the feeling we might be a bit light on api wg attendees this time00:01
*** sigmavirus24 is now known as sigmavirus24_awa00:01
*** sigmavirus24_awa is now known as sigmavirus2400:01
sigmavirus24hi00:01
etoewshi!00:02
dtroyerhi00:02
etoewshello!00:02
etoews#topic agenda00:02
*** openstack changes topic to "agenda (Meeting topic: api wg)"00:02
etoews#link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda00:02
etoewsno new topics so moving right along...00:02
etoews#topic previous meeting action items00:03
*** openstack changes topic to "previous meeting action items (Meeting topic: api wg)"00:03
etoews#link http://eavesdrop.openstack.org/meetings/api_wg/2014/api_wg.2014-12-18-16.00.html00:03
elmikoi'm still working on the barbican swagger00:03
etoewsi didn't get to all of my action items either :(00:04
*** fischerw has quit IRC00:04
etoewssick, holidays, catching up, excuses, excuses.00:04
sigmavirus24etoews: I think we should carry them forward (especially the API definition ones)00:04
elmikoi was going to just convert the wadl, but after talking about it with the barbican folks i want to move ahead on doing it programatically00:04
etoewssigmavirus24: +100:04
etoewselmiko: as in programatically building it from the source code?00:05
elmikoetoews: sorta yea, more like using the wsgi object created by pecan and dumping info from there00:05
*** VW_ has quit IRC00:05
elmikobut my pecan knowledge is still growing, so it's taking longer :/00:06
sigmavirus24hm. interesting00:06
elmikothat's how i did it for sahara, but in that case we use flask00:06
*** salv-orlando has quit IRC00:06
sigmavirus24elmiko: how much of that wsgi object is going to be turned into documentation?00:06
miguelgrinbergisn't this locking us into continuing with Pecan?00:06
* miguelgrinberg hopes one day will move to Flask00:06
* sigmavirus24 hopes we never use an April Fool's joke in production /kidding00:07
elmikosigmavirus24: for sure we could generate the skeleton docs for routes and methods, and probably schema too00:07
miguelgrinbergsigmavirus24: I think I can read when you are kidding now, took me some time ;-)00:07
elmikosigmavirus24: things like descriptions might be more hassle, or might not be wanted00:07
elmikomiguelgrinberg: well, sahara uses flask =)00:07
sigmavirus24elmiko: I guess I'm wondering if something like betamax could help generate data for the docs too00:07
*** devlaps has quit IRC00:07
*** xuhanp has joined #openstack-meeting-300:07
sigmavirus24use betamax with a requests session and you have dumps of the request/response cycle for each request and then you can parse that JSON turn it into docs00:08
etoewsbut we're not generating docs. we're generating api definition.00:08
sigmavirus24it's an idea I've thought about but never worked with00:08
sigmavirus24etoews: ah, misunderstood the purpose. sorry00:08
elmikoyea, this will generate a skeleton of all the routes and methods(and hopefully schema)00:08
etoewselmiko: just as a starting point right?00:09
elmikoit's possible to pull description type info into the swagger doc as well, but i'm not sure that's desired00:09
elmikoetoews: yes00:09
etoewsya. i'm hoping it's the api def that drives the development of the implementation. not the other way around.00:09
*** baoli has quit IRC00:09
elmikoetoews: in the end that would be awesome, but baby steps...00:10
etoews+1 baby steps.00:10
etoewsokay that's a good point to carry over the action items.00:10
etoews#action etoews update the scope section of the wiki page and include api definition format00:10
etoews#action elmiko to generate swagger doc for barbican and commit to github somewhere00:10
etoews#action etoews start discussion about api def formats on ml00:11
etoews#action sigmavirus24 reply to discussion with benefits moz saw from using an api def format00:11
etoewson the plus side i did get to do some analysis of the metadata design before i got sick.00:11
miguelgrinbergetoews: very good analysis, I might say00:12
*** xuhanp has quit IRC00:12
etoewsya. i was hoping to get some feedback about it.00:12
etoews#link https://wiki.openstack.org/wiki/API_Working_Group/Current_Design/Metadata00:12
etoewsso it made sense the way i laid it out?00:12
*** xuhanp has joined #openstack-meeting-300:12
miguelgrinbergetoews: I meant to go look at the Heat stuff, because I think metadata there does not mean the same thing00:13
miguelgrinbergbut I haven't investigated yet00:13
etoewsit was mostly a lot of copy/paste and then squinting to see the patterns.00:13
etoewsmiguelgrinberg: ya. i noticed that too. from the analysis "The outliers are Orchestration's Software Configuration metadata which seems to describe a concept different from the other services notion of metadata and Object Storage's metadata which does everything with headers."00:14
sigmavirus24etoews: yeah that makes sense the way it is layed out (at least to me)00:14
elmikoetoews: makes sense to me as well00:14
etoewscool. hopefully it catches on.00:14
miguelgrinbergso I think we now use this document and throw darts at me guideline doc?00:14
miguelgrinbergs/me/my/00:15
etoewsright00:15
etoewsapologies for not having a chance to give that one a proper review yet.00:15
miguelgrinbergI sided with nova mostly, except for the implementation of the POST00:15
etoewslet's discuss it when we get to topic guidelines.00:16
miguelgrinbergshould we reconvene about metadata next week?00:16
etoews#topic APIImpact00:16
*** salv-orlando has joined #openstack-meeting-300:16
*** openstack changes topic to "APIImpact (Meeting topic: api wg)"00:16
etoews#link https://review.openstack.org/#/q/status:open+AND+(message:ApiImpact+OR+message:APIImpact),n,z00:17
etoewsseems APIImpact is catching on...00:17
etoewsanything anyone want to point out?00:17
*** jaypipes has quit IRC00:18
miguelgrinbergI have a more general question. When I did a review I -1'd it. The cinder guys sort of did not like that00:18
miguelgrinbergShould we stay out of it and just comment?00:18
*** xuhanp has quit IRC00:19
etoewsmiguelgrinberg: would you mind linking us to that review/comment?00:19
elmikothat's a bummer...00:19
*** banix has quit IRC00:20
*** xuhanp has joined #openstack-meeting-300:20
miguelgrinberglooking for it, but it was a few weeks ago. It was not direct, I just felt they wanted to get moving, in spite of my recommendation00:20
miguelgrinbergI withdrew my -100:20
etoewsi see00:22
*** nelsnelson has quit IRC00:22
miguelgrinberghttps://review.openstack.org/#/c/136253/00:22
miguelgrinbergMy comment on Dec 1100:22
etoewsi can see us running into this more and more in the near future.00:24
elmikoDave Chen brings up an interesting point about keeping their api internally consistent, i'm curious what the wg opinion should be on these things?00:25
etoewsthe projects will want to want to remain internally consistent even at the expense of being inconsistent with other projects00:25
miguelgrinbergIt's a tough one. At some point we need to break ties with the past.00:25
miguelgrinbergInconsistencies are inevitable in my opinion00:26
etoewsi can certainly understand that point of view but we need people to start converging00:26
sigmavirus24I've never found a single API (in the world) that is entirely internally consistent00:26
elmikois there any action we can take to help smooth these transitions? (aside from providing a solid guideline)00:26
miguelgrinbergI think for this it would have helped to have an official guideline, so I think we need to get them ready00:27
elmikothat makes sense00:27
etoewsya. having a guideline we can clearly point to would carry much more weight00:27
etoewsthe only other carrot that comes to mind at the moment is pointing out other projects that are already following the guideline00:28
*** nelsnelson has joined #openstack-meeting-300:28
etoewsthat addresses Dave Chen's "it's not quite sure when will other projects formally follow the new style."00:28
miguelgrinbergshould be (I mean I) relax REST compliance and try to write guidelines that match something out there?00:29
miguelgrinbergfor metadata, my doc is almost matching nova00:29
etoewsfor sure you'll get much more traction that way.00:29
etoewsi think as long as you're being pragmatic about it, it's for the best.00:30
elmikoi like the idea of moving closer and closer to REST compliance00:30
miguelgrinbergwell, it's something we need to decide. Maybe turn a blind eye to small things. This one is a small thing IMHO.00:30
elmikoetoews: +100:30
sigmavirus24practicality beats purity00:31
* sigmavirus24 spouts useless neologisms for irony and an appearance of wisdom00:31
etoews:)00:31
elmikolol00:32
dtroyerI wouldn't ignore these cases, but just a comment and move on… the comments will eventually add up00:32
miguelgrinbergIt's still confusing. Should new projects also be written following the almost RESTful guideline?00:32
sigmavirus24miguelgrinberg: that would be the ideal00:33
miguelgrinbergor should we allow some sort of grandfathering for older projects?00:33
miguelgrinbergbut still recommend the best approach?00:33
dtroyerhow about looking at it in terms of API revisions rather than whole projects?00:33
dtroyeralthough there isn't a compute v3 soon, that would have been the time to fix a lot of stuff, should we have the guidelines ready00:34
elmikosame with sahara v2, we've talked about it at 2 summits now00:34
*** sunny__ has quit IRC00:34
etoewsmiguelgrinberg: IMO new projects should be using the one-and-only guideline.00:34
miguelgrinbergso we document the ideal solution, but mention the "close enough" solutions for legacy projects00:35
*** Piet has quit IRC00:35
etoewsto me that way lies madness00:35
etoewsi think it would be confusing to new or existing api implementors.00:36
etoewsi think what dtroyer is proposing would work00:36
*** sunny_ has joined #openstack-meeting-300:36
miguelgrinbergyes, if we start saying "do this", but if that is too odd for you then "do that", then we are going to lose credibility00:36
etoewsyep. people will throw their hands up and walk away pretty quickly.00:37
dtroyerI think the "do this" part is sufficient…it'll be followed or not00:37
etoewsrigth00:37
elmiko+100:37
miguelgrinberg+1, but that leaves those who want to be consistent with old stuff out00:38
*** VW_ has joined #openstack-meeting-300:38
*** xuhanp has quit IRC00:38
miguelgrinbergbasically we are saying join us or you're on your own00:38
elmikomiguelgrinberg: at least it will provide a path to a possible new version though00:38
etoewsbut not for the next version of their api?00:38
dtroyerit leaves them where they are today already00:38
miguelgrinbergetoews: true, only until the next rev00:39
sigmavirus24miguelgrinberg: I think the next large version of an API is really the best place to expect people to start to follow the guidelines00:39
miguelgrinbergyeah, okay, I think I worry too much :)00:39
sigmavirus24miguelgrinberg: they're going to hate us no matter what we do00:39
etoewsno no. it's really good to have these sorts of conversations early on in an effort like this.00:39
sigmavirus24we're potentially insulting their sensitive egos about the APIs they designed and we're telling them are now deficient in some respect00:40
sigmavirus24I think it will also save a lot of cross-project contention. I've seen people contributing to other projects get annoyed by having certain hacking checks disabled00:40
elmikosigmavirus24: that seems like it might be a problem with our communications as some level00:40
dtroyersigmavirus24: some are always going to be that way…let them be, there are still plenty who are hungry for guidance and commonality00:41
sigmavirus24dtroyer: that's my point exactly00:41
elmikoah, not much we can do for those folks though?00:41
*** dougwig is now known as dougwig_the_rude00:41
etoewssnowflakes be snowflakes00:41
*** dougwig_the_rude is now known as dougwig00:42
elmikolol00:42
dtroyerafter 5 years, look at what projects still actively want to do things differently…00:42
sigmavirus24yep00:42
dtroyerFWIW, I'm fixing those at the language-binding and CLI levels…00:43
dtroyerat least someone's life is going to improve00:43
etoewsdtroyer: applying spackle. :)00:44
etoewsokay. so we shoot for pragmatic REST...meaning REST but tempered with the current design where it makes sense.00:44
etoewsis that a fair statement or too broad to be of value?00:44
elmikoi dunno, that seems to leave the door open for exceptions moving forward. seems appropriate for current stuff though.00:45
sigmavirus24Thought: What about a migration path. vCurrent+1 = middle-ground, vCurrent+2 = perfect future00:45
miguelgrinbergI think it is fair, we can always improve our guidelines to drive towards closer REST00:46
dtroyerI don't think we should leave the out…our out is that we're writign guidelines, not requirements00:46
elmikodtroyer: i like the way you put it00:46
elmikosigmavirus24: sounds interesting to me00:46
etoewsright right. there was a reason we didn't call it "standards" in the first place.00:47
sigmavirus24elmiko: I'm not sure it's a good idea but it might make people more amenable to it00:47
sigmavirus24Of course that means results will be a lot longer off00:47
elmikosigmavirus24: understandable, but i feel like the conversation around that idea could produce some useful fruit in terms of actions projects can take00:48
dtroyersigmavirus24: that might be the reality, but I don't think we should codify that in our work00:48
miguelgrinbergDo we need to wait for two major revs? I'd say vCurrent+1 should shoot for compliance with our guidelines.00:48
sigmavirus24miguelgrinberg: right, that's what I *want*00:48
sigmavirus24Anyway00:48
elmikomiguelgrinberg: in an ideal world, yes00:48
sigmavirus24I think we're wasting a lot of time on this00:48
sigmavirus24This is perhaps a better discussion for the mailing list00:48
elmikodo i smell an action item?00:49
etoewssigmavirus24: do you want to give yourself an action item for kicking off a discussion on the ml?00:49
sigmavirus24elmiko: did you just volunteer?00:49
elmikosigmavirus24: hey, i'm already behind on my action ;)00:50
etoewsme too. ;)00:50
sigmavirus24#action sigmavirus24 will start a discussion on the ML about migrating to API WG standards00:50
sigmavirus24etoews: is the reason I'm behind on mine =P00:50
etoewsthat's ture00:50
etoewss/ture/true/00:50
etoews#topic guidelines00:51
*** openstack changes topic to "guidelines (Meeting topic: api wg)"00:51
sigmavirus24#link https://review.openstack.org/#/c/145579/00:51
* sigmavirus24 was waiting for this section the whole time =P00:51
sigmavirus24This seemed to spawn from a discussion on the ML surrounding how clients sort output from the API, I'm curious what people think of the spec00:52
etoewseverything surrounding pagination would benefit greatly from analysis of current design.00:53
miguelgrinbergrepeating the same query string args? Isn't that looking for trouble?00:53
*** sunny_ has quit IRC00:53
sigmavirus24miguelgrinberg: it is00:53
* sigmavirus24 is glad he isn't the only one who caught that =P00:53
sigmavirus24etoews: I agree00:53
miguelgrinbergHaven't seen this before, I'll comment on it later00:53
etoewspractically every project does it and there are a bunch of inconsistencies.00:53
etoewsi comment on it too about current design.00:53
sigmavirus24Further this will cause issues with python clients consuming this.00:54
* sigmavirus24 knows. he maintains requests00:54
miguelgrinbergyeah, I would use a single key with comma separated keys, for example00:54
etoews#action etoews to comment on https://review.openstack.org/#/c/145579/ about current design analysis00:54
sigmavirus24I've seen rubby clients have trouble with stuff like this too00:54
dtroyerdoes the suggestion for the CLI format make sense here too?   ie, sort=key1:dir1,key2:dir200:55
*** bradjones has quit IRC00:55
sigmavirus24dtroyer: it could work00:55
sigmavirus24While we still have time:00:55
sigmavirus24#link https://review.openstack.org/#/c/131736/00:55
sigmavirus24I think this has a noble purpose but will cause a lot of problems if it were actually to be accepted and (to some degree) enforced00:56
*** vishwanathj has quit IRC00:56
elmikois that talking mainly about the URIs or about json objects passed as body as well?00:56
miguelgrinberghe does not say specifically how to achieve that. Simpler JSON bodies?00:56
etoewscurl is just another client00:57
miguelgrinbergnot one that is specifically friendly to APIs00:57
miguelgrinbergJSON is hard from the cmd line00:57
sigmavirus24I mean I can curl my way around GitHub's API easily but I don't recommend it00:57
elmikohttpie makes it a little better00:58
sigmavirus24Some of their resources are huge (especially the collections)00:58
miguelgrinbergelmiko: +100:58
dtroyermy feeling is that it was about combinations of URI, headers and bodies…  the intent is 'be simple and smart'00:58
*** bradjones has joined #openstack-meeting-300:58
*** bradjones has quit IRC00:58
*** bradjones has joined #openstack-meeting-300:58
elmikoi think the idea of simplification is nice, but extending to json bodies sounds difficult00:58
dtroyerbut it became a time sink…I'm ready to just let it go00:59
miguelgrinbergI would agree with not including tenant ids in URIs whenever possible00:59
sigmavirus24Yeah I like the *intent* I just don't know how practical it really is00:59
miguelgrinbergbut I don't think there is much more that can be done00:59
elmikoi don't like tenant ids in the URI either, taking that out will be a big change for sahara01:00
miguelgrinbergit shouldn't be a problem if we had HATEAOS, but....01:00
etoewsthat's a whole other kettle of fish...01:01
miguelgrinbergyeah01:01
sigmavirus24and we're over time01:01
etoews#endmeeting01:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"01:01
openstackMeeting ended Thu Jan  8 01:01:24 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)01:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-01-08-00.00.html01:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-01-08-00.00.txt01:01
openstackLog:            http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-01-08-00.00.log.html01:01
sigmavirus24Thanks everyone01:01
sigmavirus24Sorry to drag us overtime01:01
etoewsthx!01:01
elmikoyea, thanks =)01:01
miguelgrinbergbye all01:01
elmikomiguelgrinberg: i'm not familiar with HATEOAS, got some new reading01:01
etoewssigmavirus24: not at all. i should have moved us forward earlier.01:01
sigmavirus24etoews: I stirred the pot too much ;)01:02
elmikolol01:02
etoews:)01:02
sigmavirus24My real job title: Troll01:02
sigmavirus24miguelgrinberg: can confirm01:02
miguelgrinbergelmiko: it'll be fun, that could affect the way we document APIs also01:02
etoewsand we're stirring one of the biggest pots in openstack.01:02
miguelgrinbergsigmavirus24: I fully confirm :)01:03
elmikosigmavirus24: lol, i hope you get that on business cards or something ;)01:03
sigmavirus24elmiko: I'll find you in a separate channel and relate a story =P01:04
elmikosigmavirus24: nice, find me in openstack-sahara usually01:04
*** cgascoig has joined #openstack-meeting-301:07
*** alexpilotti has quit IRC01:08
*** SumitNaiksatam has quit IRC01:09
*** SridharRamaswamy has quit IRC01:15
*** markmcclain has quit IRC01:18
*** markmcclain has joined #openstack-meeting-301:20
*** yapeng has quit IRC01:21
*** etoews has quit IRC01:33
*** sigmavirus24 is now known as sigmavirus24_awa01:34
*** sarob has quit IRC01:36
*** stanzgy has joined #openstack-meeting-301:37
*** bpokorny_ has joined #openstack-meeting-301:41
*** bpokorny has quit IRC01:44
*** mrmartin has joined #openstack-meeting-301:45
*** Piet has joined #openstack-meeting-301:46
*** VW_ has quit IRC01:47
*** yapeng has joined #openstack-meeting-301:49
*** SumitNaiksatam has joined #openstack-meeting-301:53
*** markmcclain has quit IRC01:55
*** salv-orlando has quit IRC01:58
*** bpokorny_ has quit IRC01:59
*** mrmartin has quit IRC02:00
*** baoli has joined #openstack-meeting-302:05
*** clu_ has quit IRC02:06
*** wuhg has joined #openstack-meeting-302:09
*** julim has joined #openstack-meeting-302:16
*** alexsyip has quit IRC02:21
*** sunny_ has joined #openstack-meeting-302:46
*** sunny_ has quit IRC02:52
*** qwebirc52590 has joined #openstack-meeting-302:53
qwebirc52590test02:55
*** salv-orlando has joined #openstack-meeting-303:00
*** ttrifonov is now known as zz_ttrifonov03:01
*** markmcclain has joined #openstack-meeting-303:05
*** salv-orlando has quit IRC03:07
*** etoews has joined #openstack-meeting-303:07
*** VW_ has joined #openstack-meeting-303:11
*** etoews has quit IRC03:12
*** elmiko has left #openstack-meeting-303:15
*** armax has quit IRC03:18
*** neillc_away is now known as neillc03:30
*** pballand has quit IRC03:30
*** yamahata has quit IRC03:31
*** reed has quit IRC03:38
*** cgascoig has quit IRC03:45
*** VW_ has quit IRC03:45
*** cgascoig has joined #openstack-meeting-303:49
*** badveli has quit IRC03:52
*** SumitNaiksatam has quit IRC03:53
*** salv-orlando has joined #openstack-meeting-304:04
*** salv-orlando has quit IRC04:08
*** yapeng has quit IRC04:13
*** yapeng has joined #openstack-meeting-304:14
*** carl_baldwin has joined #openstack-meeting-304:16
*** baoli has quit IRC04:17
*** banix has joined #openstack-meeting-304:18
*** yapeng has quit IRC04:18
*** yamahata has joined #openstack-meeting-304:24
*** markmcclain has quit IRC04:33
*** sarob has joined #openstack-meeting-304:37
*** sarob has quit IRC04:41
*** armax has joined #openstack-meeting-304:43
*** Longgeek has joined #openstack-meeting-304:45
*** david-lyle has quit IRC04:50
*** watanabe_isao has quit IRC04:51
*** watanabe_isao has joined #openstack-meeting-304:51
*** vineetmenon has joined #openstack-meeting-304:52
*** banix has quit IRC04:53
*** markmcclain has joined #openstack-meeting-305:05
*** markmcclain has quit IRC05:23
*** eghobo has joined #openstack-meeting-305:45
*** carl_baldwin has quit IRC05:52
*** salv-orlando has joined #openstack-meeting-305:55
*** salv-orlando has quit IRC06:02
*** yapeng has joined #openstack-meeting-306:03
*** killer_prince is now known as lazy_prince06:03
*** eghobo has quit IRC06:04
*** yapeng has quit IRC06:08
*** nelsnelson has quit IRC06:12
*** nelsnelson has joined #openstack-meeting-306:13
*** mrmartin has joined #openstack-meeting-306:25
*** mrmartin has quit IRC07:02
*** Longgeek has quit IRC07:02
*** Longgeek has joined #openstack-meeting-307:03
*** coolsvap|afk is now known as coolsvap07:08
*** mrunge has joined #openstack-meeting-307:10
*** mrmartin has joined #openstack-meeting-307:22
*** armax has quit IRC07:29
*** mestery has quit IRC07:33
*** k4n0 has joined #openstack-meeting-307:38
*** k4n0 has quit IRC07:42
*** yapeng has joined #openstack-meeting-307:52
*** yapeng has quit IRC07:57
*** belmoreira has joined #openstack-meeting-308:04
*** mrmartin has quit IRC08:05
*** iovadia has joined #openstack-meeting-308:06
*** sahid has joined #openstack-meeting-308:08
*** jtomasek has joined #openstack-meeting-308:09
*** iovadia has quit IRC08:11
*** matrohon has joined #openstack-meeting-308:13
*** egallen has joined #openstack-meeting-308:14
*** wdutch has joined #openstack-meeting-308:14
*** mestery has joined #openstack-meeting-308:14
*** mrda is now known as mrda-away08:18
*** sergef has joined #openstack-meeting-308:22
*** belmoreira has quit IRC08:22
*** iovadia has joined #openstack-meeting-308:24
*** alexpilotti has joined #openstack-meeting-308:37
*** egallen has quit IRC08:38
*** jkraj has joined #openstack-meeting-308:40
*** egallen has joined #openstack-meeting-308:40
*** watanabe_isao has quit IRC08:47
*** qwebirc89656 has joined #openstack-meeting-308:49
*** qwebirc52590 has quit IRC08:52
*** JeanBriceCombebi has joined #openstack-meeting-308:55
*** salv-orlando has joined #openstack-meeting-309:00
*** safchain has joined #openstack-meeting-309:01
*** mrmartin has joined #openstack-meeting-309:01
*** salv-orlando has quit IRC09:06
*** JeanBriceCombebi has quit IRC09:07
*** romcheg has joined #openstack-meeting-309:11
*** yamahata has quit IRC09:13
*** devvesa has joined #openstack-meeting-309:21
*** jcoufal has joined #openstack-meeting-309:29
*** yapeng has joined #openstack-meeting-309:41
*** MaxV has joined #openstack-meeting-309:44
*** yapeng has quit IRC09:45
*** qwebirc89656 has quit IRC09:50
*** zz_ttrifonov is now known as ttrifonov09:58
*** nelsnelson has quit IRC10:01
*** nelsnelson has joined #openstack-meeting-310:02
*** belmoreira has joined #openstack-meeting-310:02
*** salv-orlando has joined #openstack-meeting-310:34
*** stanzgy has quit IRC10:52
*** iovadia has left #openstack-meeting-311:09
*** marun has quit IRC11:13
*** egallen has quit IRC11:22
*** marg7175 has joined #openstack-meeting-311:27
*** yapeng has joined #openstack-meeting-311:30
*** egallen has joined #openstack-meeting-311:34
*** yapeng has quit IRC11:34
*** egallen has quit IRC11:36
*** egallen has joined #openstack-meeting-311:38
*** egallen has quit IRC11:39
*** egallen has joined #openstack-meeting-311:40
*** cgascoig has quit IRC11:44
*** cgascoig has joined #openstack-meeting-311:49
*** marg7175 has quit IRC11:52
*** marg7175 has joined #openstack-meeting-311:52
*** nelsnelson has quit IRC11:54
*** vkmc has joined #openstack-meeting-312:01
*** mwagner_lap has quit IRC12:34
*** vineetmenon has quit IRC12:47
*** cgascoig has quit IRC13:00
*** banix has joined #openstack-meeting-313:10
*** yapeng has joined #openstack-meeting-313:19
*** banix has quit IRC13:19
*** xuhanp has joined #openstack-meeting-313:20
*** yapeng has quit IRC13:23
*** mwagner_lap has joined #openstack-meeting-313:24
*** alexpilotti has quit IRC13:26
*** baoli has joined #openstack-meeting-313:28
*** romcheg has quit IRC13:34
*** romcheg has joined #openstack-meeting-313:35
*** egallen has joined #openstack-meeting-313:40
*** VW_ has joined #openstack-meeting-313:47
*** jcoufal_ has joined #openstack-meeting-313:49
*** jcoufal has quit IRC13:52
*** jaypipes has joined #openstack-meeting-313:58
*** crobertsrh has joined #openstack-meeting-314:02
*** crobertsrh has left #openstack-meeting-314:04
*** thomasem has joined #openstack-meeting-314:12
*** thomasem has quit IRC14:16
*** thomasem has joined #openstack-meeting-314:19
*** thomasem has quit IRC14:19
*** thomasem has joined #openstack-meeting-314:24
*** sigmavirus24_awa is now known as sigmavirus2414:27
*** mrmartin has quit IRC14:27
*** jcoufal_ is now known as jcoufal14:29
*** alexpilotti has joined #openstack-meeting-314:30
*** peristeri has joined #openstack-meeting-314:31
*** belmoreira has quit IRC14:32
*** lblanchard has joined #openstack-meeting-314:33
*** thangp has joined #openstack-meeting-314:42
*** mattfarina has joined #openstack-meeting-314:44
*** pkoniszewski has joined #openstack-meeting-314:46
*** carl_baldwin has joined #openstack-meeting-314:52
*** mrsmith has joined #openstack-meeting-314:53
*** romcheg has left #openstack-meeting-314:56
*** mattfarina has quit IRC14:57
*** mattfarina has joined #openstack-meeting-314:57
*** yamahata has joined #openstack-meeting-314:57
*** pc_m has joined #openstack-meeting-314:59
*** Swami has joined #openstack-meeting-314:59
mrsmithhey Swami15:00
carl_baldwinhi all15:00
pc_mhi15:00
mrsmithhi carl_baldwin15:00
carl_baldwin#startmeeting neutron_l315:00
openstackMeeting started Thu Jan  8 15:00:57 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
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:00
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
Swamihi15:01
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam15:01
*** Rajeev has joined #openstack-meeting-315:01
carl_baldwin#info Kilo-2 will be on February 5th15:02
carl_baldwinAny other announcements?15:02
*** johnbelamaric has joined #openstack-meeting-315:02
carl_baldwin#topic Bugs15:03
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:03
carl_baldwinLooks like I need to triage a little but I don’t see any new bugs to discuss15:04
carl_baldwin#action carl_baldwin to triage new bugs15:04
carl_baldwin#topic L3 Agent Restructuring15:04
*** openstack changes topic to "L3 Agent Restructuring (Meeting topic: neutron_l3)"15:04
*** ChuckC has joined #openstack-meeting-315:05
carl_baldwinI’ve been making a lot of progres on this this week.15:05
carl_baldwin#link https://review.openstack.org/#/c/143733 is about ready to merge I think.15:06
carl_baldwinamuller: ping15:06
*** dboik has joined #openstack-meeting-315:06
*** yapeng has joined #openstack-meeting-315:08
*** MikeM_ has joined #openstack-meeting-315:08
carl_baldwinYesterday, I started teasing out fip namespace logic.  I would like eyes from Rajeev, mrsmith, and other dvr expertise here.15:08
carl_baldwin#link https://review.openstack.org/#/c/145565/15:08
mrsmithsure - no prob15:08
SwamiI will take a look at it15:09
carl_baldwinmrsmith: Swami: thanks.15:09
*** Rajeev_ has joined #openstack-meeting-315:10
pc_mCan use review of FW refactoring: #link https://review.openstack.org/14088415:10
pc_mWill then work on event handlers with SridarK15:11
carl_baldwinI think my patch changes the logic a bit.  I think it better acknowledges multiple external networks.15:11
mrsmithSwami and I are working thru issues already with multiple ext nets and dvr15:11
mrsmithall these refactors make for busy reabses15:12
mrsmith:)15:12
*** Rajeev has quit IRC15:12
*** yapeng has quit IRC15:13
carl_baldwinmrsmith: I know.  That’s why I want eyes on it right away.  It proved too difficult to do the floating ip refactoring without first working on the fip namespace.15:13
carl_baldwinpc_m: I will look today.15:13
pc_mcarl_baldwin: Thanks!15:13
carl_baldwin#action carl_baldwin will review https://review.openstack.org/#/c/140884/15:14
*** dboik_ has joined #openstack-meeting-315:16
*** Swami_ has joined #openstack-meeting-315:17
*** Swami has quit IRC15:17
carl_baldwinmrsmith: Swami: feel free to ping me with your concerns.  How has multiple ext-net progress been going?15:18
Swami_carl_baldwin: we have a couple of patches that we are working on right now.15:18
mrsmithgood - definitely need some dvr agent changes15:18
Swami_The final one is the "floatingip-namespace" correction. I am currently working on it.15:18
*** dboik has quit IRC15:19
carl_baldwinDo you have links to the patches handy?15:19
*** Longgeek has quit IRC15:19
Swami_#link https://review.openstack.org/#/c/142674/15:20
Swami_#link https://review.openstack.org/#/c/143567/15:20
Swami_These two above patches fixes the current exceptions that are raised.15:20
*** xuhanp has quit IRC15:20
Swami_As I mentioned we found an issue with the FIP namespace creation issues when there are more than one external network.15:21
mrsmiththe main issue is handling separate fip-namespaces for each ext net15:21
Swami_We are working on it and when we have a wip I will push it in.15:21
*** Longgeek has joined #openstack-meeting-315:21
carl_baldwinmrsmith: You will definitely want to check out this patch in that context: https://review.openstack.org/#/c/145565/15:22
*** etoews has joined #openstack-meeting-315:22
carl_baldwinHopefully we’re not going in incompatible directions.15:23
mrsmithcarl_baldwin: okay15:23
mrsmithas you know, refactoring and bug fixing can be hard to do at the same time :)15:23
mrsmithbut we have to make progress on the refactoring15:24
carl_baldwinmrsmith: I do know.  That is why I’m trying to call attention to what I’m doing very quickly rather than waiting to post the final result later.15:25
mrsmith+115:25
carl_baldwinmrsmith: Swami_:  Yesterday afternoon, I added this:  https://review.openstack.org/#/c/145565/3/neutron/agent/l3/dvr.py L4615:25
Swami_+115:26
carl_baldwinThe new fip namespace class takes the external network id.  Multiple instances are created.  This was something that the old code wasn’t careful about.15:27
carl_baldwinAnyway, we should move on.  Please ping me with your concerns.15:27
mrsmithyes - or just plain ignorant... adding an array is something Swami and I were thinking of15:27
mrsmithyup - thanks for working on this as always carl_baldwin15:28
carl_baldwinpc_m: Anything else?15:28
Swami_carl_baldwin: Just looking at your changes in the fip patch.15:28
pc_mno, i'm all set.15:28
Swami_That was exactly what we were thinking on15:28
*** lazy_prince is now known as killer_prince15:28
Swami_I will review your patch completely, test it and will provide my inputs.15:28
carl_baldwinSwami_: At least we’re thinking along the same lines.  I will appreciate that.15:29
carl_baldwin#topic neutron-ipam15:29
*** openstack changes topic to "neutron-ipam (Meeting topic: neutron_l3)"15:29
carl_baldwinjohnbelamaric: hi15:30
carl_baldwinsalv-orlando: ping15:30
johnbelamariccarl_baldwin: hello15:30
carl_baldwinAll the relevant blueprints are in good shape, I think.15:30
johnbelamaricyes. what do we need to get your interface merged?15:31
johnbelamaric#link https://review.openstack.org/#/c/134339/15:31
johnbelamaricmost of our team was out for the holidays but we should be able to get going on refactor soon15:32
carl_baldwinjohnbelamaric: I was hoping to see salv-orlando’s work show up as a dependant patch sometime soon.15:32
carl_baldwinjohnbelamaric: Also, seeing a start on the refactoring of neutron as a dependent patch soon would be nice.15:33
johnbelamariccarl_baldwin: ok15:33
carl_baldwinI was thinking that starting both those efforts may show where the interface is deficient.15:35
carl_baldwinjohnbelamaric: What do you  think?15:35
johnbelamariccarl_baldwin: yes, good point - we'll get started ASAP15:35
carl_baldwinjohnbelamaric: great!15:36
johnbelamariccarl_baldwin: might be conflicts with salv-orlando's work, but we will resolve when we see that15:36
carl_baldwinjohnbelamaric: I’ll watch out for conflicts.  Initially, there shouldn’t be much conflict as salv-orlando will be working on mostly new code.15:37
carl_baldwinjohnbelamaric: anything else to discuss?15:38
johnbelamariccarl_baldwin: right, but depending if he works on integrating it to the existing Db plugin. anyway, the bulk should be non-conflicting15:38
johnbelamariccarl_baldwin: nope15:38
salv-orlandoI am not sure I am working on new code. I am moving existing code into new places15:38
salv-orlandoalso - I am doing work dependent on patch #134339 and contextually removing existing IPAM logic in db_base_plugin_v215:39
salv-orlandonevertheless we should not stop each other fearing conflicts. Let's work independently and fix the conflicts when they arise15:39
johnbelamaricsalv-orlando: ok, will do15:40
carl_baldwinsalv-orlando: ok.  I misunderstood a bit.  I guess I thought that you would create new code without moving out the old implementation at first.  But, I’m okay with this too.15:40
*** pkoniszewski has quit IRC15:41
carl_baldwinsalv-orlando: agree about conflicts.15:41
salv-orlandocarl_baldwin: If I did so then we would have the new and old implementation at the same time - with the new one untestable beyond unit test. Nobody would let us merge that.15:41
salv-orlandoBut on the other hand we can still have a 3rd patch in the same patch series which does the cleanup in neutron and hooks the new logic15:42
salv-orlandoI mean does the "glueing"15:42
*** fischerw has joined #openstack-meeting-315:42
carl_baldwinsalv-orlando: I’ll let you go about your business.  Don’t want to tell you how to get it done.15:42
carl_baldwinsalv-orlando: Anything else to update?15:43
salv-orlandocarl_baldwin: you can I won't get offended15:43
salv-orlandocarl_baldwin: I have nothing else on IPAM or anything l315:44
carl_baldwinsalv-orlando: thanks for the update.  I look forward to the ipam patch(es)15:44
salv-orlandoI am dealing with the aftermath of setting dnsmasq minimum requirement to 2.67, but that's not something that should concern you here ;)15:44
carl_baldwinsalv-orlando: I saw that going on.  Hope you get that straightened out without too much trouble.15:45
carl_baldwinsalv-orlando: johnbelamaric thanks.15:45
carl_baldwin#topic neutron-ovs-dvr15:45
*** openstack changes topic to "neutron-ovs-dvr (Meeting topic: neutron_l3)"15:45
salv-orlandocarl_baldwin: there is no trouble unless you have consumers insisting on using ubuntu 12.04 ;)15:45
Swami_carl_baldwin: I need to drop off, mike will provide the update on dvr15:46
carl_baldwinSwami_: thanks15:46
mrsmithwe already talked about multi-ext-nets15:46
*** Swami_ has quit IRC15:46
mrsmithRajeev and I are making progress on dvr-l3-ha15:46
mrsmithkeeping up with the refactoring15:47
*** banix has joined #openstack-meeting-315:47
Rajeev_Links to patches : https://review.openstack.org/#/c/139686/15:47
*** gholler has joined #openstack-meeting-315:47
* carl_baldwin is just making life difficult everywhere for you, isn’t he?15:48
Rajeev_https://review.openstack.org/#/c/143169/15:48
mrsmithjust keeping things interesting carl_baldwin ;)15:48
mrsmithdvr-l3-ha is still wip15:48
Rajeev_carl_baldwin: our turn will come too :)15:48
mrsmithbut we are close15:48
mrsmiththe l2pop patch seems stalled15:49
*** rcleere is now known as rcleere_away15:49
mrsmithto fix l3-ha running with l2pop15:49
mrsmithwe will need that to get fixed for dvr-l3-ha to work15:49
*** rcleere_away is now known as rcleere15:50
carl_baldwinmrsmith: link handy?15:50
mrsmithno.... let me try to find it15:50
carl_baldwinRajeev_: Did you see the discussion earlier on https://review.openstack.org/#/c/145565 ?15:51
Rajeev_carl_baldwin: no, but I will take a look at it and catch up from mrsmith15:51
carl_baldwinRajeev_: I would value your feedback on it.15:51
Rajeev_carl_baldwin: will do15:52
*** marun has joined #openstack-meeting-315:52
mrsmithhere is the stalled l2pop patch:15:53
carl_baldwinRajeev_: regarding HA/DVR, have you seen https://review.openstack.org/#/c/143733 ?15:53
mrsmithhttps://review.openstack.org/#/c/141114/15:53
Rajeev_carl_baldwin: This is the refactoring into derived classes for dvr agent side.15:54
carl_baldwin#action carl_baldwin will review https://review.openstack.org/#/c/141114/ today15:55
carl_baldwinRajeev_: Yes.  I’d value some feedback in the context of enabling dvr with ha.15:55
*** coolsvap is now known as coolsvap|afk15:55
Rajeev_carl_baldwin: will take a look with mrsmith as he is focusing on agent side ha dvr work.15:56
carl_baldwinI’d also like amuller to take a look but I’ve just heard he’ll be out for a week.15:56
*** zz_jgrimm is now known as jgrimm15:56
mrsmithcarl_baldwin: fyi I think I've already hit some oddities while using mixins and trying to implement ha and dvr15:57
mrsmithso the derived classes may help15:57
*** kaufer has joined #openstack-meeting-315:58
carl_baldwinWe’re about out of time.  I’ve got to be offline to get in to the office but should be around the rest of the day.15:59
carl_baldwinThanks for all of your work.  Let’s communicate often during this refactoring.  We’ll get through it and I think we’ll be better off for it.16:00
carl_baldwin#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Thu Jan  8 16:00:22 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-01-08-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-01-08-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-01-08-15.00.log.html16:00
*** baoli has quit IRC16:00
*** carl_baldwin has quit IRC16:01
*** igordcard has joined #openstack-meeting-316:01
*** baoli has joined #openstack-meeting-316:02
*** pc_m has left #openstack-meeting-316:02
*** igordcard has quit IRC16:04
*** mrsmith has quit IRC16:04
*** johnbelamaric has left #openstack-meeting-316:04
*** igordcard has joined #openstack-meeting-316:04
*** MikeM_ has quit IRC16:05
*** igordcard has quit IRC16:06
*** igordcard has joined #openstack-meeting-316:06
*** kaufer has left #openstack-meeting-316:20
*** ChuckC_ has joined #openstack-meeting-316:21
*** ChuckC has quit IRC16:22
*** sahid has quit IRC16:23
*** ivar-lazzaro has joined #openstack-meeting-316:27
*** ChuckC_ has quit IRC16:28
*** jkraj has quit IRC16:30
*** carl_baldwin has joined #openstack-meeting-316:31
*** VW_ has quit IRC16:31
*** bpokorny has joined #openstack-meeting-316:31
*** armax has joined #openstack-meeting-316:31
*** VW_ has joined #openstack-meeting-316:33
*** reed has joined #openstack-meeting-316:55
*** yapeng has joined #openstack-meeting-316:57
*** ChuckC_ has joined #openstack-meeting-316:58
*** ChuckC_ has quit IRC16:59
*** ChuckC_ has joined #openstack-meeting-316:59
*** Piet has quit IRC17:00
*** ChuckC_ has quit IRC17:01
*** bpokorny_ has joined #openstack-meeting-317:01
*** yapeng has quit IRC17:01
*** ChuckC_ has joined #openstack-meeting-317:01
*** ChuckC_ is now known as ChuckC17:02
*** ChuckC has quit IRC17:03
*** chuckC_ has joined #openstack-meeting-317:04
*** bpokorny has quit IRC17:04
*** egallen has quit IRC17:05
*** andymaier has joined #openstack-meeting-317:05
*** thomasem has quit IRC17:16
*** safchain has quit IRC17:18
*** cbader has joined #openstack-meeting-317:19
*** devvesa has quit IRC17:21
*** yamahata has quit IRC17:23
*** wuhg has quit IRC17:24
*** andymaier has quit IRC17:24
*** SridharRamaswamy has joined #openstack-meeting-317:28
*** sunny_ has joined #openstack-meeting-317:33
*** matrohon has quit IRC17:36
*** sunny_ has quit IRC17:38
*** eghobo has joined #openstack-meeting-317:39
*** dboik_ has quit IRC17:40
*** mageshgv has joined #openstack-meeting-317:42
*** egallen has joined #openstack-meeting-317:43
*** jcoufal has quit IRC17:44
*** mwagner_lap has quit IRC17:48
*** s3wong has joined #openstack-meeting-317:54
*** yapeng_ has joined #openstack-meeting-317:56
*** yamahata has joined #openstack-meeting-317:57
*** rkukura has joined #openstack-meeting-317:58
*** wdutch has quit IRC17:59
banixhi18:01
rkukurahi18:01
s3wonghello18:01
banixGBP meeting wasn’t canceled or was it?18:02
rkukuradon’t think so18:03
s3wongbanix: don't know, and I don't see SumitNaiksatam online...18:03
*** MaxV has quit IRC18:03
rkukuraI just sent him an email.18:04
*** banix has left #openstack-meeting-318:04
*** banix has joined #openstack-meeting-318:04
s3wongand banix has left :-)18:05
banixno i am here :) just got disconnected18:05
*** mrmartin has joined #openstack-meeting-318:05
banixgreat job you all for getting the first release18:06
rkukurahe says he’s in18:06
*** SumitNaiksatam has joined #openstack-meeting-318:06
rkukuraSumitNaiksatam: hi18:06
SumitNaiksatamrkukura: hi18:07
SumitNaiksatamsome issue with my client, perhaps because of the VPN18:07
*** dtroyer has left #openstack-meeting-318:07
*** bpokorny has joined #openstack-meeting-318:07
SumitNaiksatami kept pinging everyone but i dont think you saw it18:07
SumitNaiksatamivar-lazzaro: mageshgv s3wong banix: hi18:07
s3wongSumitNaiksatam: hello18:07
banixSumitNaiksatam: hi18:07
ivar-lazzarohi18:07
SumitNaiksatamapologies for the delay, lets get started18:07
mageshgvsumitNaiksatam: hi18:08
yapeng_hello :)18:08
SumitNaiksatam#startmeeting networking_policy18:08
openstackMeeting started Thu Jan  8 18:08:17 2015 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:08
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:08
*** openstack changes topic to " (Meeting topic: networking_policy)"18:08
openstackThe meeting name has been set to 'networking_policy'18:08
*** mwagner_lap has joined #openstack-meeting-318:08
*** Youcef has joined #openstack-meeting-318:08
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy#Jan_8th.2C_201418:08
SumitNaiksatamoh firstly, Happy New Year to all (our first meeting of the year)!18:09
banixGreat job you all for getting the first release out18:09
SumitNaiksatambanix: thanks18:09
SumitNaiksatamgood segue18:09
SumitNaiksatam#topic GBP Release18:09
*** openstack changes topic to "GBP Release (Meeting topic: networking_policy)"18:09
*** bpokorny_ has quit IRC18:10
*** pballand has joined #openstack-meeting-318:10
SumitNaiksatamindeed, congratulations to the team!18:10
ivar-lazzaroyeah!18:10
SumitNaiksatamivar-lazzaro: mageshgv: you guys did some enormous amount of heavy lifting towards the end, BIG thank you!18:10
*** KrishnaK_ has joined #openstack-meeting-318:10
rkukura+218:11
SumitNaiksatamrkukura is also making excellent progress with the packaging, but will come to that in the next topic18:11
SumitNaiksatamjust want to give it a few minutes here to digest exactly what is in the release18:12
SumitNaiksatamwe put some very basic release notes here: #link https://wiki.openstack.org/wiki/GroupBasedPolicy/ReleaseNotes/Juno18:13
SumitNaiksatamthis is missing the bit on the “external connectivity” model18:13
SumitNaiksatamamong other things18:13
*** Networkn3rd has joined #openstack-meeting-318:13
*** dboik has joined #openstack-meeting-318:14
SumitNaiksatamso once we add those details and (rkukura is done with the fedora packaging) i think we should be ready to formally announce the release18:14
SumitNaiksatamthoughts?18:14
* ivar-lazzaro looks around18:14
rkukurasounds good to me18:14
ivar-lazzaroSumitNaiksatam: I can take care of the external connectivity (or at least I can help if someone else is brave enough to volunteer :) )18:15
yapeng_SumitNaiksatam: sounds great, will there any debian package activity for Juno release?18:15
SumitNaiksatamivar-lazzaro: i will not take the bait ;-)18:15
ivar-lazzaroSumitNaiksatam: :D18:15
SumitNaiksatamyapeng_: hi18:15
*** clu_ has joined #openstack-meeting-318:16
SumitNaiksatamyapeng_: yes, mandeep has release the release candidates to PPA18:16
SumitNaiksatamone sec, let me post the link18:16
SumitNaiksatam#link https://launchpad.net/~group-based-policy-drivers/+archive/ubuntu/ppa18:16
yapeng_SumitNaiksatam: thanks.18:17
SumitNaiksatamyou will see the release tarballs here18:17
*** garyduan has joined #openstack-meeting-318:17
SumitNaiksatamhe just did not get a chance to post it, but its ready18:17
*** SridharRamaswamy has quit IRC18:17
SumitNaiksatamyapeng_: thanks also for your fantastic effort on the ODL front!18:17
SumitNaiksatamyapeng_: and for keeping the devstack branch in sync through all the churn18:18
SumitNaiksatamat some point (sooner than later) we will target the installers as well18:19
*** gduan has quit IRC18:19
SumitNaiksatambut first get the packages in place, and then the installers18:19
SumitNaiksatamcurrently the easiest way obviously is to use devstack18:19
SumitNaiksatamany thoughts/comments/suggestions/questions on the release details on the process?18:20
rkukuraUsing RDO will be the easiest by the end of today, I think18:20
SumitNaiksatamrkukura: ah ok18:20
SumitNaiksatamrkukura: packaging next topic coming up18:20
SumitNaiksatam#topic GBP Packaging18:21
*** openstack changes topic to "GBP Packaging (Meeting topic: networking_policy)"18:21
SumitNaiksatamlike i mentioned earlier, rkukura has been deligently pursuing the fedora/RH side of things18:21
SumitNaiksatamrkukura: over to you18:21
rkukuraOK18:22
*** songole has joined #openstack-meeting-318:22
rkukuraThe final server package for Fedora rawhide (f22) is at https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/x86_64/os/Packages/o/openstack-neutron-gbp-2014.2-1.fc22.noarch.rpm18:22
rkukuraSo anyone running f22 can just do “yum install openstack-neutron-gbp”.18:22
rkukuraThe other three packages (CLI, UI, automation) are still based on the latest RCs, but should all be updated to final releases today.18:23
rkukuraThe horizon integration works, but the Red Hat Horizon maintainer may think we should be doing some things a bit differently. I’ll continue to work with him on this, but I hope my current approach will be acceptable for now.18:24
rkukuraSo I’m building all these packages for Fedora 20, 21, and 22, as well as EPEL7 which should work on RHEL 7 and CentOS 7.18:25
*** sergef has quit IRC18:25
rkukuraUntil GBP gets incorporated into RDO, these packages can be installed manually on top of an existing RDO deployment on any of those platforms.18:25
rkukuraI’ll update the RDO GBP wiki instructions once all packages are ready.18:26
SumitNaiksatamrkukura: awesome18:26
rkukuraThen we’ll work with Red Hat to get the packages included in RDO, which will make things a bit easier.18:26
SumitNaiksatamrkukura: so they did not like the Horizon sub packages?18:26
rkukuraSumitNaiksatam: The sub package is needed, but they also do some stuff with compressing stuff and may have a different way of installing the panels that what we are currently doing.18:27
SumitNaiksatamrkukura: oh ok18:27
SumitNaiksatami guess we learn :-)18:27
rkukuraI think we should be able to update to our release tarballs with the existing approach, then figure out whether we need to change something for in an update to Juno and/or in our Kilo versions.18:28
SumitNaiksatamrkukura: ok18:28
rkukuraWe’ll also need to get working on puppet support that can be used by RDO’s packstack and foreman installers.18:28
rkukuraThat’s it for me.18:29
SumitNaiksatamrkukura: yes, once we have the packages we can do that18:29
SumitNaiksatamrkukura: for puppet, i am guessing we have to push some patches somewhere, to where is that?18:29
SumitNaiksatamrkukura: and for foreman as well18:29
*** carl_baldwin has quit IRC18:30
rkukuraSumitNaiksatam: I think we need to start with patches to the upstream puppet modules18:30
rkukuraUnless RDO has forks of these, but I think upstream first will be the way to go18:30
SumitNaiksatamrkukura: is upstream in stackforge or something totally different?18:31
rkukuraThen packstack and foreman will need to be patched to use the updated puppet modules18:31
rkukuraSumitNaiksatam: Not sure.18:31
rkukuraWould be great to get someone with some puppet experience involved in that.18:32
*** sunny_ has joined #openstack-meeting-318:32
*** baoli has quit IRC18:32
SumitNaiksatamrkukura: sure, i had done bit of puppet before, but have forgotten since18:32
SumitNaiksatamrkukura: but we have ratnakar in the team, lets check with him once we are done with the packaging18:33
rkukuraSumitNaiksatam: right18:33
*** dboik_ has joined #openstack-meeting-318:33
SumitNaiksatamanyone else wanting to take a stab at it, you are more than welcome!18:33
SumitNaiksatamrkukura but the cool thing is you were able to test end-to-end with the UI packages on fedora, right?18:33
rkukuraSumitNaiksatam: definitely!18:34
SumitNaiksatamrkukura: nice18:34
SumitNaiksatamany other questions for rkukura or packaging in general?18:34
SumitNaiksatamrkukura: so fedora packages today, right?18:35
rkukurathat’s the plan, unless the person at Red Hat insists we hold off on the horizon integration18:35
SumitNaiksatamrkukura: ah ok, got it18:35
SumitNaiksatam#topic GBP Kilo18:35
*** openstack changes topic to "GBP Kilo (Meeting topic: networking_policy)"18:36
SumitNaiksatamso at this point we have two branches18:36
rkukuraAnyone want to test the RDO instructions when I’ve updated them?18:36
*** dboik has quit IRC18:36
SumitNaiksatam#undo18:36
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x3bb4490>18:36
SumitNaiksatamrkukura: definitely18:36
SumitNaiksatamrkukura: you will be updating the wiki page?18:36
rkukurayes18:36
SumitNaiksatam#link https://openstack.redhat.com/Neutron_GBP18:37
rkukuraI’ll update it to include the horizon and heat parts, and with links to the final RPMs18:37
KrishnaK_rkukura: I can spend time with RDO testing ...18:37
rkukuraKrishnaK_: great - thanks!18:37
SumitNaiksatamall installation instructions are currently linked from: #link https://wiki.openstack.org/wiki/GroupBasedPolicy#Try_Group-based_Policy18:37
SumitNaiksatamKrishnaK_: thats great, and also thanks to you for fix bugs, even during the official shutdown!18:38
SumitNaiksatam#topic GBP Kilo18:39
*** openstack changes topic to "GBP Kilo (Meeting topic: networking_policy)"18:39
SumitNaiksatamso as i was saying - at this point we have two branches18:39
SumitNaiksatammaster continues to Kilo18:39
SumitNaiksatamand we have stable/juno18:39
SumitNaiksatamso any bug fixes can be backported18:39
SumitNaiksatamstandard process like other projects18:40
*** banix_ has joined #openstack-meeting-318:40
SumitNaiksatamwe already have a few blueprints proposed which we delayed on account of this release18:40
SumitNaiksatamis louis or cathy here?18:40
SumitNaiksatammy bad, i have not fixed the specs repo for a UT failure, so havent created the kilo directory yet18:41
SumitNaiksatamwill do18:41
SumitNaiksatami think most of us have been pretty much heads down into the release effort, did not get much chance to plan beyond that18:42
SumitNaiksatamanything to discuss here?18:42
*** bouthors has joined #openstack-meeting-318:42
SumitNaiksatambouthors: hi, great timing18:43
bouthorsSumitNaiksatam: hi18:43
SumitNaiksatambouthors: we were just touching on the topic of kilo blueprints18:43
SumitNaiksatambouthors: we are just wrapping up the Juno release, and Kilo branch is open18:43
SumitNaiksatambouthors: hopefully we will get to reviewing the specs soon and making progress18:43
SumitNaiksatambouthors: feel free to post code patches if you have gotten that far18:44
*** banix_ has quit IRC18:44
bouthorsSumitNaiksatam:ok18:45
SumitNaiksatambouthors: and we can sync up offline as well18:45
*** KrishnaK_ has quit IRC18:45
*** yapeng has joined #openstack-meeting-318:45
SumitNaiksatam#topic Open Discussion18:45
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"18:46
bouthorsHow can we sync up with ODL GBP on L7 extensions ?18:46
SumitNaiksatambouthors: sure18:46
*** KrishnaK_ has joined #openstack-meeting-318:46
SumitNaiksatambouthors: you mean leverage current ODL GBP integration?18:47
bouthorsyes18:47
SumitNaiksatambouthors: okay, one thing i would suggest is deploying based on the instructions provided by yapeng: #link https://wiki.openstack.org/wiki/GroupBasedPolicy/InstallODLIntegrationDevstack18:48
bouthorsSumitNaiksatam:  I will have a look18:48
*** rcleere is now known as rcleere_away18:48
SumitNaiksatambouthors: once you are at that point, it might be easier to have an informed discussion, since that way you will know exactly what is available today18:48
SumitNaiksatambouthors: and we can explore how we can extend that in implementation to match the L7 classification spec18:49
SumitNaiksatambouthors: we can involve some of the folks on the ODL side as well18:49
SumitNaiksatambouthors: sound okay?18:49
bouthorsSumitNaiksatam: excellent. This gives me a way to go18:49
bouthorsSumitNaiksatam: excellent. This gives me a way to go ahead18:49
SumitNaiksatambouthors: cool18:49
SumitNaiksatamat my end, i wanted to propose an addition to the GBP core team18:50
*** MaxV has joined #openstack-meeting-318:50
*** yapeng has quit IRC18:50
SumitNaiksatammageshgv has contributed an enormous amount, and is very familiar the GBP codebase, so i would like to propose him to the GBP core team18:51
ivar-lazzaroSumitNaiksatam: +1!18:51
SumitNaiksatamwhat does the team think about it?18:51
rkukuraSumitNaiksatam: +118:51
songoleSumitNaiksatam: +1  for Mageshgv18:51
KrishnaK_SumitNaiksatam: +1  for Mageshgv18:51
SumitNaiksatamok great18:52
s3wong+118:52
*** sunny_ has quit IRC18:52
SumitNaiksatamper standard process, i will send out an email to the openstack-dev with the proposal18:52
SumitNaiksatamjust want to get some preliminary consensus here18:52
*** thomasem has joined #openstack-meeting-318:52
SumitNaiksatamyou can respond in the dev ML if you have any objections18:52
SumitNaiksatamthanks again mageshgv for the great work!18:53
*** baoli has joined #openstack-meeting-318:53
*** rcleere_away is now known as rcleere18:53
SumitNaiksatamthats all i have for today18:53
mageshgvThanks Everyone !!18:53
SumitNaiksatamanything anyone else want to bring up?18:53
*** sunny_ has joined #openstack-meeting-318:53
SumitNaiksatamthanks everyone for joining18:54
SumitNaiksatamsee you next week!18:54
SumitNaiksatambye18:54
banix SumitNaiksatam: +118:54
s3wongbye18:54
KrishnaK_bye18:54
rkukurabye18:54
SumitNaiksatambanix: thanks :-)18:54
ivar-lazzarociao!18:54
mageshgvbye18:54
bouthorsbye18:54
songolebye18:54
rkukurathanks SumitNaiksatam!18:54
SumitNaiksatam#endmeeting18:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:54
openstackMeeting ended Thu Jan  8 18:54:48 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-01-08-18.08.html18:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-01-08-18.08.txt18:54
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-01-08-18.08.log.html18:54
*** mageshgv has quit IRC18:54
*** rkukura has left #openstack-meeting-318:55
*** etoews has quit IRC18:59
*** etoews has joined #openstack-meeting-319:00
*** dboik_ has quit IRC19:00
*** dboik has joined #openstack-meeting-319:00
*** dboik has quit IRC19:03
*** bouthors has quit IRC19:03
*** bpokorny_ has joined #openstack-meeting-319:03
*** dboik has joined #openstack-meeting-319:03
*** bpokorny has quit IRC19:06
*** baoli has quit IRC19:13
*** alexpilotti has quit IRC19:14
*** ivar-lazzaro has quit IRC19:17
*** igordcard has quit IRC19:23
*** etoews has quit IRC19:26
*** etoews has joined #openstack-meeting-319:26
*** mrmartin has quit IRC19:28
*** ameade_ is now known as ameade19:29
*** chuckC__ has joined #openstack-meeting-319:29
*** chuckC_ has quit IRC19:30
*** chuckC_ has joined #openstack-meeting-319:33
*** chuckC__ has quit IRC19:34
*** Longgeek has quit IRC19:34
*** s3wong has quit IRC19:35
*** Longgeek has joined #openstack-meeting-319:36
*** chuckC_ has quit IRC19:38
*** chuckC_ has joined #openstack-meeting-319:39
*** pballand has quit IRC19:39
*** ChuckC has joined #openstack-meeting-319:39
*** Longgeek has quit IRC19:41
*** banix has quit IRC19:48
*** carl_baldwin has joined #openstack-meeting-319:48
*** jtomasek has quit IRC19:48
*** pballand has joined #openstack-meeting-319:54
*** pballand has quit IRC19:54
*** thangp has quit IRC19:56
*** SumitNaiksatam has quit IRC19:56
*** pballand has joined #openstack-meeting-320:00
*** bpokorny has joined #openstack-meeting-320:02
*** mrunge has quit IRC20:03
*** bpokorny_ has quit IRC20:05
*** aleksandr_null has joined #openstack-meeting-320:06
*** pballand has quit IRC20:06
*** KrishnaK_ has quit IRC20:08
*** pballand has joined #openstack-meeting-320:09
*** banix has joined #openstack-meeting-320:09
*** thomasem has quit IRC20:11
*** etoews has quit IRC20:14
*** sunny_ has quit IRC20:14
*** thomasem has joined #openstack-meeting-320:19
*** etoews has joined #openstack-meeting-320:19
*** SridharRamaswamy has joined #openstack-meeting-320:19
*** dboik has quit IRC20:29
*** dboik has joined #openstack-meeting-320:30
*** yapeng has joined #openstack-meeting-320:34
*** yapeng has quit IRC20:39
*** sunny_ has joined #openstack-meeting-320:45
*** mrmartin has joined #openstack-meeting-320:50
*** sunny_ has quit IRC20:50
*** mrmartin has quit IRC20:51
*** david-lyle has joined #openstack-meeting-320:54
*** dboik has quit IRC20:56
*** dboik has joined #openstack-meeting-320:57
*** pballand has quit IRC20:59
*** pballand has joined #openstack-meeting-321:01
*** markvoelker has joined #openstack-meeting-321:04
*** mrda-away is now known as mrda21:04
*** chuckC_ has quit IRC21:11
*** dboik has quit IRC21:13
*** dboik has joined #openstack-meeting-321:14
*** dboik has quit IRC21:14
*** dboik has joined #openstack-meeting-321:14
*** marg7175 has quit IRC21:15
*** dboik has quit IRC21:17
*** dboik has joined #openstack-meeting-321:18
*** baoli has joined #openstack-meeting-321:20
*** dboik has quit IRC21:20
*** dboik has joined #openstack-meeting-321:21
*** baoli has quit IRC21:22
*** baoli has joined #openstack-meeting-321:23
*** dboik has quit IRC21:25
*** dboik has joined #openstack-meeting-321:26
*** mwang2 has joined #openstack-meeting-321:27
*** thomasem has quit IRC21:33
*** sergef has joined #openstack-meeting-321:33
*** thomasem has joined #openstack-meeting-321:34
*** sunny_ has joined #openstack-meeting-321:38
*** carl_baldwin has quit IRC21:40
*** bpokorny_ has joined #openstack-meeting-321:40
*** cgascoig has joined #openstack-meeting-321:42
*** bpokorny has quit IRC21:44
*** ycombinator_ has joined #openstack-meeting-321:52
*** fischerw has quit IRC22:03
*** fischerw has joined #openstack-meeting-322:03
*** cbader has quit IRC22:07
*** fischerw has quit IRC22:09
*** dboik has quit IRC22:11
*** lblanchard has quit IRC22:11
*** dboik has joined #openstack-meeting-322:11
*** songole has quit IRC22:13
*** fischerw has joined #openstack-meeting-322:15
*** pballand has quit IRC22:19
*** yapeng has joined #openstack-meeting-322:23
*** ycombinator_ has quit IRC22:23
*** pballand has joined #openstack-meeting-322:23
*** ycombinator_ has joined #openstack-meeting-322:26
*** mwagner_lap has quit IRC22:28
*** david-lyle has quit IRC22:28
*** yapeng has quit IRC22:28
*** Rockyg has joined #openstack-meeting-322:34
*** peristeri has quit IRC22:35
*** ivar-lazzaro has joined #openstack-meeting-322:43
*** flaper87 is now known as TheGuy22:45
*** gholler has quit IRC22:48
*** thomasem has quit IRC22:49
*** pballand has quit IRC22:50
*** pballand has joined #openstack-meeting-322:51
*** carl_baldwin has joined #openstack-meeting-322:51
*** bpokorny has joined #openstack-meeting-322:56
*** bpokorny_ has quit IRC22:59
*** pballand has quit IRC23:00
*** sigmavirus24 is now known as sigmavirus24_awa23:01
*** sergef has quit IRC23:02
*** TheGuy is now known as flaper8723:06
*** pballand has joined #openstack-meeting-323:07
*** yapeng has joined #openstack-meeting-323:09
*** Rockyg has quit IRC23:09
*** etoews has quit IRC23:11
*** pballand has quit IRC23:14
*** pballand has joined #openstack-meeting-323:14
*** banix has quit IRC23:19
*** mattfarina has quit IRC23:22
*** VW_ has quit IRC23:24
*** dboik has quit IRC23:24
*** sarob has joined #openstack-meeting-323:27
*** MaxV has quit IRC23:31
*** fischerw has quit IRC23:31
*** watanabe_isao has joined #openstack-meeting-323:34
*** pballand has quit IRC23:44
*** ivar-lazzaro has quit IRC23:49
*** cgascoig has quit IRC23:51
*** cgascoig_ has joined #openstack-meeting-323:51
*** dboik_ has joined #openstack-meeting-323:57
*** banix has joined #openstack-meeting-323:59

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