Tuesday, 2017-08-22

*** sshank has quit IRC00:01
*** yamamoto_ has joined #openstack-lbaas00:18
*** yamamoto_ has quit IRC00:24
*** catintheroof has quit IRC00:25
*** slaweq has joined #openstack-lbaas00:28
*** slaweq has quit IRC00:33
xgerman_I like socket but yeah…00:38
xgerman_also like some reviews on my stuff: proxy, active-active, so I can continuew00:39
*** JudeC has quit IRC00:50
rm_workxgerman_: well I might have to ... looks like gunicorn won't forward signals00:55
*** openstackgerrit has joined #openstack-lbaas01:12
openstackgerritOpenStack Proposal Bot proposed openstack/octavia master: Updated from global requirements  https://review.openstack.org/49605201:12
*** yamamoto_ has joined #openstack-lbaas01:21
*** yamamoto_ has quit IRC01:26
openstackgerritAdam Harwell proposed openstack/octavia master: WIP: Floating IP Network Driver (spans L3s)  https://review.openstack.org/43561201:34
johnsomhttps://usercontent.irccloud-cdn.com/file/ZWbufmf9/1503365957.JPG01:39
johnsomrm_work01:39
rm_workjohnsom01:39
rm_worki figured out the signals issue BTW01:39
rm_workand that looks ridiculous01:39
rm_workand now I'm wishing I'd taken you up on your guest room for the eclipse just so I could also be around when you eat that01:39
johnsomTried my hand at hickory smoking again01:40
rm_workyou using a barrel or you have like ... a real smoker01:40
rm_workthe barrel method always struck me as more "legit" :P at least if you want oldschool southern bbq01:41
rm_workand has the advantage of being cheap01:41
rm_workbut not as easy T_T01:41
johnsom"Real" electric smoker.  Parting gift from HP01:42
rm_worknice01:44
rm_workyeah those make it pretty straightforward01:44
rm_work(insomuch as any cooking is straightforward)01:44
rm_workDid it turn out?01:45
rm_worki normally don't eat for a bit but that's making me really hungry T_T01:45
rm_workmy favorite now is doing ribs with an Instant-Pot ... which I feel is basically like cheating but are amazing01:47
johnsomIt did.  My first attempt last year, not so much, but this is pretty good.01:48
*** yamamoto_ has joined #openstack-lbaas02:22
*** yamamoto_ has quit IRC02:28
*** catintheroof has joined #openstack-lbaas02:30
*** yamamoto has joined #openstack-lbaas02:56
*** catintheroof has quit IRC02:57
*** yamamoto has quit IRC03:02
*** links has joined #openstack-lbaas03:51
*** yamamoto has joined #openstack-lbaas04:03
*** yamamoto has quit IRC04:09
*** gcheresh has joined #openstack-lbaas04:33
*** gcheresh has quit IRC04:36
*** yamamoto has joined #openstack-lbaas05:05
*** yamamoto has quit IRC05:10
*** gcheresh has joined #openstack-lbaas05:21
*** links has quit IRC05:30
*** links has joined #openstack-lbaas05:33
*** JudeC has joined #openstack-lbaas05:46
rm_workjohnsom: -C for keepalived seems to ... completely make it stop doing anything, including communicating with peers and doing notify scripts :(06:00
openstackgerritAdam Harwell proposed openstack/octavia master: WIP: Floating IP Network Driver (spans L3s)  https://review.openstack.org/43561206:03
*** slaweq has joined #openstack-lbaas06:04
*** yamamoto has joined #openstack-lbaas06:06
openstackgerritAdam Harwell proposed openstack/octavia master: WIP: Floating IP Network Driver (spans L3s)  https://review.openstack.org/43561206:08
*** yamamoto has quit IRC06:12
*** eezhova has joined #openstack-lbaas06:26
*** armax has quit IRC06:39
*** rcernin has joined #openstack-lbaas06:45
*** pcaruana has joined #openstack-lbaas06:45
*** csomerville has joined #openstack-lbaas07:05
*** cody-somerville has quit IRC07:05
*** eezhova has quit IRC07:16
*** dmellado has joined #openstack-lbaas07:18
*** tesseract has joined #openstack-lbaas07:20
-openstackstatus- NOTICE: Gerrit is going to be restarted due to slow performance07:36
-openstackstatus- NOTICE: Gerrit has been restarted successfully07:40
*** eezhova has joined #openstack-lbaas07:45
*** aojea has joined #openstack-lbaas08:32
*** yamamoto has joined #openstack-lbaas08:35
*** aojea has quit IRC08:44
*** yamamoto has quit IRC08:59
*** yamamoto has joined #openstack-lbaas08:59
*** yamamoto has quit IRC08:59
*** JudeC has quit IRC09:00
*** aojea has joined #openstack-lbaas09:12
isantosp_hi, how does loadbalancer quota works? is setted it on a neutron side?09:17
*** csomerville has quit IRC09:50
*** yamamoto has joined #openstack-lbaas10:00
*** yamamoto has quit IRC10:05
*** yamamoto has joined #openstack-lbaas10:30
*** atoth has joined #openstack-lbaas10:31
*** slaweq_ has joined #openstack-lbaas10:59
*** junbo has quit IRC11:01
*** slaweq has quit IRC11:01
*** junbo has joined #openstack-lbaas11:05
openstackgerritOmer Anson proposed openstack/octavia master: devstack: Allow 3rd party neutron backends deployment  https://review.openstack.org/49620511:10
*** yamamoto has quit IRC11:18
*** yamamoto has joined #openstack-lbaas11:30
*** belharar has joined #openstack-lbaas11:33
*** fnaval has quit IRC11:41
*** yamamoto has quit IRC11:46
*** yamamoto has joined #openstack-lbaas11:48
*** yamamoto has quit IRC12:03
*** yamamoto has joined #openstack-lbaas12:04
*** aojea has quit IRC12:07
*** yamamoto has quit IRC12:10
*** aojea has joined #openstack-lbaas12:10
*** yamamoto has joined #openstack-lbaas12:12
*** aojea has quit IRC12:21
*** slaweq_ has quit IRC12:25
*** slaweq has joined #openstack-lbaas12:26
*** slaweq has quit IRC12:30
*** slaweq has joined #openstack-lbaas12:34
*** aojea has joined #openstack-lbaas12:36
*** aojea has quit IRC13:05
*** aojea has joined #openstack-lbaas13:10
*** yamamoto has quit IRC13:12
*** yamamoto has joined #openstack-lbaas13:14
*** yamamoto has quit IRC13:22
*** voelzmo has joined #openstack-lbaas13:27
voelzmoHello friends of the loadbalancers! A quick question about the behavior of octavia when adding members: does it add new ports in the subnet where I'm adding members from?13:29
*** fnaval has joined #openstack-lbaas13:30
voelzmoAnd how does octavia do scaling of the LBaaS? Let's say I'm adding a few thousand members, how does it keep up with the traffic to those instances?13:31
*** leitan has joined #openstack-lbaas13:34
johnsomisantosp_ If you are using neutron-lbaas, yes, it is through neutron.  If you are just using the Octavia endpoint quota is part of the API13:38
johnsomvoelzmo Yes, we hot plug the networks into the load balancer it they are not already attached.13:39
johnsomAt the moment we have not yet finished the act/act work that would help with scaling for the octavia driver.  You would need to use a vendor driver for that use case today.13:41
voelzmo@johnsom Thanks! Are there idea on how to implement the scaling part? I'm wondering how the loadbalanced members would identify that the traffic they receive is really coming from the LB and not from somewhere else13:42
voelzmoI'd like to keep security groups as tight as possible13:42
voelzmo@johnsom And a question concerning what you call "hot plugging the network": does that mean octavia creates a new port in that network and all traffic to loadbalanced members will come from that port?13:43
johnsomI see.  We have ideas and discussed options, but initially it will use DHCP for the ports13:45
johnsomYes, that is how it works13:45
voelzmo@johnsom using DHCP would be okay, I'm trying not to care about IP addresses. Currently, we use marker-security-groups which are referenced by the security groups applied to the pool members13:50
voelzmoso they allow e.g. traffic from security group 'lbaas' on port 443 and 2213:51
voelzmohowever, octavia would need to apply the security group to all ports it creates during runtime then13:51
*** slaweq has quit IRC13:51
voelzmoe.g. a user would specify a "loadbalancer security group" when creating an LBaaS and octavia takes care of the rest13:51
voelzmodoes that sound reasonable?13:51
johnsomWell, we don't want to blindly apply a user defined security group to the ports.13:53
johnsomCurrently you can restrict access to the local subnet.  If you are using TLS we plan to add backend encryption with client cert support.13:55
*** aojea has quit IRC13:55
*** aojea has joined #openstack-lbaas13:56
voelzmo@johnsom currently, it would mean that the subnet which contains my members needs to allow for incoming traffic from all IPs in that subnet, correct?13:57
voelzmoThere is no way to restrict incoming traffic to only the loadbalancer instances, right?13:57
johnsomI think we need to look at how to layer them in a safe way13:57
johnsomRight, there are some tricks with allocation pools and timing, but not the best solution13:58
*** voelzmo has quit IRC14:01
*** bcafarel has quit IRC14:05
*** voelzmo has joined #openstack-lbaas14:11
*** armax has joined #openstack-lbaas14:14
xgerman_johnsom we have the disk image build script failing on the ansible side14:14
johnsomHmm, joy.  I will take a look when I get into the office.14:15
johnsomGates or OSA?14:16
voelzmo@johnsom so you say the problem is known but you wouldn't try to solve this with a user-provided security group which is automatically applied to lbaas-created ports?14:17
johnsomvoelzmo We have to do it in a way that doesn't allow the load balancer to be exposed.14:18
voelzmo@johnsom right now I can add manually security groups which expose it, right?14:19
johnsomRight now Octavia managed the port security groups and only opens required ports, but if we take user groups someone could open a hole into the lb14:19
johnsomOnly as an Admin, yes14:20
*** links has quit IRC14:20
voelzmo@johnsom really? I've been applying security groups with neutron update-port all day today?14:20
*** bcafarel has joined #openstack-lbaas14:20
voelzmoOr is this just because my vendor-specific backend allows this by placing the ports visibly in my subnet?14:21
johnsomCould be.  The octavia ports are owned by Octavia and only Admins should be able to make changes14:22
*** yamamoto has joined #openstack-lbaas14:23
xgerman_periodic OSA14:26
xgerman_translation scenario (which includes Octavia)14:26
xgerman_http://paste.openstack.org/raw/619036/14:28
*** yamamoto has quit IRC14:28
xgerman_maybe some of the resources went away. Didn’t have yet had coffee so my thinking is slow ATM14:28
voelzmo@johnsom is there any place where you would collect ideas or a proposal about how to solve this before implementing a solution? I'd be interested in participating in the discussion if you start tackling that topic14:35
xgerman_we were thinking using LB’s ACL’s to solve that issue14:36
xgerman_there must be a spec floating around14:37
*** aojea has quit IRC14:37
voelzmo@xgerman_ LBs ACLs solve the issue to allow incoming traffic on loadbalanced members only from the LB?14:39
voelzmoI'd like to only expose what is needed on the members14:39
*** aojea has joined #openstack-lbaas14:40
xgerman_well, that feels like a subnet design question14:43
xgerman_unless you are worried about members talking to each other14:43
voelzmoI am14:45
voelzmothat's what I'm saying14:45
voelzmoI want to expose only what is necessary, even on my subnet14:45
xgerman_ok, so you would need to put sec grps on members which allow our port14:46
voelzmowhich works convenient on a lot of other IaaSes using some security group as marker for the LB14:46
voelzmohowever, I just learned that this will no longer work, once octavia isn't a singleton anymore14:46
xgerman_we haven’t crossed that bridge yet ;-)14:48
xgerman_but I can see your issue I think we can solve that with a carefully chosen remote sec grp for you to allow14:48
xgerman_then only LB traffic will hit your members14:49
voelzmo@xgerman_ sounds lovely, I'd like to stick to the concept of using marker security groups, if possible14:49
xgerman_never heard of marker sec grps - so we might talk about the same thing14:50
voelzmoyeah, not sure what to call it14:50
voelzmoI'm using a security group just to reference it in another security group14:50
voelzmoto "mark" where traffic is coming from without having to specify IPs or network ranges14:51
xgerman_yes, that’s a remote security group14:51
voelzmothanks, that's what I'm talking about14:51
xgerman_there is a similar concept in FWaaS V214:51
xgerman_if you rather use firewalls in the future ;-)14:51
voelzmo@xgerman_ who knows about the future14:51
xgerman_yes, indeed14:52
*** belharar has quit IRC14:52
voelzmoso even if I'm using a vendor-specific backend, I guess still something would need to be done in octavia to attach the same security group to all ports created, right?14:54
voelzmoso I could reference it as remote security group on my members14:54
*** aojea has quit IRC14:54
*** aojea has joined #openstack-lbaas14:55
*** belharar has joined #openstack-lbaas14:56
xgerman_I would have to check if we don’t already do that and not expose but yes, we would likely have work ahead (but easy)14:56
voelzmo@xgerman_ I couldn't see it, at least14:57
voelzmo@johnsom the documentation still says you should create an attach your own security group to the created LB's port: https://docs.openstack.org/neutron/pike/admin/config-lbaas.html#building-an-lbaas-v2-load-balancer14:58
voelzmoyou said this should only be possible for an admin?14:58
xgerman_yes14:58
voelzmoI'm doing this as regular project member14:58
xgerman_yeah, that also doesn’t sound right14:59
xgerman_since we can have a different port than the VIP to reach out to the subnet14:59
voelzmo@xgerman_ exactly, that's one of my issues15:00
xgerman_best would be to file. a bug and call it an RfE and we can go from there15:00
johnsomvoelzmo Those are old neutron docs.  Current docs are here: https://docs.openstack.org/octavia/latest/15:00
voelzmo@johnsom thanks. "Old" still means they're part of pike, though, right?15:00
xgerman_no15:00
johnsomWell, means someone added stuff to it that might not be accurate15:01
johnsomThere are errors all over the neutron docs15:01
voelzmo@johnsom this has been in since mitaka and was at least accurate then15:01
johnsomWe did a bunch of work in Pike to clean up and improve the docs15:02
voelzmos/accurate/working/15:02
johnsomI know there is some stuff in there that never was accurate15:02
johnsomvoelzmo So path forward, it would be great to post a spec with a proposal so that folks can review and comment.15:03
voelzmoand by spec you mean an 'rfe' tagged bug in launchpad, or are you using a different process?15:04
*** aojea has quit IRC15:05
johnsomYou could start as an RFE, but this seems like a big enough change that a spec might be best.15:05
johnsomhttps://github.com/openstack/octavia/tree/master/specs15:06
johnsomThere is a template and example file there15:06
*** cody-somerville has joined #openstack-lbaas15:06
*** cody-somerville has quit IRC15:06
*** cody-somerville has joined #openstack-lbaas15:06
voelzmookay, thanks15:06
voelzmow00t, github, not gerrit?15:06
voelzmoNo, I'm still proposing stuff on  https://git.openstack.org, right?15:07
xgerman_they are the same thing15:08
voelzmoah, so much process confusion15:08
voelzmowell, github PRs and gerrit reviews are different things, right15:08
*** aojea has joined #openstack-lbaas15:08
xgerman_yes, and yes15:09
xgerman_gerrit review is what we aim for15:09
voelzmofair enough, I'll try to come up with a spec and submit something for review15:09
voelzmotbh, I know very little about the current internals of octavia, so this will be more of a wishlist, but we have something to talk about at least15:10
voelzmothanks @johnsom and @xgerman_15:10
xgerman_especially how you liek that sec-grp be exposed to the user - API and CLI changes would be of interest. Slapping sec grp on ports is easy…15:10
*** eezhova has quit IRC15:12
johnsomYeah, links to github are just the easiest way to point folks to files. It's still a standard OpenStack review process15:12
johnsomxgerman_ Do you have a link to the periodic job?15:13
johnsom"In the office now" and done with my first meeting.15:13
*** rcernin has quit IRC15:15
*** belharar has quit IRC15:18
*** aojea has quit IRC15:22
*** yamamoto has joined #openstack-lbaas15:25
johnsomxgerman_ rm_work To get Project Updates on the schedule, we need you to let us know if you (or a core team member who will be presenting in your place) are confirmed to attend Sydney—approval to go, a plane ticket, etc—by September 5. Project Updates in Sydney will be 20 minutes by default—we’ve found the 20 minute video recordings have better engagement than 40—but let us know if your update needs15:29
johnsomall 40 minutes.15:29
*** yamamoto has quit IRC15:30
xgerman_ok15:34
*** dougwig has joined #openstack-lbaas15:34
xgerman_johnsom I only have the link I posted earlier — I know the translation periodic job failed but no idea where to find it15:37
johnsomOk, I think I found the job, looking now15:37
xgerman_in the paste it looked like we couldn’t download some python stuff15:38
xgerman_it’s stable/pike15:38
johnsomIt looks like there were more infra mirror issues recently, so that might be the cause15:38
xgerman_yep, it looked like something which should be intermittent15:39
*** csomerville has joined #openstack-lbaas15:39
johnsomxgerman_ So, if this is the job: http://status.openstack.org/openstack-health/#/job/periodic-openstack-ansible-deploy-translations-master-ubuntu-xenial15:42
johnsomIt's failed once in the last seven days....15:42
johnsomBut the timestamps don't match up15:42
*** cody-somerville has quit IRC15:43
*** belharar has joined #openstack-lbaas15:58
johnsomYeah, I don't see any octavia errors in there.  The only error line in the paste is dpkg: error: error writing to '<standard output>': Broken pipe15:59
johnsomWhich could just be some local issue or network issue.15:59
johnsomThe periodic job (not the paste) was a infra issue IMO15:59
xgerman_yeah, the paste was some guy running it on his box but that also had an error accessing some Internet resource16:02
*** tesseract has quit IRC16:04
*** voelzmo has quit IRC16:06
*** eezhova has joined #openstack-lbaas16:10
*** catintheroof has joined #openstack-lbaas16:10
*** gcheresh has quit IRC16:22
*** belharar has quit IRC16:24
*** yamamoto has joined #openstack-lbaas16:26
*** yamamoto has quit IRC16:32
*** belharar has joined #openstack-lbaas16:33
*** pcaruana has quit IRC16:37
*** JudeC has joined #openstack-lbaas16:56
*** belharar has quit IRC17:00
*** gcheresh has joined #openstack-lbaas17:06
*** yamamoto has joined #openstack-lbaas17:28
*** yamamoto has quit IRC17:35
rm_workhmmm17:46
rm_workthat's the VIP Port17:46
rm_workthat's the one we expose17:46
rm_workoh whoops scrolled up too much17:46
*** tongl has joined #openstack-lbaas17:48
rm_workjohnsom: so does the core doing the project-update get a speaker pass?17:48
rm_worki have approval but i wouldn't have a badge at the moment17:48
johnsomYou have the information I have, I can get you an e-mail to ask if you like17:53
*** gcheresh has quit IRC17:56
*** JudeC has quit IRC18:01
*** eezhova has quit IRC18:04
nmagnezio/18:04
rm_workhmm k18:09
*** JudeC has joined #openstack-lbaas18:18
*** yamamoto has joined #openstack-lbaas18:31
*** voelzmo has joined #openstack-lbaas18:34
*** yamamoto has quit IRC18:37
*** gcheresh has joined #openstack-lbaas18:44
*** voelzmo has quit IRC18:46
*** amotoki has quit IRC18:53
xgerman_johnsom this combination of statistics and recent module is what  I can comprehend pretty quickly: https://www.microsoft.com/developerblog/2017/06/28/scaling-udp-workloads-with-kubernetes/19:02
xgerman_downside is we probably need to rehash each time we add/remove LBs but we can fix that in the future with some of the better distributor stuff19:03
xgerman_Then I can sling that on LB1 on an ACTIVE-PASSIVE set and they become magically ACTIVE-ACTIBE ;-)19:07
*** yamamoto has joined #openstack-lbaas19:33
*** gcheresh has quit IRC19:35
*** gcheresh has joined #openstack-lbaas19:37
*** yamamoto has quit IRC19:38
*** eezhova has joined #openstack-lbaas19:44
*** armax has quit IRC19:52
*** fnaval has quit IRC19:56
*** sshank has joined #openstack-lbaas20:03
*** fnaval has joined #openstack-lbaas20:22
*** fnaval has quit IRC20:22
*** fnaval has joined #openstack-lbaas20:23
*** eezhova has quit IRC20:27
xgerman_rm_work we will get a feree code for attending the PTG20:33
johnsomAh, true20:33
xgerman_rm_work my approved budget only covers the flight and some meals… so if you know a nice bridge…20:34
xgerman_I can probably kick in a few bucks if we want to go and do the update20:34
*** yamamoto has joined #openstack-lbaas20:35
*** yamamoto has quit IRC20:38
*** yamamoto has joined #openstack-lbaas20:38
*** yamamoto has quit IRC20:39
*** rcernin has joined #openstack-lbaas20:50
*** gcheresh has quit IRC20:51
*** aojea has joined #openstack-lbaas21:02
*** fnaval has quit IRC21:04
*** armax has joined #openstack-lbaas21:04
*** yamamoto has joined #openstack-lbaas21:10
*** jmccrory has quit IRC21:13
*** jmccrory has joined #openstack-lbaas21:14
*** yamamoto has quit IRC21:15
*** kbyrne has quit IRC21:30
*** kbyrne has joined #openstack-lbaas21:32
rm_workxgerman_: i might have room in an airbnb21:36
rm_workxgerman_: i can just get a 2-room one21:36
rm_workstill way cheaper than hotel21:36
rm_worki am supposed to book that now, too21:36
xgerman_awesome21:36
rm_worki've crashed on your couch a couple times I think :P21:37
xgerman_yep21:37
xgerman_which dates are you thiking?21:37
rm_worki'm still 100% verifying21:37
xgerman_same here21:37
rm_workso i'll need till the end of the week prolly21:37
xgerman_sounds good -21:46
rm_workjohnsom / xgerman_: seems that keepalived is taking ~4s from when the MASTER dies to actually trigger transition to MASTER21:57
rm_workso I don't know how even upstream we are supposed to be doing subsecond21:57
rm_workbecause it's 4s from the last working request, until it does a GARP and theoretically would pick up new requests21:57
johnsomOh, I never quoted sub-second, I usually say around a second21:57
rm_worklol21:57
johnsomGot back and watch the video from Tokyo21:58
rm_workwell 4s seems a little sad21:58
rm_workand is not what I was expecting, quite21:58
rm_worki wonder if we can tweak that21:58
rm_worklike, are any of our settings bad?21:58
johnsomYeah, I don't think our defaults are "perfect" there21:58
*** JudeC has quit IRC21:59
rm_workhmm22:00
johnsomI think things have changed a bit too over time.22:00
*** leitan has quit IRC22:01
*** catintheroof has quit IRC22:01
rm_workoh nice, realized why storing topology on the LB is nice22:09
rm_worknow I can switch the topo to ACTIVE_STANDBY and it won't do horrific things to the old LBs :P22:09
rm_worki'd never really thought about it22:09
rm_workanyway, about to switch over to active-standby... soon22:09
*** yamamoto_ has joined #openstack-lbaas22:11
*** JudeC has joined #openstack-lbaas22:14
*** yamamoto_ has quit IRC22:17
rm_workjohnsom: wait is it related to:22:18
rm_work# vrrp_check_interval = 522:18
rm_work# vrpp_fail_count = 222:18
rm_work# vrrp_success_count = 222:18
rm_workthat doesn't actually look like how long it takes22:18
rm_workI mean I guess that's just for the check script?22:18
rm_workunless it isn't?22:19
*** sshank has quit IRC22:19
rm_workyeah looks like those are used for the check script, not for the "pair liveness"22:20
openstackgerritAdam Harwell proposed openstack/octavia master: WIP: Floating IP Network Driver (spans L3s)  https://review.openstack.org/43561222:21
openstackgerritAdam Harwell proposed openstack/octavia master: Whitespace fixes and simplification of keepalived template  https://review.openstack.org/49643022:26
rm_workjohnsom: ^^ that was bothering me a lot22:26
rm_workthe template was an absolute mess22:26
rm_workthe output had like 4 blank lines at the top, and EVERYTHING had different indentation22:26
rm_workit made me weep on the inside22:26
johnsomHahaha22:27
*** sshank has joined #openstack-lbaas22:27
rm_workand like, why were we using a macro22:28
rm_workfor one spot22:28
rm_workthat was just a for-loop22:28
rm_workthat's not a macro22:28
rm_workit still bothers me that there's two newlines at the end of the TEMPLATE, but in the output, there's only one for some freaking reason22:30
rm_workso whatever, it has to stay I guess >_<22:30
*** rcernin has quit IRC22:32
rm_workanyone know of any promo codes for the PTG? :P22:59
*** aojea has quit IRC23:05
johnsomNope23:06
*** ipsecguy has quit IRC23:07
*** ipsecguy has joined #openstack-lbaas23:08
tonglIf there is any exception raised during creating LB resource, how can we exit without any resource being created. In our vmware_nsx driver, in case of exception raised, it still go ahead to create LB in ERROR state in neutron db.23:11
tonglhttps://github.com/openstack/vmware-nsx/blob/master/vmware_nsx/services/lbaas/nsx_v3/loadbalancer_mgr.py#L4323:11
tonglWhat I want is just output the exception to user, but not creating any resource in ERROR state in db.23:12
johnsomtongl Since the API is async you should always have a record for the client to query status23:12
*** ipsecguy has quit IRC23:12
*** ipsecguy has joined #openstack-lbaas23:12
*** yamamoto_ has joined #openstack-lbaas23:13
tonglIf it fails validation at an early stage, is it possible to exit without creating any resource?23:13
tonglFor me it makes sense since it didn't pass validation. It just exit without any resource being created.23:14
johnsomYes, if it fails basic validation the user gets a direct response instead of 201, but once the data is validated it is stored in the DB for the driver to act on.23:15
rm_worktongl: yeah, by the time your driver gets it, it HAS passed validation23:16
tonglI see. So as long as the data passes basic validation, it will be created in db even if the driver validation part failed.23:16
rm_workyes, then it will go to ERROR and the user will know it failed23:17
rm_workthough, what validation happens in your driver that is being allowed through the API validation layer?23:17
rm_workthat's not ideal23:17
tonglProbably in our driver, we can delete the record if it failed the driver validation.23:17
rm_worktongl: err, that would be bad23:18
rm_workthen the user would just see their LB disappear23:18
rm_workand be very confused23:18
rm_workthey need to be able to query the LBID and see that it went to ERROR23:18
johnsomtongl That would be a bad idea.  The point of 201 is to signal that this is an async interface and the client should poll for status23:18
tongle.g $ neutron lbaas-loadbalancer-create --name lb1 private-subnet23:18
*** yamamoto_ has quit IRC23:18
tonglin our vmware-nsx driver, we requires there is a router for this subnet. otherwise it will fail lb validation.23:19
rm_workok, so in that case, you would set it to ERROR23:19
rm_workand the user would be querying the LBID and see it go to ERROR status from PENDING_CREATE23:19
tonglso during lb creation, if it fails the subnet validation, we will raise BatRequest exception23:19
rm_workunfortunately for your case, the driver enters the picture too late to be part of API validation :/23:20
rm_workit MIGHT be possible to allow for some custom validations... I've done a little bit of work on that front23:21
tonglI see. I thought it was because I didn't raise correct exception :)23:21
rm_workbut that gets into murky territory23:21
rm_workno, by the time you even get the request, we've already accepted it and sent the user a 20123:21
johnsomYeah, by the time the driver gets the request the user is already gone23:22
johnsomThis is something that could be proposed for the Octavia provider spec.  Allowing drivers to have validator.23:23
tonglthat would be awesome to allow driver validator23:23
tonglAs I got some feedback that if it fails driver validator, it is confusing it the resource is still getting created in ERROR state.23:24
johnsomYeah, it's an interesting case where drivers have additional restrictions23:25
*** sshank has quit IRC23:43
*** tongl has quit IRC23:48

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