- Yaook - lists.alasca.cloud

Help needed: 3-Minute Survey for FOSS Backstage Talk

by Daniel Gerber

Dear ALASCA members, developers, supporters and friends, In a few days I will be giving a talk at this years FOSS Backstage in Berlin. To ensure that I represent the perspectives and priorities of our community accurately, as well as help guiding ALASCA’s work going forward, I would appreciate it if you could take a moment to answer this short survey: https://nextcloud.cloudandheat.com/apps/forms/s/qMYM4FiNfjkzfCzybSGcoFYM It should not take you more then 3 minutes, the answer are anonymous and can be given till Friday the 13th of March, 23:59. Please excuse duplicate notification of this survey and please share it within our community. Cheers, Daniel P.S: In case you need an English version please contact me directly! —— Dr. Daniel Gerber Softwaredeveloper ALASCA - Verband für betriebsfähige, offene Cloud-Infrastrukturen e.V. c/o Cloud&Heat Technologies GmbH Königsbrücker Straße 96 | 01099 Dresden +49 351 479 367 00 daniel.gerber(a)alasca.cloud | https://alasca.cloud/ Let's learn. Let's discuss. Let's inspire. Let's tech-talk. Alle News zu den ALASCA-Tech-Talks gibt es hier: https://alasca.cloud/alasca-tech-talks/ Verantwortliche i.S.d. § 55 Abs. 2 RStV: Dr. Marius Feldmann (Vorsitzender | Cloud&Heat Technologies GmbH) Josephine Seifert (Stellvertretende Vorsitzende) Steffen Brauß (Schatzmeister | Schwarz IT KG) Registergericht: Amtsgericht Dresden Registernummer: VR 12961 Steuernummer: 202/140/21049

March 5, 2026

Yaook at OpenInfra PTG

by Stefan Hoffmann

Hi everyone, for the first time, yaook is part of the OpenInfra ProjectTeamGathering in April.[1] Currently the time of our session is not fixed, but the PTG will take plase at 20-24 April 2026, I will create a 2-4h session for us. Feel free to already register[2] so we know whom to expect and OpenInfra sees, the session is used. Soon we will share a etherpad where topics can be added. If you have wishes for a specific timeframe/day contact me. Best Regards Stefan [1] lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org /thread/NDYECQOHPBHRNSBSSQCHAIB7LDPDC5XO/ [2] https://ptg.openinfra.org/

March 4, 2026

[v1.2.1] Bug at release update when computenodes in creating

by Stefan Hoffmann

Hi all, we found a bug with nova-compute nodes in creating since release v1.2.1 You will run into that issue when updating yaook to 1.2.1 or any newer version, if you have computenodes in state creating while updating the nova-compute-operator. We will try to build a fix, but maybe we just keep it as is. A workaround can be found in the issue[1] and after the upgrade and fixing once, the issue don't occur again. Also it is hopefully for the most environments possible to do the update when all nodes are finished with creation. If you want a fix, of cause, you can comment at the issue[1] or reply here. Best regards Stefan [1] https://gitlab.com/yaook/operator/-/issues/653

Feb. 20, 2026

Re: [Security Advisory] OSSA-2026-002

by Stefan Hoffmann

Correction: the fixed release is 1.2.1 release-pipeline: https://gitlab.com/yaook/operator/-/pipelines/2332251028 On Tue, 2026-02-17 at 18:24 +0100, Stefan Hoffmann via Yaook wrote: > Hi, > > today OpenStack announced that there is a CVE at nova, when using flat > image backend [1]. > We have further information at our Advisory [2]. > > If you DON'T have `use_cow_images=False` configured in nova.conf you > should be not affected. > > To mitigate this issue, upgrade to yaook release v1.3.0 (will be > released tomorrow) or pin the nova-compute image at nova-operator like > described here[2] to registry.yaook.cloud/yaook/nova-compute-2025.1- > ubuntu:4.1.183 > > Best regards > Stefan > > [1] https://security.openstack.org/ossa/OSSA-2026-002.html > [2] https://yaook.cloud/security-advisories-cve-2026-24708/

Feb. 17, 2026

[Security Advisory] OSSA-2026-002

by Stefan Hoffmann

Hi, today OpenStack announced that there is a CVE at nova, when using flat image backend [1]. We have further information at our Advisory [2]. If you DON'T have `use_cow_images=False` configured in nova.conf you should be not affected. To mitigate this issue, upgrade to yaook release v1.3.0 (will be released tomorrow) or pin the nova-compute image at nova-operator like described here[2] to registry.yaook.cloud/yaook/nova-compute-2025.1- ubuntu:4.1.183 Best regards Stefan [1] https://security.openstack.org/ossa/OSSA-2026-002.html [2] https://yaook.cloud/security-advisories-cve-2026-24708/

Feb. 17, 2026

ALASCA Community Goal - SBOM

by Stefan Hoffmann

Hi yaook folks, some days ago, we discussed with the ALASCA TSC what the community goal for 2026 could be. As already some projects are working on it, as well as yaook, we decided to create a SBOM for each project. The "official" goal is called: By the end of 2026, all of our ALASCA projects should have an SBOM or a tool to generate their SBOM.[1] I'm happy, that there is already some effort to implement that. Best regards Stefan [1] https://gitlab.com/alasca.cloud/governance/governance/-/blob/main/docs/alas… -- Stefan Hoffmann DevOps-Engineer Cloud&Heat Cloud&Heat Technologies GmbH Königsbrücker Straße 96 (Halle 15) | 01099 Dresden +49 351 479 367 36 stefan.hoffmann(a)cloudandheat.com | www.cloudandheat.com Green, Open, Efficient. Ihr Cloud-Service- und Cloud-Technologie-Provider aus Dresden. [1] Commercial Register: District Court Dresden Register Number: HRB 30549 VAT ID No.: DE281093504 Managing Director: Nicolas Röhrs Authorized signatory: Dr. Marius Feldmann [1] Ihr Cloud-Service- und Cloud-Technologie-Provider aus Dresden. https://www.cloudandheat.com/

Feb. 3, 2026

Participate with yaook at OpenStack PTG

by Stefan Hoffmann

Hi, at the last OpenInfra summit or so, we asked, if it would be possible to take part at the OpenStack ProjectTeamGathering with our yaook project. We have the opportunity now to do so, I just would need to register us. Do you want to have such a meeting, where we discuss, what the next steps are for the project? As we are not forced to follow the OpenStack release cycle, we are quite free, what to do there and for what time frame to discuss stuff. But I would like to discuss open tasks at the SBOM and image build streamline process. Maybe there are other topics as well. Best regards Stefan -- Stefan Hoffmann DevOps-Engineer Cloud&Heat Cloud&Heat Technologies GmbH Königsbrücker Straße 96 (Halle 15) | 01099 Dresden +49 351 479 367 36 stefan.hoffmann(a)cloudandheat.com | www.cloudandheat.com Green, Open, Efficient. Ihr Cloud-Service- und Cloud-Technologie-Provider aus Dresden. [1] Commercial Register: District Court Dresden Register Number: HRB 30549 VAT ID No.: DE281093504 Managing Director: Nicolas Röhrs Authorized signatory: Dr. Marius Feldmann [1] Ihr Cloud-Service- und Cloud-Technologie-Provider aus Dresden. https://www.cloudandheat.com/

Feb. 3, 2026

Re: Yaook SCS Operator hackathon 2026-02-26, Hamburg - save the date!

by Friedrich Zahn

Hi everyone, we now have an official announcement and a WIP agenda for the hackathon: https://alasca.cloud/alasca-focis-yaook-scs-operator-hackathon/ We already got some confirmation that there will be experts from both the Yaook community and SCS taking part. If you would like to participate, please drop me an E-mail so we can plan accordingly and keep you in the loop. Best regards Friedrich

Feb. 3, 2026

Release v1.1.0 "solves" immutable must have randomly generated names" but will disconnect nova-compute from MQ

by Stefan Hoffmann

Hi, regarding the immutable must have randomly generated names issue: The issue is "solved" in the latest release v1.1.0 BUT if a new compute- node with same name got created, the change will interrupt connectivity to MQ of the nova-compute POD.[1] As the nova-operator recreates the nova-compute-node, a new MQ user with the same username (but different resource name) get's created and than we have 2 MQ users one old "failing" one new. With rolling out [2] the old one can get deleted, but as the username at MQ is the same, the new one don't work for the nova-compute node anymore, till infra-operator recreates the user. So [2]will lead to an interruption of nova-compute MQ connectivity. One "solution" would be to delete the finalizer for all MQ users stuck in immutable-State before rolling out the release. Or you hope, no actions are done to our OpenStack, till the MQ user got updated. Feel free to discuss possible solutions at [1] Regards Stefan [1] https://gitlab.com/yaook/operator/-/issues/630 [2] https://gitlab.com/yaook/operator/-/merge_requests/3331 -- Stefan Hoffmann DevOps-Engineer Cloud&Heat Cloud&Heat Technologies GmbH Königsbrücker Straße 96 (Halle 15) | 01099 Dresden +49 351 479 367 36 stefan.hoffmann(a)cloudandheat.com | www.cloudandheat.com Green, Open, Efficient. Ihr Cloud-Service- und Cloud-Technologie-Provider aus Dresden. [1] Commercial Register: District Court Dresden Register Number: HRB 30549 VAT ID No.: DE281093504 Managing Director: Nicolas Röhrs Authorized signatory: Dr. Marius Feldmann [1] Ihr Cloud-Service- und Cloud-Technologie-Provider aus Dresden. https://www.cloudandheat.com/

Jan. 29, 2026

OpenStack CVE-2026-22797 Privilege Escalation via Identity Headers in External OAuth2 Tokens

by Stefan Hoffmann

Hi yaook users, today OpenStack published a CVE for a keystone middleware external_oauth2_token. As you can't activate this middleware with yaook currently, we are not affected. https://yaook.cloud/security-advisories-cve-2026-22797/ Best regards, Stefan -- Stefan Hoffmann DevOps-Engineer Cloud&Heat Cloud&Heat Technologies GmbH Königsbrücker Straße 96 (Halle 15) | 01099 Dresden +49 351 479 367 36 stefan.hoffmann(a)cloudandheat.com | www.cloudandheat.com Green, Open, Efficient. Ihr Cloud-Service- und Cloud-Technologie-Provider aus Dresden. [1] Commercial Register: District Court Dresden Register Number: HRB 30549 VAT ID No.: DE281093504 Managing Director: Nicolas Röhrs Authorized signatory: Dr. Marius Feldmann [1] Ihr Cloud-Service- und Cloud-Technologie-Provider aus Dresden. https://www.cloudandheat.com/

Jan. 15, 2026