*More Salt in Infra
Session proposed by Anita Kuno
Wednesday November  6, 2013  5:30pm -  6:10pm
Design Summit 1
Infrastructure

Taking a look at what bits and pieces of Infra could work well with Salt.

*Current Status of Salt in Infra
https://etherpad.openstack.org/p/salt-slavery-and-puppetry

https://review.openstack.org/#/q/project:openstack-infra/config+topic:salt-trigger,n,z
https://review.openstack.org/#/q/project:openstack-infra/config+topic:salt_key_creation,n,z
https://review.openstack.org/#/q/project:openstack-infra/config+topic:salt,n,z

current version of salt master:  0.17.1
current version of salt minion:  0.17.1

one salt master running on the ci-puppetmaster server
salt minions running on: the ci-puppetmaster server, the jenkins slaves, salt trigger slave running on salt-trigger.slave.openstack.org (receives from jenkins.openstack.org)

*Areas to Consider Salting
alternative/answer to (lack of) strong gearman identification for access control in zuul
dealing with race conditions:
    - create a new repository

Proposed solution:
    - move to an "Event Driven Infrastructure"
	    - Use the Salt Reactor to listen for specific events
	    - Salt Overstate and/or state.sls to orchestrate changes
  - Example:
      - New Project overstate goes through step by step process in creating a new project
      - At each step a message is fired across the event bus notifiying of successful completion
      - Servers that need to update themselves listen for specific events and only take action when they are seen.
      - Diagram: https://www.dropbox.com/s/99ea4c2aucqm67l/Event-Based-Infrastructure.png

Questions:
    - Do we want to log both successes and failures? Yes.
    - Use Salt logstash module? Local logs on master and minions for now.
    - Why not heat? Providers not offering endpoints (yet), standalone doesn't support multiple clouds (yet).

*Action Items
- https://etherpad.openstack.org/p/salt-slavery-and-puppetry
- figure out why we're not upgrading from ubuntu-provided packaging to ppa packages (apt repo pin priority?)
- move infra salt from ppas to salt repo to enable version pinning
- Look into salt cloud as a tool to manage collections of long running slaves (instead of heat)