DevOps Tools Engineer

Unternehmen auf der ganzen Welt implementieren zunehmend DevOps-Praktiken, um die tägliche Systemadministration und Softwareentwicklung zu optimieren. Infolgedessen stellen branchenübergreifende Unternehmen IT-Experten ein, die DevOps effektiv einsetzen können, um Lieferzeiten zu verkürzen und die Qualität bei der Entwicklung neuer Softwareprodukte zu verbessern.

Um diesem wachsenden Bedarf an qualifizierten Fachleuten gerecht zu werden, hat das Linux Professional Institute (LPI) die DevOps Tools Engineer-Zertifizierung des Linux Professional Institute entwickelt, mit der die Fähigkeiten überprüft werden, die für die Verwendung der Tools erforderlich sind, die die Zusammenarbeit in Workflows während der gesamten Systemadministration und Softwareentwicklung verbessern.

Bei der Entwicklung der DevOps Tools Engineer-Zertifizierung für das Linux Professional Institute überprüfte LPI die DevOps Tools-Landschaft und definierte eine Reihe grundlegender Fähigkeiten für die Anwendung von DevOps. Daher konzentriert sich die Zertifizierungsprüfung auf die praktischen Fähigkeiten, die erforderlich sind, um in einer DevOps-Umgebung erfolgreich zu arbeiten - und auf die Fähigkeiten, die für die Verwendung der bekanntesten DevOps-Tools erforderlich sind. Das Ergebnis ist eine Zertifizierung, die die Schnittstelle zwischen Entwicklung und Betrieb abdeckt und für alle IT-Experten relevant ist, die im Bereich DevOps tätig sind.

Die Schulung setzt sich aus 2 Teilen (nur komplett buchbar) à 4 Tage zusammen, in denen der Trainer die vom LPI für die Prüfung vorgegebenen Inhalte (siehe weiter unten) mit den Teilnehmenden aufarbeitet und diese damit in die Lage versetzt, die Prüfung 701 des LPI bestehen. zu können.
Diese Prüfung ist kein Bestandteil der Schulung, es kann jedoch auf Wunsch ein Prüfungsvoucher mitbestellt werden und die Prüfung in einem Pearson VUE Testzentrum abgelegt werden. Prüfungssprachen: Englisch, Japanisch.

Voraussetzungen

Grundsätzliche Kenntnisse in DevOps-bezogenen Bereichen wie Software Engineering und Architektur, Container- und Maschinenbereitstellung, Konfigurationsmanagement und Monitoring.
Die Inhalte zum Beispiel unserer Linux Administrationsschulung bzw LPI-1-relevante Themen (LPI 1 Vorbereitung) sollten nicht fremd sein.

Inhalt

701: Software Engineering

701.1 Modern Software Development (weight: 6)

Key Knowledge Areas:

  • Understand and design service based applications
  • Understand common API concepts and standards
  • Understand aspects of data storage, service status and session handling
  • Design software to be run in containers
  • Design software to be deployed to cloud services
  • Awareness of risks in the migration and integration of monolithic legacy software
  • Understand common application security risks and ways to mitigate them
  • Understand the concept of agile software development
  • Understand the concept of DevOps and its implications to software developers and operators

The following is a partial list of the used files, terms and utilities:

  • REST, JSON
  • Service Orientated Architectures (SOA)
  • Microservices
  • Immutable servers
  • Loose coupling
  • Cross site scripting, SQL injections, verbose error reports, API authentication, consistent enforcement of transport encryption
  • CORS headers and CSRF tokens
  • ACID properties and CAP theorem

701.2 Standard Components and Platforms for Software (weight: 2)

Key Knowledge Areas:

  • Features and concepts of object storage
  • Features and concepts of relational and NoSQL databases
  • Features and concepts of message brokers and message queues
  • Features and concepts of big data services
  • Features and concepts of application runtimes / PaaS
  • Features and concepts of content delivery networks

The following is a partial list of the used files, terms and utilities:

  • OpenStack Swift
  • OpenStack Trove
  • OpenStack Zaqar
  • CloudFoundry
  • OpenShift

701.3 Source Code Management (weight: 5)

Key Knowledge Areas:

  • Understand Git concepts and repository structure
  • Manage files within a Git repository
  • Manage branches and tags
  • Work with remote repositories and branches as well as submodules
  • Merge files and branches
  • Awareness of SVN and CVS, including concepts of centralized and distributed SCM solutions

The following is a partial list of the used files, terms and utilities:

  • git
  • .gitignore

701.4 Continuous Integration and Continuous Delivery (weight: 5)

Key Knowledge Areas:

  • Understand the concepts of Continuous Integration and Continuous Delivery
  • Understand the components of a CI/CD pipeline, including builds, unit, integration and acceptance tests, artifact management, delivery and deployment
  • Understand deployment best practices
  • Understand the architecture and features of Jenkins, including Jenkins Plugins, Jenkins API, notifications and distributed builds
  • Define and run jobs in Jenkins, including parameter handling
  • Fingerprinting, artifacts and artifact repositories
  • Understand how Jenkins models continuous delivery pipelines and implement a declarative continuous delivery pipeline in Jenkins
  • Awareness of possible authentication and authorization models
  • Understanding of the Pipeline Plugin
  • Understand the features of important Jenkins modules such as Copy Artifact Plugin, Fingerprint Plugin, Docker Pipeline, Docker Build and Publish plugin, Git Plugin, Credentials Plugin
  • Awareness of Artifactory and Nexus

The following is a partial list of the used files, terms and utilities:

  • Step, Node, Stage
  • Jenkins SDL
  • Jenkinsfile
  • Declarative Pipeline
  • Blue-green and canary deployment

702: Container Management

702.1 Container Usage (weight: 7)

Key Knowledge Areas:

  • Understand the Docker architecture
  • Use existing Docker images from a Docker registry
  • Create Dockerfiles and build images from Dockerfiles
  • Upload images to a Docker registry
  • Operate and access Docker containers
  • Connect container to Docker networks
  • Use Docker volumes for shared and persistent container storage

The following is a partial list of the used files, terms and utilities:

  • docker
  • Dockerfile
  • .dockerignore

702.2 Container Deployment and Orchestration (weight: 5)

Key Knowledge Areas:

  • Understand the application model of Docker Compose
  • Create and run Docker Compose Files (version 3 or later)
  • Understand the architecture and functionality of Docker Swarm mode
  • Run containers in a Docker Swarm, including the definition of services, stacks and the usage of secrets
  • Understand the architecture and application model Kubernetes
  • Define and manage a container-based application for Kubernetes, including the definition of Deployments, Services, ReplicaSets and Pods

The following is a partial list of the used files, terms and utilities:

  • docker-compose
  • docker
  • kubectl

702.3 Container Infrastructure (weight: 4)

Key Knowledge Areas:

  • Use Docker Machine to setup a Docker host
  • Understand Docker networking concepts, including overlay networks
  • Create and manage Docker networks
  • Understand Docker storage concepts
  • Create and manage Docker volumes
  • Awareness of Flocker and flannel
  • Understand the concepts of service discovery
  • Basic feature knowledge of CoreOS Container Linux, rkt and etcd
  • Understand security risks of container virtualization and container images and how to mitigate them

The following is a partial list of the used files, terms and utilities:

  • docker-machine

703: Machine Deployment

703.1 Virtual Machine Deployment (weight: 4)

Key Knowledge Areas:

  • Understand Vagrant architecture and concepts, including storage and networking
  • Retrieve and use boxes from Atlas
  • Create and run Vagrantfiles
  • Access Vagrant virtual machines
  • Share and synchronize folder between a Vagrant virtual machine and the host system
  • Understand Vagrant provisioning, including File, Shell, Ansible and Docker
  • Understand multi-machine setup

The following is a partial list of the used files, terms and utilities:

  • vagrant
  • Vagrantfile

703.2 Cloud Deployment (weight: 2)

Key Knowledge Areas:

  • Understanding the features and concepts of cloud-init, including user-data and initializing and configuring cloud-init
  • Use cloud-init to create, resize and mount file systems, configure user accounts, including login credentials such as SSH keys and install software packages from the distribution’s repository
  • Understand the features and implications of IaaS clouds and virtualization for a computing instance, such as snapshotting, pausing, cloning and resource limits.

703.3 System Image Creation (weight: 2)

Key Knowledge Areas:

  • Understand the functionality and features of Packer
  • Create and maintain template files
  • Build images from template files using different builders

The following is a partial list of the used files, terms and utilities:

  • packer

704: Configuration Management

704.1 Ansible (weight: 8)

Key Knowledge Areas:

  • Understand the principles of automated system configuration and software installation
  • Create and maintain inventory files
  • Understand how Ansible interacts with remote systems
  • Manage SSH login credentials for Ansible, including using unprivileged login accounts
  • Create, maintain and run Ansible playbooks, including tasks, handlers, conditionals, loops and registers
  • Set and use variables
  • Maintain secrets using Ansible vaults
  • Write Jinja2 templates, including using common filters, loops and conditionals
  • Understand and use Ansible roles and install Ansible roles from Ansible Galaxy
  • Understand and use important Ansible tasks, including file, copy, template, ini_file, lineinfile, patch, replace, user, group, command, shell, service, systemd, cron, apt, debconf, yum, git, and debug
  • Awareness of dynamic inventory
  • Awareness of Ansibles features for non-Linux systems
  • Awareness of Ansible containers

The following is a partial list of the used files, terms and utilities:

  • ansible.cfg
  • ansible-playbook
  • ansible-vault
  • ansible-galaxy
  • ansible-doc

704.2 Other Configuration Management Tools (weight: 2)

Key Knowledge Areas:

  • Basic feature and architecture knowledge of Puppet.
  • Basic feature and architecture knowledge of Chef.

The following is a partial list of the used files, terms and utilities:

  • Manifest, Class, Recipe, Cookbook
  • puppet
  • chef
  • chef-solo
  • chef-client
  • chef-server-ctl
  • knife

Topic 705: Service Operations

705.1 IT Operations and Monitoring (weight: 4)

Key Knowledge Areas:

  • Understand goals of IT operations and service provisioning, including nonfunctional properties such as availability, latency, responsiveness
  • Understand and identify metrics and indicators to monitor and measure the technical functionality of a service
  • Understand and identify metrics and indicators to monitor and measure the logical functionality of a service
  • Understand the architecture of Prometheus, including Exporters, Pushgateway, Alertmanager and Grafana
  • Monitor containers and microservices using Prometheus
  • Understand the principles of IT attacks against IT infrastructure
  • Understand the principles of the most important ways to protect IT infrastructure
  • Understand core IT infrastructure components and their the role in deployment

The following is a partial list of the used files, terms and utilities:

  • Prometheus, Node exporter, Pushgateway, Altermanager, Grafana
  • Service exploits, brute force attacks, and denial of service attacks
  • Security updates, packet filtering and application gateways
  • Virtualization hosts, DNS and load balancers

705.2 Log Management and Analysis (weight: 4)

Key Knowledge Areas:

  • Understand how application and system logging works
  • Understand the architecture and functionality of Logstash, including the lifecycle of a log message and Logstash plugins
  • Understand the architecture and functionality of Elasticsearch and Kibana in the context of log data management (Elastic Stack)
  • Configure Logstash to collect, normalize, transform and store log data
  • Configure syslog and Filebeat to send log data to Logstash
  • Configure Logstash to send email alerts
  • Understand application support for log management

The following is a partial list of the used files, terms and utilities:

  • logstash
  • input, filter, output
  • grok filter
  • Log files, metrics
  • syslog.conf
  • /etc/logstash/logstash.yml
  • /etc/filebeat/filebeat.yml

Kurszeiten

Wer möchte, reist bis 22 Uhr am Vortag an und nutzt den Abend bereits zum Fachsimpeln am Kamin oder im Park.

An den Kurstagen dann von 9-18 Uhr (mit 2 Kaffee- und 1 Mittagspause) etwa 60% Schulungen und 40% Übungen. Selbstverständlich arbeitet jeder Teilnehmer am von uns gestellten Notebook oft parallel zum Referenten mit.

Anschließend Abendessen und Angebote für Fachsimpeln, Ausflüge uvm. Wir schaffen eine Atmosphäre, in der Fachleute sich ungezwungen austauschen. Wer das nicht will, wird zu nichts gezwungen und findet auch jederzeit Ruhe.