elmiko | anyone here for api-wg? | 00:00 |
---|---|---|
miguelgrinberg | elmiko: I'm here | 00:00 |
elmiko | miguelgrinberg: should we wait to see if a few more show up before starting? | 00:01 |
stevelle | o/ | 00:01 |
elmiko | ok, cool | 00:01 |
elmiko | #startmeeting api-wg | 00:01 |
openstack | Meeting started Thu Apr 30 00:01:30 2015 UTC and is due to finish in 60 minutes. The chair is elmiko. Information about MeetBot at http://wiki.debian.org/MeetBot. | 00:01 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 00:01 |
*** openstack changes topic to " (Meeting topic: api-wg)" | 00:01 | |
openstack | The meeting name has been set to 'api_wg' | 00:01 |
elmiko | #link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda | 00:02 |
elmiko | #topic previous meeting action items | 00:02 |
*** openstack changes topic to "previous meeting action items (Meeting topic: api-wg)" | 00:02 | |
elmiko | #link http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-04-23-16.00.html | 00:03 |
miguelgrinberg | elmiko: looks like you are the only one with an action item | 00:03 |
elmiko | yea | 00:03 |
miguelgrinberg | the only one present | 00:03 |
elmiko | etoews, handled his | 00:03 |
elmiko | i'm still working on the guidelines change, trying to figure out what would be best for inclusion | 00:03 |
sigmavirus24 | o/ | 00:04 |
sigmavirus24 | (sorry I'm late) | 00:04 |
elmiko | i started trying to make the "Change Guidelines" fit the guidelines template, but i'm not totally sure if that's correct | 00:04 |
elmiko | sigmavirus24: no worries =) | 00:04 |
elmiko | i'll put it up for review and we'll see what folks think | 00:04 |
sigmavirus24 | cool | 00:05 |
elmiko | #topic guidelines | 00:05 |
*** openstack changes topic to "guidelines (Meeting topic: api-wg)" | 00:05 | |
elmiko | #link https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z | 00:05 |
elmiko | i think everything is pretty much under review at this point, | 00:05 |
elmiko | does anyone want to mention something specific? | 00:06 |
stevelle | nothing here | 00:06 |
miguelgrinberg | When are we lifting the freeze on proposals? | 00:06 |
elmiko | oh, plus we're frozen on miguelgrinberg's proposals | 00:06 |
elmiko | miguelgrinberg: i thought once the kilo release had ended | 00:07 |
sigmavirus24 | yeah we didn't discuss when we would unfreeze them | 00:07 |
miguelgrinberg | Kilo releases tomorrow right? | 00:07 |
sigmavirus24 | we just discussed the idea that PTLs are kind of super busy now and CPLs are probably busy too | 00:07 |
elmiko | and i think etoews is out until next week | 00:07 |
elmiko | yea | 00:07 |
elmiko | #link https://wiki.openstack.org/wiki/Kilo_Release_Schedule | 00:08 |
elmiko | tomorrow is the release, maybe we should ping etoews through email | 00:08 |
sigmavirus24 | Perhaps we'll never unfreeze them. *laughs maniacally* | 00:08 |
miguelgrinberg | Glad to see a spec on filtering is in the works | 00:08 |
elmiko | lol | 00:08 |
elmiko | yea, very cool about filtering. i had questions about the best ways to implement this | 00:09 |
miguelgrinberg | Heat has a couple of specs for Liberty where there is filtering, so it's good that we put something together | 00:10 |
elmiko | sahara is discussing a v2 api and the guidelines have been very helpful in finding problem areas in the current impl | 00:10 |
stevelle | testimonails! | 00:11 |
elmiko | hehe =) | 00:11 |
stevelle | and hopefully fewer typos than me | 00:11 |
sigmavirus24 | elmiko: we're going to do a google hangouts podcast series now | 00:11 |
miguelgrinberg | yes, also the nova people reached out for help with tagging | 00:11 |
sigmavirus24 | And you'll be the guest | 00:11 |
sigmavirus24 | jaypipes: miguelgrinberg and I will grill you on how the API-WG has changed your life =P | 00:12 |
elmiko | awesome... ;) | 00:12 |
elmiko | even though it's not merged yet, the tagging guideline has helped. | 00:12 |
miguelgrinberg | yes, heat already implemented it, and now nova will | 00:13 |
elmiko | nice | 00:13 |
elmiko | anything else for guidelines? | 00:13 |
jaypipes | lol | 00:14 |
elmiko | #topic APIImpact | 00:14 |
*** openstack changes topic to "APIImpact (Meeting topic: api-wg)" | 00:14 | |
* sigmavirus24 half-heartedly apologizes for being so punchy tonight | 00:14 | |
elmiko | #link https://review.openstack.org/#/q/status:open+AND+(message:ApiImpact+OR+message:APIImpact),n,z | 00:14 |
stevelle | apology half-heartedly accepted? | 00:14 |
elmiko | any reviews we should look at? | 00:14 |
elmiko | lol | 00:14 |
jaypipes | sigmavirus24: did you see my callout to you, miguelgrinberg and etoews in a podcast recently? | 00:15 |
miguelgrinberg | jaypipes: I did! total surprise to hear my name! | 00:15 |
sigmavirus24 | jaypipes: my coworker caught it and alerted us | 00:15 |
jaypipes | heh | 00:15 |
elmiko | jaypipes: is that the bootstrapping hour? | 00:15 |
jaypipes | elmiko: no, it was a podcast with Jeff DIckey from redapt and Niki Acosta from Cisco | 00:16 |
*** Shamail has quit IRC | 00:16 | |
elmiko | oh, nice | 00:16 |
jaypipes | elmiko: I need to get with sean about the bootstrapping hour continuing.. | 00:16 |
jaypipes | thx for the reminder :) | 00:16 |
elmiko | jaypipes: +1, i've really enjoyed it so far =) | 00:16 |
jaypipes | cool! | 00:16 |
jaypipes | so, guys, I have a bit of API WG news... | 00:16 |
elmiko | #topic News | 00:17 |
jaypipes | sorry for being late to this meeting, first of all | 00:17 |
*** banix has quit IRC | 00:17 | |
*** openstack changes topic to "News (Meeting topic: api-wg)" | 00:17 | |
jaypipes | so, I've been chatting with johnthetubaguy, kenichi, mgilliard and alex_xu about a Nova contributor being a liaison to the API WG | 00:17 |
elmiko | nice | 00:17 |
jaypipes | Looks like alex_xu and mgilliard will be our liaisons. | 00:18 |
jaypipes | I suggested, however, that instead of just showing up to meetings, that they have specific tasks. | 00:18 |
jaypipes | namely, the following. one sec, grabbing copy. | 00:18 |
*** sarob_ has quit IRC | 00:18 | |
jaypipes | sorry for the paste, but here it is: | 00:19 |
jaypipes | 1) Assign someone (or some two) people to monitor the active patch queue in | 00:19 |
jaypipes | nova (and nova-specs) and look out for any patch that adds or changes the | 00:19 |
jaypipes | REST API | 00:19 |
jaypipes | 2) For each patch collected in #1, determine if the constructs used in the | 00:19 |
jaypipes | patch (or proposed spec) match the guidance currently laid out in the API | 00:19 |
jaypipes | working group repo's guidance documents. | 00:19 |
jaypipes | 3) If the patch does NOT match the guidance from the API working group, do a | 00:19 |
jaypipes | code review on the patch pointing to the guidance from the API working | 00:19 |
jaypipes | group, and ask the author to align with that guidance. Include in your | 00:19 |
jaypipes | research patches to the API working group that may actually be in review and | 00:19 |
jaypipes | not merged. (An example of this recently occurred with Sergey Nikitin's | 00:19 |
jaypipes | re-proposed instance tagging spec: https://review.openstack.org/#/c/177112/. | 00:19 |
jaypipes | See Ryan Brown's reference to an in-progress API working group guidance on | 00:19 |
jaypipes | tagging) | 00:19 |
jaypipes | 4) If there is NO guidance in the API working group repo for a particular | 00:19 |
jaypipes | proposed API change or addition, create a proposed patch to the API working | 00:19 |
jaypipes | group with guidance that clarifies the missing functionality that is | 00:19 |
jaypipes | introduced in the new Nova patch or spec patch, and bring the proposed | 00:19 |
jaypipes | guidance to the attention of the API working group. | 00:19 |
elmiko | very nice, i especially like #4 | 00:20 |
jaypipes | if you guys feel the above is OK, perhaps it's worth codifying it after a test run in Nova and recmomending these steps for other teams to take with their liaisons to the API WG? | 00:20 |
elmiko | +1 | 00:20 |
stevelle | seems like a good place to work from | 00:21 |
miguelgrinberg | very good | 00:21 |
elmiko | at the least it provides a solid guide for how other projects can get involved with the wg | 00:21 |
jaypipes | OK, well, we'll give it a shot over in Nova-land and see if it works out well. | 00:21 |
elmiko | thanks for bringing it up | 00:21 |
*** baoli has joined #openstack-meeting-3 | 00:21 | |
jaypipes | lemme know if you have any suggestions on improving the steps for liaisons to take. happy to get feedback on it. | 00:22 |
jaypipes | and sorry for dumping paste into IRC... | 00:22 |
elmiko | no worries | 00:23 |
elmiko | #topic open discussion | 00:23 |
*** openstack changes topic to "open discussion (Meeting topic: api-wg)" | 00:23 | |
elmiko | anything else folks wanna talk about? | 00:23 |
miguelgrinberg | jaypipes: my only suggestion for #4 is that alternatively the liason can alert an active member of the api-wg to write a guideline | 00:23 |
miguelgrinberg | At least in heat-land I find that some people are not interested in proposing something to api-wg | 00:24 |
miguelgrinberg | at least they should get one of us to do it for them | 00:24 |
elmiko | do they have any reason for why that might be? | 00:24 |
miguelgrinberg | nothing special, lack of time I guess? | 00:24 |
elmiko | yea, i can feel that | 00:25 |
miguelgrinberg | I was going to write something on filtering due to heat having a couple of specs in that area, but ryanb beat me to it | 00:26 |
jaypipes | miguelgrinberg: cool, good suggestion, thank you! | 00:26 |
jaypipes | Hey, so are we ready to merge the 3 guidelines that Everett had put on hold? | 00:28 |
miguelgrinberg | we were wondering when is the freeze is going to end | 00:28 |
elmiko | it seemed like they had good acceptance | 00:28 |
*** banix has joined #openstack-meeting-3 | 00:29 | |
jaypipes | Yes, I was wondering when the freeze would end as well. | 00:29 |
elmiko | maybe we should wait till next week to give the PTLs a chance to review after the kilo release? | 00:29 |
jaypipes | I must have missed an email where etoews mentioned that. | 00:29 |
elmiko | it has been a topic of some mystery | 00:29 |
jaypipes | sure, that's cool by me. no rush. | 00:29 |
elmiko | i think the idea was that as we reach the milestone releases we should impose a freeze on guidelines to give the PTLs a chance to breathe without having to worry about reviewing new guidelines | 00:30 |
elmiko | *i think* | 00:30 |
miguelgrinberg | yes, that was the idea | 00:31 |
elmiko | maybe next meeting we'll revisit? | 00:31 |
*** annegent_ has joined #openstack-meeting-3 | 00:31 | |
elmiko | i'm not sure who has +2 aside from etoews | 00:32 |
sigmavirus24 | jaypipes | 00:32 |
sigmavirus24 | cyeoh did | 00:32 |
sigmavirus24 | =( | 00:32 |
elmiko | =( | 00:32 |
annegent_ | aww sad time to join :( | 00:32 |
annegent_ | sorry I'm late | 00:33 |
elmiko | no prob | 00:33 |
elmiko | annegent_: did you have any topics to discuss? | 00:33 |
* annegent_ reads the log to catch up | 00:33 | |
annegent_ | oo I like the nova liaison ideas jaypipes | 00:34 |
elmiko | cool | 00:34 |
annegent_ | yes I had API Reference information: specification for reinvention underway | 00:35 |
sigmavirus24 | =D | 00:35 |
annegent_ | you following https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda? | 00:35 |
elmiko | sorta, we ran through those topics so i just kinda freestyled | 00:35 |
elmiko | ;) | 00:35 |
annegent_ | Hee | 00:36 |
annegent_ | ok if I can go I'll go! | 00:36 |
elmiko | please | 00:36 |
annegent_ | Okay, so I really want to be rid of WADL | 00:36 |
elmiko | \o/ | 00:36 |
annegent_ | and want to figure out how to do the work | 00:36 |
jaypipes | ++ | 00:36 |
annegent_ | so I've written a spec | 00:36 |
annegent_ | but it's still even wishy washy about where the work should live -- in the docs team or in the API WG? Discuss. | 00:37 |
annegent_ | #link https://review.openstack.org/#/c/177934/ | 00:37 |
elmiko | i had question when reading that, | 00:37 |
annegent_ | Tom Fifield has a summary post on openstack-docs about automation as well that I'll link to | 00:37 |
elmiko | what happens to things like the keystone api reference they have in their specs repo? | 00:37 |
elmiko | i always found that to be a nice place for the upstream api refs | 00:38 |
annegent_ | elmiko: this is for API Reference, that is their "narrative" form documents | 00:38 |
elmiko | ahh, ok | 00:38 |
annegent_ | elmiko: yeah there's a difference, but it may also just need to live in specs, that's up for discussion | 00:38 |
annegent_ | there's 915 calls just in the first 8 or so services that became OpenStack | 00:39 |
elmiko | would be interesting if each project owned their api-ref in the specs repo, then the "official" api-ref site did some sort of aggregation | 00:39 |
annegent_ | that doesn't even count the additional 10? 12? services | 00:39 |
annegent_ | #link http://lists.openstack.org/pipermail/openstack-docs/2015-April/006502.html | 00:39 |
annegent_ | so that's what I want to hear from you all | 00:39 |
annegent_ | automation okay? | 00:39 |
annegent_ | specs repos? <project> repos and scrape from their code? | 00:39 |
elmiko | something like that | 00:40 |
elmiko | and i really liked the swagger based ideas, fwiw | 00:40 |
annegent_ | is automation awful when you need to provide real user info though? | 00:40 |
annegent_ | and do we de-scope to only infrastructure APIs in order to bring the quality level up? | 00:40 |
annegent_ | or will each team bring the quality level up? | 00:40 |
elmiko | i think you had a good point about the errors that can creep in from automated docs | 00:40 |
*** s3wong has quit IRC | 00:40 | |
sigmavirus24 | So... I'll say this: JSON Schema can be a nightmare. I'm not an expert but I'm not a novice either. If you're going to go with JSON Schema you'll need a validator with good ways of testing things | 00:41 |
annegent_ | elmiko: I always think it's a crappier user experience, but Tom does have good points | 00:41 |
annegent_ | sigmavirus24: yeah I worry about finding expertise in community sourcing, it's really really hard already | 00:41 |
elmiko | sigmavirus24: are you talking about the validation on a swagger schema? | 00:41 |
sigmavirus24 | elmiko: I'm talking about the RST + JSON Schema proposal at the end | 00:41 |
annegent_ | Diane Fleming has single handedly done the maintenance and she's unbelieveably fast and it's still not enough | 00:42 |
annegent_ | honestly you need JSON Schema for swagger too | 00:42 |
sigmavirus24 | So I'm comfortable with JSON Schema, but I'm no expert | 00:42 |
annegent_ | if you want to validate you need json schema from what I can see | 00:42 |
elmiko | yea, that's why i asked. and yes Diane is excellent! | 00:42 |
annegent_ | she closed something like 80 doc bugs this release and we're still just barely under 170 API doc bugs | 00:42 |
elmiko | wow | 00:43 |
annegent_ | so the situation needs fixing | 00:43 |
annegent_ | but how? | 00:43 |
sigmavirus24 | yeah that's tough | 00:43 |
elmiko | i kinda like the idea of automating the generation of a skeleton json(swagger) output, then each team working to fill in the missing parts | 00:44 |
annegent_ | I'm fine with trying automation. 1. Do you think all teams will comply? 2. will it be a worse experience for consumers of the info? | 00:44 |
elmiko | one issue with automation is that projects using pecan will need to add extra markup to their code | 00:45 |
annegent_ | (the ops/admin docs are over 550 doc bugs so there's that comparison which is a bit unfair, ha ha) | 00:45 |
annegent_ | so, for pecan we already have WADL automation | 00:45 |
annegent_ | I don't know if you know that | 00:45 |
elmiko | i did not, although i started down the path of swagger automation for pecan | 00:45 |
annegent_ | but yeah there's only ceilometer using pecan? | 00:45 |
elmiko | barbican uses pecan as well | 00:46 |
annegent_ | we don't enable flask, correct? | 00:46 |
annegent_ | Looking at this list | 00:46 |
annegent_ | #link https://github.com/swagger-api/swagger-spec#python | 00:46 |
*** mwagner_lap has quit IRC | 00:46 | |
annegent_ | also what do yuo think about descoping to infra-only? non-starter? | 00:47 |
miguelgrinberg | annegent_: that is not just flask, it is a REST extension for flask, but no project uses Flask that I know of | 00:47 |
elmiko | i didn't test the flask based solutions, but it's much easier to generate the swagger from flask | 00:47 |
stevelle | ceilometer wanted to use flask but was directed to pecan as I understand | 00:47 |
annegent_ | miguelgrinberg: right, it's not "blessed" centrally | 00:47 |
annegent_ | right | 00:47 |
annegent_ | stevelle: right | 00:47 |
elmiko | miguelgrinberg: sahara is using flask | 00:47 |
*** ivar-lazzaro has quit IRC | 00:47 | |
annegent_ | Okay so what about only documenting Compute, Block Storage, Object Storage, Identity, Images APIs? | 00:48 |
annegent_ | no-go on de-scope? | 00:48 |
miguelgrinberg | elmiko: oh, nice! | 00:48 |
elmiko | i like the idea of every project documenting, but not sure how practical it will be | 00:48 |
annegent_ | elmiko: ah I hadn't realized that | 00:48 |
miguelgrinberg | do you think it'll be able to stay on flask or will it go the ceilo way? | 00:49 |
jaypipes | yeah, I feel the same as elmiko. | 00:49 |
jaypipes | I'm torn on this autogeneration stuff, frankly. | 00:49 |
annegent_ | miguelgrinberg: it's a free-for-all at this point | 00:49 |
annegent_ | jaypipes: go on :) | 00:49 |
elmiko | miguelgrinberg: i think there is pressure for us to move to pecan, but i'm not sure how far we'll get | 00:49 |
jaypipes | annegent_: If it can be shown that we can accurately autogenerate API docs from the code, then I'll play along. I havent' yet seen anything that can do it well though. :) | 00:50 |
annegent_ | jaypipes: right, to me, all automation is worser | 00:50 |
annegent_ | worser! | 00:50 |
elmiko | i don't think we can fully rely on autogeneration, especially not if we want the level of detail that api-ref currently has | 00:50 |
annegent_ | I'm fascinated with autogenerating Swagger 2.0 | 00:50 |
stevelle | +1 that | 00:50 |
elmiko | yea, it's got some really cool features | 00:50 |
annegent_ | we do a nice job with the Config Ref already, as Tom points out | 00:50 |
stevelle | as a start point it would save a ton of time to get a transition started | 00:51 |
jaypipes | annegent_: well, no, automation in general is betterer. But I'm just wary. The opposite direction -- i.e. code generated from docs -- almost NEVER works, so I'm skeptical about it. | 00:51 |
elmiko | i think it would be nice if we could provide advice on how to autogenerate then markup | 00:51 |
annegent_ | two things I haven't investigated to satisfaction with Swagger: | 00:51 |
stevelle | but only if it worked | 00:51 |
annegent_ | 1. how to display headers. Object Storage API has like 80 headers | 00:51 |
annegent_ | 2. how to indicate array requirements in requests | 00:51 |
*** zhenguo has joined #openstack-meeting-3 | 00:51 | |
jaypipes | annegent_: #2 is certainly possible. #1, I don't know. | 00:51 |
elmiko | yea, i don't remember how #1 work, but i *think* it's in there | 00:52 |
annegent_ | #link https://github.com/rackerlabs/wadl2swagger/issues/8 | 00:52 |
annegent_ | long read, but two teammates couldn't figure it out jaypipes | 00:52 |
annegent_ | this is all useful. Would you like to have a session on this at the Summit? I think I can find time | 00:52 |
annegent_ | I know docs has a slot for API docs specifically to discuss this spec. | 00:53 |
annegent_ | now, do we make it a docs spec, or an API WG guideline? Discuss. | 00:53 |
annegent_ | as in, "review all code patches to comply with this API WG doc guideline" | 00:53 |
annegent_ | would that work? | 00:53 |
*** alexsyip has quit IRC | 00:53 | |
elmiko | i see several references to headers in https://github.com/swagger-api/swagger-spec | 00:53 |
jaypipes | annegent_: a docs spec. | 00:53 |
elmiko | annegent_: i'd make time for a discussion at summit | 00:54 |
annegent_ | jaypipes: ok | 00:54 |
elmiko | agreed with jaypipes, especially if it continues to be a doc site production for the html side of the api-ref | 00:54 |
annegent_ | #link http://rackerlabs.github.io/wadl2swagger/openstack.html | 00:55 |
jaypipes | annegent_: verified in the 2.0 swagger spec, it has full support for HTTP headers in both request and response. | 00:55 |
annegent_ | but for whatever reason we don't have an Object Storage API swagger there | 00:55 |
annegent_ | so I need to figure out "whatever reason" | 00:55 |
annegent_ | Okay, I think that was all my questions. | 00:56 |
elmiko | wadl2swagger is a nice start, but imo we should ultimately help projects to autogen the base swagger | 00:56 |
annegent_ | #action please comment on the docs spec at https://review.openstack.org/#/c/177934/ | 00:56 |
*** eghobo has quit IRC | 00:56 | |
annegent_ | #action please reply on the openstack-docs mailing list thread here: http://lists.openstack.org/pipermail/openstack-docs/2015-April/006502.html about automation | 00:56 |
annegent_ | elmiko: agreed | 00:56 |
elmiko | thanks for bringing this up annegent_ | 00:56 |
annegent_ | elmiko: thanks for letting me crash in late! | 00:57 |
annegent_ | :) | 00:57 |
elmiko | always =) | 00:57 |
elmiko | ok, any other last minute notes? | 00:57 |
* sigmavirus24 has none | 00:58 | |
miguelgrinberg | nope | 00:58 |
elmiko | thanks for coming out everyone! | 00:58 |
elmiko | #endmeeting | 00:58 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 00:58 | |
openstack | Meeting ended Thu Apr 30 00:58:41 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 00:58 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-04-30-00.01.html | 00:58 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-04-30-00.01.txt | 00:58 |
openstack | Log: http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-04-30-00.01.log.html | 00:58 |
annegent_ | Kilo release tomorrow! Yay! :) | 00:58 |
elmiko | \o/ | 00:58 |
sigmavirus24 | o/ | 00:58 |
*** Rockyg has quit IRC | 00:58 | |
*** banix has quit IRC | 00:59 | |
sigmavirus24 | I'm nervously anticipating Kilo Glance | 00:59 |
elmiko | why nervous? | 01:00 |
*** annegent_ has quit IRC | 01:00 | |
*** ivar-lazzaro has joined #openstack-meeting-3 | 01:02 | |
*** ivar-lazzaro has quit IRC | 01:03 | |
*** mwagner_lap has joined #openstack-meeting-3 | 01:03 | |
*** Swami has quit IRC | 01:04 | |
*** ivar-lazzaro has joined #openstack-meeting-3 | 01:05 | |
*** ivar-lazzaro has quit IRC | 01:05 | |
*** sigmavirus24 is now known as sigmavirus24_awa | 01:05 | |
*** ivar-lazzaro has joined #openstack-meeting-3 | 01:06 | |
*** bknudson has joined #openstack-meeting-3 | 01:09 | |
*** stevemar has joined #openstack-meeting-3 | 01:11 | |
*** markvoelker has joined #openstack-meeting-3 | 01:11 | |
*** elmiko is now known as _elmiko | 01:12 | |
*** baoli has quit IRC | 01:15 | |
*** baoli has joined #openstack-meeting-3 | 01:16 | |
*** sarob has quit IRC | 01:17 | |
*** stanzgy has joined #openstack-meeting-3 | 01:32 | |
*** alex_xu has quit IRC | 01:43 | |
*** Networkn3rd has joined #openstack-meeting-3 | 01:45 | |
*** SumitNaiksatam has joined #openstack-meeting-3 | 01:52 | |
*** stevemar has quit IRC | 01:52 | |
*** SumitNaiksatam has quit IRC | 02:03 | |
*** baoli has quit IRC | 02:07 | |
*** baoli has joined #openstack-meeting-3 | 02:07 | |
*** bpokorny has quit IRC | 02:08 | |
*** yamahata has quit IRC | 02:12 | |
*** stevemar has joined #openstack-meeting-3 | 02:25 | |
*** VW_ has joined #openstack-meeting-3 | 02:30 | |
*** VW_ has quit IRC | 02:32 | |
*** VW_ has joined #openstack-meeting-3 | 02:32 | |
*** Networkn3rd has quit IRC | 02:36 | |
*** stevemar has quit IRC | 02:38 | |
*** yamahata has joined #openstack-meeting-3 | 02:43 | |
*** ir2ivps7 has quit IRC | 02:48 | |
*** stevemar has joined #openstack-meeting-3 | 02:48 | |
*** ir2ivps7 has joined #openstack-meeting-3 | 02:48 | |
*** btully has quit IRC | 02:49 | |
*** baoli has quit IRC | 02:51 | |
*** baoli has joined #openstack-meeting-3 | 02:52 | |
*** baoli_ has joined #openstack-meeting-3 | 02:53 | |
*** baoli has quit IRC | 02:53 | |
*** stanzgy__ has joined #openstack-meeting-3 | 03:31 | |
*** stanzgy has quit IRC | 03:34 | |
*** fallenpegasus has joined #openstack-meeting-3 | 03:36 | |
*** baoli_ has quit IRC | 03:36 | |
*** SumitNaiksatam has joined #openstack-meeting-3 | 03:39 | |
*** fallenpegasus has quit IRC | 03:43 | |
*** fallenpegasus has joined #openstack-meeting-3 | 03:43 | |
*** jckasper has joined #openstack-meeting-3 | 03:46 | |
*** fallenpegasus has quit IRC | 03:48 | |
*** bpokorny has joined #openstack-meeting-3 | 03:50 | |
*** bpokorny has quit IRC | 03:52 | |
*** bpokorny has joined #openstack-meeting-3 | 03:52 | |
*** _elmiko has left #openstack-meeting-3 | 04:07 | |
*** eghobo has joined #openstack-meeting-3 | 04:17 | |
*** VW_ has quit IRC | 04:22 | |
*** jckasper has quit IRC | 04:29 | |
*** ajo has joined #openstack-meeting-3 | 04:49 | |
*** fallenpegasus has joined #openstack-meeting-3 | 05:14 | |
*** wojdev has joined #openstack-meeting-3 | 05:16 | |
*** ivar-laz_ has joined #openstack-meeting-3 | 05:17 | |
*** Nikolay_St has quit IRC | 05:17 | |
*** ivar-laz_ has quit IRC | 05:17 | |
*** emagana has joined #openstack-meeting-3 | 05:19 | |
*** ivar-lazzaro has quit IRC | 05:21 | |
*** btully has joined #openstack-meeting-3 | 05:29 | |
*** wojdev has quit IRC | 05:30 | |
*** wojdev has joined #openstack-meeting-3 | 05:40 | |
*** wojdev has quit IRC | 05:40 | |
*** garyk has joined #openstack-meeting-3 | 05:50 | |
*** mrunge has joined #openstack-meeting-3 | 06:03 | |
*** mrunge has quit IRC | 06:03 | |
*** mrunge has joined #openstack-meeting-3 | 06:03 | |
*** armax has quit IRC | 06:08 | |
*** egallen has joined #openstack-meeting-3 | 06:21 | |
*** mrmartin has joined #openstack-meeting-3 | 06:28 | |
*** [1]evgenyf has joined #openstack-meeting-3 | 06:33 | |
*** eghobo_ has joined #openstack-meeting-3 | 06:36 | |
*** eghobo has quit IRC | 06:39 | |
*** eghobo has joined #openstack-meeting-3 | 06:44 | |
*** e0ne has joined #openstack-meeting-3 | 06:45 | |
*** eghobo_ has quit IRC | 06:45 | |
*** egallen has quit IRC | 06:46 | |
*** stevemar has quit IRC | 06:46 | |
*** kevinbenton has quit IRC | 06:49 | |
*** egallen has joined #openstack-meeting-3 | 06:50 | |
*** eghobo has quit IRC | 06:50 | |
*** kevinbenton has joined #openstack-meeting-3 | 06:50 | |
*** Longgeek has joined #openstack-meeting-3 | 06:52 | |
*** iovadia has joined #openstack-meeting-3 | 06:54 | |
*** jtomasek has joined #openstack-meeting-3 | 06:55 | |
*** rushiagr_away is now known as rushiagr | 06:57 | |
*** scheuran has joined #openstack-meeting-3 | 06:58 | |
*** iovadia has quit IRC | 06:59 | |
*** jcoufal has joined #openstack-meeting-3 | 07:03 | |
*** wojdev has joined #openstack-meeting-3 | 07:03 | |
*** MaxV has joined #openstack-meeting-3 | 07:06 | |
*** Longgeek has quit IRC | 07:07 | |
*** sahid has joined #openstack-meeting-3 | 07:08 | |
*** e0ne has quit IRC | 07:09 | |
*** safchain has joined #openstack-meeting-3 | 07:10 | |
*** Piet has quit IRC | 07:12 | |
*** iovadia has joined #openstack-meeting-3 | 07:13 | |
*** zz_ttrifonov is now known as ttrifonov | 07:13 | |
*** vhoward has quit IRC | 07:13 | |
*** mrmartin has quit IRC | 07:14 | |
*** vhoward has joined #openstack-meeting-3 | 07:15 | |
*** fallenpegasus has quit IRC | 07:17 | |
*** fallenpegasus has joined #openstack-meeting-3 | 07:18 | |
*** Longgeek has joined #openstack-meeting-3 | 07:22 | |
*** alexpilotti has joined #openstack-meeting-3 | 07:23 | |
*** nkrinner has joined #openstack-meeting-3 | 07:27 | |
*** mrmartin has joined #openstack-meeting-3 | 07:29 | |
*** mrmartin has quit IRC | 07:30 | |
*** mrmartin has joined #openstack-meeting-3 | 07:39 | |
*** mrmartin has quit IRC | 07:42 | |
*** irenab_ has joined #openstack-meeting-3 | 07:48 | |
*** irenab has quit IRC | 07:49 | |
*** irenab_ is now known as irenab | 07:49 | |
*** mrmartin has joined #openstack-meeting-3 | 07:59 | |
*** JeanBriceCombebi has joined #openstack-meeting-3 | 08:00 | |
*** wojdev has quit IRC | 08:07 | |
*** btully has quit IRC | 08:07 | |
*** Nikolay_St has joined #openstack-meeting-3 | 08:18 | |
*** roeyc has joined #openstack-meeting-3 | 08:18 | |
*** jcoufal_ has joined #openstack-meeting-3 | 08:21 | |
*** nkrinner has quit IRC | 08:25 | |
*** jcoufal has quit IRC | 08:25 | |
*** nkrinner has joined #openstack-meeting-3 | 08:27 | |
*** garyk has quit IRC | 08:31 | |
*** roeyc has quit IRC | 08:31 | |
*** dobson` has quit IRC | 08:31 | |
*** roeyc has joined #openstack-meeting-3 | 08:31 | |
*** garyk has joined #openstack-meeting-3 | 08:32 | |
*** ajo has quit IRC | 08:34 | |
*** ajo_ has joined #openstack-meeting-3 | 08:34 | |
*** JeanBriceCombebi has quit IRC | 08:36 | |
*** e0ne has joined #openstack-meeting-3 | 08:37 | |
*** matrohon has joined #openstack-meeting-3 | 08:43 | |
*** salv-orl_ has joined #openstack-meeting-3 | 08:45 | |
*** salv-orlando has quit IRC | 08:46 | |
*** belmoreira has joined #openstack-meeting-3 | 08:46 | |
*** dobson has joined #openstack-meeting-3 | 08:49 | |
*** JeanBriceCombebi has joined #openstack-meeting-3 | 08:50 | |
*** wojdev has joined #openstack-meeting-3 | 08:52 | |
*** pkoniszewski has joined #openstack-meeting-3 | 08:53 | |
*** mrmartin has quit IRC | 09:22 | |
*** sankarshan_away is now known as sankarshan_ | 09:40 | |
*** emagana has quit IRC | 09:40 | |
*** e0ne is now known as e0ne_ | 09:48 | |
*** MaxV has quit IRC | 09:57 | |
*** e0ne_ is now known as e0ne | 09:58 | |
*** roeyc has quit IRC | 10:09 | |
*** mwagner_lap has quit IRC | 10:13 | |
*** e0ne is now known as e0ne_ | 10:13 | |
*** e0ne_ is now known as e0ne | 10:16 | |
*** mwagner_lap has joined #openstack-meeting-3 | 10:30 | |
*** yamahata has quit IRC | 10:36 | |
*** stanzgy__ has quit IRC | 10:51 | |
*** alexpilotti has quit IRC | 10:52 | |
*** salv-orlando has joined #openstack-meeting-3 | 10:53 | |
*** salv-orl_ has quit IRC | 10:56 | |
*** banix has joined #openstack-meeting-3 | 11:00 | |
*** e0ne has quit IRC | 11:05 | |
*** rushiagr is now known as rushiagr_away | 11:08 | |
*** roeyc has joined #openstack-meeting-3 | 11:09 | |
*** e0ne has joined #openstack-meeting-3 | 11:10 | |
*** banix has quit IRC | 11:13 | |
*** markvoelker has quit IRC | 11:18 | |
*** e0ne is now known as e0ne_ | 11:20 | |
*** e0ne_ is now known as e0ne | 11:21 | |
*** mwagner_lap has quit IRC | 11:24 | |
*** Longgeek_ has joined #openstack-meeting-3 | 11:31 | |
*** Longgeek has quit IRC | 11:32 | |
*** alexpilotti has joined #openstack-meeting-3 | 11:36 | |
*** alexpilotti has quit IRC | 11:48 | |
*** jcoufal_ is now known as jcoufal | 11:51 | |
*** baoli has joined #openstack-meeting-3 | 11:56 | |
*** VW_ has joined #openstack-meeting-3 | 11:58 | |
*** VW_ has quit IRC | 12:01 | |
*** VW__ has joined #openstack-meeting-3 | 12:01 | |
*** mwagner_lap has joined #openstack-meeting-3 | 12:09 | |
*** markvoelker has joined #openstack-meeting-3 | 12:11 | |
*** sankarshan_ is now known as sankarshan_away | 12:18 | |
*** VW__ has quit IRC | 12:19 | |
*** sankarshan_away is now known as sankarshan_ | 12:29 | |
*** egallen has quit IRC | 12:30 | |
*** Networkn3rd has joined #openstack-meeting-3 | 12:30 | |
*** Longgeek has joined #openstack-meeting-3 | 12:32 | |
*** Longgeek_ has quit IRC | 12:33 | |
*** egallen has joined #openstack-meeting-3 | 12:34 | |
*** sankarshan_ is now known as sankarshan_away | 12:42 | |
*** alexpilotti has joined #openstack-meeting-3 | 12:43 | |
*** Longgeek has quit IRC | 12:44 | |
*** Longgeek_ has joined #openstack-meeting-3 | 12:48 | |
*** doug-fish has left #openstack-meeting-3 | 12:51 | |
*** jckasper has joined #openstack-meeting-3 | 12:58 | |
*** wojdev has quit IRC | 13:03 | |
*** Longgeek_ has quit IRC | 13:04 | |
*** Longgeek has joined #openstack-meeting-3 | 13:05 | |
*** peristeri has joined #openstack-meeting-3 | 13:09 | |
*** bknudson has quit IRC | 13:09 | |
*** MaxV has joined #openstack-meeting-3 | 13:10 | |
*** mrunge has quit IRC | 13:11 | |
*** fallenpegasus has quit IRC | 13:12 | |
*** fallenpegasus has joined #openstack-meeting-3 | 13:13 | |
*** JeanBriceCombebi has quit IRC | 13:14 | |
*** MaxV has quit IRC | 13:15 | |
*** fallenpegasus has quit IRC | 13:17 | |
*** stevemar has joined #openstack-meeting-3 | 13:18 | |
*** JeanBriceCombebi has joined #openstack-meeting-3 | 13:21 | |
*** VW_ has joined #openstack-meeting-3 | 13:22 | |
*** zhenguo has quit IRC | 13:27 | |
*** lsmola_ is now known as lsmola | 13:29 | |
*** wojdev has joined #openstack-meeting-3 | 13:39 | |
*** ajo_ is now known as ajo | 13:40 | |
*** bknudson has joined #openstack-meeting-3 | 13:43 | |
*** sigmavirus24_awa is now known as sigmavirus24 | 13:44 | |
*** Piet has joined #openstack-meeting-3 | 13:50 | |
*** JeanBriceCombebi has quit IRC | 13:52 | |
*** JeanBriceCombebi has joined #openstack-meeting-3 | 13:52 | |
*** Networkn3rd has quit IRC | 13:55 | |
*** garyk has quit IRC | 13:56 | |
*** absubram has joined #openstack-meeting-3 | 13:59 | |
*** irenab has quit IRC | 13:59 | |
*** armax has joined #openstack-meeting-3 | 13:59 | |
*** irenab has joined #openstack-meeting-3 | 14:00 | |
*** JeanBriceCombebi has quit IRC | 14:00 | |
*** JeanBriceCombebi has joined #openstack-meeting-3 | 14:00 | |
*** nkrinner has quit IRC | 14:04 | |
*** irenab has quit IRC | 14:04 | |
*** julim has joined #openstack-meeting-3 | 14:06 | |
*** roeyc has quit IRC | 14:09 | |
*** btully has joined #openstack-meeting-3 | 14:11 | |
*** lsmola has quit IRC | 14:12 | |
*** wojdev has quit IRC | 14:19 | |
*** weiting has joined #openstack-meeting-3 | 14:21 | |
*** jgrimm is now known as zz_jgrimm | 14:22 | |
*** e0ne is now known as e0ne_ | 14:25 | |
*** [1]evgenyf has quit IRC | 14:25 | |
*** mattfarina has joined #openstack-meeting-3 | 14:28 | |
*** VW_ has quit IRC | 14:29 | |
*** e0ne_ is now known as e0ne | 14:30 | |
*** irenab has joined #openstack-meeting-3 | 14:31 | |
*** VW_ has joined #openstack-meeting-3 | 14:32 | |
*** roeyc has joined #openstack-meeting-3 | 14:33 | |
*** irenab has quit IRC | 14:35 | |
*** evgenyf has joined #openstack-meeting-3 | 14:36 | |
*** MarkAtwood has joined #openstack-meeting-3 | 14:42 | |
*** carl_baldwin has joined #openstack-meeting-3 | 14:43 | |
*** emagana has joined #openstack-meeting-3 | 14:45 | |
*** gsagie_ has joined #openstack-meeting-3 | 14:47 | |
*** yalie has joined #openstack-meeting-3 | 14:49 | |
*** saggi1 has joined #openstack-meeting-3 | 14:50 | |
*** mlavalle has joined #openstack-meeting-3 | 14:54 | |
*** vikram__ has joined #openstack-meeting-3 | 14:55 | |
*** nelsnelson has joined #openstack-meeting-3 | 14:56 | |
*** amuller has joined #openstack-meeting-3 | 14:57 | |
mlavalle | carl_baldwin: aren't the dragon flows guys attending the meeting? | 14:57 |
*** tidwellr1 has joined #openstack-meeting-3 | 14:58 | |
gsagie_ | I am here | 14:59 |
gsagie_ | and i think saggi as well | 14:59 |
*** johnbelamaric has joined #openstack-meeting-3 | 14:59 | |
*** lblanchard has joined #openstack-meeting-3 | 15:00 | |
saggi1 | I'm here too | 15:00 |
mlavalle | gsagie_: great. should dragon flows be a point in the agenda? | 15:00 |
saggi1 | mlavalle: yea | 15:00 |
yalie | hi, where could I find the agenda? | 15:00 |
mlavalle | yalie: https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam | 15:01 |
carl_baldwin | hi all. Sorry to be a bit late. | 15:01 |
vikram__ | Carl: hi | 15:01 |
pavel_bondar | hi <carl_baldwin> | 15:01 |
carl_baldwin | #startmeeting neutron_l3 | 15:01 |
openstack | Meeting started Thu Apr 30 15:01:37 2015 UTC and is due to finish in 60 minutes. The chair is carl_baldwin. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:01 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:01 |
johnbelamaric | hi | 15:01 |
*** openstack changes topic to " (Meeting topic: neutron_l3)" | 15:01 | |
openstack | The meeting name has been set to 'neutron_l3' | 15:01 |
carl_baldwin | #topic Announcements | 15:01 |
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)" | 15:01 | |
yalie | mlavalle: thanks | 15:01 |
carl_baldwin | #link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam | 15:01 |
*** pc_m has joined #openstack-meeting-3 | 15:01 | |
saggi1 | mlavalle: We just want to talk a bit about it. And try and get our head around how we fit into liberty | 15:02 |
carl_baldwin | Kilo released today! | 15:02 |
*** emagana has quit IRC | 15:02 | |
* pc_m yay! | 15:02 | |
carl_baldwin | Also, if you have not yet heard, there are changes coming to the feature proposal process. Not merged yet but appears to be gaining momentum. | 15:03 |
carl_baldwin | #link https://review.openstack.org/#/c/177342/ | 15:03 |
*** wojdev has joined #openstack-meeting-3 | 15:04 | |
carl_baldwin | From my perspective, what this means is that there may be less work involved in proposing features for a cycle. The more detailed design discussions can happen more independently when there is more confidence that a feature can be included in the scope of a release. | 15:04 |
*** bpokorny has quit IRC | 15:04 | |
carl_baldwin | If this is the first you’ve heard, I encourage you to go take a look at the review I linked. | 15:05 |
gsagie_ | ok, thanks carl | 15:05 |
*** baoli has quit IRC | 15:05 | |
carl_baldwin | Any other announcements? | 15:05 |
yalie | thanks | 15:05 |
vikram__ | thanks | 15:05 |
carl_baldwin | #topic Bugs | 15:06 |
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)" | 15:06 | |
carl_baldwin | I bumped up the priority of bug 1438819 | 15:06 |
openstack | bug 1438819 in neutron "Router gets address allocation from all new gw subnets" [High,In progress] https://launchpad.net/bugs/1438819 - Assigned to Andrew Boik (drewboik) | 15:06 |
*** baoli has joined #openstack-meeting-3 | 15:07 | |
carl_baldwin | Unfortunately, we didn’t understand the full effect of the bug until it was too late for Kilo. So, it is release noted. | 15:07 |
carl_baldwin | I didn’t mark it critical because it is not a common use case to add a subnet to an external network. | 15:08 |
carl_baldwin | Any other bugs we should be aware of? | 15:08 |
*** stevelle has left #openstack-meeting-3 | 15:09 | |
carl_baldwin | #topic Dragonflow | 15:09 |
*** openstack changes topic to "Dragonflow (Meeting topic: neutron_l3)" | 15:09 | |
* carl_baldwin hopes he got that right. | 15:10 | |
*** MarkAtwood has quit IRC | 15:10 | |
*** iovadia has quit IRC | 15:10 | |
gsagie_ | You got it right | 15:11 |
carl_baldwin | saggi1: Do you have links to introduce this to the team? | 15:11 |
carl_baldwin | gsagie_: ^ | 15:11 |
saggi1 | Sure, https://launchpad.net/dragonflow | 15:11 |
saggi1 | carl_baldwin: Already pointed it out in a previous meeting | 15:11 |
gsagie_ | And you can also read the great blog posts from Eran Gampel here: http://blog.gampel.net | 15:11 |
*** krtaylor has quit IRC | 15:12 | |
mlavalle | saggi1: this is the repo, right: https://github.com/stackforge/dragonflow | 15:12 |
saggi1 | mlavalle: yes | 15:12 |
saggi1 | Basically we don't try and be a new full driver | 15:12 |
saggi1 | We base ourselves on the LegcayRouter and try and optimize where we can using ovs flows on the compute node | 15:12 |
saggi1 | For instance, if you have two VMs from different subnets on the same host. We detect that and install a flow that bypasses the normal routing | 15:13 |
gsagie_ | The idea in a nutshell is to achieve DVR on top of "legacy" L3 implementation using an SDN controller (based on Ryu framework) so we achieve DVR without the need of compute node L3 agents and without namespaces | 15:13 |
carl_baldwin | saggi1: gsagie_: Are there db side changes too? | 15:13 |
saggi1 | carl_baldwin: no | 15:13 |
saggi1 | carl_baldwin: We use the topology information for our optimizations | 15:14 |
saggi1 | tenants, routers, subnets | 15:14 |
gsagie_ | and i believe in the future we will be able to eliminate the L2 agent as we can also leverage security groups driver that configure flows remotely | 15:14 |
carl_baldwin | This is all contained within the L3 agent process? | 15:14 |
mlavalle | saggi1: so, the router namespaces in the network node still exist? | 15:14 |
gsagie_ | mlavalle : no | 15:14 |
gsagie_ | we use open flow flows to achieve the DVR functionallity | 15:14 |
gsagie_ | mlavalle : sorry, for SNAT we use them still | 15:15 |
tidwellr1 | so it's completely flow-based otherwise? | 15:15 |
gsagie_ | mlavalle : but we have future plans to distribute that just as well, design wise its possible | 15:15 |
mlavalle | gsagie_: also with flows, right? | 15:15 |
*** wojdev has quit IRC | 15:15 | |
vikram__ | gsagie: did this support vpn as well? | 15:15 |
saggi1 | We want to offload as much as we can to openflow flows | 15:16 |
yalie | gsagie_: is there dependency on the verison of ovs? | 15:16 |
saggi1 | 1.3 currently | 15:16 |
saggi1 | yalie: ^ | 15:16 |
gsagie_ | mlavalle : in the current design SNAT/FIP is still using legacy L3 | 15:16 |
gsagie_ | yalie: 2.1.3 | 15:16 |
gsagie_ | but we have plans to also implement that using flows, so its mostly a matter of work resources | 15:17 |
*** bpokorny has joined #openstack-meeting-3 | 15:17 | |
*** zz_jgrimm is now known as jgrimm | 15:17 | |
mlavalle | gsagie_: got it | 15:17 |
*** krtaylor has joined #openstack-meeting-3 | 15:18 | |
saggi1 | The design allows us to add more features as we go falling back to other, non-flow, packet delivery for anything we don't implement. | 15:18 |
*** roeyc has quit IRC | 15:19 | |
gsagie_ | I think that getting rid of the agents in the compute node might prove to be a big complexity reducer, and i think the design is simple enough in the controller side so this might be a good reference design for SDN | 15:19 |
carl_baldwin | So, to be clear, you have E/W routing working and N/S routing is still done with the LegacyRouter implementation? | 15:19 |
gsagie_ | carl_baldwin: currently yes | 15:19 |
carl_baldwin | gsagie_: It is a good start. | 15:19 |
mlavalle | gsagie_: what are the benefits performance / throughput wise? | 15:20 |
gsagie_ | mlavalle: we are working on benchmarking this versus current DVR, no results yet, but management complexity wise, i think you can see that we don't need the namespaces is an improvment | 15:20 |
saggi1 | mlavalle: We don't have a lot of data on it. We are still trying to asses how to properly test "real world" use cases. So any suggestions about what to benchmark will be most appriciated. | 15:21 |
vikram__ | gsagie: how it's different from other open controllers like open-contrail? | 15:22 |
saggi1 | Hammering E\W communication saw a 20% increase in throughput IIRC but it was a very simple benchmark. | 15:22 |
*** evgenyf has quit IRC | 15:22 | |
carl_baldwin | I’m very happy to see this work being done. I’d like to continue to support this effort. How has been your experience integrating with the current L3 implementation? I’m hoping your perspective might help to improve the modularity of the code. | 15:22 |
mlavalle | saggi1: I work for a big deployer. We have a tendency to do thins based on flows. I am going to bring this up to my cowworkers and we may get back to you | 15:22 |
saggi1 | carl_baldwin: It's been problematic. But it's getting better. | 15:23 |
saggi1 | carl_baldwin: A lot of dvr specific code is causing odd bus for us. | 15:24 |
*** belmoreira has quit IRC | 15:24 | |
saggi1 | That being said in the last couple of months there was a lot of work in decoupling l2 from l3 and it's been very helpful. | 15:24 |
gsagie_ | vikram_ : we are trying to build this in a very simple way, we leverage Ryu for the simplicity but any other SDN controller can be used, but we don't want to introduce more complexity if we don't need too | 15:24 |
carl_baldwin | saggi1: gsagie_: I wonder if we could get together with a little more time to discuss it. Either at summit — which may or may not be possible for me — or at another time. | 15:24 |
carl_baldwin | saggi1: I’m glad to hear that we’re moving in a good direction. | 15:25 |
vikram__ | Carl: +1 | 15:25 |
mlavalle | saggi1: by the way, we are doing things with Ryu, so there's affinity already | 15:25 |
vikram__ | gsagie: thanks got it | 15:25 |
*** e0ne is now known as e0ne_ | 15:25 | |
gsagie_ | carl_baldwin: We would love to meet in the summit and further discuss it, hopefully we will also have some numbers to show you | 15:25 |
mlavalle | gsagie_, carl_baldwin: I am available, willing to meet at summit | 15:26 |
pc_m | would be interesting to learn more | 15:26 |
gsagie_ | I think we would love to make this a joint effort, because i think that idea wise this design can be a good reference | 15:26 |
tidwellr1 | I would love to learn a little more too | 15:26 |
vikram__ | idea sounds really interesting. I am in. | 15:27 |
carl_baldwin | We’ll find some time at the summit for it. I’m not sure about my complete schedule but I’d like to fit this in. My focus will be on what steps we can take to allow your efforts to continue successfully in parallel with the existing L3 implementation. | 15:27 |
yalie | so, this is a new implement of DVR, will re-use the API now? | 15:28 |
saggi1 | carl_baldwin: That is exactly what we want to nail down. Since, as you can see, we depend on a lot of core l3 code | 15:28 |
*** MarkAtwood has joined #openstack-meeting-3 | 15:28 | |
gsagie_ | carl_baldwin: is the L3 reference implementation going out of tree? | 15:28 |
*** scheuran has quit IRC | 15:29 | |
carl_baldwin | I’m thinking about the Friday as a “contributor meetup” | 15:29 |
mlavalle | carl_baldwin: +1 | 15:29 |
vikram__ | timing? | 15:29 |
*** marun has joined #openstack-meeting-3 | 15:29 | |
carl_baldwin | gsagie_: I’m not 100% sure yet. So far, there are no immediate plans. | 15:30 |
carl_baldwin | gsagie_: saggi1: Will you be staying until Friday? | 15:30 |
*** garyk has joined #openstack-meeting-3 | 15:31 | |
gsagie_ | carld_baldwin: yes | 15:31 |
gsagie_ | carl_baldwin | 15:31 |
*** irenab has joined #openstack-meeting-3 | 15:31 | |
carl_baldwin | #action carl_baldwin to setup a time and place on Friday for a contributor meetup on L3 modularity and supporting development of dragonflow. | 15:32 |
gsagie_ | thanks carl ! | 15:33 |
saggi1 | thanks | 15:33 |
*** kozhukalov has joined #openstack-meeting-3 | 15:33 | |
carl_baldwin | gsagie_: saggi1: Thank you for coming to the meeting. I look forward to hearing more about your work. I will read the blog posts and look through the code repository that you have linked. | 15:34 |
carl_baldwin | Anything else on this topic for now? | 15:34 |
*** sergef has joined #openstack-meeting-3 | 15:34 | |
gsagie_ | not from me, thanks | 15:34 |
yalie | I have a question | 15:34 |
gsagie_ | feel free to approach any of us online if you have any question | 15:34 |
gsagie_ | yalie: yes? | 15:35 |
*** e0ne_ is now known as e0ne | 15:35 | |
yalie | about the gateway of subnet, when a VM act as a router | 15:35 |
mlavalle | gsagie_: you hang out in #openstack-neutron? | 15:35 |
gsagie_ | yes | 15:35 |
saggi1 | mlavalle: yes | 15:35 |
yalie | we can't assign the gateway with a VM' port IP | 15:35 |
mlavalle | :-) | 15:35 |
yalie | but when the VM as a service like router, we need it | 15:35 |
yalie | could we remove this limitation? | 15:36 |
*** irenab has quit IRC | 15:36 | |
saggi1 | yalie: We would need to get that information from the DB. To know that this VM is a router. Since this is where we get the topology informationfrom | 15:36 |
carl_baldwin | yalie: Could we postpone this for Open Discussion. Or, we could discuss in the neutron channel just after the meeting. | 15:36 |
saggi1 | carl_baldwin: sure | 15:36 |
yalie | carl_baldwin: yes, thanks | 15:36 |
carl_baldwin | #topic bgp-dynamic-routing | 15:37 |
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)" | 15:37 | |
carl_baldwin | devessa cannot make it today. | 15:37 |
carl_baldwin | tidwellr1: Do you want to give an update quickly? | 15:37 |
tidwellr1 | sure | 15:37 |
tidwellr1 | I'm working through the tutorial here https://wiki.openstack.org/wiki/Neutron/DynamicRouting/TestingDynamicRouting | 15:38 |
tidwellr1 | I'm deviating from it slightly as I'm interested in how to go about automated testing og BGP advertisements | 15:39 |
*** emagana has joined #openstack-meeting-3 | 15:39 | |
tidwellr1 | I'm mixing extra quagga instances, but following instructions otherwise | 15:40 |
*** Swami has joined #openstack-meeting-3 | 15:41 | |
*** pkoniszewski has quit IRC | 15:41 | |
*** sergef has quit IRC | 15:41 | |
carl_baldwin | tidwellr1: Sounds like good progress but we’ve caught you in the middle of getting it on its feet. | 15:41 |
tidwellr1 | that's OK | 15:41 |
tidwellr1 | I'm really coming at this from the testing perspective | 15:42 |
carl_baldwin | tidwellr1: understood. Keep up the good work. | 15:42 |
tidwellr1 | I'll have more to share next week | 15:43 |
carl_baldwin | tidwellr1: Do you think it would be difficult to run quagga on the same VM instance with devstack, adding routes to br-ex instead of eth0? It may be very difficult still to get automated testing in the gate needing more than one instance. | 15:43 |
carl_baldwin | Something to think about… We should probably move on and get to ipam before the meeting time is over. | 15:45 |
carl_baldwin | #topic neutron-ipam | 15:45 |
*** openstack changes topic to "neutron-ipam (Meeting topic: neutron_l3)" | 15:45 | |
tidwellr1 | yeah, that's a concern. I have a couple ideas I'm going to play with, I'll report back next week | 15:45 |
carl_baldwin | johnbelamaric: tidwellr1: pavel_bondar: ping | 15:45 |
*** jcoufal has quit IRC | 15:45 | |
pavel_bondar | pong | 15:45 |
johnbelamaric | carl_baldwin: hello | 15:45 |
carl_baldwin | I’ve been watching the progress with getting the tests to pass. | 15:46 |
carl_baldwin | Nice work so far. | 15:46 |
pavel_bondar | it's close:) | 15:46 |
carl_baldwin | I also started reviewing the patch but I did not finish. It is a pretty large patch. | 15:46 |
pavel_bondar | I switched back to pass subnet_id in interface instead of subnet_dict and has a workaround for issue with OpenContrail tests | 15:47 |
johnbelamaric | carl_baldwin, pavel_bondar, tidwellr1: I think there is one comment left to address from Ryan regarding duplicate code | 15:48 |
pavel_bondar | Also I sent to ML my finding about original issue I had with OpenContrail tests and fetching subnet using plugin. #link http://lists.openstack.org/pipermail/openstack-dev/2015-April/063004.html | 15:49 |
*** yamahata has joined #openstack-meeting-3 | 15:49 | |
pavel_bondar | john, could you please point which comment? | 15:49 |
johnbelamaric | *looking* | 15:50 |
carl_baldwin | pavel_bondar: Thanks for pointing out the ML post. I have not visited the ML yet today. :) | 15:50 |
tidwellr1 | I struggled with the OpenContrail tests as well, they extend the db_plugin tests in some interesting ways | 15:51 |
pavel_bondar | tidwellr1: yeah, they do not call super methods directly, but instead create new http request, so they are quite different from others | 15:53 |
tidwellr1 | I ended up writing new test cases that the OpenContrail tests wouldn't extend as my hack, but that's not really an option here is it :) | 15:54 |
*** lblanchard has quit IRC | 15:54 | |
*** egallen has quit IRC | 15:55 | |
johnbelamaric | pavel_bondar: nevermind, you fixed it in PS 51 | 15:55 |
*** emagana has quit IRC | 15:57 | |
pavel_bondar | johnbelamaric: yeah, right, workaround was used to bypass plugin level and call _get_subnet directly from db_base | 15:57 |
johnbelamaric | pavel_bondar: I was referring to the open comment I thought there was, it was done in 51 | 15:57 |
pavel_bondar | ah:) | 15:57 |
pavel_bondar | got it | 15:57 |
pavel_bondar | but yeah, OpenContrail issue is not high priority for now since I have workaround, but it is still interesting why it deletes port on fetching subnet | 15:59 |
*** ryansb has joined #openstack-meeting-3 | 15:59 | |
*** wojdev has joined #openstack-meeting-3 | 15:59 | |
carl_baldwin | We can take this to the neutron room. We’re out of time. :) | 15:59 |
carl_baldwin | Thanks for all your work. | 15:59 |
carl_baldwin | #endmeeting | 15:59 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 15:59 | |
openstack | Meeting ended Thu Apr 30 15:59:55 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:59 |
*** emagana has joined #openstack-meeting-3 | 15:59 | |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-04-30-15.01.html | 15:59 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-04-30-15.01.txt | 15:59 |
openstack | Log: http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-04-30-15.01.log.html | 16:00 |
pavel_bondar | thanks | 16:00 |
*** pc_m has left #openstack-meeting-3 | 16:00 | |
*** saggi1 has quit IRC | 16:00 | |
yalie | Hi carl_baldwin? could we talk about that subnet gateway problem? | 16:01 |
carl_baldwin | yalie: Yes, could you jump over to the neutron room? | 16:01 |
*** alexsyip has joined #openstack-meeting-3 | 16:01 | |
*** johnbelamaric has left #openstack-meeting-3 | 16:01 | |
*** baoli has quit IRC | 16:02 | |
carl_baldwin | openstack-neutron | 16:02 |
carl_baldwin | oops. | 16:02 |
carl_baldwin | #openstack-neutron | 16:02 |
*** weiting has quit IRC | 16:02 | |
yalie | carl_baldwin: OK, thanks! | 16:02 |
*** baoli_ has joined #openstack-meeting-3 | 16:03 | |
*** vikram__ has quit IRC | 16:06 | |
*** fallenpegasus has joined #openstack-meeting-3 | 16:08 | |
*** JeanBriceCombebi has quit IRC | 16:10 | |
ryansb | anybody about for api-wg? | 16:11 |
krotscheck | ryansb: I am | 16:11 |
krotscheck | ryansb: But I'm guessing nobody else is. | 16:11 |
ryansb | seems so ¯\_ツ_/¯ | 16:12 |
ryansb | anyways, unless anyone else shows up we'll just call it cancelled | 16:12 |
*** Swami has quit IRC | 16:13 | |
*** egallen has joined #openstack-meeting-3 | 16:13 | |
*** salv-orlando has quit IRC | 16:17 | |
*** salv-orlando has joined #openstack-meeting-3 | 16:19 | |
*** Nikolay_St has quit IRC | 16:21 | |
*** julim has quit IRC | 16:22 | |
*** krtaylor has quit IRC | 16:25 | |
*** matrohon has quit IRC | 16:25 | |
*** ryansb has left #openstack-meeting-3 | 16:26 | |
*** gsagie_ has left #openstack-meeting-3 | 16:26 | |
*** Networkn3rd has joined #openstack-meeting-3 | 16:28 | |
*** Networkn3rd has quit IRC | 16:31 | |
*** Networkn3rd has joined #openstack-meeting-3 | 16:31 | |
*** safchain has quit IRC | 16:38 | |
*** krtaylor has joined #openstack-meeting-3 | 16:38 | |
*** eghobo has joined #openstack-meeting-3 | 16:39 | |
*** tidwellr1 has left #openstack-meeting-3 | 16:42 | |
*** alexpilotti has quit IRC | 16:46 | |
*** igordcard_ has quit IRC | 16:46 | |
*** e0ne is now known as e0ne_ | 16:49 | |
*** e0ne_ is now known as e0ne | 16:50 | |
*** e0ne has quit IRC | 16:51 | |
*** cawil1 has quit IRC | 16:52 | |
*** melwitt has joined #openstack-meeting-3 | 16:55 | |
*** igordcard_ has joined #openstack-meeting-3 | 16:56 | |
*** igordcard_ has quit IRC | 16:56 | |
*** igordcard_ has joined #openstack-meeting-3 | 16:58 | |
*** bpokorny_ has joined #openstack-meeting-3 | 16:58 | |
*** igordcard_ has quit IRC | 16:58 | |
*** emagana has quit IRC | 17:00 | |
*** bpokorny has quit IRC | 17:01 | |
*** irenab has joined #openstack-meeting-3 | 17:01 | |
*** Sukhdev has joined #openstack-meeting-3 | 17:02 | |
*** Youcef has joined #openstack-meeting-3 | 17:04 | |
*** amuller has left #openstack-meeting-3 | 17:05 | |
*** irenab has quit IRC | 17:06 | |
*** emagana has joined #openstack-meeting-3 | 17:06 | |
*** yamahata has quit IRC | 17:07 | |
*** eghobo_ has joined #openstack-meeting-3 | 17:09 | |
*** beagles is now known as beagles_brb | 17:11 | |
*** eghobo has quit IRC | 17:12 | |
*** sahid has quit IRC | 17:12 | |
*** salv-orlando has quit IRC | 17:16 | |
*** wojdev has quit IRC | 17:16 | |
*** salv-orlando has joined #openstack-meeting-3 | 17:16 | |
*** yalie has quit IRC | 17:17 | |
*** beagles_brb is now known as beagles | 17:18 | |
*** salv-orlando has quit IRC | 17:21 | |
*** sarob has joined #openstack-meeting-3 | 17:21 | |
*** salv-orlando has joined #openstack-meeting-3 | 17:21 | |
*** sbalukoff has quit IRC | 17:23 | |
*** wojdev has joined #openstack-meeting-3 | 17:27 | |
*** yamahata has joined #openstack-meeting-3 | 17:29 | |
*** ivar-lazzaro has joined #openstack-meeting-3 | 17:29 | |
*** mrmartin has joined #openstack-meeting-3 | 17:30 | |
*** SumitNaiksatam has quit IRC | 17:34 | |
*** emagana has quit IRC | 17:35 | |
*** bpokorny_ has quit IRC | 17:39 | |
*** VW_ has quit IRC | 17:40 | |
*** ketem-shemen__ has joined #openstack-meeting-3 | 17:40 | |
*** megm_ has joined #openstack-meeting-3 | 17:40 | |
*** lintan_ has joined #openstack-meeting-3 | 17:41 | |
*** Nikolay_St has joined #openstack-meeting-3 | 17:41 | |
*** VW_ has joined #openstack-meeting-3 | 17:41 | |
*** GheRiver1 has joined #openstack-meeting-3 | 17:41 | |
*** VW__ has joined #openstack-meeting-3 | 17:42 | |
*** VW__ has quit IRC | 17:42 | |
*** VW__ has joined #openstack-meeting-3 | 17:43 | |
*** coolsvapl has joined #openstack-meeting-3 | 17:45 | |
*** sdague_ has joined #openstack-meeting-3 | 17:45 | |
*** VW_ has quit IRC | 17:46 | |
*** carl_baldwin_ has joined #openstack-meeting-3 | 17:46 | |
*** carl_baldwin has quit IRC | 17:46 | |
*** ketem-shemen_ has quit IRC | 17:47 | |
*** kbyrne has quit IRC | 17:47 | |
*** megm has quit IRC | 17:47 | |
*** GheRivero has quit IRC | 17:47 | |
*** lintan has quit IRC | 17:47 | |
*** sdague has quit IRC | 17:47 | |
*** coolsvap|afk has quit IRC | 17:47 | |
*** salv-orlando has quit IRC | 17:47 | |
*** jkoelker has quit IRC | 17:47 | |
*** devananda has quit IRC | 17:47 | |
*** VW_ has joined #openstack-meeting-3 | 17:47 | |
*** carl_baldwin_ is now known as carl_baldwin | 17:47 | |
*** sdague_ is now known as sdague | 17:47 | |
*** salv-orlando has joined #openstack-meeting-3 | 17:49 | |
*** jkoelker has joined #openstack-meeting-3 | 17:49 | |
*** devananda has joined #openstack-meeting-3 | 17:49 | |
*** VW__ has quit IRC | 17:51 | |
*** rkukura has joined #openstack-meeting-3 | 17:51 | |
*** kbyrne has joined #openstack-meeting-3 | 17:54 | |
*** SumitNaiksatam has joined #openstack-meeting-3 | 17:56 | |
*** igordcard has joined #openstack-meeting-3 | 17:56 | |
*** vgridnev_ has joined #openstack-meeting-3 | 17:58 | |
SumitNaiksatam | rkukura: igordcard ivar-lazzaro hi | 18:01 |
rkukura | hi | 18:01 |
ivar-lazzaro | hi | 18:01 |
SumitNaiksatam | #startmeeting networking_policy | 18:01 |
openstack | Meeting started Thu Apr 30 18:01:36 2015 UTC and is due to finish in 60 minutes. The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot. | 18:01 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 18:01 |
*** openstack changes topic to " (Meeting topic: networking_policy)" | 18:01 | |
openstack | The meeting name has been set to 'networking_policy' | 18:01 |
igordcard | hello all | 18:01 |
SumitNaiksatam | #info agenda https://wiki.openstack.org/wiki/Meetings/GroupBasedPolicy#April_30th.2C_23rd.2C_2015 | 18:01 |
*** e0ne has joined #openstack-meeting-3 | 18:02 | |
SumitNaiksatam | #topic Bugs | 18:02 |
*** openstack changes topic to "Bugs (Meeting topic: networking_policy)" | 18:02 | |
*** irenab has joined #openstack-meeting-3 | 18:02 | |
SumitNaiksatam | i think only the back port for this is not merged: #link https://bugs.launchpad.net/group-based-policy/+bug/1432779 | 18:03 |
openstack | Launchpad bug 1432779 in Group Based Policy "redirect actions don't work with external policies" [Critical,In progress] - Assigned to Ivar Lazzaro (mmaleckk) | 18:03 |
SumitNaiksatam | other than that, i dont think we have any reported outstanding critical bugs | 18:03 |
SumitNaiksatam | any other bugs to discuss today? | 18:04 |
SumitNaiksatam | okay perhaps not | 18:04 |
SumitNaiksatam | #topic Functional/Integration Tests | 18:04 |
*** openstack changes topic to "Functional/Integration Tests (Meeting topic: networking_policy)" | 18:04 | |
*** yapeng has joined #openstack-meeting-3 | 18:05 | |
SumitNaiksatam | #link https://review.openstack.org/#/c/174267 | 18:05 |
SumitNaiksatam | the above patch starts running jishnu’s test suite which performs integration testing by exercising GBP REST and client interfaces | 18:05 |
ivar-lazzaro | nice! | 18:06 |
SumitNaiksatam | at this point all tests are passing in that test suite | 18:06 |
*** huichun has joined #openstack-meeting-3 | 18:06 | |
ivar-lazzaro | do we know what is covered by the tests? | 18:06 |
SumitNaiksatam | we have to fix some bugs which this test suite caught | 18:06 |
SumitNaiksatam | it covers all the resources we had in juno | 18:06 |
SumitNaiksatam | and some scenarios | 18:07 |
rkukura | are tests disabled due to bugs? | 18:07 |
SumitNaiksatam | rkukura: no tests are currently disabled | 18:07 |
SumitNaiksatam | i mean no tests in that test suite are disabled | 18:07 |
rkukura | if they all pass, why do we have to fix some bugs? | 18:07 |
SumitNaiksatam | rkukura: they were not passing before | 18:07 |
rkukura | OK, so they have already been fixed? | 18:08 |
SumitNaiksatam | yeah, as of yesterday | 18:08 |
SumitNaiksatam | so you see the job passing today | 18:08 |
rkukura | great, I was confused by “we have to fix” implying they weren’t already fixed | 18:08 |
ivar-lazzaro | rkukura: +1 :) | 18:08 |
*** bpokorny has joined #openstack-meeting-3 | 18:09 | |
*** irenab has quit IRC | 18:09 | |
SumitNaiksatam | oh, sorry, i meant to say “had” not “have”…my bad | 18:09 |
rkukura | no problem | 18:09 |
*** songole has joined #openstack-meeting-3 | 18:09 | |
SumitNaiksatam | in some cases the bugs were fixed but the tests were not updated | 18:09 |
SumitNaiksatam | in the sense that the tests were not checking for the right result | 18:09 |
SumitNaiksatam | so a combination of things | 18:09 |
SumitNaiksatam | but anyway, right now its clean | 18:10 |
SumitNaiksatam | it would have been good to have jishnu in this meeting to answer specific questions on the extent of coverage | 18:10 |
SumitNaiksatam | but he is in travel right now | 18:10 |
SumitNaiksatam | the patch itself is just shell script enabling the tests | 18:11 |
ivar-lazzaro | SumitNaiksatam: is the test suite published anywhere? | 18:12 |
SumitNaiksatam | yapeng: songole: hi thanks for joining | 18:12 |
songole | hello | 18:12 |
ivar-lazzaro | SumitNaiksatam: It would be good to have a feeling of which datapath scenario are covered | 18:12 |
ivar-lazzaro | songole: hi | 18:12 |
*** emagana has joined #openstack-meeting-3 | 18:12 | |
rkukura | do the same tests run for both master and stable/juno? | 18:12 |
songole | ivar-lazzaro: hi | 18:12 |
SumitNaiksatam | ivar-lazzaro: firstly the test suite is not doing data path testing | 18:13 |
SumitNaiksatam | ivar-lazzaro: the tests are published in pypi package | 18:14 |
SumitNaiksatam | rkukura: the same tests run for both master and stable/juno | 18:14 |
rkukura | SumitNaiksatam: What will we do when master diverges from stable/juno so that we need different tests? Can we branch the test repo too? | 18:15 |
SumitNaiksatam | rkukura: yes | 18:15 |
SumitNaiksatam | rkukura: right now the test suite mostly covers the juno features | 18:15 |
*** Swami has joined #openstack-meeting-3 | 18:16 | |
SumitNaiksatam | any other questions on this test case? | 18:17 |
*** ivar-laz_ has joined #openstack-meeting-3 | 18:17 | |
*** mlavalle has quit IRC | 18:18 | |
*** VW_ has quit IRC | 18:18 | |
SumitNaiksatam | hopefully we can get the patch merged soon | 18:18 |
*** egallen has quit IRC | 18:18 | |
SumitNaiksatam | #topic Packaging Update | 18:18 |
*** openstack changes topic to "Packaging Update (Meeting topic: networking_policy)" | 18:18 | |
*** mwang2 has joined #openstack-meeting-3 | 18:19 | |
SumitNaiksatam | rkukura: anything to update here? | 18:19 |
rkukura | I have not made any progress on fedora/RDO packages (was on PTO last week). | 18:20 |
*** Sukhdev has quit IRC | 18:20 | |
rkukura | I checked today and it looks like all the tarballs on launchpad are at least a month old. Are we waiting for new ones? | 18:20 |
*** ivar-laz_ has quit IRC | 18:20 | |
*** baoli_ has quit IRC | 18:20 | |
*** Sukhdev has joined #openstack-meeting-3 | 18:20 | |
SumitNaiksatam | rkukura: we havent cut kilo-3 yet | 18:20 |
rkukura | that’s what I thought | 18:20 |
SumitNaiksatam | if thats what you are looking for | 18:20 |
rkukura | that, and a new stable/juno release I think | 18:20 |
SumitNaiksatam | or were you looking for another stable/juno? | 18:21 |
*** ivar-lazzaro has quit IRC | 18:21 | |
SumitNaiksatam | ah just asking that | 18:21 |
*** baoli_ has joined #openstack-meeting-3 | 18:21 | |
rkukura | I can certainly update to the stable/juno tarballs we have, but thought we had lots of fixes since then | 18:21 |
SumitNaiksatam | rkukura: okay lets sync up after this meeting on this | 18:21 |
rkukura | sure | 18:21 |
*** Yi has joined #openstack-meeting-3 | 18:21 | |
SumitNaiksatam | #topic Kilo Sync | 18:22 |
*** openstack changes topic to "Kilo Sync (Meeting topic: networking_policy)" | 18:22 | |
rkukura | I’d like to get the fedora packages update soon enough that the RDO packags will be updated by the summit. | 18:22 |
SumitNaiksatam | rkukura: okay, lets work towards getting you need for that | 18:22 |
SumitNaiksatam | *what you | 18:22 |
rkukura | SumitNaiksatam: thanks | 18:22 |
SumitNaiksatam | rkukura: i will ping you after this meeting | 18:22 |
SumitNaiksatam | regarding kilo sync | 18:23 |
SumitNaiksatam | the last vestiges of kilo sync are complete meaning - GBP-UI and GBP-Automation projects are is sync with kilo | 18:23 |
SumitNaiksatam | also the kilo-gbp devstack branch is functional with kilo | 18:24 |
igordcard | SumitNaiksatam, nice | 18:24 |
SumitNaiksatam | by functional with kilo I mean, it uses stable/kilo branches for openstack projects | 18:24 |
igordcard | SumitNaiksatam, was the kilo-gbp devstack branch broken last saturday? | 18:24 |
*** ivar-lazzaro has joined #openstack-meeting-3 | 18:24 | |
SumitNaiksatam | igordcard: yes it was broken at different times :-) | 18:25 |
igordcard | SumitNaiksatam, okay | 18:25 |
SumitNaiksatam | i have tested this, but please let me know if you see any issues | 18:25 |
ivar-lazzaro | mac died, sorry about that | 18:25 |
SumitNaiksatam | ivar-lazzaro: np | 18:25 |
*** baoli_ has quit IRC | 18:25 | |
ivar-lazzaro | did I miss anything exciting? | 18:25 |
*** songole has quit IRC | 18:25 | |
SumitNaiksatam | the kilo-gbp branch itself is based on upstream devstack stable/juno | 18:25 |
SumitNaiksatam | ivar-lazzaro: no, same old boring stuff! ;-) | 18:26 |
igordcard | last night (your afternoon) kilo-gbp ran without any issues here | 18:26 |
SumitNaiksatam | at this point i consider the kilo-sync acitivity to be complete | 18:26 |
SumitNaiksatam | ivar-lazzaro: ah okay, good to know | 18:26 |
*** ajo has quit IRC | 18:26 | |
SumitNaiksatam | one thing to note, especially rkukura - the gbp client also has progressed to sync with kilo | 18:27 |
SumitNaiksatam | it means that for using GBP stable/juno we have to use 0.9.1 version of the client | 18:27 |
rkukura | SumitNaiksatam: For fedora and RDO, we’ll need to be compatible with the client versions included in those releases | 18:28 |
SumitNaiksatam | by version, i mean its a 0.9.1 tag in the repo | 18:28 |
*** sbalukoff has joined #openstack-meeting-3 | 18:28 | |
igordcard | will python-openstackclient be extended to support gbp? | 18:28 |
SumitNaiksatam | rkukura: so 0.9.1 should work with openstack stable/juno | 18:28 |
*** egallen has joined #openstack-meeting-3 | 18:29 | |
SumitNaiksatam | igordcard: my understanding is that python-openstackclient has a modular architecture such that we could extend it without us having to push anything into python-openstackclient, is that correct? | 18:29 |
igordcard | SumitNaiksatam, I haven't seen the internals of python-openstackclient but the individual clients seem to be getting deprecated, so I asked | 18:30 |
*** mrmartin has quit IRC | 18:30 | |
SumitNaiksatam | igordcard: i believe this discussion came up in the context of neutron as well, and the last i heard they were not planning to move immediately (or at least were not being forced to) | 18:31 |
SumitNaiksatam | but i have not been uptodate with that | 18:31 |
SumitNaiksatam | that said i dont think we are targeting any of this acitivity for kilo | 18:31 |
SumitNaiksatam | unless we are forced to | 18:31 |
SumitNaiksatam | of course, definitely something we do plan to do | 18:31 |
*** mattfarina has quit IRC | 18:31 | |
SumitNaiksatam | igordcard: in case you want to scope out what it involves, that would be great | 18:31 |
igordcard | SumitNaiksatam, I can do that | 18:32 |
SumitNaiksatam | just to assess the amount of work both from a technical and resource perspective | 18:32 |
SumitNaiksatam | igordcard: great, thanks | 18:32 |
SumitNaiksatam | #topic Floating IP | 18:32 |
*** openstack changes topic to "Floating IP (Meeting topic: networking_policy)" | 18:32 | |
SumitNaiksatam | i think magesh is on PTO | 18:33 |
SumitNaiksatam | but i did notice that he addresses the review comments and has posted a new version of the spec | 18:33 |
SumitNaiksatam | Spec #link https://review.openstack.org/#/c/167174 | 18:33 |
SumitNaiksatam | Implementation #link https://review.openstack.org/#/c/167174/ | 18:33 |
*** Youcef has quit IRC | 18:33 | |
SumitNaiksatam | at this point i believe whatever was discussed in the numerous discussions has been captured and mostly implemented | 18:34 |
SumitNaiksatam | since magesh is not here, comments will have to go to the review | 18:34 |
SumitNaiksatam | #topic Service Chain provider refactor | 18:35 |
*** openstack changes topic to "Service Chain provider refactor (Meeting topic: networking_policy)" | 18:35 | |
SumitNaiksatam | Spec #link https://review.openstack.org/#/c/174118 | 18:36 |
SumitNaiksatam | Impl #link https://review.openstack.org/#/q/status:open+project:stackforge/group-based-policy+branch:master+topic:bp/sc-refactor,n,z | 18:36 |
SumitNaiksatam | so there were few revs on the spec, and ivar-lazzaro has posted WIP patches as well per the current state of the spec | 18:36 |
ivar-lazzaro | #link https://review.openstack.org/#/q/status:open+project:stackforge/group-based-policy+branch:master+topic:bp/node-centric-chain-plugin,n,z | 18:36 |
ivar-lazzaro | The topic is different, just to be more specific | 18:37 |
ivar-lazzaro | there was no blueprint yet in launchpad | 18:37 |
SumitNaiksatam | ivar-lazzaro: okay i will add it | 18:38 |
ivar-lazzaro | SumitNaiksatam: it's there now, just with a different topic #link https://blueprints.launchpad.net/openstack/?searchtext=node-centric-chain-plugin | 18:38 |
ivar-lazzaro | SumitNaiksatam: I arbitrarily chose it, but we can change it at any time if we want to | 18:39 |
SumitNaiksatam | ivar-lazzaro: nit comment - i prefer calling this a “nodes composition plugin” NCP | 18:40 |
ivar-lazzaro | SumitNaiksatam: I like node composition better too | 18:41 |
ivar-lazzaro | SumitNaiksatam: however I would use "Chain" instead of "Plugin" | 18:41 |
SumitNaiksatam | ivar-lazzaro: i would intentionally avoid “chain" | 18:41 |
ivar-lazzaro | SumitNaiksatam: plugin would be implicit in this case, but it's at least clear that it's a servicechain implementation | 18:41 |
SumitNaiksatam | other than that, the ability to pass service-specific key-value pairs also needs to be there | 18:41 |
ivar-lazzaro | SumitNaiksatam: about that, I was wondering if we need to introduce the concept of "tag" | 18:42 |
ivar-lazzaro | It would be a different URI, something like /tags | 18:42 |
ivar-lazzaro | in which you could define metadata for all the GBP objects (and SC) without changing them directly | 18:42 |
ivar-lazzaro | The main point of Tags is that they will be for consumption of entities outside of GBP itself | 18:43 |
ivar-lazzaro | (eg. UI, Automation, etc...) | 18:43 |
SumitNaiksatam | thats definitely an option as we discussed | 18:43 |
SumitNaiksatam | i would prefer to not call it tags, since we also have the notion of policy “labels” and can be confusing | 18:44 |
ivar-lazzaro | So that every "internal" API (eg. service_profile, that needs to be consumed by the Node Drivers) can be defined by APIs and Extensions | 18:44 |
SumitNaiksatam | but names aside, it would be good to hear from the rest of the team on this | 18:44 |
ivar-lazzaro | SumitNaiksatam: Difference between labels and tags is that the latter won't be understood by internal GBP components | 18:45 |
ivar-lazzaro | SumitNaiksatam: but we can choose a different name for that nonetheless | 18:45 |
SumitNaiksatam | ivar-lazzaro: i dont think it will never be the case that a node driver does not use a service-specific meta-data attribute - that is an implementation detail for the node driver | 18:45 |
ivar-lazzaro | SumitNaiksatam: right, but since the node understands it, then it could as well just be an extension of service_profile | 18:46 |
ivar-lazzaro | SumitNaiksatam: instead of a generic key-value pair | 18:46 |
SumitNaiksatam | the benefit of having this common metadata resource approach is that it allows us to associate aribitrary meta-data with any GBP resources | 18:47 |
ivar-lazzaro | SumitNaiksatam: while for externally consumed metadata, we can use tags (of course the driver could tag a node) | 18:47 |
rkukura | This is not sounding very intent-oriented :( | 18:47 |
SumitNaiksatam | the downside is that it requires the user to correlate information | 18:47 |
ivar-lazzaro | rkukura: tags are not intended to change the resource behavior, they are useful for external automation more than anythig | 18:48 |
ivar-lazzaro | rkukura: for example: which UI should I use to manage this Node? | 18:48 |
rkukura | I don’t see how “nodes” have much to do with “intent” | 18:49 |
SumitNaiksatam | rkukura: i agree that the level of the node driver its not an intent abstraction any more | 18:49 |
ivar-lazzaro | rkukura: on that I agree. However keep in mind that we are talking about an operator API | 18:49 |
rkukura | I admit I have not been following previous discussions on this, or the BP, so I’m not even sure what a “node driver” is. | 18:49 |
igordcard | but the user does not need to deal with a Node directly | 18:50 |
SumitNaiksatam | rkukura: however its not the “nodes”, its the “nodes driver” | 18:50 |
rkukura | ivar-lazzaro: If its purely operation API, I’m not as concerned. | 18:50 |
rkukura | operator | 18:50 |
ivar-lazzaro | igordcard: +1 | 18:50 |
*** Nikolay_St has quit IRC | 18:50 | |
SumitNaiksatam | rkukura: yes, per igordcard, the node driver is not visible to the user | 18:50 |
rkukura | thanks | 18:50 |
ivar-lazzaro | igordcard: that's for operator consumption | 18:50 |
SumitNaiksatam | rkukura: and yes this configuration is for opertaional reasons | 18:51 |
SumitNaiksatam | the confusion is happening because so far we have been dealing only with tenant facing resources | 18:51 |
ivar-lazzaro | rkukura: Service chain Specs/Nodes/Instances are purely Operator oriented, mostly like L2/L3 policies | 18:51 |
rkukura | Just to clarify, we mean “cloud operator” here, not the application deployment role, right? | 18:51 |
igordcard | the user simply chooses a service to be put into the service chain, eventually assigning some meaningful tags that the system supports, which could then be used internally for, e.g. as ivar-lazzaro said, show a different UI | 18:51 |
ivar-lazzaro | rkukura: yes | 18:52 |
SumitNaiksatam | however a new resource is being proposed here called “service profile” | 18:52 |
SumitNaiksatam | this resource is managed by the operator (cloud operator) | 18:52 |
ivar-lazzaro | igordcard: the user would simply chose the policy rule (REDIRECT to some chain) | 18:52 |
SumitNaiksatam | but is visible to the user | 18:52 |
igordcard | ivar-lazzaro, and the tags are predefined for the nodes that compose the chain right? | 18:53 |
ivar-lazzaro | igordcard: how the chain is implemented and which metadata are associated with it is a Cloud Operator's concern | 18:53 |
SumitNaiksatam | i would have preferred to not immediately model these as a resource, but hide them as operational details (driven via configuration) | 18:53 |
ivar-lazzaro | igordcard: this may be one use, yes. But the tag resource I have in mind actually covers *all* the GBP resources for API consistency | 18:54 |
ivar-lazzaro | SumitNaiksatam: but this would mean adding key-value attributes to certain resources, so an API change is still required right? | 18:54 |
igordcard | any thought been given on allowing users to influence the behaviour of resources by applying tags themselves? | 18:55 |
*** dtroyer has joined #openstack-meeting-3 | 18:55 | |
SumitNaiksatam | ivar-lazzaro: in that case the service profile is completely internal, you only expose its description to the user | 18:55 |
ivar-lazzaro | igordcard: I think those are "labels", and no we haven't discussed them yet | 18:55 |
igordcard | in this case the tag resource would probably be something else | 18:56 |
igordcard | ivar-lazzaro, yeah | 18:56 |
SumitNaiksatam | lets not call them tags, since it casuses confusion, i think meta-date is more appropriate here :-) | 18:56 |
SumitNaiksatam | otherwise we will go around in circles even in this small group | 18:56 |
ivar-lazzaro | SumitNaiksatam: I say we call them Endpoints! | 18:57 |
SumitNaiksatam | ivar-lazzaro: amen | 18:57 |
ivar-lazzaro | SumitNaiksatam: eheh :) | 18:58 |
igordcard | so, just to clarify, you intend to have service profiles defined by operators and used by tenants | 18:58 |
SumitNaiksatam | igordcard: yes | 18:58 |
SumitNaiksatam | perhaps we might not expose all attributes to users | 18:58 |
*** matrohon has joined #openstack-meeting-3 | 18:58 | |
igordcard | and "config" is the field where the user can input additional constraints/metadata/configs for the service? | 18:59 |
igordcard | per https://review.openstack.org/#/c/174118/7/specs/kilo/gbp-service-chain-driver-refactor.rst : "Node Driver": "This configures the service based on the “config” provided in the Service Node definition." | 18:59 |
ivar-lazzaro | igordcard: I actually think that the user should never interact with the services | 18:59 |
SumitNaiksatam | igordcard: we already have a config in the “node” definition | 18:59 |
SumitNaiksatam | igordcard: the meta-data i am referring to goes beyond that “config" | 19:00 |
ivar-lazzaro | The final user should only think "intent | 19:01 |
SumitNaiksatam | ivar-lazzaro: true, user will never directly interact with the service, that doesnt happen today either | 19:01 |
SumitNaiksatam | *will never -> should never | 19:01 |
SumitNaiksatam | okay we are a minute over | 19:01 |
SumitNaiksatam | #topic Vancouver Summit prep | 19:02 |
*** openstack changes topic to "Vancouver Summit prep (Meeting topic: networking_policy)" | 19:02 | |
SumitNaiksatam | ivar-lazzaro: rkukura: anything quick to discuss? | 19:02 |
igordcard | ivar-lazzaro, yes, yes, but if the intent can be expressed in a richer way, it may be beneficial | 19:02 |
SumitNaiksatam | igordcard: you are coming to the summit? | 19:02 |
SumitNaiksatam | yapeng: you are coming to the summit? | 19:02 |
igordcard | SumitNaiksatam, unfortunately not :( | 19:02 |
SumitNaiksatam | igordcard: oh bummer! | 19:02 |
ivar-lazzaro | SumitNaiksatam: I'm trying to figure out a way to implement shared PRS for the RMD | 19:02 |
yapeng | yes i will come | 19:02 |
SumitNaiksatam | ivar-lazzaro: ah correct | 19:02 |
ivar-lazzaro | SumitNaiksatam: I have a couple of ideas but I'm still trying to validate them | 19:02 |
SumitNaiksatam | ivar-lazzaro: that part was challenging as you mentioned | 19:03 |
ivar-lazzaro | Should we discuss them in the gbp channel? | 19:03 |
SumitNaiksatam | ivar-lazzaro: thanks for taking that up | 19:03 |
SumitNaiksatam | ivar-lazzaro: sure | 19:03 |
*** wojdev has quit IRC | 19:03 | |
SumitNaiksatam | yapeng: good | 19:03 |
ivar-lazzaro | I'd like to hear from the rest of the team, especially those with a richer Neutron background | 19:03 |
Yi | SumitNaiksatam: unfortunately, I cannot | 19:03 |
Yi | I won't be able to go to summit | 19:04 |
SumitNaiksatam | Yi: sorry, i did not notice that you had joinied, earlier i checked you were not | 19:04 |
SumitNaiksatam | Yi: damn thats a bummer | 19:04 |
Yi | was stuck in another meeting | 19:04 |
rkukura | ivar-lazzaro: Is there something for us to look at to understand your ideas? | 19:04 |
SumitNaiksatam | Yi: lets sync up offline on that | 19:04 |
Yi | sure | 19:04 |
ivar-lazzaro | rkukura: I have nothing besides some code, but it's not published yet... Maybe we can discuss it on IRC and then I can publish a WIP? | 19:04 |
rkukura | ivar-lazzaro: sure | 19:05 |
*** irenab has joined #openstack-meeting-3 | 19:05 | |
ivar-lazzaro | rkukura: I wanted to write a spec but I don't know yet what will work! So it's not easy | 19:05 |
SumitNaiksatam | one last thing | 19:05 |
rkukura | ivar-lazzaro: IRC, email, hangout, whatever works best | 19:05 |
SumitNaiksatam | #topic Refactor feature branch | 19:05 |
*** openstack changes topic to "Refactor feature branch (Meeting topic: networking_policy)" | 19:05 | |
SumitNaiksatam | yi and yapeng’s patches are finally all in | 19:06 |
yapeng | cool :) | 19:06 |
ivar-lazzaro | rkukura: anything is good for me, the sooner we discuss the best. Do you have time after the meeting? | 19:06 |
SumitNaiksatam | Yi: thanks so much for pursuing the last patch | 19:06 |
SumitNaiksatam | we will work towards merging them from the feature branch once we are done with the summit | 19:06 |
Yi | my pleasure | 19:06 |
ivar-lazzaro | yapeng: Yi: Thanks guys! | 19:06 |
SumitNaiksatam | okay lets move to -gbp | 19:06 |
SumitNaiksatam | thanks all, and apologies for going over | 19:07 |
SumitNaiksatam | bye! | 19:07 |
igordcard | cya | 19:07 |
Yi | bye | 19:07 |
ivar-lazzaro | ciaooo | 19:07 |
SumitNaiksatam | #endmeeting | 19:07 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 19:07 | |
openstack | Meeting ended Thu Apr 30 19:07:09 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 19:07 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-04-30-18.01.html | 19:07 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-04-30-18.01.txt | 19:07 |
openstack | Log: http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-04-30-18.01.log.html | 19:07 |
rkukura | ivar-lazzaro: give me a couple minutes, then ping me | 19:07 |
*** Yi has left #openstack-meeting-3 | 19:07 | |
yapeng | bye | 19:07 |
rkukura | bye | 19:07 |
*** kozhukalov has quit IRC | 19:10 | |
*** irenab has quit IRC | 19:11 | |
*** eghobo_ has quit IRC | 19:16 | |
*** marun has quit IRC | 19:17 | |
*** ttrifonov is now known as zz_ttrifonov | 19:18 | |
*** VW_ has joined #openstack-meeting-3 | 19:18 | |
*** B_Smith_ has quit IRC | 19:20 | |
*** marun has joined #openstack-meeting-3 | 19:22 | |
*** egallen has quit IRC | 19:30 | |
*** egallen has joined #openstack-meeting-3 | 19:32 | |
*** ajo has joined #openstack-meeting-3 | 19:33 | |
*** kevinbenton has quit IRC | 19:33 | |
*** d0ugal has quit IRC | 19:33 | |
*** d0ugal has joined #openstack-meeting-3 | 19:34 | |
*** kevinbenton has joined #openstack-meeting-3 | 19:35 | |
*** mattgriffin has joined #openstack-meeting-3 | 19:40 | |
*** mwang2 has quit IRC | 19:43 | |
*** dtroyer has left #openstack-meeting-3 | 19:45 | |
*** mwang2 has joined #openstack-meeting-3 | 19:48 | |
*** marun has quit IRC | 19:54 | |
*** marun has joined #openstack-meeting-3 | 19:56 | |
*** jpena has joined #openstack-meeting-3 | 19:57 | |
*** Shamail has joined #openstack-meeting-3 | 20:00 | |
*** clouddon has joined #openstack-meeting-3 | 20:00 | |
*** wojdev has joined #openstack-meeting-3 | 20:01 | |
*** e0ne has quit IRC | 20:01 | |
Shamail | Hi megm_, clouddon, mattgriffin | 20:02 |
mattgriffin | hi Shamail: got a conflict today. so can't make it... on a call now :( | 20:02 |
Shamail | Got it. Do we want to cancel for today? Did you finish the spec draft? | 20:02 |
Shamail | I don't see Nick or Sam on either. | 20:03 |
megm_ | I'm here -- wasn't sure if we were canceled or not. | 20:03 |
megm_ | I think the main item is to review the spec | 20:03 |
Shamail | I'm fine with canceling today, I could use any extra time I can get this week. | 20:03 |
mattgriffin | ack. spec is in progress/review | 20:04 |
Shamail | Agreed megm_, I haven't checked it to see if mattgriffin was able to complete. | 20:04 |
megm_ | We have a draft spec | 20:04 |
*** baoli has joined #openstack-meeting-3 | 20:04 | |
Shamail | Okay, perfect. | 20:04 |
megm_ | https://review.openstack.org/#/c/178427/2/specs/liberty/ha-guide.rst | 20:04 |
Shamail | opening now | 20:04 |
*** antares_ has joined #openstack-meeting-3 | 20:05 | |
megm_ | I've made updates but they aren't getting to gerrit -- but you can see the comments and my responses FWIW | 20:05 |
clouddon | sorry guys. system issues. connecting from mobile is painful | 20:05 |
Shamail | I know clouddon, it is always hard on mobile. | 20:05 |
Shamail | How about we all take the AI to review the draft and make additional comments (I do see your comments megm_) | 20:06 |
clouddon | thx. will check logs for action items. thx | 20:06 |
*** mattgriffin has quit IRC | 20:06 | |
Shamail | We can regroup next week and have a quick sync before moving it forward. | 20:06 |
clouddon | +1 on review AR | 20:06 |
Shamail | Does that work for you megm_? | 20:06 |
megm_ | Sounds like a plan. | 20:07 |
Shamail | Alright, see you next week! | 20:07 |
*** baoli has quit IRC | 20:07 | |
Shamail | bye megm_, clouddon | 20:07 |
megm_ | Note that we need to implement intersphinx to accomodate xrefs with Install Guide | 20:07 |
clouddon | tataa | 20:07 |
*** jpena has quit IRC | 20:07 | |
megm_ | http://sphinx-doc.org/latest/ext/intersphinx.html | 20:07 |
Shamail | good point. We should capture that requirement in the TOC wiki? | 20:07 |
*** baoli has joined #openstack-meeting-3 | 20:07 | |
megm_ | Good point -- I'll update the TOC | 20:08 |
Shamail | alrighty | 20:08 |
Shamail | later! | 20:08 |
antares_ | hi folks. I'm new here :) I'm a RabbitMQ team member. We'd like to help with the docs. | 20:08 |
Shamail | Hi antares_, nice to meet you. | 20:08 |
megm_ | Welcome, antares! We welcome your help and expertise! | 20:08 |
antares_ | we are not familiar with the OpenStack process, so learning along the way | 20:09 |
antares_ | currently we are collecting notes on what can be improved. Patches will follow hopefully next week. | 20:09 |
Shamail | antares_: This is the HA guide update team.... Please review the meeting notes from our last meeting, they contain some useful links starting at 20:16:22 to ramp up on our objective and progress. | 20:10 |
Shamail | http://eavesdrop.openstack.org/meetings/ha_guide/2015/ha_guide.2015-04-23-20.03.log.html | 20:10 |
antares_ | Shamail: thanks, will take a look | 20:10 |
Shamail | We are canceling our meeting for today due to conflicts but this is our regular time. We will also be holding a face to face meeting at the OpenStack Summit in Vancouver (Meeting Room #16, Thursday (5/21) 10:45A to 12:30P PT) | 20:11 |
megm_ | Our current status is that we have a draft spec under review for the project. After that is approved, we can set up source files, convert existing source from docbook to RST and move things around to match the proposed structure. | 20:11 |
Shamail | I have to run, take care megm_ and look forward to working with you antares_ | 20:12 |
Shamail | ttfn | 20:12 |
*** Shamail has quit IRC | 20:12 | |
antares_ | so the structure is being changed? will this affect Kilo docs? | 20:12 |
megm_ | antares, it would be great if you could look at the TOC. Top priority is explaining how the HA controller is config'ed, etc. | 20:13 |
megm_ | I think we have the right items identified; I'm less confident that we have them in the right order. | 20:13 |
antares_ | megm_: my goal is to improve the RabbitMQ sections. I'm not an expert on other things the HA guide covers. | 20:14 |
megm_ | The spec is now targeting Liberty. But I did see your mail that you have info to add. | 20:14 |
antares_ | megm_: OpenStack doc changes will be pretty light. Most of the content we have in mind will go to rabbitmq.com. | 20:15 |
megm_ | antares: I understand. But RabbitMQ is pretty central -- be sure that it is appearing at the right place, with all prerequisites done before that section | 20:15 |
antares_ | sure | 20:15 |
megm_ | I saw that you are creating a separate RabbitMQ guide, which is terrific! | 20:15 |
megm_ | Is it being coded in RST with intersphinx so we can readily xref between that guide and this one? | 20:16 |
antares_ | do you meet once a week same day same time or does it vary? | 20:16 |
antares_ | we don't use RST and our website is not yet open source (pushing that through legal) | 20:16 |
antares_ | we were thinking OpenStack docs could use plain old HTML anchors | 20:17 |
antares_ | would that work for you? | 20:17 |
megm_ | antares: Okay, so we need to figure out how we handle RabbitMQ. Perhaps you guys can contribute some basic info to this guide then we just hand off to your guide as a whole for additional info? | 20:17 |
*** mattgriffin has joined #openstack-meeting-3 | 20:18 | |
megm_ | antares, I'm not sure about the html anchors. RST can xref them but, if the URLs include version info, you will need to manually maintain them | 20:18 |
antares_ | megm_: that's the plan | 20:18 |
antares_ | megm_: our URLs are not version-specific and probably won't be | 20:19 |
*** eghobo has joined #openstack-meeting-3 | 20:19 | |
antares_ | we will keep the URLs working, even if we change them (doesn't happen often) via redirects | 20:19 |
megm_ | antares, that will solve some issues -- and create others if different software versions have different capabilities. But that's all manageable, I'm sure | 20:19 |
*** Sukhdev has quit IRC | 20:20 | |
antares_ | that's a fair point | 20:20 |
megm_ | Meanwhile, I think you have new information that needs to be added to the HA Guide for Kilo, right? | 20:20 |
antares_ | we'd like to update the Kilo version, yes | 20:21 |
megm_ | antares: we are missing key people today, alas. But I think you can go ahead and patch the docbook source for Kilo this week. | 20:21 |
antares_ | sounds good | 20:21 |
megm_ | Nick Chase will be converting that to RST and setting up the new files as soon as the spec is approved, but I think you have a little window | 20:21 |
*** pballand has joined #openstack-meeting-3 | 20:22 | |
antares_ | sorry, will the Kilo guides be ported to RST as well? or just Liberty? | 20:22 |
megm_ | Perhaps when you submit such patches, you could send email tagged [ha-guide] to alert us all to the patch | 20:22 |
antares_ | if it's only Liberty we can target that from the start | 20:23 |
antares_ | to openstack-docs, correct? | 20:23 |
megm_ | Then we can be sure it is merged before Nick converts those sections. I'm not real sure how this all works but that seems reasonable | 20:23 |
megm_ | antares: you might want to check with Andreas, Anne, etc. | 20:24 |
*** Sukhdev has joined #openstack-meeting-3 | 20:24 | |
megm_ | But I THINK that the docbook HA Guide that is out there is being used for Kilo. | 20:24 |
antares_ | we can wait for a bit, put more effort into the new rabbitmq.com guide. Then discuss what to do at the summit. | 20:24 |
megm_ | Then all that content will be converted to RST and incorporated into the appropriate place in the new structure for Liberty | 20:24 |
antares_ | I'll ask Anne | 20:24 |
megm_ | Is the new rabbitmq guide -- or what you have -- published? | 20:25 |
antares_ | thanks, this is very useful to know that you're about to migrate to RST | 20:25 |
antares_ | not yet, no. It will be once it is maybe 75% complete. | 20:25 |
antares_ | I'll announce it on the list | 20:25 |
megm_ | antares, my email is meg.mcroberts@yahoo.com if you want to chat offline before the next meeting. Caveats that I only partially know whereof I speak ;-) | 20:26 |
megm_ | Shamail, are you still there? | 20:26 |
*** asahlin is now known as asahlin_afk | 20:27 | |
megm_ | antares_afk, sounds good. I was hoping that we could at least link to your guide as soon as it is published. | 20:28 |
*** ajo has quit IRC | 20:28 | |
megm_ | But I'm not sure about policies for augmenting docs after the release | 20:28 |
antares_ | megm_: if we have to target Liberty, it's OK | 20:28 |
antares_ | our goal is to continue contributing as things change | 20:29 |
megm_ | Whatever, I'm awfully glad you guys are doing this -- I know that people have a lot of questions about exactly how RabbitMQ works, etc | 20:29 |
antares_ | :) | 20:29 |
antares_ | we are always happy to answer questions on our mailing list (rabbitmq-users) | 20:29 |
megm_ | Excellent! I think we have an unusual amount of turmoil right now as docs are being converted from docbook to RST, procedures are being established to accomodate the growth in contributors, etc. | 20:30 |
ekarlso | what meeting is this btw ? ^^ | 20:30 |
antares_ | megm_: I think we've hijacked a meeting room | 20:30 |
megm_ | Yes, the rabbit people have an excellent reputation. Still, a guide that puts it all together is valuable | 20:30 |
*** emagana has quit IRC | 20:30 | |
antares_ | ekarlso: sorry | 20:30 |
megm_ | ekarlso, this is the time slot for the HA guide but it's kind of a non-meeting today | 20:31 |
ekarlso | i was just wondering ;p | 20:31 |
*** egallen has quit IRC | 20:31 | |
megm_ | Did you mean to be here for the HA Guide meeting? | 20:31 |
ekarlso | megm_: nope .) | 20:32 |
antares_ | megm_: thank you for your help. I'll keep joining HA guide meetings and hope to meet the doc team at the summit. | 20:32 |
megm_ | Excellent, antares! Have a great week and we'll chat next week. | 20:32 |
antares_ | you too | 20:32 |
*** marun has quit IRC | 20:32 | |
*** alexsyip has quit IRC | 20:33 | |
*** antares_ has quit IRC | 20:33 | |
*** ajo has joined #openstack-meeting-3 | 20:34 | |
*** alexsyip has joined #openstack-meeting-3 | 20:37 | |
*** Networkn3rd has quit IRC | 20:42 | |
*** mwang2_ has joined #openstack-meeting-3 | 20:44 | |
*** mwang2 has quit IRC | 20:47 | |
*** mattgriffin has quit IRC | 20:48 | |
*** marun has joined #openstack-meeting-3 | 20:59 | |
*** melwitt has quit IRC | 21:04 | |
*** melwitt has joined #openstack-meeting-3 | 21:04 | |
*** melwitt has quit IRC | 21:05 | |
*** melwitt has joined #openstack-meeting-3 | 21:05 | |
*** VW_ has quit IRC | 21:10 | |
*** bpokorny_ has joined #openstack-meeting-3 | 21:10 | |
*** bpokorny has quit IRC | 21:14 | |
*** huichun has quit IRC | 21:18 | |
*** matrohon has quit IRC | 21:18 | |
*** wojdev has quit IRC | 21:22 | |
*** mwagner_lap has quit IRC | 21:22 | |
*** Longgeek has quit IRC | 21:24 | |
*** ryansb_ has joined #openstack-meeting-3 | 21:28 | |
*** ryansb_ has joined #openstack-meeting-3 | 21:28 | |
*** ryansb_ is now known as ryansb | 21:28 | |
*** Longgeek has joined #openstack-meeting-3 | 21:28 | |
*** nelsnelson has quit IRC | 21:29 | |
*** VW_ has joined #openstack-meeting-3 | 21:30 | |
*** carl_baldwin has quit IRC | 21:30 | |
*** ajo has quit IRC | 21:32 | |
*** alexsyip has quit IRC | 21:38 | |
*** emagana has joined #openstack-meeting-3 | 21:39 | |
*** stevemar has quit IRC | 21:39 | |
*** bpokorny has joined #openstack-meeting-3 | 21:41 | |
*** shwetaap has joined #openstack-meeting-3 | 21:42 | |
*** bpokorny_ has quit IRC | 21:44 | |
*** wojdev has joined #openstack-meeting-3 | 21:44 | |
*** clouddon has quit IRC | 21:48 | |
*** ryansb has left #openstack-meeting-3 | 21:48 | |
*** alexsyip has joined #openstack-meeting-3 | 21:50 | |
*** igordcard_ has joined #openstack-meeting-3 | 21:53 | |
*** jgrimm is now known as zz_jgrimm | 21:53 | |
*** igordcard has quit IRC | 21:55 | |
*** irenab has joined #openstack-meeting-3 | 21:56 | |
*** Rockyg has joined #openstack-meeting-3 | 21:58 | |
*** peristeri has quit IRC | 21:58 | |
*** emagana has quit IRC | 21:59 | |
*** bknudson has quit IRC | 22:01 | |
*** irenab has quit IRC | 22:01 | |
*** Swami has quit IRC | 22:02 | |
*** jckasper has quit IRC | 22:05 | |
*** egallen has joined #openstack-meeting-3 | 22:08 | |
*** melwitt_ has joined #openstack-meeting-3 | 22:11 | |
*** melwitt_ has quit IRC | 22:11 | |
*** melwitt has quit IRC | 22:12 | |
*** sbalukoff has quit IRC | 22:15 | |
*** armax has quit IRC | 22:15 | |
*** wojdev has quit IRC | 22:15 | |
*** Sukhdev has quit IRC | 22:19 | |
*** Sukhdev has joined #openstack-meeting-3 | 22:20 | |
*** jtomasek has quit IRC | 22:20 | |
*** melwitt has joined #openstack-meeting-3 | 22:20 | |
*** wojdev has joined #openstack-meeting-3 | 22:21 | |
*** Piet has quit IRC | 22:26 | |
*** sigmavirus24 is now known as sigmavirus24_awa | 22:27 | |
*** VW_ has quit IRC | 22:33 | |
*** wojdev has quit IRC | 22:34 | |
*** sarob has quit IRC | 22:34 | |
*** julim has joined #openstack-meeting-3 | 22:35 | |
*** emagana has joined #openstack-meeting-3 | 22:36 | |
*** igordcard has joined #openstack-meeting-3 | 22:39 | |
*** emagana has quit IRC | 22:42 | |
*** wojdev has joined #openstack-meeting-3 | 22:44 | |
*** Piet has joined #openstack-meeting-3 | 22:44 | |
*** emagana has joined #openstack-meeting-3 | 22:46 | |
*** shwetaap has quit IRC | 22:48 | |
*** yalie has joined #openstack-meeting-3 | 22:53 | |
*** Swami has joined #openstack-meeting-3 | 22:55 | |
*** bpokorny has quit IRC | 23:02 | |
*** bpokorny_ has joined #openstack-meeting-3 | 23:02 | |
*** marun has quit IRC | 23:05 | |
*** baoli has quit IRC | 23:06 | |
*** marun has joined #openstack-meeting-3 | 23:06 | |
*** melwitt has quit IRC | 23:07 | |
*** Sukhdev_ has joined #openstack-meeting-3 | 23:10 | |
*** banix has joined #openstack-meeting-3 | 23:10 | |
*** Sukhdev has quit IRC | 23:11 | |
*** marun has quit IRC | 23:11 | |
*** wojdev has quit IRC | 23:11 | |
*** vgridnev_ has quit IRC | 23:13 | |
*** egallen has quit IRC | 23:14 | |
*** salv-orl_ has joined #openstack-meeting-3 | 23:14 | |
*** fallenpegasus has quit IRC | 23:15 | |
*** MarkAtwood has quit IRC | 23:15 | |
*** salv-orlando has quit IRC | 23:17 | |
*** wojdev has joined #openstack-meeting-3 | 23:19 | |
*** wojdev has quit IRC | 23:24 | |
*** absubram has quit IRC | 23:34 | |
*** melwitt has joined #openstack-meeting-3 | 23:36 | |
*** emagana has quit IRC | 23:38 | |
*** marun has joined #openstack-meeting-3 | 23:40 | |
*** emagana has joined #openstack-meeting-3 | 23:41 | |
*** krtaylor has quit IRC | 23:44 | |
*** irenab has joined #openstack-meeting-3 | 23:45 | |
*** salv-orl_ has quit IRC | 23:46 | |
*** mrmartin has joined #openstack-meeting-3 | 23:48 | |
*** irenab has quit IRC | 23:50 | |
*** banix has quit IRC | 23:51 | |
*** Swami_ has joined #openstack-meeting-3 | 23:51 | |
*** SumitNaiksatam has quit IRC | 23:54 | |
*** Swami has quit IRC | 23:55 | |
*** krtaylor has joined #openstack-meeting-3 | 23:56 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!