Thursday, 2018-08-09

*** longkb has joined #openstack-lbaas00:41
*** yamamoto has joined #openstack-lbaas01:48
*** yamamoto has quit IRC01:51
*** SumitNaiksatam has joined #openstack-lbaas01:56
*** hongbin has joined #openstack-lbaas02:49
bzhao__Hi, @Team, may I add our project into stackalytics?  I'm so sorry to bring it up as my company wants to use stackalytics records for showing to customers the contribution status, because company treats Octavia as the standard. But now, I don't see our project in stackalytics repo, it just gets the neutron official group from openstack/governance, that means stackalytics collect the contribution or merged patches based03:10
bzhao__on its first post time, not the merge time. So the proposal is changing the collected merged patches based on the merged time.  I'm OK  if we think that's not necessary. Just want to collect some feedbacks from our @Team members.  If we are disagree, please feel free to say "No". Thanks.  Then, the slogan again, Fight for Octavia! ;-)03:10
johnsombzhao__: we are there as “Octavia official”03:12
johnsomhttp://stackalytics.com/?module=octavia-group03:15
johnsomThe merges are listed as “commits”03:16
johnsomNote though, stackalytics can get behind, it maybe tomorrow before UDP shows up there03:17
bzhao__johnsom:  Thanks,  let me think a while how to suggest to marketing. Yeah, thanks johnsom for explaining, just a marketing people catch me about this thing this morning.03:19
johnsomOk, let me know if I don’t understand your request03:20
johnsombzhao__: Is that what you were looking for or something else? I am concerned I don’t know the request03:29
bzhao__johnsom:  They want the advantage records. ;-( . But some Metrics had already matched, except review, commits, personal effort. Hmm, I think I can suggest them about other metrics. All things are that want to make customers attention.03:30
bzhao__johnsom:  Sorry, just thinking and searching something.03:30
bzhao__johnsom:  Yeah, that's it.03:32
bzhao__johnsom: That's I was looking for.03:32
johnsombzhao__: ok, our Stackalytics should be setup the same as Neutron official, just for our project and repositories.03:33
bzhao__johnsom:  Yeah, I search our octavia in Neutron official in previous time. ;-).03:35
johnsombzhao__: yeah, we are not a neutron subproject anymore. We are a top level project like neutron03:36
*** ramishra has joined #openstack-lbaas03:36
*** abaindur has joined #openstack-lbaas03:38
*** abaindur has quit IRC03:38
bzhao__johnsom: Correct. Ha, that's my mistake. OK, I remember that you suggests that the udp healthmonitor is good to using  notify_up/notify_down and store the member status in a specific file. Then I wish that you could give the kind advice about whether I need to refactor that part,  from this point, I just want to make it better and make our team member comfortable when see that part code. ;-).03:39
*** abaindur has joined #openstack-lbaas03:39
*** hongbin has quit IRC03:41
johnsombzhao__: your fix from the DRAIN issue works for me.03:41
bzhao__johnsom:  And the future features, maybe I will try to discuss with you first, then implement as you and our team members suggests. So I'm afraid that you guys may kick me if feel that bad guy(me) make you uncomfortable. ;-)03:42
johnsombzhao__: I think that is a good fix at least for now. If we need we can change it later.03:42
bzhao__johnsom:  ok. That sounds good. ;-)03:43
johnsombzhao__: Ha no, we are nice people. We just want to help and make it easier03:43
johnsombzhao__: most features should go through a specification or an RFE if it is a small patch.  This helps the team know it is being worked on and can give comments03:44
bzhao__johnsom:  Yeah. I'm prety sure that all of you and team members are very nice peoples. Sorry for that, it just a joke...;-)03:45
johnsombzhao__: ok, I hope we get to continue to work together on Octavia03:46
bzhao__johnsom:  Right. I will follow our guideline.03:46
bzhao__johnsom:  It must be a long time. ;-)03:46
johnsomOk, I am signing off for the night. Have a good day with the satisfaction of a job well done03:47
bzhao__johnsom:  Thanks vey much for your help. Have a nice sleep . ;-)03:48
abaindurjohnsom: Hi, i'm hitting some cryptic errors while trying just the first, basic loadbalancer create operation. We are hitting this both with the CLI and a POST curl api call. are you free to help?03:54
abaindurAll we see in logs is:03:55
abaindur2018-08-09 03:43:17.666 17329 DEBUG wsme.api [req-d41e4193-be0a-42cb-9bcd-2230a7c920c9 - fce11e73824a4f1a8f6ffaed87b3a16a - default default] Client-side error: Invalid input for field/attribute load_balancer. Value: ''. unable to convert to LoadBalancerRootPOST. Error: __init__() takes exactly 1 argument (2 given) format_exception /opt/pf9/octavia/lib/python2.7/site-packages/wsme/api.py:22203:55
abaindurthe curl returns an HTTP 40003:56
abaindurwith the same error string: {"debuginfo": null, "faultcode": "Client", "faultstring": "Invalid input for field/attribute load_balancer. Value: ''. unable to convert to LoadBalancerRootPOST. Error: __init__() takes exactly 1 argument (2 given)"}03:56
johnsomabaindur: it is late for me, but what is the URL you are posting to and what is the json content of the POST?03:58
abaindurhttp://paste.openstack.org/show/727690/03:58
abaindurI only did "openstack loadbalancer create --name lb1 --vip-subnet-id b6a8eb74-9197-4f7d-8280-68b8da64deaa"03:59
abaindurThe curl i tried, I got manually from the --debug of the CLI command. The json looks to be correct, looking at the API doc03:59
abaindurnp, if you're sleepy i'll ping you tomorrow04:00
bzhao__abaindur:  I think you maybe add the lb name04:02
abaindurthe CLI command is what i got straight from the lbaas doc04:02
bzhao__abaindur:  Oh, sorry .04:02
johnsomI am out of office for a few days, so let me look04:03
bzhao__let me recheck the log04:03
abaindur'{"loadbalancer": {"vip_subnet_id": "b6a8eb74-9197-4f7d-8280-68b8da64deaa", "name": "lb1", "admin_state_up": true}}'04:03
abainduris the -d payload in POST04:04
johnsomYeah, that looks fine04:04
johnsomI don't understand where you are getting load_balancer from04:04
johnsomWhich version of Octavia are you using?04:04
abaindurQueens04:04
abaindurwe have the endpoint service type as "load-balancer" in Keystone04:05
abainduropenstack endpoint list04:05
abaindur| d3ffec8b5af6492cbc8e2a0ae1e82fc4 | RegionOne | octavia        | load-balancer       | True    | internal  | https://test-du-arjun-oct-roo-966.platform9.horse/octavia                 |04:05
abaindur| d5ed0279efb841069ee6f7e7647b4e12 | RegionOne | octavia        | load-balancer       | True    | admin     | https://test-du-arjun-oct-roo-966.platform9.horse/octavia04:05
abainduris that correct?04:06
johnsomYes, that is correct04:07
abaindurhmm, and our clients are installed w/ queens upper constraints versions04:08
johnsomHTTP/1.1 400 Bad Request04:11
johnsomServer: nginx/1.14.004:11
johnsomWhy does it say the API endpoint is nginx?04:11
johnsomWe do NOT use nginx04:11
johnsomIs it going to some kind of proxy server?04:12
abaindurWe have an nginx reverse proxy that redirects /octavia to 127.0.0.1:987604:12
abaindurWe have this for all services04:12
johnsomYeah, the client doesn't matter as you are going straight to the API with curl04:13
johnsomDid you install from pip/git?04:13
abaindurOctavia?04:14
johnsomI am pretty sure the API process is looking for an load_balancer root tag on the json, but we never released that. it has always been loadbalancer04:14
johnsomYeah04:14
abaindurNo, we installed from source04:14
abaindurin our own venv04:15
johnsomCan you do a git log in the directory so we can see the commit sha04:15
johnsom?04:15
abaindurwell rather, packaged it in an rpm, then install rpm04:15
johnsomThere may have been some commits during ocata or pike that had that, but we never had an actual release with that as the root tag. Certainly not queens04:17
abaindurcommit 99319c24080bdfa51f31cb29e40381670b05e69704:17
abaindurMerge "Allow using spaces for primary common name in SSL certificates" into stable/queens04:17
abaindurhey wait a sec04:18
johnsomThat SHA looks ok04:19
abaindurwhen i curled directly to https://127.0.0.1:9876 I got an curl: (35) SSL received a record that exceeded the maximum permissible length.04:19
abaindurso i made it just http04:19
abaindurAnd it went thru04:19
johnsomOk, so I think something is wrong with your nginx config and it's going somewhere is should not , or ???? Actually it is a pretty strange error04:20
abaindurit didnt work with https04:21
abainduri'm reading in the docs, "As such, there is presently no authentication required to use the Octavia API"04:22
johnsomThat is the Octavia v1 API04:22
johnsomv2 has full RBAC04:22
abaindurhttps://serverfault.com/questions/379772/how-do-i-resolve-the-error-ssl-received-a-record-that-exceeded-the-maximum-perm04:23
johnsomYou would have had to configure the Octavia API to use TLS/SSL for HTTPS. As a wsgi application we usually rely on the web server to deal with TLS/SSL. If you are running in non-wsgi mode you would have had to added custom config to add TLS/SSL to the simple_server04:25
abaindurour nginx proxy actually redirects to proxy_pass http://127.0.0.1:9876/;04:25
abaindursame as what works for our other services04:25
johnsomCheck the API log file. What is the path the request is coming into Octavia as?04:26
abaindurthats the thing, we dont see anything in the nginx log files04:27
abaindurexcept:04:27
abaindur2018-08-09 03:57:56.911 17329 DEBUG wsme.api [req-10739a7d-fc26-4efa-9e71-bf3f44dd073a - fce11e73824a4f1a8f6ffaed87b3a16a - default default] Client-side error: Invalid input for field/attribute load_balancer. Value: ''. unable to convert to LoadBalancerRootPOST. Error: __init__() takes exactly 1 argument (2 given) format_exception /opt/pf9/octavia/lib/python2.7/site-packages/wsme/api.py:22204:27
johnsomNo not nginx, the octavia API process, the process on port 987604:27
johnsomthat nginx is forwarding to04:27
abaindursorry i meant octavia04:28
abaindurThats all in octavia04:28
abaindurnginx is showing: 127.0.0.1 - - [09/Aug/2018:03:57:48 +0000] "POST /octavia/v2.0/lbaas/loadbalancers HTTP/1.1" 400 400 - 216 "-" "curl/7.29.0" "-" to: 127.0.0.1:9876 0.009 0.010 8080 43564 -04:28
johnsomYeah, well, if it is passing /octavia through to the backend it will fail. Without the actual octavia API log I'm not sure.  I don't know how your nginx is configured04:29
johnsomWe don't have a /octavia path04:30
bzhao__This may raise by octavia api layer. It had reach the octavia I think.   They regitered the endpoint with a /octavia path.04:32
bbbbzhao_https://www.irccloud.com/pastebin/5t1y3dZA/04:32
johnsomWhich is ok if their nginx layer strips that when it passes it to Octavia04:32
abaindurhttp://paste.openstack.org/show/727694/04:32
abaindurfor comparison, our nginx locations to /designate and /neutron endpoints, which work 100%04:33
abaindurBut ok... i suppose its a problem on our end somewehre04:34
abaindurthanks for the help04:34
johnsomLet me go read up on nginx config.04:34
abaindurreason being we have that, we dont want to expose that port on public ip04:36
johnsomYes, we don't use ports either04:37
johnsomOn the host with your octavia API process, can you do a "netstat -anp" and look for the process with the 9876 port?04:38
johnsomWe need to find the actual octavia API process and it's log04:38
abainduryea, i did a GET04:38
abaindurit does not return an error, but it returns an empty04:38
abaindur[root@test-du-arjun-oct-roo-966.platform9.horse arjun(admin)]# openstack loadbalancer list04:38
abaindurand nothing else04:38
abaindurI dont see it being logged in octavi-api.log04:39
johnsomIt looks like you are just proxying with nginx, so something else is hosting the wsgi API04:39
abaindurtcp        0      0 127.0.0.1:9876          0.0.0.0:*               LISTEN      17329/python04:39
abaindur17329 ?        S      0:05 /opt/pf9/octavia/bin/python /opt/pf9/octavia/bin/octavia-api --config-file /etc/octavia/octavia.conf04:39
abaindur[root@test-du-arjun-oct-roo-966.platform9.horse arjun(admin)]# ps -ef | grep octavia04:40
abaindurroot      3797 17580  0 04:40 pts/0    00:00:00 grep --color=auto octavia04:40
abainduroctavia  17329     1  0 03:39 ?        00:00:05 /opt/pf9/octavia/bin/python /opt/pf9/octavia/bin/octavia-api --config-file /etc/octavia/octavia.conf04:40
abaindurIt is indeed the correct proc04:40
johnsomOk, so it is running the "simple_sever". Is it started with systemd?04:40
abainduryes04:40
johnsomThere is going to be a journalctl for the system service that starts it. That will likely contain the actual log given your setup04:41
abaindurAre we missing some parameter for it to be logging?04:41
johnsomNo, you would have had to add some config to disable it04:42
abaindurwe see some logs, like API server, 2018-08-09 03:39:32.384 17329 INFO octavia.cmd.api [-] Starting API server on 127.0.0.1:987604:42
abaindurlog_dir = is set correctly in the .conf file as wel04:42
johnsomThere you go, that should be the place04:42
abaindurI meant I see that in the existing octavi-api.log04:42
abaindurnot journalctl04:42
johnsomYou don't see your requests in there?  Even when you curl direct to the port?04:42
abaindurafter that, I only see the error i pasted before04:43
*** irenab has joined #openstack-lbaas04:44
abaindurNo04:46
bbbbzhao_https://www.irccloud.com/pastebin/V3fJF1tz/04:46
abaindurI am tailing it via journalctl -f04:46
johnsomOk, I am pretty sure it is a nginx config issue.  I think you need a rewrite rule inside the location block that strips off the /octavia from the URL path.04:48
johnsomI don't know where your request logs are going, but I'm pretty sure it's passing /octavia to the API simple server and that will not work and will be rejected.04:49
abaindurwell, even when it worked, when i made the req directly to http://127.0.0.1:9876/, i did not see any API req being logged04:51
abaindurI only saw:04:51
abaindur2018-08-09 03:59:51.027 17329 DEBUG oslo_db.sqlalchemy.engines [req-ff74941b-8cc7-4075-859d-c47639e8a6a7 - fce11e73824a4f1a8f6ffaed87b3a16a - default default] MySQL server mode set to STRICT_TRANS_TABLES,STRICT_ALL_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,TRADITIONAL,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION _check_effective_sql_mode /opt/pf9/octavia/lib/python2.7/site-packages/04:51
abainduroslo_db/sqlalchemy/engines.py:29004:51
abaindur2018-08-09 04:14:05.831 17329 DEBUG octavia.network.drivers.noop_driver.driver [req-73570b10-4ce6-4bd1-8655-d4a4ee86f912 - fce11e73824a4f1a8f6ffaed87b3a16a - default default] Subnet NoopManager no-op, get_subnet subnet_id b6a8eb74-9197-4f7d-8280-68b8da64deaa get_subnet /opt/pf9/octavia/lib/python2.7/site-packages/octavia/network/drivers/noop_driver/driver.py:13604:51
abaindur2018-08-09 04:14:05.832 17329 DEBUG octavia.db.repositories [req-73570b10-4ce6-4bd1-8655-d4a4ee86f912 - fce11e73824a4f1a8f6ffaed87b3a16a - default default] Checking quota for project: fce11e73824a4f1a8f6ffaed87b3a16a object: <class 'octavia.common.data_models.LoadBalancer'> check_quota_met /opt/pf9/octavia/lib/python2.7/site-packages/octavia/db/repositories.py:30204:51
abaindur2018-08-09 04:14:05.950 17329 DEBUG octavia.network.drivers.noop_driver.driver [req-73570b10-4ce6-4bd1-8655-d4a4ee86f912 - fce11e73824a4f1a8f6ffaed87b3a16a - default default] Network NoopManager no-op, allocate_vip loadbalancer <octavia.common.data_models.LoadBalancer object at 0x7facbe87c8d0> allocate_vip /opt/pf9/octavia/lib/python2.7/site-packages/octavia/network/drivers/noop_driver/driver.py:3204:51
abaindur2018-08-09 04:14:05.956 17329 INFO octavia.api.v2.controllers.load_balancer [req-73570b10-4ce6-4bd1-8655-d4a4ee86f912 - fce11e73824a4f1a8f6ffaed87b3a16a - default default] Sending created Load Balancer 7c9f31a7-1b23-4c96-a2ac-018e58a1721f to the handler04:51
johnsomIt did work correctly though right? it did create the BL?04:51
johnsomOk, those are ok logs04:52
johnsomThough you are running the noop driver, which won't actually do anything04:52
abaindurDont see any LBs04:53
johnsomSo, maybe when not running under wsgi that "simple_server" will only log the request in debug04:53
abaindurdont see any logs in worker, besides the 2018-08-07 23:45:02.044 11763 INFO octavia.controller.queue.consumer [-] Starting consumer...04:53
johnsomYeah, with no-op drivers configured you won't get any load balnacer. It is all just ghosts in the DB. We use the noop drivers for testing04:54
abainduroh, is the drivers configured for api service?04:54
abaindurok, we have that on the config file where our worker/healthmanager/housekeeper resides04:54
johnsomYes, some of those drivers matter for the API04:54
bbbbzhao_api_handler = queue_producer04:55
abaindurwhat do you mean by simple_server?04:55
johnsomWell, you are running the API as a standalone application, which uses the python "simple_server", it's not very scalable or production quality.  All(most) OpenStack services are intended to be run as wgsi applications per the community goal in Pike: https://governance.openstack.org/tc/goals/pike/deploy-api-in-wsgi.html04:56
johnsomYeah, the queue_producer is one, but networking is required as well to verify the subnets, etc. the user passes in04:59
johnsomIt's mostly for validation calls05:00
johnsomThough I think the VIP port may be created in API  as well05:01
abaindurOur [api] section is left unfilled (at defaults)05:01
ramishraIt seems octavia has broken heat gate, http://logs.openstack.org/44/584544/2/check/heat-functional-convg-mysql-lbaasv2-py35/52f40b7/logs/screen-o-cw.txt.gz#_Aug_08_19_59_12_483217 I assume it's the udp support merged yesterday05:01
johnsomThis is the code for the standalone API process: https://github.com/openstack/octavia/blob/master/octavia/cmd/api.py#L1605:01
bbbbzhao_not sure, they are same with previous release https://www.irccloud.com/pastebin/lhFQzm3h/05:02
ramishrajohnsom: Hi!, any idea what's gone wrong05:02
johnsomramishra This is an issue with the patch merge order. It should be resolved tomorrow when everything merges and updates05:02
ramishraHmm.. how do we merge changes till tomorrow, it's RC1 week. do you suggest disabling the tests is the only option?05:03
ramishrajohnsom: ^^05:03
johnsomramishra Are you using the tarballs.openstack.org testing image?05:03
ramishrajohnsom: yes05:03
johnsomramishra Yeah, that is the issue. Let me look at when that periodic job runs05:04
johnsomramishra Basically that pulled the code mid-merge of a chain of patches and has bad code.  I think it will update and build a new image in about an hour and a half05:05
bbbbzhao_{'error': '400 Bad Request: Invalid protocol information for Listener', 'http_code': 400}05:06
johnsomramishra We saw the same with some of our tests. That image is bad05:06
ramishrajohnsom: OK, once I disable the tests, bringing it back would require plenty of convincing to do, wich I want to avoid05:06
bbbbzhao_seem using the old amp image. not the full merge one05:06
johnsomYeah, watch this folder: http://tarballs.openstack.org/octavia/test-images/ the images should update in about an hour and a half, then recheck05:07
johnsombbbbzhao_ Patch 2 merged, the image built, then patch followup merged. so that image is missing followup05:08
ramishrajohnsom: Thanks, will check in an hour or so.. I assume we would try and ensure that we avoid this kind of issue in the future just before release:)05:08
bbbbzhao_johnsom:  Yeah, the image miss the followup, as we remove the protocol check in that patch.05:09
johnsomramishra Yeah it was unfortunate.05:09
bbbbzhao_ramishra:  Sorry for that.05:10
ramishrajohnsom, bbbbzhao_ np:), thanks!05:10
*** pcaruana has joined #openstack-lbaas06:38
openstackgerritOpenStack Proposal Bot proposed openstack/octavia master: Imported Translations from Zanata  https://review.openstack.org/59012806:46
*** luksky has joined #openstack-lbaas07:03
*** ispp has joined #openstack-lbaas07:06
*** velizarx has joined #openstack-lbaas07:09
*** yamamoto has joined #openstack-lbaas07:11
*** rcernin has quit IRC07:16
*** yamamoto has quit IRC07:22
abainduranyone know what permissions the certs have to be?07:26
abainduron worker, I see following error when it tries to open the ca_certificate file07:27
abaindurCertificateGenerationException: Could not sign the certificate request: Failed to load CA Certificate /root/octcerts/ca_01.pem.07:27
abaindurI am able to open the file myself in python:07:27
abaindur>>> ca_cert = open('/root/octcerts/ca_01.pem', 'rb').read()07:27
*** nmagnezi_ has joined #openstack-lbaas07:39
openstackgerritOpenStack Proposal Bot proposed openstack/neutron-lbaas master: Imported Translations from Zanata  https://review.openstack.org/59017307:44
*** kobis1 has joined #openstack-lbaas07:46
*** velizarx has quit IRC07:46
*** velizarx has joined #openstack-lbaas07:53
*** nmagnezi_ has quit IRC07:57
*** nmagnezi has joined #openstack-lbaas07:57
*** dulek has joined #openstack-lbaas08:21
*** aojea has joined #openstack-lbaas08:22
*** KeithMnemonic has quit IRC08:23
*** ktibi has joined #openstack-lbaas08:37
*** celebdor has joined #openstack-lbaas08:38
*** abaindur has quit IRC08:45
*** aojea has quit IRC08:54
*** ktibi has quit IRC09:00
*** ktibi has joined #openstack-lbaas09:01
*** ispp has quit IRC09:10
*** salmankhan has joined #openstack-lbaas09:14
*** luksky has quit IRC09:56
*** kobis1 has quit IRC10:09
openstackgerritOpenStack Release Bot proposed openstack/neutron-lbaas master: Update reno for stable/rocky  https://review.openstack.org/59022310:27
openstackgerritOpenStack Release Bot proposed openstack/octavia-dashboard master: Update reno for stable/rocky  https://review.openstack.org/59022610:27
openstackgerritOpenStack Release Bot proposed openstack/octavia master: Update reno for stable/rocky  https://review.openstack.org/59023210:27
*** kobis1 has joined #openstack-lbaas10:34
*** luksky has joined #openstack-lbaas10:35
*** frickler has left #openstack-lbaas11:08
*** aojea has joined #openstack-lbaas11:20
*** aojea has quit IRC11:33
*** longkb has quit IRC11:40
*** aojea has joined #openstack-lbaas11:45
*** yamamoto has joined #openstack-lbaas11:57
*** aojea has quit IRC11:58
*** amuller has joined #openstack-lbaas12:00
*** velizarx has quit IRC12:13
*** velizarx has joined #openstack-lbaas12:15
*** oanson has joined #openstack-lbaas12:42
*** ianychoi has quit IRC12:49
*** ramishra has quit IRC12:59
*** velizarx has quit IRC13:02
*** velizarx has joined #openstack-lbaas13:03
*** ramishra has joined #openstack-lbaas13:08
*** yamamoto has quit IRC13:31
openstackgerritGerman Eichberger proposed openstack/neutron-lbaas master: Fix proxy extension for neutron RBAC  https://review.openstack.org/55400413:35
openstackgerritGerman Eichberger proposed openstack/neutron-lbaas master: Gate API test for the lbaasv2-proxy plugin  https://review.openstack.org/53935013:35
xgerman_^^^ this needs to land in Rocky. Working on that for more than a year… that’s for review velocity in this place13:36
openstackgerritGerman Eichberger proposed openstack/neutron-lbaas master: Gate API test for the lbaasv2-proxy plugin  https://review.openstack.org/53935013:38
*** amotoki_ is now known as amotoki14:01
johnsomThat patch is blocked by a dependency14:04
nmagnezijohnsom, o/ ; maybe you'll want this in Rocky https://review.openstack.org/#/c/589408/14:09
*** KeithMnemonic has joined #openstack-lbaas14:19
openstackgerritMerged openstack/neutron-lbaas master: Update reno for stable/rocky  https://review.openstack.org/59022314:24
openstackgerritMerged openstack/octavia master: Update reno for stable/rocky  https://review.openstack.org/59023214:26
openstackgerritMerged openstack/octavia-dashboard master: Update reno for stable/rocky  https://review.openstack.org/59022614:33
cgoncalvesxgerman_, could you help me refreshing my mind please :) can one recover a LB that was once operational from an ERROR after failover failed?14:39
xgerman_if you have the amp API maybe; usually ERROR is final and all you can do is delete14:40
xgerman_also I have a ton of LB in ERROR which still work… look at operational status if it’s ONLINE it’s still working14:40
*** hongbin has joined #openstack-lbaas14:41
xgerman_but we should have someway to self heal those LB14:41
cgoncalvesxgerman_, what do you mean by having the amp API?14:44
xgerman_the amp API allows you to fix amps by failing them over.14:44
xgerman_I don’t recall if you run an lb failover if it will go back into ACTIVE or just not run at all14:45
cgoncalvesscenario is that the cluster was rebooted and the HM started to failover amps because computes were still not up. failover then failed due to black of compute capacity14:45
cgoncalvesah, that amp API, right14:46
cgoncalvess/black/lack/14:46
xgerman_yeah, I have fun adventures when nodes are being rebooted, too14:52
xgerman_I also added a self healing topic for Denver. My ops people are also not thrilled with our frequent going into ERROR when something goes wrong14:53
xgerman_to be fair it’s all nova and neutron throwing errors and we are stopping to not make things worse14:54
xgerman_but neutron and nova throw too many errors - so something’s gotta give ;-)14:54
*** aojea has joined #openstack-lbaas14:55
cgoncalvesoctavia could hint users to the compute or network services :)14:56
cgoncalvesit would be so handy to operators. instead of start looking into octavia logs, they could with great confidence immediately start looking at nova or neutron14:57
xgerman_yep, we should have some description on the LB14:57
xgerman_but then we also should have some “repair” command once nova/neutron are happy again14:58
cgoncalveswhy not invoking failover again?15:01
xgerman_that might do it15:02
*** Swami has joined #openstack-lbaas15:03
*** ivve has quit IRC15:03
*** kobis1 has quit IRC15:05
*** aojea has quit IRC15:06
*** aojea has joined #openstack-lbaas15:07
*** celebdor has quit IRC15:08
*** fnaval has joined #openstack-lbaas15:16
*** celebdor has joined #openstack-lbaas15:32
*** phuoc has quit IRC15:32
*** SumitNaiksatam has quit IRC15:59
*** velizarx has quit IRC16:16
*** hongbin has quit IRC16:37
*** ktibi has quit IRC16:37
*** Swami has quit IRC16:37
*** aojea has quit IRC16:51
*** salmankhan has quit IRC16:58
*** phuoc has joined #openstack-lbaas17:01
*** ramishra has quit IRC17:03
*** luksky has quit IRC17:27
*** SumitNaiksatam has joined #openstack-lbaas18:00
openstackgerritGerman Eichberger proposed openstack/neutron-lbaas master: Gate API test for the lbaasv2-proxy plugin  https://review.openstack.org/53935018:11
*** celebdor has quit IRC18:14
jitekaHello I got few question for you :)18:19
jiteka1. Is ubuntu bionic supported for amphora glance image in Octavia rocky ?18:19
jitekaLast time I tried in queens diskimage-builder script failed on fetching files from cloud-images.ubuntu.com18:19
*** colby_ has joined #openstack-lbaas18:29
xgerman_I have seen a bionic gate fly by. So yes18:30
xgerman_also the latest diskimage builder will support it.18:30
jitekathanks xgerman_ :)18:39
jitekaand second question18:42
jiteka2. I saw that Flavors support is targeted for Rocky but is it plan to backport it to Queens ?18:42
jitekaIf not, with active/standby topology how easy/hard it is to go from single-flavor to multi-flavor18:42
jitekawhen offering multiple class of service for LB going from : amphora VM running among all other users VMs with CPU and RAM overcomitting to dedicated host-aggregate (or cells) with faster hardware with better NICs18:49
jitekaand what is the difference between "flavors" targeted for Octavia Version 3.018:54
jitekaand Flavor support targeted for Considerations for Octavia 3.0+ ?18:54
jitekaIs it the same feature but just also in "beyond rocky" if not ready for rocky or something else ?18:54
xgerman_2) Flavors will be Stein - no plans to backport18:57
xgerman_^^ jiteka18:58
xgerman_there are no firm plans for Octavia 3.0 — not sure if this is even a thing18:58
*** luksky has joined #openstack-lbaas18:58
jitekathanks xgerman_19:02
jitekawill look for queens to rocky upgrade procedure then19:02
xgerman_well, we still have to code flavors ;-)19:02
jitekaand for bionic I confirm that it works19:02
jitekajust got an issue with squashfs on centos : http://paste.openstack.org/show/727762/19:04
jitekalast image I created with diskimage-builder didn't complained about squashfs-tools not being installed19:04
jitekaohh19:05
jitekaI though that you were using stein19:05
jitekato say rocky19:05
jiteka[...] Beer stein (/ˈstaɪn/ STYNE), or simply stein, is an English neologism for either traditional beer mugs made out of stoneware, or specifically ornamental beer mugs that are usually sold as souvenirs or collectibles. In German, the word stein means stone and is not used to refer to a beverage container. [...]19:06
jitekaI tought it was a joke rocky/rock/stein19:06
xgerman_Stein will start in a few week ;-19:06
xgerman_lol, no, it’s the name for the next release -19:06
jitekayes I wasn't aware of the you release codename19:07
jitekathat would help me to understand19:07
jitekas/you/new19:07
*** SumitNaiksatam has left #openstack-lbaas19:25
*** pcaruana has quit IRC19:33
*** amuller has quit IRC19:40
*** aojea has joined #openstack-lbaas19:47
*** abaindur has joined #openstack-lbaas19:54
*** abaindur has quit IRC19:54
*** abaindur has joined #openstack-lbaas19:55
openstackgerritGerman Eichberger proposed openstack/neutron-lbaas master: Gate API test for the lbaasv2-proxy plugin  https://review.openstack.org/53935019:56
*** abaindur has quit IRC20:31
*** abaindur has joined #openstack-lbaas20:31
abaindurAm I right in assuming that by default octavia will only wait 100 seconds for an amphora VM to become active?21:02
abaindur# amp_active_retries = 1021:02
abaindur# amp_active_wait_sec = 1021:02
abaindurIs there any downside increasing this to something mcuh larger, like 5 minutes?21:03
abaindurand might it be better to increase the retries, or the wait duration?21:05
*** dosaboy has joined #openstack-lbaas21:14
abaindurAlso... we would like the amphora VMs to come up in the same tenant as the user who creates the LB21:20
abaindurwe noticed they are instead coming up in services tenant. Is there any way to do this?21:21
*** yamamoto has joined #openstack-lbaas22:04
*** luksky has quit IRC22:07
*** rcernin has joined #openstack-lbaas22:09
*** yamamoto has quit IRC22:21
*** aojea has quit IRC22:46
*** fnaval has quit IRC22:54
*** abaindur has quit IRC23:50
*** abaindur has joined #openstack-lbaas23:51

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