 So project infrastructure for me, it's like the bread and butter of every day working with Osmo comms. So I am Probably going to miss a few details if you have any questions or stuff that is only obvious to me and not to you then Please interrupt or ask afterwards. So I'm going to talk about your typical project infrastructure mating lists wiki issue tracking continuous integration version control patch review Our manuals and our nightly bills last but not least So the mailing list For everything I will post a wiki link Which is probably more for later reference. I also have the pages pulled up here next to it so We can if you have questions we can have closer look So basically the archives are public as always you should be subscribed and We have lots of mailing lists, but the main activity is on the open BSC the traditional one We have a separate gprs one but still most of the discussion is happening here in open BSC and I don't know why I put this here, but I think it should go here. So we have some some rules Yeah, I mean have a good subject line. Don't just quote the whole mail Don't send HTML Start a new thread for a new topic Don't say something like this mail shall not be read by people not liable to our company rules, whatever no pseudo legal disclaimers Stay on topic of the mailing list don't spam and have a correct time so that our mail logs Work out and we don't get like your mail always at the bottom into the far future or something like that So that's pretty basic and that's what your typical mail looks like I don't know just picked a random one and shortened it a bit. So we have a Clear a subject line. It's sent to open BSC and Harold on April 1st Asking for a longer Line width, but it wasn't an April fools actually. So now we decided for a hundred and twenty lines of code width being permissible Yeah So that's the mailing list that should be obvious, but so if you have a question come to open BSC at lists.osmocom.org and we will most probably help you So the wiki is at osmocom.org also reachable at projects.osmocom.org It's your standard red mine we use the red mine as wiki and as issue tracker and And how to get to the juicy wiki documentation is You basically pick a project the cellular Cellular infrastructure is the umbrella thing for most other things and then you just click on wiki and This cellular infrastructure main wiki page would be the main starting point for it almost everything and You can also pick other projects. There are many as You might know so wiki is an ancient Inuit word for hopelessly outdated. So You can register easily, but you can't edit right away simply because we Don't want to allow anyone to spam right away, but I can assure you if you just ask We will just grant you wiki editing rights and you can partake and you can contribute like that Yeah, you can ask publicly on open BSC or probably mail one of us privately at sysmocom as well So don't hesitate Join us if You see outdated or erratic information the Jenkins is yes We still saw lots of wiki spam. That's why we introduced this but Interestingly, there seems to be very little people trying to spam the issue tracker So you can report issues just by self registering you yourself to red mine So yeah, you're allowed to post new issues in the issue tracker, but you're not able to edit the wiki Unless you ask for it first. So for reporting issues. There's no special permission required. I Hope no spammers are listening on the live stream Damn disclose. All right So Jenkins first of all, it's for us to check whether we introduce new bugs Of course, that's limited because we can only run the test suit and That's why we have In an aside we have the Osmo GMS GSM tester being developed where we actually have hardware BTS and modems and we set up all the software to work together and really Physically send an SMS to a modem But the Jenkins basically just the does the make check of of our projects and verifies that that still works and also makes this check and Maybe Debian packages possibly So It tests what gets into the master branch But even before that it tests every patch that we post for review So you will see that later on Garrett. We will have a little tick mark for a patch that passed the make check but also very importantly the Jenkins updates are manuals as Soon as we edit it it basically goes online right away That's why it always has this big draft watermark in the back. So, you know, it's recent and Also, the nightly packages that are very important for new users They also get built every night by our Jenkins and they get published right away So that's what your Jenkins looks like It just happened to click on the open VSC tab and you see our projects being built and then you see This is one odd job that hasn't actually run for eight months. So Take a look at that before you assert that something is wrong. So this is just a legacy the important ones are succeeding but Taking a look at the open VSC. You see that occasionally we do have unfortunately still some odd failures just sporadic if you click on it or actually I clicked on the bottom one and Pick the hold on console output, then this is our or you can investigate the errors. Everyone should know this basically it's very Basic knowledge, but this is just for interest. This is our sporadic failure that we see every now and then it's the broken pipe and one of the Vty tests. Yeah, we also test the Vty input and output So much for the Jenkins Version control is skid obviously and So by the example of lip Osmo core, that's our main upstream lip Osmo core git repository And we also have lots of other projects each in the same pattern. Here's a screenshot of the list and At git osmo com.org you can also view the details like I just showed the logging code from lip Osmo core and If you contribute patches take a look at these websites the coding standards and You would actually submit the patch on Garrett and To get started with Garrett we have this link not Something we should look into now That's just a screenshot of the Garrett. Don't worry about what is listed here. It's just a bunch of patches waiting for review and the Verified tick marks from the Jenkins and these ones failed They still need a patch up and volts plus one as soon as it gets plus two like this one with two tick marks It could be submitted right away and could be merged to master and Right Very interesting source of Quite formal information are the Osmo com manuals like the wiki is more like how do you build from source? How do you what do you need to do this or that like? recipes and so on the Osmo com manuals are your real juicy bits of Definitive documentation on what do the protocols do what VTY commands exist? How how do things connect and we always have the latest manuals at this FTP Osmo com org docs latest and Here you see the bunch of them if you can see it the recent most recent addition the Osmo GSM tester manual still undergoing Development the Osmo BTS user manual the description of what the abyss interface can do VTY reference manuals The NITB user manual so we should soon also see an Osmo MSC user manual probably SGSN What have you PCU take a look there? And that's the draft watermark. I was talking about that's what the manuals generally look like an index clickable references to Sections and to bibliography graphs and You could build from source, but it's Kind of hard for a beginner the easiest and fastest way to get started with with Osmo comm is to go check out the nightly bills we provide Debian packages and Ubuntu the bills are named Xubuntu, but I'm not actually sure if that's the Xfce flavor of Ubuntu or Whether it's really just compatible with your main Ubuntu. Do you know max? Although Ubuntu flavor so the X is for all not for Xfce. Okay, I'll see so until recently we also had Debian 7 but it got disabled and Since yesterday we also named these two on the wiki page for the nightly bills before they were just missing there so You noticed recently and yeah The open Susie page for building Yeah, we use the open Susie build service despite those being Debian packages So there that's what they are packages for lip Osmo ables lip Osmo native lip Osmo ssb Osmo core and so on the libraries Osmo HLR open BSC containing all of the NITB and so on and we're planning to also include 3g packages Like Osmo MSC and IUH and all that stuff as Debian packages soon for I 586 or 32 bit and a 64 bit platform each Some stuff failed there. We should look into that probably so What was I writing here? Oh? Yeah, that's just some more detail. You will find all the details on how to use them on the wiki page Refer to the slides later on Right, so I am through this pretty fast I hope I didn't miss anything or please remind me of Things I should be adding to this information. Yes It says Osmo com GSM manuals. Are you planning to include manuals for 3g also? Yeah, I guess the GSM is historical Also the Osmo GSM tester says GSM, but we will probably include nano 3g soon You only have x86 architecture not only not arm Well, we have builds for the sysmo BTS specifically, but that's from it's from the sysmo com Infrastructure, so that's not really Osmo Osmo com Built but that that's sysmo com provides that openly Okay, thanks Any more questions? No Okay, well then thanks Nils. Yeah pleasure