Program

opsi-Basics

Karsten Köpke, uib gmbh

First steps with opsi. Basics for a successful start in operating system and software distribution with opsi.

    opsi Mac Support

    Detlef Oertel, uib gmbh

    opsi support for MacOS

      Monitoring with opsi and icinga2

      Thomas Trapp, uib gmbh

      Monitoring of opsi clients and opsi servers

        Features of the opsi-configeditor

        Rupert Röder, uib gmbh

        Even if the course has been set for a switch to a web-based solution: In recent years, the opsi-configeditor has grown to include numerous new functions that make the opsi admin’s life easier.

          Controlling the sequence of product installations

          Bardo Wolf, uib gmbh

          A classic feature of opsi, which is used to ensure a required sequence of installations, are the product priorities and the product dependencies.

          The workshop will present how they work and how their effect can be viewed. However, if the means they offer are not sufficient, for example because the version of software installed on a computer should also be taken into account or because an uninstallation should be enforced, the opsi product data must be queried directly in the installation script and the logic for enforcing a sequence must be implemented.

          The workshop shows how it works.

            Gitlab CI/CD for opsi package maintainer

            Erol Ülükmen, uib gmbh

            opsi packages evolve parallel to the software they distribute and the platform they run on. Just as in software development, the need to use versioning tools such as GIT automatically arises in a packaging team.

            Once the need has been identified, the first questions arise: What exactly should be versioned? Above all, what to do with large binaries? Ultimately, the question of the right and appropriate workflow is also a key issue. Once these hurdles have been overcome, the right tooling in the direction of CI/CD (continuous integration/continuous deployment) makes it possible to automate a lot more than just scripting.

            This workshop is divided into two parts. The first part consists of the basic Git strategy for opsi packages. The second part of the workshop will deal with the integration of CI/CD into the workflow. For this workshop, gitlab (gitlab.com) will be used as an example. However, the concepts from this workshop are also possible with other toolchains and products.

              Backup strategies with Bareos

              Jörg Steffens, Bareos Gmbh & Co KG

              Bareos is an open source backup solution for a whole range of client platforms (Linux, Windows, MacOS, FreeBSD, AIX, HP-UX, Solaris, VMware, oVirt, …). Backups are made to hard disk, tape drives or cloud storage (S3).

              This workshop gives an overview of Bareos. At the end of the workshop, participants should have a running backup system with web frontend and 1-2 clients set up in their virtual Linux environment.

                09:00

                Erol Ülükmen, uib gmbh

                Opening opsiconf 2020

                09:15

                Thomas Besser, KIT / Jens Boettge, MPI / Detlef Krummel, GEI

                opsi 4 institutes

                10:00

                Detlef Oertel, uib gmbh

                Experiences and requirements for packaging (best practice presentation/discussion)

                11:15

                Anna Sucher, uib gmbh

                Project report new opsi-Webgui

                13:00

                Mathias Radtke, uib gmbh

                Secureboot friend or foe?

                13:30

                Jörg Steffens, Bareos GmbH

                Backup with Bareos

                14:00

                Detlef Oertel, uib gmbh

                opsi for MAC

                15:00

                Erol Ülükmen, uib gmbh

                opsi 4.2 What’s coming, what’s going…

                Impressions from 2020