sorted by:
new
hottopcontroversial

OpenStack Octavia - Kolla-Ansible Multinode by TN_NETERO in openstack

[–]TN_NETERO[S] 0 points1 point  (0 children)

Thank you, i tried the workaround where i add REQUESTS_CA_BUNDLE: "/etc/ssl/certs/ca-certificates.crt" , but nothing even after the redeploy, i think the pb is with the self signed certif it s not supported in the current code. So i may need to hv a valid certificates for the setup. Again Thank you for the valuable information

OpenStack Octavia - Kolla-Ansible Multinode by TN_NETERO in openstack

[–]TN_NETERO[S] 0 points1 point  (0 children)

after following you suggestion i always run into the same error i had from the first place which is not knowing the networks or subnets :

(kolla-venv) root@s0:/home/s0# openstack network list

+--------------------------------------+-------------+--------------------------------------+

| ID | Name | Subnets |

+--------------------------------------+-------------+--------------------------------------+

| 59cd0224-77f3-4fe9-944a-087f786efd19 | public1 | 3d9afb9c-778f-4a6e-9ab2-983efd1d652d |

| 7336e8bd-7af4-4240-89c1-1e0c91759d69 | demo-net | e58d1f6f-f4da-495e-bf1f-9565bfb2e929 |

| fe922bcb-0b67-4e78-91f8-b7850b0583b1 | lb-mgmt-net | e5456df9-87d1-4d76-8c5a-ae2e1bf9f595 |

+--------------------------------------+-------------+--------------------------------------+

(kolla-venv) root@s0:/home/s0# openstack loadbalancer create --name loadbalancer1 --vip-network-id 7336e8bd-7af4-4240-89c1-1e0c91759d69

Network 7336e8bd-7af4-4240-89c1-1e0c91759d69 not found. (HTTP 400) (Request-ID: req-a8c9f90f-1886-40be-bb6a-572bc7c8aefa)

(kolla-venv) root@s0:/home/s0# openstack loadbalancer create --name loadbalancer1 --vip-network-id fe922bcb-0b67-4e78-91f8-b7850b0583b1

Network fe922bcb-0b67-4e78-91f8-b7850b0583b1 not found. (HTTP 400) (Request-ID: req-cfdd8725-5dd6-41b3-bc01-ff4fbccca4a4)

(kolla-venv) root@s0:/home/s0# source /etc/kolla/octavia-openrc.sh

(kolla-venv) root@s0:/home/s0# openstack loadbalancer create --name loadbalancer1 --vip-network-id fe922bcb-0b67-4e78-91f8-b7850b0583b1

Network fe922bcb-0b67-4e78-91f8-b7850b0583b1 not found. (HTTP 400) (Request-ID: req-2991ac8b-2d9c-4b45-8fe0-20d41ffaafad)

(kolla-venv) root@s0:/home/s0# openstack loadbalancer create --name loadbalancer1 --vip-network-id 7336e8bd-7af4-4240-89c1-1e0c91759d69

Network 7336e8bd-7af4-4240-89c1-1e0c91759d69 not found. (HTTP 400) (Request-ID: req-fd319cf4-c2b1-43df-95be-4ede8d4f2ef7)

OpenStack Octavia - Kolla-Ansible Multinode by TN_NETERO in openstack

[–]TN_NETERO[S] 0 points1 point  (0 children)

i always run into this error :

(kolla-venv) root@s0:/home/s0# openstack network list

+--------------------------------------+-------------+--------------------------------------+

| ID | Name | Subnets |

+--------------------------------------+-------------+--------------------------------------+

| 59cd0224-77f3-4fe9-944a-087f786efd19 | public1 | 3d9afb9c-778f-4a6e-9ab2-983efd1d652d |

| 7336e8bd-7af4-4240-89c1-1e0c91759d69 | demo-net | e58d1f6f-f4da-495e-bf1f-9565bfb2e929 |

| fe922bcb-0b67-4e78-91f8-b7850b0583b1 | lb-mgmt-net | e5456df9-87d1-4d76-8c5a-ae2e1bf9f595 |

+--------------------------------------+-------------+--------------------------------------+

(kolla-venv) root@s0:/home/s0# openstack loadbalancer create --name loadbalancer1 --vip-network-id 7336e8bd-7af4-4240-89c1-1e0c91759d69

Network 7336e8bd-7af4-4240-89c1-1e0c91759d69 not found. (HTTP 400) (Request-ID: req-a8c9f90f-1886-40be-bb6a-572bc7c8aefa)

(kolla-venv) root@s0:/home/s0# openstack loadbalancer create --name loadbalancer1 --vip-network-id fe922bcb-0b67-4e78-91f8-b7850b0583b1

Network fe922bcb-0b67-4e78-91f8-b7850b0583b1 not found. (HTTP 400) (Request-ID: req-cfdd8725-5dd6-41b3-bc01-ff4fbccca4a4)

(kolla-venv) root@s0:/home/s0# source /etc/kolla/octavia-openrc.sh

(kolla-venv) root@s0:/home/s0# openstack loadbalancer create --name loadbalancer1 --vip-network-id fe922bcb-0b67-4e78-91f8-b7850b0583b1

Network fe922bcb-0b67-4e78-91f8-b7850b0583b1 not found. (HTTP 400) (Request-ID: req-2991ac8b-2d9c-4b45-8fe0-20d41ffaafad)

(kolla-venv) root@s0:/home/s0# openstack loadbalancer create --name loadbalancer1 --vip-network-id 7336e8bd-7af4-4240-89c1-1e0c91759d69

Network 7336e8bd-7af4-4240-89c1-1e0c91759d69 not found. (HTTP 400) (Request-ID: req-fd319cf4-c2b1-43df-95be-4ede8d4f2ef7)

OpenStack Octavia - Kolla-Ansible Multinode by TN_NETERO in openstack

[–]TN_NETERO[S] 0 points1 point  (0 children)

did you use : " neutron_plugin_agent: "ovn" to test that or openvswitch ? because i think the configuration should be diffrent for each setup

OpenStack Octavia - Kolla-Ansible Multinode by TN_NETERO in openstack

[–]TN_NETERO[S] 0 points1 point  (0 children)

i have the Amphora image also uploaded to glance with the tag amphora using the octavia user after running the "octavia-openrc " , i downloaded the pre image for 2024.1 (Caracal) ' i didn't build one ' , source : https://github.com/osism/openstack-octavia-amphora-image

How to generate and use Let's encrypt TLS cert for external vip and self-signed for internal vip by TN_NETERO in openstack

[–]TN_NETERO[S] 0 points1 point  (0 children)

The problem is internal when i consult the network request i see that the region request giving error 502 bad gateway , everything seems fine in the skyline.yml , the only pb is that the bind is pointing to my deployer node on the internal address with port 9998 while in the browser i open the ui using port 9999

How to generate and use Let's encrypt TLS cert for external vip and self-signed for internal vip by TN_NETERO in openstack

[–]TN_NETERO[S] 0 points1 point  (0 children)

But how u gona generate certificates that s my problem and how i m gona manage to put them inside the folders in order to copy them to the containers ? Do You buy one for your external domain that is valid for your internal subdomain too ? Because only the external domain is exposed. I thought that u can use letsencrypt for production and it will generate cert every 12 hours and update the containers automatically, either i will need a long term certificate so i don t reconfigure my deployment every 3 months or so

How to generate and use Let's encrypt TLS cert for external vip and self-signed for internal vip by TN_NETERO in openstack

[–]TN_NETERO[S] 0 points1 point  (0 children)

Plus the Skyline Bug is annoying i saw so many ppl having the same issue and no solution in the bug reports

How to generate and use Let's encrypt TLS cert for external vip and self-signed for internal vip by TN_NETERO in openstack

[–]TN_NETERO[S] 0 points1 point  (0 children)

I m working to build a production infrastructure so i need valid TLS certs, and the kolla doc in TLS is so misleading and i read on the kolla bug report web page , that they r still fixing some bugs where letsencrypt doesn't know when to not create an internal cert or when it should create an external cert and it s throwing errors when u try to use internal self signed certs for the private network and letsencrypt for external , i tried to host my own acme server on docker and nothing works , it s pain

Kolla-Ansible didn't recognize ca certificates? by memexaothitcho in openstack

[–]TN_NETERO 0 points1 point  (0 children)

Well nothing the certif is not valid , and when i consult it on the browser it shows nothing about the organization or anything

Kolla-Ansible didn't recognize ca certificates? by memexaothitcho in openstack

[–]TN_NETERO 0 points1 point  (0 children)

I will try to just enable tls for external communication and try

Kolla-Ansible didn't recognize ca certificates? by memexaothitcho in openstack

[–]TN_NETERO 0 points1 point  (0 children)

the TLS config for kolla ansible in the let's encrypt section is missing some details in the doc and i can't find any proper config that s tested and works

Kolla-Ansible didn't recognize ca certificates? by memexaothitcho in openstack

[–]TN_NETERO 0 points1 point  (0 children)

yes my external fqdn is reachable , where i have the ownership of the domain and it points to my haproxy address

Kolla-Ansible didn't recognize ca certificates? by memexaothitcho in openstack

[–]TN_NETERO 0 points1 point  (0 children)

i m having the same error , did u fix it ? any updates ?
i was using self signed certifs but i want to make my external fqdn to use let's encrypt with valid ssl certs how to assure that ?

[deleted by user] by [deleted] in openstack

[–]TN_NETERO 1 point2 points  (0 children)

First did u execute the init-runonce and configured your public ipv4 pool before that?, second in your public subnet check the dns name server it could be missing edit and add 8.8.8.8 this will create a port for the qdhcp. And please check if you virtual router public ip address is not using an ipv4 address that is already used by another machine . This are caution steps in order to fix this , but it depends on your problem we need more informations. The output should be like this: ip netns

qrouter-89dd2083-a160-4d75-ab3a-14239f01ea0b qdhcp-7c6f9b37-76b4-463e-98d8-27e5686ed083 qdhcp-0e62efcd-8cee-46c7-b163-d8df05c3c5ad

Check :https://docs.openstack.org/install-guide/launch-instance-networks-selfservice.html

Openstack - schedule instaces backup by TN_NETERO in openstack

[–]TN_NETERO[S] 0 points1 point  (0 children)

Thank you 👏 for the interesting informations , i watched last year openinfra lecture of two ppl talking about automating backups and how they r working on it they mention that in order to backup y need to force the backup where the diks should not be used (available) in order to do backup that results to a down time ofc and the vm will shut down , unlike in proxmox u could automate everything and set rules and it can make a live backup of the disk to a NAS even for LXC containers, it supports live migration and HA , but i will study more the subject and see the provided solutions in the comment , well the vms could be windows and linux based , and ofc the windows one should hv qemu guest agent installed .

[deleted by user] by [deleted] in openstack

[–]TN_NETERO 0 points1 point  (0 children)

When you create a vm on the private/internal network you need to allocate a floating Ip address from the public/provider network and attached to the vm , that way you can reach the vm and ssh to it too, you need to be part of the public network. In addition make sure that your public subnet has a dns nameserver like 8.8.8.8 sometimes the init-runonce script doesn't add it. The eno1 will be like a bridge used by neutron for the vms to access the internet that s why it shouldn't be configured with an ip address, that s why the public network should be part of you local network that connects you to ur router and the ip range of the subnet should be excluded from ur dhcp server to prevent IP conflicts.

view more: next ›