Technical Oversight Committee, August 4 2026

[clears throat] >> In all the tools meeting 4th of August we have the usual agenda without updates, working group updates. So, let's start with reviewing the action items. So, last time we approved one PR and I created another >> [clears throat] >> We approved an RFC and I created a PR for the RFC number general of that one. So, most probably that will show up in the dashboard. And we didn't have any other action items. So, then go to the dashboard. Yes, here is the uh the PR to assign the RFC number. I didn't notice that there is a number for already. >> [clears throat and cough] >> So, this was about the deprecation of the CF on Kubernetes working group. Are you going to approve I just Okay, I can just merge because Okay, approvals are coming. >> I have my rubber stamp, so it feel ashamed not to use it. >> [clears throat] >> I see. Okay. Okay, I I imagine it's hard for Ruben to approve PRs on that beautiful place. >> [laughter] >> Okay, I'm going to merge. >> Looks good to me. >> Verbal approval. >> Thanks. Okay. >> Splash twice if you're okay with it. Sorry. >> Hey then, uh continue with the uh RFCs. So, there is the one about AWS LC addition to the uh HAProxy. So, still sort of and you got uh replies on your comments on that RFC. >> Yeah, I've set a reminder for next Monday. >> Mhm. >> Uh >> Okay, I'm still on vacation. >> Mhm. >> Yeah, all fine. Sure. Okay, the next one about um 64 support. >> [clears throat] >> So, we had the initial meeting with AWS. We plan to continue that tomorrow. Um is that correct, Chris? I didn't see any meeting invitation. >> Um I haven't sent out a meeting invitation. Um Let me Do we I mean, do we have an update for them? I thought we left it kind of as I know you're going on vacation, so there was a little bit of a time crunch there, but >> Um not a major one. >> [sighs and gasps] >> So, basically we discussed what the situation with the two questions here are and So, from AWS side, they want to check about options uh for us get credits for the costs which the uh the validation builds and release will generate for um So, there was no concrete answer uh last week. On the other one, uh so this is seen as a project from AWS side. Uh that means they will work with us uh until the contribution is ready for approval and review. But after that, they don't have any uh options in that project to uh be active with an approver to maintain the contribution. So, that one will be with us uh to maintain the community. >> But the credits will go on beyond the duration of the project? >> This is in clarification. >> Uh yeah, it seemed like they were amenable to something like that, but they they need to get approval for that. Um but yeah, they they they won't be able to maintain it, but hopefully they can give us credit support. Um Yeah, and hopefully I mean, I'm I'm cautiously optimistic they can give us credit support beyond that for the AWS accounts that we're currently using outside of this, but we'll see. >> That'd be great. >> Did they provide any context on why they are suddenly interested in this? Like why now? What like Arm has been out for a while. Cloud Foundry has been out for a while, so I was wondering why they are suddenly interested in funding this and doing it. I mean >> They see that uh Cloud Foundry workloads are running on AWS and there's opportunity to um Um for they they have interest to run that on Graviton, which is a better option for AWS. Um So, from that perspective, so they see that workloads uh noticeable amount of workloads Cloud Foundry workloads are running on their infrastructure, and it makes sense for them to support uh that one on Graviton. So, if people are running Cloud Foundry on Graviton, this will be a good investment for AWS. >> I don't mean to be a pessimist, but we have to be a rounding error of all the EC2 instances that are out there, and they went, "Oh, the Cloud Foundry ones are X%?" Something feels funky. But, I mean, I'm happy to take this, but like it's definitely It still feels funny. >> [laughter] >> We hear We hear from We hear from customers that they're interested in the Graviton support, and I don't think that's necessarily coming from So, I think their account teams are pushing pushing them that when they're setting up new environments, they're pushing them that direction. So, like they definitely are motivated. Like We definitely through games of telephone heard like, "Hey, does it work on Graviton?" We're like, "No, it doesn't." Um so, they may it may be customer pressure cuz it's cheaper as well um coming from them that I don't know. I It would help us to know if if they Well, I guess it's always it's always helpful to hear from customers from our side, but if they're doing the work, then it's happening here. >> Or maybe there's secretly some like shadow Cloud Foundry deployments that no one knows about running on AWS run by some secret organizations. Secretly, like 50% of AWS traffic is people running Cloud Foundry [laughter] we don't know about. >> 52% definitely. Yep. >> Hey Han, remind me when you go on vacation. The end of this week? >> Yes. >> Okay. >> Yeah. Yeah, how do you what is your opinion in case we only get credits and uh do we don't get any maintenance support long-term maintenance support only uh >> [clears throat] >> This is the open question for the community now. So, I'm trying to clarify from SAP side whether we uh this is something we also can support. So, >> [clears throat] >> I hear that from Broadcom side you also looks like interested to have this. >> I guess there's that these customers whose AWS reps have been kind of trying to convince them to use it. If if that counts as interest, then yes. >> Yeah, I think we're Yeah, we're interested. I think there it would lower customers costs of running it, too. So, that's a good thing. So, we're I think we're interested enough to not not object to inheriting like the project's inheriting supporting it. And we can always can remove it if need be. I mean, though I mean, took us 10 years to remove PowerPC. So, it it could happen. >> I mean, uh if they do the contribution, it will be for uh the latest 10, so also is my understanding. That means we have couple of years to see how the adoption is going and whether it should be also an investment for the community to add support for the next long-term release of Ubuntu. Yeah. Okay. >> There's one other I don't know minor details. It will help for local development as well on Macs cuz I think we've been fighting uphill battles with Rosetta on a Mac. So like it will it will make our it will make our lives better on the Bosch team to have arm support and just not have to deal with crazy craziness of Rosetta translation. Which is well worth it like works for improvements, but Sorry, Chris. >> Be nice if Bosch light local worked again. On the Macs. That was I know that's channel many moons ago, but that was a nice user experience. >> We do Rubens done a bunch of work to make it work with Docker. So I definitely I don't know what state that's in. So if you have if you got a Mac with Rosetta, you can you can use the Docker CPI and it >> [gasps] >> the setup I don't think we have any good docs on the setup from Kelly on the Bosch team. Um but it is possible. Like I've I've set like you can tell it like I don't know how I've told told an AI agent to like set it up with a Docker CPI on the local Mac and it will do it. >> Mhm. >> Okay. >> I have a project called instant Bosch. So it's GitHub our coaster {slash} instant-dash-bosch. Uh and I think there's still an open PR there to uh make it work uh on Mac OS with Apple silicon. Um but there's still some things that I'm tracking. That's why it's not merged. It It works, but it's You need to build a custom stem cell. Um make it work. >> Got you. >> Okay. >> Just curious. >> Okay. >> Well, I'll I'll respond to AWS and you uh Behan and just check in see if there's updates and see if we want to schedule a call for the next couple of days. >> Mhm. Okay. Thanks, Chris. Mhm. Yeah. Yeah, this is the status on this one. So, still full time progress. Um >> [clears throat] >> regarding updates here of Do we have the storage CLI? It's all there. Stefan, you're muted if you are talking. >> Yeah. Uh I haven't checked That's what I say. What are all commits of the focal remover? I mean, well, in the latest copy release that was released I think today. [clears throat] So, might be that it is closed and done. >> Mhm. Okay. >> I can take care of it next week. >> [snorts] >> Actually, this one is already in progress. Uh uh Matthew is working on that one, Resolute Raccoon. I think at some point I also linked couple of PRs in that direction. Yeah, it's in progress. Um >> One thing I suppose I could mention here about that is we are adding when we did the Noble the Noble stem cell work, we we did a bunch of just sort of swapping Noble in for Jimmy in CI pipelines. And this time around we are we are adding we're making it an array of supported stem cells. Um so it's not just a hard cutover cuz that was really painful of like we had multiple months of the Bosch pipelines didn't work cuz they'd been cut over to Noble um and there was sort of a like well, we got to get them working to be able to cut a Bosch release. And so which may slightly like so we will have a build per stem cell line which may slightly increase infrastructure costs, but I don't expect it to be a huge percentage. Like it should just be deployed like for the length of that CI run, it shouldn't be a long-term large infrastructure increases. But we are making progress on the resolute stem cell. >> Yeah. Okay. And issues um Now, we have the two two open issues about code quality we touched last week. And the Concourse automation. >> Oh, Concourse automation is actually running again with that means the arc automation for Cloud Foundry and for Concourse that works. Uh there are two left overs that is one or two additional workflows is remove individual XSS repos so I've proposed a PR but wanted to wait for the approval by uh Taylor so that we do not because there are a lot of individual users in in the Concourse repos. And the second is then this uh checking for inactive users in the cloud from in the Concourse org additionally. >> Mhm. Is that on me? Should I okay. >> I don't know. Whatever. It's just I try to list everything that I found which was still missing. >> So, we we have again the beginning of the month and we didn't have any uh appear suggested removals. >> Oh, everybody is active, right? >> [laughter] >> There are no uh suggestions. So, the way how it works uh when there are no contributors for removal, no PR is open, but there couple of people inactive with roles. In that case, it's only worked into uh >> Mhm. Mhm. >> the GitHub action work. So, this was the agreement at that time when we uh decided how to implement um Let's see what if we don't get any any uh suggestion for removal in the next months, maybe I can open issue with the currently inactive people from the works we have. Mhm. >> [clears throat] >> Okay. I noticed that I got also sent to Concourse organization in Git on GitHub. >> Yes. >> [laughter] >> That's something uh Okay. Um >> That's not a bug, that's a feature. >> No, that's by intention actually. >> Yeah. Okay, then we are done with the dashboard automation cost update. I posted into our cost channel. Um, so it was good with uh was able to keep the level until the end of the month. And now the forecast for the current month is looking good. I just posted an update there. Yeah, it will be great if um in the working groups we monitor the cost and then take action if something increases or have an understanding why something is increasing. And then other one is about now the vacation season. Um, I pasted a thread in the posted a thread in our private channel so you can just put a thumbs up or or down to the dates so that we know which meetings we should cancel. In case we don't have quorum. It's an action item for everyone. But Chris already did the action item. Thanks. Okay, do you have anything else? >> Nope, just envious of where Ruben's hiding at. >> Um, so the the election result they got merged already? Or not? Like when will the TOC changes be effective? I've not looked at GitHub much, but that's why I want to attend. As in what when will Matthew uh be active as a person in GitHub? >> I think Chris had said starting this week is when we make it effective. >> Yeah, it should be effective now, but I I I mean I haven't opened a PR to change anything in the um in the community repo or anything like that, so you all can can set up the permissions, but yeah, it should should be good to go now. >> Should I open that PR? >> Yeah. >> Sure. >> All right, I'll do it. >> Yeah, that should be a What's actually uh there's a TOC file, right? That that's driving the org automation? Yeah. >> Yeah. >> And then you two will get an invite to the Concourse org. >> Sweet. >> That's automatically. And you see repos you never wanted to see. >> [laughter] >> What's the gummy you can never leave. >> [laughter] >> Okay. Anything else? >> Just a friendly reminder to register for Cloud Foundry Summit. Uh we're nearly at 100 registrations. It'll be nice to see that uh number trending upwards every week. >> Great. >> That's great to hear. >> I love that it's a summit again and not just a summit sounds way more awesome. Plus it makes all my t-shirts valid again. >> Yeah. Good day. It's 100. Looks very promising to me at this time of >> [laughter] >> But I don't know how the in the previous CFDs the numbers have been developing. >> [clears throat] >> Usually people register towards the end >> [clears throat] >> of the registration period. Yeah. Okay. Anything else? I will be out in the next 3 month 3 3 weeks, sorry. So someone else needs to moderate. >> [gasps] >> In case we can have quorum and have meetings. >> [clears throat] >> Then yeah. Take care. Have a nice day, evening, morning and see you in 3 weeks. >> Yeah. >> All right. Have a good vacation. Bye.