May 2023 - openstack-discuss - lists.openstack.org

[horizon][nova][masakari] Instances created with "Any AZ" problem
by Nguyễn Hữu Khôi 02 May '23

02 May '23

Hello guys. I playing with Nova AZ and Masakari https://docs.openstack.org/nova/latest/admin/availability-zones.html Masakari will move server by nova scheduler. Openstack Docs describe that: If the server was not created in a specific zone then it is free to be moved to other zones, i.e. the AvailabilityZoneFilter <https://docs.openstack.org/nova/latest/admin/scheduling.html#availabilityzo…> is a no-op. I see that everyone usually creates instances with "Any Availability Zone" on Horzion and also we don't specify AZ when creating instances by cli. By this way, when we use Masakari or we miragrated instances( or evacuate) so our instance will be moved to other zones. Can we attach AZ to server create requests API based on Any Availability Zone to limit instances moved to other zones? Thank you. Regards Nguyen Huu Khoi

5 20

[kolla-ansible][all][nova][zed][latest] USB passthrough / Hot-plug / Cold-plug
by Modyngs 02 May '23

02 May '23

090c090cFolks, A USB device (not necessarily a mass/Flash drive) needs to be connected to one of the VMs (an openstack instance). Openstack installed with kolla-ansible{Latest version/ Also tested on Zed} ALL IN ONE Deployments on ubuntu server 22.04 ( Core i9 12900K). I found the [nova-libvirt] container which contains *virsh *and is able to edit it or use custom config for VMs. I've gone through lots of the docs, to name a few: https://libvirt.org/formatdomain.html https://wiki.openstack.org/wiki/Nova/USB_device_hot_cold_plug https://wiki.openstack.org/wiki/Nova/proposal_about_usb_passthrough https://documentation.suse.com/sles/15-SP1/html/SLES-all/cha-libvirt-config… https://wiki.openstack.org/wiki/Nova/USB_device_hot_cold_plug https://docs.nxp.com/bundle/GUID-487B2E69-BB19-42CB-AC38-7EF18C0FE3AE/page/… but none of them worked for me!! To reproduce: *Cold-Plug :* *$ lsusb (on host)* Bus 001 Device 014: ID 090c:1000 Silicon Motion >>>> Note Device number changed every time I disconnect the device. So it might be different in the changed attempt shown below) *$ docker exec -it nova_libvirt /bin/bash* *%Turn the Desired VM off* *# virsh list --all* Id Name State --------------------------------------------- 2 instance-00000002 running 19 instance-00000008 running - instance-0000000a shut off *# virsh edit instance-0000000a* Add the changes [1][2][3][4],... ( many efforts have been done but few samples of them are) [1]: under <devices> added <hostdev mode='subsystem' type='usb'> <source> <vendor id='0x090c'/> <product id='0x1000'/> </source> </hostdev> [2]:under <devices> added <controller type='usb' index='0'/> <hostdev mode='subsystem' type='usb'> <source> <vendor id='0x090c'/> <product id='0x1000'/> </source> </hostdev> [3]: under <devices> added <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x090c'/> <product id='0x1000'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </hostdev> [4]: under <devices> added <controller type='usb' model='nec-xhci' index='0'/> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x090c'/> <product id='0x1000'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </hostdev> [5]: <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x090c'/> <product id='0x1000'/> </source> <address type='usb' bus='1' port='2'/> <controller type='usb' index='0'/> </hostdev> *%Start the VM* *expected behavior:* when login to the VM, lsusb or df -h shows the USB *what happened:* it wont show the USB from the VM *OR *virsh dumpxml instance-0000000a > instance-0000000a.xml and then change the configs as above and then virsh attach-device instance-0000000a --file /path/to/updated-instance-0000000a.xml --config *Hot-Plug :* *$ lsusb (on host)* Bus 001 Device 014: ID 090c:1000 Silicon Motion >>>> Note Device number changed every time I disconnect the device. So it might be different in the changed attempt shown below) *$ docker exec -it nova_libvirt /bin/bash* *# virsh list --all* Id Name State --------------------------------------------- 2 instance-00000002 running 19 instance-00000008 running 20 instance-0000000a running *#nano USB.xml* *%add changes explained in *[1][2][3][4],... *$ virsh attach-device instance-0000000a /path/to/USB.xml/file* *expected behavior:* lsusb or df -h shows the USB *what happened:* it wont show the USB from the VM *Can you please guide me through this? Any recommendation would be much appreciated!Any custom changes comes to your mind ( Reply it) would be solution for this problem /;* Thanks Best regards

2 1

[cinder][kolla][OpenstackAnsible] 2023.1 Antelope Cycle-Trailing Release Deadline
by Elõd Illés 02 May '23

02 May '23

Hello teams with trailing projects, The 2023.1 Antelope cycle-trailing release deadline is in ~1 months [1], and all projects following the cycle-trailing release model must release their 2023.1 Antelope deliverables by June 1st, 2023. The following trailing projects haven't been released yet for 2023.1 Antelope (aside the release candidates versions if exists). Cinder team's deliverables: - cinderlib OSA team's deliverables: - openstack-ansible-roles - openstack-ansible Kolla team's deliverables: - kayobe - kolla - kolla-ansible - ansible-collection-kolla This is just a friendly reminder to allow you to release these projects in time. Do not hesitate to ping us if you have any questions or concerns. [1] https://releases.openstack.org/bobcat/schedule.html#b-cycle-trail Thanks, Előd irc: elodilles @ #openstack-release

1 0

[openstack-helm] Cancelling monthly meetings
by Vladimir Kozhukalov 02 May '23

02 May '23

Dear Openstack-helmers, I would like to announce that we are going to stop having monthly IRC meetings due to the lack of interest. There are two major concerns: 1) It is usually not a good idea to wait few weeks for the next meeting to happen if you have something to discuss 2) If only few people are attending the meeting then it is anyway not enough to have a strong community consensus and to make any important decisions We discussed this a couple months ago in the IRC meeting and now it is time to do the next step and to cancel it. So, if you have something to discuss please feel free to start the discussion directly in the #openstack-helm Slack chat (Slack is our preferable way of communication). Today's meeting (May/02/2023) is also canceled. -- Best regards, Kozhukalov Vladimir

1 0

[tripleo] hold rechecks content provider gate blocker - CentOS-9 stream mirrors
by Ronelle Landy 02 May '23

02 May '23

Hello All, We have a check/gate blocker impacting all CentOS-9 jobs. Details are in: https://bugs.launchpad.net/tripleo/+bug/2018265 - CentOS-9 stream mirrors are returning Status code: 404. Per https://review.opendev.org/868392 - the Rackspace mirrors are being used to sync CentOS-9 repos - so possibly there is a lag/roll back there. We will post out once there is a fix/workaround or if the situation gets unblocked dueto an update. Thank you.

1 1

Offline Openstack Release:Train Deployment
by Vineet Thakur 02 May '23

02 May '23

Greetings openstack community members, It's regarding the deployment of openstack release: train on CentoOS 7.9 environment by using openstack-ansible tool. (Offline environment) We are facing challenges to download the packages, some package links are not accessible or somewhere PIP packages are not available as per the constraint requirement list. See: https://artifacts.ci.centos.org/sig-cloudinstance/centos-7-191001/x86-64/ce… For pip packages: https://opendev.org/openstack/requirements/raw/0cfc2ef6318b639bb4287fa051ea… During installation we are facing a lot of errors, and not sure what would be the best approach in such scenarios where packages are not available or need to be downloaded from random sites. We are in the mid of a mega deployment and appreciate it if you can guide us through. Awaiting your response, thank you. Kind Regards, Vineet Thakur

3 3

[tc] Technical Committee next weekly meeting on May 2, 2023
by Nikolla, Kristi 01 May '23

01 May '23

Hi all, This is a reminder that the next weekly Technical Committee meeting is to be held tomorrow (May 2) at 1800 UTC on Zoom. Items can be proposed by editing the wiki page at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting At the end of today I will send out an email with the finalized agenda. Thank you, Kristi Nikolla

1 1

[kolla-ansible] How to test local docker registry
by Satish Patel 01 May '23

01 May '23

Folks, I have 3 controller nodes and on controller01 I have configured the local registry and pushed all images into the local registry. I have pointed out 2 other nodes to use controller01 local registry. When i run "kolla-ansible -i multinode deploy" it works on controller01 and docker start all containers but one controller02 and 03 I encounter error related docker registry Error: https://paste.opendev.org/show/bmwbM3PB33a8hrA1Wi6e/ docker daemon.json file on controller02 and 03 (docker-reg is point to controller01) root@controller02:~# cat /etc/docker/daemon.json { "bridge": "none", "insecure-registries": [ "docker-reg:4000" ], "ip-forward": false, "iptables": false, "log-opts": { "max-file": "5", "max-size": "50m" } How do I check my docker registry is functioning? I have tried following commands on 02 and 03 nodes but following error. root@controller02:~# docker pull docker-reg:4000/openstack.kolla/ubuntu-source-fluentd Using default tag: latest Error response from daemon: manifest for docker-reg:4000/openstack.kolla/ubuntu-source-fluentd:latest not found: manifest unknown: manifest unknown Are there any way to test if my registry is functional and nothing wrong. There are no network issues. I have a test with port ping using the nc command.

1 1

[Neutron] Bug deputy Apr 24 - May 1
by Jakub Libosvar 01 May '23

01 May '23

Hi all, I was the bug deputy for the last week. There are 2 critical bugs, one is pending merge at this time and one needs an assignee: https://bugs.launchpad.net/neutron/+bug/2017992 You can find the full report below. Kuba Critical - Jobs running on vexxhost provider failing with Mirror Issues https://bugs.launchpad.net/neutron/+bug/2017992 Needs an assignee - [master][functional] test_cascading_del_in_txn fails with ovsdbapp=2.3.0 https://bugs.launchpad.net/neutron/+bug/2018130 In progress: https://review.opendev.org/c/openstack/neutron/+/881896 Assigned to Yatin High - Tenant user cannot delete a port associated with an FIP belonging to the admin tenant https://bugs.launchpad.net/neutron/+bug/2017680 In progress: https://review.opendev.org/c/openstack/neutron/+/881827 Assigned to Fernando - OVN: ovnmeta namespaces missing during scalability test causing DHCP issues https://bugs.launchpad.net/neutron/+bug/2017748 In progress: https://review.opendev.org/c/openstack/neutron/+/881487 Assigned to Lucas - Incorrect use of "db_api.CONTEXT_*” decorators https://bugs.launchpad.net/neutron/+bug/2017784 In progress: https://review.opendev.org/c/openstack/neutron/+/881569 Assigned to Rodolfo - OVN trunk subport bouncing between compute while live-migrating https://bugs.launchpad.net/neutron/+bug/2017912 Assigned to Arnau Medium - Move OVN Metadata Agent code to the new OVN Neutron Agent https://bugs.launchpad.net/neutron/+bug/2017871 Assigned to Lucas - ML2 context not considering tags at network creation and update https://bugs.launchpad.net/neutron/+bug/ Low - Remove "neutron-ovn-tempest-ovs-release-ubuntu-old” job https://bugs.launchpad.net/neutron/+bug/2017500 In progress: https://review.opendev.org/c/openstack/neutron/+/881342 Assigned to Rodolfo - ``cmd.sanity.checks._get_ovn_version`` is returning a 3 element tuple, instead of 2 https://bugs.launchpad.net/neutron/+bug/2017878 In progress: https://review.opendev.org/c/openstack/neutron/+/881708 Assigned to Rodolfo - SQL warning retrieving ports if the network list is empty https://bugs.launchpad.net/neutron/+bug/2018000 In progress: https://review.opendev.org/c/openstack/neutron/+/881830 Assigned to Rodolfo

1 0

[tc][all] Technical Committee Weekly Summary -- April 28, 2023
by Nikolla, Kristi 01 May '23

01 May '23

Hi all, Here’s another edition of “What’s happening on the Technical Committee.” Meeting ======= The Technical Committee met on April 25 on the #openstack-tc channel on OFTC IRC. The next meeting will be held on May 2 at 18:00UTC on Zoom. For more information visit https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting Happenings ========== Holding on dropping Python 3.8 ------------------------------ We are drafting guidelines to keep Python 3.8 support in OpenStack for 2023.2. This was discussed during Tuesday's TC meeting as it was causing significant breakage to the gate. [0]. https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033469.h… New proposal to add release naming recommendations for package maintainers ------------------------------------------------------- During the last TC meeting we discussed the confusion arising from upstream OpenStack standardizing on the release names (ex. 2023.2) whereas some distros were favoring codenames (ex. Bobcat). We have a proposal up to recommend package maintainers follow our naming.[1] [0]. https://meetings.opendev.org/meetings/tc/2023/tc.2023-04-25-18.00.log.html#… [1]. https://review.opendev.org/c/openstack/governance/+/881712 New Upstream Investment Opportunity: Ironic ARM Support ------------------------------------------------------- Thanks to Jay Faulkner for proposing a new investment opportunity that we just merged![0] "The OpenStack community is seeking ARM hardware and system administrators or developers with background in provisioning ARM devices to partner with the Ironic bare metal team. The Ironic project produces the OpenStack service and libraries to manage and provision physical machines." [0]. https://governance.openstack.org/tc/reference/upstream-investment-opportuni… Changes ======= • Merged • Add charmed openstack-hypervisor OpenStack Charms | https://review.opendev.org/c/openstack/governance/+/879437 • Update to hacking v6 (code-change) | https://review.opendev.org/c/openstack/governance/+/881266 • Switch to 2023.2 testing runtime py version (code-change) | https://review.opendev.org/c/openstack/governance/+/881137 • Correct the old deprecated policies removal timeline for SLURP release (formal-vote) | https://review.opendev.org/c/openstack/governance/+/880238 • Deprecate TripleO (formal-vote) | https://review.opendev.org/c/openstack/governance/+/877132 • Add Contribution Opportunity: Ironic ARM support (formal-vote) | https://review.opendev.org/c/openstack/governance/+/879080 • New Open • Appoint Jerry Zhou as Sahara PTL (formal-vote) | https://review.opendev.org/c/openstack/governance/+/881186 • Add recommendations for release naming to package maintainers (formal-vote) | https://review.opendev.org/c/openstack/governance/+/881712 • Align release naming terminology (documentation-change) | https://review.opendev.org/c/openstack/governance/+/881706 • Abandoned • All Open • https://review.opendev.org/q/project:openstack/governance+status:open How to contact the TC ===================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send an email with the tag [tc] on the openstack-discuss mailing list. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 16:00 UTC 3. IRC: Ping us using the 'tc-members' keyword on the #openstack-tc IRC channel on OFTC.

1 0