November 2020 - openstack-discuss

[docs] HTTP redirects
by Peter Matulis 18 Nov '20

18 Nov '20

Hi, So I followed instructions [1] to implement redirects and it's not working. Please let me know where I went wrong: https://review.opendev.org/#/c/763067/ Shouldn't the first URL redirect to the second? https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/late… https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/late… Thanks, Peter [1]: https://docs.openstack.org/doc-contrib-guide/redirects.html

3 2

[Victoria][Python-3.9] dhcp-agent problem
by tjoen 17 Nov '20

17 Nov '20

System: LFS. Python-3.9.0, Neutron-17.0.0, oslo.privsep-2.4.0 Got Train+Py37, Usuri+Py38 working with the help of the install-guide. Victoria+Py39 Only eventlet needed a patch. Neutron only for neutron/plugins/ml2/drivers/linuxbridge/agent/arp_protect.py def ebtables(comm, table='nat'): execute = ip_lib.IPWrapper(NAMESPACE).netns.execute - return execute(['ebtables', '-t', table, '--concurrent'] + comm, + return execute(['/usr/sbin/ebtables', '-t', table, '--concurrent'] + comm, run_as_root=True) Possible not necessary but it avoids sudo errors. Controller logs (made readable): [-] Unable to enable dhcp for cb7948eb-e5c0-4764-a653-542c3e864f54.: TypeError: <lambda>() takes 6 positional arguments but 7 were given Traceback (most recent call last): File "/site-packages/neutron/agent/dhcp/agent.py", line 192, in call_driver rv = getattr(driver, action)(**action_kwargs) File "/site-packages/neutron/agent/linux/dhcp.py", line 249, in enable common_utils.wait_until_true(self._enable, timeout=300) File "/site-packages/neutron/common/utils.py", line 703, in wait_until_true while not predicate(): File "/site-packages/neutron/agent/linux/dhcp.py", line 261, in _enable interface_name = self.device_manager.setup(self.network) File "/site-packages/neutron/agent/linux/dhcp.py", line 1675, in setup if ip_lib.ensure_device_is_ready(interface_name, File "/site-packages/neutron/agent/linux/ip_lib.py", line 960, in ensure_device_is_ready if not dev.link.exists or not dev.link.address: File "/site-packages/neutron/agent/linux/ip_lib.py", line 513, in exists return privileged.interface_exists(self.name, self._parent.namespace) File "/site-packages/oslo_privsep/priv_context.py", line 247, in _wrap return self.channel.remote_call(name, args, kwargs) File "/site-packages/oslo_privsep/daemon.py", line 224, in remote_call raise exc_type(*result[2]) TypeError: <lambda>() takes 6 positional arguments but 7 were given Launching an instance: $ openstack server create --flavor m1.nano --image cirros \ --nic net-id=cb7948eb-e5c0-4764-a653-542c3e864f54 --security-group default \ --key-name mykey provider-instance results in status=BUILD and never ACTIVE Other logs on Controller after starting Compute1: Unable to access /var/lib/neutron/dhcp/cb7948eb-e5c0-4764-a653-542c3e864f54/pid; Error: [Errno 2] No such file or directory Ownerships and permissions are OK: drwxr-xr-x 2 neutron neutron 4096 Nov 15 19:49 cb7948eb-e5c0-4764-a653-542c3e864f54/ Anybody with the same problem? I am not a Python programmer so I am at a lost

3 5

[release][infra] Discrepancy between release jobs and the "normal" jobs CI in terms of distro
by Radosław Piliszek 17 Nov '20

17 Nov '20

I did not quote the original subject because it was too long. It was: [release][masakari] - [Release-job-failures] Release of openstack/masakari-monitors for ref refs/tags/(7.0.1|8.0.2|9.0.1) failed Particularly, we are continuing the discussion from: http://lists.openstack.org/pipermail/openstack-discuss/2020-November/018743… Would it be possible what Hervé is proposing? I.e. better segregation of distro per branch of release? I believe it would be a rare situation but surely testing something on Bionic and trying to release on Focal might have its quirks. -yoctozepto

4 4

[release][masakari] - [Release-job-failures] Release of openstack/masakari-monitors for ref refs/tags/(7.0.1|8.0.2|9.0.1) failed
by Herve Beraud 17 Nov '20

17 Nov '20

During the release job for: - masakari-monitors 9.0.1 (ussuri) - masakari-monitors 8.0.2 (train) - masakari-monitors 7.0.1 (stein) uploads to PyPI failed [1][2][3] with: "No package matching 'python-libvirt' is available" [4][5][6] It's due to our recent move to focal [7] where the package 'python-libvirt' is named ''python3-libvirt'.This package is pulled by bindep during the job execution. Current status: Tag (9.0.1, 8.0.2, 7.0.1) was pushed OK No tarball upload No PyPI upload Once the issue is fixed, a new version should be released for the three stables branches. Version 9.0.1, 8.0.2, 7.0.1 these versions will never be uploaded on PyPi as the fix requires new changes in the project repo [8][9][10]. Also notice that on Victoria and Wallaby this bindep requirement have been dropped during the migration testing on ubuntu focal [11]. [1] https://zuul.opendev.org/t/openstack/build/63539177d44b4ea48d3fbfe39a638275… [2] https://zuul.opendev.org/t/openstack/build/778ace86ec8f4ef894d740d81e8f700f… [3] https://zuul.opendev.org/t/openstack/build/919cfc7df1e0408e9d6af4a9e8ef28ee… [4] http://lists.openstack.org/pipermail/release-job-failures/2020-November/001… [5] http://lists.openstack.org/pipermail/release-job-failures/2020-November/001… [6] http://lists.openstack.org/pipermail/release-job-failures/2020-November/001… [7] http://lists.openstack.org/pipermail/openstack-discuss/2020-November/018585… [8] https://opendev.org/openstack/masakari-monitors/src/branch/stable/stein/bin… [9] https://opendev.org/openstack/masakari-monitors/src/branch/stable/train/bin… [10] https://opendev.org/openstack/masakari-monitors/src/branch/stable/ussuri/bi… [11] https://opendev.org/openstack/masakari-monitors/commit/03ef3555888fdd0ea38b… -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

3 9

[tc] weekly update
by Mohammed Naser 17 Nov '20

17 Nov '20

Hi everyone, Here's an update for what happened in the OpenStack TC this week. You can get more information by checking for changes in openstack/governance repository. # Patches ## Open Reviews - Add Magpie charm to OpenStack charms https://review.opendev.org/762820 - Move Placement under Nova's governance https://review.opendev.org/760917 - Add Resolution of TC stance on the OpenStackClient https://review.opendev.org/759904 - Remove assert_supports-zero-downtime-upgrade tag https://review.opendev.org/761975 - Add election schedule exceptions in charter https://review.opendev.org/751941 - Clarify the requirements for supports-api-interoperability https://review.opendev.org/760562 - Propose Kendall Nelson for vice chair https://review.opendev.org/762014 ## General Changes - Select JSON to YAML goal for Wallaby cycle https://review.opendev.org/760957 - Adding reno and warnings example for JSON->YAML goal doc https://review.opendev.org/760956 - Add danms liaison preferences https://review.opendev.org/758822 - Add goal for migrate RBAC policy format from JSON to YAML https://review.opendev.org/759881 - Add diablo_rojo liaison preferences https://review.opendev.org/759718 - Add ricolin liaison preferences https://review.opendev.org/759704 - Add gmann liaison preference https://review.opendev.org/758602 - Resetting projects' TC liaisons empty https://review.opendev.org/758600 Thanks for reading! Mohammed & Kendall -- Mohammed Naser VEXXHOST, Inc.

1 0

[Freezer] Gerrit breach and commit audit
by caihui_nj＠163.com 17 Nov '20

17 Nov '20

1 0

[neutron] Team meetings today
by Slawek Kaplonski 17 Nov '20

17 Nov '20

Hi, Just a quick reminder that we have neutron team meeting today at 14:00 UTC and neutron CI meeting at 15:00 UTC. Both are on the #openstack-meetings-3 channel. Agenda for the meetings: https://wiki.openstack.org/wiki/Network/Meetings https://etherpad.opendev.org/p/neutron-ci-meetings -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[Freezer] Gerrit breach and commit audit
by caihui_nj＠163.com 17 Nov '20

17 Nov '20

1 0

[infra][kolla] Docker registry pull limits
by Radosław Piliszek 17 Nov '20

17 Nov '20

Hello Everyone, Kolla CI jobs started getting hit by Docker registry pull limits: docker.errors.APIError: 500 Server Error: Internal Server Error ("toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit") It is relatively random as the limit is seemingly per IP address. The question is how we should approach this issue. It seems Docker offers an open source plan that would lift any limits on the kolla namespace. [1] However, we are not entirely sure who should fill out the related form [2]. We believe it should be someone from the infra team but it is not clear. :/ Please share your thoughts. [1] https://www.docker.com/blog/expanded-support-for-open-source-software-proje… [2] https://docs.google.com/forms/d/e/1FAIpQLSd11DjfgeaKSRdqp6Br85MzQQuM4igt-xm… -yoctozepto

1 0

[manila][OSC] Priorities for implementing the OSC share commands
by Maari Tamm 17 Nov '20

17 Nov '20

Hi Everyone! Slowly but steady we are implementing the OpenStack Client for Manila. For the upcoming release we are aiming to implement the following commands, in no particular order: Share Replicas: openstack share replica create / delete / list / show / set / promote / resync Share Replica Export Locations: openstack share replica export location list / show Share Manage/Unmanage: openstack share adopt / abandon Services: openstack share service set / list Share Pools: openstack share pool list User Messages: openstack share message delete / list / show Availability Zones (add support for manila): openstack availability zone list Limits (add support for manila): openstack limits show —absolute /—rate Share Export Locations (ready for reviews: https://review.opendev.org/#/c/761661/ <https://review.opendev.org/#/c/761661/>): openstack share export location list / show Share Snapshots patch II (ready for reviews: https://review.opendev.org/#/c/746458/ <https://review.opendev.org/#/c/746458/>) : openstack share snapshot adopt / abandon openstack share snapshot export location show / list openstack share snapshot access create / delete / list To make this happen we could really use help reviewing the patches, once proposed. As linked above, two patches are currently ready for testing/reviews. We’d also very much appreciate getting some feedback on the list itself. Are we missing something important that would be useful for operators and should be implemented this cycle? If anyone has some commands in mind, please do let us know! Mohammed Naser and Belmiro Moreira, would love to get your thoughts on this as well! :) Thanks, Maari Tamm (IRC: maaritamm)

2 1

[Heat] Fwaas v2 support
by Yves Gd 17 Nov '20

17 Nov '20

Hi, Trying to use a HOT firewall template, I encounter this error: "ERROR: HEAT-E99001 Service neutron is not available for resource type OS::Neutron::Firewall, reason: Required extension fwaas in neutron service is not available." We use fwaas v2, is it supported by heat module on Train version? Our openstack environment is deployed by kolla (9.2.0) with fwaas enabled. I assume "yes" but would like to be sure. Sorry if it's written somewhere but I couldn't find this information. Here is a simple version producing the error: ------------------- heat_template_version: rocky resources: firewall1: type: OS::Neutron::Firewall properties: description: Test fwaas name: Test_fwaas ------------------- Regards, Yves

3 2

[tacker] Skip IRC meeting on Nov 17th
by Yasufumi Ogawa 17 Nov '20

17 Nov '20

Hi tacker team, I am not available to join IRC meeting today. I'd like to cancel the meeting because we may have no topics, the problem of functional test has resolved and no urgent patches. Thanks, Yasufumi

1 0

[neutron] Mixed VLAN / VxLAN Network
by DHilsbos＠performair.com 17 Nov '20

17 Nov '20

All; We're getting ready to set up an OpenStack cloud, and I have some questions about networking. I apologize if this information if available already or if a question like this has already been asked. We intend to slot it in to a location which uses VLANs heavily. In particular, our DMZ is on a VLAN, with the subnet's gateway at our firewall. We plan to use VxLANs within OpenStack. Is it possible to make OpenStack aware of the DMZ VLAN, so that we can use it in projects? Is it possible to use the DMZ VLAN without routing through the OpenStack network node(s)? Thank you, Dominic L. Hilsbos, MBA Director - Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com www.PerformAir.com

3 2

[SDK][OSC] Meeting Times
by Kendall Nelson 16 Nov '20

16 Nov '20

Hello! In the PTG session today we talked about doing some sort of regular meetings to kind of jump start things after the more recent lack of activity. We discussed beginning with more frequent meetings (a couple across the next few weeks) and then shifting to a more relaxed monthly cadence. I propose 15:00 UTC on the third thursday of each month as our monthly meeting time? If people agree, I will propose a patch :) As for the more frequent ones to keep the momentum from discussion from this week/last week. We could use that time (15 UTC) and date (Thursdays) and maybe just do them on Nov 12 and 19th to keep us moving? That gives us next week to catch up/ take a breath from the last two weeks, but not waiting till after the US Thanksgiving holiday. Let me know what you think! -Kendall Nelson (diablo_rojo)

4 6

[trove] Gerrit breach and commit audit
by Lingxian Kong 16 Nov '20

16 Nov '20

Background: http://lists.opendev.org/pipermail/service-announce/2020-October/000011.html Looking back at the patches merged between 2020-10-01 and 2020-10-20, I can confirm that the trove deliverables repos look OK. --- Lingxian Kong Senior Software Engineer Catalyst Cloud www.catalystcloud.nz

1 0

Re: Trove backup issue (Victoria)
by Lingxian Kong 16 Nov '20

16 Nov '20

(adding openstack-discuss mailing list) Hi Justin, I don't think there is a backup docker image named "openstacktrove/db-backup-mysql5.0", the backup image only support 8.0 and 5.7. You can try "openstacktrove/db-backup-mysql5.7". --- Lingxian Kong Senior Software Engineer Catalyst Cloud www.catalystcloud.nz On Tue, Nov 17, 2020 at 3:26 AM Justin Anstes <janstes(a)gmail.com> wrote: > Hi, > > Apologies to contact you about this issue. I'm sure it's a simple fix but > I've not been able to find much on it. > > I'm testing the current Victoria release. All setup ok just that I'm not > able to backup to Swift, with the following error: > > 404 Client Error: Not Found ("pull access denied for > openstacktrove/db-backup-mysql5.0, repository does not exist or may require > \'docker login\': denied: requested access to the resource is denied") > > It appears to require a Docker login.I've attached the full log just in > case you might need it. Many thanks if you have time to check. > > Kind regards > > Justin >

1 0

[qa][policy] Testing strategy discussion for new RBAC (new scope and default role combinations)
by Ghanshyam Mann 16 Nov '20

16 Nov '20

Hello Everyone, To continue the discussion on how projects should test the new RBAC (scope as well as the new defaults combination), we will host a call on bluejeans on Tuesday 10th Nov 16.00 UTC. Lance has set up the room for that: https://bluejeans.com/749897818 Feel free to join if you are interested in that or would like to help with this effort. -gmann

2 2

[ironic] Review session for API JSON conversion
by Steve Baker 16 Nov '20

16 Nov '20

Due to timezones and the nature of the change series, we're doing some group scheduled review sessions of this series which converts the WSME based REST API to a JSON: https://review.opendev.org/#/q/status:open+topic:story/1651346 Discussion can happen on IRC in #ironic. The first session will be on this Tuesday, 7pm UTC, with a follow-up on Wednesday, 8am UTC. There is a calendar invite which I can add you to on request. cheers

1 0

[monasca] Predictive Analytics
by Giacomo Lanciano 16 Nov '20

16 Nov '20

Hi all, I am new to this community, as I have only recently started using OpenStack in my research. I am working on designing an "intelligent" auto-scaling mechanism, based on resources consumption metrics forecasts, leveraging on Monasca for metrics ingestion and processing. Digging into the Wiki/Documentation, I have stumbled upon the recently retired "monasca-analytics", that seems to cover pretty much (and way more of) what I had in mind to build on top of the monitoring component, to enable proactive auto-scaling decisions. I am very interested in knowing more about why such project has been abandoned and, more importantly, whether the effort has been redirected to another project that I am not aware of. Could you point me to any resource that you consider useful to contribute on these topics? Thanks in advance. Kind Regards. Giacomo -- Giacomo Lanciano Ph.D. Student in Data Science Scuola Normale Superiore, Pisa, Italy https://www.linkedin.com/in/giacomolanciano

2 1

centos-7 infra mirror issues, lp 1904418
by Wesley Hayutin 16 Nov '20

16 Nov '20

Greetings, Just wanted to raise awareness of the following bug https://bugs.launchpad.net/tripleo/+bug/1904418 http://mirror.centos.org/centos/7/rt/x86_64/repodata/repomd.xml is a 404 Thank you!

1 0

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