 Hello, so as I said, I have been maintaining OpenStack since it existed in 2001 It says this is a lot piece of software to package in Debian I was surprised on the bits from the DPL to find out I was one of the fifth uploader last year And I've been doing Hosting us For a long time and I currently work for a info maniac, which is a gold sponsor of the event and it's also the first hosting company in Switzerland, so This This talk is Kind of an answer. I'm doing to what I've been hearing from the FSF So I hope even if John Sullivan is not here in the room that I'll be heard So It addresses to everyone that potentially needs hosting Because there's a trend of going to the cloud and I'll explain why this is happening So there's multiple types of clouds. There's infrastructure as a service platform as a service Software as a service and on this talk, I'm not going to address software as a service I just hope to lift the confusion that there is currently about that So this is all about having on demand VMs on on from a service provider Like most of us in the room and in Debian in general I also believe that we should never use software as a service Because you're not in the control of the software you're using then Nevertheless We still need Hosting services for all sorts of types of services like ticketing shops banking news content wiki media or or gaming whatnot So People have been using Dedicated servers and shared hosting for a long long time and then Slowly it's shifting to what we call infrastructure as a service for multiple reasons One of them is cost control because as time passes using the cloud is getting cheaper and cheaper and Your services can grow in an infrastructure as a service Provider as your services growing and if you are smart enough you can even do auto scaling meaning that You will automatically do provisioning of VMs inside the Infrastructure as a service whenever there is more demand on your web server for example, but that's not it people start using the cloud because Setting up the traditional way on dedicated server just takes too long and it's too complicated Like you would install the operating system with the Debian installer manually using a KVM and then Apache and then all your services one by one That that's too slow to do it and that's not the way people are doing these days I've I've met a company which is called Scale 5 in Paris in Champs Elysees. They do only infrastructure as code. So what what does that mean? It means that? to be able to do a deployment they do The right scripts using Terraform so Terraform will do the provisioning of your VMs and then It all deploys automatically and anything they have to do on their virtual infrastructure is implemented through programming and So you would use something like Terraform first that would maybe create your in vain inventory file and then it will go to Then later on you can use either a puppet or and Siebel and It will most of the time leverage More advanced service like that abasers service DNS as a service Load balancing as a service so that you don't need to implement it on your own deployment You just use whatever the the provider is giving to you so More and more company are switching to that kind of model to deploy hosted services and It's becoming the only scalable way to do things yet At the FSF I I saw Richard Stallman joining the Debian cloud list Back in 2013 so you see that that's a long time ago and He wrote Please do not talk about cloud so His idea is that just saying cloud is too much of a general term To describe something and we would better use more specific terms So, okay, I can somehow agree with that and yet That's the campaign from the FSA FSE. So What cloud are they talking about here? Is it software as a service? We don't know, right? Are they talking about? proprietary clouds like AWS. We don't know either. It's just general. It's cloud So it's exactly what Richard Stallman has been saying to us that we should not use the cloud and then they use it for the campaign and So On top of that so like the word cloud computing comes from infrastructure as a service and then People having have been saying I'm putting something in the cloud that's because we do have infrastructure as a service and Software on top of that that we say that So the word cloud does have meaning and and we should take care how to use it I agree, but we should not just dismiss cloud and say that it's a bad thing in general Anyway, this will not work like people are going to continue to do the cloud because as I said previously that's an efficient way to to go online and Then I have a slide I heard So I listened to a Benjamin Benjamin Mako Hila. Sorry. I'm not seeing it quite way and having his talk at Libre planet and I was a bit shocked by his message So I'm I'm going to make you listen to it It's going to be a little bit tricky because I have no sound on my my computer So I use my phone and the computer at the same time a big new successful projects are either software phones and embedded systems things like Android I Lots of things that are sort of cloud services base You can think of open stack or kubernetes or databases web frameworks so on and so forth and the reason those two things having worried is because Although these are free software and they're even peer production in the sense that there is peer production happening around these things Maybe less than was the case in Linux in the mid 90s, but but but it's definitely happening They're both driven by by firms who are engaging in a kind of strategic openness that that involves the Software being released freely and even distributed freely But in both cases it's companies that are developing and deploying software The where the companies who are developing and deploying the software get the freedom and the users the end users do not In the case of web services, you know software is not even running on your computer And we RMS talked about this yesterday, right? Like the software runs on someone else's computer They have the freedom to change it and to pull in things, but the users of that web service have nothing Or very or very little Not better that they would be proprietary for this certainly for the sake of the companies that are building them in the phone manufacturers They have all the freedoms that we care about But I think we need to recognize as a community that the users of both systems are almost universally and totally unfree and They're doing it in ways that provide freedom and benefits and freedom to themselves, but not their users Sorry a little bit technical issue here. It did that to me over and over All right, so I listened to that and I was shocked because I spent like maybe one-third of my professional career fighting for the clouds to become free and available to everyone and They're just saying that We should not use it that that's not ever going to happen ever like and On top of that the question is not Whether or not if you're running the cloud it's Okay, you could be renting a small VM you could be renting a one-use ever you could be Owning that server putting it in a rack and then just doing colocation You couldn't own the rack and it switches or the center or even the power grid and production It can go on and on and on yes, of course you do have more freedom when you own all these things But this is not about it. The question is whether or not you control the software that that's is powering your deployment online, right and Using non proprietary software is what is removing Freedom at least I think so So owning or leasing the The hosting infrastructure is just a question about managing your own costs Having a VM a private cloud or a public cloud is also about managing your costs The important thing is what do you run on it and do you have the full control over it? I believe in that way that the The FSF communication message is wrong and that they should aim at People not to use the proprietary clouds like Amazon Google Azure or Digital ocean because these are all all proprietary solution even though you can run debian on it. So What you should aim at so it's a bit redundant so what you should aim at is Avoiding vendor locking and being able to switch providers Switching providers means that you have an open framework to do so and that you are able to use the same API to go from one provider to another and That is what open stack is all about the important thing is Interrupt variability if I can succeed in pronouncing it So that's what you see here on the screen is the open stack manifesto. So I Will I will say the loud loud for you. So open stack is a reliable cloud infrastructure With the mission to be ubiquitous and to produce Public and private cloud regardless of size and it it needs to be massively scalable so The important thing here is ubiquitous In terms of freedom because this way you can go from one provider to another So the key is in interoperability The the open stack clients are Tested to be always the backward compatible meaning that you can use the latest version of the open stack client and still go to host on a Service provider that is using a very old version of open stack. This will continue to work The other thing a the other meaning of that manifesto is that you are able to implement open stack by yourself and Install it on prem. So you set up your own computers with open stack. So that's at least the theory, right? The other thing is that with open stack you also do have all the features that are on the proprietary solutions You have an encrypted volume auto scaling DNS as a service DB as a service and whatnot. We used to say As a joke that open stack is project as a service because it's so rich in features so Also, the API is very clean and if you compare it to the AWS API I Like it a way more If you look at some some of the tools from Google, it's just scary. So In terms of just quality of the product. I think it's really comparable And also you do have 12 region for Amazon For open stack providers, you have 18 of them Spread across 50 regions These are only the companies that Registered into the open stack marketplace. So if you go to open stack log You click on marketplace public cloud and then you see this map So for sure you will find a service provider that is next to you or next to your customer And then the next question is why should you Use open stack and on Debian and not on other distributions So other Vendors are trying to sell a product to you Most of the time they want also to sell some services around it The only operating system where I it's not the case is Debian Also, I have to Explain the Ubuntu trade trademark thing. So on my my previous employer was Burantis Burantis had this solution for setting up open stack using DVD that used to contain all the packages from from Ubuntu So they were able to do that because they had the Ubuntu license But as you may know Ubuntu even though is free software Has a trademark issue, which is on purpose blurred and especially for open stack Meaning that if you want to make a derivative without asking Canonical Then you have to remove everything that is related to Ubuntu trade Ubuntu trade mark for example you need to recompile every packages and If you see Ubuntu even on a changelog version you have to remove the word Ubuntu therefore my my my previous employer had to Remove all the Ubuntu packages from the DVD distribution so There is no problem to do derivative on Debian including with all the open stack packages And I believe that's also part of not being vendor locked in Because you're not locked in with with a provider You could fork Debian and do a derivative issue if you don't like Well what we're doing the other thing is When I say Debian packages are always on the edge it means that we get the dates first There's the biggest number of package services inside inside open stack. It has always been the case and I've been Trying to do so to always have one or more services than than what you saw on other distributions and The other thing is because of uploading to seed then we also get Updates from dependencies Learer than all the distributions so Even though I maintain an official Debian backports on on Debian.net domain name the work is still done in seed and like The great happens there. So currently there's some Python 3.7 grades That needs to happen So if you are a Python developer Debian is also a good choice and then there's the question of deploying open stack, right? So everybody knows that famously open stack isn't easy to deploy So Since I started doing this packaging I've tried to make it as easy as possible The first thing was made with depth comf screens so that you could just have easy questions to answer to set up your DB access to rabbit MQ messaging and this kind of things and then providing a preceding library so that you can choose just call a Small share script function to do the preceding so that has been available for a few years since Maybe stretch These screens on bothering at all any configuration management management tool anymore it's it's safe and tested and The other thing which is a lot more recent is Puppets so as you may know there's that puppet open stack upstream software that Deploys open stack for red hats and Ubuntu So I started in the beginning of spring to patch it to understand the beyond and now it's fully upstreamed Meaning that There is gating on upstream CI to make sure that you can install open stack using Debian packages and Hopefully it won't break because of the CI So if you want to have bigger scale You can you can use these puppet packages packages because These puppet modules. I also package them in order to create Bigger software which hopefully I will have time to explain. So as I said Earlier The other advantage is that Debian is fully free and unlike what you get from other distributions My last another thing which I want Another message I want to pass on is that if you are In the need of hosting and you decide to use the cloud then very much you should aim for Somebody that uses open stack because by doing so you will grow the number of providers and It's going to help the ecosystem so My own effort into Making the cloud free is working on open stack on Debian and making it to available for everyone and in a way so that it's easy to to use and deploy it so I'm trying to make it Open stack So my goal is that open stack on Debian is the best solution for on-prem clouds I Hope one day we will have bike sheds so that it could be backpours could be shipped into a More official way than the Debian.net domain The other thing is pipette open stack that I worked on and the last thing is the glue between all of that which is Open stack cloud installer, which I'm currently working on So the short name would be OCI so I'm not going to do a full demonstration of it, but Because that's probably not not very useful. I think it's best that I just explain what it does so what you see here is a VM but because I use it for my development, but it could as well run on bare metal So that VM does DHCP PXC and so on so that you can Network boot VMs these VMs are booting onto a Debian live system produced with live build Inside that live image. There's an agent Which is very very tiny written in shell script that reports back to that server that you see here and So that the the the bare metal machines can report What what their characteristics are so how much memory how much hard drive? What's the interfaces their MAC address and speed and so on okay? So then after that you have you do have a list of VMs that are booted over the HEP and their serial numbers so once you've Got a few machines, then you can start your deployment to do that you you got to define networks so You can define one. I don't know one for volume. Okay, I Signed it an IP address Then you have rules for your machines That you can you can add some custom ones. These are the defaults And then finally you define your clusters. So here there's one cluster which I already Made and when you when you click on it on that already existing cluster then you see a bit more so It's it's not very nice because the resolution is a little bit too small. I'm sorry for that. So at the bottom you see available machines which use also so on the first screen That you can add to your cluster and then they are numbered automatically and According to the network. I've added to the cluster then the IPs are added automatically as well and then Here you see the virtual IP for the for the cluster so that you can share one IP in a HA mode On on these two machines so these this is just to define rules and IPs for the machines There is no big Install the cluster button, but that's I will add it some someday In the meantime, you can just click the install button. So what's going to happen when when you click the install button? So first it's going to Create some puppet certificate into the this DHCP PXC server and Copy it into the live system So that it's ready for installation Then it's going to run OpenStack DBN images to Install on bare metal a system using the bootstrap and whatnot and Once that's done the server will reboot It will already be prepared for puppets It has a role and then when it boots up then it Puppets agent will contact this server And this server has an ENC for the people who knows a puppet. That's an external node classifier So that the server will be able to tell Puppet agent What services to install so that's where I'm up to right now I Have the packages. I have puppet. I have this bare metal installer and And now what's missing is composing the services, but I think that's fairly easy compared to the rest of the world that I've Done already on this. So hopefully this will be ready for Buster so that we have a point and click installer for OpenStack I think that's it. So this was my presentation. I'm open for questions So, yeah, so finally before I end so this software and all I've been doing over the last seven years is my way to fight against proprietary cloud software and So which is why I wanted to To do this talk is because I was very frustrated about the way the FSF was doing things and I found it Very frustrating to invest so much work to do To try to liberate the cloud and having the FSF being doing a very counterproductive message Okay, thank you. Is there any question? Yeah, there's only one mic So is this software that you just presented available in Debian or is it in the new queue? Like I mean this solution that you just showed Kind of you have a version in Debian, which is one month old But it's in salsa. Okay, so you can build it if you want it comes together with a So this is Yeah, the other thing is it's very ugly right now. So you please don't pay attention to the GUI I will probably give it to some designers. Okay. I'm not I'm not a GUI guy It comes with a package which is called OpenStack Cluster installer dash Pock like POC so you can install the the Pock package in your bare metal machine and then it spawns some VMs So that's that's the way I do my development. So if you want to participate to it then You can just use the Pock and then it's very easy to set up. The only thing is that it's quite demanding in terms of Resources so I have a 128 gig of ramps ever to turn that Probably you could downsize it I'm not sure that you I will be the most Important thing especially as something like this to start machines will be used more by technical That's the other thing. It comes also with an API so You can you can Push machines into the cluster. So in fact everything you saw there you can you can do it with API, okay? It's kind of not really a rest API because it's not Rest addresses, but like with parameters Cool thanks Red Hat and the CentOS supports the several most accurate use to the in one CentOS version Is there a way to achieve this in the band? So We do have back ports of Every open stack release to the whatever is the current release so There's a What mitaka? Newton pike whatever Available About us Upgraders version and one's a new Deba stable wrist and then they say how to for them for jump to new release and so yeah with with open stack you cannot upgrade from one version to another because the db migration script Imports the code of Of whatever service we are talking about So you can only jump from one version to the next Because I'm I've I've used a puppet open stack. Normally upgrades are supported I'm not planning on managing upgrades on my software. So if you want to do it to do the upgrades You will probably need to do some Manual puppet tweaking stuff. I'm not sure yet. Okay Anyone else? Have you talked the idea of make a pure blend of something like open cloud? pure blend from the end so What I'm looking forward to have is the bike sheds, you know, the Debian way to do PPAs and And It better have that than just a pure blend. I'm not sure a pure blend would be useful because I Mean pure blends are to be able to install Like I don't know the DNA you with the Di right You could do that with open stack, but I'm not sure it would make sense because What you want to do is be able to deploy a full cluster automatically You don't really want to do it by hand. Do you think that? when this will be released it would be Easier to set up an open stack environment because now open stack is very is very complicated and You boom to sell some property solutions because Paying it's more simple to do but for a smaller Stacks and now it's quite difficult to set up An open stack solution. So that's very much my goal though What I aim with this software is to be able to address People willing to Do a quick deployment on prem probably to test and try open stack I'm not sure it's How can I say If you want to have fully Working open stack for a long time. You also need the knowledge, right? If you're not capable of of setting it up by hand yourself, probably you also won't be able to maintain it Okay Having a software to do just an install is Super cool so that you can have automation to do the installation it's It's Nice to have it for people who are newbies and just want to try trade at home, but it doesn't replace knowledge two questions the first one is Which framework or language is using OCI like this? Python php power. Yeah, that's written in phps. Okay, and the second is why not like reuse triple L triple low So I've tried to make it as Small and easy to maintain as possible Which I don't think fits all the definition of triple low It's like a triple low is made by 80 engineers And they still have a lot of trouble. Yeah, okay It makes sense when you say this is for like smaller clouds Okay, I hope I hope to use it in my in infomaniac like for our For our deployments and I'm not sure what we can call small like We're having a few hundred nodes Like open stack becomes very tricky after this type of scales, right? Could you go to that slide that showed the? Benefits of Debbie and not having the vendor lock-in and those kinds of points sure I'm not sure what is It's one of those in there Vendor lock-in yes, so I was thinking about the way you're framing this as a You're concerned about the way the FSF was criticizing cloud and Yes, so let me let me explain my point of it Seems like there are two different kinds of problems like There is a problem that the masses of the world are locked into as Clients of servers they have no control over and their data Has is not in their control and their access is not in their control in these conditions And so that's the I see that is the criticism about the cloud and it also applies to administrators You know, do you have control over your machines that you're providing for your clients? Presently what my talk is about. Yes. Yeah, so it seems like I think the FSF criticism is still Valid and true and I hear what you're saying is okay. Let's make it if we're going to have a cloud Let's do it right rather than yeah, and their message is blurred Yeah, saying that it's just clouds and they are not saying please choose the correct cloud Which is what I believe they should say Yeah, it's important to parse out those different parts of it rather than just thinking of it as You're saying FSF is wrong. It's more like okay. We do have a cloud. How do we do it, right? I'm 100% with them in fact and and I just think they are doing a counterproductive message Any anyone else? All right. Thank you then