We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

openSUSE MicroOS in Production

00:00

Formale Metadaten

Titel
openSUSE MicroOS in Production
Untertitel
Deploying apps using Podman
Serientitel
Anzahl der Teile
40
Autor
Mitwirkende
Lizenz
CC-Namensnennung 3.0 Unported:
Sie dürfen das Werk bzw. den Inhalt zu jedem legalen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen.
Identifikatoren
Herausgeber
Erscheinungsjahr
Sprache

Inhaltliche Metadaten

Fachgebiet
Genre
Abstract
This talk will be about deploying comment business applications on openSUSE MicroOS It will have a 15 mins presentation about the challenges that we face at our company La Sentinelle, Mauritius and how we used openSUSE MicroOS to address those. The presentation will follow by a 30 mins technical demo deploying a business application on MicroOSp. Finally, there will be 15 mins to address questions pertaining to the technical demo and any other business.
App <Programm>Gebäude <Mathematik>SystemprogrammierungZeitbereichDigitalsignalVideokonferenzSoftwareDienst <Informatik>Güte der AnpassungZweiRechenschieberWellenpaketDatenverwaltungDienst <Informatik>SoftwareentwicklerProdukt <Mathematik>BitDivisionVideokonferenzHypermediaDigitalisierungMailing-ListeComputeranimation
MultiplikationsoperatorOffene MengeProgrammierungComputeranimation
Coxeter-GruppeGeradeMultiplikationsoperatorProdukt <Mathematik>Computeranimation
Kartesische KoordinatenMomentenproblemRechter WinkelInstallation <Informatik>Gewicht <Ausgleichsrechnung>
Physikalisches SystemQuellcodeElektronische UnterschriftSinusfunktionSpezialrechnerSteifes AnfangswertproblemSingle Sign-OnGenerizitätVirtuelle MaschineGewicht <Ausgleichsrechnung>ServerKonfiguration <Informatik>DistributionenraumSoftwaretestDienst <Informatik>SoftwareentwicklerRechenschieberPunktSkriptspracheCASE <Informatik>Kartesische KoordinatenBildgebendes VerfahrenProgrammierungElektronische PublikationKonfigurationsraumVariableProgrammierumgebungDokumentenserverWort <Informatik>BinärcodeOffene MengeApp <Programm>Physikalisches SystemMultiplikationsoperatorMetropolitan area networkTrennschärfe <Statistik>VersionsverwaltungMehrrechnersystemHypermediaWeb-SeiteNetzadresseMinkowski-MetrikLoginMapping <Computergraphik>MereologieFahne <Mathematik>ATMOvalSkalarproduktBestimmtheitsmaßGleitendes MittelCode
TouchscreenBitMetropolitan area networkMultiplikationsoperatorComputeranimation
SpezialrechnerPhysikalisches SystemMapping <Computergraphik>DatensatzMultiplikationsoperatorFormation <Mathematik>Computeranimation
VideokonferenzSoftwareDienst <Informatik>DigitalsignalSystemprogrammierungPhysikalisches SystemSpezialrechnerQuellcodeDokumentenserverProgrammbibliothekFirefox <Programm>RechenschieberComputeranimation
Physikalisches SystemNotebook-ComputerRadikal <Mathematik>Metropolitan area networkUmwandlungsenthalpieComputeranimation
Coxeter-GruppeMultiplikationsoperatorRechenschieberMetropolitan area networkRadiusStörungstheorieSpeicherabzugDifferenteElektronische PublikationComputeranimation
CASE <Informatik>NetzadresseMereologieKartesische KoordinatenUmwandlungsenthalpie
Kartesische KoordinatenGeradeNamensraumSoftwareTelekommunikationInterface <Schaltung>MereologieCoxeter-Gruppe
Vollständiger VerbandVideokonferenzComputeranimation
Transkript: Englisch(automatisch erzeugt)
Good afternoon everyone, so I suppose I can start Let me just go to the next slide and I can start talking about myself for just a few seconds so my name is Isha sukhan I
Work for a company called last night's Nell limited which is in Mauritius and I worked more specifically in the LSL digital division and I'm also an open series member. So very briefly what we do Last night's Nell is a media company that publishes newspapers magazines
manuals and school textbooks for not just for Mauritius, but Madagascar and a couple of other countries in the African continent and Then my division LSL digital that's mainly what we do we do advertising video production software development Manage services for the company and we do have a couple few external customers and we also do training
It's not an exhaustive list, but that's it a little bit So again, very quickly my journey with open Susie started a couple of years ago. Well, give a precise somewhere around 2009 With the open Susie ambassadors program. I've been
Talking every now and then but mostly only in Mauritius and this is my first time at the OSC My first time in Nuremberg my first time in Germany and my first time in Europe, so please be gentle be kind
alright, so what I'm gonna talk about is opens with a micro OS and Most of the time this is the question that pops when I tell people that I'm using micro OS in production So why micro OS? The Next few things so might be a repetition of what others have already spoken about as
in advantages of micro OS Maybe this line is not correct I should have said a micro OS the container host because micro OS the way Richard has been presenting in the presentation earlier. It's not just for containers. He's aiming for desktops
So yeah, the container host first of all, it's designed for containers, so what can I do with that? Obviously something like this right from the moment of Install it right from the moment after installation. I can already start managing containers
I can create my containers. I can deploy my applications and that's it I do not have to go around installing a couple of tools to be able to start Deploying Next a Slight weight. It doesn't come with unneeded packages. For example, if I would take a
generic Linux distribution for a server and I would like to do to run containers on those Yes, I would install a container engine and do that but at the same time I would get tons of packages, which I don't need and It will be pain to remove those packages. So yeah
And Next transactional updates which Richard and others have I suppose have already spoken about If something is messed up with an update you just roll back. So I really like that The last one is space on tumbleweed so you're always on cutting edge
So how to obtain micro OS until a few weeks ago. This was how you would get it You would go on cubic dot open sousa dot org and You would download the installation media and during installation. You're gonna select the open sousa micro OS system role, but Like I said that was until a few weeks ago now. It's no more. So now
We do not have a fancy page right now where you could just go and download The installation media but at least for me, this is what I do I go to mirrors that open sousa dot org find the closest mirror because I live in the middle of the Indian Ocean
Mauritius everything is far away from us Europe's for us is for Australia's for and the closest that I get could be South Africa with 75 milliseconds of you know Downloading things. So yes, I will find it and I will go under the tumbleweed to
You are there and I will find the open sousa micro s dvd ISO image Alright, we have our image. We've put it on pen drive or maybe we're gonna try it on a VM and This is what is going to happen you get this Until this step of the installation where you need to select a system role and you're gonna select micro OS
Container host because if you select the first one, it's not for containers. It's like You just have the micro s and you do whatever you want with that. We were very stripped down version of Open Tuesday tumbleweed So the next thing this is not about micro s but I have the micro OS
Container was running now. I need to create my containers. So this is what I'm using on my machine and build up so I Think I messed up. Yeah
so With builder the first thing that I'm gonna do is run this thing, which is just free words build up from open sousa and by doing this I get a Working container into which I can package my application. Let's say that's that could be just the
A binary from a go application that my developers just wrote and the next step Would be like this. I do build images and I could see that open sousa working containers running and Next like I said In this slide you can I would just give you a quick
Explanation of that LSL dash up is actually a folder that contains My application files a binary a couple of images most probably a configuration file Something like dot E and V with environment variables for my program And all I would do is copy all these into that working container
Alright, the next thing that I need is an entry point So like you would know that when you have a container when you spin the container and make it run using any Container engine the first thing that is going to run is What has been specified at the entry point? Otherwise you could still run your container and specify what you're gonna run in this case
I'm specifying that in the folder called up. There's a script called entry point and within that script I'm gonna obviously say, okay, you know, there's this binary here. You can run it But before running this there's a couple of few things that you need to do in this container
So, all right, that's it for creating my container With Let's say an application that my developers have developed Now after doing those first two steps, that's one last thing that I need to do I need to commit this and As you can see, it's very simple build a commit OpenCZ working container and I'm gonna give it a name and a tag. So
this application Has been developed by Let's not enough by my developer colleagues as a micro service for a single sign-on service that is we have different tools and this one is going to be the single sign-on where
Employees just come in sign in and they can make requests for transport make requests to HR make requests Well, maybe the canteen something like that And we call it passport So that is why in the name there All right now Actually what I was showing you earlier, I think I messed up with these slides the first tool
I was talking about was builder and the second tool which is present in The micro as container host is Budman But again last minute slides, you know, it happens to be master so after I've used build out you to create the container and put
The application that I do put my images just like you would use another container Engine and maybe you do docker images. You usually find your images put on images the same You will see that the repository on this and this one is localhost passport because I'm still creating that in my machine
I haven't published it on a Repository somewhere. It's just for tests So now that I have my image my image available here My next step is to just run it and test it. So very simple. These are the same
Options flags the way you want to call it that you might have been using with docker Like docker run blah blah blah blah and it happens. So the same applies to pod man So I have pod man run. I'm running that in detach mode I'm exposing the the port my application in the container runs and over port
1704 mapping that with 88 on my Host machine. I'm giving the container a name called passport and obviously the last part of that is Telling which container to run and I'm putting the tag version 1 Notice that I haven't specified a command after that because I already have an entry point which was the entry point
.sh script in which I'm telling the container when you're spinning you just have to run the binary So that's it. Oh, yeah, there's a second way to do it In the previous slide I said, okay, I'm just mapping the port or you could specify a
How do you call that a fixed IP address if you're just testing that so it's dash dash IP and you specify it And it's gonna work Almost the same. All right, I do a pod man PS this time and my container passport With the tag v1 is running and in the command you might see that it's been a search slash app
E4 the entry point and goes on there Actually this critical application also needs Postgres and Redis and that's something that I had already run on the machine and To finish I just have to put the localhost 8080 there and it's working so I
Don't know about Okay, I will try to do this it's a bit not something that I had planned
It's not working but anyway, let's do it like this I have to look at two screens at the same time But man Yes, like I said So this one is where I've mapped the port as you can see in the last
Last row there. It's mapping my host systems 8080 over container 7204 so if this time I Have to All right. I have to do it like this
okay, my Never mind Never mind Let's go until the
last slide maybe alright Yeah, this one and here it is so anyone has a question about this of Why we are doing it and Anything specific to put man builder or my cross in general?
Sorry, I was trying to do to just run the same thing again in the terminal but the mirroring of the Laptops is not working so anyone comments Questions possibly no one that's cool. Awesome. You have something. Okay
Thank you for the presentation Is there a way for you to to run multiple container at the same time with but man or?
In micro s I mean you you've shown that you're using Postgres and Redis as well If you want to deploy all them at the same time in the coordinate coordinate fashion, I Don't think I got your question clear
Is there for you a way to to reproduce the behavior of Docker compose for example Docker compose for example, so Not exactly that way but You could still write everything in a Docker file. Okay, which is I think Richard wants to answer that
so I was about to talk about but man built or Build a bit, but anyway But one of the really cool features that I forgot to talk about in my talk Portman supports pods. So in Kubernetes land when you've got a Service where you need to have more than one container, you know in Docker land
You stop it compose you put it in one yaml file in Kubernetes land You put them in another different kind of yaml file for pod Portman supports that so Use yeah use pods instead of Instead of compose, you know, it's easy You don't have to use Kubernetes so you can yeah
So you can use Portman with pods without Kubernetes and then if you grow into Kubernetes in that end It's it's even more efficient than using Yes, he Richard already explained that you could still use Portman to create your puts and
when you're running each of those containers, you could just Put just like in the previous slides. I've put Where is it? I think it was in this one dash dash IP address to specify the IP I would just have to put dash dash but to put the pod name that I created and all those containers that I'm spinning will go in a specific pod and
That's very simple. If those are different then in this case in this particular case exactly The application the go application on the first line the Redis and the Postgres would all communicate over
Once 27 0 0 1 because they are in the same port So sharing the same network namespace and then of course you can have a second port We have a tons of applications and all those will be communicating over That low back interface and not communicating there won't be the communication between the two parts. Yeah
Somebody else comment question, maybe All right, cool. That was a short and sweet presentation. Thank you people