keptn Community, 19 Mar 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Keptn Community Meeting - March 19th, 2020

Description

https://docs.google.com/document/d/1y7a6uaN8fwFJ7IRnvtxSfgz-OGFq6u7bKN6F7NDxKPg/edit#heading=h.uwwfn8xf7bjf

A

Welcome everyone to the next captain community meeting March 19th day 4 of global lockdown, thanks to Kovac 19 today with me, Hendrik hello, welcome Thanks greetings to the South of France, so we have a couple of things we want to highlight today. The first thing is again: the recording will be on YouTube later on. We didn't get the live streaming to work today, but still the recording will be up there.

A

The agenda there's two big items: the captain release zero six one just went out earlier this week on March 17th I believe was to date and then we're also going to have a Henry Craig set from Mutis talk about the neo load integration, both the SLI provider that you wrote as well as the new load service quickly. I want to talk about a the amazing release, the six one we celebrated yesterday with a release beer, so that was kind of interesting. The first week completely remote release beer, but it was definitely something worth celebrating.

A

I just want to highlight a couple of things. So folks, if you go to Cape for this age, you'll see some updates there. Some of the feedback we got from the community is hey, add a couple of links to make it easier to get to the tutorials to get to the community related links like joining the slack channel or finding the git, repos, Twitter and so on and so forth. So there's direct links. Now to these you should check this out.

A

The other thing you want to check out is, if you're, going to the release, if you want to, if you click on install captain, we also now highlight it or make sure that you wanted. You know that we have not only covered the major kubernetes distributions, but we've also covered mini Cube and there's a couple of other things here that I know in the conversation I had with users out there they're relevant so, for instance, captain on micro kubernetes, also captain with pre-installed eesti.

A

Oh, that's also a feedback that we receive because we install a steel in the full in subversion and some say well what, if I already have each do? If I use the East your service offering from let's say Google, how can I run it in so, please make sure to check this out. They are a big highlight for me, and this is now what comes with captain? Oh six, one by default, it's the new captain's bridge.

A

This is my installation here, so you can see that first of all the things that are new in case you have never seen the new the new bridge new layout I, get to see on my individual services, all the different route, events that either started the deployment or a problem. We also get the text that then show in which particular in which stage was deployed. For me to highlight, though, is you on the right side, the heat map? So if you have an evaluation done, a quality gate, I can now automatically see the last twenty.

A

You think of so evaluations, I think it's even more than twenty, and what's also nice I get to see the overall score. I can click on all of these individual builds and then on the bottom. As you can see here, you see all the individual s. Allies and why this SLI actually violated or didn't violate the DSL is I think that's pretty cool. You can also switch between the heat map and the chart, which means you can actually see some historical data here and and see like how things are trending over time.

A

So this is pretty cool. Some other smaller enhancements, the key, a rich version on the bottom right, and also for problems that were detected. We add a couple of additional things like labels, so if we get a problem in, let's say from dynaTrace, we highlight you know to which particular service and version this belongs to. So we have a couple of really cool improvements.

A

Now the good news is and watch keep an eye up on, just as we did with oh six, we for the captain's bridge we always hadn't really exists like with a couple of early access iterations, so we also keep we'll keep having those. So Yemen is one of our key developers here on the front end he's been crunching out new releases, almost on a daily basis and every time there's something new. You can check it out here, Andrew. We also make the announcement on the select channel. Let me see if I missed anything easy upgrade.

A

Oh yeah, that's that was amazing. The upgrade experience big shout out to Florian, who built this smoothers experience. If you go to the documentation and if you are instinct upgrading captain, it's just an upgrade job and it just takes care of everything and so far I think we only had positive feedback. So big applause for to floor in on this easy upgrade new bridge support for mini cube, india, the documentation is a living document. Please give us feedback. I know I, see Patrick on the call today.

A

He just gave us feedback yesterday, which we directly incorporated so give us feedback, and we want to all get better all right now. I want to switch over to the next part, and this is where Henry comes in from notice before him before I give you the word. I want to quickly introduce the topic, because this is a topic that is dear to my heart, that is dear to Henry's heart and is dear to a lot of the performance architects around the world.

A

It is what we can do with Captain when it comes to performance, is a self service and I chose this deck. The the template, because Henry goes invited me to be part of PEC the performance advisory council, which happens just before the lockdown in Greece, where we talked about captain and a Salina, slow validations and I wanna just highlight for those folks that have no never thought about that particular use case.

A

First of all, the inspiration, at least from from my side, there's a couple of people that Inspira inspired us, but one of them is Mark Tomlinson, a dear friend of us, and he a couple of years ago at PayPal. He basically automated the complete performance, let's say performance process instead of running tests on demand at the end of a release, he said: I want to automate this and I want to give it to developers as a self service.

A

So he allowed people to create a JIRA ticket where they stated I want to get this particular version tested run this particular test against and then give me this particular feedback. So these are the metrics that are important. What mark then build is an automation engine. A continuous life cycle continues test environment where, on a regular basis, I think it was every 30 minutes or an hour. He picked up.

A

One of these requests then deployed that version into that environment ran the tests he was monitored and at the end of the tests he extracted the relevant metrics from the testing tool and from the monitoring tool. Put it back on the JIRA tickets of the JIRA ticket became the self-service token, and also the one where the results were received. Now this actually inspired us also to build these capability into captain.

A

So, while captain is much more than that, it's a continuous delivery and automate operations, but what I like about it is a performance engineer is that if I install captain, if I set it up, then I can basically give my developers a self-service performance, feedback, environment or self-service performance. You know offering the only thing they need to do is say: captain you, artifact. Here's in your container captain then deploys runs. Tests evaluates against mayor slice, where the SL ice can come from different data sources.

A

We will also see from Henrik later on how you can use new load for test execution and also the new load, a slide provider and at the end, as a developer or whoever initiates it. I get back the results to score based on my ax solos, whether this is by looking at the captain's bridge or whether this is by looking at the chat, because we also obviously have a chat notification. Integration all right so without further ado.

A

I want to hand it over to Henrik to show us how this is possible with Neo load, because he built a lot of great integrations from Lidl to captain. So Henrik I'm. Stopping my sharing now and you should be able to share your screen.

B

All right, Ida, perfect, all right so first before I start I'd like to a big big round of applause for the captain team, because last week, before the shutdown I think we were pretty much in good timing, because if you were this week, you were still ready to do it, but we organized our partner event sunny as his partner events in in Bordeaux was also the wine region, and we usually on our partner event.

B

We give some some awards for the best partners of the year, and this year we decided that to have a specific award for the best innovation partner of the year, the best open-source technology that has been built so obviously captain indirectly dynaTrace won that award. So I would just make a big round of applause to all the captain team for all the efforts that you have been doing the last last year. Now almost thank you to make this captain happening and all the latest news technology that has been added, because it's it's an amazing technology.

B

A

You so much Henrik and it's obviously the onlythe only reason why this works so well is because people like you also help us and drive this community by the way. Henrik I just got some feedback from Rob. If it's any way possible that you can get a little closer to the mic or maybe speak up a little bit, I can do that.

B

If it's worth is shutting down my sound or no way, is it better? It is. Thank you all right. So so, if you need one to hear more about the world, we can. We can have a chat later on, but let's keep the timing of this meeting so before we start and jump to what we've built with the within captain, so the service and yes like provider, there will be some concepts that will be used several in during my demo, so I'd like to make sure that everyone is aligned.

B

So this is the current architecture of our product, so we have a SAS product called neo load web. It could be on frame or on on a SAS, and if you are aware of low testing products, there are several components that are involved in low testing. So controller is one of them. So control is the orchestrator of the of the tests and the load. Generator is the component that will generate the load against the application, so you can have one or several load. Generators could be on the cloud you can even Prem whatever it is.

B

What Neela? What we offer is the ability to have a dynamic infrastructure where those compose are only running. One is required, and this is the real story behind captain as well.

B

So let's have first before we jump to the SLI provider, let's remind us what we have so if you want to utilize it and have a play with it in the captain country repo, there is a new load service and you will find all the readme file how to install it, how to utilize it and there's a bunch of examples that we have done with envy as well and with Rob for for webinar that we did huge, multiple, so everything once it comes to the installation.

B

The first thing you have is the requirements related to neo load. So, first, obviously it's a SAS product, so you need a subscription or a trial version, but you need something within that trial version or that subscription. You need obviously a license, make sense and similar to the the dynaTrace approach, we're going to interact with the platform through api's, so you will have to create an API token within Neola way. So I can show you briefly how you can do that in a few seconds.

B

The next also requirements is the notion of zone zone is, is a sort of a bundle of all the different components like I presented before controllers and loaders will be registered to so. In my example, I will create a captain zone and all the machines that will be spin up directly by the Neo load service will appear in that particular Network, so so to deploy those variables needs to be defined is to be filled in and once you deploy it, it will become like a community secrets and the Neo Service will utilize this.

B

Then the idea is that we are. We want to generate load so the first thing. First, you need scenarios or projects, and this you can store it. Whatever you want, you can store it in your source, control in gate lab or github. Whatever you want from the moment, captain has access to that. That's the only requirement to make the new old service run. You need to define a one of the file which is important. Is the captain new load engine file? This captain you load engine file is a yamo file.

B

You will basically define that will allow captain to understand what will be the test that will be executed. What would be the infrastructure that will be going to spin up in the in your kubernetes cluster? So you can see here. In this example, we have several steps, and there are you can define in within a step that you have different steps to Gigi and based on what you define in your deployment model.

B

The service will pick the right tests related to the stage where you are.

A

Can I ask a quick question here? Yes, so the test strategy here that also translates to the test strategy that you have in your shipyard file. So that is that correct, so you're.

C

Making correct.

A

Yes, that's perfect and folks, if you have any questions, you know feel free to use the chat window or the the Q&A feature in in some.

B

Similar as well here there's a notion: you can replace some context of the product by replacing some constant variables. This is meaningful, especially one you want to want to change the way to reach out to the service. You can replace the hostname. You can replace different variables if required. That's the first thing.

B

So what would happen is basically the captain service received, obviously an event from captain say a I've just finished a deployment so once he received that event, he will try to each out to the captain resources to grab the captain yellowed engine file that is stored in the stage and in the service resources once he had that file he has in you know, the Anila service knows where he can get the testing assets and how many machines he needs to spin up so first thing: he knows that he has to deploy, for example, two machines so he's going to deploy in the captain name space, all the components required for tests to controller and the different load unit load meters.

B

Those low generators and controllers will register automatically in your web and then the service will send over the project that you have stored somewhere in git or github. Send it in your webinar web will start the test automatically. Once the test is finished, we send back the event to captain to say that our service, the test, has been ended and then obviously you can have graph and notifications on now.

B

Since then, captain version zero, six zero and with the SLI provider we have added also the ability to define your SL ice with neo load metrics, so neo load become now. Data source has a specified provider. So if you want to also similar to this service in the captain country, repo, there's a specific folder or project for the sli butter, so please have a look. We are eager to get your feedback so the way we are this structure it's here. It's a lot of things.

B

That's right, obviously, but just to make it understand our data model. So in yellow there are a different type of metrics and I will go through. So you can have a better understanding, so global requests. Basically, we have tons of statistics on that level. Global means, n matrix that will be aligned globally to exists, so it could be hit per seconds. It could be the average response times for all the requests. It could be the throughput. It could be the success rates whatever it is, then you couldn't be more precise by saying.

B

Oh I want to grab a specific average response times for a specific request, so you can be more precise on which request you want to get that test statistics, and then you have all the dimension, so transaction has more metrics.

B

Obviously, here you can see that we have the in the bottom P 50 P, 1995, AP 99, so you when you play with transaction. Obviously you need to precise, which transaction you want to collect, that specific SLA and last is the monitoring. So any metrics that neo load has collected during a tests could be pure dynaTrace metrics. It could be pure system or a CPU memory or whatever from a system. We will have those, so you can collect the average the mean in order max as an example.

B

This will be for type of metrics that has been defined. For example, I have a cell ID I have named basic check, P 99, so it's symmetric type transaction and the statistic time I'm eager to collect is P 99 and the element name, which is the transaction name, will be basic check.

B

Then, if I go further in the example, there is another transaction example. You can see here in the element name. We have the basic check, slash, add item, so this is a way to be more precise on the filter to get that specific transaction out of your test, and last is another example where I want to collect a monitoring data and the monitoring metrics that I want to collect is from dynaTrace data source catalog, which is the name of service and the process and total city usage.

B

So it's very simple for those who wants to define that you? Basically we follow a bit our UI, so you can just look at you I how the data is structured and you will be able to go rebuild the definition of any of them, our metrics, that we were collecting all right. So, let's demo time so here, what we have is a kubernetes cluster running on GTE I have done a trace or installed. I have, of course, Neola will be involved with neots s.

B

Captain is ever is there and he's have access to a specific repo, and here I have a two-stage, so staging and prod with andis app. This simple node application as an example and everything is in da crap, so like I mentioned here, is the app. So we have just built released. I'm gonna remove this, because it's locking me to access to the curious.

B

So here this is the app I'm referring to staging on the right on the left and prod on. It should be further on there on the right and what I'm going to show. You is first go to new web so that the requirements that I mentioned before is the token. So this is the near the web UI and to get a token you have to go to your profile in your profile.

B

You can add, there's an access token, so you'll be able to generate a fresh new token from out to that, and this will be required to deploy your service. The second second thing, which is required here, is the zone. So here I have created its dedicated captain zone, where all the machines that the service will spin up will be a register in that specific bundle all right. So if here, let's run a few small tests, I have I'm gonna, send just a new artifact event: I'm gonna deploy the 100, for example. Here is so now.

B

I have connected slack integrations here. You can see that captain is sending me different notifications, while I'm going through and the testable ID or the URL, or the test will appear here. So it's really made for the theme or the the performance has a self service that Andy just presented where you don't have to be aware or anything captain and will do the job spin up. The infrastructure will do everything. So it's quite convenient. You don't have to acts any extra test tasks to the shoulders of your team. So let's have a look.

B

First, on the how to build scenarios, so in yellowed there is the GUI. So this is the traditional GUI. You usually use the GUI to do end-to-end testing. You can record from the browser from a say, PE from Citrix and Bill your scenario, and that will be available here, and this is the main thing. So we have a notion of user path, which is the scripts, and we have several notions so variables.

B

You can define file variables, constant variables, random variables and so on, and then you can define populations and the tests that will utilize those populations. In my example, I'm not using any design in this GUI and using the design directly from another format of defining our test, which is the llamo description language we have so the amo description language is a text format and you can define whatever you want, so here, I'm, defining some bunch of variables for that specific service and then I'm defining to user path.

B

So senarios, quite I have a basic check whether I'm just doing a get request in my example and I have a simple load that do several transactions to go through different areas of the application. So that's on the design perspective. Once you have define your design. The only thing you have to do that can mention before is create a captain new load engine file and this we need to be added as a resource in your service and in the stage at whether we're performance will be involved. So this is a staging captain.

B

Engine file, I am precising where and the service will be able to grab that specific file which branch and then how I hear how the service kind of build the project. So you can combine a simple Yama file, a good traditional Greek project, which is this one or both of them. So you can. There is lots of combination possible and to build your project out for that, then you define which tests you want to do so here it's gonna, be a simple load and the infrastructure was required. You can here see here.

B

I just had a notification. The tests that we just launched through me through captain has just started so I just have the notification, so I I can jump back to these dashboards and if I refresh you can see that now, I have two machines that has been spin up by captain automatically and if I go to home here you will see that the chest is currently running.

B

It seems that there's a lot of errors, but the test is obviously the captain's simple project for staging, so he will do the tests and once this is finished, obviously we will have the indicators back in the in the light to house, and the evaluation will happen so I've already hadn't done some hue test before we before this community meeting. You can see that from the new caption bridge. We have several events that happen here and what I'm looking for is the evaluation.

B

So here you can see that SLI done and it's your load service has retrieve those SL eyes and I can see here from the captain bridge that we have several metrics average response times. P 95, throughput and similar to what Andy presented I will be able to look deeply on the heap map on the charts. So all the metrics that will collect could be basically collected through captain and you can put your own objectives out of that.

B

So yeah, basically I, think I wanted to give you another view of what we have done, and you can see that from the model of defining your SL eyes, you can be very flexible and grab any type of metrics. Just one short thing before I leave it back to Andy is how you can define the how to collect metrics here in this dashboard. I can create a new graph, and here you can see that there is a specific node.

B

So if I want to grab, for example, the transaction called homepage, which is here and I want a p95 I will basically type homepage in the field in the definition of my SLI. So here the the property I'm referring to is the element name, which would be homepage in our example, so very flexible. Like I said, if you look at the UI in the way the data structure, you can easily a query back all our metrics, so it's yeah, it's up to you, I, try it out and we are eager to get your feedback yeah.

A

Hey Henrik there's a couple of questions that just came in also something that I wanted to quickly raise. I just had a conversation earlier today with an organization and they say they're still doing traditional testing and they are used to look at them. Build dashboards and figure out which metrics make sense, and they ask me how can they get from this stage to taking some of these metrics and then putting it into SLI so that they can automatically get created and I? Think you just nailed it because you said you can run your tests.

A

You know let that captain already trigger the tests. Maybe you don't add metrics to the slis, because you don't know so. You can actually first go into new load creator, dashboards figure out, what's important for you and if you find metrics that are important for you just start one by one taking them over to the SLI so that the next time you run a test. You don't have to look at these dashboards anymore because to get automatically validated thanks to the quality it exactly.

B

And, like I said all the metrics that you can see in our screen could be queried by the SLI provider here. So if you play with clicking the Andy mansion, if you start looking at dashboards in our product, you can easily then translate those metrics as an SLI in the SLI definition.

C

A

Really cool I have a couple of more questions that just came in, but I also wanna just highlight so the beauty of captain and the event-driven model allowed you to just write a Kip. A new load service in the noodle SLI provide her so with that extending the tool set of captain without having to change anything from the process. So that means, if I would have started with the captain, installation and I wouldn't have had near load. Maybe I didn't have any testing.

A

Well, maybe I would have had, let's say Qi meter and I then wanted to switch over to notice. The beauty is with captain I. Don't need to change any of my process. Definition, which is in the shipyard I just need to install, in your case, the cap at the new to service. That is then listening to these test events and then running the tests.

A

So I think this is also great to see that that really, the reason why we, one of the reasons why we built captain the way we built it, is to decouple the process definition in the tools. Everything is event-driven and you've just shown how you have extended captain with captain services for both triggering actions, but also providing data and I think that's pretty cool the other thing, because this also comes up a lot and you know the two of us. We are performance engineers and we've done this a lot, but help me understand your cap.

A

New load service is really on demand. Creating all the load testing infrastructure in that kubernetes cluster, then registering them on your sales platform and then the sales platform, basically working straight to test itself, and at the end, when the test is done, the results are in the sales platform. That means the results are not lost somewhere or scattered. Around some load. Generators they're, all centrally stored and I can always go back in history is correct. This is correct and the URL each.

B

Test is also sent in the event, so, if so, like you said, we met there, the service manage the infrastructure, so.

C

B

Don't have to worry about installing several load generators. You will just have to define that you need four machines for your tests and you know that will do the magic for you.

C

B

The data is stored in, like you said in ours, in our SAS or on Prem, and like I said here, you can see that the link to the Porsche lady to attest is pea part of the event, so you can still jump back easily to our dashboards from a link or if you use the slack notification, you will receive those links, so you can simply have to click on the link to jump back direct to the dashboard. So it's a real performance as all service.

B

How you be described just have to fire a new artifact I. Don't have to worry about anything and if I want to look at metrics I can click on the stock channel and and I'm free, and this is the spirit and how we we wanted to take advantage of captain for.

A

Sure mm-hmm- and this might be a topic for one of the upcoming developer, meetups or meetings that we have. But can you quickly go once more back to the bridge yup, the bridge that is open here and can you do me a favor and explain the test finished.

A

The other Jason I'll test finished that you had earlier. So would what the freedom that we give you as a captain service implementer you can then, when you're done like in this case, st. big labels yeah, it's love to sweat, so labels, and they also showed up in the UI up there.

A

But it's basically a way for tools to add context to the cloud native events that we have here and I believe these labels are then also passed through because I assume your test study here is then getting passed all the way through by Captain to the SLI provider, which is then your provider, and then you can directly reference back to that test. Eddie correct the.

B

Provider is expecting that labels yeah, because the the central I would say primary key to gets the results is the test ID so in the the SLI provider expect and this this ID to be able to retrieve the s wise proper properly. So that's that's the secret sauce between behind captain for sure. That's.

A

Awesome cool, hey.

C

Guys this is Jurgen. We also got a couple of questions here in the in the chat, so I wanted to ask them. You showed this lack integration and there were also some graphs where like how to to get them. Yes, this part is this part of the captain slack integration, or is this the part of the Neo integration how to build? It's part of the Neo load.

B

Integration, so so no, the the traditional captain, slack notification won't receive that graph. It's going to be part of the new load stuck information. You.

C

Can have in the same channel right so everything is is basically together, so you can. You can directly see afterwards the tests are finished and you can then see like the the condensed version of captain. If the tests have passed or yeah, we can see hey.

A

You can this would be a great challenge for swipe and extending his captain's, like pot, so that he also visualizes the they call a decayed history, exactly yeah. That's.

C

Cool yeah, that's a cool use case, but because I like this very, very much vertical.

A

C

All sort of in the chat that people are referring to this and another question that was coming in how to best get started for the for someone that wants to kind of to try this new load integration. Do you have something like developer license is because you said in the beginning that there are you have to bring your license for new load. Is there some prettier? Can people get started really easily here so.

B

We have a free, freemium program, so you have to register. You have 30 days license with your and also access to the SAS, so I would definitely start by doing a trial. So you have all the the requirement expected requirement to be able to try captain, and then there are several repo where so, I didn't change the readme file from Andy's captain example.

B

Repo I have to do it, that's part of my job, but we did a webinar with Rob a few few months back and we added lots of in descriptions in in that repo, so the readme file is really well described. So if you want to have a look at it, I would definitely recommend to have a look at its just lost link to be honest, I'm looking at it. That should not be, but it's a captain order. Basically, there is a captain order.

B

A repo and I can share the link later on and the readme file, there's a specific branch for new load and all the step-by-step how to deploy. What are the command to add resources in the writes? As for the service for the stage everything, so basically, if you want to start with the captain order application that could be good starters, pretty.

C

Cool thank you. So we will add the link then, to the captain community meeting notes and then people can just find a link. There.

A

Alright, can I quickly take over control again, sir, all right so Hendrik. Thank you great great contribution and definitely helping our users to get closer to performances. A self-service links are also to the providers. These Nilo service and ESL a provider are in the Capon community deck. As you can see, you're going to believe you wanted to give a little outlook on what's coming next.

C

Yes, thanks Andy, so demanding kind of fun from the community and also to work a little bit more with the developer community. We are starting out with March 26 without first caps and develop meeting. That really means we are inviting all caps and developers to bring their questions. So it's a very interactive meeting. There won't be a lot of presentations from the captain team.

C

It's more that we are hoping for questions from the community and we already see a lot of questions in the captain's life channel, but we also want to open up the discussion so that you can directly interact with other captain developers and also learn best practices from the captain core development team. They will be in the captain developer meetings in the first meeting. Actually, we already have to plan to show how to write your own captain service. So today we had Henry a couple of weeks ago.

C

We had so high that they did already the job of writing their first captain service and they know how to do this, but we also want to showcase this to you. We still have to figure out like which program bring programming language we take as the weapon of our choice. So if you have any suggestions- just let us know in the captain slack channel and then in on March 26. This will be like the first meeting, where all the developers come together and talk about how to write the captain service.

C

What is needed, how to consume a cloud event? How is the workflow and we will be there and answer all the questions? This is also part of the captain community meeting calendar so and if you can do me a favor and go to captain Sh, we have a link on the very top that brings you to the community meeting or community page we'll find the calendar and also yes, there is a public calendar from Google and also the iCal formats.

C

You can add this to your calendars, like Outlook or Google Calendar, whatever you're using and we've also now added here. The next upcoming editions of the community meetings and the developer meetings, so it will be one week will be a community meeting. The other week will be the developer meeting. So we keep the two week cadence for the community meetings, if you're more interested to see like what the community is building. What are the new features of captain?

C

You can just stick to the community meetings if you want to more interact with the captain, develop a team and other developers. If you want to get more like technical insights into captain, then please also join the captain developer meetings. So we have all the dates here and they are also in the calendar and it will be the same soon meeting. So if you just if you already have the zoom meeting as a bookmark, you can just join us here. It will be the same webinar and we will also use the same YouTube integration and.

A

I think what we should ask people to really now: click on the add to calendar. That would be erection item. So it isn't.

C

A

And you get your invite getting notifications, so that's the way you never miss one.

C

From my side, yeah.

A

Last thing I want to say right after this in 20 minutes, I'm jumping over to test Buster's Vienna, it's a meet-up from Vienna, but we're doing it remotely we're also going to show captain a Celina, Silla validation in action and right after it I completely forgot about this to edit here. But we at nine o'clock European time, 4:00 p.m. in u.s. East a Louis red power. He starts a new thing that he calls DevOps and wine online meet up, so I know Henry.

A

You said you're going to join and I believe he is also ok with. If we have beer, not only wine but he's a wine lover, a Louis and and.

C

A

This is all about it's about the casual conversation. You know drinking a good glass of whatever and and having a conversation about DevOps. Not necessarily can you know the I think the discussion can go off, no also its, but I wanted to give a quick shout out here all right and with that I want to say thanks again, you can I'll stop the recording now so, hopefully they the recording on the cloud works and then we can upload it to YouTube later on yeah.

A

Thank you, bye-bye. Everyone.