July 2021 - openstack-discuss - lists.openstack.org

[release] Release countdown for week R-11, Jul 19 - Jul 23
by Herve Beraud 16 Jul '21

16 Jul '21

Development Focus ----------------- We are now past the Xena-2 milestone, and entering the last development phase of the cycle. Teams should be focused on implementing planned work for the cycle. Now is a good time to review those plans and reprioritize anything if needed based on what progress has been made and what looks realistic to complete in the next few weeks. General Information ------------------- Looking ahead to the end of the release cycle, please be aware of the feature freeze dates. Those vary depending on deliverable type: * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (August 19). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (September 2, 2021) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, September 2, 2021. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. After feature freeze, cycle-with-rc deliverables need to produce a first release candidate (and a stable branch) before RC1 deadline (September 16) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (September 27, 2021) Upcoming Deadlines & Dates -------------------------- Non-client library freeze: August 19 (R-7 week) Client library freeze: September 2 (R-5 week) Xena-3 milestone: September 2 (R-5 week) Xena release: October 6 -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

1 0

[CloudKitty] Virtual PTG October 2021
by Rafael Weingärtner 16 Jul '21

16 Jul '21

Hello everyone, As you probably heard our next PTG will be held virtually in October. I've marked October 18, at 14:00-17:00 UTC [1]. We already have a CloudKitty meeting organized for this day. Therefore, it seems the most practical choice. However, if you guys would like some other dates and/or time, just let me know. The room I selected is called "Bexar". I've also created an etherpad [2] to collect ideas/topics for the PTG sessions. If you have anything to discuss, please don't hesitate to write it there. [1] https://ethercalc.openstack.org/8tum5yl1bx43 [2] https://etherpad.opendev.org/p/cloudkitty-ptg-xena -- Rafael Weingärtner

3 4

[nova] Milestone 2 - spec freeze
by Balazs Gibizer 16 Jul '21

16 Jul '21

Hi, Yesterday we hit Xena Milestone 2. This also means nova is now in a state of spec freeze. The Yoga spec directory already exists so specs that are not merged to Xena can be propose to Yoga already. I've updated the bp states in launchpad[1]. Please check your bps and let me know if I missed something or misunderstood the status of the implementation work. We have 20 open bps at the moment which is a lot. Please note that Milestone 3 and therefore feature freeze is 3rd of September, which is 7 weeks from now. I encourage all of you to prioritize reviewing implementation of the bps that are already in NeedsCodeReview state. Cheers, gibi [1] https://launchpad.net/nova/+milestone/xena-3

1 0

Setting bandwidth limit
by Felipe Mogollon 16 Jul '21

16 Jul '21

Hi, I am running openstack victoria installed using packstack. Everything things to be fine except bandwidth limit. I have tried to limit internal traffic between two instances and between instances and "Internet" but I always get maximum data transfer speed. I have set up following rules openstack network qos rule create --type bandwidth-limit --max-kbps 3 --max-burst-kbits 2 --ingress bw-choke openstack network qos rule create --type bandwidth-limit --max-kbps 3 --max-burst-kbits 2 --egress bw-choke and applied bw-choke policy to the internal network where my instances are deployed: openstack network set --qos-policy bw-choke newdeploylab_private_network and to ports where machines connect to subnet: openstack port set --qos-policy bw-choke 503a07b8-2da0-4abe-8251-ede648ba42b4 openstack port set --qos-policy bw-choke 776d5fb3-639c-47cc-9b0f-6ec855397df7 but nothing happens. Each time I try to download something from internet or copy data from an instance to another I always get maximum data transfer speed. I have followed instructions from https://docs.openstack.org/neutron/victoria/admin/config-qos.html Any ideas? -- <https://www.vicomtech.org> Juan Felipe Mogollón Rodríguez Researcher | Investigador fmogollon(a)vicomtech.org +[34] 943 30 92 30 Digital Media <https://www.linkedin.com/company/vicomtech> <https://www.youtube.com/user/VICOMTech> <https://twitter.com/@Vicomtech> member of: <https://graphicsvision.ai/> La información que contiene este mensaje y sus adjuntos son confidenciales y están dirigidos exclusivamente a sus destinatarios. Si recibe este mensaje por error, se ruega nos lo comunique y proceda a su borrado. The information contained in this electronic message is intended only for the personal and confidential use of the recipients designated in the original message. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer.

1 0

[all] Proposed Yoga cycle schedule
by Herve Beraud 16 Jul '21

16 Jul '21

Hey everyone, The Xena cycle is going by fast, and it's already time to start planning some of the early things for the Yoga release. One of the first steps for that is actually deciding on the release schedule. Typically we have done this based on when the next Summit event was planned to take place. Due to several reasons, we don't have a date yet for the first 2022 event. The current thinking is it will likely take place in May (nothing is set, just an educated guess, so please don't use that for any other planning). So for the sake of figuring out the release schedule, we are proposing one schedule targeting a release date at the end of March. Hopefully this will then align well with event plans. Here is the proposed schedule: https://review.opendev.org/c/openstack/releases/+/800663 Please feel free to comment on the patch if you see any major issues that we may have not considered. Thanks for your reading -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

1 0

[neutron][vpnaas] Ok with V. not working with W.
by Franck VEDEL 16 Jul '21

16 Jul '21

Hello, i have been trying to fix a problem for over 2 weeks with no success so am looking for some help as my openstack is due to work in september (for my students). I need the vpnaas service. I'm doing a lab with centos / kolla-ansible / victoria ... vpnaas works, exactly what I need. I replace V with Wallaby. Exactly the same server, the same Centos, I just change V to W in the configuation file. Everything works except Vpnaas. I have a new server, and for some reason I can't have Victoria (issue with horizon that I don't understand). I'm trying Wallaby. Everything works perfectly except Vpnaas. Why ? It's incomprehensible. A bug ? The error message (neutron-l3-agent.log): Command: ['mount', '--bind', '/var/lib/neutron/ipsec/8b987595-47be-45cc-95f5-3b70d24f4976/var/run', '/var/run'] Exit code: 0 Stdout: Stderr: 2021-07-16 12:03:57.089 281941 INFO neutron_vpnaas.services.vpn.common.netns_wrapper [-] /var/lib/neutron/ipsec/8b987595-47be-45cc-95f5-3b70d24f4976/var/run has been bind-mounted in /var/run Command: ['ipsec', 'whack', '--status'] Exit code: 33 Stdout: Stderr: whack: Pluto is not running (no "/run/pluto/pluto.ctl ») Can this be a bug? I do exactly the same things, the same configurations? How to find the problem? Does anyone have a working Oopenstack Wallaby with Centos and Vpnaas? Meci in advance for your help. Franck http://www.rtgrenoble.fr <http://www.rtgrenoble.fr/>

1 0

[kolla] Ceph client version in Kolla 12.0.0 Wallaby and ubuntu containers
by J-P Methot 16 Jul '21

16 Jul '21

Hi, We've been using Kolla to provision a production cluster and we've noticed that the ceph-client version provided in the Kolla images is severely outdated as it doesn't support the fix to CVE-2021-20288 that was added in Pacific 16.2.1 (installed version in image is 16.2.0). As a result, the installed ceph-client can't connect to ceph clusters where the patch is active. Is there any Kolla image where more recent versions of ceph-client is installed? How would I be able to get them? -- Jean-Philippe Méthot Senior Openstack system administrator Administrateur système Openstack sénior PlanetHoster inc.

4 4

[nova] [magnum] Flavor names vs IDs
by Krzysztof Klimonda 15 Jul '21

15 Jul '21

Hi, Flavors have both names ands IDs and both can be set during creation - what is the background for having both being separate from each other? I'm asking this because magnum uses flavor id for it's "instance-type" node annotation (which is understandable) and by default flavor ID is an autogenerated UUID. Would there be any downside to always matching flavor id and name when creating flavors? Best Regards, Krzysztof -- Krzysztof Klimonda kklimonda(a)syntaxhighlighted.com

1 0

[kolla] multiple ceph backends
by J-P Methot 15 Jul '21

15 Jul '21

Hi, I'm progressing in figuring out Kolla and I've hit another issue. On our regular setups, we happen to be using multiple Ceph backends in cinder. Each of those backend uses a differently named ceph config file (like ceph.conf and ceph-rep.conf). While adding a custom configuration to cinder.conf is pretty easy, what's the best way to ensure that my second ceph config file ends up in my containers at the correct path? I've considered using ansible to add the file after kolla has deployed but I doubt this would be permanent. -- Jean-Philippe Méthot Senior Openstack system administrator Administrateur système Openstack sénior PlanetHoster inc.

2 1

[TripleO] next irc meeting Tuesday 20 July @ 1400 UTC in OFTC #tripleo
by Marios Andreou 15 Jul '21

15 Jul '21

Reminder the next TripleO irc meeting is this coming Tuesday 20 July 1400 UTC in OFTC irc channel #tripleo. agenda: https://wiki.openstack.org/wiki/Meetings/TripleO one-off items: https://etherpad.opendev.org/p/tripleo-meeting-items (feel free to add any tripleo status/ongoing work etc to the etherpad). Our last meeting was on Jul 6 - you can find logs @ http://eavesdrop.openstack.org/meetings/tripleo/2021/tripleo.2021-07-06-14.… Hope you can make it on Tuesday, regards, marios

1 0