Friday, 2017-05-12

openstackgerritMichael Johnson proposed openstack/octavia master: Add v2 health monitor API section  https://review.openstack.org/46409500:04
johnsomHmmm, http://specs.openstack.org/openstack/charm-specs/specs/pike/approved/openstack-load-balancer.html00:17
*** kobis has quit IRC00:32
*** kobis has joined #openstack-lbaas00:33
*** sanfern has quit IRC00:37
*** sanfern has joined #openstack-lbaas00:37
*** catintheroof has quit IRC01:18
rm_workjohnsom: hmmm01:18
rm_workdoes that mean an ACTUAL health-monitor?01:18
*** blogan_ has joined #openstack-lbaas01:32
*** blogan has quit IRC01:35
johnsomThere is no health on an HM02:15
*** catintheroof has joined #openstack-lbaas02:40
*** JudeC has quit IRC03:04
*** sanfern has quit IRC03:07
*** sanfern has joined #openstack-lbaas03:08
*** sanfern has quit IRC03:09
*** kobis has quit IRC03:13
*** yamamoto has quit IRC03:55
*** yamamoto_ has joined #openstack-lbaas03:56
*** catintheroof has quit IRC03:57
*** yamamoto_ has quit IRC04:00
*** yamamoto has joined #openstack-lbaas04:09
*** cpuga has quit IRC04:22
*** cpuga has joined #openstack-lbaas04:22
*** cpuga has quit IRC04:27
*** yamamoto has quit IRC04:37
*** fnaval has quit IRC04:40
*** fnaval has joined #openstack-lbaas04:41
*** fnaval has quit IRC04:59
*** cody-somerville has joined #openstack-lbaas05:15
*** cody-somerville has quit IRC05:15
*** cody-somerville has joined #openstack-lbaas05:15
*** csomerville has quit IRC05:15
*** yamamoto has joined #openstack-lbaas05:22
*** ndahiwade has quit IRC05:25
*** JudeC has joined #openstack-lbaas06:01
*** pcaruana has joined #openstack-lbaas06:14
*** rcernin has joined #openstack-lbaas06:18
*** JudeC has quit IRC06:21
*** cpuga has joined #openstack-lbaas06:38
*** voelzmo has joined #openstack-lbaas06:56
*** voelzmo has quit IRC07:00
*** voelzmo has joined #openstack-lbaas07:00
*** tesseract has joined #openstack-lbaas07:12
*** cpuga has quit IRC07:15
*** gcheresh has joined #openstack-lbaas07:28
*** aojea has joined #openstack-lbaas07:36
openstackgerritcheng proposed openstack/octavia master: Add allocate vip port when create loadbalancer in server side  https://review.openstack.org/46328908:08
*** ndahiwade has joined #openstack-lbaas08:57
*** rcernin has quit IRC09:05
*** rcernin has joined #openstack-lbaas09:14
*** krypto has joined #openstack-lbaas09:49
*** krypto has joined #openstack-lbaas09:49
*** yamamoto has quit IRC10:46
*** yamamoto has joined #openstack-lbaas11:28
*** chlong has quit IRC11:36
*** yamamoto has quit IRC11:37
*** yamamoto has joined #openstack-lbaas11:42
*** yamamoto has quit IRC12:01
*** yamamoto has joined #openstack-lbaas12:05
*** atoth has joined #openstack-lbaas12:05
*** yamamoto has quit IRC12:14
*** yamamoto has joined #openstack-lbaas12:14
*** cpuga has joined #openstack-lbaas12:32
*** aojea has quit IRC12:56
xgermano/13:17
-openstackstatus- NOTICE: The Gerrit service on http://review.openstack.org is being restarted to address hung remote replication tasks.13:37
*** ecelik has joined #openstack-lbaas13:46
*** krypto has quit IRC13:48
*** krypto has joined #openstack-lbaas13:48
*** ecelik has quit IRC13:50
*** rcernin has quit IRC13:55
*** blogan_ has quit IRC13:56
*** blogan__ has joined #openstack-lbaas13:56
*** krypto has quit IRC14:01
*** krypto has joined #openstack-lbaas14:02
*** rcernin has joined #openstack-lbaas14:05
*** chlong has joined #openstack-lbaas14:09
*** rcernin has quit IRC14:17
*** krypto has quit IRC14:24
*** krypto has joined #openstack-lbaas14:24
*** rcernin has joined #openstack-lbaas14:25
*** krypto has quit IRC14:42
*** voelzmo has quit IRC14:50
*** rcernin has quit IRC15:06
*** cpuga has quit IRC15:10
johnsomo/15:17
*** aojea has joined #openstack-lbaas15:18
*** aojea has quit IRC15:22
*** cpuga has joined #openstack-lbaas15:30
*** bzhao has quit IRC15:37
*** bzhao has joined #openstack-lbaas15:38
*** aojea has joined #openstack-lbaas15:38
*** aojea has quit IRC15:42
*** kobis has joined #openstack-lbaas15:57
atothbeagles, what are these reno files that you mention are missing from https://review.openstack.org/#/c/314225/ ?16:10
johnsomreno is the release notes tool.  "<reno new short-title-for-release-note>"16:11
beaglesatoth: https://docs.openstack.org/developer/reno/16:11
beaglesfor more deets16:11
*** pcaruana has quit IRC16:12
atothjohnsom, beagles thanks, I'll look into it16:12
*** voelzmo has joined #openstack-lbaas16:21
johnsomxgerman https://review.openstack.org/#/c/446082/16:25
*** sshank has joined #openstack-lbaas16:25
xgermanon it16:25
*** voelzmo has quit IRC16:25
johnsomThanks, we waited so long on that it needed a minor update since you last +2'd16:26
openstackgerritMerged openstack/octavia-tempest-plugin master: Initial setup of the octavia-tempest-plugin repo  https://review.openstack.org/44608216:29
*** voelzmo has joined #openstack-lbaas16:29
johnsomHa, not much in the way of gates there yet...16:29
*** voelzmo has quit IRC16:37
*** cpuga has quit IRC16:42
*** voelzmo has joined #openstack-lbaas16:43
*** aojea has joined #openstack-lbaas16:44
*** kobis has quit IRC16:45
*** voelzmo has quit IRC16:47
*** blogan__ is now known as blogan17:03
rm_workjohnsom: can you post an update on that bug with the exact details of what you're seeing? (the HM status thing you mentioned)17:07
rm_workbecause I am not sure I follow exactly17:08
rm_workLike, repo + what am I looking for on what object17:08
rm_work*repro17:08
johnsomSure, I just created a HM and it never goes online, it just sits OFFLINE.  I think we need to fake up the ONLINE in the flow like we did with the others that don't actually have anything to monitor for health17:08
xgermanrm_work still in BOS?17:09
rm_workxgerman: over the midwest17:09
rm_workjohnsom: yeah ok so on the *actual HM object*17:09
xgermanmy planes were so small they didn’t even have space for a backpack inside17:09
*** mugsie|phone has quit IRC17:09
johnsomYep.  There is nothing on an AMP to monitor, so when we mark it active we should be marking it ONLINE too17:09
rm_workwas trying to connect to gogo and failing, it wouldn't actually list the plans... eventually i noticed i could still get to google and some other https sites somehow17:10
rm_workand eventually it redirected me to a gogo splash page with a "connect" button and said "Enjoy your free Gogo Internet session" >_>17:10
rm_workanyway, works now17:10
xgermanNice!17:12
johnsomCool, amazing you have room to actually type.  Anyhow, updated.17:12
rm_workAlaska is pretty good for space...17:13
rm_workanyway yeah I thought I fixed that too17:13
rm_workguess I'll go looking17:13
johnsomOh, interesting, it is there:17:13
johnsomhttps://github.com/openstack/octavia/blob/master/octavia/controller/worker/tasks/database_tasks.py#L163017:13
johnsomOh, nevermind, I am an idiot17:14
johnsomMy test script set admin state down17:14
johnsomrm_work ^^17:15
rm_worklol k17:17
johnsomI should get through health monitor today.  That will leave l7policy, l7rules, quota left for the API-ref.  Those will have to wait until after my vacation (assuming no one else is motivated)...17:18
johnsomI might be able to at least get one of the others started today though.17:19
atothjohnsom, beagles, is the convention to use the name of the BZ as the name of the reno file?17:21
johnsomatoth It should just be something that people can match to the release note contents.  There is no real convention.17:22
atothok, thanks17:22
beaglesatoth: I just give it a descriptive name - afaik there is no hard rule17:22
beaglesjohnsom beat me to it17:22
atoth:-)17:23
johnsomFYI, we have had so much recent impact on the stable branches from outside changes, I'm posting some test patches to have them cycle through the full gates.  If all is good I will try to cut a stable branch release today.17:24
johnsomSorry for the patch spam, but it's the fastest way for me to check that we have resolved all of those issues.17:25
rm_workyeah I think that's fine17:26
xgermank, send links so we know what to review with priority17:27
rm_workhmm, I met someone at the summit that said they had a lot of experience with image building with Alpine and they might have time to look at our stuff and help get something up and running17:28
rm_workwhich would be sweet17:28
johnsomHa, and Suse...17:29
xgermanSuse has their own people17:29
johnsomI just remember someone asking about Suse Amphora images in one of the talks17:33
rm_workyeah17:33
rm_workI think they can contribute that one themselves17:33
rm_workbut we can have a gate to make sure it works still17:33
rm_workagain, non-voting, already too many voting jobs IMO <_<17:34
rm_workmultiplying the effect of random errors in our gate exponentially17:34
johnsomYeah, we still have to make lbaas voting long enough to close out of py35 goal17:34
rm_workit is17:35
rm_workisn't it?17:35
rm_worki thought we did that17:35
johnsomNo, the requirement is voting gates, we aren't on the lbaas gates17:35
rm_worki see the jobs voting17:35
rm_work?17:35
rm_workgate-octavia-v1-dsvm-py3x-scenario-ubuntu-xenialSUCCESS in 26m 40s17:36
rm_workgate-octavia-v1-dsvm-py3x-scenario-multinodeSUCCESS in 34m 11s17:36
rm_worknot enough?17:36
johnsomThose are octavia gates, I'm talking about the lbaasv2 gates17:36
rm_workoh17:36
rm_workthat project is dead17:36
rm_workwho cares17:36
johnsomNot in the eyes of the TC17:37
rm_workT_T17:37
rm_workso just turn them on17:37
rm_workwe don't need to merge anything anyway17:37
xgermanthat TC again…17:37
rm_work*turn them on for n-lbaas, not octavia*17:37
johnsomYeah, that might be a trick17:37
rm_workthey seem to be passing last I see17:38
johnsomYeah, they are passing17:38
rm_workthey aren't a dependent project of octavia17:38
rm_workso we don't need to gate them on octavia17:38
johnsomThe only real issue we have at the moment (knock on wood) is the random OVH host failures17:38
rm_workpretty clear cut IMO17:38
rm_workyeah but in n-lbaas we can recheck 1000 times17:39
rm_workjust don't enable the n-lbaas gates in octavia and it's fine17:39
johnsomWell, and those strange 404 issues with the amp agent17:39
atothbeagles, I'm wondering about your comment in https://review.openstack.org/#/c/314225/ around octavia interaction and if we would guard against other lbaasv2 implementaions being active. are we not allowing for multiple lbaas providers to be active at the same time?17:43
johnsomneutron-lbaas and octavia can be run concurrently17:43
beaglesI'm thinking of how the service providers are configured17:45
* beagles double checks17:45
xgermanmmh? LBaaS V1 and V2?17:46
atothjohnsom, my work is around tripleo, from the sessions this week @ summit I thought I heard that the current tiple0-octavia integration was around the octavia-lbaas2 setup. Is that looking to change for Pike?17:46
johnsomYeah, neutron-lbaas is under "networking" (i.e. neutron) and octavia is under "load-balancer"17:47
johnsomLBaaS V1 is dead and the code is gone, so ignore that17:47
atothxgerman, yeah, behind the times slightly, but not V1 behind :-)17:47
xgermanok, there is no issue17:47
xgerman—provider is your friend17:47
*** cpuga has joined #openstack-lbaas17:48
atothI'm trying to get the generic one in before doing the F5 integration17:48
johnsomatoth Not sure I follow.  At the end of Pike, Octavia with have it's own endpoint implementing a superset of LBaaSv2 API (we are kind of calling it Octavia V2 API) and has a service type in keystone of "load-balancer".17:48
johnsomYou can still use the neutron-lbaas endpoint however, if you need.17:49
xgermanwith F5 he needs it17:49
xgermanuntil wer have the shim ready17:49
johnsomYeah, we don't have the providers stuff in Octavia v2 API yet17:50
atothjohnsom, discussions on the octavia -tripleo integration was thin :-) just reconciling my understanding17:50
johnsomYeah, I'm not super familiar with the tripleo stuff either.  nmagnezi is the expert here17:50
xgermanyeah, I don’t use it so have to go on good authority from nmagnezi17:50
rm_workyeah we are running n-lbaas v2 that is providing a hardware vendor's lbs, and also octavia which is doing the service-vm thing17:51
atothmention nmagnezi one more time and ... oops just did17:51
xgermanI know they asked questions here about how we did OSA and were thinking doing the same17:51
rm_worksimultaneously17:51
*** aojea has quit IRC17:51
beaglesjohnsom: can you run lbaas with something other than octavia as a backend at the same time?17:51
xgermanyep17:51
* beagles concedes his understandings of all things lbaas is limited17:51
beaglesok cool17:52
*** aojea has joined #openstack-lbaas17:52
rm_workthe shim is re-worked a little bit and seems to be ... "passing" our basic tests, but we need a vendor to get some CI set up and their driver shoved under it17:52
rm_workso we can see if it REALLY works17:52
xgermanyou can select with —provider WHERE the load balancer should be created17:52
rm_workI'm honestly a little stalled on it until that happens17:52
johnsomYes, the providers parameter defines the driver used for the load balancer17:52
beaglesso atoth, then the thing you need to make sure of is that one does not "wipe out the other"17:52
* atoth see beagles knowledge points increase17:52
xgermanand you can pick one as the default17:52
xgermanthough all products/installs I can influence make Octavia default17:53
xgerman:-)17:53
atothhow would they collide with different endpoints?17:53
rm_workyep :)17:53
rm_workthey would not collide ^_^17:54
* beagles is referring to configuration only17:54
beaglesI'm not sure if there is any overlap at all, but the docs are kind of wonky in this regard so I'm exercising caution :)17:54
rm_workif both are using Octavia though, you'd use the proxy driver instead of the regular octavia driver17:54
rm_workin neutron-lbaas17:54
*** cpuga has quit IRC17:55
johnsomOr the old octavia v1 driver17:55
*** cpuga has joined #openstack-lbaas17:55
*** aojea has quit IRC17:57
atothso can you even guard against it if multiple providers are allowed?17:57
rm_workI just don't even understand what collisions you're even considering17:58
atothwhich ever ones beagles is exercising caution against ;-)17:58
rm_workright17:59
beaglesrm_work: the collisions I am referring to are actually all tripleo and configuration specific17:59
rm_workhmm17:59
rm_workbut like17:59
rm_workcollisions between... what and what?17:59
beaglesso like the implementation of the service_plugins for lbaas wipes  out octavia17:59
beaglesand so on17:59
*** krypto has joined #openstack-lbaas18:00
*** krypto has joined #openstack-lbaas18:00
beaglesthere probably is little else.. I'm guessing?18:00
rm_workerr18:00
rm_workok yeah I guess you lost me18:00
atothme too :-)18:00
atothbut that just shows how new I am to this maybe18:00
rm_workthis is with tripleo automated configuration elements or something?18:01
rm_worklike it deletes config sections?18:01
beaglesrm_work: yes, but no18:01
* atoth loves the clarity18:01
beagleslol18:01
rm_workAFAIK there should not be any possible collisions when the services are running, pretty much no matter what your configuration looks like18:02
rm_workso if you find one, file a bug I guess :P18:02
beaglesrm_work that's not what I'm referring to18:02
rm_work(with clearer repro steps than what you've described here so far ^_^)18:02
johnsomTo clarify, the neutron service plugin will be lbaasv2 if you want neutron-lbaas in neutron.18:02
beaglesjohnsom: an afaik it is also lbaasv2 if you use octavia with neutron18:03
rm_workbeagles: right, I have yet to be able to follow what you're actually referring to T_T18:03
johnsomThen service_provider is a list of drivers18:03
beaglesjohnsom: yes .. an afaict the lbaas config code doesn't treat it as such - it kind of sidesteps the neutron configruation of same18:04
beagles(puppet config code)18:04
johnsombeagles Yeah, it's lbaasv2 if you use neutron-lbaas.  Independent on the backend driver(s) that you have in neutron-lbaas.  The drivers list is service-providers.18:04
beaglesso my comments to atoth patches, were along the lines of making sure they either can work together or make them not deploy togehter18:04
beagles(it really doesn't have anything to do with lbaas I think, just make sure they can be deployed properly)18:05
atoth Sounds like a QA thing ;-)18:05
atothso when I get to the point of adding test to the ci pipeline, I should make that the test case18:06
*** ssmith has quit IRC18:08
*** ssmith has joined #openstack-lbaas18:08
xgermanyeah, we are of little help when it comes to tripleO18:12
rm_worknmagnezi can speak to that maybe? :P18:12
atotha little new knowledge doesn't hurt :-)18:12
*** yuanying_ has joined #openstack-lbaas18:17
*** krypto has quit IRC18:18
*** yuanying has quit IRC18:19
rm_workkk landing shortly18:54
rm_workbbl18:54
*** tesseract has quit IRC19:00
*** harlowja has quit IRC19:02
*** aojea has joined #openstack-lbaas19:14
*** sshank has quit IRC19:18
*** voelzmo has joined #openstack-lbaas19:51
*** blogan has quit IRC19:59
*** voelzmo has quit IRC20:01
*** kobis has joined #openstack-lbaas20:27
*** aojea has quit IRC20:32
*** aojea has joined #openstack-lbaas20:38
*** gcheresh has quit IRC20:41
*** yamamoto has quit IRC20:44
*** yamamoto_ has joined #openstack-lbaas20:44
*** kobis has quit IRC20:57
*** kobis has joined #openstack-lbaas21:17
*** ssmith has quit IRC21:25
*** fnaval has joined #openstack-lbaas21:30
openstackgerritMichael Johnson proposed openstack/octavia master: Add v2 health monitor API section  https://review.openstack.org/46409521:35
*** blogan has joined #openstack-lbaas21:37
*** aojea has quit IRC21:41
*** aojea has joined #openstack-lbaas21:41
*** aojea has quit IRC21:46
*** cpuga has quit IRC22:02
*** kobis has quit IRC22:31
*** harlowja has joined #openstack-lbaas22:40
johnsomxgerman Can you take a quick look at this: https://review.openstack.org/#/c/464272/22:40
johnsomstable/newton fix22:40
xgermank22:47
johnsomThanks22:49
*** chlong has quit IRC23:00

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