21:03:59 #startmeeting Networking 21:04:00 Meeting started Mon Oct 21 21:03:59 2013 UTC and is due to finish in 60 minutes. The chair is markmcclain. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:04:01 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:04:04 The meeting name has been set to 'networking' 21:04:41 #topic General Announcements 21:05:20 #info 2013.2 (Havana) was released last Thursday 21:05:56 #link http://lists.openstack.org/pipermail/openstack-announce/2013-October/000151.html 21:06:38 I'm very excited about this release and thanks to everyone for their hard work 21:08:10 In addition there was stable release on 10/17 21:08:10 http://tarballs.openstack.org/neutron/quantum-2013.1.4.tar.gz 21:08:14 #link http://tarballs.openstack.org/neutron/quantum-2013.1.4.tar.gz 21:08:38 markmcclain, congrats on the Technical Committee elections 21:08:44 dkehn: thanks! 21:08:47 dkehn: +1 to markmcclain! 21:09:29 congrat! 21:09:37 mestery, nati_ueno: thanks 21:10:04 Now that that Havana has been released the stable team will now focus on backports from master to Havana 21:10:51 if you have backports which have landed in master, but were not in the final Havana release please make sure they are tagged havana-backport-pontential 21:11:18 Any questions on the releases and stable backports? 21:12:06 #topic API docs 21:12:08 #link https://bugs.launchpad.net/openstack-api-site/+bugs?field.tag=netconn-api 21:12:35 salv-orlando is on vacation this week 21:12:53 I have the mutli-provider api doc on my list of todo's for this week. 21:13:02 awesome thanks! 21:13:30 arosen1: I can review that if you want as well, add me as a reviewer if you don't mind! 21:13:56 mestery: awesome sounds good. 21:14:00 I'm still working on finding an author for the metering extensions 21:14:55 #topic API 21:14:57 emagana: hi 21:15:09 you mean Docs 21:15:12 :-) 21:15:17 #undo 21:15:18 Removing item from minutes: 21:15:21 #topic docs 21:15:24 :) 21:15:31 no updates from my side, I still owe some time to Tom for working on the install review and also to Cisco Folks on their plugins changes (if not already committed) 21:15:50 also waiting on markmcclain for the metering part 21:15:54 emagana: Thanks much for the help on the Cisco side! 21:16:04 I'm cleaning up some of the duplication in the config docs. 21:16:05 emagana: do you have a link for the install review? 21:16:11 mestery: let me finish it and then you can thank me! :-) 21:16:24 exchange for some beers in HK 21:16:41 emagana: :) 21:16:49 mestery: promise to be in ASAP!!! 21:16:59 emagana: Awesome! 21:17:23 markmcclain: nothing more but maybe Tom or Anne want to include something 21:17:55 ok.. they can chime in if they've got anything to add 21:18:17 #topic Summit 21:18:41 #info the deadline to submit sessions was last Thursday 21:19:00 We had a bunch of late submissions, we're still working our way through the list 21:19:13 our track is oversubscribed by 2:1 margin 21:21:22 Throughout this week we'll be working our way through the list to hopefully have a rough draft schedule by the 25th 21:21:36 markmcclain: I noticed that some session are duplicated 21:22:09 markmcclain: maybe an issue during the submission 21:22:27 emagana: yes there are duplicate topic ideas because we encourage duplicate submissions 21:22:40 mainly to ensure that different variants of ideas are documented 21:23:07 markmcclain: No, I dont mean that. I do see the same entry twice 21:23:08 and then we'll work with the proposers to structure sessions where the ideas can be discussed 21:23:21 markmcclain: I know one I submitted shows up twice in the list, as do some others 21:23:39 rkukura: mine shows three times!! :-) 21:24:16 yeah.. even removing those we will be out of space 21:24:40 Since conference time is at a premium 21:25:20 we may choose to move some topic discussions to the mailing lists or special one off IRC meetings 21:25:45 which route we go really depends on proposal 21:26:22 I'd like to discuss them all, but unfortunately we cannot 21:27:22 Any questions on the selection or review process? 21:27:47 Would it make sense to reserve one session for BOF-style mini-meetings to address the topics that miss the cut? 21:28:09 geoffarnold: I believe there are already unconference slots for that purpose. 21:28:49 I understand. That thought it might be good to do some deliberate scheduling around that 21:28:57 That>Just 21:29:50 geoffarnold: unconference space is a good outlet for it 21:30:07 but I don't want to preemptively register time for sessions 21:30:46 I willl include some brief time each day for those that want to announce their networking related unconference meetings 21:31:01 OK. I'll look forward to seeing the whole schedule 21:31:15 #topic Open Discussion 21:31:53 The meeting between release and the conference is usually one of our shortest ones.. any have topics that we need to cover this week? 21:32:20 just a reminder - IRC meeting tomorrow (tuesday) at 15.30 UTC for "advance services" 21:32:28 common requirements 21:32:39 ? 21:32:44 continuation of discussion from previous meeting 21:33:25 Which IRC? or is it WebEx? 21:33:30 in #openstack-meeting? 21:33:38 thx 21:33:42 geoffarnold: IRC 21:33:53 markmcclain: yeah its listed 21:34:00 same as last week 21:34:06 SumitNaiksatam: perfect 21:34:15 only different time to accommodate folks from asia 21:34:32 SumitNaiksatam: Is it in #openstack-meeting-alt? I have that written down as the channel. 21:34:35 BTW, thanks to Sumit for hosting the svcs F2F last week 21:34:39 little early for folks in PDT, aplologies in advance 21:34:44 geoffarnold: sure 21:35:35 According to here, it is #openstack-meeting-alt (in case anyone else was confused): https://wiki.openstack.org/wiki/Meetings#Neutron_Advanced_Services.27_Common_requirements_team_meeting 21:35:47 mestery: thats right 21:35:50 mestery: thanks for the info 21:35:52 its on the alt channel 21:36:01 markmcclain: sorry i mis spoke 21:36:07 Sure. Just wanted to clarify for folks since it was confusing to me at least. :) 21:36:17 mestery: thanks :-) 21:36:21 SumitNaiksatam: no worries 21:36:25 i am multitasking, sorry folks 21:36:26 what is the meeting for? the wiki page is blank 21:36:34 SumitNaiksatam: Thanks for leading all this service work, great job! 21:37:03 marun: we created a new etherpad 21:37:21 SumitNaiksatam: link? 21:37:24 that has the agenda 21:37:42 mestery: thanks :-) 21:37:47 marun: one sec looking it up 21:38:10 here it is: #link https://etherpad.openstack.org/p/icehouse-neutron-fwaas 21:38:31 KJ_: thanks! :-) 21:38:49 oh sorry thats the fwaas 21:39:07 still relevant ;-) 21:39:19 SumitNaiksatam: any plans on including testing in fwaas plans for icehouse? I see no mention on the etherpad. 21:39:47 marun: thats the first item we discussed in the IRC meeting last week 21:40:08 marun: for: http://eavesdrop.openstack.org/meetings/networking_fwaas/2013/networking_fwaas.2013-10-16-18.01.log.html 21:41:02 don't mean to pick on fwaas, btw. but anybody contemplating adding features without planning on adding the tests in advance or shortly after merge will be feeling the heat next cycle. 21:41:51 a feature isn't 'done' until it has tests. 21:42:01 unit, functional, integration. 21:42:14 https://etherpad.openstack.org/p/NeutronAdvancedServices 21:42:30 This should be it. 21:42:36 danke 21:42:39 marun: tests are a must for new features 21:42:40 garyduan: thanks the ether pad for common requirements discussion 21:43:07 Any other items to discuss this week? 21:43:57 i have one thing 21:44:05 Dan Smith is pushing upgrade compatibility in Nova 21:44:50 marun: in terms of database or upgrading running systems with no downtime? 21:44:53 Specifically on the issue of cross-version RPC compatibility, he's scheduled to give 2 talks - one nova and one tempest track 21:45:08 I've asked him to try to schedule at least one of these on Thursday so that Neutron folk can attend. 21:45:20 marun: perfect 21:45:29 I'd like to sit in that one myself 21:45:29 I suspect we're going to have to approach this issue and it would be good to provide input before his ideas solidify in oslo 21:45:55 Neutron upgrade are fairly nebulous to me at the moment. This will be good to listen in on. 21:46:25 yes.. the upgrade process is something we need to work on in Icehouse 21:46:31 I'm going to have to focus on this issue in the short-term, since we're looking at providing a documented upgrade between rhos 3.0 and 4.0. 21:46:49 Hopefully I'll have some issues to discuss with you all, if only hallway track, at the summit. 21:47:12 marun: That's really good. One thing to think about: What exactly is our current supported upgrade strategy? Does anyone know? 21:47:27 'dead' migration ;) 21:47:30 E.g. can you just leave VMs running, stop neutron, load a new version, restart, and expect things to run ok? 21:47:32 marun: Heh 21:48:05 TBD I think - being able to leave vm's running is a goal but we're still investigating feasibility. 21:48:24 marun: Agreed. I'm very interested in this area as well, look forward to talking in person. 21:48:31 great :) 21:48:45 mestery: it's in the release notes :) 21:48:54 markmcclain: :) 21:49:19 that said the release notes for notes for upgrades are a stop gap 21:49:48 I'd like to see us participating in grenade style testts 21:50:08 +1 21:50:12 +100 21:50:31 any other items? 21:50:50 may be discuss migrations for sqlite? 21:51:04 enikanorov: I'd prefer to cover that in HK 21:51:09 sure 21:51:22 one more thing 21:51:30 markmcclain: will that be a session on that? 21:51:50 yes.. it will be on our agenda 21:51:54 not a full block 21:51:55 carl baldwin and I will be looking into doing functional testing of iptables interaction. hopefully have something to show at summit that others can build on. 21:51:58 but a mini topic 21:52:01 ok 21:52:10 marun: great! 21:52:44 Thanks again to everyone our team for their hard work on Havana! 21:53:04 The schedule rough schedule should be available late this week or over the weekend. 21:53:17 Have a great week and talk to everyone on the mailing list or IRC 21:53:20 #endmeeting