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

[kolla-ansible][xena][vmware][neutron]
by Andrej Moravčík 09 May '23

09 May '23

Hello community, I am evaluating OpenStack release Xena with VMware vSphere deployed using Kolla-ansible. I would really appreciate if someone with similar environment can confirm my findings or share his/her experience. I did some research and choose Xena, because it is still maintained release and vmware-nsx latest stable branch is xena. I have built customised Docker images with additional Neutron plugins from opendev.org/x/vmware-nsx<http://opendev.org/x/vmware-nsx>, then I deployed single controller using all-in-one Ansible inventory with customised globals.yml according https://docs.openstack.org/kolla-ansible/xena/reference/compute/vmware-guid… 1) Neutron creates flat or VLAN type provider networks and add related Distributed Virtual Port Group (PG) to vSphere Distributed Switch (vDS or DVS). PG is automatically created with naming convention “<network name>”-“<network ID suffix>", which may not be suitable for same use cases, eg. PG was created by Cisco ACI ahead of Neutron and is part of ACI EPG. Question: is this PG naming convention fixed by design or is it configurable? If I want to use existing vDS PG with Neutron how this can be achieved? 2) Neutron metadata and DHCP agents are not accessible to Nova instance attached to DVS PG. I can deploy simple instance from Cirros image, but I cannot provision DHCP or fixed IP address. Provisioning via config drive doesn’t work either, I filled bug report to Nova … https://bugs.launchpad.net/nova/+bug/2018973 The documentation says … "For VMware DVS, the Neutron DHCP agent does not attaches to Open vSwitch inside VMware environment, but attach to the Open vSwitch bridge called br-dvs on the OpenStack side and replies to/receives DHCP packets through VLAN. Similar to what the DHCP agent does, Neutron metadata agent attaches to br-dvs bridge and works through VLAN.” Question: Is it expected that Kolla-ansible creates working configurations for Nova and Neutron, if all related options in globals.yml are set up? Or further adjustment is needed on Openstack or vCenter side? Thank you. — Andrej Moravcik ________________________________ Táto správa a jej prílohy sú dôverné. Prosím, narábajte s týmito informáciami ako s dôvernými a nezverejňujte, nekopírujte ani neposielajte tieto informácie bez predchádzajúceho súhlasu spoločnosti Aliter Technologies, a.s. Ak nie ste adresátom indikovaným v záhlaví tejto správy alebo želaný príjemca, upovedomte prosím spoločnosť Aliter Technologies, a.s. odpoveďou na tento e-mail a pôvodnú správu vymažte zo svojho systému. Aliter Technologies - registrovaná ochranná známka pre EU, USA This message and any attachments are confidential. Please treat the information as confidential, and do not disclose, copy or deliver this message to anyone without Aliter Technologies' approval. If you are not the addressee indicated in this message or an intended recipient please notify Aliter Technologies a.s. by return e-mail and delete the message from your system. Aliter Technologies - Registered in WIPO & U.S. Patent and Trademark Office

1 0

[neutron][Secure RBAC] New policies enabled by default
by Slawek Kaplonski 09 May '23

09 May '23

Hi, It's just a heads up that [1] was merged recently and Neutron is using new, secure RBAC policies by default now. If You would see any issues with that, please report bug(s) and let me know. [1] https://review.opendev.org/c/openstack/neutron/+/879827 -- Slawek Kaplonski Principal Software Engineer Red Hat

3 4

[neutron] Bug deputy May 01 - May 07
by Rodolfo Alonso Hernandez 09 May '23

09 May '23

Hello Neutrinos: This is the bug report from last week. High: * https://bugs.launchpad.net/neutron/+bug/2018727: [SRBAC] API policies for get_policy_*_rule are wrong. Assigned to Slawek. Medium: * https://bugs.launchpad.net/neutron/+bug/2018009: ML2 context not considering tags at network creation and update. Assigned to Miro. * https://bugs.launchpad.net/neutron/+bug/2018289: OVN trunk subport missing bounding information. Assigned to Arnau. * https://bugs.launchpad.net/neutron/+bug/2018529: [OVN] Virtual ports cannot be used as VM ports. Assigned to Rodolfo. * https://bugs.launchpad.net/neutron/+bug/2018585: [SRBAC]New policies change the behavior for check rule type. Assigned to Rodolfo. * https://bugs.launchpad.net/neutron/+bug/2018599: Disable config option use_random_fully does not work. *Not assigned*. * https://bugs.launchpad.net/neutron/+bug/2018737: neutron-dynamic-routing announces routes for disabled routers. Assigned to Felix. Low: * https://bugs.launchpad.net/neutron/+bug/2018474: Unnecessary agent resource version. *Not assigned*. Regards.

1 0

Stepping down as Ironic core
by Arne Wiebalck 09 May '23

09 May '23

Dear all, With a change in my role at work about a year ago, the time I have had available for upstream technical work has dropped significantly. I would therefore like to step down from my role as one of the Ironic cores. I am really grateful to have worked closely with this team of incredibly talented, helpful and kind people, and would like to use this occasion to thank them for all the support they have provided during these past years ... and of course for all the fun we had! Cheers, Arne -- Arne Wiebalck CERN IT

4 3

Using Veeam
by Robert Winbladh 09 May '23

09 May '23

Hi, Not sure I am in the right place but thought I would give it a go. We have a s3 service using IBM Spectrum Scale that builds on/uses Openstack Swift. The problem that we are having is that if the client/user is using Veeam the bucket gets locked. IBM explains that it has something to do with outstanding requests/timeouts. And the bucket gets locked, and the client/user/Veeam cannot access it any longer. This happens all the time. So my questions is: * What can I do about it? Anything that can be tuned in Swift? * IBM tells me to spread the load across multiple buckets - but Veeam does not have support for that (as far as I understand) * Any kind of tuning that needs to be done in Veeam (if anyone would know) * We have tried lowering "concurrent tasks" to 1, but still the bucket gets locked. [cid:image001.png@01D98259.E2C0B2C0] Robert Winbladh Seniorkonsult Technical Operations Manager Incident Manager Problem Manager Change Control Board member Asigra Certified Engineer IBM Spectrum Protect

1 0

[gate][tripleo] gate blocker
by Ananya Banerjee 09 May '23

09 May '23

Hello, All Centos 8 jobs which deploy standalone are failing at the moment. Please hold rechecks if you hit standalone deploy failure on Centos 8 jobs. We are working on the bug: https://bugs.launchpad.net/tripleo/+bug/2018588 Thanks, Ananya -- Ananya Banerjee, RHCSA, RHCE-OSP Software Engineer Red Hat EMEA <https://www.redhat.com/> anbanerj(a)redhat.com M: +491784949931 IM: frenzy_friday @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 1

[all][tc][release] Hold the Python3.8 dropping
by Ghanshyam Mann 09 May '23

09 May '23

Hello Everyone, As you know the gate is breaking due to Python3.8 drop[1][2], which we discussed in the TC channel and meeting[3]. TC is preparing the guidelines on not dropping Python3.8 in 2023.2 pti. Meanwhile, governance guidelines are prepared, this email is a heads-up to hold the dropping of Python3.8 from your project/repo. Do not bump the min py version in setup.cfg (do not bump version in python_requires ). @Release team, It will be helpful if you can check/hold the release of any project/lib dropping the Python3.8. [1] https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033450.h… [2] https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033454.h… [3] https://meetings.opendev.org/meetings/tc/2023/tc.2023-04-25-18.00.log.html#… -gmann

1 1

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

09 May '23

Hi all, This is a reminder that the next weekly Technical Committee meeting is to be held on Tuesday, May 9, 2023 at 1800 UTC on #openstack-tc on OFTC IRC Please propose items to the agenda 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

[Diversity] Diversity and Inclusion WG Meeting reminder
by Amy Marrich 08 May '23

08 May '23

This is a reminder that the Diversity and Inclusion WG will be meeting tomorrow at 14:00 UTC in the #openinfra-diversity channel on OFTC. We hope members of all OpenInfra projects join us as we review the Foundation-wide diversity survey questions for release at Summit. Thanks, Amy (spotz)

1 0

Fwd: (Openstack-Cinder) Error
by Adivya Singh 08 May '23

08 May '23

HI, Can you please guide me, There is this error which i am getting "fatal: [t1w_cinder_volumes_container-29d71abf]: FAILED! => {"msg": "The conditional check 'cinder_backend_lvm_inuse | bool' failed. The error was: error while evaluating conditional (cinder_backend_lvm_inuse | bool): {{ (cinder_backends|default(\"\")|to_json).find(\"cinder.volume.drivers.lvm.LVMVolumeDriver\") != -1 }}: {'lvm': {'iscsi_ip_address': '{{ 172.29.244.50 }}', 'volume_backend_name': 'LVM_iSCSI', 'volume_driver': 'cinder.volume.drivers.lvm.LVMVolumeDriver', 'volume_group': 'cloud'}}: float object has no element 244\n\nThe error appears to be in '/opt/openstack-ansible/playbooks/common-playbooks/cinder.yml': line 67, column 7, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n - name: Configure container (cinder-volume) when lvm is in-use\n ^ here\n"} I understand this error to some extent, but want to confirm with you if any body have seen similiar kind of error storage_hosts: s1w: ip: 172.29.236.50 container_vars: #cinder_storage_availability_zone: nova #cinder_default_availability_zone: nova cinder_backends: lvm: volume_backend_name: LVM_iSCSI volume_driver: cinder.volume.drivers.lvm.LVMDriver volume_group: cloud-volume iscsi_ip_address: "{{ cinder_storage_address }}" limit_container_types: cinder_volume Regards Adivya Singh

1 0