3 ms·
> To me, an orchestration system should control the entire provisioning process, turning a plan defined in code into a production system. As a result I (perhaps
by twic 11y ago
> To me, an orchestration system should control the entire provisioning process, turning a plan defined in code into a production system. As a result I (perhaps unhelpfully) don’t believe anyone has built an orchestration system
Stackbuilder!
https://github.com/tim-group/stackbuilder https://github.com/tim-group/stackbuilder
The docs for Stackbuilder are still horrible, but here's an example stack:
https://github.com/tim-group/stackbuilder-config-example/blob/master/stack.rb https://github.com/tim-group/stackbuilder-config-example/blo...
Assuming you have a compute fabric in place, running a script like that through the tool will provision and configure VMs for all the parts of a production system: it knows about Java applications (started with java -jar), Apache proxy servers, Linux NAT, IPVS load balancing, MySQL databases, Puppetmasters, and possibly other things. The fabric provides KVM for VMs, and BIND for DNS, controlled via some custom MCollective plugins. Configuration is done via Puppet, but Stackbuilder creates the Puppetmaster as part of the build. Application firewalls and Nagios checks get configured as part of the build, but i can't remember if it's Stackbuilder itself that does that, or some of the Puppet code.
BOSH is the same space:
https://bosh.io/ https://bosh.io/
Again, it requires an existing fabric, but that can be plain AWS or OpenStack (or VMware). It can then build anything you can write a manifest for; it operates at a lower level of abstraction than Stackbuilder.
- falcolas 11y agoSaltstack, with the cloud module, fits into this role rather well. It's more of a declarative setup and a discoverable setup, but I've found that to be acceptable.