January 2021 - openstack-discuss - lists.openstack.org

[tripleo][ussuri][centos8] overcloud deploy fails with no valid host was found, GRUB2 cannot mount with regular user
by Ruslanas Gžibovskis 23 Jan '21

23 Jan '21

Hi all, I am trying to build some cloud again and failing with [1]. I think this is a most critical line. It fails during GRUB2 deployment on overcloud image, I believe main error message is: mount: only root can do that. I used the following steps to create image: cp -ar /etc/yum.repos.d repos # enable: repos/CentOS-HA.repo sed -i "s/enabled=0/enabled=1/g" repos/CentOS-Linux-HighAvailability.repo sed -i "s/gpgcheck=1/gpgcheck=0/g" repos/*repo export DIB_YUM_REPO_CONF="$(ls $(pwd)/repos/*repo)" export STABLE_RELEASE="ussuri" source /home/stack/stackrc mkdir /home/stack/images cd /home/stack/images openstack overcloud image build --config-file /home/stack/overcloud-images-python3.yaml openstack overcloud image upload --update-existing # openstack overcloud node configure --all-manageable overcloud-images-python3.yaml file content can be found here [2], just added additional packages, such as tcpdump, iperf, iptraf and so on... And steps from link [3] to set root pass to troubleshoot if needed. any thoughts? Maybe there were some changes recently (from 22 of December) PRevious images from there. Thank you for your thoughts and attention. [1] http://paste.openstack.org/show/GDYriAXxQniZTPQGJGbH/ [2] http://paste.openstack.org/show/2tkVFdwSZ0QMjoJKmOrm/ [3] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16… -- Ruslanas Gžibovskis +370 6030 7030

2 5

[SIG] [all] [TC] [Automation] [Cloud Research] [k8s] [Containers] [Multi Arch] [Packaging] [PowerVMStacker] [Public Cloud] [Resource Management] Updates Required?
by Kendall Nelson 22 Jan '21

22 Jan '21

Hello Everyone! I don't know if any of you have looked at the sigs governance[0] site lately, but there are a number of SIGs that seem to have out of date statuses and/or chairs listed that are no longer active in the community. >From what I can tell, the following list of SIGs could maybe use some updating. - Automation - Cloud Research - Containers - k8s - Multi Arch - Packaging - PowerVMStacker - Public Cloud - Resource Management I have created an etherpad[1] with all the SIGs for more cohesive discussion on changes. Please make comments there! I am happy to push the updates if things need to change; I just need to know what to change it to. Tangentially related, kudos Rico for chairing the most SIGs by far! -Kendall Nelson (diablo_rojo) [0] https://governance.openstack.org/sigs/ [1] https://etherpad.opendev.org/p/2021-SIG-Updates

1 0

Re: [nova] unit testing on ppc64le
by aditi Dukle 21 Jan '21

21 Jan '21

2 3

[infra][ci] no more 3rd party CI test result in gerrit
by Lu, Lianhao 21 Jan '21

21 Jan '21

Hi All, I noticed that we're no longer be able to see the 3rd party CI test results in most of the projects in openstack gerrit, such as nova, neutron. But we can still see them in the ci-sandbox project. I'm wondering how to see those test results in gerrit now? Thanks! BR, -Lianhao

1 0

[tempest] extending python-tempestconf
by Szabolcs Tóth 21 Jan '21

21 Jan '21

Hej! The official tool named python-tempestconf has a parameter named --create, which allows to create the following resources: * CirrOS image (uploads the image based on the location defined with --image parameter), * Flavors (based on default values - DEFAULT_FLAVOR_RAM, DEFAULT_FLAVOR_RAM_ALT, DEFAULT_FLAVOR_DISK - which can be changed with --flavor-min-mem and --flavor-min-disk). In order to verify our specific installation with Tempest, we need to create the basic resources as * Flavors (with extra-spec parameters like hw:mem_page_size). * Networks (one for fixed_network_name and one for floating_network_name). * python-tempestconf is able to find an already existing network created with router:external flag and set it as value for floating_network_name. * Router and port (for routing traffic between internal and external networks). I would like to ask the following: * Is there any particular reason why the basic resource create functionality is limited to the image and flavor? * Are there any plans to extend the basic resource create functionality? * Ability to set extra parameters for the flavors. * Creating networks, routers and ports (based on a user inputs, which can be separate parameters or a specific file). Would the community accept contributions extending python-tempestconf into this direction? -- BR, Szabolcs

3 2

[All] copyright
by Kanevsky, Arkady 21 Jan '21

21 Jan '21

We have in a few places openstack copyright: # Copyright (c) 2020 OpenStack Foundation Should we use OpenInfra copyright going forward? Something like # Copyright (c) 20XX Open Infrastructure Foundation Thanks, Arkady Kanevsky, Ph.D. SP Chief Technologist & DE Dell EMC office of CTO Dell Inc. One Dell Way, MS PS2-91 Round Rock, TX 78682, USA Phone: 512 7204955

3 3

[barbican][release] Barbican deliverables questions
by Herve Beraud 21 Jan '21

21 Jan '21

Hi Barbican Team, The release team noticed some inconsistencies between the Barbican team's deliverables described in the governance’s reference and deliverables defined in the openstack/releases repo (c.f our related meeting topic [1]). First, we noticed that ansible-role-atos-hsm and ansible-role-thales-hsm are new barbican deliverables, and we would appreciate to know if we should plan to release them for Wallaby. The second thing is that barbican-ui (added in Oct 2019) was never released yet and was not ready yet for ussuri and victoria. maybe we should abandon this instead of waiting? Notice that Wallaby's milestone 2 is next week so it could be the good time to update all these things. Let us know your thoughts, we are waiting for your replies. Thanks for reading, [1] http://eavesdrop.openstack.org/irclogs/%23openstack-release/%23openstack-re… -- 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-----

2 2

[neutron]Drivers meeting agenda - 22.01.2021
by Slawek Kaplonski 21 Jan '21

21 Jan '21

Hi, Agenda for tomorrow's drivers meeting is at [1]. We have one RFE ready to discuss: - https://bugs.launchpad.net/neutron/+bug/1911126 We also have 2 new things which are now triaging, so please take a look at them if You have some time and ask questions if You have any: - https://bugs.launchpad.net/neutron/+bug/1912460 - https://bugs.launchpad.net/neutron/+bug/1911864 [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[Octavia] Network issue between amphora and health manager port
by CHANU ROMAIN 21 Jan '21

21 Jan '21

Hello, I try to install Octavia and i'm facing an issue with octavia-health- manager-listen-port interface. I use Openstack Ussuri on Ubuntu 18.04 with linuxbridge plugin I followed this procedure: https://docs.openstack.org/octavia/latest/install/install-ubuntu.html#insta… When I try to create my loadbalancer I got this error: WARNING octavia.amphorae.drivers.haproxy.rest_api_driver [-] Could not connect to instance. Retrying.: requests.exceptions.ConnectionError: HTTPSConnectionPool(host='10.244.3.243', port=9443): Max retries exceeded with url: // (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7fe1ec077080>: Failed to establish a new connection: [Errno 113] No route to host',)) From my interface "o-hm0" I cannot ping 10.244.3.243 but if I try to ping from DHCP namespace it works fine. I think the problem is my "octavia-health-manager-listen-port" port appears "DOWN" when I list every ports. I figured out than Neutron didnt update iptables rules, probably because the interface is DOWN but if I add these rules: iptables -A neutron-linuxbri-FORWARD -m physdev --physdev-out o-bhm0 -- physdev-is-bridged -m comment --comment "Accept all packets when port is trusted." -j ACCEPT iptables -A neutron-linuxbri-FORWARD -m physdev --physdev-in o-bhm0 -- physdev-is-bridged -m comment --comment "Accept all packets when port is trusted." -j ACCEPT Amphora is able to communication with health manager port then the loadbalancer becomes UP but now I got this WARNING: 2021-01-21 15:27:21.230 2999834 WARNING octavia.amphorae.drivers.health.heartbeat_udp [-] Health Manager experienced an exception processing a heartbeat message from ('10.244.3.243', 30684). Ignoring this packet. Exception: 'NoneType' object has no attribute 'encode' I guess it's all about the port being stuck in DOWN state. Do you have any input how to configure this port? Best regards, Romain

2 1

[monasca][release] Abandoning monasca-ceilometer and monasca-log-api?
by Herve Beraud 21 Jan '21

21 Jan '21

Dear Monasca team, The release team noticed an inconsistency between the Monasca team's deliverables described in the governance’s reference and deliverables defined in the openstack/releases repo (c.f our related meeting topic [1]). Indeed, monasca-ceilometer and monasca-log-api were released in train but not released in ussuri nor victoria. Do you think that they should be deprecated (abandoned) in governance? Notice that Wallaby's milestone 2 is next week so maybe it could be a good time to update this. Let us know your thoughts, we are waiting for your replies. Thanks for reading, [1] http://eavesdrop.openstack.org/irclogs/%23openstack-release/%23openstack-re… -- 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 4

[tc] weekly meeting
by Mohammed Naser 21 Jan '21

21 Jan '21

Hi everyone, Here’s the agenda for our weekly TC meeting. It will happen tomorrow (Thursday the 21st) at 1500 UTC in #openstack-tc and I will be your chair. If you can’t attend, please put your name in the “Apologies for Absence” section https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting # ACTIVE INITIATIVES * Follow up on past action items * Audit SIG list and chairs (diablo_rojo) * Add Resolution of TC stance on the OpenStackClient (diablo_rojo) - https://review.opendev.org/c/openstack/governance/+/759904 * Gate performance and heavy job configs (dansmith) - http://paste.openstack.org/show/jD6kAP9tHk7PZr2nhv8h/ * Audit and clean-up tags (gmann) - 'supports-api-interoperability' tag - Manila request: https://review.opendev.org/c/openstack/governance/+/770859 * infra-core team (mnaser / diablo_rojo) - Stepping up to help with review load that will be new to everyone * Dropping lower-constraints testing from all projects (gmann) - http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019672.… * Decide on OpenSUSE in testing runtime (gmann) - https://review.opendev.org/c/openstack/devstack/+/769884 * Define 2021 upstream investment opportunities - https://review.opendev.org/c/openstack/governance/+/771707 * Open Reviews - https://review.opendev.org/q/project:openstack/governance+is:open Thank you Mohammed -- Mohammed Naser VEXXHOST, Inc.

1 0

[OpenStackSDK][release] Abandoning js-openstack-lib?
by Herve Beraud 21 Jan '21

21 Jan '21

Dear OpenStackSDK team, The release team noticed an inconsistency between the OpenStackSDK team's deliverables described in the governance’s reference and deliverables defined in the openstack/releases repo (c.f our related meeting topic [1]). Indeed, js-openstack-lib (added January 9, 2020) was never released yet and was not ready for ussuri or victoria. maybe we should abandon this instead of waiting? Notice that Wallaby's milestone 2 is next week so maybe it could be a good time to update this. Let us know your thoughts, we are waiting for your replies. Thanks for reading, [1] http://eavesdrop.openstack.org/irclogs/%23openstack-release/%23openstack-re… -- 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-----

2 2

[all][tc][goals] Migrate RBAC Policy Format from JSON to YAML: Week R-16 Update
by Ghanshyam Mann 20 Jan '21

20 Jan '21

Hello Everyone, Please find the week's R-16 updates on 'Migrate RBAC Policy Format from JSON to YAML' community-wide goals. Tracking: https://etherpad.opendev.org/p/migrate-policy-format-from-json-to-yaml Gerrit Topic: https://review.opendev.org/q/topic:%22policy-json-to-yaml%22+(status:open%2… Progress: ======= * Projects completed: 5 * Projects left to merge the patches: 25 * Projects left to push the patches: 2 (horizon and Openstackansible) * Projects do not need any work: 17 Updates: ======= * I have pushed the patches for all the required service projects. ** Because of many services gate is already broken for lower constraints job, these patches might not be green in the test results. I request projects to fix the gate so that we can merge this goal work before m-2. ** There are many project tests where CONF object was not fully initialized before the policy is init. This was working till now as policy init did not use the CONF object but oslo_policy 3.6.0 onwards it needs fully initialized CONF object during init only. ** Aodh work for this goal is blocked because it needs oslo_policy 3.6.0 but gnocchi is capped for oslo_policy 3.4.0 [1] - https://review.opendev.org/c/openstack/aodh/+/768499 * Horizon and Openstackansible work is pending to use/deploy the YAML formatted policy file. I will start exploring this next week or so. [1] https://github.com/gnocchixyz/gnocchi/blob/e19fda590c7f7f07f1df0ba93177df07… Merry Christmas and Happy Holidays! -gmann

6 11

[cinder] wallaby new driver status
by Brian Rosmaita 20 Jan '21

20 Jan '21

At today's Cinder meeting [0] we discussed the unmerged proposed drivers (3 volume drivers, 1 backup driver) in light of tomorrow's new driver merge deadline. Here's a summary of what we decided: 1. s3 cinder backup driver https://review.opendev.org/c/openstack/cinder/+/746561 The code looks basically OK but the driver hasn't been independently tested. There's a proposed CI job but it currently isn't passing. ==> plan: aim for two +2s on the patch before the merge deadline, but hold off on merging until we have confirmation that the driver works, hopefully but the CI working by next week (Thursday 28 January). 2. TOYOU ACS5000 driver https://review.opendev.org/c/openstack/cinder/+/767290/ Code is looking good and they've been good about quickly revising patches. The CI is running and driver is passing tempest and cinder-tempest-plugin tests, though it's not reporting reliably on patches. They've agreed to get their CI responding properly by milestone-3. ==> plan: the requested revisions haven't been major, so this is looking good for tomorrow's deadline. We anticipate that the CI situation will be corrected by M-3. 3. Ceph iSCSI driver https://review.opendev.org/c/openstack/cinder/+/662829 Code is looking good but the CI isn't passing yet. ==> plan: this is an important community driver so we're extending the deadline two weeks to 5 February. 4. Kioxia Kumoscale driver (and brick changes) https://review.opendev.org/c/openstack/cinder/+/768574 https://review.opendev.org/c/openstack/os-brick/+/768575 https://review.opendev.org/c/openstack/os-brick/+/768576 Kioxia reports that their CI is up though it's not reporting yet. This is a large change and the cinder team review bandwidth has been low this cycle, but with the other drivers (mostly) done at this point, we should be able to get faster reviews on these. ==> plan: new driver merge extension to 8 Feb, that is, code merged and CI running and reporting by that date to be included in wallaby. cheers, brian [0] http://eavesdrop.openstack.org/meetings/cinder/2021/cinder.2021-01-20-14.00…

1 0

Requesting help with OpenStack configuration files
by Bessghaier, Narjes 20 Jan '21

20 Jan '21

Dear OpenStack team, I’m a Ph.D. student in software engineering at the ETS Montreal, University of Quebec working on the quality and configuration of web-based software systems. I’m particularly interested in analyzing configuration files from different OpenStack files. One of the main challenges I am currently facing is the proper identification of configuration files. I’m mostly confused between the python files used for production and the python files used for configuration. I am kindly requesting your precious help with the following questions: 1- How to distinguish between python files used for configuration and python files used for production? It will be very helpful if there are some configuration-based patterns (eg, textual patterns or expressions) that we can find in python files to help us distinguish between source code and configuration files? 2- Certain python files use the oslo_config to access and define configuration options. Could "all" these python files be considered as configuration files? For example, the following python file of the keystone project: keystone/keystone/conf/auth.py, is it considered a source code or configuration file? 3- Why are there different source code and configuration repositories for OpenStack projects (eg, nova and puppet-nova)? For instance, does the OpenStack-nova service have some configuration files in its repository and have the puppet-nova as a separate configuration repository as well? Thank you very much in advance for your time and your help! Kind regards, Narjes Bessghaier Narjes Bessghaier Ph.D student in Software Engineering École de Technologie Supérieure (ETS)| University of Quebec Montreal, Canada narjes.bessghaier.1(a)ens.etsmtl.ca<mailto:yasmine.makroum.1@ens.etsmtl.ca>

3 4

[masakari] Masakari Team Meeting - the schedule
by Radosław Piliszek 20 Jan '21

20 Jan '21

Hello, Folks! I have realised the Masakari Team Meeting is to run on even weeks [1]. However, anyone who created the meeting record in their calendar (including me) has likely gotten the meeting schedule in odd weeks this year (because last year finished with an odd week and obviously numbering also starts on odd: the 1). So I have run the first meeting this year the previous week but someone came for the meeting this week. :-) According to the "new wrong" schedule, the next meeting would be on Jan 19, but according to the "proper" one it would be on Jan 26. I am available both weeks the same so can run either term (or both as well, why not). The question is whether we don't want to simply move to the weekly meeting schedule. We usually don't have much to discuss but it might be less confusing and a better way to form a habit if we met every week. Please let me know your thoughts. [1] http://eavesdrop.openstack.org/#Masakari_Team_Meeting -yoctozepto

2 2

[nova] Selecting PCI devices by their addresses
by Mauricio Tavares 20 Jan '21

20 Jan '21

Stupid question of the day: if I am not mistaken, I can ask nova[1] which pci/pcie devices it knows and where they are. And it will reply with the PCI address for each device it knows of. But, when I want to create flavours so I can create (libvirt-based) instances using them, I cannot tie an alias to a specific pci address; all I can do is say "this pci_alias is for all the pci devices with this vendor_id and product_id that I whitelisted already"[2]. Since libvirt allows me to feed a vm guest the exact pci device I want, could anyone point out which obvious step I am missing here? [1] https://wiki.openstack.org/wiki/Pci-api-support [2] https://docs.openstack.org/nova/latest/admin/pci-passthrough.html#configure…

2 1

[tc] weekly meeting summary (Jan 14)
by Mohammed Naser 20 Jan '21

20 Jan '21

Hi everyone, Here’s a summary of what happened in our TC weekly meeting last Thursday, Jan 14th. # ATTENDEES (LINES SAID) 1. mnaser (123) 2. gmann (56) 3. fungi (31) 4. rosmaita (19) 5. ricolin (11) 6. dansmith (9) 7. jungleboyj (8) 8. knikolla (6) 9. clarkb (3) 10. apevec (2) 11. slaweq (2) 12. belmoreira (1) # MEETING SUMMARY 1. Rollcall 2. Follow up on past action items - DONE: mnaser submit a patch to officially list no community goals for X cycle - DONE: diablo_rojo update resolution for tc stance on osc - IN PROGRESS: diablo_rojo complete retirement of karbor - ALMOST DONE - TBD: diablo_rojo reach out to SIGs/ML and start auditing states of SIGs - TBD: gmann continue to audit tags + outreach to community to apply for them 3. Write a proposed goal for X about stabilization/cooldown This topic mostly continues to live inside gerrit, so ti will be removed from the agenda. 4. Audit SIG list and chairs (diablo_rojo) No progress update, we'll keep an action item to keep up with it. 5. Annual report suggestions (diablo_rojo) Topic to be removed from the agenda as this is getting drafted already. 6. Add Resolution of TC stance on the OpenStackClient (diablo_rojo) dansmith will update osc change to include ci/docs commentary. 7. Audit and clean-up tags (gmann) gmann bumped the email with PTL tag for API interoperability tag, we’ll see how many projects start applying it. 8. infra-core additions (was Farewell Andreas) (diablo_rojo) The reposition is quiet for the moment and there is no backlog yet. We are bringing this up at the OpenDev infrastructure meeting on Tuesday the 19th, mnaser will add openstack/infra-core as a discussion topic in the OpenDev meeting. 9. Dropping lower-constraints testing from all projects (gmann) This is something projects asked TC for consensus and direction for all projects. l-c testing is not part of PTI but there should exist some direction for consistency testing and providing a lower bound to package maintainers. A few projects already started dropping l-c job, and it seems that our current l-c were not exactly testing in a valid way. Also, most testing (except for the l-c job) is being done with versions close to the upper-constraints. We will keep this an open topic for next week. 10. Decide on OpenSUSE in testing runtime (gmann) OpenSUSE distro job is broken for a month and DevStack team is approaching removing it as there is no investment from the company or the community. It was discussed to make the governance change and if that goes through the DevStack one, it will be merged. We’ll have an ML before and after moving testing/governance change, gmann will update supported distros to drop OpenSUSE. # ACTION ITEMS 1. diablo_rojo complete retirement of karbor 2. mnaser to remove proposed goal topic from agenda 3. diablo_rojo reach out to SIGs/ML and start auditing states of SIGs 4. mnaser remove annual report suggestions from agenda 5. dansmith update osc change to include ci/docs commentary 6. mnaser add openstack/infra-core as discussion topic in opendev meeting 7. gmann follow-up with zigo if debian uses l-c 8. gmann update supported distros to drop opensuse To read the full logs of the meeting, please refer to http://eavesdrop.openstack.org/meetings/tc/2021/tc.2021-01-14-15.00.log.html -- Mohammed Naser VEXXHOST, Inc.

1 0

[$nova] [$horizon] [$nova-scheduler] [$heat]
by Nagaraj Akkina 20 Jan '21

20 Jan '21

I think we have a big problem, scheduler is able to allocate more memory than actual physical memory in the compute node, the same statistics are also there in database. For example : if we have a physical memory of 125GB in a node, the total memory allocated to all the instances(virsh dommemstat of all vms) in that host is more than physical memory say around 147GB, being ram_allocation_ratio defined as 1 and reserve_host_memory_mb defined as required. How can nova allocates more memory than actual? Statistics from database +-----------+----------------+-------------+----------------------+ | memory_mb | memory_mb_used | free_ram_mb | ram_allocation_ratio | +-----------+----------------+-------------+----------------------+ | 128897 | 154624 | -25727 | 1 | +-----------+----------------+-------------+----------------------+ we are using openstack stein Regards, Akkina

2 1

[qa][release] Abandoning openstack-tempest-skiplist?
by Herve Beraud 20 Jan '21

20 Jan '21

Dear QA team, The release team noticed an inconsistency between the QA team's deliverables described in the governance’s reference and deliverables defined in the openstack/releases repo (c.f our related meeting topic [1]). Indeed, openstack-tempest-skiplist (added Mar 20, 2020) was never released yet, was not ready yet for ussuri and victoria. maybe we should abandon this instead of waiting? Notice that Wallaby's milestone 2 is next week so maybe it could be a good time to update this. Let us know your thoughts, we are waiting for your replies. Thanks for reading, [1] http://eavesdrop.openstack.org/irclogs/%23openstack-release/%23openstack-re… -- 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 6

docs about ironic-inspector
by Ankele zhang 20 Jan '21

20 Jan '21

Hi, I have an rocky OpenStack platform, and I need openstack-ironic-inspector to inspect my baremetal node, but the documentation on the websit https://docs.openstack.org/ironic/rocky/admin/inspection.html is too concise, without a detailed configuration process. I need a link to documentation for detailed ironic-inspector configuration and usage. Looking forward to your help. Ankele

2 1

[TripleO] moving stable/rocky for tripleo repos to unmaintained (+ then EOL) OK?
by Marios Andreou 19 Jan '21

19 Jan '21

Hello TripleO I would like to propose that we move all tripleo stable/rocky repos [1] to "unmaintained", with a view to tagging as end-of-life in due course. This will allow us to focus our efforts on keeping the check and gate queues green and continue to deliver weekly promotions for the more recent and active stable/* branches train ussuri victoria and master. The stable/rocky repos have not had much action in the last few months - I collected some info at [2] about the most recent stable/rocky commits for each of the tripleo repos. For many of those there are no commits in the last 6 months and for some even longer. The tripleo stable/rocky repos were tagged as "extended maintenance" (rocky-em) [2] in April 2020 with [3]. We have already reduced our CI commitment for rocky - these [4] are the current check/gate jobs and these [5] are the jobs that run for promotion to current-tripleo. However maintaining this doesn’t make sense if we are not even using it e.g. merging things into tripleo-* stable/rocky. Please raise your objections or any other comments or thoughts about this. Unless there are any blockers raised here, the plan is to put this into motion early in January. One still unanswered question I have is that since there is no ‘unmaintained’ tag, in the same way as we have the <release>-em or <release-eol> for extended maintenance and end-of-life, do we simply _declare_ that the repos are unmaintained? Then after a period of “0 to 6 months” per [6] we can tag the tripleo repos with rocky-eol. If any one reading this knows please tell us! Thanks for reading! regards, marios [1] https://releases.openstack.org/teams/tripleo.html#rocky [2] http://paste.openstack.org/raw/800464/ [3] https://review.opendev.org/c/openstack/releases/+/709912 [4] http://dashboard-ci.tripleo.org/d/3-DYSmOGk/jobs-exploration?orgId=1&var-in… [5] http://dashboard-ci.tripleo.org/d/3-DYSmOGk/jobs-exploration?orgId=1&fullsc… [6] https://docs.openstack.org/project-team-guide/stable-branches.html#maintena…

3 5

Ironic Midcycle - Three time windows next week
by Julia Kreger 19 Jan '21

19 Jan '21

Greetings everyone, Given we have a global community, I think the statement "Scheduling is hard" is definitely one of those things that we've all had to learn over the years. Luckily we have some time slots where many of the participants have indicated they will be able to attend. From that, it appears that the following times seem in terms of trying to cover time zones as well as including participants that have expressed interest. Monday January 25th @ 5PM - 6PM UTC / 9AM - 10AM US Pacific Tuesday January 26th @ 8 PM - 9PM UTC / 12:00 PM - 1 PM Pacific Wednesday January 27th @ 3PM - 4PM UTC / 7AM - 8AM US Pacific We will meet in MeetPad[0], and the etherpad is still open if more topics wish to be added, although we cannot guarantee we will get to them. I've also tried to spread them up across days in order to try and make efficient use of the time. Thanks everyone, and see you there. -Julia [0]: https://meetpad.opendev.org/ironic [1]: https://etherpad.opendev.org/p/ironic-wallaby-midcycle

1 0

Openstack integration with NSX-T
by ali ali 18 Jan '21

18 Jan '21

Hi. I use Openstack train version and I want to integrate openstack with nsx-t. I only found the following documentation. https://docs.vmware.com/en/VMware-NSX-T-Data-Center/2.5/nsxt-openstack-plug… and at the start of integration, I install, following packages apt install python-vmware-nsxlib openstack-vmware-nsx python-neutron-fwaas outputs: E: Unable to locate package openstack-vmware-nsx The following packages have unmet dependencies: python-neutron-fwaas : Depends: python-neutron (>= 2:12.0.0~) but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). when I checked there are no python-neutron packages but there was a python3-neutron package. I don't know what to do with this problem. I think if I delete python3-neutron and install python-neutron, everything will crash and mess up. is it basicly possible to integrate openstack train or ussuri or victoryia with nsx-t?

3 2

[tc] weekly update
by Mohammed Naser 18 Jan '21

18 Jan '21

Hi everyone, Here’s an update on what happened in the OpenStack TC this week. You can get more information by checking for changes in openstack/governance repository. # Patches ## Open Reviews - Setting Ke Chen as Watcher's PTL https://review.opendev.org/c/openstack/governance/+/770913 - Drop openSUSE from commonly tested distro list https://review.opendev.org/c/openstack/governance/+/770855 - [manila] add assert:supports-api-interoperability https://review.opendev.org/c/openstack/governance/+/770859 - Add Resolution of TC stance on the OpenStackClient https://review.opendev.org/c/openstack/governance/+/759904 - Define Xena release testing runtime https://review.opendev.org/c/openstack/governance/+/770860 - Cool-down cycle goal https://review.opendev.org/c/openstack/governance/+/770616 - Remove Karbor project team https://review.opendev.org/c/openstack/governance/+/767056 - WIP NO MERGE Move os-*-config to Heat project governance https://review.opendev.org/c/openstack/governance/+/770285 ## Project Updates - Setting Xinran Wang as Cyborg's PTL https://review.opendev.org/c/openstack/governance/+/770075 - Add glance-tempest-plugin to Glance https://review.opendev.org/c/openstack/governance/+/767666 - molteniron does not make releases https://review.opendev.org/c/openstack/governance/+/769805 ## General Changes - Add link to Xena announcement https://review.opendev.org/c/openstack/governance/+/769620 - Add doc/requirements https://review.opendev.org/c/openstack/governance/+/769696 # Other Reminders - Our next [TC] Weekly meeting is scheduled for January 21st at 1500 UTC. If you would like to add topics for discussion, please go to https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting and fill out your suggestions by Wednesday, January 20th, at 2100 UTC. Thanks for reading! Mohammed & Kendall -- Mohammed Naser VEXXHOST, Inc.

1 0