YaST – Yet another SUSE Talk?
This is a modal window.
Das Video konnte nicht geladen werden, da entweder ein Server- oder Netzwerkfehler auftrat oder das Format nicht unterstützt wird.
Formale Metadaten
| Titel |
| |
| Untertitel |
| |
| 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 | 10.5446/54433 (DOI) | |
| Herausgeber | ||
| Erscheinungsjahr | ||
| Sprache |
Inhaltliche Metadaten
| Fachgebiet | ||
| Genre | ||
| Abstract |
|
openSUSE Conference 20194 / 40
7
11
12
13
15
16
17
18
19
20
23
25
26
27
34
38
40
00:00
Inverser LimesProdukt <Mathematik>Computeranimation
00:23
EnergiedichteGüte der AnpassungVorlesung/Konferenz
00:43
Produkt <Mathematik>Prozess <Informatik>DatenverwaltungBitSupersymmetrieProjektive EbeneComputeranimation
01:23
Stochastische AbhängigkeitOffene MengeKette <Mathematik>QuellcodeUnternehmensarchitekturBildverstehenFaktor <Algebra>ZahlenbereichSupersymmetrieOpen SourceAutomatische HandlungsplanungVerschlingungKeller <Informatik>DatenverwaltungSoftwareProjektive EbeneOffene MengeSoftwareentwicklerKette <Mathematik>FokalpunktFunktionalMereologieFaktor <Algebra>EinsBitDienst <Informatik>StabDifferenteMultiplikationsoperatorProdukt <Mathematik>MAPRechenschieberUltraviolett-PhotoelektronenspektroskopieProgrammbibliothekWinkelGüte der AnpassungGruppenoperationOffice-PaketStochastische AbhängigkeitAusnahmebehandlungBenutzeroberflächeZentrische StreckungLipschitz-StetigkeitPunktwolkeComputeranimation
07:00
Faktor <Algebra>SystemplattformCAN-BusDatenverwaltungDefaultRechnernetzStrom <Mathematik>Wurzel <Mathematik>ServerSoftwareentwicklerLineares GleichungssystemEreignishorizontFunktion <Mathematik>Coxeter-GruppeCompilerChi-Quadrat-VerteilungGamecontrollerKubischer GraphSynchronisierungMixed RealityProgrammierumgebungSoftwareProjektive EbeneBildgebendes VerfahrenRechenschieberGebäude <Mathematik>MereologieVerschlingungGreen-FunktionHilfesystemVersionsverwaltungOpen SourceDienst <Informatik>Web logDifferenteLastteilungSoftwareplattformZusammenhängender GraphFramework <Informatik>Profil <Aerodynamik>Rechter WinkelTouchscreenBitWeb SiteTermComputersicherheitDistributionenraumProzess <Informatik>Coxeter-GruppeServerPunktMoment <Mathematik>TransaktionComputeranimationFlussdiagramm
12:05
SpezialrechnerFaktor <Algebra>QuellcodeUnternehmensarchitekturMakrobefehlFokalpunktSoftwareplattformMigration <Informatik>AppletSoftwareentwicklerProgrammHackerSoftwareentwicklerCodeWeb SiteRelativitätstheorieNeuroinformatikProjektive EbeneVisualisierungSoundverarbeitungPortscannerBildgebendes VerfahrenDifferenteProgrammbibliothekKonfigurationsdatenbankRechter WinkelOffene MengeWhiteboardWurzel <Mathematik>Faktor <Algebra>PasswortQuaderComputersicherheitLipschitz-StetigkeitMehrrechnersystemMAPDreiecksfreier GraphProgrammierungNichtlinearer OperatorHilfesystemRoboterMakrobefehlFreewareDefaultPerspektiveMultiplikationsoperatorBitrateNotebook-ComputerHackerComputeranimation
17:09
HackerEin-AusgabeRechter WinkelDrahtloses lokales NetzFormation <Mathematik>Computeranimation
18:27
VideokonferenzVorlesung/Konferenz
Transkript: Englisch(automatisch erzeugt)
00:06
All right, we're going to go ahead and get started. I want to thank Thomas DiGiacomo, president of engineering product and innovation for SUSE, coming here and giving his talk. He's going to have to leave quickly after his talk,
00:20
so try to keep questions to a limit if it gets into questions. So here's Thomas. Thanks. Thanks, Doug. Hey, good morning, everyone. It's good to see that you have so much energy early in the morning, but you will need a lot of energy for the coming two, three days.
00:42
Thanks for coming to OSC. And we are always very happy and excited to see the community coming together. And I want to thank Doug and everybody who helped and made that happen. It's a lot of work for people, and they're already doing a great job.
01:00
Thanks for them. So I'm Thomas. I'm a SUSE employee and working with engineers with product managers, and I'm very honored to be here as well. So I will try not to talk too much about SUSE,
01:21
but I have to talk about SUSE a little bit. So we are actually independent since March 15th. So we had a lot of parties and cakes around the world. You cannot really see that, but it's in Beijing, the SUSE Beijing office. The cake was huge. So there was food for maybe two weeks
01:41
for 50 people in a single cake. And some people say, well, you're not really independent. You're owned by private equity. And so that's not being independent. And yes, we are more independent than in the past because we are not under the micro focus group anymore. That means we have SUSE HR people.
02:01
We have SUSE finance people. We already had SUSE dedicated engineers, sales, product and marketing and all of that. But now we are getting all the functions under the green flag, except for IT for now. So we are still relying on micro focus IT for another 12 to 18 months. But we will move to a SUSE IT stack
02:23
in the future as well. And we hope to make it more green than it was in the past more based on open source obviously, as much as we can. So we are working on that. And I'm sure there are probably people in the room that are involved in those kind of discussions. I wanted to give a few numbers as well. So SUSE today, we are about 1800 people.
02:45
We make about 400 millions of revenues per year. And the plan is to be in five years, around 3000 people and around 800 million revenues. I joined SUSE in 2016 and the company was 600 people. So we are growing.
03:02
We are welcoming more and more people in the company. And with that, we realized that all the good culture, the open source DNA that SUSE has, we need to bring that to the new people coming to us as well. And sometimes they come already
03:20
with an open source background, but we decided to write an open source policy. So after 26 years without having an open source policy, we worked on an open source policy back in September last year. It's mentioning a lot of the open source stuff. It's actually, there's a link in the SUSE open source policy to open SUSE website as well.
03:43
We joined the open chain compliance to make sure that we are delivering as a company software in an open source compliant way as well. So we've done some of that to also help new people when they join us to understand how we do our things.
04:03
Now, as you know, we are contributing to a lot of upstream projects, so Linux, OpenStack, all of that. I just wanted to highlight a couple of examples there of some of maybe smaller projects, but that we pushed upstream. So on the left, you have OpenAttic.
04:21
It's a storage manager, open source solution. It was open source, but we pushed that to safe upstream. So it's now part of safe upstream. The other example is Stratos. Stratos is a user interface for Cloud Foundry. We got that software from HPE. It was not open source, so we open sourced that.
04:43
Then it was on GitHub, but it was not part of the Cloud Foundry upstream, so we pushed that as well to Cloud Foundry upstream. And that's what we try to do. So as much as we can, open source is great, but we try to be upstream as well with the development that we do. And when they are not, we try to push them upstream and contribute there.
05:02
Airship is another one, if you're interested. That's under the OpenStack Foundation. It's a lifecycle manager to deploy containerized services. So we are planning to containerize OpenStack, containerize safe, and deploy and manage that with Airship. That could be an interesting thing to look at.
05:22
That's it about SUSE. So what's great with the way that OpenSUSE community and SUSE work is that I think we collaborate in a very unique way. So it probably started two or three years ago with the LIP and factory and Tumbleweed split.
05:42
And it took a little bit of time, but I think today the factory first concept is working very nicely. There are always things that we can improve, but whatever SUSE does for products, it goes into factory. And that's how we release SLES.
06:00
That's how we release the different flavors of SLES. And the latest child of that union is LIP 15.1. And it was released two, three days ago. I haven't upgraded yet. I wanted to do that on stage, but I will not do it. I will do it later so that I can continue with my slides.
06:24
But that's a great new thing. If you haven't upgraded, you should probably try it. It seems to work quite nicely. It's borrowing, even people are saying. Borrowing upgrades are good upgrades. So congratulations to everybody involved in that.
06:45
So that's for the things between OpenSUSE and SUSE that works fine. There are things that are a bit more challenging. And we want to be transparent as well. So I don't want only to talk about good things. I want to talk about things that we need to improve and look from a different angle.
07:01
So I'm gonna use the Cubic and SUSE CAS container as a service platform example. Today, those two things are not tightly integrated. They are not actually working together. So on the left, you have version three of CASP. It's the current version. And we are going to release CASP version four on the right.
07:23
And what we are changing is we are aligning from an architectural standpoint, the open source project and components that CASP is using to be closer to Cubic. Because we think that will help us working together more efficiently in the future. So from an OS standpoint,
07:43
there are still discussion as well because CASP was based on micro OS. Now we want to be able to run CASP so the SUSE Kubernetes distribution on top of SLE, including transactional upgrades. So there are still things that we need to discuss with the Cubic community as well in there. We are moving.
08:01
CASP was a bit lagging in terms of supporting the latest upstream Kubernetes releases. Kubernetes is released every quarter. Cubic was much faster to adapt and include the latest Kubernetes, but we were not able to do that with CASP. So we are changing this. We have different processes. And now we can be in sync much better with Kubernetes upstream.
08:21
And that means that will help us as well to be more closer to Cubic. Starting from CASP before. We changed the container engine in CASP before. Dropping, we are using the Docker community engine, community edition engine. In the previous version, we are moving to Cryo on top of Francie.
08:41
And that again is going to make us closer to Cubic, which is Cryo friendly since quite a while already. And we are pretty happy actually to drop some of the links with the Docker engine and go Cryo. On the networking side as well, tomorrow morning I think there's a keynote about Selium from Thomas Graff.
09:02
We are very interested by that project. We contribute to that. And we are planning to bring Selium in CASP before too. So on the slide I'm putting some reference to sessions that are happening today, tomorrow and Sunday. So if you're interested by any of the topics that I'm mentioning, you can also join those sessions later.
09:22
They will be much more interesting and detailed than what I can say about the topics. So one last thing I wanted to mention as well, it's Rook. Rook is a project to help use Ceph for container infrastructure.
09:41
And we are actually building Rook now on top of CASP with Cubic as well. And it's almost all green. So it's from yesterday night. I hope today it's green as well. On the top left side of things. Now I talked about SUSE and OpenSUSE, but what's really making a difference
10:01
is the people and the project. So I'm using a few screenshots from GitHub profiles. I hope people don't mind. I didn't ask them for permission to put their faces on the screen. I hope that's okay. But I wanted to highlight the fact that it's about people doing things. And whether they are SUSE employees or part of the OpenSUSE community
10:20
and not SUSE employees, it doesn't really matter. But they are doing really cool, cool things. And I took just a few examples there. One of them is OpenFaz. So that's a serverless framework. There was a talk at OSC 18 last year. And it was a slide-less presentation. So no slides from Panos.
10:42
I also wanted to mention traffic. And there's a great blog post on the Cubic website by Panos, again, describing how to use traffic and the security policies of Kubernetes to do some ingress and load balancing in a Kubernetes environment. Very cool stuff on top of Cubic.
11:02
And the last one is Kata, Kata containers. So if you're not familiar with Kata, it's a kind of, it's a mix between a container and a VM. They are some part of the hypervisor in the container image. It's actually improving the isolation of containers. It's run C compliant as well.
11:22
And the people there, they helped integrating Kata with Cubic, with SUSEcast platform as well, and with Cryo. So the Kata project is actually running their CI infrastructure on top of SLES. And they use OBS as well, apparently, to build Kata.
11:43
So that's pretty cool. And yeah, on the right, I added a cup of coffee for this morning, that's Vagrant. And we're doing, Danny's doing really cool things with Vagrant, building images as well. So you can check that too if you're interested.
12:05
Talking about building, so OBS, you all know that, right? So we can build with Kiwi container images from OBS now. And different flavor of container images for sleep, for leap.
12:24
The good thing is that then we have an open SUSE registry to host the container images and scan them. So it's a good thing. We don't want to do Docker Hub. I don't know if you read the news recently, but like a few days ago, they discovered that there were about 2,000 container images
12:42
on Docker Hub where the root password was blank. So some security concerns there, and I think what we're doing there is actually a lot better and SUSE is also working on a SUSE registry to be used for commercial customers and partners and also tightly integrated with OBS.
13:04
So again, there are talks about that on Friday and tomorrow as well. Now I had two more projects that I wanted to highlight and one is Maven, and I think Friedrich is in the room.
13:21
So based on the work, yeah, he's hiding somewhere. If you keep hiding, I will ask you to come on stage. So we have to give credit to people as well, so it's based on what the Fedora guys have done with RPM macros, but Friedrich and a few other people,
13:41
they've done a lot of work to make that work properly with factory and also building that quite nicely in OBS without adding cycles to OBS. It's pretty cool. A lot of packages, and talking about packages, I'm very happy with package.hub. I've been very excited about package.hub in the past and I'm even more now because by default,
14:03
all the lib packages are coming into package.hub now. I think it's from package.hub 15, but it started with 12sp4 as well, so it's pretty cool. And I also wanted to give credit there because from a SUSE perspective,
14:20
it helps us a lot to have thousands of packages on package.hub for our customers, actually. Now, well, we've started the developer program inside SUSE. I think Marco will be there if he's not already there, and there's a session tomorrow,
14:41
there are actually two sessions about that. With the developer program, we are trying to address a gap that we think we have at a SUSE level. SLES is well known by ops guys, by sys admins, but we are lacking visibility with the developer community. We don't want to become Ubuntu, but still we need to be closer to the developers
15:00
and show them all the great tools that we have, thanks to the OpenSUSE community as well, OBS, OpenQA, all of that. Bring that together and help developers with OpenSUSE and SLES. So that's why we do stuff like vagrant as well, and we try to improve how we can deliver technologies
15:21
to developer for developers. Last thing I wanted to mention, we are doing HackWix inside SUSE, so that's a week where engineers are free to do whatever they want to do. It doesn't have to be work-related, doesn't have to be, sometimes they don't even code anything, or they don't even open a laptop,
15:41
they can do paintings or whatever, but most of the time, engineers when they have free time, they do stuff with computers. So I wanted to highlight a couple of projects. So there's a website where people are creating their projects, or you can check the projects and join them, and there are a lot of OpenSUSE related projects there,
16:01
where everybody is actually free. You don't have to be a SUSE employee to participate as well, so you're welcome to join that. So I just took three examples, one in the UI UX space, so this is about doing a UI to upgrade OpenSUSE, and we have a UI UX team in the room as well,
16:20
there's a session later this morning at 10.45, they are doing, it's not only about code, it's also about UI UX and documentation as well, so yeah, I would encourage you to go there and see what they are doing, if you don't know what they are doing. There's a project to bring some of the visual effects libraries in PackageHub,
16:45
so that's the one on the right. And finally, one is about specific boards from a set-up box that someone wants to try to bring LIP or probably Factorion. So it's end of June,
17:00
if you have time, if you're interested, you could check the projects, you could add one of your projects there, and work together. And that's all I had for today, but I'd like to make it open as well, so if you have any questions, comments, or inputs, please, I think there's a mic in the back of the room,
17:22
or I can throw my mic to you as well, yeah, if you have questions. Do you have a question, Doug, or are you just going for coffee? Okay.
17:45
So if you do have a question, you do have to come back here because it's not wireless, and I can't bring it to you, so.
18:04
Yeah, cool. So I'll hand over to you, Doug, for some of the welcome stuff. You have to run.
18:26
No. Okay, all right, thank you, Thomas, appreciate it.