Wednesday, 2014-09-10

*** xgerman has quit IRC00:08
*** sbfox has joined #openstack-lbaas00:18
*** woodster_ has quit IRC00:25
*** markmcclain has quit IRC01:04
*** sbfox has quit IRC01:09
*** ptoohill-oo has quit IRC01:20
*** sbfox has joined #openstack-lbaas01:26
*** jroyall has joined #openstack-lbaas01:31
*** jroyall is now known as joeroyall01:31
*** joeroyall has quit IRC01:55
*** jroyall has joined #openstack-lbaas02:07
*** jroyall is now known as joeroyall02:07
*** jroyall has joined #openstack-lbaas02:09
*** joeroyall has quit IRC02:13
*** sbalukoff has quit IRC02:42
*** jroyall has quit IRC03:15
*** jroyall has joined #openstack-lbaas03:40
*** jroyall has quit IRC03:46
*** jroyall has joined #openstack-lbaas03:46
*** sbalukoff has joined #openstack-lbaas04:04
*** sbalukoff has quit IRC04:28
*** sbalukoff has joined #openstack-lbaas05:01
*** amotoki has joined #openstack-lbaas05:11
*** sbalukoff has quit IRC05:48
*** rm_you has quit IRC05:49
*** rm_you has joined #openstack-lbaas06:31
*** rm_you| has joined #openstack-lbaas06:33
*** jroyall has quit IRC06:36
*** rm_you has quit IRC06:37
*** jroyall has joined #openstack-lbaas07:46
*** sbalukoff has joined #openstack-lbaas07:54
*** jschwarz has joined #openstack-lbaas07:54
*** jroyall has quit IRC07:59
*** sbfox has quit IRC08:01
*** amotoki has quit IRC13:21
*** markmcclain has joined #openstack-lbaas13:40
*** markmcclain has quit IRC13:40
*** markmcclain has joined #openstack-lbaas13:41
*** woodster_ has joined #openstack-lbaas14:26
*** ptoohill has joined #openstack-lbaas14:36
*** xgerman has joined #openstack-lbaas15:00
*** jorgem has joined #openstack-lbaas15:00
*** jorgem has quit IRC15:02
*** sbfox has joined #openstack-lbaas15:03
*** xgerman has quit IRC15:08
*** xgerman has joined #openstack-lbaas15:10
*** sbfox has quit IRC15:31
*** mlavalle has joined #openstack-lbaas15:41
*** mlavalle has quit IRC15:42
*** mlavalle has joined #openstack-lbaas15:42
*** sbfox has joined #openstack-lbaas15:44
*** sbfox has quit IRC15:59
*** sbfox1 has joined #openstack-lbaas15:59
*** sbfox1 has quit IRC16:01
*** sbfox has joined #openstack-lbaas16:02
*** mestery has quit IRC16:10
*** mestery has joined #openstack-lbaas16:11
*** markmcclain has quit IRC16:12
*** jschwarz has quit IRC16:14
TrevorVdougwig, can I bother you with another tox issue I'm having?16:19
dougwigShoot.  I'm driving, so the reply might be delayed.16:23
TrevorVOkay sure thing.16:27
TrevorVoctavia.tests.unit.db.test_repositoryNon-zero exit code (2) from test listing.16:28
TrevorVerror: testr failed (3)16:28
TrevorVERROR: InvocationError: '../octavia/.tox/py26/bin/python setup.py testr --slowest --testr-args='16:28
TrevorVThat's the error I'm getting dougwig, and I have no idea what it means.16:28
TrevorVI forgot the --- import errors --- line16:28
TrevorVEither way, my IDE doesn't show any import errors, so any insight here?16:28
*** crc32 has joined #openstack-lbaas16:32
*** sbalukoff has quit IRC16:33
*** sbfox has quit IRC16:34
*** sbfox has joined #openstack-lbaas16:34
*** johnsom_ has quit IRC16:43
*** jroyall has joined #openstack-lbaas16:45
dougwigrun it with the py26 env; that one shows errors for some reason.16:45
dougwigand it looks like an import error.16:45
TrevorVYeah, dougwig, I'm still tinkering16:46
TrevorVLet me know when you're at a desk and I can tell you if I solved it or not :)16:46
dougwigi just got to my desk.  :)16:46
TrevorVperfect16:46
TrevorVIs "InvocationError" just some generic error they throw when something fails?16:47
TrevorVI'm confused... Meaning it doesn't look like it errored to invoke, since its run some tests and THEN fails.16:48
TrevorVI feel like the program doesn't throw the right error16:48
*** markmcclain has joined #openstack-lbaas16:51
dougwighalf the time i use strace to see the real error.16:53
dougwigi do not like how opaque testr is.16:53
TrevorVYeah, got it dougwig16:53
rm_workyeah testr output is shitty16:54
TrevorVI didn't explicitly say this, but I figured out the import error I had, now I just have to fix my tests16:54
*** jroyall has quit IRC17:14
*** ptoohill has quit IRC17:37
*** ptoohill has joined #openstack-lbaas17:37
*** crc32 has quit IRC17:49
*** ajmiller has joined #openstack-lbaas18:25
*** crc32 has joined #openstack-lbaas18:27
*** crc32 has quit IRC18:29
*** mlavalle has quit IRC18:33
*** mlavalle has joined #openstack-lbaas18:34
*** sbalukoff has joined #openstack-lbaas18:40
*** markmcclain has quit IRC19:09
*** jorgem has joined #openstack-lbaas19:15
*** rm_you|wtf has joined #openstack-lbaas19:16
*** rm_you| has quit IRC19:20
*** johnsom has joined #openstack-lbaas19:24
*** ptoohill has quit IRC19:28
*** markmcclain has joined #openstack-lbaas19:30
TrevorVThe meeting is going to be held in here again right?  No webex?19:35
TrevorVsbalukoff, ^^?19:35
xgermanNot today - but we can vote today to return to webex19:35
TrevorVxgerman, thanks, that's what I was getting at19:36
TrevorVI left my mac at home, and webex no happy on linux19:36
xgermanGoogle "hackintosh" "vmware", just saying19:36
*** jamiem has joined #openstack-lbaas19:37
TrevorVKeep your frivolous opinions to yourself, xgerman19:37
johnsomUgh-oh, I think I see the voting starting early...19:37
xgerman:-)19:37
*** VijayB has joined #openstack-lbaas19:46
sbalukoffHaha19:47
*** sballe has joined #openstack-lbaas19:52
rm_worklol19:53
*** vivek-ebay has joined #openstack-lbaas19:55
*** crc32 has joined #openstack-lbaas19:57
*** rohara has joined #openstack-lbaas19:58
*** dlundquist has joined #openstack-lbaas20:00
xgermano/20:00
sbalukoffWhoo-hoo!20:00
sbalukoffMeeting time!20:00
sbalukoff#startmeeting Octavia20:00
openstackMeeting started Wed Sep 10 20:00:13 2014 UTC and is due to finish in 60 minutes.  The chair is sbalukoff. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
openstackThe meeting name has been set to 'octavia'20:00
*** tmc3inphilly has joined #openstack-lbaas20:00
sbalukoffOk, folks!  This is our agenda for today:  https://wiki.openstack.org/wiki/Octavia/Weekly_Meeting_Agenda#Agenda20:00
*** jarendt has joined #openstack-lbaas20:00
sballeo/20:01
*** jarendt has quit IRC20:01
rm_worko/20:01
sballeI was on the wrong IRC ;-)20:01
TrevorVo/20:01
bloganhi20:01
crc32hello20:01
sbalukoff#topic Discuss: Use storyboard instead of launchpad for blueprints?20:01
johnsomo/20:01
roharahi20:01
rm_work(we should really have a "roll call" topic for a minute or so)20:01
*** davidlenwell has joined #openstack-lbaas20:01
tmc3inphillygood day20:01
masteinhausero/20:01
sbalukoffHaha!20:01
dlundquisto/20:01
davidlenwello/20:01
sbalukoffOk, so!20:01
*** juliancash has joined #openstack-lbaas20:01
blogandlundquist: you're back from iceland?20:01
dlundquistblogan: yep20:01
dougwigo/20:02
sbalukoffI would like to propose using StoryBoard for project management and blueprints instead of launchpad.20:02
*** jwarendt has joined #openstack-lbaas20:02
jamiemhi all20:02
bloganwelcome back!20:02
sballedlundquist, Where you on the plane the pilot took and flew around the volcano?20:02
rm_work"iceland? isn't that in finland?" --random person on Yahoo Answers20:02
dougwigsbalukoff: have you asked anyone in infra whether it's ready for that?20:02
xgermanstoryboard: https://wiki.openstack.org/wiki/StoryBoard/Roadmap20:02
xgermanthe lack of cross-outs make me +1 dougwig20:02
sbalukoffdougwig: I have not, but I do know that other "official" OpenStack projects already are.20:02
davidlenwellI've been using storyboard to manage refstack development for months now .. its been a lot better than trying to use launchpad20:03
dougwigsbalukoff: which ones?  have you talked to those folks?20:03
blogansbalukoff: according to that roadmap it looks like infra isn't ready for other projects, but I could be wrong20:03
johnsomI feel that we already have a start in launchpad and storyboard does not seem ready.  It looks like there are at least a few releases before they plan for projects to use it20:03
*** barclaac has joined #openstack-lbaas20:03
jwarendtHi everyone - new member of HP LBaaS team.20:03
*** markmcclain has quit IRC20:03
barclaacHi all20:03
bloganjwarendt: welcome!20:03
dougwigjwarendt: hiya, welcome20:03
sballeI agree storyboard is not ready as far as I know20:03
ajmillerHi, another new HP LBaaS Person here -- Al Miller.20:03
davidlenwellI dissagree .. I feel its ready for use..20:03
dougwigajmiller: hiya, welcome20:04
vivek-ebaywelcome20:04
sbalukoffI would say that launchpad is not ready as a tool for project management, but then I am opinionated.20:04
*** KunalGandhiEbay has joined #openstack-lbaas20:04
bloganarent we all20:04
davidlenwellsbalukoff: +220:04
sballebefore we switch I want to get a confirmaiton from Monty who is actually in charge of making StoryBoard happen20:04
sbalukoffI'm especially opinionated.20:04
johnsomLaunchpad is not great, but it has the basic features.20:04
xgermansballe +120:04
johnsomStoryboard is missing links to specs and subscriptions20:04
bloganill definitely want to move to storyboard, not sure now is the right time20:05
dougwigi'm of the opinion that whoever has to wrangle it for making milestones can make the call, but you'd better be ready to fall back, and not ride it into the ground of your opinionation.20:05
sbalukofflaunchpad is very clunky to use. It doesn't provide a good, standard way to split up blueprints into tasks and assign those tasks to different people.20:05
xgermansbalukoff we hear you20:05
sbalukoffIt doesn't provide any native mechanism to discuss a given blueprint. You have to turn to external systems for that which is a huge disruption in workflow.20:05
xgermanbut I am not in the camp anyhting is better than launchpad :-)20:06
rm_workI've been using launchpad for a bit with Barbican, and the auto-linkages and such seem to work fine, it might not be perfect but it definitely works -- i would vote to wait at least for a few remaining features in storyboard to show up and for confirmation that it's "ready for general use" from the maintainers20:06
bloganetherpad!20:06
sballesbalukoff, I am IM with mordred20:06
johnsomMilestone support in StoryBoard is still two releases out....20:06
dougwigwe're really talking launchpad+gerrit specs vs storyboard, right?20:06
sballeand the answer is "no. it's not ready for that yet"20:06
sbalukoffWe're still going to use gerrit.20:06
*** mordred has joined #openstack-lbaas20:06
mordredsup?20:06
dougwigbecause launchpad is nothing more than a link organizer, really.20:06
sballemy question was: @mordred Is storyboard ready? in our Octavia meeting today some people are talking about using Storyboard instead of launchpad. Does that even make sense20:06
sbalukoffIt would be StoryBoard + gerrit.20:06
mordredstoryboard is not ready yet20:06
mordredwe're getting close to moving infra on to it20:06
sballemordred, Thanks Monty20:06
mordredsorry - wish it was20:07
mordredit's getting close!20:07
dougwigmordred: thank you20:07
davidlenwellmordred: refstack has been using it successfully for a while20:07
dougwigsbalukoff: i can't support switching, given that.  :)20:07
barclaacLaunchpad it is then.20:07
xgermandougwig +120:07
mordredone sec20:07
rm_workdougwig +120:07
sballedougwig, +120:07
sballemordred, +120:08
sbalukoffmordred: Is there something else you wanted to add?20:08
johnsomdougwig +120:08
mordredyeah - hang on just a sec ...20:08
sbalukoffOk.20:08
tmc3inphillyis moving ot launchpad amid a very busy dev cycle worth the potential impact to velocity or can we get by with what we have for the near-term?20:08
mordredok. yeah. what I said20:08
blogantcm3inphilly: it really wouldn't be impactful of velocity, the move at least20:09
sballesbalukoff, I would like fo rus in the future not to make choice based on opinion but on facts.changing to StoryBoard could have been horrible for us at this point20:09
bloganif it isn't ready and it meltsdown then that woudl be an issue20:09
sbalukoffmordred: It would be less pain to switch now, while we really don't have much in launchpad. We're still bootstrapping this project. Does that change your opinion at all?20:09
*** ptoohill has joined #openstack-lbaas20:10
*** juliancash_ has joined #openstack-lbaas20:10
*** ptoohill has quit IRC20:10
*** ptoohill has joined #openstack-lbaas20:11
sbalukoffsballe: Ironically, we're making this decision based on the opinion of mordred. (Who is probably the most informed of us, but still, I hesitate to call it "fact.")20:11
sballemordred is in charge of the project so he is in the know He runs hte project20:11
bloganwell I think that roadmap wiki also backs it up20:11
rm_workwell, if someone came in and asked us to use LBaaS in production at our 0.5 milestone, what would we say? would it be opinion? :P20:12
*** juliancash has quit IRC20:12
sballesbalukoff, He has all the "facts" around storyboard20:12
sbalukoffsballe: Which is why we trust his opinion.20:12
bloganso its a very educated opinion20:12
sbalukoffblogan: Exactly.20:12
davidlenwellSo I actually have some facts here20:12
sballesbalukoff, Yes but again his opinion is backed up byfacts...20:12
sbalukoffAnyway, so:20:12
dlundquistI think we are getting off topic here20:13
*** krotscheck has joined #openstack-lbaas20:13
sballeI agree20:13
dougwigdlundquist: +120:13
roharadlundquist: agree20:13
xgermandlunquist +120:13
krotscheckeh? wha?20:13
sbalukoff#agreed we stick with launchpad for project managment for now.20:13
TrevorV+1 sbalukoff20:13
sballesbalukoff, Great! +120:13
davidlenwellfact 1 .. switching from lp to storyboard cause a marked increase in vilocity and orginization20:13
sballemordred, Thaks for jumping in with so short notice :-)20:13
sbalukoff#topic Vote on whether haproxy.cfg should be rendered in the amphora or the amphora driver20:13
sballesbalukoff, can you remind me the three options; Yes, No, abstain?20:14
dougwigi think we just cut off davidlenwell.  perhaps move that discussion to the ML?20:14
sbalukoffIs anyone not up to speed with the discussion which happened on the mailing list regarding this topic last last week?20:14
sballesbalukoff, +1 on speed up20:14
TrevorVsbalukoff, I'm not caught up in emails... I've been working on a blueprint really intimately :D20:14
blogandoes everyone know what an amphora is?20:15
xgermanor short amp20:15
rm_workI hope so :P20:15
dougwigoption 4: don't care as long as there is an interface in-between either way.20:15
barclaacIf not, then not eligible to vote :-P20:15
sballexgerman, -1 on amp20:15
dougwigand by interface, i mean driver.20:15
sbalukoffdougwig: So, I see two topics we should probably vote on.20:15
sbalukoffxgerman: Correct me if I'm wrong, but one of the central features of your argument is that you don't want an amphora driver layer, is that correct?20:16
sbalukoffIf so, then we should vote on that first.20:16
dougwigvotes are not consensus, and whether we structure it with an interface should not be a vote.  where we render it, i really don't care.20:16
sbalukoffWhere we render haproxy.cfg is actually a secondary problem.20:16
davidlenwelldougwig I was cut off.. but that is okay..  having actually ptl'd a project that successfully uses storyboard and never touched launchpad I do have a lot of information on the subject and am always happy to talk about it.. but if nobody wants to listen I won't waste my breath going on abou tit20:16
crc32what where the vote topics?20:16
sbalukoffcrc32: I'm introducing those now.20:17
sbalukoffxgerman: Do you want to say anything before we vote on that?20:17
xgermansure20:17
sbalukoffPlease be brief.20:17
sbalukoff:)20:17
xgermanI think that REST is a much better interface than some drive rin the comtroller. That doesn't preclude having drivers on the amphora20:18
*** markmcclain has joined #openstack-lbaas20:18
sbalukoffxgerman: That was discussed, in both models, the API on the amphora will be RESTful.20:18
blogani think the only thing that makes rendering on the controller, is that minor updates do not result it having to update thousands of amphora20:19
dougwigthat only works if every amphora implements the same rest interface.  that is horribly limiting.20:19
sbalukoffblogan: That's the second voting topic.20:19
bloganwell then im confused20:19
bloganwe're voting on whether we want a driver layer in the controller first?20:20
TrevorVsbalukoff, what is the first vote then exactly?20:20
sbalukoffSo here's what I see us voting on in a moment:  First vote will be:  Should we use a driver layer when interfacing with the amphora? Yes No Abstain20:20
bloganand then where the rendering is done second?20:20
xgermanworks for me20:20
sbalukoffSecond vote will be: Should we render the haproxy config on the controller / driver or on the amphora? Yes No aAbstain20:20
sbalukoffOk!20:20
bloganokay20:20
sbalukoff#startvote Should we use a driver layer when interfacing with the amphora? Yes No Abstain20:20
openstackBegin voting on: Should we use a driver layer when interfacing with the amphora? Valid vote options are Yes, No, Abstain.20:20
openstackVote using '#vote OPTION'. Only your last vote counts.20:20
crc32#abstain20:20
sbalukoff#vote Yes20:20
blogan#vote Yes20:20
dougwig#vote Yes20:20
rm_work#vote Yes20:20
TrevorVsbalukoff, forgive me, but wouldn't the voting be moot if we don't vote to have a driver?20:20
barclaac#vote Yes20:20
TrevorV#vote Yes20:20
sbalukoffTrevorV: No, it's unrelated.20:20
sballe#vote Yes20:21
crc32#vote abstain20:21
xgerman#vote No20:21
rohara#vote Yes20:21
davidlenwell#vote Yes20:21
dlundquist#vote No -- This will require defining an additional interface this early in development20:21
tmc3inphilly#vote Yes20:21
jamiem#vote No20:21
openstackdlundquist: No -- This will require defining an additional interface this early in development is not a valid option. Valid options are Yes, No, Abstain.20:21
sbalukoff60 seconds until voting is closed.20:21
rm_worklol dlundquist20:21
dlundquist#vote No20:21
xgermandlundquist +120:21
dougwigi'm glad i didn't editorialize mine.20:21
johnsom#vote abstain20:21
ajmiller#vote No20:21
sballedougwig, lol20:22
sbalukoff#endvote20:22
openstackVoted on "Should we use a driver layer when interfacing with the amphora?" Results are20:22
openstackYes (10): rm_work, sballe, tmc3inphilly, sbalukoff, TrevorV, barclaac, dougwig, rohara, davidlenwell, blogan20:22
openstackAbstain (2): crc32, johnsom20:22
openstackNo (4): xgerman, dlundquist, ajmiller, jamiem20:22
sbalukoffOk, So we're using a driver layer.20:22
sbalukoffNext vote...20:22
sbalukoff#startvote Shoud we render the haproxy.cfg in the driver layer or the amphora? Driver Amphora Abstain20:23
openstackBegin voting on: Shoud we render the haproxy.cfg in the driver layer or the amphora? Valid vote options are Driver, Amphora, Abstain.20:23
openstackVote using '#vote OPTION'. Only your last vote counts.20:23
blogan#vote yes20:23
openstackblogan: yes is not a valid option. Valid options are Driver, Amphora, Abstain.20:23
dougwig#vote Abstain20:23
sbalukoff#vote Driver20:23
rm_work#vote Driver20:23
dlundquist#vote Driver20:23
barclaac#vote Amphora20:23
sballe#vote Driver20:23
blogan#vote Driver20:23
TrevorV#vote Driver20:23
xgerman#vote Amphora20:23
crc32#vote abstain20:23
tmc3inphilly#vote Driver20:23
rohara#vote Driver20:23
ajmiller#vote Amphora20:23
davidlenwell#vote Driver20:23
crc32#vote driver20:24
sbalukoff60 seconds until voting is closed20:24
*** krotscheck has quit IRC20:24
VijayB#vote Amphora20:24
johnsom#vote abstain20:24
sbalukoff#endvote20:25
openstackVoted on "Shoud we render the haproxy.cfg in the driver layer or the amphora?" Results are20:25
openstackAmphora (4): xgerman, barclaac, ajmiller, VijayB20:25
openstackAbstain (2): dougwig, johnsom20:25
openstackDriver (10): rm_work, tmc3inphilly, sbalukoff, TrevorV, sballe, dlundquist, crc32, rohara, davidlenwell, blogan20:25
sbalukoffOk, we're rendering the haproxy.cfg in the driver20:25
VijayBmy vote's assuming that hopefully, coming in late, I understand Amphora right20:25
juliancash_#vote Abstain20:26
dougwigamphora == vm/container/backend/appliance.20:26
sbalukoffVijayB: you can see the discussion on this on the mailing list.20:26
sbalukoffCrap, did we just have a netsplit?20:26
bloganthe amphora is a vase20:26
sbalukoff:)20:26
crc32yea a netsplit right in a vote too.20:26
blogani think the vote captured everyone's vote20:26
sbalukoffI think it did, too.20:26
sbalukoffFrom what I can tell.20:26
dlundquistnet split?20:26
*** dlundquist has quit IRC20:26
*** dlundquist1 has joined #openstack-lbaas20:26
sbalukoff:P20:26
VijayBdougwig, blogan: thanks - so, is it the controller or the backend VM that will run haproxy?20:26
dougwigVijayB: backend VM20:27
VijayBsbalukoff: Yes, I'll take a look at the MLs...20:27
sbalukoff#topic Vote on whether we should keep meetings in IRC or move back to webex20:27
rm_work...20:27
bloganVijayB: i was being sarcastic, a sore loser, the amphora is the VM that is hosting the haproxy instance20:27
crc32#vote abstain20:27
bloganinstances20:27
dlundquist1#vote IRC20:27
davidlenwell#vote IRC20:27
sbalukoffcrc32: Hold on20:27
bloganvote hasn't started it20:27
VijayBdougwig: ok, how many entities will actually update a single amphora?20:27
dougwiglol20:27
sbalukoffI actually need to start the vote.20:27
rm_work#vote IRC20:27
sballe;-)20:27
barclaac#vote abstain20:28
*** dlundquist1 is now known as dlundquist20:28
blogansbalukoff: hold up lets make sure VijayB understand what the amphora is20:28
dougwigVijayB: likely multiple api controllers, similar to neutron-server20:28
sbalukoffThe topid hasn't been changed yet, so I think the bot got split20:28
xgerman#vote webex20:28
sballe#vote webex20:28
vivek-ebayhold on20:28
davidlenwellyou can't use webex and expect other developers in openstack to participate20:28
davidlenwellperiod..20:28
TrevorVYou guys realize he has to start the vote still right?  H aha20:28
barclaacsbalukoff - start the vote already :-)20:28
davidlenwellif you want larger community support you have to have irc meetings.20:28
sbalukoffbarclaac: Ok, I'll try, but I think the bot got netsplit20:29
xgermanI though he was counting with his fingers20:29
crc32let the votehappen. IRC is gonna win anyways.20:29
bloganup up down down left right left right a b select start20:29
TrevorVdavidlenwell, hence one of the reasons to vote for keeping it IRC or not.20:29
sbalukoff#startvote Where should we hold our weekly meetings? IRC Webex Abstain20:29
openstackBegin voting on: Where should we hold our weekly meetings? Valid vote options are IRC, Webex, Abstain.20:29
openstackVote using '#vote OPTION'. Only your last vote counts.20:29
TrevorV:)20:29
dougwig#vote IRC20:29
dlundquist#vote IRC20:29
rm_work#vote IRC20:29
VijayBdougwig, blogan: Ok.. so we can have multiple controllers firing off simultaneous requests for haproxy.cfg rewrites - these would need to be serialized at some place... one place to do that is the MQ, the other, in the VM running the haproxy..20:29
barclaac#vote abstain20:29
sbalukoff#vote Abstain20:29
blogan#vote IRC20:29
TrevorV#vote Abstain20:29
crc32#vote abstain20:29
rohara#vote IRC20:29
tmc3inphilly#vote IRC20:29
xgerman#vote Webex20:29
davidlenwellI do not understand why this is even a question20:29
dlundquistI will point out that holding this vote on IRC does result in a certain bias20:29
jamiem#vote IRC20:29
roharadavidlenwell: +120:29
rm_workdavidlenwell: me either but we vote because we vote20:29
ajmiller#vote abstain20:29
johnsom#vote IRC20:29
jamiemdlundquist: +1 :)20:29
jwarendt#vote abstain20:30
sbalukoffdlundquist: We've held the vote in webex, on gerrit and now on IRC.20:30
dougwigdlundquist: similar to how it went when we held it in webex?  :)20:30
sbalukoffSo, we have all flavors of bias represented.20:30
VijayBI'm confused about what all the voting is for :'(20:30
rm_workVijayB: where our meetings are20:30
sbalukoff60 seconds until voting closes20:30
VijayBrm_work: ok :)20:30
dlundquistyeah, atleast I dont' need a VM to join these meetings20:30
rm_workif we continue to hold the meetings on IRC, or if we go back to holding meetings on Webex20:30
VijayB#vote IRC20:30
sballe#vote wenex20:30
openstacksballe: wenex is not a valid option. Valid options are IRC, Webex, Abstain.20:30
davidlenwelldlundquist: +220:30
sballe#vote wenex#vote webex20:30
openstacksballe: wenex#vote webex is not a valid option. Valid options are IRC, Webex, Abstain.20:30
TrevorVdavidlenwell, all I can say is both have pros and cons, and in this case we're voting to see where it ends up.  Whether or not you understand its necessity is irrelevant at this point20:30
sballe#vote webex20:30
rm_work:P20:31
sballeTrevorV, +120:31
tmc3inphillyICQ?20:31
rm_workwoo20:31
davidlenwellicq meetings for the win20:31
crc32telegraph20:31
sbalukoff#endvote20:31
openstackVoted on "Where should we hold our weekly meetings?" Results are20:31
davidlenwellpony express20:31
openstackAbstain (6): jwarendt, sbalukoff, TrevorV, barclaac, ajmiller, crc3220:31
openstackIRC (9): jamiem, rm_work, tmc3inphilly, johnsom, dougwig, VijayB, dlundquist, rohara, blogan20:31
sbalukoffHAHA20:31
openstackWebex (2): xgerman, sballe20:31
TrevorV#vote morse-code20:31
sbalukoffOk, so, It looks like IRC wins.20:31
bloganwebex is dead!!!!!!!! hip hip hooray!20:31
davidlenwellyay20:32
blogansorry20:32
sbalukoffSo, we'll be keeping our meetings in IRCS for the time being.20:32
xgermanwell, I need to work on my writing skills then :-(20:32
dougwigwe should likely move these meetings to a slot on the actually meeting channels at some point.20:32
rm_workwe can still use webex/gchat for day to day discussions on the fly...20:32
sbalukoff#topic Discuss use of Pecan, WSME, and jsonschema for the API20:32
TrevorVsbalukoff, I have one question first20:32
TrevorVBefore we switch to this20:32
sbalukoffTrevorV: Ok.20:32
dougwigsbalulkoff, type "#undo"20:32
sbalukoff#undo20:32
xgermanrm_work this is like you still finished the race20:32
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x326b050>20:32
sballeblogan, When we do IRC meetings we neve discus thing in a lot of details and laways end up differing to the ML where nothing happens. the few time we have met in webex/google hangout we have been better at making decidsion20:32
rm_workxgerman: lol20:33
dlundquistsbalukoff: could you clarify which API we are talking about20:33
TrevorVThe meeting minutes are different than the recordings of the conversations in the meeting, right?20:33
rm_workxgerman: I got that a lot as a kid <_<20:33
TrevorVAre both captured by the bot?20:33
rm_workduring, you know, actual races20:33
*** sbfox has quit IRC20:33
blogansballe: i nkow and when something needs to be discussed that in depth we should do a webex20:33
sbalukoffdlundquist: Can we wait until open discussion to talk about that?20:33
dougwigTrevorV: yes20:33
sbalukoffTrevorV:20:33
sbalukoffYes.20:33
sbalukoffHaha20:33
rm_work#trevorv Yes20:34
sbalukoffYes, so, the meetbot makes "minutes" which are just a summary of the stuff we explicitly tell it to log with #commands20:34
TrevorVsbalukoff, dougwig, awesome, okay.  I was just going to ask if it would be necessary for me to write up the meeting notes or not still.20:34
TrevorVLooks like I don't have to do that :D20:34
bloganyou sound like you enjoyed doing that20:34
rm_workhe did20:34
sbalukoffTrevorV: You don't have to do that, but if you want to, that's certainly welcome.20:34
dougwigTrevorV: check out the links after stephen does the end meeting, or browse eavesdrop.openstack.org20:34
rm_workI think we should still make him do it20:34
TrevorVHonestly, it helped me learn quite a bit more than I would normally20:34
dlundquistsbalukoff: I just wanted clarification on what which API was meant by "the API", operator facing, internal (controller - amphora) or both20:34
crc32rm_work: I agree20:34
xgermantrevorV you should have voted webx -- wonder what blogan is paying you guys :-)20:34
blogandlundquist: operator20:34
bloganfor now at least20:35
sbalukoffTrevorV: Your meeting minutes are higher quality than the ones auto-generated by the meetbot.20:35
bloganlol20:35
dlundquistblogan: thanks20:35
sbalukoffMostly because I suck at remembering to tell it what to log.20:35
TrevorV#action TrevorV to suck it up and make meeting minutes anyway20:35
sbalukoffHaha!20:35
barclaacsbalukoff can we discuss the single driver per controller we discussed last week?20:35
dougwigthe quality of the irc minutes is in large part controlled by the use of the meta tagging by the chair.  :)20:35
rm_work#startvote Should TrevorV still have to make IRC minutes? Yes Abstain20:35
openstackOnly the meeting chair may start a vote.20:35
sbalukoffbarclaac: Let's do that after the next topic.20:35
barclaack thx20:35
bloganok we're getting off topic now20:36
sballe#vote yes20:36
sbalukoff#topic Discuss use of Pecan, WSME, and jsonschema for the API20:36
bloganokay20:36
rm_work:P20:36
sbalukoff#chair blogan20:36
openstackCurrent chairs: blogan sbalukoff20:36
sbalukoffGo for it, eh!20:36
bloganso I don't think we need to use jsonschema yet because from what I can tell so far WSME's built in validation will give us what we need20:36
bloganalso I am going with Pecan adn WSME since it appears that is what the newer projects are going with20:37
blogandoes anyone have any issues with that?20:37
sbalukoffblogan: None from me!20:37
dougwigi'm good with that.  pecan was announced as the new standard at the last summit20:37
sballeblogan, What are the other OpenStack project using? I have hear a lot abut PECAN20:37
davidlenwellblogan: I don't think that wsme pecan is a bad idea.. but I also dissagree that we should choose a technology just because "its what the other projects are doing"20:37
davidlenwellso the merrits of each should be discussed20:38
sbalukoffdavidlenwell: +120:38
blogansballe: the newer ones are using Pecan, and I believe a lot are using WSME20:38
xgerman+120:38
vivek-ebayPECAN +120:38
sballeblogan, thx20:38
bloganthe older projects are supposed to switch to pecan20:38
TrevorVdavidlenwell, that argument is somewhat invalidated by your IRC opinion earlier ;)20:38
sballePECAN+1 since that is where the OpenStack tooling is going20:38
xgermanhe can change his mind :-)20:38
blogandavidlenwell: you're correct and thats why I am bringing it up here, it is what I have chosen, but I would like people to voice their concerns about it20:39
dougwigdavidlenwell: eh, it's a rest framework, not exactly the height of innovation.  debating them tends to come to personal biases, when it's mostly six and one-half dozen.  now if we can talk about using ruby...20:39
davidlenwelllol20:39
* blogan kicks dougwig20:39
sballe:-)20:39
* davidlenwell facepalms20:39
*** dlundquist has quit IRC20:40
* TrevorV kicks dougwig after blogan 20:40
bloganso does anyone have any concerns about it?20:40
sbalukoffblogan: Do you want to vote on this, or are you comfortable just going with Pecan?20:40
dougwigtrolling aside (though i do love ruby), i think there is value in standardizing on the commodity libraries.20:40
bloganHP people I know you use pecan and possibly wsme in libra, any issues you've had that might make this a bad choice for us?20:40
xgermandougwig +120:40
sbalukoffblogan: I'm not really hearing any objections.20:40
xgermanwell, SSL was sketchy20:40
*** rm_work has quit IRC20:40
sballedougwig, +120:41
*** rm_work has joined #openstack-lbaas20:41
*** rm_work has quit IRC20:41
*** rm_work has joined #openstack-lbaas20:41
bloganxgerman: because of pecan or wsme?20:41
davidlenwellI don't object20:41
*** dlundquist has joined #openstack-lbaas20:41
xgermanmore because it needs to run in some app server20:41
davidlenwellI've done apis for projects with flask, pecan .. it is largly 6 one way half a dozon the other20:42
xgermanalso the wsme syntax needs getting used to. Flask, etc. are more clear20:42
TrevorVI'm confused, is anyone against Pecan/WSME?20:42
ctracey+1 davidlenwell20:42
davidlenwellno20:42
sbalukoffTrevorV: I don't think so.20:42
bloganxgerman: agreed and I prefer flask's but pecan isn't so bad now, its just different than flask20:42
TrevorVThen what is the discussion covering right now?20:42
davidlenwellI wrote the original python libra api with it for a reason20:42
johnsomI have no issue with pecan20:43
xgermanwe are talking wsme20:43
crc32#vote abstain20:43
sbalukoffblogan: Anything else you want to discuss here, or would it be OK to move on to the next topic?20:43
xgermanbut I bow to what OpenStack decided20:43
TrevorVxgerman, WSME as in pro/con WSME?  or alternatives to it?20:43
blogansbalukoff: I have another, but I'll add it to the end if we have time20:43
sbalukoffblogan: Ok.20:43
blogansounds like no vote is needed though20:44
sbalukoff#topic dlundquist's question about APIs20:44
bloganalready answered20:44
sbalukoffOk,20:44
dlundquistI already did -- just wanted clearification on which API previous was discussing20:44
*** sbfox has joined #openstack-lbaas20:44
sbalukoff#topic barclaac discussion of multiple controllers idea20:44
sbalukoffbarclaac: Go for it!20:44
blogansingle driver on controller!20:44
dlundquistblogan: +1 as a starting point20:45
xgerman+120:45
sballeblogan, +120:45
barclaacRight. So given we were originally talking about controllers having multiple drivers20:45
dlundquistonce we have that working we can move on20:45
sbalukoffAgreed, as a starting point.20:45
johnsomblogan +120:45
barclaacit seems to be a simplification to restrict to a single driver.20:45
blogandlundquist: i was more clarifying, but yes single driver only at first, until octavia is more mature20:45
crc32#vote abstain20:45
barclaacIf you want another driver type at the same time then start a new controller20:45
roharablogan: +120:45
xgermanbaclaac +120:45
sbalukoffbarclaac: How does the user / operator API know which controller to talk to?20:46
VijayB-1 for having to start a new controller for a new driver type20:46
dougwigmildly dislike, but accept the initial simplification.20:46
barclaacwe'll have multiple controllers in the system anyway so this makes it much simpler but doesn't prevent multiple driver types20:46
sballe+120:46
VijayBthat could get restrictive20:46
rm_workVijayB +1, not sure why that's a good ideas20:46
rm_work*idea20:46
VijayBneutron already supports multiple driver types doesn't it? So why do we need to limit ourselves?20:46
barclaacWe've got to look in the DB anyway to figure out which controller because not every controller knows every LB20:47
sbalukoffbarclaac: So are you proposing to use a dispatcher-like service (ie. as in the v1.0 preliminary design document) for determining which controller to talk to?20:47
xgermanwell, if you have a controller running driver A and B -- you have to restart the controller just to update driver A even if B stays the same20:47
barclaacRight20:47
sbalukoffOk.20:47
rm_workController is for the Amphora type (VM / Container / etc), Driver is for the Software inside the Amphora (HAProxy, nginx, etc), right?20:47
VijayBeach type can have its own implementation of the plugin_driver that will let it choose the appropriate driver20:47
dougwigxgerman: driver changes are rare, so that's not a big deal.20:47
xgermanI disagree20:48
dougwigrm_work: no20:48
rm_workdougwig: ok, maybe I need another explanation for this then20:48
roharawe're talking about 0.5, though, right? seems like everyone agrees that this would be a simplifcation that can be address lates20:48
sbalukoffrm_work: No20:48
barclaacIt's the 90% solution.20:48
rm_worksbalukoff: yes, dougwig just said that. WTB clarification :P20:48
dougwigcontroller (api) has driver (talks to amphora).  amphora might have a driver layer, but that's outside the scope of this discussion.20:48
barclaacIf the 10% is an issue we can go to multiple drivers later20:48
rm_workhmm k20:49
sbalukoffrohara: +120:49
xgermanI guess we should vote agian. people didn't know what they were voting for/against :-)20:49
blogani think the best solution is to go with a single driver right now, and explore whether the controller can handle multiple drivers easily when octavia is more mature20:49
TrevorV+1 barclaac20:49
sbalukoffrm_work: Sorry, catching up on reading.20:49
roharablogan: +120:49
rm_workdougwig: but the driver doesn't know whether the Amphora is a comtainer or VM right?20:49
dougwigbarclaac: i think it's the 30% solution, but i'm mildly ok with it initially because that's more than the 0% we have now.20:49
TrevorV+1 blogan20:49
rm_workdougwig: the controller is in charge of that?20:49
sbalukoffblogan: +120:49
VijayBcan someone confirm/edit this workflow: neutron-controller->neutron octavia driver -> octavia controller -> driver on amphora ?20:49
sbalukoffdougwig: +120:49
dougwigthe driver is the only part of the controller that knows the details of the amphora.20:49
dougwigrm_work:20:49
rm_workdougwig: so the *driver* is actually in charge of spinning up the Amphora?20:50
sbalukoffVijayB: That's correct, from a high level.20:50
barclaacVijayB you missed the dispatcher20:50
rm_workdougwig: and ALSO in charge of configuring the software inside it?20:50
dougwigrm_work: no.20:50
sbalukoffbarclaac: Dispatcher doesn't come into play until v1.020:50
VijayBbarclaac: which dispatcher is this? Within neutron?20:50
rm_workdougwig: what layer spins up the Amphora (VM / Container / etc)?20:50
sbalukoffVijayB: It's in the 1.0 design.20:50
dougwigrm_work: that's the controller.20:50
rm_work...20:50
barclaacVijayB an additional component in sbalukoff's arch. Listen to him, not me (one time offer only ;-)20:50
rm_workand what layer communicates with the software inside it (HAProxy, nginx, etc)?20:51
sbalukoffVijayB: So, it doesn't really affect the v0.5 workflow per se, though it is probably where we will end up in later versions.20:51
rm_workdougwig: ^^20:51
VijayBsbalukoff: ok20:51
dougwigrm_work: that's up to the driver/amp combo.20:51
rm_workdougwig: so then that's exactly what I said in the beginning :P maybe I just didn't word it well20:51
sbalukoffrm_work: There will be a RESTful agent on the amphora20:51
sballesbalukoff, +120:51
rm_workright20:51
VijayBsbalukoff: so now the voting will be for how many octavia driver instances do we support in the neutron controller to talk to the octavia controller?20:51
barclaacAll I'm trying to do with the single driver approach is to simplify to make the 0.5 actually happen with a speed that doesn't get me fired.20:51
rm_workso the Controller spins up the Amphora (as a VM / Container / etc), the Driver renders the config for the Software inside the Amphora (HAProxy, nginx, etc) and passes it to the Amphora20:52
xgermanok, I think we agreed on that20:52
bloganbarclaac: i think we're all in agreement to not worry about multiple drivers until after 0.520:52
sbalukoffVijayB: I'm hoping we don't have to vote on that just yet. I don't think the project is mature enough to need to decide that yet.20:52
sbalukoffbarclaac: +120:52
dougwigrm_work: yes.20:52
rm_workok20:52
bloganand if after 0.5 we decide multiple drivers is not worth the hassle, we won't do it20:52
rm_workthat's exactly what I was trying to say originally20:52
rm_workI guess my wording was just slightly off20:52
xgermanyeah, but you voted for irc :-)20:53
rm_workI just made it a little bit more clear :P20:53
barclaacblogan +120:53
johnsomrm_work, yes, that is my understanding20:53
xgermanblogan +120:53
sbalukoffPlease tell me if this is incorrect:20:53
sballesbalukoff, Can we agree to postpone this decision until after 0.5? and do 1 driver for 0.5?20:53
rm_worksballe: I'd vote for that :)20:53
xgermansballe +120:53
sbalukoff#agreed We will develop a single driver per controller for the v0.5 release, re-evaluate afterward.20:53
xgermanyeah!!20:53
sballe!!!20:53
openstacksballe: Error: "!!" is not a valid command.20:53
barclaacSo let's vote on the 0.5 decision and that we'll revisit for 1.020:53
dougwigi think we have full consensus.20:54
rm_workbut... voting20:54
bloganyes we do20:54
sballedougwig, I agree20:54
rm_workwe just got the voting stuff working :P20:54
sballe;-)20:54
sbalukoffOk!20:54
xgermanyeah, it's exciting20:54
* rm_work wants to #vote20:54
dougwigwhen you've got a hammer...20:54
sbalukoffOnly 5 minutes left... so...20:54
barclaacdougwig +120:54
sbalukoff#topic blogan's next question20:54
sbalukoffFeel free to change that topic. ;)20:55
blogan#topic support json only, and json format20:55
rm_work#vote Yes20:55
blogantopic not working20:55
sbalukoffI think it is.20:55
sballesbalukoff, I have a question around hte Paris design summit sessions.Has anybody heard anythign about any deadlines/20:55
sbalukoffMaybe?20:55
sbalukoffI dunno.20:55
blogani eblieve we had an unofficial consensus before, but do we want to support xml?20:55
xgermanno xml20:56
sballexgerman, +120:56
sbalukoffblogan: So, I think that it should be valid for someone to develop some interfaces that are not RESTful if they can justify it.20:56
bloganok better question, does anyone feel strongly about supporting xml?20:56
johnsomxgerman +120:56
ajmillerxgerman +120:56
sbalukoffLike the HMAC-signed UDP health checks and whatnot.20:56
xgermanfor the operator API?20:56
barclaacblogan: I feel strongly about not supporting xml :-)20:56
sbalukoffBut otherwise, we should default to RESTful unless deviation from that is justified.20:56
sbalukoffAnd yes, XML is the devil.20:56
bloganbarclaac: i think most of us do20:56
xgermansbalukoff that would be up to the driver how to talk to the amphora20:56
sballesbalukoff, +120:56
bloganok just making sure nobody really wants it20:57
bloganalso20:57
sbalukoffxgerman: True.20:57
bloganabout json20:57
barclaacASN.1 ?20:57
sbalukoffxgerman: but for the drivers we write, let's follow that standard. :)20:57
xgerman\me likes them to be asynchronous and update the db straight20:57
sbalukoff#agreed XML is the devil and should die in a fire.20:57
bloganwhat format do most people prefer: {"load_balancer": {"name": "some load balancer"}} or {"name": "some load balancer"}20:57
dougwigxml is a child of the 00's.20:57
rm_workblogan: root tags?20:58
bloganyes20:58
blogani dont now if that is the official name, but thats what i call them20:58
rm_workBarbican does not use root tags20:58
rm_work(for POSTs)20:58
dougwigi prefer no root tags, and then adding them to batch api calls as needed (i.e., if you add a call that fetches the entire LB tree, they go in there.)20:58
rm_workit DOES return with root tags20:58
dougwigyuck.  it should post what it returns.20:58
bloganrm_work: i don't like that inconsistency20:59
rm_workit makes sense when you're using it20:59
bloganI'm fine with either, but it should be consistent20:59
sbalukoffIsn't root-tagging in some ways less DRY?20:59
blogansbalukoff: yes, bc the resource is in the url20:59
sbalukoffI mean, don't you know it's a "loadbalancer" from the URL?20:59
dougwigit's redundant, for sure.20:59
sbalukoffRight.20:59
xgermanwe have one minute - ML?21:00
sbalukoffSo, no root tags. :)21:00
sbalukoffxgerman: Yeah, ML.21:00
roharaI like root tags, but I do not feel strongly21:00
rm_workoh, hmm maybe it doesn't... wonder why i was getting root tags on GET before in python21:00
blogani still like them because pulling from the url isn't as easy as just parsing json21:00
rm_workwell, ignore me then -- Barbican uses no root tags21:00
sbalukoffOk, we've got to end the meeting.21:00
sbalukoff#endmeeting21:00
bloganrm_work: ignored you long ago21:00
openstackMeeting ended Wed Sep 10 21:00:40 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/octavia/2014/octavia.2014-09-10-20.00.html21:00
dougwigblogan: do you forget where you are regularly?21:00
dougwig:)21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/octavia/2014/octavia.2014-09-10-20.00.txt21:00
rm_workblogan: :P21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/octavia/2014/octavia.2014-09-10-20.00.log.html21:00
blogandougwig: where am I regularly?21:00
rm_workwe don't *have* to end the meeting, technically, because this is our channel :P no other meetings here21:00
bloganthe bathroom?21:01
rm_workbut whatever21:01
sbalukoffrm_work: I'm trying to respect the time of people who need to go do other stuff now.21:01
dougwigback to launchpad vs storyboard... too bad we can't use trello in the interim.21:01
sbalukoffdougwig: Agreed.21:01
rm_workBTW: my Neutron-LBaaS action item from last week is not done because the keystone folks keep messing up my plans21:01
rm_workwhat with their "information about how the system works" >_>21:01
dougwigkneecap 'em.21:01
sbalukoffdougwig: Too bad we can't use a text file we e-mail to each other. Seriously, could they have made a worse interface than launchpad?21:01
sballedougwig, What's trello?21:01
rm_workI will need to bring up the interaction model in the meeting I think21:02
roharabreaking news ...21:02
xgermantrello is some distributed todo.project management app21:02
dougwigsballe: a free but commercial storyboarding/agile planner.21:02
blogansbalukoff: yes, rm_work's computer science professor "Dr. Web"21:02
rm_worklol21:02
sbalukoffblogan: HAHA!21:02
sballeoh cool! BTW I am all for moving away from launchpad21:02
sballewhen the time is ready21:02
rm_worksame21:03
blogansballe: +121:03
blogani don't like launchpad either21:03
sballeneither do I.21:03
bloganand storyboard looks like its shaping up nice21:03
bloganly21:03
sbalukoffWell, in the mean time, I'm going to try to sort-of use launchpad as I would StoryBoard. :P21:03
sballe:-)21:03
dougwigi'd be interested in a smaller group getting the details of mordred's "not ready", and combining that with davidlenwell's successful use of storyboard, and then letting the main user of the tool pick his poison.21:03
sbalukoffStoryBoard honestly feels like it's got enough features to be really useful to us right now. :P21:03
sbalukoffBut, eh... I'll go with the majority on this.21:04
dougwigsbalukoff: only if the majority is gonna do the planning.21:04
blogansbalukoff: you might be right, but I fear that since its not finished it doesn't mean it will get finished, it could get abandoned21:04
sbalukoffdougwig: Good point.21:04
sballedougwig, I agree. If we had more information before the vote I might have changed my cote21:04
sballes/cote/vote21:04
sbalukoffblogan: Well, then we'd have to transition to something else.21:04
sballewe need use cases and compare them against launpach and storyboard21:04
bloganback to launchpad probably21:05
sbalukoffIn the mean time, there are "official" OpenStack projects already using it. :P21:05
sbalukoffblogan: Sure.21:05
*** tmc3inphilly has quit IRC21:05
johnsomsbalukoff I don't see any "official" projects on storyboard yet.  The infra stuff hasn't fully moved yet.21:05
bloganbb in a few21:06
davidlenwellsorry I got pulled afk for a minute..21:07
davidlenwellI will email the list with some of my thoughts and ask monty to weigh in21:08
sballedavidlenwell, +121:08
sbalukoffTrevorV: When you write up today's meeting minutes, would you mind putting them in the wiki? (If you severely dislike wiki markup, I'm happy to do it. But... if you don't, might as well skip a step, eh.)21:08
sbalukoffdavidlenwell: Thanks!21:08
sbalukoffdavidlenwell: Are you going to send it to the list under the [Octavia] topic or [StoryBoard] (or both?)21:09
davidlenwelloctavia21:09
sbalukoffCool, thanks!21:09
davidlenwellprobably over the weekend21:09
davidlenwellwhen I am recovered from travel21:10
sbalukoffSounds good.21:10
TrevorVsbalukoff, I can definitely just put them in the wiki first and just email the mailing list with a wiki link, how does that sound?21:12
sbalukoffTevorV: Perfect! Thanks!21:12
*** VijayB has quit IRC21:14
blogani can't believe TrevorV wants to do that21:16
dougwigglutton for minutes.21:17
dougwigoh, and now that the voting is done:21:18
* dougwig does an IRC dance.21:18
blogansbalukoff: I really believe storyboard or launchpad does not matter right now, they will both suffice in the beginning21:18
* rm_work dances the IRC dance with dougwig 21:18
bloganbut since you will be using it most...I can see why you'd want to use storyboard and get the transition out of the way21:19
bloganhmm so maybe i would vote for storyboard...21:19
*** sbfox has quit IRC21:19
*** VijayB has joined #openstack-lbaas21:20
sballeblogan, ;-)21:21
sbalukoffblogan: How about this: I will do both for a couple weeks (up to a month).21:23
bloganworks for me21:24
rm_workWFM, YMMV21:25
*** mestery has quit IRC21:25
davidlenwellrefstack used both for like a week before we decided that we didn't need lp anymore21:25
davidlenwellthe flow in refstack is a lot better21:26
johnsomI think there are a number of people that have to use this for planning, not just sbalukoff.21:26
bloganjohnsom: good point21:26
*** mestery has joined #openstack-lbaas21:26
johnsomDidn't we make a decision during the meeting?  Do we need to vote on this again?21:26
davidlenwellI even created a flow chart showing the work flow which I will include in my email this weekend21:26
bloganjohnsom: lol no its just inner thoughts coming out21:26
blogandoesn't hurt to get more information though21:26
johnsomOk, cool21:26
sbalukoffjohnsom: We did decide during the meeting, but also during the meeting it was mentioned that I cut off davidlenwell's discussion points-- and he's volunteered to take it up on the mailing list (which I think is a good thing)21:27
johnsomI agree on the more info.  My biggest issue with storyboard is the lack of tie in with the specs and the missing subscriptions/tracking21:27
sbalukoffI don't think we want to ever make a policy that we won't revisit past decisions (especially in light of new ideas / evidence), but obviously having had a vote on something does give it a lot more weight, eh.21:28
davidlenwellthe good news is that if we make noise about wanting these things they'll get done faster21:28
rm_workalthough the direct linkage from gerrit to LP is broken right now for non-openstack projects (stackforge)21:28
sbalukoffdavidlenwell: +121:28
johnsomAgreed, just 30 minutes after the decision seems a bit concerning... Grin21:28
sbalukoffjohnsom: That's my fault.21:29
*** dlundquist has left #openstack-lbaas21:29
sballedavidlenwell, sbalukoff Most of HP Storyboard developers are in Seattle ;-) you can go an nok at their door to speed things tp ;-)21:29
sballes/tp/up21:30
sbalukoffI didn't introduce this topic well-- I should have sent something to the mailing list and gotten discussion going before the meeting, and/or I should have just floated the idea here during this meeting so we could gather more data for a vote next week or something.21:30
blogani don't think its a big deal to discuss it after the vote, the vote was made and it was a large majority.  Discussing details directly after seems natural to me anyway21:30
sbalukoffYep, we didn't really discuss details much before people started vetoing the idea.21:30
sballeI probably started that but I knew from Monty that he didn't think it was ready and since is the PTL for that I have to trust his opinion. We could have decided not to vote today and gather more date before the vote21:32
sballes/date/dadta21:32
blogani don't think we even voted, i think we just got a good feeling from the majority opposiing it21:33
rm_workyeah usually the PTL/devs for a project are its biggest proponents, so when one of them says "don't use this yet", usually to me that is a good sign that it isn't ready :P21:33
sballerm_work, My thoughts as well21:33
bloganptls and devs can also be their projects biggest critic as well21:33
sballeyeah!! maybe21:34
*** sbfox has joined #openstack-lbaas21:36
*** sballe_ has joined #openstack-lbaas21:45
dougwigi am guilty of bringing it up after the meeting, after we voted, because i have kind of a big problem with the community telling stephen what he has to use to do his job, when he's already stood up and told us that it's not working for him.  i can't say that i do more than click LP once or twice a month; my workflow as a dev lives in gerrit or IRC, so me21:48
dougwigadvocating for sticking with it (which I do for now) is an opinion that I don't consider particularly relevant.21:48
*** vivek-ebay has quit IRC21:48
*** vivek-ebay has joined #openstack-lbaas21:49
*** sballe has quit IRC21:49
*** vivek-ebay has quit IRC22:05
*** TrevorV_ has joined #openstack-lbaas22:08
*** TrevorV_ has quit IRC22:09
*** ptoohill has quit IRC22:12
*** vivek-ebay has joined #openstack-lbaas22:13
xgermanrmwork is blogan celebrating his victory with irc at a local bar?22:19
xgermanI trust you to have your cell to tell me :-)22:19
*** vivek-ebay has quit IRC22:23
*** johnsom has quit IRC22:25
xgermanI guess they are all on WebEX :-)22:26
*** sbfox has quit IRC22:27
*** sbfox has joined #openstack-lbaas22:27
*** vivek-ebay has joined #openstack-lbaas22:27
*** sbfox has quit IRC22:29
*** sbfox has joined #openstack-lbaas22:29
*** VijayB has quit IRC22:30
*** VijayB has joined #openstack-lbaas22:30
*** VijayB has quit IRC22:33
*** VijayB has joined #openstack-lbaas22:34
rm_workxgerman: hah we were having a celebratory game of foosball :)22:38
xgermanneat --22:38
blogancelebratory on my side22:40
bloganbc I won, if you didnt know22:40
xgermanlol22:40
sbalukoffHeh!22:43
rm_workso again, should I add an item to the LBaaS wiki for an agenda item tomorrow, or should I just bring it up? since the wiki doesn't seem to have been used for agenda planning for a month or so22:44
rm_workright now I am assuming "just bring it up during the meeting"22:45
dougwigadd to the wiki.22:45
dougwigwhen i show up 30 seconds before and get told to chair, i do use the wiki agenda.22:45
rm_workok22:47
*** nealph has quit IRC22:47
dougwigwhat do we have tomorrow, besides the obligatory incubator update?  adv. services cancelled their meeting this week.22:47
rm_workmy keystone/barbican update22:48
dougwigare you editing now?  else i'll add tomorrow22:49
rm_workyes22:49
rm_workjust edited22:49
dougwigok, i fleshed it out a little bit.22:53
*** sbfox1 has joined #openstack-lbaas22:59
*** sbfox has quit IRC22:59
*** barclaac has quit IRC23:01
rm_workI was going to put my update last23:05
rm_workbut that's fine :P23:05
*** jorgem has quit IRC23:30
dougwigfront and center.23:31
*** sbfox1 has quit IRC23:40

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