 Hi everybody. So, yeah, let's start this new weekly inframitting. The first topic that I want to cover is According to Paul, we can move the meeting times midi time at 430 UTC. I mean, that's the time that where most of the people are available. So, I hope we will have more people next week. So, the second topic is regarding the migration from ACS to AKS. Most of the services that we need on now, we're running on AKS. The only one that we did not migrate is repo.azure, which is an NGENIX proxy cache. We put that service in place three years ago because you had a lot of time out issues with architecture, but those issues things have begun now. So, I'm just wondering if we can just stop that service. So, we don't have to migrate that service. And we can just update every mention of that repo.azure or repo.azure in Seattle.org. So, that's one of the topics. I don't know if you have any inputs on this. Could we just hop it over before it's going to get shut off and see how it goes for the next week or so? Yes. So, because we still have two weeks before ACS is done, we can just update all the repository by the end of the week. And so, if there is anything wrong, we can still deploy the service in the new cluster. The next topic is also regarding Fastly. So, I contacted the support Fastly and they told me that normally they should support us, but I was supposed to contact someone else. So, my support ticket is still open as long as I don't have any news from the people working on the OSS board. So, I mean, I hope that we will have positive answer. But until now, for them, they thought that they were supporting Jenkins already, but I cannot find any mention of that in the infrastructure or either from Taylor. So, to me, I don't know if someone else just, someone else is sponsored on the off of Jenkins. I mean, I have no idea what's the current status there. So, in the past, I had a play around and some Jenkins-CI.org has been created in Fastly because I wasn't able to create it. So, I was messing around with Jenkins.io and then I tried a service on Jenkins-CI.org that said another Fastly customer has got this configured. So, it has been configured at some point on the dash CI.org domain. Yep. So, that's basically what I'm looking for. The funny part is the first time when I contact them, they just said, oh, you know, you should contact, you should go to Jenkins.io website. It says yes, vserver and we'll just know. My point is just who is using, who is, I mean, who are you sponsoring? Because it's definitely not Jenkins projects. So, anyway, so this thing is pending right now. There is another topic where I would like to have more inputs, which is the Google Analytics. So, the CDF folks asked more people on the Google Analytics account. So, until today, only, so, yeah, until recently, it was only Kazuki, Tyler, Alisa and me who have access to them to the Google Analytics account. Now, we also have a leg and I have to add Ulrich and Alex as a small board member. So, for them, it's pretty obvious and it's satisfying. The question that I have in a list, one of the CDFs asked me to add more people is what would be the rule to remove people and what would be the rules to use Jenkins data because right now we don't have any like data policy, like you have access to the monitoring, you have access to the analytics, you have access to whatever and you can do basically what you want to do with it because, for example, the only thing that we have in place right now is a contributor license agreement, which only cover the codes that you're providing to the projects. So, I don't know what would be the next step regarding that project. Yeah, I don't know if you have any inputs on this. Yeah, I would firstly like to understand what exactly CDF needs in terms of data because access to analytics is quite wide, especially since we have a number of services connected there. So, I assume that I have it, but for me, if you could set up a kind of data policy, it would be nice. Probably it's something to raise to Daniel because Daniel is a security officer, he might provide some feedback in terms of what would be security conditions for grant and conditional access. Thank you. So, yeah, I don't think there is need to do it in hardware and if CDF wants any specific data, they can just specify the request and we can probably publish data. Okay, I'll do that for now. The other topic, the next topic is regarding the Azure functions. So, I spent some time this morning to understand how it was configured in the past, how it was configured, how it's working and the thing is right now it's not really transparent because either you have access to the Azure account and you can debug things or you don't have access and then it's quite difficult to understand what's happening and so I'm just wondering what are your feedback on this topic. The main reason what I'm asking is because we have several open ticket open issues regarding the incremental service and it's open since beginning of December and yeah, we have, I mean, it would be nice to move this forward. So, do we have any alternatives to using Azure functions? Are people interested to work on this? I don't know if you have any inputs. I don't have strong opinion. Yeah, I joked about the Jinx file runner somewhere in the IRC. I don't have a strong opinion about that because yeah, still you would need to run them from somewhere. Well, the main problem that I have right now with the Azure function is that to access the logs or whatever you need to access the Azure accounts and we are quite respective on who can access the Azure accounts. So, I granted read on the access to Jesse so he can debug, I mean, he has access to the logs but he cannot change anything and each time you need to change something on those functions, you need someone with right permission of the accounts. Yeah, one question about that is is it possible to resolve it on the Jenkins side because if we hit such issue on our infrastructure, maybe it's something which impacts other Jenkins users? So, the function doesn't work even from the Azure portal. So, from the Azure portal, some destiny doesn't work. It was just easier to debug from there but the error log is, I mean, really unclear. Like, I think I updated some data that was working on this morning and I couldn't find any information regarding that. So, maybe we should either organize a session where we only work on that, like with a shared screen. So, I can plan this for the next week and next week. That's an amazing kind of a list. Okay, if you could find someone who would be willing to help us, I mean, from Microsoft or from basically, whoever has some experience with it. I mean, I can have a fiddle with it. I don't think it'll take much. Okay. Well, I've had a poker. I've played with it before. I've ran it locally. It's quite easy to run. Okay. My point, personally, I mean, I don't want to set up an environment for that. So, if you already have everything in place, that would be easier. Yeah, I've already got it locally. Okay. So, I'll bring you later. Regarding the automated release, there is nothing new yet. I'm still the same. We are waiting for a digital inputs. So, we cannot move that project at the moment. And finally, I'm still regarding the automated release. Last Friday, I tried to run my neural bits. I have a Docker container, but for some reason I have five of the tutorials right now, so it's not working. So, I should try to find some time by the end of the week to make it working. But I already have a shot ready and a Docker container. So, I guess it's a matter of time to identify what's wrong right now. But my plan is to replace neural brain by neural bits in the new automated release process. Otherwise, this is pretty old for the last two weeks. So, I don't know if you have any topics that we want to discuss right now. For me, one question was about the Jenkins server brain. So, the last bot meeting, we agreed to have it. So, we lost you, right? The only thing that we hear from you was the last meeting you agreed. And that's it. Tyler's archive to repository. Sorry. Tyler's archive to the green repository. Okay. Is my audio working now? Yes, it's working. Yeah. So, Tyler archived the depositories. We also approved the immediate shutdown. Okay. So, basically, you can shut down when you feel it's convenient. So, basically what I did right now is I removed the Dennis record. So, just arrived nowhere. Now is this. And the question that I have is regarding the database, should I just delete the database? Do you think it contains valuable information? Should I need a backup of that database? I personally would just delete it. Yeah. So, it follows configuration as code. Yes. So, the database is used for tracking updates or something like that, if I recall correctly. Yeah. So, we can recreate it. So, the database was used to just to query the data. Okay. So, otherwise, then I would just delete the database. And so, I already started working in the deprovisioning, but I'm not done yet. Any other topics? Nope. Then, thanks for your time.