Systemd: translate dependencies service in unit files / an overview of its testsuite
No video of the event yet, sorry! Meanwhile...
systemd has been officially introduced by openSuSE since end of 2011 through the first release of openSUSE-12.1.
However a couple of the bugs opened against systemd recently shows that there are some misunderstandings about one of the basic but fundamental concept of systemd: service dependencies and orderings and how to translate such constraints into a native unit file.
This might also explain why a limited number of packages is still using the old sysV init scripts instead of migrating towards the systemd native unit file.
The first part of this short talk will try to explain simply how services are started by systemd and how to translate service dependencies and ordering contraints into a unit file.
The second part of the talk will be a short introduction to the systemd testsuite, its content, usage and extensibility.
Indeed the systemd source code also contains a test suite for checking the proper functionality of the compiled sources.
It was introduced in 2012 and has been extended since then to test for known problems in various areas.
It is useful for automatic testing of code changes and helps to provide quality assured code. systemd testsuite will be part of the SuSE Quality Assurance tests for the next SLES release and might also be become part of OpenQA.
This talk should fit in "Technology & Development" track.
- 2016 June 23 - 12:30
- 1 h
- Seminarraum 2
- openSUSE Conference 2016
- Technology & Development