January 2024 - openstack-discuss - lists.openstack.org

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

09 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 09 Jan '24

09 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 09 Jan '24

09 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 09 Jan '24

09 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 09 Jan '24

09 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 08 Jan '24

08 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 08 Jan '24

08 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 08 Jan '24

08 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

[openstack-helm] Nominate Sergiy Markin as a core reviewer
by Vladimir Kozhukalov 08 Jan '24

08 Jan '24

Hi Openstack-Helm team, I would like to nominate Sergiy Markin as a core reviewer for the project. He's been doing many reviews recently [1]. He also contributed some Mariadb and ingress related improvements. Besides that he has wide experience in Airship which is historically closely related to Openstack-Helm. I believe we as a team will benefit a lot from Sergiy being a core team member. [1] https://www.stackalytics.io/report/contribution?module=openstack-helm-group… -- Best regards, Kozhukalov Vladimir

2 2