| *** wchrisj has joined #openstack-meeting-3 | 00:05 | |
| *** wchrisj has quit IRC | 00:09 | |
| *** cjellick has quit IRC | 00:14 | |
| *** cjellick has joined #openstack-meeting-3 | 00:14 | |
| *** cjellick has quit IRC | 00:18 | |
| *** sweston has quit IRC | 00:21 | |
| *** TravT has quit IRC | 00:54 | |
| *** alexpilotti has quit IRC | 00:54 | |
| *** mfer has joined #openstack-meeting-3 | 00:58 | |
| *** wchrisj has joined #openstack-meeting-3 | 01:06 | |
| *** SumitNaiksatam has quit IRC | 01:10 | |
| *** wchrisj has quit IRC | 01:10 | |
| *** mestery has quit IRC | 01:15 | |
| *** baojg has joined #openstack-meeting-3 | 01:18 | |
| *** eguz has joined #openstack-meeting-3 | 01:20 | |
| *** eguz has quit IRC | 01:20 | |
| *** eghobo has quit IRC | 01:24 | |
| *** banix has joined #openstack-meeting-3 | 01:24 | |
| *** mestery has joined #openstack-meeting-3 | 01:26 | |
| *** wchrisj has joined #openstack-meeting-3 | 01:43 | |
| *** wchrisj has quit IRC | 01:48 | |
| *** wchrisj has joined #openstack-meeting-3 | 01:54 | |
| *** wchrisj has quit IRC | 01:59 | |
| *** SumitNaiksatam has joined #openstack-meeting-3 | 02:04 | |
| *** devlaps has quit IRC | 02:21 | |
| *** mfer has quit IRC | 02:32 | |
| *** coolsvap|afk is now known as coolsvap | 02:33 | |
| *** sweston has joined #openstack-meeting-3 | 02:41 | |
| *** chuckC has joined #openstack-meeting-3 | 02:41 | |
| *** chuckC has quit IRC | 02:45 | |
| *** mfer has joined #openstack-meeting-3 | 02:47 | |
| *** sankarshan is now known as sankarshan_away | 02:47 | |
| *** chuckC has joined #openstack-meeting-3 | 02:47 | |
| *** enykeev has quit IRC | 02:48 | |
| *** mfer has quit IRC | 02:48 | |
| *** chuckC has quit IRC | 02:48 | |
| *** chuckC has joined #openstack-meeting-3 | 02:49 | |
| *** enykeev has joined #openstack-meeting-3 | 02:50 | |
| *** chuckC has quit IRC | 02:50 | |
| *** chuckC has joined #openstack-meeting-3 | 02:51 | |
| *** mfer has joined #openstack-meeting-3 | 02:53 | |
| *** mfer has quit IRC | 02:53 | |
| *** wchrisj has joined #openstack-meeting-3 | 02:55 | |
| *** wchrisj has quit IRC | 02:57 | |
| *** wchrisj_ has joined #openstack-meeting-3 | 02:57 | |
| *** wchrisj_ has quit IRC | 03:01 | |
| *** cjellick has joined #openstack-meeting-3 | 03:07 | |
| *** chuckC has quit IRC | 03:16 | |
| *** sankarshan_away is now known as sankarshan | 03:19 | |
| *** david-lyle has joined #openstack-meeting-3 | 03:19 | |
| *** eghobo has joined #openstack-meeting-3 | 03:48 | |
| *** david-lyle has quit IRC | 03:54 | |
| *** banix has quit IRC | 04:06 | |
| *** eghobo has quit IRC | 04:10 | |
| *** eghobo has joined #openstack-meeting-3 | 04:10 | |
| *** eguz has joined #openstack-meeting-3 | 04:13 | |
| *** eghobo has quit IRC | 04:17 | |
| *** coolsvap is now known as coolsvap|afk | 04:45 | |
| *** coolsvap|afk is now known as coolsvap | 04:57 | |
| *** baojg has quit IRC | 05:01 | |
| *** baojg has joined #openstack-meeting-3 | 05:02 | |
| *** baojg_ has joined #openstack-meeting-3 | 05:04 | |
| *** baojg has quit IRC | 05:08 | |
| *** markmcclain has joined #openstack-meeting-3 | 05:20 | |
| *** coolsvap is now known as coolsvap|afk | 05:28 | |
| *** markmcclain has quit IRC | 05:30 | |
| *** coolsvap|afk is now known as coolsvap | 05:36 | |
| *** cjellick has quit IRC | 05:41 | |
| *** cjellick has joined #openstack-meeting-3 | 05:42 | |
| *** cjellick has quit IRC | 05:46 | |
| *** jtomasek has joined #openstack-meeting-3 | 06:00 | |
| *** ttrifonov_zZzz is now known as ttrifonov | 06:01 | |
| *** jtomasek has quit IRC | 06:17 | |
| *** eguz has quit IRC | 06:42 | |
| *** ttrifonov is now known as ttrifonov_zZzz | 06:45 | |
| *** lsmola has joined #openstack-meeting-3 | 06:48 | |
| *** jtomasek has joined #openstack-meeting-3 | 07:03 | |
| *** jcoufal has joined #openstack-meeting-3 | 07:08 | |
| *** ttrifonov_zZzz is now known as ttrifonov | 07:13 | |
| *** mrunge has joined #openstack-meeting-3 | 07:23 | |
| *** nacim has joined #openstack-meeting-3 | 07:23 | |
| *** safchain has joined #openstack-meeting-3 | 07:58 | |
| *** nacim has quit IRC | 08:11 | |
| *** baojg_ has quit IRC | 08:12 | |
| *** baojg has joined #openstack-meeting-3 | 08:13 | |
| *** baojg_ has joined #openstack-meeting-3 | 08:15 | |
| *** nacim has joined #openstack-meeting-3 | 08:15 | |
| *** baojg has quit IRC | 08:17 | |
| *** amotoki has joined #openstack-meeting-3 | 08:18 | |
| *** sankarshan is now known as sankarshan_away | 08:40 | |
| *** baojg_ has quit IRC | 09:00 | |
| *** baojg has joined #openstack-meeting-3 | 09:00 | |
| *** banix has joined #openstack-meeting-3 | 09:04 | |
| *** jcoufal has quit IRC | 09:14 | |
| *** jamie_h has joined #openstack-meeting-3 | 09:25 | |
| *** alexpilotti has joined #openstack-meeting-3 | 09:46 | |
| *** sankarshan_away is now known as sankarshan | 09:53 | |
| *** baojg has quit IRC | 10:00 | |
| *** baojg has joined #openstack-meeting-3 | 10:00 | |
| *** mrunge has quit IRC | 10:01 | |
| *** banix has quit IRC | 10:08 | |
| *** baojg_ has joined #openstack-meeting-3 | 10:15 | |
| *** jcoufal has joined #openstack-meeting-3 | 10:18 | |
| *** baojg has quit IRC | 10:18 | |
| *** nacim has quit IRC | 10:21 | |
| *** overlayer has joined #openstack-meeting-3 | 10:37 | |
| *** overlayer has quit IRC | 10:37 | |
| *** coolsvap is now known as coolsvap|afk | 10:38 | |
| *** nacim has joined #openstack-meeting-3 | 10:40 | |
| *** mrunge has joined #openstack-meeting-3 | 10:55 | |
| *** jamielennox is now known as jamielennox|away | 11:02 | |
| *** baojg_ has quit IRC | 11:02 | |
| *** baojg has joined #openstack-meeting-3 | 11:02 | |
| *** baojg has quit IRC | 11:07 | |
| *** MaxV has joined #openstack-meeting-3 | 11:12 | |
| *** mwagner_lap has quit IRC | 11:19 | |
| *** coolsvap|afk is now known as coolsvap | 12:01 | |
| *** mrunge has quit IRC | 12:24 | |
| *** alexpilotti has quit IRC | 12:35 | |
| *** alexpilotti has joined #openstack-meeting-3 | 12:41 | |
| *** lblanchard has joined #openstack-meeting-3 | 12:55 | |
| *** mwagner_lap has joined #openstack-meeting-3 | 12:59 | |
| *** mfer has joined #openstack-meeting-3 | 13:02 | |
| *** baojg has joined #openstack-meeting-3 | 13:07 | |
| *** baojg has quit IRC | 13:11 | |
| *** haleyb has quit IRC | 13:20 | |
| *** jamie_h has quit IRC | 13:28 | |
| *** jamie_h has joined #openstack-meeting-3 | 13:29 | |
| *** jamie_h has quit IRC | 13:31 | |
| *** ttrifonov is now known as ttrifonov_zZzz | 13:36 | |
| *** peristeri has joined #openstack-meeting-3 | 13:38 | |
| *** jamie_h has joined #openstack-meeting-3 | 13:38 | |
| *** xuhanp has joined #openstack-meeting-3 | 13:43 | |
| *** ttrifonov_zZzz is now known as ttrifonov | 13:54 | |
| *** wchrisj has joined #openstack-meeting-3 | 13:56 | |
| *** ttrifonov is now known as ttrifonov_zZzz | 14:08 | |
| *** ttrifonov_zZzz is now known as ttrifonov | 14:09 | |
| *** markmcclain has joined #openstack-meeting-3 | 14:14 | |
| *** MaxV has quit IRC | 14:14 | |
| *** ttrifonov is now known as ttrifonov_zZzz | 14:20 | |
| *** ttrifonov_zZzz is now known as ttrifonov | 14:21 | |
| *** julim has joined #openstack-meeting-3 | 14:26 | |
| *** markmcclain has quit IRC | 14:27 | |
| *** ttrifonov is now known as ttrifonov_zZzz | 14:28 | |
| *** markmcclain has joined #openstack-meeting-3 | 14:29 | |
| *** ttrifonov_zZzz is now known as ttrifonov | 14:30 | |
| *** ttrifonov is now known as ttrifonov_zZzz | 14:35 | |
| *** ttrifonov_zZzz is now known as ttrifonov | 14:37 | |
| *** otherwiseguy has joined #openstack-meeting-3 | 14:39 | |
| *** TravT has joined #openstack-meeting-3 | 14:40 | |
| *** lblanchard has quit IRC | 14:46 | |
| *** lblanchard has joined #openstack-meeting-3 | 14:51 | |
| *** ttrifonov is now known as ttrifonov_zZzz | 14:52 | |
| *** ttrifonov_zZzz is now known as ttrifonov | 14:54 | |
| *** enykeev has quit IRC | 14:54 | |
| *** david-lyle has joined #openstack-meeting-3 | 14:55 | |
| *** TravT has quit IRC | 14:56 | |
| *** jcoufal has quit IRC | 14:58 | |
| *** jcoufal has joined #openstack-meeting-3 | 15:01 | |
| *** TravT has joined #openstack-meeting-3 | 15:02 | |
| *** banix has joined #openstack-meeting-3 | 15:02 | |
| *** julim has quit IRC | 15:11 | |
| *** otherwis_ has joined #openstack-meeting-3 | 15:20 | |
| *** otherwiseguy has quit IRC | 15:23 | |
| *** amrith is now known as amrith-is-awol | 15:25 | |
| *** baojg has joined #openstack-meeting-3 | 15:26 | |
| *** otherwis_ is now known as otherwiseguy | 15:26 | |
| *** samchoi has joined #openstack-meeting-3 | 15:28 | |
| mfer | #startmeeting openstack-sdk-php | 15:30 |
|---|---|---|
| openstack | Meeting started Wed Apr 23 15:30:56 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 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:30 |
| *** openstack changes topic to " (Meeting topic: openstack-sdk-php)" | 15:30 | |
| openstack | The meeting name has been set to 'openstack_sdk_php' | 15:31 |
| *** ycombinator has joined #openstack-meeting-3 | 15:31 | |
| mfer | Please state your name and any relevant association. | 15:31 |
| mfer | Matt Farina, HP | 15:31 |
| samchoi | Sam Choi, HP | 15:31 |
| ycombinator | Shaunak Kashyap, Rackspace | 15:31 |
| jamie_h | Jamie Hannaford, Rackspace | 15:31 |
| mfer | Welcome folks | 15:32 |
| mfer | #topic Agenda | 15:32 |
| *** openstack changes topic to "Agenda (Meeting topic: openstack-sdk-php)" | 15:32 | |
| mfer | #link https://wiki.openstack.org/wiki/Meetings/OpenStack-SDK-PHP | 15:32 |
| mfer | 1. Intro to the PHP SDK if there is anyone new? (mfer) | 15:32 |
| mfer | 2. Near term roadmap (mfer) | 15:32 |
| mfer | 3. Blueprints / Bugs / Reviews (mfer) | 15:32 |
| mfer | 5. Open Discussion (mfer) | 15:32 |
| mfer | 4. JSON Schema (jamiehannaford) | 15:32 |
| mfer | is there anything else that should be added before we proceed? | 15:32 |
| jamie_h | I have nothing | 15:33 |
| ycombinator | me too | 15:33 |
| *** cjellick has joined #openstack-meeting-3 | 15:33 | |
| mfer | I think we can skip #1 because no one is new here. | 15:33 |
| mfer | #topic Near term roadmap | 15:33 |
| *** openstack changes topic to "Near term roadmap (Meeting topic: openstack-sdk-php)" | 15:33 | |
| mfer | #link https://wiki.openstack.org/wiki/OpenStack-SDK-PHP#Short_Term_Roadmap | 15:34 |
| jamie_h | I have 1-2 things to discuss about near-term roadmap | 15:34 |
| mfer | I have this on the agenda because I had an action to link the items on the roadmap to the blurprints which I did | 15:34 |
| mfer | jamie_h what are they? | 15:34 |
| jamie_h | I've started work on the codebase yesterday and my immediate priority was addressing the tests. At the moment there seems to be 2 problems: the first is that integration tests (hitting the API) are intermingled with unit tests, which is causing incredible slowness. The second is that many of the integration tests initially didn't work with Rackspace APIs | 15:35 |
| mfer | jamie_h i'm aware of a couple issues that would cause problems. They are listed as bugs and samchoi is working on them right now | 15:36 |
| mfer | was there something else beyond that? | 15:36 |
| jamie_h | The patch I've submitted fixes the second issue, i.e. hotfixes which make tests work with Rackspace. I thought that was important before all other work commenced | 15:36 |
| jamie_h | I can liaise with Sam about other stuff he's working on | 15:36 |
| samchoi | sure, it's still early here so I haven't seen the changes yet. Will look into it shortly | 15:37 |
| mfer | jamie_h we want the full test suite to work. for our testing purposes we'll be using devstack and our setup. devstack is is the openstack reference point. | 15:37 |
| mfer | jamie_h we do want all the tests passing | 15:37 |
| jamie_h | mfer yes, but I'm talking about splitting up integration tests from unit tests. Unit tests should not hit the API | 15:38 |
| jamie_h | They should mock out responses or dependent classes | 15:38 |
| jamie_h | Right now, that's not happening | 15:38 |
| mfer | most of the test suite is integration testing | 15:38 |
| jamie_h | exactly | 15:38 |
| jamie_h | Today I've split them out into separate phpunit groups | 15:38 |
| mfer | can we carve out some time to talk handling this at the openstack summit? | 15:39 |
| jamie_h | mfer I won't be at the summit, I'm at a talk in Italy then | 15:39 |
| mfer | ah, doh | 15:39 |
| ycombinator | mfer: same here, I'm at a talk in NYC | 15:39 |
| mfer | i'll miss meeting you two face to face | 15:39 |
| ycombinator | yeah, its a bummer | 15:39 |
| jamie_h | The main takeaway I have is that the initial code I've submitted in that patch (just the test fixes) is required for all other work to continue. I can look into extracting out the copyright headers into a separate patch | 15:40 |
| jamie_h | mfer is that okay with you? extracting the copyright stuff out | 15:40 |
| mfer | possibly. can you file a bug for this and detail out the issue as well. then link the commit to the bug. | 15:41 |
| jamie_h | sure | 15:42 |
| mfer | thanks | 15:42 |
| jamie_h | would it be easier to delete the current patch in Gerrit? Can that happen? | 15:42 |
| mfer | in the commit message on a link put Closes-Bug: 123 where 123 is the number | 15:42 |
| mfer | you can abandon a patch set | 15:43 |
| *** ttrifonov is now known as ttrifonov_zZzz | 15:43 | |
| mfer | if you do the closes bug thing it will become a link to the bug in the review. it's useful for navigating the system | 15:43 |
| mfer | jamie_h you said there was 1-2 things. is there something else? | 15:43 |
| jamie_h | That's all I had | 15:44 |
| mfer | anything else about the near term roadmap? | 15:44 |
| ycombinator | I'm good | 15:44 |
| jamie_h | Me too | 15:44 |
| *** Sukhdev has joined #openstack-meeting-3 | 15:44 | |
| mfer | samchoi are you good? | 15:45 |
| samchoi | I'm wondering what the priorities are, for the short term roadmap, in light of the testing issues jamie_h brought up | 15:45 |
| samchoi | but we can save it for later | 15:45 |
| samchoi | maybe open disc | 15:45 |
| mfer | samchoi I think there is always a priority to have the system working. in the open discussion i'd like to now talk about testing. | 15:46 |
| mfer | after than I think the priorities are numbered at the moment | 15:46 |
| samchoi | ok, great | 15:46 |
| mfer | does anyone disagree with the ordering? | 15:46 |
| jamie_h | can we have json-schema before open discussion? since it follows on from blueprints | 15:46 |
| samchoi | I would bump up the documentation a bit higher. I believe updating docs would be very helpful for newer contributors. | 15:47 |
| mfer | jamie_h yes. i re-numbered above but slipped up where i hit enter | 15:47 |
| ycombinator | samchoi: are you referring to user-facing docs (#8) or phpdoc (#3)? | 15:47 |
| samchoi | user facing docs ycombinator | 15:47 |
| samchoi | parts of the doc are out of date, due to a slew of recent changes | 15:48 |
| ycombinator | that's good because I've started working on them :) | 15:48 |
| ycombinator | I'll report in the BP section | 15:48 |
| samchoi | thanks ycombinator | 15:48 |
| mfer | samchoi i'm not sure we'll get many more contributors until after the first basic usable release is out. | 15:48 |
| mfer | ycombinator btw, thanks for taking this on now | 15:48 |
| jamie_h | me neither | 15:48 |
| mfer | samchoi or I can somehow drum up some others at the summit. but, i'm not counting on it | 15:48 |
| ycombinator | mfer: do you feel I should switch to something higher up on the list? | 15:48 |
| ycombinator | since user-facing docs are #7 | 15:49 |
| samchoi | well, either for new contributors or even for jamie_h and ycombinator since they are getting into the codebase now | 15:49 |
| samchoi | I'd hate for them to get into outdated docs, that's all | 15:49 |
| mfer | ycombinator while it's a lower priority I still consider it a priority and a good chunk of work | 15:49 |
| ycombinator | okay, thanks, I'll keep on keeping on | 15:49 |
| mfer | priority doesn't necessairly suggest order we tackle | 15:49 |
| mfer | though, maybe it should :) | 15:49 |
| ycombinator | bingo, that was my confusion | 15:50 |
| mfer | in any case, ycombinator i was happy to see you work on that | 15:50 |
| samchoi | same | 15:50 |
| ycombinator | cool cool | 15:50 |
| mfer | are we ready to move on? | 15:50 |
| jamie_h | yeah | 15:50 |
| samchoi | yes | 15:50 |
| ycombinator | yes | 15:50 |
| mfer | #topic Blueprints / Bugs / Reviews | 15:50 |
| *** openstack changes topic to "Blueprints / Bugs / Reviews (Meeting topic: openstack-sdk-php)" | 15:50 | |
| mfer | #link https://review.openstack.org/#/q/status:open+project:stackforge/openstack-sdk-php,n,z | 15:51 |
| mfer | there are currently two reviews listed | 15:51 |
| mfer | The .gitignore one I was reviewing when the meeting started | 15:51 |
| mfer | that is https://review.openstack.org/#/c/89528/ | 15:51 |
| mfer | jamie_h what does the .idea directory work with? | 15:51 |
| jamie_h | mfer PhpStorm | 15:51 |
| jamie_h | it's becoming increasingly more common to add .idea to your .gitignore - I looked at a handful of other projects | 15:52 |
| mfer | ok, i'll poke around at that shortly. | 15:53 |
| mfer | samchoi can you take a look at that as well? | 15:53 |
| samchoi | sure mfer | 15:53 |
| mfer | great. | 15:53 |
| mfer | the other issue was https://review.openstack.org/#/c/89785/ | 15:53 |
| mfer | it contains two separate changes so I've asked that it be broken up. | 15:54 |
| jamie_h | yep | 15:54 |
| jamie_h | copyright issue needs further investigation | 15:54 |
| jamie_h | and the test fixes need consultation with Sam and a bug report | 15:54 |
| *** rossella_s has joined #openstack-meeting-3 | 15:54 | |
| mfer | the copyright headers portion is a legal thing. that might take a little time to track down guidance on. these are logically separate as well | 15:54 |
| mfer | jamie_h if you hit any roadblocks on the bug portion please be sure to ping me | 15:55 |
| jamie_h | mfer will do. I'll probably ping you about closing the existing patch too | 15:55 |
| *** eghobo has joined #openstack-meeting-3 | 15:55 | |
| mfer | ok | 15:55 |
| mfer | any other discussion on that one? | 15:55 |
| jamie_h | not from me | 15:56 |
| mfer | i have one other. https://review.openstack.org/#/c/88315/ | 15:56 |
| mfer | this change to infra would notify us in the sdk room when something went into review | 15:56 |
| mfer | it's not landed yet but I thought it was worth automating | 15:56 |
| ycombinator | yeah, I've seen it in solum | 15:56 |
| ycombinator | I'm in favor of it | 15:56 |
| jamie_h | also, another thing: what does Jenkins actually do when it checks a patch? It doesn't seem to run any testsuite | 15:57 |
| mfer | unfortunately no. | 15:57 |
| samchoi | correct, there are no gate tests at the moment | 15:57 |
| jamie_h | is that something we can add in, or is out of our hands? | 15:57 |
| mfer | the current setup works for python stuff. other languages and we run into problems | 15:57 |
| mfer | it's out of our hands right now. i've spoken with the infra folks about it | 15:57 |
| mfer | out of our hands for now not forever | 15:58 |
| jamie_h | I think that should be the top priority issue with infra | 15:58 |
| mfer | I do too. but, alas it's not. | 15:58 |
| mfer | they have some bigger issues in the short term | 15:59 |
| ycombinator | mfer: without knowing how the github mirroring of git.openstack.org works, could we setup a post-push hook in github to run the tests using something like travis? | 15:59 |
| ycombinator | ... until infra gets php testing going | 15:59 |
| jamie_h | ycombinator that would activate the hook after it's been merged though. I guess it's better than nothing | 16:00 |
| *** amotoki_ has joined #openstack-meeting-3 | 16:00 | |
| ycombinator | yeah, its not perfect but its better than nothing, imo | 16:00 |
| mfer | ycombinator i'd like to do that. i've been holding off asking them much about it lately because of other priorities. i was going to bring up the issue again at or after the summit | 16:00 |
| mfer | other priorities for them that is | 16:00 |
| mfer | ycombinator if you want to chance down an alternative setup in the short term that would be good | 16:01 |
| ycombinator | ok, I'll investigate | 16:01 |
| ycombinator | thanks | 16:01 |
| mfer | there are currently two listed bugs http://bugs.launchpad.net/openstack-sdk-php | 16:01 |
| mfer | they are related and samchoi is working on them | 16:02 |
| jamie_h | samchoi I think I ran into the stream wrapper default region one | 16:02 |
| jamie_h | and fixed it by pulling the region value out of the context options | 16:02 |
| mfer | jamie_h i expected you would. i reported it thinking of you | 16:03 |
| jamie_h | :) | 16:03 |
| samchoi | mfer: jamie_h Yea the bugs aren't too bad, but I was holding off on submitting my changes until I have DevStack up and running | 16:03 |
| samchoi | so that I'm able to test against a reliable environment | 16:03 |
| mfer | gotcha | 16:03 |
| mfer | there are two blueprints in progress as well https://blueprints.launchpad.net/openstack-sdk-php | 16:03 |
| mfer | i've started the multiple api version one https://blueprints.launchpad.net/openstack-sdk-php/+spec/multiple-api-versions | 16:04 |
| mfer | there's a spec at https://wiki.openstack.org/wiki/OpenStack-SDK-PHP/Design/Multi-Version | 16:04 |
| mfer | did anyone want to have any discussion about this? | 16:04 |
| ycombinator | I've started (barely) the https://blueprints.launchpad.net/openstack-sdk-php/+spec/sphinx-docs one | 16:04 |
| ycombinator | process question: do we report progress about the BP here? | 16:04 |
| ycombinator | or how does that work? | 16:04 |
| jamie_h | mfer the blueprint you've referenced ties in heavily with schemas - are you happy with starting to write that code? | 16:05 |
| mfer | if you have something you want to talk about you can. but, this isnt' a standup | 16:05 |
| mfer | jamie_h yes. and i'm prepared for schema discussions | 16:05 |
| mfer | and how they relate | 16:05 |
| *** sweston has quit IRC | 16:05 | |
| jamie_h | okay, so everything falls into its own version directory. Nearly all of a service's functionality is defined by its schema file - right? | 16:05 |
| jamie_h | Which utilizes classes, etc. inside the version directory | 16:06 |
| mfer | this change doesn't do the schema portion. just the versions live in their own directories. it's a small change | 16:06 |
| jamie_h | ah okay | 16:06 |
| ycombinator | I have 2 questions about the sphinx docs BP but I'm holding off until the multiple-api-versions discussion is done | 16:06 |
| mfer | micro changes. that's why i'm happy schemas has it's own blueprint | 16:06 |
| jamie_h | so what would the directory structure look like? | 16:07 |
| jamie_h | src / Identity / v3.0 / | 16:07 |
| mfer | src / OpenStack / Identity / v3.0 / | 16:07 |
| *** otherwis_ has joined #openstack-meeting-3 | 16:07 | |
| *** otherwiseguy has quit IRC | 16:08 | |
| jamie_h | and inside 3.0 directory, would there be other standard folders? Is that covered in this blueprint? | 16:08 |
| jamie_h | like Iterator or Resource etc. | 16:08 |
| mfer | in that directory would be the thing to work with the service. this issue isn't dealing with what that thing is | 16:08 |
| jamie_h | okay | 16:08 |
| mfer | i'm intentionally keeping it vauge. the commit would keep the thing what's already in place. | 16:08 |
| mfer | and leave changes to the thing to come separately | 16:09 |
| jamie_h | which OpenStack services are you adding for now? Just Identity and Storage? | 16:09 |
| mfer | identity and storage is all. adding more would mean more refactoring. that's whey we didn't put more out there from the start | 16:09 |
| *** baojg has quit IRC | 16:09 | |
| *** devlaps has joined #openstack-meeting-3 | 16:09 | |
| jamie_h | Today I worked on moving to a standard workspace structure, pretty much as you've outlined above with Identity and Storage as separate directories | 16:10 |
| jamie_h | and common stuff (like transport, exceptions) in a Common directory | 16:10 |
| mfer | ok | 16:10 |
| jamie_h | How shall I continue with that work? Wait until you've submitted a patch and then rebase? | 16:11 |
| mfer | sure. if you work on the bugs with sam i'll have my bit in for review here by tomorrow | 16:11 |
| *** chuckC has joined #openstack-meeting-3 | 16:11 | |
| jamie_h | okay | 16:11 |
| mfer | or, your work day might end first :) | 16:12 |
| mfer | anything else or can we move on to ycombinators stuff? I'd like to have time for the json schema stuff | 16:12 |
| jamie_h | I have nothing else | 16:12 |
| mfer | and we have 18 mintues left | 16:12 |
| ycombinator | okay - | 16:12 |
| mfer | ycombinator what are your questions? | 16:12 |
| ycombinator | mine should be quick | 16:12 |
| ycombinator | 1. I've created a "spec" for the user facing docs here: https://wiki.openstack.org/wiki/OpenStack-SDK-PHP/UserFacingDocumentation | 16:12 |
| ycombinator | nothing ther eyet | 16:12 |
| *** otherwiseguy has joined #openstack-meeting-3 | 16:13 | |
| ycombinator | but: what is the process of getting all of your feedback on it? | 16:13 |
| *** safchain has quit IRC | 16:13 | |
| mfer | ycombinator you can email me, email the dev mailing list, and/or ping me in IRC | 16:13 |
| mfer | as soon as I see any of this come through I'll jump on it | 16:14 |
| mfer | I do hope that samchoi and jamie_h jump in with feedback as well | 16:14 |
| ycombinator | okay, so there's no way of having the discussion in the wiki directly | 16:14 |
| samchoi | we have a mailing list for the PHP SDK? Did I miss that | 16:14 |
| ycombinator | got it | 16:14 |
| jamie_h | ycombinator for now, maybe send it via e-mail to us all? | 16:14 |
| ycombinator | samchoi: its just openstack-dev with the openstack-sdk-php tag | 16:14 |
| mfer | samchoi no, all dev conversations go through the openstack dev list with a prefix for the project | 16:14 |
| samchoi | ah i see | 16:14 |
| samchoi | thanks | 16:14 |
| jamie_h | okay, mailing list it is | 16:14 |
| mfer | that's they way the openstack community does things | 16:14 |
| ycombinator | and question 2. based on Matt's and Anne's email responses to my questions, I'm going to focus on having Sphinx spit out HTML in a directory (like build/) for now | 16:14 |
| ycombinator | not worry about where they would be published eventually | 16:15 |
| mfer | good | 16:15 |
| ycombinator | I want to make sure everyone is okay with that scope for this BP | 16:15 |
| mfer | i'm ok with it | 16:15 |
| jamie_h | I'm happy with it | 16:15 |
| ycombinator | cool | 16:15 |
| samchoi | ok | 16:15 |
| ycombinator | thanks | 16:15 |
| ycombinator | that was it | 16:15 |
| mfer | great | 16:15 |
| mfer | if everyone is ok with it, lets move on to json schema | 16:15 |
| *** otherwis_ has quit IRC | 16:15 | |
| samchoi | sure | 16:16 |
| ycombinator | ok | 16:16 |
| mfer | #topic JSON Schema | 16:16 |
| *** openstack changes topic to "JSON Schema (Meeting topic: openstack-sdk-php)" | 16:16 | |
| mfer | jamie_h since this is your thing, can you present it? | 16:16 |
| jamie_h | Okay | 16:16 |
| jamie_h | So a few OpenStack services right now (Glance, Common, and possibly KeyStone) use json-schema to encapsulate data structures | 16:17 |
| jamie_h | The plan is to use json-schemas in the SDK as a way to define services like Swift, Nova, etc. | 16:17 |
| jamie_h | For example, HTTP operations will be clearly defined - with expected parameters, HTTP method types, URLs, etc. This avoids writing hundreds of lines of userland code which duplicates common functionality | 16:18 |
| jamie_h | It also serves as living documentation - allowing end-users to understand exactly what they're expected to enter for operations | 16:19 |
| jamie_h | Recently I've been working a light-weight library that allows schema files to be validated and consumed against live data | 16:19 |
| *** xuhanp has quit IRC | 16:19 | |
| ycombinator | jamie_h: dumb question: will this account for variances when certain services use PUT instead of POST to do resource creation, etc. | 16:19 |
| ycombinator | s/account/allow | 16:19 |
| jamie_h | yes, exactly. All API operations have their own entry, and allows for differences, say, in verb types | 16:20 |
| jamie_h | we can also define models. Say for a Server, or for a DataObject | 16:20 |
| jamie_h | so instead of writing a Server class, we define it in a few lines of JSON | 16:20 |
| mfer | jamie_h i have a bunch of questions when you're ready | 16:20 |
| jamie_h | sure | 16:21 |
| mfer | jamie_h in your library you deal with validation. in your concepts how do you deal with the difference between testing and usage when it comes to validation? | 16:21 |
| jamie_h | can you elaborate what you mean by "testing" and "usage"? | 16:22 |
| jamie_h | do you mean how strict we'll be when using invalid schemas? | 16:22 |
| *** tjones has joined #openstack-meeting-3 | 16:23 | |
| mfer | this isn't user submitted data. we don't need to spend the time validating it every time the SDK uses it. it's not going to change over time. can you skip validation in use and do it as part of the test suite? | 16:23 |
| mfer | i'm concerned with keeping things simple and code execution paths | 16:24 |
| jamie_h | that's a good idea. Right now, it doesn't skip validation - but it's something I can look it when incorporating into the SDK | 16:24 |
| mfer | when working with json schema files, how would you do debugging? | 16:24 |
| jamie_h | debugging errors with schemas? | 16:24 |
| *** markmcclain has quit IRC | 16:24 | |
| mfer | that's one case | 16:25 |
| jamie_h | so right now you have a ErrorHandler which collects validation errors | 16:25 |
| mfer | to understand exactly what's going on and where. it's not in a line of code | 16:25 |
| mfer | what happens if it's not a validation issue | 16:25 |
| mfer | for example, the call goes through the proxy and the proxy changes things | 16:25 |
| mfer | now you need to know what's going on and where it's happening | 16:25 |
| jamie_h | There are two conceivable types of error: when a schema is itself invalid, or when a chunk of API data does not validate against a schema | 16:26 |
| jamie_h | Is that what you're referring to? I don't know what you mean by proxy changes | 16:26 |
| mfer | i'm thinking of the practical workflow of debugging. | 16:27 |
| jamie_h | the error handler collects the errors, and it's up to you how you want to handle them. right now they're buffered, and i collect them after the validation process over a foreach | 16:27 |
| mfer | when something normally encompassed in a method is now in a schema... what's that experience like? | 16:27 |
| jamie_h | alternatively, you can emit them over STDOUT | 16:27 |
| jamie_h | or save to a log file - it depends on how you implement ErrorHandlerInterface | 16:28 |
| mfer | that assumes the issue is a schema not validating. the schema could be proper and the requests could still fail | 16:28 |
| jamie_h | mfer when it comes to understanding normal SDK workflow debugging, I plead ignorance - I haven't got that far yet | 16:28 |
| mfer | ok. | 16:28 |
| jamie_h | If the request fails it indicates that the request data is invalid | 16:28 |
| jamie_h | in which case you'll get precise reasons why | 16:28 |
| mfer | given the time and the next meeting starting I think we need to take this offline. can we move this to an email? | 16:29 |
| jamie_h | okay | 16:29 |
| samchoi | please cc the rest of us, I'm interested as well | 16:29 |
| ycombinator | jamie_h is there a BP + spec for this? | 16:29 |
| mfer | i'm sorry to interrupt. i'd love to talk about this for a long time. i'll try to send it out later today | 16:29 |
| jamie_h | https://blueprints.launchpad.net/openstack-sdk-php/+spec/service-json-schema | 16:29 |
| mfer | samchoi i'll send it to the openstack-dev list. but, i'll cc you too. make sure you're getting that list | 16:29 |
| mfer | #link https://blueprints.launchpad.net/openstack-sdk-php/+spec/service-json-schema | 16:30 |
| ycombinator | thanks jamie_h | 16:30 |
| mfer | ok, i'm calling the meeting so the next one can get started | 16:30 |
| mfer | thanks for coming | 16:30 |
| ycombinator | thanks | 16:30 |
| mfer | #endmeeting | 16:30 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 16:30 | |
| openstack | Meeting ended Wed Apr 23 16:30:27 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:30 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack_sdk_php/2014/openstack_sdk_php.2014-04-23-15.30.html | 16:30 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_sdk_php/2014/openstack_sdk_php.2014-04-23-15.30.txt | 16:30 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/openstack_sdk_php/2014/openstack_sdk_php.2014-04-23-15.30.log.html | 16:30 |
| tjones | #start meeting nova bug scrub | 16:30 |
| tjones | #startmeeting nova bug scrub | 16:30 |
| openstack | Meeting started Wed Apr 23 16:30:56 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 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:30 |
| *** openstack changes topic to " (Meeting topic: nova bug scrub)" | 16:31 | |
| openstack | The meeting name has been set to 'nova_bug_scrub' | 16:31 |
| tjones | hi anyone around? | 16:31 |
| tjones | guess i'll get started anyway | 16:32 |
| tjones | #link https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=NEW | 16:32 |
| wendar | \o | 16:34 |
| *** jcoufal has quit IRC | 16:35 | |
| tjones | hi wendar | 16:35 |
| tjones | no one here but you and me | 16:36 |
| tjones | :-D | 16:36 |
| wendar | tjones: hi! sorry I've had a busy few weeks, got sucked into a lot of internal strategy stuff | 16:36 |
| tjones | no worries | 16:36 |
| wendar | tjones: hoping we can start knocking out some of these bugs :) | 16:36 |
| tjones | yeah | 16:36 |
| wendar | I postponed a lot of the oslo and testing stuff, for freeze, but should be able to spin that up again now. | 16:37 |
| tjones | great! | 16:37 |
| tjones | so i talked to mikal last night and he wants me to continue doing this. he'd like to get info on bugs that are lingering because of lack of review. so i am going to get a script going for that. i have one for vmware but i can tweak it to be general | 16:38 |
| wendar | That sounds great. | 16:38 |
| tjones | he's also like to have a bug day | 16:38 |
| wendar | Yeah, it's good to have one early in the cycle. | 16:39 |
| tjones | i have no idea what a bug day is ;-) | 16:39 |
| wendar | Kind of like this, but more hours at a stretch. | 16:39 |
| wendar | Looking to see if I can find info on an old one. | 16:40 |
| tjones | ah ok thanks that would help | 16:40 |
| wendar | There's this, but it looks like it's only useful on the bugday http://status.openstack.org/bugday/ | 16:40 |
| tjones | hm - that looks like its for fixing bugs not triaging bugs? | 16:41 |
| tjones | id rather fix them too | 16:41 |
| wendar | http://lists.openstack.org/pipermail/openstack-dev/2013-May/009239.html | 16:42 |
| wendar | Yes, the focus is on fixing bugs. | 16:42 |
| tjones | cool | 16:42 |
| wendar | But, it's a dogpile effect, so if some people join in to do triage, that's also welcome. | 16:42 |
| wendar | (Not everyone has the skills for fixing bugs.) | 16:43 |
| tjones | true | 16:43 |
| tjones | wow - 1151 nova bugs | 16:44 |
| wendar | One for documentation rather than Nova, but has more details https://wiki.openstack.org/wiki/Documentation/BugDay | 16:44 |
| tjones | nice | 16:45 |
| tjones | ok i can create something like this for us | 16:45 |
| tjones | now - when is it usually held? i mean what time? | 16:46 |
| wendar | http://osdir.com/ml/openstack-dev/2014-02/msg00537.html | 16:46 |
| wendar | AFAIK, just the day is declared, and people jump in anytime during the day. | 16:46 |
| wendar | So, it rolls around the time-zones. | 16:46 |
| tjones | ok great | 16:47 |
| *** otherwiseguy has quit IRC | 16:48 | |
| wendar | From infrastructure: http://princessleia.com/journal/?p=9277 | 16:48 |
| tjones | im do tagging btw - they were all pretty obvious | 16:48 |
| tjones | anything else we should discuss? | 16:48 |
| *** mfer has quit IRC | 16:48 | |
| wendar | excellent, you chewed through all of them | 16:48 |
| wendar | can't think of anything | 16:49 |
| wendar | tjones: thanks! | 16:49 |
| tjones | ok im going to create a bug day wiki - i'll send it out to you and others for feedback and talk to mikal about when he wants to do it. | 16:49 |
| tjones | r u going to atlanta? | 16:49 |
| wendar | Yup, I'll be there. | 16:50 |
| tjones | great - hope to meet you face to face then | 16:50 |
| tjones | c ya | 16:50 |
| wendar | looking forward to it | 16:50 |
| wendar | cya | 16:50 |
| tjones | #endmeeting | 16:50 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 16:50 | |
| openstack | Meeting ended Wed Apr 23 16:50:27 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:50 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/nova_bug_scrub/2014/nova_bug_scrub.2014-04-23-16.30.html | 16:50 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/nova_bug_scrub/2014/nova_bug_scrub.2014-04-23-16.30.txt | 16:50 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/nova_bug_scrub/2014/nova_bug_scrub.2014-04-23-16.30.log.html | 16:50 |
| *** nacim has quit IRC | 17:03 | |
| *** amotoki_ has quit IRC | 17:03 | |
| *** markmcclain has joined #openstack-meeting-3 | 17:07 | |
| *** SumitNaiksatam has quit IRC | 17:07 | |
| *** Kanzhe has joined #openstack-meeting-3 | 17:11 | |
| *** amrith-is-awol is now known as amrith | 17:12 | |
| *** markmcclain has quit IRC | 17:14 | |
| *** eghobo has quit IRC | 17:17 | |
| *** emagana has joined #openstack-meeting-3 | 17:18 | |
| *** eghobo has joined #openstack-meeting-3 | 17:19 | |
| *** eghobo has quit IRC | 17:20 | |
| *** eghobo has joined #openstack-meeting-3 | 17:20 | |
| *** jtomasek has quit IRC | 17:26 | |
| *** OSM has joined #openstack-meeting-3 | 17:28 | |
| *** rkukura has joined #openstack-meeting-3 | 17:29 | |
| *** OSM is now known as songole | 17:29 | |
| *** s3wong has joined #openstack-meeting-3 | 17:30 | |
| *** sweston has joined #openstack-meeting-3 | 17:30 | |
| *** Swami has joined #openstack-meeting-3 | 17:30 | |
| *** sballe has joined #openstack-meeting-3 | 17:30 | |
| *** SumitNaiksatam has joined #openstack-meeting-3 | 17:31 | |
| *** pcm_ has joined #openstack-meeting-3 | 17:31 | |
| s3wong | meeting? | 17:31 |
| *** SridarK has joined #openstack-meeting-3 | 17:31 | |
| banix | hi | 17:31 |
| sballe | hi | 17:31 |
| SridarK | Hi | 17:31 |
| s3wong | Hello | 17:31 |
| Swami | hi all | 17:32 |
| SumitNaiksatam | s3wong: Swami banix: hi | 17:32 |
| *** Sukhdev has quit IRC | 17:32 | |
| emagana | Hi There! | 17:32 |
| SumitNaiksatam | SridarK: sballe: hi | 17:32 |
| Kanzhe | hi all | 17:32 |
| cgoncalves | hi | 17:32 |
| enikanorov_ | hi folks | 17:32 |
| SumitNaiksatam | Kanzhe: cgoncalves enikanorov_ emagana: hi | 17:32 |
| SumitNaiksatam | i think we have critical mass, lets get started | 17:32 |
| *** jsoares has joined #openstack-meeting-3 | 17:32 | |
| SumitNaiksatam | #startmeeting Networking Advanced Services | 17:32 |
| openstack | Meeting started Wed Apr 23 17:32:57 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 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 17:33 |
| *** openstack changes topic to " (Meeting topic: Networking Advanced Services)" | 17:33 | |
| openstack | The meeting name has been set to 'networking_advanced_services' | 17:33 |
| SumitNaiksatam | #info the advanced services common requirements session is accepted for the summit #link http://summit.openstack.org/cfp/details/19 | 17:34 |
| SumitNaiksatam | we have our task cut out in terms of prioritzing what we want to discuss in that slot | 17:34 |
| SumitNaiksatam | lets bring that up again in the open discussion | 17:34 |
| SumitNaiksatam | #topic Flavors Framework | 17:35 |
| *** openstack changes topic to "Flavors Framework (Meeting topic: Networking Advanced Services)" | 17:35 | |
| SumitNaiksatam | our standing agenda item | 17:35 |
| SumitNaiksatam | enikanorov_: any plans to submit the blueprint spec? | 17:35 |
| enikanorov_ | SumitNaiksatam: working on it right now. | 17:35 |
| SumitNaiksatam | enikanorov_: great | 17:35 |
| SumitNaiksatam | btw, the current PoC patch: #link https://review.openstack.org/#/c/83055 | 17:36 |
| enikanorov_ | not really. it seems that i hate the new process! :) | 17:36 |
| SumitNaiksatam | enikanorov_: ouch! :-) | 17:36 |
| SumitNaiksatam | unfortunately undo will not work on that! | 17:36 |
| enikanorov_ | so, on the patch and on the FW in general | 17:36 |
| SumitNaiksatam | enikanorov_: yes please | 17:36 |
| enikanorov_ | i heard many complaints about the term 'flavor' | 17:37 |
| enikanorov_ | so let's may be discuss the name again? | 17:37 |
| enikanorov_ | i don't remember we have finalized this | 17:37 |
| s3wong | enikanorov_: really? I thought flavor was favored due to its name being in tune with Nova | 17:37 |
| enikanorov_ | or we can leave it to ML | 17:37 |
| enikanorov_ | i've started the thread | 17:37 |
| SumitNaiksatam | enikanorov_: no we havent | 17:37 |
| SumitNaiksatam | enikanorov_: sure | 17:37 |
| SumitNaiksatam | enikanorov_: i thought the main change over the STF was the name :-P | 17:37 |
| enikanorov_ | s3wong: nope... actually didn't head of a positive feedback on the name | 17:37 |
| enikanorov_ | haha | 17:38 |
| SumitNaiksatam | STF -> flavor | 17:38 |
| SumitNaiksatam | kidding! :-) | 17:38 |
| SumitNaiksatam | enikanorov_: you obviously deserve more credit than that | 17:38 |
| banix | can we reuse service type or it will be confusing | 17:38 |
| enikanorov_ | yep, it's confusing | 17:38 |
| s3wong | banix: well, the flavor object contains service type, so a bit confusing | 17:38 |
| banix | and rename service type :) | 17:39 |
| enikanorov_ | i don't have strong opinion on name though | 17:39 |
| SumitNaiksatam | enikanorov_: what are the current candidates for the name? | 17:39 |
| banix | noy really | 17:39 |
| enikanorov_ | per ML there is a suggestion to actually split the resource name into service-specific resource names | 17:39 |
| enikanorov_ | like FirewallType, LoadbalancerType | 17:39 |
| enikanorov_ | etc | 17:39 |
| enikanorov_ | it somewhat makes sense to me | 17:40 |
| SumitNaiksatam | enikanorov_: hmmm | 17:40 |
| SumitNaiksatam | enikanorov_: what would you call the framework, though | 17:40 |
| SumitNaiksatam | ? | 17:40 |
| enikanorov_ | but I'd prefer single name and single resource | 17:40 |
| SumitNaiksatam | enikanorov_: agree | 17:40 |
| *** tjones has left #openstack-meeting-3 | 17:40 | |
| enikanorov_ | framework is mostly around scheduling, capability matching, etc... | 17:40 |
| SumitNaiksatam | folks, banix: if you have thoughts, perhaps a good idea to send to the ML | 17:40 |
| enikanorov_ | internally we may have one model exposed through different resources | 17:41 |
| SumitNaiksatam | enikanorov_: ok | 17:41 |
| banix | enikanorov_: which is good | 17:41 |
| SumitNaiksatam | enikanorov_: regarding the PoC patch | 17:41 |
| SumitNaiksatam | i noticed that nachi put some comments | 17:41 |
| SumitNaiksatam | enikanorov_: i dont think there is anything major suggested there | 17:42 |
| enikanorov_ | yeah, but those are code style nits | 17:42 |
| enikanorov_ | yep | 17:42 |
| SumitNaiksatam | yeah, mostly cosmetics | 17:42 |
| *** german_ has joined #openstack-meeting-3 | 17:42 | |
| *** carl_baldwin has joined #openstack-meeting-3 | 17:42 | |
| SumitNaiksatam | enikanorov_: i guess not as many people are looking at the patch, they expect the BP spec first | 17:42 |
| *** german_ has quit IRC | 17:42 | |
| SumitNaiksatam | *expect to see | 17:42 |
| enikanorov_ | i guess so. plan to push it tomorrow | 17:43 |
| SumitNaiksatam | enikanorov_: nice | 17:43 |
| *** german has joined #openstack-meeting-3 | 17:43 | |
| SumitNaiksatam | any more questions for enikanorov_? | 17:43 |
| *** german has quit IRC | 17:43 | |
| SumitNaiksatam | #topic Service context with Service Interfaces | 17:44 |
| *** openstack changes topic to "Service context with Service Interfaces (Meeting topic: Networking Advanced Services)" | 17:44 | |
| *** german has joined #openstack-meeting-3 | 17:44 | |
| SumitNaiksatam | #link https://docs.google.com/document/d/1AlEockwk0Ir267U9uFDc-Q6vYsWiAcAoKtCJM0Jc5UI/edit | 17:44 |
| SumitNaiksatam | Kanzhe: there? | 17:44 |
| Kanzhe | SumitNaiksatam: yes | 17:44 |
| *** german has quit IRC | 17:44 | |
| *** barclaac has joined #openstack-meeting-3 | 17:44 | |
| SumitNaiksatam | so there was some discussion on this through the week | 17:45 |
| SumitNaiksatam | people have provided comments | 17:45 |
| SumitNaiksatam | the above is an evolution over the original bp spec | 17:45 |
| SumitNaiksatam | Kanzhe: you want to summarize the discussions till this point? | 17:45 |
| Kanzhe | There have been some feedbacks on the difficulties in using the current serviceContext API. | 17:46 |
| banix | SumitNaiksatam: which original bp? | 17:46 |
| SumitNaiksatam | banix: #link https://docs.google.com/document/d/1fmCWpCxAN4g5txmCJVmBDt02GYew2kvyRsh0Wl3YF2U/edit | 17:46 |
| banix | SumitNaiksatam: thanks | 17:47 |
| *** german has joined #openstack-meeting-3 | 17:47 | |
| SumitNaiksatam | Kanzhe: go ahead | 17:47 |
| *** german has quit IRC | 17:47 | |
| Kanzhe | An alternative API was proposed, and defines a provider workflow and tenant workflow. | 17:47 |
| Kanzhe | On the provider side, ServiceContext is a list of serviceInterface. | 17:48 |
| Kanzhe | When a provider makes a service available, it defines a list of available serviceInterfaces, which may capture the physical location, mac address, etc. | 17:49 |
| Kanzhe | Then tenant uses the XaaS API to create a logic service. | 17:49 |
| *** emaganap has joined #openstack-meeting-3 | 17:50 | |
| SumitNaiksatam | Kanzhe: serviceInterface is per the definition in your document, but not a resource, right? | 17:50 |
| Kanzhe | We will introduce add/delete interface API for tenant to define the serviceContext for the logic services. | 17:50 |
| Kanzhe | It will be a resource. | 17:50 |
| banix | isnt it already a resource in the doc? | 17:50 |
| Kanzhe | and has UUID. | 17:51 |
| *** german has joined #openstack-meeting-3 | 17:51 | |
| *** prasadv has joined #openstack-meeting-3 | 17:51 | |
| *** lsmola has quit IRC | 17:51 | |
| jsoares | Kanzhe: do you consider that a serviceInterface can be created by regular OpenStack tenant? | 17:51 |
| *** emagana has quit IRC | 17:51 | |
| Kanzhe | jsoares: whoever is responsible to stand up the actual service instance defines the serviceInterface. | 17:52 |
| SumitNaiksatam | Kanzhe: hmmm…if its a purely provider artifact, perhaps not required to make this a resource | 17:52 |
| *** markmcclain has joined #openstack-meeting-3 | 17:52 | |
| SumitNaiksatam | Kanzhe: the tenant only needs to see the port side of this interface | 17:52 |
| Kanzhe | My understanding of provider is admin user that creates serviceInterface. | 17:53 |
| Kanzhe | SumitNaiksatam: yes, serviceInterface is a resource not visible to tenant. If that makes sense. | 17:54 |
| SumitNaiksatam | Kanzhe: my questions is that whether that orchestration happens internal to the provider implementation | 17:54 |
| SumitNaiksatam | *question | 17:54 |
| jsoares | Kanzhe: but the admin user "owns" OpenStack right? What if, a tenant wants to introduce himself a function that he owns? | 17:54 |
| SumitNaiksatam | btw, to put this in context for anyone not following this discussion - we are discussing the insertion of a single service | 17:55 |
| SumitNaiksatam | jsoares: how would that function be configured? | 17:55 |
| Kanzhe | SumitNaiksatam: Don't quite understand the question. | 17:55 |
| s3wong | SumitNaiksatam: the admin user would still need to get a handle of the serviceInterface (add/delete, plug), so it needs to be a resource, right? | 17:56 |
| SumitNaiksatam | Kanzhe: by “that” i meant creation of the service interface (but you answered my question, I think) | 17:56 |
| jsoares | SumitNaiksatam: that function would be configured by the tenant itself, which could be an external system | 17:56 |
| SumitNaiksatam | s3wong: isnt that an implementation detail? | 17:56 |
| SumitNaiksatam | jsoares: good, as far as OpenStack is concerned, its just a VM, right? | 17:57 |
| s3wong | SumitNaiksatam: but the admin user would still need to GET/POST on that interface, right? | 17:57 |
| SumitNaiksatam | s3wong: to do what? | 17:57 |
| jsoares | SumitNaiksatam: right! just a VM, but we have seen that the notion of "port" is not enough for Service Function, therefore it would need something like a Service Interface | 17:58 |
| s3wong | SumitNaiksatam: add, delete, connect/plug? | 17:58 |
| SumitNaiksatam | s3wong: can those operations can be performed on the service resource? | 17:59 |
| s3wong | SumitNaiksatam: yeah, I see what you are saying | 18:00 |
| Kanzhe | jsoares: Tenant should only consume Neutron port. There are discussion to extend the Neutron port to support L1 interfaces. | 18:00 |
| SumitNaiksatam | jsoares: yeah, to add to what Kanzhe said, we are thinking if the service interface part can be hidden inside the implementation, the tenant only sees the port counterpart of that service interface | 18:01 |
| *** eguz has joined #openstack-meeting-3 | 18:01 | |
| SumitNaiksatam | i dont think this is in the document yet | 18:01 |
| jsoares | Kanzhe: but then, a Neutron port would evolve and be able to be what we are referring as Service Interface? I mean, it can be just L1, L1+L2, L1+L2+L3? | 18:01 |
| SumitNaiksatam | perhaps might make things a little clearer with a diagram in the document | 18:01 |
| s3wong | jsoares: exactly. I believe that came up with our discussion earlier. We need to evolve neutron port | 18:02 |
| Kanzhe | jsoares: yes. SumitNaiksatam : I finally see where you question is from? | 18:02 |
| jsoares | s3wong, Kanzhe: then it's clear for me now! | 18:03 |
| *** jtomasek has joined #openstack-meeting-3 | 18:04 | |
| SumitNaiksatam | Kanzhe: plans to update the document? | 18:04 |
| Kanzhe | SumitNaiksatam: However, provider needs to be able to define serviceInterfaces (add/delete). If SI is not a resource, how are the config tracked? | 18:04 |
| SumitNaiksatam | Kanzhe: can it not be just internal objects? | 18:05 |
| *** eghobo has quit IRC | 18:05 | |
| Kanzhe | SumitNaiksatam: I am thinking there needs to be a DB table for serviceInterface, hence a resource. | 18:06 |
| SumitNaiksatam | Kanzhe: DB table yes, but that does not necessarily translate to a resource | 18:06 |
| SumitNaiksatam | ok, Kanzhe perhaps updating the document will help others to come up to speed with the discussion | 18:07 |
| s3wong | SumitNaiksatam: so it is just a list of things attached to a Service resource | 18:07 |
| Kanzhe | SumitNaiksatam: Ok, DB table is what I meant. | 18:07 |
| SumitNaiksatam | Kanzhe: i guessed as much :-) | 18:07 |
| SumitNaiksatam | s3wong: kind of | 18:08 |
| SumitNaiksatam | s3wong: as long as the provider can make sense of it | 18:08 |
| s3wong | SumitNaiksatam: cool | 18:08 |
| SumitNaiksatam | s3wong: but then its the provider’s implementation, so it should be possible | 18:08 |
| SumitNaiksatam | Kanzhe: i believe there was also a suggestion to define a southbound interface | 18:08 |
| Kanzhe | SumitNaiksatam: Yes, we just covered the provider workflow. | 18:09 |
| SumitNaiksatam | Kanzhe: perhaps we can add to the document | 18:09 |
| Kanzhe | There is a tenant workflow, where tenant can instantiate a logic resource. | 18:09 |
| Kanzhe | SumitNaiksatam: yes, I will update the doc. | 18:09 |
| s3wong | SumitNaiksatam: I think the SB interfaces are for a generic service plugin to send API calls to service drivers | 18:09 |
| SumitNaiksatam | Kanzhe: thanks | 18:10 |
| SumitNaiksatam | s3wong: yes | 18:10 |
| SumitNaiksatam | s3wong: its more than the just the provider workflow | 18:10 |
| Kanzhe | Once the logic service is created, user can add an interface to the service. | 18:10 |
| SumitNaiksatam | lets wait for Kanzhe’s update to the document | 18:10 |
| Kanzhe | The tenant workflow mirros well with the existing router interface workflow. | 18:11 |
| SumitNaiksatam | Kanzhe: ok | 18:11 |
| SumitNaiksatam | ok moving on | 18:11 |
| SumitNaiksatam | #topic Port Chaining Proposal | 18:11 |
| *** openstack changes topic to "Port Chaining Proposal (Meeting topic: Networking Advanced Services)" | 18:11 | |
| s3wong | Kanzhe: agreed. It is a clean model | 18:11 |
| SumitNaiksatam | #link https://docs.google.com/document/d/1Bk1e8-diE1VnzlbM8l479Mjx2vKliqdqC_3l5S56ITU/edit | 18:11 |
| *** Sukhdev has joined #openstack-meeting-3 | 18:11 | |
| SumitNaiksatam | cgoncalves jsoares: there? | 18:12 |
| cgoncalves | SumitNaiksatam: we are :) | 18:12 |
| SumitNaiksatam | cgoncalves: thanks for updating the proposal | 18:12 |
| SumitNaiksatam | cgoncalves: nicely documented, including the use cases | 18:12 |
| cgoncalves | since last meeting we had 1,5 days of public holidays so not much of work on this :) | 18:12 |
| SumitNaiksatam | cgoncalves: no worries | 18:13 |
| cgoncalves | SumitNaiksatam: thanks | 18:13 |
| cgoncalves | I've already start writting some API and DB code but it's still early to share | 18:13 |
| SumitNaiksatam | cgoncalves: so as we discussed before, i think we can potentially leverage this work as a traffic steering building block | 18:13 |
| SumitNaiksatam | what do others think about this? | 18:14 |
| cgoncalves | hoping that way we can gather more input from the community | 18:14 |
| jsoares | as a side note, we have also been looking how to enforce this via ODL (OpenDaylight)...we've been doing some tests | 18:14 |
| s3wong | SumitNaiksatam: agreed. there are enough overlaps that we should merge the two efforts - unify the way we will do traffic steering | 18:14 |
| SumitNaiksatam | jsoares: nice | 18:14 |
| cgoncalves | SumitNaiksatam: it sounds good! :) | 18:14 |
| SumitNaiksatam | s3wong: i am thinking that there are three pieces that we are dealing with here | 18:15 |
| jsoares | SumitNaiksatam: agree with the steering building block. | 18:15 |
| SumitNaiksatam | (1) service insertion (the part we just discussed with Kanzhe’s proposal) | 18:15 |
| *** jaypipes has quit IRC | 18:15 | |
| SumitNaiksatam | (2) trafffic steering (including classifier) as being discussed in cgoncalves and jsoares’ proposal | 18:16 |
| *** samchoi has quit IRC | 18:16 | |
| SumitNaiksatam | (3) service chain (which includes addressing neutron services) | 18:16 |
| SumitNaiksatam | (3) would rely on (1) and (2) | 18:17 |
| *** emaganap has quit IRC | 18:17 | |
| Kanzhe | SumitNaiksatam: yes, agreed. | 18:17 |
| s3wong | SumitNaiksatam: in that case, both (2) and (3) should depend on (1) | 18:18 |
| cgoncalves | SumitNaiksatam: our proposal addresses (2) traffic chaining as a dependency for (3) service chain which is our ultimate goal | 18:18 |
| Kanzhe | 3 leverages 2, which leverages 1. | 18:19 |
| jsoares | SumitNaiksatam: but do you see (2) exposed like the proposal presents it now? I mean, something like "Traffic Steering Chain" | 18:19 |
| s3wong | Kanzhe: so we are all relying on you to get (1)'s proposal out :-) | 18:19 |
| banix | jsoares: should not be exposed in my opinion | 18:19 |
| SumitNaiksatam | jsoares: we need to think through, but it does seem like it is a candidate for a lower level traffic steering API | 18:19 |
| banix | where would t be used beyond service chains? | 18:20 |
| Kanzhe | s3wong: end of the day, it is a team effort to the serviceChaining holy grail. :-) | 18:20 |
| SumitNaiksatam | banix: i agree that it would be very difficult to consume for the tenant to consume | 18:20 |
| s3wong | jsoares: traffic steering framework should be lower level in that you are creating classifers/rules to move traffic flow off of its natural flow | 18:20 |
| SumitNaiksatam | difficult -> complex | 18:20 |
| s3wong | jsoares: but service chain would be a composition of tenant addressable neutron service objects | 18:21 |
| SumitNaiksatam | s3wong: agree | 18:21 |
| jsoares | SumitNaiksatam, s3wong: That would suit Neutron services, but what if the tenant itself want to build a Service Function Chain himself? | 18:21 |
| SumitNaiksatam | banix s3wong: i think where jsoares is coming from is to be able to make service VMs to be part of the chain | 18:22 |
| jsoares | with its own Functions, or other functions that are not within Neutron today | 18:22 |
| SumitNaiksatam | jsoares: yes, i get that, see ^^^ :-) | 18:22 |
| Kanzhe | s3wong: we will need a generic service object for other services that not yet defined in Neutron. | 18:22 |
| s3wong | jsoares: it sounds like for BYOS, we need to have a service object able to reference to a VM | 18:22 |
| SumitNaiksatam | Kanzhe: good point | 18:22 |
| jsoares | SumitNaiksatam: Yes, we highlight that in the introduction of our proposal | 18:22 |
| SumitNaiksatam | s3wong: BYOS, nice!! :-) | 18:23 |
| banix | SumitNaiksatam: shouldnt that be through the "service in VM" work? | 18:23 |
| s3wong | Kanzhe: absolutely | 18:23 |
| SumitNaiksatam | s3wong: copyright it! :-) | 18:23 |
| s3wong | banix: service VM is now being moved out of Neutron | 18:23 |
| banix | s3wong: i know but there should be something higher level | 18:23 |
| s3wong | banix: we can have generic service object able to point to a VM designated by a tenant | 18:24 |
| SumitNaiksatam | cgoncalves jsoares: i see in your document that you had plans to update it | 18:24 |
| SumitNaiksatam | cgoncalves jsoares: we will need to normalize on some of the terminology | 18:24 |
| SumitNaiksatam | endpoints in being used int he GP proposal | 18:24 |
| s3wong | banix: but lifecycle management of the service in VM should not be Neutron's job | 18:24 |
| banix | s3wong: that's great and desirable but the question is how that gets done and through what APIs .... | 18:25 |
| jsoares | SumitNaiksatam: sure! | 18:25 |
| SumitNaiksatam | also, i would propose a traffic sterring terminlogy, rather than chain | 18:25 |
| cgoncalves | SumitNaiksatam: gp_endpoint, sf_endpoint; gp_classifier, sf_classifier :) kidding | 18:25 |
| s3wong | banix: the service VM effort is still going :-) just not a Neutron project | 18:25 |
| SumitNaiksatam | s3wong banix: lets have the service VM discussion next week | 18:25 |
| SumitNaiksatam | cgoncalves: :-) | 18:25 |
| SumitNaiksatam | #topic Certificate Management | 18:26 |
| *** openstack changes topic to "Certificate Management (Meeting topic: Networking Advanced Services)" | 18:26 | |
| SumitNaiksatam | Swami: there? | 18:26 |
| Swami | yes | 18:26 |
| Swami | I am here. | 18:26 |
| SumitNaiksatam | the issue is that there is a requirement across services to be able to deal with certificates | 18:26 |
| SumitNaiksatam | and we dont have a way to do that today | 18:26 |
| SumitNaiksatam | Swami: over to you | 18:26 |
| Swami | There was some concerns and discussions about storing the certificates for the services in neutron. | 18:27 |
| Swami | Both Lbaas and VPNaaS had an issue with the Icehouse. | 18:27 |
| SumitNaiksatam | Swami: is there a ML thread on this? | 18:27 |
| Swami | My question is, does this Advanced Services team need to own this as part of addressing the advanced services. | 18:27 |
| SumitNaiksatam | Swami: okay, lets first bring this up with the PTL | 18:28 |
| SumitNaiksatam | lets get initial thoughts, and we can accordingly start discussing this (either here, or as a separate thread) | 18:28 |
| Swami | SumitNaiksatam: Recently the ssl VPN work and the Lbaas ssl offload work was stopped, since there was no infrastructure to support secure certificates. | 18:28 |
| Swami | SumitNaiksatam: Yes that makes sense. | 18:29 |
| SumitNaiksatam | #action SumitNaiksatam Swami to follow up with PTL regarding certificate management | 18:29 |
| SumitNaiksatam | Swami: thanks | 18:29 |
| SumitNaiksatam | #Atlanta Summit Discussion | 18:29 |
| enikanorov_ | there is some progress with barbican which has incubated | 18:29 |
| SumitNaiksatam | #topic Atlanta Summit Discussion | 18:30 |
| *** openstack changes topic to "Atlanta Summit Discussion (Meeting topic: Networking Advanced Services)" | 18:30 | |
| SumitNaiksatam | enikanorov_: thanks, we can check that | 18:30 |
| *** jtomasek has quit IRC | 18:30 | |
| SumitNaiksatam | at this point, i have collected the following prirorities from the previous discussion: | 18:30 |
| SumitNaiksatam | * flavors framework | 18:31 |
| SumitNaiksatam | * base service definition | 18:31 |
| SumitNaiksatam | * service insertion framework | 18:31 |
| SumitNaiksatam | * service chaining framework | 18:31 |
| SumitNaiksatam | * certificate management | 18:31 |
| SumitNaiksatam | this is just a laundry list | 18:31 |
| *** ttrifonov_zZzz is now known as ttrifonov | 18:31 | |
| s3wong | SumitNaiksatam: that is very ambitious for one 40 minutes session | 18:31 |
| SumitNaiksatam | putting it out there early so that we can think through | 18:31 |
| SumitNaiksatam | s3wong: i know | 18:31 |
| SumitNaiksatam | if we converge on some topics, we can knock them off this list | 18:31 |
| *** jsoares has quit IRC | 18:32 | |
| SumitNaiksatam | also, we have made it clear to the PTL that a shared 40 min slot is pretty short time for this discussions | 18:32 |
| SumitNaiksatam | what we can do is, if there is enough interest, have follow up break up sessions | 18:32 |
| SumitNaiksatam | or even prior to this session | 18:32 |
| SumitNaiksatam | i believe our session will be on thursday | 18:33 |
| SumitNaiksatam | any thoughts/comments on this or in general? | 18:33 |
| banix | SumitNaiksatam , others: are ypou planning on having specs for review? | 18:33 |
| SumitNaiksatam | banix: yes definitely | 18:33 |
| SumitNaiksatam | banix: so we need to have some basic level of convergence on the design | 18:34 |
| SumitNaiksatam | banix: based on that we can go to the neutron core team/PTL and request prioritization | 18:34 |
| s3wong | SumitNaiksatam: we definitely need to work on getting base service object definition nailed down | 18:34 |
| SumitNaiksatam | banix: and accordingly out the specs in | 18:34 |
| SumitNaiksatam | s3wong: definitely agree | 18:34 |
| *** german has left #openstack-meeting-3 | 18:34 | |
| banix | s3wong: agree | 18:34 |
| SridarK | SumitNaiksatam: should we also outline the impacts to the current reference implementations | 18:34 |
| SumitNaiksatam | SridarK: yes, that will be a part of the feasibility discussion when choosing a particular approach | 18:35 |
| SridarK | ok got it | 18:36 |
| SumitNaiksatam | SridarK: i agree, changes to the base service definition might need changes to existing service implementations | 18:36 |
| SumitNaiksatam | ok folks, we are over time | 18:36 |
| SumitNaiksatam | any parting thoughts/comments? | 18:36 |
| SumitNaiksatam | alright thanks all! | 18:37 |
| SumitNaiksatam | see you next week | 18:37 |
| s3wong | thanks! | 18:37 |
| banix | bye | 18:37 |
| SumitNaiksatam | bye | 18:37 |
| SumitNaiksatam | #endmeeting | 18:37 |
| SridarK | bye | 18:37 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 18:37 | |
| openstack | Meeting ended Wed Apr 23 18:37:31 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 18:37 |
| *** rkukura has left #openstack-meeting-3 | 18:37 | |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-04-23-17.32.html | 18:37 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-04-23-17.32.txt | 18:37 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-04-23-17.32.log.html | 18:37 |
| Swami | bye | 18:37 |
| *** Kanzhe has quit IRC | 18:37 | |
| SumitNaiksatam | Kanzhe: cgoncalves Swami : thanks for the updates! :-) | 18:37 |
| SumitNaiksatam | enikanorov_: you too, thanks! | 18:38 |
| enikanorov_ | thanks, see ya | 18:38 |
| s3wong | enikanorov_: sleep well! | 18:38 |
| enikanorov_ | :) | 18:38 |
| cgoncalves | SumitNaiksatam: yw | 18:39 |
| SumitNaiksatam | s3wong: there? | 18:41 |
| s3wong | SumitNaiksatam: yes, still here :-) | 18:41 |
| SumitNaiksatam | s3wong: per your earlier comment on base service definition | 18:42 |
| *** chuckC has quit IRC | 18:42 | |
| SumitNaiksatam | s3wong: do you want to take a crack at this? | 18:42 |
| s3wong | SumitNaiksatam: sure, I definitely need it for GBP also | 18:42 |
| SumitNaiksatam | s3wong: ok good | 18:43 |
| s3wong | SumitNaiksatam: so you can put me down on that | 18:43 |
| SumitNaiksatam | s3wong: action item for you for the next week? :-) | 18:43 |
| s3wong | SumitNaiksatam: sure. Will run by you and Kanzhe before hand | 18:43 |
| SumitNaiksatam | s3wong: great! | 18:43 |
| *** redrobot has joined #openstack-meeting-3 | 18:45 | |
| *** markmcclain1 has joined #openstack-meeting-3 | 18:49 | |
| *** markmcclain has quit IRC | 18:50 | |
| *** chuckC has joined #openstack-meeting-3 | 18:51 | |
| *** pcm_ has left #openstack-meeting-3 | 18:51 | |
| *** mfer has joined #openstack-meeting-3 | 18:51 | |
| *** SridarK has quit IRC | 18:57 | |
| *** ttrifonov is now known as ttrifonov_zZzz | 18:59 | |
| *** markmcclain1 has quit IRC | 19:04 | |
| *** prasadv has quit IRC | 19:09 | |
| *** gduan has joined #openstack-meeting-3 | 19:13 | |
| *** garyduan has quit IRC | 19:15 | |
| *** beyounn has quit IRC | 19:15 | |
| *** beyounn has joined #openstack-meeting-3 | 19:15 | |
| *** jaypipes has joined #openstack-meeting-3 | 19:30 | |
| *** SumitNaiksatam has quit IRC | 19:30 | |
| *** markmcclain has joined #openstack-meeting-3 | 19:35 | |
| *** julim has joined #openstack-meeting-3 | 19:41 | |
| *** songole has quit IRC | 19:48 | |
| *** devlaps has quit IRC | 19:54 | |
| *** sankarshan is now known as sankarshan_away | 20:06 | |
| *** Sukhdev has quit IRC | 20:11 | |
| *** chuckC has quit IRC | 20:19 | |
| *** eguz has quit IRC | 20:19 | |
| *** eghobo has joined #openstack-meeting-3 | 20:20 | |
| *** sweston has quit IRC | 20:21 | |
| *** jamie_h has quit IRC | 20:22 | |
| *** devlaps has joined #openstack-meeting-3 | 20:25 | |
| *** devlaps has quit IRC | 20:29 | |
| *** julim has quit IRC | 20:33 | |
| *** overlayer has joined #openstack-meeting-3 | 20:39 | |
| *** mwagner_lap has quit IRC | 20:47 | |
| *** markmcclain has quit IRC | 20:55 | |
| *** devlaps has joined #openstack-meeting-3 | 20:55 | |
| *** redrobot has left #openstack-meeting-3 | 20:57 | |
| *** devlaps has quit IRC | 20:59 | |
| *** markmcclain has joined #openstack-meeting-3 | 21:00 | |
| *** overlayer has quit IRC | 21:01 | |
| *** Swami has left #openstack-meeting-3 | 21:06 | |
| *** david-lyle has quit IRC | 21:09 | |
| *** lblanchard has quit IRC | 21:10 | |
| *** sweston has joined #openstack-meeting-3 | 21:14 | |
| *** devlaps has joined #openstack-meeting-3 | 21:17 | |
| *** overlayer has joined #openstack-meeting-3 | 21:20 | |
| *** overlayer has quit IRC | 21:20 | |
| *** overlayer has joined #openstack-meeting-3 | 21:21 | |
| *** overlayer has quit IRC | 21:25 | |
| *** yamahata has joined #openstack-meeting-3 | 21:26 | |
| *** jamielennox|away is now known as jamielennox | 21:40 | |
| *** Sukhdev has joined #openstack-meeting-3 | 21:57 | |
| *** carl_baldwin has quit IRC | 22:01 | |
| *** mfer has quit IRC | 22:10 | |
| *** mfer has joined #openstack-meeting-3 | 22:14 | |
| *** SumitNaiksatam has joined #openstack-meeting-3 | 22:15 | |
| *** markmcclain has quit IRC | 22:18 | |
| *** peristeri has quit IRC | 22:20 | |
| *** overlayer has joined #openstack-meeting-3 | 22:21 | |
| *** overlayer has quit IRC | 22:28 | |
| *** banix has quit IRC | 22:35 | |
| *** sweston has quit IRC | 22:37 | |
| *** sweston has joined #openstack-meeting-3 | 22:39 | |
| *** yamahata has quit IRC | 22:47 | |
| *** HenryG has quit IRC | 22:51 | |
| *** HenryG has joined #openstack-meeting-3 | 22:55 | |
| *** chuckC has joined #openstack-meeting-3 | 23:09 | |
| *** jamielennox has left #openstack-meeting-3 | 23:16 | |
| *** mfer has quit IRC | 23:19 | |
| *** mfer has joined #openstack-meeting-3 | 23:20 | |
| *** chuckC has quit IRC | 23:21 | |
| *** mfer has quit IRC | 23:30 | |
| *** mfer has joined #openstack-meeting-3 | 23:30 | |
| *** mfer has quit IRC | 23:47 | |
| *** barclaac has quit IRC | 23:47 | |
| *** s3wong has quit IRC | 23:50 | |
| *** jaypipes has quit IRC | 23:54 | |
| *** rockyg has joined #openstack-meeting-3 | 23:56 | |
| *** Sukhdev has quit IRC | 23:57 | |
| *** lblanchard has joined #openstack-meeting-3 | 23:59 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!