21:01:13 #startmeeting 21:01:13 Meeting started Mon Jul 2 21:01:13 2012 UTC. The chair is danwent. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:01:14 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:01:19 hi 21:01:21 Hi 21:01:22 hi 21:01:29 #info agenda: http://wiki.openstack.org/Network/Meetings 21:01:57 I'd like to keep things pretty tightly focused on F-2 for this meeting, as I know many of your are busily working away on finishing up code and reviews 21:02:24 #info F-2 status: https://launchpad.net/quantum/+milestone/folsom-2 21:02:27 o/ 21:02:59 Overall, there's been a great effort to finish things up, very exciting 21:03:04 gongys: https://launchpad.net/quantum/+milestone/folsom-2 21:03:11 are we still blocked on that test? 21:03:18 Yes. 21:03:28 I reprod it internally, and it does seem to be that commit that breaks things, as I rolled back and did not get the test faiures 21:03:40 gongys: is it correct that this was introduced in a later patchset? 21:03:56 (i.e., can we do binary search to figure out the patchset that introduced it?) 21:04:33 I am looking at it - it seems the problem started in patch set #5 21:05:05 Ok, figuring out that issue is probably top priority for the community at this point for F-2 21:05:17 gongys: its really late for you, correct? 21:05:38 we can bang on this issue and try to figure it out while you sleep 21:05:44 not. it is morning here. 21:05:54 ah, yes, very early… that's right. 21:06:00 yes. 21:06:00 ok, then we can just all pitch in :) 21:06:49 ok. 21:06:52 I also spoke with tr3buchet, lead for nova-network. 21:07:18 he's going to talk to vishy about some aspects of how the nova + quantum integration works. 21:07:39 i'm hoping we can defer any major changes until a later release, but its his call 21:08:08 he had some good suggestions on how to change a couple things, which I will file as bugs that can hopefully be addressed in F-3 21:08:41 gongys: are there any outstanding issues outside of the unit tests and the need for nova core dev reviews? 21:08:53 (vish also said that he would review, so with trey that would be two) 21:09:30 There are some minor comments happened last night, I will deal with them after the meeting. 21:09:50 ok, great. anything else on this review? 21:10:12 whoops, just realized I sent out the wrong link above. here is the review: https://review.openstack.org/#/c/8916/ 21:10:29 and then deal with the jenkins failure on xenapi. 21:11:01 salv-orlando: hopefully you can keep looking there, as you probably have some helpful background around the xenserver stuff. 21:11:16 markmcclain: DHCP status? https://review.openstack.org/#/c/9064/ 21:11:31 working through the latest set of comments 21:11:38 danwent: yes, if you can tell me how to repro after the meeting that would help - have been trying unsuccessfully in the last hour 21:12:06 salv-orlando: oh… i just had to run the unit tests with gongys's patch. 21:12:27 markmcclain: ok, anything you need other folks in the community to help with? 21:12:39 danwent: well, so the difference between my env and your env might pinpoint the root cause of the problem :) 21:12:56 salv-orlando: indeed 21:13:01 we'll talk later 21:13:29 arosen: sounds like OVS v2 plugin just went in? 21:13:38 Yup 21:13:44 great 21:13:47 https://review.openstack.org/#/c/9160/ 21:14:02 garyk: so path is cleared for LB v2 plugin, which needed a rebased after OVS v2? https://review.openstack.org/#/c/9101/ 21:14:24 danwent: current;y rebasing and addressing commenst from aaron 21:15:17 garyk: ok, but reasonable to expect that to land today (or wait, its really late for you?) 21:15:30 danwent: maybe by end of meeting. 21:15:38 maybe get a quick rev in, and if so, hopefully its good to merge 21:15:56 ok 21:16:13 or we can just do it early tomorrow, just really want it in before main openstack mtg. 21:16:25 rkukura: https://review.openstack.org/#/c/9069/ 21:16:38 Plan to resubmit tomorrow, dropping V1 and adding V2. 21:16:51 ok, i think that's the right strategy 21:17:11 if possible, let's sync quickly on the API extension details after the main mtg. 21:17:17 OK 21:17:44 zhhuabj, debo-os : quantum gating 21:17:53 pinged dean 21:18:05 for review 21:18:18 hi, dan, yesterday I have replied your mail about quantum gating 21:18:19 I think zhhuabj and I did some overlapping work 21:18:26 yeah, he passed my request on about adding new quantum reviewers to devstack. 21:18:45 ok I will keep pinging devstack folks for our reviews 21:18:47 with the amount of churn that will happen in quantum in the next month or two, we'll need a lot of changes to devstack. 21:18:59 I will reping them as well :) 21:19:11 so are all changes that are needed changes to devstack? 21:19:16 Deffo 21:19:27 I concur indefinitely 21:19:42 they are not really devstack changes 21:19:51 they are changes to the exercise script 21:19:57 and the euca tests are devstack changes 21:19:59 debo-os: and can you create an issue for updating excercise scripts to use quantum v2 in F-3? 21:20:07 yes I will do 21:20:32 danwent: any progress on core reviewer for devstack? 21:20:34 thx. 21:20:52 just mentioned above… dean passed my request on to the people who manage the devstack-core team 21:21:21 i'll ping them again though, as devstack is definitely becoming a bottleneck here. 21:21:34 and the best way to help is to contribute ourselves 21:21:45 Ok, any other F-2 items we need to discuss 21:22:08 any critical bugs that MUST be completed by the F-2 milestone release? 21:22:39 #topic community topics 21:22:51 what's your opinion on bug 1019899 21:22:52 Launchpad bug 1019899 in quantum "add support for requested_networks extension to Nova/Quantum v2 code" [High,Confirmed] https://launchpad.net/bugs/1019899 21:23:06 should we make an extra effort to push it by folsom-2? 21:23:10 salv-orlando: I'd really like to see that, and discussed it with Trey. 21:23:27 it will be very confusing if "--nic" no longer works for spinning up a VM 21:23:37 and it should be a pretty straightforward change 21:23:55 If someone could grab that one, I'd appreciate it 21:24:04 ok, consider it taken 21:24:33 thx 21:24:47 After my change gets in, the issue should be easy to dealt with. 21:24:55 gongys: agreed 21:25:17 Ok, so on the ML we talked about dropping v1 support during folsom, specifically during the F-3 period. 21:25:18 If no one seize it, I will fix it. 21:25:40 I think there was rough consensus, but wanted to raise it here before considering it final 21:26:16 going once, twice... 21:26:25 #info: quantum will drop v1 quantum API support in Folsom-3 time period. 21:27:20 other than that, I don't want to take the focus off of F-2 reviews and testing by discussing anything else. 21:27:47 oh, one other thing is that we'll need someone to do the devstack work for DHCP, as I mentioned in my email this morning. 21:28:14 arosen has done the base v2 devstack work, so we can build on that. 21:28:21 (still out for review) 21:28:33 #topic open discussion 21:28:40 I can probably add that to what I have up on review if I figure out how to use the dhcp stuff. 21:28:53 arosen: I can help you with it 21:28:57 arosen: ok, that would be great. 21:29:05 Don't make the review of one change too big. 21:29:20 gongys: hehe, yeah, definitely do it as a separate review 21:29:34 though we don't seem to have good luck even with short devstack reviews :) 21:29:40 ok, any other open discussion? 21:30:05 Kjm 21:30:12 Smh 21:30:12 my quantumclient binary name 21:30:20 00110000 21:30:20 it is quantumv2 21:30:22 now 21:30:29 gongys: yes… i think it should just be 'quantum' 21:30:31 should I change it back into quantum. 21:30:46 yeah, then we can get rid of the old one (currently, both are installed) 21:30:50 So I will remove the old binary for v1. 21:31:02 ok, anyone have concerns with that? 21:31:07 After we drop v1. 21:31:20 Yes, after or at same time 21:31:30 ok. 21:31:46 ok, so it will continue to be quantumv2 for F-2, but then in F-3 we'll remove? 21:32:08 yes. 21:32:13 ok, sounds like a plan 21:32:14 Looks good to me :) 21:32:47 ok, thanks folks. keep up the good work reviewing. Remember that starting tuesday we should shift to testing, and that any serious bugs should be flagged in a way to make sure i"m aware of them. 21:33:03 (so i can let thierry know that we need them fixed before he pulls the milestone) 21:33:14 danwent: https://review.openstack.org/#/c/9101/ is ready (i hope) 21:33:19 have a good afternoon/evening/morning! 21:33:26 garyk: just in time! will take a look 21:33:30 #endmeeting