- openstack-discuss - lists.openstack.org

[release] Release countdown for week R-11, Jan 15-19
by Elõd Illés 13 Jan '24

13 Jan '24

Development Focus ----------------- We are now past the Caracal-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 the 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 (February 22nd, 2024). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (February 29th, 2024) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, February 29th, 2024. 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 (March 14th, 2024) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (March 28th, 2024) Upcoming Deadlines & Dates -------------------------- Non-client library freeze: February 22nd, 2024 (R-6 week) Client library freeze: February 29th, 2024 (R-5 week) Caracal-3 milestone: February 29th, 2024 (R-5 week) 2024.1 Caracal final release: April 3rd, 2024 2024.2 'D' virtual PTG ( https://openinfra.dev/ptg/ ): April 8th-12th, 2024 Előd Illés irc: elodilles @ #openstack-release

1 0

[openstack][keystone] user who mapped from openid cannot create application credentials
by Nguyễn Hữu Khôi 12 Jan '24

12 Jan '24

Hello. I have a problem that I use openid for authentication to my cloud but my users cannot create application credentials. I must add them to a group via Horizon UI to use application credentials. Is there any way to do that without adding users to a group from Horizon? Thank you. Nguyen Huu Khoi

1 1

[kolla-ansible][magnum]Private CA in Fedora-CoreOS
by Franck VEDEL 12 Jan '24

12 Jan '24

Hello, I have two platforms: on the first (Yoga), which is connected with public names and addresses, certificates issued by trusted CAs, no problem, creating a cluster template and deploying a cluster based on Fedora-CoreOS-35 works perfectly. On the second, I have a private certification authority (and privates addresses) and when I create a template then deploy a cluster, obviously there is a problem (in each node of the cluster) with the certificate issued by an untrusted CA. For the cluster to be deployed, I need to connect to the nodes, copy my CA certificate to /etc/pki/ca-trust/source/anchors/ then run the "update-ca-trust" command. My question is: is it possible to deploy a cluster using this method but without having to do what I am obliged to do if the CA is not trusted? If the answer exists, I couldn't find it in the documentation, I apologize. Thanks in advance Franck

1 0

[masakari] is going to be deprecated?!
by garcetto 12 Jan '24

12 Jan '24

good morning, maybe my comprehension fault, but is masakari going to be abandoned?! ... https://docs.openstack.org/kolla-ansible/latest/reference/compute/masakari-… "Support for deploying Masakari has been deprecated in the 2023.2 (Bobcat) release due to failures in the CI and lack of contributors working on fixing this."

2 2

[octavia] [octavia-ingress-controller][k8s]
by Johnny Yang 12 Jan '24

12 Jan '24

Hi, We are following https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/oct… to create octavia ingress controller. we are in openstack yoga version, and octavia ingress control version as ( registry.k8s.io/provider-os/octavia-ingress-controller:v1.28.1) we are getting the following error from octavia ingress controller pod =========== ❯ k logs octavia-ingress-controller-0 -n kube-system 2024/01/10 17:47:16 Running command: Command env: (log-file=, also-stdout=false, redirect-stderr=true) Run from directory: Executable path: /bin/octavia-ingress-controller Args (comma-delimited): /bin/octavia-ingress-controller,--config=/etc/config/octavia-ingress-controller-config.yaml 2024/01/10 17:47:16 Now listening for interrupts INFO [2024-01-10T17:47:16Z] Using config file file=/etc/config/octavia-ingress-controller-config.yaml W0110 17:47:16.597288 12 client_config.go:618] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work. FATAL [2024-01-10T17:47:16Z] failed to initialize openstack client error="Get \"/\": unsupported protocol scheme \"\"" 2024/01/10 17:47:16 running command: exit status 1 ======= the following are our service account/configmap/deployment yaml files: ============== serviceaccount.yaml ----- kind: ServiceAccount apiVersion: v1 metadata: name: octavia-ingress-controller namespace: kube-system --- kind: ClusterRoleBinding apiVersion: rbac.authorization.k8s.io/v1 metadata: name: octavia-ingress-controller roleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole name: cluster-admin subjects: - kind: ServiceAccount name: octavia-ingress-controller namespace: kube-system --- config.yaml ---- kind: ConfigMap apiVersion: v1 metadata: name: octavia-ingress-controller-config namespace: kube-system data: config: | cluster-name: cedev17 openstack: auth_url: https://srelab501.wpc.az1.eng.pdx.wd:5000 project_domain_name: Default user_domain_name: Default project_name: cedev17.t501.eng.pdx.wd project_id: 94ba42c68e1346189b666f17e49e22f5 username: admin user-id: b0f2b611d99e444cbe1c1fa068940411 password: password region_name: RegionOne cacert: /etc/pki/tls/certs/ca-bundle.crt octavia: subnet-id: 37abc0d8-f5ab-4109-8864-622ab4b47b1f floating-network-id: 42d4ba58-ccd6-407b-a887-5727ee7fe275 manage-security-groups: false provider: amphora ----- --- kind: StatefulSet apiVersion: apps/v1 metadata: name: octavia-ingress-controller namespace: kube-system labels: k8s-app: octavia-ingress-controller spec: replicas: 1 selector: matchLabels: k8s-app: octavia-ingress-controller serviceName: octavia-ingress-controller template: metadata: labels: k8s-app: octavia-ingress-controller spec: serviceAccountName: octavia-ingress-controller tolerations: - effect: NoSchedule # Make sure the pod can be scheduled on master kubelet. operator: Exists - key: CriticalAddonsOnly # Mark the pod as a critical add-on for rescheduling. operator: Exists - effect: NoExecute operator: Exists imagePullSecrets: - name: regcred containers: - name: octavia-ingress-controller image: docker-dev-artifactory.workday.com/wpc5/dev/octavia-ingress-controller:v1.2… imagePullPolicy: IfNotPresent args: - /bin/octavia-ingress-controller - --config=/etc/config/octavia-ingress-controller-config.yaml volumeMounts: - mountPath: /etc/kubernetes name: kubernetes-config readOnly: true - name: ingress-config mountPath: /etc/config hostNetwork: true volumes: - name: kubernetes-config hostPath: path: /etc/kubernetes type: Directory - name: ingress-config configMap: name: octavia-ingress-controller-config items: - key: config path: octavia-ingress-controller-config.yaml ------ Thank you in advance for help! -Johnny

2 1

beginning with [masakari]
by Shubham Kumar Yadav 12 Jan '24

12 Jan '24

Hi, i have recently started working on Masakari (kubernetes in openstack) so i wanted some help with it please i was trying to test the masakari-instance-monitor & masakari-host-monitor but having trouble with it. i have created a pacemaker remote cluster (with pacemaker & corosync on controller nodes and pacemaker remote on compute node). *pcs statusCluster name: lab-clusterCluster Summary: * Stack: corosync * Current DC: lab-11053-26006-ceph-2 (version 2.1.2-ada5c3b36e2) - partition with quorum * Last updated: Thu Dec 14 08:41:41 2023 * Last change: Thu Dec 14 08:41:22 2023 by root via cibadmin on lab-11053-26006-ceph-1 * 6 nodes configured * 3 resource instances configuredNode List: * Online: [ lab-11053-26006-ceph-1 lab-11053-26006-ceph-2 lab-11053-26006-ceph-3 ] * RemoteOnline: [ lab-11053-26006-comp-1.cluster.local lab-11053-26006-comp-2.cluster.local lab-11053-26006-comp-3.cluster.local ]Full List of Resources: * lab-11053-26006-comp-1.cluster.local (ocf:pacemaker:remote): Started lab-11053-26006-ceph-1 * lab-11053-26006-comp-2.cluster.local (ocf:pacemaker:remote): Started lab-11053-26006-ceph-2 * lab-11053-26006-comp-3.cluster.local (ocf:pacemaker:remote): Started lab-11053-26006-ceph-3Daemon Status: corosync: active/enabled pacemaker: active/enabled pcsd: active/enabled* i have also created segment and added segment hosts(computes) in it. when i tried to test the masakari host monitor by manually powering off the compute node, masakari should move the vms from powered off computes to some running compute but after the compute is powered off vms still remains on the powered off compute. Am i missing some conf? is there any need to add some conf in nova and keystone too? *in masakari engine logs i seehost_failure.evacuate_all_instances = Trueinstance_failure.process_all_instances = Falsehost_failure.add_reserved_host_to_aggregate = Falsehost_failure.ha_enabled_instance_metadata_key = HA_Enabled log_opt_valueshost_failure.ignore_instances_in_error_state = Falsehost_failure.service_disable_reason = Masakari detected host failed.* *2 - question do i have to create some notification and vmoves?* openstack notification create <type> <hostname> <generated_time> <payload> if yes what is the use of notification & vmoves i ahve attached a file with the email which contains the componenets i created for masakari(segments &hosts in segments)

2 1

[senlin] Rolling updates issues future support and alternatives
by Devin Patterson 12 Jan '24

12 Jan '24

Hello folks, We are attempting to find a solution for tenants in our OpenStack environment and have been testing Senlin for auto-scaling, auto-healing and rolling updates. The goal is similar functionality to AWS auto-scaling groups. Auto-scaling and health check functionality is working properly but we are getting some errors when attempting to update Senlin clusters to new profiles. Specifically, we would like to update VM user_data and VM images and roll those changes out in alignment with batch policies. The Senlin clusters attempt to update but fail with errors in the senlin_engine logs either related to lack of support for user_data updates or duplicate images when updating images in the profile. Proxy.rebuild_server() got multiple values for argument 'image' 2024-01-11 16:16:10.050 1009 ERROR senlin.profiles.base [] The following properties are not updatable: user_data. 16:10.086 1009 ERROR senlin.engine.event [] NODE_UPDATE[] error: Node update failed. Is anyone able to help with a path forward as well as provide any input on future support for Senlin as I saw some messages related to it no longer being supported? If so, can anyone recommend OpenStack project alternatives to achieve autoscaling, auto-healing and rolling updates for tenant VMs? Thanks in advance for any help, Devin

1 0

[magnum] autoscaling feature not working
by Satish Patel 11 Jan '24

11 Jan '24

Folks, I am trying to set the auto scaling feature in magnum "auto_scaling_enabled '' true but somehow the auto scaling is not working. truly speaking I don't understand the workflow of scaling up and down of worker nodes. How does magnum know that it requires scaling up and down without monitoring? On what basis will it trigger that action?

2 8

[Openstack-Chef][all][tc] Retiring Openstack-Chef
by Ghanshyam Mann 11 Jan '24

11 Jan '24

Hello Everyone, You might have seen that OpenStack-Chef project (provides the Chef cookbooks for OpenStack life cycle management) is leaderless in this cycle, and further investigation by TC found that this project's health is not green and does not have maintainers. - https://etherpad.opendev.org/p/2024.1-leaderless A few of the stats about this project's activities: - gate health unclear, no activity for > 1y in openstack/openstack-chef repo - most recent branch is stable/train - zuul config errors fixed by frickler We contacted the previous PTL Lance Albertson and he would not be able to continue maintaining it and are ok with the retirement. Considering the current situation and no maintainers in this project, TC is planning to retire this project. This is the last call if any of you or your organization are interested in maintaining it (or using it and would like to discuss the possible path forward). Feel free to reply to this email or add your feedback in Gerrit: - https://review.opendev.org/c/openstack/governance/+/905279 -gmann

1 0

[all] Nomination for extra-ACs
by Jay Faulkner 11 Jan '24

11 Jan '24

OpenStackers: Elections are beginning soon. This means as a community, we have a responsibility to identify and credit any extra Active Contributors (extra ACs) who may not have committed code in the last six months. Being named an extra AC has a simple, but important impact: it permits the individual named to vote in elections for the Technical Committee. Additionally, it's an important form of recognition which can encourage future non-code contributions. If there's someone who has made non-code contributions to a project who should be recognized, please contact me, in my role as the Technical Committee Chair (per the TC Charter https://governance.openstack.org/tc/reference/charter.html#voters-for-tc-se…) and the TC will evaluate the request and approve it if reasonable. Please note; this is not just an exercise for PTLs. Self-nominating for extra-AC status is not only permitted; it's encouraged -- if you've contributed, we want to recognize you. Additionally, any existing project contributors are eligible to nominate peers they think are deserving. Thank you in advance for taking time to recognize your upstream peers! Jay Faulkner OpenStack TC Chair

1 0

[nova][release][tooz] Hold your rechecks
by Sylvain Bauza 10 Jan '24

10 Jan '24

Hey folks, FWIW, our grenade check on SLURP upgrades is 100% failing now [1] due to a behavioural change in the tooz library [2] that's pulled by Cinder and which was released [3] and delivered to upper-contraints yesterday [4] There are different possibilities in order to unblock the gate, but until one of them is agreed and merged, please avoid wasting our CI resources by asking to recheck for something which will fail. Thanks, -Sylvain (who will send an email once the job is back up) [1] https://zuul.opendev.org/t/openstack/builds?job_name=grenade-skip-level-alw… [2] https://review.opendev.org/c/openstack/tooz/+/891355 [3] https://review.opendev.org/c/openstack/releases/+/899966 [4] https://review.opendev.org/c/openstack/requirements/+/901131

4 6

[largescale-sig] Next meeting: Jan 10, at 9UTC
by Kristin Barrientos 10 Jan '24

10 Jan '24

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 9UTC. Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Thanks, Kristin Barrientos Marketing Coordinator OpenInfra Foundation

2 1

Help with [masakari]
by Shubham Kumar Yadav 10 Jan '24

10 Jan '24

Hi, i have recently started working on Masakari (kubernetes in openstack) so i wanted some help with it please i was trying to test the masakari-instance-monitor & masakari-host-monitor but having trouble with it. i have created a pacemaker remote cluster (with pacemaker & corosync on controller nodes and pacemaker remote on compute node). inside masakari-instance-monitor pods i see *cat /etc/masakari/masakarimonitors.conf[DEFAULT]debug = truehostname = lab-11053-26006-cmp-1.cluster.local,lab-11053-26006-cmp-2.cluster.local,lab-11053-26006-cmp-3.cluster.local* but still im getting this error,it is still trying to find the short hostname. *2024-01-05 08:32:39.494 1 WARNING masakarimonitors.ha.masakari [-] Retry sending a notification. (BadRequestException: 400: Client Error for url: http://masakari-api.openstack.svc.cluster.local:15868/v1/9db00e10af034fc6a4… <http://masakari-api.openstack.svc.cluster.local:15868/v1/9db00e10af034fc6a4…>, Host with name lab-11053-26006-cmp-1 could not be found.): openstack.exceptions.BadRequestException: BadRequestException: 400: Client Error for url: http://masakari-api.openstack.svc.cluster.local:15868/v1/9db00e10af034fc6a4… <http://masakari-api.openstack.svc.cluster.local:15868/v1/9db00e10af034fc6a4…>, Host with name lab-11053-26006-cmp-1 could not be found.* do you hvae some suggestions to resolve this *2 - question do i have to create some notification and vmoves in openstack(masakari)?* openstack notification create <type> <hostname> <generated_time> <payload> *3 - host monitor also kinda doesnt work ,*when i tried to test the masakari host monitor by manually powering off the compute node, masakari should move the vms from powered off computes to some running compute but after the compute is powered off vms still remains on the powered off compute. Am i missing some conf? is there any need to add some conf in nova and keystone too? *4 - i have disabled "*pcs property set stonith-enabled=false" does it needs to be enabled and setup? 5- is there any other channels(slack) when i can contact teams directly?

1 0

[tc][all] Inactive projects, new contributors, and core access
by Jay Faulkner 10 Jan '24

10 Jan '24

Hi all, An interesting debate popped up during today's Technical Committee meeting which I thought would be wise to bring before the larger community. I will note, despite this referencing a current event, any discussions about this are about general policies and not any individual persons or situations. Monasca, a recently marked inactive project, has had someone -- a single individual -- volunteer to attempt to maintain the service. There was some debate among the TC about whether or not this was sufficient to consider Monasca an active project again, with two primary concerns. First, there were trust-related concerns -- for a project that would essentially be maintained by a single person, is it acceptable to grant core access or appoint someone DPL/PTL (giving the ability to merge code) who is new to the OpenStack community. Some TC members expressed a concern that granting such access, without a commitment from a trusted community member to act as a mentor or monitor on the project, could open us up to insider attacks against our deliverables, while others made the argument that we should default to trust and ensure our community remains welcome to new contributors. Secondly, there are concerns regarding sustainability -- is it acceptable for an OpenStack project to move from "inactive" to "active" based on the promised maintenance of a single person, with no backup? Some TC members expressed a concern that projects moving from "active" to "inactive" repeatedly are taxing on governance volunteers and not an ideal outcome, while others argued that there is value in keeping projects in the OpenStack release. There was a very involved debate in today's TC meeting about these topics. I encourage interested parties to review this log before replying. https://meetings.opendev.org/meetings/tc/2024/tc.2024-01-09-18.00.log.html#… We have an item on the TC agenda for next meeting, a week from today, to help decide on these items for the sake of Monasca, but it's my hope we can determine a reasonable precedent to apply consistently to these cases going forward. Your input will help guide the decision of the committee on these items. Thanks, Jay Faulkner OpenStack TC Chair

2 1

Team Signup for April 2024 OpenInfra PTG
by Kendall Nelson 10 Jan '24

10 Jan '24

Hello Everyone, Hopefully, you have seen by now, that the next OpenInfra PTG[1] will take place April 8-12, 2024 virtually! *To sign up your team, you must complete the survey[2] by February 18 at 7:00 UTC.* We NEED accurate contact information (email and IRC nickname ideally) for the moderator of your team’s sessions. This is because the survey information will be used to organize the schedule sign ups which will be done via the PTGBot. If you are not on IRC, please get set up[3] on the OFTC network and join #openinfra-events. You are also encouraged to familiarize yourself with the PTGBot documentation[4] as well. If you have any questions, please reach out! Information about signing up for timeslots will be sent to moderators late February after the team sign up deadline. Continue to visit openinfra.dev/ptg for updates. Registration will open soon! -Kendall Nelson (diablo_rojo) [1] PTG Site: https://openinfra.dev/ptg/ [2] Team Survey: https://openinfrafoundation.formstack.com/forms/april2024_ptg_survey [3] Setup IRC: https://docs.openstack.org/contributors/common/irc.html [4] PTGBot README: https://opendev.org/openstack/ptgbot/src/branch/master/README.rst

1 0

Re: [kolla] [skyline] help configuring monitor center
by Satish Patel 10 Jan '24

10 Jan '24

He did something for the monitor center to make it work with prometheus. I was planning to submit a patch. Let's see if he has anything to offer. ( He was planning to submit a patch. Lets see if he has anything to offer. ) On Tue, Jan 9, 2024 at 6:25 PM Satish Patel <satish.txt(a)gmail.com> wrote: > /cc - Nguyen Huu Khoi > > He did something for the monitor center to make it work with prometheus. I > was planning to submit a patch. Lets see if he has anything to offer. > > On Tue, Jan 9, 2024 at 6:17 PM 吴文相 <wu.wenxiang(a)99cloud.net> wrote: > >> Hello, Garcetto >> >> No guide as I known. >> You can create a ticket to ask skyline dev team. >> Beside enable_prometheus, you also need to add other prometheus related >> configuration items, such as url / username / passsword, etc. >> >> Thanks >> >> Best Regrads >> Wu Wenxiang >> >> >> >> Original: >> >> - From：garcetto <garcetto(a)gmail.com> >> - Date：2024-01-08 17:50:17(中国 (GMT+08:00)) >> - To：OpenStack Discuss <openstack-discuss(a)lists.openstack.org> >> - Cc： >> - Subject：[kolla] [skyline] help configuring monitor center >> >> good morning, >> is there a guide to help me configure monitor center for skyline? >> I have already set: >> >> enable_skyline: "yes" >> enable_prometheus: "yes" >> >> >> [image: image.png] >> >> thank you. >> >> >>

1 0

Re:[kolla] [skyline] help configuring monitor center
by 吴文相 10 Jan '24

10 Jan '24

Hello, Garcetto No guide as I known. You can create a ticket to ask skyline dev team. Beside enable_prometheus, you also need to add other prometheus related configuration items, such as url / username / passsword, etc. Thanks Best Regrads Wu Wenxiang Original: From：garcetto <garcetto(a)gmail.com>Date：2024-01-08 17:50:17(中国 (GMT+08:00))To：OpenStack Discuss <openstack-discuss(a)lists.openstack.org>Cc：Subject：[kolla] [skyline] help configuring monitor centergood morning, is there a guide to help me configure monitor center for skyline? I have already set: enable_skyline: "yes" enable_prometheus: "yes" thank you.

1 0

[TripleO][all][tc] Retiring TripleO completely
by Ghanshyam Mann 10 Jan '24

10 Jan '24

Hello Everyone, As you might know TripleO last maintained release was wallaby[1] and accordingly all the deliverables of this project ware marked as deprecated[2] in previous cycle. In today TC meeting, we discussed about the release clarity of its remaining deliverables (stable/wallaby or its needed master only CI repo) and got to know that TripleO team has retired the stable/wallaby ( no longer maintaining it) so we are good to move to next step of TripleO retirement completely . I have proposed the governance change to record the retirement officially. Feel free to provide your feedback in this email or in gerrit change or let TC knows if any of the deliverables you are dependent on and interested to maintain. - https://review.opendev.org/c/openstack/governance/+/905145 [1] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/03208… [2] https://review.opendev.org/c/openstack/governance/+/877132 -gmann

1 0

OpenStack "D" Release Voting
by Kristin Barrientos 10 Jan '24

10 Jan '24

Hi everyone, It’s time to vote for the OpenStack “D” Release! The nominees are: - Dalmatian - Daikon - Dijon Get your votes in here: https://civs1.civs.us/cgi-bin/vote.pl?id=E_28514d041f523c11&akey=c3d26e4bc2… Voting will close on January 12, 2024, at 20:00 UTC. Thanks, Kristin Barrientos Marketing Coordinator OpenInfra Foundation

1 0

[designate] Proposal to deprecate the agent framework and agent based backends
by Michael Johnson 10 Jan '24

10 Jan '24

TLDR: The Designate team would like to deprecate the backend agent framework and the agent based backends due to lack of development and design issues with the current implementation. The following backends would be deprecated: Bind9 (Agent), Denominator, Microsoft DNS (Agent), Djbdns (Agent), Gdnsd (Agent), and Knot2 (Agent). Designate includes many backend DNS server drivers[1], many of which are "native" (also known as xfr type backends) backend implementations. In addition to the "native" backends, Designate has an agent backend[2] that supports other backends via an agent process. To quote the agent backend documentation[2]: This backend uses an extension[3] of the DNS protocol itself to send management requests to the remote agent processes, where the requests will be actioned. The rpc traffic between designate and the agent is both unauthenticated and unencrypted. Do not run this traffic over unsecured networks. Here are the reasons we are proposing to deprecate the agent framework now: 1. The agent protocol used by Designate is using an "unassigned"[4][5] DNS opcode (14) that is causing problems with the dnspython library >= 2.3.0 which is now validating the opcode when building DNS messages. It is a bad practice to use "unassigned" values as they may be officially assigned at any time, likely with an incompatible message format. 2. The agent backends are not tested in the OpenStack jobs[1]. 3. Many of the agent backends have been marked as "Experimental" since 2016 with no additional contributions beyond general repository code maintenance. 4. The protocol between the Designate worker process and the agent process is unauthenticated and unencrypted. 5. We do not know of a development resource to rewrite the agent framework protocol to address issue #1 and #4 above. 6. The introduction of catalog zones[6] may eliminate the need for some of the agent based backend drivers. By marking the agent framework and agent based backends "deprecated" in the Antelope cycle, we would remove the code no earlier than the "C" release of OpenStack (per the OpenStack deprecation policy[7]). In the meantime, issue #1 has been worked around by overriding the dnspython opcode validation[7] as needed in the Designate code (similar to a monkey patch). This is not a sustainable long term solution. The following backend agent based drivers would be marked "deprecated" in addition to the agent framework itself: Bind9 (Agent) Denominator Microsoft DNS (Agent) Djbdns (Agent) Gdnsd (Agent) Knot2 (Agent) We plan to propose patches for the deprecation over the next week, but will not merge them until at least January 24th to allow time for comment from the community. If you have concerns about this deprecation plan or are interested in rewriting the agent framework protocol to address the above issues, please reply to this announcement. Michael [1] https://docs.openstack.org/designate/latest/admin/support-matrix.html [2] https://docs.openstack.org/designate/latest/admin/backends/agent.html [3] https://github.com/openstack/designate/blob/master/designate/backend/privat… [4] https://www.rfc-editor.org/rfc/rfc6895.html#section-2.2 [5] https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-pa… [6] https://www.ietf.org/archive/id/draft-ietf-dnsop-dns-catalog-zones-08.txt [7] https://docs.openstack.org/project-team-guide/deprecation.html [8] https://review.opendev.org/c/openstack/designate/+/870678

3 13

[tc] Technical Committee Meeting Jan 9
by Jay Faulkner 10 Jan '24

10 Jan '24

Hi all, The next meeting of the OpenStack Technical Committee is today (sorry for the late email!) Jan 9, at 1800 UTC in #openstack-tc on OFTC. The proposed agenda is: - Roll call - Follow up on tracked action items - Spotz - (due Jan 7 2024) Look into updating https://docs.openstack.org/install-guide/openstack-services.html and report back to TC - Gate health check - Leaderless projects (gmann) - Implementation of Unmaintained branch statuses - TC charter updates and TC votes on OpenInfra Bylaw changes (gmann) - Charter updates: https://review.opendev.org/c/openstack/governance/+/903236/ - Resolution for TC votes: https://review.opendev.org/c/openstack/governance/+/903239/ - 2024.1 TC Tracker - https://etherpad.opendev.org/p/tc-2024.1-tracker - TripleO next steps (fungi) - Stable-branching repos were deprecated but single-branch weren't - We're approaching membership freeze for 2024.1/Caracal and the Release Managers need to know what to do with them - The VMT still gets notified about newly discovered security vulnerabilities from people who think the repos are maintained - Open Discussion and Reviews Thanks, Jay Faulkner OpenStack TC Chair

1 0

[all] OpenInfra Foundation Individual Director Election
by Jeremy Stanley 09 Jan '24

09 Jan '24

Just a heads up that the election to choose representatives for the Individual Members of the OpenInfra Foundation is open through Friday of this week. Ballots have already been sent by E-mail, but there have been reports of delivery challenges for some members. If you believe you should have received a ballot but don't find it in your inbox nor spam/junk folder, see this post on the foundation ML for further instructions: https://lists.openinfra.dev/archives/list/foundation@lists.openinfra.dev/th… Please note, to be considered eligible, you must have been an OpenInfra Foundation member by July 16, 2023. -- Jeremy Stanley

1 0

[tc][all] Technical Committee Charter updated
by Jay Faulkner 09 Jan '24

09 Jan '24

Hi all, I wanted to inform you that the OpenStack Technical Committee Charter was recently updated in coordination with the Open Infrastructure Foundation (OIF) bylaws. As a high level summary, these changes are moving some aspects of OpenStack policy from OIF Bylaws into the OpenStack Technical Committee charter, mirroring the way later OIF projects were configured. As always, the actual changes are recorded directly in git in the governance repo. Please review the changes directly if you want to get deeper than my surface-level summary. The TC Charter update commit is at https://opendev.org/openstack/governance/commit/bead7751833b78600853c22faac… and the resolution expressing support for OIF Bylaws changes is at https://opendev.org/openstack/governance/commit/5c683c25013e5e004bf6f9c9b67… . Thanks, Jay Faulkner OpenStack TC Chair

1 0

[octavia][neutron] ask about LB with DVR
by Nguyễn Hữu Khôi 09 Jan '24

09 Jan '24

Hello guys. I see that more and more people use Octavia but it depends on network nodes which cause bottlenecks or single point of failure . I would like to know if we have some plan to make Octavia works without network nodes. Thank you. Nguyen Huu Khoi

2 4

[Cinder][Glance][Image Encryption] First overall patchset for the image encryption ready
by Josephine Seifert 08 Jan '24

08 Jan '24

Hi everyone, I am happy to announce, that the first patch set of image encryption is ready. If you would like to test and review it, it would be a great help. The patchset can be found under the topic "image encryption": https://review.opendev.org/q/topic:%22image-encryption%22 It contains patches for: - Glance - Cinder - os-brick - openstackclient - cinderclient All patches need to be present for testing. Our test-environment had ceph as a backend, test with other backends would be nice. I hope for feedback from the glance and cinder teams, but also Operator feedback is welcome. Thank you Josephine (Luzi)

1 0