Open Build Service - Development Roadmap
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
| Title |
| |
| Subtitle |
| |
| Title of Series | ||
| Number of Parts | 57 | |
| Author | ||
| Contributors | ||
| License | CC Attribution 3.0 Unported: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. | |
| Identifiers | 10.5446/54465 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
|
openSUSE Conference 201730 / 57
3
6
10
15
16
19
21
23
24
27
28
29
34
36
38
40
41
42
46
47
51
53
55
00:00
Open setBuildingService (economics)Software developerService (economics)Computer animationUML
00:12
Service (economics)Right angleClosed setLecture/ConferenceMeeting/Interview
00:31
Software developerOpen setBuildingService (economics)Computer animation
00:42
BitView (database)Web pageLecture/ConferenceMeeting/Interview
00:54
Service (economics)Physical systemGeneric programmingOpen setBuildingConsistencyFingerprintDistribution (mathematics)Binary codeFile formatSource codeWeb pageConsistencyMultiplication signComa BerenicesCASE <Informatik>Computer architectureRight angleService (economics)Physical systemData structureServer (computing)MereologyBuildingPoint (geometry)Computer animation
02:23
Data structureOscillationBitServer (computing)Web browserWeb 2.0Line (geometry)Data structureMereologyRuby on RailsPhysical systemCartesian coordinate systemInterface (computing)CodeProgram flowchart
03:02
Time evolutionEvoluteConnectivity (graph theory)Multiplication sign
03:16
Distribution (mathematics)MiniDiscFile formatBuildingPower (physics)ArmPowerPCFunction (mathematics)Repository (publishing)Revision controlMobile appFile formatVirtual machineInstance (computer science)Fiber bundleMultiplication signComputer architecturePowerPCRepository (publishing)Function (mathematics)Medical imagingInternet service providerDistribution (mathematics)VirtualizationBuildingComputer animation
04:47
User profileWeb pageSource codeRevision controlView (database)Computer fileMultiplicationOpen setBranch (computer science)Repository (publishing)Public key certificateKey (cryptography)AlgorithmBuildingService (economics)Distribution (mathematics)Computing platformSoftware developerACIDComputer-generated imagerySource codeComputer fileRow (database)Profil (magazine)Web pageResultantInstance (computer science)Medical imagingDescriptive statisticsKey (cryptography)Template (C++)Dot productComputer clusterElectronic mailing listXMLComputer animation
06:40
Web 2.0
06:57
DivisorMathematicsSoftware testingSuite (music)Human migrationIndependence (probability theory)Computer fileState of matterSoftware frameworkOpen setGroup actionMeasurementPhysical systemChi-squared distributionMessage passingDigital filterEvent horizonFrequencyDecimalText editorVisual systemSoftware testingProjective planeMedical imagingSuite (music)VideoconferencingMultiplication signDebuggerVisualization (computer graphics)Game controllerComputer fileEndliche ModelltheorieFrequencyStudent's t-testCodeSoftware frameworkCategory of beingPhysical systemView (database)EmailMessage passingStatisticsMereologyInstance (computer science)NumberOpen setSemantics (computer science)Computer configurationAttribute grammarBus (computing)Right anglePole (complex analysis)CASE <Informatik>Condition numberWeb 2.0Front and back endsTwitterBuildingElectronic mailing listUnit testingFile formatWeb pageComputer animation
12:04
Service (economics)Point (geometry)Bit
12:20
Service (economics)Open setBuildingContinuous integrationNumberDistribution (mathematics)Repository (publishing)SoftwareSelf-organizationLevel (video gaming)Associative propertyService (economics)NumberWeb 2.0Continuous integrationComputer animation
13:48
Cartesian closed categoryHypermediaMeeting/InterviewComputer animation
Transcript: English(auto-generated)
00:09
Hello, everybody. We are here to talk about the open build service roadmap, more or less, talking about the past, and somehow about the present, and also I hope that the close future, right?
00:26
So we are Moises and David. We work together in the OBS team that is called Build Service Team, right? We work from Canary Islands. So we are here now just for this, the conference, I mean.
00:42
I want to show you a little bit, an overview of OBS for who doesn't know how it works or what it does. So we are now taking a look at the phrase that we have in the web page for the open service that says that we are a generic system that can build and distribute binary packages
01:06
from sources in a reproducible, automatic and consistent way, right? So this is a very big phrase, right? So I can show you how it works, more or less.
01:21
When you are just a packager along in your house and you want to package something and distribute to some users out there, you have your source and then you have to build something, maybe in the simple case for one architecture, one format of the package for one distribution, this is just one build.
01:40
If you change something, you only need to rebuild and send it, right? But what if you want to have more users there and then you have to, I don't know, have more distributions, more architectures, and more package formats, right? So that will be a lot. You will get crazy, right? Because each time you change a comma because you are back fixing something, then you have
02:05
to build like 30 things. So that's why OBS is to the rescue. We do it automatically, we can reproducibly do it, so done. You are winning. You don't have to build the things by hand.
02:21
That's the good point of it. We are talking about now the structure a little bit, because the OBS server part is divided in two applications right now, one in Ruby on Rails, the other in Perl. If you are a user, you can deal with our system by the web UI, so using a browser,
02:41
or you can have using the common line interface that is OSC written in Python, right? This deals with the API. It's actually separate code in our code base that we want to already mix, but we are on it. Those talk to the bacon and get the builds done and the things out.
03:02
Okay, now we are sharing the time, so David, it's your turn. Hi, everybody. We are talking about the evolution of the components of OBS. So, at the beginning, we support, of course, your own distributions, and also all of those.
03:22
That's with us in your own public OBS instance. We support and we update all the versions of all of those, and we distribute to all people. So, now we support the package format like RSpec from RPM, this from Devia,
03:46
and also like KV and live builds. After, we support also Colax and RPM package builds, and from later also AppImage and Snap.
04:05
The support architecture, in your own instance, for a long time, we support almost 40 architectures, and now we only have 10 of them. The most of them, you recognize are like Intel, ARM, and PowerPC.
04:27
The outputs, we have packages, repositories, and also KV. KV of course supports providers, most of them like ISO, virtual machines, Dockers,
04:41
and we also provide bundles like AppImage and Snap. So the last main feature, we have Moises. Yeah, again here. Then talking about the last features in the last year, right? So, we have improved a list for KULO that is here right now.
05:05
The loading of the profile page. Before it was many lists there that loaded all the records all together and then show it in JavaScript, then you can package it. Now it is server-side, so you only have to load the things that you need, right?
05:21
Talking about a big, big feature, because it is KV, you can have build descriptions and build from it, so you already know maybe KV. Also we have the multi-build thing that is popping out in the UI now. Now you can have in one source container a description of which files are creating
05:46
which binary packages out there. So you can see in the right side that you can have both build results, so you can see what is going on with each. Also the GPG key and the SSL cert, you can now load it by the UI, so you have
06:05
a dialogue here, and if you have both or each, you can see a button for the loading. This is something new also, and I don't know if in our public instance it is shown now, because there are some dots there, but we have image templates, so that means
06:24
that you have a package with all set up with a KV thing there, and then you can just branch from it and work and put your stuff on. So you can just branch from those templates there and create your appliance, right?
06:40
Now David, it is your turn. Okay, the future. We have a workshop to think about what we want to do in the future, what we want to change, what we want to achieve. So the first one is refactor and change the web UI. Why? Because it's old.
07:00
Not that we showed the web UI and we saw it's old-fashioned, it's like, why? So for first, we have to mirror the tests, tweets. Now right now we have many tests and we want to change to RSpec. Not because with many tests it's bad, but we have smoke tests, where you only click
07:23
and visit the page and say, oh, it worked fine. You have huge files with huge tests, so maybe a gazillion of code then, and also they only test a workflow. They don't do me tests, sorry, unit tests or controller tests.
07:43
Only workflow and that's enough. And it needs a backend to run these tests. RSpec support is more modern, but not more better, but it's new. We will try another smoke test, you have small file with test property done or property
08:06
reported in these files, and independent tests and no need to back end, thanks to the VCR. Now, we also try to increase the coverage with one of your goals, because right now
08:24
we have 89% and we try to reach maximum possible. The front end, we have some new technologies like Vue, React, maybe also do it in vanilla
08:42
JavaScript, we don't know. And also new frameworks from CCS like Miriam, Semantic UI, Bulma, Foundation, we don't know. We have a look at them and when we start we saw one of them or something new appear and we will see.
09:00
Why? Like I said before, it's old-fashioned, we have old frameworks from GS and old frameworks from CCS like Bento, and because it's not responsive. We want now also introduce a health monitoring like InfluxDB to measure the numbers of users
09:22
we have, also the open and closed reviews, the package that saved it, updated, to have a collection of statistics and to have more data than now is my part.
09:42
We have in the format days, we have Hermes and on top of it a notification system, and we want someone to get rid of this, so it's gone right now. Now we want to have another notification system, better than just sending emails, and that's
10:01
why we are going to base on Ruby and Q, thanks to Kulo again, for having a list push a message instead of polling, because now time open QA, for instance, just polls there. Also we want to have better filtering for just not saying I want to be just notified
10:21
if something pops up in a package that I'm entering on, but also I can say only in that project or I want to have it in the case of something, so many conditionals and many other kind of filtering, right? Besides that, we have a thing about having frequency like before, and also having a digest
10:43
instead of just sending a notification each time, so something that maybe once a day have all the things inside and then you just read them. We want to have more channels even, so not only email or SS, so maybe others we have to figure out what, but the good thing is that based on a message bus we can just
11:04
talk to it, other tools, not only for people, right? And this is one big thing for us is just creating something that helps people to deal with the kivy files, why? Because this is an XML, you don't know the options that you can have in each attribute,
11:24
so the values that you are doing well or not, so you don't have any clue if you don't read the documentation, right? So we want to help people to do it easily, supposedly, so we are doing something visual inside the OBS.
11:40
And this is pretty new, it's just because before we had kivy creating Docker images but we wanted or needed just native support for kivy Docker files, right? So we can now create, I hope in no time, building native Dockers from Docker files.
12:04
And that's it. Maybe we are now talking about a little bit, not talking about, at least pointing to other talks that are holding here for related somehow to OBS. So now we are in the OpenBill service realm up, for sure you have lost the reposible
12:26
bills from Bernard because it passed or not, maybe. I encourage you to go to the continuous integration with OpenBill service of Marmuel and Christian
12:41
and also to the SUSE package hub from Wolfgang. Also on Saturday we have all of those. I also encourage you to go to OBS number by Anna and of course of anchor, it's very interesting and also by the OBS package, OBS amplions, a talk and also a workshop
13:12
done by Simon and Adrian and also by Wolfgang, the next one and Alex.
13:21
And also we have another one on Sunday about packaging by Simon and reposible discussions by Bernard. So, any questions? We are finished, right? If you have any questions, if not, we can go lunch.
13:46
No? One, two, three, then go. Thank you so much. Thank you very much.