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

[puppet] Sessions in June 2023 PTG
by Takashi Kajinami 12 Jun '23

12 Jun '23

Hello, I'm attending the upcoming OpenInfra Summit and PTG at Vancouver so would like to moderate some puppet sessions in PTG. I've reserved slots from 14:30 to 16:20 on Wednesday. However we can be flexible so please let me know if you are interested but have any conflicts. https://etherpad.opendev.org/p/vancouver-june2023-puppet-openstack I've added a few topics including the recent discussion about module modernization. However it'd be nice if we can have a few more topics, especially any feedback from users or (potential) new contributors. Please add your name and topics if you are planning to join us. Thank you, Takashi

4 3

[kolla-ansible][ovn][ovs] connection dropped and inactivity errors
by Satish Patel 12 Jun '23

12 Jun '23

2 1

[neutron][ptg] PTG schedule
by Rodolfo Alonso Hernandez 12 Jun '23

12 Jun '23

Hello all: This is the PTG week and we are thrilled to have you there. Just as a heads-up, on Tuesday at 11:20 [1] we have the "*Neutron meet and greet: Operators feedback session*". Join us to share your feedback. We have also booked the* table 15* [2] on Wednesday and Thursday, from 9:00 to 12:50. Please remember our previously used etherpad [3] is now combined in the PTG generated etherpad [4]. Please use this last link [4]. Regards and see you tomorrow! [1]https://vancouver2023.openinfra.dev/a/schedule [2]https://ptg.opendev.org/ptg.html [3]https://etherpad.opendev.org/p/neutron-vancouver-2023 [4]https://etherpad.opendev.org/p/vancouver-june2023-neutron

1 0

[tc] No weekly meeting on June 13
by Nikolla, Kristi 12 Jun '23

12 Jun '23

Hi all, As this week is the Open Infra Summit and PTG there will be no weekly meeting of the TC on June 13. The next meeting will be Tuesday, June 20, 2023. Best, Kristi Nikolla

1 0

package installation
by Mohd Haniff Bin Abdullah 12 Jun '23

12 Jun '23

Hi, We have installed OpenStack CLI VM and can access to CLI. Our VM does not have internet connection. Thus, we need the whole package to be downloaded and sftp to the VM. Where could we get the package? I got this from previous colleague, but he left our company and we don't have a clue where he got that packages.tar.gz. Would you please help us? Thank you so much! [cid:image001.png@01D99D66.73040A90] Regards, Haniff

1 0

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