 Okay, let's get started Welcome everyone to today's CNCF webinar vanilla stack as a per as a platform for a truly bendered agnostic open-source ecosystem I'm Jerry Fallon and I'll be moderating today's webinar. We would like to welcome our presenter today Karsten Shemashke CEO at Clotical Just a few housekeeping items before we get started during the webinar. You are not able to talk as an attendee There is a Q&A box at the bottom of your screen. So please feel free to drop your questions in there And we'll get to as many as we can at the end This is an official webinar of the CNCF and as such is subject to the CNCF code of conduct Please do not add anything to the chat or questions. I would be in violation of the code of conduct Please be respectful of your fellow participants and presenters Please also note that the recording and slides will be posted later today to the CNCF webinar page at cncf.io Slash webinars and with that I'll hand it over to our presenter for today's webinar. Thanks Sorry, sorry, Gary was my fault here a little bit confused with the slides and with the screen controls But I hope it works now Good morning Good evening wherever you are and welcome to this presentation. I want to give you some insights into Vanilla stack what it is all about and basically I want to do that from and not obviously not a sales perspective But more from a community perspective Initially, I'm going to give you a little insight into what vanilla stack is actually all about then I'm going to showcase you Some aspects of vanilla stakes specifically on the installer because we feel like that is very important And then I'm going to touch on why it is important from our perspective to the community Why we and where we position that for a community and how we are going to proceed with that As Gary already mentioned Know down all your questions. We will answer them later on and in the end So from my perspective, let's get started first of all, let's talk a little bit about what is currently going on outside our daily environment outside our World in that regard and so to say But we are basically confronted with a lot of requirements from our stakeholders when we are talking about and thinking about IT greater flexibility in infrastructure faster deployments Faster reactions better scalability 24-7 availability automation governance and so on so forth, you know all of that and you know The caveat dot all of that is expected at lower costs obviously and why shouldn't it be different in that regard so What we need to to talk about and what we need to focus about ultimately is how to proceed from there and how to handle that and that is basically part of the the situation and part of the positioning of vanilla stack where we basically Started when we talked about vanilla stack because I'm pretty much all of the customers our company and our organization and pretty much everywhere They are basically saying okay, let's do cloud and we totally accept that because it is obviously The thing of the future and the thing for the future Nonetheless Cloud is not per se the answer. There are different flavors to that and let me touch on them very shortly I don't want to bore you, but again, I feel like that is pretty important there. So Cloud is most often perceived as something where you do some lift and shifting where you basically set up some infrastructures and deploy things problem with is if you do that Well, let me put it that way. You won't be able to gather all of the advantages of a cloud environment You might save some money or might actually not basically depending on your workload and basically depending on what you are doing So quite often the next logical step beyond lift and shift to most and if not all of the companies we are talking to is basically Heading over to containers. So when we talk about containers, they are perceived as basically Solution to all problems, but are they actually solving all of the problems? Let me put it that way with containers. You would basically be able to To to virtualize to some extent your workloads. It's a way Less invasive kind of virtualization in a traditional virtualization. It's more lightweight But that again brings new challenges because on the same infrastructure where you would have been able to run say dozens of virtual machines in the past you would now be able to run hundreds of Containers, but those containers need to be orchestrated and that imposes real challenge in that kind of remove to the cloud approach because those containers Need to be orchestrated by a container orchestrator We just ran over those and we just finished those container wars Kubernetes was the winner and Kubernetes is basically the Container orchestrator now. It's an open source project. You know about that It provides us with the opportunity to have some self-healing services to have automatic load management. It's Implemented with security by design. It's 100% open source and there is a huge ever-growing community Behind it that is awesome That is actually so awesome that according to a study of four or five one research group just conducted some weeks ago 76% of all enterprises plan to move towards Kubernetes over the next three years Problem is Kubernetes alone is then again, not the final answers because to that open source Ecosystem based on communities. There are again a lot of challenges and post because Basically, we are confronted with an environment where proprietary solutions are pushed with huge sums of a huge amount of money Because that is the market of the future and even if you don't want to hand over Hand over your luck or your future towards proprietary solutions, which is highly welcome You would be confronted with a lot of Integrational efforts for your open source project It is very very important to keep in mind that Kubernetes alone is not a solution to your answers It's just a building block. It's a very fundamental building block But it is just a building block So you have to integrate a lot of things onto your Kubernetes classes say storage operational tools and so on so forth and Then you would just have your start it would not even be done Then there is one thing which troubles me personally a lot and that is The vendor lock that is even post on top of open source solutions So if you look on to some of the products provided by the biggest open source Windows in the market, I don't want to say the names of those red and green Companies they impose a vendor lock on you as well because you just can run their Kubernetes solutions on top of their Linux's Coupled with their storage solution. That is the classical definition of a vendor lock the next challenge is that vanilla projects are often understood by stakeholders as not ready for prime time and then Ecosystem what ecosystem so with Open source projects in the market competing with proprietary and vendor lock solutions You have a problem in regards to an ecosystem because there is no such thing as a real and true ecosystem It's just single products that are basically waiting for you to be integrated So a lot of work for you a lot of efforts for you requiring a lot of knowledge and ultimately I'm making it quite expensive to Hand over to those open source Ecosystems that is basically the situation that we find ourselves in today and that is why Something as vanilla stack is now there again. I don't Want you to touch the commercial aspects here. So I'm just giving you a short overview of vanilla stick vanilla stack is an open source Enterprise cloud stack We basically try to combine both things. We understand Kubernetes as our operating system. This is very important to keep in mind. Remember the vendor lock We try to solve that by basically not caring about which Linux you are running your vanilla stack upon vanilla stack is Vanilla Kubernetes. We don't touch it. We just roll it out vanilla stack is Vanilla cloud foundry. We don't touch it. We just roll it out in an opinionated way Vanilla stack is Vanilla open stack. We don't touch it. We just roll it out in an opinionated way Vanilla stack is Rook Vanilla Rook we don't touch it We just roll it out in an opinionated way and we understand ourselves as an organization that is able To to make that available as a community project and that project is a truly open-source project because what we wrote out With vanilla stick and I'm going to showcase you the vanilla installer in a few seconds What we wrote out there is 100% Open source projects and it's not those vendor locked or vendor locking projects You might be seeing from other platforms. It is the vanilla edition of the project So of the projects so that is actually where the name came from. We did not want to alter Kubernetes We do not want to alter OpenStack. We do not want to alter anything there We just take it we integrate it and we roll it out in a way that you would be able to run for example Your open stack on top of Kubernetes within an hour Basically obviously depending on the strength of your ecosystem and of your infrastructure, but that is basically What we promise you? Vanilla stack is made by the community for the community. So we Position that as something that supports the community. I'm going to touch on that in a few seconds as well And we don't impose any vendor lock Vanilla stack which is currently available in its very first iteration Will have in its final iteration Basically, I will present you with an ecosystem that is giving you the whole Complete picture. So it is a complete open source deck period What you roll out with vanilla stack with the installer and with the store is open source We will later on have commercial products in there as well, but we will always focus on the open source Versions of the products. We will always make them available And if there is then later on some commercial offering us on top of that, well, we need to refine the project any house So it is based on Kubernetes. We support docker and Creo Istio, Rook and Seth for your storage purposes We have an integration with net at Trident currently running in beta Which will be available in next edition the Lero for your backup I don't want to touch all the projects here pretty importantly Open stack as infrastructure as a services layer with the next iteration Being available in one month from now. We will also have Support for Qtvert in there. It is based on Ansible and Terraform We provide you already in the current version with cloud foundry in the next editions We will also have support for GitLab and Jenkins. We always ship it with hover For your operational approaches Prometheus kafana the F stack Yeager will be there and are actually there Security is done by the likes of key club flaco aqua Claire and then vanilla installer and vanilla app store I'm going again to touch them in a few seconds. They are also part of the stack and they are also open source So that is basically The complete stack and it's not done there because from our perspective That is just the beginning. First of all, let me Touch again on the promises that the community and open source version already gives Components are rolled out automatically. The initial installation is done by a vanilla installer to bring in additional functionality By the so-called vanilla store and we promise you again in the open source version and let me be very clear on that The community edition does not differ in any kind from the commercial edition there Out of all the box integration and out of the box Operability so whatever you roll out something with vanilla stick you can rest assured it just works and it is again Not any kind of vendor locks product. It is not. I don't know the Kubernetes running with Microsoft AKS or the Amazon version It is the Kubernetes we roll out But we want to go a little bit further than that. We do not just want to provide you with a platform We want to set up and start something like an ecosystem in the end and we mean it in that way It should be an open source ecosystem So the ecosystem and the platform are open by design and mindset. We support vanilla projects We won't provide any kind of window lock It can be expanded with a huge amount of open source and commercial components and again We understand it as an ecosystem. So what we will provide you and what we will provide The community with is a complete trust worthy environment with 100% open source components Which is 100% supported by us and obviously by the community and which is open sourced on its own You might ask where vanilla stack is able to run Well, let me be very clear on that it runs everywhere It runs on everything starting from bare middle environments via my hands Public private clouds up to the hyperscalers. It runs everywhere and now I'm going to showcase you How simple it is to set up something with one elastic installer for the purposes of basically This webinar given that we don't have the time to actually roll out something I'm going to do that in a dry run, but rest assured it runs the same way In a real Environment in a real ecosystem. So now My virtual machine should be visible I Should have changed the screen Sharing accordingly. Let me recheck that again yet. Yes, it should be so here you see basically The starting screen of vanilla stick vanilla stick installer is just a docker image. It's available today There's also an iso image available So there's ideally no need for you to install anything on your local machine perhaps besides a docker image or mounting the iso image to your virtual machine software and then basically start it up We currently That that thing I'm going to showcase you now is still based on the previous version this evening It will be changed to be the version 29 Dot own 20 20 dot o nine And the first Selection you have to do in the first choice you have to make is basically do you want to have an h a installation or not? Just make your choice there. If it is an h a installation, we will set up three master nodes if it is A non-h a installation We will just set up one master node and then you basically define your initial workloads. Keep in mind You can always change that later on you can always add things later on we start always with rook as As your storage solution currently you cannot deselect rook That is by intent because we want Your covenetus installation always to be in a production grade state Cloudical my company is amongst the biggest root contributors on this planet. So we love that project We understand it and we are able to roll it out Additionally, you can decide whether to install open stack here as well as whether to instake cloud foundry if you like And you can then basically select the amount of master nodes you want to have Vanilla stack be rolled out with this can then again later on be expanded The minimum amount of worker nodes is three. You can basically go up up to like 90 95 If you liked it, but I would not recommend that So we keep it for the purpose of this demonstration pretty short and just with three worker nodes And now is the only moment where you would need to touch a terminal during the installation because the installer creates An ssh key it uses a private key and asks you to deploy the public key Onto your worker and master nodes. So once you did that and how it is done is describe within the installer as well you just accept or you just Say that you did that press next and then You can basically go and Define your master and your worker nodes Again, I'm just doing a presentation. So basically I can use any kind of random ip address I want to use because in this presentation nothing is going to be rolled out So I just add some ip addresses I do the same for my workers I today did that already like five times on a real environment with real ip addresses and I can show you Um, once you defined your master and worker nodes You can basically define and basically Make your selection, uh, which workload will be available on which Worker node If you have more than three workers, it makes obviously sense to basically say, okay on which worker would I want to have? My rook deployed because you might have fast SSDs there Here in this case, you basically say, okay, I assign hook opens they can call fondly whatever you want to roll out To all of the nodes now the next step is basically Already a step that is working with your infrastructure because now you need to do a node check So this node check is basically connecting to your nodes It is basically Checking and whether you have enough ram A minimum of two gigabytes should be there That way you have enough cpus. We would recommend a minimum of two vcpus And whether you have enough storage or disk space like 20 gigabytes should do perfectly fine And for the rook nodes, whether you already have a raw device provisioned if not Um, you find the appropriate information here so you can then provision your raw devices for work Once you successfully Validated your nodes you can press the next button and now We actually are approaching the cluster settings. So you can basically Either use an external load balancer or a cluster ip or Perhaps even the ip address of your first Or perhaps only master as you like and then you would basically Give Your cluster a domain name So we might call it here demo dot vanilla stack dot arc And this domain name is the later on used For basically all the components being exposed to the outside world automatically. So you just have to do The prefixing thing and we pre-propolate that With useful values Manila state then again is always is already coming Integrated with let's encrypt you can basically choose whether you want to have let's encrypt in staging or non production production mode or in production mode You would always recommend for any kind of test clusters your staging mode, although it might to as a certificate issues you need to give a Proper email address for let's encrypt to be able to communicate to you And then you would go and do Your basic settings for your workloads you want to roll out So for root for example, if you want to have the root dashboard being exposed. Well, just press That option and enable that option the same is true for monitoring You can basically find how many replica levels would be there for root Basically, how often is the data replicated on sef three times is the default you can go down to two and you can go up to five According to your needs and according To the power of your infrastructure the higher the number the slower it gets then you have to Basically do your open stack settings. We support three open stack releases again the open source releases there Not any kind of vendor locked ones And then you would basically be able to do some some basic settings for your open stack components So we pre-populated them those settings again You could just leave them or you could basically adjust them To your name to your needs the same is true for cloud foundry We always ship it with the stratus dashboard So you always would have some sort of nice little Web front end and then basically comes the additional tool selection to be rolled out initially Harbour is pretty important to us because we feel like it makes a lot of sense to have your own Docker registry available. So harbour is already pre-selected the same is true for pomeatrous and kafana You can basically pretty easily select the whole elastic stack. You can install jager tracing We always rely on engine x ingress We always install with a community desert manager and we give you the option to install a community dashboard as well Once you did your selection here You'll be you are presented with a summary You can always jump back to the different sections here by pressing the edit link But once you are satisfied just press the install button and then the installation might start that is just again Not a real installation now going on here. It's just a dry run So we can wait for a very short time In again in reality, it takes like an hour Depending on your workloads your rollout and depending on your network connection Before your installation is done here. It is done in a few seconds And you would then basically see the final screen With your open stack basic password with your cloud foundry password You can download your kubectl config You can show your locks. You can download your locks and then you are done. That is basically the Pretty rough view on the installer Again, that installer is available today with everything we do internally as open source So you can basically use your vanilla stack For several use cases right away For infrastructure as a services with open stack count with rook We you can later on install it via the app store once that one is available and be checked it It's able to run to be rolled out and operational within 40 minutes at best although my colleague Basically claimed he can do that in less than 30 minutes with vanilla stack And another or a different use case would be platform as a services On vanilla stack where you would basically roll out Kubernetes harbour rook GitLab Jenkins cloud foundry currently just cloud foundry On the environment Istio and GitLab and Jenkins will be there with The store again in like two to four weeks. It will be there We recommend to have a decent setup there. The same is true for ops You can basically roll out per meter as kafana f or xx Rook and set for storage And everything will be rolled out and directly usable The most important aspect in that and we are in the cncf webinar is the community and that is very very important to us We don't want to just have a classical based product So we understand vanilla stack as a community project. First of all, it is open source Head over to vanilla stack i o or head over to vanilla stack dot arc And you would be able to Basically use vanilla stack now download it now You can see the resources they are available now But we want to go a little step further first of all Again, the open source or the sources are available now It is available under Apache 2.0 license So you can basically use it and Work with it as you like It is open to community contributors now And we are actually and currently reaching out to many Linux foundation and cloud native foundation projects already have some interesting conversations there because we invite all of you And to Participate in that It is a completely open system and we want to make it even more open That's why we want to hand it over to a newly formed foundation in q1 next year It's basically depending on some formal stuff and some Legal Stuff there, but we don't want this thing We don't want vanilla stack to be just something for claudical for my company And to be just the next window locked kind of thing We want it to be open. We will donate it to the community and pretty importantly to us It is available now, and it is available today In two versions the community version and the commercial version And you might ask but a difference between both of those versions is there is actually just one Singular difference the community the community version is a rolling release pretty much similar to fedora, for example Or to open Susan tumbleweed Whereas the commercial version is a more stable version in regards to that. We basically Have a little If you are a little bit slower in publishing things there Um Other than that you can do whatever you want to do with the community version It is again open source the same is true for the for the commercial version. It just uses a different repository And ultimately you can Basically use the community version for any kind of production grade workloads We give you a there. There's a there's a support option there called expert call You will find more information on that from tomorrow on our homepage That basically gives you support for vanilla steak as well as every workload you run on top of a community version as well as your linux installation That is done on a per incident basis, but you can basically have that kind of support even for the community versions There are other support versions for the commercial or support options for the commercial versions available but basically Just take the community version work with that be happy and Just use it Use it to build up your own ecosystem We are highly highly into that Vanilla installer is available today. The same is true for the forums The same is true for the beginning of the documentation always the Achilles heel of open source projects We know that we are no better than other projects in that regard and again commercial support is available From today as well the road map, which might be of interest to you as well Vanilla steak road map we today And I speak of today support fedora and wuntu So you can basically roll it out on those platforms if you would mind wait just two more days You would be able to roll it out on deviant centers or open suzer as well Um, so what we basically want to achieve and what is very important to us in that regard is That vanilla steak is not limiting you in everything in anything. We basically run on any modern linux distribution on pretty much any environment With commercial access we will support rel and slash in october this year There will be a separate announcement and we will provide another tool to the community In november that is the so-called remote installer Which prevents you from even having to download an iso image or a docker image because it's basically completely web based And there will be a so-called cloud installer which basically provisions your Azure aws or google cloud environments for you and rolls it out there available from december as well, so I know that was quite run if you want to learn more want to understand more Head over to vanilla steak dot i o that is basically the home page up to the commercial edition The community is on links to the community staff are available from vanilla steak dot arc And we would happily share and spread the word if you and we would basically Want to do that using the hashtag vanilla steak and I'm now stopping my presentation because I need to take a short Break I just need to Breathe I just wanted to give you that insight into vanilla steak Well, thank you very much karson for a wonderful presentation Um, thank you. I have plenty of time for questions at all. So if anybody has any questions They'd like to ask Please feel free to drop them into the q&a box and we'll get to as many as we can Could you elaborate a bit on open stack? I can do that. Um, perhaps you want to understand a little bit more I'm not sure into which direction your question Is heading but Let me first of all give you Perhaps an understanding Of which open stack version you support. We basically support open stack helm So we use the helmed version of open stack roll it out on top of vanilla steak on top of cuba didis And ultimately Give you with vanilla stack Then the option to Finally just have your infrastructure as a services environment there again. It's a community open stack So it's with neutron. It's with uh mist trial. It's with all the great open stack projects although And that is a small caveat at this moment since open stack provides you with like Three quadrillion Different opportunities and setups We are opinionated in that way. So the open stack installation Is basically open stack helm again three different Editions are currently available starting with Now I need to look it up for myself. Thank you for that Starting with Give me a second train stein and usui. Um, exactly We would recommend setting it up On the stein release because that's the currently most stable version But again, um, also the more modern versions are available there In regards to open stack and in regards to the other projects one pretty important aspect is we cannot go And provide you with always the newest version when they come out Obviously, we need to uh, basically Adjust our installation Scripts we need to install uh, perhaps the installer on its own So we basically plan to be um with kubernetes a maximum of half a year behind the major We usually tend to do that in one or two months, but Basically maximum half a year Later and with open stack it could be up to a year depending on the compatibility depending on the underlying Pre-requisites, um, that is part of the truth there as well If you have more questions on open stack, let me put it that way Um We could provide you with those. Uh, if you would read the fifth detail really detailed answers to that if you would reach out I don't want to to uh, I don't know Is it called a grab your email addresses or whatever? It's not about that, but we have the experts there Um, so we can give you any answer you like Um, again, it's open stack helm. It's the open source version. Um, it provides a minimum of free worker nodes You should have plenty of ram. You should plenty. You should have plenty of storage. You should have plenty of cpu's But yeah, that's true for every kind of open stack environment. It runs perfectly on top of kubernetes. That is what I can say um In regards to open stack Does it answer your question or do you want to know a little bit more or want to want me to elaborate into a different direction? Please Ask that in in the q&a as well Anyone have anything further they would like to ask we have plenty of time folks There is oh, pardon me, uh, gary you need to to accept that question pardon me that I just wanted to answer it or early right away Will you support off-site installations? Yeah, that is a good question. Um, um, well, um, yes, um over time We are actually working on that at the moment offset installation basically have the Uh, I'll give you the the the challenge of not being able to download stuff From the official repositories anywhere because you don't have any kind of internet connection um We are working on that and we will provide you with support on that But I cannot give you an exact time frame on that because There's a lot of challenge With that but let me put it that way We are actively working on that and we expect to have a solution there Until the end of this year There's a lot of challenge with that Frankly because you have to have all the images downloaded onto some sort of a local medium That is basically to be done other than that We are able to then support So we are working on that the team the awesome team is working on it Frankly, let me be very clear on that vanilla stack is on our end a community project as well. So on our team They are all working in their spare time on vanilla stack We have some full-time employees working on it But the other part of the team and the the more enthusiastic part of the team Is actually working in its spare time on it So kudos to the team because that project would not have been possible Without their support. I just want to mention it there Anyone else? I was too fast Okay Gary What do you think shall we wrap up? Yeah, no one has any more questions here at all. We'll um, we'll we'll wrap this up Um, we'd like to thank everybody for attending today and thanks to karson for a wonderful presentation Um, as I said before today's presentation will be on the cncf webinar page at cncf.io Slash webinars. Thank you all again for attending. Stay safe. Take care and we'll see you all next time Thank you. Bye