 Welcome. This is the in for meeting the 29th of September. It is a beautiful day to be here. Thanks. Agenda topics so change in Docker terms of services, JFrog, Artifactory, really status reports, Jerry upgrade plan, Oracle cloud, Azure costs, any other topics that need to go on the agenda. Okay, then let's go ahead. Oh, all right. So by way of schedules, Olivier will be back in the office. Two days from now. Very grateful. And Oleg's limited availability continues. Probably throughout October is my guess. Nothing won't be back until next week. And new topic or same topic change in Docker terms of service effective November of 2020. Any insights there, Alex on. I haven't seen any updates. I know that GitHub is now has a, you don't have to authenticate for Docker, like an image repository, but I haven't looked at it enough to know whether it's it would be a good replacement or not or if there any catch it catches or gotches. That is the GitHub and it actually is really, really nice, especially when you incorporate actions with it, like really, really nice. Okay. Do they have any, do you know if they have any sort of limitations is it because I mean rate limiting that sort of thing because that's one of our biggest concerns I think with the Docker hub stuff is just, you know, I think they said it's 600 polls or something like that per hour. But some number I don't remember the exact details but yeah, just wondering if they have any similar rate limiting on GitHub. I think the rate limiting that they have is similar to what their API rate limiting is and that's like three or 5,000 calls an hour. If I recall reading the documentation correctly. I think we've kind of. Sorry, go ahead, Mark. No, no after you. We're just kind of in a waiting game on this to see how the changes affect things and I guess having some mitigation possibilities like GitHub or stuff like that is something to look at but I think our kind of stance has been kind of wait and see if it affects it, you know, how adversely it affects us, I guess would be the and that's just kind of what I've seen, like Tim and everyone kind of talk about so. Yeah, I'm worried by this one. I'm very worried by it. But my actions do not support my being worried right because I've done nothing to investigate it. I'm hoping with Olivier's return. We can do more investigation here. This to me feels like a big risk. It's not as big a risk as the next topic on the agenda but it's still a big risk. So, I think. Does the Linux foundation have any with Docker hub, like that we can get get underneath that all since we're with the Linux foundation was CTF or I can check on that. I'll take an action item to check on that. I want to say no but that's just more of a guess. The non fiber gods are blessing us right now. Yeah, sorry Alex we're having difficulty hearing you here we may have lost Alex. I propose let's go forward, Markey, address the other topics and, and then as as if Alex comes back we can go back to the doctor topic. Plus one. Can you hear me now. Yeah, Alex go ahead. I forgot my train of thought was. We can move on. Sorry. Cool. Alright, should we should we be recording this meeting. Just. Okay, never mind. I was looking in the wrong spot. Sorry. Yes, good. Thank you. So our JFrog and our Artifactory instance. The email thread is ongoing. And now the next step is, I need to remind. I need to convene a meeting with me, Daniel Beck and Baruch Sadogarski of JFrog to understand the sources of the costs and alternatives to reduce the costs. They're talking about the way they phrase is the costs are six figures right now. That's the C I that are for repose that Jenkins. Wow, that's pretty impressive. Yeah, that's awe inspiring and figuring we, we barely pay six figures in a year for our entire Azure infrastructure so it's unfair for them to carry that much burden. And I agree with them wholeheartedly it is unfair we've got to find a way to carry that or reduce it. Any investigation into ways we could reduce some of those artifacts my guess is is we just have old artifacts that aren't getting cleaned out. Well, so the challenge right now for us is before we before we attempt to reduce anything we want to understand what are the sources of the costs. Is it bandwidth, or is it storage space and depending on which of those it is will guide us to choose the most beneficial thing to reduce or do to change if it's bandwidth for instance, and we could prove that an unexpected volume is coming from C I that Jenkins that I owe and its agents, we could probably cash on C I Jenkins that I owe if it's storage space, we could delete old artifacts right so it just depends we've got to have that conversation with them because it's not clear to us what the source of those costs are just that they're they're out of bounds we've got to find a way to help solve them. Okay. All right so that one is my action item. And, and Daniel back. Next topic release status reports. So this one we've got, we just released two dot 259 today. The release build process was successful. Thanks to his marvelous marvelous work on infra nine 10 it continues to work for us and do just great. We do still need the merge in for nine 10 to master and with, but that will wait a while there are some urgent things that Olivia will be working on the returns. So, it don't be dismayed if it's a week or two yet before that happens. So we've got this hot one Alex for your topic. The Docker image is not yet available given your current state. Is this something we have to risk having somebody else try working on it or what's your, what's your sense. I should be able to work on it today. I'm going to be having some good internet a little bit later that I can work on this. Excellent. Thank you. Don't, don't be shy at saying hey I want to hand it to somebody else that's very kind of you to work on it but if it's just not going to work for you. I suspect you're the most effective at doing it since you understand best the structure that but we can ask for other help if it would, if it would be better for you. I'll definitely reach out if I need it. So, thanks. Then we've got another hot one coming about a week ago I guess it was a week and a half ago now. We had an outage where the update center took itself offline because it saw that it's an internally use certificate that's used to sign content or to encrypt content was detected that it would expire in less than 30 days. The system is designed to say hey if we're within 30 days of expiry, take yourself offline so people work on it. It did that. Unfortunately, we weren't able to get the replacement certificate into place. So Daniel Beck applied a workaround of setting the code to only one after 14 days. Prior to expiry that 14 days expires October 7 and Olivier will start working on it when he returns Thursday. We think we've got enough time to complete. That's for working days before October 7, but I've been poking and prodding various people to see any questions there on that update center certificate. Next topic the Jira upgrade plan. So, we need to get the SSL and the DNS experts from Linux foundation and from the Jenkins project together to talk about how we do that piece of the transition. We need to retain issues dot Jenkins CI.org. So that's, I've asked for help from Andrew Grimberg of Linux foundation, and we'll hopefully have that conversation next week. Any questions on Jira upgrade plan next Oracle cloud. So Oracle cloud had started a conversation with the Jenkins project about two or three maybe four weeks ago through Corey Quinn of all people and Tyler Croy. And after conversations with me and a group of their people. I've signed a confidential disclosure agreement with them, and we're going to try to work together to they would like to. They want to highlight Jenkins on Oracle cloud and include it in their offering. So we're we're having those discussions. One of the possible outcomes of this that we need to bundle Jenkins in a slightly different way or do we know anything about that or is there going to require work on our part I guess is and how much. I don't know right now the indications are if they may want us to do some additional things with our Docker images. They're interested in our Docker images that were already sort of on our minds anyway. So they're already on our list anyway and on our road now. So Docker images may be of interest to them. But there's been no request so far, no request thus far for any specific Jenkins project work. And my assumption is if they want it done, they will bring developers to help do it. Okay, just your question Alex. Yeah, I was just wondering. Yeah, and if we had any idea how much work or whatever. Yeah, the conversations with them did not involve what I anything I detected as Oh, this will be a lot of work for the Jenkins project. They may be able to help us accelerate some of our some of the things that we already have on the roadmap. Cool. And are they also possibly providing infrastructure that we can use is that part of this as well or is is it that's that's part of my assumption is what they're doing may include infrastructure. For instance, one of the things that they highlight is their bandwidth is cheaper than other people's bandwidth. And one of the substantial portions of our cost is in fact bandwidth in and out of Azure. Right. So, we might consider hosting a mirror on Oracle cloud or we might consider other other things. But right now it's still in discussion phase. Okay, cool. Thanks for the update. And then last point I had was that we are as your cost for August we're in budget. We were about $1000 under if I remember correctly, and we're looking about the same for September so that's good. We don't want to exceed our budget that CDF is allocated to us. We've also been assigned to customer success manager. And she and I are in just Caleb in the bill. He's provided some documentation that may be able to help us and interestingly enough the Oracle people said hey if you let us look at your Azure bill we may be able to offer some recommendations on ways to reduce costs. So, just so you're aware we've got. We've got that person available now I've not used her extensively yet, but she's offered some hints and suggestions. Any other topics we need to discuss today. Nothing for me. Okay. I think we can call this meeting done then thanks very much. Thanks Mark, thanks Marky. Hey Alex Mark have a great day. Thanks Alex.