Using SaltStack for event-driven
orchestration of OpenStack
infrastructure components
Anita Kuno – hp
and
Dave Boucha - SaltStack
Who are we?
Anita Kuno
works on upstream OpenStack
a member of the infra team
receives paycheques from hp
Dave Boucha
does all the Salt things
more great stuff
even more great stuff
OpenStack Infrastructure
What is the purpose of the
OpenStack Infrastructure team?
Provide automated services for
OpenStack development
Creation and hosting of git repos
Automating check and gate
testing
Communication tools
Etherpad, Mailing Lists, Asterisk
Looking at the components
Gerrit
Zuul
Jenkins(es)
Nodepool
some glue from Gearman
Looks complicated, where's the
Salt?
Salt Plays Nicely With Others
Salt-master running on the same
server as the Puppet master
Salt-minions running on:
Puppet master server
Jenkins slaves
Salt trigger server
Jenkins and Salt Event Bus
Jenkins sends test success
message
Reactor tells puppetmaster to
update git clone
Reactor executes:
salt * puppet.run
OpenStack Orchestration History
Historically OpenStack has used
Puppet for automated
configuration
At the time, the choice was Chef
or Puppet and Monty got Puppet
to work
Puppet has been triggering off of
cron jobs
Time based orchestration no
longer fits our use case in all
situations
Event Based Orchestration
Separation of Concerns
Avoid Programming the
Orchestration
Let's take a look at OpenStack's
manage-projects script
manage-projects.py
New repos are created by
submitting a patch to gerrit
Example:
review.openstack.org/#/c/62069
After an infra core ran manage-
projects by hand
stackforge/openstack-sdk-php
Right now time based
orchestration doesn't get us the
results we need for creating new
repos
We need event based
orchestration
How does Salt enable this?
Salt Event Bus
Salt Reactor
Salt Event Bus
Communication bus between
minions and master
salt-call event.fire_master
Salt Reactor
Salt Master system that
“watches” the event bus
Matches event “tags” to sls files
Salt Reactor Config
Reactor Doc
Benefits of Salt in Openstack
Infrastructure
Separation of Concerns
Adapt easily to variable
infrastructure
Domain Experts can focus on
their areas
Each step is isolated from other
steps
Process can be restarted at any
point
Process can be modified easily
Process is clear
Anita: anteaya
anteaya@anteaya.info
Dave: UtahDave
dave@saltstack.com
Questions?
SaltConf14 - Anita Kuno, HP & OpenStack - Using SaltStack for event-driven orchestration of OpenStack infrastructure compo...
SaltConf14 - Anita Kuno, HP & OpenStack - Using SaltStack for event-driven orchestration of OpenStack infrastructure compo...
SaltConf14 - Anita Kuno, HP & OpenStack - Using SaltStack for event-driven orchestration of OpenStack infrastructure compo...
SaltConf14 - Anita Kuno, HP & OpenStack - Using SaltStack for event-driven orchestration of OpenStack infrastructure compo...
SaltConf14 - Anita Kuno, HP & OpenStack - Using SaltStack for event-driven orchestration of OpenStack infrastructure compo...
SaltConf14 - Anita Kuno, HP & OpenStack - Using SaltStack for event-driven orchestration of OpenStack infrastructure compo...
SaltConf14 - Anita Kuno, HP & OpenStack - Using SaltStack for event-driven orchestration of OpenStack infrastructure compo...
Upcoming SlideShare
Loading in …5
×

SaltConf14 - Anita Kuno, HP & OpenStack - Using SaltStack for event-driven orchestration of OpenStack infrastructure components

1,326 views
1,106 views

Published on

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

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,326
On SlideShare
0
From Embeds
0
Number of Embeds
14
Actions
Shares
0
Downloads
27
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

SaltConf14 - Anita Kuno, HP & OpenStack - Using SaltStack for event-driven orchestration of OpenStack infrastructure components

  1. 1. Using SaltStack for event-driven orchestration of OpenStack infrastructure components
  2. 2. Anita Kuno – hp and Dave Boucha - SaltStack
  3. 3. Who are we?
  4. 4. Anita Kuno works on upstream OpenStack a member of the infra team receives paycheques from hp
  5. 5. Dave Boucha does all the Salt things more great stuff even more great stuff
  6. 6. OpenStack Infrastructure
  7. 7. What is the purpose of the OpenStack Infrastructure team?
  8. 8. Provide automated services for OpenStack development
  9. 9. Creation and hosting of git repos Automating check and gate testing Communication tools Etherpad, Mailing Lists, Asterisk
  10. 10. Looking at the components
  11. 11. Gerrit Zuul Jenkins(es) Nodepool some glue from Gearman
  12. 12. Looks complicated, where's the Salt?
  13. 13. Salt Plays Nicely With Others
  14. 14. Salt-master running on the same server as the Puppet master
  15. 15. Salt-minions running on: Puppet master server Jenkins slaves Salt trigger server
  16. 16. Jenkins and Salt Event Bus
  17. 17. Jenkins sends test success message
  18. 18. Reactor tells puppetmaster to update git clone
  19. 19. Reactor executes: salt * puppet.run
  20. 20. OpenStack Orchestration History
  21. 21. Historically OpenStack has used Puppet for automated configuration
  22. 22. At the time, the choice was Chef or Puppet and Monty got Puppet to work
  23. 23. Puppet has been triggering off of cron jobs
  24. 24. Time based orchestration no longer fits our use case in all situations
  25. 25. Event Based Orchestration Separation of Concerns Avoid Programming the Orchestration
  26. 26. Let's take a look at OpenStack's manage-projects script
  27. 27. manage-projects.py
  28. 28. New repos are created by submitting a patch to gerrit
  29. 29. Example: review.openstack.org/#/c/62069
  30. 30. After an infra core ran manage- projects by hand
  31. 31. stackforge/openstack-sdk-php
  32. 32. Right now time based orchestration doesn't get us the results we need for creating new repos
  33. 33. We need event based orchestration
  34. 34. How does Salt enable this? Salt Event Bus Salt Reactor
  35. 35. Salt Event Bus Communication bus between minions and master salt-call event.fire_master
  36. 36. Salt Reactor Salt Master system that “watches” the event bus Matches event “tags” to sls files
  37. 37. Salt Reactor Config Reactor Doc
  38. 38. Benefits of Salt in Openstack Infrastructure
  39. 39. Separation of Concerns
  40. 40. Adapt easily to variable infrastructure
  41. 41. Domain Experts can focus on their areas
  42. 42. Each step is isolated from other steps
  43. 43. Process can be restarted at any point
  44. 44. Process can be modified easily
  45. 45. Process is clear
  46. 46. Anita: anteaya anteaya@anteaya.info Dave: UtahDave dave@saltstack.com Questions?

×