Hello, everyone. I'm Rupa from Cumulus Networks and for those of you who don't know what Cumulus is, Cumulus is a derivative of Debian for network switches and I belong to the engineering team in Cumulus. I work on the kernel and other networking packages in user space. Happy to be here, happy to be seeing the Canadian summer actually. I've been here multiple times, numerous conferences and it's all been in winter. Okay, to set the tone of the talk, I wanted to just give a high-level overview. So this talk is about open networking revolution that happened or is still happening in about six years, around six years now, and how Debian has been at the center of this revolution. Thinking of Debian just not as a server OS but also a network OS. There are a bunch of changes in the two operational models, but fundamentally, we have tried to bring Linux to the networking world and shown that you can run a server OS on a networking box. And it's about a journey of building a network operating system with Debian and also how extending Linux hardware acceleration model to network switches. I'm not sure how many people are know or know about open networking, so I just put this slide up to give some context. So this is a sample modern-day data center network topology. It's called a class topology. Basically you have racks of servers and then the Tor switches and on top of that the spine switches and there's many more things around it. But so when I talk about closed network devices, I'm talking about the Tor's and the spine switches. So these have been always been the Cisco's and Arista's closed box switches and routers which can do terabits or packet switch and switch packets in hardware. These have specialized switch ASICs which are capable of doing this. And the server racks, as you know, they run Debian and any other Linux distribution. So this talk is about Debian moving up the rack, basically running Debian not only on your servers but also on your Tor switches and spine. So all this started with the open networking movement and cumulus networks was very much a part of it and kind of started it. Basically networking boxes with these high-end chips were mainly closed boxes with the CLI and nobody could access anything other than the CLI. You program the network using the CLI. So the open networking revolution actually brought desegregation just like what happened to server world basically separating the hardware with the OS and then you have an open box where you can run networking apps on. So basically bringing the Linux ecosystem to networking. It was about leveraging lessons from the server world, open bootloaders, getting more platforms adopted in an easier way, open Linux ecosystem and Linux API which would help your apps move to different Linux devices. So in the open networking landscape today, the NOS architectures. There are two types of NOS architectures. Again, this slide is again laying context for what I'm going to talk next. So with the open software model, desegregated model, you have two types of architectures, one where it like what cumulus does, basically use native Linux kernel and accelerate that to hardware. For example, you program routes in the Linux kernel like you do on a normal Linux box or a server and there's a driver which offloads that to hardware, Switch A6. And there is another architecture which is actually run by most of the other vendors who are now pressurized to join the open networking movement to not lose control over their software or their SDK to keep some control over the closed parts of their SDK. And this other architecture actually provides a hardware offload API which apps can, networking apps can write to. So there are pros and cons to both architectures. Well, the native Linux architecture actually wins overall. You basically your applications written to a Linux API, like for example, Quagga or LLDPD for that matter, which is using the native Linux API or API to program network interfaces can work on a server or any other networking box. On the other hand, the closed or the software stack that is being pushed by other vendors is basically using hardware offload API apps directly write to it and that makes your networking app non-portable and you will have to rewrite the app to other network chips and hardware. So advantages of using the Linux networking API is basically, as shown in the picture, you basically run your same applications, your Quagga routing suite or your LLDPD or DHCPD, the same application runs on your server or your switches or any other network device. With this, you're actually bringing the server and the networking communities together as well, uniform Linux networking models. You don't want to create a bond or a bridge in a different way on a server and a different way on a tour. This unifies all networking. It minimizes operational problems. You can use your same monitoring and debugging tools everywhere to monitor your servers and your TORs and other network devices and package management. Package management, as we all know, it's not a simple problem. In this picture, we show servers and all these use the same code base and the same package management and it's Debian everywhere. So now, the next few slides are, I don't dive deep into a lot of things, but it's a high level rundown of all the packages and all the features that we touched for Debian and to make it a successful network operating system. So why Debian? As some of us, there are other cumulus folks here. They started with the ODM PowerPC switches from Taiwan and, yeah, they were PowerPC and Debian was the only architecture at that point or only distribution that supported PowerPC at that point. And Debian has the largest ecosystem of networking applications. You can actually search for any networking protocol or any networking package and it is there. And it has a growing and strong community. Then came the need for a open networking NAS installer to standardize NAS loading across open hardware. And this was critical because if you don't get this in and there will be a lag in movement. So this is another project that cumulus worked on. It's called ONI. It's the open networking install environment, which is today almost a de facto standard for open networking boxes. It is open. It is an open compute foundation. And, yeah, now most of these open networking boxes from or desegregated boxes from Taiwan or any of the ODMs, they come prepackaged with ONI, which gives them a choice to run any network operating system. Kernel and platform bring up. Again, these were closed boxes, no hardware specs, very difficult to port Linux to these in an open way, like any, like pick up Debian and port to it. So it was not, I've not personally worked on a platform bring up, but there are many people who have in the company have worked on this and yeah, it was a laborious process, getting specs, reverse engineering and so on. So this says that this industry needs a lot of standardization in this area about hardware standardization to get platforms integrated quicker and early. And there is an effort going on, which is to extend ACPI for network hardware. And this is again bringing, leveraging whatever was done for the server world to the open networking industry. So there's a spec, there's a link to a spec describing this. Netlink. I had to add a slide on this because, so Netlink is the protocol that we know, which is a protocol between kernel and user space, and it's kind of becoming the de facto network configuration API for Linux. Every new kernel API that you add for Linux networking has, is Netlink. So, and we have reused Netlink to a great extent. We, it for us, it's also an offload API, basically offload Linux networking to our switch ASICs. It's configuration monitoring. It's also become a very powerful tool or powerful API to add monitoring capabilities to, to Debian or Linux in general, and for network troubleshooting as well. So in the course, we did enhance, we had to enhance a lot of Netlink libraries for, say, scale, like Libnl. And we did take these packages from Debian, and we had to enhance them for scale. And we also had to, we actually ended up writing another Python Netlink manager or library. So networking bring up. So since we have modeled a switch ASIC as a Linux server, or a Linux, or any general Linux operating system, we represent every switch port as a network device. And so now your switch looks like a Debian server with 128 Nick ports, 128 or more Nick ports. And these Nick ports are now 100 gig, 40 gig, or whatever these high-end switches are capable of. So there are many switch features that have been deployed by other vendors, like port ganging, splitting ports, and so on. All these became necessary when we brought necessary elements to Linux, when we got this on the open hardware. So the challenges here were again scale. When we started picking up packages from Debian and started running on these, now your 120 Nick ports and LLDPD on servers runs on two or three Nick ports, ETH0, ETH1. So some of these challenges with scale we fixed LLDPD and many other packages, Libnl, DHCPD, move them to Netlink or upgrade them to latest packages where they were already fixed. L1 config. Yeah, there's lots of SFPs. I'm not an expert in SFPs, but there's lots of SFPs and lots of other parameters for link settings, 100 gig, 40 gig, FPC settings, and so on. So that also is critical for a NAS. And tons of networking attributes on switch ports for bridging, for STP, lots of timers, tuning of timers, and so on, a lot of networking attributes that need to be added. Now, offloading all this to the Switch ASIC, most of these vendors still have proprietary SDKs, which mostly run in user space. So we had to map the Linux API to the SDK API. And for example, a bridge FTP add which adds a forwarding entry into a bridge had to be, yeah, mapped to an SDK API which programmed the hardware. So the user basically sees the Linux API. You do everything what you did on a server, exactly on a network hardware, and we seamlessly offload the networking functions to hardware. Switch ship initialization. This is something different and it's required in some of these vendor SDKs or APIs are proprietary and closed.  And this is also being worked upstream to include this natively in the Linux kernel, in the Switch Dev project. And the Switch Dev project is basically natively in the kernel handlers for offloading to hardware. So yeah, this API is called DevLink. It's again a generic Netlink API. It's available in latest IP route two versions. Tunables, network parameters. So on a server, many of these parameters are default to the Linux defaults. Now on a Switch, it's very critical to change some of these defaults because, yeah, because Switch is forwarding and also something like ignore routes with link down. This is, yeah, this is critical. Basically Linux by default does not forwards or routes through ports with link down. And so this is something that we got in the kernel to, because it was critical, you cannot, you have to ignore routes with link down interfaces. Networking demons. Like I said, Debian has, Debian ecosystem repos has network, all sorts of network. There's a ton more. I've not added here, like PTP and so on. So yes, the initial days was of porting Debian to a networking hardware was getting all these demons, testing them for interface scale mainly and interrupt. And most challenges that we faced were on scale because it's not only the number of physical ports, but now when you do bridging and VLAN in a Linux native way, you end up creating network interfaces on the ports. So we could easily scale to hundreds and thousands of network interfaces. Network interface configuration. I've talked about this in DevCon before, and it's a hard problem. It's again the sheer scale and a scale of not only the number of net devs, but it's also the number of networking attributes that you have to now configure on each port, STP parameters and STP. There are tons of STP parameters. I don't even know half of them. And in the same time, you have to handle differences between servers and switches. So the pressures here, pressure or challenges here that we faced were basically from the users. Of course, we are now trying to sell this to people who have used closed boxes with CLIs, selling them a config file and telling them to configure thousands of interfaces or interface attributes in a flat file. Yeah, that did not go that well. So, yeah, and people do, there is a lot of people who love Linux and the files and config files and all that, but an automation, but there's also a group of people who do not want to move from their CLI. So, yes, we ended up doing two things. One is rewriting IF up down to IF up down two, just for scale, dependency tracking, because people didn't want to do dependency, interface dependency on their own. So IF up down two, it's in Debian now. And there are many differences between how you set CCTLs on Debian and the default CCTLs on Debian and servers. So what we have done is we have controlled these differences via policy files, so a user can drop in a policy to change the defaults. And that's what Cumulus does. We have a bunch of Cumulus default policy files to tailor to a network operating system. And, yes, there was a very great need of a CLI or many people wanting a CLI or people not wanting to change SNMPD config in a file or an LLDPD and interfaces on another file. So, yes, we now have actually a unified Linux file editor and manager, which basically translates edits files and appends to files and so on. Kernel networking. So we exercise a lot of kernel network features, bridging, routing, routing to a great extent, ACLs, and networking tools, IP route to bridge you tools, ETH tool. So we end up back quoting a lot of latest... We started from Debian and some of these we have moved to the latest upstream versions, or some of them we have kept the Debian version, but we back put a lot of patches from upstream. We do work closely with upstream, the Linux kernel community to add many of these enhancements to Linux. So talking about Linux networking features, some of these are important to a NOS and I've listed them here to complete the picture on what it takes to build a NOS. Worf. Worf is a virtual routing and forwarding instance. It's like a VLAN for L3 or for your IP addresses, isolation. It provides IP addresses, isolation. It's a very important feature in a network operating system. For example, there is something called Management Worf, which is a default feature in a networking operating system, isolating your ETH0 port from your switch ports. So ETH0 carries all management traffic and the IP address and everything, the L3 context is completely isolated from your switch port traffic. And so Linux kernel now has the Worf feature and the newer kernels, the newer Debian releases already have it. I've done two has support for provisioning Worf, also provisioning management Worf. And we have, by our defaults, the NOS defaults, we manage by I've done two policy files. Then MPLS. MPLS is another protocol, label switching protocol, sometimes in the data center or other environments. So we have enhanced the kernel data path, MPLS data path and I've done two also has support to configure it or to enable it per port. Then some of the other features I've just listed is QNQ, multicast routing, and lightweight tunnels. Lightweight tunnels is again a way to to configure your network tunnel interfaces by not creating a net device. Again, this was done to solve the net dev scale problem because on a NOS, yeah, creating 1000 tunnel endpoints, VXLan tunnel endpoints, you end up creating 1000 VXLan devices and that won't scale. So with this LWT, you can move to a single VXLan device. MPLS tunnels are no more a device. So this is something that is catching on. There are many tunnel net devices that are being eliminated or moved to a single device or you don't need a network interface at all. Routing. Routing, we started with the Quaga package from Debian and we had a lot of enhancements. We have contributed to the Quaga community and now there is a fork of Quaga which is called FRR which hopefully will be in Debian also. Overlays. Overlays is another net NOS feature, VXLan tunnel endpoints. So overlays is a good example or the Linux model of deploying overlays is a, it's a good example to prove the Linux native hardware acceleration model that I was talking about earlier. You can do VXLan overlays the same way that you did on servers or hypervisors, the exact same way you do it on a switch and you get the benefit of hardware accelerating it with a switch ASIC. Monitoring. Monitoring applications. Again, net SNMP, S-Flow and I'm pretty sure there are many others. We have picked up many of these from Debian as well. Again, I mean everything worked right off the box. Just the issues that we have had is with scale and number of interfaces which we have fixed or in some cases in net SNMP, I think the latest version in Debian moved to Netlink and that helped a lot. S-Flow is another sampling protocol. It's, yeah, now we have an upstream Linux API to actually do S-Flow on using TC on the servers and which can be offloaded seamlessly on a network switch. SystemD. We do use SystemD for most of our monitoring of our network services. SystemD worth enhancements is a recent addition. These are not upstream yet but at some point we do want to get some of our worth packages into Debian. The worth is an isolation, L3 isolation for a, you can isolate a process into a particular L3 context. For example, you can run multiple instances each having their own isolated L3 context. SystemD unit files kind of helped here a bit. The worth uses C groups. C groups to attach a particular L3 process in a, put a service in an L3 context and we use the SystemD C group mechanism to actually do this. Futures. We do want to push some of these enhancements. Some are already upstream. Some are, the latest version of Debian has already picked them up. And, yeah, new tools and managers that we have written to make things easier for deploying in a NOS environment. We would like to push it to Debian at some point slowly over the years. Yep, that's all my talk. Thank you. Thanks, everyone. Any questions? Hi. Well, I'm a happy user of Communist Linux for more than a year. So thank you for this product. I love it. I have a few questions regarding the relationship between Communist and Debian. For instance, when you look at the GitHub repository of Communist and you look at the issues and stuff, there are mentions of, okay, we will make a refresh from the master repo or we plan to, but there are usually no deadlines and I would like to have some clarification on, okay, how does that work? Do you have a private repo? And then periodically, when does that happen? Do you contribute your code to the open source? Yeah, so it depends on the project. So most of the projects we work directly with upstream, like for the kernel, we have everything going in the kernel directly, the upstream kernel, and then Debian picks it up. The one package that we are still trying to move to an open development model is I have done too, which we, yeah, so yeah, that's just purely because of no cycles right now, but that's the intention. And we want to move to an open development model. But yeah, we don't mind pushing code every day there is just that it's easier for us to right now push into a release and then when we have cycles move. Because one thing that we want to make sure is the lag is mainly because one thing we want to make sure that the changes we have done work on Debian, or what we do is immediately when we know that it breaks, we have to wrap into a policy file so that it's only invoked on an OS. So it just requires some cycles and that's why it's delayed, but we'll soon, we'll soon be having an open repo. I can elaborate slightly with up down to it is also in the released version that comes with every release is available as a Debian source package. So you can get the source that way as well. The definitely understand the point about wanting to have new features go into the public repo first, but you know, that's, that's a different thing. But all of the, all of the source for the actual release is available. Okay, thanks. And what about PTMD? I never saw any Debian package for that. And actually, I wanted to use it for our servers. Yeah, I don't think there is a Debian package for that, but we will probably be putting it soon. Yeah. Okay. And one last question then. Well, apart from, you know, for instance, imagine I'm using if up down to, but not on community switches, but on my server and stuff, where should I report bugs that I find? Where should I contribute patches and stuff like that? Should I do that on GitHub? GitHub is better right now. GitHub or Debian, we both, we monitor both places. So yeah, GitHub, you can send a pull model. You can use the pull request to actually send us a patch or yeah, or just email us. So there is, we have Julian here in there who's monitoring the GitHub website and thank you. Can you speak a little about how the cumulus kernel and ASIC drivers and other things are structured packaged and delivered? Sure. So the offload itself or just the distribution of the ASIC drivers? Okay. So you support a lot of different hardware vendors boxes, I guess, and with a variety of ASICs. And are these proprietary drivers and are using your own kernel package or are they structured as out-of-tree drivers? Yeah. So our kernel contains a lot of GPL platform drivers, additional drivers that sometimes we get from the vendor and most of them are GPL, but they are not upstream. Some of them are upstream. So you'll find them in our kernel package. We do ship a user space offload driver that is offloads to hardware. And that interfaces with the vendor SDKs. In most cases, those are closed. But yeah, soon we'll have, I guess, a switch dev implementation also, which will be based on a pure, completely open driver. Yeah, it depends on the vendor. And Melanox right now is the one vendor which has an open source driver. Thank you. I was a little bit late from your talk. Sorry for that. So I may be totally mistaken, but why didn't you mention OpenV switch, the project I mean? OpenV switch? Yeah. Why didn't I mention? So we, as OpenV switch to offload flows, because we don't, it's not an flow offload hardware. And we don't offload flows to hardware? No, I mean the software project. It has a similar scope at least partly with what you do. It supports some offload switching engines and ASICs probably. I'm not, I'm no expert, but I find it surprising that you do something very similar and still I can't hear a single word of mention. Okay. So I know there are OpenV switch, there are distributions which offload OpenV switch directly to hardware. So what we have, we do have an implementation where we take OpenV switch flows and they're translated into Linux forwarding elements. And then that gets offloaded to hardware. It's kind of the same thing. But if you want an obvious front end and you have a controller and so on, you can still use our box to offload it to hardware. But our default model, it runs with just Linux commands and the Linux API and we offload to hardware. Okay. Thank you. Hi. I do discover the product like a month ago. I was so happy to see that in the market. But I'm always curious about how do you get success as a company? It means because I know it's a lot of work and there's, I think, a lot of developers that you pay for that work. So my question is about the business model, if you want to share it, because it's always like good to know who people can go inside the open source ecosystem, especially when you are going more in the hardware place that is hardest that juice the software part. So the business model is we do sell support. We do sell, it's like any other Linux distribution, like our Red Hat is. We do license support. And yeah, that's basically the business model. So I'm asking a couple of questions from people watching an IRC. First of all, question one, how far are you with the VRF? Can I run a routing protocol, for example, BGP? Wurf and BGP. Is that what the question is? Yeah, we do have BGP support for Wurf and it should already be in the FRR repo or the Quagga repo. Okay, cool. And the second one, could you provide any ideas on performance for top of whack, as compared to, say, a Coen Cesco Nexus? No, I don't know. But I can get that information. I don't know on top of my head. Does anybody else? You probably know Nolan? Nolan is the founder. Yeah, hi. So the performance of like a Cesco Nexus, like a 3064, for example, will be strictly identical to any cumulus platform that has the same forwarding asic. And in which this case is a Broadcom Trident Plus. Yeah, Trident Plus. And so all of the actual forwarding is being offloaded, is being run in the hardware. So the CPU is just running things like BGP and all the various protocols. And most of these things have fast multi-core x86 chips in them. So there's plenty of extra CPU around and memory around if you want to run applications on it as well. So performance, they're mostly idle, usually. How logical are some of these pieces like you just mentioned that you have a Quagga branch or something like that? Would it be possible to run another software like Bird as an alternate routing protocol? Yeah, definitely. We have people doing that as well. Because it's an open box, you are. And because Bird talks Linux to the kernel again, it uses the same API. So why do you have a separate Quagga branch that you're talking about? So the FRR, the Quagga FRR repo, the FRR project. So the FRR project is again not a closed repo or a closed branch. It's again a community-driven fork of Quagga because of various other reasons. Because patches were not going in as. So but it's not a closed thing. It's again a foundation which is built around FRR. And I think it's part of Linux Foundation now. Yeah, okay. I misunderstood. I thought it was a cumulus specific branch of Quagga. No, it was again a community fork. Okay. Thank you.


I'm going to join her in the journey and today's journey is right here in Honolulu, close to home. And we have with us Dr. Len Pang from YNI Cares and Lisa, you know, I'll never get your last name right so we're going to skip that. Just know this is Lisa. And she is from the organization which we get or participate with adopting a family. So that's where we are today adopting a family. I heard on the news this morning, just this morning, that one out of every six children in the United States is hungry. The richest nation in the world, that's obscene, one out of six. But there are people like Lisa and Glenn that make sure that local children are taken care of. So, Glenn, Aloha. Wow. How are you, Marsha? Marsha's my colleague on YNI Care. Well, tell us about YNI Care. Well, you know, when I decided to come on the air, I really wanted to hear more about adoptive family. You know, I'm very impressed with their organization. We're just one of the many organizations that try to do something with adoptive family because we realize, you know, there's so many needy families that aren't really going to have a very merry Christmas because of this pandemic. And just wanted to do something. But I'm here just mainly to listen to Lisa. Well, Dr. Pang. Yeah, come on now tell us. All right, with Dr. Pang is retired, but he's a real, real one of the best doctors in the whole world because of his empathy and his compassion. And one day he told me, this is what we're doing. And I said, well, okay, of course, anything he wanted, of course. But that was years ago. And he put together this group to give free testing to children on the YNI Coast, so that they could participate in athletics and the schools are required that they have these tests. So it was done free to all of the kids so they could participate in the school activities. So that is my memory of the beginning of YNI care. And from that day until today, it's been caring not just to YNI, but to everybody. So, here we are. And Glenn told me we are going to adopt a family, which is just a precious thing to do this time of year. Now, tell us about adopting a family. How do we do that. And if there's anyone that wants to adopt a family. How do we participate, how can they participate. Yes, hi, thank you so much for having us on your show today. And parents Inc. has been in Hawaii for over 44 years serving Hawaii families. It's an organization, so we serve a lot of families, needy families and a variety of different things happening, especially this year with COVID people losing their jobs and kids not in school and not having the income or the funds to do cover the basics rent food. So parents Inc. has done an adopt a family program, usually around the holidays, just for those families that are unable to do the extras, you know, the Christmas gifts and the Christmas tree and you know all the holiday festivities. But unfortunately this year is they're much more needy because of other circumstances with the COVID pandemic. So we have just seen a really influx of donors generous donors like you guys, Dr paying who just have stepped up and said hey we want to help in any way we can. This year we've had the most families and donors participating in our program, as ever. This is good and bad I mean it's bittersweet because it's sad that there's so many more people that needy, but then great that donors are stepping in and they have the compassion and the heart to help others that need help this holiday season. So, what we do is we put out a email blast through our cohorts and through his letters and ask any donor that wants to participate and adopt a family meaning to take on that family for the season to give them gifts and food and holiday spirit. So they can enjoy something and have something positive in their life during the holidays, and then we also ask the families we service and other needy families around Hawaii. If you have a need this this Christmas let us know we're going to match you up to a donor that's interested in helping out. So that's what we've been doing for the last couple of months and it's just been an awesome thing. You send us some pictures. Yes. What, what you're doing so we can show this. This is something that just happened over the weekend. This was a donor group and they were called on foolish addiction and they're into making wishes and dreams come true. We adopted one of our families a family of four mom dad and two children, and they showed up with a truck full of goods, a lot of food items, as well as some gifts for the children, and I was able to be part of that on exchange. And then parents in staff member needs to be present during the drop off and delivery of a donor and family. So when we make sure we take pictures and and then they get thank yous afterwards a formal thank you letter, and it just is really a nice thing to be part of to see the joy and people's face donors love to give that makes them happy. Yes, the families love to receive when they have a need so it's really something that's heartwarming to experience. So, when you go with us when we deliver the gifts. Yes, there will be some staff member at parenting. It will be at every drop off and pick up for gifts. Yes. And Glenn has been really excited about getting things for the children. Well, we're excited because what happens is we ask our families, you know what is your need. And then of course we share the ages of the children, and the genders of the children and gift ideas that maybe they want, and share that with the donor, and the donor gets to decide what they want to donate and pick out the gifts or, you know, like I said, sometimes it's food it's it's a dinner Christmas dinner from Safeway, or it's an activity. When you're a donor gave a family tickets to the UH game. So there's all different kinds of things you can do to support the family to just bring them together and bring some joy and connect connection through the holiday so it's positive and happy and not sad. And we just are really happy that Dr. Payne reached out to us and wanted to adopt one of our families and brought the group in. I mean, like I said that the overwhelming response this year has just been awesome and we just really appreciate the generous hearts we have here in Hawaii the aloha spirit and donors like you guys that care so much. When you're hiding there you are. So, tell us how you got started with this adoptive family. Every year we kind of come up with projects to do I mean we, we do various things and we mainly we've done in a lot of physical exams for children that can afford physical exams and the main one like you mentioned was to do those sports physicals for the people and those kids in wine I and at that time cost I was still working so we were able to have contact with a lot of nurses and doctors that wanted to volunteer.  And do we wanted these kids to be able to qualify for sports because they felt, you know their grade point average actually increased when they did sports so we didn't have any contact with the, you know, physicians and then if they did the physical you had to pay for it but we were able to do it on a volunteer basis. That's just one of our projects but you know we have a project. We have a schedule we're supposed to do it this year with St. Francis, being on the board with St. Francis I was able to connect with them to use one of their classrooms to teach Kapuna how to work their iPhones and their students to connect with their families you know because during this pandemic, you know they're at home and they're not able to, or they're in assisted living facilities not able to connect with their families so we were trying to work with Chamber of students to connect this to a couple of high schools, you know with the students with the seniors would have to do the community service, you know for college. So we would have them who, you know they're these seniors are very adept at using technology to teach. I teach the Kapuna how to do their technology. So yeah we were going to do that and there's another project we're going to do with the Sisters of Keau with Wainae to help them set up aquaponics to have the homeless, you know, work the aquaponics and or sustainability, you know, being able to grow vegetables and raised fish and they could either sell it or use it for their shells but but you know we have different projects and plan but you know with this pandemic we've been on hold so since we were so dormant I wanted to do something and I said I don't know where we got it that you know a lot of these kids were not going to have a very merry Christmas because of you know this pandemic a lot of the parents were not working and so this is why I got on the computer and I looked for you know gifting to some family and this is how we found adopt the family and I'm so happy that we're able to do that at least you know we're doing something oh you're always doing something yeah but we enjoy you know just paying back you know we've had you know we've been so blessed I have been blessed you know in my practice is be able to practice medicine for 35 years and having that opportunity and meeting so many wonderful people and that's how we started with wine I care is as I met my patients a lot of them came from wine I and when I talked to them I they invited me to wine I and I met with a lot of the corner there we talked about a lot of the homeless in wine I and and this is how I met Katie our president was she is our she's a PhD and she teaches non non-profit she has a college that she goes to and without why without Katie I don't think I could have she's really gotten this organization and he said that she couldn't join us today because she had a class but people like my show and all the people on our board have had some experience with nonprofits and they've been contributing a lot to you know this organization we're fledging and we try to do whatever we can and we we enjoy just giving back yeah now my daughter who isn't an iron work because she met you when you were testing the children and why and I because she worked with you then as a volunteer that's how you met Marilyn yeah and we hope you know this year just coming year we'll be able to do you know a lot more we we try to do some project with the homeless but that didn't yeah try to work with the state but that didn't turn out yeah well you know everything is really crazy with the state because they're so involved with the pandemic like I don't know that they have time for anything else and then the budget is like so you know for them this is I like to tell Lisa as Lisa if you know we like to collaborate with different organizations and maybe we can get together to do something in the future oh yes we would definitely like that we collaborate with nonprofits and other community members all the time we feel like that's the best thing to do to make sure that we're all doing our part in Hawaii and reaching as many people as we can and right now I'd like to mention that we are collaborating with Unprevent Child Abuse Hawaii we're running a photo contest so it's another holiday thing we're doing we're asking families to take a holiday picture of themselves and get a little creative if they want to dress in certain attire or they want to you know spice it up a little bit to make it funny or they want to sit around the Christmas tree or just whatever is special to them to take a holiday photo submit it to our Facebook page and then we're going to announce a winner and we're giving them $100 gift card for food at some restaurant would you put your contact in the email you said your web page telephone number whatever you want so people can participate and they know how to reach you yes definitely yes an answer to Dr. Payne we would love to collaborate with you in the future near future as soon as the holidays are over we can get in contact and sounds like you're already doing great work volunteering for the Y&I community and I'm sure other areas as well like the whole Oahu and we also have two offices on the big island so we have a really big reach in Hawaii and we'd love to have more support and collaboration in our services as well I think the good thing about your organization Lisa is that you know you're accommodating and you know you return calls that makes a big difference and you know you facilitate our connection with the family and give us information we need so I think that you know I commend you for the organization you have well thank you that we really appreciate that we try to do the best we can we think relationships are the most important thing that's why parenting is so important to us we understand and realize that the relationship between a parent and child is significant for their development and them to thrive as adults in the future so we have to learn how to build relationships with everyone in order to teach that to parents and build strong families and foundations I think that that's very important you know when people call an organization and I found that sometimes we don't get a call back when we ask questions we don't get an answer so I think that the success depends upon how how that is facilitated making it easier for the person that wants to donate don't you get sick Glenn that's not allowed my allergy but thank you Lisa for allowing us to participate yes thank you for participating it's just I've been overwhelmed this year at the response it's just really nice when we're in this kind of situation in our country now in our world and people just want to give back they want to support each other and it's just really nice I think the lowest spirit is thriving always has been when we're at our lowest we seem to rise up and donate the most giving is just significant and that's something that a lot of nonprofits are experiencing right now is a lack of giving in our funding areas you know like the fundraisers we used to have we can't have anymore because of COVID or the donations we used to get we don't get because they're all earmarking the money towards the COVID issues so I think a lot of nonprofits are kind of struggling and we feel that the same is like how families are struggling and it's important for us to understand that we need to accommodate them as well they're just you know there's so much pain I think going on right now and challenges and so many areas of people's lives that we want to do anything we can to make it just a little bit better now we the program will be aired we'll get to send you a link at the end of the day but it will be on YouTube and everywhere else and the people that are watching that will watch not today but as it goes around the world can they send pictures can they participate also absolutely yes anyone can participate and I can send a flyer out to you guys to post if you want I'm showing the details of that but we it's open to everyone anyone that needs help at this time we want to accommodate and we know that that's a lot of people and there's a lot of people that don't want to reach out and that's another thing that we're struggling with some of our needy families don't out of guilt and shame or you know other various reasons are afraid to ask for support or feel like that's not you know kind of shameful to ask for support and we want to encourage everyone if you need help and support please ask for it because we're here to offer that so don't get in shame when you need support we all go through our challenges in life and we want to make sure that you get what you need and that the children are safe and taken care of and that they have a little joy in their life during these holiday seasons as well now we can take pictures when we go to visit the family is that we have had a few families not want that so it depends on the family but we do require everyone to sign a waiver so that we can take the pictures and use the pictures you know to display or what have you most I would say 90% of the families do allow pictures yeah well we don't want to step on anybody's toes and if they feel uncomfortable we want to know we want to know that yeah we find all that information out in advance and let the donor know beforehand so we are going to go take the gifts next week I think it is is that right Glenn then when are we going when are we going to take the gifts to the children I'm sorry I muted myself but we're going to meet this Friday and as Katie and we're going to join us but you can't make it can you join us and send you the address but then you know we wanted to emphasize adopt the family more we're just a small player in this we're just enjoying enjoying this so much to be able to communicate and I think they're going to pick up their dinner on Christmas day so they'll we ordered a meal for them but we deliver the gifts on Friday yes that is so nice when parents can go pick up a full get a full meal for Christmas and feed their whole family it's awesome if the meal from Zippy's is fabulous the Christmas oh my goodness they have so much stuff for the Christmas dinner and it's Hawaiian yeah I'm sure that they're going to love it it's pig chicken long rice salmon and help here boy that was recommended by it was recommended by your organization yes that's something that families really enjoy especially that local food right can't always afford or have the means to do all those fixing so special thank you so much yeah that one sounds really good I am absolutely I'm sure they will enjoy it no doubt yeah you know we only have a minute left and this has been such a pleasure Glenn I just adore Glenn he has given for as long as I know him he just gives and gives and gives whatever it is and so thank you Glenn for all the years that we've been together and all that you've done and Lisa what a wonderful project you have I am so pleased that there are people like you in the world that give and make sure that other people have this is just a wonderful opportunity and again we have your address Eric did you put up the address I didn't see it but I'm sure you did where they can reach Lisa and anybody that wants to contribute and how they can contribute and you call and how to reach Lisa thank you thank you so much we are just about out of time as I said it by the end of the day you will get a link from Haley that gives you where you can send the program to whomever you want for as many people you can put it on your website right we will do that yeah and thank you so much thank you so much for having parent sync on and for Glenn Dr. Peng and your generous hearts and giving back to the community and our adoptive family program thank you again so much and we'll see you next time


Welcome back to another episode of the shocker of the week today We're here at the muscle farm gym, and I want to introduce you to a workout that is I think Pretty insane. It's a cross-speed workout and it's called Diane The fastest athlete did it in one minute and 35 seconds That could be really the shortest video of the shocker of the week, but I doubt it because all you have to do 21 deadlifts I think with 225 pounds and 21 handstand push-ups Then you go back to deadlifts 15 reps back to handstand 15 reps back 9 reps 9 reps for all of you guys who do Cross-fit on a regular basis. This might be an easy workout or you know You're used to it and it might not be a shocker for me personally It's gonna be a shocker for sure really important for this workout because it's such a short But high intensity workout you need a warm-up, but before I do that. I gotta change Okay, I think I'm ready for that. Yeah, my biggest concern right now is the 21 deadlifts with 225 pounds that I haven't done that many reps with that weight Wow a shocker of the week sure um I was exhausted I'm still exhausted. I still feel it took me three times longer or two times longer than the world record One minute and 52 seconds took me four minutes and 37 seconds It was brutal not gonna lie puke of the clown almost Stopped by he knocked on my door, but I didn't open One thing I totally forgot to mention that earlier in 2012 I took the course and became a level one certified Crossfit trainer, so I've done this certification process I've done all the workouts back in 2012 and I know Crossfit has a bad reputation sometimes, but it's only because Some people just jump in don't know the technique don't know the philosophy of Crossfit and then they just make the sport the Yeah, the workout routines just look bad. So most important thing is Really digging deep and and understand what is the purpose why like why should I do Crossfit workouts? Or why should I do bodybuilding? You know like different different purposes, but definitely a shocker of the week I'm so happy that I did it. I'm for sure gonna do that again Yeah, I was like I said Switch it up sometimes, you know do different things if you always do the same thing as at the gym Where you do bodybuilding and then you throw in like a Diane workout for for crossfitters out there They might look at me like that was pretty slow my boy Yes, correct because I haven't done it in so long and now I Shocked my system and now I can go back and do my bodybuilding routines. Thank you so much for watching. See you next time


A Stecker is primarily a high-tech machining shop, CNC machines, computer numerical-controlled machines. We cover anything from agricultural to construction to other commercial facets. And training is immensely important. It's been very difficult balancing the fluctuation of the need for both a skilled workforce as well as technological advances allowing for relatively unskilled laborers to become machinists. So it's very difficult for us to try to bridge that gap between the labor force and the skills we need. By utilizing LTC we were really able to have a focused setting in which we could dedicate training time specifically as opposed to worrying about making sure the machine stays running while we're trying to explain something, some of these more complex ideas to somebody who is new to. I think everybody took away something from schooling whether they're older or younger I think everybody picked up on something. I started out knowing nothing here and in the last two years I've learned a great deal I think everybody should go through it. Between all three shifts we've seen a greater confidence in the workforce people seem better able to do their jobs.


In this presentation, we will take a look at multiple choice questions related to property, plant, and equipment. First question, straight line depreciation calculation. A, cost divided by useful life. B, cost and salvage value divided by useful life. C, cost minus salvage value divided by useful life. D, cost multiplied by useful life percent. E, cost divided by useful life in units. The best way to look at this type of problem might be to actually put some numbers in there and just think through a calculation. So if we had a straight line depreciation calculation, how would we calculate that? Typically, we would have the cost. So if you were to make something up and say, well the cost is like 11,000 and that's how much we bought it for. The thing that you need to remember is then we subtract out the salvage value. So if it had a salvage value of 1,000, we'd subtract that out. That gives us the amount to be depreciated. And then we're going to divide that by the useful life. So we're going to take that over the useful life if we're saying that there's 10 years and we're going to divide that will give us the depreciation. So if you think through this and think through the components here, then you can that might be the easiest way to do it put some numbers to it. So then we're going to say the A says cost divided by the useful life. Now that's close and you might think that's the answer but we knew we don't forget the salvage value. So we have to take into account the salvage. So it's not that cost and salvage value divided by useful life. Now that would imply and implying addition and we're not adding or subtracting. So it's not adding salvage. C says cost minus salvage value divided by useful life. That seems good. That seems right. D says cost might multiply by useful life percent. Now we could have a straight line percentage used but not the it wouldn't be called the useful life percent. In other words we you know we might come up with some straight line percentage but that's not doesn't look right. And then E says cost divided by useful life in units. And the straight line method isn't a method that's going to use units for allocations. That doesn't look good. So C looks like the correct answer. So we have the straight line depreciation calculation C cost minus salvage value divided by the useful life. Next question. Land improvements are a assets that increase the useful usefulness of land and are not subject to depreciation. B assets to increase the usefulness and are subject to depreciation. C included in the cost of the land. D expense in the period purchased. And E also called intangible assets. So let's go through the skin. Land improvements are a assets that increase the usefulness of land and are not subject to depreciation. Now it does increase the usefulness of land but the question of course is comes to this depreciation. Now note that B says as you know much the same thing assets that increase the usefulness and are not subject to depreciation. So oftentimes when we have two answers that are pretty much the same and they have a bit different wording somewhere that we could suspect that those one of those two would be the correct answers. So I'm going to go back to those two and I'm going to think that one of those probably looks good. So C says included in the cost of the land and that might seem appropriate but we're not going to include the land improvements in the cost of the land. We're going to actually break out the land improvements into into their own subcategory. And so D says expense in the period purchased. And if they're land improvements that are going to help for multiple periods in the future then typically we will not will capitalize those also called intangible assets. And if they're part of land they're going to be tangible we can touch land. So land is typically tangible so that doesn't look correct. So between A and B land improvements are A assets that increase usefulness of land and are not subject to depreciation or B assets that increase usefulness and are subject to depreciation. Now when we think about improvements we usually think about something that's like connected to the land but part of the land like a parking lot or if a road on the land or you know if we're putting some kind of sign on the land or something like that or just the landscaping. So something that's part of the land but it typically will go down in value if we don't maintenance it. So a parking lot will go down and if we just have a parking strike it will go down in value. The landscaping will go down in value. So although the land itself we don't depreciate the improvements we do and so that's going to be B here is going to be the more correct answer the the correct answer. So land improvements are B assets to increase the usefulness and are subject to depreciation. Next question which of the following is not property, plant, and equipment. A, land, B, parking lot, C, buildings, D, forklift, E, patent. So if we go through this again which of the following is not property, plant, and equipment. So remember property, plant, and equipment is going to have a useful life of more than typically one year more than one period and it's something that's tangible typically we can touch it. So first we have land. Now you might think land might not seem right but it because but it is it's it's going to be it's part of property, plant, and equipment. So it's a bit unusual for property, plant, and equipment in that we don't depreciate it but it still is included in the property, plant, and equipment. Parking lot. Parking lot is is part of property, plant, and equipment. A building is part of property, plant, and equipment. A forklift if used in normal business operations would be equipment that would be included. So we're left with a patent and the patent does have a useful life but isn't property, plant, and equipment typically because it's intangible. So that's going to be an intangible asset. We're going to treat it much the same put it on the books as an asset and then try to allocate the cost over its useful life but not a tangible asset. So therefore answer patent question which of the following is not property, plant, and equipment? E. Patent


Let's roll! Hello everyone, welcome to the Jenkins Infrastructure Weekly Team Meeting. We are the 21 of November 2023, and around the table today we have self-damaged portal, R.V. Le Meur, Stephen Merle, Bruno Verrarten and Kevin Mortitz. Let's get started with announcements. The new weekly release, I already forgot the number. It's 2.43. We have the war released properly. Package is released and pushed to mirrors. We are retaining the Docker image build, though. R.V. and the HIE have an operation to do on the windows, Docker images from last week LTS, and for windows. Once it's done, we will create the tag build and push the images. It's not done yet, it should be done, let's say, 30 minutes after our meeting. So we'll have a message on Jenkins release channel. We train as windows image re-tagging is required before. What's the status on the changelog port for you, Kevin? It's set to auto merge now, so as soon as it finishes doing it, it checks it'll merge. Cool. So I propose, Stefan, that you wait for tomorrow to upgrade in Frazier, is that okay for you? It's perfect, thank you. We have other announcements, folks. I don't either, so let's look at the upcoming calendar. First of all, next release last week, next week, as usual. Next LTS, I don't know when is the next LTS, since we had one last week. NA. Well, we have adversaries announced. We don't have any adversaries announced. So NA also. And next major event, let me copy past from last week. Because I'm lazy. If you don't mind, I'm going back to the announcement because we had an announcement. We were able to release a LTS last week, right? I've already forgotten the number. Okay. I was right. Released last week. We had an issue during the windows packaging. Scaling up windows. Kubernetes node. Failed with no abuse error. It's by manually scaling up. We're not sure why did we have that issue. So after more or less 20 minutes, we saw that the windows environment wasn't up. So we had to manually scale and relaunch the build, which was already failed. There were a word errors. Looks like AKS had some issue. And restarting the packaging build fixed the problem. So again, we know what to do here. That should be a program of switching from windows container to windows virtual machine. Because a windows virtual machine takes two to three minutes to start. It's way faster than scaling up, then pulling an image, et cetera. But that might need a bit of tests beforehand. So, yeah. We know how to do it. It's not that problem. It happened on half of the LTS release. I don't know why only on LTS on weekly. Usually it works very well. So maybe Wednesday is a bad day. I don't know. No other info issue. Everything else went really fine. Thanks everyone for the help on deploying that new version to the infrastructure on CI release, trusted on third CI. Following that update, I saw the G-CASK change the... We had some hiccups, configuration hiccups on G-CASK along with both new appearance section and data. Plug-in. So we have to be careful to check the G-CASK configuration for on Puppet. Because I don't think we have been able yet to fix it. So Stefan, are they having in mind that we should wait and restrain ourselves to update plug-in on CI and Kinsai on the other until we have checked that the new appearance section has been updated like it was on Kubernetes. I think if it's okay for you, we'll open a new issue for Puppet controllers. Is that clear or do you want clarification on this one? Okay, what do we have else on LTS? Do we have something else on the LTS, folks? Okay, so let's go on the work that we were able to finish or close. Let's start with plug-in details for Ogaton. No work there. Oh, Erwe, I saw you were able to change the closure. Should I be able to... Oh, yeah, I can close as not planned. You have to click on it. Yeah, that's what I don't. Oh, sorry. Oh, no, okay. Okay, good catch. Thanks. Okay, so that issue moved to the next section. We had a user who wanted to have their account deleted. Yeah, it's not automated. There are numerous flows of accounts junk inside you. You cannot remove. So we need to be careful on this one. In that case, there was a doubt about the person because they were claiming to have this email, which wasn't the email inside their LDAP account. So we had to explain multiple times that had to access the account and change the email. And then answer to the email I sent to the private email or to prove by changing things. In the end, they were able to confirm and change the email. So they had both access to the account and they were able to access the email and answer my emails on the private and the new one. So we removed the account. Always be careful because we have people trying to social engineer accounts here. And that could be an account takeover of a plugin maintenance. Be careful on that. Any question? Okay. So we were able to finish the updates on LTS for all the account, all the controllers. As we mentioned earlier. Again, two issues closed around Jenkins account. That's always the same. We explain and no more answer at all. So we closed them. Now let's roll on the walk in progress. So let's start with the date center. Hervé, can I let you report on that topic for everyone, please? Yes, so we've got our last test up and running. The caller is also updating our file share and our packets. The pull request to add the synchronization to update center job is ready for review. This additional thing are behind an option flag. So we can merge it and use it when we want. We'll probably have to plan a run out to test it in situ. And that's most of it for me. Sorry, I was muted. Nice, that's clear. That's a really good news functional test is success. Even though we had even though we had different behavior between Jenkins UI and Jenkins CLA, which was expected somehow. So Jenkins CLA. So next steps. As you said, verify update center to once per is merged. So just a reminder, you wrote it, but don't forget backups. On the on the PKGVM. As you said, plan a brown out. Yeah, and start the reduction of C. Yep. Which should happen before even planning the brown out. To start. If we get enough approval on the. Jeff draft. And also for later or in parallel performance test. Of the new. Is that okay for you folks. I have also. To not forget. Copying the. How did the plugins tools installer. These are tools installer crawler, which are not working anymore. So. These are not in the generated content. And we have to ensure we've got initial copy of them. Installer and. Installer. Installer. You did already had an item on the issue on the issue, right. I've reported it on the issue. Yes. Oh. As well as not updates. Cool. Do you have any updates on the issue reports this fifth five element. Do you have other elements in the UC. No, just to note that we disabled. The. Automatic scan. Which was set with a crown on your orbits. Because since the update center job will run every three minutes. So I already have scanning progress. So. We don't need the. Cron scan. Avoid. Good. Good one. That was an hypothesis. We initially initially stated that. We don't care, but in fact it's creating a lot of reproducible error. Because every three minutes, if there is the five minutes automatic. Instance at the same time, it failed the job. So better. Since we updated every three minutes, that doesn't make sense to have a background. I think one better to have it synced with the updates enter generation every three minutes. And also the last point in the. Full request. I've also did the. Ability to add. Many buckets. For now, we only have one, but. As is. Bucket synchronization are running in parallel. It shouldn't impact the. Total job time. Nice. Okay. Which mean. Plan adding. US East one. Let's say US East mirror. So we will start and put in production, at least during the brown out. And you update center with two different mirror one for us. Because today it's already on the US East. Well, so we don't want to change the latency of the US users. However, the European users should benefit from the initial. Brown outs because they would already have a West Europe. Which is what we have today. And in the future, we can have more. Is that okay for everyone any question clarification. Okay, cool. Let's continue with. 64 migration. Stephen. Yes. From the top of my head, I am. I did the move the. All the, the three. I've got the name. I'm sorry. Yeah, I need that. Plug inside plug inside issue and plug inside API. To the. I am 64 not poor. And I tried this morning. To move the CI, the weekly CI Jenkins.io. But it seems that I was not patient enough. So we'll try again after that meeting. You also migrated. And. Oh yeah. Or the new. You see charts. You see it's a big center for the. None. And so the last. The last mile for that issue is weekly CI. Later today. Nice. Next step after this issue. So you have hoping. Two new issues about that. That's correct. Yes. We will have to state the first one is. Infra CI. Migration. I am 64. And the other one is CI Jenkins. I. I propose that this new issue will be stated and had it on a milestone or not a bit later stuff that. Operationally, that will be the next steps. I also have a next step on top on top of my mind that I haven't mentioned earlier. Public. Gates. Resize not. Because. We used to have big Intel machines. And we started with tiny. Machines that. Scaled quite often. I think we have now seven machines running. Oh yeah. One for the technical. One for the technical services. To Intel and for. Now the Intel are almost empty. While the RM are packed. So the goal will be to decrease the size of the Intel machine increase the size of the IRM machine. And they'll resize that will be a separate. It should be done. But that will have a direct impact on the bill. Does it make sense? Is that clear? Yes, it's perfectly clear. Cool. We can take care of writing the shoe. Both of us in Peru. I don't mind the writing it. Because you already did the heavy work here. But this. There for now. And we'll come on. Okay. Is that all for RM 64? Do you have other. Points to add things, things you learned. All things I learned a lot. But. No, nothing to add. Okay. Next step. It's the contributor. Where is that? Okay. Your turn. Yeah. I haven't. I have no progress to report. For now. I work on it this week. Okay. Okay. Okay. Same for the digital. Sorry. I was traveling. Same status. No progress to report. And I need to write the mail and make you validate the email. Any question. Okay. So now. I got some report to do though. On setting up the secondary subscription. First of all. Permissions. Human admins. So you should all be able to access the subscription. And service principles. So the service principles are technical accounts used by our automated system to manage. As your resources for terraform or Jenkins to Azure. For. For. So that's a good thing. And that also demonstrated the ability to have a single terraform project. Manipulating resources on two different subscription at the same time. For that we use. Two different. Providers. They both have the same ID as your RM for Azure resource manager. But one other specific subscription. And for each resource that you define on terraform you have to select. The secondary the new subscription provider otherwise it's the default one. So I've kept the default one right now. And you must explicitly set resources to be created on the new subscription system. Virtual network. For. Public zone. Created. So that was second step on Azure net project. Created a new public network with subnet. And it's paired with the actual one. Even if it's a different subscription. Is. Back to one. Peering to network allows request to to be sent or to traverse to to cross both. By staying internal. It's as if you had to submit. Without having to go through the internet and paying for the bandwidth. We still have a fee for the whole bandwidth and gateway data. But it's. Close to nothing. It's 10 to 15 bucks per month. That allows us to have a machine on the current public network to be able to communicate with the new public network. For public. So now the work in progress is. Creating resources. To allow CIG in SIO. To spin up agents. In the new. The net of the new subscription. That one is taking quite some time because I've had to. Let's say to increase the. But to fine tune the modules we use in terraform to define controllers agent and stuff. I there is an open pull request in draft. I have to find the modules. To fine tune the modules we use in terraform to define controllers agent and stuff. There is an open pull request in draft. That is being reviewed. That should do the trick. And then I should be able to start creating resources by. Adding a new call to the module but on the new provider. Initially I wanted to do it manually but the risk of errors in copy and pasting were too high. So right now it's a big terraform module split. But that looks to look really, really, really good. And if it work as expected. We should be able in less than half a day to also do the same for trusted and third CI. So all that these workloads could move immediately. To the new subscription on peer networks. I'm really happy with the outcome. Then. Next step. Rested. And so that CI workloads. That's all for this one. The goal is to be able to decrease the bill. And see that we can consume a bit of. Of data on the new subscription on November and be able to pay the sponsorships. With the sponsor credits. Any question. Cool. Let's continue. I saw you were able to start diagnosing doing some diagnostics. With the plugin. Plugin site built failing on infrasy. CI. Can you report with us? Well. I'm still. Diagnosing it because. It is really flaky. Flaky. Only one built. Of five is passing. The young fetch. Step. So it's a bit difficult to reproduce your. I've got it on. I've heard it. Currently looking at difference between. CI. And I've heard it. I've heard it. I've heard it. Different. I might have found something around. I stay home. Environment. Variable. To. CI. And to. Jenkins on. I've heard it. And I'm wondering if I stay as a right to. Have on. The home. The Jenkins. Order. So I'm looking at it right now. The good news is. I've. Successfully. Running on. Without using. The curve in the pipeline. So. If. When I. Got. The running. Probably. Merge. One. And remove the docker. I'm on. CI. Good job. Thanks. Is there any. Question. Things to confuse. Okay. Yes. Yeah, no, it was about the contributors. But life is your. Report but. Question for Kevin. I've asked him. It's. We can wait later. I was thinking about the duplication of. Image. For the avatar, for example, they are duplicated in a static. And a source. Folder. In the robot. I see that later when I. Put in place the. I see this. Thanks. Stefan. Can you report for the. Sponsorship. Oh, I haven't done much. Just calling fewer. Few contact in there, but I. I have to fulfill a form. That have not done. But yes, the content said to wait a little because of that. Even they had. Huge haven't and everyone was focused on it. Had. Last week. Last week. In France. We for president. I mean. Good news. Their event. Had president macro. And. Things that you open source was important. Speaking about. Open source. Yeah, I said. Mark that he used his. Presentation. He used his presentation in New York to. Deal with the open source. Good way of working. That Macron. Said that Mark. Had a good way of presenting the open source. It's too bad. It's not here. But that's a good news. I mean. With the. The marketing and the noise it's doing. Let's. Fulfill the point. And. Push the contact. Hey, we are open source. And the president of the company. He said that's good. So. Do you want to help? Because that's your life. Right. We'll see. Kevin. Where are you able to work a bit on the. Chinese website or is it still. Working progress. And to find out where the. The web page. I built this. And I also built some charts. Kubernetes management and C. And followed the instructions and the Jenkins IO helmet chart. Configuration. The instructions were a little off. So everybody was able to help me figure out where the build. Archive. Zip file would end up and how to get that. But. I had a couple issues trying to set it up. So I changed course. And I started. So I ended up finding a handful of like stack overflow questions, Reddit threads, other resources that were explaining the rewrite call. So, yeah, so I actually understand how that works now, kind of a little bit. So Mark hasn't had a chance to set it up the last time I spoke with him at least. He still needs to do a little bit of work there. He still needs to do that on his end. But yeah, I think at this point, we're probably going to need another session to go over it with you some more. And don't hesitate to ask if you need any explanation or help. Of course. Cool. Good job, folks. Thanks for the help on this one. Stefan, your turn. Again. Oh, God, yes, I did move all the sanity check from the Linux part from the shell script to the to God's. So we got a God's Linux file. And I updated all the data line manifest to point on that new file. So it's done. Next step is to check on the windows part and do the same. So moving all the rest residual, the leftovers of checks to God's windows, and then to update all the data line manifests. And after that, we would have to factorized and get out every common parts to a common file goes common. And, and of course, after that update all the update CLI manifest again. It's kind of time consuming all that. Okay. And my side, I have to report that I had to do a quick fix up on one of the CLI manifest. Oh, I did a mistake. No, you forgot the git version. And it's fixed. Because there is a new 2.43 oh git version for both Linux and windows that has been released recently. It's already available. I guess there might be a security issue we haven't checked yet. And it's, it has been merged on Packer image and realized that yeah, we forget it for Linux. So just have it in mind for windows that you might have to add the kit as well. I mean, given the list of tools for getting one tools is highly probable. That's, that's absolutely normal. There is no problem. And as soon as we catch it, we fix it. That's the only important thing. I'm pretty sure it's it's Bruno's fault. That's fine. I'm joking. Okay, I tried to delay as much as possible waiting for March. First of all, was not working. So his VPN was not working. So for the LTS required team help. So I had to help Mark did not have time with him to check more check with him on his windows machine. I believe there is months configuration or something. VPN search is signed and deployed them. So I believe there is misconfiguration on client side or an unplanned issue. Last one plugin install stats. I haven't followed. It was between Mark and spin it. And I believe no work was done since last week. So no progress to report. So, unless I mistaken all the issues from the current milestone need to be moved to the next milestone because we should work on all of them. Is that okay for everyone. Okay. There are two issues that we should assess if we have if we're able to work on them or not. New issues. Here we are. First of all, I am 64. Stephen. Yes. I am 64 not pool. Will you feel like you can start working on this on the upcoming milestone. Given the current workload. I think so. Yes. Okay. Not the second one, but the first one. Yes. Work on it. So I'm adding it to the new milestone and I'm removing the triaged and second issue. Thanks for opening both of them. So the second issue require some work from Bruno. You didn't know, but yes. I'm sure you already did the work. The goal is to test a plugin builds on a pull request and see I can see you for using a Linux RM 64 virtual machine. Yeah, I have migrated one plugin for timing just to test. Oh, and it's already working. Yep. Okay. So let me add it to the milestone then. No estimation, not triage. May I ask you Bruno to have the comments linking to the plugin or the pull request you tried so we have a work log that oh okay we know that it should work at least on that plugin. Yes, for sure. Cool. So you are volunteering to help, you know, reporting on this one. No, you mean just making sure that it not forget to do this. Okay. Okay, I'm removing the milestone. We won't have much effort to spend on this one. So that Stefan can focus on on infras here first, but yeah, if you can already report the work done by Bruno on this one that will help. So when we will take it in one or two weeks, we should be able to continue. Great. Is that good for everyone? Oh, Mark is there. Hello, Mark. Let's finish the issue and then we can, we can ask questions to Mark. I don't see any new issues here. So, I need to write was the issue that I had raised. Oh no it wasn't there. I'm sorry. Nothing. Excuse me it was a documentation thing different. No problem. So I got a few issues to write. I'm going to try to the new charts and use I am 64 for it's. So, get Jenkins I use is like what I call the legacy mirror bits charts and updates enter work that are made it shows that the new mirror bits parent charts which is a composition of sub charts is now the way to go. We invested time and effort on the new charts. And that new chart allows a Stefan demonstrated this week to run separately. They're single and I am 64 while mirror bits remains on Intel until we have an official RM support for it. So we need to migrate get Jenkins to that new short. That operation can have impact on get Jenkins I also it has to be announced. And the migration need to be done carefully, even though the risk of losing that is not a problem, because we have a ready space and the ready space can be is updated on each mirror bit scan. So we run a scan we wait 10 minutes and it's okay. And the data, the persistent data is on Azure volume, which is, which won't lost any data. So there is a low risk, but it can have an effect on get Jenkins IO starting to serve request slowly because it has to go to the fallback. Another issue to be written off course issue. We had something earlier today. Public gates, not resize Stefan. I will need your help to, I will try to call right this with you. So again, the goal is now that we have migrated a lot of workloads to RM 64. We need to study the sizing of the machines and the scale horizontal scaling to have the best pricing as for today given the current workloads. The first step is to is to use smaller Intel to lower the price first and then smaller in for notes. Check for RM 64 notes size and amount changes. The goal to see if we are able to have the promises of RM 64 saying hey five to 10% decrease of the cost. I don't have any other new issues. Just a reminder, if you haven't seen the message for the weekly release packages and while we're released Kevin did the work on the changelogs which will be done soon if it's not already. However, I've retained the Docker image tag creation, because we need to first do a few operation on the windows LTS images before taking the risk of building the new weekly and accidentally override the tag. Thank you. We will report on the channel. So yeah, it's just delayed a few hours, but we should work on it right now. The date for the next weekly is wrong. It's 28 November. Good catch. That's unfixed. Thank you. Do you have new issues or thing you want to mention? So, so one that's worth mentioning here, not an issue for us, but you should be aware. I received a request from Steve Chin of JFrog asking hey could the Jenkins project please publish an attribution on the download page so www.jankens.io slash downloads that notes that we use JFrog to store our binary artifacts. I've submitted a ticket to the Jenkins.io site to do that and explain to Steve that downloads that Jenkins or the www.jankens.io slash downloads actually is does not use. Oh, you had it. You already got this. Okay, so I'm wasting time telling you something you've already processed. No problem credits, credits due to RV. We'll already let us know on this one. Great. Yeah, so, so the long, the long discussion I was about to do is unnecessary. Excellent. Yes, we will I think we should do it. I think unless there are objections from others, I'll plan to go ahead and be the one to implement it with some description of our mirroring infrastructure and attribution for each of our mirror providers as well. Absolutely good idea. So, Tsinghua, OSU, OSL, Yamagata, Aachen, Belmet, Xmission, etc. They're all we're deeply grateful to all of them. And Cloudflare. Yes, and and when Cloudflare is implemented we'll put Cloudflare there as well and we should put Cloudflare on updates.jankens.io. Digital Ocean because it's hosting archives.jankens.io since two months ago. Yes. Oh, I had forgotten that one. Thank you. Okay, very good. Right. Today's meeting. And so, at Digital Ocean. Right, because they host archives.jankens.io. Yes, thank you. I had forgotten that. Thanks very much. No problem. I'd like to state to ask a review from everyone from the team. I believe everyone from the team should take time on the pull request that Mark will have to check that it's running properly and we don't forget any sponsor. Well, and I think I want to do a separate page that talks about our mirroring system, right, because I think it's a nice piece of technology that we're using with links to mirror bits with a highlight of how grateful we are for their involvement as a project and ongoing development. Yeah, it's attribution on that page and then links elsewhere to a longer description about this is why we mirror and it's crucial that we do so. Thanks. I don't have anything else. Mark, just to confirm the statistics issue, no progress to report. I am not sending any message or changes. No, no progress to report. And I consider it low risk. Therefore, it will probably be a while before I make progress. So you're welcome to drop it from the from the specific milestone if you need to. Okay. Thanks. About the VPN, I assume you did not have time to check. I did not have time to spend on either any member of the team. Right. That would also be dropped from the any milestone because I did my need for it turned out to not be as crucial because the weekly the LTS release was so successful. Okay, I believe we should still ensure that you have VPN access. We should, we should close that issue with success. I agree. Okay, I don't have any other topic. Is that the case for you? Do you have something else to add folks? Nothing else from me. Okay, so I'm going to stop screen sharing. I'm going to stop recording. So goodbye for people watching us.


Good morning everybody. It is actually Thursday Not really the normal Monday lot walk that we do, but it's Thursday today. Yesterday was Wednesday. We had the 4th of July I was on vacation. So a bunch of stuff came in while I was gone and we're gonna go over that right now Hope everybody had a happy 4th of July and it is currently July 6th, so Thursday we're gonna get to it.  We delivered over 180 cars. It was it was a really really good month or close to 180 New and used so it was a really good month. Hope everybody had a great June and let's get July rolling right now There's my t-bird a couple sold challenges that we're waiting to get picked up first off here. We got a 2022 Ford F-250 this is an XLT with the black appearance package This one's got the power stroke diesel and the 10 speed automatic transmission You know what you get the 20 inch blacked out wheels blacked out step bars and the Blacked out grill with the kind of bronze Ford logo on it. This one's got 19,000 miles This is a one owner from Kentucky and it's absolutely perfect. I didn't see a dent or ding on it So really excited to get that truck going and through our shop. I've got a 2016 this week was the this weekend was the week of trade-ins. We got just a ton of trade-ins in this is a trade-in This is a 2016 Dodge Charger SE all-wheel drive. It's got a hundred twenty two thousand miles on it We got a couple little things to do on the interior We got some dings and stuff to take care of but I think that'll be a really nice ride. That's jazz blue This is a 2018 Dodge Ram I think this is a Laramie Yes, this is a Laramie Sport package and it's got the Cummins diesel in it. This one has I Want to say 28,000 miles once again all these vehicles are going to be linked in the description below So click the links. I'll have them all labeled and everything, but this is the 2018 Ram 2500 once again I think it's got 28,000 miles. Don't quote me on that. This is a 2015 GMC Sierra bronze alloys the color It's a double cab short box. It's got 95,000 miles not even sure if we're gonna keep this one yet I really haven't even looked at it. It's got the Z71 package not too bad Would have to get a couple interior things fixed on it Right here. We have a really nice B5 blue 2010 Dodge Challenger SRT. This one's only got 7,000 miles on it It's got the options group two with the subwoofer It's got the moon the nav the heated seats the 20 inch wheels and B5 blue really a good-looking vehicle. I didn't see a ding on it So as soon as we get this one cleaned up and through the shop I'm sure it will sell fast and here is the 2022 Dodge Challenger super stock So this one's got the drag radials on it the wide body kit the high output Hellcat 6.2 liter engine supercharged Indigo blue is the color and really a sharp ride. It's got the moon the black stripes over the top You get the red eye badges on the Hellcat logo there This one's only got 2,000 miles and believe it or not. This was a trade-in on just a normal Hellcat. So Really a cool car. I've never seen one, but now I have anyways. We got a 2020 Chevy Equinox. This is an all-wheel drive LT with the red line package on it It's got leather heated seats backup cam and for life me. I can't remember any miles around this. I want to say like 50,000 maybe You have to check the website. This is one that we've already got through our shop. It's already cleaned up I got to do a video on it today 13956 that's a Camaro convertible ZL1. That's a really nice car as well. This is a 2017 Ram 3500 and I want to say this one has Can't remember it's got like 42,000 miles on it, I believe and this one's got the high output Cummins diesel and just Super super clean. I didn't see a single ding on it. No scratches It just needs a bath and this thing will be 100% ready to go Really a hot truck and it's loaded out. It's got a nav system on it heated cool seats It's got a nice big brush guard on it as well The Monaco reds a color on there and then we have another 2016 Dodge Charger SE all-wheel drive. It's like a clone to the other one that we just got in in Trade this is also a trade in it's an all-wheel drive It's got 99,000 miles so a little less miles than the other one if you like white better than blue. There you go here is a 2019 I believe 2019 2018 no 2019 Ram 3500 so this is a 2019 Ram 3500 single rear-wheel. It's got the Cummins diesel This one's got the high output Cummins diesel. So it's got the icing transmission and this one is A Laramie as no a bighorn. This is a bighorn, but what's really cool about this one is somebody is wrapped the top So it's got a two-tone effect Really looks good whoever did it did a really nice job wrapping it the roofs wrapped as well It's got some nice wheels and tires on it color-match bumpers and Yes, that's a bighorn. I think it's a night edition But that one's got 64,000 miles on it and that one's just about perfect as well This is a 2020 power wagon so this one has the 64 hemi this one comes with a an 18,000 pound easy lift fifth wheel It's got the leather interior. So it's really a nicely optioned out power wagon it's got the big radio and I want to say that this one has I can't remember the exact miles on it I Think it's right around 36,000 miles on this one. This is a brand new Pacifica trade-in that we got So it's a dealer trade. We just got that through. This is a forward Mustang GT premium convertible Mazda 3 I got to do a video on a ram 2500. I got to do video on all these are through our shop Here's a really nice 2020 Jeep Grand Cherokee limited. It's got nav and moon. It's got some really nice BFG tires bright whites of color It's got the 3.6 liter Pentastar V6 engine that was a trade-in from yesterday. So that's as fresh as they get that's the last one I booked in yesterday and We have a convertible Corvette.  So we had to take that off and we're gonna redo videos on that We also got a Shelby GT 07 that came in From California. That's really nice. What else came in? I've got a 2012 Sorry, this is kind of a long video, but like I said, it's been a couple days So we got that Mustang in yesterday as well. I believe that's in a 17 I think this is a 17 GT premium convertible stick shift It's got like 30, no 20,000 miles on that one. This one is a Shelby GT 500 2012 If you watched any of my other videos, I have one of these cars mine's a 13, but this thing's really nice It's got the rickaros. It's got that SVT performance package This one has the red stripes. These are factory stripes on this car with the silver ingot or ingot silver Lines on the outside and this car is just about as nice as they come. It's got 11,000 miles That's going into the shop in just a little bit. So that's all the stuff that we got outside This one has Roush exhaust on it too sounds really good 2012 just about mint with Only 11,000 miles on it and then I got two more in the shop right here. Let me I Won't bore you all the way over there We got our little arid desert right over here. So Patches here is Pringlay Largest cactus in the world right there that big one. Anyways, let's hop inside the booking area or the drive-up. We should say 2022 Ram 2500 Laramie Patriot blue metallic this and got the Cummins diesel. It's got the Obviously the Laramie package color match bumpers as well 20 inch polished aluminum wheels. This one's got 8,000 miles does have a couple little dings We got a fix on there, but that's nothing too serious And you get those color match bumpers with the sport appearance package can see only 83 100 miles on this one's got the big radio still has a water bottle in it too So we're actually waiting to find out what the stock number is on this But anyways really nice truck and then lastly we've got a 2020 Lincoln aviator This one has 30 Want to say 36,000 miles on it? Something like that 39,000 miles. Anyways, this thing's kind of cool new aviators. I haven't seen too many of those. Anyways, that's the lot walk and I think it's ruby reds color on this one and Hope you enjoyed it and let's get July rolling and check out the description below Remember to like subscribe and share and hope everybody has a fantastic day