November 2021 - openstack-discuss

RE: Nova Local Disk Storage (Seena Fallah)
by Steven Relf 30 Nov '21

30 Nov '21

Hi Seena, Do you mean passing an entire disk to an instance, or moving where nova stores its ephemeral disks? (e.g. /var/lib/nova/instances?) Rgds Steve. The future has already arrived. It's just not evenly distributed yet - William Gibson Hi, Is there any support for creating instances on a whole separate disk, not an LVM?

1 0

[glance][image-import] local disk space required by image import and conversion
by Tony Liu 30 Nov '21

30 Nov '21

Hi, The target is for user to import .qcow2 image from download site and automatically stored as raw image. Read through [1], this seems doable. I am not sure the workflow. Does it download the whole qcow2 and convert it to raw locally, or download, convert and upload in a streaming way, which only require small space for caching? The question is that, how much local disk space is required for such import and conversion? [1] https://docs.openstack.org/glance/latest/admin/interoperable-image-import.h… Thanks! Tony

2 2

[tripleo] puppet_config: immutable relationship between config_volume and config_image?
by Brent Eagles 30 Nov '21

30 Nov '21

Hi all, I've been working on https://review.opendev.org/c/openstack/tripleo-heat-templates/+/816895 and the current pep8 check error on the designate-api-container-puppet.yaml template appears to disallow using different container config images on the same config volume. I see where this makes sense but because the way the puppet_config sections seem to be structured I wonder if it was intentional. The templates happen to work in this patch's case because the api specific config image in this template only includes some additional binaries for apache+wsgi necessary for the puppet. However, I can see where this might cause some really unfortunate issues if the config images for a given config_volume were to have different versions of puppet. While I will alter the templates so the designate config volume use the same config image, it does beg the question if having the puppet_config config_volume definitions duplicated across the templates is a good pattern. Would it be a better choice to adopt a pattern where the immutable parts of the config_volumes (e.g. config_volume name, config_image) can only be defined once per config volume? Perhaps in a separate file and have the mutable parts in their respective template definitions? Cheer, Brent -- Brent Eagles Principal Software Engineer Red Hat Inc.

2 2

[ironic] End of year meeting schedule
by Julia Kreger 30 Nov '21

30 Nov '21

Greetings everyone, Today, during the Ironic team meeting, we reached consensus[0] that we would not hold meetings during the last half of December and for the first week of January. Much as we've done the past few years to give contributors time they can feel safe taking off without missing any meetings, coupled with end of year PTO usage and holidays. We will resume our regular meetings on January 10th, 2022. Dates of cancelled meetings: * December 20th, 2021 * December 27th, 2021 * January 3rd, 2022 Hopefully everyone will get plenty of rest, and be ready to review plenty of code when they get back! Thanks, -Julia [0]: https://meetings.opendev.org/meetings/ironic/2021/ironic.2021-11-29-15.00.l…

1 0

[neutron][nova] [kolla] vif plugged timeout
by Michal Arbet 30 Nov '21

30 Nov '21

Hi, Has anyone seen issue which I am currently facing ? When launching heat stack ( but it's same if I launch several of instances ) vif plugged in timeouts an I don't know why, sometimes it is OK ..sometimes is failing. Sometimes neutron reports vif plugged in < 10 sec ( test env ) sometimes it's 100 and more seconds, it seems there is some race condition but I can't find out where the problem is. But on the end every instance is spawned ok (retry mechanism worked). Another finding is that it has to do something with security group, if noop driver is used ..everything is working good. Firewall security setup is openvswitch . Test env is wallaby. I will attach some logs when I will be near PC .. Thank you, Michal Arbet (Kevko)

8 12

[wallaby][ovn][Open vSwitch] HA for OVN DB servers using pacemaker
by Faisal Sheikh 30 Nov '21

30 Nov '21

Hi, I am using Openstack Wallaby release with OVN on Ubuntu 20.04. My environment consists of 2 compute nodes and 1 controller node. ovs-vswitchd (Open vSwitch) 2.15.0 Ubuntu Kernel Version: 5.4.0-88-generic compute node1 172.16.30.1 compute node2 172.16.30.3 controller/Network node/Primary ovs-db IP 172.16.30.46 backup ovs-db 172.16.30.47 I added another node for backup ovs-db server (172.16.30.47 ) and installed openvswitch-ovn and networking-ovn packages on it for backup ovs-db server and using Pacemaker to manage the ovn-northd(Open vSwitch) service between primary and backup ovs-db server active/passive HA mode. Pacemaker cluster is successful and after creating a pacemaker cluster, I am using the following commands to create one active and one backup server for OVN databases. $ pcs resource create ovndb_servers ocf:ovn:ovndb-servers \ master_ip=172.16.30.46 \ ovn_ctl=<path of the ovn-ctl script> \ op monitor interval="10s" \ op monitor role=Master interval="15s" But i am getting below error: Error: Agent 'ocf:ovn:ovndb-servers' is not installed or does not provide valid metadata: Metadata query for ocf:ovn:ovndb-servers failed: Input/output error, use --force to override I would really appreciate any input in this regard. Best regards, Faisal Sheikh

1 0

Regarding Drop down of frequently used stacks in OpenStack Wallaby Version 23.1.2
by Adivya Singh 29 Nov '21

29 Nov '21

Dear Team, I want a Drop down of frequently used stack in my orchestration --> Launch Stack parametre in openstack version given above, Is there any Solution for this, How should i go ahead with this Regards Adivya Singh

2 2

[wallaby][ovn][Open vSwitch] HA for OVN DB servers using pacemaker
by Faisal Sheikh 29 Nov '21

29 Nov '21

Hi, I am using Openstack Wallaby release with OVN on Ubuntu 20.04. My environment consists of 2 compute nodes and 1 controller node. ovs-vswitchd (Open vSwitch) 2.15.0 Ubuntu Kernel Version: 5.4.0-88-generic compute node1 172.16.30.1 compute node2 172.16.30.3 controller/Network node/Primary ovs-db IP 172.16.30.46 backup ovs-db 172.16.30.47 I added another node for backup ovs-db server (172.16.30.47 ) and installed openvswitch-ovn and networking-ovn packages on it for backup ovs-db server and using Pacemaker to manage the ovn-northd(Open vSwitch) service between primary and backup ovs-db server active/passive HA mode. Pacemaker cluster is successful and after creating a pacemaker cluster, I am using the following commands to create one active and one backup server for OVN databases. $ pcs resource create ovndb_servers ocf:ovn:ovndb-servers \ master_ip=172.16.30.46 \ ovn_ctl=<path of the ovn-ctl script> \ op monitor interval="10s" \ op monitor role=Master interval="15s" But i am getting below error: Error: Agent 'ocf:ovn:ovndb-servers' is not installed or does not provide valid metadata: Metadata query for ocf:ovn:ovndb-servers failed: Input/output error, use --force to override I would really appreciate any input in this regard. Best regards, Faisal Sheikh

1 0

[neutron]Some floating IPs inaccessible after restart of L3 agent
by Kamil Madáč 29 Nov '21

29 Nov '21

Hello Everyone, We have openstack Victoria deployed since the beginning of the year with kolla/ansible in docker containers. Everything was running OK, but few weeks ago we noticed issues with networking. Our installation uses Openvswitch networking with DVR non HA routers. Everything is running smoothly until we restart L3 agent. After that, some floating ips of VMs running on the node where L3 agent is running becomes inaccessible. Workaround is to reassign floating IP to affected VM. Every restart affects same floating IPs and VMs. No errors/excpetions found in logs. I was able to find out that after restart there are missing routes for those particular floating IPs in fip- namespace, which causes that proxy arp responses are not working. After floating IP address is reassigned, routes are added by L3 agent and floating IP is working again. Looks like some sort of race condition in L3 agent, but I was not able to identify any possible existing bug. L3 agent is in version 17.0.1.dev44. Is anyone aware of any existing bug which could explain such behavior, or does anyone have idea how to solve the issue? Kamil Madáč Slovensko IT a.s.

2 3

[Image Encryption] No meeting today
by Josephine Seifert 29 Nov '21

29 Nov '21

Hi, due to a conflicting meeting today I will not be able to hold the popup team meeting. Next meeting will be next week. greetings Josphine (Luzi)

1 0