Let’s take a look at two popular orchestration and configuration management frameworks. We’ll compare and contrast them as we work through some examples learning how to deploy a simple application stack that will require managing users, installing packages, writing templates, and controlling services.
Outline
- Systems Engineering Challenges -- Introduction to the problem space
- Inventory -- What do we have and what’s it doing?
- Configuration -- What is it running and how is it running it?
- Deployment -- What do we need to change to get it to run new stuff?
- Solutions
- Historical view
- Corporate offerings
- OpenSource / Free Software
- Ways to skin a cat -- Introduction to Fabric, SaltStack, and Ansible
- Communications channels -- Message Queueing vs SSH
- Execution Models
- Agent vs Agent-less
- Push vs Pull
- Imperative vs Declarative
- High level DevOps concepts
- Infrastructure as code
- Deterministic Builds/Deployments
- Eventual Convergence and Anomaly Detection
- Whiskey Tango Foxtrot is “Idempotent”
- Getting going
- Fabric
- Requirements
- Installation
- SaltStack
- Requirements
- Installation
- Configuration
- Ansible
- Requirements
- Installation
- Configuration
- Our first executions
- Scripts/Recipies/States/Playbooks
- Adding users
- Installing software
- distributing files
- Your Challenge (should you accept it)
- Deploy a web application
- python
- web server - nginx
- our application
- pyramid and dependencies
- application code
- Rinse and repeat (with a different tool/framework)
- Open discussion
- Observations
- Likes/dislikes
Everyone will need to bring a computer with an ssh client and have very basic understanding of how to operate in a Unix environment.
G. Clifford Williams is currently DevOps Practice Manager at 8ions, Inc. and is a longtime advocate of open source software, maintainer of the wempy template system and contributor to such projects as Cherokee, SaltStack, and Web2py. He provides hosting, consulting, and bootstrapping services for various startups focused on building opensource solutions.
Login to leave a comment
Hari (ഹരി)
@haricm
Clifford, What's the duration of this workshop?
G. Clifford Williams
@gcw Submitter
@haricm, The session is designed to be 6 hours in duration
Zainab Bawa
@zainabbawa
To complete the review, we need draft slides and link to a self-recorded video explaining what this workshop is about and why the audience should attend it. Also, is there link to a GitHub repo for this workshop? Please share this information, latest by Wednesday, 22 Feb.
G. Clifford Williams
@gcw Submitter
@zainbbawa, regarding github, I have not yet put together the exact curriculum for this class. I've taught both subsets and supersets of this material in the past: https://2015.eurobsdcon.org/tutorials/ (see DevOps'ing on BSD) and https://us.pycon.org/2015/schedule/presentation/331/
as well as https://2016.eurobsdcon.org/tutorials/ (see Novice to Advanced Salt on BSD). I'll put the course material specifically for this conference and put it on github after I get confirmation that the session have been approved/selected and well in advance of the event. Here is an example from a previous session: https://github.com/DevOpsing/workshop00
For workshops I tend not to produce slides as everthing is interactive and hands-on. In the repository I will include step-by-step instructions that do not break down easily into slides but the totality of the information will be available.
As for the video, my apologies but I have not had time to put one together. Is this for potential students to see or simply for the selection process?