Monday, 2013-01-21

*** danwent has joined #openstack-meeting00:01
*** danwent has quit IRC00:09
*** koolhead17 has joined #openstack-meeting00:16
*** dosaboy has joined #openstack-meeting00:23
*** vishy is now known as vishy_zz00:32
*** vishy_zz is now known as vishy00:44
*** Mandell has joined #openstack-meeting00:46
*** dprince has joined #openstack-meeting01:12
*** ijw has quit IRC01:34
*** ijw has joined #openstack-meeting01:35
*** reed has quit IRC01:36
*** reed has joined #openstack-meeting01:36
*** dosaboy has quit IRC01:40
*** dripton__ has joined #openstack-meeting01:43
*** dripton_ has quit IRC01:46
*** aabes has quit IRC02:02
*** rongze has joined #openstack-meeting02:18
*** jcooley|away is now known as jcooley02:27
*** shang has joined #openstack-meeting02:39
*** galthaus has joined #openstack-meeting02:42
*** stevebaker has quit IRC02:43
*** stevebaker has joined #openstack-meeting02:46
*** jcooley is now known as jcooley|away03:07
*** mdomsch has joined #openstack-meeting03:32
*** Edward_Zhang has joined #openstack-meeting03:34
*** dprince has quit IRC03:34
*** dolphm has quit IRC03:36
*** jcooley|away is now known as jcooley03:37
*** mdomsch has quit IRC03:38
*** persia has quit IRC03:40
*** dripton__ is now known as dripton03:50
*** jcooley is now known as jcooley|away03:58
*** Edward_Zhang has quit IRC04:18
*** roaet-away is now known as roaet04:19
*** jcooley|away is now known as jcooley04:33
*** jcooley is now known as jcooley|away04:42
*** afazekas_ has joined #openstack-meeting04:59
*** Edward_Zhang has joined #openstack-meeting05:16
*** jcooley|away is now known as jcooley05:17
*** woodspa has quit IRC05:20
*** zhuadl has joined #openstack-meeting05:28
*** bdpayne has joined #openstack-meeting05:31
*** bdpayne has quit IRC05:32
*** bdpayne has joined #openstack-meeting05:32
*** adjohn has quit IRC05:33
*** bdpayne has quit IRC05:36
*** dwcramer has quit IRC05:37
*** redbo has quit IRC05:50
*** galthaus has quit IRC06:03
*** vishy is now known as vishy_zz06:15
*** vishy_zz is now known as vishy06:16
*** vishy is now known as vishy_zz06:18
*** adjohn has joined #openstack-meeting06:23
*** spn has joined #openstack-meeting06:31
*** koolhead17 has quit IRC06:34
*** afazekas_ has quit IRC06:37
*** danwent has joined #openstack-meeting06:41
*** asalkeld has quit IRC07:15
*** afazekas_ has joined #openstack-meeting07:15
*** ijw has quit IRC07:18
*** asalkeld has joined #openstack-meeting07:18
*** salv-orlando has joined #openstack-meeting07:20
*** adiantum has joined #openstack-meeting07:22
*** mrunge has joined #openstack-meeting07:30
*** psedlak has joined #openstack-meeting07:49
*** garyk has joined #openstack-meeting07:53
*** rafaduran has joined #openstack-meeting08:01
*** EmilienM has joined #openstack-meeting08:06
*** ijw has joined #openstack-meeting08:06
*** garyk has quit IRC08:18
*** bencherian has quit IRC08:18
*** adjohn has quit IRC08:23
*** koolhead17 has joined #openstack-meeting08:34
*** garyk has joined #openstack-meeting08:36
*** ttrifonov_zZzz is now known as ttrifonov08:37
*** ttrifonov is now known as ttrifonov_zZzz08:46
*** danwent has quit IRC09:04
*** ndipanov has joined #openstack-meeting09:05
*** fnaval_ has joined #openstack-meeting09:09
*** fnaval has quit IRC09:10
*** jhenner has joined #openstack-meeting09:14
*** darraghb has joined #openstack-meeting09:23
*** zhuadl_ has joined #openstack-meeting09:25
*** zhuadl has quit IRC09:27
*** zhuadl_ is now known as zhuadl09:27
*** spn has quit IRC09:33
*** jhenner1 has joined #openstack-meeting09:34
*** spn has joined #openstack-meeting09:34
*** jhenner has quit IRC09:34
*** afazekas_ has quit IRC09:35
*** almaisan-away is now known as al-maisan09:38
*** stevebaker has quit IRC09:44
*** stevebaker has joined #openstack-meeting09:54
*** EmilienM has quit IRC09:58
*** mrunge has quit IRC10:07
*** afazekas has joined #openstack-meeting10:07
*** jhenner1 has quit IRC10:12
*** mrunge has joined #openstack-meeting10:16
*** Edward_Zhang has quit IRC10:19
*** zhuadl has quit IRC10:20
*** EmilienM has joined #openstack-meeting10:23
*** jhenner has joined #openstack-meeting10:26
*** vkmc has joined #openstack-meeting10:37
*** derekh has joined #openstack-meeting10:40
*** EmilienM has quit IRC10:44
*** adiantum has quit IRC10:52
*** adiantum has joined #openstack-meeting10:54
*** al-maisan is now known as almaisan-away11:22
*** shang has quit IRC11:25
*** spn has quit IRC11:35
*** spn has joined #openstack-meeting11:35
*** maurosr has joined #openstack-meeting11:35
*** spn is now known as spn__11:36
*** spn has joined #openstack-meeting11:36
*** ijw has quit IRC11:37
*** spn has quit IRC11:38
*** almaisan-away is now known as al-maisan11:40
*** salv-orlando has quit IRC11:44
*** beagles has joined #openstack-meeting11:50
*** salv-orlando has joined #openstack-meeting11:56
*** alexpilotti has joined #openstack-meeting11:57
*** salv-orlando_ has joined #openstack-meeting12:08
*** salv-orlando has quit IRC12:11
*** salv-orlando_ is now known as salv-orlando12:11
*** adiantum has quit IRC12:11
*** vkmc has quit IRC12:14
*** spn has joined #openstack-meeting12:19
*** spn__ has quit IRC12:20
*** vkmc has joined #openstack-meeting12:22
*** eharney has joined #openstack-meeting12:29
*** eharney has joined #openstack-meeting12:29
*** aabes has joined #openstack-meeting12:32
*** aabes has quit IRC12:56
*** psedlak has quit IRC13:09
*** psedlak has joined #openstack-meeting13:10
*** cmagina_away is now known as cmagina13:26
*** EmilienM has joined #openstack-meeting13:27
*** dprince has joined #openstack-meeting13:38
*** joesavak has joined #openstack-meeting13:43
*** cmagina has quit IRC13:51
*** al-maisan is now known as almaisan-away13:53
*** radez_g0n3 is now known as radez14:02
*** galthaus has joined #openstack-meeting14:08
*** cmagina has joined #openstack-meeting14:09
*** lbragstad has joined #openstack-meeting14:18
*** ayoung has quit IRC14:22
*** adiantum has joined #openstack-meeting14:26
*** eharney has quit IRC14:32
*** dwcramer has joined #openstack-meeting14:34
*** mtreinish has joined #openstack-meeting14:43
*** fnaval_ has quit IRC14:47
*** martine_ has joined #openstack-meeting14:48
*** vishy_zz is now known as vishy14:53
*** ijw has joined #openstack-meeting14:53
*** markvan has joined #openstack-meeting14:58
*** yaguang has joined #openstack-meeting14:59
*** dosaboy has joined #openstack-meeting14:59
*** blamar has joined #openstack-meeting15:02
*** dolphm has joined #openstack-meeting15:06
*** mrodden has joined #openstack-meeting15:08
*** annegentle has joined #openstack-meeting15:08
*** fnaval has joined #openstack-meeting15:08
*** EmilienM has quit IRC15:13
*** sandywalsh has joined #openstack-meeting15:15
*** markvan_ has joined #openstack-meeting15:20
*** rnirmal has joined #openstack-meeting15:22
*** markvan has quit IRC15:23
*** markvan_ is now known as markvan15:23
*** otherwiseguy has joined #openstack-meeting15:25
*** bencherian has joined #openstack-meeting15:30
*** john5223 has joined #openstack-meeting15:32
*** fnaval has quit IRC15:33
*** psedlak has quit IRC15:36
*** fnaval has joined #openstack-meeting15:36
*** afazekas has quit IRC15:41
*** zyluo has joined #openstack-meeting15:50
*** danwent has joined #openstack-meeting15:52
*** blamar has quit IRC15:56
*** eharney has joined #openstack-meeting15:57
*** eharney has joined #openstack-meeting15:57
*** blamar has joined #openstack-meeting16:00
*** woodspa has joined #openstack-meeting16:07
*** Mandell has quit IRC16:07
*** cp16net|away is now known as cp16net16:10
*** adjohn has joined #openstack-meeting16:12
*** valdiyen has joined #openstack-meeting16:12
*** cmagina has quit IRC16:13
*** valdiyen is now known as cmagina16:13
*** cmagina has left #openstack-meeting16:16
*** cmagina_away has joined #openstack-meeting16:20
*** beagles has quit IRC16:22
*** beagles has joined #openstack-meeting16:25
*** ijw has quit IRC16:34
*** blamar has quit IRC16:35
*** blamar has joined #openstack-meeting16:36
*** vishy is now known as vishy_zz16:39
*** jhenner has quit IRC16:44
*** markvan_ has joined #openstack-meeting16:47
*** markvan has quit IRC16:47
*** markvan_ is now known as markvan16:47
*** markvan_ has joined #openstack-meeting16:49
*** markvan has quit IRC16:49
*** markvan_ is now known as markvan16:49
*** vishy_zz is now known as vishy16:49
*** blamar has quit IRC16:51
*** adiantum has quit IRC16:53
*** blamar has joined #openstack-meeting17:02
*** martine_ has quit IRC17:04
*** jaypipes has quit IRC17:06
*** garyk has quit IRC17:08
*** vishy is now known as vishy_zz17:13
*** cdub_ has joined #openstack-meeting17:16
*** vishy_zz is now known as vishy17:16
*** rafaduran has quit IRC17:21
*** jaypipes has joined #openstack-meeting17:22
*** jaypipes has quit IRC17:29
*** jaypipes has joined #openstack-meeting17:35
*** Adri2000 has quit IRC17:37
*** noxon has quit IRC17:38
*** blamar has quit IRC17:39
*** vishy is now known as vishy_zz17:43
*** ayoung has joined #openstack-meeting17:45
*** Adri2000 has joined #openstack-meeting17:49
*** Adri2000 has joined #openstack-meeting17:49
*** noxon has joined #openstack-meeting17:50
*** afazekas has joined #openstack-meeting17:51
*** vishy_zz is now known as vishy17:51
*** Mandell has joined #openstack-meeting17:59
*** noxon has quit IRC17:59
*** Adri2000 has quit IRC17:59
*** dabo has quit IRC17:59
*** dendrobates has quit IRC17:59
*** dendrobates has joined #openstack-meeting17:59
*** dendrobates has joined #openstack-meeting17:59
*** dabo has joined #openstack-meeting17:59
*** cdub_ has quit IRC18:00
*** ayoung has quit IRC18:03
*** cdub_ has joined #openstack-meeting18:08
*** darraghb has quit IRC18:08
*** Adri2000 has joined #openstack-meeting18:10
*** yaguang has quit IRC18:11
*** noxon has joined #openstack-meeting18:11
*** Adri2000_ has joined #openstack-meeting18:14
*** markmcclain has joined #openstack-meeting18:17
*** bearovercloud has joined #openstack-meeting18:18
*** danwent has quit IRC18:21
*** danwent has joined #openstack-meeting18:23
*** ociuhandu has joined #openstack-meeting18:28
*** dosaboy has quit IRC18:29
*** EmilienM has joined #openstack-meeting18:36
*** cp16net is now known as cp16net|away18:44
*** danwent has quit IRC18:44
*** topol has joined #openstack-meeting18:46
*** martine has joined #openstack-meeting18:46
*** khaido has quit IRC18:50
*** martine has quit IRC18:52
*** martine has joined #openstack-meeting18:52
*** blamar has joined #openstack-meeting18:52
*** markmcclain has quit IRC19:02
*** jsavak has joined #openstack-meeting19:03
*** joesavak has quit IRC19:04
*** lbragstad has quit IRC19:05
*** dosaboy has joined #openstack-meeting19:05
*** lbragstad has joined #openstack-meeting19:06
*** mrodden has quit IRC19:10
*** jcmartin has joined #openstack-meeting19:16
*** adjohn has quit IRC19:20
*** dosaboy has quit IRC19:21
*** mrodden has joined #openstack-meeting19:27
*** cp16net|away is now known as cp16net19:27
*** jcmartin has quit IRC19:42
*** novas0x2a|laptop has joined #openstack-meeting19:45
*** stevebaker has quit IRC19:48
*** yamahata_ has joined #openstack-meeting19:50
*** yaguang has joined #openstack-meeting19:57
*** ayoung has joined #openstack-meeting19:57
*** otherwiseguy has quit IRC20:02
*** dosaboy has joined #openstack-meeting20:02
*** sandywalsh_ has joined #openstack-meeting20:05
*** avishayb has joined #openstack-meeting20:10
*** colinmcnamara has joined #openstack-meeting20:21
*** stevebaker has joined #openstack-meeting20:22
*** sharis has joined #openstack-meeting20:26
*** yaguang has quit IRC20:32
*** dosaboy has quit IRC20:34
*** yaguang has joined #openstack-meeting20:37
*** dosaboy has joined #openstack-meeting20:40
*** sthakkar has joined #openstack-meeting20:43
*** avishayb has quit IRC20:44
*** bearovercloud_ has joined #openstack-meeting20:44
*** sharis has left #openstack-meeting20:45
*** sharis has joined #openstack-meeting20:45
*** bearovercloud has quit IRC20:45
*** bearovercloud_ is now known as bearovercloud20:45
*** rkukura has joined #openstack-meeting20:45
*** maurosr has quit IRC20:46
*** otherwiseguy has joined #openstack-meeting20:47
*** vkmc has quit IRC20:48
*** henrynash has joined #openstack-meeting20:48
*** sharis has quit IRC20:50
*** SumitNaiksatam has joined #openstack-meeting20:51
*** amotoki has joined #openstack-meeting20:54
*** Youcef has joined #openstack-meeting20:54
*** emagana has joined #openstack-meeting20:55
*** yamahata_ has quit IRC20:55
*** yamahata_ has joined #openstack-meeting20:56
*** gongysh has joined #openstack-meeting20:57
*** shiv has joined #openstack-meeting20:57
*** markmcclain has joined #openstack-meeting20:58
*** danwent has joined #openstack-meeting20:59
danwenthi folks20:59
salv-orlandoaloha20:59
enikanorovhi20:59
*** dosaboy has quit IRC20:59
rkukurahi20:59
mesteryhowdy folks20:59
shivhi all20:59
gongyshhi20:59
danwentdoing this meeting on a holiday is nice… i get to be outside in the sun :)20:59
yamahata_hi20:59
SumitNaiksatamgreetings!20:59
amotokihi21:00
markmcclainhi21:00
mesterydanwent: At least you're not in the midwest. Currently -8F right now here in MN.21:00
sthakkarhi all21:00
danwentmestery: yeah, talked to my mom yesterday, she said it was freezing :)21:00
danwent#startmeeting quantum21:00
*** Hg has joined #openstack-meeting21:00
openstackMeeting started Mon Jan 21 21:00:37 2013 UTC.  The chair is danwent. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
emaganahi folks!21:00
*** openstack changes topic to " (Meeting topic: quantum)"21:00
*** garyk has joined #openstack-meeting21:00
*** Hg_ has joined #openstack-meeting21:00
openstackThe meeting name has been set to 'quantum'21:00
*** mlavalle has joined #openstack-meeting21:00
danwent#info agenda: http://wiki.openstack.org/Network/Meetings21:00
garykhi21:00
mlavallehi21:01
danwent#topic announcements21:01
*** openstack changes topic to "announcements (Meeting topic: quantum)"21:01
alexpilottihi21:01
danwent#info I updated the "community projects" page with some work items that would be useful for the whole community in Grizzly, but currently have no one assigned: http://wiki.openstack.org/QuantumStarterBugs21:01
danwent#info if you're looking for a way to get more engaged with the community, please take a look at this list.21:01
danwentothers, feel free to add additional projects to this page21:01
danwent(even if they are assigned to you, but you're having trouble finding time to work on them, and would be happy if someone else took it off your plate)21:02
danwentany other announcements?21:02
*** bobmel has joined #openstack-meeting21:02
danwent#topic documentation21:02
*** openstack changes topic to "documentation (Meeting topic: quantum)"21:02
arosenhi21:03
danwentseems like we still have this floating around: https://bugs.launchpad.net/openstack-manuals/+bug/108830421:03
uvirtbotLaunchpad bug 1088304 in openstack-manuals "quantum security group doc is confusing when it comes to use nova security group features" [High,In progress]21:03
*** nati_ueno has joined #openstack-meeting21:03
nati_uenoHi21:03
danwentarosen or nati_ueno does it make sense just to remove references to the nova handler for now, since it is not merged?21:03
gongyshthat bug is waiting for the nova-security commands to be implemented to call quantum.21:04
gongyshjust like the way we do in floating ip.21:04
*** colinmcnamara has quit IRC21:04
arosendanwent:  I think so since we are not going to push the nova handler upstream.21:04
*** otherwiseguy has quit IRC21:05
nati_uenoso whta's blocker?21:05
arosendanwent:  yup what gongysh said21:05
danwentgongysh: yes, but I suspect that when we complete https://blueprints.launchpad.net/nova/+spec/nova-quantum-security-group-proxy, the config instructions will be diference21:05
nati_uenos/whta/wtat/21:05
danwentnati_ueno: that nova blueprint isn't currently being worked on.21:05
nati_uenodanwent: nova-quantum-security-group-proxy,?21:06
danwentthe approach arosen used in the past used the security group triggers in nova, but its not a fully reliable mechanism, hence, it is better to do more of a redesign in nova21:06
danwentnati_ueno: yes21:06
danwentarosen is assigned, but i think its below a stack of stuff for him21:06
nati_uenoMay I take that?21:07
amotokido we need nova proxy for sg? Regarding floating ip proxy, it only works when one nic. It may fail when nova instance has multiple nics.21:07
danwentamotoki: i think its important for people who use euca-* commands, or deploy with only one nic.21:08
amotokidanwent: i see.21:08
salv-orlandoI think the sg proxy can made to work with multiple nice, with some caveats. arisen, what's your take?21:08
danwentamotoki: to proxy floating-ips, but not security groups seems strange.21:08
salv-orlandoarisen => arosen (damn autocorrect)21:08
arosennati_ueno: yea i think it should work fine with multiple nics.21:08
arosenUsing the security group handler that we have now it works fine with muliple nics.21:08
danwentok, well, we don't need to design it here, but let's have nati_ueno and arosen agree to follow-up, with nati_ueno potentially working on it.21:09
danwent#action nati_ueno and arosen: follow up about nova security group proxy blueprint https://blueprints.launchpad.net/nova/+spec/nova-quantum-security-group-proxy21:09
arosendanwent:  nati_ueno sounds good to me.21:09
nati_uenoHow we handle source_ip on multi nic case?21:09
nati_uenodanwent: gotcha21:09
danwentnext doc bug that is 'high': https://bugs.launchpad.net/openstack-manuals/+bug/109983721:09
uvirtbotLaunchpad bug 1099837 in openstack-manuals "dhcp-agent and l3-agent should run without namespace" [High,Triaged]21:09
danwentamotoki: the title of this bug seems deceptive21:09
danwentreally its saying that they should not be run together on the same host, if use_namespace = False, right?21:10
amotokiyes.21:10
danwentamotoki: I also have a half written email to be sent to the list about this, as I think the limitations that we need to document are even more severe21:10
danwent#action danwent sent out note on issues when name_spaces are disabled21:10
danwentthere are currently no items in the api-docs labeled as 'high'21:11
*** avishayb has joined #openstack-meeting21:11
danwentbut from last meeting we had an action item on salv-orlando to file additional issues around any extensions not current documented21:11
danwentsalv-orlando: any progress on that?21:11
danwenti shall i re-issue the action item.21:11
salv-orlandoyes. The news is that there no progress :)21:12
gongyshI opened the bug21:12
salv-orlandoseriously the cisco ones are all undocumented21:12
salv-orlandobut that's little news21:12
salv-orlandowhat we regard as 'community' extensions are documented. I heard provider networks were not documented21:12
*** Nachi has joined #openstack-meeting21:12
salv-orlandobut I recall Bob filed the patch and it was approved21:13
rkukurathat was to the admin guide, not the api guide21:13
salv-orlandoI see21:13
danwentok, is there a reason it doesn't show here: https://bugs.launchpad.net/openstack-api-site/+bugs?field.tag=netconn-api21:13
danwent(for the api docs?)21:13
salv-orlandook cool. Dan, please reissue the action and I will send a note with items to complet21:13
*** otherwiseguy has joined #openstack-meeting21:13
danwent #action salv-orlando to file doc bugs for new undocumented API21:14
danwent    extensions (both netconn-api and openstack-manuals)21:14
danwentargh21:14
danwent #action salv-orlando to file doc bugs for new undocumented API  extensions (both netconn-api and openstack-manuals)21:14
danwentstupid copy/paste :)21:14
danwentok, anything else on docs?21:14
*** adjohn has joined #openstack-meeting21:15
salv-orlando#action all quantum people to beat salv-orlando if he forgets about it again21:15
gongyshahah21:15
danwentsalv-orlando: careful, these meetings are fully archived :P21:15
Nachilol21:15
danwentsalv-orlando: that counts as evidence in court21:15
danwent#topic grizzly-3 milestone status21:15
*** openstack changes topic to "grizzly-3 milestone status (Meeting topic: quantum)"21:15
danwent#info branch date for g-3 is Feb 19th, that is less than a month away21:16
*** nati_ueno has quit IRC21:16
danwent#info the number of blueprints filed last week was 31 (insanely high) and has increased to 36 this week.21:16
*** Nachi is now known as nati_ueno21:17
danwent#info summary is that we're very unlikely to get even most of this stuff merged.  If you have something that is not a community priority ('high' or above), best to make sure you line up reviewers ahead of time, as they will likely be crunched later in the cycle.21:17
danwentdue to the holiday, i don't think a lot of the sub-team leaders added items to the agenda.  I will send an email bugging them about this later this week, so we're ready for next weeks meeting.21:18
danwent#action danwent bug sub-team leads to fill in agenda items for next weeks meeting21:18
salv-orlandoIt might be rude, but I think we should agree on a number of about 20 bps, and then defer the others.21:18
*** Adri2000_ has quit IRC21:18
salv-orlandothere's just no way we can do 36, especially as most members of the core are busy with development as well21:19
garyksalv-orlando: i agree with you.21:19
markmcclainI agree too21:19
enikanorovsalv-orlando: is it a matter of time spent on reviews?21:19
danwentmy feeling is that core devs should feel "compelled" to do reviews for community items that are "high" or above21:19
danwentanything that is medium or low, they should review based on whether they think its a valuable contribution, but would not be "obligated".21:20
salv-orlandoTime on review and time developing. I can't commit more than 40% of time on reviews, for instance. And the remaining 60% I'm generating burden for reviewers through code :)21:20
danwentmy general policy is that if you're medium or below, you need to convince a reviewer that your stuff brings value (or horse-trade with them)21:21
danwentbut if we think it woudl be valuable to start booting out items this early, I think there is a lot of "not started" items to look at :)21:21
emaganadanwent: +121:21
danwentso, do you all want to specify particular non-high/critical BPs to remove21:22
danwentor just have a policy that core devs are only "compelled" to make sure high/critical blueprints get merged.21:23
danwenti'm fine either way21:23
markmcclainI think high above21:23
salv-orlandoI'm fine too… my real goal if avoiding the code deluge that usually happen in the last week21:23
danwentyeah, everyone tries to push everything in G-3, and there's no reason this should put an insane burden on core devs.21:24
danwentwe need to stay focused on key community items21:24
danwentplus, each core dev will have his own project priorities, from which he can allocate additional review time.21:24
zykes-will the l3 + dhcp scaling / ha stuff lad for G ?21:25
danwentzykes-: it is ranked 'high', so it means its a community priority, and thus is likely to land21:25
danwentok, anyone else want to discuss this more before we move on?21:26
danwent#info due to extremely high number of blueprints, it is decided that core devs need only be "compelled" for focus on community blueprints "high and above", and can choose which medium/low blueprints they feel are valuable enough to the community to be reviewed.21:26
*** blamar has quit IRC21:27
danwenti noticed XML support was filed: https://blueprints.launchpad.net/quantum/+spec/quantum-v2-api-xml21:27
gongyshyes21:27
danwentdo we feel this is valuable enough to merit a 'high' ranking?21:27
*** joesavak has joined #openstack-meeting21:27
danwenti tend to think so, but wanted to check with people.21:27
danwent(assuming we think the approach is clean)21:27
gongyshI don't assume it can get in with just two patch sets21:28
danwentother than that, there are still some continueing discussions around vif-plugging on the ML, but i'm marking garyk's BP as implemented, since further changes are likely only in nova: https://blueprints.launchpad.net/quantum/+spec/vif-plugging-improvements21:28
*** dprince has quit IRC21:28
danwentgongysh: ok, let's keep it at high for now21:28
salv-orlandoI've started the review. The point is that we need to see whether the way in which collections and null values are handled is satisfactory.21:29
salv-orlandobut I'm happy to spend time on this.21:29
danwentsalv-orlando: ok.21:29
gongyshyes.21:29
danwentnati_ueno: https://blueprints.launchpad.net/quantum/+spec/quantum-security-groups-iptables-ovs21:29
gongyshsee the test cases.21:29
mesterydanwent: I've been reviewing the Nova side changes for VIF plugging as well. Some of them appear likely to go in soon.21:29
*** radez is now known as radez_g0n321:30
danwentmestery: yes, i need to get my reviews in today.  as we saw last week, it seems like some of these reviews are going a little too quickly :)21:30
nati_uenodanwent: The bp is under review now21:30
*** jsavak has quit IRC21:30
danwentnati_ueno: is whiteboard still accurate that you are blocked by: https://bugs.launchpad.net/nova/+bug/105043321:30
uvirtbotLaunchpad bug 1050433 in nova "LibvirtBridgeDriver crashes when spawning an instance with NoopFirewallDriver" [High,Confirmed]21:30
nati_uenodanwent: I'll check21:30
danwentwhich is unassigned and not targeted for g-3?21:31
danwentnati_ueno: ok, anything else to add on this BP?21:31
danwentgongysh: https://blueprints.launchpad.net/quantum/+spec/quantum-scheduler21:31
nati_uenodanwent: The fix is in https://review.openstack.org/#/c/19126/. We should update bug report21:31
danwentnati_ueno: ok, please do21:32
salv-orlandoI think this blueprint is already covered by at least two core devs, isn't?21:32
danwentsalv-orlando: ah, thanks for asking21:32
nati_uenodanwent: sure21:32
danwentlooks like arosen and amotoki are actively reviewing the OVs plugin SG patch, so we should be covered there21:33
danwentgoing back to the xml patch for a sec21:33
danwentdo we have two core devs there yet?21:33
danwentif its 'high', we should21:33
garykdanwent: i started to look at it and asked a question or two21:34
markmcclainI've reviewed the XML patch21:34
markmcclainand salv-orlando is on it too right?21:34
danwentyup, with salv-orlando we should be covered21:34
salv-orlandoyes, I'll work on XML as well.21:34
gongyshmarkmcclain: I have uploaded a new patch set.21:34
danwentok, now back to gongysh for https://blueprints.launchpad.net/quantum/+spec/quantum-scheduler21:34
danwentlooks like salv-orlando and garyk are reviewing.  i'll promise a review today as well :)21:35
*** yaguang has quit IRC21:35
gongyshthanks21:35
danwentgongysh: if you haven't already, you'll notice that i put a freeze on the nova side change until the quantum side merges.21:36
gongyshdanwent: I can understand.21:36
danwentok, next up, lbaas21:36
*** mrunge has quit IRC21:37
danwentwe have https://blueprints.launchpad.net/quantum/+spec/lbaas-agent-and-rpc as well as https://blueprints.launchpad.net/quantum/+spec/lbaas-haproxy-driver21:37
enikanorovgood progress on both21:37
enikanorovIlya is going to put the first one on review this week21:37
enikanorovhowever we have planned to add dev management and scheduling as well, but danwent moved it out g-321:38
enikanorovi still think it's something we should have in some form21:38
sthakkarbased on the update in the blueprint, review is expected to post later this week21:38
danwentenikanorov: yeah, i think that makes sense21:38
*** nati_ueno has quit IRC21:38
sthakkardo we have core devs?21:38
danwentok, please make a note to update that on the blueprint.21:38
sthakkar(for those that are imminently posting)21:38
*** nati_ueno has joined #openstack-meeting21:38
enikanorovdanwent: what bp you are meaning now?21:39
danwent(i.e., the whiteboard section of the blueprint) if you have estimates of when the review will be avialable21:39
danwentboth of the two mentioned above21:39
salv-orlandoI think I can do review on both patches. I've already done the reviews for the other two LB patches21:39
danwenthttps://blueprints.launchpad.net/quantum/+spec/lbaas-agent-and-rpc as well as https://blueprints.launchpad.net/quantum/+spec/lbaas-haproxy-driver21:39
enikanorovok, regarding lbaas i think there is one thing that is totally missing21:39
danwentif something is priority 'high', we should be tracking its progress weekly.21:39
enikanorovand we even didn't discuss it21:39
danwentenikanorov: yes?21:40
gongyshenikanorov: what is it?21:40
enikanorovi'd call it "service insertion configuration" or something21:40
enikanorovin fact, all we've done for lbaas misses device configuration for particular insertion21:40
enikanorov*for particular insertion type21:41
enikanorovso we didn't even agree on which type will be default21:41
danwentenikanorov: are you talking about how they "plug" into L2 networks, or something else?21:41
enikanorovyes21:41
enikanorovl2 and l321:42
*** emaganap has joined #openstack-meeting21:42
danwentthis is something we discussed at the summit, I believe.21:42
danwentanyway, probably best to start an ML thread on this, as we only have 18 minutes in the meeting.21:42
*** dwcramer has quit IRC21:42
amotokido you have a plan to add lbaas support in devstack?21:43
enikanorovok, i think i'll start such thread21:43
danwentenikanorov: great, thank you21:43
enikanorovand less of concern, we have salv-orlando's code regarding service types, but no use of it yet21:44
danwentenikanorov: because there will only be one driver to start?21:44
enikanorovis it something left for better days of after grizzly?21:44
salv-orlandoenikanorov: I think it's up to you guys if you want to add support the lb plugin for service types.21:44
salv-orlandoOtherwise I can do that on top of your patch as soon as it is available21:44
avishaybI have submitted a BP on this (service type)21:44
salv-orlandoassuming that it's doable21:44
salv-orlandoyeah let's avyshayb do that then21:45
enikanorovok, i'll check it out21:45
danwenti think avishayb's blueprint is general, not specific to lbaas?21:45
bobmelSorry, which bp is that?21:45
danwentavishayb: i read the blueprint quickly, but it wasn't clear to me what it meant21:45
danwentavishayb: do you have a pointer?21:46
enikanorovdanwent: is there a chance we can have scheduling& dev management in g-3? code is ready, btw21:46
danwentenikanorov: at this point, its the review cycle that worries me more than anything.  let's get the base lbaas stuff in, and then see where we stand with respect to the G-3 deadline21:46
avishaybthe idea is to add the service type (Golden,Silver,etc) on the VIP creation21:46
danwentavishayb: yes, but isn't that what salvatore's blueprint already enables? or are you just talking about making sure the lbaas plugin supports the service-type introduced by salv-orlando ?21:47
avishaybThe BP explains how to do it.21:47
danwentok, running low on time, so let's move this discuss to ML if we can't wrap it up quickly.21:47
enikanorovmay i send you guys an email regarding the scheduling& dev management explaining in details of what have been done so you could decide? I think a part of that code should be in one way or another, so you have to choose which part and how to do it bettter21:48
danwentsalv-orlando: do we need to discuss more before reaching consensus on "core" nature of provider network and l3 apis?21:48
salv-orlandoI think in light of what we said today21:48
salv-orlandowe will consider "de facto core"21:49
salv-orlandomeaning document them as core api, but don't touch the code21:49
danwentenikanorov: i think it makes sense to have basic scheduling in your lbaas plugin.  But I don't want the community consumed by a larger debate on representing devices and scheduling in G-3… there's just too much on our plate already21:49
danwentsalv-orlando: but does "core" mean that all plugins need to expose it, or it is more like the "community supported extensions" idea i mentioned on the ML?21:50
enikanorovdanwent: yep. the code is simplistic. it's all about conf management rather than about comprehensive scheduling or dev management.21:50
danwentenikanorov: ok, pls send note.  we're running out of time in meeting :)21:50
salv-orlandocommunity supported extensions21:50
salv-orlandothat's what I mean by "de facto"21:51
danwentsalv-orlando: ok, I think that makes sense.  Unless we see significant disagreement on the ML, let's document that somewhere and go with it as a plan21:51
SumitNaiksatamsounds reasonable to me too21:51
salv-orlandobenefit/burdess ratio is definitely too low21:51
salv-orlandoburdess -> burden21:51
*** blamar has joined #openstack-meeting21:52
*** avishayb has quit IRC21:52
danwentok, given time constraints, please let me know if there are updates for quantum tempest or quantum horizon,21:52
danwentotherwise, i want to discuss quantum stable, quantum client, and the brocade plugin in the final minutes21:52
amotokigo ahead.21:52
danwent#topic quantum stable21:52
*** openstack changes topic to "quantum stable (Meeting topic: quantum)"21:52
danwentgaryk, i believe mark is targeting jan 24th for all stable fixes being in ?21:52
danwentfor final release on the 31st?21:53
garykdanwent: yes. just have one minor backport to do and then a few in the queue. looking good at the moment21:53
danwentgaryk: ok, great work.  please sent a note to the core team once you have the full list ready for review, as the 24th is before our next meeting.21:53
danwent#topic quantum client21:53
*** openstack changes topic to "quantum client (Meeting topic: quantum)"21:53
garykdanwent: ok, will do21:53
danwentI wanted to start having a section where we track these items, as sometimes they end up under the radar21:54
danwentgongysh: looks like we still need to create a 2.0 release in launchpad to track client changes that we will release in conjunction with grizzly?21:54
gongysh3.0?21:54
danwentgongysh: ah, yes :)21:54
danwentgongysh, markmcclain anything else on client/cli side?21:55
gongyshmarkmccleain said he is going to study it.21:55
markmcclainnot from me21:55
danwentin general, i just want to make sure we're using launchpad to keep track of releases and high priority items.21:55
enikanorovwe have lbaas-cli changes on review as well21:55
gongyshstudy how to create a 3.0 milestone on launchpad.21:55
enikanorovclose to approval, i believe21:55
danwentenikanorov: yup, exactly. :)21:55
danwentok, markmcclain you are going to be creating the milestone on LP?21:56
markmcclainyes21:56
danwent#action markmcclain to create 3.0 milestone on LP for python-quantumclient project and associate appropriate blueprints21:56
danwent#topic open discussion21:56
*** openstack changes topic to "open discussion (Meeting topic: quantum)"21:56
danwentok the one topic i had for open discussion was the brocade plugin21:56
danwentshiv has pushed code to a public github repo21:56
shivbrocade plugin is ready for review-checkin - need bp approval21:56
*** avishayb has joined #openstack-meeting21:57
danwentand garyk has volunteered to be core maintainer.21:57
danwentwhile garyk has a lot on his plate, he is also extremely active in the community, so i think he has the cycles to maintain this if he says he will21:57
danwentis there an active review already?21:57
danwentlast i saw, i just saw code on github21:58
*** jhenner has joined #openstack-meeting21:58
markmcclainalso has the code on github been brought up to hacking standards?21:58
shivare we ok to move code to quantum?21:58
danwentmarkmcclain: i would assume that is  pre-req to getting it merged into quantum, but if they missed some items, it can be handled in review.21:59
*** stevebaker has quit IRC21:59
danwentshiv: are you familar with the HACKING guidlines?  make sure the code is compliant will save a lot of reviewer pain21:59
garykdanwent: shiv : let me know when it is in gerrit for review21:59
danwentgaryk: can you confirm for the logs that you are going to be the maintainer?21:59
*** stevebaker has joined #openstack-meeting21:59
shivwill take care of that, also i have gary for guidance.21:59
garykdanwent: yes, i confirm. is this written in stone?22:00
shivgary: yes..22:00
danwentprobably up to the maintainer to make sure the code is in reasonable shape before asking other core devs to review22:00
danwentgaryk: IRC stone :)22:00
garykdanwent: :) and now its pumpkin.22:00
danwentok, so I just want to make sure no one has any significant concerns with this plugin being added to the main repo22:00
danwentif you do, please work with garyk and shiv on them.22:00
*** yaguang has joined #openstack-meeting22:01
shivlmk, any issues, thx.22:01
danwentat this point, i'll approve the BP and it can be posted to gerrit for more detailed review22:01
danwentwe are over time, but does anyone have any other open issues?22:01
garyki am going to crash. thanks and good night22:01
danwent#info brocade plugin with garyk as a maintainer is cleared to begin review for merging into the main repo22:01
danwent#endmeeting22:02
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"22:02
openstackMeeting ended Mon Jan 21 22:02:04 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/quantum/2013/quantum.2013-01-21-21.00.html22:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/quantum/2013/quantum.2013-01-21-21.00.txt22:02
openstackLog:            http://eavesdrop.openstack.org/meetings/quantum/2013/quantum.2013-01-21-21.00.log.html22:02
danwentthanks folks!22:02
danwenthave a good rest of the holiday if you are in the US :)22:02
mesterythanks!22:02
nati_uenobye22:02
amotokibye22:02
yamahata_bye22:02
avishaybbye22:02
sthakkarthanks22:02
shivbye!22:02
emaganaciao22:02
enikanorovgbye22:02
*** sthakkar has quit IRC22:03
markmcclainbye22:03
*** Nachi has joined #openstack-meeting22:03
*** avishayb has quit IRC22:04
*** zyluo has quit IRC22:04
*** bobmel has quit IRC22:05
*** Nachi has quit IRC22:05
*** jsavak has joined #openstack-meeting22:06
*** mlavalle has left #openstack-meeting22:06
*** nati_ueno has quit IRC22:07
*** Hg_ has quit IRC22:08
*** Hg has quit IRC22:08
*** emagana has quit IRC22:09
*** joesavak has quit IRC22:09
*** shiv has quit IRC22:10
*** emaganap has left #openstack-meeting22:12
*** emagana has joined #openstack-meeting22:14
*** joesavak has joined #openstack-meeting22:15
*** jsavak has quit IRC22:17
*** gongysh has quit IRC22:19
*** yamahata_ has quit IRC22:19
*** otherwiseguy has quit IRC22:20
*** topol has quit IRC22:21
*** nati_ueno has joined #openstack-meeting22:22
*** derekh has quit IRC22:23
*** dwcramer has joined #openstack-meeting22:25
*** stevebaker has left #openstack-meeting22:30
*** stevebaker has joined #openstack-meeting22:31
*** rnirmal has quit IRC22:31
*** maurosr has joined #openstack-meeting22:31
*** maurosr has quit IRC22:35
*** maurosr has joined #openstack-meeting22:35
*** dwcramer has quit IRC22:39
*** martine has quit IRC22:40
*** joesavak has quit IRC22:43
*** annegentle has quit IRC22:45
*** garyk has quit IRC22:53
*** jhenner has quit IRC22:55
*** garyk has joined #openstack-meeting22:57
*** ijw has joined #openstack-meeting22:58
*** john5223 has quit IRC22:58
*** ijw has quit IRC22:58
*** colinmcnamara has joined #openstack-meeting22:59
*** ijw has joined #openstack-meeting22:59
*** yaguang has quit IRC23:00
*** mtreinish has quit IRC23:01
*** cdub_ has quit IRC23:03
*** markmcclain has quit IRC23:05
*** reed has quit IRC23:05
*** dwcramer has joined #openstack-meeting23:07
*** henrynash has quit IRC23:08
*** ijw has quit IRC23:08
*** yaguang has joined #openstack-meeting23:08
*** fifieldt has joined #openstack-meeting23:09
*** yaguang has quit IRC23:10
*** Nachi has joined #openstack-meeting23:11
*** colinmcnamara has quit IRC23:11
*** dwcramer has quit IRC23:12
*** nati_ueno has quit IRC23:13
*** rturk has quit IRC23:14
*** rturk has joined #openstack-meeting23:17
*** dolphm has quit IRC23:18
*** dolphm has joined #openstack-meeting23:19
*** dwcramer has joined #openstack-meeting23:25
*** fnaval has quit IRC23:27
*** markvan has quit IRC23:28
*** lbragstad has quit IRC23:32
*** woodspa has quit IRC23:32
*** blamar has quit IRC23:35
*** afazekas has quit IRC23:37
*** lloydde has joined #openstack-meeting23:37
*** cmagina_away has quit IRC23:41
*** cdub_ has joined #openstack-meeting23:43
*** annegentle has joined #openstack-meeting23:46
*** fnaval has joined #openstack-meeting23:46
*** eharney has quit IRC23:48
*** bearovercloud has quit IRC23:48
*** cdub_ has quit IRC23:53
*** yaguang has joined #openstack-meeting23:56
*** dosaboy has joined #openstack-meeting23:57

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!