| etoews | #startmeeting api wg | 00:00 |
|---|---|---|
| openstack | Meeting started Thu Feb 5 00:00:05 2015 UTC and is due to finish in 60 minutes. The chair is etoews. Information about MeetBot at http://wiki.debian.org/MeetBot. | 00:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 00:00 |
| *** openstack changes topic to " (Meeting topic: api wg)" | 00:00 | |
| openstack | The meeting name has been set to 'api_wg' | 00:00 |
| etoews | hiya | 00:00 |
| elmiko | hi | 00:00 |
| cyeoh | hi! | 00:00 |
| stevelle | hello | 00:00 |
| ryansb | hey | 00:00 |
| etoews | hey cyeoh! good to have you back. | 00:00 |
| sigmavirus24 | o/ | 00:00 |
| cyeoh | etoews: thx :-) | 00:00 |
| sigmavirus24 | cyeoh: long time no see | 00:00 |
| sigmavirus24 | etoews: I'm pretty sure miguelgrinberg wont' make it tonight | 00:01 |
| etoews | k | 00:01 |
| etoews | #link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda | 00:01 |
| etoews | we currently have 2 big matzah balls out there | 00:01 |
| etoews | mission statement and which repo to use | 00:02 |
| etoews | #topic mission statement | 00:02 |
| *** openstack changes topic to "mission statement (Meeting topic: api wg)" | 00:02 | |
| *** nikhil_k has joined #openstack-meeting-3 | 00:02 | |
| etoews | have people been following the thread on the ml? | 00:03 |
| elmiko | yup | 00:03 |
| cyeoh | sorry missed it, is there a draft up somewhere? | 00:03 |
| sigmavirus24 | yep | 00:03 |
| elmiko | cyeoh: don't think we made it to draft phase yet | 00:03 |
| sigmavirus24 | cyeoh: http://lists.openstack.org/pipermail/openstack-dev/2015-February/055763.html | 00:04 |
| cyeoh | sigmavirus24: thx | 00:04 |
| sigmavirus24 | cyeoh: actually it starts http://lists.openstack.org/pipermail/openstack-dev/2015-January/055694.html | 00:04 |
| sigmavirus24 | #link http://lists.openstack.org/pipermail/openstack-dev/2015-January/055694.html | 00:04 |
| sigmavirus24 | #link http://lists.openstack.org/pipermail/openstack-dev/2015-February/055763.html | 00:04 |
| elmiko | there are some nice suggestions in the thread | 00:04 |
| etoews | yes. it's been helping me think about it. | 00:05 |
| *** xuhanp has joined #openstack-meeting-3 | 00:06 | |
| sigmavirus24 | I'm not sure what the value of "pragmatic" is in that context to be honest | 00:06 |
| sigmavirus24 | But it doesn't bother me. It just seems superfluous | 00:06 |
| *** rosmaita has joined #openstack-meeting-3 | 00:06 | |
| ryansb | I like "pragmatic" because (to me) it drives home that we're looking for implementable, practical solutions | 00:07 |
| *** hemanth has joined #openstack-meeting-3 | 00:07 | |
| stevelle | I'd hope we can make it slightly fewer words still. If something else can be tightened that makes more room. | 00:07 |
| *** bpokorny has joined #openstack-meeting-3 | 00:08 | |
| stevelle | But it feels like it has developed nicely. | 00:08 |
| etoews | i like stefano's suggestion about including our audience | 00:08 |
| cyeoh | so I like the bit about identifying existing practice because I don't think we should be very cautious about recommending anything that hasn't been tried in practice yet | 00:08 |
| ryansb | +1 cyeoh | 00:08 |
| stevelle | that seems to be harmonious with "practical" imo | 00:09 |
| sigmavirus24 | So I think there are two things that people are talking about simultaneously in that thread: 1. elevator pitch 2. full mission statement | 00:09 |
| etoews | yes | 00:09 |
| sigmavirus24 | We might want to develop the former from the latter and the latter should be longer form than initially proposed | 00:09 |
| sigmavirus24 | cyeoh: my hesistancy with that is the implication that we'll favor existing (insufficient) openstack API designs over better and not unattainable designs that have been implemented successfully outside of openstack | 00:10 |
| stevelle | +1 sigmavirus24 | 00:10 |
| elmiko | sigmavirus24: +1 | 00:10 |
| sigmavirus24 | By which I mean, it should be made clear that we won't only be pulling from prior art of OpenStack and nothing more | 00:11 |
| cyeoh | sigmavirus24: well thats a possibility, but recommending something that turns out not to work at all is even worse | 00:11 |
| cyeoh | especially if multiple projects adopt it because its in the guidelines | 00:11 |
| elmiko | i'm all for breaking a few eggs to make things better, at the same time we have to hammer home the "guidelines not standards" message | 00:11 |
| etoews | here's what i originally envisioned. 1-3 sentences of text describing our purpose. which could be followed by longer text going into more detail. | 00:11 |
| sigmavirus24 | == elmiko | 00:12 |
| *** melwitt has left #openstack-meeting-3 | 00:12 | |
| cyeoh | for example, I wouldn't have a recommendation for microversions in the document yet until we actually see it working in Nova | 00:12 |
| *** melwitt has joined #openstack-meeting-3 | 00:12 | |
| sigmavirus24 | cyeoh: fair | 00:12 |
| elmiko | makes sense | 00:12 |
| etoews | +1 elmiko but i think there's a caveat that one day particular guidelines could become a standard. | 00:12 |
| cyeoh | but I think it would be ok to have something saying"this is what Nova is trying, might want to consider it" | 00:12 |
| sigmavirus24 | for example, I want to see metadata sent via headers killed because there are so many issues that other projects have run into | 00:12 |
| elmiko | etoews: yeah, i kinda left of ", yet..." from the end ;) | 00:13 |
| sigmavirus24 | I think we're all in agreement though =) | 00:13 |
| etoews | cyeoh: i would go further by saying to not include it until client code has been written against it too. | 00:13 |
| etoews | let's hammer out something! | 00:13 |
| cyeoh | etoews: agreed | 00:13 |
| etoews | something we can take back to the ml | 00:14 |
| stevelle | etherpad? | 00:14 |
| etoews | http://etherpad.openstack.org/p/api-wg-mission-statement | 00:15 |
| etoews | #link http://etherpad.openstack.org/p/api-wg-mission-statement | 00:15 |
| sigmavirus24 | +1 | 00:15 |
| sigmavirus24 | perhaps we should move on? | 00:16 |
| * sigmavirus24 pings etoews | 00:17 | |
| sigmavirus24 | we can go through and update the etherpad further after the meeting | 00:17 |
| etoews | can we give this 5 more minutes? | 00:17 |
| etoews | *really wants to hammer something out* | 00:18 |
| *** Sukhdev has quit IRC | 00:18 | |
| sigmavirus24 | okay | 00:19 |
| cyeoh | so I kind of like Dean's the best, but I would like to add something that says we're a group that can be approached if a project is not sure about something not covered by the existing guidelines | 00:19 |
| cyeoh | s/can/should/ | 00:19 |
| *** annegent_ has quit IRC | 00:20 | |
| ryansb | I like Dean's as well, just trying out some different wording options | 00:21 |
| sigmavirus24 | cyeoh: yeah. If miguelgrinberg were here though, he could attest to the fact that every time we're approached for advice people are expecting a rubber stamp, not actual constructive criticism | 00:21 |
| elmiko | Dean's does have a nice compactness to it | 00:22 |
| cyeoh | sigmavirus24: we'll give them constructive criticism anyway :-) | 00:22 |
| stevelle | my one issue with Dean's is, as sigmavirus24 pointed out, we should also look beyond OpenStack for existing practices | 00:22 |
| ryansb | cyeoh: righto, they can't stop us from sending emails. | 00:22 |
| elmiko | stevelle: good point | 00:23 |
| etoews | to me dean's leaves too many questions open. the kind of questions we've been getting from the people we're trying to engage | 00:23 |
| ryansb | moving the "OpenStack REST APIs" fixes stevelle's issue, so we're collecting implementations/best practices and bringing them into openstack | 00:24 |
| etoews | i think we could distill a tweetable mantra out of something slightly longer form. | 00:24 |
| elmiko | yea, would be nice to mention guidelines in there somewhere, i think we have to | 00:24 |
| rosmaita | i prefer ryan's over dean's because it says API convergence, not project convergence | 00:24 |
| etoews | elmiko: +1 | 00:24 |
| ryansb | thanks to whoever fixed my grammar. ;) | 00:24 |
| elmiko | rosmaita: +1 | 00:24 |
| sigmavirus24 | ryansb: it wasn't me but I would have been proud to have done so | 00:25 |
| sigmavirus24 | == rosamita | 00:25 |
| etoews | also dean's doesn't say for who or why | 00:25 |
| ryansb | well this is the API-WG mission statement, I think that covers "who" | 00:26 |
| ryansb | why though. Good point. | 00:26 |
| etoews | ryansb: so who is the who? | 00:27 |
| rosmaita | i'd like if we could add stefano's improve dev experience to ryan's second statement | 00:27 |
| sigmavirus24 | ryansb: why? because we should | 00:27 |
| etoews | put another way, who is our audience? | 00:27 |
| *** marun has quit IRC | 00:28 | |
| rosmaita | API consumers == developers ? | 00:28 |
| stevelle | +1 rosmaita identifying the why in naming the developer experience | 00:28 |
| cyeoh | well ultimately I see it to make life as easy as possible for the users of the OpenStack APIs (not openstack developers generally) | 00:28 |
| sigmavirus24 | That's the hardest one to answer since we consumer our APIs via our python-*client s and openstacksdk | 00:28 |
| cyeoh | sigmavirus24: yep I'd definitely include those people | 00:29 |
| etoews | that's my thinking as well. our audience is the api consumers. | 00:29 |
| cyeoh | sigmavirus24: I guess I mean to stay its not primarily for those writing the api implementations, though it certainly helps | 00:29 |
| sigmavirus24 | cyeoh: right | 00:29 |
| rosmaita | i don't see "improve developer experience" implying openstack devs | 00:29 |
| nikhil_k | +1 to rosmaita's point about API consumers == developers | 00:29 |
| rosmaita | though it would definitely include them | 00:30 |
| sigmavirus24 | I think the other thing is that the python-*clients often mirror the respective APIs in the CLI so this will provide a more consistent cli for users as well (e.g., operators in this case) | 00:30 |
| ryansb | the who is "API-WG" for "distill" and the why is "to make developers happier" IMO | 00:30 |
| etoews | this is why it's so important to clearly identify the audience. developers actually has double meaning in openstack | 00:30 |
| nikhil_k | (sorry to jump in unnoticed, felt like a strong case to vote) | 00:30 |
| etoews | there are developers building apps on openstack and developers contributing to openstack | 00:31 |
| ryansb | in this case (I think) it's both kinds | 00:31 |
| stevelle | welcome, nikhil_k | 00:31 |
| rosmaita | is "API consumers" OK? would cover everyone | 00:31 |
| nikhil_k | stevelle: :) | 00:31 |
| etoews | rosmaita: something along those lines | 00:31 |
| ryansb | consumers of openstack (app builders/tool builders) and producers of openstack (openstack contributors) | 00:31 |
| cyeoh | rosmaita: +1 | 00:31 |
| elmiko | i think we should use different language than "API consumers" | 00:31 |
| sigmavirus24 | == elmiko | 00:32 |
| sigmavirus24 | I don't know what better language exists though | 00:32 |
| etoews | it's especially important because if we just use the word developers, the "producers of openstack" will assume it's them that's being talked about | 00:32 |
| elmiko | hmm, sticky wicket... | 00:32 |
| elmiko | it just seems axiomatic that the API-wg is talking to API consumers | 00:32 |
| ryansb | argh, etherpad connection failures. | 00:33 |
| nikhil_k | API patrons | 00:33 |
| rosmaita | ok, how about "to improve the OpenStack experience" ? | 00:33 |
| sigmavirus24 | to me API consumers doesn't just mean people though, it also means applications etc. | 00:33 |
| elmiko | nikhil_k: +1 i like patrons | 00:33 |
| *** annegent_ has joined #openstack-meeting-3 | 00:33 | |
| elmiko | sigmavirus24: that's a good point too, plus we are talking to api creators as well | 00:33 |
| cyeoh | hrm I think patrons might just confuse people | 00:34 |
| elmiko | probably, but sounds cool | 00:34 |
| stevelle | point of order, we have spent 20 minutes on this so far | 00:34 |
| sigmavirus24 | stevelle: good point to order | 00:34 |
| etoews | i'm willing to move if people pinky swear to chime in on the ml | 00:35 |
| etoews | s/move/move on/ | 00:35 |
| rosmaita | is there an emoticon for that? | 00:35 |
| * elmiko pinky swears | 00:35 | |
| elmiko | rosmaita: lol | 00:35 |
| etoews | #topic api guideline repo | 00:35 |
| *** openstack changes topic to "api guideline repo (Meeting topic: api wg)" | 00:35 | |
| * ryansb \nnnn pinky swears | 00:36 | |
| *** Sukhdev has joined #openstack-meeting-3 | 00:36 | |
| etoews | we decided on 1 repo. so which one? openstack-specs or api-wg | 00:36 |
| etoews | i'm leaning towards api-wg | 00:36 |
| elmiko | i'm +1 for api-wg | 00:36 |
| sigmavirus24 | +1 for api-wg | 00:36 |
| rosmaita | +1 | 00:36 |
| etoews | if we ever need to truly make something a standard, it can be proposed to openstack-specs | 00:36 |
| nikhil_k | rosmaita: \mXm/ | 00:36 |
| cyeoh | yea, api-wg | 00:37 |
| rosmaita | nikhil_k: good one! | 00:37 |
| elmiko | nikhil_k: LOL +1 | 00:37 |
| etoews | nikhil_k: nice! | 00:37 |
| ryansb | legit | 00:37 |
| * rosmaita \mXm/ | 00:37 | |
| elmiko | well, at the least we figured that mystery out ;) | 00:37 |
| etoews | let me throw this thought out there. | 00:37 |
| etoews | what if we changed how we wrote guidelines to be a bit more spec-like | 00:38 |
| etoews | each guideline becomes its own doc | 00:38 |
| *** annegent_ has quit IRC | 00:38 | |
| etoews | with section for examples, prior art, motivation, etc. | 00:38 |
| etoews | too much process/overhead? | 00:38 |
| elmiko | i like that approach | 00:38 |
| * sigmavirus24 too | 00:39 | |
| cyeoh | etoews: I'd prefer at the moment to concentrate on getting something out soon | 00:39 |
| etoews | or would it short circuit a lot of the discussion that goes on in the review? | 00:39 |
| rosmaita | i think it woudl be worth the trouble | 00:39 |
| cyeoh | as in ensure we can do a release in Kilo | 00:39 |
| rosmaita | well cyeoh definitely has a point there | 00:39 |
| etoews | i feel like it's the discussion asking for examples, prior art, motivation, etc. that's slowing us down | 00:40 |
| stevelle | I would like to see process evolve in the next cycle. | 00:40 |
| * sigmavirus24 wasn't aware we were planning a release in kilo | 00:40 | |
| elmiko | etoews: i would think they would have the same level of discourse, just in a spec review instead. | 00:40 |
| sigmavirus24 | planning this for the next cycle makes sense though | 00:40 |
| elmiko | sigmavirus24: +1 | 00:40 |
| cyeoh | so I like the idea of prior art, motivation etc, but I think its something we can add in the future | 00:40 |
| etoews | alright. i just wanted to throw it out there for thought. | 00:41 |
| elmiko | i can certainly get on board with planning a spec-like change for the M cycle | 00:41 |
| *** watanabe_isao has joined #openstack-meeting-3 | 00:41 | |
| elmiko | er L, whatever is next lol | 00:42 |
| etoews | #startvote do we use the api-wg repo to write our guidelines? | 00:42 |
| openstack | Begin voting on: do we use the api-wg repo to write our guidelines? Valid vote options are Yes, No. | 00:42 |
| openstack | Vote using '#vote OPTION'. Only your last vote counts. | 00:42 |
| sigmavirus24 | #vote use the api-wg repo | 00:42 |
| elmiko | #vote Yes | 00:42 |
| sigmavirus24 | or #yes | 00:42 |
| sigmavirus24 | #vote yes | 00:42 |
| etoews | #vote yes | 00:42 |
| stevelle | #vote yes | 00:42 |
| cyeoh | #vote yes | 00:42 |
| rosmaita | #vote yes | 00:42 |
| ryansb | #vote yes | 00:42 |
| nikhil_k | do I get to vote? | 00:43 |
| etoews | yep | 00:43 |
| nikhil_k | (doesn't seem to matter now though) | 00:43 |
| nikhil_k | #vote yes | 00:43 |
| etoews | as far as i'm concerned. you're here and you care. you get to vote. | 00:43 |
| elmiko | nikhil_k: stil... best to be heard =) | 00:43 |
| etoews | #endvite | 00:44 |
| nikhil_k | elmiko: :) | 00:44 |
| etoews | #endvote | 00:44 |
| openstack | Voted on "do we use the api-wg repo to write our guidelines?" Results are | 00:44 |
| *** ChuckC_ has joined #openstack-meeting-3 | 00:44 | |
| etoews | #agreed we use the api-wg repo to write our guidelines | 00:44 |
| etoews | #action etoews to take vote result to ml | 00:45 |
| etoews | #topic Glance and functional API | 00:45 |
| *** openstack changes topic to "Glance and functional API (Meeting topic: api wg)" | 00:45 | |
| etoews | #link https://etherpad.openstack.org/p/glance-adding-functional-operations-to-api | 00:45 |
| etoews | #link https://review.openstack.org/#/c/135122 | 00:45 |
| nikhil_k | o/ | 00:45 |
| * sigmavirus24 thanks etoews for noticing that | 00:45 | |
| *** ChuckC has quit IRC | 00:45 | |
| nikhil_k | Hi, miguelgrinberg sigmavirus24 stevelle hemanth and I had a small :) discussion last evening (EST) on this topic | 00:46 |
| nikhil_k | It was suggested to bring it up here for the reasons of | 00:46 |
| nikhil_k | 1. Finding the best possible approach | 00:47 |
| nikhil_k | 2. Keeping the project goals intact and solving the API guideline issue at hand | 00:47 |
| nikhil_k | The proposal is | 00:47 |
| nikhil_k | adding ' POST /v2/images/{image_id}/actions/{action_type} ' to Glance existing APIs set | 00:48 |
| nikhil_k | (on line 102-5 in the etherpad) | 00:48 |
| nikhil_k | This is to enable a operation of the likes of " being able to deactive a malicious/unusable/licence revoked image and stop the booting process until operators find a good way to fix the image (or its data) | 00:50 |
| hemanth | The reasons for that proposal are listed here, lists.openstack.org/pipermail/openstack-dev/2014-May/036416.html | 00:50 |
| nikhil_k | That being the primary use case; some others were proposed in ATL summit (to which I'm still trying to dig the info out) | 00:51 |
| etoews | so is an action actually being created? or is it strictly a functional point in time thing? | 00:51 |
| rosmaita | functional point in time | 00:51 |
| *** pavel_bondar has quit IRC | 00:51 | |
| *** pavel_bondar has joined #openstack-meeting-3 | 00:52 | |
| *** annegent_ has joined #openstack-meeting-3 | 00:52 | |
| *** annegent_ has quit IRC | 00:52 | |
| sigmavirus24 | etoews: also you're POST'ing without a body | 00:52 |
| sigmavirus24 | (iirc) | 00:52 |
| rosmaita | sigmavirus24: yrc | 00:53 |
| sigmavirus24 | rosmaita: ty | 00:53 |
| etoews | and what if one day the glance api needed to do an action that needed multiple parameters. some of which might be complex? | 00:53 |
| nikhil_k | Also: The project design needs to keep 'status' field non-writable (from the client/user's perpective); it should happen from within the code. | 00:53 |
| sigmavirus24 | Ah yes, nikhil_k's constraint is an important one | 00:54 |
| etoews | 100% agreed that the status field is non-writable. | 00:54 |
| nikhil_k | :) | 00:54 |
| etoews | so let me at least throw this out there. | 00:55 |
| etoews | http://developer.openstack.org/api-ref-compute-v2-ext.html#ext-os-instance-actions | 00:55 |
| salv-orlando | so the execution of an action ultimately has an effect on the representation of the resource it acts upon | 00:55 |
| etoews | the nova api apparently actually creates an action resource | 00:55 |
| etoews | (for that particular extension anyway) | 00:55 |
| rosmaita | i don't think we want to do that here | 00:56 |
| sigmavirus24 | etoews: right, glance seems to have ruled that out at the Atlanta Summit | 00:56 |
| salv-orlando | in that case I personally think the use of "actions" might be legit, even if I'd say it should be a PUT because at the end of the day the goal of the API is modifying the status of the resource once the task associated with the action completes | 00:56 |
| sigmavirus24 | This seems to be more of an on/off switch though | 00:56 |
| etoews | i read it like the use case of those action resources is as an audit log | 00:56 |
| salv-orlando | fwiw, neutron API implements this kind of construct for attaching or detaching interfaces from a router | 00:56 |
| stevelle | etoews: I felt similarly | 00:57 |
| etoews | rosmaita: can you tl;dr that decision | 00:57 |
| etoews | ? | 00:57 |
| rosmaita | well, we had just introduced tasks into glance | 00:57 |
| elmiko | i thought it was bad form to tunnel controller like commands through a single endpoint? | 00:57 |
| rosmaita | as actual entities | 00:57 |
| rosmaita | that track long-running asynchronous operations | 00:58 |
| rosmaita | this just seemed like a different kind of thing | 00:58 |
| sigmavirus24 | elmiko: it is, which is why miguelgrinberg and I are not fond of it | 00:58 |
| elmiko | sigmavirus24: ack, thanks | 00:58 |
| etoews | elmiko sigmavirus24: do you have a reference for why it's bad form. something that might help everyone understand? | 00:59 |
| cyeoh | fwiw instance-actions in nova will basically go away once we have tasks | 00:59 |
| etoews | cyeoh: good to konw | 00:59 |
| rosmaita | but a lot of those instance-actions actually are better modelled as tasks | 00:59 |
| salv-orlando | as operations are async what are the proposed solutions to track the progress of a operation, if I might ask? | 01:00 |
| nikhil_k | That's v3 though, right? | 01:00 |
| elmiko | etoews: my only reference is the o'reilly rest design book, i'll see if has an argument though | 01:00 |
| cyeoh | nikhil_k: well v2.1 microversions ;-) | 01:00 |
| etoews | elmiko: thx | 01:00 |
| nikhil_k | ahh | 01:00 |
| sigmavirus24 | etoews: well, miguelgrinberg will love this, but it's certainly not HATEOAS for one | 01:00 |
| etoews | dang. we're at time. | 01:00 |
| etoews | #endmeeting | 01:00 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 01:00 | |
| openstack | Meeting ended Thu Feb 5 01:00:54 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 01:00 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-02-05-00.00.html | 01:00 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-02-05-00.00.txt | 01:00 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-02-05-00.00.log.html | 01:01 |
| salv-orlando | goodnight | 01:01 |
| ryansb | night folks | 01:01 |
| *** ryansb has left #openstack-meeting-3 | 01:01 | |
| etoews | i really really don't want to block rosmaita nikhil_k and the glance crew | 01:01 |
| sigmavirus24 | gnight all | 01:01 |
| sigmavirus24 | time to feast on some dinner | 01:01 |
| etoews | g'night! | 01:01 |
| sigmavirus24 | etoews: ML thread? | 01:01 |
| elmiko | night, etoews thanks again =) | 01:01 |
| etoews | does that work for you rosmaita nikhil_k ? | 01:01 |
| *** hemanth is now known as hemanth-away | 01:02 | |
| rosmaita | etoews: i think it will have to! | 01:02 |
| rosmaita | i guess we can get a sense of what the consensus is | 01:02 |
| *** VW_ has quit IRC | 01:02 | |
| rosmaita | but nikhil_k will have to say if the delay will be bad for glance | 01:03 |
| nikhil_k | etoews: yeah, I guess we will have to | 01:03 |
| nikhil_k | We don't mind waiting another week? | 01:03 |
| nikhil_k | Should we catch up next one? | 01:03 |
| *** penick has quit IRC | 01:03 | |
| *** sigmavirus24 is now known as sigmavirus24_awa | 01:03 | |
| nikhil_k | etoews: rosmaita ^ | 01:03 |
| etoews | yes | 01:03 |
| *** melwitt has quit IRC | 01:04 | |
| nikhil_k | Thanks! | 01:04 |
| nikhil_k | s/week?/week./ | 01:04 |
| rosmaita | so is the decision ML & next week discussion, or jsut discuss next week? | 01:04 |
| etoews | nikhil_k: should we still start an ml thread to get things moving before then. | 01:04 |
| *** xuhanp has quit IRC | 01:04 | |
| etoews | ? | 01:05 |
| nikhil_k | I think Eddie is leading the dev work on it | 01:05 |
| nikhil_k | and hemanth-away has some ideas | 01:05 |
| etoews | let's do ml and meet next week | 01:05 |
| nikhil_k | etoews: How about I confirm with you with a few more details by Mon? | 01:05 |
| etoews | hopefully we get a good discussion and vote next week. | 01:05 |
| nikhil_k | Aight, that sounds good. | 01:06 |
| rosmaita | ok | 01:06 |
| rosmaita | etoews: thanks | 01:06 |
| etoews | nikhil_k: you sure. i can hold off if you like. | 01:06 |
| nikhil_k | Appreciate the time etoews :) | 01:06 |
| nikhil_k | etoews: oh sure | 01:06 |
| nikhil_k | (I'm getting a lag in my IRC client) | 01:06 |
| etoews | actually, it would be better if you kicked off the ml thread when you're ready | 01:06 |
| etoews | nikhil_k ^ | 01:07 |
| nikhil_k | etoews: sure thing | 01:07 |
| nikhil_k | See you next otherwise ;) | 01:07 |
| etoews | nikhil_k: and don't hesitate to ping the wg people on irc to respond on the thread | 01:07 |
| etoews | or ping me to ping them if you prefer. :) | 01:08 |
| nikhil_k | sounds like a plan :D | 01:08 |
| rosmaita | k, night all! | 01:08 |
| *** rosmaita has left #openstack-meeting-3 | 01:08 | |
| etoews | thanks! | 01:08 |
| nikhil_k | Thanks too | 01:09 |
| *** bradjones has quit IRC | 01:17 | |
| *** david-lyle is now known as david-lyle_afk | 01:18 | |
| *** bradjones has joined #openstack-meeting-3 | 01:18 | |
| *** ChuckC has joined #openstack-meeting-3 | 01:23 | |
| *** annegent_ has joined #openstack-meeting-3 | 01:23 | |
| *** ChuckC_ has quit IRC | 01:26 | |
| *** annegent_ has quit IRC | 01:35 | |
| *** SumitNaiksatam has quit IRC | 01:41 | |
| *** SumitNaiksatam has joined #openstack-meeting-3 | 01:42 | |
| *** SridharRamaswam1 has quit IRC | 01:46 | |
| *** salv-orlando has quit IRC | 01:48 | |
| *** markvoelker has joined #openstack-meeting-3 | 01:54 | |
| *** stanzgy has joined #openstack-meeting-3 | 01:55 | |
| *** etoews has quit IRC | 01:57 | |
| *** lblanchard has joined #openstack-meeting-3 | 01:58 | |
| *** etoews has joined #openstack-meeting-3 | 02:01 | |
| *** Networkn3rd has joined #openstack-meeting-3 | 02:02 | |
| *** lblanchard has quit IRC | 02:05 | |
| *** MarkAtwood has joined #openstack-meeting-3 | 02:13 | |
| *** banix has joined #openstack-meeting-3 | 02:16 | |
| *** alexsyip has quit IRC | 02:20 | |
| *** etoews has quit IRC | 02:23 | |
| *** etoews has joined #openstack-meeting-3 | 02:24 | |
| *** tellesnobrega_ has quit IRC | 02:31 | |
| *** penick has joined #openstack-meeting-3 | 02:31 | |
| *** penick_ has joined #openstack-meeting-3 | 02:32 | |
| *** SumitNaiksatam has quit IRC | 02:32 | |
| *** Sukhdev has quit IRC | 02:36 | |
| *** SumitNaiksatam has joined #openstack-meeting-3 | 02:36 | |
| *** penick has quit IRC | 02:36 | |
| *** penick_ is now known as penick | 02:36 | |
| *** etoews has quit IRC | 02:38 | |
| *** ivar-lazzaro has quit IRC | 02:38 | |
| *** bpokorny has quit IRC | 02:39 | |
| *** melwitt has joined #openstack-meeting-3 | 02:39 | |
| *** melwitt has left #openstack-meeting-3 | 02:39 | |
| *** salv-orlando has joined #openstack-meeting-3 | 02:49 | |
| *** mattgriffin has joined #openstack-meeting-3 | 02:50 | |
| *** tellesnobrega_ has joined #openstack-meeting-3 | 02:53 | |
| *** yamahata has quit IRC | 02:55 | |
| *** yamamoto_ has joined #openstack-meeting-3 | 02:57 | |
| *** Longgeek has joined #openstack-meeting-3 | 02:57 | |
| *** tellesnobrega_ has quit IRC | 02:59 | |
| *** eghobo has quit IRC | 03:02 | |
| *** mattgriffin has quit IRC | 03:03 | |
| *** salv-orlando has quit IRC | 03:06 | |
| *** marun has joined #openstack-meeting-3 | 03:10 | |
| *** tellesnobrega_ has joined #openstack-meeting-3 | 03:12 | |
| *** tonyb has left #openstack-meeting-3 | 03:13 | |
| *** marun has quit IRC | 03:15 | |
| *** amotoki has joined #openstack-meeting-3 | 03:25 | |
| *** Networkn3rd has quit IRC | 03:25 | |
| *** banix has quit IRC | 03:25 | |
| *** banix has joined #openstack-meeting-3 | 03:29 | |
| *** mattgriffin has joined #openstack-meeting-3 | 03:34 | |
| *** killer_prince is now known as lazy_prince | 03:37 | |
| *** etoews has joined #openstack-meeting-3 | 03:39 | |
| *** etoews has quit IRC | 03:44 | |
| *** MarkAtwood has quit IRC | 03:49 | |
| *** thomasem has quit IRC | 03:52 | |
| *** Longgeek has quit IRC | 03:53 | |
| *** VW_ has joined #openstack-meeting-3 | 03:56 | |
| *** absubram has joined #openstack-meeting-3 | 04:06 | |
| *** badveli has quit IRC | 04:06 | |
| *** absubram has quit IRC | 04:06 | |
| *** Longgeek has joined #openstack-meeting-3 | 04:10 | |
| *** etoews has joined #openstack-meeting-3 | 04:14 | |
| *** lazy_prince is now known as killer_prince | 04:15 | |
| *** banix has quit IRC | 04:18 | |
| *** etoews has quit IRC | 04:18 | |
| *** penick has quit IRC | 04:25 | |
| *** Networkn3rd has joined #openstack-meeting-3 | 04:26 | |
| *** VW_ has quit IRC | 04:26 | |
| *** VW_ has joined #openstack-meeting-3 | 04:27 | |
| *** salv-orlando has joined #openstack-meeting-3 | 04:27 | |
| *** Networkn3rd has quit IRC | 04:31 | |
| *** julim has joined #openstack-meeting-3 | 04:32 | |
| *** VW_ has quit IRC | 04:39 | |
| *** SridharRamaswamy has joined #openstack-meeting-3 | 04:40 | |
| *** killer_prince is now known as lazy_prince | 04:43 | |
| *** mattgriffin has quit IRC | 04:44 | |
| *** salv-orlando has quit IRC | 04:47 | |
| *** eghobo has joined #openstack-meeting-3 | 05:04 | |
| *** etoews has joined #openstack-meeting-3 | 05:15 | |
| *** etoews has quit IRC | 05:19 | |
| *** ivar-lazzaro has joined #openstack-meeting-3 | 05:25 | |
| *** Networkn3rd has joined #openstack-meeting-3 | 05:27 | |
| *** Networkn3rd has quit IRC | 05:31 | |
| *** salv-orlando has joined #openstack-meeting-3 | 05:33 | |
| *** salv-orlando has quit IRC | 05:34 | |
| *** yamahata has joined #openstack-meeting-3 | 05:36 | |
| *** salv-orlando has joined #openstack-meeting-3 | 05:44 | |
| *** coolsvap_ is now known as coolsvap | 05:49 | |
| *** ivar-laz_ has joined #openstack-meeting-3 | 05:50 | |
| *** salv-orlando has quit IRC | 05:51 | |
| *** ivar-la__ has joined #openstack-meeting-3 | 05:52 | |
| *** ivar-lazzaro has quit IRC | 05:52 | |
| *** SridharRamaswamy has quit IRC | 05:54 | |
| *** ivar-laz_ has quit IRC | 05:55 | |
| *** tellesnobrega_ has quit IRC | 05:58 | |
| *** salv-orlando has joined #openstack-meeting-3 | 06:02 | |
| *** salv-orlando has quit IRC | 06:03 | |
| *** etoews has joined #openstack-meeting-3 | 06:16 | |
| *** salv-orlando has joined #openstack-meeting-3 | 06:16 | |
| *** salv-orlando has quit IRC | 06:16 | |
| *** etoews has quit IRC | 06:20 | |
| *** salv-orlando has joined #openstack-meeting-3 | 06:26 | |
| *** Networkn3rd has joined #openstack-meeting-3 | 06:28 | |
| *** salv-orlando has quit IRC | 06:31 | |
| *** Networkn3rd has quit IRC | 06:32 | |
| *** MarkAtwood has joined #openstack-meeting-3 | 06:52 | |
| *** etoews has joined #openstack-meeting-3 | 06:57 | |
| *** MarkAtwood has quit IRC | 06:57 | |
| *** Networkn3rd has joined #openstack-meeting-3 | 07:00 | |
| *** etoews has quit IRC | 07:02 | |
| *** Networkn3rd has quit IRC | 07:05 | |
| *** markvoelker has quit IRC | 07:06 | |
| *** wuhg has joined #openstack-meeting-3 | 07:09 | |
| *** jmanko has joined #openstack-meeting-3 | 07:17 | |
| *** sahid has joined #openstack-meeting-3 | 07:20 | |
| *** jmank has quit IRC | 07:20 | |
| *** mwang2__ has joined #openstack-meeting-3 | 07:23 | |
| *** zz_ttrifonov is now known as ttrifonov | 07:26 | |
| *** mwang2_ has quit IRC | 07:26 | |
| *** scheuran has joined #openstack-meeting-3 | 07:27 | |
| *** SumitNaiksatam has quit IRC | 07:29 | |
| *** salv-orlando has joined #openstack-meeting-3 | 07:38 | |
| *** jcoufal has joined #openstack-meeting-3 | 07:38 | |
| *** salv-orlando has quit IRC | 07:51 | |
| *** SumitNaiksatam has joined #openstack-meeting-3 | 07:54 | |
| *** etoews has joined #openstack-meeting-3 | 07:58 | |
| *** ivar-lazzaro has joined #openstack-meeting-3 | 07:59 | |
| *** Networkn3rd has joined #openstack-meeting-3 | 08:02 | |
| *** jtomasek has joined #openstack-meeting-3 | 08:02 | |
| *** ivar-laz_ has joined #openstack-meeting-3 | 08:02 | |
| *** belmoreira has joined #openstack-meeting-3 | 08:02 | |
| *** ivar-la__ has quit IRC | 08:02 | |
| *** etoews has quit IRC | 08:02 | |
| *** devvesa has joined #openstack-meeting-3 | 08:03 | |
| *** eghobo has quit IRC | 08:03 | |
| *** ivar-lazzaro has quit IRC | 08:04 | |
| *** mrmartin has joined #openstack-meeting-3 | 08:05 | |
| *** lsmola has quit IRC | 08:05 | |
| *** stanzgy has quit IRC | 08:06 | |
| *** stanzgy has joined #openstack-meeting-3 | 08:06 | |
| *** Networkn3rd has quit IRC | 08:06 | |
| *** sergef has joined #openstack-meeting-3 | 08:07 | |
| *** iovadia has joined #openstack-meeting-3 | 08:11 | |
| *** iovadia has quit IRC | 08:15 | |
| *** jtomasek has quit IRC | 08:18 | |
| *** ivar-laz_ has quit IRC | 08:20 | |
| *** lsmola has joined #openstack-meeting-3 | 08:22 | |
| *** stanzgy has quit IRC | 08:24 | |
| *** sahid has quit IRC | 08:25 | |
| *** iovadia has joined #openstack-meeting-3 | 08:31 | |
| *** salv-orl_ has joined #openstack-meeting-3 | 08:32 | |
| *** yamamoto_ has quit IRC | 08:35 | |
| *** lsmola has quit IRC | 08:36 | |
| *** yamahata has quit IRC | 08:36 | |
| *** matrohon has joined #openstack-meeting-3 | 08:38 | |
| *** lsmola has joined #openstack-meeting-3 | 08:38 | |
| *** MaxV has joined #openstack-meeting-3 | 08:44 | |
| *** watanabe_isao has quit IRC | 08:48 | |
| *** evgenyf has joined #openstack-meeting-3 | 08:49 | |
| *** safchain has joined #openstack-meeting-3 | 08:50 | |
| *** armax has quit IRC | 08:54 | |
| *** mrda is now known as mrda-away | 08:57 | |
| *** matrohon has quit IRC | 08:59 | |
| *** etoews has joined #openstack-meeting-3 | 08:59 | |
| *** Networkn3rd has joined #openstack-meeting-3 | 09:02 | |
| *** JeanBriceCombebi has joined #openstack-meeting-3 | 09:03 | |
| *** etoews has quit IRC | 09:03 | |
| *** Longgeek has quit IRC | 09:05 | |
| *** Networkn3rd has quit IRC | 09:07 | |
| *** stanzgy has joined #openstack-meeting-3 | 09:09 | |
| *** sandr8 has quit IRC | 09:16 | |
| *** sahid has joined #openstack-meeting-3 | 09:18 | |
| *** salv-orl_ has quit IRC | 09:19 | |
| *** JeanBriceCombebi has quit IRC | 09:24 | |
| *** marun has joined #openstack-meeting-3 | 09:41 | |
| *** salv-orlando has joined #openstack-meeting-3 | 09:41 | |
| *** sandr8 has joined #openstack-meeting-3 | 09:42 | |
| *** marun has quit IRC | 09:45 | |
| *** zz_johnthetubagu is now known as johnthetubaguy | 09:54 | |
| *** etoews has joined #openstack-meeting-3 | 10:00 | |
| *** Networkn3rd has joined #openstack-meeting-3 | 10:03 | |
| *** etoews has quit IRC | 10:04 | |
| *** JeanBriceCombebi has joined #openstack-meeting-3 | 10:07 | |
| *** Networkn3rd has quit IRC | 10:08 | |
| *** JeanBriceCombebi has quit IRC | 10:08 | |
| *** JeanBriceCombebi has joined #openstack-meeting-3 | 10:11 | |
| *** tellesnobrega_ has joined #openstack-meeting-3 | 10:28 | |
| *** coolsvap is now known as coolsvap_ | 10:29 | |
| *** salv-orlando has quit IRC | 10:35 | |
| *** jtomasek has joined #openstack-meeting-3 | 10:37 | |
| *** JeanBriceCombebi has quit IRC | 10:39 | |
| *** tellesnobrega_ has quit IRC | 10:43 | |
| *** tellesnobrega_ has joined #openstack-meeting-3 | 10:45 | |
| *** stanzgy has quit IRC | 10:51 | |
| *** alexpilotti has joined #openstack-meeting-3 | 10:56 | |
| *** etoews has joined #openstack-meeting-3 | 11:00 | |
| *** etoews has quit IRC | 11:05 | |
| *** tellesnobrega_ has quit IRC | 11:10 | |
| *** salv-orlando has joined #openstack-meeting-3 | 11:35 | |
| *** yamamoto has joined #openstack-meeting-3 | 11:36 | |
| *** salv-orlando has quit IRC | 11:38 | |
| *** pkoniszewski has joined #openstack-meeting-3 | 11:40 | |
| *** markvoelker has joined #openstack-meeting-3 | 11:40 | |
| *** coolsvap_ is now known as coolsvap | 11:46 | |
| *** markvoelker has quit IRC | 11:47 | |
| *** coolsvap is now known as coolsvap_ | 12:01 | |
| *** reed has joined #openstack-meeting-3 | 12:06 | |
| *** salv-orlando has joined #openstack-meeting-3 | 12:07 | |
| *** wuhg has quit IRC | 12:09 | |
| *** salv-orlando has quit IRC | 12:11 | |
| *** salv-orlando has joined #openstack-meeting-3 | 12:28 | |
| *** salv-orlando has quit IRC | 12:33 | |
| *** xuhanp has joined #openstack-meeting-3 | 12:34 | |
| *** mwagner_lap has quit IRC | 12:35 | |
| *** salv-orlando has joined #openstack-meeting-3 | 12:39 | |
| *** markvoelker has joined #openstack-meeting-3 | 12:43 | |
| *** salv-orlando has quit IRC | 12:43 | |
| *** markvoelker has quit IRC | 12:47 | |
| *** VW_ has joined #openstack-meeting-3 | 12:50 | |
| *** markvoelker has joined #openstack-meeting-3 | 13:01 | |
| *** JeanBriceCombebi has joined #openstack-meeting-3 | 13:02 | |
| *** etoews has joined #openstack-meeting-3 | 13:02 | |
| *** etoews has quit IRC | 13:07 | |
| *** yamamoto has quit IRC | 13:07 | |
| *** VW_ has quit IRC | 13:10 | |
| *** jckasper has quit IRC | 13:11 | |
| *** matrohon has joined #openstack-meeting-3 | 13:11 | |
| *** enikanorov_ has quit IRC | 13:16 | |
| *** baoli has joined #openstack-meeting-3 | 13:22 | |
| *** etoews has joined #openstack-meeting-3 | 13:25 | |
| *** mwagner_lap has joined #openstack-meeting-3 | 13:27 | |
| *** etoews has quit IRC | 13:38 | |
| *** etoews has joined #openstack-meeting-3 | 13:39 | |
| *** igordcard has joined #openstack-meeting-3 | 13:39 | |
| *** matrohon has quit IRC | 13:40 | |
| *** jpomero has joined #openstack-meeting-3 | 13:41 | |
| *** igordcard has quit IRC | 13:42 | |
| *** thomasem has joined #openstack-meeting-3 | 13:44 | |
| *** jckasper_ has joined #openstack-meeting-3 | 13:55 | |
| *** igordcard has joined #openstack-meeting-3 | 13:57 | |
| *** elmiko has left #openstack-meeting-3 | 13:57 | |
| *** VW_ has joined #openstack-meeting-3 | 13:57 | |
| *** thomasem has quit IRC | 13:59 | |
| *** thomasem has joined #openstack-meeting-3 | 14:00 | |
| *** amotoki has quit IRC | 14:00 | |
| *** etoews has quit IRC | 14:03 | |
| *** salv-orlando has joined #openstack-meeting-3 | 14:04 | |
| *** scheuran has quit IRC | 14:04 | |
| *** igordcard has quit IRC | 14:07 | |
| *** andymaier has joined #openstack-meeting-3 | 14:07 | |
| *** sergef_ has joined #openstack-meeting-3 | 14:07 | |
| *** salv-orlando has quit IRC | 14:08 | |
| *** thomasem has quit IRC | 14:08 | |
| *** alazarev has quit IRC | 14:09 | |
| *** sergef has quit IRC | 14:10 | |
| *** sergef_ is now known as sergef | 14:10 | |
| *** alazarev has joined #openstack-meeting-3 | 14:11 | |
| *** lblanchard has joined #openstack-meeting-3 | 14:14 | |
| *** thomasem has joined #openstack-meeting-3 | 14:15 | |
| *** qwebirc34322 has joined #openstack-meeting-3 | 14:18 | |
| *** igordcard has joined #openstack-meeting-3 | 14:20 | |
| *** qwebirc18494 has joined #openstack-meeting-3 | 14:21 | |
| *** qwebirc34322 has quit IRC | 14:22 | |
| *** salv-orlando has joined #openstack-meeting-3 | 14:26 | |
| *** xuhanp has quit IRC | 14:29 | |
| *** jcoufal_ has joined #openstack-meeting-3 | 14:30 | |
| *** jcoufal has quit IRC | 14:33 | |
| *** enikanorov_ has joined #openstack-meeting-3 | 14:35 | |
| *** mattgriffin has joined #openstack-meeting-3 | 14:38 | |
| *** evgenyf has quit IRC | 14:46 | |
| *** absubram has joined #openstack-meeting-3 | 14:47 | |
| *** absubram has left #openstack-meeting-3 | 14:48 | |
| *** amuller has joined #openstack-meeting-3 | 14:57 | |
| *** tidwellr has joined #openstack-meeting-3 | 14:57 | |
| *** carl_baldwin has joined #openstack-meeting-3 | 14:59 | |
| carl_baldwin | hi all | 15:00 |
| *** mlavalle has joined #openstack-meeting-3 | 15:00 | |
| pavel_bondar | hi | 15:00 |
| *** pc_m has joined #openstack-meeting-3 | 15:00 | |
| *** sigmavirus24_awa is now known as sigmavirus24 | 15:00 | |
| mlavalle | hi | 15:00 |
| *** stevelle has left #openstack-meeting-3 | 15:00 | |
| *** johnbelamaric1 has joined #openstack-meeting-3 | 15:00 | |
| pc_m | hi | 15:00 |
| carl_baldwin | pavel_bondar: mlavalle: pc_m: hi | 15:00 |
| carl_baldwin | amuller: ping | 15:00 |
| johnbelamaric1 | hello | 15:00 |
| *** qwebirc18494 has quit IRC | 15:00 | |
| carl_baldwin | tidwellr: ping | 15:00 |
| amuller | morning | 15:00 |
| carl_baldwin | johnbelamaric1: hi | 15:00 |
| tidwellr | pong | 15:00 |
| carl_baldwin | #startmeeting neutron_l3 | 15:01 |
| openstack | Meeting started Thu Feb 5 15:01:09 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 |
| *** openstack changes topic to " (Meeting topic: neutron_l3)" | 15:01 | |
| openstack | The meeting name has been set to 'neutron_l3' | 15:01 |
| *** johnbelamaric1 has quit IRC | 15:01 | |
| carl_baldwin | #topic Announcements | 15:01 |
| *** openstack changes topic to "Announcements (Meeting topic: neutron_l3)" | 15:01 | |
| *** johnbelamaric has joined #openstack-meeting-3 | 15:01 | |
| carl_baldwin | #link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam | 15:01 |
| carl_baldwin | I think Kilo-2 is today! | 15:01 |
| *** armax has joined #openstack-meeting-3 | 15:02 | |
| carl_baldwin | That means if it hasn’t entered the queue yet, it won’t make it. I’m not sure when they’ll cut it. | 15:02 |
| *** Swami has joined #openstack-meeting-3 | 15:02 | |
| carl_baldwin | Also means that Kilo-3 is coming right up. It’ll be here before we know it. | 15:02 |
| carl_baldwin | #link https://wiki.openstack.org/wiki/Kilo_Release_Schedule | 15:03 |
| carl_baldwin | Any other announcements? | 15:04 |
| carl_baldwin | #topic Bugs | 15:04 |
| *** openstack changes topic to "Bugs (Meeting topic: neutron_l3)" | 15:04 | |
| *** Rajeev has joined #openstack-meeting-3 | 15:04 | |
| carl_baldwin | Any bugs to bring up? | 15:04 |
| amuller | https://bugs.launchpad.net/neutron/+bug/1418097 | 15:05 |
| amuller | Probably more OVS related than L3, but I need help to triage that one | 15:05 |
| *** marun has joined #openstack-meeting-3 | 15:05 | |
| carl_baldwin | This one has eluded me until this week: https://bugs.launchpad.net/neutron/+bug/1404743 I’ll take a look at it. | 15:05 |
| carl_baldwin | amuller: Anything to discuss wrt to this kernel panic? | 15:06 |
| *** etoews has joined #openstack-meeting-3 | 15:06 | |
| *** sahid has quit IRC | 15:06 | |
| *** sahid has joined #openstack-meeting-3 | 15:06 | |
| amuller | Logic dictates it's more to do with OVS / kernel versions, and some OVS bug. However, that doesn't explain why it only started happening since the patch linked in the bug report. | 15:07 |
| Rajeev | amuller: I encountered a Jenkins failure for dsvm-functional neutron.tests.function yesterday evening too | 15:07 |
| amuller | Rajeev: Can you link? | 15:07 |
| carl_baldwin | amuller: I can’t imagine how the patch referenced could cause it but I’ve not thought deeply about it yet. | 15:07 |
| Swami | amuller: Is this only seen in the functional test. | 15:07 |
| *** VW__ has joined #openstack-meeting-3 | 15:07 | |
| Rajeev | amuller: http://logs.openstack.org/77/153077/1/check/check-neutron-dsvm-functional/a1a6a1f/ | 15:08 |
| amuller | carl_baldwin: I can rebase back to before that patch, and I can run the tests reliably. I then go one patch forward and it happens on the first run. It's very odd. I agree Carl that the patch looks innocent. | 15:08 |
| Rajeev | amuller: my recheck went through ok | 15:08 |
| amuller | Rajeev: That seems unrelated but still interesting | 15:08 |
| Rajeev | amuller: good to know, thanks. | 15:09 |
| *** VW_ has quit IRC | 15:09 | |
| carl_baldwin | amuller: Well, I can’t say there is nothing in the patch but it is strange. | 15:09 |
| amuller | Swami: Some more context: Internal testing on a Juno based build (!) started seeing the same issue, with ovs-vswitch crashing or causing a kernel panic | 15:09 |
| *** sahid has quit IRC | 15:09 | |
| Swami | amuller: thanks | 15:10 |
| amuller | Now, that's the same symptom, but a Juno based build obviously doesn't have any Kilo patches | 15:10 |
| *** sahid has joined #openstack-meeting-3 | 15:10 | |
| carl_baldwin | armax: Is Rajeev’s timeout exception similar to or the same as the one you saw? | 15:10 |
| amuller | Swami: And internal testing was done on a 'production' system, not via functional testing | 15:10 |
| amuller | I suspect that some combinations of kernels and OVS builds are utterly broken | 15:10 |
| armax | carl_baldwin: yes it’s the same I believe | 15:11 |
| amuller | and will cause catastrophic failures in any openstack cloud using that combination | 15:11 |
| *** banix has joined #openstack-meeting-3 | 15:11 | |
| carl_baldwin | amuller: Does the ovs crash with Juno have the same trace or other symptoms? | 15:12 |
| amuller | It looks the same | 15:12 |
| carl_baldwin | amuller: But, yet, when you rebase to before the patch, it no longer happens? Is that reliably repeatable? | 15:13 |
| carl_baldwin | armax: Any idea yet if this timeout thing is happening with any frequency? | 15:13 |
| amuller | But to reiterate, I have a VM, where if I go back in time everything works properly, then when I fast forward to HEAD it starts breaking, without reinstalling anything, without changing any versions of anything. Simply git rebasing back and forward. | 15:13 |
| amuller | carl_baldwin: Yes it's reliable. | 15:13 |
| haleyb | and if you have the crashdump trace let's get it in the bug and/or sent to the OVS/netdev ML - could be a known bug | 15:13 |
| *** [1]evgenyf has joined #openstack-meeting-3 | 15:14 | |
| armax | carl_baldwin: not directly, but it should be fairly trivial to pull a logstash query and see what’s going on | 15:14 |
| carl_baldwin | armax: okay | 15:15 |
| *** wojdev has joined #openstack-meeting-3 | 15:16 | |
| amuller | haleyb: Will do | 15:16 |
| carl_baldwin | amuller: I’ll look in to it a bit more after the meeting and add notes to the bug report. | 15:17 |
| carl_baldwin | amuller: Anything else we can discuss here? | 15:17 |
| amuller | Nay | 15:17 |
| Rajeev | amuller: do you know what specific operation is it crashing on ? | 15:17 |
| amuller | Rajeev: No | 15:17 |
| Rajeev | ovs agent log might be of some help | 15:18 |
| amuller | We don't use the OVS agent for the L3 functional testing though | 15:18 |
| amuller | I'll see if there's anything in the OVS logs or crash traces | 15:18 |
| *** VW__ has quit IRC | 15:19 | |
| carl_baldwin | amuller: Rajeev: thanks. Let’s move on and discuss this on the mail thread or IRC. | 15:19 |
| Rajeev | carl_baldwin: agreed | 15:19 |
| carl_baldwin | Any other bugs? | 15:19 |
| carl_baldwin | #topic L3 Agent Restructuring | 15:20 |
| Swami | carl_baldwin: there are couple of dvr related bugs still waiting for review | 15:20 |
| *** openstack changes topic to "L3 Agent Restructuring (Meeting topic: neutron_l3)" | 15:20 | |
| carl_baldwin | Swami: Okay, we’ll get the the dvr section soon. | 15:20 |
| Swami | carl_baldwin: thanks | 15:21 |
| carl_baldwin | I have three refactoring patches up for review. | 15:21 |
| carl_baldwin | amuller has one that I can see now. | 15:21 |
| carl_baldwin | The chain starts here: https://review.openstack.org/#/c/150154 | 15:21 |
| carl_baldwin | Then mlavalle has a namespace patch. | 15:22 |
| mlavalle | correct | 15:22 |
| *** igordcard has quit IRC | 15:22 | |
| carl_baldwin | amuller: will you be able to visit your patch today? | 15:22 |
| amuller | carl_baldwin: Yeah you should expect a new revision in a few minutes | 15:23 |
| *** david-lyle_afk is now known as david-lyle | 15:23 | |
| carl_baldwin | amuller: Great. Thanks. It is a good patch. I rebased my stuff behind it. | 15:23 |
| carl_baldwin | mlavalle: Anything on yours to discuss? | 15:23 |
| *** egallen has joined #openstack-meeting-3 | 15:24 | |
| mlavalle | carl_baldwin: as far as the namespace patchset, I finieshed testing it locally in devstack and with the l3 agent funtional tests. I will push the next reviision today. I didn't do it last night because it was late and wanted to respond to all the comments made by amuller pc_m and you | 15:24 |
| carl_baldwin | After these patches, there is only a little bit of router stuff left in the agent. All dealing with plugging interfaces if I’m not mistaken. That’ll be another patch. | 15:24 |
| *** VW_ has joined #openstack-meeting-3 | 15:24 | |
| *** isviridov is now known as isviridov_away | 15:25 | |
| pc_m | good job guys! | 15:25 |
| carl_baldwin | mlavalle: Great. | 15:25 |
| mlavalle | carl_baldwin: there were some changes to the functional test | 15:25 |
| mlavalle | nothing big | 15:26 |
| carl_baldwin | After the interfaces patch, I think there will be one more. I’m nearly convinced that DvrRouter needs to split in to two classes. | 15:26 |
| carl_baldwin | … one for compute nodes and one for shared snat nodes. | 15:26 |
| carl_baldwin | So, two new patches and I think we’ll be in pretty good shape with this project. | 15:27 |
| * carl_baldwin sees the light at the end of the tunnel. | 15:27 | |
| mlavalle | carl_baldwin: the interfaces patch, is that what we talked about last Friday? | 15:27 |
| carl_baldwin | mlavalle: I don’t think so. | 15:27 |
| mlavalle | ok | 15:28 |
| carl_baldwin | mlavalle: ping me a bit later. | 15:28 |
| mlavalle | will do | 15:28 |
| carl_baldwin | #topic neutron-ipam | 15:28 |
| *** openstack changes topic to "neutron-ipam (Meeting topic: neutron_l3)" | 15:28 | |
| mlavalle | carl_baldwin: after lucnh | 15:28 |
| carl_baldwin | salv-orlando: ping | 15:28 |
| carl_baldwin | johnbelamaric: pavel_bondar: hi | 15:29 |
| carl_baldwin | tidwellr: hi | 15:29 |
| pavel_bondar | carl_baldwin: hi | 15:29 |
| tidwellr | hey | 15:29 |
| johnbelamaric | hello | 15:29 |
| carl_baldwin | I feel some good momentum starting to build here. | 15:29 |
| carl_baldwin | I will address feedback on my patch sometime this morning. | 15:29 |
| carl_baldwin | I also put some notes on salv-orlando ’s patch. | 15:30 |
| carl_baldwin | Is there anything to discuss now? | 15:31 |
| pavel_bondar | I have added an early WIP for db_base_refactoring | 15:31 |
| pavel_bondar | #link https://review.openstack.org/#/c/153236/ | 15:31 |
| carl_baldwin | pavel_bondar: ^ it passed one test. ;) | 15:32 |
| pavel_bondar | :) | 15:32 |
| pavel_bondar | yeah, it does not work | 15:32 |
| pavel_bondar | and too early for reviewing it | 15:32 |
| *** VW_ has quit IRC | 15:32 | |
| pavel_bondar | will keep working on it | 15:32 |
| *** VW_ has joined #openstack-meeting-3 | 15:33 | |
| carl_baldwin | pavel_bondar: I added me as a reviewer. Do you think it is worth looking at it from a high level perspective? Or wait? | 15:33 |
| *** jcoufal_ has quit IRC | 15:33 | |
| pavel_bondar | it is better wait for next patset | 15:34 |
| carl_baldwin | pavel_bondar: ack | 15:34 |
| *** jcoufal has joined #openstack-meeting-3 | 15:34 | |
| carl_baldwin | Anything else to discuss about IPAM? | 15:34 |
| johnbelamaric | carl_baldwin: I think any questions are best addressed in the reviews right now | 15:34 |
| tidwellr | agreed | 15:35 |
| johnbelamaric | carl_baldwin: well, there is this open question on the sequence, but I think it may be easier to deal with in the review than here | 15:35 |
| carl_baldwin | johnbelamaric: Fair enough. With refactoring winding down, I can have a better presence on the reviews. | 15:35 |
| johnbelamaric | carl_baldwin: excellent! | 15:35 |
| carl_baldwin | johnbelamaric: okay. | 15:35 |
| carl_baldwin | #topic dvr | 15:35 |
| *** openstack changes topic to "dvr (Meeting topic: neutron_l3)" | 15:35 | |
| carl_baldwin | Swami: hi, I wanted to be sure to leave some time for dvr. | 15:36 |
| Swami | carl_baldwin: thanks | 15:36 |
| Swami | We are currently working on finding a solution to fix the issues in the gate with the dvr related tests. | 15:36 |
| Swami | One thing that came up is, should we always delete the "fip namespace" when vms and come and go. Is it introducing some delay and complexity. | 15:37 |
| carl_baldwin | Swami: That is a good question. I have wondered about that myself. | 15:38 |
| Swami | One idea we had is, can we leave the fip namespace and the fip-agent-gateway there until the external network is there for that particular router. | 15:38 |
| Swami | When external network or the gateway is droped we can go ahead and clean up all the fip-agent port and namespaces. | 15:38 |
| Swami | That would substantially reduce the inter communication between the agents and plugin. | 15:39 |
| carl_baldwin | Swami: The L3 agent knows which external networks are available to it, right? | 15:40 |
| Swami | Yes. | 15:40 |
| carl_baldwin | Swami: Will the list of external networks ever be very big? | 15:41 |
| *** sahid has quit IRC | 15:41 | |
| carl_baldwin | I guess it could be. | 15:41 |
| *** sahid has joined #openstack-meeting-3 | 15:41 | |
| Swami | Just give it a thought and let me know if that is ok and then I can push in the patch. | 15:41 |
| Swami | I also wanted to reduce an rpc call from agent to the plugin to create the "fip agent gw port". | 15:42 |
| carl_baldwin | Swami: So, if I understand it correctly, you want to change so that the fip namespace will stay even if there are no fips. As long as the router has an external gateway then you will create the namespace. | 15:42 |
| carl_baldwin | Swami: Is that correct? | 15:42 |
| Swami | Instead the plugin can create during a floatingip associate. | 15:42 |
| Swami | carl_baldwin: Yes you are right, that is my proposal | 15:42 |
| *** jaypipes has joined #openstack-meeting-3 | 15:43 | |
| carl_baldwin | Swami: That sounds fine to me. I think it would be good to reduce the potential for thrash in creating/deleting the namespace. | 15:43 |
| carl_baldwin | Do others want to weigh in? | 15:43 |
| Swami | carl_baldwin: thanks | 15:43 |
| carl_baldwin | Swami: Just off the top of my head, you’d change it to reference count routers with gateway ports on the compute host instead of floating ips. | 15:44 |
| Rajeev | we like the idea. one clarification | 15:44 |
| Rajeev | is the the ns will be deleted when all the routers on the node do not have external gateway | 15:44 |
| *** jcoufal has quit IRC | 15:45 | |
| Swami | The fip namespace is related to the external network, so when particular external network is removed from the router, that particular fip namespace will be deleted. | 15:46 |
| *** jcoufal has joined #openstack-meeting-3 | 15:46 | |
| carl_baldwin | Swami: when particular network is removed from *all* routers, right? | 15:46 |
| carl_baldwin | *all* meaning all routers present on the compute node. | 15:46 |
| Swami | Yes, from all routers? | 15:46 |
| *** VW_ has quit IRC | 15:46 | |
| *** absubram has joined #openstack-meeting-3 | 15:46 | |
| Swami | If there is even a single router that has a gateway with the specified external network, we will leave the namespace intact. | 15:47 |
| *** jcoufal_ has joined #openstack-meeting-3 | 15:47 | |
| Swami | carl_baldwin: Just a last note before I quit. | 15:47 |
| carl_baldwin | Swami: Just pointing out that more than one router on the compute node may be connected to the same external network. | 15:47 |
| Swami | Can you shed some light on the high bugs that are out there. | 15:47 |
| *** yamahata has joined #openstack-meeting-3 | 15:47 | |
| Swami | #link https://bugs.launchpad.net/neutron/+bug/1411883 | 15:47 |
| Swami | #link https://bugs.launchpad.net/neutron/+bug/1374473 https://bugs.launchpad.net/neutron/+bug/1413630 | 15:48 |
| Swami | carl_baldwin: I need to drop off. | 15:48 |
| carl_baldwin | Swami: What do you mean by “shed some light" | 15:48 |
| carl_baldwin | ? | 15:48 |
| Swami | Rajeev: can continue the discussion if he has any. Or I will ping you later if you have questions. | 15:48 |
| *** sahid has quit IRC | 15:48 | |
| carl_baldwin | Swami: Okay. ttyl | 15:48 |
| Swami | carl_baldwin: Sorry I meant can you take a look at those patches. I is waiting for a while. | 15:49 |
| Swami | Thanks | 15:49 |
| Swami | bye | 15:49 |
| *** iovadia has quit IRC | 15:49 | |
| carl_baldwin | Swami: Yes, I expect to have some more review time freed up. bye. | 15:49 |
| *** sahid has joined #openstack-meeting-3 | 15:49 | |
| carl_baldwin | Rajeev: anything more? | 15:50 |
| Rajeev | carl_baldwin: sure | 15:50 |
| *** jcoufal has quit IRC | 15:50 | |
| *** VW_ has joined #openstack-meeting-3 | 15:51 | |
| Rajeev | in one of the test failures we see that the agent is returning floating ip status as not active | 15:51 |
| Rajeev | because the fip namespace is still being set | 15:51 |
| Rajeev | the tests in dvr job doesn't check the status of the fips before using | 15:51 |
| Rajeev | so attempts to ping and times out | 15:52 |
| carl_baldwin | Rajeev: So, the agent does not allow the fip namespace to get fully constructed before reporting state on the floating ip? | 15:52 |
| carl_baldwin | Rajeev: Does it eventually report active status for the fip? | 15:53 |
| *** Swami has quit IRC | 15:53 | |
| Rajeev | carl_baldwin: correct, because there is no waiting in the agent | 15:53 |
| Rajeev | carl_baldwin: for eventually I believe not | 15:53 |
| Rajeev | but have to look into the code | 15:54 |
| *** wojdev has quit IRC | 15:54 | |
| carl_baldwin | Does the test attempt to wait for active status? Or, does it ignore status and try to ping anyway? | 15:54 |
| *** wojdev has joined #openstack-meeting-3 | 15:55 | |
| Rajeev | carl_baldwin: the test doesn't check status, just pings | 15:55 |
| *** VW_ has quit IRC | 15:55 | |
| Rajeev | carl_baldwin: and fails | 15:55 |
| carl_baldwin | Rajeev: Maybe the test could be enhanced to first wait for active status (fail if it is *never* acheived) | 15:56 |
| Rajeev | carl_baldwin: yes that would be a better approach. | 15:57 |
| carl_baldwin | Rajeev: hence my question about whether it eventually reports active. | 15:57 |
| carl_baldwin | We only have about a minute left. | 15:58 |
| Rajeev | carl_baldwin: since there is no wait/retry only | 15:58 |
| Rajeev | a new update will cause that to happen so will make it unreliable. | 15:58 |
| carl_baldwin | Rajeev: I’m not sure I follow. | 15:59 |
| carl_baldwin | Rajeev: do you want to continue in the openstack-neutron room? | 15:59 |
| Rajeev | carl_baldwin: can take offline. Otherwise we are continuing to look into ways to stabilize the job and resume HA work | 15:59 |
| carl_baldwin | Rajeev: great. ping me later. | 16:00 |
| Rajeev | carl_baldwin: sure. will sign in | 16:00 |
| carl_baldwin | Thanks all! | 16:00 |
| carl_baldwin | #endmeeting | 16:00 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 16:00 | |
| openstack | Meeting ended Thu Feb 5 16:00:23 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:00 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-02-05-15.01.html | 16:00 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-02-05-15.01.txt | 16:00 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-02-05-15.01.log.html | 16:00 |
| mlavalle | have a nice day | 16:00 |
| *** tidwellr has quit IRC | 16:00 | |
| pc_m | bye | 16:00 |
| johnbelamaric | bye | 16:00 |
| *** pc_m has left #openstack-meeting-3 | 16:00 | |
| *** johnbelamaric has left #openstack-meeting-3 | 16:00 | |
| *** VW_ has joined #openstack-meeting-3 | 16:01 | |
| *** bpokorny has joined #openstack-meeting-3 | 16:01 | |
| *** Rajeev has quit IRC | 16:02 | |
| *** baoli has quit IRC | 16:02 | |
| *** baoli has joined #openstack-meeting-3 | 16:03 | |
| *** gholler has joined #openstack-meeting-3 | 16:03 | |
| *** erikmwilson has joined #openstack-meeting-3 | 16:04 | |
| *** sahid has quit IRC | 16:05 | |
| *** amuller has left #openstack-meeting-3 | 16:07 | |
| *** devvesa has quit IRC | 16:10 | |
| *** pkoniszewski has quit IRC | 16:11 | |
| *** vishy has quit IRC | 16:11 | |
| *** vishy has joined #openstack-meeting-3 | 16:12 | |
| *** wojdev has quit IRC | 16:13 | |
| *** JeanBriceCombebi has quit IRC | 16:14 | |
| *** jcoufal_ has quit IRC | 16:17 | |
| *** jcoufal has joined #openstack-meeting-3 | 16:17 | |
| *** [1]evgenyf has quit IRC | 16:27 | |
| *** SridharRamaswamy has joined #openstack-meeting-3 | 16:30 | |
| *** SridharRamaswamy has quit IRC | 16:35 | |
| *** SridharRamaswam1 has joined #openstack-meeting-3 | 16:35 | |
| *** ybathia has joined #openstack-meeting-3 | 16:55 | |
| *** sarob has joined #openstack-meeting-3 | 16:59 | |
| *** mattfarina has joined #openstack-meeting-3 | 17:01 | |
| *** SumitNaiksatam has quit IRC | 17:02 | |
| *** SumitNaiksatam has joined #openstack-meeting-3 | 17:03 | |
| *** pballand has joined #openstack-meeting-3 | 17:03 | |
| *** sbalukoff has quit IRC | 17:04 | |
| *** pkoniszewski has joined #openstack-meeting-3 | 17:05 | |
| *** sarob has quit IRC | 17:05 | |
| *** sarob has joined #openstack-meeting-3 | 17:05 | |
| *** sarob has quit IRC | 17:05 | |
| *** sarob has joined #openstack-meeting-3 | 17:06 | |
| *** SumitNaiksatam has quit IRC | 17:09 | |
| *** sarob has quit IRC | 17:10 | |
| *** SumitNaiksatam has joined #openstack-meeting-3 | 17:13 | |
| *** sarob has joined #openstack-meeting-3 | 17:17 | |
| *** devvesa has joined #openstack-meeting-3 | 17:18 | |
| *** VW__ has joined #openstack-meeting-3 | 17:19 | |
| *** andymaier has quit IRC | 17:20 | |
| *** VW_ has quit IRC | 17:21 | |
| *** mlavalle has quit IRC | 17:21 | |
| *** jtomasek has quit IRC | 17:23 | |
| *** yamahata has quit IRC | 17:24 | |
| *** MaxV has quit IRC | 17:26 | |
| *** lazy_prince is now known as killer_prince | 17:26 | |
| *** mageshgv has joined #openstack-meeting-3 | 17:31 | |
| *** VW__ has quit IRC | 17:35 | |
| *** pkoniszewski has quit IRC | 17:39 | |
| *** SumitNaiksatam has quit IRC | 17:41 | |
| *** belmoreira has quit IRC | 17:41 | |
| *** johnthetubaguy is now known as zz_johnthetubagu | 17:43 | |
| *** VW_ has joined #openstack-meeting-3 | 17:44 | |
| *** VW_ has quit IRC | 17:44 | |
| *** VW_ has joined #openstack-meeting-3 | 17:44 | |
| *** baoli has quit IRC | 17:55 | |
| *** yapeng has joined #openstack-meeting-3 | 17:57 | |
| *** armax has quit IRC | 17:57 | |
| *** baoli has joined #openstack-meeting-3 | 17:57 | |
| *** bpokorny_ has joined #openstack-meeting-3 | 17:59 | |
| *** yamahata has joined #openstack-meeting-3 | 17:59 | |
| *** LouisF has joined #openstack-meeting-3 | 18:00 | |
| *** Youcef has joined #openstack-meeting-3 | 18:01 | |
| *** armax has joined #openstack-meeting-3 | 18:01 | |
| *** rkukura has joined #openstack-meeting-3 | 18:01 | |
| *** bpokorny has quit IRC | 18:02 | |
| rkukura | hi | 18:02 |
| *** Piet has joined #openstack-meeting-3 | 18:02 | |
| *** susaant has joined #openstack-meeting-3 | 18:02 | |
| yapeng | hello | 18:02 |
| mageshgv | Hi | 18:02 |
| *** clu_ has joined #openstack-meeting-3 | 18:02 | |
| yapeng | do we have meeting today? | 18:03 |
| mageshgv | SumitNaiksatam is not visible online. Is he joining ? | 18:03 |
| *** s3wong has joined #openstack-meeting-3 | 18:04 | |
| *** ivar-lazzaro has joined #openstack-meeting-3 | 18:06 | |
| s3wong | no GBP meeting? | 18:06 |
| rkukura | should be - I just emailed Sumit | 18:06 |
| ivar-lazzaro | hi | 18:06 |
| *** SumitNaiksatam has joined #openstack-meeting-3 | 18:07 | |
| *** pballand has quit IRC | 18:07 | |
| s3wong | SumitNaiksatam: hello | 18:07 |
| SumitNaiksatam | rkukura: ivar-lazzaro mageshgv s3wong banix: hi | 18:07 |
| SumitNaiksatam | apologies for the delay | 18:07 |
| yapeng | hi | 18:07 |
| banix | SumitNaiksatam: hi | 18:07 |
| mageshgv | hi | 18:07 |
| rkukura | hi SumitNaiksatam | 18:07 |
| SumitNaiksatam | yapeng: i | 18:08 |
| LouisF | hi | 18:08 |
| SumitNaiksatam | hi | 18:08 |
| SumitNaiksatam | #startmeeting networking_policy | 18:08 |
| openstack | Meeting started Thu Feb 5 18:08:07 2015 UTC and is due to finish in 60 minutes. The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot. | 18:08 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 18:08 |
| *** openstack changes topic to " (Meeting topic: networking_policy)" | 18:08 | |
| openstack | The meeting name has been set to 'networking_policy' | 18:08 |
| SumitNaiksatam | #info agenda https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy#Feb_5th.2C_2015 | 18:08 |
| *** pballand has joined #openstack-meeting-3 | 18:08 | |
| *** vgridnev has joined #openstack-meeting-3 | 18:08 | |
| SumitNaiksatam | nothing in terms of announcements at my end | 18:08 |
| *** ivar-lazzaro has quit IRC | 18:08 | |
| SumitNaiksatam | anyone want to share anything upfront? | 18:08 |
| *** ivar-lazzaro has joined #openstack-meeting-3 | 18:09 | |
| SumitNaiksatam | we will be mostly focussing on the kilo-1 work items | 18:09 |
| *** VW__ has joined #openstack-meeting-3 | 18:09 | |
| *** armax has quit IRC | 18:09 | |
| SumitNaiksatam | #topic Bugs | 18:09 |
| *** openstack changes topic to "Bugs (Meeting topic: networking_policy)" | 18:09 | |
| SumitNaiksatam | in the meeting agenda i have put links to the critical, high and medium bugs | 18:10 |
| *** vgridnev has quit IRC | 18:10 | |
| SumitNaiksatam | thankfully we dont have any outstanding critical bugs | 18:10 |
| *** VW_ has quit IRC | 18:10 | |
| SumitNaiksatam | the links are to the bugs currently targeted for k-1 | 18:10 |
| SumitNaiksatam | can you please take a look at the links and update the status for your assigned bugs? | 18:11 |
| SumitNaiksatam | there were a few bugs popping up on the deletion of resources (in the resource mapping driver) | 18:11 |
| SumitNaiksatam | are there any specific bugs anyone wants to discuss now (and/or the approach to fixing them)? | 18:12 |
| *** mwagner_lap has quit IRC | 18:12 | |
| rkukura | SumitNaiksatam: I started going through my bugs yesterday and adding comments | 18:12 |
| *** VW__ has quit IRC | 18:12 | |
| SumitNaiksatam | rkukura: okay | 18:12 |
| rkukura | if we don’t think a fix will make k1 (in about a week), should we re-target k2? | 18:12 |
| SumitNaiksatam | rkukura: yes | 18:13 |
| SumitNaiksatam | rkukura: but some bugs might need to be fixed asap | 18:13 |
| *** VW_ has joined #openstack-meeting-3 | 18:13 | |
| SumitNaiksatam | rkukura: since they leave the system in an inconsistent state | 18:13 |
| SumitNaiksatam | rkukura: the ones where the deletion is of a resource is not allowed because there are associated resources | 18:14 |
| *** carl_baldwin has quit IRC | 18:14 | |
| rkukura | Unless they get backported to stable-juno, how would k1 get delivered? | 18:14 |
| SumitNaiksatam | but the deletion partially happens, and only the post-commit fails | 18:14 |
| *** carl_baldwin has joined #openstack-meeting-3 | 18:14 | |
| SumitNaiksatam | rkukura: yes, we should backport those to stable/juno | 18:14 |
| ivar-lazzaro | About #link https://bugs.launchpad.net/group-based-policy/+bug/1414139 | 18:15 |
| rkukura | do we have a target for a stable/juno release? | 18:15 |
| SumitNaiksatam | #chair rkukura ivar-lazzaro s3wong mageshgv | 18:16 |
| openstack | Current chairs: SumitNaiksatam ivar-lazzaro mageshgv rkukura s3wong | 18:16 |
| SumitNaiksatam | rkukura: yes, its on launchpad | 18:16 |
| SumitNaiksatam | rkukura: also in the etherpad i shared in the last meeting #link https://etherpad.openstack.org/p/kilo-gbp-plan | 18:16 |
| SumitNaiksatam | ivar-lazzaro: go ahead | 18:17 |
| *** armax has joined #openstack-meeting-3 | 18:17 | |
| *** hemanthravi has joined #openstack-meeting-3 | 18:17 | |
| rkukura | I’m not seeing a juno/stable release on either of those | 18:17 |
| ivar-lazzaro | RMD assumes implicit driver running, to give some context, when the RMD is running alone it accepts any object even if not linked properly (l2 without L3policy_id) | 18:17 |
| ivar-lazzaro | now the issue here is on where to do the check | 18:18 |
| ivar-lazzaro | If I were to check the missing link in the precommit, the implicit driver case would fail | 18:18 |
| SumitNaiksatam | rkukura: ah, i imagined you were asking about k-1 | 18:18 |
| ivar-lazzaro | since all the pre-commits are executed before all the post commits | 18:18 |
| rkukura | ivar-lazzaro: I think RMD should validate the needed resources | 18:19 |
| SumitNaiksatam | rkukura: we can decide in a stable/juno release date once we actually fix these bugs | 18:19 |
| ivar-lazzaro | rkukura: I'm wondering where though... Doing it in the precommit will break the ID case | 18:19 |
| SumitNaiksatam | rkukura: these have been pending for some time now, ideally we should have had another stable/juno by now, IMHO | 18:19 |
| *** mattfarina has quit IRC | 18:19 | |
| rkukura | ivar-lazzaro: What do you mean by “ID case”? | 18:19 |
| ivar-lazzaro | rkukura: *IMD | 18:20 |
| rkukura | SumitNaiksatam: I defintely agree we should plan a 2014.2.1 release that fixes anything making 2014.2 unusable | 18:20 |
| ivar-lazzaro | rkukura: I mean that when you have IMD, all the precommit run before the postcommits. But the implicit link still doesn't exist at that time | 18:20 |
| rkukura | IPD? | 18:21 |
| ivar-lazzaro | rkukura: so the RMD will raise an exception before the implicit driver has a chance to create the implicit resource | 18:21 |
| SumitNaiksatam | ivar-lazzaro: by IMD you mean IPD i think ;-) | 18:21 |
| SumitNaiksatam | implicit-policy-driver | 18:21 |
| ivar-lazzaro | rkukura, SumitNaiksatam: that one :D | 18:21 |
| rkukura | ivar-lazzaro: I see what you mean | 18:22 |
| *** jcoufal has quit IRC | 18:22 | |
| rkukura | Maybe IPD needs to create the resources in pre-commit, but that would be within the TX. How about another pre-precommit phase for this? | 18:23 |
| ivar-lazzaro | rkukura: creating the object in the precommit may take too long | 18:23 |
| ivar-lazzaro | rkukura: and the DB lock may expire | 18:23 |
| rkukura | Basically, one phase outside TX for validation and implicit creation, then the precommit phase in the TX, then a the postcommit phase outside | 18:24 |
| ivar-lazzaro | rkukura: one solution could be to make the RMD accept even non linked objects and resolve them only when actually linked | 18:24 |
| rkukura | ivar-lazzaro: I’m suggesting we add a validate phase before the precommit phase | 18:24 |
| rkukura | And this would be before any TX is started | 18:24 |
| ivar-lazzaro | rkukura: how would this solve the problem? | 18:25 |
| *** ChuckC_ has joined #openstack-meeting-3 | 18:25 | |
| ivar-lazzaro | rkukura: the RMD will just raise the exception even earlier | 18:25 |
| rkukura | The IPD would do all its work during the validate phase. | 18:25 |
| ivar-lazzaro | rkukura: the problem is that the IPD should create the reference *before* the RMD validation kicks on | 18:25 |
| *** sbalukoff has joined #openstack-meeting-3 | 18:25 | |
| *** annegent_ has joined #openstack-meeting-3 | 18:26 | |
| rkukura | Each driver’s validate phase would be called in order | 18:26 |
| rkukura | The IPD (if used) would create implicit resources during the validate phase | 18:26 |
| rkukura | The RMD would see they are there when it gets called in the validate phase | 18:26 |
| *** etoews has quit IRC | 18:26 | |
| *** etoews has joined #openstack-meeting-3 | 18:27 | |
| *** melwitt has joined #openstack-meeting-3 | 18:27 | |
| rkukura | The issue I see with this is that there would be side effects if things get rolled back during or after the validate phase | 18:27 |
| ivar-lazzaro | rkukura: you would still need transactions to create the objects right? | 18:27 |
| ivar-lazzaro | rkukura: true | 18:28 |
| *** mattfarina has joined #openstack-meeting-3 | 18:28 | |
| rkukura | ivar-lazzaro: These transactions would be within the create methods of the resources that get implicitly created | 18:28 |
| ivar-lazzaro | the fact that the "initial" object doesn't exist in the DB yet is not a problem? | 18:28 |
| SumitNaiksatam | ivar-lazzaro: is this specifically an issue with regards to the l2p -> l3p association, or there are other places also where this can blow up? | 18:29 |
| rkukura | ivar-lazzaro: I don’t think so - the L3P has no dependency on the L2P for which it is first created | 18:29 |
| *** ChuckC has quit IRC | 18:29 | |
| ivar-lazzaro | SumitNaiksatam: everything that require the link to be in place. Also PTG -> L2P is broken | 18:29 |
| *** VW_ has quit IRC | 18:30 | |
| SumitNaiksatam | ivar-lazzaro: okay | 18:30 |
| ivar-lazzaro | In any case I think this is something we should document for Juno, and maybe that's not a good idea to backport the fix | 18:30 |
| rkukura | I think this issue requires more thought, but seems like something we could address in kilo | 18:30 |
| ivar-lazzaro | rkukura: +1 | 18:30 |
| SumitNaiksatam | ivar-lazzaro: rkukura: agree | 18:30 |
| rkukura | But its probably not something we’d backport to stable/juno | 18:31 |
| rkukura | ivar-lazzaro: +1 | 18:31 |
| SumitNaiksatam | i think we can release note Juno with the requirement for the IPD to be configured | 18:31 |
| rkukura | SumitNaiksatam: +1 | 18:31 |
| *** sergef has quit IRC | 18:31 | |
| SumitNaiksatam | stating the obvious - i think we should get this one fixed sooner, since it affects every critical path, and better to get it done early in the cycle | 18:32 |
| SumitNaiksatam | ivar-lazzaro: thanks for bringing it up for discussion here | 18:32 |
| rkukura | I wonder if we should think about a TaskFlow based approach for kilo in place of the current ML2-like structure, where tasks have ways to undo themselves | 18:32 |
| SumitNaiksatam | rkukura: +1 | 18:33 |
| SumitNaiksatam | that said we have other changes planned as well, so we can’t have too many structural changes in flight at the same time | 18:33 |
| SumitNaiksatam | we can decide which ones are of critical importance and prioritize accordingly | 18:34 |
| SumitNaiksatam | we currntly have a priority of tasks, but we can revisit | 18:34 |
| ivar-lazzaro | russellb: ++ | 18:34 |
| ivar-lazzaro | russellb: ops | 18:34 |
| ivar-lazzaro | rkukura: ++ | 18:34 |
| SumitNaiksatam | rkukura: do you have a feel for how much effort it would take to move to taskflow? | 18:34 |
| rkukura | SumitNaiksatam: I wish I did | 18:34 |
| SumitNaiksatam | resources/time | 18:34 |
| SumitNaiksatam | rkukura: ok | 18:34 |
| SumitNaiksatam | i think we need a fix for this issue one way or the other | 18:35 |
| rkukura | There are WIP patches for incorporating TaskFlow into ML2 - I’ll at least try to understand those by next week | 18:35 |
| SumitNaiksatam | rkukura: okay | 18:35 |
| rkukura | We could probably do something with a validate phase in kilo and TaskFlow in L if necessary | 18:36 |
| SumitNaiksatam | #action rkukura to evaluate and report on the effort to migrate to taskflow | 18:36 |
| rkukura | SumitNaiksatam: OK | 18:36 |
| SumitNaiksatam | ivar-lazzaro: in the meanwhile do you want to evaluate if there is any other workaround for this IPD issue? | 18:36 |
| SumitNaiksatam | or may be you already have | 18:37 |
| ivar-lazzaro | SumitNaiksatam: yup | 18:37 |
| SumitNaiksatam | ivar-lazzaro: rkukura: great | 18:37 |
| SumitNaiksatam | ok any other bugs that we want to discuss (or people having problems with making progress on fixing them)? | 18:37 |
| rkukura | yes | 18:38 |
| SumitNaiksatam | rkukura: go ahead | 18:38 |
| rkukura | The nova preexisting port deleteion fix is close to merging: https://review.openstack.org/#/c/126309/ | 18:39 |
| SumitNaiksatam | rkukura: okay good | 18:39 |
| ivar-lazzaro | rkukura: nice | 18:39 |
| rkukura | Wouldn’t hurt for others to review that | 18:39 |
| SumitNaiksatam | this would still mean that we have to delete the policy targets (and the ports would get deleted at that time), right? | 18:39 |
| rkukura | And we’ll need to think about how it effects us, and whether we want to encourage backporting it to nova’s stable/juno | 18:40 |
| rkukura | We’d probably change the FK to not null on delete | 18:40 |
| SumitNaiksatam | rkukura: ok | 18:41 |
| rkukura | could impact our users though so wanted to mention it | 18:41 |
| SumitNaiksatam | rkukura: okay, you mean since they use the port to spin up the VM? | 18:42 |
| SumitNaiksatam | however, the PT delete will take care of deletion of the port, right? | 18:43 |
| rkukura | SumitNaiksatam: Actually, as long as they expliciltly delete the PT after killing the VM, they’ll be OK | 18:43 |
| SumitNaiksatam | rkukura: yeah | 18:43 |
| rkukura | maybe a false alarm then | 18:43 |
| SumitNaiksatam | so that workflow does not change | 18:43 |
| SumitNaiksatam | good to know though | 18:43 |
| rkukura | OK | 18:43 |
| SumitNaiksatam | okay we need to get to the next topic | 18:43 |
| SumitNaiksatam | #topic Re-factor Group Based Policy with Neutron RESTful APIs | 18:43 |
| *** openstack changes topic to "Re-factor Group Based Policy with Neutron RESTful APIs (Meeting topic: networking_policy)" | 18:43 | |
| SumitNaiksatam | #link https://review.openstack.org/#/c/153126 | 18:44 |
| SumitNaiksatam | yapeng: hi | 18:44 |
| SumitNaiksatam | not sure if yi is around too | 18:44 |
| yapeng | hi, Yi seems offline right now | 18:44 |
| SumitNaiksatam | yapeng: do you want to summarize what approach you are taking? (sorry to put you on the spot) | 18:44 |
| yapeng | sure, Yi and I plan to add neutron RESTful API driver first, then modify resource mapping driver to use neutron RESTful APIs. | 18:46 |
| yapeng | i briefly described it in the spec. | 18:46 |
| SumitNaiksatam | yapeng: i noticed that you mention adding it as a driver | 18:46 |
| SumitNaiksatam | yapeng: i was thinking of this more as a library | 18:46 |
| SumitNaiksatam | perhaps we are thinking the same think, not sure | 18:46 |
| SumitNaiksatam | others please chime in based on your experience so far (those who have worked on the GBP to Neutron integration) | 18:47 |
| yapeng | yes. "library" maybe more accurate. I can make a change in the spec. | 18:47 |
| SumitNaiksatam | yapeng: thanks | 18:47 |
| SumitNaiksatam | yapeng: since for us a neutron driver means something slightly different (its current the resource mapping driver which does that) | 18:48 |
| s3wong | SumitNaiksatam, yapeng: RMD is pretty much the only thing affected here, right? | 18:48 |
| SumitNaiksatam | *currently | 18:48 |
| SumitNaiksatam | s3wong: yes, most likely | 18:48 |
| *** bpokorny has joined #openstack-meeting-3 | 18:48 | |
| rkukura | Is there a need to support both direct calls and REST calls, selectable via config? | 18:48 |
| SumitNaiksatam | we need to get mageshgv’s input here as well | 18:48 |
| SumitNaiksatam | rkukura: good point, i thought about that one | 18:48 |
| yapeng | SumitNaiksatam, yes, make sense to me now. | 18:48 |
| SumitNaiksatam | rkukura: but if we are a separate server, the direct calls will never work | 18:49 |
| yapeng | s3wong: yes, RMD is the only thing to be changed. | 18:49 |
| SumitNaiksatam | rkukura: and direct calls will also assume the same service framework as of neutron, but that may or may not be the case | 18:49 |
| rkukura | SumitNaiksatam: I agree but I’m concerned if we don’t succeed in moving to a separate server in kilo, REST calls could be a problem. | 18:49 |
| SumitNaiksatam | rkukura: i was thinking of the direct calls more of a transistion mechanism | 18:49 |
| s3wong | GBP as independent API endpoint, and DB are two independent tasks related to this direct call to Neutron APIs | 18:49 |
| SumitNaiksatam | rkukura: yes, a transition mechanism to fall back on | 18:50 |
| mageshgv | SumitNaiksatam: REST calls would be mandatory if we want GBP as an independent server | 18:50 |
| SumitNaiksatam | s3wong: yes, this is the first step | 18:50 |
| *** carl_baldwin has quit IRC | 18:50 | |
| s3wong | rkukura: why would the REST call be a problem? because we can't make a REST call to ourselves? | 18:50 |
| rkukura | If we are commiting to separate server for kilo, then I’m happy with just switching to REST client calls and not adding any additional complexity | 18:50 |
| SumitNaiksatam | mageshgv: i was asking also from the service chain driver impl perspective | 18:51 |
| *** bpokorny_ has quit IRC | 18:51 | |
| rkukura | REST calls to the same server going out through a loadbalancer and back could be a problem | 18:51 |
| ivar-lazzaro | Do we need to support also calls from Neutron to GBP? That's something that could be useful in the ML2 drivers that some of the vendor plugins have implemented for GBP | 18:51 |
| SumitNaiksatam | rkukura: but i think i agree with you that it might be a good option to have handy | 18:51 |
| yapeng | SumitNaiksatam, is the seperate server chanage targeted for k-1? | 18:51 |
| SumitNaiksatam | yapeng: the evaluation of the separate server is definitely targeted for k-1, and perhaps more | 18:52 |
| SumitNaiksatam | yapeng: but that work has a dependency on what you are doing | 18:52 |
| s3wong | SumitNaiksatam, rkukura: I see that GBP as independent API server (to pecan) as a K-1 milestone item? | 18:52 |
| *** bpokorny has quit IRC | 18:52 | |
| SumitNaiksatam | s3wong: that is a proposal | 18:52 |
| rkukura | Isn’t our K-1 in a week? | 18:52 |
| SumitNaiksatam | s3wong: may or may not be pecan right away | 18:52 |
| mageshgv | SumitNaiksatam: The service chain plugin also could reuse this new framework wherever needed. | 18:52 |
| SumitNaiksatam | rkukura: true :-) | 18:53 |
| SumitNaiksatam | 10 days to be precise | 18:53 |
| rkukura | It might be realistic to get the REST calls in K-1, but I think the pecan-based server will take more time | 18:53 |
| s3wong | mageshgv: actually for service chain it is interesting. Service chain is a Neutron service plugin, right? | 18:53 |
| SumitNaiksatam | rkukura: yes | 18:53 |
| yapeng | ivar-lazzaro: yes, some ML2 driver will need to call GBP APIs. | 18:54 |
| SumitNaiksatam | s3wong: so is GBP | 18:54 |
| s3wong | mageshgv: and this GBP API server task would not change service chain's position, i.e., it would remain Neutron service plugin, right? | 18:54 |
| SumitNaiksatam | rkukura: but independent server need not be pecan-based from day one | 18:54 |
| *** alexsyip has joined #openstack-meeting-3 | 18:54 | |
| SumitNaiksatam | we can have a transition path there as well | 18:54 |
| yapeng | SumitNaiksatam, rkukura, s3wong, do you see a problem that ML2 driver calls GBP APIs? | 18:54 |
| rkukura | SumitNaiksatam: True, but why not go straight to pecan? | 18:54 |
| mageshgv | s3wong, SumitNaiksatam: I assume when we have an independent server, the service chain plugin also would follow suit. Please correct me if you think otherwise | 18:55 |
| rkukura | yapeng: I don’t see an issue for ML2 driver to call GBP via its REST client, as long as they are separate servers | 18:55 |
| s3wong | yapeng: not really, other than having your ML2 drive dependent on GBP | 18:55 |
| s3wong | mageshgv: I actually don't know --- hence asking :-) | 18:56 |
| SumitNaiksatam | rkukura: we might want to enable some of the other work to go in parallel that might need the indepedent server to be in place | 18:56 |
| yapeng | rkukura, if this is the case, we need GBP server changes at the same time, right? | 18:56 |
| s3wong | mageshgv: the idea would be invoking service chain would still be Neutron APIs | 18:56 |
| SumitNaiksatam | so based on the discussion here, my suggestion is that we try to design this in a way that rkukura suggested earlier | 18:57 |
| *** sarob has quit IRC | 18:57 | |
| *** mattfarina has quit IRC | 18:57 | |
| rkukura | I think REST client calls in either or both directions within the same server should be OK for the interim | 18:57 |
| SumitNaiksatam | that is both REST and internal API call options are available (and config driven) | 18:57 |
| s3wong | mageshgv: thus allowing yapeng and yi to uniformly migrate RMD from direct call to the new library calls | 18:57 |
| *** sarob has joined #openstack-meeting-3 | 18:57 | |
| *** mwagner_lap has joined #openstack-meeting-3 | 18:57 | |
| rkukura | SumitNaiksatam: That’s probably safest, but maybe not necessary | 18:57 |
| SumitNaiksatam | rkukura: ok | 18:57 |
| SumitNaiksatam | lets comment on the spec in that case | 18:57 |
| rkukura | OK | 18:58 |
| SumitNaiksatam | also to ivar-lazzaro’s point, lets include the part about the calls from the ML2 drivers to GBP also in the spec | 18:58 |
| yapeng | SumitNaiksatam, rkukura, sure, I will check the gerrit review. | 18:58 |
| *** ybathia has quit IRC | 18:58 | |
| SumitNaiksatam | we have one minute left | 18:59 |
| SumitNaiksatam | there was one more topic on the agenda | 18:59 |
| SumitNaiksatam | but i think we will have to skip it for this meeting | 18:59 |
| SumitNaiksatam | #topic Open Discussion | 18:59 |
| *** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)" | 18:59 | |
| SumitNaiksatam | mageshgv: you have been working on the floating IP support design and impl | 18:59 |
| SumitNaiksatam | hopefully you can provide an update in the next meeting | 18:59 |
| s3wong | Deadline for conference session proposal for L-Summit is next Monday | 18:59 |
| SumitNaiksatam | meanwhile lets keeping it going on the emails | 19:00 |
| mageshgv | SumitNaiksatam: yes, sure | 19:00 |
| SumitNaiksatam | and please review | 19:00 |
| SumitNaiksatam | okay we are out of time | 19:00 |
| SumitNaiksatam | thanks all for joining | 19:00 |
| SumitNaiksatam | bye | 19:00 |
| s3wong | bye | 19:00 |
| mageshgv | bye | 19:00 |
| rkukura | that was quick | 19:00 |
| banix | bye | 19:00 |
| yapeng | bye | 19:00 |
| rkukura | bye | 19:00 |
| SumitNaiksatam | #endmeeting | 19:00 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 19:00 | |
| openstack | Meeting ended Thu Feb 5 19:00:37 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 19:00 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-02-05-18.08.html | 19:00 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-02-05-18.08.txt | 19:00 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-02-05-18.08.log.html | 19:00 |
| *** sbalukoff has quit IRC | 19:00 | |
| SumitNaiksatam | sorry for ending quickly | 19:00 |
| ivar-lazzaro | bye | 19:01 |
| rkukura | SumitNaiksatam: I hadn’t looked at the time and figured we were half done | 19:01 |
| SumitNaiksatam | the hour flew past (and we started a little late today) | 19:01 |
| SumitNaiksatam | rkukura: yes, my bad, we lost about 6 mins in the beginning | 19:01 |
| SumitNaiksatam | since i was not on time | 19:01 |
| *** Networkn3rd has joined #openstack-meeting-3 | 19:01 | |
| *** mattfarina has joined #openstack-meeting-3 | 19:01 | |
| s3wong | SumitNaiksatam: as I said above, deadline for proposal for conference session for L-Summit is next Monday | 19:02 |
| s3wong | SumitNaiksatam: hopefully you guys have talk proposals already | 19:02 |
| *** mageshgv has quit IRC | 19:04 | |
| *** susaant has quit IRC | 19:05 | |
| *** pkoniszewski has joined #openstack-meeting-3 | 19:10 | |
| *** huichun has joined #openstack-meeting-3 | 19:12 | |
| *** huichun has left #openstack-meeting-3 | 19:12 | |
| *** sbalukoff has joined #openstack-meeting-3 | 19:13 | |
| *** ChuckC has joined #openstack-meeting-3 | 19:13 | |
| *** baoli has quit IRC | 19:14 | |
| *** VW_ has joined #openstack-meeting-3 | 19:14 | |
| *** thangp has joined #openstack-meeting-3 | 19:14 | |
| *** ChuckC_ has quit IRC | 19:17 | |
| *** LouisF has quit IRC | 19:19 | |
| *** jpomero has quit IRC | 19:20 | |
| *** s3wong has quit IRC | 19:20 | |
| *** devvesa has quit IRC | 19:21 | |
| *** s3wong has joined #openstack-meeting-3 | 19:22 | |
| *** safchain has quit IRC | 19:30 | |
| *** sarob_ has joined #openstack-meeting-3 | 19:31 | |
| *** sarob has quit IRC | 19:32 | |
| *** [1]evgenyf has joined #openstack-meeting-3 | 19:33 | |
| *** Sukhdev has joined #openstack-meeting-3 | 19:40 | |
| *** sarob_ is now known as sarob | 19:43 | |
| *** [1]evgenyf has quit IRC | 19:53 | |
| *** sarob has quit IRC | 19:55 | |
| *** sarob has joined #openstack-meeting-3 | 19:57 | |
| *** thangp has quit IRC | 19:57 | |
| *** sarob has quit IRC | 20:02 | |
| *** sarob has joined #openstack-meeting-3 | 20:02 | |
| *** ttrifonov is now known as zz_ttrifonov | 20:02 | |
| *** megm has joined #openstack-meeting-3 | 20:14 | |
| *** sigmavirus24 is now known as sigmavirus24_awa | 20:21 | |
| *** Youcef has quit IRC | 20:25 | |
| *** bpokorny has joined #openstack-meeting-3 | 20:33 | |
| *** qwebirc83652 has joined #openstack-meeting-3 | 20:34 | |
| *** mrda-away is now known as mrda | 20:35 | |
| *** qwebirc83652 has left #openstack-meeting-3 | 20:35 | |
| *** matrohon has joined #openstack-meeting-3 | 20:43 | |
| *** wojdev has joined #openstack-meeting-3 | 20:48 | |
| *** carl_baldwin has joined #openstack-meeting-3 | 20:52 | |
| *** annegent_ has quit IRC | 20:55 | |
| *** nickchase has joined #openstack-meeting-3 | 20:59 | |
| mattgriffin | hello HA Guide update team! | 21:00 |
| megm | Hi, Matt! | 21:00 |
| nickchase | Hello, mattgriffin! | 21:00 |
| nickchase | hey, megm | 21:00 |
| megm | Hi, Nick! | 21:00 |
| mattgriffin | megm, nickchase - hello... is clouddon around? | 21:01 |
| mattgriffin | doesn't look like it | 21:01 |
| *** annegent_ has joined #openstack-meeting-3 | 21:02 | |
| mattgriffin | pinging him on google | 21:02 |
| *** vmorris has joined #openstack-meeting-3 | 21:03 | |
| mattgriffin | hello vmorris | 21:03 |
| vmorris | Hey matt | 21:03 |
| mattgriffin | no reply from clouddon | 21:03 |
| *** tahirs has joined #openstack-meeting-3 | 21:03 | |
| mattgriffin | have one main thing on the agenda for today - clouddon | 21:04 |
| mattgriffin | wrong paste - https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update#Next_Meeting | 21:04 |
| tahirs | hi all (sorry for being late.... and now this interruption) =) | 21:04 |
| *** tahirs is now known as Shamail | 21:04 | |
| mattgriffin | nickchase, do you know how to use all of the irc commands for meetings? | 21:04 |
| mattgriffin | hey Shamail | 21:04 |
| Shamail | hi mattgriffin | 21:05 |
| nickchase | I am looking for the instructions, please hang on | 21:06 |
| nickchase | #startmeeting | 21:06 |
| mattgriffin | :) cool | 21:06 |
| openstack | nickchase: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee' | 21:06 |
| nickchase | #startmeeting HA Guide | 21:06 |
| openstack | Meeting started Thu Feb 5 21:06:23 2015 UTC and is due to finish in 60 minutes. The chair is nickchase. Information about MeetBot at http://wiki.debian.org/MeetBot. | 21:06 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 21:06 |
| *** openstack changes topic to " (Meeting topic: HA Guide)" | 21:06 | |
| openstack | The meeting name has been set to 'ha_guide' | 21:06 |
| nickchase | That was easy. :) | 21:06 |
| mattgriffin | excellent! | 21:06 |
| vmorris | #agreed | 21:07 |
| mattgriffin | :) | 21:07 |
| mattgriffin | i think there are a few things to bring up this week... | 21:07 |
| *** megm has quit IRC | 21:08 | |
| mattgriffin | 1. continue to look for bugs. here's some useful tips - https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update#Bug_Bash | 21:08 |
| mattgriffin | i see the Docs team doing some triaging and tagging | 21:08 |
| mattgriffin | 2. content structure changes | 21:09 |
| nickchase | Mirantis people have been going through as well. | 21:09 |
| mattgriffin | nickchase, cool | 21:09 |
| nickchase | So on structure: | 21:09 |
| nickchase | megm and I were talking about the install guide issue | 21:09 |
| nickchase | and we were thinking that perhaps it would be best if we did the following: | 21:09 |
| *** megm has joined #openstack-meeting-3 | 21:10 | |
| *** mrmartin has quit IRC | 21:10 | |
| nickchase | In the HA Guide, we start with... | 21:10 |
| nickchase | a general overview of the install steps, with a link to where to get more information, and a note about any steps that require special treatment for HA (with a link to that section of the guide). | 21:10 |
| nickchase | That sets the context. Then ... | 21:10 |
| *** erikmwilson has quit IRC | 21:11 | |
| nickchase | In the install guide, any places where HA makes a difference, we make a note and link them back to the HA Guide. | 21:11 |
| Shamail | nickchase: +1, I like the idea since both documents are no longer stand-alone docs that users have to find/parse individually. | 21:11 |
| mattgriffin | makes sense to me | 21:11 |
| Shamail | plus it would be bad to find conflicting information (or missing steps in install that prevent HA later), etc | 21:12 |
| nickchase | right. | 21:12 |
| mattgriffin | no need to repeat info and maintain it | 21:12 |
| megm | Yes, they need tobe intertwined... | 21:12 |
| megm | +1, matt! | 21:12 |
| nickchase | but this enables us to decouple them as much as possible. | 21:12 |
| nickchase | (but no more :)) | 21:12 |
| mattgriffin | shall we put it to an official meetbot vote? i think we should run this by the docs team though | 21:14 |
| megm | What about information about how to manage HA after initial configuration? | 21:14 |
| megm | e.g. I have HA configured, a server crashed, how do I replace it, etc? | 21:14 |
| nickchase | So an HA operations section | 21:15 |
| nickchase | I think that would be good to have | 21:15 |
| nickchase | but as far as voting or running by the docs team... | 21:15 |
| Shamail | I had proposed that as a change to include "recovery" information (e.g. how do I get my availability or operations back to my desired availability/performance) | 21:15 |
| megm | But does it go in HA Guide or does HA Guide point to other guides? | 21:16 |
| nickchase | I think that we should just make a decision here -- does anybody object? -- and then provide a summary set of minutes to the list as a decision people can dispute if they want to. I don't think they will. | 21:16 |
| *** matrohon has quit IRC | 21:16 | |
| Shamail | I think that it might be a nice to have since it is subject to qualitative guidelines or best practice recommendations. | 21:16 |
| Shamail | mattgriffin: thoughts? | 21:16 |
| nickchase | I think that recovery information is definitely crucial. | 21:16 |
| *** matrohon has joined #openstack-meeting-3 | 21:17 | |
| mattgriffin | Shamail, nickchase yes. i wonder how much is included in the Ops Guide though | 21:17 |
| nickchase | Whether it goes here or in the Operations Guide... that's a differen tquestion | 21:17 |
| nickchase | :) | 21:17 |
| Shamail | mattgriffin: should I take the action item to parse through Ops guide? | 21:17 |
| nickchase | So we need to find out. | 21:17 |
| mattgriffin | Shamail, that would be great | 21:17 |
| *** eghobo has joined #openstack-meeting-3 | 21:17 | |
| nickchase | #action Shamail Parse Ops guide for recovery information. | 21:17 |
| Shamail | alright, I'll take the first stab and report back to the team. | 21:18 |
| nickchase | (Not sure why an action item wasn't generated.) | 21:18 |
| nickchase | But mattgriffin, are you taking notes for minutes or should I? | 21:18 |
| mattgriffin | nickchase, hadn't started so please do | 21:19 |
| nickchase | k | 21:19 |
| Shamail | I think the bot should handle it since we formally started the meeting but good backup plan nonetheless. | 21:20 |
| *** sergef has joined #openstack-meeting-3 | 21:20 | |
| nickchase | The bot will do the log. I'm talking about a simplified version to post to the openstack-docs list. | 21:21 |
| *** baoli has joined #openstack-meeting-3 | 21:21 | |
| Shamail | oh, I get it. Sorry! | 21:21 |
| mattgriffin | nickchase, you'll run with outlining the structure approach and sending to the list? | 21:22 |
| nickchase | yes. | 21:22 |
| mattgriffin | cool. thank you | 21:22 |
| nickchase | or I can send it to you and you can send it to the list. either way. | 21:23 |
| mattgriffin | nah. go for it | 21:23 |
| nickchase | :) NP | 21:23 |
| vmorris | is there a place to request access to the mailing list or just let you know my address? | 21:23 |
| nickchase | #link http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs | 21:23 |
| vmorris | ty | 21:24 |
| nickchase | OK, so what's next, mattgriffin? | 21:24 |
| *** baoli has quit IRC | 21:24 | |
| *** banix has quit IRC | 21:24 | |
| Shamail | We are using [ha-guide] for our prefix in the same ML right? | 21:24 |
| *** banix has joined #openstack-meeting-3 | 21:24 | |
| mattgriffin | nickchase, as an action item, should we start to map out the points to cross guides? | 21:24 |
| *** baoli has joined #openstack-meeting-3 | 21:24 | |
| nickchase | shamail yes | 21:25 |
| nickchase | mattgriffin yes, I think we need to do that. At the very least.... | 21:25 |
| nickchase | we need the basic install guide steps | 21:25 |
| nickchase | any volunteers...? | 21:25 |
| Shamail | Unfortunately, I don't want to over-commit. I can help with this (if it's not done) after going through Ops Guide | 21:26 |
| nickchase | I think we can set it as a "to do" | 21:27 |
| mattgriffin | nickchase, yes. i wonder if that list isn't captured in the http://docs.openstack.org/juno/install-guide/install/apt/content/ | 21:27 |
| nickchase | It may be. I suppose the question may be... | 21:28 |
| nickchase | the granularity. I mean, we could have "Install Keystone" as a step. :) | 21:28 |
| mattgriffin | ack | 21:28 |
| nickchase | Yeah, I think maybe a bit TOO chunky. :) | 21:28 |
| mattgriffin | i can take that action item | 21:29 |
| nickchase | great. | 21:29 |
| mattgriffin | i'll just be using an etherpad so i'll email [ha-guide] with the link to contribute, follow along, criticize :) | 21:29 |
| nickchase | #action mattgriffin Define install steps in an etherpad. | 21:30 |
| nickchase | :) | 21:30 |
| mattgriffin | cool. i think that's the agenda | 21:30 |
| mattgriffin | if there isn't anything else to cover, then i think we can end this meeting | 21:30 |
| nickchase | Just to note that we still need to restructure the overall TOC. | 21:30 |
| mattgriffin | ack | 21:31 |
| nickchase | maybe after the install step? | 21:31 |
| mattgriffin | yeah. let's do that | 21:31 |
| nickchase | ok, so let's keep it on the agenda | 21:31 |
| megm | And the introductory material is good but it needs to go a little farther. | 21:31 |
| mattgriffin | great | 21:32 |
| mattgriffin | end meeting? | 21:32 |
| mattgriffin | #endmeeting | 21:32 |
| megm | bye | 21:32 |
| nickchase | thanks, all! | 21:32 |
| vmorris | thanks, bye | 21:32 |
| mattgriffin | nickchase, i think you have to do that | 21:32 |
| mattgriffin | since you started the meting | 21:32 |
| *** vmorris has quit IRC | 21:33 | |
| *** absubram has left #openstack-meeting-3 | 21:39 | |
| *** matrohon has quit IRC | 21:40 | |
| *** Sukhdev has quit IRC | 21:40 | |
| *** SridharRamaswam1 has quit IRC | 21:45 | |
| *** Piet has quit IRC | 21:46 | |
| *** jmankov has joined #openstack-meeting-3 | 21:49 | |
| *** jmanko has quit IRC | 21:51 | |
| *** dhellmann_ has joined #openstack-meeting-3 | 21:51 | |
| *** banix has quit IRC | 21:53 | |
| *** pkoniszewski has quit IRC | 21:53 | |
| *** Rockyg has joined #openstack-meeting-3 | 21:54 | |
| *** Shamail has quit IRC | 21:54 | |
| *** MaxV has joined #openstack-meeting-3 | 21:55 | |
| *** dhellmann_ has quit IRC | 21:55 | |
| *** s3wong has quit IRC | 21:56 | |
| *** s3wong has joined #openstack-meeting-3 | 21:57 | |
| *** dhellmann_ has joined #openstack-meeting-3 | 21:57 | |
| *** VW__ has joined #openstack-meeting-3 | 21:58 | |
| *** dhellmann_ has quit IRC | 21:58 | |
| *** MaxV has quit IRC | 22:00 | |
| *** etoews_ has joined #openstack-meeting-3 | 22:01 | |
| *** VW_ has quit IRC | 22:01 | |
| *** etoews has quit IRC | 22:02 | |
| *** mattfarina has quit IRC | 22:02 | |
| *** dhellmann_ has joined #openstack-meeting-3 | 22:03 | |
| *** jaypipes has quit IRC | 22:04 | |
| *** VW_ has joined #openstack-meeting-3 | 22:05 | |
| *** dhellmann_ has quit IRC | 22:08 | |
| *** sergef has quit IRC | 22:08 | |
| *** VW__ has quit IRC | 22:08 | |
| *** lblanchard has quit IRC | 22:11 | |
| *** dhellmann_ has joined #openstack-meeting-3 | 22:20 | |
| *** VW_ has quit IRC | 22:21 | |
| *** rkukura has left #openstack-meeting-3 | 22:24 | |
| *** salv-orlando has quit IRC | 22:25 | |
| *** salv-orlando has joined #openstack-meeting-3 | 22:30 | |
| *** VW_ has joined #openstack-meeting-3 | 22:34 | |
| *** s3wong has quit IRC | 22:37 | |
| *** gholler has quit IRC | 22:38 | |
| *** eghobo has quit IRC | 22:38 | |
| *** eghobo has joined #openstack-meeting-3 | 22:41 | |
| *** banix has joined #openstack-meeting-3 | 22:46 | |
| *** banix has quit IRC | 22:47 | |
| *** pjnaik1990 has joined #openstack-meeting-3 | 22:48 | |
| pjnaik1990 | Hi, I am new to openstack. I liked the idea of Congress project and would like to contribute to it. Could anybody suggest me few ideas/modules in congress project where I could work for a span of 2-3 months? | 22:51 |
| *** annegent_ has quit IRC | 22:55 | |
| *** ybathia has joined #openstack-meeting-3 | 22:57 | |
| *** Networkn3rd has quit IRC | 22:57 | |
| *** VW__ has joined #openstack-meeting-3 | 23:01 | |
| *** VW_ has quit IRC | 23:03 | |
| *** wojdev has quit IRC | 23:06 | |
| *** banix has joined #openstack-meeting-3 | 23:07 | |
| *** VW__ has quit IRC | 23:10 | |
| *** sarob has quit IRC | 23:11 | |
| *** Rockyg has quit IRC | 23:16 | |
| *** jckasper_ has quit IRC | 23:17 | |
| *** SridharRamaswamy has joined #openstack-meeting-3 | 23:17 | |
| *** SridharRamaswam1 has joined #openstack-meeting-3 | 23:22 | |
| *** VW_ has joined #openstack-meeting-3 | 23:22 | |
| *** SridharRamaswamy has quit IRC | 23:22 | |
| *** alexpilotti has quit IRC | 23:25 | |
| *** hemanthravi has quit IRC | 23:28 | |
| fungi | #endmeeting | 23:31 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 23:31 | |
| openstack | Meeting ended Thu Feb 5 23:31:15 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 23:31 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/ha_guide/2015/ha_guide.2015-02-05-21.06.html | 23:31 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/ha_guide/2015/ha_guide.2015-02-05-21.06.txt | 23:31 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/ha_guide/2015/ha_guide.2015-02-05-21.06.log.html | 23:31 |
| fungi | pjnaik1990: you might want to ask that question on the http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev mailing list | 23:32 |
| *** annegent_ has joined #openstack-meeting-3 | 23:35 | |
| *** VW_ has quit IRC | 23:39 | |
| *** banix has quit IRC | 23:39 | |
| *** VW_ has joined #openstack-meeting-3 | 23:40 | |
| *** annegent_ has quit IRC | 23:41 | |
| *** VW_ has quit IRC | 23:41 | |
| *** david-lyle is now known as david-lyle_afk | 23:41 | |
| *** jmanko has joined #openstack-meeting-3 | 23:43 | |
| *** baoli has quit IRC | 23:46 | |
| *** jmankov has quit IRC | 23:46 | |
| *** Sukhdev has joined #openstack-meeting-3 | 23:47 | |
| *** banix has joined #openstack-meeting-3 | 23:47 | |
| *** etoews_ has quit IRC | 23:49 | |
| *** Piet has joined #openstack-meeting-3 | 23:50 | |
| *** carl_baldwin has quit IRC | 23:51 | |
| *** sbalukoff has quit IRC | 23:53 | |
| *** openstack has joined #openstack-meeting-3 | 23:56 | |
| *** ChanServ sets mode: +o openstack | 23:56 | |
| *** carl_baldwin has joined #openstack-meeting-3 | 23:58 | |
| *** Sukhdev has quit IRC | 23:58 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!