May 2021 - openstack-discuss - lists.openstack.org

[neutron] CI meeting 4.05.2021 cancelled
by Slawek Kaplonski 03 May '21

03 May '21

Hi, Sorry for the late notice but I'm on PTO today and I will not be able to chair our team meeting so let's cancel it this week. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[neutron] Team meeting 4.05.2021 cancelled
by Slawek Kaplonski 03 May '21

03 May '21

Hi, Sorry for the late notice but I'm on PTO today and I will not be able to chair our team meeting so let's cancel it this week. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[all][tc] What's happening in Technical Committee: summary 30th April, 21: Reading: 5 min
by Ghanshyam Mann 03 May '21

03 May '21

Hello Everyone, Here is last week's summary of the Technical Committee activities, Sorry for missing to send this on Friday 30th April. 1. What we completed this week: ========================= Project updates: ------------------- ** None Other updates: ------------------ ** Updated TC onboarding guide for correcting the meeting times etc[1]. 2. TC Meetings: ============ * TC held this week meeting on Thursday; you can find the full meeting logs in the below link: - http://eavesdrop.openstack.org/meetings/tc/2021/tc.2021-04-29-15.00.log.html * We will have next week's meeting on May 6th, Thursday 15:00 UTC[2]. 3. Activities In progress: ================== TC Tracker for Xena cycle ------------------------------ TC is using the below etherpad for Xena cycle working item. We will be checking and updating the status biweekly in same etherpad. - https://etherpad.opendev.org/p/tc-xena-tracker Open Reviews ----------------- * Four open reviews for ongoing activities[3]. Starting the 'Y' release naming process --------------------------------------------- * Governance patch is up to finalize the dates for Y release naming process[4] * https://wiki.openstack.org/wiki/Release_Naming/Y_Proposals Others --------- * Swift and Ironic applying for "assert:supports-standalone" tag * Reduce office hours to one per week[5] * Update Nodejs Runtime to Nodejs14 From Nodejs10 for Xena Cycle[6] PTG ----- TC had discussions on various topics in virtual PTG. I have summarized the PTG discussion on ML[7]. 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[8]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [9] 3. Office hours: The Technical Committee offers a weekly office hour every Tuesday at 0100 UTC [10] 4. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://governance.openstack.org/tc/reference/tc-guide.html [2] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [3] https://review.opendev.org/q/project:openstack/governance+status:open [4] https://review.opendev.org/c/openstack/governance/+/789385 [5] https://review.opendev.org/c/openstack/governance/+/788618 [6] https://review.opendev.org/c/openstack/governance/+/788306 [7] http://lists.openstack.org/pipermail/openstack-discuss/2021-April/022120.ht… [8] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [9] http://eavesdrop.openstack.org/#Technical_Committee_Meeting [10] http://eavesdrop.openstack.org/#Technical_Committee_Office_hours -gmann

1 0

[openstack-helm] Meeting Cancelled
by Gage Hugo 03 May '21

03 May '21

Hey team, Since there are no agenda items [0] for the IRC meeting today May 4th, the meeting is cancelled. Our next meeting will be May 11th. Thanks [0] https://etherpad.opendev.org/p/openstack-helm-weekly-meeting

1 0

[CloudKitty] April 2021 - PTG Summary
by Rafael Weingärtner 03 May '21

03 May '21

Hello, CloudKitty community, Below is my summary of the CloudKitty session during the PTG meeting in April. - CloudKitty community -- we started discussing the CloudKitty community and how to get more people engaged with the project. If we were having physical summits, it would be easier to onboard people. However, that is not our case right now. Therefore, we agreed that if we improve the user stories of CloudKitty showcasing different use cases might help increase people's awareness. These use cases could be added to the following page: https://docs.openstack.org/cloudkitty/latest/#what-can-be-done-with-cloudki…. Furthermore, we also agreed to monitor Storyboard more: https://storyboard.openstack.org/#!/project_group/cloudkitty, to engage with people reporting bugs. - Review of past releases -- after discussing the CloudKitty community, we moved on to revisit the past release (Wallaby). We agreed that it might be interesting to add more effort to merge things at the beginning of the release cycle; then, we work from the middle to the end to stabilize things. This would allow/enable us to add more new features and bug fixes into the release. - CloudKitty Next release main focus -- we discussed that besides the already ongoing efforts to fix bugs, and create new features, we will try to work towards the following new features: - Reprocessing API - Reprocessing with data still on Backend - Reprocessing without data on the backend (for cases when the data has already been deleted) will not be addressed now. - V2 CI testing: https://review.opendev.org/c/openstack/cloudkitty-tempest-plugin/+/685344 - Date to start a new price for a metric Those are the main topics we covered during the PTG. If I forgot something, please let me know. Now, we just gotta work to keep evolving this awesome billing stack :) Link for the PTG Etherpad: https://etherpad.opendev.org/p/apr2021-ptg-cloudkitty -- Rafael Weingärtner

1 0

[charms] OpenStack Charms 21.04 release is now available
by Peter Matulis 03 May '21

03 May '21

The 21.04 release of the OpenStack Charms is now available. This release brings several new features to the existing OpenStack Charms deployments for Queens, Stein, Ussuri, Victoria, Wallaby and many stable combinations of Ubuntu + OpenStack. Please see the Release Notes for full details: https://docs.openstack.org/charm-guide/latest/2104.html == Highlights == * OpenStack Wallaby OpenStack Wallaby is now supported on Ubuntu 20.04 LTS (via UCA) and Ubuntu 21.04 natively. * Ceph Pacific The Pacific release of Ceph is now supported, starting with OpenStack Wallaby. * Denying service restarts and charm hook calls The deferred service events feature can be enabled on a per-charm basis to avoid sudden service interruptions caused by maintenance and operational procedures applied to the cloud. This allows operators to apply the service restarts and hook calls at their prerogative. * Cloud operational improvements Improvements have been implemented at the operational level through the addition of scaling down actions for the hacluster and nova-compute charms. It is also now possible to query a nova-compute unit's hypervisor node name, list all hypervisor node names, and mark individual Ceph OSDs as 'out' or 'in'. * Sync Juju availability zones with Nova availability zones The nova-cloud-controller charm has a new action that synchronises Juju availability zones with Nova availability zones. This effectively configures host aggregates in Nova using the AZs already known to the nova-compute application. * Tech-preview charms Two tech-preview charms are now available for the deployment of OpenStack Magnum. The list of Manila charms is also expanded by two tech-preview charms. The new charms are magnum, magnum-dashboard, manila-dashboard, and manila-netapp. * Documentation updates Ongoing improvements to the OpenStack Charms Deployment Guide, the OpenStack Charm Guide, and the charm READMEs. A central documentation presence is also now available: https://ubuntu.com/openstack/docs . == OpenStack Charms team == The OpenStack Charms team can be contacted on the #openstack-charms IRC channel on Freenode. == Thank you == Lots of thanks to the below 37 contributors who squashed 54 bugs, enabled new features, and improved the documentation! Alex Kavanagh Alvaro Uria Arif Ali Aurelien Lourot Bartosz Woronicz Bayani Carbone Billy Olsen Chris MacNaughton Corey Bryant Cornellius Metto Cory Johns Dariusz Smigiel David Ames Dmitrii Shcherbakov Edward Hope-Morley Erlon R. Felipe Reyes Frode Nordahl Garrett Thompson Hemanth Nakkina Hernan Garcia Ionut Balutoiu James Page James Vaughn Liam Young Marius Oprin Martin Kalcok Mauricio Faria Nicolas Bock Nobuto Murata Pedro Guimaraes Peter Matulis Przemysław Lal Robert Gildein Rodrigo Barbieri Seyeong Kim Yanos Angelopoulos -- OpenStack Charms Team

1 0

[wallaby][magnum] Cluster Deployment Unhealthy
by Ammad Syed 03 May '21

03 May '21

Hi, I have upgraded my magnum environment from victoria to wallaby. The upgrade went successfully. When I am trying to deploy a cluster from template, the status of cluster shows UNHEALTHY but create complete. I have logged into the master nodes and found no error message in heat logs. The nodes status still sees NotReady. [root@k8s-cluster-iomfrpuadezp-master-0 kubernetes]# kubectl get nodes --all-namespaces NAME STATUS ROLES AGE VERSION k8s-cluster-iomfrpuadezp-master-0 NotReady master 14m v1.18.16 k8s-cluster-iomfrpuadezp-node-0 NotReady <none> 9m51s v1.18.16 Also there is no pods running in kube-system namespace. [root@k8s-cluster-iomfrpuadezp-master-0 kubernetes]# kubectl get pods --all-namespaces No resources found I have checked the logs, the flannel was deployed. + printf 'Starting to run calico-service\n' + set -e + set +x + '[' flannel = calico ']' + printf 'Finished running calico-service\n' + set -e + set +x Finished running calico-service + '[' flannel = flannel ']' + _prefix=quay.io/coreos/ + FLANNEL_DEPLOY=/srv/magnum/kubernetes/manifests/flannel-deploy.yaml + '[' -f /srv/magnum/kubernetes/manifests/flannel-deploy.yaml ']' + echo 'Writing File: /srv/magnum/kubernetes/manifests/flannel-deploy.yaml' Writing File: /srv/magnum/kubernetes/manifests/flannel-deploy.yaml ++ dirname /srv/magnum/kubernetes/manifests/flannel-deploy.yaml + mkdir -p /srv/magnum/kubernetes/manifests + set +x + '[' '' = 0 ']' + /usr/bin/kubectl apply -f /srv/magnum/kubernetes/manifests/flannel-deploy.yaml --namespace=kube-system podsecuritypolicy.policy/psp.flannel.unprivileged created clusterrole.rbac.authorization.k8s.io/flannel created clusterrolebinding.rbac.authorization.k8s.io/flannel created serviceaccount/flannel created configmap/kube-flannel-cfg created daemonset.apps/kube-flannel-ds created I tried to deploy the flannel again, but it showing unchanged. [root@k8s-cluster-iomfrpuadezp-master-0 heat-config-script]# kubectl apply -f /srv/magnum/kubernetes/manifests/flannel-deploy.yaml --namespace=kube-system podsecuritypolicy.policy/psp.flannel.unprivileged configured clusterrole.rbac.authorization.k8s.io/flannel unchanged clusterrolebinding.rbac.authorization.k8s.io/flannel unchanged serviceaccount/flannel unchanged configmap/kube-flannel-cfg unchanged daemonset.apps/kube-flannel-ds unchanged The other thing I have noticed that cluster deployment still uses old parameters of victoria like heat_agent_tag and others. Its not using latest default tags of wallaby release. I am using magnum on ubuntu 20.04. The other components in stack are already upgraded to wallaby release. -- Regards, Ammad Ali

3 3

[release] Meeting Time Poll
by Herve Beraud 03 May '21

03 May '21

Hello We have a few regular attendees of the Release Management meeting who have conflicts with the current meeting time. As a result, we would like to find a new time to hold the meeting. I've created a Doodle poll[1] for everyone to give their input on times. It's mostly limited to times that reasonably overlap the working day in the US and Europe since that's where most of our attendees are located. If you attend the Release Management meeting, please fill out the poll so we can hopefully find a time that works better for everyone. For the sake of organization and to allow everyone to schedule his agenda accordingly, the poll will be closed on April 5th. On that date, I will announce the time of this meeting and the date on which it will take effect. Thanks! [1] https://doodle.com/poll/ip6tg4fvznz7p3qx -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

1 5

[oslo] Stepping down as Oslo core
by Ken Giusti 03 May '21

03 May '21

Hi all, The time has come to face the fact that I'm unable to give my role as an Oslo core contributor the attention and effort it deserves. I'd say that it has been great to work will all of you - and it most certainly has - but that would be a bit premature because this isn't "good bye". I'll still be kicking around the oslo.messaging project, helping out as time permits. Cheers -- Ken Giusti (kgiusti(a)gmail.com)

3 2

[barbican][oslo][nova][glance][cinder] cursive library status
by Brian Rosmaita 03 May '21

03 May '21

Hello Barbican team, Apologies for not including barbican in the previous thread on this topic: http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019430… The situation is that cursive is used by Nova, Glance, and Cinder and we'd like to move it out of the 'x' namespace into openstack governance. The question is then what team would oversee it. It seems like a good fit for Oslo, and the Oslo team seems OK with that, but since barbican-core is currently included in cursive-core, it make sense to give the Barbican team first dibs. From the consuming teams' side, I don't think we have a preference as long as it's clear who we need to bother about approvals if a bugfix is posted for review. Thus my ask is that the Barbican team indicate whether they'd like to move cursive to the 'openstack' namespace under their governance, or whether they'd prefer Oslo to oversee the library. Thank you! brian

5 5