20:00:08 #startmeeting Octavia 20:00:09 Meeting started Wed Feb 11 20:00:08 2015 UTC and is due to finish in 60 minutes. The chair is xgerman. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:00:13 The meeting name has been set to 'octavia' 20:00:23 #topic roll call 20:00:25 o/ 20:00:26 o/ 20:00:27 o/ 20:00:39 o/ 20:00:46 Agenda: https://wiki.openstack.org/wiki/Octavia/Weekly_Meeting_Agenda#Agenda 20:01:01 o/ 20:01:05 o/ 20:01:43 o/ 20:01:45 late 20:01:53 o/ 20:02:40 #topic Brief progress reports 20:02:48 o / 20:02:59 Focus on neutron-lbaas for me. 20:03:33 I am getting back to working on the controller worker. I have removed the WIP from the spec, so if you can review it would be great. 20:03:43 #link https://review.openstack.org/#/c/149801/ 20:03:43 working on health manager database model, have changed based on the comment, now working on the update health method 20:04:13 Watching neutron-lbaas bork out on tox during neutron egg installation. 20:04:16 So I've been working on the neutron lbaas v2 tempest tests, with franklin and carlos, and have essentially stalled my work on the octavia amphora api 20:04:38 hi! 20:04:44 HP guys may pick up work on the amphora api 20:04:57 We (RS) may focus on a ssh-client/agent 20:05:00 thing 20:05:06 ok, sound sgood 20:05:25 atleast according to chats earlier. 20:05:36 yeah, that's our intention ;-) 20:05:42 ;) 20:05:51 jorgem submitted another patch for the queue-consumer 20:06:22 xgerman: will yall take over the api spec bp sbalukoff started? 20:06:29 well HP will for the REST API right? Someone here at Rax will probably do an SSH driver... as far as I recall 20:06:30 yep, will do 20:07:29 o/ 20:07:48 assigned that spec to me for now 20:08:01 s/spec/blueprint/ 20:08:19 anything else? 20:08:30 o/ 20:08:38 moving on... 20:08:43 #topic Demo Octavia in Neutron LBaaS Talk 20:09:28 so the plan is to have at least one neutron lbaas talk and in that talk we'll be demoing octavia 20:09:52 exactly + and we are trying to pull together the missing puzzle pieces 20:10:38 The pieces are: 20:10:45 Amphora Driver 20:10:45 Network Driver 20:10:45 Deploy Worke 20:10:59 dis we miss anyhting? 20:11:06 how about compute driver? 20:11:12 neutron lbaas driver 20:11:24 or is that part of the deploy worker 20:11:32 dougwig: +1 20:11:33 sballe__ that one is already merged 20:11:38 dougwig +1 20:11:51 compute driver is pretty much done i think 20:11:57 btu yeah forgota bout neutron lbaas driver 20:11:58 xgerman: Are we only talking about he missing pieces? or all the pieces? 20:12:04 missing 20:12:21 ok thx 20:12:50 so dougwig any progress on the neutron driver ? 20:13:01 (it's your piece :-) 20:13:27 i volunteered for the network driver for this, because phil and I have already dong a run through of neutron and nova calls to set up the appropriate plumbing 20:13:33 none yet, i've been focused on the lbaas v2 stuff, flavors, and this: https://review.openstack.org/#/c/154736 20:13:40 i will circle back to that driver shortly. 20:14:24 dougwig ill run through what we've done manually if you want 20:15:57 let's take that offline 20:16:22 sounds good 20:16:55 johnsom + me will do deploy worker 20:17:01 +1 20:17:04 what 20:17:09 I will be doing reviews! :) 20:17:12 what's the timeframe on that you think? 20:17:46 it's high on our list so the next few weeks 20:17:53 Timeframe for controller worker code? 20:17:55 What he said. 20:18:11 xgerman: johnsom: correct 20:18:12 I hope to have another WIP check in today. 20:18:24 k I'll check it out. 20:18:34 ditto on the review 20:19:53 leaves the amphora driver -- 20:20:05 Oh, you mean the amphora ssh driver? 20:20:13 I think HP will try an API version whereas RAX will do the ssh driver 20:20:24 TrevorV yes 20:20:36 and i will make popcorn and side bets. 20:20:42 I would put my name on that, but I'm not entirely sure when I can get to it (tempest testing and all that) 20:21:14 eh dougwig already convinced me of the sense in using ssh 20:21:27 wow. 20:21:39 Alright, I'll take ownership of that one 20:21:40 dougwig: +1 20:21:57 dougwig: so no bets to be found here, I would think :P 20:22:12 i didn't say i wasn't rooting for one side. :) 20:22:25 was just talking abput the popcorn 20:22:41 sballe__: oh, heh. :) 20:22:50 #agreed TrevorV will write ssh amphora driver 20:23:06 #agreed HP will attempt REST based driver/agent 20:23:47 how do we decide what solution we want to use in the demo? 20:24:04 ;-) 20:24:12 sballe_: Wait to see which one performs better or works in reality. 20:24:17 sballe__: that's a problem that i'd love to have. 20:24:25 let's get there first. 20:24:25 dougwig: ;-) 20:25:27 Theyll both work, i was under the assumption that the ssh driver we were going to work on to get done quick to get our point and this demo across 20:25:39 so. Is paramiko still a good idea these days or is something better out there now? 20:25:42 yep, that wa smy impression as well 20:25:48 the rest api will require more devlopment and a concensus of the contract amongst other things 20:26:14 ptoohill +1 20:26:23 we likely need to iterate 20:26:38 indeed 20:26:46 paramiko bleh 20:26:52 I'm kinda burnt out on Rest APIs now. specially sense this isn't something that is customer facing. 20:26:54 crc32: paramiko or just popen('ssh ' + foo) 20:27:14 popen is super ugly <_< 20:27:26 paramiko would have to be REALLY bad 20:27:35 but I feel like this is getting off-topic 20:27:48 At the very least let us use paramiko. I'm not in the mood for STDIN STDOUT parsing and mangling. 20:27:56 +1 20:27:59 eh, wrap it once, hide the ugly. example (not claiming it's not ugly, though): https://github.com/a10networks/neutron-thirdparty-ci/blob/master/ax/ax_ssh.py 20:28:05 good thing I'll be working on it then, eh crc32 ? 20:28:14 yea the wrapper is called Paramiko. 20:28:40 maybe there is an oslo version 20:28:41 just use whatever, its going to just be simple and if people want to improve upon it go ahead 20:28:53 no, paramiko is a pure python implementation. it's much slower. but i don't think that matters at all here. 20:29:15 yep + long term I expect us to use an agent on the amphora 20:29:22 Alright, since its my task for the amphora driver I'll sort out the logistics later, kk? We can move on at this point :P 20:29:45 #topic Open Discussion 20:29:54 since it's open, we can bring up ssh again. 20:29:55 jk 20:30:04 * xgerman hides 20:31:42 dougwig you have the etherpad links for the Vancouber talks 20:31:44 ? 20:32:04 dangit, forgot that. one sec, i'll create and post a link here or in lbaas channel 20:32:14 great 20:32:29 dougwig could I steel your attention later for some reviews 20:32:47 also regarding Vancouver - are we trying to do something in the design summit? 20:32:48 ^ steal 20:33:43 i woudl like to 20:33:57 me, too - so 20:34:02 for octavia? 20:34:04 or for neutron-lbaas 20:34:13 i mean both kind of need one 20:34:19 yep 20:34:21 Agreed 20:34:40 #action find out to get Octavia and Neutron LBaaS into the design summit 20:34:49 https://etherpad.openstack.org/p/lbaas-vancouver-talks 20:34:59 i'll get talk outlines added there as well. 20:35:27 dougwig so johnso, jorgem, na dme need our won talk? 20:35:33 what contentious stuff do we have that needs the entire community? 20:35:59 xgerman: i can barely parse that sentence, but those speaker lists are far from final. 20:36:02 xgerman: eh? lol 20:36:22 well, last time we said johnsom, jorgem, and I would like to talk, too 20:36:33 so reading that we need a third talk ;-)]\ 20:36:40 everyone is welcome to add their feedback, requests, new speakers, etc, there, and then we can talk about what makes sense. i just had to get the slots submitted by monday. 20:36:55 we need to be careful with too many speakers on the talks. it gets confusing. Should we do a panel with more companies represented? 20:37:03 xgerman: that was for a standalone octavia talk, which i didn't submit. did stephen send that? 20:37:10 nope 20:37:30 i doubt it would have been accepted anywya, no one knows what octavia is yet 20:38:22 Who is Sam? 20:38:27 Radware 20:38:41 nothing says we can't fold some or all of those folks into the octavia part of the lbaas talk. note it in the etherpad, and we can talk about what makes sense. 20:39:11 The talk is 20 minute right? or is it longer> 20:39:26 40 minutes. 20:39:38 5 minutes for qa, 10 for demo, the rest for talking. ish. 20:41:40 btw, i'm not dead set on being a speaker, either. please give your feedback on the etherpad. 20:41:48 dougwig, didn't you ask me for my openstack details for a talk or was that for something else? 20:42:14 well, so we lock in on those two talks or are we trying to submit an Octavia talk as well? 20:42:20 Maybe it was Stephen 20:42:22 i was testing the speaker submissions, but ended up not being the octavia submitter. 20:42:27 dougwig: I think one person from each company makes sense to me. 20:42:49 +1 sballe__ 20:42:56 +1 20:44:13 +1 20:44:29 +1 20:44:30 let's put our feedback into the etherpad, and circle back next week? my apologies if anyone feels left out; i think he octavia half got lost in the transition shuffle, and I never considered the current submissions final. 20:44:56 Sounds good 20:45:01 dougwig: no problem. 20:45:01 i mean, i agree that it seems unlikely Octavia talks would get accepted, since it's still Stackforge and relatively unknown 20:45:24 rm_work - and HP was ready to run a super bowl ad foer it 20:45:30 heh 20:45:36 that would have been awesome :P 20:45:36 We could submit the octavia talk as a brownbag or whatever they call the 10 mins talks 20:45:44 the submission deadline was this last monday. 20:45:47 yeah I assume that'd be where we'd fit 20:45:57 so if we don't have a placeholder in there, i think that ship has sailed. 20:46:00 brownbag submissions are much later I thought? 20:46:13 i meant for the conference talks 20:46:17 yes They are after the people have voted on the talks 20:46:19 or "lightning talks" or whatever they are called in the Openstack world 20:46:22 yeah 20:47:03 let's do that 20:47:12 and people don;t vote on lighting talks so we can submit more than one and they will be accepted ;-) 20:49:20 so who is taking the action item to submit that talk 20:49:23 ? 20:50:00 Did you agree on the list of speakers? 20:50:44 I was talking brownbag - I am really afraid things fall again through cracks 20:51:12 I agree but one of the speakers will have to submit the talk and not random peopel 20:51:45 one of the speakers of an accepted talk has to submit it? 20:51:50 eh, it's pretty fluid, actually. any speaker can add or remove others, so you can bootstrap it. 20:52:59 I was talking about speakers for the brownbag. never mind. 20:53:28 ok, I will try to keep an eye on that deadline 20:54:19 i'd suggest we add design session topics in the same etherpad. 20:54:22 if any 20:54:26 +q 20:54:30 +1 20:54:30 +1 ;-) 20:55:26 we have 5 minutes left... 20:55:41 (in case we have other topics :-) 20:56:30 the beauty of ssh and ruby! 20:56:38 sorry, in a weird mood today. :) 20:56:42 #link https://etherpad.openstack.org/p/lbaas-vancouver-talks 20:56:56 pretty ruby... 20:56:59 Gem stones? 20:57:20 gems versus pip, lord yes. 20:57:31 lol 20:57:52 guess better finish before somebody gets hurt 20:57:57 clear 20:57:57 #endmeeting