 All right. Welcome everyone. This is the Jenkins infrastructure meeting from the for 18 August 2020. Thanks for being here. Okay, so we've got one topic change in Docker terms of service. Another topic or oh, these are from last time I'm so no no no this is not these are new topics right. So Oracle cloud conversation is another topic. Are there other topics that need to be added to the agenda. So Jira one. Oh yes Jira migration Jira upgrade plan status report good. Okay. You mind doing that one earlier. I'm interested in that I have to leave soon. You bet. Absolutely. Let's put it with unless there are objections I'm going to put it first on the list. Sounds good. Okay. Let's see, September release release status reports. Yeah, so really status reports I think would be good to discuss any other topics. Okay, then let's get started. Yeah, I think we have enough. Okay. All right. So the Jira upgrade plan status met with Linux foundation, including Andrew Grimborg, Brian Warner, Steve Ira, and one other person to discuss that reviewed reviewed the plan with them. They confirmed that they are willing to host our Jira with our identity management, and they identified several action items that I need to take in order to confirm that we can make the transition successfully. They also are willing to host with our identity management so we do not have to do a transition to their identity management. They noted that it would be easier for them if we did use their identity management, but I said that I had to acknowledge the clear expectation, I can't see us transitioning 100,000 accounts from the Jenkins infrastructure to their identity and reading the Jira upgrade all by the November 28 end of support of our current Jira version. So, actions for Mark, I will need additional reviewers on the plan. There are some specific questions around SSL certificates for the test drive and SSL certificates for the certificate control for the final destination, because right now we own the Jenkins dash CI dot org domain completely and we control it correctly. And they will be running a server that is in that domain. Can I do let's encryptively give them access. They said that they can and that is their preference. And so that's what our intention is to work through let's encrypt, continue to use let's encrypt the way we do today. And we've got to coordinate the precise details of how that, how we can do that let's encrypt delegation, so that they can use a let's encrypt generated certificate just like we do. And that's that's just, it's just details that have to be made to work. It's not that I'm frightened of technical difficulty. Our data volume is not of any great worry to them at all, compared to some others that they've transitioned we look small. They said to be heaven with 300 with southern tech arms. So, Jenkins is probably 30% of these database. But, well, let's trust them. Well it was the thing that we were checking was I was checking the size of our, the number of records in our database and the size of our assets. We were asking if we needed to do a physical data transfer on drive or something and they looked at the data science that now we can transfer that data very easily over the network so not a big risk. Any questions with regard to that your upgrade plan the plan document is available it's public you're welcome to comment on it, I would love to have comments on it. I can link to that document here in the. I'll just put a link into the notes so that everybody's got easy access. I'm going to assume with no other questions at the next topic then change in Docker terms of service. Someone else is going to need to guide me on this when I don't feel terribly comfortable that I understand the details of it. There are two major issues one is retention for six months for unused images so like written before. Okay, and second topic is pull limits, because basically you have limited pools from your free account, and at the same time users for not paid accounts also have limited pools for them. And my understanding that is going to be a more significant issue than image retention for this year. Because I guess we could make it that right to have garbage collection of images, because in the worst case, you should be able to restore all of them. But pull limits is likely going to be a serious issue for us. So then is that is the question and then do we need to seek seek funding for a for a pro or whatever for a non free license. So it really depends on how they could create users, because the price per user is really low, it's something like seven dollars per enterprise account. There are two of these issues what if the price goes up. And secondly, how they do to create users, because all of us know that you can create them differently. Well, if it's just a number of accounts registered in the organization, the opposite would be something like $50 commands. It's not something to really worry about taking all the infrastructure costs. But if it's going to rise or if they let's say control users who pull from the Jenkins infrastructure, it's completely different matter. So as long as the current prices remain in place, I'm not concerned. For example, I would rather prefer to pay than to invest them in infrastructure immigration. So I agree with we can come from that it's within let's say $100 per month. Yeah, we can sustain it even with our current budget. Are they still are they still talking about the pool? I can't see it when I'm googling everything's just talking about the idle image. Let's see. I haven't checked it since the two storms. They definitely updated their guidance after the tweet storms. It's possible. So that one needs needs more investigation to see if that is a real plan or not. I wouldn't worry too much because the real plan may change multiple times before November. But yeah, first, what do we do if the fund doesn't change? And if paying for enterprise account is not feasible. Yeah, I saw on Twitter that the Linux foundation saying that they could, they can offer them for the Kubernetes one, I assume we can do the same thing if we want it through the CDS. So, so, so that feels like it's something we ought to take should is that something we should take to the CD into a CDF board meeting and say, Hey, this is, this is a potential risk. And they need to be aware of it because all CDF projects are host on Buckingham. So it would be a reasonable strategy. Right, so I'm putting myself an action item to propose something to the CDF board. Anything else there on Docker terms of service. So effective date, tell me again it was effective date is sometime in November. Okay, so lots of quiet, ready to go on to the next topic then or is there more that we need to discuss on Docker terms of service. Okay, Oracle cloud conversation. So this was a conversation that started between Tyler Croy and I believe Corey Quinn and someone at Oracle cloud expressing possible interest in hosting or contributing to Jenkins infrastructure. They initially described Jenkins as a service on Oracle cloud. And I don't think the community wants to create such a thing, but I would assume oracles developers would create such a thing. Then there was also mention of hosting some portion of the Jenkins infrastructure on it. And there Olivier was suggesting that hey, for instance, they could help offload some bandwidth requirements. There are, we could conceivably host agents there as we host agents on AWS. Yeah, assuming that there are stable plugins for that. All right. Well, and that's a good point that Oracle cloud plugins may be needed. Well, there are Oracle cloud plugins available. But yeah, they have a whopping 100 installations. And obviously they have never passed security review, they have never passed whatever. Well, at least we haven't related them. I don't know whether they would work. But if you want to move to Oracle, it's not just installing plugin like EC2. For EC2, yeah, you know the situation. It's also not that easy. Right, right. Well, so that's some assessment process before of the Oracle plugins, before we deploy them, etc. Well, firstly, well, it's not a done deal with Oracle right now. So, right. It's discovered before we even give different details, what are the requirements, what are the strings attached, etc. It seems though that there's no reason we can, it seems that we could very readily continue those discussions begin discussion or continue discussions with Oracle, see what they are willing to do. Bring status report to future meetings. Any objections to that as a plan? Objections for me. Talk with chief. And does anybody want to volunteer to step in on those I can certainly get involved in the conversations and let someone else just like who I'd like to do that instead. I certainly have no bandwidth for serious conversation. I'd like to be in the loop just for my information. But I cannot commit the bandwidth for something serious. Great. Yeah, I'm interested to be in the light, I don't really have time for it. That sounds good so keep the info team informed and just continue the discussions exploratory. Great. Anything else on Oracle cloud. Okay, last topic release status reports. So Jenkins 2.2 35.5 has released. It includes an alpine update. Security releases security fixes and an alpine update and then Jenkins 2.253. Has released. And as far as I know it also includes the alpine update infrastructure did that when no issues detected in the infrastructure and no issues detected in infrastructure for 2.2 35.5. Any any concerns from either of you on that stating that as the report. Now everything was quite smooth. All right. That covered the topics I had any additional topics that we need to add. Just some heads up about my availability. People on the school already know it but I will have to limit the availability for the community until October. Thank you for some personal reasons and some work reasons. I will be still doing key things like Jenkins governance also JSOC commitments and Google season of dogs but the most likely my capacity for any other efforts will be close to zero, including hosting request permission management and other things. There are multiple people who have commissions and co-active contributors. So, yeah. It shouldn't be a big deal. I'm not aware about anything where it would be bottleneck. But if you see anything or if you want permission anywhere, just let me know. Yeah. Thank you for, thank you for what you do for us or like much appreciated. Thanks. And we know that Olivier is out as well. So, maybe a is out for at least a month. And we're covering as best we can. All right, let's call an end to the session and thanks everybody recording will be posted. And thanks for the money. Oh, yeah. Super talk to everybody later.