Ask Your Question

wby1089's profile - activity

2019-04-17 21:04:09 -0500 received badge  Popular Question (source)
2019-04-12 14:48:33 -0500 received badge  Famous Question (source)
2019-04-04 20:00:11 -0500 commented answer How to disable failover fuction of amphora in Octavia?

Hi

Thanks for your answer.

If the RFE is approved, it would be very helpful for production enviroment.

2019-04-04 19:57:41 -0500 answered a question How to disable failover fuction of amphora in Octavia?

Hi

Thanks for your answer.

If the RFE is approved, it would be very helpful for production enviroment.

2019-03-15 17:00:16 -0500 received badge  Notable Question (source)
2019-03-15 17:00:16 -0500 received badge  Popular Question (source)
2019-03-14 00:12:23 -0500 received badge  Enthusiast
2019-03-13 22:21:36 -0500 asked a question How to disable failover fuction of amphora in Octavia?

Hi

I have two Openstack pod with Octavia. One is for development, so loadbalancer_topology is SINGLE, another is for production, so loadbalancer_topology is ACTIVE_STANDBY.

While maintenance window, health cheking would be failed and Octavia would try to failover amphra. But if there are some problems in Openstack Infra(eg. AMQP down, all compute nodes down), all amphora instance would be removed and provisioning_status of loadbalancer would be ERROR.

I think ACTIVE_STANDBY topology provides high-availbility already and deleting existing amphora can lead unexpectable situations. So I would like to stop removing amphora automatically by health_manager.

How can I disable automatic failover fuction of amphora? Is it can be done by setting "heartbeat_timeout=604800" ?

2019-03-13 21:44:24 -0500 answered a question Octavia - instance is not reachable via the lb-mgmt-net

It is depends on your network environment.

If you have only one controller which has octavia-health-manager, the controller should reach to lb-mgmt-net.

Here is easy way to check connectivity: - create an instance in lb-mgmt-net (cirros would be ok) - ping to the instance from the controller - ssh to the instance from the controller

2019-03-13 21:40:20 -0500 answered a question OCTAVIA SSL ERROR

You should not use lb-mgmt-net as vip-subnet-id.

=as-is= openstack loadbalancer create --project admin --vip-subnet-id lb-mgmt-net --name test1

=to-be= openstack loadbalancer create --project admin --vip-subnet-id selfservice --name test1

2018-11-13 04:14:08 -0500 answered a question Could not connect to instance. Retrying.: SSLError: [SSL: BAD_SIGNATURE] bad signature (_ssl.c:579)

I guess your Octavia keys and certificates are not configured correctly. Please try to check following documents: https://docs.openstack.org/octavia/ro...

2018-11-12 10:46:09 -0500 received badge  Nice Answer (source)
2018-11-12 03:01:57 -0500 asked a question octavia-dashboard - TERMINATED_HTTPS greyed out

Hi

I'm using Octavia Dashboard 2.0.0 and Horizon 14.0.1.

I am having trouble gaining access to the TERMINATED_HTTPS protocol while using octavia load balancers via the horizon dashboard plugin. I can access and control all settings via using octavia cli but the TERMINATED_HTTPS protocol appears grey and inaccessible within horizon.

The existing listener created with the CLI appears in horizon, but SSL certificates are not available - none shown - for viewing or updating.

I found that Horizon shows 500 when calling barbican APIs.

==> horizon/horizon-access.log <== 192.168.60.93 - - [12/Nov/2018:17:51:46 +0900] "GET /api/barbican/secrets/ HTTP/1.1" 500 138 34033 "https://our.openstack.com/project/load_balancer/115999eb-3496-4f44-a583-e50818071d3d" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0"

==> horizon/horizon.log <== [Mon Nov 12 17:51:46.037008 2018] [wsgi:error] [pid 24:tid 140589167392512] [remote 10.168.11.136:56498] UserWarning: Using keystoneclient sessions has been deprecated. Please update your software to use keystoneauth1.

==> horizon/horizon-access.log <== 192.168.60.93 - - [12/Nov/2018:17:51:46 +0900] "GET /api/barbican/certificates/ HTTP/1.1" 500 138 35589 "https://our.openstack.com/project/load_balancer/115999eb-3496-4f44-a583-e50818071d3d" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0"

2018-11-06 17:47:01 -0500 commented answer kernel: vxlan: non-ECT from IP_ADDRESS with TOS=0x2

Great! It works well!

I could be freed from thousands of non-ECT logs per a day.

2018-10-31 02:34:55 -0500 received badge  Teacher (source)
2018-10-30 18:26:31 -0500 answered a question how to create an amphora image for octavia

If you have trouble in creating amphora, try to use test image.

https://tarballs.openstack.org/octavia/test-images/ (https://tarballs.openstack.org/octavi...)

2018-10-30 18:26:31 -0500 answered a question openstack image create returns 500

Try to check keystone by issuing "openstack endpoint list". I think your keystone was not configured correctly.