Tuesday, 2015-01-20

*** galstrom is now known as galstrom_zzz00:06
*** salv-orlando has quit IRC00:07
*** salv-orlando has joined #openstack-meeting-400:07
*** VW_ has joined #openstack-meeting-400:14
*** sigmavirus24 is now known as sigmavirus24_awa00:38
*** VW_ has quit IRC00:39
*** salv-orlando has quit IRC00:55
*** galstrom_zzz is now known as galstrom01:11
*** mestery has quit IRC01:29
*** salv-orlando has joined #openstack-meeting-401:58
*** yamahata has quit IRC02:00
*** emagana has quit IRC02:01
*** salv-orlando has quit IRC02:02
*** sarob has joined #openstack-meeting-402:04
*** ajmiller has joined #openstack-meeting-402:04
*** sarob has quit IRC02:12
*** salv-orlando has joined #openstack-meeting-402:16
*** sarob has joined #openstack-meeting-402:16
*** galstrom is now known as galstrom_zzz02:20
*** salv-orlando has quit IRC02:21
*** sarob has quit IRC02:21
*** sarob has joined #openstack-meeting-402:29
*** sarob has quit IRC02:46
*** emagana has joined #openstack-meeting-402:46
*** ivar-laz_ has joined #openstack-meeting-402:48
*** ivar-lazzaro has quit IRC02:52
*** ivar-laz_ has quit IRC02:53
*** yamahata has joined #openstack-meeting-402:55
*** salv-orlando has joined #openstack-meeting-403:03
*** salv-orlando has quit IRC03:04
*** emagana has quit IRC03:16
*** qwebirc93676 has joined #openstack-meeting-403:22
*** banix has joined #openstack-meeting-403:35
*** yamahata has quit IRC03:58
*** yamahata has joined #openstack-meeting-403:58
*** qwebirc21178 has joined #openstack-meeting-404:00
*** sbalukoff has quit IRC04:01
*** qwebirc21178 has quit IRC04:04
*** ajmiller has quit IRC04:06
*** VW_ has joined #openstack-meeting-404:23
*** carl_baldwin has joined #openstack-meeting-404:47
*** carl_baldwin has quit IRC04:55
*** qwebirc93676 has quit IRC05:01
*** david-lyle has joined #openstack-meeting-405:15
*** VW_ has quit IRC05:23
*** sarob has joined #openstack-meeting-405:46
*** sarob has quit IRC05:51
*** ivar-lazzaro has joined #openstack-meeting-406:11
*** ivar-lazzaro has quit IRC06:23
*** SridharRamaswamy has joined #openstack-meeting-406:32
*** SridharRamaswamy has quit IRC06:39
*** SridharRamaswamy has joined #openstack-meeting-406:40
*** banix has quit IRC06:41
*** numan has joined #openstack-meeting-406:45
*** SridharRamaswamy has quit IRC06:57
*** david-lyle has quit IRC06:57
*** david-lyle has joined #openstack-meeting-407:31
*** ivar-lazzaro has joined #openstack-meeting-407:33
*** david-lyle has quit IRC07:35
*** david-lyle has joined #openstack-meeting-407:42
*** ivar-lazzaro has quit IRC07:46
*** david-lyle has quit IRC07:47
*** kobis has joined #openstack-meeting-407:50
*** belmoreira has joined #openstack-meeting-407:52
*** david-lyle has joined #openstack-meeting-408:01
*** david-lyle has quit IRC08:05
*** kobis has quit IRC08:06
*** kobis has joined #openstack-meeting-408:23
*** watanabe_isao has quit IRC08:37
*** yamahata has quit IRC08:58
*** david-lyle has joined #openstack-meeting-409:19
*** Viswanath has joined #openstack-meeting-409:24
*** gmatefi has joined #openstack-meeting-409:28
*** gmatefi has quit IRC09:28
*** Viswanath has quit IRC09:48
*** ivar-lazzaro has joined #openstack-meeting-410:14
*** ivar-lazzaro has quit IRC10:19
*** pkoniszewski has joined #openstack-meeting-410:39
*** pkoniszewski has quit IRC11:04
*** igordcard has joined #openstack-meeting-412:37
*** salv-orlando has joined #openstack-meeting-412:43
*** belmorei_ has joined #openstack-meeting-412:55
*** belmoreira has quit IRC12:56
*** markvoelker has joined #openstack-meeting-413:06
*** belmorei_ has quit IRC13:16
*** salv-orlando has quit IRC13:17
*** salv-orlando has joined #openstack-meeting-413:24
*** salv-orlando has quit IRC13:24
*** salv-orlando has joined #openstack-meeting-413:25
*** salv-orlando has quit IRC13:31
*** salv-orlando has joined #openstack-meeting-413:32
*** lakshmiS has joined #openstack-meeting-413:36
*** banix has joined #openstack-meeting-413:57
*** evgenyf has joined #openstack-meeting-414:02
*** mestery has joined #openstack-meeting-414:11
*** banix has quit IRC14:15
*** VW_ has joined #openstack-meeting-414:28
*** pkoniszewski has joined #openstack-meeting-414:32
*** Swami has joined #openstack-meeting-414:45
*** VW_ has quit IRC14:51
*** dboik has joined #openstack-meeting-414:56
*** matrohon has joined #openstack-meeting-414:56
*** pc_m has joined #openstack-meeting-414:59
Swamipc_m: hi14:59
*** sigmavirus24_awa is now known as sigmavirus2414:59
*** mestery has quit IRC14:59
pc_mSwami: Hi!14:59
Swamipc_m: I saw your comment on one of my vpn patch.15:00
Swamifor manual testing15:00
SwamiI have done the manual testing with DVR and Vpn patch.15:00
pc_mSwami: Yeah, we can chat in the meet...15:00
pc_mmeeting15:00
SwamiDo you see any issuee.15:00
matrohonhi15:00
Swamiok15:00
pc_mmatrohon: hi15:01
numanhi15:01
pc_m#startmeeting vpnaas15:01
openstackMeeting started Tue Jan 20 15:01:36 2015 UTC and is due to finish in 60 minutes.  The chair is pc_m. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: vpnaas)"15:01
openstackThe meeting name has been set to 'vpnaas'15:01
pc_mhi numan15:01
numanhi15:01
numanpc_m, hi15:01
pc_mOK. let's go...15:02
pc_m#topic Announcements15:02
*** openstack changes topic to "Announcements (Meeting topic: vpnaas)"15:02
pc_mI updated the Wiki with info on running VPN on a single DevStack with two routers15:03
*** mestery has joined #openstack-meeting-415:03
pc_m#link https://wiki.openstack.org/wiki/Neutron/VPNaaS/HowToInstall#VPNaaS_with_Single_DevStack_and_Two_Routers15:03
matrohonpc_m : great!15:03
pc_mWe can use that to do a nice functional/scenario test for VPN.15:03
numanpc_m, great15:03
Swamipc_m: nice15:04
pc_mAny other announcements?15:04
pc_m#topic Bugs15:05
*** openstack changes topic to "Bugs (Meeting topic: vpnaas)"15:05
*** VW_ has joined #openstack-meeting-415:05
pc_mPlease take some time and look at the VPN bugs and provide comments so we can move everything forward.15:06
pc_mHere's the list https://review.openstack.org/#/q/status:open+project:openstack/neutron-vpnaas,n,z15:06
pc_mWant to touch on a few and get feedback from people...15:06
pc_mOne is PID issue on CentOS. #link https://review.openstack.org/#/c/147852/15:07
Swamipc_m: I got a comment from you on one of my patch for the vpnaas support for DVR15:08
*** vikram___ has joined #openstack-meeting-415:08
Swamiregarding manual testing.15:08
pc_mI'm a little concerned about whether that temp fix is adequate. Anyone know of a long term solution?15:08
pc_mSwami: hang on. we'll hit that one in a sec.15:08
Swamipc_m: thanks15:09
pc_mAppears to be that if dir is not owned by root, there are issues in CentOS.15:10
pc_mShould we bring this up on ML or neutron IRC?15:11
*** VW_ has quit IRC15:11
numanthe temp solution solves this problem by adding '/' at the end of the pid path ?15:12
*** mestery has quit IRC15:12
pc_mnuman: yeah15:12
numanok.15:13
pc_mAt the min. we need some comment to indicate this special workaround. Wondering about final solution.15:13
pc_m#action Discuss 147852 on ML to see if there is a permanent solution.15:14
pc_mSwami: We can talk about your review... do you have the review link...15:14
pc_mI got it... #link https://review.openstack.org/14320315:14
Swamiyes15:15
Swami#link https://review.openstack.org/#/c/143203/15:15
pc_mI need to go over it again. My main concern was that we've manually tested setting up IPSec connections, as we don't have any functional/scenario tests.15:15
SwamiYou have a comment in there to make sure that I do the manual testing.15:15
SwamiYes we are planning to add some functional and scenario test for the ipsec vpn.15:16
pc_mI see you have. Great!  I'll approve.15:16
SwamiBut that should be submitted as a separate patch and will work on it.15:16
matrohonSwami : please have a look at fullstack for functional tests15:17
pc_mSwami: Yes, we badly need functional tests. I have a way to run on one node.15:17
*** mhanif has joined #openstack-meeting-415:17
matrohonSwami : https://review.openstack.org/#/c/128259/15:18
pc_mWas planning on talking to Maru and others about what is needed for a test.15:18
numanpc_m,  Swami, presently jenkins doesn't run functional job for vpnaas. I have raised a bug for it. https://bugs.launchpad.net/openstack-ci/+bug/141277015:18
pc_m#action pc_m to investigate what is needed for function/scenario test.15:18
Swamipc_m: Yes I understand, we are in the process of adding functional tests and vpn will be also under the radar. That is a good point.15:18
matrohonSwami : do you have an assigned bug?15:19
pc_mCan use help is creating the test cases, especially for variants, like DVR.15:19
pc_mnuman: Yeah, saw that. Do we have any functional tests?15:19
Swamimatrohon: no i have not created a bug for the functional test, but we are working with marun and carl_baldwin to fill in the issues with functional tests.15:20
numanpc_m, not yet, but there are two patches which have functional tests15:20
pc_mnuman: Gotcha. So we have a place holder for enabling, once these are working.15:21
pc_mAnother bug is FQDN #link https://review.openstack.org/#/c/145005/15:21
numanpc_m, i saw your comments. I will address them15:22
*** b3rnard0 has left #openstack-meeting-415:22
numanpc_m, one question is about the functional tests. Are they really functional tests ?15:22
pc_mYeah, the test seems to just be testing the get next hop method. Seems just like a UT to me.15:23
numani added those tests in the functional test section because they interact with the system15:23
pc_mnuman: Did you have something different in mind, or am I missing something.15:23
numani can move them to unit tests. can the unit tests create namespace and other resources ?15:24
pc_mI see your reply... good question. I'm not sure if it needs to be in functional test due to the namespace.15:24
numanok. In that case I will move them to unit tests15:25
pc_mnuman: Let's ask on IRC and see if they should be functional or unit.15:25
numansure15:26
pc_mnuman: Especially because getaddrinfo is mocked out, right?15:26
numanAlso do we need to support running functional tests in jenkins before the patch (with functional tests) merges ?15:26
numanpc_m, right.15:27
pc_mYeah, that's a bit of a catch-2215:27
numanpc_m, i will see if i can get away mocking getaddrinfo15:27
matrohonnuman : that seems reasonnable15:27
pc_m#action numan to see if tests for 145005 need to be fucntional or UT.15:27
numanmatrohon, you mean mocking getaddrinfo ?15:28
pc_mnuman: I'm thinking if you just mock, and consider a UT, you avoid the whole issue.15:28
pc_mIn general though, I guess we need to determine what functional tests we need for VPN.15:28
matrohonI meant waiting for functional test to be run in neutron-vpnaas15:28
numanmatrohon, ok15:29
pc_mThe one with StrongSwan seems to make sense.15:29
pc_mnuman: Check on the IRC. I think you can progress much faster, if you don't have the functional test dependency.15:30
numanpc_m, ok sure15:30
pc_mNext one is netns for StrongSwan #link https://review.openstack.org/#/c/146508/15:31
pc_mI'm struggling a bit on netns_wrapper.py in that bug.15:32
* pc_m not versed in /proc files15:32
matrohonme too : it's very hard to review!15:32
pc_mLogic in  execute_with_wount() is hard to understand.15:33
pc_mI've been chatting with people on IRC. I'm questioning whether or not we can require kernel 3.8+ and thus use ns/mnt check.15:33
pc_m#action pc_m discuss on ML whether we can require kernel 3.8+ for StrongSwan netns (146508)15:34
*** SantoshNetScaler has joined #openstack-meeting-415:35
pc_mDoes anyone know what the check on L129-130 does?15:35
* pc_m wondering if Zhang is on-line15:35
matrohonI think he is located in beijing15:36
pc_mmatrohon: I'll post on ML as, we may be able to require kernel 3.8+ and be able to use /ns/mnt.15:37
matrohonI think that nati_ueno could be asked to, this code is inspired from a previous patch of nati15:37
pc_mWill see what the response is on the review.15:37
pc_mmatrohon: good point.  Checking...15:38
pc_mdon't see him on now, but can talk to him. It's an old file. Just not sure the assumptions are still true.15:38
*** mhanif has quit IRC15:38
pc_mNext one is StrongSwan #link https://review.openstack.org/#/c/144391/15:39
numani think the code checks 2 points in one shot 1. if the caller is root or not 2. if the file /proc/1/ns/net exists or not15:39
pc_m#undo15:39
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x2000a50>15:39
pc_m#redo15:40
* pc_m oops. didn't mean to undo...15:40
pc_m#topic Bugs15:40
*** openstack changes topic to "Bugs (Meeting topic: vpnaas)"15:40
* pc_m might have messed that up.15:40
pc_mnuman: Yeah, but isn't this always called as root? Or is it a double check.15:41
numanpc_m, if it isn't called as root os.getpid() will not be 1 i think15:41
pc_mnuman: Then the log message seems to confuse me as well.15:41
numanpc_m, right. i think the code can be clearer.15:42
pc_mnuman: We'll let Zhang respond.15:42
pc_mOn StrongSwan review, 144391, I need to look it over again.15:42
*** nikhil_ has joined #openstack-meeting-415:43
pc_mAnyone have any other bugs to discuss?15:43
*** nikhil_ is now known as Guest4537515:44
pc_mPlease review the ones we have right now. We can use more eyes on these, from different perspectives.15:44
matrohonnumam reported a bug to enable functional test in neutron-vpnaas, but we already discussed that earlier15:45
matrohonhttps://bugs.launchpad.net/openstack-ci/+bug/141277015:45
*** ajmiller has joined #openstack-meeting-415:45
pc_mmatrohon: Yes, appreciate the creation to track that.15:45
matrohonI don't know if we have to wait for the infra to add the job15:46
numani am still not clear. if we need to fix this bug first or let some functional tests gets merged before enabling in infra15:46
matrohonoh numan already assigned it to himself!15:46
pc_m#action pc_m find out the sequencing for enabling functional tests and first reviews with functional pieces.15:46
numanmatrohon, i unassigned myself as i dont have the necessary expertise :)15:47
*** SantoshNetScaler has quit IRC15:47
matrohonI think you have to enable funct test job first, to have it voting on your new func test15:47
pc_mnuman: If you have bandwidth, do you want to pursue it though (none of us have expertise, I think)?15:48
*** johnsom has joined #openstack-meeting-415:48
numanpc_m, i will try :)15:48
pc_mI think we're all groping in the dark on the test stuff. Will need to consult with other.15:48
pc_mnuman: AWESOME!15:48
pc_m#action numan to follow up on 1412770 needs15:49
matrohondoes anyone know who configured the job to run the vpnaas project15:49
*** sballe__ has joined #openstack-meeting-415:49
pc_mmatrohon: I don't know.15:49
pc_mnuman: You may want to ask Maru on IRC. He may know.15:50
*** SantoshNetScaler has joined #openstack-meeting-415:50
pc_m#topic Open Discussion15:50
numanok15:50
*** openstack changes topic to "Open Discussion (Meeting topic: vpnaas)"15:50
pc_mAnyone have anything to discuss?15:50
pc_mAnything we're missing or need to do differently?15:51
pc_mThanks for joining in everyone!15:52
pc_m#endmeeting15:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:52
openstackMeeting ended Tue Jan 20 15:52:49 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vpnaas/2015/vpnaas.2015-01-20-15.01.html15:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vpnaas/2015/vpnaas.2015-01-20-15.01.txt15:52
openstackLog:            http://eavesdrop.openstack.org/meetings/vpnaas/2015/vpnaas.2015-01-20-15.01.log.html15:52
numanthank you15:53
numanbye15:53
pc_mnuman: bye15:53
pc_mbye15:53
*** pc_m has left #openstack-meeting-415:53
*** vikram___ has quit IRC15:55
*** numan has quit IRC15:55
dougwigo/15:56
*** numan has joined #openstack-meeting-415:56
johnsomMorning Doug15:57
SantoshNetScalerHi All15:57
bloganhi15:57
*** xgerman has joined #openstack-meeting-415:59
*** jamiem has joined #openstack-meeting-415:59
kobishi15:59
dougwig#startmeeting neutron lbaas16:00
openstackMeeting started Tue Jan 20 16:00:04 2015 UTC and is due to finish in 60 minutes.  The chair is dougwig. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: neutron lbaas)"16:00
openstackThe meeting name has been set to 'neutron_lbaas'16:00
*** numan has quit IRC16:00
dougwig#topic good morning/evening16:00
*** openstack changes topic to "good morning/evening (Meeting topic: neutron lbaas)"16:00
dougwigo/16:00
ajmillero/ hi16:00
xgermano/16:00
johnsomo/16:00
jamiemo/16:00
dougwigagenda:16:00
dougwig#link https://wiki.openstack.org/wiki/Network/LBaaS16:00
dougwig#topic Announcements16:02
*** VW_ has joined #openstack-meeting-416:02
*** openstack changes topic to "Announcements (Meeting topic: neutron lbaas)"16:02
*** VW_ has quit IRC16:02
sballe__o/16:02
dougwigthe usual mid-cycle reminder, kilo-2 reminder (2/5).16:02
dougwigNext lbaasv2 review to focus on:16:02
dougwig#link https://review.openstack.org/#/c/144831/516:02
dougwigany other announcements?16:02
*** VW_ has joined #openstack-meeting-416:03
bloganlets try and get that one and the one after merged, just to reduce the insanity of the dependency chains16:03
sballe__+116:03
dougwiggot a link handy?16:03
dougwigfor the second.16:03
rm_workah, this is where people are16:03
*** jorgem has joined #openstack-meeting-416:03
rm_worko/16:03
jorgemo/16:03
jorgemsorry thought it was in alt16:04
blogan#link https://review.openstack.org/#/c/144832/16:04
*** carl_baldwin has joined #openstack-meeting-416:04
*** galstrom_zzz is now known as galstrom16:04
dougwig#topic Mid-cycle meetup details16:04
*** openstack changes topic to "Mid-cycle meetup details (Meeting topic: neutron lbaas)"16:04
dougwig#link https://etherpad.openstack.org/p/lbaas-kilo-meetup16:04
SantoshNetScaler##16:05
dougwigI wanted to tear through the main areas quickly this morning.  Highlight areas that need an owner, and ask current owners if there's anything blocking them or that they need before the sprint.16:05
dougwig1. Finish outstanding v2 reviews (dougwig, blogan)16:05
dougwigblogan, anything blocking us?16:05
blogannot the first 2, but the one after will need a neutron review to be merged first16:06
dougwigok16:06
bloganwhich im sure you will be able to help on come thursday ;)16:06
dougwig2. Complete Agent Ref Impl16:06
dougwigi've seen the ref driver reviews have some activity. anyone signed up to agent-ify yet?16:06
* dougwig hears crickets while waiting for his tea to brew.16:07
*** pc_m has joined #openstack-meeting-416:07
dougwig3. API Improvements (blogan)16:07
dougwigthis is the one with a neutron review, right?16:07
bloganyep16:07
dougwig4. Client/CLI (johnsom)16:07
dougwigjohnsom in the house?16:07
johnsomI got in touch with Ryan, he hasn't had time to work on the client16:07
dougwiganything you need from the team in the next 2 weeks? any progress on neutron client vs openstack client?16:08
johnsomI looked at the openstack client docs but I haven't yet looked at how much it aligns to the API16:08
bloganyou find out more on whether we should go with openstack-client or neutron client?16:08
bloganoh ditto16:08
johnsomI think we should get a neutron client out and working as we can get the reviews16:08
blogando you have the review that ctracey already had up?16:09
johnsomSo that is the path I think we should go down.  I know there is some work complete is that direction, but send me the link16:09
*** carl_baldwin has quit IRC16:09
dougwig#link https://review.openstack.org/#/c/111475/16:09
blogandougwig too quick16:10
xgermanyeah, ajmiller knows all aboit it ;-)16:10
blogangerrit too damn slow16:10
johnsomYep.16:10
dougwigi used the etherpad.  :)16:10
dougwig#link https://etherpad.openstack.org/p/lbaas_reviews16:10
*** banix has joined #openstack-meeting-416:10
blogani dont care what mestery says about you, you actually aren't that dumb16:10
dougwigany other issues/questions/blockers with the client for this morning?16:11
dougwighaha.16:11
johnsomI don't have any16:11
dougwig5. Tests - Rama (HP QA )16:11
dougwigis Rama around? (what's his irc nick?)16:11
xgermanhe volunteered at one of our meetings so I pinned him down16:11
xgermanhe is still getting up to speed16:12
dougwigxgerman: excellent.16:12
dougwigis he able to attend the sprint, or will he be remote?16:12
bloganare those tempest tests going into tree?16:12
xgermanremote16:12
bloganetherpad says he'll be remote16:12
*** VW_ has quit IRC16:12
dougwigok.  xgerman, can you check with him as to progress/blockers/anything he needs?16:12
xgermanwill do!16:13
dougwigty16:13
dougwig6. TLS (ptoohill, evgeny)16:13
dougwigptoohill or evgenyf awake yet?  :)16:13
ptoohillIm working on updating the ref sync impl as of now16:13
ptoohillevgenyf had a couple pieces to put together now that we have deps set up for the cert stuffs16:14
rm_workCarlos and I have related reviews too, and all of the TLS related reviews are stuck at the end of that review chain we mentioned earlier16:14
ptoohilland fixing tests all around16:14
evgenyfI'm working on using real tls certificates manager code16:14
dougwiggreat. anything blocking you guys besides reviews?16:14
ptoohillNo sir16:14
evgenyfNo16:14
dougwiggreat.16:14
dougwig7. L7 (evgeny)16:14
dougwigi saw these reviews got re-posted. are we waiting on anything else for them?16:15
*** Guest45375 has quit IRC16:15
dougwigevgenyf: you're listed as tentative for the sprint. are you able to make it?16:15
evgenyfre-proposed to neutron-lbaas, ready for review https://review.openstack.org/#/c/148232/16:15
evgenyfdougwig, yes, extensions code is missing16:16
dougwigcan you propose the extension code against neutron, or do you need someone else to do that?16:16
bloganhe alreayd did it16:16
dougwigoh, ok.16:17
ptoohillawesomesauce16:17
dougwigso that's all in review land.16:17
bloganwith unicorns16:17
dougwig8. Docs16:17
dougwigdid we resurrect the v2 api docs?16:17
bloganthats what i was wondering16:17
bloganemail on ML saying they were looking at them and i didnt know they were viewable by anyone16:18
dougwigwho was the original author?16:18
xgermanmin16:18
bloganmin i believe16:18
xgermanwe have them in a Google drive16:18
dougwigis she going to take that back over, or do we need a new owner?16:18
xgermanI think she can do it16:18
dougwiggreat. can you close the loop with her?16:18
xgermanyep, will do16:18
dougwigty16:19
dougwig(almost done)16:19
dougwig9. Heat?16:19
dougwigdo we need to do anything for heat?16:19
xgermanwell, we likely need to test that it works16:19
xgermanbut I never used heat16:19
bloganwon't heat need some code updates to support v2?16:19
dougwiganyone want to wade into that for kilo?16:19
sballe__What do we need to test with Heat?16:20
*** carl_baldwin has joined #openstack-meeting-416:20
dougwigsballe__: that's step 1 of the task.  :)16:20
sballe__That we can orchestrate things with heat?16:20
jorgemthe spurs handled the heat just fine last year dougwig16:20
ptoohillOut of left field16:20
sballe__jorgem: :-)16:20
rm_workjohnsom: <_<16:20
jorgemlol16:20
rm_workerr16:20
rm_workjorgem: <_<16:20
jorgemYou can check that one off the list :)16:20
dougwigsports humor in a nerd chatroom.  the whooshing noise is really loud.16:20
evgenyfblogan: regarding extensions code proposal to neutron, I did not do it. Did you mean ptoohill did it?16:21
ptoohilldid i?16:21
*** carl_baldwin has quit IRC16:21
dougwigblogan: the l7 extension is proposed? i missed it, if so.16:21
evgenyfptoohill: did you ?:)16:21
bloganevgenyf: maybe ptoohill did, i just saw it linked in your review16:21
sballe__I have to look into heat fro some other project so if we can agree what we want to do woth heat I can probably sign up for it16:21
ptoohilli havnt touched anything for l716:21
blogannvm16:21
ptoohillblogan, we were going to wait for that when i was messing with it16:21
blogani misread it16:22
bloganmisread the comment16:22
dougwigevgenyf: can you re-propose the extension in neutron master?16:22
ptoohillSo, yea, that still needs to be done in that case16:22
evgenyfdougwig: I will16:22
dougwigback to heat, we'll leave that as open and needing an owner for now.16:22
dougwig#action evgenyf Propose L7 extension in neutron master16:22
rm_workdougwig: i think sballe__ possibly volunteered :P16:23
dougwig10. Horizon?16:23
*** carl_baldwin has joined #openstack-meeting-416:23
dougwigre: heat - Oh, missed that.  Sweet, thank you sable.16:23
dougwigsballe.16:23
rm_workwho was it that was working on horizon before? one of the paypal guys?16:23
bloganvivek16:24
dougwighorizon - anyone heard from vivek lately? I think we're far enough into Kilo that we'd need to do it as an add-on module for horizon in our own repo.16:24
jorgemhave not heard from him lately16:24
dougwigok, i'll email him. i may have someone here that can work on that, if he doesn't have any cycles.16:25
bloganhere as in your office or in the channel?16:25
dougwigand that's the list of big areas.  anything missing or any other meetup details anyone wants to talk about?16:25
dougwig(as in my office.)16:25
dougwigok, moving on...16:26
dougwig#topic Statuses (Provisioning and Operating) (blogan)16:26
*** openstack changes topic to "Statuses (Provisioning and Operating) (blogan) (Meeting topic: neutron lbaas)"16:26
SantoshNetScalerFollowing is change-set addressing the earlier review comments for  NetScaler Driver for neutron_lbaas v2 APIs. https://review.openstack.org/#/c/148541/16:27
dougwigblogan: this topic is all yours.16:27
dougwigSantoshNetScaler: ty16:27
bloganso dougwig last week you had mentioned that you thought the load balancer and listener objects would have operating status and everything else provisioning status16:28
blogancurrently all objects just have a status field, which means different things for each object16:28
dougwigactually, i'd like *everything* to have both, and leave it up to the driver, but that's me.16:29
bloganwell that means the drivers have to do a lot of status management for every entity16:29
dougwig(oh, you're going to leap on leaving it to the driver.  poor phrasing.  still with the automated provisioning statuses we've talked about previously.)16:29
bloganlol16:29
*** dboik has quit IRC16:30
bloganwhat do you mean automated provisioning statuses?16:30
dougwigin the normal cases, the plugin would manage status.  in exceptional cases, the driver could just raise.  some other mechanism to enable async and tell the plugin to leave it alone.  but the driver always handles operational.16:31
dougwigthis has the makings of a dougwig/blogan argument. shall we take it offline and into channel later, or do we have any other opinions?16:32
bloganwell that would require some extra work to get that automated provisioning status still, and id like for the operational status to somehow be managed by the plugin as well but realize that is not realistic in a short amount of time16:32
xgermanI am with dougwig16:32
dougwigblogan: we'd need some way for the underlying subsystem to communicated operational state back to the plugin, for the plugin to update the status.  like, maybe, updating the status?  :-)16:33
xgermanalso how does that all work wgen we say share pools16:34
blogani know, or other ways ive thought about but in the end it is the plugin reacting on something the driver did16:34
dougwigxgerman: that goes back to the good argument to only have status trees in the LoadBalancer object.16:35
* blogan jedi mind tricks xgerman16:35
xgermanbut that is a different discussion than having two fields16:36
xgerman;-)16:36
dougwigi think one of us needs to write up a short proposal and try to converge on a plan.  we've had this discussion about 5 times now in a vacuum.  :)16:36
sballe__dougwig: +116:36
bloganwell if we have two fields on a pool, then we enable sharing then we'll have to remove those fields and cause a break in contract, which would cause a new version of the api16:36
dougwigblogan: +116:37
dougwignothing says we can't have two statuses, but only in the LB (or just one set in the LB)16:37
bloganwell one thing needs to be decided on, do we want to leave this version open to sharing objects?16:37
dougwigi'm against sharing, and always have been.  :)16:37
*** mestery has joined #openstack-meeting-416:38
bloganwell im against it right now as it is a big blocker and has been for a while16:38
xgermanok, no sharing works for me16:39
dougwigseems to be a solution searching for a problem, to me.16:39
dougwigi can see merit, but not enough to offset the implementation woes.16:39
bloganwell the problem is especially with L7 rules16:39
dougwigautocorrect just made that "implementation whores"16:39
bloganlol16:39
dougwigi'd rather see M:N on an l7 parent object than of pools.16:39
blogananyone stongly in favor of sharing objects? (if only sam was here)16:40
jorgemI need to understand the problem better16:41
ptoohillspeak of the devil16:41
ptoohilljk16:41
jorgemIs this on the ML somewhere?16:41
dougwigshort write-up to ML?  short, because no one reads long.16:41
bloganits been a discussion for a long time16:41
rm_workhave we been using the ML for the past several months? >_>16:41
bloganill write it up16:41
rm_workif so, i have some catching up to do16:41
jorgemblogan: It was a discussion a long time ago you mean?16:41
bloganim not sure i can keep it short though, but i will try16:41
bloganno its been ongoing, peaks and valleys16:42
bloganit always comes up bc it is a big decision that affects the api in a major way16:42
rm_workah i see posts about it from sam as recent as a month ago16:42
dougwig#action blogan Two status/status tree/sharing of objects writeup to ML16:42
jorgemblogan: Has the dust settled a bit on it at least. (i.e do we have a couple of options to compare?)16:43
dougwigwe just need to close on a plan and not be blocked, even if we can't get perfect consensus.16:43
bloganyes 2 options16:43
jorgemk16:43
bloganone sam has proposed and the other option is no sharing and provisioning and operating statuses remain on the entities16:43
jorgemokay ML it is16:44
bloganso aside from that, we can still decide on which entities have provisioning and operating statuses16:44
xgermanyeah, having two statuses shouldn't impact where they live16:45
dougwigi'd suggest you pick one and just say that, instead of asking the ML to decide. if you pick the wrong one, everyone will scream.16:45
xgerman+ 116:45
bloganpick one of the sharing models or where the entities live?16:45
dougwigyes.16:45
bloganlol16:45
ptoohill:P16:45
xgermanwe can have two sttauses and put them on an lb tree16:46
bloganwell im going to just go with what is there, which is similar to octavia16:46
dougwigis that two status no sharing?16:46
bloganxgerman: no point if we have two statuses on the entities and then introduce a tree, the statuses on the entities won't make sense if they're being shared16:46
bloganunless you mean just a status tree on the lb without sharing16:47
xgermanyep, there are just a ton of permutations16:47
blogantwo status is independent of sharing, its just where the statuses live that is dependent16:47
xgermanyep16:47
dougwigwe could also put a status tree on the lb without sharing, and status helper methods in the sub-objects that go look in the parent.16:48
xgermanexactly - and that might make it easier to got to sharing if we ever need to16:48
dougwig2 minutes, then we need to move on to other topics.16:48
bloganand in the db it can remain on the entities, the api just doesn't show it in the entities16:48
bloganthats going to look messy but i can go for that16:49
dougwigok, gotta move us along now.  blogan will take this up on the ML.16:50
xgermanwell, ML16:50
dougwig#topic Add constraint that V1 and V2 cannot be enabled at the same time16:50
*** openstack changes topic to "Add constraint that V1 and V2 cannot be enabled at the same time (Meeting topic: neutron lbaas)"16:50
dougwiganother one for blogan!16:50
*** mestery_ has joined #openstack-meeting-416:50
bloganthis came up with the client ctracey was writing and I believe we all agreed that we can put that constraint in, just wanted to bring it up if anyone disagrees with it16:51
jorgemHmm...16:51
jorgemso this hits on the topic of versioning going forward16:51
jorgemwhat are the plans there?16:51
ptoohillWhat would you need v1 for if v2 is enabled?16:51
dougwigi hate it as unnecessary. it came up because some folks wanted to overload the CLI/api endpoints between v1/v2.  i think i got out-voted.16:51
jorgemFor example, are we going to be able to host multiple versions, deprecate, etc.?16:51
*** dboik has joined #openstack-meeting-416:52
xgermanat one point we have to...16:52
rm_workcan we do versioning in our URL now?16:52
bloganjorgem that will go into the neutron microversioning discussion, which is in its infancy but will probably follow the nova model which i dont fully understand16:52
dougwigptoohill: operationally, I'm not sure you would. it's handy from a dev perspective.  might also make lazy upgrades a possibility, though i'm not sure we have to worry about upgrades.16:52
rm_workif we can version in our URL, it doesn't matter, the client can just take a VERSION setting (just like keystone, nova, etc)16:52
bloganrm_work: no, still beholden to neutron's, unless we did neutron.com/v2.0/lbaas/v2.016:53
rm_workblogan: hmm, i don't mind that TOO much16:53
rm_workit's not ideal...16:53
xgermanmicroversions don't need the URL - they do so with the ACCEPT header16:53
rm_workok, so, that16:53
rm_workheader versioning16:53
*** mestery has quit IRC16:53
bloganah16:53
rm_workwin?16:53
bloganid still like to know how they version all their models and api entities16:54
bloganin code16:54
rm_workugh16:54
rm_worktable-name prepend?16:54
rm_workv1_16:54
rm_workv2_ ?16:54
rm_worklol16:54
* blogan barfs of rm_work16:54
blogan*on16:54
xgermannova also has sub_modules ewith their own verisons16:54
xgermanbut again I don't know how that works16:55
rm_workyeah that's how web-shit always did it in the past (back when everyone coding for the web hated their lives -- oh wait that hasn't changed much)16:55
bloganwell lets tackle what we need to right now16:55
dougwigi think we're too far along to stop and micro-version v2. unless someone disagrees with that, can we pull back to v1/v2 simultaneous or not?16:55
*** mestery has joined #openstack-meeting-416:55
*** carl_baldwin has quit IRC16:55
xgermanwe should go v2 only16:55
ptoohill+116:55
blogandougwig: thats honestly going to be up to the neutron code16:55
sballe__+116:55
rm_worki feel like every time this comes up we ask "does anyone actually run v1?" <_<16:56
bloganim all for v1 and v2 being mutually exclusive16:56
ptoohill^^ It would be nice if we could get hold of those magical unicorns that do run it and talk with them16:56
*** mestery_ has quit IRC16:56
dougwigi just pinged kevin to ask if neutron will require it. i doubt that it would, as existing extensions would all break.16:56
dougwigptoohill: what questions would you like to ask?16:57
rm_work"do you care about running v1 and v2 at the same time?"16:57
rm_workfor starters16:57
ptoohilloh, you are magical unicorn???16:57
ptoohillbut yea, that16:57
dougwigi know many unicorns.16:57
dougwignone of them would care.16:57
ptoohillWould like to hear their opinion on that,16:58
ptoohillwell that settles that i suppose16:58
ptoohill:P16:58
rm_workk, well, that's an easy answer then16:58
dougwigor rather, i'm sure they'd be fine running it on separate hosts.16:58
rm_work^^ holy shit this16:58
rm_workwho would even want to run it all on the same host <_<16:58
rm_workand then, it doesn't matter at all16:58
*** mestery has quit IRC16:59
rm_worklbaas.myhost.com + v2.lbaas.myhost.com16:59
rm_workdone16:59
jorgemeek16:59
bloganwell its the api node that decides which version to run17:00
bloganor which plugin to run17:00
dougwigyeah, that's what i'm pondering.17:00
*** VW_ has joined #openstack-meeting-417:00
bloganso usually you just have one consistent api, two hosts for the api17:00
rm_workugh and neutron has to be our API host?17:00
dougwigdb tables need stay separate.17:00
*** mestery has joined #openstack-meeting-417:00
dougwigrm_work: for kilo, yes.17:00
bloganfor neutron-lbaas, for now yes17:00
rm_workso they'd need different neutron hosts of the same version, for two different lbaas versions >_< bah17:01
bloganwhich is what we had17:01
dougwigyeah, i'm not liking that much.  different agent nodes, fine.  but then we get back to needing separate CLI commands.17:01
bloganwell what we had when we allowed both versoin to be running17:01
blogani think we're in a consensus, other than dougwigs reservations17:02
dougwigmaybe if we use a similar CLI namespace, but require an environment variable if they want to access v1 while v2 is loaded?17:02
dougwigi can take my questions offline.17:02
dougwigoops, we're over.17:02
dougwigthanks and by folks.17:02
ptoohillIll work on the agent-ified driver BTW dougwig, forgot to respond earlier.17:02
dougwigptoohill: awesome, thanks.17:02
*** emagana has joined #openstack-meeting-417:02
dougwig#endmeeting17:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:02
sballe__bye17:02
openstackMeeting ended Tue Jan 20 17:02:50 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_lbaas/2015/neutron_lbaas.2015-01-20-16.00.html17:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_lbaas/2015/neutron_lbaas.2015-01-20-16.00.txt17:02
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_lbaas/2015/neutron_lbaas.2015-01-20-16.00.log.html17:02
*** johnsom has left #openstack-meeting-417:04
*** VW_ has quit IRC17:06
*** tholtzen has joined #openstack-meeting-417:07
*** SantoshNetScaler has quit IRC17:08
*** pc_m has left #openstack-meeting-417:12
*** tholtzen has quit IRC17:13
*** jorgem has quit IRC17:19
*** evgenyf has quit IRC17:20
*** matrohon has quit IRC17:22
*** galstrom is now known as galstrom_zzz17:24
*** galstrom_zzz is now known as galstrom17:31
*** mestery has quit IRC17:33
*** mestery has joined #openstack-meeting-417:34
*** dboik has quit IRC17:44
*** mestery has quit IRC17:51
*** banix has quit IRC17:51
*** kobis has quit IRC17:53
*** mestery has joined #openstack-meeting-417:53
*** yamahata has joined #openstack-meeting-417:54
*** dboik has joined #openstack-meeting-417:56
*** pkoniszewski has quit IRC17:56
*** igordcard has quit IRC17:58
*** VW_ has joined #openstack-meeting-417:59
*** dboik has quit IRC17:59
*** dboik has joined #openstack-meeting-417:59
*** galstrom is now known as galstrom_zzz18:00
*** mestery has quit IRC18:04
*** mestery has joined #openstack-meeting-418:06
*** xgerman has left #openstack-meeting-418:08
*** banix has joined #openstack-meeting-418:09
*** jorgem has joined #openstack-meeting-418:12
*** matrohon has joined #openstack-meeting-418:12
*** ivar-lazzaro has joined #openstack-meeting-418:17
*** ivar-lazzaro has quit IRC18:18
*** ivar-lazzaro has joined #openstack-meeting-418:19
*** ajmiller has quit IRC18:38
*** ajmiller has joined #openstack-meeting-418:38
*** VW_ has quit IRC18:44
*** carl_baldwin has joined #openstack-meeting-418:49
*** VW_ has joined #openstack-meeting-418:49
*** mestery_ has joined #openstack-meeting-418:52
*** mestery has quit IRC18:55
*** lakshmiS has quit IRC18:55
*** mestery has joined #openstack-meeting-419:01
*** VW_ has quit IRC19:03
*** mestery_ has quit IRC19:03
*** mestery has quit IRC19:14
*** SridharRamaswamy has joined #openstack-meeting-419:15
*** carl_baldwin has quit IRC19:16
*** carl_baldwin has joined #openstack-meeting-419:17
*** banix has quit IRC19:23
*** isq has joined #openstack-meeting-419:32
*** david-lyle has quit IRC19:37
*** openstackstatus has joined #openstack-meeting-419:45
*** ChanServ sets mode: +v openstackstatus19:45
*** banix has joined #openstack-meeting-419:49
*** carl_baldwin has quit IRC19:51
*** sbalukoff has joined #openstack-meeting-419:53
-openstackstatus- NOTICE: Gerrit restarted to address likely memory leak leading to server slowness. Sorry if you were caught in the restart19:53
*** SridharRamaswamy has quit IRC19:53
*** banix has quit IRC19:59
*** SridharRamaswamy has joined #openstack-meeting-420:03
*** jorgem has quit IRC20:06
*** banix has joined #openstack-meeting-420:09
*** dboik has quit IRC20:14
*** dboik has joined #openstack-meeting-420:14
*** VW_ has joined #openstack-meeting-420:18
*** VW_ has quit IRC20:18
*** VW_ has joined #openstack-meeting-420:19
*** dboik has quit IRC20:20
*** dboik_ has joined #openstack-meeting-420:20
*** VW_ has quit IRC20:27
*** salv-orlando has quit IRC20:45
*** dboik_ has quit IRC20:51
*** dboik has joined #openstack-meeting-420:51
*** VW_ has joined #openstack-meeting-420:52
*** krtaylor has quit IRC21:00
*** jamiem has quit IRC21:02
*** dboik has quit IRC21:03
*** dboik has joined #openstack-meeting-421:03
*** SridharRamaswam1 has joined #openstack-meeting-421:03
*** SridharRamaswamy has quit IRC21:04
*** jorgem has joined #openstack-meeting-421:06
*** salv-orlando has joined #openstack-meeting-421:08
*** salv-orlando has quit IRC21:09
*** salv-orlando has joined #openstack-meeting-421:10
*** krtaylor has joined #openstack-meeting-421:13
*** matrohon has quit IRC21:19
*** matrohon has joined #openstack-meeting-421:24
*** banix has quit IRC21:30
*** banix has joined #openstack-meeting-421:33
*** galstrom_zzz is now known as galstrom21:37
*** banix has quit IRC21:40
*** jorgem has quit IRC21:42
*** SridharRamaswam1 has quit IRC21:45
*** banix has joined #openstack-meeting-421:49
*** SridharRamaswamy has joined #openstack-meeting-422:14
*** banix has quit IRC22:29
*** igordcard has joined #openstack-meeting-422:35
*** igordcard has quit IRC22:36
*** matrohon has quit IRC22:42
*** dboik has quit IRC23:01
*** s3wong has joined #openstack-meeting-423:06
*** VW_ has quit IRC23:09
*** VW_ has joined #openstack-meeting-423:11
*** sballe__ has quit IRC23:18
*** ChuckC has quit IRC23:21
*** ChuckC has joined #openstack-meeting-423:21
*** ChuckC has quit IRC23:30
*** galstrom is now known as galstrom_zzz23:36
*** ChuckC has joined #openstack-meeting-423:42
*** ivar-laz_ has joined #openstack-meeting-423:42
*** ivar-lazzaro has quit IRC23:45

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