1.
Using SaltStack for event-driven
orchestration of OpenStack
infrastructure components

2.
Anita Kuno – hp
and
Dave Boucha - SaltStack

3.
Who are we?

4.
Anita Kuno
works on upstream OpenStack
a member of the infra team
receives paycheques from hp

5.
Dave Boucha
does all the Salt things
more great stuff
even more great stuff

6.
OpenStack Infrastructure

7.
What is the purpose of the
OpenStack Infrastructure team?

8.
Provide automated services for
OpenStack development

9.
Creation and hosting of git repos
Automating check and gate
testing
Communication tools
Etherpad, Mailing Lists, Asterisk

10.
Looking at the components

11.
Gerrit
Zuul
Jenkins(es)
Nodepool
some glue from Gearman

12.
Looks complicated, where's the
Salt?

13.
Salt Plays Nicely With Others

14.
Salt-master running on the same
server as the Puppet master

15.
Salt-minions running on:
Puppet master server
Jenkins slaves
Salt trigger server

16.
Jenkins and Salt Event Bus

17.
Jenkins sends test success
message

18.
Reactor tells puppetmaster to
update git clone

19.
Reactor executes:
salt * puppet.run

20.
OpenStack Orchestration History

21.
Historically OpenStack has used
Puppet for automated
configuration

22.
At the time, the choice was Chef
or Puppet and Monty got Puppet
to work

23.
Puppet has been triggering off of
cron jobs

24.
Time based orchestration no
longer fits our use case in all
situations

25.
Event Based Orchestration
Separation of Concerns
Avoid Programming the
Orchestration

26.
Let's take a look at OpenStack's
manage-projects script

27.
manage-projects.py

28.
New repos are created by
submitting a patch to gerrit

29.
Example:
review.openstack.org/#/c/62069

30.
After an infra core ran manage-
projects by hand

31.
stackforge/openstack-sdk-php

32.
Right now time based
orchestration doesn't get us the
results we need for creating new
repos

33.
We need event based
orchestration

34.
How does Salt enable this?
Salt Event Bus
Salt Reactor

35.
Salt Event Bus
Communication bus between
minions and master
salt-call event.fire_master

36.
Salt Reactor
Salt Master system that
“watches” the event bus
Matches event “tags” to sls files

37.
Salt Reactor Config
Reactor Doc

38.
Benefits of Salt in Openstack
Infrastructure

39.
Separation of Concerns

40.
Adapt easily to variable
infrastructure

41.
Domain Experts can focus on
their areas

42.
Each step is isolated from other
steps

43.
Process can be restarted at any
point

44.
Process can be modified easily

45.
Process is clear

46.
Anita: anteaya
anteaya@anteaya.info
Dave: UtahDave
dave@saltstack.com
Questions?