Conclusion - miroswan/vagrant_spec GitHub Wiki

So let's go over what we've accomplished:

• Configured Vagrant for multiple machines
• Configured Ansible to deploy Apache Mesos to multiple Vagrant instances
• Wrote ServerSpec/RSpec to validate that Mesos was running

We've accomplished all of this with a small, manageable amount of code. By now, you should have enough power at your fingertips to get started with deployment testing for your clustered and distributed systems. While vagrant_spec does cater heavily toward Ansible, the .vagrantspec_machine_data file generated from vagrant spec init should provide the information required to use just about any configuration-as-code deployment tool within Vagrant for testing.

If you experience any issues or have ideas for new features, please open an issue! Thank you for trying VagrantSpec.