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

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

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

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

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

09 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 吴文相 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