Wednesday, 2014-06-04

*** devlaps has quit IRC00:00
*** devlaps1 has quit IRC00:00
*** carl_baldwin has joined #openstack-meeting-300:01
*** kenhui has joined #openstack-meeting-300:03
*** yamahata has joined #openstack-meeting-300:03
*** cjellick_ has joined #openstack-meeting-300:07
*** hurgleburgler has quit IRC00:08
*** hurgleburgler has joined #openstack-meeting-300:10
*** cjellick has quit IRC00:10
*** cjellick_ has quit IRC00:12
*** kenhui has quit IRC00:13
*** kenhui has joined #openstack-meeting-300:14
*** sarob has quit IRC00:16
*** sarob_ has joined #openstack-meeting-300:16
*** kenhui1 has joined #openstack-meeting-300:16
*** carl_baldwin has quit IRC00:17
*** kenhui1 has quit IRC00:17
*** kenhui has quit IRC00:20
*** lcheng_ has quit IRC00:22
*** nati_uen_ has quit IRC00:32
*** nati_ueno has joined #openstack-meeting-300:33
*** sarob_ has quit IRC00:33
*** lcheng_ has joined #openstack-meeting-300:35
*** nati_ueno has quit IRC00:38
*** nati_ueno has joined #openstack-meeting-300:39
*** lcheng_ has quit IRC00:45
*** kevinbenton has joined #openstack-meeting-300:45
*** nati_ueno has quit IRC00:47
*** nati_ueno has joined #openstack-meeting-300:48
*** SumitNaiksatam has quit IRC00:53
*** yamahata has quit IRC00:53
*** yamahata has joined #openstack-meeting-300:54
*** maurosr has quit IRC01:00
*** maurosr has joined #openstack-meeting-301:02
*** nati_uen_ has joined #openstack-meeting-301:18
*** msundara has joined #openstack-meeting-301:19
*** tomoe_ has quit IRC01:19
*** banix has joined #openstack-meeting-301:21
*** nati_ueno has quit IRC01:22
*** emagana has joined #openstack-meeting-301:23
*** otherwiseguy has joined #openstack-meeting-301:24
*** msundara has quit IRC01:24
*** clu_ has quit IRC01:33
*** nati_uen_ has quit IRC01:39
*** nati_ueno has joined #openstack-meeting-301:39
*** amotoki has quit IRC01:40
*** hurgleburgler has quit IRC01:41
*** otherwiseguy has quit IRC01:50
*** otherwiseguy has joined #openstack-meeting-301:52
*** tomoe_ has joined #openstack-meeting-302:00
*** jackib has joined #openstack-meeting-302:07
*** jackib has quit IRC02:08
*** devlaps2 has quit IRC02:11
*** kenhui has joined #openstack-meeting-302:15
*** emagana has quit IRC02:20
*** emagana has joined #openstack-meeting-302:20
*** kenhui has quit IRC02:28
*** tomoe_ has quit IRC03:19
*** vkmc has quit IRC03:23
*** tomoe_ has joined #openstack-meeting-303:23
*** banix has quit IRC03:25
*** msundara has joined #openstack-meeting-303:28
*** ericpeterson has joined #openstack-meeting-303:38
*** ericpeterson has quit IRC03:39
*** otherwiseguy has quit IRC03:42
*** banix has joined #openstack-meeting-303:44
*** otherwiseguy has joined #openstack-meeting-303:52
*** banix has quit IRC03:53
*** amotoki has joined #openstack-meeting-303:58
*** beyounn has joined #openstack-meeting-304:01
*** lcheng_ has joined #openstack-meeting-304:08
*** yamamoto_ has joined #openstack-meeting-304:11
*** lcheng_ has quit IRC04:27
*** emagana has quit IRC04:27
*** emagana has joined #openstack-meeting-304:30
*** emagana has quit IRC04:33
*** nelsnelson has quit IRC04:35
*** lcheng_ has joined #openstack-meeting-304:36
*** amotoki has quit IRC04:39
*** yamamoto_ has quit IRC04:44
*** yamamoto_ has joined #openstack-meeting-304:44
*** lcheng_ has quit IRC04:52
*** nati_ueno has quit IRC04:55
*** sarob has joined #openstack-meeting-304:56
*** nati_uen_ has joined #openstack-meeting-304:57
*** nati_uen_ has quit IRC04:57
*** otherwiseguy has quit IRC05:02
*** shakamunyi has joined #openstack-meeting-305:04
*** lcheng_ has joined #openstack-meeting-305:05
*** emagana has joined #openstack-meeting-305:28
*** coolsvap|afk is now known as coolsvap05:30
*** jtomasek has joined #openstack-meeting-305:30
*** jtomasek has quit IRC05:38
*** alexpilotti has joined #openstack-meeting-305:39
*** sarob has quit IRC05:46
*** sarob has joined #openstack-meeting-305:46
*** sarob has quit IRC05:50
*** coolsvap is now known as coolsvap|afk05:52
*** alexpilotti has quit IRC05:54
*** coolsvap|afk is now known as coolsvap05:58
*** alexpilotti has joined #openstack-meeting-306:01
*** jtomasek has joined #openstack-meeting-306:03
*** sarob has joined #openstack-meeting-306:08
*** nati_ueno has joined #openstack-meeting-306:10
*** sarob has quit IRC06:12
*** sarob has joined #openstack-meeting-306:17
*** tmazur has joined #openstack-meeting-306:17
*** sarob_ has joined #openstack-meeting-306:19
*** sarob has quit IRC06:21
*** sarob_ has quit IRC06:24
*** beyounn has quit IRC06:26
*** beyounn has joined #openstack-meeting-306:27
*** nati_ueno has quit IRC06:28
*** coolsvap is now known as coolsvap|afk06:31
*** jamie_h has joined #openstack-meeting-306:33
*** msundara has quit IRC06:34
*** lsmola has quit IRC06:40
*** bauzas has joined #openstack-meeting-306:43
*** beyounn has quit IRC06:45
*** coolsvap|afk is now known as coolsvap06:47
*** alexpilotti has quit IRC06:59
*** mrunge has joined #openstack-meeting-307:02
*** eghobo has joined #openstack-meeting-307:08
*** aloga has quit IRC07:09
*** ttrifonov_zZzz is now known as ttrifonov07:16
*** emagana has quit IRC07:16
*** sarob has joined #openstack-meeting-307:19
*** coolsvap is now known as coolsvap|afk07:21
*** sarob has quit IRC07:23
*** eghobo has quit IRC07:24
*** coolsvap|afk is now known as coolsvap07:29
*** lcheng_ has quit IRC07:45
*** lcheng_ has joined #openstack-meeting-307:53
*** nacim has quit IRC07:58
*** nacim has joined #openstack-meeting-307:58
*** MaxV has joined #openstack-meeting-307:59
*** lcheng_ has quit IRC08:05
*** nacim has quit IRC08:07
*** nacim has joined #openstack-meeting-308:09
*** shakamunyi has quit IRC08:10
*** sarob has joined #openstack-meeting-308:17
*** sarob has quit IRC08:21
*** safchain has joined #openstack-meeting-308:31
*** igordcard has joined #openstack-meeting-308:37
*** markmcclain has joined #openstack-meeting-308:40
*** mrunge has quit IRC08:48
*** jamie_h has quit IRC08:48
*** tmazur has quit IRC08:48
*** mrunge has joined #openstack-meeting-308:49
*** tmazur has joined #openstack-meeting-308:49
*** jamie_h has joined #openstack-meeting-308:49
*** tomoe_ has quit IRC08:52
*** tomoe_ has joined #openstack-meeting-308:53
*** rm_work has quit IRC09:20
*** rm_work has joined #openstack-meeting-309:23
*** lsmola has joined #openstack-meeting-309:24
*** markmcclain has quit IRC09:44
*** samchoi has joined #openstack-meeting-309:45
*** markmcclain has joined #openstack-meeting-309:45
*** yamamoto_ has quit IRC09:52
*** rm_work has quit IRC09:53
*** rm_work has joined #openstack-meeting-309:53
*** tomoe_ has quit IRC09:57
*** jcoufal has joined #openstack-meeting-310:01
*** markmcclain has quit IRC10:11
*** sarob has joined #openstack-meeting-310:17
*** MaxV has quit IRC10:21
*** MaxV has joined #openstack-meeting-310:21
*** sarob has quit IRC10:22
*** shakamunyi has joined #openstack-meeting-310:37
*** shakamunyi has quit IRC10:41
*** armax has joined #openstack-meeting-310:45
*** yamahata has quit IRC10:47
*** nacim has quit IRC10:55
*** MaxV has quit IRC10:59
*** amotoki has joined #openstack-meeting-311:11
*** tomoe_ has joined #openstack-meeting-311:14
*** samchoi has quit IRC11:14
*** sarob has joined #openstack-meeting-311:17
*** sarob has quit IRC11:21
*** coolsvap is now known as coolsvap|afk11:23
*** kenhui has joined #openstack-meeting-311:27
*** r0j4z0 has joined #openstack-meeting-311:27
*** r0j4z0 has left #openstack-meeting-311:27
*** tomoe_ has quit IRC11:29
*** nacim has joined #openstack-meeting-311:34
*** shakamunyi has joined #openstack-meeting-311:38
*** yamahata has joined #openstack-meeting-311:41
*** shakamunyi has quit IRC11:43
*** kenhui has quit IRC11:49
*** yamahata has quit IRC11:50
*** jackib has joined #openstack-meeting-311:50
*** kenhui has joined #openstack-meeting-311:50
*** yamahata has joined #openstack-meeting-311:50
*** alexpilotti has joined #openstack-meeting-311:53
*** nacim has quit IRC11:54
*** coolsvap|afk is now known as coolsvap11:58
*** kenhui has quit IRC12:01
*** MaxV has joined #openstack-meeting-312:03
*** coolsvap is now known as coolsvap|afk12:04
*** alexpilotti has quit IRC12:07
*** tomoe_ has joined #openstack-meeting-312:09
*** sarob has joined #openstack-meeting-312:17
*** sarob has quit IRC12:21
*** alexpilotti has joined #openstack-meeting-312:22
*** banix has joined #openstack-meeting-312:31
*** banix has quit IRC12:34
*** tomoe_ has quit IRC12:39
*** tomoe_ has joined #openstack-meeting-312:39
*** MaxV has quit IRC12:43
*** MaxV has joined #openstack-meeting-312:44
*** jackib has quit IRC12:45
*** mfer has joined #openstack-meeting-312:53
*** markmcclain has joined #openstack-meeting-312:59
*** markmcclain1 has joined #openstack-meeting-313:00
*** HenryG has quit IRC13:02
*** markmcclain has quit IRC13:03
*** thomasem has joined #openstack-meeting-313:03
*** lblanchard has joined #openstack-meeting-313:09
*** mrunge has quit IRC13:09
*** peristeri has joined #openstack-meeting-313:11
*** shakamunyi has joined #openstack-meeting-313:16
*** sarob has joined #openstack-meeting-313:17
*** julim has joined #openstack-meeting-313:18
*** sarob has quit IRC13:22
*** tomoe_ has quit IRC13:23
*** otherwiseguy has joined #openstack-meeting-313:24
*** msundara has joined #openstack-meeting-313:28
*** alexpilotti has quit IRC13:30
*** markmcclain1 has quit IRC13:31
*** jpomero has quit IRC13:32
*** jpomero has joined #openstack-meeting-313:33
*** jpomero has quit IRC13:34
*** jpomero has joined #openstack-meeting-313:35
*** jpomero has quit IRC13:36
*** otherwiseguy has quit IRC13:41
*** otherwiseguy has joined #openstack-meeting-313:43
*** yamamoto has joined #openstack-meeting-313:50
*** jpomero has joined #openstack-meeting-313:53
*** mwagner_lap has joined #openstack-meeting-313:53
*** tomoe_ has joined #openstack-meeting-313:54
*** jgrimm has joined #openstack-meeting-313:56
*** thinrichs has joined #openstack-meeting-313:57
*** pballand has joined #openstack-meeting-313:58
*** pballand has quit IRC14:00
*** ericpeterson has joined #openstack-meeting-314:03
*** jtomasek has quit IRC14:05
*** tmazur has quit IRC14:06
*** kenhui has joined #openstack-meeting-314:07
*** jtomasek has joined #openstack-meeting-314:08
*** amrith has left #openstack-meeting-314:09
*** markmcclain has joined #openstack-meeting-314:09
*** nelsnelson has joined #openstack-meeting-314:11
*** sarob has joined #openstack-meeting-314:17
*** jackib has joined #openstack-meeting-314:17
*** sarob has quit IRC14:21
*** kenhui has quit IRC14:24
*** kenhui has joined #openstack-meeting-314:24
*** yamamoto has quit IRC14:25
*** coolsvap|afk is now known as coolsvap14:30
*** jackib has quit IRC14:30
*** jackib has joined #openstack-meeting-314:31
*** yamamoto has joined #openstack-meeting-314:36
*** markmcclain has quit IRC14:45
*** kenhui has quit IRC14:46
*** zehicle_at_dell has quit IRC14:51
*** beyounn has joined #openstack-meeting-314:58
*** yamamoto has quit IRC14:59
*** yamamoto has joined #openstack-meeting-315:00
*** zehicle_at_dell has joined #openstack-meeting-315:00
*** nedbat has joined #openstack-meeting-315:01
*** thinrichs has quit IRC15:01
*** carl_baldwin has joined #openstack-meeting-315:01
*** cjellick has joined #openstack-meeting-315:06
*** jackib has quit IRC15:11
*** coolsvap is now known as coolsvap|afk15:14
*** HenryG has joined #openstack-meeting-315:15
*** sarob has joined #openstack-meeting-315:17
*** MaxV has quit IRC15:18
*** MaxV has joined #openstack-meeting-315:18
*** sarob has quit IRC15:21
*** nati_ueno has joined #openstack-meeting-315:23
*** samchoi has joined #openstack-meeting-315:26
*** coolsvap|afk is now known as coolsvap15:28
*** hurgleburgler has joined #openstack-meeting-315:28
*** beyounn has quit IRC15:29
mfer#startmeeting openstack-sdk-php15:30
openstackMeeting started Wed Jun  4 15:30:17 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 along with any applicable association15:30
*** kashyap has left #openstack-meeting-315:30
mferMatt Farina, HP15:30
glencGlen Campbell, Rackspace15:30
jamie_hJamie Hannaford, Rackspace15:30
samchoiSam Choi, HP15:30
*** jackib has joined #openstack-meeting-315:30
mferThanks for coming folks15:31
mfer#topic Agenda15:32
*** openstack changes topic to "Agenda (Meeting topic: openstack-sdk-php)"15:32
mfer1. 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
mfer2. Testing discussion, how to approach refactoring of tests, etc (samchoi). Also how are we going to approach integration tests (jamie_h)15:32
*** ericpeterson has left #openstack-meeting-315:32
mfer3. Discussion: do we need a "scripts" or "bin" folder at the top level? (jamie_h)15:32
mfer4. Discussion: do we need our own autoloader? Can we rely on Composer's instead? (jamie_h)15:32
mferIs there anything else we should add?15:32
*** hurgleburgler has left #openstack-meeting-315:32
jamie_hI have nothing else15:32
samchoiI'm ok with the topics15:33
glencok15:33
mfergreat.15:33
mfer#topic Reviews in progress - any questions/concerns?15:34
*** openstack changes topic to "Reviews in progress - any questions/concerns? (Meeting topic: openstack-sdk-php)"15:34
mfer#link https://review.openstack.org/#/q/status:open+project:stackforge/openstack-sdk-php,n,z15:34
samchoiSince this patch is needed by a few others, I believe it'd be worth discussing the status: https://review.openstack.org/#/c/93089/15:34
mferThere are a number of them and due to dependencies some that could land have not yet15:34
mferI'm in the process of reviewing that one right now15:35
mfersamchoi can you take a look at that one today as well?15:35
samchoimfer: sure, I had already reviewed a fairly recently patch so I'll check the additions today15:36
mfergreat15:36
*** jamiehannaford has joined #openstack-meeting-315:36
samchoithat review reminds me, should Shaunak be reviewing that one as well?15:36
jamiehannafordsorry - my wifi died15:36
mfersure15:36
samchoiOr are we fine with having 2 core reviewers?15:36
mfersamchoi two is enough15:37
*** jamie_h has quit IRC15:37
samchoimfer: thanks. Would the protocol be the same for very simple reviews? 2 core reviewers?15:37
mferjamiehannaford samchoi and I are going to look at the guzzle work today15:37
mfersamchoi yes15:37
jamiehannafordmfer thanks15:38
jamiehannafordcan I get a quick recap on what's just been said?15:38
mferwe're looking at the items that need to be reivewed starting with that one15:38
mferi'd like that one to get finished soon so it stops blocking the others15:39
*** jamie_h has joined #openstack-meeting-315:39
jamiehannafordyeah, exactly15:39
jamiehannafordthat one's a blocker for me15:39
mferbesides the guzzle work, are there any other reviews we should discuss?15:39
mferit's a blocker for me too15:39
jamiehannafordfor now, I'd say no - we can talk about others next week probably15:39
mfersamchoi do you have any others you'd wanted to talk about?15:40
samchoino I'm good15:40
mfer#topic Testing discussion, how to approach refactoring of tests, etc (samchoi). Also how are we going to approach integration tests (jamie_h)15:41
*** openstack changes topic to "Testing discussion, how to approach refactoring of tests, etc (samchoi). Also how are we going to approach integration tests (jamie_h) (Meeting topic: openstack-sdk-php)"15:41
mfersamchoi jamie_h would you like to get this discussion started?15:41
*** markmcclain has joined #openstack-meeting-315:42
jamie_hsamchoi did you have an opinion about the best way to refactor tests in line with proposal?15:42
samchoiI primarily just wanted to get a feel for how to best proceed with refactoring current tests, given jamie_h's email to the dev mailing list15:42
jamie_hyeah, okay15:42
samchoiI've been looking at other projects' test suites and see an array of approaches and am open to suggestions15:42
jamie_hso, in terms of approach - shall we refactor gradually (patch by patch) or do it all in 1 patch?15:43
*** yamahata has quit IRC15:43
jamie_hI don't think there's that much to do15:43
jamie_hstream wrappers were a big chunk of it (in terms of lines), which is in a pending patch15:43
mferjamie_h i think it depends on how it comes in. if you wanted to write a patch it would get reviewed15:43
mferor, it could happen with each change being made15:44
jamie_hI prefer the second option, personally - as long as there isn't massive scope creep15:44
jamie_hsamchoi which approaches of other SDKs caught your attention?15:45
samchoiI don't have a strong opinion on either way at the moment. I do wonder if the one shot approach would potentially become a blocker if it's too large though15:45
samchoiThe one that's caught my attention the most is the Ruby SDK, despite not having had enough time to look through it in detail yet jamie_h15:45
*** flaviof has joined #openstack-meeting-315:46
*** devlaps has joined #openstack-meeting-315:46
jamie_hfor now, IMO all we need to do is incorporate mocks when we unit test classes - which isn't that hard15:46
samchoiI spoke with a few of them, and their approach seems to be in line with what you pointed out in the email jamie_h15:46
jamie_hfog's testing setup is...interesting :)15:46
jamie_hwell, the old way at least15:46
*** Sukhdev has joined #openstack-meeting-315:46
samchoithey also spoke highly of VCR, which makes me wonder if PHP-VCR may be a good addition for our testing suite15:47
jamie_hthe problem I have with VCR is that it doesn't help unit tests at all - because units of code should be isolated. capturing network traffic, although clever, goes against that isolation15:47
jamie_hVCR is cools for integration tests where you're mixing lots of modules together, like a full run-through15:48
mferthis is more their way of handling integration testing w/o having an environment for that. they don't have the same limitations we do.15:48
jamie_hintegration testing (i.e. hitting the API) is also something I wanted to talk about15:48
*** tomoe__ has joined #openstack-meeting-315:48
samchoijamie_h: Correct, but the Ruby guys had mentioned to me that their focus was on unit and functional tests, with fucntional tests benefitting from VCR15:48
*** banix has joined #openstack-meeting-315:48
jamie_hI definitely agree we need something for functional tests15:49
*** tomoe_ has quit IRC15:49
mferjamie_h did you have something you wanted to suggest for integration tests?15:49
jamie_hI've been investigating testing tools we can use for integration tests15:50
*** ttrifonov is now known as ttrifonov_zZzz15:50
jamie_hI really like the look of one, called http://behat.org/15:50
jamie_hthe basic idea is that you define each SDK feature as a "story"15:50
jamie_hthat story is defined in human-readable language, and can be automatically tested against the API15:51
jamie_hthe whole idea is that it allows us to define the scope of a feature (listContainers, getContainer) and define its acceptance criteria, i.e. a common definiton of "done"15:51
jamie_hso apart from integration testing, we also know what our customer's use-cases are and have a way of tracking when those features are complete (project progress)15:53
mferThis is quite scrum story based15:53
mfercan you point to any projects using behat?15:54
jamie_hi can find that out. It has like 600k downloads on packagist, so it's well-established15:54
mferi'm thinking about this project in terms of developer experience. this is a little different from a PHP app built by a team. I can see how behat is useful for that... especially with stories15:54
mferI'm trying to see how this would be useful for a developer consuming this library in addition to testing15:55
jamie_hit's making sure the experience of our users is well defined15:55
mfera library like this is a slightly different animal15:55
jamie_hthis is what I'm referring to: http://dannorth.net/whats-in-a-story/15:55
mferfor example, i was looking at the acceptance tests of gophercloud (https://github.com/rackspace/gophercloud)15:56
mfertalking with a number of developers they thought this was a great idea15:56
mferthey are acceptance tests and they work great as examples of how to do things15:56
mferthe audience is developers rather than a PM who is checking the story in human readable language15:56
mferi'm curious what y'all think15:57
samchoiI haven't encountered a projet using behat yet, I have no opinion at the moment15:57
jamie_hit's a way of us defining user requirements15:58
jamie_hand testing them with our SDK15:58
mferjamie_h do you know of any open source libraries using behat. i'd like to look at usage and who it applies to15:58
jamie_hmfer I'll add that as an action point15:58
jamie_hwe don't need to reach decisions now, just sharing what I've been researching recently15:59
mferi'll tell ya, what we did in my last gig would have benefited from behat. i'm just not sure about an SDK with all developers working on it.15:59
mferi think it's great. and i'm going to look more into behat15:59
*** nati_ueno has quit IRC15:59
jamie_hit's a tool that benefits any software project which has consumers15:59
mferdifferent kinds of consumers do things and prefer things in a different way16:00
jamie_hbecause you're defining their engagement and making sure those user requirements are always tested16:00
mferlots of enterprise developers don't use scrum or stories. this will be different for them16:00
*** emagana has joined #openstack-meeting-316:00
mferit might be good if each of us who isn't familiar with behat can take a look at it16:01
mferit might be good to look at who our target audiences are (and not assume that ourselves are the 80% of that group in style) and look at the context16:01
jamie_hthis is a good intro to behat: http://behat.readthedocs.org/en/latest/quick_intro.html16:01
jamie_hthe whole idea of behat is for us to be able to target our audience and establish use cases16:02
jamie_hand then ensuring our SDK meets those user expectations16:02
mferi think that's useful. the format matters as well. this is very scrum story formatted.16:02
*** lcheng_ has joined #openstack-meeting-316:03
samchoijamie_h: I would think that the test suite is primarily for the contributors as I think it's unlikely that many casual users would be too concerned with understanding/reading the entire test suite.16:03
samchoidid you have other people in mind?16:03
samchoifor the audience?16:03
jamie_hsamchoi primarily for us. but it's accessible to anyone. we're effectively offering them blueprints of our features16:04
*** markmcclain has quit IRC16:04
jamie_hit would serve as our integration suite16:04
jamie_h"make sure feature x works exactly as our users would want it to"16:04
jamie_h"if there's another conceivable use case, test that too"16:04
jamie_hall against the API16:04
samchoialright thanks for clarifying16:05
mferjamie_h and our developer users would want to define that in a scrum story?16:05
jamie_hmfer they could look at the use-cases if they wanted to, but it's primarily about us understanding what our users want from our SDK16:06
mferthat's what I'm questioning. particularly after the summit where just about no one like things done for you. they all wanted to write and see code. that's why so many people liked the gophercloud style of acceptance tests16:06
jamie_hwe'd have documentation for that16:06
mferglenc can you make sure the folks on gophercloud know that people liked the style of acceptance tests16:06
jamie_halthough i see the appeal of gophercloud's acceptance tests, it doesn't offer anything that good example code or documentation can16:07
mferjamie_h samchoi i always like comparing things. it helps ideas to pop or not. what would the alternative be?16:07
jamie_hwrite stand alone scripts that hit the API16:07
mferjamie_h those acceptance tests are written in a format developers like. Code. That's really really important.16:08
mferPersonally, I'd rather write code than a story any day16:08
jamie_hall acceptance tests will need to be written in code - but the priority is making sure customer use cases are met16:08
jamie_hwith a script that gets ambiguous16:08
glencmfer - I will pass that along16:08
mfercustomers are other developers. not management or PMs. that's important here16:09
jamie_hsample code + documentation is what devs will go to16:09
mferbesides devs as customers who else is there?16:09
mferit's the devs who consume it and the devs who work on it16:09
mferI question so much because I want anything we do to fit well.16:09
samchoiI would think that's basically it, no?16:10
jamie_hwith standalone scripts, you're not testing dev use cases. you're just ensuring that nothing breaks16:11
jamie_hthat's my only concern16:11
jamie_hwe need to make sure devs are getting what they should16:11
jamie_hshall postpone this until next week when we've had more time to research stuff?16:12
samchoisure jamie_h16:12
mfercan't you test use cases by writing them? then folks who consume it have example code of exactly how to do that the best way. and if someone has a better way it can be changed?16:12
mferi think we should postpone this. get to know behat and spend some time focusing on the needs of our audiences. that could be good16:13
mferare we ready to move on?16:14
samchoisure16:14
jamie_hyep16:14
mfer#topic Discussion: do we need a "scripts" or "bin" folder at the top level? (jamie_h)16:14
*** openstack changes topic to "Discussion: do we need a "scripts" or "bin" folder at the top level? (jamie_h) (Meeting topic: openstack-sdk-php)"16:14
jamie_hjust a general question: what do we anticipate these folders get used for?16:14
mferI think we can delete these folders. In practice we don't need them and they had been added as part of the pear spec16:14
jamie_hokay16:15
jamie_hjust want to keep top-level as light as possible16:15
mferanyone disagree?16:15
samchoiI'm in favor on anything that simplifies the directory structure...we have plenty of layers already16:15
samchoifavor of*16:16
mfergreat16:16
mfershall we move on to the autoloader discussion?16:17
*** jcoufal has quit IRC16:17
jamie_hI have nothing more to add16:17
samchoisure, go ahead mfer16:17
*** otherwiseguy has quit IRC16:17
mfer#topic Discussion: do we need our own autoloader? Can we rely on Composer's instead? (jamie_h)16:18
*** openstack changes topic to "Discussion: do we need our own autoloader? Can we rely on Composer's instead? (jamie_h) (Meeting topic: openstack-sdk-php)"16:18
jamie_hrealistically - do we need our own autoloader class?16:18
mferi don't think so. we should just document using it with another autoloader.16:19
glenc+116:19
jamie_h+116:19
jamie_hfor everyone's interest, ZF3 might be doing this too: https://github.com/zendframework/zf2/issues/628516:20
jamie_hplus, IDK how our autoloader handles dependencies like guzzle16:20
mferlikely doesn't16:21
mferlets delete it16:21
mferi'm happy to take that on too16:21
mferok, i think that's everything on the agenda16:21
mfer#topic Open Discussion16:21
*** openstack changes topic to "Open Discussion (Meeting topic: openstack-sdk-php)"16:21
mferwho wants to talk about what16:21
mfer?16:22
samchoiI didn't want to slow us down before, but did anyone have any reasons why PHP-VCR couldn't be used to supplement our test suite?16:22
*** Youcef has joined #openstack-meeting-316:23
samchoiIf not, I'm interested in seeing how well it'd work for our purposes16:23
jamie_hfrom my perspective, we need two types of tests: unit tests (which are isolated, thus don't need VCR) and acceptance/integration tests16:23
samchoisince it'd simply speed up our HTTP requests and doesn't seem to have a drawback16:23
*** davlaps has joined #openstack-meeting-316:23
jamie_hIDK whether VCR will help us with acceptance tests because we need a real API response to judge whether our feature works16:23
samchoiWell yes, it's definitely not for unit tests. Why not use it for other tests though? I could reach out to the Ruby guys again, but they've had great success with it16:24
jamie_hdon't get me wrong - I really really like VCR and have used it before. I just don't know whether it helps us16:24
jamie_hsamchoi sure okay16:24
mferwe need to get setup on the openstack infra for testing. VCR might help to speed up local testing but we should hit a real API16:24
jamie_hif we all think we need to hit a real API for acceptance tests, not sure that VCR is the tool for us16:24
mferwhen reviews go into gerrit the tests should be automated against a real api. we can do this i'm told16:25
samchoihmm I'll follow up on this16:25
samchoiI'd assume others are just creating new VCR cassettes after a set period16:26
jamie_hwith VCR you can refresh cassettes by overriding their content with a new API hit, I think16:26
jamie_hmfer would we have control over which tests to run when a patch enters gerrit? like travis16:27
mferi belive we have that control16:27
jamie_hawesome16:27
jamie_hthat can't come soon enough IMO :)16:28
mferwe'd have any control we'd have anywhere else because we'd script what gets run16:28
mferwe have two minutes left. anything else before we wrap this up for the next group?16:29
glencnot from me16:30
mfer#endmeeting16:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:30
openstackMeeting ended Wed Jun  4 16:30:14 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-06-04-15.30.html16:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_sdk_php/2014/openstack_sdk_php.2014-06-04-15.30.txt16:30
mferhave a good one y'all16:30
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_sdk_php/2014/openstack_sdk_php.2014-06-04-15.30.log.html16:30
samchoithat's a first, we're wrapping up on time :)16:30
glency'all have a good week16:30
*** tjones has joined #openstack-meeting-316:30
tjones#startmeeting NovaBugScrub16:30
openstackMeeting started Wed Jun  4 16:30:52 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:31
*** jamiehannaford has quit IRC16:31
*** ericpete_ has joined #openstack-meeting-316:31
*** otherwiseguy has joined #openstack-meeting-316:32
*** emaganap has joined #openstack-meeting-316:33
tjonesgoing to go an do some tagging unless anyone appears16:33
*** emagana has quit IRC16:34
*** tomoe__ has quit IRC16:42
*** ericpete_ has left #openstack-meeting-316:43
*** MaxV has quit IRC16:44
*** MaxV has joined #openstack-meeting-316:45
tjonestriage done16:46
*** MaxV has quit IRC16:49
*** digambar_ has joined #openstack-meeting-316:55
*** jackib has quit IRC16:55
tjones#endmeeting16:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:55
openstackMeeting ended Wed Jun  4 16:55:51 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/novabugscrub/2014/novabugscrub.2014-06-04-16.30.html16:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/novabugscrub/2014/novabugscrub.2014-06-04-16.30.txt16:55
openstackLog:            http://eavesdrop.openstack.org/meetings/novabugscrub/2014/novabugscrub.2014-06-04-16.30.log.html16:55
*** tjones has left #openstack-meeting-316:57
*** jackib has joined #openstack-meeting-317:00
*** digambar_ has quit IRC17:10
*** anil_rao has joined #openstack-meeting-317:11
*** thomasem has quit IRC17:13
*** shakamunyi has quit IRC17:13
*** thomasem has joined #openstack-meeting-317:13
*** jackib has quit IRC17:16
*** jackib has joined #openstack-meeting-317:16
*** safchain has quit IRC17:17
*** vinay_yadhav has joined #openstack-meeting-317:24
*** thomasem has quit IRC17:25
*** rkukura has joined #openstack-meeting-317:25
*** thomasem has joined #openstack-meeting-317:26
*** Sukhdev has quit IRC17:28
*** bauzas has left #openstack-meeting-317:29
*** pcm_ has joined #openstack-meeting-317:29
*** s3wong has joined #openstack-meeting-317:29
mesteryHi folks!17:30
*** pgpus has joined #openstack-meeting-317:30
mesterySumitNaiksatam won't be around to run the services meeting today, so he asked me to do that.17:30
s3wongmestery: hello, are you chairing the adv-service meeting today?17:30
banixmestery: hi17:30
mesterys3wong banix: Yes!17:30
pgpusGood to see you Kyle17:30
banixs3wong: hi17:30
mesteryI'll wait until we get quorum here.17:30
s3wongbanix: hello17:30
banixhi everybody17:30
*** SridarK has joined #openstack-meeting-317:30
mesteryLooks like we may have it. :)17:30
mestery#startmeeting Networking Advanced Services17:30
openstackMeeting started Wed Jun  4 17:30:59 2014 UTC and is due to finish in 60 minutes.  The chair is mestery. 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
mestery#link https://wiki.openstack.org/wiki/Meetings/AdvancedServices Agenda17:31
rkukurahi17:31
mesterySo, SumitNaiksatam can't be with us today, he asked me to run this.17:31
mesteryI'd mainly like to go over the BP reviews/approval process, per SumitNaiksatam's request.17:31
s3wongmestery: OK17:31
mestery#link https://wiki.openstack.org/wiki/Neutron/AdvancedServices/JunoPlan17:32
mesteryOK, so shall we walk through the JunoPlan here?17:32
s3wongmestery: sure17:32
vinay_yadhavok17:32
cgoncalveshi!17:32
banixyeah17:32
*** shivharis has joined #openstack-meeting-317:32
mesteryOK, so lets just start at the top.17:32
mesteryThe over-arching BP was approved already.17:32
*** natarajk has joined #openstack-meeting-317:32
*** jcoufal has joined #openstack-meeting-317:33
mesteryThe next one on the list is flavor framework.17:33
mesteryenikanorov: Are you around?17:33
banixso this one has been under review for a long time17:33
mesteryYes, there were some issues which markmcclain had wiht htis one if I recall.17:33
mesteryThere is a ML thread as well I believe from enikanorov.17:33
banixmestery: yes17:33
mesteryWe need to close on this one ASAP I believe.17:33
mestery#action enikanorov to re-post ML thread.17:34
*** nati_ueno has joined #openstack-meeting-317:34
mestery#action mestery to bringup flavor framework discussion at Neutron meeting on Monday.17:34
mesteryAnything else with flavor framework?17:34
*** jmsoares has joined #openstack-meeting-317:34
s3wongno17:34
enikanorovmestery: sorry, i'm late17:34
mesteryOK, cool,17:34
mesteryNext one is service insertion.17:35
mesteryThis one has gone through many iterations as well.17:35
enikanorovso i think it makes sense to limit initial implementation to those aspects that don't involve integration with services17:35
s3wongmestery: well, since enikanorov is here, does he have anything else to say about flavor framework?17:35
enikanorovso the question posted to ML could be addressed later17:35
mesteryenikanorov: for flavor framework?17:35
enikanorovyes17:35
pgpusServicde Insertion I did not find any sharing of a given service, any comments?17:35
mesteryenikanorov: OK, got it.17:35
enikanorovi'm planning to have implementation at ~J-1 time so we could spend J-2 reviewing and hopefully merge it by J-0217:36
mesteryenikanorov: Perfect!17:36
s3wongenikanorov: J-1 is next week, right? :-)17:36
*** jmsoares_ has joined #openstack-meeting-317:36
*** beyounn has joined #openstack-meeting-317:36
*** jmsoares_ has left #openstack-meeting-317:36
enikanorovs3wong: right, but flavors API is no big deal IMO17:36
enikanorovstill hoping to get whole patch < 1k lines17:36
*** ivar-lazzaro has joined #openstack-meeting-317:36
s3wongenikanorov: that's including STF, which is still part of flavor, right?17:37
mesteryenikanorov: Cool!17:37
*** yamamoto has quit IRC17:37
pgpusI have added mysellf to service Insertion and will see what I can contribute after review17:37
enikanorovthat's probably it from my side17:37
enikanorovfeel free to approve flavor framework bp17:37
enikanorov:)17:38
banixenikanorov: done!17:38
mesteryenikanorov: Ha! I will review it again this afternoon.17:38
mesteryenikanorov: Thanks!17:38
mesteryOK, so service insertion now.17:38
mesteryThis one is also looking like it's ready for some core reviewer and approval love I think.17:38
*** jmsoares has quit IRC17:38
s3wongmestery: OK, since kanzhe and kevinbenton aren't here, I will take this one17:38
mesterys3wong: thanks!17:38
*** jmsoares has joined #openstack-meeting-317:39
s3wongmestery: yes, I have been advertising it everywhere, so it is now waiting for cores to look at, if they have time17:39
banixthis one has not received many reviews outside the advanced service sub team17:39
s3wongas kanzhe talked about last week, the division of tasks between kanzhe, kevinbenton and me were decided17:39
pgpusDoes the Service Insertion bp require any reveiw or is it approved?17:40
mesteryOK, perfect!17:40
s3wongand I believe kanzhe and kevinbenton are currently working on API and db17:40
mesterypgpus: It's not approved yet, reviews welcome.17:40
SridarKs3wong: so first target will be fwaas - no change correct ?17:40
s3wongSridarK: FWaaS is the natural first, the tough one is LBaaS17:40
SridarKs3wong: :-)17:40
pgpusok did one pass and will do another to make sure it meets J-1 time farme deliveries17:40
mesterys3wong: Lets see if we can get this integrated before LBaaS departs Neutron. ;)17:41
mesterypgpus: J-1 is next week, none of this is targeted for J-117:41
s3wongand luckiy and forunately, LBaaS is going through model change at J-2, so we can work with their db migration naturally17:41
mesteryThis is all J-2 and beyond at this point. :)17:41
s3wongon the right time :-)17:41
SridarKmestery: without this no one can go anywhere :-)17:41
*** regXboi has joined #openstack-meeting-317:41
pgpusHas anyone looked at ServiceBase class definitions?17:41
pgpusor is it wating for Data Models?17:42
s3wongpgpus: I deifned it, please look into it and see if it fits into your expectation :-)17:42
banixregXboi: Any comments wrt the service insertion beyond your comments on the review system?17:42
regXboibanix: sorry for being late - no - I need to re-read the new patch17:43
pgpusThanks s3wong17:43
banixregXboi: just noticed you joined; thats the topic being discussed17:43
banixs3wong: what are you referring to? in the service insertion spec?17:43
regXboiI read through all the BPs on the status page as of Sunday and added comments where I had them - haven't had a chance to follow up on all of them since17:43
pgpuswill we cover more than l2, l3 insertion in j-117:44
*** sarob has joined #openstack-meeting-317:44
s3wongbanix: regarding love outside of adv serv. subteam, what we really want is people from LBaaS (no one), FWaaS ( SridarK ) and VPNaaS ( nachi_ueno )17:44
mesterypgpus: Again, none of this work is being done for J-1, the specs are targeted to be approved by J-1.17:44
pgpushttps://review.openstack.org/#/c/93128/9/specs/juno/service-base-and-insertion.rst17:44
mesterypgpus: J-1 is next week, it may be cut Tuesday, but as late as Thursday. :)17:44
banixs3wong: speak of love got me confised for a second :)17:44
*** eghobo has joined #openstack-meeting-317:44
s3wongbanix: no love so far :-(17:45
regXboiactually, banix, I'm worng17:45
regXboiI did read through the new SI draft17:45
*** thomasem_ has joined #openstack-meeting-317:45
mesterys3wong: I'm from the LBaaS team, I'll review in more detail and spread the word with the broader team.17:45
pgpusok atleast lets get bp clerared for coding on service insertion17:45
regXboiand I still want some text on equating service port and service attachment point17:45
s3wongmestery: cool, but you are everywhere, so I don't know if it counts :-)17:45
regXboibecause if I read it as someone from outside, the equivalency isn't obvious17:45
mesterys3wong: :P17:45
s3wongmestery: but we do need your approval eventually  for sure :-)17:46
banixregXboi: agree; that should be easily addressed17:46
SridarKs3wong: i am on board - have had many discussions with u and kanzhe - will put my +1 soon - just minor things i am trying to work out17:46
*** thomasem has quit IRC17:46
s3wongSridarK: cool, We can talk more if you want (even f2f)17:47
SridarKs3wong: sure thanks17:47
mesteryOK, should we move on to traffic steering now?17:47
*** lcheng_ has quit IRC17:47
pgpusIntegration with devstack, heat and other modules for service insertion is bit unclear and does anyone have any clue on that?17:47
s3wongmestery: sure, I have nothing else to say :-)17:47
*** mandeep has joined #openstack-meeting-317:47
mesterypgpus: There are people signed up for some of those, but I don't see devstack under that project at all.17:48
pgpusor we leave the impact to later time frames?17:48
s3wongpgpus: not yet, though Louis volunteered for Heat17:48
s3wongand kanzhe , kevinbenton , and I will likely include devstack work as part of our ongoing development and testing17:49
pgpusGood atleast Heat as Orchestartion tools and template of Service will help us give some idea17:49
banixs3wong: need to add devstack to the tables17:49
s3wongpgpus: however, if you want to volunteer to join in, we welcome you :-)17:49
*** jamie_h has quit IRC17:49
s3wongbanix: yes17:49
pgpusMay I can look into devstack and add my comments to bp17:50
banixs3wong: thanks17:50
*** jamie_h has joined #openstack-meeting-317:50
s3wongpgpus: of course. Thanks!17:50
*** vishnu_ has joined #openstack-meeting-317:50
mesteryOK, on to traffic steering.17:51
mesterycgoncalves: This is your area I believe.17:51
cgoncalvesmestery: indeed17:51
pgpusdevstack will need nova / neutron config changes for service creation by few params possibly will verify by flow one time17:51
cgoncalvessince last week we addressed some comments and submitted a new patchset17:51
*** nedbat_ has joined #openstack-meeting-317:51
cgoncalveswe are in need of more reviewers I believe17:51
s3wongpgpus: OK17:51
pgpusOk we move to traffic steering17:51
mesterycgoncalves: OK, good to know!17:51
mestery#info Traffic Steering BP is in need of more reviewers17:52
s3wongcgoncalves: will review17:52
cgoncalvesand I apologise for the late patchset17:52
cgoncalvess3wong: thanks17:52
regXboimestery: I plan on reading17:52
s3wongcgoncalves: though I am still hoping that traffic steering will take advantage on the connectivity map that we are going to store in ServiceBase objects17:52
mesterys3wong regXboi: Thanks!17:52
shivhariscgoncalves: link?17:52
cgoncalvestraffic steering can play a significant role in the new openstack nfv sub-team vision17:52
mestery#link https://review.openstack.org/#/c/9247717:53
cgoncalvesmestery: tks17:53
shivharismestery: thx17:53
s3wongcgoncalves: yes, I noticed your participation during the NFV meeting this morning17:53
*** nedbat has quit IRC17:53
cgoncalvesalso, I have not nominated myself to all items that are in the wiki17:54
s3wongcgoncalves: there are others in your team as well, right?17:54
mesterycgoncalves: OK, can you remove yourself where appropriate?17:54
cgoncalvesso I look forward for volunteers wanting to help me on heat, horizon, etc17:54
pgpushttps://blueprints.launchpad.net/neutron/+spec/traffic-steering-abstraction17:54
*** Sukhdev has joined #openstack-meeting-317:54
cgoncalvesmestery: ok17:55
cgoncalvess3wong: yes, but not directly involved in openstack17:55
cgoncalvess3wong: jsoares is collaborating with me on the proposal though17:55
pgpuslooks like port to port traffic forwarding is involved and will help service chaining is it states17:55
cgoncalvespgpus: yes17:56
banixs3wong: have a pointer to the nfv meeting wiki?17:56
mandeeppgpus: Correct17:56
cgoncalves#link https://wiki.openstack.org/wiki/Meetings/NFV17:56
cgoncalvesbanix: ^17:56
banixcgoncalves: thx17:56
s3wongbanix: https://wiki.openstack.org/wiki/Meetings/NFV17:56
banixs3wong: thx17:56
*** kenhui has joined #openstack-meeting-317:56
*** jamie_h has quit IRC17:57
pgpusAre we using ovs flolw control to steer traffic and does it mean control plane data plane seperation as sdn/nfv here?17:57
*** OSM has joined #openstack-meeting-317:57
cgoncalveson the implementation side I have still some concerns, but probably are out of scope for now17:57
pgpusSure I will lookinto nfv meetings and join that besides here17:57
*** kenhui has quit IRC17:58
*** jackib has quit IRC17:58
*** kenhui has joined #openstack-meeting-317:58
mesteryOK, anything else on traffic steering or should we move onto the service chaining BP?17:58
cgoncalvesmestery: I think I've nothing more to add for now. thanks17:58
mesterycgoncalves: Thanks!17:59
mesterymandeep: I believe Service Chaining is your BP?17:59
mandeepmestery: Correct17:59
mesteryHow is the review going for this one?18:00
mandeepThe status is:18:00
pgpusI am still not sure what's the assumption here , do we steer traffic first or chain the phyiscal pipe (logical pipe ) first, as what preceeds what, chaining or steering?18:00
mandeep1. A use-case needs to be added to the BP, that is still pending18:00
mandeep2. I just updated the plan and I am targeting J1 for BP approval and J3 for code in neutron/CLI18:00
pgpusOK mandeep that's a good point to start18:00
pgpusfor which one steering or chaining you mean?18:01
mandeep3. I still need to identify volunteers for Heat/Horizon/Devstack - TBD18:01
mandeepmestery: That is all18:01
mandeeppgpus: Chaining18:01
mesterymandeep: thanks!18:01
*** cjellick_ has joined #openstack-meeting-318:02
mesterymandeep: I had one comment in the latest review around creating a separate launchpad BP for this one as well so we can track it with LP milestones.18:02
mesterymandeep: I added it in the review.18:02
mandeepOK, will do.18:02
*** jamie_h has joined #openstack-meeting-318:02
pgpusdevstack for neutron service shaining you mean mandeep, may be let me review it for you18:02
regXboiI'm still concerned about the non-sunny day18:02
mandeeppgpus: Sure18:02
mesteryregXboi: I saw your concerns as well18:02
mandeepregXboi: non-sunny day?18:03
*** kenhui1 has joined #openstack-meeting-318:03
regXboiwhat happens in re notifications if something goes wrong18:03
regXboithe statement "1. All updates to service-chain resources need to be relayed to the configured service-chain-providers"18:03
regXboineeds clarification around what happens if the relay fails18:03
s3wongregXboi: somethig goes wrong meaning something within the chain going down?18:03
mandeepregXboi: I am hoping that is where an infrastructure like group-policy can hep18:03
*** sarob has quit IRC18:04
regXboimandeep: I think you should identify that dependency in the text then18:04
mandeepregXboi: Got it. That is a function call, not a message,18:04
*** vishnu_ has quit IRC18:04
*** sarob has joined #openstack-meeting-318:04
*** kenhui has quit IRC18:04
mandeepregXboi: Good point. I will add that18:05
*** cjellick has quit IRC18:05
pgpusAre we looing Infra GP and Service GP as layered GP for Endpoints involved?18:05
regXboimandeep: ah, I read the text as a message, not an rpc18:05
s3wongpgpus: by service GP do you mean an EPG wrapping a service?18:05
regXboiin general though, I'm going to be thinking about the "how do we handle something not working" aspect18:05
*** beyounn1 has joined #openstack-meeting-318:05
mandeepregXboi: So ignore my comment on GP, that was in a generic sense - not for this specific interaction18:05
pgpusSure that is Group Policy within Group Policy hierarcy that was demoed by Sumit's team and had some codes in github I believe18:05
regXboimandeep: got it18:06
s3wongpgpus: that is hierarchical contracts, which is division more between infra owner and app owner (roles)18:06
pgpusOK lets move on ignore GP for now18:06
regXboibut I will followup with the "fixup" concept on 175 needs some thought about what do we do if a servicechaininstance can't be "fixed up"18:06
*** beyounn has quit IRC18:06
cgoncalvesregXboi: it should also be of interest for this spec to know what are ODL plans on this as I see there is a Service Function Chaining proposal there and you're somehow involved :-)18:06
cgoncalves#link https://wiki.opendaylight.org/view/Project_Proposals:Service_function_chaining18:07
pgpusService failure is diff from Infra failure so will need some thinking and borrow some ideas from service VM or wherever18:07
regXboicgoncalves: guilty as charged - I'm not 100% sure yet - I'm only peripherally involved at this point18:07
*** jackib has joined #openstack-meeting-318:07
mesteryregXboi: You are involved in more than I am I believe. ;)18:07
regXboicgoncalves: I'll have a better idea when I have a chance to dig through the proposed yang models18:08
mandeeppgpus: My comment was that in general, your "actual" can deviate from "expected" and there needs to be a way to recover to the "expected" state, anf group-policy allows a clean way to achieve that.18:08
cgoncalvesmestery: jealous? hehe18:08
mesterycgoncalves: Ha!18:08
*** jackib_ has joined #openstack-meeting-318:08
regXboimandeep: that's a very good thing to say in the BP I think18:08
regXboibecause it takes care of a lot of my budding concerns :)18:08
mandeepregXboi: Yes, I will add that.18:08
regXboimandeep: thx18:09
pgpusIs Service chaing tied to ODL or is it generic ? this links shows ODL way?18:09
cgoncalvesregXboi: ok, thanks. I'd also like to get a peek on ODL's work on this matter. anyway... i'm offtopic-ing, sorry18:09
s3wongpgpus: I certainly hope we don't have to tie it to the ODL project18:09
regXboicgoncalves: there is a patch spec in ODL gerrit right now...18:09
regXboiwill pm it to you18:09
*** sarob has quit IRC18:09
mandeeppgpus: As defined, it is designed to independent of any specific backend/provider18:10
regXboimandeep: +118:10
banixyeah lets not mix in the group policy here18:10
banixthis is more generic as mandeep said18:10
mesteryOK, 20 minutes left and 2 BPs to go.18:10
* mestery thinks we have a chance at completing these.18:11
s3wongbanix: yes, a service chain can be implemented by GBP18:11
mandeepbanix: Agreed18:11
pgpusThat is welcome, so the focus is stitching service and default is OVS for underlay and for overlay we need Group or Chain policy18:11
regXboimestery: don't say that - murphy will hear!18:11
mesteryregXboi: hehehehe18:11
mandeepregXboi: ;-)18:11
*** jackib has quit IRC18:11
mesteryOK, moving on to L3 agent consolidation.18:12
pgpusLooks this needs more detail look into bp, will try cover this offline, but what's the last date for approval on this one?18:12
pgpusCould be per Service Chaining policy18:14
regXboipgpus: +118:14
pgpusadd to that per Tenant18:14
mesteryDoes anyone know the IRC nick of hte L3 agent consolidation author?18:14
mesteryLooks like it's iwamoto, who likely is sleeping right now. :)18:15
s3wongyes18:15
mesteryI have some serious concerns with this BP, adding comments now.18:15
mandeeppgpus: Please go ahead and add review comments, it is more important that we get it right.18:15
regXboimestery: join the club, we've got jackets?18:16
pgpusOk madeep will do that18:16
mesteryregXboi: :)18:16
mesteryAnyways, lets move on to the last one, and my personal "favorite named BP of all time": Tap as a Service.18:16
vinay_yadhav:)18:16
* regXboi hears trumpets in the background18:16
s3wongit is on Tap!!!18:16
vinay_yadhavgood one18:17
regXboiI haven't had a chance to read the new patchset18:17
vinay_yadhavwell reviews are on and we are refining it each patch set18:17
vinay_yadhavtargeting juno 2 for spec as well as neutron code18:18
regXboiunderstood I'm just saying I commented on ps 3 and haven't had a chance to re-read ps 418:18
mesteryvinay_yadhav: Cool, thanks! I haven't reviewed this one yet either.18:18
regXboiso I still owe a re-read18:18
mesteryregXboi: Get on that man! ;)18:18
vinay_yadhavregXboi: i got it :)18:18
cgoncalvesvinay_yadhav: great work on quickly addressing reviewers' comments!18:18
regXboimestrey: right behind you :)18:18
pgpuswhere is the link for tap, I see virtualResource one did I miss tap one?18:18
regXboi#link https://review.openstack.org/#/c/96149/18:18
anil_raoDid not see any major concerns18:19
regXboiso, one thing that jumps out at me18:19
pgpusis this tp mirroring intended for HA or reslliance to service?18:19
regXboiwho can create a tap service?18:19
vinay_yadhavi will start a dev thread soon as sumit suggested18:19
vinay_yadhavtenant can create the service instance18:19
pgpustap mirroring on tap iterface of VM?18:20
vinay_yadhavthe work flow for using the service is described in short in the spec18:20
anil_raoSeveral use cases are documented - debugging and more importantly traffic monitoring/visiblity for security and analytics18:20
s3wongvinay_yadhav: and admin can redirect traffic flow to it if they use GBP :-)18:20
s3wongthen we can rename this NSA-as-a-Service18:20
vinay_yadhavhaha sure :)18:21
mandeeps3wong: Or the copy action for GBP can use the tap service ;-)18:21
regXboiso... how does this interact with shared networks?18:21
vinay_yadhavpgpus: we mirror the traffic transiting the port in the VSwitch18:21
pgpusI see good use cases for port mirroring on neutron a good one need to study this , but what's security risk on this , any thoughts?18:21
s3wongmandeep: yes, forgot about that, sorry :-(18:21
mandeeps3wong: Nothing to be sorry about, another option!18:22
anil_raoWe have documented the security aspects in the spec. We try to honor the existing Security Group policies .18:22
pgpusWhat if some spurious process redirects the traffic will it not cause serious attack or compromise on the service?18:22
regXboianil_rao: you've identified the security aspects at the traffic/port level18:23
*** nati_uen_ has joined #openstack-meeting-318:23
regXboianil_rao: I'm asking the administrative/tenant level18:23
anil_raothe service can be initiated by a tenant owner and its scope is restricted to that tenant.18:23
vinay_yadhavregXboi: do u mean tenant misbehaving18:23
regXboivinay_yadhav: I'm thinking if I have a shared network and the tenant of the network can tap any port on that network, that might be an issue18:24
s3wongregXboi: you want admin to have the ability to remove a tap from tenant?18:24
pgpuswell secuirty is wast bust aslong it covers for the said use case we should be OK18:24
regXbois3wong: I'm starting to think *only* admin can set up TaaS18:24
mesteryregXboi: Have you expressed these concerns in the BP review? If not, please do.18:24
anil_raowe would like a tenant on say a public cloud to be able to initiate traffic monitoring for his/her tenat. Ideally without cloud admin intervention.18:25
regXboimestery: will do - honestly, I only started thinking of them just now18:25
mesteryWhy would a non-admin need to setup TaaS?18:25
vinay_yadhavregXboi: need to think on the acpects of shared networks18:25
banixregXboi: i think even that may have unwanted implications18:25
vinay_yadhavanil_rao: agree18:25
regXboivinay_yadhav: I'll craft some comment text for the security impact section18:25
vinay_yadhavsure thanx18:25
anil_raoThe scope of the Tap is limited to the tenant that initated the service, so I believe it should be okay.18:25
s3wongregXboi: please do18:26
s3wonganil_rao: only on the tenant's own vport, right?18:26
*** nati_ueno has quit IRC18:26
banixanil_rao: which may be more reasonable than allowing the admin to do so18:26
s3wongstuff like external port is something tenants can't tap18:26
*** ivar-lazzaro has quit IRC18:26
anil_raoYes, that is correct. The ports in question must belong to the tenant18:27
vinay_yadhavs3wong: yes only on tenants vports18:27
mestery3 minutes left folks, I think we should start wrapping this up now.18:27
mesteryI propose this discussion move to the BP at this point.18:27
mesteryIt seems serious enough to warrant some thought, per regXboi.18:27
regXboianil_rao: aha! let me see if I find that text18:27
s3wongmestery: sure18:27
pgpusI believe port redirection is important for VM agents to Hypervisopr Agents communication and hence this should get priority irrespective of security which will evolve overtime18:27
anil_raoVinay and I will make sure to update the spec with some additional detail18:27
vinay_yadhavsure18:27
regXboianil_rao: ok, I found that text18:28
mesterypgpus: I'm not following that comment at all.18:28
regXboibut I still need to think through shared networks18:28
regXboipgpus: er?!?!?!18:28
mesteryregXboi: It's not just me at least.18:28
regXboimestery: no, I want an explanation before I say -118:28
mesteryAgreed, but with 1 minute left, not sure we'll get there. :)18:29
*** mandeep has quit IRC18:29
mesteryOK, lets wrap this up for this week.18:29
regXboiyes - let's go BP on this one18:29
mesteryI think we're all focused on BP review at this point.18:29
vinay_yadhavregXboi: Can you please leave your comment on the spec18:29
pgpustenant isolation is different but network sharing yes from that perspeactive, logical noverlays are allocated to tennat can be restricted to tenant to avoid security risks for those tenents who desire it18:29
regXboivinay_yadhav: yes18:29
banixbye all18:29
mesteryPlease keep the momentum up, and I'll see if we can focus some attention on service BPs at the Neutron meeting on MOnday.18:29
mesteryThanks!18:29
s3wongbye18:29
mestery#endmeeting18:29
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:29
openstackMeeting ended Wed Jun  4 18:29:47 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-06-04-17.30.html18:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-06-04-17.30.txt18:29
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-06-04-17.30.log.html18:29
anil_raoThanks18:29
vinay_yadhavbye18:30
vinay_yadhavthanx18:30
*** natarajk has quit IRC18:30
beyounn1Sridar, are you there?18:30
SridarKHi beyounn118:30
regXboiall: I didn't get a chance to put in minutes18:30
regXboibut I will leave comments in review on 6/1018:30
regXboiI'm ooo 6/11-6/16 (needed pto)18:30
SridarKbeyounn1: gduan and others also cannot make the mtg today18:30
beyounn1I know, Gary is on traveling18:31
*** regXboi has left #openstack-meeting-318:31
beyounn1SridarK, I think we only need to get review moving18:31
SridarKif Karthik and any one else interested in FWaaS we can have the mtg - Sumit asked me to run in case we have a quorum18:31
beyounn1Sridark: Ok18:32
*** badveli has joined #openstack-meeting-318:32
SridarKbeyounn1: yes - thanks for addressing my comments - i am good - just want to make sure we are all ok on the 1:1 mapping btwn serv obj and serv grp18:32
*** sarob has joined #openstack-meeting-318:32
beyounn1SridarK: Yes, it is 1:118:32
beyounn1SridarK: BTW-- do you know who should look at code review if we are fixing Horizon FWaaS bug?18:33
SridarKbeyounn1: just want to make sure that we are not locked into that - so we are good18:33
*** s3wong has quit IRC18:33
SridarKbeyounn1: i was going to reach out to some Horizon folks in our team to see if then can comment18:33
beyounn1SridarK, I mentioned in the BP, 1:1 is only for simplicity, we can add M:N later18:34
beyounn1SridarK, great!!, we have one customer is waiting on the fix :-)18:35
SridarKbeyounn1: yes hopefully that will not get us into a backward compat issue - once we clarify we are good18:35
SridarKthen we can get some core attention18:35
SridarKbeyounn1: ok18:35
beyounn1SridarK, for the backward compat, I think what we need to open up later is to change "service_group" to "service_groups" in the service object18:36
beyounn1How can we get core attention?18:36
beyounn1Show I bring this the mestry?18:36
beyounn1s/mestry/mestery/18:37
SridarKbeyounn1: - Since Gary and i have reviewed once Sumit is back we can get this18:37
beyounn1No, I was talking about Horizon bug18:37
beyounn1Since you mentioned "core attention" on the horizon bug18:38
SridarKbeyounn1: ok - let me ask our Horizon guy and get back18:38
beyounn1Great!!18:38
beyounn1and Thanks!!18:38
SridarKbeyounn1: i was talking abt BP's18:38
SridarK:-)18:38
beyounn1Understood18:38
*** emaganap has quit IRC18:39
beyounn1Ok, it seems that only you and me are here18:39
SridarKthe plan was to have mestery attend so we can clarify on priorities - we can punt that to next week when sumit is back18:39
beyounn1That is better18:39
badvelihello all18:40
SridarKbeyounn1: yes if nothing else - since no one is around today - we can wrap and get back to usual schedule next week18:40
beyounn1Hi18:40
beyounn1SridarK, btw-- we have a new member badveli18:40
*** emagana has joined #openstack-meeting-318:40
beyounn1He will also work on FWaaS18:40
badvelihello sridar18:40
SridarKbeyounn1: oh ok did not realize ok great18:41
badvelithanks beyounn118:41
beyounn1He may take on my current service group works18:41
SridarKhi badveli18:41
SridarKok18:41
badvelihello sridar18:41
badvelinice to meet you18:41
beyounn1OK, I think we can wrap it up early then18:42
SridarKbadveli: in addition to gduan & beyounn1 - pls feel free to reach out if any questions18:42
SridarKbeyounn1: yes lets do that18:42
badvelithanks sridar18:42
*** rkukura has left #openstack-meeting-318:42
SridarKok then next week18:42
beyounn1Ok, have a good day guys18:42
SridarKbye18:42
beyounn1Bye18:42
*** jcoufal has quit IRC18:42
badvelihave a good day and nice to talk to you, thanks18:43
*** zehicle_at_dell has quit IRC18:43
*** jmsoares has quit IRC18:43
*** anil_rao has left #openstack-meeting-318:48
*** vinay_yadhav has quit IRC18:48
*** OSM has quit IRC18:49
*** ttrifonov_zZzz is now known as ttrifonov18:49
*** jackib has joined #openstack-meeting-318:50
*** jackib_ has quit IRC18:52
*** msundara has quit IRC19:04
*** msundara has joined #openstack-meeting-319:05
*** kenhui1 has quit IRC19:07
*** zehicle_at_dell has joined #openstack-meeting-319:07
*** jackib has quit IRC19:08
*** emaganap has joined #openstack-meeting-319:12
*** emagana has quit IRC19:14
*** otherwiseguy has quit IRC19:23
*** pcm_ has left #openstack-meeting-319:26
*** cjellick_ has quit IRC19:27
*** cjellick has joined #openstack-meeting-319:28
*** Sukhdev has quit IRC19:33
*** jamie_h has quit IRC19:33
*** nati_uen_ has quit IRC19:33
*** shivharis has quit IRC19:38
*** Sukhdev has joined #openstack-meeting-319:38
*** nati_ueno has joined #openstack-meeting-319:39
*** safchain has joined #openstack-meeting-319:48
*** sarob has quit IRC19:49
*** HenryG has quit IRC19:51
*** otherwiseguy has joined #openstack-meeting-319:53
*** msundara has quit IRC19:57
*** nati_ueno has quit IRC20:04
*** nati_uen_ has joined #openstack-meeting-320:07
*** nati_ueno has joined #openstack-meeting-320:09
*** nati_uen_ has quit IRC20:10
*** msundara has joined #openstack-meeting-320:13
*** nedbat has joined #openstack-meeting-320:17
*** pgpus has quit IRC20:17
*** nedbat_ has quit IRC20:18
*** mwagner_lap has quit IRC20:20
*** jackib has joined #openstack-meeting-320:29
*** emaganap has quit IRC20:29
*** armax has quit IRC20:36
*** emagana has joined #openstack-meeting-320:41
*** jackib has quit IRC20:41
*** jackib has joined #openstack-meeting-320:41
*** TravT has joined #openstack-meeting-320:44
*** armax has joined #openstack-meeting-320:45
*** sarob has joined #openstack-meeting-320:49
*** SridarK has quit IRC20:54
*** kenhui has joined #openstack-meeting-321:00
*** mfer has quit IRC21:05
*** mfer has joined #openstack-meeting-321:06
*** mfer has quit IRC21:11
*** emaganap has joined #openstack-meeting-321:12
*** sarob_ has joined #openstack-meeting-321:12
*** emagana has quit IRC21:14
*** ericpeterson has joined #openstack-meeting-321:15
*** sarob has quit IRC21:15
*** badveli has quit IRC21:17
*** lblanchard has quit IRC21:23
*** nati_ueno has quit IRC21:26
*** julim has quit IRC21:32
*** kenhui has quit IRC21:32
*** armax has left #openstack-meeting-321:33
*** Sukhdev has quit IRC21:38
*** peristeri has quit IRC21:44
*** msundara has quit IRC21:49
*** MaxV has joined #openstack-meeting-321:51
*** ivar-lazzaro has joined #openstack-meeting-321:54
*** markmcclain has joined #openstack-meeting-321:58
*** MaxV has quit IRC21:58
*** jgrimm has quit IRC21:59
*** nedbat has quit IRC22:00
*** sarob_ has quit IRC22:04
*** sarob has joined #openstack-meeting-322:04
*** carl_baldwin has quit IRC22:05
*** jtomasek has quit IRC22:10
*** ttrifonov is now known as ttrifonov_zZzz22:11
*** sarob has quit IRC22:11
*** kenhui1 has joined #openstack-meeting-322:16
*** emaganap has quit IRC22:22
*** kenhui1 has quit IRC22:27
*** otherwiseguy has quit IRC22:30
*** msundara has joined #openstack-meeting-322:30
*** banix has quit IRC22:38
*** gothicmindfood has left #openstack-meeting-322:40
*** MaxV has joined #openstack-meeting-322:44
*** ericpeterson has quit IRC22:47
*** sarob has joined #openstack-meeting-322:51
*** thomasem_ has quit IRC22:58
*** sarob_ has joined #openstack-meeting-323:04
*** sarob has quit IRC23:07
*** markmcclain has quit IRC23:08
*** msundara has quit IRC23:12
*** MaxV has quit IRC23:16
*** sarob_ has quit IRC23:23
*** tomoe_ has joined #openstack-meeting-323:32
*** Sukhdev has joined #openstack-meeting-323:45
*** jaypipes has quit IRC23:48
*** Sukhdev has quit IRC23:51
*** Sukhdev has joined #openstack-meeting-323:52
*** Sukhdev has quit IRC23:56
*** igordcard has quit IRC23:59

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