November 2020 - openstack-discuss

RE: Fwd: freezer
by Cyrille CARTIER 16 Nov '20

16 Nov '20

Hi Ali, Last week I’ve got a response in StoryBoard, thanks to Carl : « The bug is fixed in victoria, please update new version. Thanks. » My Colleague confirm that Ussuri version still have the same problem. Is it good for you with Stein ? We're going to test the Victoria version soon, I'll get back to you if it works. Thanks, Cyrille De : Ali Ebrahimpour [mailto:ali74.ebrahimpour@gmail.com] Envoyé : samedi 7 novembre 2020 08:06 À : Cyrille CARTIER <Cyrille.CARTIER(a)antemeta.fr>; smooney(a)redhat.com Objet : Re: Fwd: freezer hi Cyrille,sean thank you for attention I have this problem by requesting a backup with nova i used the ussuri version and two days ago got pull the version by opendev and had not changed and I want to try to install the Stein version with python2. Maybe it works correctly Did you find a solution for versions with python3? On Fri, Nov 6, 2020 at 12:08 PM Cyrille CARTIER <Cyrille.CARTIER(a)antemeta.fr<mailto:Cyrille.CARTIER@antemeta.fr>> wrote: Hi Ali, Which openstack version do you use ? I have a similar problem on my Train plateform (deployed by kolla-ansible), using freezer-scheduler. There are many commit for py3 correction for Ussuri and Victoria branch, in Git repository [1]. Did you try these version? I have already post the problem on StoryBoard [2] and Launchpad [3]. -----Message d'origine----- Objet : Re: Fwd: freezer On Thu, 2020-11-05 at 12:42 +0330, Ali Ebrahimpour wrote: > hi i recently install the freezer api and i have problem with using it > if run this command: > freezer-agent --debug --action backup --nova-inst-id > a143d11d-fa27-4716-9795-e03b4e601df4 --storage local --container > /tmp/ali --backup-name test --mode nova --engine nova > --no-incremental true > --log-file a.log --consistency-check > > and freezer api doesn't work current and error with: > Engine error: a bytes-like object is required, not 'str' > Engine error: Forced stop that looks like a python 3 issue im not sure how active it still is but it looks like its an issue between text string and byte strings > > Adn attach the log > please help me ! > > thank you for attention [1]: https://opendev.org/openstack/freezer [2]: https://storyboard.openstack.org/#!/project/openstack/freezer [3]: https://bugs.launchpad.net/freezer/+bug/1901179 Cyrille

1 0

Victoria RDO Release Announcement
by Amy Marrich 16 Nov '20

16 Nov '20

If you're having trouble with the formatting, this release announcement is available online https://blogs.rdoproject.org/2020/11/rdo-victoria-released/ --- RDO Victoria Released The RDO community is pleased to announce the general availability of the RDO build for OpenStack Victoria for RPM-based distributions, CentOS Linux and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds. Victoria is the 22nd release from the OpenStack project, which is the work of more than 1,000 contributors from around the world. The release is already available on the CentOS mirror network at http://mirror.centos.org/centos/8/cloud/x86_64/openstack-victoria/. The RDO community project curates, packages, builds, tests and maintains a complete OpenStack component set for RHEL and CentOS Linux and is a member of the CentOS Cloud Infrastructure SIG. The Cloud Infrastructure SIG focuses on delivering a great user experience for CentOS Linux users looking to build and maintain their own on-premise, public or hybrid clouds. All work on RDO and on the downstream release, Red Hat OpenStack Platform, is 100% open source, with all code changes going upstream first. PLEASE NOTE: RDO Victoria provides packages for CentOS8 and python 3 only. Please use the Train release, for CentOS7 and python 2.7. Interesting things in the Victoria release include: - With the Victoria release, source tarballs are validated using the upstream GPG signature. This certifies that the source is identical to what is released upstream and ensures the integrity of the packaged source code. - With the Victoria release, openvswitch/ovn are not shipped as part of RDO. Instead RDO relies on builds from the CentOS NFV SIG. - Some new packages have been added to RDO during the Victoria release: - ansible-collections-openstack: This package includes OpenStack modules and plugins which are supported by the OpenStack community to help with the management of OpenStack infrastructure. - ansible-tripleo-ipa-server: This package contains Ansible for configuring the FreeIPA server for TripleO. - python-ibmcclient: This package contains the python library to communicate with HUAWEI iBMC based systems. - puppet-powerflex: This package contains the puppet module needed to deploy PowerFlex with TripleO. - The following packages have been retired from the RDO OpenStack distribution in the Victoria release: - The Congress project, an open policy framework for the cloud, has been retired upstream and from the RDO project in the Victoria release. - neutron-fwaas, the Firewall as a Service driver for neutron, is no longer maintained and has been removed from RDO. Other highlights of the broader upstream OpenStack project may be read via https://releases.openstack.org/victoria/highlights. Contributors During the Victoria cycle, we saw the following new RDO contributors: Amy Marrich (spotz) Daniel Pawlik Douglas Mendizábal Lance Bragstad Martin Chacon Piza Paul Leimer Pooja Jadhav Qianbiao NG Rajini Karthik Sandeep Yadav Sergii Golovatiuk Steve Baker Welcome to all of you and Thank You So Much for participating! But we wouldn’t want to overlook anyone. A super massive Thank You to all 58 contributors who participated in producing this release. This list includes commits to rdo-packages, rdo-infra, and redhat-website repositories: Adam Kimball Ade Lee Alan Pevec Alex Schultz Alfredo Moralejo Amol Kahat Amy Marrich (spotz) Arx Cruz Bhagyashri Shewale Bogdan Dobrelya Cédric Jeanneret Chandan Kumar Damien Ciabrini Daniel Pawlik Dmitry Tantsur Douglas Mendizábal Emilien Macchi Eric Harney Francesco Pantano Gabriele Cerami Gael Chamoulaud Gorka Eguileor Grzegorz Grasza Harald Jensås Iury Gregory Melo Ferreira Jakub Libosvar Javier Pena Joel Capitao Jon Schlueter Lance Bragstad Lon Hohberger Luigi Toscano Marios Andreou Martin Chacon Piza Mathieu Bultel Matthias Runge Michele Baldessari Mike Turek Nicolas Hicher Paul Leimer Pooja Jadhav Qianbiao.NG Rabi Mishra Rafael Folco Rain Leander Rajini Karthik Riccardo Pittau Ronelle Landy Sagi Shnaidman Sandeep Yadav Sergii Golovatiuk Slawek Kaplonski Soniya Vyas Sorin Sbarnea Steve Baker Tobias Urdin Wes Hayutin Yatin Karel The Next Release Cycle At the end of one release, focus shifts immediately to the next release i.e Wallaby. Get Started There are three ways to get started with RDO. To spin up a proof of concept cloud, quickly, and on limited hardware, try an All-In-One Packstack installation. You can run RDO on a single node to get a feel for how it works. For a production deployment of RDO, use TripleO and you’ll be running a production cloud in short order. Finally, for those that don’t have any hardware or physical resources, there’s the OpenStack Global Passport Program. This is a collaborative effort between OpenStack public cloud providers to let you experience the freedom, performance and interoperability of open source infrastructure. You can quickly and easily gain access to OpenStack infrastructure via trial programs from participating OpenStack public cloud providers around the world. Get Help The RDO Project has our users(a)lists.rdoproject.org for RDO-specific users and operators. For more developer-oriented content we recommend joining the dev(a)lists.rdoproject.org mailing list. Remember to post a brief introduction about yourself and your RDO story. The mailing lists archives are all available at https://mail.rdoproject.org. You can also find extensive documentation on RDOproject.org. The #rdo channel on Freenode IRC is also an excellent place to find and give help. We also welcome comments and requests on the CentOS devel mailing list and the CentOS and TripleO IRC channels (#centos, #centos-devel, and #tripleo on irc.freenode.net) however we have a more focused audience within the RDO venues. Get Involved To get involved in the OpenStack RPM packaging effort, check out the RDO contribute pages, peruse the CentOS Cloud SIG page, and inhale the RDO packaging documentation. Join us in #rdo and #tripleo on the Freenode IRC network and follow us on Twitter @RDOCommunity. You can also find us on Facebook and YouTube.

1 0

[edge] Open Geospatial Consortium presentation on the next Edge WG call
by Ildiko Vancsa 16 Nov '20

16 Nov '20

Hi, I’m reaching out to draw your attention to an upcoming presentation on the Edge Computing Group weekly call next Monday. We will have a presentation from the Open Geospatial Consortium where you can learn about their use cases relevant to edge computing and more specifically about the importance of location in that context. In the remaining time on the call we will discuss some of the requirements of the use cases such as location-awareness of infrastructure services and look into collaboration opportunities. The call is on __Monday (November 16) at 1400 UTC__. If you are interested in joining the call and the discussions you can find the dial-in information here: https://wiki.openstack.org/wiki/Edge_Computing_Group#Next_meeting:_Monday_.… Please let me know if you have any questions. Thanks, Ildikó

1 1

[neutron] Bug Deputy Report Nov 9-16
by Lucas Alvares Gomes 16 Nov '20

16 Nov '20

Hi, This is the Neutron bug report of the week of 2020-11-09. Critical: * https://bugs.launchpad.net/neutron/+bug/1903982 - "[neutron-tempest-plugin] Error when executing "hostname" in the VM" Assigned to: Rodolfo Alonso * https://bugs.launchpad.net/neutron/+bug/1903531 - "Update of neutron-server breaks compatibility to previous neutron-agent version" Unassigned High: * https://bugs.launchpad.net/neutron/+bug/1904117 - "Nodes in the OVN scenario multinode jobs can't talk to each other" Assigned to: slaweq * https://bugs.launchpad.net/neutron/+bug/1903985 - " [functional] Timeouts during setting link attributes in the namepaces" Unassigned * https://bugs.launchpad.net/neutron/+bug/1903696 - "Security group OVO object don't reloads and make compatible rules objects" Assigned to: slaweq * https://bugs.launchpad.net/neutron/+bug/1903696 - "Security group OVO object don't reloads and make compatible rules objects" Assigned to: slaweq * https://bugs.launchpad.net/neutron/+bug/1903985 - "[functional] Timeouts during setting link attributes in the namepaces" Unassigned Medium: * https://bugs.launchpad.net/neutron/+bug/1903989 - " Bug in logging potentionally causing neutron to fail" Assigned to: Michal Arbet * https://bugs.launchpad.net/neutron/+bug/1903689 - "[stable/ussuri] Functional job fails - AttributeError: module 'neutron_lib.constants' has no attribute 'DEVICE_OWNER_DISTRIBUTED'" Unassigned * https://bugs.launchpad.net/neutron/+bug/1903433 - "The duplicate route in l3 router namespace results in North-South traffic breaking" Assigned to: yangjianfeng * https://bugs.launchpad.net/neutron/+bug/1903689 - "stable/ussuri] Functional job fails - AttributeError: module 'neutron_lib.constants' has no attribute 'DEVICE_OWNER_DISTRIBUTED" Unassigned * https://bugs.launchpad.net/neutron/+bug/1903982 - " [neutron-tempest-plugin] Error when executing "hostname" in the VM" Assigned to: Rodolfo Alonso * https://bugs.launchpad.net/neutron/+bug/1903989 - " Bug in logging potentionally causing neutron to fail" Assigned to: michalarbet Needs further triage: * https://bugs.launchpad.net/neutron/+bug/1904178 - "[ovn] neutron not support Vlan backed DVR N-Sredirect packet via localnet port," Unassigned * https://bugs.launchpad.net/neutron/+bug/1904041 - " Victoria neutron-db-sync fails with I38991de2b4_source_and_destination_ip_prefix_neutron_metering_rule.py" Unassigned * https://bugs.launchpad.net/neutron/+bug/1903835 - " linuxbridge-agent ERRORS with pyroute2.netlink.exceptions.NetlinkError if ipv6 link local address exist " Unassigned * https://bugs.launchpad.net/neutron/+bug/1903835 - "linuxbridge-agent ERRORS with pyroute2.netlink.exceptions.NetlinkError if ipv6 link local address exist" Unassigned Wishlist: * https://bugs.launchpad.net/neutron/+bug/1904188 - "Include standard attributes ID in OVO dictionaries to improve the OVN revision numbers operation" Assigned to: Rodolfo Alonso

1 0

[kolla] Proposing wu.chunyang for Kolla core
by Mark Goddard 16 Nov '20

16 Nov '20

Hi, I would like to propose adding wu.chunyang to the kolla-core and kolla-ansible-core groups. wu.chunyang did some great work on Octavia integration in the Victoria release, and has provided some helpful reviews. Cores - please reply +1/-1 before the end of Friday 13th November. Thanks, Mark

8 8

CloudKitty deployment on Train and/or Ussuri
by Thode Jocelyn 16 Nov '20

16 Nov '20

Hi, I was looking at the possibilities to have Rating-as-A-Service in our Openstack (currently train but planning to move to Ussuri) and I stumbled upon CloudKitty. I'm currently facing multiple issues with cloudkitty itself and with openstack-ansible. (We are using a containerized deployment with LXC) * I noticed that openstack-ansible has no playbook yet to install a service like CloudKitty even though starting from Ussuri it was added in the ansible-role-requirements.yml. I have created a small patch to be able to install CloudKitty via openstack-ansible and if this is of interest I could potentially submit a PR with this. * The os_cloudkitty role seems to kinda work and only with a relatively old version of CloudKitty. For example, here : https://opendev.org/openstack/openstack-ansible-os_cloudkitty/src/branch/st… since CloudKitty v8.0.0 the section should be named "[fetcher_keystone]", but I found no information as to which CloudKitty version should be used with this role. Does someone have any recommendation as to which version should be used and if there is any interest in improving the role to support more recent versions of CloudKitty? * Even when tweaking the configuration and installing v7.0.0 of Cloudkitty it only fixes cloudkitty-processor, I was never able to make cloudkitty-api work I always get an error like "Fatal Python error: Py_Initialize: Unable to get the locale encoding ModuleNotFoundError: No module named 'encodings'". Any input on this would be greatly appreciated. Cheers Jocelyn

4 5

[nova] MessageUndeliverable from nova-conductor and MessagingTimeout from nova-compute
by Tony Liu 16 Nov '20

16 Nov '20

It's not about connection, but message transmitting. Title is changed. I am having rabbitmq 3.8.4 and nova 21.0.0. When I check rabbitmq queues for compute, I see 3 messages in compute.compute-1 and 0 messages in other compute node queues. In nova-conductor log of all 3 instances, I see "oslo_messaging.exceptions.MessageUndeliverable". In nova-compute log on compute-1, I see "Timed out waiting for nova-conductor." Actually, 4 out of 5 compute nodes have such warning. One compute node has exception "oslo_messaging.exceptions.MessagingTimeout". "rabbitmqctl list_bindings | grep compute-1" shows this. ================================= exchange compute.compute-1 queue compute.compute-1 [] nova exchange compute.compute-1 queue compute.compute-1 [] ================================= Is this some known issue? How did it happen? What's the cause of it and any way to prevent it from happening? Thanks! Tony > -----Original Message----- > From: Arnaud Morin <arnaud.morin(a)gmail.com> > Sent: Saturday, November 14, 2020 2:10 AM > To: Tony Liu <tonyliu0592(a)hotmail.com> > Cc: OpenStack Discuss <openstack-discuss(a)lists.openstack.org> > Subject: Re: [nova-compute] not reconnect to rabbitmq? > > Hello, > > What we noticed in our case is that nova compute is actually > reconnecting, but cannot communicate with the conductor because the > queue binding is either absent or not working anymore. > > So, first, which version of nova are you running? > Which version of rabbitmq? (some bugs related to shadow bindings are > fixed after 3.7.x / dont remember x) > > Can you check if you have any queue related to your compute? > something like that: > rabbtitmqctl list_queues | grep mycompute > > Also check the bindings, better using the management interface or > rabbitmqadmin: > rabbitmqadmin list bindings | grep mycompute > > What usually fixed our issue by the past was to delete / recreate the > binding (easy to do from the management interface). > > Cheers, > > -- > Arnaud Morin > > On 14.11.20 - 00:34, Tony Liu wrote: > > Hi, > > > > I'm having a deployment with Ussuri on CentOS 8. > > I noticed that, in case the connection from nova-compute to rabbitmq > > is broken, nova-compute doesn't reconnect. > > I checked nova-conductor who seems keeping trying reconnect to > > rabbitmq when connection is broken. But nova-compute doesn't seem > > doing the same. I've seen it a few times, after I fixed rabbitmq and > > bring it back, nova-conductor gets reconnected, but nova-compute > > doesn't, I have to manually restart it. Anyone else has the similar > > experiences? > > Anything I am missing? > > > > > > Thanks! > > Tony > > > >

2 2

Where to send mascot graphic adjustment proposals
by Michael Chapman 16 Nov '20

16 Nov '20

While doing some work on the designate docs I wanted to replace the logo on the diagrams (for example https://docs.openstack.org/designate/latest/contributor/architecture.html) with the mascot graphics available, specifically the horizontal one here: https://object-storage-ca-ymq-1.vexxhost.net/swift/v1/6e4619c416ff4bd19e1c0… The bottom line of the crocodile is just slightly not aligned with the text, which I think could be improved, and perhaps the crocodile could also be increased in size to match that of the text. In addition, the bottom of the mascots page mentions to contact anne(a)openstack.org which is no longer an active address. Are the above proposed changes reasonable, and is there a new contact available for getting mascot graphics modified? I can change it in the designate diagrams myself but they are marked ND so I don't think that's technically allowed. - Michael

1 0

Which deployment method for ceph (rook|ceph-ansible|tripleo)
by Oliver Weinmann 15 Nov '20

15 Nov '20

Hi, I'm still in the process of preparing a OpenStack POC. I'm 100% sure that I want to use CEPH and so I purchased the book Mastering CEPH 2nd edition. First of all, It's a really good book. It basically explains the various methods how ceph can be deployed and also the components that CEPH is build of. So I played around a lot with ceph-ansible and rook in my virtualbox environment. I also started to play with tripleo ceph deployment, although I haven't had the time yet to sucessfully deploy a openstack cluster with CEPH. Now I'm wondering, which of these 3 methods should I use? rook ceph-ansible tripleo I also want to use CEPH for NFS and CIFS (Samba) as we have plenty of VMs running under vSphere that currently consume storage from a ZFS storage via CIFS and NFS. I don't know if rook can be used for this. I have the feeling that it is purely meant to be used for kubernetes? And If I would like to have CIFS and NFS maybe tripleo is not capable of enabling these features in CEPH? So I would be left with ceph-ansible? Any suggestions are very welcome. Best Regards, Oliver

5 7

[masakari] Teams cleanup
by Radosław Piliszek 14 Nov '20

14 Nov '20

Hello Everyone! To avoid the ghost town effect in Masakari teams, I propose to clean up the memberships. I've already had a chance to discuss it with Takashi Kajinami on IRC [0] as he wanted to remove himself. We have 3 teams (1 gerrit, 2 launchpad): - Gerrit masakari-core [1] - Launchpad masakari-drivers [2] - Launchpad masakari-bugs [3] I plan to set these to the following people: - myself [Radosław Piliszek] (the new PTL) - suzhengwei (new active contributor and core) - Jegor van Opdorp (new active contributor and core) - Sampath Priyankara (the previous PTL) - Tushar Patil (the previously most active core) I will enact the change in a week from now if there are no objections. I also see a few issues likely to discuss with the infra team: 1) Launchpad masakari-drivers - there is a pending invitation for the release team - I doubt it has much use but I would love to see it accepted/rejected/accepted&removed. 2) Gerrit masakari-core - there is an external CI in the core team - why would it need this level of privilege? It does not add its flags to changes, only replies with job status. [0] http://eavesdrop.openstack.org/irclogs/%23openstack-masakari/%23openstack-m… [1] masakari-core: https://review.opendev.org/#/admin/groups/1448,members [2] https://launchpad.net/~masakari-drivers/+members [3] https://launchpad.net/~masakari-bugs/+members Kind regards, -yoctozepto

1 1