Hi Team Nova develop!
I build OpenStack version Queens with 05 node (03 node controller, 02 node
compute). I use HAproxy to load balancer all services.
First, I create endpoint with http protocol. Everything is successful.
Next, I change endpoint from http to https. After complete, I
Dear all,
is it possible to define exceptions in the group_binds definition for a network?
for instance we have something like this:
- network:
container_bridge: "vlan4"
container_type: "veth"
container_interface: "eth1"
ip_from_q: "container"
type: "r
>
> But, I can not use nova command, endpoint nova have been redirected from
> https to http. Here: http://prntscr.com/k2e8s6 (command: nova –insecure
> service list)
First of all, it seems that the nova client is hitting /v2.1 instead of /v2.1/
URI and this seems to be triggering the redire
Hi,
I am still trying to figure how to best utilise the small set of
hardware, and discovered the NUMA configuration mechanism. It allows me
to configure reserved cores for certain VMs, but it does not seem to
allow me to say "you can share these cores, but VMs of, say, appropriate
flavour take p
Hi Team Nova develop!
I build OpenStack version Queens with 05 node (03 node controller, 02 node
compute). I use HAproxy to load balancer all services.
First, I create endpoint with http protocol. Everything is successful.
Next, I change endpoint from http to https. After complete, I
Thanks you katynski for response.
But, I had config Haproxy correctly. Here is my config:
http://prntscr.com/k2ofwv
And, when I use openstack command, that is successful. Here:
http://prntscr.com/k2ogau
I don’t think I config wrong. I can create, delete, list, show any VM with
openstack comma
Are you using http_to_wsgi_middleware? Gotta enable that in the nova config
and make sure its in your paste config.
On Wed, 4 Jul 2018, 20:22 Nguyễn Trọng Tấn,
wrote:
> Thanks you katynski for response.
>
> But, I had config Haproxy correctly. Here is my config:
> http://prntscr.com/k2ofwv
>
> A
Thank you Juan Antonio Osorio!
With you response, I had fixed this error. I must add more config in nova.conf.
Here:
[oslo_middleware]
secure_proxy_ssl_header = X-Forwarded-Proto
enable_proxy_headers_parsing = true
Now, I can use nova command normally.
http://prntscr.com/k2oq7o
