- openstack-discuss - lists.openstack.org

[swift][s3api] put-object-acl in SLO objects
by Thiago De Moraes Teixeira 12 Mar '24

12 Mar '24

Hi, I've got this error when trying to put acl in objects that are a multipart upload with s3api client. *aws s3api put-object-acl --bucket ramac --key darwin --acl public-readAn error occurred (BadDigest) when calling the PutObjectAcl operation (reached max retries: 4): The Content-MD5 you specified did not match what we received.* And for objects greater than 5Gb the error is: *An error occurred (EntityTooLarge) when calling the PutObjectAcl operation: Your proposed upload exceeds the maximum allowed object size.* I noticed this is happening because s3 middleware did not recognize this object as an SLO, so when the request reaches the ServerSideCopyMiddleware, the request did not have the query param "multipart-manifest". I tried this swift patch, to solve this problem, identifying if the object is an SLO, on head object in acl_handlers.py class, and retrieving this information before request transformation to swift_request, adding the query param. While this patch resolves the immediate issue, I believe there's room for improvement. I welcome any suggestions or feedback on enhancing this patch further. Your insights would be greatly appreciated. https://paste.openstack.org/show/bd2nAHIHPtUtDNbWLorD/ Best regards -- _‘Esta mensagem é direcionada apenas para os endereços constantes no cabeçalho inicial. Se você não está listado nos endereços constantes no cabeçalho, pedimos-lhe que desconsidere completamente o conteúdo dessa mensagem e cuja cópia, encaminhamento e/ou execução das ações citadas estão imediatamente anuladas e proibidas’._ * **‘Apesar do Magazine Luiza tomar todas as precauções razoáveis para assegurar que nenhum vírus esteja presente nesse e-mail, a empresa não poderá aceitar a responsabilidade por quaisquer perdas ou danos causados por esse e-mail ou por seus anexos’.*

1 0

[swift][middleware][s3] Content-type of s3api versioning response
by m.victorello＠luizalabs.com 12 Mar '24

12 Mar '24

Hello, We are having some compatibility problems caused by the lack of content-type in this part: https://github.com/openstack/swift/blob/5e5fde12400fc76b9df43b3fcd13eb8a226… def GET(self, req): """ Handles GET Bucket versioning. """ sysmeta = req.get_container_info(self.app).get('sysmeta', {}) elem = Element('VersioningConfiguration') if sysmeta.get('versions-enabled'): SubElement(elem, 'Status').text = ( 'Enabled' if config_true_value(sysmeta['versions-enabled']) else 'Suspended') body = tostring(elem) return HTTPOk(body=body, content_type=None) Is there a reason for it?

1 0

[swift][s3][multipart] S3 multipart re-upload leaves orphan segments
by m.victorello＠luizalabs.com 12 Mar '24

12 Mar '24

Hello, I understand that this is a known issue for some time, but I dont know if it has been resolved. As far as I know stable/2023.2 still has this problem, is there any related work? We think there are two fronts: - Segments of incomplete multipart, forgotten by the user - Completed re-uploads We plan to fix those: - Using the object-expirer in a new middleware - Deploying workers to review all files, checking if they are still in use What are your thoughts?

1 0

[kolla-ansible] Building images from source
by wodel youchi 12 Mar '24

12 Mar '24

Hi, I am trying to build kolla's container images from source, especially octavia's images. I've read the kolla-build documentation, then I tried to follow along but I am having some problems. I am not a developper, my goal is to be able to push patches to kolla images if something goes wrong. For example now I am having a problem with octavia not being able to create an LB when using a self-signed certificate. I searched and I found a patch and I wanted to test-it. https://bugs.launchpad.net/kolla-ansible/+bug/2046382 https://launchpadlibrarian.net/706867161/octavia.patch Here are the steps I followed : - I am using podman - I've created a local registry - pyhton3.9 -m venv kollavnenv/2023.2 - source kollavnenv/2023.2/bin/activate - pip install kolla - pip install podman - I downloaded octavia source code from git 2023.2 version - https://github.com/openstack/octavia/tree/stable/2023.2 - I've prepared kolla_build.conf like this - [octavia] type = local location = /root/work/octavia - And I started the build like this - kolla-build --registry 192.168.2.35:4000 --push -b rocky --tag 2023.2-1 --engine podman --config-file ./kolla_build.conf octavia - Results - (2023.2) [root@r9localrepo work]# podman images REPOSITORY TAG IMAGE ID CREATED SIZE 192.168.2.35:4000/kolla/octavia-driver-agent 2023.2-1 1a6217ad71b4 22 minutes ago 1.31 GB 192.168.2.35:4000/kolla/octavia-api 2023.2-1 41ad8e1760a2 22 minutes ago 1.31 GB 192.168.2.35:4000/kolla/octavia-health-manager 2023.2-1 4922b7f0259f 22 minutes ago 1.28 GB 192.168.2.35:4000/kolla/octavia-housekeeping 2023.2-1 8b5a4785fc18 22 minutes ago 1.28 GB 192.168.2.35:4000/kolla/octavia-worker 2023.2-1 46107a14e78d 22 minutes ago 1.28 GB 192.168.2.35:4000/kolla/octavia-base 2023.2-1 23963c04eda7 22 minutes ago 1.28 GB 192.168.2.35:4000/kolla/openstack-base 2023.2-1 add627cfde2f 25 minutes ago 1.14 GB 192.168.2.35:4000/kolla/base 2023.2-1 a8299a02411a 29 minutes ago 580 MB <none> <none> 0421c38fd25c 8 hours ago 1.14 GB docker.io/library/registry 2 a8781fe3b7a2 6 weeks ago 26 MB quay.io/rockylinux/rockylinux 9 da830f5e2510 3 months ago 181 MB - The problem : - When exploring the octavia-api images for example (podman save),* and verifying the modified file I didn't find the patched-code* It seems that the build process is not using the local code? What am I missing? I think that my kolla_build.conf is wrong or not complete ... any ideas? Regards.

1 2

[kolla-ansible][2023.2] Cloudkitty support for Openseach?
by wodel youchi 11 Mar '24

11 Mar '24

Hi, Does Cloudkitty now support Opensearch as a storage backend in kolla? Regards.

2 1

[oslo][release][requirements] RFE for tooz and taskflow
by Takashi Kajinami 11 Mar '24

11 Mar '24

Hello, During this cycle we updated the redis support implementations to support authentication and SSL for redis sentinel, following the new implementation in oslo.cache. However later it turned out this change breaks kolla because it has been using redis sentinel without authentication while it enables authentication in redis[1]. I've submitted the changes[2] to restore the old behavior (not to enable AUTH or SSL for sentinel even when one is enabled in redis). Once these are merged in master then I'll propose backports to stable/2024.1 and propose new stable/2024.1 release. I'd like to request approval about the release and also bumping tooz and taksflow version in stable/2024.1 requirements to unblock kolla and any other deployments using the partial authentication for redis sentinel. Thank you, Takashi [1] https://bugs.launchpad.net/python-tooz/+bug/2056656 [2] https://review.opendev.org/c/openstack/taskflow/+/912346 https://review.opendev.org/c/openstack/tooz/+/912344/ -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

3 3

[neutron] Bug deputy report Mar 4th to 10th
by Oleg Bondarev 11 Mar '24

11 Mar '24

Hello Neutron Team, Bug report for the week of March 4 is below: High: - https://bugs.launchpad.net/neutron/+bug/2055876 - [ovn-octavia-provider] OVN LB health checks for IPv6 not working - in progress: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/911413 - assigned to froyoredhat Medium: - https://bugs.launchpad.net/neutron/+bug/2056199 - ``DvrDriver`` and ``OvnDriver`` incorrectly define distributed flag - fix released: https://review.opendev.org/c/openstack/neutron/+/911151 - fixed by rodolfo-alonso-hernandez - https://bugs.launchpad.net/neutron/+bug/2056276 - unmaintained/yoga periodic jobs broken - confirmed - assigned to yatinkarel - https://bugs.launchpad.net/neutron/+bug/2056366 - Neutron ml2/ovn does not exit when killed with SIGTERM - in progress: https://review.opendev.org/c/openstack/neutron/+/911625 - assigned to otherwiseguy - https://bugs.launchpad.net/neutron/+bug/2056537 - [ovn-octavia-provider] gateway chassis not filled on LogicalRouterPort event - in progress - assigned to froyoredhat - https://bugs.launchpad.net/neutron/+bug/2056558 - ``OVNL3RouterPlugin._port_update`` can be called before the LRP is created in the OVN DB - in progress: https://review.opendev.org/c/openstack/neutron/+/912349 - assigned to rodolfo-alonso-hernande Low: - https://bugs.launchpad.net/neutron/+bug/2055886 - [FT] Check port binding object in "test_virtual_port_host_update_upon_failover" - fix released: https://review.opendev.org/c/openstack/neutron/+/910941 - fixed by rodolfo-alonso-hernandez Thanks, Oleg

1 0

[kolla-ansible][2023.2] Manila cephFS NFS ganesha need some clarifications
by wodel youchi 10 Mar '24

10 Mar '24

Hi, I am trying to configure Manila with cephsfs NFS as backend. My first problem is with installing and configuring nfs ganesha : - Do I have to deploy nfs ganesha from ceph? - What about the /etc/ganesha/ganesha.conf config file? Could someone give me some steps to follow... Regards.

3 11

deploy error
by Parsa Aminian 09 Mar '24

09 Mar '24

hello I want to add new compute to my kolla ansible but i gave this error : TASK [nova-cell : Get a list of existing cells] ****************************************************************************************************************** fatal: [R6SC15.cpaas.ir -> control01]: FAILED! => {"msg": "The conditional check 'existing_cells_list.rc != 0' failed. The error was: error while evaluating conditional (existing_cells_list.rc != 0): 'dict object' has no attribute 'rc'"} can anyone help me whats the problem ?

1 0

[neutron][horizon] disable permission to release floating ip for non-admin users
by Satish Patel 09 Mar '24

09 Mar '24

Folks, I want to disable permission or the horizon button or whatever best way to not allow end users to "Release floating IP" because I want them to stick with assigned IP and not releasing them because of some regulatory process. Not sure what is the best way to have this level of control. I found neutron policy delete_floatingip: but is this the correct way to implement this policy? OR Does Horizon have some level of ACL to remove buttons or disable it? Looking for advice or clues. Thanks!

3 2

[nova][telemetry][watcher][requirements] RFE requests for client libraries
by Elõd Illés 09 Mar '24

09 Mar '24

Hi Requirements team, During today's Release Management weekly meeting we discussed 3 extra client library releases that we would like to ask for Requirements Freeze Exception for: - python-aodhclient [1] 3.5.1 - python-novaclient [2] 18.6.0 - python-watcherclient [3] 4.4.0 contents: [1] python-aodhclient (from comment on the release patch): "Indeed, c10ea92f050b9c53d398eb4570feab2cc442bed7<https://review.opendev.org/#/q/c10ea92f050b9c53d398eb4570feab2cc442bed7> from Dr. Harbott indicated install issues due to the lingering oslo.db cap, 80c9d8608a2f4d04999937800cc30bbf9fc482e0<https://review.opendev.org/#/q/80c9d8608a2f4d04999937800cc30bbf9fc482e0> flagged that there was issue on release notes building that we had missed. And as we had to get those in we also improved testing (not affecting the lib) 31fec512e3ba3c596866c234eefc7a33506c8ef7<https://review.opendev.org/#/q/31fec512e3ba3c596866c234eefc7a33506c8ef7>." c10ea92 Remove oslo.db test cap 31fec51 Add functional tests for prometheus type alarms 80c9d86 Fix releasenotes build of yoga moved to unmaintained [2] python-novaclient: 533d5df5 Bump microversion to 2.96 [3] python-watcherclient 9aace80 Update python classifier in setup.cfg 63d305c Remove untested lower-constraints.txt Thanks, Előd Illés irc: elodilles @ #openstack-release

1 0

[kolla][ptg] Reminder about 2024.2 PTG dates and call for ideas
by Michał Nasiadka 09 Mar '24

09 Mar '24

Hello Koalas, I’ve set up a Dalmatian/2024.2 PTG etherpad - https://etherpad.opendev.org/p/kolla-dalmatian-ptg If you have any ideas for improvements in Kolla/Kolla-Ansible/ansible-collection-kolla or Kayobe - feel free to add that somewhere under line 89. The PTGbot registered meeting slots are: 8-12 April 2024: • Monday - 13.00 - 17.00 UTC (general, Kolla and Kolla-Ansible) • Tuesday - 13.00 - 17.00 UTC (Kolla-Ansible) • Thursday - 13.00 - 15.00 UTC (Kayobe) See you then! Michal

1 0

[heat][monasca][sahara][senlin] Features dependent on inactive projects
by Takashi Kajinami 09 Mar '24

09 Mar '24

Hello, As you know, some of the OpenStack projects were marked inactive during this cycle. There are still on-going discussions but from my view these are very likely excluded from the upcoming 2024.1 release and it's unclear yet if any of these projects will be kept. Currently heat provides features integrated with some of the inactive projects (Monasca, Sahara and Senlin), and we have to decide how we deal with these features[1]. The main concern is that we can't maintain the features for the inactive projects, and IMO we should retire these features if these inactive projects are abandoned or are no longer maintained in the consistent way with the other active projects. Based on the current situation, I'd propose the following steps for upcoming cycles. - Deprecate the features dependent on inactive projects in 2023.2 release - Note that we have to remove these features directly during this cycle in case any problems related to these project block the upcoming heat release. - Remove these features in 2024.1 release unless we are sure that these projects are kept maintained as active projects in the openstack namespace, with following the global release cycle. Please let me know if you have any concern about the proposed plan. If I hear no objections then I'll propose patches for deprecation. Thank you, Takashi Kajinami irc: tkajinam [1] I've submitted a series of patches to remove these features and these would give a clear view about the features affected. https://review.opendev.org/q/topic:%22inactive-project-removal%22+project:o…

3 6

[release] Release countdown for week R-3, Mar 11-15
by Elõd Illés 09 Mar '24

09 Mar '24

Development Focus ----------------- The Release Candidate (RC) deadline is next Thursday, March 14th, 2024. Work should be focused on fixing any release-critical bugs. General Information ------------------- All deliverables released under a cycle-with-rc model should have a first release candidate by the end of the week, from which a stable/2024.1 branch will be cut. This branch will track the 2024.1 Caracal release. Once stable/2024.1 has been created, the master branch will be ready to switch to 2024.2 Dalmatian development. While the master branch will no longer be feature-frozen, please prioritize any work necessary for completing 2024.1 Caracal plans. Release-critical bugfixes will need to be merged in the master branch first, then backported to the stable/2024.1 branch before a new release candidate can be proposed. Actions ------- Early in the week, the release team will be proposing RC1 patches for all cycle-with-rc projects, using the latest commit from the master branch. If your team is ready to go for cutting RC1, please let us know by leaving a +1 on these patches. If there are still a few more patches needed before RC1, you can -1 the patch and update it later in the week with the new commit hash you would like to use. Remember, stable/2024.1 branches will be created with this, so you will want to make sure you have what you need included to avoid needing to backport changes from the master branch (which will technically then be 2024.2 Dalmatian) to this stable branch for any additional RCs before the final release. The release team will also be proposing releases for any deliverable following a cycle-with-intermediary model that has not produced any 2024.1 Caracal release so far. Finally, now is a good time to finalize release highlights. Release highlights help shape the messaging around the release and make sure that your work is properly represented. Upcoming Deadlines & Dates -------------------------- RC1 deadline: March 14th, 2024 (R-3 week) Final RC deadline: March 28th, 2024 (R-1 week) Final 2024.1 Caracal release: April 3rd, 2024 Dalmatian PTG: April 8-12, 2024 Előd Illés irc: elodilles @ #openstack-release

1 0

[tacker][FFE] Mgmt driver sample for deploying Cilium
by Yasufumi Ogawa 08 Mar '24

08 Mar '24

Hi, I'd like to request FFE in this cycle for the update for introducing a sample of management driver for deploying Cilium with K8s VIM as I proposed at the previous IRC meeting. Please let me know if you have any comment although there was nothing opposite then. https://review.opendev.org/c/openstack/tacker/+/911639 Thanks, Yasufumi

1 0

[neutron] Is the vxlan(overlay) network a Provider network or a self-service network
by 韩光宇 08 Mar '24

08 Mar '24

Hi, In neutron install doc[1], I got the concept of Provider network and Self-service network. And I got that: - Provider network bridges virtual networks to physical networks and relies on physical network infrastructure for layer-3 (routing) services - Self-service network routes virtual networks to physical networks using Network Address Translation (NAT) So I understand: Flat/Vlan network are Provide network and vxlan/gre network are Self-service network. But, in openstack cmd, I found that all network types are classified as provider network types. ``` openstack network create --help ... --provider-network-type <provider-network-type> The physical mechanism by which the virtual network is implemented. For example: flat, geneve, gre, local, vlan, vxlan. ``` I am confused, why do vxlan and gre appear in the **provider network type**? According to the installation doc[1], overlay networks should not all be self-service networks Or is the provider network in cmd not the same as the provider network in the installation document, the provider network here is only different from the tenant network? Can someone help me distinguish between these concepts, or suggest questions that I can read: why vxlan is provider network I will appreciate for any help. Best wishes, Han Guangyu [1] https://docs.openstack.org/neutron/latest/install/controller-install-obs.ht…

2 1

[magnum] Speaker Requested for OpenInfra Day Türkiye
by Allison Price 08 Mar '24

08 Mar '24

Hi Magnum community, The organizers of OpenInfra Day Türkiye have reached out mentioning that Magnum has garnered great interest in Türkiye and would like to offer a keynote to any contributor who can provide an overview, new features and the roadmap of the project. The event is May 20 at Boğaziçi University in Istanbul. More information is available here: https://openinfraturkiye.org.tr/ Please let me know if you have any questions. If you represent another OpenStack project and are interested in providing an update, please feel free to reach out. Cheers, Allison Allison Price VP of Marketing & Community OpenInfra Foundation <https://openinfra.dev/> p: +1-214-686-6821

1 0

[cinder][glance][nova][telemetry][monasca][oslo][vmware] Can we deprecate(and remove) VMWare support ?
by Takashi Kajinami 07 Mar '24

07 Mar '24

Hi all, As you might know, some of the OpenStack projects currently support usage of VMWare component. However recently the VMware virt driver in nova was marked experimental in 2023.2 release [1] and it has been discussed that the driver will be removed in 2023.2 release[2], after deprecation is backported to 2023.1. (Please someone from nova team correct me if I'm wrong) So my current question is; Does it make sense to deprecate all of the features to support VMWare component ? My understanding is that these features were added to be used along with VMWare virt driver in nova, but once the virt driver is removed this use case is voided. I'll list up the features within the discussion scope below. nova: VMWare virt driver (this is already experimental by [1]) cinder: VMware Storage Driver (vmdk) glance: VMWare Datastore (I proposed deprecating this in [3][4]) ceilometer: VMWare virt driver (this was deprecated by [5]) os-brick: VmdkConnector monasca-agent: vcenter collector (*1) oslo.vmware: the whole project NOTE: These features are found based on dependency on oslo.vmware but there can be a few not listed here. Outside of OpenStack's governance, there are two projects dependent on oslo.vmware, networking-vsphere and vmware-nsx but both of these look inactive. Because of SLURP, we have to complete deprecation during in 2024.1 release so that we can drop the feature right after 2024.1. If we fail then we have to maintain these features until 2025.1 (the features already deprecated can be removed earlier, though). So I'd like to get feedback and decision before deadline for 2024.1 Thank you, Takashi (*1) Monasca is now inactive so I doubt anyone would work on this topic before it is retired. [1] https://review.opendev.org/c/openstack/nova/+/863911 [2] https://review.opendev.org/c/openstack/nova/+/897017 [3] https://review.opendev.org/c/openstack/glance_store/+/893696 [4] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [5] https://review.opendev.org/c/openstack/ceilometer/+/894540

6 21

[oslo][requirements] RFE for new tooz release
by Takashi Kajinami 07 Mar '24

07 Mar '24

Hello, We have identified a regression[1] in tooz 6.0.0, which is the latest version in 2024.1 u-c. I have identified its cause and prepared the bug fix[2] and the follow up change to fix CI coverage[3]. I'll create 6.0.1 release once both of these two land. I'm sending this email to get early approval to bump tooz version in caracal requirements. The bug is at least known to be blocking kolla, but would affect any deployment which is using redis sentinel as tooz backend. Thank you, Takashi [1] https://bugs.launchpad.net/python-tooz/+bug/2056429 [2] https://review.opendev.org/c/openstack/tooz/+/911648 [3] https://review.opendev.org/c/openstack/tooz/+/911682 [4] https://review.opendev.org/c/openstack/releases/+/911711 -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

1 0

RE: openstack-discuss Digest, Vol 65, Issue 27
by Asma Naz Shariq 07 Mar '24

07 Mar '24

Hello team, I am intending to deploy Openstack AIO (zed) release, directly at ubuntu 20.04 BareMetal server. The issue I am facing as below: RUNNING HANDLER [MariaDB : Wait for MariaDB service port liveness] Failed - Retrying : [Localhost]: Wait for MariaDB service port liveness ( 10 retries left) Fatal: [localhost]: FAILED! => {"attempts": 10, "changed": false, "elapsed": 60, "msg": "Timeout when waiting for search string MariaDB in ip address:3306"} I need assistance to resolve this issue, -----Original Message----- From: openstack-discuss-request(a)lists.openstack.org <openstack-discuss-request(a)lists.openstack.org> Sent: Thursday, March 7, 2024 5:12 AM To: openstack-discuss(a)lists.openstack.org Subject: openstack-discuss Digest, Vol 65, Issue 27 Send openstack-discuss mailing list submissions to openstack-discuss(a)lists.openstack.org To subscribe or unsubscribe via email, send a message with subject or body 'help' to openstack-discuss-request(a)lists.openstack.org You can reach the person managing the list at openstack-discuss-owner(a)lists.openstack.org When replying, please edit your Subject line so it is more specific than "Re: Contents of openstack-discuss digest..." Today's Topics: 1. [ansible][aio][glance] Cannot create image, TypeError: Response is undefined (Tang Chai Keong) 2. Devstack (BEDDA Fadhel) 3. Re: [kolla-ansible][2023.2] Manila cephFS NFS ganesha need some clarifications (Goutham Pacha Ravi) 4. Re: Devstack (Alvaro Soto) ---------------------------------------------------------------------- Message: 1 Date: Thu, 7 Mar 2024 06:40:20 +0800 From: Tang Chai Keong <tchaikeong(a)gmail.com> Subject: [ansible][aio][glance] Cannot create image, TypeError: Response is undefined To: openstack-discuss(a)lists.openstack.org Message-ID: <CADnLa1bZ7AAy+FsxggR3up+3XhooNCuJZteTzj3vijXnL_sG9w(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" I deployed openstack-ansible AIO and is trying to create a new image but is encountering "TypeError: Response is undefined" and "Error: Unable to create the image". The image creation task is just stuck in the "queued" mode forever after that. I also do not see any of the service logs in the lxc containers under /var/logs/ folder. Appreciate any advice on how I can troubleshoot this. Thank you. Regards, Ben ------------------------------ Message: 2 Date: Wed, 6 Mar 2024 23:48:35 +0100 From: BEDDA Fadhel <fadhel.bedda(a)gmail.com> Subject: Devstack To: openstack-discuss(a)lists.openstack.org Message-ID: <CAE1GhS7rhRi_qZt_vvwViSaHXoFUzkse5V+=hof+NcR7s-cnYg(a)mail.gmail.com> Content-Type: multipart/alternative; boundary="000000000000e690e2061305c23f" Good morning, as part of a test lab, I installed DevStack on Ubuntu. and I want to start linux and windows instances. I created the images and instances. but none that starts. on the console I have: boot from disk and nothing happens Thank you for your help

1 0

Openstack installation on Virtual Machines: External network issue
by KK CHN 07 Mar '24

07 Mar '24

Hi OpenStackers, I am just beginning with openstack. I am trying kolla-ansible all-in-on installation on a Virtual Machine(on an Ubuntu 22.04 VM hosted by ESXi Server). Deployment success, able to create VMs and networks. Base VM Ubuntu-22.04 ( kolla-ansible all-in-one installation) Network details. [image: image.png] From the base VM, I am able to ping tenant VMs through network namespace from base VM . But from a tenant VM, I can't ping to 10.176.17.61( the base VM address) [image: image.png] I am unable to ping to my base VM IP from my tenant VM, whether my deployment is wrong ? How to check? also how to test internet connectivity from Tenant VM ( all VMs are default cirros VMs). [image: image.png] *Note: Why ovs-vsctl not found on base VM ? Do I need to explicitly install, apt get install openvswitch-switch ?* Kolla-ansible won't install it by default?? (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ ovs-vsctl show Command 'ovs-vsctl' not found, but can be installed with: sudo apt install openvswitch-switch (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ If any more details are required other than the following, I can provide. # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* auto lo iface lo inet loopback auto ens224 iface ens224 inet static address 10.220.0.51 netmask 255.255.255.0 gateway 10.220.0.1 dns-nameserver 0.0.0.0 auto ens160 iface ens160 inet static address 10.176.17.61 netmask 255.255.254.0 gateway 10.176.16.1 dns-nameserver 10.176.0.11 auto ens192 iface ens192 inet manual up ip link set dev ens192 up down ip link set dev ens192 down globals.yml (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ grep ^[^#] /etc/kolla/globals.yml --- workaround_ansible_issue_8743: yes config_strategy: "COPY_ALWAYS" kolla_base_distro: "ubuntu" openstack_release: "2023.1" kolla_internal_vip_address: "10.220.0.24" kolla_external_vip_address: "{{ kolla_internal_vip_address }}" kolla_container_engine: docker network_interface: "ens224" neutron_external_interface: "ens192" neutron_plugin_agent: "openvswitch" nova_compute_virt_type: "qemu" (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ BUT why brctl shows nothing enabled state as "no" (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ brctl show bridge name bridge id STP enabled interfaces qbr1f4a7fde-87 8000.525b9c0d0f71 no qvb1f4a7fde-87 tap1f4a7fde-87 qbr6800c928-bb 8000.82aaa756a3cc no qvb6800c928-bb tap6800c928-bb qbr83937c49-06 8000.16da67140926 no qvb83937c49-06 tap83937c49-06 qbr9304eb11-59 8000.fa7e2e6ca3e3 no qvb9304eb11-59 tap9304eb11-59 (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ +--------------------------------------+-----------------------------------------------+ (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ nova list nova CLI is deprecated and will be a removed in a future release +--------------------------------------+--------------+--------+------------+-------------+--------------------+ | ID | Name | Status | Task State | Power State | Networks | +--------------------------------------+--------------+--------+------------+-------------+--------------------+ | d402d554-a56e-4cc6-af06-694ea913c939 | greenboxes-1 | ACTIVE | - | Running | GREEN=10.10.10.177 | | a69e4c16-e02f-4b5c-b6b1-e929ec309495 | greenboxes-2 | ACTIVE | - | Running | GREEN=10.10.10.6 | | 6b4d4b5d-2cc6-463d-89d9-5180f16ec3e3 | redboxes-1 | ACTIVE | - | Running | RED=20.20.20.104 | | a29576e8-46ca-4311-93ad-f2ca540a9880 | redboxes-2 | ACTIVE | - | Running | RED=20.20.20.121 | +--------------------------------------+--------------+--------+------------+-------------+--------------------+ (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ neutron port-list -c id -c fixed_ips neutron CLI is deprecated and will be removed in the Z cycle. Use openstack CLI instead. +--------------------------------------+------------------------------------------------------ (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ neutron port-list -c id -c fixed_ips neutron CLI is deprecated and will be removed in the Z cycle. Use openstack CLI instead. +--------------------------------------+-------------------------------------------------------------------------------------+ | id | fixed_ips | +--------------------------------------+-------------------------------------------------------------------------------------+ | 02344545-8003-4f0c-bc58-b0812d400939 | {"subnet_id": "754de697-6cdb-4277-9d87-0b3fbabb9744", "ip_address": "20.20.20.2"} | | 1f4a7fde-87dc-4547-9ea2-cd0084cd68ff | {"subnet_id": "754de697-6cdb-4277-9d87-0b3fbabb9744", "ip_address": "20.20.20.104"} | | 6800c928-bbac-4c9f-9db0-5d6126a4f46f | {"subnet_id": "b3f4fb8c-a926-4fc0-a9b5-28d7c2ac649b", "ip_address": "10.10.10.177"} | | 83937c49-06a0-4fc6-b34c-76a627989fb2 | {"subnet_id": "b3f4fb8c-a926-4fc0-a9b5-28d7c2ac649b", "ip_address": "10.10.10.6"} | | 9304eb11-5970-4197-b589-2c04a158fad9 | {"subnet_id": "754de697-6cdb-4277-9d87-0b3fbabb9744", "ip_address": "20.20.20.121"} | | 9fcaebab-36a7-401e-97dc-06755b20e817 | {"subnet_id": "b3f4fb8c-a926-4fc0-a9b5-28d7c2ac649b", "ip_address": "10.10.10.2"} | +--------------------------------------+------------------------------------------------------------------------------- (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ openstack network list +--------------------------------------+-------+--------------------------------------+ | ID | Name | Subnets | +--------------------------------------+-------+--------------------------------------+ | 20374e5f-6639-4e90-8241-2c3ddec72684 | RED | 754de697-6cdb-4277-9d87-0b3fbabb9744 | | 35fe9fe1-05d1-42ea-a3cb-e8f7588ca571 | EXT1 | c35e54e2-4ff5-4775-ab4e-21b24074745b | | 515ec17a-16fa-4be2-ae5f-afc4af388c3d | GREEN | b3f4fb8c-a926-4fc0-a9b5-28d7c2ac649b | +--------------------------------------+-------+--------------------------------------+ (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ Thank you, Krish

1 0

[tacker] FFE request for tacker-horizon's patch and obsoleting Legacy API patch
by Ayumu Ueha (Fujitsu) 07 Mar '24

07 Mar '24

Hi tacker team, As we talked about in today's regular IRC, I would like to request FFE in the 2024.1 Caracal cycle for the following patch: 908983: Support NFV Orchestration API v2.0 | https://review.opendev.org/c/openstack/tacker-horizon/+/908983 910104: Obsolete Legacy APIs excluding VIM feature | https://review.opendev.org/c/openstack/tacker/+/910104 Reasons: [Support NFV Orchestration API v2.0] The tacker-horizon patch provides GUI of NFV Orchestration API V2.0 operations that are very useful to users and developers. This is a major feature addition to tacker-horizon which has not been maintained for a long time, but change is green and now usable. [Obsolete Legacy APIs excluding VIM feature] I could not check Zuul CI pass due to some gate issue that occurred before the Feature freeze and my work was stopped to resolve the issue. The removal of the Legacy API has been declared since the 2023.1 Antelope release, so I would like to merge it if possible in this 2024.1 Caracal cycle. Regards, Ayumu

2 1

[tacker] FFE request for RBAC change for project personas
by Ghanshyam Mann 07 Mar '24

07 Mar '24

Hi Team, I would like to request the Feature freeze exception for the Tacker RBAC work for project personas. - https://review.opendev.org/q/topic:%22bp/implement-project-personas%22+stat… Reason: All the changes are green, including the testing framework/tests for existing RBAC. Finishing the RBAC works for project personas in this cycle will help enable the new defaults and remove the old ones in coming cycles. We are already behind the schedule for RBAC community-wide goal -gmann

2 1

[kolla][cinder][nfs] NFS backend error for volumes
by Satish Patel 07 Mar '24

07 Mar '24

Folks, I am configuring NFS for the cinder backend but somehow it doesn't go well. I am running kolla-ansible with the 2023.1 release. cinder.conf [DEFAULT] enabled_backends = volumes-ssd,volumes-nfs [volumes-nfs] volume_driver = cinder.volume.drivers.nfs.NfsDriver volume_backend_name = volumes-nfs nfs_shares_config = /etc/cinder/nfs_shares nfs_snapshot_support = True nas_secure_file_permissions = False nas_secure_file_operations = False Inside the cinder_volume docker container I can see it mounts NFS automatically and directory permissions is also cinder:cinder also I am able to write on NFS share also so it's not a permission issue also. $ docker exec -it cinder_volume mount | grep nfs 192.168.18.245:/volume1/NFS on /var/lib/cinder/mnt/1ec32c051aa5520a1ff679ce879da332 type nfs (rw,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.18.245,mountvers=3,mountport=892,mountproto=udp,local_lock=none,addr=192.168.18.245) But service is still showing down. | cinder-volume | os-ctrl2@volumes-nfs | nova | enabled | down | 2024-02-28T04:13:11.000000 | In logs I am seeing these 3 lines but then no activity in logs even after restarting the container so that is very strange. 2024-02-28 04:13:12.995 153 ERROR os_brick.remotefs.remotefs [None req-6bcb8eab-6aa6-4c36-9a7a-ed673c39dcbc - - - - - -] Failed to mount 192.168.18.245:/volume1/NFS, reason: mount.nfs: Protocol not supported : oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command. 2024-02-28 04:13:13.501 153 WARNING cinder.volume.drivers.nfs [None req-6bcb8eab-6aa6-4c36-9a7a-ed673c39dcbc - - - - - -] The NAS file permissions mode will be 666 (allowing other/world read & write access). This is considered an insecure NAS environment. Please see https://docs.openstack.org/cinder/latest/admin/blockstorage-nfs-backend.html for information on a secure NFS configuration. 2024-02-28 04:13:13.501 153 WARNING cinder.volume.drivers.nfs [None req-6bcb8eab-6aa6-4c36-9a7a-ed673c39dcbc - - - - - -] The NAS file operations will be run as root: allowing root level access at the storage backend. This is considered an insecure NAS environment. Please see https://docs.openstack.org/cinder/latest/admin/blockstorage-nfs-backend.html for information on a secure NAS configuration. Has anyone configured NFS and noticed any behavior?

3 12

[all][elections][tc] TC Election Voting Kickoff
by Tony Breeds 07 Mar '24

07 Mar '24

The poll for the TC Election is now open and will remain open until Mar 20, 2024 23:45 UTC. We are selecting 5 TC members, please rank all candidates in your order of preference. You are eligible to vote if you are a Foundation individual member[1] that also has committed to one of the official project teams' deliverable repositories[2] over the Mar 03, 2023 00:00 UTC - Feb 28, 2024 00:00 UTC timeframe (2023.2 to 2024.1) or if you are one of the extra-acs.[3] If you are eligible to vote in an election, you should find your email with a link to the Condorcet Internet Voting Service (CIVS) page to cast your vote in the inbox of your Gerrit preferred email[4]. What to do if you don't see the email and have a commit in at least one of the official deliverables[2]: * due to a new CIVS policy, to get the email from poll supervisors, you must opt in to email communication opt in with your Gerrit email address at: https://civs1.civs.us/cgi-bin/opt_in.pl * eligible voters who opt in to email communication late can see a pending poll invitation and vote until Mar 20, 2024 23:45 UTC. * check the trash or spam folder of your Gerrit Preferred Email address[4], in case it went into trash or spam * wait a bit and check again, in case your email server is a bit slow * find the sha of at least one commit from an official deliverable repo[2] and email the election officials[1]. If we can confirm that you are entitled to vote, we will add you to the voters list and you will be emailed a ballot. Our democratic process is important to the health of OpenStack, please exercise your right to vote. Candidate statements/platforms can be found linked to Candidate names[6]. Happy voting! Thank you, [1] https://www.openstack.org/community/members/ [2] https://opendev.org/openstack/governance/src/tag/0.16.0/reference/projects.… [3] Look for the extra-acs element in [2] [4] Sign into review.openstack.org: Go to Settings > Contact Information. Look at the email listed as your preferred email. That is where the ballot has been sent. [5] https://governance.openstack.org/election/#election-officials [6] https://governance.openstack.org/election/#tc-candidates Yours Tony.

1 0