22:01:41 <danwent> #startmeeting
22:01:41 <rkukura> o/
22:01:42 <openstack> Meeting started Tue May 22 22:01:41 2012 UTC.  The chair is danwent. Information about MeetBot at http://wiki.debian.org/MeetBot.
22:01:43 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
22:01:43 <marktvoelker> o/
22:01:44 * mtaylor wastes time
22:01:46 <garyk> hi
22:01:52 <danwent> mtaylor: damn you!
22:02:03 <salv-orlando> hi
22:02:08 <danwent> hi folks
22:02:14 <gongys> hi
22:02:17 <danwent> #link agenda: http://wiki.openstack.org/Network/Meetings
22:02:19 <danwent> hi gongys
22:02:24 <mestery> o/
22:02:27 <SumitNaiksatam> Hi All!
22:02:31 <danwent> gongys: what time is it for you?
22:02:41 <gongys> 6:00 in the morning
22:02:50 <danwent> yikes… appreciate you making the meeting :)
22:03:00 <gongys> Yes. not easy.
22:03:04 <danwent> between you and garyk, maybe we should be consider a new time.
22:03:12 <danwent> its not easy for salv-orlando either
22:03:14 <garyk> +1
22:03:28 <danwent> ok, let's bring it up during open discussion
22:03:56 <danwent> #topic F-1 Release
22:04:20 <danwent> branchpoint will be tonight.  anything other than important bug fixes should be in by tonight.
22:04:22 <danwent> https://launchpad.net/quantum/+milestone/folsom-1
22:04:56 <danwent> any critical bug fixes found between now and release on thurs should be pushed to master, then send me a note and I can pull them to the milestone proposed branch
22:05:00 <danwent> jkoelker: here?
22:05:11 <danwent> _cerberus_: ?
22:05:29 <danwent> big update is that we're not going to try and push v2 API code in F-1
22:05:32 <_cerberus_> What's it worth to you?
22:05:57 <danwent> there's been a lots of good progress, but there's still some more work to be done, and I want to make sure folks have ample time to review
22:06:09 <danwent> _cerberus_: I think plan is to get a spec of sorts out quickly for feedback though?
22:06:22 <_cerberus_> Yes
22:06:29 <danwent> as many items in F-2 require people to start writing code against the v2 API
22:06:32 <SumitNaiksatam> is there a github repo that we call look at in the interim?
22:06:45 <danwent> SumitNaiksatam: yes
22:06:45 <SumitNaiksatam> for the v2 API that is
22:06:58 <danwent> jkoelker has a branch
22:07:00 <danwent> one sec
22:07:05 <danwent> I think its linked from BP
22:07:24 <danwent> yeah, at bottom of BP
22:07:27 <SumitNaiksatam> oh ok
22:07:28 <danwent> https://github.com/jkoelker/quantum/tree/melange
22:07:32 <SumitNaiksatam> I did not notice it
22:07:34 <SumitNaiksatam> thanks!
22:07:41 <danwent> jkoelker is sly like that :P
22:08:12 <SumitNaiksatam> or I was lazy to scroll :-)
22:08:12 <garyk> silly question: is the nova code also being taken care of? this may also take time to get through
22:08:21 <gongys> is this one: https://github.com/jkoelker/quantum/tree/melange
22:08:30 <danwent> garyk: which nova code?
22:08:35 <danwent> gongys: yup
22:08:43 <garyk> nova/network/...
22:09:14 <danwent> garyk: I guess i'm not sure what you mean by "being taken care of"… do you mean maintained?  most of the quantum manager code will go away in Folsom
22:09:43 <danwent> tr3buchet has a BP in F-2 to rework nova code to work with new v2 API (and some other cool changes, like eliminating nova-network)
22:09:49 <danwent> at least when running with quantum
22:09:58 <garyk> ok, that makes sense
22:10:03 <jkoelker> https://github.com/jkoelker/quantum/compare/openstack:master...melange that's the current diff with trunk so far
22:10:17 <jkoelker> i havn't merged trunk though in a few days, so it might be behind a bit
22:10:21 <danwent> here's link to tr3buchet's work : https://blueprints.launchpad.net/quantum/+spec/improved-nova-quantum-integration
22:10:31 <danwent> jkoelker: thanks
22:10:40 <salv-orlando> does the v2 api amounts to quantum + melange or is there something new as well? Just asking, not been following closely lately.
22:10:59 <danwent> salv-orlando: trying to keep it very simple… I think its actually less than quantum + melange
22:11:06 <danwent> a lot of the other stuff will be extensions in this version
22:11:19 <salv-orlando> got it
22:11:21 <danwent> including a lot of the stuff for nova parity
22:11:35 <danwent> its hard enough just focusing on the simple things :)
22:12:04 <danwent> Ok, any other F-1 topics that we need to discuss?
22:12:09 <gongys> So We still need an standalone melange in the folsom?
22:12:41 <danwent> gongys: no, not once the v2 API is complete and the corresponding back-ends have been completed.
22:13:00 <gongys> ok
22:13:10 <danwent> two reviews that are currently targeted for F-1:
22:13:11 <danwent> https://review.openstack.org/#/c/7336/
22:13:28 <danwent> gongys: looks like this just needs a bit of pep-8 love?
22:13:52 <danwent> would be good to get another core approval on this one-liner: https://review.openstack.org/#/c/7685/
22:14:09 <danwent> and I need to refresh the following review to incorporate feedback: https://review.openstack.org/#/c/7460/
22:14:09 <salv-orlando> (and the reviewer new specs for missing it :))
22:14:52 <danwent> that last branch is not really needed for F-1, its more about laying groundwork for things in F-2, so I'm fine with it not going in F-1
22:15:19 <danwent> ok, any other issues people are tracking for F-1?
22:15:23 <gongys> About 7685.ok.  I will do it as soon as possible after this meeting.
22:15:43 <danwent> gongys: great, thanks.
22:16:22 <danwent> Ok, hopefully F-1 will wrap up without too much drama, as we really need to focus on F-2… there's a lot of essential stuff there, with a lot of interdependencies
22:16:43 <danwent> F-2 is due start of July
22:16:53 <danwent> so really just over a month away...
22:17:26 <danwent> and that is our target for demonstrating nova-parity with the new v2 API.
22:17:38 <danwent> #topic community topics
22:18:10 <danwent> just wanted to put out a "help wanted" ad for people to work on developer docs (thanks to garyk for getting things kicked off).
22:18:45 <marktvoelker> #help danwent
22:18:52 <danwent> also, if someone out there is interested in helping me maintain an essex-stable branch, let me know, as there's definitely a set of fixes from F-1 that we'll want to backport
22:19:11 <danwent> marktvoelker: that's a tag?  never knew :)
22:19:14 <salv-orlando> danwent: this means adding security groups, floating ips, and all the other network-related bits of the OS api on the Quantum API?
22:19:34 <danwent> salv-orlando:  yes, though as extensions.
22:20:02 <salv-orlando> please send Dan as many amphetamins as you can
22:20:09 <marktvoelker> danwent: Yep, just learned that in the last meeting =)
22:20:13 <salv-orlando> he is not going to sleep for the next month.
22:20:28 <danwent> salv-orlando: haha… yeah, my wife will love that :)
22:20:49 <danwent> ok, also wanted to draw attention to ttx's comments about Bug Triage day: https://lists.launchpad.net/openstack/msg12040.html and http://wiki.openstack.org/BugTriage
22:21:15 <danwent> I think they are talking about doing this on June 7th
22:21:38 <danwent> goal is to clean up our bug tracker, identifying real issues, classifying them, and getting rid of the rest.
22:21:53 <danwent> and final topic: meeting time
22:22:25 <danwent> so there are two things that aren't great about our current meeting time.  Its very inconvenient for some people salv-orlando, garyk, gongys, at least.
22:22:31 <garyk> can me move it a few hours forward or backswards it is 1:22 here
22:22:49 <danwent> and also, its right after the main meeting, so I don't have fresh info to report during the main openstack meeting.
22:23:34 <danwent> does anyone know where the irc channel calendar is?  I think openstack-meeting is booked a lot of tuesday, but perhaps we could meet on a quantum-dev channel or something?
22:24:09 <danwent> do people that attend this meeting have conflicts earlier in the day on tuesday?
22:24:12 * marktvoelker digs for that link
22:24:30 <danwent> http://wiki.openstack.org/Meetings
22:24:30 <rkukura> if I do, they can be rescheduled
22:24:39 * marktvoelker would favor earlier in the day
22:24:49 <edgarmagana> danwent: I am fine earlier
22:25:12 <rkukura> seems we'd need to be at least 6 or 7 hours earlier for gongys
22:25:16 <danwent> Ok, I will send out a propsed time change to early tuesday to the netstack and main openstack lists.
22:25:22 <salv-orlando> If u want to keep tuesday 17UTC sound reasonable for US and EU
22:25:24 <gongys> now is 6:30 Wed.
22:25:25 <marktvoelker> http://wiki.openstack.org/Meetings
22:25:27 <danwent> rkukura: good point.
22:25:32 <marktvoelker> See iCal link there
22:25:42 <danwent> I think this is the problem we always get to with scheduling these meetings….
22:25:56 <danwent> often people propose to alternate, but alternately weekly seems tough.
22:26:42 <danwent> gongys: do you have a preference between late and night vs. early in morning?
22:27:15 <gongys> now is good time for me.
22:27:15 <danwent> gongys: it seems like no US time will be good for you, is that right?
22:27:40 <danwent> gongys: ok.
22:27:57 <salv-orlando> is garyk the only in eastern EU tz?
22:28:03 <gongys> I mean current scheduling is fine with me.
22:28:23 <gongys> one hour earlier will be also ok for me.
22:28:29 <danwent> ok, well, I will start a thread about this on nestack with some options.  having a time that works across the world clearly isn't feasible.
22:28:36 <gongys> that will help garyk. I think
22:28:49 <garyk> :)
22:28:54 <danwent> gongys: unfortunately, one hour earlier is openstack meeting on tuesday, though we could switch to monday .
22:29:41 <garyk> monday is better for me - i am fine with the middle of the night on a monday
22:29:52 <gongys> Yes, we can switch our meeting to wed,  11 hours after main meeting.
22:29:57 <danwent> garyk: ok, so an hour earlier and a day earlier?
22:30:05 <salv-orlando> +1
22:30:13 <garyk> +1
22:30:28 <danwent> mmm.  that might conflict with doc team.
22:30:42 <danwent> would that be 2000 UTC?
22:30:49 <salv-orlando> 21UTC
22:31:13 <gongys> Wed 21 UTC?
22:31:20 <danwent> ok, there's a nova-subteam meeting at that point.  but perhaps we could us another channel.  I'll also check with vish to make sure that is active
22:31:33 <danwent> gongys: I'd prefer to do it before the main openstack meeting if possible.
22:31:48 <gongys> ok.
22:31:58 <gongys> Mon 21 UTC?
22:32:33 <danwent> gongys: Ok, let's have Mon 21 UTC as an option, possibly doing that on another channel if needed?
22:32:47 <danwent> is that at least a better option for people?
22:33:08 <garyk> works for me
22:33:10 <rkukura> works fine for me
22:33:11 <gongys> 21 UTC if fine with me  on any day.
22:33:15 <edgarmagana> 21UCT is 12:00 PST?
22:33:32 <danwent> Ok, send me email soon if you have concerns with this timeslot.
22:34:16 <danwent> #todo #danwent revise meeting time to be 21 UTC on monday.
22:34:26 <danwent> edgarmagana: no, its same time as main openstack meeting, I believe
22:34:33 <danwent> so 2pm pacific
22:34:51 <soren> No.
22:34:55 <soren> Uh.
22:34:56 <soren> Sorry.
22:34:58 <soren> Yes.
22:35:12 <danwent> i'm just going by this: http://wiki.openstack.org/Meetings
22:35:18 <danwent> i'm terrible at timezone calculations :)
22:35:33 <marktvoelker> 21 utc = 2pdt = 1 pst
22:35:37 <soren> PDT is 7 hours behind UTC.
22:35:53 <edgarmagana> danwent: sounds good to me!
22:36:01 <danwent> ok, let's go forward with this.
22:36:11 <soren> I'm good at timezone stuff, I just can't subtract.
22:36:15 <soren> Sad.
22:36:24 <danwent> only possible hiccup I see is if doing it on another published IRC channel is OK.
22:36:27 <danwent> soren: :)
22:36:34 <jkoelker> so always count forward then ;)
22:36:43 <danwent> #topic open discussion
22:36:45 <danwent> anything?
22:37:14 <garyk> anyone want to run tomorrow morning? :)
22:37:21 <gongys> regarding my change:
22:37:22 <gongys> https://review.openstack.org/#/c/7596/
22:37:25 <danwent> ok, thanks folks.  Please help wrap up the last few reviews for F-1
22:37:28 <rkukura> feedback on updates/discussion on https://blueprints.launchpad.net/quantum/+spec/provider-networks would be welcome
22:37:39 <danwent> rkukura: great, will do.
22:37:49 <danwent> ok, have a good week folks!
22:37:52 <danwent> #endmeeting