June 2023 - openstack-discuss - lists.openstack.org

Monitoring
by Murilo Morais 12 Jun '23

12 Jun '23

Good morning everybody! Guys, which monitoring stack do you recommend to monitor Host and VM resources? Or what monitoring strategies do they recommend?

3 3

[tacker] Skip weekly IRC meeting
by Yasufumi Ogawa 11 Jun '23

11 Jun '23

Hi team, Since we'll have PTG this week, I would like to skip the next IRC meeting on Jun 13. Thanks, Yasufumi

1 0

[magnum] kubectl loses access after 31 days
by Vivian Rook 09 Jun '23

09 Jun '23

After 31 days I lose kubectl access to magnum clusters. This has happened consistently for any cluster that I have deployed. The clusters run just fine, though around 31 days of operation kubectl cannot connect, and the web service shows the service as down (Though the web service on the cluster is responding enough to say that nothing is working, so the cluster has not completely crashed) All kubectl commands have a long pause (about 10 minutes) then gives errors like: Error from server (Timeout): the server was unable to return a response in the time allotted, but may still be processing the request (get deployments.apps) Unable to connect to the server: stream error: stream ID 11; INTERNAL_ERROR; received from peer I have a little more information in https://phabricator.wikimedia.org/T336586 It feels like a cert is expiring as it always seems to happen right about 31 days after deployment. Does magnum have some kind of certificate like that? I checked the kubectl certs, they were set to be fine for years, so I don't think it is them unless I didn't check them correctly (Let's not discount that possibility, I totally could have read the wrong bit of the cert). I can still generate a new kubectl config file with openstack coe cluster config <cluster> Though the resulting configuration will have the same issue as the original config (long pause, then timeout errors). I have also tried to run: openstack coe ca rotate <cluster> Which is accepted and seems to run fine, but after that point if I regenerate a kubeconfig file as above I get new errors when running kubectl: Unable to connect to the server: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "<cluster>") If the key rotation would work, and I'm not doing it correctly, I would be delighted to hear how to run it correctly. Though ideally I would like to find where the original key is failing, and if it is an expiration, how to set it to a longer time. Thank you! -- *Vivian Rook (They/Them)* Site Reliability Engineer Wikimedia Foundation <https://wikimediafoundation.org/>

1 1

[release] Release countdown for week R-16, June 12-16
by Thierry Carrez 09 Jun '23

09 Jun '23

Development Focus ----------------- The bobcat-2 milestone will happen in next month, on July 6, 2023. 2023.2 Bobcat-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/bobcat/schedule.html for details. General Information ------------------- Please remember that libraries need to be released at least once per milestone period. At milestone 2, the release team will propose releases for any library that has not been otherwise released since milestone 1. Other 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. At milestone-2 we also freeze the contents of the final release. If you have a new deliverable that should be included in the final release, you should make sure it has a deliverable file in: https://opendev.org/openstack/releases/src/branch/master/deliverables/bobcat You should request a beta release (or intermediary release) for those new deliverables by milestone-2. We understand some may not be quite ready for a full release yet, but if you have something minimally viable to get released it would be good to do a 0.x release to exercise the release tooling for your deliverables. See the MembershipFreeze description for more details: https://releases.openstack.org/bobcat/schedule.html#b-mf Finally, now may be a good time for teams to check on any stable releases that need to be done for your deliverables. If you have bugfixes that have been backported, but no stable release getting those. If you are unsure what is out there committed but not released, in the openstack/releases repo, running the command "tools/list_stable_unreleased_changes.sh <cycle_name>" gives a nice report. Upcoming Deadlines & Dates -------------------------- OpenInfra Summit in Vancouver: From June 13 to June 15, 2023 Bobcat-2 Milestone: July 6, 2023 -- Thierry Carrez (ttx)

1 0

[ironic][ops] Forum Session at OIS Vancouver 2023
by Iury Gregory 09 Jun '23

09 Jun '23

Hello everyone, I would like to invite everyone interested in ironic to join our Forum Session next week during the Open Infrastructure Summit in Vancouver! The forum session *Ironic: Our Future starts Now! *will be held on *Wed, June 14, 10:20am - 10:50am | Vancouver Convention Centre - Room 9* This is a chance to provide feedback to our work, see you all next week in Vancouver! -- *Att[]'s* *Iury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Ironic PTL * *Senior Software Engineer at Red Hat Brazil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 0

[glance][ops][ptg] glance operator event at the summit/PTG
by Brian Rosmaita 09 Jun '23

09 Jun '23

Hello operators, Come by and meet members of the Glance project team and give us feedback, unusual use cases, feature requests, etc. Wednesday 14 June 15:10-15:40 (UTC-7) Table #13 in the PTG area etherpad: https://etherpad.opendev.org/p/vancouver-june2023-glance

1 0

[cinder][ops] cinder operator events at the summit/PTG
by Brian Rosmaita 09 Jun '23

09 Jun '23

Hello operators, Just want to alert you about some opportunities to give feedback to the Cinder project team while you're at the summit or PTG: Wednesday 14 June, 11:40-12:10 Forum session: Cinder, the OpenStack Block Storage service ... how are we doing? (Looking for feedback from operators, vendors, and end-users) Vancouver Convention Centre - Room 9 Wednesday 14 June, 15:50-16:20 PTG session: Operator Half-Hour (Focus on operator feedback) Table #13 in the PTG area Thursday 15 June, 16:40-17:10 PTG session: Open Discussion with the Cinder project team (Focus on developers, but willing to discuss anything, really) Table #13 in the PTG area

1 0

[cinder][ptg] cinder PTG schedule
by Brian Rosmaita 09 Jun '23

09 Jun '23

Hello Argonauts, We're going to have a small presence at the PTG next week, so we've only scheduled 3 sessions: Wednesday 14 June 10:20-10:50 Support for NVMe-OF in os-brick 15:50-16:20 Cinder Operator Half-Hour Thursday 15 June 16:40-17:10 Open Discussion with the Cinder project team All times are Vancouver time (UTC-7) and all will take place at Table #13 in the PTG area. Here's the Cinder PTG etherpad: https://etherpad.opendev.org/p/vancouver-ptg-june-2023 cheers, brian

1 0

[cinder][all] EOL EM branches
by Rajat Dhasmana 09 Jun '23

09 Jun '23

Hi, We had a discussion in the last cinder meeting regarding making EM branches EOL for the cinder project[1]. The discussion started because of the CVE fixes where we backported to active stable branches i.e. Yoga, Zed and 2023.1 but there were no backports to further EM stable branches like Xena, Wallaby ... all the way to Train. Cinder team doesn't see much merit in keeping these EM stable branches alive since there is rarely any activity that requires collaboration and if there is, it is usually by the core cinder team. Following are some of our reasons to EOL these branches: 1) We have less review bandwidth even for active stable branches (Yoga, Zed and 2023.1) 2) No one, apart from the project team, does backport of critical fixes implying that those branches aren't used much for collaboration 3) Will save gate resources for some periodic jobs and the patches proposed 4) Save project team's time to fix gate issues We, as the cinder team, have decided to EOL all the existing EM branches that go from Train to Xena. It was agreed upon by the cinder team and no objections were raised during the upstream cinder meeting. We would like to gather more feedback outside of the cinder team regarding if this affects other projects, deployers, operators, vendors etc. Please reply to this email with your concerns, if you have any, so we can discuss again and reconsider our decision. Else the week after the summit we will be moving forward with our current decision. If you will be at the Vancouver Summit, you can also give us feedback at the cinder Forum session at 11:40 am on Wednesday June 14. [1] https://meetings.opendev.org/irclogs/%23openstack-meeting-alt/%23openstack-… Thanks Rajat Dhasmana

8 14

[kolla] Image building process getting stuck
by Satish Patel 09 Jun '23

09 Jun '23

Folks, I am trying to build images using 2023.1 kolla tag but every time it's getting stuck here and there and I have to ctrl+c and re-run the build. It's very frustrating. How do CI jobs build images without getting stuck? Because of that I have to build images role-by-role instead of all images in a single shot. Example, This is stuck here since 24 hours and not moving at all : https://paste.opendev.org/show/bf1rRhg9V3BCy4KmHPRg/

1 0