September 2022 - openstack-discuss

[horizon] instance filtering dropdown default
by John Ratliff 07 Sep '22

07 Sep '22

When I load certain pages in horizon, like the compute instances page, the default filter is "Instance ID". How can I change the default to "Instance Name" instead? Thanks. --John Ratliff

1 0

Horizon
by Atharva Dhanwate 06 Sep '22

06 Sep '22

4 3

[neutron] Bug deputy report for week of August 29th
by Brian Haley 06 Sep '22

06 Sep '22

Hi, I was Neutron bug deputy last week. Below is a short summary about the reported bugs. BTW, you don't have to wait for me to be deputy to file all your bugs :) -Brian Critical bugs ------------- * https://bugs.launchpad.net/neutron/+bug/1988026 - Neutron should not create security group with project==None - Talked to Security Response Team and they decided to add a tracker to it since the quota system doesn't seem to limit how many random default security groups one can create. - https://review.opendev.org/c/openstack/neutron/+/855580 High bugs --------- * https://bugs.launchpad.net/neutron/+bug/1988037 - Neutron does not find an existing route - https://review.opendev.org/c/openstack/neutron/+/854986 * https://bugs.launchpad.net/neutron/+bug/1988296 - neutron-lib pep8 CI failing with pylint==2.15.0 - https://review.opendev.org/c/openstack/neutron-lib/+/855061 Medium bugs ----------- * https://bugs.launchpad.net/neutron/+bug/1988069 - neutron-dhcp-agent fails when small tenant network mtu is set - Could not reproduce issue reported with MTU as 70 for network, only saw that instances could not do DHCP with it so small. Looks like a potential kernel bug since this works on later versions. * https://bugs.launchpad.net/neutron/+bug/1988199 - https://review.opendev.org/c/openstack/neutron/+/855257 * https://bugs.launchpad.net/neutron/+bug/1988220 - large unused dependency ncclient + paramiko in os-ken - Assigned to Rodolfo since he made change to remove nose https://review.opendev.org/c/openstack/os-ken/+/850631 - closed (won't-fix) as ncclient is required for os-ken, just wasn't explicitly called-out in requirements. * https://bugs.launchpad.net/neutron/+bug/1988549 - Trunk status is down after a live-migration - Arnau Verdaguer took ownership Low bugs -------- * https://bugs.launchpad.net/neutron/+bug/1988298 - [neutron-lib] "registry.has_resource_extenders" is the same as "resource_extend.has_resource_extenders" - Needs owner * https://bugs.launchpad.net/neutron/+bug/1586731 - restart neutron ovs agent will leave the fanout queue behind - Old bug re-opened - Partial patch posted, asked commenter to submit to master Misc bugs --------- * https://bugs.launchpad.net/neutron/+bug/1988281 - neutron dhcp agent state not consistent with real status - After a restart, the agent status is UP even though it is still doing a full-sync operation, is there a way to signify this status? See bug for further discussion. * https://bugs.launchpad.net/neutron/+bug/1988382 - L3 agent(agent_mode=dvr_snat) restart, fip namespace removed rfp-port, resulting in fip not connecting - Failure is seen in code from 2019, asked submitter to try tip of stable/victoria and reproduce since there have been fixed in this area since then. Wishlist bugs ------------- * https://bugs.launchpad.net/neutron/+bug/1988077 - Noisy neutron-openvswitch-agent service - There are some deployments that wanted more logging which is why the agent is more verbose. Will have to have a further discussion to see if there is a way to address concern of log being noisy, besides using more aggressive log rotation as suggested. * https://bugs.launchpad.net/neutron/+bug/1988188 - Create an automated tool to retrieve the needed OVS version depending on the OVN one - Suggested by Rodolfo to help improve gate dependencies. * https://bugs.launchpad.net/neutron/+bug/1988542 - [RFE] OVN support for vnic type virtio-forwarder - Will need to add to Drivers meeting agenda

1 0

Two containers fail
by Derek O keeffe 06 Sep '22

06 Sep '22

Hi, I recently successfully installed OSA and I am now trying to install it again from scratch with all the configuration changes I needed in place. Unfortunately this time around it is failing on setup_hosts.yml here: TASK [lxc_container_create : Create container (dir)] ******************************************************************ok: [infra1_memcached_container-b92f4db7 -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_rabbit_mq_container-d286a482 -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_utility_container-05f756fc -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_galera_container-5beef059 -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_aodh_container-639f5ad8 -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_neutron_server_container-f67e972d -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_horizon_container-dfeaa0dc -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_placement_container-350e4ede -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_heat_api_container-82cbd764 -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_nova_api_container-b30c38d1 -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_repo_container-f16e50a9 -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_ceilometer_central_container-910a888f -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_keystone_container-32dcd68b -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_gnocchi_container-30ccb451 -> infra1(CONTROLLER_IP_ADDRESS)]fatal: [infra1_cinder_api_container-840a18bb -> infra1(CONTROLLER_IP_ADDRESS)]: FAILED! => {"changed": false, "error": "Failed to start container [ infra1_cinder_api_container-840a18bb ]", "lxc_container": {"init_pid": -1, "interfaces": [], "ips": [], "name": "infra1_cinder_api_container-840a18bb", "state": "stopped"}, "msg": "The container [ infra1_cinder_api_container-840a18bb ] failed to start. Check to lxc is available and that the container is in a functional state.", "rc": 1}fatal: [infra1_glance_container-b50e16a6 -> infra1(CONTROLLER_IP_ADDRESS)]: FAILED! => {"changed": false, "error": "Failed to start container [ infra1_glance_container-b50e16a6 ]", "lxc_container": {"init_pid": -1, "interfaces": [], "ips": [], "name": "infra1_glance_container-b50e16a6", "state": "stopped"}, "msg": "The container [ infra1_glance_container-b50e16a6 ] failed to start. Check to lxc is available and that the container is in a functional state.", "rc": 1} I don't understand how 14 containers are fine (can be attached to and commands run through lxc-attach) and 2 containers are failing. I have a deploy host, controller and two computes all with a fresh install of Ubuntu 20.04. The bootstrap_ansible script ran fine on the deploy host and the setup_hosts playbook ran through fully as after the above it skipped cinder and glance containers every where else. Can anybody please point me in the direction of getting more info or a possible cause. Thanks in advance.

2 2

[Octavia][release] Requesting exception for python-octaviaclient
by Gregory Thiemonge 06 Sep '22

06 Sep '22

Hi Folks, I am requesting a Feature Freeze Exception for the release of python-octaviaclient for Zed. One patch [0] was merged at the end of last week in python-octaviaclient (we were waiting for the related feature to get merged in the octavia repo) and a new release (3.1.0) was proposed for Zed in the release repo [1], but it wasn't merged in time. We would like to get the approval for this new release so we could base the stable/zed branch on this new tag (we would need to update [2]). Thanks, Gregory [0] https://review.opendev.org/c/openstack/python-octaviaclient/+/664473 [1] https://review.opendev.org/c/openstack/releases/+/855675 [2] https://review.opendev.org/c/openstack/releases/+/855912

2 1

[election][tripleo] PTL Candidacy for Antelope cycle
by Rabi Mishra 06 Sep '22

06 Sep '22

Hi All, I would like to nominate myself for Antelope cycle TripleO PTL. As some of you would know, I have been part of the OpenStack community for a long time and have been a core contributor for TripleO and Heat. I have also served as Heat PTL for Ocata cycle. James has done a great job as PTL for the last few cycles. I would like to take the opportunity to thank him for all his effort and we all would agree that he needs a well deserved break. I am looking forward to take the opportunity to help the community to achieve some of the already planned goals and in-progress workstreams like standalone roles, multi-rhel and other challenges that come along the way. Also, as before, our focus would continue to be on review prioritization, in progress work streams and collaboration on common priorities. Regards, Rabi Mishra

9 8

[nova]How to confirm whether a arm64 node supports hardware acceleration for virtual machines
by 韩光宇 06 Sep '22

06 Sep '22

Hello, I see `egrep -c '(vmx|svm)' /proc/cpuinfo` in nova install documentation[1]. It can be used to confirm whether a node supports hardware acceleration for virtual machines on x86 architecture. But it is not applicable in the ARM architecture. Do we have an officially recommended method to confirm in ARM architecture? Thanks, Han Guangyu [1]https://docs.openstack.org/nova/latest/install/compute-install-rdo.html#f…

3 2

[oslo][relmgmt][taskflow][nova] fasteners.ReaderWriterLock and oslo.concurrency's fair lock is broken if used in eventlet
by Balazs Gibizer 06 Sep '22

06 Sep '22

Hi, It is hard to properly figure out which OpenStack project is affected exactly. But I want to give a heads up. If the following is true for your project then you are affected: * using eventlet and * using oslo.concurrency fair internal lock (external lock or non fair locks are not affected) or using fasteners.ReaderWriterLock directly. I know that nova is affected and based on code search taskflow is affected at least. The oslo.concurrency's fair lock uses fasteners.ReaderWriterLock[1]. The fasteners.ReaderWriterLock relies on threading.current_thread to identify a thread and decide if a thread already has a lock and therefore can reenter the lock. However in an eventlet monkey patched environment, a thread that is created with eventlet.spawn_n() or the patched threading.Thread() the threading.current_thread call does not return an eventlet unique ID. This causes that the lock can be reentered from multiple eventlets at the same time. We have 4 ways forward: 0) Fix eventlet. There is an open issue in eventlet[3] for this open since October 2021. Based on the ticket this direction does not seems to feasible. 1) Sean recently opened an issue[4] on fasteners to restore a previously existing workaround that could fix our issues. If an new fasteners lib is released with the workaround[5] then at least oslo.concurrency requirements needs to be bumped and a new oslo release is pushed. 2) If the fasteners' maintainer does not accept [4][5] in time then I have an oslo.concurrency patch[6] that implements a workaround in oslo. This also requires a new olso.concurrency release. Also this means that projects that are using fasteners.ReaderWriterLock directly need to re-implement the fix locally. 3) If all odds fails I have a nova only patch[7] that implements the workaround locally in nova. Note that this issue is present in stable/yoga and on master. On stable/xena we uses fasteners < 0.15.0 which is not affected. Cheers, gibi [1] https://github.com/openstack/oslo.concurrency/blob/052b2f23572900601b0f4138… [2] https://bugs.launchpad.net/oslo.concurrency/+bug/1988311 [3] https://github.com/eventlet/eventlet/issues/731 [4] https://github.com/harlowja/fasteners/issues/96 [5] https://github.com/harlowja/fasteners/pull/97 [6] https://review.opendev.org/q/topic:bug/1988311+project:openstack/oslo.concu… [7] https://review.opendev.org/q/topic:bug/1988311+project:openstack/nova

2 2

[ops][largescale-sig] rabbitmq and the durability of reply_ queues
by Felix Hüttner 06 Sep '22

06 Sep '22

Hi everyone, the largescale-sig currently recommends the following rabbitmq policy [1]: '^(?!(amq\.)|(.*_fanout_)|(reply_)).*'. If I found the history of this setting correctly, it resulted from this mailinglist thread [2] which came to the conclusion: > * use durable-queue and replication for long-running queues/exchanges > * use non-durable-queue without replication for short (fanout, reply_) queues However I am unsure if reply_ queues are actually shorted lived than the "long-running" ones. If we take the example of the cinder-scheduler we have the following queues: * cinder-scheduler: Tied to the lifetime of the whole cinder-scheduler cluster; currently durable + replicated * cinder-scheduler.myhostname: Tied to the lifetime of the cinder-scheduler service, but not removed when the service stops; currently durable + replicated * cinder-scheduler_fanout_somerandomid: Tied to the lifetime of the cinder-scheduler service, but removed when the service stops; currently neither durable nor replicated * reply_somerandomid: Tied to the lifetime of the cinder-scheduler service, but removed when the service stops; currently neither durable nor replicated If I read got all of the above correctly then reply_ and fanout queues are actually not shorter lived than the normal queue to send requests to that service. The only difference is that we remove them when the service itself stops. Therefor I want to propose the question if we should not also make these queues durable and replicated. Thank you [1]: https://docs.openstack.org/large-scale/other/rabbitmq.html#pattern [2]: https://lists.openstack.org/pipermail/openstack-discuss/2020-August/016562.… -- Felix Huettner Diese E Mail enthält möglicherweise vertrauliche Inhalte und ist nur für die Verwertung durch den vorgesehenen Empfänger bestimmt. Sollten Sie nicht der vorgesehene Empfänger sein, setzen Sie den Absender bitte unverzüglich in Kenntnis und löschen diese E Mail. Hinweise zum Datenschutz finden Sie hier<https://www.datenschutz.schwarz>.

2 2

[puppet] Gate blocker: enabling neutron-ovn-metadata-agent consistently fails in CentOS Stream 9
by Takashi Kajinami 06 Sep '22

06 Sep '22

Hello, Currently we are facing a problem with integration jobs with ml2+ovn in CentOS Stream 9 ( puppet-openstack-integration-7-scenario00[35]-tempest-centos-9-stream ) and these jobs are consistently failing. Details can be found in https://launchpad.net/bugs/1988552 . I've already reported the issue to RDO and CentOS Stream to get their help while I'm also implementing a temporary workaround. https://review.opendev.org/c/openstack/puppet-openstack-integration/+/855617 Please avoid rechecking/approving patches until these jobs are fixed. Thank you, Takashi

1 1

Re: Secret getPayload() openstack4j
by Srinivasan T 06 Sep '22

06 Sep '22

Hi, Does anyone have any idea on this? >From the REST API documentation, it seems GET /v1/secret/{uuid} may not fetch the payload and we need to use a different endpoint GET /v1/secret/{uuid}/payload . Is there any equivalent Java API (openstack4j) for this? Regards, Srini On Mon, Sep 5, 2022 at 11:08 PM Srinivasan T <tsrini.alr(a)gmail.com> wrote: > Thanks Artem for the response. > > I face the same issue when using the below version as well (snippet from > pom.xml), > > <modelVersion>4.0.0</modelVersion> > <artifactId>openstack4j-core</artifactId> > <name>OpenStack4j Core</name> > <description>OpenStack Java API</description> > <url>http://github.com/openstack4j/openstack4j/</url> > > Regards, > Srini > > On Mon, Sep 5, 2022 at 9:48 PM Artem Goncharov <artem.goncharov(a)gmail.com> > wrote: > >> Hi, >> >> The library is not an official OpenStack delivery. I guess nobody here >> would be able to give you proper suggestion. Moreover it does not look like >> being actively maintained. >> >> Regards, >> Artem >> >> On 5. Sep 2022, at 18:03, Srinivasan T <tsrini.alr(a)gmail.com> wrote: >> >> Hi, >> >> I'm unable to get the secret's payload from openstack4j, it always >> returns null. >> >> Secret secret = os.barbican().secrets().get("19cbc4e8-cd06-450b-aa5d-2a4d20bf7d60"); >> secret.getPayload(); //Always returns null >> >> The same works when using the OpenStack CLI, >> >> openstack secret get --payload_content_type 'application/octet-stream' --file secret-payload http://x.x.x.x:9311/v1/secrets/19cbc4e8-cd06-450b-aa5d-2a4d20bf7d60 >> >> I'm using the below OpenStack4j version, >> >> Bundle-Name: OpenStack4j Core >> >> Bundle-Version: 3.6.0 >> >> OpenStack is in Queens version. >> >> Let me know if someone can help on this. >> Regards, >> Srini >> >> >>

1 0

Kolla-ansible all-in-one and Hyper Converged solution
by KK CHN 06 Sep '22

06 Sep '22

Hi, [1 ] I am aiming for a prototype of HCI on a DELL ( R650 2 CPU and 40 cores . 2.4 TB) server machine. The Operating System choice is Debian 10. [2] Right now I am successful in Kolla-ansible all-in-one installation of Wallaby/stable on a Debian 10 Virtual machine with the default configs enabled as in the documentation " https://docs.openstack.org/project-deploy-guide/kolla-ansible/wallaby/uicks… " in Virtualenv setup. Able to get the horizon dashboard with the default services enabled and created and tested the cirros VM launching .. working fine. [3 ] I have to repeat the same all-in-one deployment on the physical machine as in [1] with the default configs and then convert it as an HCI node. What all features do I need to configure / enable in all-in-on / globals.yml to convert this box as a working HCI node ? Any hints / directives for the essential configurations needed for this server box to convert it as an HCI node are most welcome. kindly shed some light on this and any reference documents/URLs to do this ? Thank you, Krish

5 5

Microstack - VM networking & installation probs
by Tim Kahlke 06 Sep '22

06 Sep '22

Hi, I tried to install microstack 245 via Canonical and am running into the “old” VM-can’t-connect-external-network problem. OS: Ubuntu 20.04 Microstack v245 Install seems to have worked ok using sudo snap install microstack --beta. However, journalctl -xe shows ovsdb-server[83528]: ovs|26322|socket_util|ERR|6642:0.0.0.0: bind: Address already in use But not sure if that’s related or not. Network setup is the default, i.e., external 10.20.20.0/24 and internal 192.168.1.0/24. From the host machine I can ping the VMs and vice versa, but I can’t get past the host from the VM. I tried to apply some of the solutions I found on the web, so far without success. This one seems to work for people but my microstack doesn’t seem to have the ovs-vsctl command anywhere. Any suggestions would be much appreciated. Tim

2 1

[manila] LVM shares are unmounted on reboot
by Vaibhav 06 Sep '22

06 Sep '22

Dear All, One of the host running Manila-share service has rebooted. After the reboot the LVMs are not mounted on the Manila mount points. I use LVM Driver with DHSS=False. default_share_type = default_share_type share_name_template = manila-%s rootwrap_config = /etc/manila/rootwrap.conf api_paste_config = /etc/manila/api-paste.ini auth_strategy = keystone my_ip=192.168.82.2 enabled_share_backends = lvm enabled_share_protocols = NFS state_path=/var/lib/manila [lvm] share_backend_name = LVM share_driver = manila.share.drivers.lvm.LVMShareDriver driver_handles_share_servers = False lvm_share_volume_group = VGZunManila lvm_share_export_ips = 192.168.82.2 lvm_share_export_root = $state_path/mnt After the reboot LVMs are there but they are mounted on their respective share location. Any way to solve this and this to be done automatically? Regards, Vaibhav

2 2

[all][elections][ptl][tc] Combined PTL/TC antelope cycle Election Nominations Last Days - FINAL REMINDER
by Amy Marrich 06 Sep '22

06 Sep '22

This is your last reminder for the election, I know the US , CA, and a few other countries are on holiday today. Please also read Jeremy's early email about the TC seats and governance. Thank, Amy\ ----------------------------------------------- A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Sep 07, 2022 23:45 UTC. If you want to stand for election, don't delay, follow the instructions at [1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. Election statistics[2]: Nominations started @ 2022-08-24 23:45:00 UTC Nominations end @ 2022-09-07 23:45:00 UTC Nominations duration : 14 days, 0:00:00 Nominations remaining : 2 days, 4:16:33 Nominations progress : 84.44% --------------------------------------------------- Projects[1] : 52 Projects with candidates : 35 ( 67.31%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 17 (Adjutant Barbican Keystone Masakari Mistral OpenStackSDK OpenStack_Charms Openstack_Chef Oslo Release_Management Requirements Sahara Senlin Skyline Swift Venus Zun) =================================================== Stats gathered @ 2022-09-05 19:28:27 UTC This means that with approximately 2 days left, 17 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. Thank you, [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.openstack.org/#/q/is:open+project:openstack/election have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for…

1 0

[neutron] Team meeting on Sept. 6 cancelled
by Lajos Katona 05 Sep '22

05 Sep '22

Hi, Sorry for late mail, but tomorrow I can't drive the team meeting, so I have to cancel it. I will be otherwise available tomorrow (except around the meeting time), so you can reach me on neutron channel for example. Lajos Katona (lajoskatona)

1 0

Error During installation devstack ModuleNotFoundError: No module named 'neutron'
by mahdi n 05 Sep '22

05 Sep '22

I was installing DevStack on Ubuntu 20.04 when I encountered this error It says that the Neutron module was not found while neutron is installed ++lib/neutron_plugins/ovn_agent:filter_network_api_extensions:439 > /usr/local/bin/python3.8 -c 'from neutron.common.ovn import extensions ;\ > > print(",".join(extensions.ML2_SUPPORTED_API_EXTENSIONS)) > ' > Traceback (most recent call last): > > File "<string>", line 1, in <module> > > ModuleNotFoundError: No module named 'neutron' > > +lib/neutron_plugins/ovn_agent:filter_network_api_extensions:439 > >

3 2

[all][election][tc] TC election at risk of single-employer majority
by Jeremy Stanley 05 Sep '22

05 Sep '22

The extended nomination period for the upcoming TC election closes in just over two days. We need to elect people to fill 4 of the 9 seats on the TC during this round. We currently have just enough candidates to fill the open seats, but in so doing we would end up with a majority of the TC members employed by the same company. Appendix 4 of the bylaws of the Open Infrastructure Foundation, the Technical Committee Member Policy[*], states: > In the event of a Technical Committee election that would result > in half or more of the members of the Technical Committee being > Affiliated, the Board of Directors may defer the effective date of > office of the newly elected Technical Committee members who are > Affiliated for a period not to exceed thirty (30) days after a > resolution by the Board of Directors approving such deferral. The > Board of Directors must pass such resolution within thirty (30) > days of the notice of election results from the Technical > Committee. During such period of deferral, the Technical Committee > and the Board of Directors shall work to resolve the issue by > agreement among themselves, such as by a resignation of one or > more Technical Committee members or having the Individual Member > with the next highest number of votes become a member of the > Technical Committee. If the Technical Committee and the Board of > Directors are not able to agree on a resolution within such thirty > (30) day period, the Board of Directors may require another > election for such positions. In order to avoid this outcome, we need additional nominees with a variety of affiliations immediately. If you've considered running for a seat on the OpenStack TC before, now is definitely the time. Please see earlier announcements[**] from the election officials for details on how to submit your nomination. Thanks! [*] https://openinfra.dev/legal/openstack-technical-committee-member-policy [**] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030094.… https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030241.… -- Jeremy Stanley

1 0

Secret getPayload() openstack4j
by Srinivasan T 05 Sep '22

05 Sep '22

Hi, I'm unable to get the secret's payload from openstack4j, it always returns null. Secret secret = os.barbican().secrets().get("19cbc4e8-cd06-450b-aa5d-2a4d20bf7d60"); secret.getPayload(); //Always returns null The same works when using the OpenStack CLI, openstack secret get --payload_content_type 'application/octet-stream' --file secret-payload http://x.x.x.x:9311/v1/secrets/19cbc4e8-cd06-450b-aa5d-2a4d20bf7d60 I'm using the below OpenStack4j version, Bundle-Name: OpenStack4j Core Bundle-Version: 3.6.0 OpenStack is in Queens version. Let me know if someone can help on this. Regards, Srini

2 1

[adjutant][magnum][mistral][sahara][watcher][zaqar][tc] broken gate for deliverables
by Előd Illés 05 Sep '22

05 Sep '22

Hi, Now that we have passed Zed-3 milestone, Release team starts to check the health of deliverables via their gate healthiness. The 1st round of checks showed that the following deliverables seem to have blocked gates: python-adjutantclient [1] python-magnumclient [2] python-mistralclient [3] python-saharaclient [4] python-watcherclient [5] python-zaqarclient [6] We are asking the teams to fix their gates and propose a release after it is fixed as soon as possible, otherwise these deliverables might not be part of the official Zed release. [1] https://review.opendev.org/c/openstack/python-adjutantclient/+/855763 [2] https://review.opendev.org/c/openstack/python-magnumclient/+/855778 [3] https://review.opendev.org/c/openstack/python-mistralclient/+/855781 [4] https://review.opendev.org/c/openstack/python-zaqarclient/+/855796 [5] https://review.opendev.org/c/openstack/python-watcherclient/+/855795 [6] https://review.opendev.org/c/openstack/python-saharaclient/+/855787 Thanks, Előd Illés irc: elodilles

2 1

http proxy support
by Oliver Weinmann 02 Sep '22

02 Sep '22

Hi, I was wondering if there is a way to set a http proxy in kolla-ansible during deployment / update etc. Today I wanted to pull new containers and this saturates our internet connection. What we usually do is have machine that massively download stuff from the internet use a squid proxy that throttles their bandwidth. I found the following feature request: https://bugs.launchpad.net/kolla-ansible/+bug/1829586 And it seems some work had been done, but I can't seem to find any info if the change really made it into production: https://review.opendev.org/c/openstack/kolla-ansible/+/692006/ Any help or hints are highly appreciated. Cheers, Oliver

2 4

[all][tc] What's happening in Technical Committee: summary 2022 Sept 2: Reading: 5 min
by Ghanshyam Mann 02 Sep '22

02 Sep '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Sept 01. Most of the meeting discussions are summarized in this email. Meeting full recording is available @ https://www.youtube.com/watch?v=WDfOx1m-wog and summary logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-09-01-15.01.log.html * Next TC weekly meeting will be on Sept 08 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Sept 07. 2. What we completed this week: ========================= * Appointed Dale Smith as Adjutant PTL for Zed cycle[2] * Switched requirements to distributed leadership [3] * Added Exception for the combined 2023.1(Antelope) elections [4] 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[5], four are completed and others items are in-progress. Open Reviews ----------------- * Four open reviews for ongoing activities[6]. 2023.1 cycle Technical Election (TC + PTL) planning ------------------------------------------------------------- By considering the holiday weeks, we decided to extend the nomination by a week[7]. The new deadline for nomination is Sept 7 [8]. We request you not to delay your nomination for PTL or TC. Define 2023.1 cycle testing runtime ------------------------------------------- Testing runtime for the 2023.1 cycle is up for review [9]. 2023.1 cycle TC PTG planning ------------------------------------ Updates on PTG planning: * "TC + Leader interaction" sessions is scheduled for Oct 17 Monday 15-17 UTC[10], * I have created the TC PTG etherpad to collect the topic[11]. * I sent email about the 'Operator Hours' slots in this PTG, please check and reserve the operator hour slot for your project[12] 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[13]. Feel free to check and provide feedback. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[14]15]. Project updates ------------------- * Switch release management to distributed leadership[16] 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[17]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [18] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/849606 [3] https://review.opendev.org/c/openstack/governance/+/854685 [4] https://review.opendev.org/c/openstack/governance/+/854624 [5] https://etherpad.opendev.org/p/tc-zed-tracker [6] https://review.opendev.org/q/projects:openstack/governance+status:open [7] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030241.… [8] https://governance.openstack.org/election/ [9] https://review.opendev.org/c/openstack/governance/+/854375 [10] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [11] https://etherpad.opendev.org/p/tc-2023-1-ptg [12] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [13] https://review.opendev.org/c/openstack/governance/+/836888 [14] https://etherpad.opendev.org/p/zuul-config-error-openstack [15] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [16] https://review.opendev.org/c/openstack/governance/+/855276 [17] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [18] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[tc][ptl] TC + Community Leaders interaction in 2023.1 Antelope Virtual PTG
by Ghanshyam Mann 02 Sep '22

02 Sep '22

Hello Everyone, We had successful TC+Community leaders interaction sessions in the last couple of PTG, and we will continue the same for 2023.1 cycle PTG also. I have created the poll to select the best suitable time. It will be for two hours (single or two sessions) either on Monday or Tuesday. Please add your preference in the below doodle poll (including TC members): - https://framadate.org/zsOqRxfVcmtjaPBC Also, I have created the below etherpad with the draft agenda, If you as PTL or project representatives or SIG Chair and would like to attend this session, please add your name: - https://etherpad.opendev.org/p/tc-leaders-interaction-2023-1 -gmann

1 1

[tripleo] gate blocker tripleo-ci-centos-9-content-provider
by Chandan Kumar 02 Sep '22

02 Sep '22

Hello tripleo, Please hold your recheck on master tripleo branch, we have a gate blocker for tripleo-ci-centos-9-content-provider. https://bugs.launchpad.net/tripleo/+bug/1988514 The team is currently working on fixing it. With Regards, Chandan Kumar

2 1

[PTL][release] Zed Cycle Highlights
by Előd Illés 02 Sep '22

02 Sep '22

Hi, This is a reminder, that *this week* is the week for Cycle highlights [1][2]! They need to be added to deliverable yamls so that they can be included in release marketing preparations. (See the details about how to add them at the project team guide [3].) [1]https://releases.openstack.org/zed/schedule.html [2]https://releases.openstack.org/zed/schedule.html#z-cycle-highlights [3] https://docs.openstack.org/project-team-guide/release-management.html#cycle… Thanks, Előd Illés irc: elodilles

4 6