Monday, 2012-07-16

*** dryan2 has quit IRC00:00
*** dolphm has joined #openstack-meeting00:13
*** dolphm has quit IRC00:16
*** dryan1 has joined #openstack-meeting00:24
*** dryan1 has left #openstack-meeting00:25
*** sacharya has quit IRC00:30
*** sacharya has joined #openstack-meeting01:31
*** Mandell has quit IRC01:36
*** ryanpetrello has joined #openstack-meeting01:45
*** ryanpetrello has quit IRC01:49
*** Mandell has joined #openstack-meeting01:51
*** blamar has left #openstack-meeting02:01
*** dolphm has joined #openstack-meeting02:35
*** ryanpetrello has joined #openstack-meeting03:08
*** sacharya has quit IRC03:11
*** zvm-vlam has quit IRC03:20
*** dcramer_ has quit IRC03:33
*** dolphm has quit IRC03:40
*** zvm-vlam has joined #openstack-meeting03:51
*** ryanpetrello has quit IRC04:03
*** ryanpetrello has joined #openstack-meeting04:07
*** dolphm has joined #openstack-meeting04:08
*** dtroyer is now known as dtroyer_zzz04:14
*** sdake has quit IRC04:30
*** kindaopsdevy has quit IRC04:30
*** ovidwu has joined #openstack-meeting04:32
*** ryanpetrello has quit IRC04:32
*** ovidwu has quit IRC04:33
*** ovidwu_ has joined #openstack-meeting04:33
*** ovidwu has joined #openstack-meeting04:34
*** sdake has joined #openstack-meeting04:40
*** dolphm has quit IRC04:47
*** dolphm has joined #openstack-meeting04:47
*** dolphm has quit IRC04:52
*** dendrobates is now known as dendro-afk04:57
*** littleidea has quit IRC05:09
*** garyk has joined #openstack-meeting05:10
*** dtroyer_zzz is now known as dtroyer05:38
*** dtroyer is now known as dtroyer_zzz05:41
*** GheRivero has joined #openstack-meeting06:10
*** derekh has joined #openstack-meeting08:00
*** Mandell has quit IRC08:45
*** darraghb has joined #openstack-meeting08:46
*** p3N74 has joined #openstack-meeting09:09
*** GheRivero has quit IRC09:54
*** GheRivero has joined #openstack-meeting10:10
*** ovidwu has quit IRC10:32
*** milner has joined #openstack-meeting11:13
*** Razique has joined #openstack-meeting11:41
*** derekh has quit IRC11:43
*** ameade has quit IRC11:43
*** tightwork has quit IRC11:43
*** ttrifonov has quit IRC11:43
*** derekh has joined #openstack-meeting11:43
*** ameade has joined #openstack-meeting11:44
*** tightwork has joined #openstack-meeting11:44
*** ttrifonov has joined #openstack-meeting11:44
*** markvoelker has joined #openstack-meeting11:57
p3N74 hi folks12:02
p3N74I am totally new to openstack12:02
p3N74and I would like to create a redundantarchitecture12:02
p3N74just with swift12:02
p3N74can you please help me12:02
p3N74or direct to a documentation link12:02
p3N74thanks12:02
jd___p3N74: this is probably not the right channel to ask for that12:03
*** dcramer_ has joined #openstack-meeting12:07
*** Razique has quit IRC12:41
*** jamespage has quit IRC12:41
*** Adri2000 has quit IRC12:42
*** Adri2000 has joined #openstack-meeting12:43
*** Adri2000 has joined #openstack-meeting12:43
*** sdake has quit IRC12:46
*** dprince has joined #openstack-meeting12:46
*** sdake has joined #openstack-meeting12:46
*** jamespage has joined #openstack-meeting12:48
*** sacharya has joined #openstack-meeting12:48
*** jaypipes has joined #openstack-meeting12:50
*** markmcclain has joined #openstack-meeting12:57
*** GheRivero has quit IRC12:57
*** sacharya has quit IRC12:59
*** dcramer_ has quit IRC13:09
*** ryanpetrello has joined #openstack-meeting13:23
*** blamar has joined #openstack-meeting13:32
*** blamar has quit IRC13:32
*** blamar has joined #openstack-meeting13:33
*** sacharya has joined #openstack-meeting13:36
*** ayoung has joined #openstack-meeting13:46
*** sandywalsh has joined #openstack-meeting13:56
*** dendro-afk is now known as dendrobates13:57
*** ayoung has quit IRC14:00
*** ayoung has joined #openstack-meeting14:01
*** dtroyer_zzz is now known as dtroyer14:04
*** Gordonz has joined #openstack-meeting14:07
*** derekh has quit IRC14:08
*** derekh has joined #openstack-meeting14:08
*** cp16net is now known as cp16net|away14:12
*** dtroyer is now known as dtroyer_zzz14:32
*** dolphm has joined #openstack-meeting14:45
*** mdomsch has joined #openstack-meeting14:45
*** dcramer_ has joined #openstack-meeting14:46
*** dolphm has quit IRC14:48
*** dolphm has joined #openstack-meeting14:48
*** cp16net|away is now known as cp16net14:50
*** littleidea has joined #openstack-meeting14:54
*** nikhil has joined #openstack-meeting14:55
*** metral has joined #openstack-meeting14:57
*** dtroyer_zzz is now known as dtroyer14:57
*** danwent has quit IRC14:57
*** jgriffith has quit IRC15:13
*** jgriffith has joined #openstack-meeting15:15
*** cp16net is now known as cp16net|away15:18
*** cp16net|away is now known as cp16net15:18
*** danwent has joined #openstack-meeting15:27
*** joearnold has joined #openstack-meeting15:28
*** davidkranz_ has joined #openstack-meeting15:31
*** davidkranz has quit IRC15:33
*** ryanpetrello has quit IRC15:38
*** ryanpetrello has joined #openstack-meeting15:40
*** GheRivero has joined #openstack-meeting15:44
*** mattray has joined #openstack-meeting15:53
*** Razique has joined #openstack-meeting15:57
*** ncode has joined #openstack-meeting15:59
*** ncode has joined #openstack-meeting15:59
*** tr3buchet has quit IRC16:03
*** mdomsch has quit IRC16:07
*** Razique has quit IRC16:09
*** PotHix has joined #openstack-meeting16:18
*** jgriffith has quit IRC16:23
*** jgriffith has joined #openstack-meeting16:24
*** jgriffith is now known as Guest5757116:24
*** p3N74 has quit IRC16:25
*** Mandell has joined #openstack-meeting16:26
*** danwent has quit IRC16:28
*** dcramer_ has quit IRC16:38
*** Guest57571 is now known as jgriffith16:42
*** GheRivero has quit IRC16:49
*** danwent has joined #openstack-meeting16:49
*** jog0 has joined #openstack-meeting16:51
*** dcramer_ has joined #openstack-meeting16:52
*** jakedahn_zz is now known as jakedahn16:53
*** jdurgin has joined #openstack-meeting16:58
danwentvishy: is you have a sec, could you re-review (https://review.openstack.org/#/c/9161/)?  You had +2'd in the past and I'd really like to get this into devstack.16:59
*** ncode has quit IRC17:01
*** dhellmann has joined #openstack-meeting17:01
*** dcramer_ has quit IRC17:02
danwentvishy: thanks!17:04
vishyyw17:06
*** johnpur has joined #openstack-meeting17:12
*** garyk has quit IRC17:15
*** dcramer_ has joined #openstack-meeting17:15
*** mnewby has joined #openstack-meeting17:18
*** derekh has quit IRC17:24
*** dolphm has quit IRC17:32
*** dolphm has joined #openstack-meeting17:36
*** darraghb has quit IRC17:37
*** tr3buchet has joined #openstack-meeting17:54
*** tr3buchet has left #openstack-meeting17:59
*** jakedahn is now known as jakedahn_zz18:04
*** dolphm has quit IRC18:06
*** jog0 has quit IRC18:06
*** littleidea has quit IRC18:16
*** littleidea has joined #openstack-meeting18:17
*** tr3buchet has joined #openstack-meeting18:19
*** joearnol_ has joined #openstack-meeting18:26
*** joearnold has quit IRC18:26
*** nati_ueno has joined #openstack-meeting18:28
*** anderstj has joined #openstack-meeting18:46
*** patelna has joined #openstack-meeting18:50
*** GheRivero has joined #openstack-meeting19:00
*** novas0x2a|laptop has joined #openstack-meeting19:12
*** nati_ueno has quit IRC19:35
*** dolphm has joined #openstack-meeting19:35
*** nati_ueno has joined #openstack-meeting19:37
*** salv-orlando has joined #openstack-meeting19:40
*** cp16net is now known as cp16net|away19:42
*** dprince has quit IRC19:48
*** dhellmann has quit IRC19:52
*** joearnol_ has quit IRC19:57
*** novas0x2a|laptop has quit IRC19:58
*** novas0x2a|laptop has joined #openstack-meeting19:58
*** shivh has joined #openstack-meeting20:01
*** dolphm_ has joined #openstack-meeting20:02
*** anderstj has quit IRC20:04
*** dolphm has quit IRC20:05
*** shivh has quit IRC20:11
*** shivh has joined #openstack-meeting20:12
*** dcramer_ has quit IRC20:17
*** nati_ueno has quit IRC20:19
*** nati_ueno has joined #openstack-meeting20:20
*** blamar has quit IRC20:32
*** dcramer_ has joined #openstack-meeting20:34
*** markvoelker has quit IRC20:37
*** markvoelker has joined #openstack-meeting20:47
*** rcloran has joined #openstack-meeting20:51
*** rkukura has joined #openstack-meeting20:52
*** cdub_ has joined #openstack-meeting20:57
*** gongys has joined #openstack-meeting20:57
*** markvoelker1 has joined #openstack-meeting20:58
gongyshi20:58
salv-orlandogongys: hi20:58
gongyssalv-orlando: good afternoon20:59
shivhhio20:59
danwenthi folks20:59
mesteryo/20:59
markmcclainhi20:59
markvoelker1o/20:59
danwentman, gongys beat all of you to saying hello :)21:00
*** arosen has joined #openstack-meeting21:00
danwentmarkvoelker, mestery, i expect better from you in the future :)21:00
markvoelker1Hah21:00
gongysYou know it is early morning here.21:00
salv-orlandoso we should award gongys with a blueprint21:00
PotHixo/21:00
rkukurahi21:00
mestery:D21:00
danwentgongys has been chewing through blueprints like a madman already :)21:00
danwent#startmeeting21:01
openstackMeeting started Mon Jul 16 21:01:03 2012 UTC.  The chair is danwent. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** amotoki has joined #openstack-meeting21:01
gongyshaha. Is that  a reward?21:01
danwent#link Agenda: http://wiki.openstack.org/Network/Meetings21:01
*** marktvoelker has joined #openstack-meeting21:01
*** markvoelker1 has quit IRC21:01
danwenttoday we have a couple design/coordination issues to discuss21:01
*** SumitNaiksatam has joined #openstack-meeting21:01
SumitNaiksatamHi21:02
*** garyk has joined #openstack-meeting21:02
danwenthoping to nudge along a few discussion to make sure they don't become blockers21:02
*** amotoki has quit IRC21:02
garykevening all21:02
danwentgaryk: hey21:02
garykdanwent: hi21:02
danwentfirst up, here's the current status of folsom-3: https://launchpad.net/quantum/+milestone/folsom-321:02
*** s0mik has joined #openstack-meeting21:02
*** markvoelker has quit IRC21:02
*** marktvoelker is now known as markvoelker21:02
danwentwe are 3 weeks out from when all features should be pushed for review21:02
*** amotoki has joined #openstack-meeting21:02
danwenta month out from the final release date.21:03
danwentA couple key reviews to draw attention to (unfortunately, both are not in quantum)21:03
danwentfirst, garyk's devstack + dhcp patch: https://review.openstack.org/#/c/9362/21:03
danwent(arosen's v2 devstack patch got merged earlier today)21:03
danwentgaryk: just need a rebase, i assume now that arosen's patch is in?21:04
garykdanwent: correct21:04
*** zhuadl has joined #openstack-meeting21:04
danwentgreat.  once you do that, i'll bug dean to get the second devstack core review21:04
garykok21:04
danwentsecond is salv orlando's patch to let you specify --nic option again with v2 quantum: https://review.openstack.org/#/c/9295/21:04
danwentthis is pretty important to testing more interesting topologies21:05
danwentsalv-orlando: any update on this?21:05
salv-orlandoreviewers comments21:05
salv-orlandohave been addressed - waiting for another round of review21:05
danwentlooks like we already have the attention of a few nova core devs, which is great.21:05
*** jjm3 has joined #openstack-meeting21:05
danwentok, any other key reviews people want to call out (this is main reviews that may be holding up additional work)21:06
garykdanwent, salv-orlando: is this related to vnic or the nic of the agent21:06
danwentthis is to be able to specify the set of networks that a vm is connected to when it boots21:06
garykdanwent: thanks21:07
salv-orlandootherwise nova will just create interface on each network the tenant has access to21:07
salv-orlandoeach => every21:07
danwentOk, so I have a few items I'd like to discuss21:07
garyk:)21:07
gongyshello, https://review.openstack.org/#/c/9506/21:07
gongyswhat are these two different?21:07
danwentgongys: the difference is whether we allow IP address to be specified.21:08
danwentthis is a discussion we were having with tr3buchet (as I mention in my review comment)21:08
danwentthe concern is that we don't want every new thing that can be set on a quantum port (IP, security group, etc.) to be proxied through nova when a VM is created.21:08
danwentthus, the idea was that if someone wanted to customize their network connectivity, they would first create a port with exactly that connectivity via quantum, and then just passin the port-id when specifying the vNIC.21:09
gongysMy god, These two changes are submitted almost at the same time.21:09
gongysThey are trying to deal with the same problem.21:10
salv-orlandoWe should at least make sure that they do not conflict each other21:10
*** ncode has joined #openstack-meeting21:10
*** ncode has joined #openstack-meeting21:10
salv-orlandothen we can stack the larger patch set (9506 I believe) on top of the other one21:11
gongysBut these two are fixing same bug.21:11
danwentI think 9506 needs more discussion, about whether we want to support the fixed_ip attribute, or require that they pass in a port.  I could see making an exception for fixed_ip, but I am very nervious about having all quantum port attributes sent in via nova.21:11
danwentwe should loop tr3buchet into this discussion, as when I previously spoke with him, I think he was in favor of not supporting the fixed_ip field being passed in.21:12
danwentgongys or salv-orlando do you want to start a ML discussion on this?21:12
gongysI just want to avoid these duplication efforts.21:13
mesterydanwent: I agree with your concerns, and I think the model you propose around pre-creating the Quantum port seems reasonable.21:13
salv-orlandoyeah I am fine with bringing the discussion on ML21:13
gongysWhy do we have these two changes fixing the same bug?21:13
danwentare they both linked to the same bug?  or did we have duplicate bugs that led to duplicate fixes?21:13
salv-orlandoin lp terms not the same bug21:14
gongysSorry, I made a mistake.21:14
salv-orlandowe probably want to discuss in the ML whether they are actually the same bug or not according to semantics21:15
salv-orlandoI think not, but we probably want to move on as there's plenty to discuss today21:15
danwentah… ok.  well, at least there was some overlap there.  part of the confusion was probably about whether the bug should be filed in quantum or nova21:15
gongyshaha, they are not the same bug number.21:15
amotokione is nova bug and the other is quantum bug. They are not linked.21:15
danwenti agree.  let's move on, remember to always check for duplicates when you file a bug.21:16
rkukuraAnyone interested in extensions adding attributes to core resources, please comment on https://review.openstack.org/#/c/9849/ soon so we can decide whether to go forward with that approach and update the provider network patch set to use it.21:16
*** GheRivero has quit IRC21:16
salv-orlandorkukura: thanks I will look at the code later on today21:16
rkukuraLots of patch sets are touching the RESOURCE_ATTRIBUTE_LIST, including moving it out of router.py, so we'll need to coordinate.21:16
danwentsalv-orlando: can you kick off quick discussion with tr3buchet and gongys at least to resolve differences between the two patches?21:16
rkukurasalv-orlando: thanks21:17
danwentOk, next topic I wanted to bring up was about adding names to port and subnets, and their uniqueness21:17
danwenthttps://review.openstack.org/#/c/9836/21:18
garykdanwent: i think that if they are not unique then there is no point for the name - for example if one is to do a gui represntation of a network21:18
garykdanwent: it only leads to confusion21:19
danwentgaryk: I think the "standard" approach is that the user can decide if they want to keep them unique or not21:19
salv-orlandodan went, gongys, tr3buchet - I am happy to discuss it at anytime on irc, ML or w/e21:19
danwentthat is what nova does for servers, and what we currently do for networks.21:19
markmcclain+1 to letting user decide name uniqueness21:19
garykit is what we do, i do not think that it is very usable.21:19
danwentif a user decides to have two things named the same think, they likely need to click through to the details page to see a UUID and disambiguate in a gui, which I agree is cumbersome21:20
salv-orlandoI am with dan went on this. If we enforce name uniqueness then let's just get rid of uuid21:20
garykhow does the user decide? who can enforce this?21:20
*** matwood has joined #openstack-meeting21:20
garyki agree, one or the other. why both? it juest seems another column in the table that is a burden21:20
salv-orlandoon that node, I would not even make the name attribute mandatory (and make it non mandatory for networks as well)21:21
zhuadlWhat's the name used for?21:21
PotHixI have the same question21:21
danwentits really just an easier to remember/type display handle21:22
gongysName is more user-friendly21:22
salv-orlandoI guess for having something human-suitable on the client-side21:22
PotHixOk, so it makes sense to be optional IMHO21:22
ncode+1 on PotHix21:22
danwentin my experience, systems like this tend to have optional display names that are not-unique.21:23
PotHixmake*21:23
gongys+1 for optional21:23
danwentthis seems to be what nova does for servers, I'm not sure about other services within openstack.21:23
amotoki+1 for optional. it is useful.21:23
zhuadlIf it is only for human-suitable, then  uniqueness is not a must option.21:23
salv-orlandoI'll add my +1 - adding that we should make the name optional for networks too21:23
PotHixagree21:24
ncodesalv-orlando: I agree with you21:24
danwentgaryk: I think its up to you to try and convince folks otherwise.  Want to send an email to the list about it?21:24
garyki can live with the optional. +121:24
gongysHi, if we make network name optional, I have to run 'quantum network-create' instead of 'quantum network-create myname'21:24
gongyswhich means we don't need any arguments to create a network.21:24
salv-orlandoyep, create without any parameter will give you a network21:24
danwentgongys: but I assume there would be a --name=foo21:25
danwentoption?21:25
*** dolphm_ has quit IRC21:25
gongysYes. the name is going to become a optional argument.21:25
*** nati_ueno has quit IRC21:25
gongysSo we need nothing to create one network.21:25
PotHixLooks good to me :)21:26
zhuadlis there any problem here?21:26
danwentok.  please coordinate with devstack changes when pushing this into the client.  We'll also need to change the resource-map to make network name optional (maybe do this in same patch as adding name for port/subnet?)21:26
gongys+1 for optional network name.21:26
zhuadlwithout a name?21:26
gongysI will update my change.21:27
danwentzhuadl: can you clarify what you're asking?21:27
shivhIt is tough to associate a uuid of network in CLIs and UI21:27
danwentwhoops, realized I skipped an item on the agenda.  want to go back to talk about opentack-common updates.21:27
zhuadlI mean is there any problem without a name when creating a network?21:27
shivh-1 for optional21:27
shivhwe need netwotks with names (sorry) to be the bad guy.21:28
danwentshivh: is specifying --name=foo much more difficult?21:28
shivhuuid are difficult yo handle21:28
shivhthe assumption is not agreeable.21:28
shivhwhen you create a network you may want ot have a human readable name21:29
shivhlike (vlan3 based network)(21:29
danwentshivh: yes, that would still be possible.21:29
danwentOk, in the interest of time, shivh, please send your concerns to the ML21:29
danwentwe have a lot to cover still21:29
shivhwill do.21:29
danwentthx21:29
danwentgongys: i'm trying to figure out the issue with the two patches to update openstack-common21:30
danwentwe need to get this change in soon, as garyk pointed out that others things depend on it21:30
gongysdan, obviously without needing any information to create a network will lead to creating network unintentionally.21:30
danwentwhat is the key difference between the two?21:30
*** hggdh has quit IRC21:30
salv-orlandoI reckon gongs has a patch that is a superset of the other - but fixes some pep8 errors21:30
gongysI need notifier part too.21:31
danwentgongys: ok, so is the concern just that the other patch was proposed first?21:31
danwentbut does a subset?21:31
gongysI disabled pep8 check on openstack common codes.21:32
danwentgongys: yes, i think that's the right thing to do21:32
gongysI dealt with context problem in order to integrate the common code into our system.21:32
danwentespecially given that openstack-common folks do not seem to want to use latest pep8 version21:32
*** hggdh has joined #openstack-meeting21:33
garykdanwent, gongys: sounds reasonable. which patch will be used then. there are 2 conflicting patches21:33
gongysBut I am sorry to know there is another change trying to import the codes.21:33
gongysAt that time I am just gobbling the BP.21:34
garykgongys: the scalable agents got a -1 because it did not use the versioned RPC code (this also needs to be updated)21:34
danwentgongys: other one was proposed first, right?  and is someone new to the community?  are we able to merge that patch, and put yours on top?21:34
danwentor is it more complicated than that?21:34
gongysI agree, but that change is claiming to fix a bug which needs import the notifier part.21:35
danwentgongys: ok, could we merge it as a partial fix for that bug, then have you do the second half of the bug?  Otherwise, let's just merge yours in.  I just want to get this roadblock cleared.21:35
gongysOk.21:36
garykgongys: can you please make sure that you have the latest and greatest openstack codethen21:36
gongysof course.21:36
garyktx21:36
gongysI will redo the update.sh.21:36
danwentok, so we're going to approve Yaguang's patch, then apply gongys patch on top.  everyone in agreement?21:36
gongys+121:37
garyk+121:37
zhuadl+121:37
danwentgongys: looks like you'll be the second +2 on the patch.21:37
danwentok, great.21:37
gongys+221:37
danwentok, last (and probably trickiest) of the discussion points.21:37
salv-orlando-2 (sorry I just couldn't resist the temptation to troll :))21:37
danwentarghhh!21:37
danwent:P21:37
salv-orlandoplz go ahead21:38
mesterysalv-orlando: Party pooper!21:38
ncode+121:38
danwentnon-polling work for plugin agents, and dhcp21:38
garykiff names are key :)21:38
danwentgaryk has work related to making plugins more scalable21:38
danwentusing rpc calls, though we need to add more logic to trigger off of API changes to notifiy agents.21:39
garykdanwent: not sure if anyone saw - i wrote a mail to the list with some issues about the updates21:39
danwentgaryk: ok… actually, perhaps for something this complex, ML is better place to resolve anyway21:39
* salv-orlando saw the mail, starred it and will eventually read21:39
danwentgiven how long the meeting is running, how about we table that and just encourage folks to respond on the ML.21:39
garykthat would be great!21:40
danwenti think this is a key item to get consensus on though, as it will be used by plugins, dhcp-agent, and l3-agent21:40
danwent#help please check-out ML thread from garyk about scalable agents and respond with thoughts21:40
danwentok, moving on :)21:40
PotHixwill do21:40
PotHix:)21:40
garyki'll be happy to clarify if anyone needs further explanations. https://review.openstack.org/#/c/9591/ gives the basic idea21:40
danwent#info we're looking for people to contribute to the Quantum integration into horizon21:41
danwentI'm very worried that this isn't going to really land for Folsom, and it would be a shame if people didn't have a good graphical way to use Quantum21:41
danwentarvind has an initial patchset (https://github.com/asomya/horizon/tree/quantum-v2), but the GUI widgets he's created need to be hooked up to the Quantum client library.21:42
danwentthere's also a lot more work that we wanted to do in F-3, but first we need to get this base functionality in21:42
gongysIs there any problem to be hooked to the quantum client?21:42
*** johnpur has left #openstack-meeting21:42
danwentgongys: i think its pretty simple, he's just not familiar with any of the v2 stuff (and he's on vacation for two weeks now)21:42
danwentso no progress is being made.21:43
gongysI will have a look what is going on.21:43
zhuadlIs there any BP created for this work?21:43
danwentgongys: that woudl be awesome.21:43
amotokii will check the horizon code.21:43
danwentbp is at https://blueprints.launchpad.net/quantum/+spec/quantum-horizon21:43
gongyszhuadl, Do you want to take it?21:43
zhuadlI can also help to look at this.21:44
amotokiI just started to look the current asomya repository.21:44
danwentgreat… we could really use a few people familiar enough with horizon that we can expose new quantum functionality there once its available in the API21:44
danwent(in F-3 we'll also need to work on floating Ips and other l3 constructs)21:44
danwent#todo (again) dan create additional F-3 bps/bugs for horizon work21:45
danwentplease use the BP whiteboard to coordinate the work you're doing.  wouldn't want multiple people to do the same thing (resources are too precious for that)21:45
danwentwe can split up the blueprint into additional chunks if people think that is useful21:46
*** pballand has joined #openstack-meeting21:46
danwentok, anything else for F-3?21:46
gongyshow is the floating-ip feature going?21:46
danwentif you have a BP that is high or above and the status is unclear, I've probably already pinged you, or will be pinging you soon.21:46
danwentgongys: started on the spec over the weekend21:46
danwentif I don't have something by thursday, i'll give it up to you, deal? :P21:47
gongysN    O21:47
danwenti'm hoping to break it out into three major chunks, so multiple people can work on it21:47
gongys:)21:47
danwent:)21:47
danwent#topic community topics21:48
*** openstack changes topic to "community topics"21:48
danwentOk, i had a TODO that we should come up with a template for Quantum Specs21:48
garyki have an issue with devstack and linux bridge and dhcp21:48
danwentI haven't had time yet, so I'm curious if anyone wanted to volunteer for that.21:48
danwentotherwise, i'm creating a spec template as I do the L3 stuff, so we can go with that as well.21:49
danwentok, garyk go ahead21:49
garykdanwent: when i run devstack with v2 i ave issues.21:49
salv-orlandoI can do the spec template - and post it on the wiki.21:49
danwentsalv-orlando: ok, that would be great.21:50
garyk1. when using dhcp and linux bridge - the dhcp requets do not arrive at the dnsmasq device. could be iptables.21:50
garyk2. occasionally nova launches vms with vnics21:50
danwentyeah gongys and I have chatted about that.21:50
garykanyone else experienced this?21:50
amotokii also have the same issue.21:50
amotokithe same issue #1.21:50
danwentyou need to set the firewall drive to the NullFirewallDriver until we fix the bug we filed.21:51
danwentone sec21:51
*** kindaopsdevy has joined #openstack-meeting21:51
garykdanwent: i'll try21:51
gongysWe need use NullFirewallDriver driver for now since we have not yet exposed the right dhcp server ip.21:52
danwentgaryk: ok, i forget the exact syntax, but it was on that wiki page arosen sent out21:52
gongysI remember we have a BP for it.21:52
danwenthttps://blueprints.launchpad.net/quantum/+spec/expose-dhcp-server-ip21:52
zhuadlYes, I saw it.21:52
garykdanwent: cool, i'll take a look tomorrow. silly me should have written to list instead on gridning water with it21:52
danwentthen we'll need the quantum/nova integration code to pass that as part of the network object in nova, I think.21:52
danwentok, other communit topics21:53
gongysAbout notification event.21:53
garykgongys: configuration files21:53
danwentgongys: i see notifications as being a key part of the non-polling stuff, but that's part of what we need to discuss on the ML21:54
danwent(as notifications would need to be more fine-grained)21:54
danwentgongys: sorry, go ahead...21:54
gongysok, time is up, I prefer to do it on the ML.21:55
danwentbtw, 5 minutes to end of meeting21:55
danwentok, great21:55
danwentplease sign up for the next set of review days if you're a core dev (or even if you're not)21:55
danwenthttp://wiki.openstack.org/Quantum/ReviewDays21:55
danwentreview queue is starting to grow again, let's make sure we all pitch in to keep it manageable21:55
PotHixI'm reviewing a bit each day21:55
danwentand just another reminder to use the openstack-dev (not openstack) list for design discussions21:56
danwent#topic open discussion21:56
*** openstack changes topic to "open discussion"21:56
danwentany final questions (4 mins left)?21:56
ncodeDo we have anyone from quantum here at oscon?21:56
danwentncode: perhaps some of the dreamhost guys?21:57
salv-orlandofor public networks, please follow up discussion on the ML (I already owe garyk a reply)21:57
rkukuraAny change of an official quantum-2012.1.1 essex stable tarball soon?21:57
danwentunfortunately, i suspect people at oscon may be the same people missing the meeting :)21:57
danwentrkukura: garyk picked up the latest today.  after testing, we can definitely do a "release"21:57
rkukuras/change/chance/21:57
rkukuragreat21:57
markmcclainncode: we (Dreamhost) but I'm not sure who21:58
ncodedanwent: hahahaha I will look for them21:58
danwentok, thanks folks.  see you all next week!21:58
danwent#endmeeting21:58
*** openstack changes topic to "OpenStack meeting channel. See http://wiki.openstack.org/Meetings for schedule and http://eavesdrop.openstack.org/meetings/openstack-meeting/ for meeting logs"21:58
openstackMeeting ended Mon Jul 16 21:58:28 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-16-21.01.html21:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-16-21.01.txt21:58
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-16-21.01.log.html21:58
garykthanks and goodnight21:58
danwenthave a good afternoon, evening, morning :)21:58
PotHixThanks folks!21:58
*** markmcclain has left #openstack-meeting21:58
zhuadlenjoy yourselves!:-)21:58
amotokihave a good day!21:58
markvoelker'Night all!21:58
shivhbye21:58
ncodefalooo21:58
*** nati_ueno has joined #openstack-meeting21:59
*** shivh has quit IRC21:59
*** markvoelker has quit IRC22:00
*** rkukura has left #openstack-meeting22:00
*** anderstj has joined #openstack-meeting22:00
salv-orlandobye bye22:01
salv-orlandoadios22:01
*** dolphm has joined #openstack-meeting22:04
*** amotoki has quit IRC22:10
*** kindaopsdevy has quit IRC22:12
*** ncode has quit IRC22:17
*** metral_ has joined #openstack-meeting22:19
*** anderstj has quit IRC22:19
*** danwent has quit IRC22:19
*** salv-orlando has left #openstack-meeting22:20
*** metral_ has quit IRC22:20
*** danwent has joined #openstack-meeting22:22
*** metral has quit IRC22:23
*** sacharya has quit IRC22:25
*** dolphm has quit IRC22:26
*** joearnold has joined #openstack-meeting22:30
*** Gordonz has quit IRC22:30
*** ncode has joined #openstack-meeting22:33
*** ncode has quit IRC22:33
*** ncode has joined #openstack-meeting22:33
*** patelna_ has joined #openstack-meeting22:34
*** danwent has quit IRC22:37
*** patelna has quit IRC22:38
*** mattray has quit IRC22:43
*** nati_uen_ has joined #openstack-meeting22:53
*** dtroyer is now known as dtroyer_zzz22:53
*** danwent has joined #openstack-meeting22:55
*** nati_ueno has quit IRC22:56
*** danwent has quit IRC23:03
*** sacharya has joined #openstack-meeting23:06
*** ncode has quit IRC23:11
*** ncode has joined #openstack-meeting23:14
*** ncode has quit IRC23:14
*** ncode has joined #openstack-meeting23:14
*** dcramer_ has quit IRC23:17
*** danwent has joined #openstack-meeting23:19
*** danwent has quit IRC23:23
*** Mandell has quit IRC23:24
*** Mandell has joined #openstack-meeting23:37
*** mnewby has quit IRC23:38
*** danwent has joined #openstack-meeting23:38
*** dcramer_ has joined #openstack-meeting23:51
*** matwood_ has joined #openstack-meeting23:53
*** cp16net|away is now known as cp16net23:54
*** matwood has quit IRC23:57
*** patelna_ has quit IRC23:58
*** patelna has joined #openstack-meeting23:59
*** dtroyer_zzz is now known as dtroyer23:59

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