Everyone has a stake in the fight against the climate crisis. Climate action is a priority for the UPU, whose 192 members have resolved to reduce greenhouse gas emissions in the postal sector. Posts have implemented measures to reduce their footprint, switching to renewable energy sources, planning smarter delivery routes, and creating reusable and environmentally friendly packaging options. The UPU will help posts exchange knowledge on emissions reduction strategies, climate finance, and climate adaptation while monitoring the sector's progress.


Sometimes you're going to have a teacher that comes in and their only thing that they really want to do here and take away from here is seeing the mansion. And other teachers say, you know, it meant everything to me to go on a slave life tour and learn more about the history of the enslaved community. And then still others say, you know, I just really wanted to do a hands-on workshop and walk away with these materials that I know I can just translate right into my classroom. Oftentimes the group leader will have different expectations than the group members themselves. And so the way that I try to mitigate that is I try to put something in the schedule for everyone.  And someone has thought about, you know, even the direction that it will be placed on the thing and what is next to it and why it's there and every single one of those objects is supposed to, you know, sort of tell you a whole story about something. One thing I found kind of a little bit hard was the shaving kit, the actual little brush that actually people use to put the shaving cream on their face. What I'm going to give you this afternoon is our internal memo that kind of goes through all the highlights of what's actually there and some of the decision-making processes that the curators used to get stuff back. And so yeah, the shaving kit, you know, is based upon a period shaving kit. It's really not enough to just say this is what history was. You really have to ask people, kids to really think about it and draw their own conclusions and take their own interpretations and that the process of evaluating the different sources and different places really leads them to a much deeper, richer understanding of history that really stays with you You know, things that you can actually work with in everyday life.


The first person charged under the national security law in Hong Kong has pleaded not guilty as his trial began almost a year after he was accused of driving his motorbike into offices at a rally while carrying a flag with a protest slogan. The case of Tong Ying Kit is seen as a departure from Hong Kong's common law traditions and it was denied bail and a jury and a test of the government's claim that the slogan liberate Hong Kong revolution of our times is secessionist. He was arrested on the 1st of July 2020, hours after the enactment of the national security law which punishes what China deems as subversion, secessionism, terrorism and collusion with foreign forces with up to a life in prison. Tong faces charges of terrorism and inciting a secession as well as an alternative charge of dangerous driving causing grievous bodily harm which can lead to up to 7 years in prison.


So hello, everyone. Welcome to the second day of DefCon check 2022. And it's my pleasure to announce the next meetup or actually first meetup of today being innovation in complex projects empowered by communities. If you have any questions, utilize the Q&A tab or basically enter the meetup by clicking share, audio and video. I will kick you in the room as well. And I hand it over to Natal. Hey, good morning, everyone. How are you today? I'm very excited to be here to talk about how in this meetup room today we're going to talk how innovation in complex project is empowered by the communities. This is a very good example on how a community could build around an open source project and then develop and you will hear from the people from this community how cool is to start a community, join a community and contribute actively to this community. So I'm really excited to be here at DefCon 2022. Looking forward to be there again in 2023 on site. But for this year, let's have this meetup virtual because we have lots of very, lots of cool stuff to talk about. So if we go next into the slide, we can kick off this conversation. We have an agenda for today. So we will like to introduce you who are the speaker of today. You see some folks here in this window and then we go into the technical details about the unarchitectural overview on how this project is built. We're going to share more info. Yesterday we had a session with Andrea, Ben and Mattia talking about also how to build cross-platform build for the edge. So we're going to talk about how to run those work in the edge. And then we're going to do another walkthrough into technology in a walkthrough on how containers work in this environment, how we can build a secure environment. And then finally connect the work to open source. We have some appointment also for the community we would like to share. So if we go to the next slide, please we can start. Now we would like to introduce you the team. So please come in the chat and say hi to the team. Let's go to the first one. You see here this is the those are the Quarkus for IoT community. Let's say leaders, those are people that are actively contributing in the community. Everyone is really welcome to join this community. We're going to share also in the chat link soon on how to join the community. So if you see those folks here, you see some of those today's presenting. But we have Andrea, Andreas, Mattia, Mario, Marcus, Jeff, Ben, and I would like you to present them today. So if you go into the next slide, Andrea, I'm ending over to you. How are you? Thanks, thanks Natale. And hi everyone. I hope you're still enjoying the DevConf. It's remote and we again are looking forward to be with you next year on site. But so yeah, you've probably heard about me yesterday, Andrea Battaglia from Italy. I live in Pao South, thanks to them. Today they did a pandemic lockdown. So I'm still enjoying the warm and shiny and sunny land in southern Italy. I'm here today with my peers here to tell you how we can work together on your project on some innovation as the technology or the community elite. And also I will introduce some key architectural points and will explain you why all these people are here to ready to have an open conversation. Please feel free to stop us anytime to share your voice to ask questions. We will make sure this will be an interactive session. So we are not here just to present what we have done and what we are about to do. As you can see from the picture Andrea is an experienced traveler and joining conferences, open source conferences. So you will see for sure in the next DevConf on site. So yeah, let's go into the other team members. Hey Ben, how are you? Hey, good himself. So yeah, I'm Ben Salyard. My day job. I'm a solution architect at Red Hat. But as part of the community I've been focusing a lot on some of the consignment technologies, how we actually bring that closer to our IRT and edge devices. Yeah, I'm basing the Netherlands. Cool, cool Ben. Yesterday Ben also did a great demo. I really like to recommend you to see again the recording that will be available soon about the presentation. And let's go next to the next team member. Hey, Mattia. Hi, Mattia, Magia, Principles and Red Hat. Based on Halps region, which is Switzerland, Austria, a kind of specialist in a lot of stuff. But yeah, I like to dig around cool stuff. That's why I joined this community because always working on the edge, on the cutting edge technology. And I like doing sport recently ballet training. You see in the picture trying to escape from customer meetings and do fancy stuff. Cool. Thanks, Mattia. Yeah, this sport looks really kind of adventurous. So that met up, I like the analogy you made that you try to escape. Sorry, this is a meetup. I would like to ask a question to the audience here. Do you really think that's Mattia? Because that doesn't really look Mattia. Probably that's a picture from the internet. That's me. Come on. Look at my arm. Look at my arm. Yeah. Yeah. Maybe he just rotated the image. He was not doing this. Okay, let's see. We have 20 people connected. I would like to give a big shout out to all the people attending today. I know it's Saturday in virtual. I promise you this is really cool topic. And we will see how in a few seconds, let's finish presenting the team. Let's go to the next step. Hey, Andreas, how are you? Hi there. I'm Andreas. I also work for Red Hat. I'm in far down south of Germany. As you can see, if you go south in Germany and you can't get any further, that's probably way with me somewhere. I'm the only up sky in this team in the shark tank of developers speaking Java code. I don't speak Java code at all. I'm taking care of the rollout, pixie booting and the edge device setup and OS 3 image and that kind of stuff. That's what I do in the project. Fantastic. And I like this picture, Andreas. This is where you live basically. It's fantastic. It's taken over there somewhere. Wow. So, Andreas, as you heard from me is the ops person. If you want to hear from rail for edge or kind of under kernel system administrator, this is the person to talk with. And if you have any questions, please send it in the chat. And of course, sensible automation. And of course, sensible automation. Yeah, of course. Oh, as we say in Italy, dulcis in fundo. The best at the end, as I'm joking. My name is Natale Vinto. If you see here, I put some YAML. As Andreas will say here, we are all developers, all kind of Kubernetes developer. So, here's the YAML to present me. I'm developer advocate here in Red Hat for Open Shift. You can follow me on Twitter, Natale Vinto, love football. Actually, I didn't push this container image yet, but I will do soon. You can see it on the top right, this book that I wrote with another colleague, Marcos Isole, about how to modernize enterprise Java. And we also mentioned it in the book with Marcos, this project, which is because it's very, very cool. And I agree with Andreas.  So thanks. This is me. I think we can go next. Let's have a YAML person. Let's have now an overview, an architectural overview as we discussed it. So if we go to the next slide, I think we can hand it over to Andreas again, because he can present. Andreas, what is this project about? What are we talking about? Yeah, thanks Natale. So let's start talking here because Andreas is right. He's the real only ops guy here, even though only few of us develop Java, actually, just Mati and myself. And one of the other main contributors, or Jack Newsom, he does, but the other, so Ben, Andreas, also Mario, they are amazing technicians. So we started this community because back in the days, two years ago, I was implementing on my own, supported by Natale, another colleague of mine, a small POC to play with Quarkus at the edge. That grown so much that we got the interest of IBM, Intel and other competitors. So instead of having just partners learning how to do this kind of stuff at the edge, we wanted to build something that could be useful to others, right? It's useful to customers, to people from outside the community, because the community is contributed by several people. As I said, also yesterday, there are some great specialists in the IoT. I can, for example, mention Domenico Briganti, for example. They are specialists in IoT, and by IoT we mean small sensors, small devices. Not all of them can cover by our project, but definitely all of them are pluggable in. And this is what we are trying to do. We present at the enterprise level what we keep building in the community. The only boundary, hard boundary in our community is, let's try using enterprise products. So it's still open source, it's still completely open and available and consumable and forkable, whatever. But still, we want to base our discussion, our interaction with other people, with our technical people and also the technical business people, on top of something that is reproducible that could be used as a POC, or a demo like we demonstrated yesterday for something tangible, something that the market could use. And so we use OpenShift, Andreas, for example, mentioned Red Porage. So it's not just for the IoT, the absolute version of that, but it's the real enterprise version of the operating system at the edge. And this is what we try to do. Based on complex architectures and setup, we try to build something that is reproducible. So that means, in turn, we don't do only Ansible, we don't do only Quarkus, we don't do only Red Porage. We do everything together, making sure that all the products, the third-party products compared to, or in relationship with the Red Hat portfolio and platform work together to do something that makes sense. And we covered several use cases, we covered generic edge computing use cases, we covered manufacturing, we will cover probably something around energy and utilities, something that we know the market is trying to understand and work on. So the more expertise we have, also around third-party products, the better or the larger is going to be and more reusable is going to be the PSE we built at the end. And we have development cycles. As we are contributors, we are not fully allocating this, we try to allocate some spare time on the community. And this is what also makes sense in terms of, let's build something if requested, is needed, if needed, and something that makes us having fun with that technology. And okay, this is not very readable, but that's just to give you an idea of how we think of complex projects. And this is something we built entirely. So we are able to cover SQL, no SQL storage, we are able to cover Red Porage, and Andreas will take care of some automation with Ansible, for example. Andreas mentioned also VXE Boot, which is incredible technology that of course takes time to be implemented and tested and also apply to specific use cases or projects. And on the data center side, we, of course, based everything on the OpenSheet platform. But again, to roll out applications, to roll out container images, workload, or to set up pipelines, we use technologies that maybe are not worth to be mentioned most of the time, but that are very important to customers, partners, to everyone here who is approaching the cloud-native world. So we used effect on pipelines, we used Helm charts, something that the people you can see here had already knowledge about, all that wanted to learn. And this is the beauty of this community. So thanks a lot. I guess I can hand over back to you, Natale. Yes, thanks, Andrea. And actually, that was really interesting. If you can come back to slide them back. So I would like to, this was very cool, because as you see, it's for two reasons. One is the architectural overview, so all the people can see how the progress is made. The second, I use this image for an upcoming tweet. So I would like all the people coming while we're speaking, because there are lots of cool stuff we're going to talk about. Andrea, correct me if I'm wrong. The innovation today, this year, for this year's edition is the rail for edge. I know we started with Fedora IoT. Now we're using rail for edge. And then we integrated all the components for edge and also for the open sheet part. As you can see here, there's the edge part, the data center plan part, where there's lots of innovation around messaging, the queue system. In fact, Andrea, if we go to the next slide, I think we can go to the next step. If we go to another one, we continue the flow. Yes, now we talk about running it on the edge. So let's explore this part. And let's hand over again to Andreas, because he was in charge of building practically this part. And I'm really curious about how you made it, Andreas. So thanks. The idea that we're having here is, you know, this whole setup is controlling a manufacturing plant and the edge IoT device is the one attached to the machine that actually does the manufacturing and controlling the manufacturing process. So the idea is you will not have full data center capabilities here. You will not set up a satellite and manage and patch the things. You want to have it quickly rolled out. You want to have it easy. You want to have it secure. And you want to be flexible. What happens if the IoT device attached to your factory machine dies out? So what we did here to build is we took the Fitlet 2 device, which is an industry standard Intel-based device. You could take other devices. And of course, in the long run, you could also take ARM-based devices for that. And to create the operating system, we use the image builder, which is a part of rail. But it's also, of course, an upstream open-source project based on Lorex and Welder that you can use to build Fedora or Center Streams image or whatever. So they are used with the OS tree imaging because that has a couple of advantages. First of all, you have a simple, quickly rolled out image, which is immutable. It also mounts the root system read only, which is a small but important fact. Because remember, if you have a machine, which the IoT device is attached to, the manufacturing machine has this big red button.  Let me shut down cleanly that machine first. That's not going to happen. They just hit the red button, turn it off. And you know what happens to file systems, they're reading right. And you just turn it off without shutdown. And that's why the OS tree image built with read only root is quite stable on that. So we deploy the image to the edge using Pixie boot with UEFI. We could do BIOS, but as mentioned in an earlier talk today, it's not secure. It's slower. It uses TFTP and that kind of stuff. And we do Pixie with UEFI. We could also do UEFI HTTPS boot. We just haven't implemented that yet. But the Pixie UEFI boot that we do could also, since we use the shim as a boot loader, you could also build that as a UEFI secure boot chain, once you configure your own security chain from that. And all you need in the center is a simple web server with DNS mask for the TFTP where you actually get the image and push it to the edge. On the edge itself, on the device, we just run containers with partman. And actually, depending on the use case that we're thinking about, you can start these containers through Ansible from a central management system, like Ansible controller system, or what you also can do, which is maybe more like the, what we're using now and which is more comfortable is you just push the partman configuration as a system defile. So you create your pods as units. So they auto-start so you can have dependencies and so on and so forth. Why we're using partman and not something like MicroShift? We see this edge device more like with a local configuration, maybe local drivers, maybe you have GPIOs that actually tie into the machine that you control. So you want to have the possibility to run containers and application more closer to the hardware. You want to run local drivers and that kind of stuff. And therefore, MicroShift in this case might not be the optimal setup, but it could be in a different way. So we documented and used it with REL, REL for the edge, but it also will work with Enterprise Linux Clones and Fedora. As I mentioned, RootFS is mounted on read only. And I just, you know, there's some links in this presentation pointing out to other presentations that were in this conference about edge and IoT devices that were very, very interesting. And we see some more next slide, please, on that. So what we want to go from here, I would like to go from here is we had a lot of stuff about security here. And the last talk was about full disk encryption on the edge devices. What happens if the edge device is stolen and these things? I actually want to try to push into a different direction because remember you have an edge device with an unstable SD card and you know how often SD cards break, especially when they're doing read writes for more time or run in, let's say, hostile environments like in a manufacturing plant. So I think about a diskless IoT device. So and using Pixiboot not to actually kick in the install process, but actually run the device diskless because it has, you know, it has two network cards. It can do failover and have boot over NFS or root over NFS or root over iSCSI even. So and if somebody steals the device and rips it off the machine, takes it home, there's nothing on it because it doesn't even have a disk. So that's one of the ideas I want to follow up in the future of the project. And also the possibility, as I mentioned, running MicroShift in addition to Portman containers or depending on the workload as an alternative to Portman could be both of that. So that's going to be interesting. And also after that very interesting talk yesterday about using Nvidia devices with MicroShift to do AI stuff, you know, like you have an intelligence video surveillance where you put the AI on camera face recognition directly on that Edge device, like what you can do with the Jetson Nano or Jetson Javier or something like that. And sorry for interrupting you here, Andreas. This is something we are in a discussion for. So we have this on the ongoing discussion with Nvidia. We want to do something interesting on that. And we want, and I want to use the same basically Edge build process that works for the FitLit until the same for some devices like that and also use the same distribution so that you could have a mixed environment and have your Edge IoT device network with something attached to a machine controlling it, but also having kind of a surveillance device that does the face recognition directly. So that's basically for the ops part. Yeah, for the audience also I wanted to mention that back in the days when we were using Raspberry Pi for the first use case, we actually used direct connection with the GPIO for the sensors connected to the to the serial port and using the open source driver from the technology vendor, the sensor vendor, and that worked like they were Python based. So we had several containers running at the Edge and one directly connecting to the Edge devices to these are into the sensors. And so exposing REST APIs to make the business logic at the Edge capable of reading those data, of course, decorate them and then send the telemetry to the data center. So it's plenty of stuff we can do, actually. Exactly. And that's it from my side. I don't want to take all your time. That was very interesting, Andreas. So we've seen the real Edge part, from the operating system. We mentioned the micro shift as an possible next step as an innovation on this part. Now let's go in the other part. So let's talk about a little bit how container technology, open container technology enabled and speeded up the innovation. For this part, I think now if we go into the next slide, please, we have been talking about it. Thanks, Natalia. So yes, I'm going to just quickly tell you about how we've used some of the container technology to help speed up our development at the Edge or for IoT. I'm not going to go into all the technical details. I mean, if you want to see that, you're welcome to look at the recording for the session we had last night. But in essence, by using containers and our IoT and Edge devices, we give a lot of flexibility towards developers, right? So think about having to manage all your dependencies when you want to deploy your applications. Using containers sort of simplifies that process quite a lot. Like Andrea also mentioned, it's also possible that we can deploy our applications as a set of multiple different containers for a specific need, right? So you get that isolation when I want to deploy something, right? So in essence, that allows us to ship our applications quicker towards our Edge devices. Next slide, please, Andrea. So as part of the community, we also ran into some challenges when dealing with different different architectures. Like Andrea also mentioned, before in the previous run, we dealt with ARM devices on our Raspberry, for example. And in the last hack-faced run, we dealt with Intel architectures, right? So to help us actually develop and compile our Quarkus applications, the community developed a set of multi-ARC containers, essentially, that allows you to run containers for different architectures in an emulated way, right? With QMU embedded inside the container. So we are maintaining a set of these native builder images that allows you to get rid of your virtual machines and stuff to actually compile Quarkus natively. Next slide, please, Andrea. Ben, sorry. If I may, what you are talking about is quite interesting. And this is something we are trying to achieve now in the community. If you think of all the things that these gentlemen are talking about and thinking of sensors somewhere, not maybe attached to the devices, but in the network, right? We can, thanks to this work Ben has done, we can pick up the real sensors, including the physical CPU architecture of the devices. You think of the workload in a completely isolated space. So if Andrea's works on the big book, right? And Mattia thinks of the security around the data coming from, coming through now the network from the sensors to the data center and several decoration. The business logic working on the data and transferring them or working on some AI analysis can be completely coupled and could run on microchip, could run on R4H, could run on Fedora IoT and whatever kind of probably platform or operating system that provides, then correct me gentlemen if I'm wrong, a container technology to run the workload, right? So that brings cloud native stuff everywhere actually. Yeah, exactly. And I mean, if you go to the next slide, why this is important is that essentially your developers working on building these solutions can keep a consistent workflow, right? So if they are familiar with container technologies and use Kubernetes for stuff like your data center components or for your edge location components, they can keep that consistent workflow. Never mind what the actual architecture is for their edge devices, right? Or their IoT devices. So that's also part of the extensions that we did to essentially allow teams to incorporate these bold images that we create inside their workflow, right? So in opening up opportunities for them to test their applications on Kubernetes, even if it needs to run on a Raspberry, right? If we go to the next slide, so some of the the challenges that we see in the future though is that well, how do we manage devices at scale? Since now we've sort of tackled some of our developer workflows, we've tackled stuff like our packaging formats with containers. But if we now need to scale this up and start managing hundreds of devices, then suddenly the management of that also becomes a bit of a challenge, right? And for that, I'm also quite excited to talk about Microsoft, which essentially adds a layer on top of Podman to make it appear like a Kubernetes cluster, right? So it's this lightweight layer with a low footprint that allows you to actually manage your edge devices as any other Kubernetes cluster. Now, what makes this important or useful is that now if you couple that to your cluster management tools, like Rackam, for example, now you can actually start managing your edge devices as just another Kubernetes cluster and actually deal with stuff like updating your OS on your device, making sure that they're all on the correct version, right? So it simplifies that management of your devices. So I'm quite eager for our community to actually explore how this can actually help simplify the management of these devices. So for more information, I think Natalia has also added some links in the chat if you want to actually explore those projects yourself, right? Yeah. Thanks, Ben. I put some link in the chat. This is really, really cool and interesting. We're talking basically here about what is the future of managing multiple ubiquitous Kubernetes endpoints, clusters. And if we look at the edge, now we have a rail for a hedge on top, the micro shift container. So it's kind of a connector that can talk to Kubernetes controller. And so you can control Kubernetes also at the edge, but having a minimal footprint container base. So that's the evolution around the edge. And let me also, since you mentioned it, let me also mention that Open Cluster Management is the red dot effort on open sourcing our Advanced Cluster Manager for Kubernetes, which is a tool to control multiple cluster, multiple Kubernetes on multiple cloud. This is fully open sourced now. And it can be used to control several workload, data center and moreover edge. So there's lots of excitement around edge development. And since there are many, many pieces that can many, many computing units, I think, and Matia, maybe probably makes sense to start talking about security. What do you think about? Before Matia goes, and I have an interesting story, Matia, because this is a meetup, right? So I want to push a bit all of you, that's an endless discussion actually. So we had the chance to use Fitlet devices, so enterprise great stuff. We had the chance to use Jetson because we have some stuff at home. And we had the chance to use Raspberry Pi, Raspberry Pi 3B Plus. We wanted to have some physical hardware restriction to be able to really prove that work was native, as we mentioned yesterday, can run with a very small footprint on small devices. But now the question is, is it really worth it to use MicroShift and where should I put it? So before we were, we connected early to test that was set up here. And with Andreas, we had this discussion, and this would be, and I also encourage Matia to discuss this also during his piece. It's interesting to see why should I put MicroShift on an Edge device if I'm short on resources? I mean, on a small device, it could be Arduino, Raspberry, whatever. I cannot put MicroShift there, or it's not worth it. But if you think of, based on the initial architectural review, I have some powerful servers that do AI or ML, whatever. And then I have the devices in the same, so it's not in the same local area. I could put MicroShift somewhere in between on an Edge device, but shipping more physical resources. Gentlemen, what do you think? Otherwise, MicroShift is... It depends, for me, it depends on the architecture and on the kind of application that you have. Think about it, because MicroShift also works with the OC CLI, you know, the OpenShift command line. And if you have the Advanced Cluster Manager or the Open Cluster Manager, which is the upstream of that, you can also manage your MicroShift with your Advanced Cluster Manager. So if the applications that you will use on the Edge are quite similar to what you run on the data center and you have a central management for all your Kubernetes, you can also include the Edge into the management and then push your applications directly from your Dev cluster or from your data center cluster straight to the Edge.  If you're in an industry application that says, I need to have an application which is closer to the hardware, which actually uses GPIO or these kind of stuff and needs special drivers, then you're better off, I think, with pure podman. The overheat in the hardware, I don't think is a valid point a lot, because MicroShift actually uses one CPU, one tool, maximum two gigs of memory, which is nothing compared to what you have. Think about it, you know, even Raspberry Pi has come with four gig today. And eight gig is the next step, even for the Edge devices. That's not a lot. And which is, it's absolute commodity. So I think it's more a point of the view, how you manage your environments. If the Edge is completely disconnected and local isolated network, then you rather go off with, you know, deploying podman containers from a local registry. And if you include it in the big management, you might be better off with MicroShift. So this connection means that it's better to do what Ben was discussing rather than having a central cluster management, right? So where is the boundary between Ansible Management and Advanced Cluster Management? Well, Advanced Cluster Management can use Ansible under the hood. It's super setting, it can also run Ansible workloads. And yeah, I think to come back to your question, Andrea, it depends on also what Andrea said, what do you want to do? Do you want to control those Edge endpoints? Or do you want to consider as a far edge where eventually always disconnected and then reporting via batch or kind of, but if you want to control them, I think it makes sense to consider them as a Kubernetes cluster or Kubernetes endpoints so you can have a consistency across all your deployments. If you want consistency standardization across one deployment model, I think you can, considering using MicroShift in this case, otherwise for other more disconnected, less interactive endpoints, probably you can rely on just Podman and those kind of workloads. It's an open place, very cool. And if there's somebody in the chat that would like to contribute to this, what are your thoughts, please send it over in the chat. It's an open discussion, it's a meetup. I know it's virtual, but it's still open and we would like to hear from you. Yeah, so in the while, since we're talking about multiple cluster, multiple workloads, hey, Mattia, what about security? Yes, it's like always the last piece on the puzzle. Yeah, also, if you just to conclude this MicroShift, I will say that having a standard solution across different platforms is ideal also for developer rights. And as we're talking about security, I will see this as the next step to create a unified service mesh federated with also out the edge, which is really nice. And so you don't need to kind of a custom solution to satisfy the security, but you can have a standard way to secure the edge as well. So because the challenge is you see how you can scale the security about micro-savage in general on edge device. So think about renewable process, revocation process, of 1000 devices that are connected on your platform. So the idea is to have a kind of standard solution, right? And working with Kubernetes and micro-savage, the standard factor provided by the community and is a search manager. Because search managers provide an easy tool to manage certificates, a standard API to interact with the multiple certificate authority, like Venafi and Ashikop, which we use it for our POC on the community, and give really the confidence to the developer to work on the security part. I help you to speed up the development because you can create a self-sign certificate. And when you're ready, when your production run, they use the real certificate authority. And as well, in case you work with a API, which is not standard or non-common, you can implement a custom integration because it provides a standard API to export the certificate from your custom certificate authority. Next, please. And of course, when you work in cloud native rate, you want to use Quarkus. And Quarkus allow you loves Kubernetes because it provides a native extension based on the fabricated Kubernetes cladding. And so it makes it easy to work with the Kubernetes environment. And why we want to use Quarkus? Let's talk about how to dynamically provision and certificate in Kubernetes environment. So we want to, of course, when you work with microservice, you want to recognize not just the servers, but also the client. And this is called like Muta-TLS. Muta-TLS is an additional security layer on top of the standard TLS because you won't as well recognize the client who is calling it, not just the server. So in this architecture, we see the integration that we have done for this POC around the PK provider with the choose fold and the cert manager component. You need to click. Yes. So now considering this is a meetup, you all, your audience should know, shouldn't know that Matias is expecting me to know exactly when to click on the next slide. I do like this. 20 slides with one more line, every slide. So it's crazy. And I'm okay. May I show them all of them? Yeah, okay. You're so kind. How many of them, seven? Eight. Eight, I guess. Tell them the numbers. So in cert manager, there is a component called issue. Issue is that you're interfaced with your PKI provider. So when you configure the issue, you configure the issue to tell, please vote your PKI and give me this certificate and specification based on this domain value, whatever. What's happening is that when you create an issue, you are able to start creating a certificate type. And then cert manager is going to watch certificate. And based on the information that you give it like common name, subject, alternative names, type of the key, and is going to contact the PKI provider, get the certificate, create a secret for you. And then when you have a secret, your application client server can mount to secret in a classy way. And then they can start doing the client server connection with Mooda TLS capability. And then user can access the information from the client. But how you can, next, please. Oh, thank you. Now I wanted just to say, Mathias, if I may. So when we started developing a bit of a history and also open discussion, when I started developing the first use case, that was completely unsecured. So I was just creating a self-signed certificate to make the edge, the workload at the edge in a container connect to the MQTT protocol exposed by ActiveMQ, AMQ on OpenShift. And of course, once Mathias started implementing this piece, I found it quite easy. Because the only thing I was supposed to do was to download the certificates and use them for the connection. So we introduced something very important that's very high level actually here. Mathias is giving you lots of information that, okay, it's mutual TLS, but we have to distinguish to make a distinction between two type of certificates, the bootstrap certificate and the runtime certificate. So the certificates you use to connect to the MQTT endpoint to some telemetries. And the other one is that the certificate that the each and every edge device we've been talking about stalling devices or blocking device or dropping devices because they've been hacked somehow. So those bootstrap certificates are the certificates that the device owns because they are tightly coupled to that hardware ID or stuff, which is again completely different from the runtime certificates. The certificates the device receives through the mutual TLS with some other endpoints on some servers in the network. Yeah, let me go to the next slide. Yeah, if you go to click up to four. Up to four, okay. Thank you, Mathias. You're welcome. So what happens here is that when this hour, the latest POC with the Magnum Factory, we want to kind of scale out the provisioning of the factory self, but also all the services around and the data center service running factory and services running on the edge. So we because we want to kind of scale out this we implement a register services, which allow you to which provide an API to register a factory or as well a machinery or a normal services running in the platform. So what happens here, you have a booster part, which Andrea explained you before, which allow you to connect to the register services and kind of telling, look, I'm a factory, one, I want to register my factory to start working on the on the data center. So what's happening here, the device and the request to register the API. And because it has a proper certificate is allowed to send those requests. And the registration is going to get the information. It's going to create the certificate resources under the data center in space. And then certain manager take care about the connected API provider extract the certificate to create a secret. And then the registration service API is going to watch the secret when it's ready, because it's a synchronous communication. So you kind of need to implement this capability, but Quarkus because we with reactive capability is able to work really in a nice way for the synchronous mechanism. And then when the certificate ready is going to send those certificate on the factory. And then when the because we want to kind of scale out, think about the factory can go offline or the center got flying when the factory is going to register is going to request a type of intermediate certificate. Why is that in because we want to kind of give the job to the factory self to spin up all those certificates for the factory instead to rely to the data center. So and the data center is going to give an intermediate certificate authority. So the factory can spin up the old certificate for the device and the services and can work by itself. But there will be everything will be trusted by the same Piki central Piki I certificate authority. And this is part of the job we are doing to make sure that we dig up all the data center plant from the factors, right. So in an enterprise grade architecture, we want to make sure that each and every layer can leave also without the VPN connection that actually could could drop. It's a matter of that's what I see in the future. Hopefully this year with micro shift and the service mesh federation, I will see, I would like to drop all those these things leverage a steel search manager as an entry point and all your Piki provider. But all those messages will be taken by the service mesh itself. And you have really a standard cross solution. Yeah. Well, super cool. We had this extensive overview on how the community build security. And Mattia was specifically in charge of this part. So how add the security bits to the overall architecture. And as Mattia was eventually know, security should be first. No, for you have to think about security at the beginning. But you know, you start from scratch and then you eventually adapt. I think this is a really good solution. With search managers, it's all open source around Kubernetes, the ecosystem enabled this. And in this case, there are integration with a vault system also external vault system. I see mentioned it here. There's also Ashikorp. There are many. But the cool thing is that it's a pluggable secure infrastructure. Yeah. So folks, we're going into the end of the session. But before closing, I have some quick reminder, quick appointment to give you. So how do we connect the word to this community? Mattia also shared in the chat the link to open feature request pull request. So the first thing you knew if you would like to join this community, the first thing you need to do is going into the Quarks for IoT website, join the GitHub organization. We're going to share again the link in the chat. And the second thing, we would like to talk to you about how we celebrate the winners of this Ackfest. This is the third year. So for the previous two years of the Ackfest, we all celebrated on OpenShift TV, which is our channel. We used to do a show talking about OpenShift and all clownative architecture here at Red Hat. So we have this show available. And actually, we celebrated the winners in one of the main show inviting those people talking about their experience. And in the slide, you will have also the recording available. You see there are the links also to those recording if you would like to hear about the previous editions. If we go to the next slide, actually, we would like to invite you to this year's edition. So we have two appointments. One is the February the 9th. We will celebrate the Red Hat Ackfest winners on OpenShift TV. If you go to OpenShift TV, you will see the full shadow of this series of show we do around OpenShift. On February the 9th, the OpenShift Coffee Break show will be really pleased to have the community and the Ackfest winners to talk about what was their experience and to celebrate with them. In the Ackfest landing page, you have the list of those three winners, the first, the second, the third place. And I will not spoil that if the people that doesn't know yet. We're going to celebrate with the winners. We're going to talk about the Ackfest. So I think it's really cool if you can join us on February the 9th at 10 a.m. Central Europe time. This is very cool. The show will be published in both YouTube and Twitch.  And the second appointment is March 9th. Again, the OpenShift Coffee Break is a weekly show happening on Wednesday at 10 a.m. Central Europe time. Again, on March, it will be another episode where we're going to invite the community. So next episode, February the 9th, we're going to talk about and celebrate the winners. And on March 9th, we're going to invite and talk about the community like we did today with more people from the community. So those are our points. We will try to give updates on what we are doing. So a lot of the folks here, they have mentioned MicroShift. We started last week investigating MicroShift because we want to make sure that makes sense for the business, but we will give updates on several additional stuff we are doing. And let me also mention one of the things that Mattia put in the chat. If you have any idea, any need, any curiosity, if you want to join, if you want to challenge us to do something specific, we will try to do this at our best convenience, of course. Please join us. Please open a PR request on one of our repos to propose use cases and challenges. That's what we are looking for. Yeah, that's the spirit of the community, right? Please join us. Please join us in the, Andrea also showed the link of the Quarkus variety organization on GitHub. Please join the organization. Please join us in the community. Please join us on our next appointment, February the 9th. And I think that's all folks, right? It was a very cool discussion, very deep architectural. I'm really excited about this discussion. And now I'm handing over it to Lucia. And thank you, everyone. Thanks, Radek, for your comment in the chat. Thanks to everyone that joined us today. It was really, really a pleasure to be here at Defcon 2022. Thank you and happy Defcon. Thank you. Thank you for a lovely meetup. It was awesome, guys. Like really awesome, energetic, and we covered so much information, but still lightweight. And I'm curious how many attendees will actually meet you on the February 9th or March 9th? Yeah. We're looking forward to it. All right. Thank you. Thank you so much, both attendees and the speakers. Thank you. The next session, like the next the next meetup will happen at 3 p.m. Central European time. So see you soon, like after lunch. Bye. Bye-bye.


Shake what broken? Ah, yo, of course. Oh, zima. Bro, like, it has to happen. No pika ma lume pika, it has to happen. So that's a heartbreak sum? I think so, is it? Ya niya pili ana yo. Yeah, it is. It is. Shapa, nyele kitu you have to in, with the tissues and everything.  Pasmiya sabi et pili.  Ha, hi, say, goodbounds and nation. That's what you are on. Shout out to everybody tuned in right now. We have a guest in studio. We wanna talk to her just now, but before we do that, I think it was a lume. Just maybe five people.  Now I'm gonna start with IG, Instagram. Madhu, su u wa sahaw sana. Leo tume, zima ma la zima. We have to shout you out. I have young Painei, we say hello guys. I'm gonna follow you back. I promise. Say hi to Ken Ken. Bless up. Young Painei 125. Rungai, well represented. Love your show guys. Keep grinding my guys. We love and appreciate you. Thank you so much. Rasa jeset na kwa nadi this to the IG. U nasama kasaonga kusaonga naks. Filiin wasap rachaw kofiti. And then I'll show you kumoto. Mbaya sana logs from Mavivi. His name is The Way to Take It. Okay. See what Makauki Kitega. Was inform kaka mega sho ikon on the fire. And it says why the, why ya ben and platinum. And then to the other kikuyu marsive. His name is fire brigade. What's up? Hashtag bounce nation. All right. So we're gonna go back to that in a few. But first we talk to our artist today. We, no. I was going to tell him. We're gonna have two of them. We had a brapa come through. Shout out to him by the way. He's dope. And of course right now we have a phenomenal vocalist. She's a songwriter. She's a recording and performing artist. Of course. Beautiful in person and on video. Her name is Raguru. How are you? I'm good. How are you? So good to see you. We're fine. Thank you so much for coming. Thank you for having me. I'm so excited to be here. No, we're excited to have you actually. Your voice is, you have an amazing voice. Thank you so much. You're welcome. All right, so Raguru. For the people who've never heard you. Last month Fanevo. Last month Elisha. I can introduce you but you can do a better job doing that. So please, can you let us know who Raguru is? Okay. My name is Raguru. I'm a 21-year-old Kenyan musician. I'm currently studying international relations while singing, writing, releasing music, performing and everything. All right. Awesome. So I first heard about you when you released No Love. Yeah, I think what we really could do on No Love. So tell us about the whole experience and how that came about. Yeah, No Love was the first song that I released under the label that I'm currently signed under Taurus. So it was the first huge music video that I created and released and it was the most amazing experience and it opened me up to a whole new world of music that I had not even known. So it was just me. I love No Love for that. It was that one song, the one that put you out, the one that put you on the map. You talked about Taurus music. How long have you been there and how is it working with them? Because you didn't do one song with them. You've done a couple of singles. Yeah, I did around three, three, four singles before them and I signed with them in 2020. Right. So I've been there since 2020. It's been such an amazing time with them because they have so much insight especially to do with the music industry especially the business side of music because for me it's just I want to make music and I want to sing and that's it. So they come in and they can help me with every other aspect of music because it's not just singing and releasing music it's also greater than that. So they help me a lot with that aspect. Yeah, it's amazing and a lot of people shy away from signing. But I'm sure you have a good experience because it can be crazy. It can be very crazy because I was an independent artist before so at least I understand how it is being independent and how it is being signed. There are pros and cons for both of them. But pros of course are to weigh the cons in this case. So you released an AP self-title to depend on and depend on love yourself. Love me honestly. Love yourself. What's the name of the AP? It's called Rogoro. It's not yet out yet. I'm going to be releasing it very soon. It's going to have no love crazy, foshizi, blessings and a couple of other amazing songs that I've been working on for the past year or so. So it's Rogoro. It's self-titled because it's my first AP it's my first project so it's my introduction It's called Rogoro. Here I am. Ah, nice. They better know. What a better way to know you than that. So that means the music must be very personal to you. Yes, definitely. There's a lot of love because I've gone through a lot of love and heartbreak over the last few years. There's a lot of partying. I'm young. We like to have fun. Of course that's what 21 is all about. There's a lot of sherehe in that album. So it's just me basically as I am.  So how's that working out? Being in school and working on your EP it must not be easy. Definitely. It's a lot balancing the two. But we make it work. I make it work. I have my schedule I gave my schedule to my team. I tell them I'm in class this time you cannot call me to do anything at that point in time. When I have exams I'm basically not there, I'm nonexistent. Yeah, but we make it work. Right, and your songwriting process tell us about that because the music is the same as you shakwa heartbroken So, who writes out for you? You do that yourself? No, not by myself. I write with this artist called Mbifi. He's a rapper. Amazing. And also Mero Page, another amazing vocalist. She's a great musician as well. So, I really just alternate between the two. I work with Mbifi I work with Mero Page. Right. And I've barely seen in collabs on your work. It's been like singles and singles even though you know all these great artists. So, why haven't you worked with anyone? Are we going to see that on the EP? Yes, most definitely. I've been working on a bunch of collabs this year and I know in the EP you're definitely going to see a collab with Kahush which is really amazing. It's also a great song. So, so far for the EP it's just one collab. But more to come. That's just the introduction. And of course you were also part of Project X alongside Siza. I tell us about the whole experience and yeah. That's taking me back. I thought it was when I had released Deserve with Siza he was such a great rapper. I heard him and I thought that I was listening to Tupac. He's so great and he has such an amazing story and he's just a great rapper. So we recorded and we released Deserve in 2018 and Project X had called us to come in and do a live performance which was the best experience as well. Especially because I was also very new into the industry. Like making music and everything. That's a whole lot of experience. And you've actually in a span of like that short time you've experienced a lot. That's because you can show that you're going far. You have a great weight. I hope so. Definitely. I keep pushing from your side and I keep pushing from our side. Grave. I keep not on you. Definitely. Alright, let's breathe for Shizzy. Yeah. Now for Shizzy is a love song. We released Crazy which was a heartbreak song. No love which was basically just saying no love. Like there's no love here. Just pipes. For Shizzy is just love. Like it's just like I was explaining it's just like the purest like description of love. Like how you feel like you've cheesied when you're into somebody. They make you feel like you want to be with them for so long until you even start to look like them. Like this is a love I see last. Love so deep. Exactly. So it's just about love and the greatness of it. Alright. We love to see that. We love to hear that and we are glad that you are here and of course we wish you all the best and everything. We're going to play it for sure as soon as it's out. This is Helm. Do you have anything you want to ask her? No man. I just want to advise. I'm really happy we've met. I want to ask her that this is a love I see the way Kingsley is just looking at the love when he's just like when are you going to stop talking he was ready a long time. He was ready at some point this song. Actually we've met two of the same girls but we can't do justice if we let people listen to that before you tell where to find all these like your YouTube I'd like to shout out my mom and my dad My brother as well who just started his exams today Good luck And who else? Mokami in the states, I don't think she can see this But shout out to you, I love you so much as well She can, she can definitely stream it We would have sent you the stream That is kbcdoco.kefodslash y254fodslash For those who want to stream, that easy And you can stream from everywhere, anywhere And kanzu, shout out to him for coming to We had him a few weeks ago on the show Super talented And he pushes other people Nakumka, you had that conversation About him being one of the people who vouch for others as well Like he's an artist, but akun ele jelasia She's going to make it more than me I don't want to be So yeah, shout out to him as well Shout out to kanzu Okay, now we want to see you perform for us You ready? Okay, cool, let's go


This is one way that I teach the strategy counting on using dot cards with my students.  See, there's two cards, okay? And I would have the class and I would count together the dots on the two cards. One, two, three, four, five, six, seven, eight. Then I would ask them, boys and girls, how many dots are on the two cards? And they would hopefully tell me eight. If they tell me something different than I would count the cards again until they agreed as a group, there are eight dots on these two cards. And I would say, gosh, I wonder if there's a faster way to count the dots on these cards. And they might give me some ideas and different things that they think would be there. And then I would tell them we're going to learn the strategy of counting on. All right, boys and girls, how many dots are on this card? And then we would count them. One, two, three, four, five. How many dots? Five, excellent. Boys and girls, how many dots are on this card? One, two, three. How many dots on this card? Three, okay. Now, which card has the most dots? Hopefully they would see that the five has more dots than the three. So we would take five and put it in our head. We're going to hold the five in our head. Boys and girls, don't forget it. What number is in your head? Five. And then we're going to start with five and count on. Five, six, seven, eight. Boys and girls, how many dots are on the two cards? Eight. That is right. Let's try that strategy again. Boys and girls, here are two more cards. Okay, let's count the dots. One, two, three, four, five, six. Can we count that faster? Can we do that job any quicker? Hopefully they're going to say we could count on. If they do not, then I would say, remember, we can count on. Which card has the most dots? One, two, three, four. I'm going to put these dots in my head. Four. Remember, don't lose it. What's in your head? Four. And I'm going to start with four and count on five, six. How many dots are on both cards? Boys and girls, six. Then we're going to move on to two more cards. We're going to do the same process, but this time I might have them do more of the work. Boys and girls, which card do we start with? Hmm, which card has the most dots? Hopefully they notice this one, and then we would count it. One, two, three, four, five, six. And put that number in our head. What number is in our head? Six. Start there, six, seven, eight, nine, ten. How many dots are on the cards, boys and girls? Ten. The strategy is counting on, and it's quicker than counting dot by dot. I would continue this until every student was confident. If they just weren't, I would take cards like this and put them in a bag and do small group activities and to build their confidence. If you have no cards, you can also use dice. They work the same way and count the dots. This is one way that I would teach the strategy counting on to my early childhood students.


Live from Las Vegas, it's theCUBE. Covering NetApp Insight 2018. Brought to you by NetApp. Welcome back to theCUBE. We are live at NetApp Insight 2018. I'm Lisa Martin with Stu Miniman and we're pleased to welcome, for the first time to theCUBE, Sydney Warner, SVP of Worldwide Service and support at NetApp City. It's great to have you here. Thank you, I'm thrilled to be here. So this morning's keynote, talked a lot about transformation, transformation of NetApp transformation that your customers need to execute, to be competitive, to be successful. Tell us about the customer transformation that you're seeing as the leader of service and support. Sure, our customers want outcomes, plain and simple. They are buying solutions that lead to outcomes. So in the service and support area, the conversations we're having with our customers now are all about outcomes. What can we do to ensure their outcomes? To ensure their transformation, to ensure they can provide the services to their customers that they're looking to provide or new revenue streams or what have you. But it's really all about outcomes and that's awesome because they don't care what's behind the curtain. They don't care if it's this box or that box, they care about outcomes. So that's a really big transformation for us. Yeah, Sydney, one of the big challenges that used to be, okay, I've got a box. I know exactly where it is. I know exactly who set it up and all the configuration. Now it's like, wait, it's a multi-hybrid cloud world and I've got software spanning all of these environments and my data's all over the place. That has to have a huge ripple effect on the service and support. Walk us through a little bit about what that looks like. Yeah, I would tell you the number one thing in our world, if you really think about it is data sovereignty because where's my data? If I were a CTO or a CIO, I'd wake up in the morning and go, where's my data? Because, and we're managing that data for a lot of clients and so it's really all about where's my data and making sure that the sovereignty of the data, it's supposed to be in a certain place, it's supposed to be protected in a certain way. We work with a lot of regulated environments. So think healthcare, think even automotive to some extent. All that IOT data, who's touching that data? That's personal data. So as the future has talked about this morning, the ethical side of data for service and support is really intriguing to us actually. What's the conversation like Cindy with your enterprise legacy customers who weren't born in the cloud? How are you helping them kind of embrace the change that they have to go through? Yeah, I think the number one thing is to not be dissuade into thinking that it's all cloud, right? It's not everything is not made for the cloud, especially if it wasn't born on the cloud. The pathway to the cloud could be very difficult and maybe not even prudent. So we're doing a lot of assessments for our clients to decide what workloads belong in the cloud and helping them to understand it isn't all cloud. It's some cloud and it's hybrid cloud and so it's this wonderful Lego cube that we build for them. That episode has done quite a few acquisitions in the last couple of years. How does that impact what you're doing? Think about everything from the Kubernetes pieces and what's happening in AI to talk about some of those challenges and opportunities. Sure, I mean I would tell you something like green cloud that we did last year. When we look at managing those workloads and helping to build out that Rubik's cube, right? Of piece parts and what that overall orchestration and architecture looks like in the future. Something like a green cloud helps us to orchestrate that. It helps us to manage that and really that management plane for our clients is really where the hard burn is. It's taking a look and seeing that entire data landscape and managing and orchestrating that and the movement of all of that data. That's the biggie. Yeah, follow a question. When I think about NetApp, NetApp was heavily involved in helping to really fix storage in a virtualized environment. Lots of us have the wounds and memories of over a decade of fighting through that. What does NetApp see as its role in the cloud native this next wave? Yeah, I think it's the overall integration. Our team now is really fixated on where do we go with the overall integration of legacy and then the cloud native stuff that clients are building and granted the cloud native stuff gives competitive differentiation, gives speed, gives scale, really great stuff but you can't leave the other stuff behind, right? So for us, integration and how that integration is going to work through APIs or otherwise is really a huge fixation in service and support. So NetApp has grown a lot, done a lot of transformation. Talk about some of the changes to your customer segmentation and how you're using that information and that segmentation to really deliver differentiated services because let's face it, customers have a lot of choice. Right, and that's a key word for us. Actually, we say as a tagline that for service and support we're looking for value-based differentiated services that deliver outcomes. Big mouthful, I know, and I have no marketing chops, as you can tell, but the truth be told, when we look at our Global 1000 customers, they want high touch and in some cases, no touch. They want to get to information, solve problems really quickly without having to go L1, L2, all through the tiers and so we're piloting programs that are proactive, predictive and that are very high touch to ensure that they can solve their problems quite quickly either on their own or to the right person instead of going through some of the typical pathways to support. All right, Cindy, I love you. You're going to help us decode some of this marketing discussion. So, you know, hashtag data-driven is something we're seeing at the show. Right. Help connect for us, you know, how are customers being data-driven as they look at their future in the cloud and beyond? Well, when I think of data-driven I think of new services. That to me means new services and looking at the correlation, if you may say, give you a thought here. So the gentleman that had the DNA and genome data, right, in the keynote, if we can take that data and correlate it to somebody's overall health history and see the transition, right? See as your blood pressure's going up or see as certain changes and deltas are happening in your health profile overall holistically, you can I think see the train before it hits you, right? You can see a stroke coming and that would be the most beautiful thing is to see stuff before it hits you. Same with the car manufacturers. If they see a pattern of brakes that are going out, Mary-Bara probably never wants to sit in front of the Senate again, right? So we can see those patterns before a massive recall has to happen. So that's data-driven to me, is either new goods and services or seeing a train before it hits you. Cindy, I know this is a short segment, but we want to thank you so much for stopping by. I'm going to give you a cube sticker because you are now officially an alumni. I'll feel cubed forever more. Excellent, cubed forever more. That's a new hashtag. We want to thank you for sharing your perspective from a services and support standpoint because those are critical services that customers need. And we want to thank you for watching this segment. I'm Lisa Martin with Stu Miniman. You're watching theCUBE Live from NetApp Insight 2018.


Hello and welcome back here to the channel It's been a couple days since I dropped the server and the discord and I couldn't be happier big Thank you to all you guys for making this drop of the server and this new car pack as great success That's something I've been wanting to do for a very long time So throughout the past couple days the server has been full of amazing driving and amazing people and so Much talent and I've just been going to replays as a replays of things I've saved just watching some of these replays and just seeing the Amount of like talent that is in this server and in this discord with you know We're running four-man trains right here there gets bigger trains You know later in this day This was like a 60-minute session of just non-stop driving and it was just so much fun You know getting tandem with all you guys and tandem, you know with the community and you know Just have a blast and you know having my own server up 24-7 is a great thing and it's just Incredible thing for me and one of the big things I want to do to start off the 2021 year 2021 is a big year for the channel is a lot of big things happening Not only with the cars the discord the team the server and everything like that There's a lot of other big things that are gonna be coming into this channel this year So it's great that you guys are now can be a full part of it with the discord that's open and it's Amazing and I can't like I said, I can't thank you guys enough for the Amount of people and the amount of support and the amount of you know Good feedback. I've gotten with these cars. You can see this this was just day one of The server release and we were just thrashing there's cars everywhere 16 slots were full Almost all the time and open up a second server on the opening day just to Go with all of these people as you can see just look at this one two three four five six seven eight nine We were nine cars deep at one point and the tandem just keep getting better and better people getting more comfortable in the cars They're understanding the flow. They're realizing which cars they're most comfortable in So it's definitely an amazing sight to see this community growing the way it is And it's just crazy to me to think that you know this is The effort I put forth to do this and this is what comes out of it You can see there's just people stacking up getting doors having a good time. I'll sort on some leads We're gonna take a look at some other clips from these replays I think it gets to the point where I get to follow a 14 and we start running another train We got starry on 13s are 30s. I kind of stacked them up there a little bit I was kind of my mistake, but people are just Incredible on this server and you know in the discord everybody's willing to help everybody It's an amazing thing to see like I said, it's incredible that you know I was able to finally do something like this that I've been wanting to do for a very long time and it's here and It's bigger than I could have imagined right now. So As you see, we're just running trains after Trains we're just throwing in deep angles having a lot of fun doing some door bangs and just a great Time and you know because I had so much fun just tandoming with you know Everybody on opening day for a little bit when I could actually get a spot on the server and we're a little deep there But he managed to bring it out alive. So like I said Everybody knows about the team and that all you got to do is drive as you know, well, are there three kind of decided to Cut in stage left there and kind of have a little bit of a Fault there, but as you can see, we're you know six cars deep right now going into the first turn at clutch kickers And you know, it's just it's awesome to see just next to a little agricultural racing there Yeah, I know it's grassroots. You don't got to be in the grass there, buddy So I hope you guys are all enjoying the cars the positive feedback I'm getting on the on the discord and everything is incredible So, you know, like I said, if you guys have any types of tweaks or things that you think could be a little bit better Let me know down in the comments if you're not in the discord if you're not in the discord You don't have these cars Well, the link to discord will be in the description join the discord get the cars hop on the server Have some fun grab some doors. The community is great so far. Everybody in my server has been an amazing You know drivers and people that were Just learning are starting to you know get even better in tandem's and are starting to get more comfortable And they're starting to you know feel the flow and get you know able to get doors with people and things of that nature. So it's What I wanted to do with this server I wanted to make the server on you know some lower power cars to give people a chance from rookies to pros that could Learn and grow with community and people are gonna help out and everything like that and that's what we have So the evil rabbit community and people you guys the subscribers is definitely a huge thing Man, I was that corolla was throwing sauce on my door for sure Brian B throwing throwing some sauce there Trying to get to some other parts in this replay I got a couple more another few replays that I'm gonna show up there I think I think I was chasing Christmas there could have or Christmas was chasing me. No still Brian B so Everybody is loving the car. So we're gonna go take a look at another replay and Get some more footage from opening day. I recorded a bunch of different things So let's switch over replays and see what other kind of cool tandems and cool things We got from day one basically release of the server on Monday. So let's see what else we got Oh Sean going deep So like I said, I recorded so many replays on day one and there's just so much to go through Just so many good drivers that I wanted to watch and just you know be able to scroll through and just take a look at You know the progression from now from then until now. It's definitely extremely Great to go back and watch some of these runs and you know pan through different drivers and watch certain drivers that you know We're on day one so where they are now and everybody's improving which is the best thing in the world Sean is on my door not giving me a inch On that he was running my door during that time. I was falling some drift snacks and we had a Facts 120 back there, too We were just having feeling the vibe vibing off each other having a good time So, you know, like I said a lot of great drivers came from day one and they're continuing to grow the discord I believe is over 300 over 300 now and it's you know, just growing every day and You know just watching raw Tandems like this and just the raw basically thrasher bashing that was going on in the server is Always fun to look at and I know this is a little different than my normal videos normally I show You know me driving with the wheel cam stuff like that But I thought this what better way to actually show you guys who maybe weren't in day one drop of this server To like what was happening like it was a Massively good time. We were throwing doors. We were having fun. Everybody was getting to know each other who didn't know each other I was you know So got a chance to hop in and talk to a bunch of people and it was it was a great time, you know Jumping into the server into the discord chat and talking to you know some subscribers that have been around for a very long time Since back when I had two thousand three thousand subscribers They've been subscribed to the channel and you know, you know, I've communicated them with through chat and messaging and all that You know and you know hopping in there and getting to talk to them, you know on Chat was, you know, totally different, you know, you don't understand, you know, the Diversity of people that follow you, you know, you can see names You can see the diversity from the countries the regions the states the areas But when you actually get a chance to talk to a lot of people you can realize how diverse the community really is and how Much drifting just brings these people together and a server that is nice chill and you know Very good and flowing and people just are out there just to have fun and do the same thing It makes it so much better because then there's there's no hate. That's one thing.  It was Super scary because I didn't want to wreck a car and then you just build up confidence And you start throwing more angle you start throwing more speed You just keep building up confidence it goes the same way and say a set of Corsa and you know When you're first starting out, you may not have the confidence to go up there and just try and charge somebody's door but You can't so like if you put the thing is if you have a server that Has a lot of people that will just be get real mad if you charge a door and hit them Maybe make a mistake or whatever, you know, that's not on here. Like I I Challenge any new driver if you ever see me on a server and you want to try and get up on my door Charge my door try and catch up as close as you can you bump me you push me around I can take some bumps I can take some licking and keep on going I mean if you if you hit me too hard we mess up whatever it's drifting It's how you learn Get confident get comfortable the more confidence you have the more you can build people up the better Everybody's gonna be and it's just gonna make the community that much better so I hope you guys enjoyed this little recap of the Drift bash entry of my server There's gonna be a lot more content coming with the server with random tandems The search for the streets team is real, so I wish you guys found me and also show media all that you found the scripture box below as always Thank you guys for watching. I'm evil rabbit. I'll see you guys on the track