# Ansible Fest Talk: Deploying AAP 2.2

Speakers:
* Yanis Guenane
* Christian Adams

## Overall notes:
* don't rush
* present who we are ~ 1 min.
* closing remarks
* no time for demos, ~10-12 slides

Synopsis: How best to deploy and update Ansible Automation Platform 2.2

### Where are we coming from?
* Ansible Tower only

### Where are we going to?
* Controller
* Hub
* Service Catalog

### What do these components provide? Why?
* Automation Controller - central, RBAC controlled, console for launching ansible playbooks as jobs
* Automation Hub - console for managing content used by ansible playbooks (roles, collections, Execution Environments)
* Service Catalog - form based console enabling non-technical to run jobs in Automation Controller to satisfy business tasks

### How can I deploy them?
* VM
* Operator
* maybe show a decision flow chart here. pros and cons, what is right for me? what is available in house?
* VM-based
* Operator (if you have ocp and gitops), con, does not include Service Catalog yet.

GitOps? Perhaps include how this is a pro for Operator installations
* CR's ready in a single yaml file, used for Continuous Deployment. Allows you to do the same deployment in different namespaces or different clusters. Infrastructure as Code. Pipeline to apply commited yaml

### How do I get updates?
* What do channels mean for Operators?
* How do I upgrade this? What do channels mean for Operators?
* Explicitly mention the ability to backup before upgrades and restore from a backup in the case of issues.

### Closing Remarks
* Talk to us on IRC Matrix
* Put a plug in for the booth