Tuesday, 2015-02-17

*** narenhn has quit IRC00:03
*** markvoelker has joined #openstack-meeting-400:04
*** markvoelker has quit IRC00:09
*** sbalukoff has quit IRC00:13
*** sarob has joined #openstack-meeting-400:26
*** sbalukoff has joined #openstack-meeting-400:29
*** sarob has quit IRC00:31
*** SridharRamaswamy has joined #openstack-meeting-400:52
*** SridharRamaswamy has joined #openstack-meeting-400:52
*** SridharRamaswamy has quit IRC00:57
*** markvoelker has joined #openstack-meeting-401:05
*** markvoelker has quit IRC01:11
*** sigmavirus24 is now known as sigmavirus24_awa01:17
*** banix has quit IRC01:19
*** banix has joined #openstack-meeting-401:23
*** sarob has joined #openstack-meeting-401:28
*** VW_ has joined #openstack-meeting-401:32
*** sarob has quit IRC01:32
*** VW_ has quit IRC01:55
*** markvoelker has joined #openstack-meeting-402:08
*** markvoelker has quit IRC02:13
*** salv-orlando has quit IRC02:13
*** sarob has joined #openstack-meeting-402:29
*** sarob has quit IRC02:34
*** markvoelker has joined #openstack-meeting-403:09
*** sarob has joined #openstack-meeting-403:12
*** salv-orlando has joined #openstack-meeting-403:14
*** markvoelker has quit IRC03:14
*** galstrom_zzz is now known as galstrom03:39
*** emagana has joined #openstack-meeting-403:51
*** fnaval has quit IRC03:54
*** markvoelker has joined #openstack-meeting-404:10
*** galstrom is now known as galstrom_zzz04:10
*** markvoelker has quit IRC04:16
*** ajmiller_ is now known as ajmiller04:22
*** SridharRamaswamy has joined #openstack-meeting-404:35
*** emagana_ has joined #openstack-meeting-404:37
*** SridharRamaswamy has quit IRC04:39
*** SridharRamaswamy has joined #openstack-meeting-404:39
*** emagana has quit IRC04:40
*** jckasper has joined #openstack-meeting-404:52
*** jckasper_ has quit IRC04:53
*** banix has quit IRC05:08
*** markvoelker has joined #openstack-meeting-405:12
*** yamahata has joined #openstack-meeting-405:14
*** markvoelker has quit IRC05:17
*** ajmiller has quit IRC05:27
*** sarob has quit IRC05:52
*** markvoelker has joined #openstack-meeting-406:13
*** SridharRamaswam1 has joined #openstack-meeting-406:15
*** SridharRamaswamy has quit IRC06:16
*** markvoelker has quit IRC06:19
*** SridharRamaswam1 has quit IRC06:25
*** sarob has joined #openstack-meeting-406:57
*** yamahata has quit IRC07:00
*** sarob has quit IRC07:04
*** evgenyf has joined #openstack-meeting-407:07
*** salv-orlando has quit IRC07:07
*** markvoelker has joined #openstack-meeting-407:15
*** markvoelker has quit IRC07:21
*** wojdev has joined #openstack-meeting-407:52
*** rm_work is now known as rm_work|away07:57
*** kobis has joined #openstack-meeting-407:58
*** wojdev has quit IRC08:05
*** belmoreira has joined #openstack-meeting-408:09
*** belmoreira has quit IRC08:14
*** markvoelker has joined #openstack-meeting-408:17
*** markvoelker has quit IRC08:22
*** sarob has joined #openstack-meeting-408:25
*** sarob has quit IRC08:31
*** matrohon has joined #openstack-meeting-408:36
*** salv-orlando has joined #openstack-meeting-408:38
*** ivar-lazzaro has quit IRC08:47
*** wojdev has joined #openstack-meeting-409:01
*** salv-orlando has quit IRC09:15
*** markvoelker has joined #openstack-meeting-409:18
*** markvoelker has quit IRC09:23
*** sarob has joined #openstack-meeting-409:28
*** sarob has quit IRC09:36
*** salv-orlando has joined #openstack-meeting-410:03
*** markvoelker has joined #openstack-meeting-410:19
*** markvoelker has quit IRC10:24
*** sarob has joined #openstack-meeting-410:33
*** pkoniszewski has joined #openstack-meeting-410:35
*** sarob has quit IRC10:41
*** salv-orlando has quit IRC11:02
*** rfolco has joined #openstack-meeting-411:10
*** wojdev has quit IRC11:16
*** markvoelker has joined #openstack-meeting-411:20
*** markvoelker has quit IRC11:25
*** bobmel has quit IRC11:31
*** bobmel has joined #openstack-meeting-411:31
*** sarob has joined #openstack-meeting-411:38
*** sarob has quit IRC11:42
*** VW_ has joined #openstack-meeting-411:49
*** wojdev has joined #openstack-meeting-411:54
*** salv-orlando has joined #openstack-meeting-412:02
*** banix has joined #openstack-meeting-412:19
*** markvoelker has joined #openstack-meeting-412:21
*** markvoelker has quit IRC12:26
*** sarob has joined #openstack-meeting-412:42
*** sarob has quit IRC12:49
*** salv-orlando has quit IRC12:50
*** salv-orlando has joined #openstack-meeting-412:50
*** markvoelker has joined #openstack-meeting-412:52
*** banix has quit IRC12:57
*** galstrom_zzz is now known as galstrom13:02
*** wojdev has quit IRC13:04
*** wojdev has joined #openstack-meeting-413:05
*** jckasper has quit IRC13:13
*** galstrom is now known as galstrom_zzz13:41
*** jckasper has joined #openstack-meeting-413:47
*** HenryG has quit IRC13:49
*** sarob has joined #openstack-meeting-413:49
*** HenryG has joined #openstack-meeting-413:52
*** belmoreira has joined #openstack-meeting-413:54
*** sarob has quit IRC13:57
*** klamath has joined #openstack-meeting-413:59
*** klamath has quit IRC14:00
*** klamath has joined #openstack-meeting-414:00
*** VW_ has quit IRC14:06
*** banix has joined #openstack-meeting-414:10
*** rfolco_ has joined #openstack-meeting-414:13
*** rfolco has quit IRC14:13
*** watanabe_isao has quit IRC14:20
*** kobis has quit IRC14:30
*** kobis has joined #openstack-meeting-414:31
*** VW_ has joined #openstack-meeting-414:41
*** nfedotov1 has joined #openstack-meeting-414:45
*** VW_ has quit IRC14:48
*** sarob has joined #openstack-meeting-414:54
*** sigmavirus24_awa is now known as sigmavirus2414:54
*** dboik has joined #openstack-meeting-414:55
*** vikram has joined #openstack-meeting-414:57
*** pc_m has joined #openstack-meeting-415:00
*** banix has quit IRC15:00
*** mestery_ is now known as mestery15:01
pc_mhi15:01
matrohonhi15:02
pc_mmatrohon: hi15:02
pc_mgiving a few mins for people to hop on15:02
vikramhi15:02
pc_mvikram: hi15:03
nfedotov1Hello All!15:03
pc_mnfedotov1: hi!15:03
pc_mOK, let's start...15:03
pc_m#startmeeting vpnaas15:04
openstackMeeting started Tue Feb 17 15:04:06 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:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:04
*** openstack changes topic to " (Meeting topic: vpnaas)"15:04
openstackThe meeting name has been set to 'vpnaas'15:04
pc_m#topic Announcements15:04
*** openstack changes topic to "Announcements (Meeting topic: vpnaas)"15:04
*** sarob has quit IRC15:05
*** banix has joined #openstack-meeting-415:05
pc_mFunctional gate is non-voting. Will defer making it voting, as some changes may be needed (will disuss)15:05
pc_mStrongSwan functional/scenario tests will need a separate job due to setup needs are different.15:06
pc_mIf you have functional tests, please put them out for review and check functional test results from Jenkins.15:06
pc_mPlease help out on reviews15:07
pc_mAnyone have any other new announcements?15:07
pc_m#topic Functional Testing15:07
*** openstack changes topic to "Functional Testing (Meeting topic: vpnaas)"15:07
pc_mAs mentioned, check dsvm-neutron-vpnaas-functional test results on your reviews15:08
pc_mFor StrongSwan, we're seeing that we need to have it installed (for Ubuntu 14.04) and AppArmor disabled.15:09
pc_mAs a result a new job will be needed to test this.15:09
pc_mMust figure out the best way to organize the directory structure to support OpenSwan vs StrongSwan testing.15:10
pc_mI posted an email on the ML this morning asking for feedback from QA team on this an many other items.15:10
pc_mMy thoughts are that maybe it may be best to have a sub-dir called strongswan and use filters to only run tests in that area, when the new job runs.15:11
*** salv-orlando has quit IRC15:11
pc_mWe do need to develop functional tests for both OpenSwan and StrongSwan.15:11
pc_mIf you have time to help out, please chime in.15:12
pc_mYou can provide review comments on Zhang's functional tests for StrongSwan under https://review.openstack.org/#/c/144391/15:13
pc_mAny questions/comments on Functional testing?15:13
nfedotov1Sorry for interupting you. Are there any difference between OpenSwan and StrongSwan from API point of view?15:13
*** salv-orlando has joined #openstack-meeting-415:13
pc_mnfedotov1: Sure, np at all... no the API is the same.15:13
nfedotov1In my understanding OpenSwan and StrongSwan is a two diferrent implementations of a singel API.15:14
pc_mStrongSwan has more capabilities, and I think, for some things, like encryption protocols, the client API accepts strings, so can handle both.15:14
pc_mnfedotov1: From a OpenStack standpoint yes.15:14
pc_mAny other Qs on the functional tests?15:15
*** carl_baldwin has joined #openstack-meeting-415:16
nfedotov1And I expect functional tests have (or maybe should have) same  Design Principles as tempest. I mean "Tests in Tempest should only touch public interfaces, API calls"15:16
*** rm_work|away is now known as rm_work15:18
pc_mThere's a lot of confusion (on my part at least) between the tempest tests (which I understand tempest is a tool and repo), and functional tests (which we're placing in our repo, and which use devstack, but not the tempest libraries).15:18
pc_mPlease see the email I sent, on openstack-dev mailing list and chime in on that topic. There I expressed what I think are our goals, namely...15:19
nfedotov1Ahh. OK. Thanks for reply. I will take a look15:20
pc_mTo have functional test coverage of the device driver implementations (we have limited coverage), and to have a end to end scenario test to check operation.15:20
nfedotov1Yes there are a lot confusions around functional tests15:20
pc_mnfedotov1: There is a bunch of issues around the scenario tests (also discussed in that email). Let's talk about that for a bit...15:21
pc_m#topic Scenario Testing15:21
*** openstack changes topic to "Scenario Testing (Meeting topic: vpnaas)"15:21
pc_mSo here are the issues here...15:21
pc_m1) We'll need different jobs, as StrongSwan needs a different setup that OpenSwan.15:22
pc_m2) Right now we have two (slightly different) scenario tests created and out for review, under Tempest repo. We need to decide which to go forward with.15:23
nfedotov1Do you mean jobs in check gate?15:23
pc_m3) They are not allowing *aaS tests to be added to Tempest, because that is migrating to Neutron in tree and a tempest lib is being setup.15:24
*** kobis has quit IRC15:24
pc_mnfedotov1: We'll need to have two separate jobs that run in check/gate pipelines, one that sets up for OpenSwan, and a separate job for StrongSwan.15:25
pc_mCan't run them both under same job, because they both cannot be installed in a system at the same time, and because StrongSwan needs to have apparmor disabled.15:25
pc_mSo #1 is sort of mechanical. I guess a pre_test_hook will be needed to setup the environment right.15:27
pc_mFor #2, we, as a team, need to decide on which of the two implementations should be used. We have...15:27
pc_m#link https://review.openstack.org/#/c/140072/815:28
pc_m#link https://review.openstack.org/#/c/153292/515:28
pc_mBoth authors are fine with either proceeding. Zhang is on vacation for 10 days.15:28
nfedotov1Yes there should be some script that configures test environment. Is it possible to use Devstack for it?15:28
pc_mnfedotov1: My undertstanding (from talking to people) is that the pre_test_hook should set that up.15:29
pc_mHowever, issue #3 is the big one.15:29
matrohonI don't understand what is the fundamental difference between those two scenario tests?15:30
matrohonthey cant be merged?15:30
pc_mmatrohon: Not much, two independent implementations of the same test. One does pings and one does ssh to check connection.15:30
pc_mThe one with pings checks before and after.15:31
pc_mNikolay is willing to proceed forward with his version, and Zhang was cool with that as well.15:31
pc_mIs that OK with folks?15:31
matrohonzhang's patch also seems to ping15:32
matrohonok, the most important here is to have a first test available15:32
pc_mmatrohon: I think Zhang's pings, and Nikolay's ssh'es15:32
matrohonpc_m : ha ok!15:33
pc_mIf I scanned them right. Not sure that much about the tests.15:33
nfedotov1There is a basic use case for vpnaas. Here: https://wiki.openstack.org/wiki/Neutron/VPNaaS/HowToInstall , section "IPSec Site-to-site Connection Creation"15:33
nfedotov1I think both patchsets do this scenario. At least my patchset follows steps described there.15:33
pc_mWith Zhang's it is obvious what the subnet's IPs are in the test.15:33
*** VW_ has joined #openstack-meeting-415:34
pc_mnfedotov1: Does yours use a single node and two routers/nets/subnets (hard to tell what the tempest calls all do)15:34
pc_m?15:34
nfedotov1It uses two instaces. Each one is connected to dedicated private network + dedicated router15:35
pc_mDo we know if Zhang's also does that? I thought it used one devstack instance...15:36
nfedotov1so there are two sides: instance -> private network (subnet) -> router (router IP)15:36
*** Aish has joined #openstack-meeting-415:37
pc_mnfedotov1: Just to clarify, by instance, do you mean that there are two devstack nodes started up, or is this one devstack node, with two routers and two private nets?15:37
pc_m(and two VM instances on that single devstack)15:38
nfedotov1Yes. There is one devstack node (all-in-one), one tenant, one user15:38
pc_mnfedotov1: So two routers, subnets, on one node. So, I think the two implementations are pretty close.15:39
nfedotov1and two instances15:39
nfedotov1It looks like Zhang's patchset does same thing.15:39
pc_mDoes anyone have any strong preference for one over the other? If not, then we should focus on reviewing nfedotov1, because he's available to proceed on this now.15:40
pc_mThoughts?15:40
pc_m#action team to review https://review.openstack.org/#/c/140072/8 for Scenario test15:41
nfedotov1well I can pick some best things from Zhang's patchset. And later if Zhang wants to change something I will not mind15:41
pc_mnfedotov1: Great, will be good for you two to collaborate, when Zhang is back.15:42
nfedotov1Ok15:42
pc_mThe big issue is #3.15:42
pc_mI've asked in the email if we can get an exception and add this scenario test into tempest, before the migration.15:43
nfedotov1But eventually they will be removed. Yes?15:44
pc_mOtherwise, we have to either wait for migration and availability of tempest lib, or try to adapt this to run without tempest, which doesn't really sound good to me (not leveraging over the avail infra).15:44
*** kobis has joined #openstack-meeting-415:44
pc_mnfedotov1: Well, they will be migrated to run under Neutron (in-tree), and then the VPN ones will be moved to the VPN repo.15:44
*** vikram has quit IRC15:45
pc_mConcern here is over whether we can do all that for K-3.15:45
*** TrevorV has joined #openstack-meeting-415:45
pc_mDoes anyone have any other ideas on this? I don't know if there is any better way to do the scenario test.15:45
nfedotov1Maybe it would be better to place tests to neutron-vpnaas. In my opinion15:46
pc_m#action nfedotov1 will collaborate with zhang and merge in useful bits from other commit.15:46
pc_mnfedotov1: To place them directly in the VPN repo now?15:47
nfedotov1Maybe I do not know some obstacles that prevents us from doing this.15:48
pc_mTo do that, we need the tempest lib or modify the test to run w/o tempest libs. Not sure when that will be available (I asked in email).15:48
pc_m#action Get decision from QA team on whether scenario test can be added to tempest or when tempest lib will be available15:48
pc_mAny more discussion on the scenario/functional tests? We've got 10 mins left for other items.15:49
pc_m#topic Bugs15:50
*** openstack changes topic to "Bugs (Meeting topic: vpnaas)"15:50
pc_mPlease take a look at the bugs out and provide review comments. There are about 10 out.15:51
pc_mOh, I forgot to mention. After setting up coverage testing, I've put out another commit for review to enable coverage testing of any functional tests.15:52
pc_mHere's the bug list: https://review.openstack.org/#/c/140072/8 If you have any of interest t discuss here, please speak up.15:53
matrohonpc_m : ^^wrong link?15:53
pc_mWhoops...  https://review.openstack.org/#/q/status:open+project:openstack/neutron-vpnaas,n,z15:54
pc_m#topic Open Discussion15:54
*** openstack changes topic to "Open Discussion (Meeting topic: vpnaas)"15:54
pc_mAnyone have any other questions/concerns to discuss?15:55
*** rromans has joined #openstack-meeting-415:55
*** wojdev has quit IRC15:55
pc_mOK. that's a wrap then. Thanks for joining in, and please take a look at the open reviews so people can progress on their commits.15:56
*** ajmiller has joined #openstack-meeting-415:56
pc_m#endmeeting15:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:56
openstackMeeting ended Tue Feb 17 15:56:56 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vpnaas/2015/vpnaas.2015-02-17-15.04.html15:56
pc_mbye all!15:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vpnaas/2015/vpnaas.2015-02-17-15.04.txt15:57
openstackLog:            http://eavesdrop.openstack.org/meetings/vpnaas/2015/vpnaas.2015-02-17-15.04.log.html15:57
nfedotov1thank you. buy15:57
nfedotov1...bye15:57
*** pc_m has left #openstack-meeting-415:58
*** xgerman has joined #openstack-meeting-415:58
dougwigo/15:58
*** johnsom has joined #openstack-meeting-415:59
xgermano/15:59
rm_worko/15:59
johnsomo/15:59
rm_workmeeting start?15:59
kobishi15:59
xgerman60 s15:59
johnsomI always wonder that myself15:59
bloganhi16:00
dougwig#startmeeting neutron lbaas16:00
openstackMeeting started Tue Feb 17 16:00:08 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
*** rromans has left #openstack-meeting-416:00
dougwig#topic roll call16:00
*** openstack changes topic to "roll call (Meeting topic: neutron lbaas)"16:00
xgermano/16:00
ajmillerGood Morning16:00
dougwigagenda:16:00
dougwighttps://wiki.openstack.org/wiki/Network/LBaaS#Agenda16:00
rm_worko/16:00
TrevorVo/16:00
johnsomo/16:00
*** sarob has joined #openstack-meeting-416:01
evgenyfHi16:01
dougwig#topic Announcements16:02
*** openstack changes topic to "Announcements (Meeting topic: neutron lbaas)"16:02
dougwigSummit talk info16:02
*** fnaval has joined #openstack-meeting-416:02
dougwiggathering thoughts for our summit stuff here:16:02
dougwighttps://etherpad.openstack.org/p/lbaas-vancouver-talks16:02
ptoohillo/16:02
dougwigAnd a few talks to consider voting on:16:02
dougwigour friends at haproxy:16:02
dougwighttp://www.openstack.org/vote-vancouver/presentation/cool-haproxy-tips-you-want-to-know16:02
fnavalo/16:02
*** mcginn has joined #openstack-meeting-416:02
dougwigours:16:03
dougwighttp://www.openstack.org/vote-vancouver/presentation/load-balancing-as-a-service-temp16:03
dougwighttp://www.openstack.org/vote-vancouver/presentation/neutron-mitosis-and-the-l7-services-roadmaps16:03
sballe__morning16:03
dougwigany others folks want to highlight for this group?16:03
Aisho/16:03
dougwigLast announcement from me: Kilo-3 is coming up fast (code proposal deadline is 3/5).  Vendor drivers especially, the earlier you submit the higher chance we'll have review cycles.16:04
dougwigyou realistically want to be a week before the 5th, in case there need to be a few roundtrips (find code is about 5 days after that)16:05
dougwig /find/final/16:05
dougwigany other announcements?16:06
rm_workgoing to squeeze this in as it's somewhat time sensitive: it would be super useful if people would go +1 this (if you haven't already): https://review.openstack.org/#/c/156623/ (would like to have a decent number of +1s by the time we discuss this at the Barbican meetup)16:06
*** dboik has left #openstack-meeting-416:06
*** santosh has joined #openstack-meeting-416:06
dougwigthat's the castellan tis library stuff, fyi.16:06
rm_workyes16:06
dougwigtls16:06
rm_workSo the thing I've been promising for a while now :)16:06
dougwig:)16:06
dougwig#topic v2 update16:07
*** openstack changes topic to "v2 update (Meeting topic: neutron lbaas)"16:07
rm_workThere's discussion about whether to include Certs in it or not -- the "not" case would be sucky for us16:07
dougwigHow our agent driver coming?  Any blocking issues?16:07
bloganyes these reviews16:07
*** nfedotov1 has quit IRC16:07
bloganhttps://review.openstack.org/#/c/155545/16:07
bloganhttps://review.openstack.org/#/c/155051/16:07
*** sarob has quit IRC16:08
dougwiggreat.  i'll put them on my list for today.  other eyeballs would also be good.16:08
dougwigTesting...  how are we doing?16:08
santoshhi All16:08
bloganafter those, the agent driver base is ready to be reviewed, the actual agent is being worked on by jorge, phil and myself so we can get it knocked out16:08
fnavaldougwig: we have some outstanding PRs that are in the process of getting fixed16:09
fnavalI think we'll be done with the initial API tests by the end of the week.16:09
dougwiggreat.  how far do you think we are from a jenkins job?16:09
*** jorgem has joined #openstack-meeting-416:09
dougwigyou are telepathic.  :)16:09
dougwigTLS & L7?16:09
fnavalI'm currently researching how to do the scenario tests.  but ran into some issues with connectiing a network to a server in devstack16:09
dougwigfnaval: does the existing v1 scenario test help at all?16:10
evgenyfTLS & L7 - waiting for reviews16:10
evgenyfhttps://review.openstack.org/#/c/145085/16:10
dougwigevgenyf: can you link them here if you have them handy?16:10
evgenyfhttps://review.openstack.org/#/c/148232/516:10
fnavaldougwig:  it does - i'm basing off the test I'm writing off of it16:10
fnavaldougwig: i'm sure how to go about in setting up a jenkins job for it externally.16:11
dougwigfnaval: you might want to ping mtreinish and get his opinion.  there are things he doesn't like about that test.16:11
dougwigfnaval: i can help with that when the code is ready.16:11
dougwigevgenyf: thank you16:11
fnavaldougwig: ok thanks16:11
dougwigDocs? I think HP was taking those on?16:11
xgermanyep, mwang2 was working on those16:12
bloganhttps://review.openstack.org/#/c/148687/16:12
bloganneeds some reviews and address comments16:12
xgermanok, I will let Min know16:12
dougwigdo we have install or cli usage docs, like v1?  are we planning those?16:12
dougwigblogan: thanks for the link16:13
dougwigDevstack?  I saw that Al had new reviews up.16:13
blogandougwig: if anyone wants to tackle thsoe, it would add value fo rsure16:13
ajmillerYes.  I need to post an update to the readme, but otherwise I think it is ready to go.16:13
dougwighere's the lbaas side of ajmiller's review:16:14
dougwighttps://review.openstack.org/#/c/155540/16:14
ajmillerAnd this is the devstack side:16:14
ajmillerhttps://review.openstack.org/#/c/153079/16:14
dougwigAny takers for install or CLI docs?  Anyone awake yet?  :)16:14
xgermanAish?16:14
dougwigxgerman: can you coordinate finding an owner for that?16:15
xgermanyep, we will find someone16:15
dougwigxgerman: thank you.16:15
dougwigStats?  blogan had comments here.16:15
bloganso the stats are currently just a total for a load balancer16:16
blogani believe we had discussions where the stats would be split up by listener16:17
xgermanyep, that would be better16:17
Aishyes.. German..?16:17
dougwigif we're going to change anything, let's finalize a decision *today*.16:17
xgermanAish, Al + I will take it offline16:17
bloganeven if it is split up by listener, the REST API will still have the stats call off the load balancer16:18
Aishokay.16:18
bloganand the body will have to split it up by listener16:18
xgermanworlks for me16:19
dougwigfine by me as well.16:19
bloganso option 1) dont split up now, add that in later since that is just additional fields in the response body, so its not backwards incompatible16:19
TrevorVBlogan you mean you'll have a list of listener stats where each object in the list will include the id of the listener they pertain to?  Sorta thing?16:19
bloganyes TrevorV16:19
TrevorVkk16:19
bloganoption 2) split up now, which requires a change in how the drivers return their stats16:20
*** galstrom_zzz is now known as galstrom16:20
bloganif someone thinks they can do option 2 now, great go for it16:20
dougwigor 1+2) split it now for ref, allow the listener data to be optional for others.16:20
xgermandougwig +1`16:20
bloganbut id still like the REST stats call body to return total stats for a load balancer16:21
xgermanso why can't we do that?16:21
bloganso if its optional, the REST call returns nothing for the listeners?16:21
xgermanreturn both?16:21
dougwigi'm not seeing an incompatible change here, so if we have time, let's do it.  if not, we can add it later?16:21
bloganxgerman: we can16:21
blogandougwig: yeah its not incompatible if we add it later16:22
xgermanlet's try to squeeze it in -- if not we do it later...16:22
bloganit might be a change for the drivers though, but if we go with the mentality that listener stats is optional for a driver then that works16:22
bloganwell to squeeze it in, someone needs to do it16:22
dougwigi think we can add methods to the object managers and it's not backwards incompatible with the drivers.16:22
dougwigwe just have to write the plugin to cope with a default base class return value.16:23
bloganyeah, there's a few way to skin it16:23
dougwigok, i'm calling this horse dead.  :)16:24
dougwig#topic The future of this meeting16:24
*** openstack changes topic to "The future of this meeting (Meeting topic: neutron lbaas)"16:24
bloganunless someone wants to volunteer to give CPR to that horse16:24
*** wojdev has joined #openstack-meeting-416:24
xgermanI am trying to volunteer people but they are not responding...16:24
bloganyou mean voluntell people eh?16:25
xgermanlike jorgem16:25
dougwigthis topic is to get folks thinking.  after kilo, without v2, we won't have much to talk about.  so, options are: 1) we get a new big feature list brainstormed at vancouver, 2) we fold this meeting into the neutron on-demand agenda, 3) we fold together lbaas and octavia, or 4) we keep getting up early because we enjoy the sunny conversation.16:25
jorgemhey now16:25
rm_work#vote 316:25
johnsomHahaha16:25
jorgem#416:25
dougwigis this community ready for another big rush of features, or do we need time to assimilate v2?16:26
johnsomI think once V2, TLS, and L7 are cooked we go for #316:26
blogan#vote 3, we'll have a lot to talka botu to implement sharing, but i think that will all be implementation discussions16:26
xgermanfold ocatvia in lbaas?16:26
dougwigxgerman: merge those two meetings.16:26
sballe__I like #316:26
jorgem#3 too.16:26
kobis#3 makes sense. #1 is ideal, dunno about realistic :)16:27
xgermanjorgem, you can hve #3 and #4 :-()16:27
dougwigi'm not in a hurry to make a decision, but something else to consider: which meeting slot do we use if we merge?  it'd be better for our overseas members to not do US afternoon.16:27
rm_workT_T16:27
jorgem:)16:27
sballe__dougwig: +116:27
blogani think #1 will need to happen after everything has settled down and stabilized16:27
sballe__blogan: I agree with you16:27
kobisblogan: +116:28
dougwigno fans of using the neutron on-demand format?  (you add topics to the wiki when you have something to talk about, use their rotating slots.)16:28
xgermanI don't ven know when the neutron meeting is16:28
dougwiglol16:28
rm_workyeah what is this Neutron thing16:28
*** Chitr has joined #openstack-meeting-416:28
dougwigwe are, technically, part of the neutron project.  :)16:28
blogandougwig: not at this moment, but if we get to a point where we have nothing to talk about in many meetings then that would make sense16:28
rm_workI thought we revolted and made our own country16:28
TrevorVdougwig I'm a fan of the on-demand one16:29
xgermanwell, we finish lbaas meeting and octavia meeting often early so combining wpould make sense16:29
rm_work$@$% it TrevorV16:29
rm_worklol16:29
kobisso we have to monitor the neutron agenda? how does it work?16:29
jorgemrm_work: We are like the Texas of manifest destiny16:29
blogankobis: same as lbaas, just longer16:29
xgermanlink?16:29
sballe__rm_work: +116:29
*** galstrom is now known as galstrom_zzz16:29
dougwigkobis: yes. their decisions affect us quite a bit, so I go to those anyway (in addition to being interested in neutron in general, anyway.)16:30
bloganhttps://wiki.openstack.org/wiki/Network/Meetings16:30
dougwighere's neutron's agenda:16:30
dougwighttps://wiki.openstack.org/wiki/Network/Meetings16:30
dougwigscroll down to the "On Demand" section.  anyone can add any topic in there.16:30
dougwigmost of the neutron meeting is usually stuff from that part of the agenda.16:31
kobisthat would make sense only if lbaas+octavia won't fill a weekly meeting in any case16:31
bloganyeah, i think the natural evolution is to first combine lbaas into octavia, and then to the on-demand16:31
dougwigor if the crowds involve diverge.16:31
xgerman+116:31
kobistowgan: +116:31
bloganlol16:31
dougwiglol16:31
rm_workso, merge for now, revisit later16:31
xgermanlol16:31
xgerman+10016:32
blogandougwig: crowds involve diverge?16:32
dougwiglet's decide at or after vancouver.16:32
sballe__perfect16:32
dougwigblogan: if the folks involved in octavia and neutron lbaas start to diverge.  right now, they are very similar.16:32
bloganah ok i see16:33
dougwig#topic Open discussion16:33
*** openstack changes topic to "Open discussion (Meeting topic: neutron lbaas)"16:33
xgermanso you don't think we can assimilate...16:33
kobisQ: do we have/want to set any convention for how to hold lbaas v1/v2?16:33
dougwigparse failure.16:33
dougwigkobis:16:33
kobise.g under <vendor>/v1/driver <vendor>/v2/driver16:34
kobisor <vendor>/driver_v116:34
kobisetc?16:34
blogankobis actually the new agent changes addresses that16:35
dougwigi was planning $vendor/driver_v{1,2}, but i'm pretty neutral on the subject.16:35
dougwigoh right.  blogan, do you want to describe that?16:35
ChitrCan you share status for SSL/Offload and L7 Switching changes to plugin? Will it be available by Kilo3?16:35
dougwigChitr: see the log at 9;10am16:35
bloganso basically, there's no reason to have the services.loadbalancer naemspace since we arent in neutron's tree16:36
dougwig23 minutes ago, for those not in the mountain time zone16:36
sballe__:-)16:36
bloganso v2 code should go into the neutron_lbaas.* namespace16:36
bloganso v2 drivers would be in neutron_lbaas.drivers16:36
dougwig(yay!)16:36
bloganv1 drivers remain in neutron_lbaas.services.loadbalancer.drivers16:36
kobisso each vendor code is scattered between here and there?16:36
evgenyfcurrently v1 drivers code is copied to neutron-lbaas16:37
bloganunless you think having neutron_lbaas.drivers.v1/v2 makes sense16:37
kobiswhouldn't it make sense to keep a reference in the old namespace for backward compatibility16:37
*** SridharRamaswamy has joined #openstack-meeting-416:37
dougwigyes, though v1 is effectively dead from a dev perspective, so we're planning the tree based on how it should be laid out when that code is gone.16:37
xgerman+116:37
kobisand have it all in neutron_lbaas.drivers?16:37
dougwigblogan: which review is this in, so folks can comment on the new layout scheme or give feedback?16:38
evgenyfradware does services/loadbalancer/drivers/radware/v2/16:38
bloganhttps://review.openstack.org/#/c/156131/ but it might make sense to just have a review that does it explicitly16:39
bloganbc this is the agent driver base review16:39
bloganevgenyf: can that not be changed before it gets merged?16:39
dougwigkobis: we weren't planning to move the v1 plugin and such.  moving them and leaving a placeholder means we hit name collision issues and have to propagate the v2 on every module, which will be irritating once v1 is actually removed from tree. that'd be the biggest drawback.  drivers are much easier to do what you're suggesting, though.16:39
dougwigthough i'd rather just let them die than churn them, IMO.16:40
evgenyfblogan: not be changed or changed?16:40
bloganevgenyf: can it be changed?16:40
xgermanyeah, dead to v1!!16:40
evgenyfblogan: sure16:40
bloganv1 wont be dead, it'll just be quarantined :)16:41
dougwigseparate but equal?16:41
dougwigwait, isn't that how lbaas is with neutron?  :)16:41
kobisyep - for that miserable dude who actually uses it and won't migrate :(16:41
evgenyfso going for drivers/<vendor>?16:41
bloganlbaas is separate yes, equal? i dont think so16:41
bloganevgenyf: yes16:41
xgermansome projects are more equal than others...16:41
bloganwoudl a more explicit review that pushes this change in be better for everyone?16:42
dougwigblogan: yep, soundsl ike16:42
bloganit'll just be setting up the new structure16:42
blogani dont think we should move the code that has been merged just yet though16:42
blogansuch as the v2 plugin16:43
bloganbut id like to at some point16:43
bloganbefore kilo 316:43
bloganbc that changes how people point to hte plugin in the config16:43
bloganany opinions on moving the v2 specific code that has already merged?16:44
dougwigi'm in favor of moving it.16:44
xgerman+116:44
bloganall o fit?16:44
kobis+116:44
dougwigv2 to the new scheme?  yes.16:45
bloganid prefer to do it in a separate review then16:45
bloganjust so the new structure can go in quickly and driver writers can get to it16:45
dougwigyou'll likely need a placeholder for the service plugin until we can unwind the old location from devstack.16:45
bloganyeah that can just be a redirect16:45
bloganthrough inheritance16:46
dougwigwe will eagerly await for gerrit review.16:46
xgerman+116:46
dougwigor just set "blah = new.spot.blah"16:46
bloganin the interest of getting +2's can someone else do this?16:46
ajmillerI'm into devstack right now, would it make sense for me to do it?16:46
xgermanI altreday volunteered you for stats16:47
blogani dont know, would it al?16:47
ajmillerHmm, well what xgerman said, I don't want to get spread too thin.16:47
xgermanwe will find somebody - moving code looks like a easys ATC16:48
dougwigi'll assume towgan can find a victim offline.16:48
bloganokay someone from our team will do it16:48
dougwigany other open discussion items today?16:48
dougwigi'm going to end by repeating this, for the later risers among us:16:49
dougwigLast announcement from me: Kilo-3 is coming up fast (code proposal deadline is 3/5).  Vendor drivers especially, the earlier you submit the higher chance we'll have review cycles.16:49
dougwigthanks, folks16:49
sballe__have a great day16:49
kobisbye16:49
dougwig#endmeeting16:49
xgermanbye16:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:49
openstackMeeting ended Tue Feb 17 16:49:38 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_lbaas/2015/neutron_lbaas.2015-02-17-16.00.html16:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_lbaas/2015/neutron_lbaas.2015-02-17-16.00.txt16:49
Aishbye16:49
evgenyfbye16:49
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_lbaas/2015/neutron_lbaas.2015-02-17-16.00.log.html16:49
fnavalbye16:50
TrevorVo/16:50
*** TrevorV has left #openstack-meeting-416:50
*** johnsom has left #openstack-meeting-416:50
*** galstrom_zzz is now known as galstrom16:53
*** sarob has joined #openstack-meeting-416:53
*** Aish has quit IRC17:01
*** santosh has quit IRC17:01
*** matrohon has quit IRC17:01
*** tholtzen has joined #openstack-meeting-417:02
*** ativelkov has joined #openstack-meeting-417:03
*** ativelkov has left #openstack-meeting-417:03
*** jorgem has left #openstack-meeting-417:04
*** kobis has quit IRC17:05
*** kobis has joined #openstack-meeting-417:05
*** fnaval_ has joined #openstack-meeting-417:06
*** ivar-lazzaro has joined #openstack-meeting-417:06
*** fnaval has quit IRC17:06
*** wojdev has quit IRC17:08
*** ivar-lazzaro has quit IRC17:09
*** ivar-lazzaro has joined #openstack-meeting-417:10
*** evgenyf has quit IRC17:10
*** nlahouti has joined #openstack-meeting-417:10
*** emagana_ has quit IRC17:10
*** wojdev has joined #openstack-meeting-417:11
*** tholtzen has quit IRC17:14
*** nlahouti has left #openstack-meeting-417:16
*** belmoreira has quit IRC17:21
*** xgerman has left #openstack-meeting-417:21
*** kobis has quit IRC17:22
*** kobis has joined #openstack-meeting-417:23
*** carl_baldwin has quit IRC17:23
*** kobis has quit IRC17:25
*** kobis has joined #openstack-meeting-417:25
*** Aish has joined #openstack-meeting-417:31
*** asselin has quit IRC17:32
*** asselin has joined #openstack-meeting-417:32
*** wojdev has quit IRC17:36
*** asselin has quit IRC17:38
*** asselin has joined #openstack-meeting-417:39
*** SridharRamaswamy has quit IRC17:50
*** carl_baldwin has joined #openstack-meeting-417:52
*** carl_baldwin_ has joined #openstack-meeting-417:55
*** carl_baldwin has quit IRC17:56
*** carl_baldwin_ is now known as carl_baldwin17:56
*** Aish has left #openstack-meeting-417:58
*** galstrom is now known as galstrom_zzz18:04
*** mwang2 has joined #openstack-meeting-418:04
*** yamahata has joined #openstack-meeting-418:06
*** kobis has quit IRC18:08
*** kobis has joined #openstack-meeting-418:08
*** carl_baldwin has quit IRC18:11
*** emagana has joined #openstack-meeting-418:12
*** carl_baldwin has joined #openstack-meeting-418:14
*** emagana has quit IRC18:15
*** fnaval has joined #openstack-meeting-418:18
*** mcginn has quit IRC18:19
*** kobis has quit IRC18:21
*** fnaval_ has quit IRC18:21
*** SridharRamaswamy has joined #openstack-meeting-418:22
*** sigmavirus24 is now known as sigmavirus24_awa18:25
*** sigmavirus24_awa is now known as sigmavirus2418:31
*** carl_baldwin has quit IRC18:32
*** wojdev has joined #openstack-meeting-418:47
*** s3wong has joined #openstack-meeting-418:48
*** carl_baldwin has joined #openstack-meeting-418:54
*** SridharRamaswam1 has joined #openstack-meeting-419:04
*** Rockyg has joined #openstack-meeting-419:04
*** SridharRamaswamy has quit IRC19:05
*** galstrom_zzz is now known as galstrom19:06
*** pmesserli has joined #openstack-meeting-419:08
*** fnaval has quit IRC19:19
*** fnaval has joined #openstack-meeting-419:20
*** fnaval has quit IRC19:21
*** fnaval has joined #openstack-meeting-419:21
*** wojdev has quit IRC19:27
*** Rockyg has quit IRC19:35
*** Rockyg has joined #openstack-meeting-419:36
*** VW_ has quit IRC19:44
*** Rockyg_ has joined #openstack-meeting-419:45
*** Rockyg_ has quit IRC19:47
*** Rockyg has quit IRC19:47
*** Rockyg has joined #openstack-meeting-419:48
*** wojdev has joined #openstack-meeting-419:52
*** SridharRamaswam1 has quit IRC20:03
*** SridharRamaswamy has joined #openstack-meeting-420:09
*** VW_ has joined #openstack-meeting-420:13
*** rfolco_ has quit IRC20:16
*** pmesserli has quit IRC20:47
*** pmesserli has joined #openstack-meeting-420:48
*** pmesserli has quit IRC20:52
*** SridharRamaswamy has quit IRC21:03
*** SridharRamaswamy has joined #openstack-meeting-421:04
*** VW_ has quit IRC21:04
*** matrohon has joined #openstack-meeting-421:12
*** watanabe_isao has joined #openstack-meeting-421:14
*** galstrom has quit IRC21:21
*** galstrom has joined #openstack-meeting-421:21
*** pmesserli has joined #openstack-meeting-421:30
*** rm_work is now known as rm_work|away21:44
*** banix has quit IRC21:57
*** VW_ has joined #openstack-meeting-421:58
*** SridharRamaswamy has quit IRC22:05
*** SridharRamaswamy has joined #openstack-meeting-422:08
*** salv-orlando has quit IRC22:10
*** VW_ has quit IRC22:10
*** salv-orlando has joined #openstack-meeting-422:13
*** wojdev has quit IRC22:14
*** Chitr has quit IRC22:17
*** ivar-laz_ has joined #openstack-meeting-422:52
*** ivar-lazzaro has quit IRC22:55
*** pkoniszewski has quit IRC22:58
*** jckasper has quit IRC23:03
*** matrohon has quit IRC23:04
*** pmesserl_ has joined #openstack-meeting-423:30
*** bobmel has quit IRC23:31
*** bobmel has joined #openstack-meeting-423:31
*** pmesserl_ has quit IRC23:32
*** pmesserl_ has joined #openstack-meeting-423:33
*** pmesserli has quit IRC23:33
*** pmesserli has joined #openstack-meeting-423:45
*** pmesserl_ has quit IRC23:48
*** ivar-laz_ has quit IRC23:48
*** ivar-lazzaro has joined #openstack-meeting-423:49
*** VW_ has joined #openstack-meeting-423:49
*** pmesserli has quit IRC23:49
*** fnaval has quit IRC23:49
*** fnaval has joined #openstack-meeting-423:50
*** galstrom is now known as galstrom_zzz23:53
*** ajmiller has quit IRC23:59

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