November 2023 - openstack-discuss

[swift][OpenStackSDK][keystone] Warnings about (my) swift endpoint URL by keystoneauth1 discovery
by Christian Rohmann 13 Nov '23

13 Nov '23

Hey openstack-discuss, we use Ceph RadosGW (Quincy release) to provide Swift as part of an OpenStack cloud. The endpoints are configured as such: > # openstack endpoint list > +----------------------------------+--------+--------------+----------------+---------+-----------+----------------------------------------------------------------------+ > | ID | Region | Service Name | Service > Type | Enabled | Interface | URL | > +----------------------------------+--------+--------------+----------------+---------+-----------+----------------------------------------------------------------------+ > | 1234567890 | region | swift | object-store | True | > public | > https://object-store.region.cloud.example.com/swift/v1/AUTH_%(tenant_id)s > | > | 2345678901 | region | swift | object-store | True | > internal | > https://object-store.region.cloud.example.com/swift/v1/AUTH_%(tenant_id)s > | > | 3456789012 | region | swift | object-store | True | > admin | > https://object-store.region.cloud.example.com/swift/v1/AUTH_%(tenant_id)s > | > so according to https://docs.ceph.com/en/latest/radosgw/keystone/#cross-project-tenant-acce…, if I am not mistaken. I can also use the openstack client to access containers: > # openstack container list > +---------------+ > | Name | > +---------------+ > | containera | > | containerb | > +---------------+ and there is no warnings or other apparent issues. But when using "project cleanup" via e.g. "openstack project cleanup --dry-run --project $PROJECT" I see multiple warnings like > Failed to contact the endpoint at > https://object-store.region.cloud.example.com/swift/v1/AUTH_f2bc4bd34567ddc… > for discovery. Fallback to using that endpoint as the base url. > but only mentioning the swift endpoint. Following the warning string this originates from the discovery method of keystoneauth1, see https://github.com/openstack/keystoneauth/blob/28048af9593740315df8d9027c3b…. Could anybody help me understand what is issue might be? Why does this warning not appear for every use of object storage / swift via openstackclient? Is there any way for me to "fix" this? Could this even be a bug? Thanks and with kind regards Christian

4 10

report an error
by 许伟祥 13 Nov '23

13 Nov '23

carry out iaas-pre-host.sh report an error Downloading packages: warning: /var/cache/yum/x86_64/7/iaas/packages/python-fixtures-3.0.0-2.el7.noarch.rpm: Header V4 RSA/SHA1 Signature, key ID 764429e6: NOKEY Public key for python-fixtures-3.0.0-2.el7.noarch.rpm is not installed Please Reboot or Reconnect the terminal How to fix it 从 Windows 版邮件<https://go.microsoft.com/fwlink/?LinkId=550986>发送

1 0

[nova] what nova filter scheduler are you using?
by Satish Patel 13 Nov '23

13 Nov '23

Folks, Just curious about what schedulers people using in their cloud for better distribution or management of VMs? And why? In entire my life I never touch that config also go with default but just curious what people doing and how?

1 0

[kolla-ansible] Galera DR across multiple datacenters
by Jahns, Jay 13 Nov '23

13 Nov '23

We currently run OpenStack on top of two datacenters, and we need to ensure we have datacenter redundancy for the database. With this, we would have 2-3 nodes in each DC running galera. Its been recommended by multiple people that we use an externally managed database server (or cluster) that has its own redundancies built around the two DC layout, and not have kolla manage that. Is there a way we can use kolla to deploy a galera cluster per DC, and use that to provide redundancy in the event that we lose one of the DCs? We were currently looking at proxysql but folks have recommended against it. Thanks.

4 4

[neutron] Bug Deputy Report November 06 - 12
by Lucas Alvares Gomes 13 Nov '23

13 Nov '23

Hi, This is the Neutron bug report from November 6th to 12th. Quieter week than usual. High: * https://bugs.launchpad.net/neutron/+bug/2042938 - "[OVN] Neutron Service Restart Disrupts Octavia OVN Load Balancer Floating IP" Unassigned * https://bugs.launchpad.net/neutron/+bug/2042941 - "neutron-{ovn,ovs}-tempest-with-sqlalchemy-master jobs not installing sqlalchemy/alembic from source" Unassigned * https://bugs.launchpad.net/neutron/+bug/2043141 - " neutron-lib unit tests need update for sqlalchemy 2.0" Assigned to: Brian Haley Medium: * https://bugs.launchpad.net/neutron/+bug/2042925 - "DNS Integration throws expection logs entries were warnings would be sufficient" Assigned to: Jayce Houtman * https://bugs.launchpad.net/neutron/+bug/2042947 - "[stable branches] nftables job inherits from openvswitch-iptables_hybrid master job" Assigned to: Yatin Cheers, Lucas

1 0

[neutron][ovs][kolla-ansible] Does neutron-openvswitch-agent required for sriov only compute node
by Satish Patel 13 Nov '23

13 Nov '23

Folks, I have an openstack cloud just running SRIOV workload, We don't have a requirement to run standard vms on compute nodes. Currently I have noticed neutron-sriov-agent and openvswitch-agent running on all compute nodes. Technically in my case I don't have any use of openvswitch-agent so I am planning to get rid of those agents to reduce pressure on the neutron-server. Just wanted to check with export if that is ok to not run ovs agent. I hope neutron-server won't freak out.

2 2

[release] Release countdown for week R-20, Nov 13-17
by Elõd Illés 10 Nov '23

10 Nov '23

Development Focus ----------------- The Caracal-1 milestone is next week, on November 16th, 2023! Project team plans for the 2024.1 Caracal cycle should now be solidified. General Information ------------------- Libraries need to be released at least once per milestone period. Next week, the release team will propose releases for any library which had changes but has not been otherwise released since the 2023.2 Bobcat release. PTL's or release liaisons, please watch for these and give a +1 to acknowledge them. If there is some reason to hold off on a release, let us know that as well, by posting a -1. If we do not hear anything at all by the end of the week, we will assume things are OK to proceed. NB: If one of your libraries is still releasing 0.x versions, start thinking about when it will be appropriate to do a 1.0 version. The version number does signal the state, real or perceived, of the library, so we strongly encourage going to a full major version once things are in a good and usable state. Upcoming Deadlines & Dates -------------------------- Caracal-1 milestone: November 16th, 2023 Előd Illés irc: elodilles @ #openstack-release

1 0

[OpenstackAnsible][cinder][newtron][nova]
by Tecstim 10 Nov '23

10 Nov '23

Hi, I am testing to deploy a multi-node environment. I tried openstack-helm because I thought it was cool to have containers and virtual machines in the same environment, but it is not very stable and seems difficult to operate. Now I am testing with openstack ansible. I just deployed AIO in a VM. I want to achieve this: Use a physical interface for networks with vlans, and the gateway and dhcp are managed outside openstack. Use NetApp NFS as storage for persistent data of lxd containers of the openstack-ansible, images for VMs and deplyment and use this https://docs.openstack.org/cinder/2023.2/configuration/block-storage/driver… to create volumes for vms.

1 0

[neutron] CI meeting for next week is cancelled
by Yatin Karel 10 Nov '23

10 Nov '23

Hello Neutron Team !! Next Tuesday we have a Public Holiday so I will not be available to chair the meeting. So, the next Neutron CI Meeting will be on 21st November, 2023. Thanks and Regards Yatin Karel

1 0

[all] Failing sqlalchemy-tips jobs should now be passing again
by Stephen Finucane 10 Nov '23

10 Nov '23

Just FYI, for projects that have sqlalchemy-tips jobs that have been failing recently, they should now be passing again. The root cause was neither sqlalchemy nor alembic but rather oslo.utils [1]. It was fixed in oslo.utils 6.3.0 which was released [2] roughly an hour ago. A recheck should be sufficient to clear errors and as these tips jobs only run on master there should be no issues with stable branches. A further point to add: while I appreciate that broken gates are never a good thing, I would be careful making these jobs non-voting. I've already seen a few instances where SQLAlchemy 2.0 support has regressed and I for one have no desire to re-herd cats as we push to get SQLAlchemy uncapped in the coming weeks. If this happens again then we can re-examine things, naturally. Cheers, Stephen [1] https://review.opendev.org/c/openstack/oslo.utils/+/900343 [2] https://review.opendev.org/c/openstack/releases/+/900382

2 2