Wednesday, 2014-05-21

*** ttrifonov is now known as ttrifonov_zZzz00:02
*** MarkAtwood has joined #openstack-meeting-300:06
*** Sukhdev has joined #openstack-meeting-300:10
*** sarob has quit IRC00:16
*** nati_uen_ has joined #openstack-meeting-300:21
*** MarkAtwood has quit IRC00:23
*** nati_ueno has quit IRC00:24
*** HenryG_ has joined #openstack-meeting-300:37
*** HenryG_ has quit IRC00:38
*** eguz has quit IRC00:40
*** eghobo has joined #openstack-meeting-300:41
*** jpomero_ has quit IRC00:44
*** MarkAtwood has joined #openstack-meeting-300:46
*** MarkAtwood has quit IRC00:47
*** rand738 has quit IRC00:54
*** rand738 has joined #openstack-meeting-300:54
*** eghobo has quit IRC01:15
*** banix has joined #openstack-meeting-301:21
*** nati_uen_ has quit IRC01:21
*** devlaps has quit IRC01:24
*** MaxV_ has joined #openstack-meeting-301:24
*** nati_ueno has joined #openstack-meeting-301:28
*** nati_ueno has quit IRC01:29
*** otherwiseguy has joined #openstack-meeting-301:29
*** nati_ueno has joined #openstack-meeting-301:30
*** nati_ueno has quit IRC01:38
*** n0ano has quit IRC01:40
*** shakamunyi has quit IRC01:45
*** cjellick_ has joined #openstack-meeting-301:46
*** cjellick has quit IRC01:48
*** cjellick_ has quit IRC01:50
*** terryw has joined #openstack-meeting-301:53
*** otherwiseguy has quit IRC01:53
*** shakamunyi has joined #openstack-meeting-301:59
*** terryw has quit IRC02:00
*** Sukhdev has quit IRC02:05
*** shakamunyi has quit IRC02:05
*** otherwiseguy has joined #openstack-meeting-302:11
*** MaxV_ has quit IRC02:17
*** sankarshan is now known as sankarshan_away02:18
*** chuckC has joined #openstack-meeting-302:28
*** MaxV_ has joined #openstack-meeting-302:36
*** rand738 has quit IRC02:39
*** rand738 has joined #openstack-meeting-302:41
*** MaxV_ has quit IRC02:42
*** cjellick has joined #openstack-meeting-302:47
*** cjellick has quit IRC02:54
*** baojg has joined #openstack-meeting-302:55
*** kenhui has joined #openstack-meeting-302:58
*** baojg has quit IRC03:01
*** baojg has joined #openstack-meeting-303:02
*** cjellick has joined #openstack-meeting-303:05
*** baojg_ has joined #openstack-meeting-303:07
*** rand738 has quit IRC03:08
*** rand738 has joined #openstack-meeting-303:08
*** baojg_ has quit IRC03:09
*** baojg has quit IRC03:09
*** baojg has joined #openstack-meeting-303:10
*** baojg_ has joined #openstack-meeting-303:17
*** baojg has quit IRC03:20
*** kenhui has quit IRC03:21
*** sankarshan_away is now known as sankarshan03:26
*** kenhui has joined #openstack-meeting-303:35
*** otherwiseguy has quit IRC03:39
*** banix has quit IRC03:41
*** rgbkrk has joined #openstack-meeting-303:43
*** eghobo has joined #openstack-meeting-303:45
*** kenhui1 has joined #openstack-meeting-303:50
*** kenhui has quit IRC03:51
*** beyounn has quit IRC03:55
*** gcb has joined #openstack-meeting-304:04
*** jaypipes has joined #openstack-meeting-304:11
*** rgbkrk has quit IRC04:11
*** Sukhdev has joined #openstack-meeting-304:21
*** baojg has joined #openstack-meeting-304:59
*** baojg_ has quit IRC05:00
*** baojg has quit IRC05:00
*** kenhui has joined #openstack-meeting-305:04
*** kenhui2 has joined #openstack-meeting-305:07
*** kenhui has quit IRC05:07
*** kenhui has joined #openstack-meeting-305:07
*** kenhui1 has quit IRC05:08
*** kenhui2 has quit IRC05:11
*** Sukhdev has quit IRC05:13
*** yamamoto_ has joined #openstack-meeting-305:21
*** ttrifonov_zZzz is now known as ttrifonov05:25
*** kenhui has quit IRC05:27
*** rgbkrk has joined #openstack-meeting-305:31
*** lcheng_ has joined #openstack-meeting-305:43
*** ttrifonov is now known as ttrifonov_zZzz05:45
*** ttrifonov_zZzz is now known as ttrifonov05:46
*** cjellick has quit IRC05:54
*** cjellick has joined #openstack-meeting-305:54
*** rgbkrk has quit IRC05:57
*** jtomasek has joined #openstack-meeting-306:00
*** jtomasek has quit IRC06:05
*** jtomasek has joined #openstack-meeting-306:14
*** mrunge has joined #openstack-meeting-306:24
*** mrunge has quit IRC06:24
*** mrunge has joined #openstack-meeting-306:24
*** bauzas1 has quit IRC06:49
*** bauzas has joined #openstack-meeting-306:49
*** lcheng_ has quit IRC06:49
*** lcheng_ has joined #openstack-meeting-306:50
*** jcoufal has joined #openstack-meeting-307:05
*** eghobo has quit IRC07:12
*** 16WAAB1RW has joined #openstack-meeting-307:16
*** ttrifonov is now known as ttrifonov_zZzz07:23
*** lsmola has quit IRC07:39
*** lsmola has joined #openstack-meeting-307:39
*** lcheng_ has quit IRC07:55
*** lcheng_ has joined #openstack-meeting-307:56
*** 16WAAB1RW has quit IRC07:57
*** nacim has joined #openstack-meeting-308:18
*** jamie_h has joined #openstack-meeting-308:31
*** safchain has joined #openstack-meeting-308:32
*** lcheng_ has quit IRC08:54
*** jcoufal has quit IRC09:10
*** sankarshan is now known as sankarshan_away09:19
*** coolsvap|afk is now known as coolsvap10:11
*** jcoufal has joined #openstack-meeting-310:15
*** yamamoto_ has quit IRC10:24
*** rgbkrk has joined #openstack-meeting-310:31
*** jcoufal has quit IRC10:39
*** jcoufal has joined #openstack-meeting-310:40
*** nacim has quit IRC10:44
*** rgbkrk has quit IRC10:48
*** nacim has joined #openstack-meeting-310:58
*** coolsvap is now known as coolsvap|afk11:07
*** coolsvap|afk is now known as coolsvap11:10
*** ajo has quit IRC11:15
*** banix has joined #openstack-meeting-311:15
*** coolsvap is now known as coolsvap|afk11:23
*** mwagner_lap has quit IRC11:33
*** banix has quit IRC11:38
*** coolsvap|afk is now known as coolsvap11:41
*** sankarshan_away is now known as sankarshan11:53
*** kashyap has left #openstack-meeting-311:57
*** coolsvap is now known as coolsvap|afk12:00
*** mrunge is now known as mrunge_away12:14
*** lblanchard has joined #openstack-meeting-312:19
*** dkorn has joined #openstack-meeting-312:22
*** rgbkrk has joined #openstack-meeting-312:22
*** gcb has quit IRC12:39
*** bauzas has quit IRC12:41
*** bauzas has joined #openstack-meeting-312:41
*** bauzas has quit IRC12:42
*** bauzas1 has joined #openstack-meeting-312:42
*** HenryG has joined #openstack-meeting-312:49
*** mwagner_lap has joined #openstack-meeting-312:50
*** thomasem has joined #openstack-meeting-313:00
*** mfer has joined #openstack-meeting-313:02
*** rgbkrk has quit IRC13:17
*** peristeri has joined #openstack-meeting-313:26
*** julim has joined #openstack-meeting-313:27
*** jpomero has joined #openstack-meeting-313:34
*** dhellmann_ is now known as dhellmann13:35
*** yamamoto has joined #openstack-meeting-313:47
*** yamamoto has quit IRC13:52
*** otherwiseguy has joined #openstack-meeting-313:59
*** cjellick has quit IRC14:03
*** terryw has joined #openstack-meeting-314:03
*** pgpus has joined #openstack-meeting-314:06
*** otherwiseguy has quit IRC14:06
pgpusWhat Pacific Standard Time does this meet occur today?14:06
*** yjiang51 has joined #openstack-meeting-314:07
*** rgbkrk has joined #openstack-meeting-314:08
*** bauzas1 has left #openstack-meeting-314:15
*** rgbkrk has quit IRC14:15
*** pgpus has left #openstack-meeting-314:16
*** lcheng_ has joined #openstack-meeting-314:18
*** nelsnelson has joined #openstack-meeting-314:18
*** Munish has joined #openstack-meeting-314:19
*** lcheng_ has quit IRC14:23
*** nelsnelson has quit IRC14:23
*** nelsnelson has joined #openstack-meeting-314:23
*** vinay_yadhav has joined #openstack-meeting-314:27
*** lcheng_ has joined #openstack-meeting-314:29
*** shakamunyi has joined #openstack-meeting-314:31
*** cjellick has joined #openstack-meeting-314:35
*** cjellick has quit IRC14:35
*** sc68cal has joined #openstack-meeting-314:35
*** cjellick has joined #openstack-meeting-314:36
*** Munish has quit IRC14:36
*** david-lyle has joined #openstack-meeting-314:37
*** yjiang51 has quit IRC14:38
*** markmcclain has joined #openstack-meeting-314:40
*** markmcclain has quit IRC14:40
*** markmcclain has joined #openstack-meeting-314:40
*** lcheng_ has quit IRC14:46
*** yamahata has joined #openstack-meeting-314:46
*** devlaps has joined #openstack-meeting-314:50
*** rgbkrk has joined #openstack-meeting-314:51
*** Munish_ has joined #openstack-meeting-314:52
*** coolsvap|afk is now known as coolsvap14:54
*** banix has joined #openstack-meeting-314:59
*** beyounn has joined #openstack-meeting-315:01
*** yisun has joined #openstack-meeting-315:02
*** beyounn has quit IRC15:02
*** beyounn has joined #openstack-meeting-315:03
*** beyounn has quit IRC15:05
*** nacim has quit IRC15:05
*** dkorn has quit IRC15:05
*** vinay_yadhav has quit IRC15:07
*** TravT has joined #openstack-meeting-315:07
*** regXboi has joined #openstack-meeting-315:09
*** Munish_ has quit IRC15:10
*** samchoi has joined #openstack-meeting-315:22
*** glenc_ has quit IRC15:29
*** coolsvap is now known as coolsvap|afk15:30
mfer#startmeeting openstack-sdk-php15:30
openstackMeeting started Wed May 21 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
mferWelcome everyone.15:30
glenc-o/15:30
mferPlease state your name and any applicable association15:30
mferMatt Farina, HP15:30
samchoiSam Choi, HP15:31
glenc-Glen Campbell, Rackspace15:31
jamie_hJamie Hannaford, Rackspace15:31
*** glenc has quit IRC15:31
*** glenc- is now known as glenc15:31
mfer#topic Agenda15:32
*** openstack changes topic to "Agenda (Meeting topic: openstack-sdk-php)"15:32
mfer#link https://wiki.openstack.org/wiki/Meetings/OpenStack-SDK-PHP15:32
mferThere are 7 items on the agenda but given the audience we can do just the last 6.15:32
mferIs there anything that should be added?15:32
mfer1. Intro to the PHP SDK if there is anyone new? (mfer)15:32
mfer2. FQCNs in DocBlocks (mfer)15:32
mfer3. json schema (mfer)15:32
mfer4. transport layer (mfer)15:32
mfer5. testing (mfer)15:32
mfer6. 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
mfer7. What are the essential blueprints/bugs that need to be finished before we can move on to working on additional services? (samchoi)15:32
jamie_hI have nothing to add15:33
mfer#topic FQCNs in DocBlocks15:33
*** openstack changes topic to "FQCNs in DocBlocks (Meeting topic: openstack-sdk-php)"15:33
mferIn a recent review samchoi noticed that some cases have shortened references to classes to just the imported name rather than that full name15:34
mferAs I understand it, some IDEs don't handle this well15:34
mfersamchoi did you have anything else you wanted to add?15:34
samchoiI can confirm several versions of Zend Studio (Eclipse) have the issue with auto complete. NetBeans appears to have the issue as well.15:35
samchoiThat's about it15:35
mfersamchoi when the full path is provided it works?15:35
samchoiyes15:35
mferjamie_h what do you think about using the full path for classes in @params, @returns, and @throws?15:36
jamie_hthe only advantage of short forms is that it's briefer and saves space15:36
jamie_hplaying devil's advocate: should IDE support inform technical/internal decisions?15:37
jamie_hI don't really mind either way as long as we're consistent15:37
glenc+115:37
*** Sukhdev has joined #openstack-meeting-315:38
mferI think that's a good question. here was my initial take but i'm open to someone telling me something different. the goal of the SDK is developer experience. we want to have a good one. A lot of PHP devs use these IDEs so we should give them a good experience.15:38
mferthat would lead to the longer form15:38
mferjamie_h glenc samchoi thoughts? other ways to look at it?15:39
jamie_hthere's also nothing really stopping us using short forms, say in a year or two, if IDEs start supporting them15:39
jamie_hso for now I'm happy using FQCNs15:39
mferwe can always change in the future. even without a major point release because the API wouldn't be changing15:39
glencI probably wouldn't spend a huge amount of time retrofitting existing stuff, but simply set a standard and change them as we encounter them.15:40
glencMake it a standard to use the FQCN15:40
samchoiFor the reasons jamie_h mentioned in response to my reviews, I also like local/short names as well if all things were equal. I think using FQCN and considering future changes would be a good approach15:40
mferok, then i think this is settled. we can move on to the next topic. sorry if i push this a little quickly. there are a bunch of topics15:41
mfer#topic json schema15:41
*** openstack changes topic to "json schema (Meeting topic: openstack-sdk-php)"15:41
mferjamie_h glenc have the two of you had a chance to talk with jesse noller about this?15:41
*** devlaps has quit IRC15:41
glencYes, we've had some extensive email threads15:42
jamie_hjesse e-mailed us about a decision being made at the summit about not using JSON schemas for the time being - but to some how bake in support for the future15:42
glencI understand that it's not recommended for the time being15:42
glencbut IMHO they don't really understand our use case within the SDK; doesn't make sense to develop something else and then replace it in six months to a year.15:42
mferJesse and I each went out to assess the situation at the summit. we came together to talk about it. let me share what I learned and we can discuss.15:43
mferjson schema was a fairly big and common topic at the summit. a number of projects want to or are starting to use it in different ways. For example, some wand to describe their "objects" in it and use that for validation. this is a fairly different case from ours.15:44
mferothers want to use it to describe api interactions at the REST level. this is in line with what we are looking for.15:45
mferI spoke with several people on different teams who told me that using json schema the way we want to is a great idea. they also said don't do it yet15:45
mferof all the people i spoke with the common theme was that sdks should use json schema but not yet. no one was saying do it now.15:46
mferat least to me15:46
mferit opens up questions of who manages the schemas, where do they live, how are they shared and kept up to date.15:46
mferthere is my context. i want to know what the rest of you think15:46
jamie_hwas there a reason for not using it right now? the ownership/location issue you just brought up isn't a temporary one, it will always be the case15:47
mfernote, i'm sharing what i heard not my opinion on this topic15:47
mferjamie_h until service create schemas for their services and manage them themselves. then we would be a consumer of that15:47
jamie_hanother reason i can see for not using JSON schemas right now is because the actual spec is still a bit rough around the edges15:48
mferthere were a number of sessions on cleaning up the api. there was quite a bit of agreement that it "needs work"15:48
jamie_hif an API provides us with schemas (in the future), that won't give us the DSL we were talking about15:49
jamie_hi.e. defining REST operations15:49
glencThe use case for the SDK is that we need a way to describe a service so that the underlying code can be simplified and be metadata-driven. If we DON'T use json schema, then we need some other way to describe those services, and I don't know what that could be.15:49
jamie_hall JSON schema is useful for is modelling data structures. We still need a way to describe services15:50
jamie_heither in a DSL (metadata) or userland code15:50
glencWADL :(15:50
mferglenc there were a number of conversations on the side about metadata driven SDKs. I was surprised how many SDK devs there were opposed to it. I'm not opposed to it, personally.15:50
jamie_hI don't mind not using schemas - but we need to think about how we'll describe services15:50
mfereven if we do it on PHP there will be opposition on other SDKs which brings up a consistency problem15:50
glencI'm nervous about it but I can see the benefits, if implemented properly. FWIW, I did a ton of metadata-driven libraries back in my past, and sometimes the metadata DSL became more complicated than the underlying programming language.15:51
*** yjiang51 has joined #openstack-meeting-315:51
*** yjiang51 has quit IRC15:51
jamie_hwhen I was searching on the mailing list, most people seem enthused about a metadata-driven SDK because it was so powerful. So I'm surprised to hear the contrary15:51
mferit more or less changes the problem from one of coding for the API or coding to make the DSL/metadata work well.15:52
mferjamie_h i was surprised too!15:52
glencYes, and coding a DSL interpreter that is sufficiently rich to support everything in all the services15:52
jamie_hbut the tradeoffs are clear: userland code is slower to write, has duplication, bloats the codebase and requires hundreds more tests15:53
jamie_hthe debate between a DSL and userland code is separate from that of JSON schemas - I'm happy to ignore json schemas if openstack does not think it's ready15:54
mferwell, a DSL and schema needs to be learned which is not common in many circles which takes more ramp up time. you can write userland code to cut down duplication.15:54
mferjamie_h how about this. we next look at what a DSL would look like without json schema. test the waters15:55
samchoimfer: Agreed..was just about to mention that implementing a DSL can create more of a barrier to entry for new contributors15:55
samchoiIf we don15:55
jamie_ha DSL can also serve as living documentation, which is beneficial to end-users15:55
*** coolsvap|afk is now known as coolsvap15:55
*** eghobo has joined #openstack-meeting-315:55
jamie_hmfer that sounds good. Let's leave JSON schema behind and make this a question of how to describe services15:55
*** yamamoto has joined #openstack-meeting-315:56
mferjamie_h we need to make sure it makes sense to those using an IDE or documentation system. A schema and DSL aren't self documentation to many in the long tail.15:56
mferjamie_h samchoi what about comparing a DSL to that of a userland code solution?15:56
jamie_hmfer let's do some more investigation about DSL vs userland code - and then make a decision15:57
samchoimfer: My only thought at the moment is that topic could take us the rest of the meeting. I don't know that we've explored that enough.15:57
jamie_hI think it's best to investigate outside of this meeting15:57
mferyeah15:57
mferjamie_h since you're interested in the DSL portion would you be willing to put something together for us to evaluate there?15:57
jamie_hsure15:57
mfersamchoi since you brought up the userland code option, would you be up for a solution that does that for us to look at?15:58
samchoialright15:58
mferyay! progress15:58
glencmfer - FYI, I have to step out to attend another meeting.15:59
glencsee y'all next week15:59
mfer#action jamie_h create a DSL demo to compare for an architecture path forward.15:59
mfer#action samchoi create a userland code demo to compare for an architecture path forward.15:59
mferglenc see ya and thanks for coming15:59
mferok, can we move on to the next topic16:00
jamie_hI don't know whether it'll be a full demo - I'll outline tradeoffs and provide a sample implementation :)16:00
jamie_hhappy to move on to next topic16:00
samchoisure, ready to move on16:00
mferjamie_h yeah, i'm not looking for a full demo. just enough for evaluation16:00
mfer#topic transport layer16:00
*** openstack changes topic to "transport layer (Meeting topic: openstack-sdk-php)"16:00
mferjamie_h i like what you'd started with the guzzle change. i just had one outstanding question...16:01
mferwhy the use of events to fire off exceptions?16:01
mfermuch of what you did could be implemented with a single class. i'm trying to understand the differences16:01
jamie_hGuzzle uses events in the life cycle of its requests. This is how it handles exceptions. So if we're using Guzzle, it makes sense to take advantage of their underlying system16:02
jamie_hplus events are extremely beneficial because it allows you to add in functionality instead of extending/overriding other library classes16:02
jamie_hplus it allows you to have a class whose responsibilities are exception handling, instead of mixing that logic with others16:03
mferone of the things we should take care of doing is making the transport layer transparent to end users. you use one but in your general code it doesn't matter. an event attached to a service call is on the service and happens with all transport layers16:04
mferthere is a clean separation16:04
mfer#link http://docs.guzzlephp.org/en/latest/clients.html?highlight=exception#asynchronous-response-handling16:05
*** yamahata has quit IRC16:05
mferin that section of the guzzle docs it does say to use exceptions from events. so, this makes sense. not sure how i didn't see this before16:06
mferjamie_h what do you think of my thoughts on the separation?16:06
jamie_hall that code does is attach the callback to the client16:06
mferyeah16:06
jamie_hcan you rephrase what you mean about separation - not sure I understood16:06
mfera service is one thing and a transport layer is separate. so, if we add events to services it's separate from events on the transport layer.16:07
mferi would like to see clear separation between the two systems16:07
mfereven if one implents the system for the other16:08
jamie_hme too. a transport client is injected into a service, with its own (i.e. exception) subscribers16:08
*** devlaps has joined #openstack-meeting-316:08
mfergreat16:08
jamie_hthe exception handling thing I coded isn't coupled to services - it's purely transport16:08
mferyeah16:09
jamie_hkeeping that separation is very important, I agree16:09
mferok, great. i'm looking forward to the next patch set to fix the segfault issue so we can keep this moving.16:09
mfersamchoi do you have any other questions about this?16:09
jamie_hdo you want me to submit that fix as a separate patch or shall I update the current patch with the changes?16:09
samchoino, it seems like we're just making sure the transport layer is still loosely coupled for flexibility16:09
mferjamie_h just update the current set. it's a dependency to your other one that's ready to go in.16:10
mferare we ready for the next topic?16:10
jamie_hyep16:10
mfer#topic testing16:10
*** openstack changes topic to "testing (Meeting topic: openstack-sdk-php)"16:10
mferwhen I was at the summit I wanted to know how we can get the PHP SDK tested against multiple PHP versions16:11
mferI found out that we now can. where there were limitation stopping us before we can do this and nodepool should enable it to work16:11
mferunless someone else wants the action, I was going to take a look into how we can get this setup16:12
jamie_hthat sounds *really* useful16:12
samchoisure mfer , I can't see anyone refusing automated testing16:12
mferthat's all i wanted to say. i know it had been a point of frustration and we'd talked about Travis CI as an alternative16:13
mferdoes anyone else want to talk about testing the things or shall we move on?16:13
jamie_hi have something to add about our testing setup - but more related to code than infra16:13
mferjamie_h is it about faster testing?16:14
jamie_hthat's one of them16:14
jamie_hthe other is for us not to use @depends16:14
mferwhy is that?16:14
jamie_hbecause it tightly couples tests together and makes them brittle. unit tests should be completely isolated and autonomous16:14
jamie_hthere's nothing wrong with using class properties (like $this->resource), but a unit test should not rely on another for input16:15
mferjamie_h how would you handle all the different setup and tear down cases?16:15
jamie_hyou'd have a generic setup and tear down case, and allow individual tests to instantiate their own fixtures as needed16:16
jamie_hbut the majority of cases tests will probably need a generic fixture16:16
mferjamie_h in the interest of time can you send an email to the list about this? I'm not opposed to it but I fear we'll run out of time on this topic.16:17
jamie_hsure16:17
mferwould that work?16:17
mferthanks16:17
mferi look forward to that email. i know testing is a broader topic than just this and we really don't have the time today. if we aren't done on the list by next week we can pick it up again then.16:18
mferIf we're ok with it, let's jump into the reviews in progress16:18
jamie_hhappy to move on16:18
samchoisure16:18
mfer#topic Reviews in progress16:19
*** openstack changes topic to "Reviews in progress (Meeting topic: openstack-sdk-php)"16:19
mfer#link https://review.openstack.org/#/q/status:open+project:stackforge/openstack-sdk-php,n,z16:19
mferfirst up we have https://review.openstack.org/#/c/93892/. This removed even having default swift regions.16:20
mferjamie_h would you have a chance to review this one?16:20
jamie_hI'll take a look tomorrow morning16:20
mferthanks16:20
samchoiIn the interest of time, I'm ot too worried about the first three since it looks like those are fairly straightforward and already got positive reviews16:20
mfersamchoi ok16:20
mferhttps://review.openstack.org/#/c/93089/ the clientinterface and guzzle changes. besides the segfault fix is there anything else that needs to be handled or talked about?16:21
*** igordcard_ has joined #openstack-meeting-316:22
mfersamchoi jamie_h ??16:22
jamie_hi have nothing to add16:22
samchoiSince we're not going with JSON schema at this point, it seems like the concerns we had about having to refactor are invald now16:22
samchoiso yes16:22
samchoithat's it16:22
mferand if they aren't we'll modify things later16:22
mferhttps://review.openstack.org/#/c/92280/ the sphinx one. i was hoping Shaunak would be here to talk about this16:23
jamie_hif there are any comments about this patch, i can pass them on16:23
mferjamie_h do you know when he'll be back to chat?16:23
mferthere are questions on it16:23
jamie_hi'm not sure, i think shaunak is travelling for conferences for a while16:24
jamie_hshall we postpone this one until we know more16:24
mfersure.16:24
samchoiSure, this review has less of an effect on others' work16:24
mferif he's too busy and one of us wants to jump in we can talk about it then16:25
mferthen there is https://review.openstack.org/#/c/90407/ which is on testing16:25
mferto be honest, i'd like to see if there is a better option16:26
jamie_hso, some preamble: I'm completely for end-to-end testing, it's incredibly important. But it should not be mixed with unit tests16:26
mferhow much isn't integration tests?16:26
jamie_hi think the vast majority are integration tests16:27
mferis it worth the effort to separate them if we can have a way to run the who suite really fast?16:27
jamie_hprobably not - perhaps it requires a more comprehensive solution16:27
jamie_hthis was just a temporary workaround16:27
mferare you familiar with php vcr? i'm not but samchoi has been looking into it16:28
jamie_hyeah, I've looked into it16:28
*** rgbkrk has quit IRC16:28
samchoiFrom what I understand, the Ruby Fog guys are using it quite extensively and had great results16:28
samchoiso it got my attention16:28
jamie_hyeah, but that just speeds up integration tests. I can go into more detail on the mailing list16:28
jamie_habout what I mean, because I don't think we have time now16:28
samchoisure16:29
mferjamie_h thanks. i'm not opposed to any changes. it would just be good to talk through it so we can all understand all the things16:29
*** garyduan has joined #openstack-meeting-316:29
mferand we are out of time. thanks everyone for coming. feels like this was a good meeting.16:30
samchoihmm the last agenda item wasn't a high priority btw, since we're going to be kicked out16:30
mfer#endmeeting16:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:30
openstackMeeting ended Wed May 21 16:30:26 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-21-15.30.html16:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_sdk_php/2014/openstack_sdk_php.2014-05-21-15.30.txt16:30
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_sdk_php/2014/openstack_sdk_php.2014-05-21-15.30.log.html16:30
*** tjones has joined #openstack-meeting-316:30
tjones#startmeeting NovaBugScrub16:30
openstackMeeting started Wed May 21 16:30:48 2014 UTC and is due to finish in 60 minutes.  The chair is tjones. Information about MeetBot at http://wiki.debian.org/MeetBot.16:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:30
*** openstack changes topic to " (Meeting topic: NovaBugScrub)"16:30
openstackThe meeting name has been set to 'novabugscrub'16:30
tjoneshi anyone here today?16:30
wendartjones: hi16:31
tjoneshi wendar16:31
tjones*listens for others*16:31
tjonesok just you and me then16:32
*** pballand has joined #openstack-meeting-316:33
wendarI've been working on nova/oslo bugs.16:33
tjonesi've already tagged most of the untagged bugs.  thanks for doing that.16:33
tjonesi spoke with mikal at the summit and we said we would hold a bug day next week (or the week after).  so i'll send something to the ML about that.  probably on a wednesday16:34
tjones#action tjones schedule bug day and send out the info to the ML16:34
*** yisun has quit IRC16:34
tjonesthe other thing he wanted me to do is help to drive the critical bug list at the weekly nova meeting.  However - with only priority  it is hard to see what else is critical.  any ideas on that?16:35
tjoneslike come up with a top 10 list of bugs people should be pushing on16:35
tjonescurrently there is 1 marked critical - but is seems like there are probably others that are super high prio but not *quite* critical16:36
wendarI guess I'd tackle it two ways: Which bugs underpin Juno release goals? and Which bugs do the various section leads need soonest?16:36
tjonessounds good - but im not sure i am in a position to judge..  Unless it is an area i am very involved in i cannot really tell other than the prio that people set.16:37
tjonesprob not fair for me to push vmwareapi bugs just because i have intimate knowlege of them16:38
tjonesi guess i need to lean on the section leads to help with this16:38
tjonesi've started an etherpad to review during the nova meeting16:39
tjones#link https://etherpad.openstack.org/p/NovaTopTenBugs16:39
tjonesi'll ask people to add to it if they have critical issues and i can help drive that16:40
tjonesthat's all i really had for today.16:40
wendarThat sounds good.16:41
*** vinay_yadhav has joined #openstack-meeting-316:41
tjonesanything you think i should be doing differently?16:42
tjonesok im going to go ahead and end then.  thanks for helping out16:45
tjones#endmeeting16:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:45
openstackMeeting ended Wed May 21 16:45:11 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/novabugscrub/2014/novabugscrub.2014-05-21-16.30.html16:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/novabugscrub/2014/novabugscrub.2014-05-21-16.30.txt16:45
openstackLog:            http://eavesdrop.openstack.org/meetings/novabugscrub/2014/novabugscrub.2014-05-21-16.30.log.html16:45
*** ndipanov has quit IRC16:50
*** safchain has quit IRC16:54
*** rgbkrk has joined #openstack-meeting-316:58
*** igordcard_ has quit IRC16:59
*** SumitNaiksatam has quit IRC16:59
*** igordcard has joined #openstack-meeting-316:59
*** jamielennox is now known as jamielennox|away17:00
*** rkukura has joined #openstack-meeting-317:07
*** rgbkrk_ has joined #openstack-meeting-317:09
*** kenhui has joined #openstack-meeting-317:09
*** rgbkrk has quit IRC17:10
*** garyduan has quit IRC17:11
*** terryw has quit IRC17:13
*** garyduan has joined #openstack-meeting-317:13
*** nati_ueno has joined #openstack-meeting-317:13
*** mandeep has joined #openstack-meeting-317:13
*** otherwiseguy has joined #openstack-meeting-317:16
*** SumitNaiksatam has joined #openstack-meeting-317:16
vinay_yadhavHi sumit17:17
SumitNaiksatamvinay_yadhav: hi17:17
vinay_yadhavi have prepared a first draft for Tap-as-a-service17:18
vinay_yadhavi will share it on the mailing list17:18
*** markmcclain has quit IRC17:18
SumitNaiksatamvinay_yadhav: nice17:18
SumitNaiksatamvinay_yadhav: if you want to discuss in the meeting, you can add it to the agenda: https://wiki.openstack.org/wiki/Meetings/AdvancedServices17:19
vinay_yadhavi will formally commit it after the meeting ot tomorrow17:19
*** kenhui has quit IRC17:21
*** kenhui has joined #openstack-meeting-317:22
*** garyduan has quit IRC17:22
*** gduan has joined #openstack-meeting-317:22
*** beyounn_1 has joined #openstack-meeting-317:23
*** kanzhe has joined #openstack-meeting-317:23
*** igordcard has quit IRC17:26
vinay_yadhavi have added TaaS in the agenda17:27
*** pballand has quit IRC17:27
*** kenhui has quit IRC17:28
*** arao012 has joined #openstack-meeting-317:28
*** kenhui has joined #openstack-meeting-317:29
*** pgpus has joined #openstack-meeting-317:29
SumitNaiksatamvinay_yadhav: thanks17:30
SumitNaiksatamhello neutron folks!17:30
pgpusYes indeepd this is my first meeting after 3 years with opesntack neutron!!!17:30
cgoncalvesSumitNaiksatam: greetings17:30
*** natarajk has joined #openstack-meeting-317:30
SumitNaiksatampgpus cgoncalves: hi17:30
banixhi17:31
SumitNaiksatampgpus: welcome ot the meeting17:31
rkukurahi17:31
*** s3wong has joined #openstack-meeting-317:31
vinay_yadhavhi all17:31
SumitNaiksatamrkukura banix: hi17:31
*** jmsoares has joined #openstack-meeting-317:31
s3wongIs the advanced service still taken place today?17:31
regXboi'ola17:31
SumitNaiksatamok i think we have critical mass lets get started17:31
SumitNaiksatams3wong: ^^^ :-)17:31
pgpussuper17:31
kanzhehi17:31
SumitNaiksatam#startmeeting Networking Advanced Services17:31
openstackMeeting started Wed May 21 17:31:59 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.17:32
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:32
*** openstack changes topic to " (Meeting topic: Networking Advanced Services)"17:32
openstackThe meeting name has been set to 'networking_advanced_services'17:32
*** pcm_ has joined #openstack-meeting-317:32
s3wongvinay_yadhav: welcome!17:32
beyounn_1hi17:32
vinay_yadhavthanx!17:32
SumitNaiksatam#topic Atlanta summit recap17:32
*** openstack changes topic to "Atlanta summit recap (Meeting topic: Networking Advanced Services)"17:32
*** lcheng_ has joined #openstack-meeting-317:32
SumitNaiksatam#link https://etherpad.openstack.org/p/juno-advanced-services17:32
s3wongvinay_yadhav is working on network tap / port mirroring, and kanzhe and I asked him to join us here17:32
SumitNaiksatamwe had long discussions during the summit, and most of you were part of that17:32
rkukuraSumitNaiksatam: agenda link?17:33
SumitNaiksatams3wong: yes, sure, vinay_yadhav mentioned that to me, we interacted at the summit as well17:33
*** eguz has joined #openstack-meeting-317:33
SumitNaiksatam#info agenda: https://wiki.openstack.org/wiki/Meetings/AdvancedServices17:33
*** sballe has joined #openstack-meeting-317:33
sballeHi17:34
SumitNaiksatamthe summit session time was on the shorter side, to go through the design in detail17:34
SumitNaiksatamsballe: hi17:34
*** SridarK has joined #openstack-meeting-317:34
SumitNaiksatamany after thoughts from the summit?17:34
SumitNaiksatamif not, lets get into the specifics17:35
SumitNaiksatam#topic Juno planning and feature tracking17:35
*** openstack changes topic to "Juno planning and feature tracking (Meeting topic: Networking Advanced Services)"17:35
SumitNaiksatam#link https://wiki.openstack.org/wiki/Neutron/AdvancedServices/JunoPlan17:35
SumitNaiksatami made a first cut with links to the blueprints that have been posted in gerrit so far17:35
*** emagana has joined #openstack-meeting-317:36
SumitNaiksatamthis is not to say that what we intend to discuss in this forum is only limited to what is currently in the table17:36
SumitNaiksatamjust a starting point17:36
SumitNaiksatammy proposal is that we populate the items in that table, and start tracking them in this meeting (based on prirority)17:37
SumitNaiksatamthoughts?17:37
*** eghobo has quit IRC17:37
cgoncalvesSumitNaiksatam: thank you for creating that page. it will definitely help all of us keep track of most if not all BPs17:37
SumitNaiksatamcgoncalves: sure17:37
kanzheSumitNaiksatam: +117:37
SumitNaiksatamkanzhe: ok17:37
SumitNaiksatami have volunteered names for owners ;-)17:37
*** Sukhdev has quit IRC17:38
cgoncalvesSumitNaiksatam: :-)17:38
SumitNaiksatambut if anyone wants to take up items which are not being looked at, please feel free to do so and add17:38
cgoncalvesSumitNaiksatam: what will be the prioritization criteria?17:38
SumitNaiksatamcgoncalves: good question17:38
SumitNaiksatamcgoncalves: to a large extent we need to align balance the priorities of Neutron as a whole, with what we do here17:39
SumitNaiksatamcgoncalves: so the things which have direct dependencies, should obviously higher priority17:39
SumitNaiksatamwe need to eventually discuss this with the PTL and the core team17:39
cgoncalvesSumitNaiksatam: agreed17:39
SumitNaiksatamfor now, my suggestion is that, lets populate the table with the items, and when you think you can achieve these17:40
SumitNaiksatamwe can take it from there17:40
*** tjones has left #openstack-meeting-317:40
SumitNaiksatamsound okay to everyone?17:40
mandeep+117:40
cgoncalves+117:41
kanzhe+117:41
SumitNaiksatamok17:41
s3wongSumitNaiksatam: how about the spec approval? is anyone looking to push those forward?17:41
SumitNaiksatams3wong: good question, we have to do that as a team :-)17:41
kanzhes3wong: I was going to ask the same question.17:41
SumitNaiksatamcore reviewer cycles are limited, so this going to be tough17:42
SumitNaiksatambut +1s do matter17:42
s3wongSumitNaiksatam: kanzhe: I am OK with starting to code, but it would be difficult if some core dev keeps on requesting changes17:42
rkukuraI’d like to see several +1’s on each spec from subteam members before we start recruiting core reviewers17:42
SumitNaiksatamso as a team lets start getting comments out (we dont have to wait for the cores)17:42
* cgoncalves senses a '+1 specs review trading'17:42
kanzheThis team should converge on the spec first. +1 from all members would be a good indication.17:42
SumitNaiksatamcgoncalves: by all means17:42
SumitNaiksatamrkukura: +117:42
* mandeep cgoncalves ;-)17:42
pgpusThe order seems ok to me as enetered for now flvaor, insertion, steering and chaninig17:42
SumitNaiksatams3wong: yes lets get the spec approved before any major coding, you can definitely do a quick PoC to validate17:43
pgpusmay be chaining and traffic steering can be paralle17:43
SumitNaiksatampgpus: ok, thanks for that feedback17:43
SumitNaiksatampgpus: agree17:43
banixpgpus: well, we may not need steering for chaining; so will change the order at the end17:44
banixpgpus: yes17:44
*** kenhui has quit IRC17:44
pgpusthats should be fine17:44
mandeeppgpus: The objective was to keep chaining as independent as possible so that it can provided by different technologies (using service ports + steering or existing services)17:44
SumitNaiksatamso let me ask, what other “topics” from the ones that are mentioned in the table are on our immediate radar?17:44
pgpusservice sharing by users belonging to a tenant17:45
s3wongSumitNaiksatam: you mean, other topics in addition to what is on the wiki?17:45
SumitNaiksatams3wong: yes, in addition to what is noted in: https://wiki.openstack.org/wiki/Neutron/AdvancedServices/JunoPlan17:45
pgpusNo sure if sharing is there may be  i need to look little deper into that17:46
banixSumitNaiksatam: NA means Not Applicable as in we are not going to do it?17:46
SumitNaiksatambanix: probably bad choice of words :-)17:46
SumitNaiksatambanix: will change that to Juno17:46
SumitNaiksatampgpus: are you planning a blueprint for this?17:46
*** Zzeedd has joined #openstack-meeting-317:47
SumitNaiksatamok in, general, let me propose that for topics to appear in the above table, you need to have a gerrit spec submitted, does that sound reasonable?17:47
banixSumitNaiksatam: yes got a bit confusng, thanks.17:47
cgoncalvesSumitNaiksatam: +117:47
mandeepagreed17:47
vinay_yadhavok17:47
SumitNaiksatamok good17:48
pgpusOK after reviewing of all BPs I will see if I need to add  a new BP if its required as service offerred by a Service Provider must be shared among many users belonging to that tenant17:48
SumitNaiksatampgpus: ok17:48
SumitNaiksatamat this point we have a lot on our plates, so we cannot go too much beyond what we currently have17:48
SumitNaiksatamthe resource contention is on the reviewer time (not so much on the developer effort)17:49
pgpusOK but is it's just adding a flag or two to share with minimum code I don't see that a big deal17:49
SridarKSumitNaiksatam: +1 i hope we can get Flavors and Service Insertion at least17:49
SumitNaiksatampgpus: sure, i was not commenting on your suggestion, i was just making a general statement17:49
s3wongSumitNaiksatam: +1, getting too ambitious here now, it seems :-)17:49
SumitNaiksatamSridarK s3wong agree (i tempted to say, show me the code ;-))17:50
SridarK:-)17:50
pgpusSure falvor is easier once we compare wth nova flavors and add what we ned from our resources and pools17:50
s3wongSridarK: that would be great accomplishment by Juno already17:50
SumitNaiksatamok, so starting today, we will track based on the table :-)17:50
SumitNaiksatamthe table might have more items in the coming weeks, and we will evaluate accordingly17:51
pgpusok17:51
SumitNaiksatameveryone okay?17:51
s3wong+117:51
vinay_yadhavok17:51
SridarK+117:51
cgoncalves+117:51
rkukura+117:51
arao012ok17:51
kanzhe+117:51
banix+117:51
SumitNaiksatamok cool17:52
SumitNaiksatammoving on17:52
SumitNaiksataminto specifics17:52
SumitNaiksatam#topic Neutron Advanced Services'  Common Framework gerrit spec17:52
*** openstack changes topic to "Neutron Advanced Services' Common Framework gerrit spec (Meeting topic: Networking Advanced Services)"17:52
SumitNaiksatamso this is just FYI, most of you already know17:52
SumitNaiksatam #link https://review.openstack.org/#/c/9220017:52
SumitNaiksatamwas approved during the last week17:52
SumitNaiksatami guess the a concrete development coming out of the summit :-)17:53
*** emagana has quit IRC17:53
SumitNaiksatam#topic: Neutron Flavor Framework17:53
*** openstack changes topic to ": Neutron Flavor Framework (Meeting topic: Networking Advanced Services)"17:53
*** sarob has joined #openstack-meeting-317:53
*** emagana has joined #openstack-meeting-317:53
SumitNaiksatam#link https://review.openstack.org/#/c/9007017:54
SumitNaiksatami dont think eugene is here17:54
SumitNaiksatamwe discussed this again at the summit17:54
SumitNaiksatami think the consensus was that most of what is currently in the spec is good17:54
SumitNaiksatamfor the tenant facing API17:54
SumitNaiksatameveryone agree?17:54
pcm_+117:55
SumitNaiksatamalthough there are a few -1s on the review (i think eugene will address those when gets off the road)17:55
SridarK+117:55
SridarKSumitNaiksatam: also we want to keep the scheduling of the backend fairly simple for the first pass17:55
SumitNaiksatamSridarK: yeah coming to that17:55
*** nati_uen_ has joined #openstack-meeting-317:56
*** nati_uen_ has quit IRC17:56
SumitNaiksatami was going to say that there was some objection on using the service type framework for the backend17:56
SumitNaiksatami did not quite understand what the push back was17:56
SridarKSome concern on this becoming too complex - perhaps for the right reasons but it will be good to phase out the implementation17:56
SumitNaiksatamSridarK: ok17:56
SridarKSumitNaiksatam: Yes - i think a lot of us were on the same page on that17:56
s3wongSumitNaiksatam: really? most of the complains I heard was how to properly standardize a basic set of tags?17:57
SumitNaiksatamSridarK: we already have the framework, and i guess people understand it17:57
SridarKSumitNaiksatam: yes i hope we can push for that17:57
SumitNaiksatams3wong: in the summit session i heard some differing opinion from mark mcclain on the provider side of things (in the context of STF)17:58
*** nati_uen_ has joined #openstack-meeting-317:58
SumitNaiksatamalthough that was the only differing opinion i heard17:58
*** amrith is now known as not-arborism17:58
SumitNaiksatamperhaps eugene can better explain next week17:58
s3wongsure17:58
SumitNaiksatammeanwhile, does everyone agree that this is highest priority?17:58
s3wongmark seems to support it for sure17:59
SumitNaiksatami mean flavors framework17:59
*** nati_ueno has quit IRC17:59
SumitNaiksatamif so, please comment on the review, so that we can move this forward17:59
*** not-arborism is now known as amrith17:59
pcm_+117:59
SumitNaiksatamwe need to start knocking off these gerrit specs18:00
s3wongSumitNaiksatam: yes, ServiceBase class has a field for flavor, so I hope to see it done soon also18:00
SumitNaiksatamas a team effort18:00
*** markmcclain has joined #openstack-meeting-318:00
SumitNaiksatamok next topic18:00
pgpusI see flavor being shared and similar should be available for instances of service ..shared - boolean - whether the flavor is visible to all tenants11618:00
pgpus18:00
SumitNaiksatampgpus: ok, perhaps you can add that comment to the review18:01
pgpusok will do18:01
SumitNaiksatampgpus: the issue with sharing is that, its difficult to nail down the semantics on the datapath18:01
SumitNaiksatampgpus: its probably different across services18:01
*** pballand has joined #openstack-meeting-318:02
SumitNaiksatampgpus: we faced this debate at the time we were introducing fwaas18:02
SumitNaiksatambut i agree that most vendors want to see some notion of this (opinios differ though on what they actually want)18:02
pgpusAgreed and that shared must be limited to with tenant data users and not to admin to see all what I mean and will look into that18:02
SumitNaiksatam#topic: Service base definition and Insertion18:02
*** openstack changes topic to ": Service base definition and Insertion (Meeting topic: Networking Advanced Services)"18:02
*** pballand has quit IRC18:02
SumitNaiksatam#link https://review.openstack.org/#/c/9312818:03
SumitNaiksatamkanzhe, s3wong: ?18:03
SumitNaiksatamquick summary of summit discussion?18:03
*** kenhui has joined #openstack-meeting-318:03
kanzheSumitNaiksatam: yes. The spec is up for review.18:03
s3wongWe presented it at the design summit, and there was no objection :-)18:03
SumitNaiksatamkanzhe s3wong: okay :-)18:04
banixs3wong: and not much nodding either :)18:04
kanzheAt the summit, I didn't hear any major objection.18:04
pgpusOK let me review and give feedback in next meeting for service insertion (if its still open for review)18:04
s3wongWe have also had a Neutron pod discussion - some guys from F5 were questioning on external port, but it was clarified18:04
SumitNaiksatams3wong: yes that was addressed, and we will be meeting rick again18:05
s3wongWe also had discussion with HP (DVR guys), FWaaS team, and ServiceVM subteam. There is some level of consensus here18:05
SumitNaiksatamthat said the external port is not the main thing in the proposal18:05
SumitNaiksatamso lets not get distracted by that18:05
s3wongso we are cautiously optimistic :-)18:05
SumitNaiksatams3wong: yes, good18:05
kanzheHow does everyone here feel about the proposal?18:05
kanzheNot much feedback on the spec yet.18:06
SumitNaiksatami had some questions earlier, which kanzhe, you seem to have answered, but i havent had a chance to circle back18:06
SridarKkanzhe: i think this is good - i am trying to fit this into our use case as well and will add comments to the review18:06
pgpusNot clear to me is it Blueprint review or Code review as I see some pathchens in it , may be I am new need to do some homework on this18:06
kanzheSumitNaiksatam: ok. SridarK : thx.18:07
cgoncalveskanzhe: sorry about that. I will review it this week18:07
SumitNaiksatampgpus: our specs are also now reviewed in gerrit18:07
s3wongpgpus: not code, just the definitions18:07
*** mandeep has quit IRC18:07
SumitNaiksatamok sometimes, no objection is passive agreement :-)18:07
kanzhecgoncalves: That would be great.18:07
pgpusOK I see Blueprint steps and will give feedback comments on it if Ok to dos o18:08
SumitNaiksatampgpus: thanks18:08
*** coolsvap is now known as coolsvap|afk18:08
SumitNaiksatamnext topic18:08
SumitNaiksatam#topic traffic steering18:08
*** openstack changes topic to "traffic steering (Meeting topic: Networking Advanced Services)"18:08
cgoncalves\o/18:08
SumitNaiksatam#link https://review.openstack.org/#/c/9247718:08
SumitNaiksatamcgoncalves: normally i would have asked you to give an update, but i guess we owe you an update as well :-)18:09
SumitNaiksatamcgoncalves: since you were not able to make it to the summit18:09
*** rgbkrk_ has quit IRC18:09
SumitNaiksatamanyone wants to summarize the disccusion we had in the neutron pod on this?18:09
cgoncalvesSumitNaiksatam: ah! maybe you've already summed it up yesterday?18:09
SumitNaiksatamcgoncalves: yes i did, but i want others to provide their opinion as well18:10
cgoncalvesSumitNaiksatam: sure, I would really appreciate that18:10
s3wongSumitNaiksatam: cgoncalves: so the summary conclusion is that community is asking if traffic steering and service chaining should be the same thing18:10
pgpusYou mean on traffic ssteering absraction?18:10
cgoncalvess3wong: traffic steering would accomplish the same use case as service chaining at the end18:11
jmsoaress3wong: not the same thing I guess, one is an enabler of the other.18:11
cgoncalvess3wong: service chaining is focused on neutron adv services whereas traffic steering on port chaining18:11
s3wongi.e., traffic steering as it is defined in the bp today seems to be a special case of service chaining (I am just reflecting on what the community came about :-) )18:12
pgpusOK i subscribed to it and will reveiw the traffic steering too18:12
s3wongcgoncalves: jmsoares: you guys may want to clarify the differences, or see if the spec can combine with service chaining one18:13
pgpusSo this week I should have my hands full with reviewing atleast 3 of 4 topivcs18:13
jmsoaress3wong: right. I guess that we started the BP with the "service chaining" in mind and as an ultimate goal. With time it evolved to be something more generic and, let's say, low level18:13
cgoncalvess3wong: the traffic steering BP was originally created to propose a different approach from the at the time original service chaining where you would create chains based on services and thus only supporting the existing services18:13
cgoncalvespgpus: thanks18:14
s3wongcgoncalves: jmsoares: I know :-) but we need further clarification for community to see it as such18:14
cgoncalvess3wong: ah, gotcha18:14
SumitNaiksatamcgoncalves jmsoares: to extend what s3wong  was saying, people were asking if we can create the notion of a “generic services” wrapper that can be used in teh service chain18:14
jmsoaress3wong: agree :) the spec needs to reflect that and currently is not that clear18:14
pgpusTraffic steering needs to be dynamic as flow maps change so not sure if we can mix it up with service shaning which may be static18:15
SumitNaiksatamsuch that traffic steering need not have to be directly exposed to the user18:15
SumitNaiksatamin general people dont want to see two different ways of achieving service chains18:15
*** lcheng_ has quit IRC18:16
SumitNaiksatamlet me rephrase, two different ways of exposing service chains to the user18:16
SumitNaiksatamand they prefer the higher level abstraction18:16
SumitNaiksatamthis does not change a whole lot in terms of what we are already saying, or is in the spec18:17
jmsoaresSumitNaiksatam: how high level is that abstraction?18:17
pgpusNot sure as service policy may require the srveice to be veiwed in different way, however abstractions must hide it, so may be we are same page18:17
SumitNaiksatamjmsoares: something similar to what is being discussed in: https://review.openstack.org/#/c/9352418:17
SumitNaiksatamhowever, that said, the general abstraction would need to capture the case where the service is on a VM, and neutron does not expose that service abstraction18:18
SumitNaiksatamso for now, lets focus in the review that has been submitted for this18:19
SumitNaiksatami guess its a matter of considering whether the port chain API is tenant facing or just admin18:19
cgoncalvesSumitNaiksatam: ok, but that would be just a matter of whether exposing an API or not right? if so, we can create the core base and propose a user API too. either the API would be accepted or not that would be a thing not to worry much about18:20
pgpusAre this related to ServiceVM which is a sepoerate BP?18:20
SumitNaiksatamcgoncalves: yeah, i think we said the same thing :-)18:20
SumitNaiksatampgpus: Service VM is a whole beast in itself18:20
SumitNaiksatampgpus:  we will leverage that18:20
*** Louis__ has joined #openstack-meeting-318:21
cgoncalvesSumitNaiksatam: yes :-)18:21
SumitNaiksatampgpus: and most likely drive some requirements from this discussion18:21
jmsoaresSumitNaiksatam: How would we in the high level abstraction perform a chaining sequence dependent on the type of traffic?18:21
pgpusOK I see, so let me just stick to the 4 topics and put my comments on them before next meeting to catchup with group18:21
SumitNaiksatams3wong has been attending teh service VM meetings, and will try to sync up, others can participate as well18:21
jmsoaresSumitNaiksatam: maybe is not how, but whether if it would be possible18:22
s3wongSumitNaiksatam: sure - the next meeting will resume on June 2nd, for anyone interested18:22
SumitNaiksatamjmsoares: good question, but the expectation is that there is some context to the chain18:22
SumitNaiksatamjmsoares: which will allow specifying the traffic classification (internally, not necessarily exposed to the user)18:22
pgpusYou mean Monday June2 or or Wed june 4?18:23
SumitNaiksatamok since we are running low on time (as usual)18:23
s3wongpgpus: ServiceVM meetings is on Tues 5:00 UTC18:23
s3wongso June 1st (sorry)18:23
SumitNaiksatami will skip the service chainig blueprint, since i saw mandeep drop off, but will try to get an update from him18:23
jmsoaresSumitNaiksatam: but if that's done internally, Neutron must known "why" the chain is there18:24
SumitNaiksatam#topic Tap as a Service spec18:24
pgpusSumit - thanks for all your info18:24
*** openstack changes topic to "Tap as a Service spec (Meeting topic: Networking Advanced Services)"18:24
SumitNaiksatamjmsoares: lets continue discussion offline (sorry :-))18:24
SumitNaiksatamvinay_yadhav: quick summary?18:24
jmsoaresSumitNaiksatam: sure, no prob :)18:24
vinay_yadhavi have mailed the initial version of the spec on the mailing list18:25
s3wongvinay_yahav: you have five minutes :-)18:25
SumitNaiksatamvinay_yadhav: is this in gerrit?18:25
vinay_yadhavthe blueprint intended to make it an extension, but in the spec we propose it as a service18:25
SumitNaiksatamvinay_yadhav: ok18:25
vinay_yadhavas per the discussion we had in the summit18:25
vinay_yadhavsumit: not yet18:25
vinay_yadhavi will put it in tomorrow18:25
*** emagana has quit IRC18:26
SumitNaiksatamvinay_yadhav: ok, great18:26
vinay_yadhavor tonight18:26
s3wongvinay_yadhav: you may want to put it on gerrit - and forget about the initial bp, it is irrelevant now since it was never on gerrit18:26
SumitNaiksatamand perhaps you can add to the table so that we can track18:26
SumitNaiksatamvinay_yadhav: thanks for the update18:26
vinay_yadhavs3wong: ok sure18:26
SumitNaiksatam#topic NFV discussions18:26
*** openstack changes topic to "NFV discussions (Meeting topic: Networking Advanced Services)"18:26
SumitNaiksatamthis subteam has started work18:27
SumitNaiksatamand there are points of intersection with what we are trying to achieve here18:27
SumitNaiksatamso we need to collaborate18:27
s3wongNFV meeting will be every Wed starting June 2nd at 1700 UTC, I believe18:27
SumitNaiksatami believe mestery will be participating in those meetings18:27
SumitNaiksatams3wong: yes18:27
mesterySumitNaiksatam: Yes, it's on my calendar and I plan to attend.18:28
s3wongor June 4th (again, what's up with my June 2nd typo)...18:28
banixday/time may change after the first meeting18:28
SumitNaiksatammestery: thanks18:28
SumitNaiksatam#link https://wiki.openstack.org/wiki/Meetings/NFV18:28
s3wong1400 UTC18:28
SumitNaiksatamsee above ^^^ for details18:28
SumitNaiksatamand #link https://etherpad.openstack.org/p/juno-nfv-bof for summit discussion recap18:29
*** ttrifonov_zZzz is now known as ttrifonov18:29
SumitNaiksatam#topic Open Discussion18:29
*** openstack changes topic to "Open Discussion (Meeting topic: Networking Advanced Services)"18:29
s3wonggot it wrong, because I remember it is 7am PDT, sorry guys18:29
*** nati_uen_ has quit IRC18:29
SumitNaiksatamanyone wants to bring up anything that we did not cover?18:29
SumitNaiksatamit was great meeting everyone at Atlanta18:29
SumitNaiksatamhope everyone had a pleasant flight back18:30
*** Cathy_ has joined #openstack-meeting-318:30
pgpusno thanks18:30
SumitNaiksatamlooks like we will actually wrap on time today!18:30
SumitNaiksatamthats a first18:30
s3wongright on time!18:30
SumitNaiksatamnot make the fwaas folks wait for a change18:31
SumitNaiksatamalright thanks everyone18:31
SumitNaiksatamuntil next week18:31
SumitNaiksatam#endmeeting18:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:31
cgoncalvesthanks. cya!18:31
openstackMeeting ended Wed May 21 18:31:15 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-05-21-17.31.html18:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-05-21-17.31.txt18:31
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-05-21-17.31.log.html18:31
vinay_yadhavthanx bye18:31
arao012Bye18:31
*** arao012 has quit IRC18:31
s3wongthanks! bye18:31
*** lcheng_ has joined #openstack-meeting-318:31
rkukurabye18:31
pgpusthanks bye18:31
kanzhelater18:31
*** rkukura has left #openstack-meeting-318:31
*** kanzhe has quit IRC18:31
SumitNaiksatamSridarK gduan beyounn_1: there?18:32
SridarKHi SumitNaiksatam18:32
beyounn_1yo18:32
*** Louis___ has joined #openstack-meeting-318:32
SridarKHi All18:32
SumitNaiksatamok great, lets get started18:32
beyounn_1I'm here18:32
*** Louis__ has quit IRC18:32
SumitNaiksatamwe can wrap up early if we dont need the entire hour18:32
SumitNaiksatam#startmeeting Networking FWaaS18:32
openstackMeeting started Wed May 21 18:32:56 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:32
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:32
*** openstack changes topic to " (Meeting topic: Networking FWaaS)"18:33
openstackThe meeting name has been set to 'networking_fwaas'18:33
SumitNaiksatam#topic bugs18:33
*** openstack changes topic to "bugs (Meeting topic: Networking FWaaS)"18:33
*** regXboi has left #openstack-meeting-318:33
SumitNaiksatam#link https://bugs.launchpad.net/neutron/+bug/131431318:34
SumitNaiksatamSridarK: you are working on this18:34
SridarKSumitNaiksatam: yes - a bit slow this week18:34
SridarKi think we may have a corner case timing issue18:34
SumitNaiksatamSridarK: thanks for your effort18:34
*** nati_ueno has joined #openstack-meeting-318:35
SumitNaiksatamSridarK: ok18:35
SridarKSumitNaiksatam: no worries  - will keep u posted on this18:35
SumitNaiksatamSridarK: per salvatore’s comments, i am glad that this is not hitting the gate as much now18:35
SridarKi need to drive the workflow programattically to see if i can reproduce18:35
SumitNaiksatamSridarK: but lets try to wrap this up, if its outside our control, we can create a different bug for the router18:35
SridarKSumitNaiksatam: sounds good18:35
SumitNaiksatam#link https://bugs.launchpad.net/neutron/+bug/132077518:36
SumitNaiksatamnot sure if Rajesh is here18:36
rand738Hi Sumit18:37
SumitNaiksatamit was great that he got the fix in quickly: #link https://review.openstack.org/#/c/94516/18:37
SumitNaiksatamrand738: hi18:37
*** rand738 has quit IRC18:37
SridarKSumitNaiksatam: I went thru the review - just need to validate on the deferred being turned off18:37
SumitNaiksatamRajesh’s fix looks good, but i just wanted to check if we can add a UT, so that we catch this18:37
*** Zzeedd has quit IRC18:38
SridarKi will also post a review on this18:38
SumitNaiksatamSridarK: nice!18:38
SumitNaiksatam#link https://bugs.launchpad.net/neutron/+bug/131085718:39
SumitNaiksatamlooks like the author needs to address some comments18:40
SumitNaiksatamhowever this is high, may be we need to follow up with him18:40
SridarKYes - i was not sure on the approach of getting the FWaaS Plugin on the agent18:41
SumitNaiksatam#link https://bugs.launchpad.net/neutron/+bug/131861718:41
*** Youcef_ has joined #openstack-meeting-318:41
*** ttrifonov is now known as ttrifonov_zZzz18:41
SumitNaiksatamhavent investigated this18:42
SumitNaiksatambut its currently low18:42
SumitNaiksatamif anyone wants to take it18:42
SridarKHmm this is odd18:42
*** jmsoares has left #openstack-meeting-318:42
*** ttrifonov_zZzz is now known as ttrifonov18:42
SridarKfairly easy recreate - let me try a recreate and post comments on the bug18:43
SumitNaiksatamSridarK: nice18:43
*** vinay_yadhav has quit IRC18:43
SumitNaiksatam#topic Juno planning and feature tracking18:44
*** openstack changes topic to "Juno planning and feature tracking (Meeting topic: Networking FWaaS)"18:44
SumitNaiksatamso my proposal is that we start tracking things in this meeting18:44
SumitNaiksatam#link https://wiki.openstack.org/wiki/Neutron/FWaaS/JunoPlan18:44
*** Rm_mobile has joined #openstack-meeting-318:44
*** Munish has joined #openstack-meeting-318:44
SridarKSumitNaiksatam: +118:44
beyounn_1+118:45
SumitNaiksatamok cool18:45
SumitNaiksatami volunteered your names for a lot of things :-P18:45
SumitNaiksatamthese are placeholders18:45
SridarKSumitNaiksatam: thats good18:45
beyounn_1+118:45
SumitNaiksatamothers can jump in18:45
SumitNaiksatambut we need to be cognizant of the fact that these aspects need to be covered for every feature18:46
SumitNaiksatami havent checked if there are any tempest related pending blueprints, we would need to add those here18:46
*** natarajk has quit IRC18:46
SridarKSumitNaiksatam: spoke to mlavalle as well18:46
SumitNaiksatamso we are in general agreement with the process of tracking here?18:46
SumitNaiksatamSridarK: great18:46
SridarKhe will be adding something for tempest scenario18:47
SridarKyes in agreement18:47
SumitNaiksatamok18:47
*** Youcef_ is now known as Youcef18:47
SumitNaiksatam#topic proposed features’ and blueprints18:48
*** openstack changes topic to "proposed features’ and blueprints (Meeting topic: Networking FWaaS)"18:48
SumitNaiksatamrather than going into each blueprint today, i suggest that we just have a general discussion18:49
SridarKSumitNaiksatam: yes that is better18:49
SumitNaiksatamis there any feedback that you folks got after our session18:49
SumitNaiksatam?18:49
SumitNaiksatami had to leave to catch the flight18:49
beyounn_1other than dvr, no much from me18:49
SridarKSumitNaiksatam: i thought it was well recvd - had a few folks come and talk after and looks like we are on track with our priorities18:50
SumitNaiksatambeyounn_1: ok, again great that you brought it up18:50
SumitNaiksatamSridarK: nice18:50
SumitNaiksatambeyounn_1: suggestion - to get the DVR issue on record, can you send out an email to the mailing list?18:50
beyounn_1I put it in the DVR ether pad already18:50
beyounn_1and had an discussion with DVR forks this morning18:51
*** Rm_mobile has quit IRC18:51
beyounn_1i will keep update based on the discussion18:51
SumitNaiksatambeyounn_1: cool, but people might forget the etherpad (and its not searchable via google)18:51
*** ttrifonov is now known as ttrifonov_zZzz18:51
beyounn_1Yes, let me collect all the feedbacks and thoughts then send an email18:51
SumitNaiksatambeyounn_1:  i would just say that you can copy paste your input in the etherpad and send to the dev mailer18:51
*** ttrifonov_zZzz is now known as ttrifonov18:51
SumitNaiksatambeyounn_1: thanks18:51
beyounn_1Sure18:51
SumitNaiksatambeyounn_1: is there any solution apparent?18:52
beyounn_1yes18:52
beyounn_1That is what I want to talking about18:52
beyounn_1Do we have time now?18:52
beyounn_1I you prefer that I send an private email among all of us ?18:53
SumitNaiksatambeyounn_1: sure18:53
SumitNaiksatambeyounn_1: may be quick update, so that others who read these logs know what is going on18:53
beyounn_1Since the br-int knows whether a packet has be routed or switched, so we can add something in the br-int to force the traffic to fw before the traffic hits on the DVR18:54
beyounn_1I got two questions that is working on, 1 if we are not on router, then we don't don't have zone but just can use address book18:54
beyounn_1even if we are using address book, how can we get the namespace info is something I'm still not clear18:55
beyounn_1And I took action item to dicuss these with FWaaS team18:55
beyounn_1Ok, this is the summary for this morning's meeting18:55
*** jcoufal has quit IRC18:56
beyounn_1shot, bad bad typing18:56
*** jcoufal has joined #openstack-meeting-318:56
beyounn_1can you guys understand what I have typed ? :-)18:57
*** shakamunyi has quit IRC18:57
SridarKbeyounn_1: ;-)18:57
*** jamielenz has joined #openstack-meeting-318:57
SumitNaiksatami am trying to :-P18:57
SridarKbeyounn_1: perhaps more offline discussion18:57
beyounn_1Ok, let's me send out email :-)18:57
beyounn_1sorry, for the typing...18:57
beyounn_1in a meeting ... :-)18:57
SumitNaiksatambeyounn_1: i did not get the address book part, but that might just be terminology18:58
beyounn_1think about subnets18:58
SumitNaiksatambeyounn_1: ok, sorry to put you on the spot18:58
SumitNaiksatambeyounn_1:  you can follow up in your email18:58
beyounn_1SumitNaiksatam: not at all18:58
beyounn_1I will send email later today18:59
SumitNaiksatamSridarK gduan: any other feedback you received?19:00
*** jamielennox|away has quit IRC19:00
*** ttrifonov is now known as ttrifonov_zZzz19:00
SridarKSumitNaiksatam: had some discussion on Zones with some folks - mostly other vendors19:00
*** jamielennox|away has joined #openstack-meeting-319:00
SumitNaiksatamSridarK:  ok good, do agree with the idea?19:00
*** ttrifonov_zZzz is now known as ttrifonov19:01
SumitNaiksatam*do they19:01
SridarKSumitNaiksatam: yes we are aligned19:01
SumitNaiksatamSridarK: ok good19:01
*** jamielenz has quit IRC19:02
SumitNaiksatamgduan: any discussions on the flavors?19:02
gduanHi19:03
gduanMark commented on the spec review and asked to added detail19:04
gduanDid Eugene put on his spec?19:04
*** nati_ueno has quit IRC19:04
SumitNaiksatamgduan: eugene is on the road19:05
SumitNaiksatamgduan: so he has not updated his spec19:05
SumitNaiksatamgduan: i think he is going to be on the road at least for a week19:05
*** nati_ueno has joined #openstack-meeting-319:05
beyounn_1Gary is on customer call now19:06
SumitNaiksatamonce eugene gets back, lets have a focussed meeting with the reviewers and hash out the details once and for all19:06
SumitNaiksatambeyounn_1: sure np19:06
SumitNaiksatamSridarK: is pradeep around?19:06
SridarKSumitNaiksatam: Hmm i am not sure19:06
SumitNaiksatamI would like to understand if he has everything he needs to get started for the hit count bp19:07
*** kenhui has quit IRC19:07
SridarKBased on conversations in the Summit he is good to get started19:07
SumitNaiksatamfor starters he needs to file a gerrit spec so that we are all aligned in terms of what we want to do19:07
SridarKon the other stuff19:07
SumitNaiksatamSridarK: good19:07
SridarK not hit count19:07
SumitNaiksatamSridarK: ah ok19:07
*** kenhui has joined #openstack-meeting-319:07
SumitNaiksatamSridarK: perhaps he can join next meeting?19:07
SridarKSumitNaiksatam: i think their priority is to get the basic usage stats down19:08
SridarKSumitNaiksatam: i will remind him19:08
SumitNaiksatamSridarK: that sounds like a good start19:08
SridarKSumitNaiksatam: as they have nothing right now and this was echoed in their  Design session as well19:08
SumitNaiksatamSridarK: good19:08
SumitNaiksatam#topic  Vendor blueprints19:10
*** openstack changes topic to "Vendor blueprints (Meeting topic: Networking FWaaS)"19:10
SumitNaiksatamis Karthik here?19:10
SumitNaiksatamok hopefully he will join next week as well19:10
SumitNaiksatamso can you all add the vendor blueprints as topics on the table as well?19:11
SridarKSumitNaiksatam: yes will do19:11
SumitNaiksatamSridarK: thanks19:11
beyounn_1Ok19:11
SumitNaiksatamthings that we dont add to the table will fall off the radar and most likely not make it19:12
SumitNaiksatambeyounn_1:  thanks19:12
SumitNaiksatam#open discussion19:12
SumitNaiksatam#topic open discussion19:12
*** openstack changes topic to "open discussion (Meeting topic: Networking FWaaS)"19:12
beyounn_1Sumit, how to get the bp spec approved?19:12
SumitNaiksatambeyounn_1:  :-)19:13
SumitNaiksatambeyounn_1:  you mean the service objects?19:13
beyounn_1Yes19:13
SridarKbeyounn_1: i added some comments to ur review19:13
beyounn_1Saw it19:13
beyounn_1I will updated19:13
beyounn_1s/updated/update/19:13
SumitNaiksatambeyounn_1: our best chance is as a team19:13
*** nati_ueno has quit IRC19:13
*** sarob has quit IRC19:13
SridarKbeyounn_1: we can do the internal reviews and get the +1 first to push for cores as Sumit mentioned in the prev mtg19:14
SumitNaiksatambeyounn_1: i mean we all review each other’s blueprints and provide enough information for cores to act on this19:14
SumitNaiksatamyeah like SridarK said19:14
beyounn_1Ok, let's clean up my spec ASAP19:14
SridarKSumitNaiksatam: which was really like u said :-)19:14
beyounn_1s/let's/let me/19:14
SumitNaiksatambeyounn_1: any chance that you can get your potential “users” to look at this as well?19:14
SumitNaiksatamSridarK: :-)19:14
SumitNaiksatammy comment is in general19:14
beyounn_1SumitNaiksatam: don't think so19:15
SumitNaiksatami would strongly suggest that we involve potential users in this, and let them drive the requirements19:15
SumitNaiksatambeyounn_1: ah, ok19:15
beyounn_1SumitNaiksatam: but I will try, harmless anyway19:15
SumitNaiksatamit becomes much easier to prioritize when its requirements driven19:15
SumitNaiksatambeyounn_1: i think its critical19:16
beyounn_1SumitNaiksatam: agreed19:16
SridarKSumitNaiksatam: also perhaps some folks filing bugs now are potential users19:16
SumitNaiksatamSridarK: yes, reach out to them :-)19:16
SridarKyes will do19:17
SumitNaiksatamin general, the more people we get to do meaningful reviews, the better our chances19:17
*** lblanchard has quit IRC19:17
SumitNaiksatamit was mentioned during the summit discussions that meaningful +1s also carry a lot of weight19:17
*** lblanchard has joined #openstack-meeting-319:17
SumitNaiksatamok what else?19:18
beyounn_1I'm good19:18
SridarKSumitNaiksatam: thats all from me as well19:18
SumitNaiksatamgreat, thanks eveyrone, it was great meeting you in Atlanta19:18
*** ttrifonov is now known as ttrifonov_zZzz19:18
SumitNaiksatamonward to Juno! ;-)19:18
beyounn_1:-)19:18
SridarKyes sam here19:18
SumitNaiksatamsee you next week, bye19:18
SridarKsame19:18
SridarKbye19:18
SumitNaiksatam#endmeeting19:19
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:19
openstackMeeting ended Wed May 21 19:19:01 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:19
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-05-21-18.32.html19:19
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-05-21-18.32.txt19:19
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-05-21-18.32.log.html19:19
*** pcm_ has left #openstack-meeting-319:19
*** kenhui has quit IRC19:20
*** kenhui has joined #openstack-meeting-319:22
*** Munish has quit IRC19:25
*** eguz has quit IRC19:47
*** eghobo has joined #openstack-meeting-319:47
*** kenhui has quit IRC19:48
*** Sukhdev has joined #openstack-meeting-319:51
*** pgpus has quit IRC19:52
*** lsmola2 has joined #openstack-meeting-320:01
*** s3wong has quit IRC20:01
*** s3wong has joined #openstack-meeting-320:01
*** Cathy_ has quit IRC20:04
*** thomasem has quit IRC20:06
*** devlaps has quit IRC20:06
*** devlaps has joined #openstack-meeting-320:15
*** jrist_ has joined #openstack-meeting-320:19
*** jrist has quit IRC20:21
*** jrist_ is now known as jrist20:21
*** thomasem has joined #openstack-meeting-320:52
*** SumitNaiksatam has quit IRC20:52
*** chuckC has quit IRC20:57
*** lblanchard has quit IRC21:04
*** sarob has joined #openstack-meeting-321:07
*** otherwiseguy has quit IRC21:07
*** otherwiseguy has joined #openstack-meeting-321:10
*** nati_ueno has joined #openstack-meeting-321:13
*** peristeri has quit IRC21:14
*** lsmola2 has quit IRC21:15
*** mfer has quit IRC21:18
*** krotscheck has quit IRC21:19
*** krotscheck has joined #openstack-meeting-321:20
*** jcoufal has quit IRC21:21
*** nati_ueno has quit IRC21:26
*** nati_ueno has joined #openstack-meeting-321:26
*** chuckC has joined #openstack-meeting-321:28
*** julim has quit IRC21:32
*** jamie_h has quit IRC21:42
*** kenhui has joined #openstack-meeting-321:44
*** rgbkrk has joined #openstack-meeting-321:44
*** SumitNaiksatam has joined #openstack-meeting-321:47
*** mwagner_lap has quit IRC21:47
*** pgpus has joined #openstack-meeting-321:48
*** SumitNaiksatam has quit IRC21:49
*** Sukhdev has quit IRC21:51
*** SumitNaiksatam has joined #openstack-meeting-322:12
*** SumitNaiksatam has quit IRC22:12
*** yamahata has joined #openstack-meeting-322:19
*** sarob has quit IRC22:20
*** sarob has joined #openstack-meeting-322:21
*** devlaps has quit IRC22:21
*** devlaps has joined #openstack-meeting-322:22
*** sarob_ has joined #openstack-meeting-322:22
*** markmcclain has quit IRC22:22
*** markmcclain has joined #openstack-meeting-322:23
*** sarob has quit IRC22:25
*** pgpus has quit IRC22:25
*** sarob_ has quit IRC22:26
*** troytoman has joined #openstack-meeting-322:28
*** chuckC has quit IRC22:29
*** Adri2000_ has joined #openstack-meeting-322:31
*** Adri2000_ has joined #openstack-meeting-322:31
*** cgoncalv1s has joined #openstack-meeting-322:31
*** SumitNaiksatam has joined #openstack-meeting-322:32
*** ttrifonov_zZzz has quit IRC22:33
*** Youcef_ has joined #openstack-meeting-322:33
*** notmyname_ has joined #openstack-meeting-322:33
*** rgbkrk has quit IRC22:33
*** troytoman_ has quit IRC22:33
*** notmyname has quit IRC22:33
*** notmyname_ is now known as notmyname22:34
*** rgbkrk has joined #openstack-meeting-322:36
*** ttrifonov_zZzz has joined #openstack-meeting-322:36
*** dansmith_ has joined #openstack-meeting-322:37
*** Adri2000 has quit IRC22:38
*** anteaya has quit IRC22:38
*** cgoncalves has quit IRC22:38
*** Youcef has quit IRC22:38
*** dansmith has quit IRC22:38
*** dansmith_ is now known as dansmith22:38
*** kenhui has quit IRC22:40
*** pgpus has joined #openstack-meeting-322:41
*** jamielennox|away is now known as jamielennox22:43
*** s3wong_ has joined #openstack-meeting-322:45
*** mike-grima1 has joined #openstack-meeting-322:45
mike-grima1Hello, is the FWaaS meeting today?22:46
s3wong_mike-grima1: yes, but about 4 hours ago22:46
mike-grima1ooh. that website that shows the time said it was at 6:3022:48
mike-grima1only i'm EST, so it's 2:3022:48
*** Louis___ has quit IRC22:48
*** krotscheck has quit IRC22:49
*** nelsnelson has quit IRC22:49
*** mike-grima1 has left #openstack-meeting-322:50
s3wong_mike-grima1: I think it is 18:30 UTC, which is 11:30 PDT, or 14:30 EDT22:50
s3wong_mike-grima1: all OpenStack meeting time posted are in UTC - so it isn't affected by daylight saving time22:51
*** otherwiseguy has quit IRC22:53
*** pgpus has quit IRC22:54
*** rgbkrk has quit IRC22:54
*** s3wong has quit IRC22:54
*** s3wong_ is now known as s3wong22:55
*** krotscheck has joined #openstack-meeting-322:56
*** anteaya has joined #openstack-meeting-322:56
*** rgbkrk has joined #openstack-meeting-322:57
*** eguz has joined #openstack-meeting-322:59
*** eguz has quit IRC22:59
*** otherwiseguy has joined #openstack-meeting-323:00
*** banix has quit IRC23:01
*** ttrifonov_zZzz is now known as ttrifonov23:01
*** ttrifonov is now known as ttrifonov_zZzz23:02
*** eghobo has quit IRC23:02
*** ttrifonov_zZzz is now known as ttrifonov23:03
*** thomasem has quit IRC23:09
*** nelsnelson has joined #openstack-meeting-323:13
*** mwagner_lap has joined #openstack-meeting-323:14
*** ttrifonov is now known as ttrifonov_zZzz23:15
*** s3wong has quit IRC23:16
*** terryw has joined #openstack-meeting-323:18
*** ttrifonov_zZzz is now known as ttrifonov23:19
*** otherwiseguy has quit IRC23:21
*** chuckC has joined #openstack-meeting-323:23
*** terryw has quit IRC23:25
*** david-lyle has quit IRC23:26
*** yamahata has quit IRC23:29
*** ttrifonov is now known as ttrifonov_zZzz23:29
*** ttrifonov_zZzz is now known as ttrifonov23:29
*** nati_ueno has quit IRC23:30
*** ttrifonov is now known as ttrifonov_zZzz23:31
*** ttrifonov_zZzz is now known as ttrifonov23:31
*** nati_ueno has joined #openstack-meeting-323:50
*** chuckC has quit IRC23:52

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