While we all probably think we're doing all the DevOps stuff the right way (and we do, don't we?), drift happens.
Even as an experienced Terraform user, as your infrastructure team and codebase grows, it often becomes harder to track drift.
I'll share here war stories from different teams, and show common pitfalls of popular commands we use when we want to know what's changed in our infrastructures.
Automate your infrastructure with the same CI/CD tooling that your applications go through
This talk will do a deep dive on how Ansible can be used to assess the operational state of your IT infrastructure (especially network appliances) and effectively take remediation actions as required
“We are all YAML engineers now” as Bob Walker said in 2018 in Ghent. So we now need something to manage these millions of lines of YAML.
There’s the “Kubernetes application management tools” list by Bryan Grant with over 120 tool aiming at config management for Kubernetes. This area is evolving fast, and as k8s users we need some guidance to make informed decisions on what to use.
In this talk I’ll describe the problem I need to solve and take a look into what we can learn from the previous generation of cfg mgmt tools. Then, will show some of the new tools and methods. Will not go into details of each solution, but rather compare different approaches and discuss which is good for specific needs.
Small businesses and non-profits may opt for Platform-as-a-Service solutions such as Heroku to avoid the operational burden of managing their own infrastructure. However, PaaS solutions quickly become cost-prohibitive for compute- or memory-intensive applications. In this talk, I’ll demo an open source infrastructure automation toolchain based on Ansible, Github Actions, Vagrant, Packer, Terraform, and Sentry. Once instrumented, this toolchain incurs a $0 recurring cost and can be safely and trivially scaled up. Each component of the toolchain requires minimal operational expertise and is managed through a UI. State-change notifications are routed to email or a Slack channel, ensuring everyone stays on the same page. Test, deploy, monitor, and scale transparently, and with confidence!
You need to migrate some workloads from a private datacenter to public cloud. The result? The unavoidable hybrid environment. How do you observe traffic and mitigate risky changes to each system? In this talk, I’ll discuss how you can supercharge your cloud migrations with a combination of network automation for your datacenter and a service mesh across environments.
The "pet vs cattle" thing is getting pretty long in the tooth, but the one thing one keeps hearing is that the management layer somehow always remains a pet.
While there is certainly some truth to that - you don't want to rebuild your management plane every day - wouldn't it be cool if you could?
Container registries are becoming an important source of software distribution.
Why package content in a container image?
A container image includes an assorted collection of software - often hundreds of software components. This format facilitates use of the software, because a complete set of the needed components are delivered as a single unit.
In this talk we look into how to ship content regardless of how it is packaged (rpm, python, ansible roles) in a container image and build the image with just one single tool - Pulp3.
With Pulp3 you will be able to take advantage of software distribution using the container first strategy :
- Containerize your application: build and run application in a container;
- Build execution environment images - which provide security features such as isolated execution and integrity of applications;
- Cache the content - allow container images to build without relying on external infrastructure by caching(or permanently storing) the application and dependencies.
Pulp helps you fetch, upload, organize, and distribute software packages.
With Pulp 2 approaching EOL and Pulp 3 being more stable than before, we strongly encourage you to move to Pulp 3. It might be a big deal if you have a large setup and a lot of carefully curated content and repositories.
To make it easy for you, we'd like to introduce a plugin which allows you to migrate from Pulp 2 to Pulp 3 smoothly and without recreating everything from scratch.
This talk will demo the setup and features of an on-premise software for storing, mirroring, and distributing Ansible Collection and Role content. This is analogous to an on-premise version of galaxy.ansible.com. To get up and running quickly, we’ll be using a pre-built container with pulp_ansible (https://pulp-ansible.readthedocs.io/) and (https://github.com/ansible/galaxy_ng/).
Infrastructure as Code (IaC) is an approach that takes proven coding techniques used by software systems and extends it to infrastructure. It is one of the key DevOps practices that enable teams to deliver infrastructure, and the software running on it, rapidly and reliably, at scale.
In this presentation, we will look at Principles, Patterns, and Practices for Effective Infrastructure as Code that have helped me and the teams I have worked with over the years. We will look at anecdotes about deploying & operating infrastructure and applications in production.
How to compose the configuration and secrets of microservices taking into account various variables without dying in the attempt.
luster API is a Kubernetes sub-project focused on providing declarative APIs and tooling to simplify provisioning, upgrading, and operating multiple Kubernetes clusters.
Cluster API provides clusterctl, which can be configured with environment variables and allows the generation of Kubernetes manifests that describe your workload clusters.
While this provides a great on-boarding experience, managing and wrangling more YAML isn't something we're all yearning to do.
Fortunately, there's a better way.
Introducing Cluster API bindings for TypeScript, Go, and Python.
In this talk, I'll introduce you to managing Cluster API through your favourite programming languages.
Transform Release Management role from System administration to software development for Release operations thru GitOps practices
How we manage Facebook's desktop Linux fleet, and how it is positioned as a way to drive features into our server fleet.
Currently, you can provision individual servers very well with foreman / katello and configure them using Ansible, Puppet or Salt. However, modern applications are composed of different services that are operated on separate servers and are connected to each other.
This presentation introduces the new plugin foreman_acd, which allows the orchestration of entire interconnected applications.