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

12 Jan '24

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

2 1

[senlin] Rolling updates issues future support and alternatives
by Devin Patterson 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 11 Jan '24

11 Jan '24

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

1 0

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

11 Jan '24

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

1 0

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

10 Jan '24

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

4 6

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

10 Jan '24

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

2 1

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

10 Jan '24

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

1 0