Wednesday, 2014-05-28

*** vkmc has quit IRC00:00
*** lcheng_ has joined #openstack-meeting-300:03
*** banix has quit IRC00:08
*** otherwiseguy has quit IRC00:10
*** otherwiseguy has joined #openstack-meeting-300:11
*** lcheng_ has quit IRC00:15
*** otherwiseguy has quit IRC00:17
*** shakamunyi has quit IRC00:18
*** SumitNaiksatam_ has joined #openstack-meeting-300:22
*** SumitNaiksatam has quit IRC00:23
*** SumitNaiksatam_ is now known as SumitNaiksatam00:23
*** chuckC has quit IRC00:24
*** SumitNaiksatam has quit IRC00:28
*** briancurtin has joined #openstack-meeting-300:38
*** Sukhdev has quit IRC00:38
*** yamahata has joined #openstack-meeting-300:39
*** kenhui has joined #openstack-meeting-300:40
*** SumitNaiksatam has joined #openstack-meeting-300:46
*** tomoe_ has quit IRC00:46
*** banix has joined #openstack-meeting-300:53
*** chuckC has joined #openstack-meeting-301:10
*** iben has quit IRC01:14
*** iben has joined #openstack-meeting-301:24
*** rgbkrk has quit IRC01:24
*** kenhui has quit IRC01:25
*** rgbkrk has joined #openstack-meeting-301:25
*** eguz has quit IRC01:27
*** kenhui has joined #openstack-meeting-301:29
*** kenhui has quit IRC01:29
*** kenhui has joined #openstack-meeting-301:29
*** kenhui1 has joined #openstack-meeting-301:39
*** kenhui has quit IRC01:41
*** thomasem has joined #openstack-meeting-301:46
*** thomasem has quit IRC01:46
*** thomasem has joined #openstack-meeting-301:49
*** tomoe_ has joined #openstack-meeting-301:49
*** kenhui1 has quit IRC01:50
*** thomasem_ has joined #openstack-meeting-301:52
*** thomasem has quit IRC01:53
*** nati_uen_ has quit IRC02:13
*** iben has quit IRC02:20
*** thomasem_ has quit IRC02:27
*** banix_ has joined #openstack-meeting-302:30
*** banix has quit IRC02:33
*** banix_ is now known as banix02:33
*** kenhui has joined #openstack-meeting-302:45
*** otherwiseguy has joined #openstack-meeting-302:49
*** thomasem has joined #openstack-meeting-302:50
*** kenhui has quit IRC02:51
*** thomasem has quit IRC02:51
*** kenhui has joined #openstack-meeting-302:51
*** otherwiseguy has quit IRC02:54
*** kenhui1 has joined #openstack-meeting-303:15
*** carl_baldwin has joined #openstack-meeting-303:17
*** kenhui has quit IRC03:18
*** kenhui1 has quit IRC03:18
*** kenhui has joined #openstack-meeting-303:19
*** shakamunyi has joined #openstack-meeting-303:19
*** beyounn_1 has quit IRC03:21
*** kenhui has quit IRC03:21
*** thomasem has joined #openstack-meeting-303:22
*** shakamunyi has quit IRC03:24
*** eghobo has joined #openstack-meeting-303:33
*** thomasem has quit IRC03:44
*** shakamunyi has joined #openstack-meeting-303:53
*** david-lyle has joined #openstack-meeting-304:01
*** shakamunyi has quit IRC04:27
*** otherwiseguy has joined #openstack-meeting-304:35
*** lcheng_ has joined #openstack-meeting-304:36
*** garyk has quit IRC04:37
*** shakamunyi has joined #openstack-meeting-304:52
*** shakamunyi has quit IRC04:54
*** david-lyle has quit IRC04:57
*** david-lyle has joined #openstack-meeting-304:57
*** david-lyle has quit IRC05:02
*** carl_baldwin has quit IRC05:09
*** shakamunyi has joined #openstack-meeting-305:11
*** otherwiseguy has quit IRC05:21
*** rgbkrk_ has joined #openstack-meeting-305:25
*** rgbkrk has quit IRC05:25
*** alexpilotti has quit IRC05:26
*** shakamunyi has quit IRC05:40
*** baojg has joined #openstack-meeting-305:40
*** shakamunyi has joined #openstack-meeting-305:40
*** baojg_ has joined #openstack-meeting-305:47
*** baojg_ has quit IRC05:50
*** baojg_ has joined #openstack-meeting-305:50
*** baojg has quit IRC05:51
*** rgbkrk_ has quit IRC05:51
*** markmcclain has joined #openstack-meeting-305:52
*** markmcclain1 has joined #openstack-meeting-305:54
*** alexpilotti has joined #openstack-meeting-305:54
*** markmcclain has quit IRC05:57
*** alexpilotti has quit IRC05:59
*** markmcclain1 has quit IRC06:01
*** eghobo has quit IRC06:05
*** alexpilotti has joined #openstack-meeting-306:08
*** garyk has joined #openstack-meeting-306:38
*** boris-42 has quit IRC06:45
*** boris-42 has joined #openstack-meeting-306:49
*** lcheng_ has quit IRC06:52
*** eghobo has joined #openstack-meeting-306:58
*** mrunge has joined #openstack-meeting-307:06
*** mrunge has quit IRC07:11
*** mrunge has joined #openstack-meeting-307:12
*** jcoufal has joined #openstack-meeting-307:28
*** ttrifonov_zZzz is now known as ttrifonov07:29
*** banix has quit IRC07:31
*** eghobo has quit IRC07:44
*** baojg_ has quit IRC07:49
*** baojg has joined #openstack-meeting-307:51
*** igordcard has joined #openstack-meeting-307:52
*** markmcclain has joined #openstack-meeting-307:55
*** ttrifonov is now known as ttrifonov_zZzz07:59
*** ttrifonov_zZzz is now known as ttrifonov07:59
*** markmcclain has quit IRC08:00
*** coolsvap|afk is now known as coolsvap08:11
*** tomoe__ has joined #openstack-meeting-308:22
*** tomoe_ has quit IRC08:23
*** amotoki has joined #openstack-meeting-308:30
*** nacim has joined #openstack-meeting-308:32
*** shakamunyi has quit IRC08:43
*** markmcclain has joined #openstack-meeting-308:50
*** garyk has quit IRC08:58
*** nacim has quit IRC09:21
*** yamahata has quit IRC09:22
*** markmcclain has quit IRC09:24
*** tomoe__ has quit IRC09:32
*** shakamunyi has joined #openstack-meeting-309:40
*** shakamunyi has quit IRC09:45
*** nacim has joined #openstack-meeting-309:48
*** boris-42 has quit IRC09:52
*** markmcclain has joined #openstack-meeting-309:54
*** boris-42 has joined #openstack-meeting-310:15
*** jtomasek has joined #openstack-meeting-310:20
*** nacim has quit IRC10:25
*** markmcclain has quit IRC10:50
*** baojg has quit IRC11:09
*** tomoe_ has joined #openstack-meeting-311:10
*** baojg has joined #openstack-meeting-311:10
*** tomoe_ has quit IRC11:14
*** baojg has quit IRC11:15
*** igordcard has quit IRC11:30
*** coolsvap is now known as coolsvap|afk11:33
*** jamie_h has joined #openstack-meeting-311:52
*** baojg has joined #openstack-meeting-311:54
*** markmcclain has joined #openstack-meeting-312:02
*** banix has joined #openstack-meeting-312:02
*** markmcclain1 has joined #openstack-meeting-312:04
*** markmcclain1 has quit IRC12:04
*** markmcclain1 has joined #openstack-meeting-312:04
*** markmcclain has quit IRC12:06
*** nacim has joined #openstack-meeting-312:10
*** julim has joined #openstack-meeting-312:21
*** markmcclain1 has quit IRC12:36
*** banix has quit IRC12:40
*** lblanchard has joined #openstack-meeting-312:41
*** xuhanp has joined #openstack-meeting-312:42
*** thomasem has joined #openstack-meeting-312:46
*** nacim has quit IRC12:56
*** jcoufal has quit IRC12:56
*** jcoufal has joined #openstack-meeting-312:57
*** baojg has quit IRC12:58
*** bknudson has quit IRC13:11
*** devlaps has joined #openstack-meeting-313:15
*** mrunge has quit IRC13:17
*** jthopkin has joined #openstack-meeting-313:20
*** jaypipes has quit IRC13:20
*** jthopkin has quit IRC13:21
*** jaypipes has joined #openstack-meeting-313:23
*** dkorn has joined #openstack-meeting-313:32
*** mfer has joined #openstack-meeting-313:32
*** peristeri has joined #openstack-meeting-313:33
*** alexpilotti has quit IRC13:39
*** otherwiseguy has joined #openstack-meeting-313:52
*** jcoufal has quit IRC13:54
*** jcoufal has joined #openstack-meeting-313:55
*** shakamunyi has joined #openstack-meeting-313:55
*** nacim has joined #openstack-meeting-313:55
*** jcoufal has quit IRC13:56
*** jcoufal has joined #openstack-meeting-313:56
*** amotoki has quit IRC14:00
*** nacim has quit IRC14:02
*** rgbkrk has joined #openstack-meeting-314:05
*** davlaps has joined #openstack-meeting-314:07
*** markmcclain has joined #openstack-meeting-314:13
*** yjiang51 has joined #openstack-meeting-314:14
*** yamahata has joined #openstack-meeting-314:20
*** nacim has joined #openstack-meeting-314:22
*** david-lyle has joined #openstack-meeting-314:24
*** markmcclain has quit IRC14:29
*** jcoufal has quit IRC14:33
*** markmcclain has joined #openstack-meeting-314:33
*** eghobo has joined #openstack-meeting-314:39
*** eghobo has quit IRC14:42
*** kenhui has joined #openstack-meeting-314:43
*** kenhui has quit IRC14:43
*** kenhui has joined #openstack-meeting-314:43
*** alexpilotti has joined #openstack-meeting-314:50
*** markmcclain has quit IRC14:55
*** lcheng_ has joined #openstack-meeting-314:57
*** davlaps has quit IRC14:57
*** devlaps has quit IRC14:57
*** carl_baldwin has joined #openstack-meeting-314:59
*** yjiang51 has left #openstack-meeting-314:59
*** banix has joined #openstack-meeting-315:02
*** igordcard has joined #openstack-meeting-315:02
*** kenhui1 has joined #openstack-meeting-315:03
*** kenhui1 has quit IRC15:03
*** kenhui1 has joined #openstack-meeting-315:06
*** kenhui has quit IRC15:06
*** nacim has quit IRC15:07
*** alexpilotti has quit IRC15:11
*** baojg has joined #openstack-meeting-315:13
*** shakamunyi has quit IRC15:16
*** shakamunyi has joined #openstack-meeting-315:18
*** devlaps has joined #openstack-meeting-315:19
*** davlaps has joined #openstack-meeting-315:19
*** ycombinator has joined #openstack-meeting-315:27
*** samchoi has joined #openstack-meeting-315:29
mfer#startmeeting openstack-sdk-php15:30
openstackMeeting started Wed May 28 15:30:22 2014 UTC and is due to finish in 60 minutes.  The chair is mfer. Information about MeetBot at http://wiki.debian.org/MeetBot.15:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:30
*** openstack changes topic to " (Meeting topic: openstack-sdk-php)"15:30
openstackThe meeting name has been set to 'openstack_sdk_php'15:30
mferHello everyone. Please state your name and any applicable association.15:30
mferMatt Farina, HP15:30
ycombinatorShaunak Kashyap, Rackspace15:30
samchoiSam Choi, HP15:30
jamie_hJamie Hannaford, Rackspace15:30
glencGlen Campbell, Rackspace15:30
mfer#topic agenda15:31
*** openstack changes topic to "agenda (Meeting topic: openstack-sdk-php)"15:31
mfer#link https://wiki.openstack.org/wiki/Meetings/OpenStack-SDK-PHP15:32
mfer1. Intro to the PHP SDK if there is anyone new? (mfer)15:32
mfer2. Copyright statements in code files (mfer)15:32
mfer3. Service creation - context/bootstrap class which instantiates services, classnames of services, moving all authentication functionality (including X-Auth-Token stuff) to dedicated class (jamie_h)15:32
mfer4. Reviews in progress - any questions/concerns? We are quickly accumulating reviews that touch overlapping files. It would be in our best interest to move forward with reviews soon. (samchoi)15:32
mfer5. What are the essential blueprints/bugs that need to be finished before we can move on to working on additional services? (samchoi)15:32
mferanything else to add?15:32
jamie_hI have nothing15:33
mfersamchoi, glenc, ycombinator?15:33
ycombinatornothing here either15:33
glencnope15:33
*** busterswt has left #openstack-meeting-315:33
samchoiI'm ok, I thought testing would be an item though15:34
mfer6. Testing15:34
mferI think we can skip number 1 since there is no one new.15:34
mfer#topic Copyright statements in code files15:34
*** openstack changes topic to "Copyright statements in code files (Meeting topic: openstack-sdk-php)"15:34
mferI had an action to dig into this so I went to talk with our legal folks. They are quite familiar with OpenStack.15:35
mferI was essentially told to put the HP copyright statement in any file we add or modify. If another organization adds or modifies a file they too can add their copyright statement to the file. That this is appropriate.15:36
glencYup; cf. https://wiki.openstack.org/wiki/LegalIssuesFAQ#Copyright_Headers15:37
ycombinatorso mfer, to be clear, there can be multiple copyright headers per file if it is modified by multiple organizations?15:37
mferycombinator yes. for example, https://github.com/openstack/swift/blob/6ac036fd013032287cfd8296c776ff57d7fcf79d/swift/common/middleware/tempurl.py15:37
ycombinatorcool, thanks15:38
glencThe CLA gives OpenStack a license to use it but it does not transfer the copyright15:38
mferFor us at HP, we'll be adding the appropriate HP copyright header. I'm not sure what rackspace is doing by jamie_h has suggested openstack having the copyright for your code.15:38
jamie_hso would this be okay: https://gist.github.com/jamiehannaford/0b0801b6056217d04c97 ?15:38
mferjamie_h yes15:39
glencis that new code? if so, it shouldn't have then OpenStack Foundation line "the only valid reason for OpenStack Foundation copyright notices on new code these days is where the code was authored by an employee or contractor of the foundation"15:39
jamie_hI'll add rackspace then15:40
glencYes15:40
*** Sukhdev has joined #openstack-meeting-315:40
jamie_hbut otherwise, that's fine with me. I wanted to have a consistent formatting. ATM we're using colons instead of asterisks, which doesn't seem to be standard15:40
mferglenc it had previously been suggested that rackspace would use the OpenStack Foundation copyright. is should be rackspace instead?15:40
glencThat's my understanding. Older stuff that Rackspace had done got transferred to the Foundation but, if you're working for Rackspace, then Rackspace holds the copyright and licenses it15:41
glenc[to the Foundation]15:41
mferthat makes sense. thanks for clearing that up15:41
glencPer that FAQ page as well as discussions with our legal folks a while back15:41
samchoiAbout the specific type of license, what happens if two or more orgs use different licenses? (MIT, Apache etc)15:42
mfereverything in OpenStack should be Apache 2.15:42
mfersamchoi are you referring to dependencies?15:42
samchoiNo, I'm not familiar with all the copyright rules, but I was just wondering if that could happen15:43
samchoihaving multiple licenses that is15:43
mferyou can dual license something. a copyright holder can do that. in our case that doesn't apply.15:43
jamie_hso, moving forward: go through files that have been edited/added by Rackspace and add relevant copyright header15:44
*** igordcard has quit IRC15:44
mferjamie_h please15:44
jamie_hand reformat to use standard docblock format (i.e. with asterisks instead of colons) - is that okay?15:44
glenchttp://lists.openstack.org/pipermail/legal-discuss/2014-January/000150.html15:44
jamie_hbut no content changes15:44
mferjamie_h will you take on that action?15:44
jamie_hsure, I can do that15:44
mferjamie_h colons? Where is that used?15:45
jamie_hsorry, ===== not colons15:45
jamie_hlong day :)15:45
mferjamie_h sure. i understand the long days15:46
mferis there anything else with regard to copyrights we should talk about?15:46
mferalso, license and copyright are two related by separate issues. license is apache 2 and through the CLA. I don't think there are any issues with that.15:47
jamie_hI don't have anything to add15:47
*** emagana has joined #openstack-meeting-315:47
ycombinatorI'm good too15:48
samchoisame, ready to move to 3.15:49
mfer#topic Service creation15:49
*** openstack changes topic to "Service creation (Meeting topic: openstack-sdk-php)"15:49
mferjamie_h since you added this could you please start it up15:49
*** nelsnelson has quit IRC15:49
*** HenryG has quit IRC15:49
*** nelsnelson has joined #openstack-meeting-315:50
jamie_hI've been working for the past 1-2 days on abstracting service creation. Nothing to do with how services are defined (since we still need to talk about that), but just the procedure of instantiating services and injecting the HTTP client into them15:50
jamie_hI had a few questions before carrying on15:50
jamie_h1. Have we decided on a naming convention for services?15:51
jamie_hso, for v2 swift - are we calling it ObjectStoreService, ObjectStorev2Service, or just ObjectStore\v2\ServiceClient15:51
mfer#link https://wiki.openstack.org/wiki/SDK-Development#Goals_for_each_SDK15:52
notmynamejamie_h: v2 swift?15:52
*** HenryG has joined #openstack-meeting-315:52
jamie_hor v1 - just an example15:52
mferwe should be using names reflective of the serivce not it's openstack name. so names like object store, identity, etc15:52
mfernotmyname one of the considerations is the audience. these are app developers who don't know openstack. they don't typically understand what names like swift, keystone, etc are.15:53
jamie_hyes, I agree. I have nothing against calling each one ServiceClient, and letting the namespace give the context15:53
ycombinatorI'd prefer ObjectStore\v2\ServiceClient15:53
jamie_hme too - we already have a long namespace15:54
notmynamemfer: no, my question is "what is 'v2' swift?" the v2 part, not the swift part15:54
mferjamie_h I was thinking something like ObjectStore\v1\ObjectStore or ObjectStore\v1\ObjectStoreClient. Something descriptice.15:54
*** eghobo has joined #openstack-meeting-315:54
mfernotmyname ah, we're bouncing around conventions. we know there is no v2 swift yet15:54
jamie_hmfer surely the namespace describes the context, though? I want to keep namespaces as succinct as possible15:55
*** HenryG has quit IRC15:55
*** ttrifonov is now known as ttrifonov_zZzz15:55
*** HenryG has joined #openstack-meeting-315:55
mferWhat likes in ObjectStore\v1\ isn't something I have a strong opinion on15:55
ycombinatorokay, so are we agreeing on ObjectStore\v1\<something> as opposed to ObjectStoreV1Something?15:56
mferycombinator I think so. it works better with the PHP namespaces and it's what we'd already put in place15:56
ycombinatorcool15:57
jamie_hsecond thing I was working on was removing all auth logic from concrete services, and letting a subscriber do it15:57
mferwhat do you mean by a subscriber doing it?15:57
jamie_hit listens out for any requests being sent, figures out whether the cached token is valid, and then re-authenticates as necessary15:57
jamie_hinstead of making services add their own headers whenever they make calls15:57
jamie_hbasically centralizing the process with a class that has a single responsibility, instead of dissipating the process over the codebase15:58
jamie_hI can provide more details over mailing list15:58
mferjamie_hf ah, like a session handler?15:59
jamie_hyeah pretty much15:59
jamie_hyou just attach it to the HTTP client and let it handle authentication15:59
mferattach it to the HTTP client?16:00
jamie_has a subscriber. and when the HTTP client sends a request, it informs the auth subscriber16:00
*** otherwiseguy has quit IRC16:00
jamie_hwhich checks the token, re-authenticates, and adds the token to the request headers16:00
mferfirst, i'm up for a session handler like that. i even have stub code somewhere to do that. it's also what the python sdk is doing.16:00
mferjamie_h so, you're talking about the way guzzle handles things. we can give that a shot. i see where you're going16:01
mfersamchoi ycombinator glenc any thoughts on this?16:01
mferjamie_h the one thing we need to be careful of is the retry logic if the creds intentionally change and providing a means to catch errors around that16:02
samchoiThe general idea sounds fine. It seems we've even discussed this idea in the past mfer16:02
glencseems reasonable. better than some of the ways I've implemented reauth before :)16:02
ycombinatorI'm okay with the subscriber pattern16:02
ycombinatorbut are we going to be tied into guzzle?16:02
mferwe need to stay loosly coupled16:02
mferi think that's possible16:03
jamie_hthat's a good question - if we're using the subscriber, we can either create our own classes or use a dependency16:03
glencright. You might have to create a small wrapper around another HTTP client to implement this, right?16:03
jamie_hsubscriber dependency is separate from HTTP/transport layer16:03
jamie_hwe could use either symfony or guzzle IMO16:03
jamie_hglenc that's what we're doing with the transport layer - wrapping guzzle to satisfy our interface16:04
*** davlaps has quit IRC16:04
*** devlaps has quit IRC16:04
glencright16:04
jamie_hI see no reason why we can't rely on dependencies for utility classes, like subscribers16:04
jamie_hit wouldn't compromise our decision to decouple the transport layer16:05
jamie_hthe last thing I did was rename Bootstrap to OpenStack, and having that as the main entry point for end-users to instantiate services16:06
mferthere is a blueprint for that as well16:07
mferI'd like all dependencies to be injected and be replacable in some manner. loose coupling.16:07
jamie_hyeah, me too16:07
mferit makes it a lot easier to not do major api breaking changes in the future if dependencies change16:07
jamie_hI was thinking of something like:16:07
jamie_h$openstack = new OpenStack(['username' => 'foo', etc. etc.]);16:08
mferyup16:08
jamie_h$os = $openstack->objectStore();16:08
*** xuhanp has quit IRC16:08
jamie_hor something16:08
jamie_hthat's all I had - I can elaborate on details in mailing list after this meeting if anyone has questions or concerns16:09
ycombinatorjamie_h: how would they choose version?16:09
ycombinatorv1 vs. v2?16:09
ycombinatorin that construction16:09
samchoiminor point, but I feel like the naming could be more descriptive. As a new user, I'd have no clue what an Openstack.php file would entail.16:09
mferI'd been thinking the same thing expect using something like $openstack->service('objectstore') .... so we can add more service w/ extensions16:09
jamie_hthey'd probably pass in to objectStore method16:09
jamie_hmfer yeah - I used "get" method instead and had magic methods16:09
mferycombinator in my service model we'd need to be able to firgure out things like version, region, etc16:09
mferservice detection is something we can learn about from the openstackclient folks16:10
mferthey've been learning the nuances of that in regard to different setups of openstack16:10
mferi'm good with this direction. shall we move on to the next item or is there more to talk about?16:12
jamie_hsamchoi I'll wrap all this stuff in an e-mail and we can talk about better alternatives for naming16:13
jamie_hother than that, I have nothing else for this topic16:13
samchoisure, ready to move on16:13
mferjamie_h great. i think we're mostly on the same page with this stuff so that makes me quite happy16:13
mfer#topic Reviews in progress16:14
*** openstack changes topic to "Reviews in progress (Meeting topic: openstack-sdk-php)"16:14
mfer#link https://review.openstack.org/#/q/status:open+project:stackforge/openstack-sdk-php,n,z16:14
mferthere are a bunch of them.16:14
mferwhich ones should we talk about with the 15 minutes we have left?16:14
mferthe guzzle refactoring i'm in the process of reviewing given the latest changes16:15
jamie_ha lot of patches hinge on the guzzle refactoring - but if that's mid-review there's not much to talk about16:15
jamie_hShaunak had reservations about the URL one16:15
mferjamie_h ycombinator can you look at https://review.openstack.org/#/c/94336/ and https://review.openstack.org/#/c/93892/16:15
ycombinatorlooking16:15
mferi think you can look at them offline. we just need another person to review each of those16:16
mferycombinator i saw your changes and i'll get to reviewing them this week. i hope others can as well.16:16
jamie_hi'll take a look too16:17
mferjamie_h why a URL class rather than then PHP parse url function to an array? I'm not debating... just asking the why question.16:17
samchoiI think ycombinator's changes were fairly independent of the others so that one should be easier to get in...16:17
jamie_hbecause a lot of time we need more than what parse_url offers16:18
jamie_hthe ability to modify queries, add paths, etc.16:18
jamie_hit's also useful for type hinting16:18
jamie_hmanipulating strings can also be verbose and annoying16:19
mferand why our own implementation rather than a dependency on someone else?16:19
jamie_hbecause i wanted to have looser coupling16:20
*** otherwiseguy has joined #openstack-meeting-316:20
jamie_hif we relied on an external dependency, I think it might compromise our decision to have a generic transport layer16:21
jamie_hplus the external dependency (non-Guzzle) has a lot of baggage we don't need16:21
mferwe'd end up needing to have an interface and a default mechanism that would be easily overridden. for something like a URL class that could be difficult16:21
mferycombinator you had concerns. do you have a strong opinion or any other thoughts?16:22
jamie_hif that's the case - would folks be against using GuzzleHttp\Url ?16:22
mferjamie_h how would we make it easy to swap that out?16:23
jamie_hI don't think we'd need to swap out a Url class16:23
jamie_hit'd be up to an adapter to make other Url classes compatible with ours16:23
mferwhat if someone wasn't using guzzle or wanted to change to a newer major version where the Url class had been moved?16:23
jamie_hthey'd need to write an adapter than satisfies our type hints16:24
mferah, ok. as long as it can be swapped i'm ok with it. the question is... should we? would making it an adapter be so much more code/complexity to make it worth it?16:24
jamie_hthe adapter would be required for the client to satisfy our ClientInterface16:25
*** igordcard has joined #openstack-meeting-316:25
ycombinatorI'm hesitant to roll something on our own for something so fundamental but I see Jamie's point about not pulling in a heavy dependency either16:25
*** tjones has joined #openstack-meeting-316:25
ycombinatorthe lightest dependency I found with some traction was this: https://packagist.org/packages/webignition/url16:25
jamie_hwhy not use Guzzle's URL class instead of that, though? They'd both result in a tightly coupled dependency16:26
mferycombinator given that we'd need to have an adapter/dependency injector for it... is using that worth it for something relatively small and simple?16:26
ycombinatorI'd be fine with using Guzzle's URL class if we are going to be pulling in Guzzle anyway16:26
jamie_hI'm fine with using Guzzle for non-HTTP classes - like event subscribers - but I'm wary about keeping the transport layer as independent as possible16:27
ycombinatorin fact, if we are going to pull in Guzzle anyway, I'd /prefer/ to use its URL class16:27
mferycombinator we loosly couple to Guzzle. we need to keep the things loosly coupled16:27
ycombinatorso - let me ask: are we going to be pulling in Guzzle as a dependency at all time?16:27
ycombinatorok, so guzzle wouldn't be in composer.json then?16:28
jamie_hit's a trade off between keeping things DRY or keeping things loosely coupled16:28
jamie_hycombinator it would because it acts as the default client. But users can override16:28
ycombinatorokay, so in that case, I say we use Guzzle's URL class16:28
jamie_hso all the Guzzle codebase is there for us to use16:28
ycombinatoras opposed to pulling in yet another dependency or rolling our own16:28
jamie_hhypothetical: say we add support for ZF2's HTTP client. their adapter would need to turn their URLs into Guzzle ones16:29
jamie_his that fine with you?16:29
mferi would be ok with using the Guzzle URL class if it can be swapped out in a similar manner to the the http client16:29
ycombinatorjamie_h: it wouldn't be different from turning it into our own URL class16:29
ycombinatorso yes, I'd be fine with that16:29
mferwe should be able to use something like https://packagist.org/packages/webignition/url with ZF2's http client if someone wants16:30
*** emagana has quit IRC16:30
ycombinatorshould we continue in openstack-sdks?16:30
samchoisure ycombinator16:30
mferycombinator yes. thanks for keeping time16:30
mfernext meeting needs to start16:30
mfer#endmeeting16:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:30
openstackMeeting ended Wed May 28 16:30:51 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_sdk_php/2014/openstack_sdk_php.2014-05-28-15.30.html16:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_sdk_php/2014/openstack_sdk_php.2014-05-28-15.30.txt16:30
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_sdk_php/2014/openstack_sdk_php.2014-05-28-15.30.log.html16:30
*** emagana has joined #openstack-meeting-316:31
tjones#startmeeting NovaBugScrub16:31
openstackMeeting started Wed May 28 16:31:03 2014 UTC and is due to finish in 60 minutes.  The chair is tjones. Information about MeetBot at http://wiki.debian.org/MeetBot.16:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:31
*** openstack changes topic to " (Meeting topic: NovaBugScrub)"16:31
openstackThe meeting name has been set to 'novabugscrub'16:31
tjonesanyone here today?16:31
*** otherwiseguy has quit IRC16:32
*** dkorn has quit IRC16:32
tjones*listens to crickets*16:33
tjones*listens to crickets*16:34
*** pgpus has joined #openstack-meeting-316:35
tjonesstill no one here?16:36
tjonesno one here?16:40
pgpusnor do I see one?16:41
pgpusPossibly lets look at wiki may be date and time differ?16:41
tjoneswaiting to start the meeting until people come - this is the time it has been for months now…16:42
pgpuslooks like its biweekly16:43
pgpushttp://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/?C=M;O=D16:44
tjonesthis is the nova bug scrub meeting16:44
pgpusOK may be I am on wrong channel so will quit thanks16:44
tjonesno prob16:44
tjonesending the meeting with no attenees16:45
pgpusquit16:45
pgpusbye16:45
*** pgpus has quit IRC16:46
*** gduan has quit IRC16:47
tjones#endmeeting16:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:47
openstackMeeting ended Wed May 28 16:47:47 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/novabugscrub/2014/novabugscrub.2014-05-28-16.31.html16:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/novabugscrub/2014/novabugscrub.2014-05-28-16.31.txt16:47
openstackLog:            http://eavesdrop.openstack.org/meetings/novabugscrub/2014/novabugscrub.2014-05-28-16.31.log.html16:47
*** leifz has joined #openstack-meeting-316:48
*** baojg has quit IRC16:50
*** tjones has left #openstack-meeting-316:50
*** garyduan has joined #openstack-meeting-316:50
*** otherwiseguy has joined #openstack-meeting-316:55
*** beyounn_1 has joined #openstack-meeting-316:55
*** eghobo has quit IRC16:56
*** nati_ueno has joined #openstack-meeting-316:57
*** eghobo has joined #openstack-meeting-316:59
*** garyduan has quit IRC16:59
*** rm_work is now known as rm_work|away16:59
*** garyduan has joined #openstack-meeting-316:59
*** vinay_yadhav has joined #openstack-meeting-317:00
*** yamahata has quit IRC17:03
*** rm_work|away is now known as rm_work17:06
*** devlaps has joined #openstack-meeting-317:08
*** anil_rao has joined #openstack-meeting-317:10
*** otherwiseguy has quit IRC17:11
*** eghobo has quit IRC17:11
*** otherwiseguy has joined #openstack-meeting-317:22
*** LouisF has joined #openstack-meeting-317:22
*** mandeep has joined #openstack-meeting-317:23
*** regXboi has joined #openstack-meeting-317:24
*** rkukura has joined #openstack-meeting-317:28
regXboidone and done17:29
*** Cathy_ has joined #openstack-meeting-317:30
SumitNaiksatamhello Neutron folks!17:30
cgoncalveshi all17:30
*** pcm_ has joined #openstack-meeting-317:30
banixhello!17:30
vinay_yadhavHi all17:30
regXboialoha17:30
enikanorovhi17:31
rkukurahi17:31
garyduanHi17:31
SumitNaiksatamok, i think we have critical mass, lets get started17:31
SumitNaiksatam#startmeeting Networking Advanced Services17:31
openstackMeeting started Wed May 28 17:31:39 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.17:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:31
*** openstack changes topic to " (Meeting topic: Networking Advanced Services)"17:31
openstackThe meeting name has been set to 'networking_advanced_services'17:31
SumitNaiksatam#info agenda: https://wiki.openstack.org/wiki/Meetings/AdvancedServices17:31
SumitNaiksatamwe have a packed agenda17:32
SumitNaiksatami will like to address some process issues towards the end of the meeting17:32
cgoncalvesSumitNaiksatam: there is no news there :-)17:32
SumitNaiksatamin the open discussion17:32
SumitNaiksatamcgoncalves: :-)17:32
SumitNaiksatamlets get rolling17:32
SumitNaiksatam#topic Juno planning and feature tracking17:32
*** openstack changes topic to "Juno planning and feature tracking (Meeting topic: Networking Advanced Services)"17:32
SumitNaiksatam#link https://wiki.openstack.org/wiki/Neutron/AdvancedServices/JunoPlan17:33
*** hemanthravi has joined #openstack-meeting-317:33
SumitNaiksatamlast week we decided to start using this table as record of our priorities17:33
SumitNaiksatamand what we want to track first in this meeting17:33
SumitNaiksatama couple of items got added to that table17:33
SumitNaiksatamin addition, the PTL has set milestone dates on the blueprints17:34
SumitNaiksatamJuno 1 blueprints (as set by PTL):17:34
SumitNaiksatam#link https://launchpad.net/neutron/+milestone/juno-117:34
SumitNaiksatamJuno 2 blueprints (as set by PTL):17:34
SumitNaiksatam#link https://launchpad.net/neutron/+milestone/juno-217:35
SumitNaiksatammost of what we are tracking in this meeting was earlier slated for Juno 117:35
*** natarajk has joined #openstack-meeting-317:35
SumitNaiksatamhowever, if you see above, it has now been pushed to Juno 217:35
regXboi@Sumit: I assume we can ask about items that are "not set" during the individual project updates?17:36
SumitNaiksatammy understanding is this is on account of the fact that the blueprint specs have not been approved yet17:36
SumitNaiksatamregXboi: i am not sure i completely got that, but please go ahead17:36
regXboiLooking at the table I see certain items that are marked "Not Set" for Milestone17:36
regXboiI wanted to ask if we could bring those up during the individual project updates17:37
SumitNaiksatamregXboi: oh yeah, definitely17:37
regXboithanks17:37
SumitNaiksatamregXboi: the expectation is that each task owner should set these17:37
regXboiok17:37
SumitNaiksatamregXboi: and we should track them here17:37
SumitNaiksatamregXboi: if these are not set during this week, we have to investigate why17:38
regXboisound good - thanks for the answer17:38
SumitNaiksatamregXboi: we cannot track things without milestones being set (we already well into Juno 1 now)17:38
SumitNaiksatamok, so summary from the above links, we have already been pushed into Juno 217:38
*** kenhui1 has quit IRC17:39
SumitNaiksatamrealistically, this was going to be the case17:39
cgoncalvesSumitNaiksatam: items with BPs not yet approved are no worth setting milestones17:39
SumitNaiksatamhowever, we have to make sure that we make enough progress in Juno 1 as well17:39
SumitNaiksatamcgoncalves: we should set the milestones as to how we would want to pursue them17:39
SumitNaiksatamcgoncalves: and accordingly socialize with the PTL and the bigger neutron core team17:40
cgoncalvesSumitNaiksatam: ok17:40
*** Sukhdev has quit IRC17:40
SumitNaiksatamcgoncalves: if they do not agree, we can reconcile with that17:40
SumitNaiksatamcgoncalves: but as taks owners, the initial esitmate has to come from you17:40
SumitNaiksatamcgoncalves: do others agree?17:40
SumitNaiksatamquestion for everyone, rather17:41
cgoncalvesSumitNaiksatam: ok, agreed. I'll set them after meeting17:41
SumitNaiksatamok17:41
SumitNaiksatamso i propose that we go through each individual task items on the agenda17:41
SumitNaiksatamand then circle back to the process discussion17:41
SumitNaiksatami want to spend some time on it17:42
SumitNaiksatam#topic Service base definition and Insertion17:42
*** openstack changes topic to "Service base definition and Insertion (Meeting topic: Networking Advanced Services)"17:42
SumitNaiksatamwe are still in spec review: #link https://review.openstack.org/#/c/9312817:42
SumitNaiksatamis Kanzhe here?17:42
SumitNaiksatami know s3wong is not17:42
SumitNaiksatamkevinbenton: do you know if kanzhe is around?17:43
SumitNaiksatamlooking at the review, does not seem like much progress17:43
SumitNaiksatamif kanzhe, joins we can circle back to this17:43
SumitNaiksatamanything anyone wants to bring up on this?17:43
regXboiSumitNaiksatam: that was the first place I wanted to circle back on17:44
SumitNaiksatamregXboi: sure, go ahead17:44
regXboispecifically the HEAT line17:44
SumitNaiksatamyeah17:44
cgoncalvesSumitNaiksatam: you skipped the flavor framework, no?17:44
*** Kanzhe has joined #openstack-meeting-317:45
SumitNaiksatamcgoncalves: yes i will come to it17:45
cgoncalvesKanzhe: :-)17:45
regXboiI believe Kanzhe has joined17:45
SumitNaiksatamregXboi: go ahead17:45
Kanzhesorry, got stuck in a diffferent meeting.17:45
*** jamie_h has quit IRC17:45
regXboiI'm looking through the BP and wondering if we need to put some more detail relating to heat to get from "Not Set" to a milestone17:46
regXboior is it here and I'm missing it?17:47
SumitNaiksatamKanzhe: is the Heat owner identified for this?17:47
KanzheAbout ServiceInsertion? not yte.17:47
Kanzheyet.17:47
SumitNaiksatamKanzhe: ok17:47
KanzheShould I give a quick update?17:48
SumitNaiksatamKanzhe: can i request that we scope this, and identify the owner by next week?17:48
KanzheYes.17:48
SumitNaiksatamKanzhe: thanks17:48
SumitNaiksatamregXboi: you want to participate in that?17:49
SumitNaiksatamregXboi: please reach out to Kanzhe if you do (for this item)17:49
SumitNaiksatamKanzhe: yes please go ahead with the update17:49
regXboiIf I can shake free, I will17:49
SumitNaiksatamregXboi: :-)17:49
KanzheStephen, Kevin, and I had a meeting to break up the work.17:50
KanzheThe current plan is to submit servicePort early next week. I am the owner.17:50
SumitNaiksatamKanzhe: ok17:50
KanzheKevin will finish external port, then start serviceBase class.17:50
SumitNaiksatamKanzhe: its great to have the implementation going in parallel17:51
KanzheStephen will look into integration with LB and DB migration.17:51
SumitNaiksatamKanzhe: great17:51
KanzheCLI and Horizon will come after that.17:51
SumitNaiksatami would however suggest that we also pursue getting the gerrit spec approved17:51
SumitNaiksatamwe need to put a timeline on getting the gerrit specs approved17:52
KanzheYes. cgoncalves, thank you for your review comment.17:52
SumitNaiksatamand in this meeting figure out how we can get there (or if we cannot)17:52
regXboipoo in reading the gerrit spec - is serviceport === serviceattachmentpoint?17:52
KanzheregXboi: yes. :-)17:52
regXboithanks17:52
cgoncalvesKanzhe: hope I've provided some useful reviewing17:53
SumitNaiksatamKanzhe: can you identify a date that we would like this gerrit spec to get approved?17:53
SumitNaiksatamKanzhe: and put that date on the table17:53
SumitNaiksatamwe will discuss during the open discussion on how to get there17:53
KanzheNext wednesday?17:53
SumitNaiksatamKanzhe: we will discuss today17:54
KanzheSumitNaiksatam: sure.17:54
SumitNaiksatamcgoncalves: thanks for your review17:54
SumitNaiksatamany more questions for Kanzhe right now?17:54
*** otherwiseguy has quit IRC17:54
Kanzhecgoncalves: I am still going through your comments. May reach out to you if I have any question.17:54
regXboiI'll see if I can add a comment about the === question above to the review because that helped clarify it for me17:55
cgoncalvesKanzhe: sure!17:55
SumitNaiksatamregXboi: thanks17:55
SumitNaiksatamKanzhe: i know the gerrit spec approval is blocking you, apart from that are there any techincal blockers?17:55
KanzheSumitNaiksatam: not at the moment.17:55
SumitNaiksatamKanzhe: ok good17:55
KanzheBoth stephen and Kevin are out this week.17:56
SumitNaiksatamKanzhe: ok17:56
KanzheI expect more progress next week.17:56
SumitNaiksatamgoing forward, i would like to use this forum, for discussing not only reviewer input, but the blockers for a particular task owner, so be prepared when we discuss your item17:56
SumitNaiksatamok next item17:56
SumitNaiksatami wanted to discuss flavors later, since its takes more time17:57
SumitNaiksatambut since cgoncalves brought it up17:57
SumitNaiksatam#topic Flavors17:57
*** openstack changes topic to "Flavors (Meeting topic: Networking Advanced Services)"17:57
*** prad has joined #openstack-meeting-317:57
SumitNaiksatam#link https://review.openstack.org/#/c/9007017:57
SumitNaiksatamenikanorov: there?17:57
SumitNaiksatamenikanorov: i know you were on vacation17:57
enikanorovyep, i'm here17:57
enikanorovi'm addressing comments of the spec17:58
SumitNaiksatamenikanorov: are you getting enough reviewer attention?17:58
SumitNaiksatamenikanorov: ok thanks17:58
enikanorovi also need to discuss the scheduling (or 'selection' process)17:58
*** prad has left #openstack-meeting-317:58
SumitNaiksatamenikanorov: can you populate the table: https://wiki.openstack.org/wiki/Neutron/AdvancedServices/JunoPlan with the milestone dates?17:58
enikanorovas on design session there was mark mcclains opinion on how to implement it17:58
*** prad has joined #openstack-meeting-317:58
enikanorovSumitNaiksatam: ok17:58
SumitNaiksatamenikanorov: yes definitely, we discussed a bit of that last well, when you were not present17:59
enikanorovoh, i need to find logs then17:59
SumitNaiksatamenikanorov: do you think a separate meeting on just that topic with mark and whoever else is interested, will help?17:59
enikanorovcan you provide a short summary of that discussion?17:59
enikanorovmark has asked me to start an email thread17:59
SumitNaiksatamenikanorov: we felt that STF would serve the purpose, and were not clear on what the objections were :-)18:00
enikanorovactually i'm fine with any of implementation option18:00
SumitNaiksatamenikanorov: sure, you can start the implementation thread18:00
enikanorovah, you're talking about STF18:00
enikanorovthat's a different matter18:00
enikanorovdid Gary try to talk to Mark on that?18:00
garyduanNo. I have not18:00
garyduanI am not sure what his concern is18:01
enikanorovmy current understanding is that STF has only drawback of public provider attribute18:01
SumitNaiksatamenikanorov garyduan: for both these, i would recommend that we get together in a dedicated IRC meeting, and decide on an agreed upon path forward18:01
enikanorovonce we remove that it should be fine18:01
SumitNaiksatamenikanorov: other blueprints has dependency on flavors18:01
enikanorovSumitNaiksatam: understand18:01
SumitNaiksatamenikanorov: so we need to get the plan fleshed out at the earliest18:02
enikanorovok, i'll try to sort this out sooner18:02
SumitNaiksatam#action enikanorov garyduan SumitNaiksatam to set up an IRC meeting to discuss flavors backend scheduling and STF18:02
pcm_SumitNaiksatam: +118:02
enikanorovok, good plan18:02
SumitNaiksatamenikanorov: lets have a plan by next meeting, and lets have the milestone dates populated18:03
SumitNaiksatamenikanorov: we will pull the PTL into the next meeting and get an agreement on the plan18:03
enikanorovwill do18:03
SumitNaiksatamquestions for enikanorov?18:03
SumitNaiksatamenikanorov: thanks for the update18:04
SumitNaiksatamKanzhe: thanks for the earlier update as well, i forgot to mention18:04
SumitNaiksatam#topic Traffic steering18:04
*** openstack changes topic to "Traffic steering (Meeting topic: Networking Advanced Services)"18:04
SumitNaiksatam#link https://review.openstack.org/#/c/9247718:04
SumitNaiksatami believe we have one +118:04
SumitNaiksatampcm_: thanks for reviewing18:05
pcm_SumitNaiksatam: np18:05
SumitNaiksatamdoes anyone want to discuss anything specific in the spec here?18:05
cgoncalvesI'm sorry I've havent addressed yet the clarification on the BP on there this blueprint differs from the service chain one18:06
SumitNaiksatamcgoncalves: ok18:06
cgoncalvesit's on my TODO list, high priority18:06
SumitNaiksatamcgoncalves: i believe you have prototype code as well, to back your spec?18:06
mandeepcgoncalves: The service chain blueprint does address this as a potential implementation, so can refer to that (if it helps)18:06
cgoncalvesSumitNaiksatam: you're right. I'm quite new to Neutron code architecturing but I've learnt a few things during this past days18:07
cgoncalvesmandeep: ok18:07
regXboicgoncalves: one clarification...18:08
cgoncalvesSumitNaiksatam: and with that, I've been looking at the ML2 and GP PoC code18:08
cgoncalvesregXboi: shoot :-)18:08
SumitNaiksatamcgoncalves: i saw your message18:08
regXboiI assume that the list of lists of ports implies that I can pick one from each list18:08
SumitNaiksatamcgoncalves: thats a slightly different topic18:08
*** lcheng_ has quit IRC18:08
cgoncalvesregXboi: each port_chain lists are independent from other port_chain lists18:09
regXboiI'm reading into the port chain data model18:09
*** lcheng_ has joined #openstack-meeting-318:09
regXboithat's not exactly how I read this18:09
regXboia port chain includes a list of lists of ports18:09
regXboithere is no indication that I could find how that is to be interpreted18:10
regXboiI have an educated guess :)18:10
cgoncalvesregXboi: ok, fair point, will surely need to be clarified on the BP18:11
regXboithanks18:11
regXboiI'll add a comment now18:11
SumitNaiksatamregXboi: i agree, it was a little confusing for me at first as well (the list of lists)18:11
cgoncalvesregXboi: thanks for bringing that up. I'll document that and get back to you18:11
SumitNaiksatamregXboi: this gives more flexibility, but difficult to interpret in an unambiguous way18:11
cgoncalvesregXboi: better yet. thanks18:11
SumitNaiksatamcgoncalves: any techincal blockers, or help that you seek from the rest of the team?18:12
cgoncalvesSumitNaiksatam: in terms of code?18:12
regXboicomment so added18:13
SumitNaiksatamcgoncalves: both in terms of the spec and the code18:13
cgoncalvesSumitNaiksatam: if so, I think the email I sent to -dev on the GP mapping driver thread also applies here: http://lists.openstack.org/pipermail/openstack-dev/2014-May/035976.html18:13
cgoncalvesregXboi: tks18:13
SumitNaiksatamcgoncalves: i dont see a direct correlation, but i might be missing something18:13
SumitNaiksatamcgoncalves: we can go back to the mailer for that18:14
SumitNaiksatamcgoncalves: thanks for the update18:14
SumitNaiksatammoving on18:14
SumitNaiksatam#topic Service Chaining18:14
*** openstack changes topic to "Service Chaining (Meeting topic: Networking Advanced Services)"18:14
SumitNaiksatam#link https://review.openstack.org/#/c/9352418:14
SumitNaiksatami dont think this got much reviewer attention yet18:14
SumitNaiksatammandeep: ?18:14
mandeepyes not much, but nachi reviewed18:15
SumitNaiksatammandeep: ah ok, thanks nachi18:15
mandeepHe has requested for a use-case, and I am adding that18:15
SumitNaiksatammandeep: ok thanks18:15
SumitNaiksatamany questions for mandeep?18:15
mandeepThere were a couple of other helpful commnets as well, and18:15
SumitNaiksatammandeep: good to know18:15
mandeepI will be updating the name "ServiceChain" to "ServiceChainSpec"18:16
SumitNaiksatammandeep: are you blocked on anythig?18:16
SumitNaiksatammandeep: apart from the reviewer feedback18:16
mandeepFor the now, the goal is to get the spec reviewed by a few more people18:16
SumitNaiksatammandeep: ok18:16
SumitNaiksatamlet me keep this rolling, got to cover a few more items18:16
SumitNaiksatammandeep: thanks for the update18:16
*** jamielennox is now known as jamielennox|away18:16
mandeepok18:17
SumitNaiksatam#topic L3 Agent Framework18:17
*** openstack changes topic to "L3 Agent Framework (Meeting topic: Networking Advanced Services)"18:17
regXboimandeep: let me know after you add a use case and I'll take another look18:17
SumitNaiksatam#link https://review.openstack.org/#/c/9153218:17
mandeepregXboi: will do,18:17
SumitNaiksatami dont think toshi is here18:17
SumitNaiksatambut i want to put this on the radar18:17
SumitNaiksatami have sent him an email, hopefully he will be able to participate and provide updates in the future18:17
SumitNaiksatamif anyone else wants to proxy for him that will be great (else i will take it up to sync up with him)18:18
SumitNaiksatam#topic Tap as a Service spec18:18
*** openstack changes topic to "Tap as a Service spec (Meeting topic: Networking Advanced Services)"18:18
SumitNaiksatam#link https://review.openstack.org/#/c/96149/18:18
SumitNaiksatamvinay_yadhav: thanks for proposing the spec18:18
SumitNaiksatamsince this just landed, i am guessing that not many people got a chance to go through it18:19
vinay_yadhavi made some more changes to it and commited it but it went as another commit and not as a patch18:19
*** OSM has joined #openstack-meeting-318:19
vinay_yadhavi had one person review it18:19
vinay_yadhavi guess other can start the review process too18:19
SumitNaiksatamvinay_yadhav: nice, lets give people some more time, and we can circle back to this next week18:19
anil_raoI will be adding my review comments too shortly.18:19
vinay_yadhavthanx18:19
SumitNaiksatamanil_rao: great, thanks18:20
SumitNaiksatamvinay_yadhav: i believe you also have a -dev thread going on this18:20
vinay_yadhavi need to start it18:20
SumitNaiksatamall please respond there in the interim18:20
vinay_yadhavi will do that soon18:20
SumitNaiksatamvinay_yadhav: thanks18:20
vinay_yadhavany pointer on how to start the dev thread18:21
regXboiI'm a little concerned that the data model isn't complete, but I'll look at it and drop email/comments if need be18:21
vinay_yadhavjust on the mailing list18:21
SumitNaiksatamregXboi: yes please18:21
SumitNaiksatam#topic NFV and Service VM updates18:21
*** openstack changes topic to "NFV and Service VM updates (Meeting topic: Networking Advanced Services)"18:21
*** ivar-lazzaro has joined #openstack-meeting-318:21
SumitNaiksatami believe the NFV meetings have not started18:21
SumitNaiksatam#link https://wiki.openstack.org/wiki/Meetings/NFV18:21
SumitNaiksatamand neither stephen or isaku is here today to provide the update on service VMs18:22
SumitNaiksatami will wing it18:22
SumitNaiksatam#topic Group Policy Requirements18:22
*** openstack changes topic to "Group Policy Requirements (Meeting topic: Networking Advanced Services)"18:22
SumitNaiksatambanix: quick one minute update?18:22
banixnothing beyond new patches submitted18:22
SumitNaiksatambanix: ok18:23
SumitNaiksatamstephen sent an update on the services’ integration that he has tried18:23
SumitNaiksatambut i will skip it for now18:23
SumitNaiksatammight take more time18:23
SumitNaiksatambanix: thanks18:23
SumitNaiksatamsorry for rushing18:23
*** nati_ueno has quit IRC18:24
SumitNaiksatam#topic Open Discussion18:24
*** openstack changes topic to "Open Discussion (Meeting topic: Networking Advanced Services)"18:24
SumitNaiksatamso firstly, an action item for all the task owners -18:24
SumitNaiksatam#action Kanzhe enikanorov cgoncalves mandeep vinay_yadhav toshi to put milestone dates in https://wiki.openstack.org/wiki/Neutron/AdvancedServices/JunoPlan18:24
vinay_yadhavok18:25
Kanzhe+118:25
SumitNaiksatamwe will need the table with your estimated dates to be populated by next meeting18:25
vinay_yadhavsure18:25
enikanorovsure18:25
SumitNaiksatamand we will discuss the feasibility of achieving that next week, hopefully by pulling the PTL in18:25
cgoncalvesSumitNaiksatam: where devstack fits best? client or have its own row? I'm guessing the latter18:26
SumitNaiksatammestery: agree ^^^ ?18:26
cgoncalvesSumitNaiksatam: agreed18:26
SumitNaiksatamcgoncalves: you can add a separate item for devstack18:26
mandeepok18:26
SumitNaiksatamin fact, please do, thanks for bringing that up18:26
SumitNaiksatamits a separate line item18:26
banixSumitNaiksatam: +118:27
SumitNaiksatamand needs to be tracked18:27
cgoncalvesSumitNaiksatam: ok, thanks for clarifying18:27
* mestery reads scrollback.18:27
SumitNaiksatammestery: we were just saying that we would like to pull you into the meeitng next week18:27
mesterySumitNaiksatam: +1 to that idea I think.18:27
SumitNaiksatammestery: to look at our estimates18:28
mesterySumitNaiksatam: That should be fine, yes.18:28
SumitNaiksatammestery: thanks18:28
mesterySumitNaiksatam: thanks!18:28
SumitNaiksatamsecondly, if you see the recurrent theme during the meeting is that we are blocked on the spec reviews18:28
SumitNaiksatamand people have asked this several times as to how we can speed this up18:29
SumitNaiksatami would like explore a process that we can make this a little more detereministic18:29
SumitNaiksatamso my first suggestion is that we identify a team of “assigned-reviewers” for this advanced services’ sub team18:29
SumitNaiksatamthis can be both +1 and +2 reviewers18:30
SumitNaiksatamyou can volunteer your name for this and we will put it on the wiki18:30
*** SridarK has joined #openstack-meeting-318:30
*** nati_ueno has joined #openstack-meeting-318:30
banixSumitNaiksatam: thats what is being done by ML2 subteam18:30
regXboiSumitNaiksatam: I'm only +1, but throw my name in18:30
SumitNaiksatambut it means that every week you will need to at least review all the specs that we have identified as priority items18:30
SumitNaiksatamso we want to hold this team accontable18:31
SumitNaiksatam*accountable18:31
SumitNaiksatamcurrently we have only a few specs that we are tracking as priority18:31
SumitNaiksatamso its should not be as much18:31
banixand probably more importantly on a known schedule i think18:31
SumitNaiksatamdoes everyone agree?18:31
SumitNaiksatambanix: yes absolutely18:32
SumitNaiksatamso the schedule will be driven by the dates we put on the milestones in teh table18:32
banixagree; lets add that to the table maybe?18:32
SumitNaiksatambanix: absolutely, was going to say that18:32
SumitNaiksatamso on that same wiki page, we will add a section at that top, which will have the reviewer’s names18:33
SumitNaiksatamif you want to be included, please add your name to: https://wiki.openstack.org/wiki/Neutron/AdvancedServices/JunoPlan18:33
SumitNaiksatami will put a section “Reviewers” at the top18:33
regXboiSumitNaiksatam: feel free to put regXboi in - I'll fill in my details later18:34
regXboithat way it won't be empty :)18:34
SumitNaiksatamevery week, this reviewer team should tell us if we are on track for to approve a particular patch (either spec or code) in time for the milestone set18:34
SumitNaiksatamregXboi: sure18:34
SumitNaiksatamand if we are not on track, what is the blocker18:34
KanzheSumitNaiksatam: +118:34
SumitNaiksatami would not like the task owners to waste their time, if a particular feature is not going to be reviewed in time or has no chance of merging and getting approved18:35
SumitNaiksatamsecondly, i would also like to identify at least 4 cores who can shepherd each blueprint18:36
regXboiunfortunately, there I can't help you :(18:36
mandeep4 cores?18:36
SumitNaiksatammandeep: yes18:36
mandeepThat is a significant request ... but it would be nice to have18:36
SumitNaiksatammandeep: since on bigger blueprints, sometimes its not enough to just have two, sometimes cores go MIA :-)18:37
mandeep;-)18:37
SumitNaiksatammandeep: yes, my suggestion is that we identify at least four cores for each patch18:37
SumitNaiksatammandeep: that increase our chances of making progress18:38
SumitNaiksatamat the end of the day, this is all best effort, so we cant force anyone18:38
SumitNaiksatambut we can try and plan18:38
mandeepI agree. I was just worried if that will make it impossible if we ca not find that many core reviewers18:38
mandeepBut this is a good idea18:38
SumitNaiksatamso if you are a taks owner, please try to identify cores upfront who can help with your patch18:39
mandeepok18:39
SumitNaiksatamif you cannot identify more than 2 cores, then lest bring this up in the meeting, and we can assess18:39
SumitNaiksatamall the above were suggestions to make deterministic/predicatable progress18:39
SumitNaiksatamthoughts/suggestions/opinions?18:40
SumitNaiksatami know we have run out of time18:40
cgoncalvesSumitNaiksatam: +1 for this masterplan of yours18:40
SumitNaiksatamcgoncalves: ok18:40
SumitNaiksatam#action SumitNaiksatam to add reviewers section at the top of https://wiki.openstack.org/wiki/Neutron/AdvancedServices/JunoPlan18:41
SumitNaiksatamok anything else?18:41
SumitNaiksatamif you have further thoughts on making the process better, please do chime in on the maling list or in the next meeting18:42
SumitNaiksatamalright, lets call it wrap18:42
SumitNaiksatamthanks all for attending18:42
SumitNaiksatam#endmeeting18:42
mandeepbye18:42
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:42
openstackMeeting ended Wed May 28 18:42:27 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:42
vinay_yadhavbye18:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-05-28-17.31.html18:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-05-28-17.31.txt18:42
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-05-28-17.31.log.html18:42
regXboibye18:42
banixbye everybody18:42
*** regXboi has left #openstack-meeting-318:42
*** Cathy_ has quit IRC18:42
*** Kanzhe has quit IRC18:43
SumitNaiksatambye!18:43
*** mandeep has quit IRC18:43
SumitNaiksatamSridarK garyduan beyounn_1 natarajk: there?18:43
*** eghobo has joined #openstack-meeting-318:43
SridarKHi yes18:44
SridarKhere18:44
garyduanHi18:44
garyduanI probably have to drop off earlier. We have a customer meeting at 12, again.18:45
SumitNaiksatamsorry for the delay in getting started18:45
*** dkorn has joined #openstack-meeting-318:45
SumitNaiksatam#startmeeting Networking FWaaS18:45
openstackMeeting started Wed May 28 18:45:34 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:45
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:45
*** openstack changes topic to " (Meeting topic: Networking FWaaS)"18:45
openstackThe meeting name has been set to 'networking_fwaas'18:45
SridarKSumitNaiksatam: no worries18:45
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/FWaaS18:45
SumitNaiksatam#topic bugs18:46
*** openstack changes topic to "bugs (Meeting topic: Networking FWaaS)"18:46
SumitNaiksatam#link https://bugs.launchpad.net/neutron/+bug/131085718:47
SumitNaiksatamSridarK: you were reviewing this18:47
SumitNaiksatami think we need to reach out to the owner since this has not be updated18:47
SridarKSumitNaiksatam: not much update on this as got swamped with other things last week18:48
SumitNaiksatamSridarK: ok18:48
SumitNaiksatam#action SridarK SumitNaiksatam to reach out to patch owner for: https://bugs.launchpad.net/neutron/+bug/131085718:48
SridarKSumitNaiksatam: will need to recreated this via the API as manual recreate things are fine18:48
SumitNaiksatamSridarK: ok18:49
SumitNaiksatam#link https://bugs.launchpad.net/neutron/+bug/131431318:49
SumitNaiksatamSridarK: i believe you were looking at this as well18:49
SridarKSumitNaiksatam: oops i reported on the wrong bug18:49
SridarKmy prev update was on this bug (1314313)18:50
SumitNaiksatamah ok18:50
SridarKSumitNaiksatam: perils of multitasking :-(18:50
SumitNaiksatami imagine the same update applies to both :-)18:50
SridarKon 1310857 - we need to understand if the approach taken on the patch is acceptable18:51
SumitNaiksatamSridarK: any chance that we can finalize on the next steps for 1314313 by next week?18:51
SridarKthat was my last comment and others also had comments18:51
SridarKi will reach out to him18:51
SumitNaiksatamSridarK: thanks18:51
SumitNaiksatamSridarK: any chance that we can finalize on the next steps for 1314313 by next week?18:51
SridarKOk on 1314313 - will certainly shoot for that - need to be able to recreate consistently18:51
SumitNaiksatam#action SridarK to change status of bug https://bugs.launchpad.net/neutron/+bug/1314313 by next meeting18:52
SridarKthnk there is a race but will need to confirm with recreate18:52
SumitNaiksatamSridarK: sorry for all the action items :-P18:52
SridarKwill exchg some notes with u offline on that18:52
SridarKno worries :-)18:52
SumitNaiksatamSridarK:  we need to decide whether a patch is necessary or not18:53
SridarKSumitNaiksatam: yes18:53
*** anil_rao has left #openstack-meeting-318:53
SumitNaiksatami see a new one: https://bugs.launchpad.net/neutron/+bug/132332218:53
SumitNaiksatami think enikanorov was checking regarding this yesterday, since he is triaging bugs in general18:54
garyduanSorry guys. I have to leave.18:54
*** OSM has quit IRC18:54
garyduanI will read the log18:54
SumitNaiksatamoh its already merged18:54
SumitNaiksatamgaryduan: thanks18:54
SridarKSumitNaiksatam: nice bug :-)18:55
SumitNaiksatamSridarK: :-)18:55
SumitNaiksatam#link https://bugs.launchpad.net/neutron/+bug/132329918:55
*** gduan has joined #openstack-meeting-318:56
SumitNaiksatami just noticed this and haven’t investigated18:56
SumitNaiksatamwe probably need to check with Rajesh as well18:57
SridarKSumitNaiksatam: yes - i thought this should work18:57
SridarKalso looks like it is assigned18:57
SumitNaiksatamhmm...wait18:57
SumitNaiksatami am wondering if this is mis-classified18:58
SumitNaiksatamhe seems to be talking about security group rules18:58
SumitNaiksatamlets ask for clarification18:59
*** garyduan has quit IRC18:59
SridarKHmm not clear - i see some reference to fw policy in the log18:59
*** peristeri has quit IRC19:00
SumitNaiksatamah ok19:00
SumitNaiksatamany how i have asked for confirmation19:00
SridarKok19:00
SumitNaiksatamother than that nothing at medium or higher19:01
SumitNaiksatam#topic Juno planning and feature tracking19:01
*** openstack changes topic to "Juno planning and feature tracking (Meeting topic: Networking FWaaS)"19:01
SumitNaiksatam#link https://wiki.openstack.org/wiki/Neutron/FWaaS/JunoPlan19:01
*** vinay_yadhav has quit IRC19:02
SumitNaiksatamso i dont see much activity in the table from where we left it the last time19:02
SumitNaiksatamwe really need to put our estimates of milestones here for each item19:02
SumitNaiksatamSridarK beyounn_1: agree?19:03
SridarKSumitNaiksatam: i think if we close on some of the discussion on Service Objects we can get going19:03
SumitNaiksatamSridarK: regardless, i would like to see a proposed milestone here19:03
SumitNaiksatamSridarK: factoring in the discussion time19:03
SridarKSumitNaiksatam: i will push a review for Zones by early next week19:03
SumitNaiksatamSridarK: ok19:03
*** emagana has quit IRC19:03
SridarKSumitNaiksatam: Oh ok19:03
SridarKWill update19:04
SumitNaiksatamas with the advanced services, i would like to pull the PTL into the meeting next week, to get an agreement on the milestone dates19:04
*** Sukhdev has joined #openstack-meeting-319:04
SridarKSumitNaiksatam: yes that will be good19:04
SridarKWe should be targeting J2 for most things19:05
*** emagana has joined #openstack-meeting-319:05
SumitNaiksatam#topic FWaaS and DVR19:05
*** openstack changes topic to "FWaaS and DVR (Meeting topic: Networking FWaaS)"19:05
SumitNaiksatambeyounn_1: there?19:05
SumitNaiksatamthe DVR gerrit spec was merged19:05
SumitNaiksatami had put a comment on that spec that it be called out that there are issues with integration with FWaaS19:05
SumitNaiksatamperhaps, beyounn_1 has dropped off too19:06
SridarKSumitNaiksatam: saw a mail from Swami that the DVR mtg today was cancelled - not sure if beyounn_1 got any more updates19:06
SumitNaiksatamso we are probably going to have a shorter meeting :-)19:06
SridarK:-)19:07
SumitNaiksatam#topic Juno blueprints19:07
*** openstack changes topic to "Juno blueprints (Meeting topic: Networking FWaaS)"19:07
SumitNaiksatamI was hoping to discuss service objects today19:07
SridarKSumitNaiksatam: yes - i think we are a point of getting to some agreement in the review19:08
SumitNaiksatamSridarK: ok19:08
SridarKSumitNaiksatam: I had a few points - once that is cleared - i am +119:08
SumitNaiksatamok19:08
SridarKhopefully with a few more - from internal team - we can get core attention19:09
SumitNaiksatamSridarK: yes, i have to jump on it as well19:09
SumitNaiksatam#topic Open Discussion19:10
*** openstack changes topic to "Open Discussion (Meeting topic: Networking FWaaS)"19:10
SumitNaiksatamanything else to discuss for today?19:10
*** lblanchard has quit IRC19:10
SridarKSumitNaiksatam: should we reach out to at least one other core so along with u - we will have 2 to shepherd the BP ?19:10
*** lblanchard has joined #openstack-meeting-319:10
SumitNaiksatamSridarK: yes, thats what i would like to bring up in the discussion with the PTL next week19:11
SridarKSumitNaiksatam: yes that will be great19:11
SumitNaiksatamanything for us to discuss today?19:12
SridarKSumitNaiksatam: no i am good - will reach out offline if some thing else comes up19:12
SumitNaiksatamSridarK: thanks!19:12
SridarKnp at all19:13
SridarKthanks19:13
SumitNaiksatam#action SridarK beyounn_1 garyduan prad kanzhe to add milestone dates before next meeting to: https://wiki.openstack.org/wiki/Neutron/FWaaS/JunoPlan19:13
SumitNaiksatamthanks19:14
SumitNaiksatam#endmeeting19:14
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:14
openstackMeeting ended Wed May 28 19:14:22 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:14
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-05-28-18.45.html19:14
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-05-28-18.45.txt19:14
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-05-28-18.45.log.html19:14
SridarKBye SumitNaiksatam19:14
*** emagana has quit IRC19:14
SumitNaiksatamSridarK: bye19:14
*** emagana has joined #openstack-meeting-319:15
*** emagana has quit IRC19:17
*** ivar-lazzaro1 has joined #openstack-meeting-319:18
*** chuckC has quit IRC19:19
*** ivar-lazzaro has quit IRC19:20
*** emagana has joined #openstack-meeting-319:20
*** nati_ueno has quit IRC19:32
*** pcm_ has left #openstack-meeting-319:34
*** garyduan has joined #openstack-meeting-319:37
*** gduan has quit IRC19:39
*** rkukura has left #openstack-meeting-319:41
*** otherwiseguy has joined #openstack-meeting-319:49
*** rgbkrk has quit IRC19:56
*** devlaps has quit IRC19:57
*** devlaps has joined #openstack-meeting-320:01
*** rgbkrk has joined #openstack-meeting-320:01
*** chuckC has joined #openstack-meeting-320:03
*** emagana has quit IRC20:04
*** emagana has joined #openstack-meeting-320:04
*** nati_ueno has joined #openstack-meeting-320:06
*** jaypipes has quit IRC20:08
*** garyduan has quit IRC20:09
*** nati_ueno has quit IRC20:11
*** hemanthravi has quit IRC20:11
*** garyduan has joined #openstack-meeting-320:12
*** ivar-lazzaro1 has left #openstack-meeting-320:15
*** ivar-lazzaro has joined #openstack-meeting-320:18
*** hemanthravi has joined #openstack-meeting-320:25
*** ivar-lazzaro has quit IRC20:30
*** ivar-lazzaro has joined #openstack-meeting-320:30
*** terryw has joined #openstack-meeting-320:30
*** otherwiseguy has quit IRC20:31
*** terryw is now known as otherwiseguy20:32
*** emagana has quit IRC20:39
*** mestery has quit IRC20:39
*** mestery has joined #openstack-meeting-320:40
*** ivar-lazzaro has quit IRC20:46
*** nati_ueno has joined #openstack-meeting-320:50
*** emagana has joined #openstack-meeting-320:52
*** davlaps has joined #openstack-meeting-320:52
*** eghobo has quit IRC21:04
*** Sukhdev has quit IRC21:04
*** eghobo has joined #openstack-meeting-321:07
*** mfer has quit IRC21:09
*** hemanthravi has quit IRC21:14
*** Sukhdev has joined #openstack-meeting-321:15
*** lblanchard has quit IRC21:20
*** emaganap has joined #openstack-meeting-321:24
*** emagana has quit IRC21:26
*** SridarK has quit IRC21:26
*** eghobo has quit IRC21:27
*** LouisF has quit IRC21:30
*** david-lyle has quit IRC21:35
*** TravT has joined #openstack-meeting-321:43
*** rgbkrk has quit IRC21:44
*** rgbkrk has joined #openstack-meeting-321:45
*** nati_ueno has quit IRC21:49
*** thomasem has quit IRC21:49
*** dhellmann is now known as dhellmann_21:58
*** dhellmann_ is now known as dhellmann21:58
*** dhellmann is now known as dhellmann_21:58
*** ivar-lazzaro has joined #openstack-meeting-321:59
*** carl_baldwin has quit IRC22:03
*** yamahata has joined #openstack-meeting-322:06
*** nati_ueno has joined #openstack-meeting-322:07
*** lblanchard has joined #openstack-meeting-322:12
*** lblanchard has quit IRC22:13
*** emaganap has quit IRC22:13
*** emagana has joined #openstack-meeting-322:15
*** emagana has quit IRC22:18
*** emagana has joined #openstack-meeting-322:18
*** lblanchard has joined #openstack-meeting-322:26
*** lblanchard has quit IRC22:30
*** lblanchard has joined #openstack-meeting-322:33
*** eghobo has joined #openstack-meeting-322:34
*** lblanchard has quit IRC22:36
*** lblanchard has joined #openstack-meeting-322:37
*** lblanchard has quit IRC22:37
*** lblanchard has joined #openstack-meeting-322:40
*** rgbkrk has quit IRC22:42
*** lblanchard has quit IRC22:42
*** emagana has quit IRC23:02
*** banix has quit IRC23:04
*** yamahata has quit IRC23:09
*** rgbkrk has joined #openstack-meeting-323:10
*** ivar-lazzaro has left #openstack-meeting-323:10
*** prad has quit IRC23:14
*** Sukhdev has quit IRC23:15
*** natarajk has quit IRC23:18
*** amotoki has joined #openstack-meeting-323:20
*** jtomasek has quit IRC23:36
*** jtomasek has joined #openstack-meeting-323:49
*** tomoe_ has joined #openstack-meeting-323:53
*** armax has joined #openstack-meeting-323:53
*** jaypipes has joined #openstack-meeting-323:54
*** armax has left #openstack-meeting-323:55
*** tomoe_ has quit IRC23:56
*** tomoe_ has joined #openstack-meeting-323:57
*** tomoe__ has joined #openstack-meeting-323:58

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