December 2022 - openstack-discuss

Kolla ansible, add a service to a running openstack deployment
by A Monster 21 Dec '22

21 Dec '22

is there a way to add a service such as elasticsearch to an already done openstack deployment using kolla-ansible?

2 1

[cinder] Cancelling meeting on 28th December
by Rajat Dhasmana 21 Dec '22

21 Dec '22

Hello Argonauts, As discussed in today's meeting[1], we will be cancelling the upstream cinder meeting on 28st December, 2022 and will meet in the meeting on 4th January, 2023. Wishing everyone Merry Christmas and a happy new year! [1] https://meetings.opendev.org/meetings/cinder/2022/cinder.2022-12-21-14.00.l… Thanks Rajat Dhasmana

1 0

[Openstack Heat] - Problems to find right Heat syntax to declare static route in a router template
by ddorra＠t-online.de 21 Dec '22

21 Dec '22

Hi Lajos, many thanks for your hints! Dieter > Hi, > > For adding extra/static routes for your routers you have 2 ways in Heat > (actually Neutron API has it, and you can use them in hot also): > > OS::Neutron::ExtraRoute https://docs.openstack.org/api-ref/network/v2/index.html#update-router > > OS::Neutron::ExtraRouteSethttps://docs.openstack.org/api-ref/network/v2/ind… > > The 1st one is the "old" set router attribute, and the 2nd is add_extraroutes & remove_extraroutes is optimized for concurrent > updates (see the API ref's > description for add_extraroutes). > So in hot template it will look something like this: > type: OS::Neutron::ExtraRouteSet > properties: > router: { get_resource: myrouter0 } > routes: > - destination: 179.24.2.0/24 > nexthop: 192.168.222.221 > > Lajos > > > ddorra(a)t-online.de <ddorra(a)t-online.de> ezt írta (időpont: 2022. dec. 19., H, 21:43): > > Hi, > > > > I want extend my router HOT template by adding a static route. > > > > In the Openstack cli this would be > > > > openstack router add route --route destination='1.2.3.4/17',gateway='10.0.0.66' myrouter > > > > From the OS::Neutron::Router resource description I guess this belongs into the value_specs > > section as a map, but all my attempts failed, e.g. > > > > router1: > > type: 'OS::Neutron::Router' > > properties: > > external_gateway_info: > > network: provider > > name: myrouter > > value_specs: > > route: > > destination: '0.0.0.0/0' > > gateway: '10.0.0.62' > > > > Can somebody help me with the correct syntax? > > > > > > Thanks & best regards, > > Dieter

1 0

[cinder] Bug Report from 12-21-2022
by Sofia Enriquez 21 Dec '22

21 Dec '22

This is a bug report from 12-14-2022 to 12-21-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- High - https://bugs.launchpad.net/cinder/+bug/1999706 "Cinder fails to automatically map availability zones to volume types." Unassigned. Medium - https://bugs.launchpad.net/cinder/+bug/1999766 "Retype VM root Volume Cause VM failed to boot." Unassigned. Cheers, Sofia -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

Magnum private docker registry (insecure_registry) not working?
by Oliver Weinmann 21 Dec '22

21 Dec '22

Hi,I can't seem to get magnum (k8s) to accept my private docker registry. I wanted to have a central registry so not all hosts pull the images during deployment.For this I configured a registry:v2 docker container, pulled the images and pushed them to the local registry and added the following label to my k8s template:container_infra_prefix=172.28.7.140:4000/At first this seems to be working fine and when deploying a new k8s cluster using magnum I can see that it pulls the heat-container-agent image from my local registry:[core@k8s-admin-test-local-reg-6c4hx7gxbdhr-master-0 ~]$ sudo podman ps -aCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES2d08559b9cdc 172.28.7.140:4000/heat-container-agent:wallaby-stable-1 /usr/bin/start-he... 1 second ago Up 1 second ago heat-container-agentBut then it fails to pull the next container:tail -f /var/log/heat-config/heat-config-script/64d35aad-5453-4da4-97c7-45abb640fc90-k8s-admin-test-local-reg-6c4hx7gxbdhr-kube_masters-h3wbcqgm6qv4-0-sfagopiu52se-master_config-2f5lhvr32z7j.logWARNING Attempt 8: Trying to install kubectl. Sleeping 5s+ ssh -F /srv/magnum/.ssh/config root@localhost '/usr/bin/podman run --entrypoint /bin/bash --name install-kubectl --net host --privileged --rm --user root --volume /srv/magnum/bin:/host/srv/magnum/bin 172.28.7.140:4000/hyperkube:v1.23.3-rancher1 -c '\''cp /usr/local/bin/kubectl /host/srv/magnum/bin/kubectl'\'''Trying to pull 172.28.7.140:4000/hyperkube:v1.23.3-rancher1...Error: initializing source docker://172.28.7.140:4000/hyperkube:v1.23.3-rancher1: pinging container registry 172.28.7.140:4000: Get "https://172.28.7.140:4000/v2/": http: server gave HTTP response to HTTPS clientI don't know why but there is no /etc/docker/daemon.json and the /etc/sysconfig/docker also doesn'T contain the line for my insecure registry:root@k8s-admin-test-local-reg-6c4hx7gxbdhr-master-0 ~]# cat /etc/sysconfig/docker# /etc/sysconfig/docker# Modify these options if you want to change the way the docker daemon runsOPTIONS="--selinux-enabled \ --log-driver=journald \ --live-restore \ --default-ulimit nofile=1024:1024 \ --init-path /usr/libexec/docker/docker-init \ --userland-proxy-path /usr/libexec/docker/docker-proxy \"As soon as I manually add my insecure registry here it works just fine. I looked at the magnum code and there is indeed some lines that should actually handle this, but it doesn't seem to be working. What is also weird is that while there is the Option in the Horizon WebUI to set an insecure registry, the openstack coe command doesn't offer this.Best Regards,Oliver

1 1

[kolla] Cancelling meetings on 21 and 28 Dec
by Michał Nasiadka 21 Dec '22

21 Dec '22

Hello Koalas, Cancelling this and next weekly meeting due to Christmas/New Year period. See you next year! Best regards, Michal

1 0

horizon policy
by Parsa Aminian 21 Dec '22

21 Dec '22

Hello is it possible to prevent access to delete instance on horizon for some users ? I want to access only admin user to delete instances from dashboard

1 0

Instance console works only if opened from one of the deployment nodes
by A Monster 21 Dec '22

21 Dec '22

I've deployed openstack yoga using kolla ansible, in three controller nodes, a storage cluster and multiple compute nodes. The deployment included using haproxy, keepalived and hacluster. everything seems to work fine, I can launch instances and networking is doing great, however I found out a problem that I didn't get in all the deployment tests that i've run before. I've combien openstack networks under the same network 10.10.10.0/24 and used the same ip address for both : *kolla_internal_vip_address* and *kolla_external_vip_interface *which is 10.10.10.254, and used an ip route to access to the openstack cluster from an external pc > ip route add 10.10.10.0/24 via 192.168.129.29 dev eth0 where *192.168.129.29* is the address of one of my controllers, however when I try to login to the horizon dashboard using *10.10.10.254 *i don't get a response from the web page, and when I log to the dashboard using the ip address of one of my controller nodes, I cannot use the instance console since it is under the ip address of 10.10.10.254 which is assigned to both *kolla_internal_vip_address* and *kolla_external_vip_interface.* although i can ping 10.10.10.254 from the external network using ip route.

1 0

[all][tc] Technical Committee next weekly meeting on 2022 Dec 21 at 1600 UTC
by Ghanshyam Mann 21 Dec '22

21 Dec '22

Hello Everyone, The technical Committee's next weekly meeting is scheduled for 2022 Dec 21, at 1600 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Tuesday, Dec 20 at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

[horizon] Cancelling next three weekly meetings
by vishal manchanda 20 Dec '22

20 Dec '22

Hello Team, As agreed, during the last weekly meeting, we are canceling our weekly meeting on 21st, 28th December and 4th January. The next weekly meeting will be on 11th January. Happy holidays and a happy new year in advance! Thanks & Regards, Vishal Manchanda

1 0