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

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

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

11 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 10 Jan '24

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

10 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 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

[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

LVM Cinder
by Jorge Visentini 08 Jan '24

08 Jan '24

Hi all! My scenario: We currently use oVirt and are studying the possibility of migrating to OpenStack in the future. Today we use Storages Enterprise 3PAR and Dell PowerVault. I've even tried to integrate 3PAR, but it's too complex for me for now... Stupid question... If I work directly with LVM, that is, deliver a LUN to all my hosts, create an LVM and deliver it to Cinter, will I have the Live Migration, HA instances, snapshot and other features ? Cheers! -- Att, Jorge Visentini +55 55 98432-9868

6 10

[publiccloud-sig] Reminder - next meeting January 10th - 0800 UTC
by Felix Kronlage-Dammers 08 Jan '24

08 Jan '24

Hi everyone, This Wednesday (January 10th) the first meeting of the new year of the public cloud sig is going to happen. Since we do every other meeting as a videosession, we’ll be meeting at 0800 UTC here: https://conf.scs.koeln:8443/OIF-public-cloud-sig See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG For the agenda, I have couple of suggestions (that I also added to the etherpad): - FOSDEM is coming up. Maybe we want to meet at FOSDEM? - The last meetings we’ve discussed and worked on user stories regarding discoverability of flavors and features of a public cloud. We should find a way this becomes actionable with concrete next steps (see: https://input.scs.community/ZfP4d2kNTbagN9-Jk2ccEQ?view - this is also linked from the Etherpad: https://etherpad.opendev.org/p/publiccloud-sig-meeting) See you Wednesday! felix -- Felix Kronlage-Dammers Product Owner IaaS & Operations Sovereign Cloud Stack Sovereign Cloud Stack — standardized, built and operated by many Ein Projekt der Open Source Business Alliance - Bundesverband für digitale Souveränität e.V. Tel.: +49-30-206539-205 | Matrix: @fkronlage:matrix.org | fkr(a)osb-alliance.com

1 0

[neutron] Bug Deputy Report January 1 - January 7
by Elvira Garcia Ruiz 08 Jan '24

08 Jan '24

Hi folks! I was the Neutron bug deputy last week. It was a quiet week. See the report below: Medium ----------- https://bugs.launchpad.net/neutron/+bug/2047849 - [RFE] Start using oslo messaging namespaces Unassigned Low ------ https://bugs.launchpad.net/neutron/+bug/2048198 - neutron-lib role enforcer is writing warning messages Unassigned Best regards, Elvira

1 0

[kolla] [skyline] help configuring monitor center
by garcetto 08 Jan '24

08 Jan '24

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

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

08 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.* *2 - question do i have to create some notification and vmoves?* 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

Re:
by Rohit Sansiya 07 Jan '24

07 Jan '24

Please answer On Sat, 6 Jan, 2024, 13:47 Rohit Sansiya, <rsansiya(a)gmail.com> wrote: > i hvnt heard about ...how the openstack is getting the dhcp ip without > registration of mac address ? > > > Your message is ready to be sent with the following file or link > attachments: > Rohit Sansiya > https://sites.google.com/view/rpgcloud/research-india > > Note: To protect against computer viruses, e-mail programs may prevent > sending or receiving certain types of file attachments. Check your e-mail > security settings to determine how attachments are handled. >

1 0

[nova] patch delete dangling bdms lead to VM Error
by Sang Tran Quoc 07 Jan '24

07 Jan '24

Hi community, I've got the error with this patch while rebooting VM with volume source from the image, the result VM state is Error with the message "VolumeDeviceNotFound" (Tested with Netapp & PowerStrore iSCSI SAN driver) Please take a look at this! https://review.opendev.org/c/openstack/nova/+/882284

2 2

[kolla] help installing skyline UI
by garcetto 07 Jan '24

07 Jan '24

good evening, i dont find where i can enable the skyline ui frontend could have an help? thank you

3 3

Re: New OpenStack machine on new node not responding
by 韩光宇 07 Jan '24

07 Jan '24

Hi Do you configure security group? The default security group provided by OpenStack denies any incoming traffic. ----------Reply to Message---------- On Tue, Jan 2, 2024 21:54 PM kjme001<kjme001(a)gmail.com> wrote: hello, I added a new node to OpeStack. I can create a new instance on it. The instance creates itself without error, its IP address is assigned. But however, the connection over ssh to this new machine does not work for me, nor does ping. I have the network traffic passed, what else can I check why the new machine is not responding to me network-wise regards

2 1

[ironic][glance] tradeoffs between ceph and swift glance backends for ironic+kvm?
by Michael Sherman 06 Jan '24

06 Jan '24

Hey! We’re looking into deploying a cloud with a mix of VM and baremetal hosts (nova-compute vs ironic), and discovered some tension between the recommendations for glance for each case. At scale, ironic seems to recommend usage of the swift backend to remove the conductor as a bottleneck when streaming disk images, but for KVM usage, the RBD backend allows for faster launches by cloning the source image. Any thoughts on these or any other tradeoffs, or some recommended configurations? Thanks! -Mike -- Michael Sherman Infrastructure Lead – Chameleon Computer Science, University of Chicago MCS, Argonne National Lab

3 2

reset-state instances with Api in openstack
by Parsa Aminian 06 Jan '24

06 Jan '24

hello Is there any Api for reset-state instance status to active or error on openstack api ?

5 5

[release] Release countdown for week R-12
by Thierry Carrez 05 Jan '24

05 Jan '24

Development Focus ----------------- The Caracal-2 milestone is next week, on January 11th, 2024! 2024.1 Caracal-related specs should now be finalized so that teams can move to implementation ASAP. Some teams observe specific deadlines on the second milestone (mostly spec freezes): please refer to https://releases.openstack.org/caracal/schedule.html for details. General Information ------------------- Libraries need to be released at least once per milestone period. Next week, the release team will propose releases for any library that has not been otherwise released since milestone 1. PTL's and release liaisons, please watch for these and give a +1 to acknowledge them. If there is some reason to hold off on a release, let us know that as well. A +1 would be appreciated, but if we do not hear anything at all by the end of the week, we will assume things are OK to proceed. Remember that non-library deliverables that follow the cycle-with-intermediary release model should have an intermediary release before milestone-2. Those who haven't will be proposed to switch to the cycle-with-rc model, which is more suited to deliverables that are released only once per cycle. Next week is also the deadline to freeze the contents of the final release. All new 2024.1 Caracal deliverables need to have a deliverable file in https://opendev.org/openstack/releases/src/branch/master/deliverables and need to have done a release by milestone-2. Changes proposing those deliverables for inclusion in 2024.1 Caracal have been posted, please update them with an actual release request before the milestone-2 deadline if you plan on including that deliverable in 2024.1 Caracal, or -1 if you need one more cycle to be ready. Upcoming Deadlines & Dates -------------------------- Caracal-2 Milestone: January 11th, 2024 -- Thierry Carrez (ttx)

1 0

[neutron] Neutron drivers meeting
by Rodolfo Alonso Hernandez 05 Jan '24

05 Jan '24

Hello Neutrinos: Due to the lack of quorum, I've cancelled the meeting 5 minutes after starting it. We'll retake the pending issues next week. Regards.

1 0

tox -e pep8 error
by Alex Song (宋文平) 05 Jan '24

05 Jan '24

Folks, my env run 'tox -e pep8' error with the info below, any body can help? Thanks. /opt/stack/nova/.tox/pep8/lib/python3.8/site-packages/setuptools/__init__.py :80: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. !! **************************************************************************** **** Requirements should be satisfied by a PEP 517 installer. If you are using pip, you can try `pip install --use-pep517`. **************************************************************************** **** !! dist.fetch_build_eggs(dist.setup_requires) /opt/stack/nova/.tox/pep8/lib/python3.8/site-packages/setuptools/command/dev elop.py:39: EasyInstallDeprecationWarning: easy_install command is deprecated. !! **************************************************************************** **** Please avoid running ``setup.py`` and ``easy_install``. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://github.com/pypa/setuptools/issues/917 for details. **************************************************************************** **** !! easy_install.initialize_options(self) /opt/stack/nova/.tox/pep8/lib/python3.8/site-packages/setuptools/_distutils/ cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! **************************************************************************** **** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. **************************************************************************** **** !! self.initialize_options() pep8 develop-inst-nodeps: /opt/stack/nova pep8 installed: alembic==1.9.4,amqp==5.1.1,async-timeout==4.0.3,attrs==23.1. 0,autopage==0.5.1,backports.zoneinfo==0.2.1,bcrypt==4.0.1,cachetools==5.3.1, castellan==4.3.0,certifi==2023.11.17,cffi==1.15.1,cfgv==3.4.0,charset-normal izer==3.2.0,cliff==4.4.0,cmd2==2.4.3,cryptography==41.0.4,cursive==0.2.3,deb tcollector==2.5.0,decorator==5.1.1,Deprecated==1.2.14,distlib==0.3.7,dnspyth on==2.4.2,dogpile.cache==1.2.2,eventlet==0.33.3,fasteners==0.19,filelock==3. 12.4,fixtures==4.1.0,futurist==2.4.1,greenlet==2.0.2,identify==2.5.33,idna== 3.4,importlib-metadata==6.0.1,importlib-resources==6.1.1,iso8601==2.0.0,Jinj a2==3.1.2,jmespath==1.0.1,jsonpatch==1.33,jsonpointer==2.4,jsonschema==4.19. 1,jsonschema-specifications==2023.7.1,jwcrypto==1.5.1,keystoneauth1==5.4.0,k eystonemiddleware==10.5.0,kombu==5.3.2,lxml==4.9.3,Mako==1.2.4,MarkupSafe==2 .1.3,microversion-parse==1.0.1,msgpack==1.0.6,netaddr==0.9.0,netifaces==0.11 .0,nodeenv==1.8.0,-e git+ssh://songwenping@review.opendev.org:29418/openstack/nova@39f560d6730f2b 212506b7d754645c288d13f1cd#egg=nova,numpy==1.24.2,openstacksdk==2.0.0,os-bri ck==6.5.0,os-client-config==2.1.0,os-resource-classes==1.1.0,os-service-type s==1.7.0,os-traits==3.0.0,os-vif==3.3.0,os-win==5.9.0,osc-lib==2.8.1,oslo.ca che==3.5.0,oslo.concurrency==5.2.0,oslo.config==9.2.0,oslo.context==5.3.0,os lo.db==14.1.0,oslo.i18n==6.2.0,oslo.limit==2.2.0,oslo.log==5.4.0,oslo.messag ing==14.5.0,oslo.metrics==0.7.0,oslo.middleware==5.2.0,oslo.policy==4.2.1,os lo.privsep==3.2.0,oslo.reports==3.1.0,oslo.rootwrap==7.1.0,oslo.serializatio n==5.2.0,oslo.service==3.2.0,oslo.upgradecheck==2.2.0,oslo.utils==6.3.0,oslo .versionedobjects==3.2.0,ovs==3.1.2,ovsdbapp==2.5.0,packaging==23.1,paramiko ==3.3.1,Paste==3.5.3,PasteDeploy==3.0.1,pbr==6.0.0,pkgutil_resolve_name==1.3 .10,platformdirs==3.10.0,pre-commit==3.5.0,prettytable==3.9.0,prometheus-cli ent==0.17.1,psutil==5.9.5,pycadf==3.1.1,pycparser==2.21,pyinotify==0.9.6,PyJ WT==2.8.0,PyNaCl==1.5.0,pyOpenSSL==23.2.0,pyparsing==3.1.1,pyperclip==1.8.2, pyroute2==0.7.9,python-barbicanclient==5.6.1,python-cinderclient==9.4.0,pyth on-dateutil==2.8.2,python-glanceclient==4.4.0,python-keystoneclient==5.2.0,p ython-neutronclient==11.1.0,pytz==2023.3.post1,PyYAML==6.0.1,redis==5.0.0,re ferencing==0.30.2,repoze.lru==0.7,requests==2.31.0,requestsexceptions==1.4.0 ,retrying==1.3.4,rfc3986==2.0.0,Routes==2.5.1,rpds-py==0.10.3,simplejson==3. 19.1,six==1.16.0,sortedcontainers==2.4.0,SQLAlchemy==1.4.41,statsd==4.0.1,st evedore==5.1.0,tenacity==6.3.1,testresources==2.0.1,testscenarios==0.5.0,tes ttools==2.7.0,tooz==4.2.0,typing_extensions==4.8.0,tzdata==2023.3,urllib3==1 .26.16,vine==5.0.0,virtualenv==20.24.5,voluptuous==0.13.1,warlock==2.0.1,wcw idth==0.2.6,WebOb==1.8.7,websockify==0.11.0,wrapt==1.15.0,yappi==1.4.0,zipp= =3.17.0 pep8 run-test-pre: PYTHONHASHSEED='2048831401' pep8 run-test: commands[0] | pre-commit run --all-files --show-diff-on-failure [INFO] Locking pre-commit directory [INFO] Initializing environment for https://github.com/pre-commit/pre-commit-hooks. An unexpected error has occurred: CalledProcessError: command: ('/usr/bin/git', 'fetch', 'origin', '--tags') return code: 128 stdout: (none) stderr: (none) Check the log at /root/.cache/pre-commit/pre-commit.log ERROR: InvocationError for command /opt/stack/nova/.tox/pep8/bin/pre-commit run --all-files --show-diff-on-failure (exited with code 3) ____________________________________________________________________________ _______________________________________________________________ summary ____________________________________________________________________________ _______________________________________________________________ ERROR: pep8: commands failed

2 2

Issue when connecting to openstack object storage with openstacksdk
by sadir＠free.fr 05 Jan '24

05 Jan '24

Hello, I am currently developing a software application to access the OpenStack object store service on an IBM Spectrum Scale server. I first created a Python application which is manipulating objects and containers thru the OpenStack's object storage REST API (https://docs.openstack.org/api-ref/object-store) It works fine and I had no issue to access the server object store service by this way. But I also need to access the OpenStack object store service thru the openstacksdk (https://docs.openstack.org/openstacksdk/latest) Unfortunately, the connection does not seem to work properly in this case, even when using the same identifiers than in the working Python/REST application. The connection stalls and goes into some sort of timeout. I also made some tests by putting wrong identifiers, and then it fails immediately with a different error message. It makes me think that something goes wrong after the authentication process. The error message I have is this one: Failed to contact the endpoint at http://yeti.ds.eurecom.fr:8080/v1/AUTH_da0d8589692741d1b2a82956568227e6 for discovery. Fallback to using that endpoint as the base url. I am wondering if there is some additional configuration to perform on the server or the network to make it work as expected. Could you please provide me with some support so that I can sort out what's going on? I could of course share the Python piece of code I am using for my testing. Thank you for your help.

5 4

zun containers
by Jaime Ibar 05 Jan '24

05 Jan '24

Hi, anyone using zun for containers? I'm getting an error when launching one. Thanks Jaime -- Jaime

1 0

RE: openstack-discuss Digest, Vol 62, Issue 108- Neutron Issue | Urgent Assistance
by Asma Naz Shariq 05 Jan '24

05 Jan '24

Hi Neutron_ Team I have deployed Multinode cluster of Openstack through kolla-ansible zed release. The problem I am facing is instances created cannot pick any Ip addresses (Rather than loop back ip or ipv6 addresses) from the created tenant networks with the default network type is vxlan. However, if I can assign ip manually to the eth0 interface in cirros instance, the interface is up with the ip address, but still, it can’t able to ping even its router gateway. Router can’t be able to ping instance ip address but only ping itself as verified below: The following troubleshooting steps, I have followed and concluded: ~ The Tenant network is created and its port: network: router_interface, network:dhcp, compute:nova are in admin up and active state. ~ The router interfaces are in up state and in complete nova zone. ~ The instance is running and active state and automatically pick ip address from the created tenant network as displayed in gui but inside the vm it can’t pick any ip address. ~ The security groups have been defined to allow icmp, tcp, udp for inbound/outbound traffic. Hence, I may not be able to ping and ssh instance from the controller node further these instances won’t be able to connect to the internet until the issue get resolved. Can you guide me how to resolve these issues related to network connectivity so I may able to send you the required files to troubleshoot easily? -----Original Message----- From: openstack-discuss-request(a)lists.openstack.org <openstack-discuss-request(a)lists.openstack.org> Sent: Tuesday, January 2, 2024 7:39 PM To: openstack-discuss(a)lists.openstack.org Subject: openstack-discuss Digest, Vol 62, Issue 108 Send openstack-discuss mailing list submissions to openstack-discuss(a)lists.openstack.org To subscribe or unsubscribe via email, send a message with subject or body 'help' to openstack-discuss-request(a)lists.openstack.org You can reach the person managing the list at openstack-discuss-owner(a)lists.openstack.org When replying, please edit your Subject line so it is more specific than "Re: Contents of openstack-discuss digest..." Today's Topics: 1. Re: [trove][victoria] can't connect to trove DB from outside - although ssh to the trove instance works (Tony Breeds) 2. Re: [trove][victoria] can't connect to trove DB from outside - although ssh to the trove instance works (dieter.dorra(a)hsnr.de) 3. Re: Trove installation filed (dieter.dorra(a)hsnr.de) 4. Re: Trove installation filed (KEREM CELIKER) 5. Re: [kolla] ceilometer and nova compute agent (KEREM CELIKER) 6. Re: ceilometer cli client install help (KEREM CELIKER) 7. [neutron] Bug deputy report (last week of 2023) (Bernard Cafarelli) 8. New OpenStack machine on new node not responding (kjme001(a)gmail.com) 9. Re: New OpenStack machine on new node not responding ( 韩光宇 ) ---------------------------------------------------------------------- Message: 1 Date: Fri, 29 Dec 2023 23:28:42 +1100 From: Tony Breeds <tony(a)bakeyournoodle.com> Subject: Re: [trove][victoria] can't connect to trove DB from outside - although ssh to the trove instance works To: dieter.dorra(a)hsnr.de Cc: openstack-discuss(a)lists.openstack.org Message-ID: <CAFT5D2RzaXi6==waA732R0PVe6H0OeKBwzF_qUSOTHPVfCu7Ww(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" On Fri, 29 Dec 2023 at 19:58, <dieter.dorra(a)hsnr.de> wrote: > > >From the guest vm I can ssh into the trove instance (so port 22 is > >open and accepting) From the guest vm I cannot reach port 3306 From > >within the trove instance I can reach port 3306 and mysql is > >functional > > It feels like the security group does not allow 3306, but the entry is > there (see etherpad) > > What puzzles me is that netstat in the trove instance does only show > listen to 3306 for tcp6 but not for tcp - whereas 22 listens for tcp6 > AND tcp > > root@ms57plain:~# netstat -anp | head -17 Active Internet connections > (servers and established) > Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name > tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 3867/systemd-resolv > tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1074/sshd > tcp 0 0 10.9.9.126:22 10.9.9.128:60126 ESTABLISHED 9412/sshd: root@pts > tcp 0 0 10.10.10.84:54326 10.0.0.120:5672 ESTABLISHED 1002/python3 > tcp 0 0 10.9.9.126:22 10.9.9.128:57880 ESTABLISHED 9021/sshd: root@pts > tcp 0 0 10.10.10.84:44266 10.0.0.120:5672 ESTABLISHED 1002/python3 > tcp6 0 0 :::3306 :::* LISTEN 4881/mysqld You can see here that mysql is listening on all interfaces via an IPv4-mapped IPv6 address (https://en.wikipedia.org/wiki/IPv6#IPv4-mapped_IPv6_addresses) and from your previous post we can see that there is an explicit ACCEPT for the lo interface. That's how you're able to get access to the DB from within the guest. It looks to me that whatever added the ' -A openstack-INPUT -p tcp -m tcp --dport 22 -j ACCEPT' to the guest's firewall didn't also add an explicit rule for the database. At this point I don't know if that's trove, nova or neutron. If I had to guess I'd say that there is a mismatch in the trove configuration and the networks assigned to the guest. For example how does --- network_driver = trove.network.neutron.NeutronDriver # provider management_networks = 98b0de37-40af-4859-81f2-d89a4df2d6df # trovemgmt # provider ## management_networks = 3928eb68-edf9-4cca-8fa6-151ed26b7c04 # trove-mgmt 3928eb68-edf9-4cca-8fa6-151ed26b7c04 # management_networks = 3928eb68-edf9-4cca-8fa6-151ed26b7c04 management_security_groups = 26c4af6e-56f0-4644-8c55-e96983c74c1d --- relate to the "dozenet" and "trovemgmt" networks. Tony. ------------------------------ Message: 2 Date: Sun, 31 Dec 2023 11:27:37 -0000 From: dieter.dorra(a)hsnr.de Subject: Re: [trove][victoria] can't connect to trove DB from outside - although ssh to the trove instance works To: openstack-discuss(a)lists.openstack.org Message-ID: <170402205718.409.7027996557330367167(a)lists01.opendev.org> Content-Type: text/plain; charset="utf-8" The problem is solved! I tested a newer trove image from https://tarballs.opendev.org/openstack/trove/images/ The Victoria image caused the problem, it never showed the exposed ports in "docker ps". The Zed image is working: ubuntu@dd:~$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 1741ae3e7815 mysql:5.7.29 "docker-entrypoint.s…" 4 minutes ago Up 4 minutes 0.0.0.0:3306->3306/tcp, :::3306->3306/tcp, 33060/tcp database ubuntu@dd:~$ Thank you all so much for your assistance and help!!! Happy new year!! ------------------------------ Message: 3 Date: Sun, 31 Dec 2023 16:49:39 -0000 From: dieter.dorra(a)hsnr.de Subject: Re: Trove installation filed To: openstack-discuss(a)lists.openstack.org Message-ID: <170404137950.409.18389774625483655904(a)lists01.opendev.org> Content-Type: text/plain; charset="utf-8" Hi, when you log in as user trove in the service project - can you launch an instance? "no valid host was found" sounds that nova has a problem... BR Dieter ------------------------------ Message: 4 Date: Mon, 01 Jan 2024 05:40:46 -0000 From: "KEREM CELIKER" <kmceliker(a)gmail.com> Subject: Re: Trove installation filed To: openstack-discuss(a)lists.openstack.org Message-ID: <170408764655.409.16151116383780837301(a)lists01.opendev.org> Content-Type: text/plain; charset="utf-8" Please provide and check the Trove guest agent log file (by default, /var/log/trove/trove-guestagent.log) for any errors or warnings.. Also share with us the logs output that we can take a look. By the way, dont forget to check this following link to troubleshoot; https://docs.openstack.org/trove/latest/admin/troubleshooting.html Kerem Çeliker ------------------------------ Message: 5 Date: Mon, 01 Jan 2024 05:46:32 -0000 From: "KEREM CELIKER" <kmceliker(a)gmail.com> Subject: Re: [kolla] ceilometer and nova compute agent To: openstack-discuss(a)lists.openstack.org Message-ID: <170408799208.407.10760598762569499228(a)lists01.opendev.org> Content-Type: text/plain; charset="utf-8" You dont need to create a custom nova container to measure instances metrics. Only can use the “openstack host show” and “openstack server list” to get basic stats on resource usage for hosts and instances. Also use tools, such as Ganglia or Graphite, to gather more detailed data. It’s up to you! Kerem Çeliker ------------------------------ Message: 6 Date: Mon, 01 Jan 2024 06:07:02 -0000 From: "KEREM CELIKER" <kmceliker(a)gmail.com> Subject: Re: ceilometer cli client install help To: openstack-discuss(a)lists.openstack.org Message-ID: <170408922210.407.17546497674894904858(a)lists01.opendev.org> Content-Type: text/plain; charset="utf-8" It seems that you have not gnocchi plugin on OSP All-In-One. Also your OSP has not correct openstack client version or you needed the install the gnocchi plugin correctly. Please check gnocchi plugin if installed.. Here is the cli’s ; • openstack plugin list and check for gnocchi in the output any issues.. or try it; • pip install python-gnocchiclient. Kerem Çeliker ------------------------------ Message: 7 Date: Tue, 2 Jan 2024 09:52:31 +0100 From: Bernard Cafarelli <bcafarel(a)redhat.com> Subject: [neutron] Bug deputy report (last week of 2023) To: OpenStack Discuss <openstack-discuss(a)lists.openstack.org> Message-ID: <CABHdKwov77XQ31h26vq6UvzyOjaANcU1F6zjY1opS_H2XZp=PQ(a)mail.gmail.com> Content-Type: multipart/alternative; boundary="0000000000001b8f3a060df29f3c" Hey neutrinos, and happy new year! Here is the bug reported between 2023-12-25 and 2023-12-31 (as per tradition, it was a quiet week) The firewall group is ACTIVE without associate with a router or any firewall policies - https://bugs.launchpad.net/neutron/+bug/2047325 neutron-fwaas bug, patch proposed: https://review.opendev.org/c/openstack/neutron-fwaas/+/904317 Best wishes -- Bernard Cafarelli

2 5

[neutron] Drivers meeting
by Rodolfo Alonso Hernandez 05 Jan '24

05 Jan '24

Hello Neutrinos: Today we have the Neutron drivers meeting at 14:00UTC. There is one topic in the agenda [1]: * https://bugs.launchpad.net/neutron/+bug/2047849: [RFE] Start using oslo messaging namespaces See you in the IRC Neutron channel. [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda

1 0

[TC][Monasca] Proposal to mark Monasca as an inactive project
by Sławek Kapłoński 04 Jan '24

04 Jan '24

Hi, I just proposed patch [1] to mark Monasca as inactive project. It was discussed during last TC meeting on 03.10.2023. Reasons for that are described in the commit message of the [1] but I will also put all of it here: previous cycle there wasn't almost any contributions to that project and most active contributors in last 180 days were Elod Illes and Dr. Jens Harbott who were fixing some Zuul configuration issues only. Here are detailed statistics about Monasca projects: Validating Gerrit... * There are 7 ready for review patches generated within 180 days * There are 2 not reviewed patches generated within 180 days * There are 5 merged patches generated within 180 days * Unreviewed patch rate for patches generated within 180 days is 28.0 % * Merged patch rate for patches generated within 180 days is 71.0 % * Here's top 10 owner for patches generated within 180 days (Name/Account_ID: Percentage): - Dr. Jens Harbott : 42.86% - Joel Capitao : 28.57% - Elod Illes : 28.57% Validate Zuul... Set buildsets fetch size to 500 * Repo: openstack/monasca-log-api gate job builds success rate: 82% * Repo: openstack/monasca-statsd gate job builds success rate: 95% * Repo: openstack/monasca-tempest-plugin gate job builds success rate: 81% * Repo: openstack/monasca-common gate job builds success rate: 84% * Repo: openstack/monasca-kibana-plugin gate job builds success rate: 83% * Repo: openstack/monasca-ceilometer gate job builds success rate: 100% * Repo: openstack/monasca-events-api gate job builds success rate: 83% * Repo: openstack/monasca-ui gate job builds success rate: 88% * Repo: openstack/monasca-specs gate job builds success rate: 100% * Repo: openstack/monasca-grafana-datasource gate job builds success rate: 100% * Repo: openstack/monasca-persister gate job builds success rate: 98% * Repo: openstack/monasca-notification gate job builds success rate: 93% * Repo: openstack/monasca-thresh gate job builds success rate: 100% * Repo: openstack/monasca-api gate job builds success rate: 76% * Repo: openstack/monasca-agent gate job builds success rate: 98% * Repo: openstack/python-monascaclient gate job builds success rate: 100% * Repo: openstack/monasca-transform gate job builds success rate: 100% What's next? According to the "Emerging and inactive projects" document [2] if there will be no volunteers who will step up and want to maintain this project before Milestone-2 of the 2024.1 cycle (week of Jan 08 2024) there will be no new release of Monasca in the 2024.1 cycle and TC will discuss if project should be retired. So if You are interested in keeping Monasca alive and active, please reach out to the TC to discuss that ASAP. Thx in advance. [1] https://review.opendev.org/c/openstack/governance/+/897520 [2] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… -- Slawek Kaplonski Principal Software Engineer Red Hat

8 14

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

04 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 see host_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.* and i get below error when i turn off an instance on the compute, logs are from masakari-instance-monitor *2024-01-03 13:01:15.574 1 DEBUG openstack.resource [-] Attribute [] not found in [<openstack.resource._ComponentManager object at 0x7fa051f48730>]: ''. __getattribute__ /var/lib/openstack/lib/python3.8/site-packages/openstack/resource.py:6222024-01-03 13:01:15.595 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 i need to create some masakari notifications for it to work in openstack? if yes how may i do it) below i have attached the logs from masakari-hostmonitor and masakari-engine and also some components which i created in openstack about masakari do you have any suggestion please let me know! Thank You

2 1

[magnum][cluster-api] Why magnum creating bunch of users
by Satish Patel 04 Jan '24

04 Jan '24

Folks, I have deployed Magnum-CAPI for testing and things working fine but just noticed magnum creating a bunch of users and have no idea what they are those for? This list is small in real I have 100s of them. is this normal? # openstack user list +----------------------------------+-----------------------------------------------------------------------+ | ID | Name | +----------------------------------+-----------------------------------------------------------------------+ | 01ff85efed43419486558864e35f39cf | 90e763f2-c566-4c1f-92f0-e36be5933538_08cae850a5bb47d998da180a7f0e2660 | | bd8c2337df0a451da92732aae1fe5f68 | abf42808-d67c-450e-88e0-a20e65f35232_08cae850a5bb47d998da180a7f0e2660 | | 81d6c4c23bd84d62ab3422f109ced3d5 | ee1b8a35-d23b-42eb-9574-edb6562b4147_08cae850a5bb47d998da180a7f0e2660 | | 988550004ee3413eba2bb20f73f24013 | 8eaf2db3-d13c-4849-a517-5528219fc32f_08cae850a5bb47d998da180a7f0e2660 | | a50a0b596a024edb8c4a9bae05d1844c | e7194788-4ae5-4e17-9c48-fa3bf4e65016_08cae850a5bb47d998da180a7f0e2660 | | 664e7708f64f4b9d8071dac8d9fc580f | ea999930-8d10-42b2-ae31-2236fffb07a1_08cae850a5bb47d998da180a7f0e2660 | | 67de8c5761564fdbba998cc7c2a14948 | 0ef17525-9ee5-4416-b3bc-f6ccd5a1f3b0_08cae850a5bb47d998da180a7f0e2660 |

2 2

[magnum] magnum-capi management cluster controle plane in HA
by Satish Patel 04 Jan '24

04 Jan '24

Folks, In the lab I have deployed a magnum-capi driver with a single node kind cluster and it works great. Now I want to take it to production and make sure my capi management cluster runs on a HA environment of k8s and survives all kinds of failure. I have deployed 3 node k8s using kubespray and deployed CAPI applications on top of it using clusterctl init command but it default created a replica of 1/1 for all pods. How do I tell clusterctl to create a replica with 3 for HA and how does data replication work? How do I take backup/restore of data in k8s cluster using clusterctl for disaster recovery? I have checked official documents but it's a little confusing so I'm asking question here to clear my doubts. Cheers! ~S

3 6

Re: [kolla-ansible][magnum] question
by Oliver Weinmann 03 Jan '24

03 Jan '24

Hi Franck, Great. Glad it works. That is the k8s version and the url where magnum will pull the container from. The official docs are quite helpful. In the latest Openstack release bobcat there is already some support for CAPI. It is not 100% working out of the Box but it looks very promising. I have taken my blog post offline since I didn’t manage to get it working. But I will look into it again in the next couple of days. Cheers, Oliver Von meinem iPhone gesendet > Am 03.01.2024 um 12:21 schrieb Franck VEDEL <franck.vedel(a)univ-grenoble-alpes.fr>: > > Hi Oliver, > and thanks a lot for your help. > I followed the instructions on the blog and indeed, with [trust] it works. > I'm trying to understand everything. what are the parameters for: > > --labels kube_tag=v1.21.11-rancher1,hyperkube_prefix=docker.io/rancher/ > > Thanks in advance > > Franck > > > >> Le 25 déc. 2023 à 19:26, Franck VEDEL <franck.vedel(a)univ-grenoble-alpes.fr> a écrit : >> >> Hi Oliver and thanks you for this help. >> >> I was wrong in my explications. >> I had seen this article (roksblog.de ) and I did what it said: >> I first tried: >> enable_cluster_user_trust = True in globals.yml >> It didn't work. >> >> I then made the modification in /etc/kolla/config/magnum.conf: >> cluster_user_trust = True >> >> Same problem. >> >> That's why I asked the question. Is this really the way to do it? >> If so, I will have to restart the containers (keystone?) >> >> Franck >> >> >> >>> Le 25 déc. 2023 à 18:40, Oliver Weinmann <oliver.weinmann(a)me.com> a écrit : >>> >>> Hi Frank, >>> >>> According to the official kolla docs the option needs to be in globals.yml >>> >>> Ensure that you understand the consequences before enabling this option. Inglobals.yml: >>> >>> In case this also doesn’t work, you can try: >>> >>> yoga) [vagrant@seed ~]$ cat /etc/kolla/config/magnum.conf >>> [trust] >>> cluster_user_trust = True >>> >>> *www.roksblog.de >>> >>> Cheers, >>> Oliver >>> >>> Von meinem iPhone gesendet >>> >>>> Am 25.12.2023 um 18:10 schrieb Franck VEDEL <franck.vedel(a)univ-grenoble-alpes.fr>: >>>> >>>> enable_cluster_user_trust = True >> >

1 0

New OpenStack machine on new node not responding
by kjme001＠gmail.com 02 Jan '24

02 Jan '24

hello, I added a new node to OpeStack. I can create a new instance on it. The instance creates itself without error, its IP address is assigned. But however, the connection over ssh to this new machine does not work for me, nor does ping. I have the network traffic passed, what else can I check why the new machine is not responding to me network-wise regards

1 0

[neutron] Bug deputy report (last week of 2023)
by Bernard Cafarelli 02 Jan '24

02 Jan '24

Hey neutrinos, and happy new year! Here is the bug reported between 2023-12-25 and 2023-12-31 (as per tradition, it was a quiet week) The firewall group is ACTIVE without associate with a router or any firewall policies - https://bugs.launchpad.net/neutron/+bug/2047325 neutron-fwaas bug, patch proposed: https://review.opendev.org/c/openstack/neutron-fwaas/+/904317 Best wishes -- Bernard Cafarelli

1 0

ceilometer cli client install help
by garcetto 31 Dec '23

31 Dec '23

good afternoon, i have a running kolla-ansible openstack all-in-one cluster, so far so good (zed version based on ubuntu). i have installed ceilometer, and then i am trying to use this command to show metrics, but seems i cannot find the right command option, what am i missing? " (my-virt-env) marcello@mg-ostack-119:~$ openstack metric resource list openstack: 'metric resource list' is not an openstack command. See 'openstack --help'. Did you mean one of these? service create service delete service list service provider create service provider delete service provider list service provider set service provider show service set service show " thank you.

3 2

[kolla] ceilometer and nova compute agent
by garcetto 31 Dec '23

31 Dec '23

good morning, i would like to measure instances metrics but i cannot understand if i need to add this package on nova containers or the apt package is already installed (or do i need to create a custom nova container?) https://docs.openstack.org/ceilometer/latest/install/install-compute-ubuntu… thank you.

3 2

Trove installation filed
by Tamim Wasif 31 Dec '23

31 Dec '23

Hello openstack team I can not install openstack database service Trove. its some times showing this error "No valid host was found" "polling request timed out" "can not create volume for instance ..." what can be the solution? from Tamim Wasif Software Engineer Teton Private limited

3 2