BOSH is an open source tool that allows developers to easily package, release, deploy, and manage distributed systems and applications at scale across multiple cloud environments. It provides capabilities for deployment, configuration management, updates/upgrades with minimal downtime, remediation, and scaling. BOSH abstracts away infrastructure details through "stem cells" and treats applications as logical concepts rather than physical servers through a "release" process, providing consistency, reproducibility and agility in deployments.

1. BOSH
configuring services
Andrew Clay Shafer
Gent 2015

2. Andrew Clay Shafer
@littleidea

3. Andrew Clay Shafer

4. has been very good to me

5. ASK ME ABOUT
PARETO INEFFICIENT
NASH EQUILIBRIUMS

7. What is BOSH?

8. Why is BOSH?

10. Platform as a Service
Whatever that means…

11. routers
Linux
LinuxLinux
Containers
message
bus
cloud controller
loggregators
controller
DB
etcd
hm9000
metrics firehose
a couple dozen services
UAA
login
What even is Elastic Runtime?
service
brokers
object
store
stagers

12. how do you
manage that thing?

13. if you wish to deploy a distributed
system from scratch, you must
first deploy the universe

14. stateful services
Elastic Runtime
“cloud”
BOSH
“metal”
configuration management™
apps
(the reason we put ourselves through this)
containers
VMs
machines
Typical
fast
unfast

15. distributed systems managing
distributed systems managing
distributed systems managing
distributed systems

16. <rant>managing</rant>

17. back to BOSH

18. BOSH is an open source tool chain for
release engineering, deployment, and
lifecycle management of large-scale
distributed services.

19. BOSH allows individual
developers and teams to easily
version, package and deploy
software in a reproducible manner.

20. Purposeful Goals
• Identifiability
• Reproducibility
• Consistency
• Agility

21. GOALS
• Identifiability - Being able to identify all of the source, tools,
environment, and other components that make up a particular
release.
• Reproducibility - The ability to integrate source, third party
components, data, and deployment externals of a software system
in order to guarantee operational stability.
• Consistency - The mission to provide a stable framework for
development, deployment, audit, and accountability for software
components.
• Agility - The ongoing research into what are the repercussions of
modern software engineering practices on the productivity in the
software cycle, i.e. continuous integration.

22. I READ IT ON
THE INTERNET

23. Whatever

24. need to manage a large
distributed system
• deployment
• configuration changes
• updates/upgrades - minimal downtime
• remediation
• scale out/scale in
• across multiple IaaS

25. need to manage a large
distributed system
configuration management™
necessary but not sufficient

26. BOSH is a distributed
package and process
orchestrator

27. packages and
processes
assumes knowledge…

28. idempotent resource
abstractions for fun and profit
desired state current state

29. service centric, not
server centric

30. – no CEO ever
“Good job provisioning servers this year”

31. highest level primitive:
deployment

32. Learning BOSH

33. Deployment - map release to IaaS
Release - package with some jobs
Stem Cell - VM with BOSH agent
Vocabulary

34. Stem Cell
Base VM with embedded BOSH agent

35. Release
• Manifest
• Packages
• spec
• packaged bits
• Jobs
• spec
• monit
• templates

36. Deployment
• releases
• compilation VMs
• canary settings
• network configurations
• resource pools (VMs, Disks, Networks)
• jobs
• job properties

37. So…what happens
when I deploy?

38. CLI
Director
message
bus
worker
VMs
IaaS
object storage
health
monitor

39. Director VM
CPI
(Cloud Provider Interface)
Director Starts VMs

40. Director VM
BOSH Agent Boots

41. Director VM
Director Pings Agent

42. Director VM
Assign Job to Agent

43. BlobstoreVM
Agent Fetches Releases

44. Agent Starts Jobs
VM

45. this happens for every
VM described in the
deployment

46. idempotent resource
abstractions for fun and profit
desired state current state
except now the resource is a running service

48. but how do I?

49. don’t

50. <rant>
automate brokeness
</rant>

52. learn you some Pareto Power Law

53. Warning

54. do you need a deathstar?

55. is your goal to deploy a
single instance of wordpress?

56. maybe, maybe not?

57. Learning Curve
effort
capability
That’s it

58. I’m here to help
https://www.flickr.com/photos/simplebitsdan/2477674571/

59. Now Hiring

60. DANK
@littleidea