This talk will highlight how the OpenStack Infrastructure team uses SaltStack for event-driven orchestration of its various cloud infrastructure components. The speakers will review the flexibility of Salt in a complex automation environment. Salt plays very well with other tools, including Puppet, which is especially critical in the OpenStack Infrastructure environment which requires the event-driven orchestration functions of Salt to synchronize workflow timing of OpenStack Infrastructure components and events. To learn when and where the next SaltConf will be, subscribe to our newsletter here: http://www.saltstack.com/salt-ink-newsletter or follow us on Twitter: http://www.twitter.com/saltstackinc

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

3. Anita Kuno – hp
and
Dave Boucha - SaltStack

4. Who are we?

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

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

7. OpenStack Infrastructure

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

9. Provide automated services for
OpenStack development

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

11. Looking at the components

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

14. Looks complicated, where's the
Salt?

15. Salt Plays Nicely With Others

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

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

19. Jenkins and Salt Event Bus

20. Jenkins sends test success
message

21. Reactor tells puppetmaster to
update git clone

22. Reactor executes:
salt * puppet.run

24. OpenStack Orchestration History

25. Historically OpenStack has used
Puppet for automated
configuration

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

27. Puppet has been triggering off of
cron jobs

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

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

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

32. manage-projects.py

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

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

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

37. stackforge/openstack-sdk-php

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

39. We need event based
orchestration

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

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

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

43. Salt Reactor Config
Reactor Doc

45. Benefits of Salt in Openstack
Infrastructure

46. Separation of Concerns

47. Adapt easily to variable
infrastructure

48. Domain Experts can focus on
their areas

49. Each step is isolated from other
steps

50. Process can be restarted at any
point

51. Process can be modified easily

52. Process is clear

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