| 47 | | 1. Hands-On with Chef and Ansible. |
| | 47 | ''Agenda and speakers subject to change.'' |
| | 48 | |
| | 49 | 1. Motivation: Why use CM tools for experimentation? |
| | 50 | |
| | 51 | ''Automation is very important for repeatability and experimenter sanity but install scripts and custom images have drawbacks. As an alternative we will explore existing tools from the wider sysadmin/operations communities.'' |
| | 52 | |
| | 53 | ''Will also discuss best practices and include examples as appropriate.'' |
| | 54 | 2. Overview of existing CM tools and their suitability to experimentation. |
| | 55 | |
| | 56 | ''In addition to using version control (git, svn, cvs) to keep files and documents safe, there are four popular configuration management tools (Puppet, Chef, Ansible, and Salt) and at least one software deployment tool (Fabric).'' |
| | 57 | |
| | 58 | ''Someone experienced in each of these tools will briefly describe the tools and discuss it’s applicability to doing experiments.'' |
| | 59 | |
| | 60 | Planned speakers are: |
| | 61 | * Puppet - Tim Upthegrove, GPO. |
| | 62 | * Chef - Max Ott, NICTA |
| | 63 | * Ansible - Tim Upthegrove, GPO. |
| | 64 | * Salt - TBD |
| | 65 | * Fabric - TBD |
| | 66 | |
| | 67 | 3. Hands-On with Chef and Ansible. |
