April 2024 - openstack-discuss - lists.openstack.org

[Neutron] Openvswitch forcing MTU 1450
by Karl Kloppenborg 27 Apr '24

27 Apr '24

Hey Neutron team. I have an issue where within the VXLAN network of tenancies the expected 1500 MTU is honoured but despite all MTU in the underlay being 9k and all networks and paths set to 1500, Openvswitch caps the MTU transiting north/south to 1450. This is causing considerable pain to some of our customers and despite trying to force the openvswitche bridges request_mtu to 1500, and all interfaces look right, it’s still caping at 1450. Note, TCP dumps show the pings set to 1500 getting to the network namespace on the openvswitch agent, so it appears something between the nat/snat process. VM1 private -> VM2 private (mtu 1500) = works VM1 private -> VM2 public (mtu 1500) = fails VM -> External (mtu 1500) = fails External Host -> VM (mtu 1500) = fails Adusting to 1422 on ping sizes works. Anyone experienced this? I cannot seem to make heads or tails of it. Thanks, Karl.

1 1

[nova] allow only specific instances on host aggregate
by Eugen Block 26 Apr '24

26 Apr '24

Hi, I'm playing around with host aggregates and the aggregate_instance_extra_specs for flavors. I successfully created a host aggregate, it allows me to schedule instances with a specific flavor on that aggregate only. But is there a way to prevent other VMs from starting on that aggregate (which were launched with different flavors)? The only thing coming to mind is to put that compute node(s) into a different availbility zone. Since the default is "nova", this would prevent anything else to start on that hypervisor. Is there anything I missed with aggregates? Any pointers are appreciated! Thanks! Eugen

3 7

how to set up configuration parameter for a datastore
by 龚永生 26 Apr '24

26 Apr '24

hi, chunyang I installed torve 2023.2, but failed to list the configuration parameter list: root@compute2:~# openstack datastore list +--------------------------------------+----------+ | ID | Name | +--------------------------------------+----------+ | ee74cbff-92d1-4f83-a06e-cd40fb45bac6 | dt_mysql | +--------------------------------------+----------+ root@compute2:~# openstack datastore version list dt_mysql +--------------------------------------+------------+---------+ | ID | Name | Version | +--------------------------------------+------------+---------+ | 82e71712-4e4d-4ff6-947f-8de4c1535d15 | ver_5.7.29 | 5.7.29 | | 8ba2ab5f-6dd1-4f25-b571-4031361a91cf | ver_8.3 | 8.3 | +--------------------------------------+------------+---------+ root@compute2:~# openstack database configuration parameter list 82e71712-4e4d-4ff6-947f-8de4c1535d15 and failed to create configruantion group as well: root@compute2:~# openstack database configuration create group1 '{"sync_binlog" : 1}' --datastore dt_mysql Configuration groups are not supported for this datastore: dt_mysql ver_8.3 (HTTP 422) could you tell me how to enable the configuration parameter list? regards. 龚永生浙江九州未来信息科技有限公司 99CLOUD Co. Ltd. 邮箱（Email）：gong.yongsheng(a)99cloud.net 地址：海淀区上地六街研华大厦5层南侧手机（Mobile)：+86-18618199879 公司网址（WebSite）：http://99cloud.net

1 0

Instance stuck in BUILD status
by 西岭 25 Apr '24

25 Apr '24

Dear openstack trove module developers, I was having trouble creating a trove instance and kept showing build status. My create command is: trove create mysql_zh-11 1 --size 5 --nic net-id=5f161d13-0cfb-4707-9bd6-f23850d86fbf --databases dbtest --users user:password --datastore mysql --datastore_version mysql-5.6 After entering the trove list command, the final state is: | bdcb298c-86d3-42c5-b7af-1cc0c7f93904 | mysql_zh-11 | mysql | mysql-5.6 | BUILD | 1 | 5 | RegionOne | The image I used was downloaded from the openstack website: trove-train-mysql-ubuntu-xenial Enter the openstack server list command and it will display: 2bf580eb-3c93-4689-9b53-e76307beb241 | mysql_zh-11 | ACTIVE | external-net=192.168.0.56 | trove-train-mysql-ubuntu-xenial | mysql-mini | I don't know the username and password of the image, so I can't see the specific information inside the cloud host. In addition, when I used the tool to change the login username and password of the above image, and created the trove instance with the image, after waiting 3600 seconds, it showed: trove.taskmanager.models [-] Service status: ERROR, service error description: guestagent error: TroveError: Failed to get server 0908ee4e-9f1d-444a-9c69-c8b8cc9d8938 for instance 03c2a10c-87f1-4169-9cf7-13735ff8756c, error: Failed to validate token (HTTP 404) (Request-ID: req-9604fb4c-4aae-4351-8996-5ee4dfbd9ad3) This time, I was able to log in to the cloud host generated during the creation of trove. After entering, I found that the guest-agent service failed to start. The reasons were: sudo chown -R ubuntu:root /etc/trove/conf.d cannot be executed. I wonder if it is because the password of the image has been changed? Then, I used the same image to create the trove instance again, and during the instance creation process, I went to the cloud host and started the guest-agent service manually. The result was the same. What else did I miss when creating the instance? How to solve this problem? See attachment for details of trove log. Thank you very much for your help. ----------------------------------------------------- Xi Ling, from Qingdao, China April 25, 2024

2 1

[openstack][nova] Resize instance cause instance error
by Nguyễn Hữu Khôi 25 Apr '24

25 Apr '24

Hello everyone. Sometimes, I resize instance and this instance cannot be resized then it will be error state. I use Kolla-Ansbile Yoga with Dell Powestore5000T as backend with iscsi protocol. I report in this: https://bugs.launchpad.net/nova/+bug/2063345 Pls give some ideas on it? Thank you much Nguyen Huu Khoi

1 1

red hat integration with ceph error
by Adivya Singh 25 Apr '24

25 Apr '24

hi, anybody see this error before, while integrating red hat open stack with ubuntu ceph overcloud-computeids-2 | error={"ansible_job_id": "34 6042025410.662459", "attempts": 2, "changed": false, "finished": 1, "msg": "Paunch failed with config_id tripleo_step4", "rc": 1, "stderr": "Error executing ['podman', 'container', 'exists' , 'nova_libvirt_init_secret']: returned 1\nDid not find container with \"['podman', 'ps', '-a', '--filter', 'label=container_name=nova_libvirt_init_secret', '--filter', 'label=config_id=tri pleo_step4', '--format', '{{.Names}}']\" - retrying without config_id\nDid not find container with \"['podman', 'ps', '-a', '--filter', 'label=container_name=nova_libvirt_init_secret', '--f ormat', '{{.Names}}']\"\nError executing ['podman', 'run', '--name', 'nova_libvirt_init_secret', '--label', 'config_id=tripleo_step4', '--label', 'container_name=nova_libvirt_init_secret', '--label', 'managed_by=tripleo-Computeids', '--label', 'config_data={\"command\": [\"/bin/bash\", \"-c\", \"/usr/bin/virsh secret-define --file /etc/nova/secret.xml && SECRET_UUID=$(fgrep \ \\\\"fsid = \\\\\" /etc/ceph/ceph.conf | cut -d \\\\\" \\\\\" -f 3) && test -n \\\\\"$SECRET_UUID\\\\\" && SECRET_KEY=$(fgrep \\\\\"key = \\\\\" /etc/ceph/ceph.client.openstack.keyring | cu t -d \\\\\" \\\\\" -f 3) && test -n \\\\\"$SECRET_KEY\\\\\" && /usr/bin/virsh secret-set-value --secret $SECRET_UUID --base64 $SECRET_KEY\\\\n\"], \"detach\": false, \"image\": \"192.168.0. 1:8787/rhosp-rhel8/openstack-nova-libvirt:16.2\", \"net\": \"host\", \"privileged\": false, \"security_opt\": \"label=disable\", \"user\": \"root\", \"volumes\": [\"/etc/hosts:/etc/hosts:ro \", \"/etc/localtime:/etc/localtime:ro\", \"/etc/pki/ca-trust/extracted:/etc/pki/ca-trust/extracted:ro\", \"/etc/pki/ca-trust/source/anchors:/etc/pki/ca-trust/source/anchors:ro\", \"/etc/pk i/tls/certs/ca-bundle.crt:/etc/pki/tls/certs/ca-bundle.crt:ro\", \"/etc/pki/tls/certs/ca-bundle.trust.crt:/etc/pki/tls/certs/ca-bundle.trust.crt:ro\", \"/etc/pki/tls/cert.pem:/etc/pki/tls/c ert.pem:ro\", \"/dev/log:/dev/log\", \"/etc/puppet:/etc/puppet:ro\", \"/var/lib/config-data/puppet-generated/nova_libvirt/etc/nova:/etc/nova:ro\", \"/etc/ceph:/etc/ceph:ro\", \"/etc/libvirt :/etc/libvirt\", \"/var/run/libvirt:/var/run/libvirt:shared,z\", \"/var/lib/libvirt:/var/lib/libvirt:shared\"], \"environment\": {\"TRIPLEO_CONFIG_HASH\": \"f780b2585d2cb2edc5954608158cf938 \"}}', '--conmon-pidfile=/var/run/nova_libvirt_init_secret.pid', '--log-driver', 'k8s-file', '--log-opt', 'path=/var/log/containers/stdouts/nova_libvirt_init_secret.log', '--env=TRIPLEO_CON regards Adivya Sungh

2 1

[I18n][PTG] 2024.2 Dalmatian PTG - I18n SIG summary
by Ian Y. Choi 25 Apr '24

25 Apr '24

Hi all, As I18n SIG lead, I would like to share with you a summary of the recent discussions held during the 2024.2 Dalmatian PTG regarding the Internationalization (I18n) Special Interest Group (SIG). Firstly, I would like to express my sincere appreciation to the entire community for their commitment to make OpenStack more internationalized. The efforts put forth in translating and making OpenStack accessible globally are truly commendable, thanks to the contributions of numerous individuals, although we are under unprecedented situations and even Zanata will sunset soon [1]. During the PTG, I18n SIG covered several important topics with active and invaluable contributors including Seongsoo (a special thanks for his leadership both I18n team and within the Korea User group): 1. Progress on open reviews for I18n: We discussed pending items in the OpenStack/I18n repository and the status of various reviews. 2. Discussion on the OpenStack/I18n repository structure: This included plans to embrace the use of Weblate - wlc library and add tox environment and corresponding requirements.txt. 3. Pilot work progress on governance translation support: A demonstration was provided on setting up a new project with API and CLI. 4. Feasibility discussion on migrating from translate.openstack.org earlier than [1]. Deliberation on target languages and next steps for user survey translation. 5. User survey translation discussion: Target languages and next steps were deliberated upon. In sum, I18n will continue our effort to finalize the migration from Zanata to Weblate to emphasize the importance of I18n as a fundamental component for global OpenStack accessibility. Thank you for your continuation of the I18n SIG. If you have any questions or would like further information on any of the discussed topics, please don't hesitate to reach out. Best regards, /Ian [1] https://lists.osci.io/hyperkitty/list/zanata-sunset@lists.osci.io/thread/6F… [2] I18n PTG Etherpad: https://etherpad.opendev.org/p/apr2024-ptg-i18n [3] I18n PTG Team Photo 1: https://1drv.ms/i/s!AgSCQctkWshsgb8ZvM-l7Ol1UOxNjA?e=5tdLpb [3] I18n PTG Team Photo 2: https://cdn.discordapp.com/attachments/1192271703057911888/1228373792162840…

1 0

Compute Resources
by Gk Gk 25 Apr '24

25 Apr '24

Hi, Is there a way to find out the available ram, disk and vcpus on a compute node for vm creation using any placement APIs or any other way ?

3 3

[cinder][dev][ptl] NVMe/FC
by yian.zong＠dell.com 25 Apr '24

25 Apr '24

Hi cinder team, I'd like to know if cinder supports NVMe/FC. From nvmeof connector [1], it seems only RoCE(RDMA) and TCP. [1] https://opendev.org/openstack/os-brick/src/branch/master/os_brick/initiator… Thank you! Yian

5 5

[cinder][PTG] 2024.2 Dalmatian PTG summary
by Jon Bernard 25 Apr '24

25 Apr '24

Hello everyone, thanks for a very productive PTG for the Dalmatian cycle. Below is a brief summary of the highlights. The raw etherpad notes are here[1] and both the summary and transcribed etherpad notes are captured in our wiki here[2]. # Improve driver documentation When proposing new or updating existing drivers, our interface can be confusing. We agreed on an effort to migrate class documentation to the interface definitions, make clear the mandatory and optional methods for drivers, and maintain this documentation going forward. # User visible information in volume types Volume type metadata and extra specs are not visible to users, making it difficult to ascertain whether a volume type will lead to encryption or replication. Agreement was reached on metadata fields similar to Glance's metadefs, allowing drivers to report capabilities in a standard way and allowing that metadata to become visible to admins and users. # Optional backup driver dependencies Although volume driver dependencies are optional, those of our backup drivers are listed in requirements and are therefore always installed irrespective of deployment configuration. Agreement was reached to move these dependencies to driver-requirements. This should simplify efforts of both deployers and packagers. # Simplify deployments A few ideas were proposed to improve our deployment: * When cinder-volume is deployed in an active-active configuration, our `backend_host` parameter must be updated on every backend to have the same value, we would like to remove this additional step. * Use of predictable names to define tenants, instead of unique IDs. * Have dedicated quote section in our configuration for quote-related options. # Response schema validation A spec to add response schema validation in addition to our existing request validation was proposed. With adequate coverage, clients in various languages could be autogenerated (in theory). No significant objects were raised, agreement to review related patches this cycle. # Documentation of Ceph auth requirements We do not provide comprehensive and easy-to-find documentation on exactly what authentication/permission expectations there are between different services, leading deployers troubleshoot themselves and not be able to rely on upstream best practices. Agreement to improve this situation in the current cycle. # Cinder backup improvements An accumulation of bug fixes and performance improvements have stalled in the review queue. We went through the major ones as a team to attempt to bring awareness and unblock the remaining review requirements. See WIKI notes for specific details. # Migrating backups between multiple backends There is desire to support multiple backup backends where new backups go to a new backend while backups in an old backend remain readable. We want to avoid needing to create a full backup in the new backend to support incremental snapshots (and the associated charge). A spec will be proposed for review and work towards this goal will proceed during this cycle. # Cross-project with Glance In a cross-project collaboration with the Glance team, an improved method for image migration was proposed. Agreement to introduce a new migration operation in Glance. Cinder context was provided and a consensus on path forward was reached. # Cross-project with Nova In a cross-project collaboration with both Nova and Glance, the topic of image encryption was discussed. Dan Smith from the Nova team provided input from the Nova side. Cinder and Nova expect LUKS formatted images, but Glance currently supports GPG encrypted images - requiring re-encryption prior to use. It was noted that LUKS encrypted images can be created without root permission and the Glance team is now looking to drop GPG support and consolidate around LUKS as our unified format. # Active-Active support for NetApp A NetApp engineer raised questions about adding active-active support to the driver. Questions were answered and that work should proceed in this cycle. # Performance of parallel clone operations For the clone operation in cinder we're using a single distributed lock to prevent the source volume from being deleted mid-operation. This causes multiple concurrent clone operations to block. Under the right conditions, this can cause a significant performance degradation. Multiple possible solutions were discussed (read-write locks) and a consensus to use the DB was reached. Some details are unclear, awaiting a spec before moving forward. # Volume encryption with user defined keys Cinder does not currently support encryption with key provided by the user. Users could both manage their own keys and data could be recovered even if keys are lost at the deployment. There are several technical challenges to support this. Several of these hurdles were raised, more thought and research is needed before we have a spec that could be reviewed. [1] https://etherpad.opendev.org/p/dalmatian-ptg-cinder [2] https://wiki.openstack.org/wiki/CinderDalmatianPTGSummary -- Jon

2 1