April 2021 - openstack-discuss - lists.openstack.org

[Diversity] D&I WG Office Hours at the PTG
by Amy Marrich 16 Apr '21

16 Apr '21

The Diversity and Inclusion WG has grabbed our usual PTG slot Monday at 16:00UTC and we will be holding office hours to help any project with Inclusive Naming or other D&I related topics. If you'd like us to attend any of your sessions please let me know. If you've been interested in learning more about the WG please come join us! Thanks, Amy (spotz)

1 0

[all][elections][tc] Technical Committee April 2021 Special Election Results
by Kendall Nelson 16 Apr '21

16 Apr '21

Hello! Please join me in congratulating the 1 newly elected member of the Technical Committee (TC). Amy Marrich (spotz)! Full results: https://civs1.civs.us/cgi-bin/results.pl?id=E_69909177d200947c Election process details and results are also available here: https://governance.openstack.org/election/ Thank you to all of the candidates, having a good group of candidates helps engage the community in our democratic process. Thank you to all who voted and who encouraged others to vote. We need to ensure your voice is heard. Thank you for another great round! -Kendall Nelson (diablo_rojo) & the Election Officials

4 3

[kolla-ansible][horizon] policy.yaml/json files
by Adam Tomas 16 Apr '21

16 Apr '21

Hi, Im not quite clear about policy.yaml/json files in kolla-ansible. Let assume, that I need to allow one of project users to add other users to the project. So I create „project_admin” role and assign it to this user. Then I found /etc/kolla/keystone/policy.json.test file, which I use as template. There is rule „identity:create_credential” : „(role:admin and system_scope:all)” so I add „or role:project_admin” and put file in /etc/kolla/config/keystone/ and reconfigure kolla. And now few questions: 1. policy.json (or policy.yaml) always overwrite all default policies? I mean if I only add one rule to this file then other rules will „disappear” or will have default values? Is there any way to only overwrite some default rules and leave rest with defaults? Like with .conf files 2. what about Horizon and visibility of options? In mentioned case putting the same policy.json file in /etc/kolla/config/keystone/ and /etc/kolla/config/horizon/ should „unblock” Add User button for user with project_admin role? Or how to achieve it? 3. does Horizon need the duplicated policy.json files from other services in it’s configuration folder or is it enough to write policy.json for services I want to change? 4. when I assign admin role to a user with projectID (openstack role add —project PROJECT_ID —user SOME_USER admin) this user sees in Horizon everything systemwide, not only inside this project… Which rules should be created to allow him to see only users and resources which belongs to this project? Best regards Adam

2 7

[neutron] Drivers meeting - Friday 23.04.2021 cancelled
by Slawek Kaplonski 16 Apr '21

16 Apr '21

Hi, As we have PTG, let's cancel next week's drivers meeting. See You on the PTG sessions. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[neutron] CI meeting - Tuesday 20.04.2021
by Slawek Kaplonski 16 Apr '21

16 Apr '21

Hi, As we have PTG, let's cancel next week's CI meeting. See You on the PTG sessions. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[neutron] Team meeting - Tuesday 20.04.2021
by Slawek Kaplonski 16 Apr '21

16 Apr '21

Hi, As we have PTG, let's cancel next week's team meeting. See You on the PTG sessions. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[neutron] Drivers meeting agenda - 16.04.2021
by Slawek Kaplonski 16 Apr '21

16 Apr '21

Hi, Agenda for our tomorrow's drivers meeting is at [1]. We have 1 new RFE to discuss: - https://bugs.launchpad.net/neutron/+bug/1922716 - [RFE] BFD for BGP Dynamic Routing [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda -- Slawek Kaplonski Principal Software Engineer Red Hat

1 1

[announce][debian][wallaby] general availability of OpenStack Wallaby in Debian
by Thomas Goirand 15 Apr '21

15 Apr '21

Hi! It's my pleasure to announce the general availability of OpenStack Wallaby in Debian. I've just finished uploading everything to Debian Experimental today (not in unstable, as Bullseye is frozen), and the Bullseye backports are available the usual way, for example using extrepo (which is in the official Debian backports): apt-get install extrepo extrepo enable openstack_wallaby apt-get update ... or directly setting-up the http://bullseye-wallaby.debian.net repository the usual way. Note that while Victoria is available on Buster and Bullseye (to ease the transition), Wallaby is only available on Bullseye, which is due to be released next month (if everything goes as planned, there's no official release date decided yet if I understand well). New in this release =================== Masakari is now packaged. Masakari-dashboard is still waiting on the FTP master NEW queue though. A quick update on openstack-cluster-installer ============================================= Wallaby can already be installed by OCI [1]. Note that OCI is now public-cloud ready, and can deploy specific nodes for the billing (with cloudkitty): - messaging (separate RabbitMQ cluster and Galera for Gnocchi) - billmon / billosd (separate Ceph cluster for Gnocchi) Our tests showed that this setup can scale to 10k+ VMs without any issue (the separate Galera + RabbitMQ bus really helps) reporting 400+ metrics per seconds. As always, OCI is smart enough so the additional nodes are all optional (and not needed for smaller scales), and the cluster reconfigures itself if you decide to add new node types in your deployment. Thanks to new features added to puppet-openstack [2], the number of uwsgi process adapts automatically to the number of cores available in controller nodes. Last, with OCI you may now enjoy a full BGP-to-the-host (over IPv6 un-numbered link local) networking setup. This also works with compute nodes, as long as you decide to not use the DVR mode (if you do with to use DVR, then you need L2 connectivity on the computes: that's a Neutron "feature", unfortunately), or if you decide to use Neutron BGP routed networking [3] (though this mode also still has some limitations at this time, such as no support for virtual router external gateways). In this setup, only the Network nodes need L2 connectivity to the outside world. This also scales very nicely to *a lot* of nodes... without any ARP spanning tree problems. We (at Infomaniak) now only use this deployment mode in production due to its scalability. Final words =========== Please report any issue you may find, on OCI or on the Debian packages. Cheers, Thomas Goirand (zigo) [1] https://salsa.debian.org/openstack-team/debian/openstack-cluster-installer [2] https://review.opendev.org/q/topic:%22debian-uwsgi-support%22+(status:open%… [3] https://docs.openstack.org/neutron/latest/admin/config-bgp-floating-ip-over…

2 1

[manila] Propose Liron Kuchlani and Vida Haririan to manila-tempest-plugin-core
by Goutham Pacha Ravi 15 Apr '21

15 Apr '21

Hello Zorillas, Vida's been our bug czar since the Ussuri release and she's conceptualized and executed our successful bug triage strategy. She has also painstakingly organized several documentation and code bug squash events and kept the pulse on multi-release efforts. She's taught me a lot about project management and you can see tangible results here, I suppose :) Liron's fixed a lot of test code bugs and covered some old and important test gaps over the past few releases. He's driving standardization of the tempest plugin and bringing in best practices from tempest, refstack and elsewhere into our testing. It's always a pleasure to work with Liron since he's happy to provide and welcome feedback. More recently, Liron and Vida have enabled us to work with the InteropWG and define refstack guidelines. They've also gotten us closer to members from the QA community who they work with more closely downstream. In short, they bring in different perspectives while also espousing the team's core values. So I'd like to propose their addition to the manila-tempest-plugin-core team. Please give me your +/- 1s for this proposal. Thanks, Goutham

5 5

[TripleO] Xena PTG schedule please review
by Marios Andreou 15 Apr '21

15 Apr '21

Hello TripleO o/ Thanks again to everybody who has volunteered to lead a session for the coming Xena TripleO project teams gathering. I've had a go at the agenda [1] trying to keep it to max 4 or 5 sessions per day with some breaks. Please review the slot assigned for your session at [1]. If that time is not ok then please let me know as soon as possible and indicate if you want it later or earlier or on any other day. If you've decided the session no longer makes sense then also please tell me and we can move things around accordingly to finish earlier. I'd like to finalise the schedule by next Monday 12 April which is a week before PTG. We can and likely will make changes after this date but last minute changes are best avoided to allow folks to schedule their PTG attendance across projects. Thanks everybody for your help! Looking forward to interesting presentations and discussions as always regards, marios [1] https://etherpad.opendev.org/p/tripleo-ptg-xena

10 14