In another step we validate that the output is what we expect. To do so, we get the version that is installed by executing the rethinkdb -v command and save the output.
#Define vagrant install#
So for instance the install-rethinkdb role should validate that it did install the package provided.
Making sure roles are doing what they should The role itself should validate if the work it did was actually executed and working as intended. Instead I focussed on a few other things: In my case the roles I created where specific for my situation so I didn't, wanted to, create unit tests as that would have been a bit overkill. You can have Ansible roles unit tests, which will validate if the roles 'works'.
There are a few levels of testing that can be done for the Ansible playbook. The part we will focus on is the test folder. There will be some specific commands for rethinkDB, but most of it will be about the testing setup and ways you should test.Ī pretty normal layout for Ansible projects. You probably didn't heard from it before, and you can forget about it after reading this. We will be provisioning a 3 server cluster of a database server, RethinkDB Turned out it was not that hard to create, but getting all the information was.īecause of the combination of Ansible and Vagrant and probably my lack of knowledge on those topics 😃~įirst off, what are we actually going to provision? Or ways to test the playbook on the target systems, but I wanted to test the playbook before deployment during the build and/or locally. Looking through all the things, I mostly saw tests for Ansible Roles. (still don't) So Google it was to get the journey started. So I thought there should be a smarter and better way.Īs I am mainly a dev engineer, I didn't had thorough expertise on Ansible. As the setup was a bit larger and the overhead (commit, deploy) was bigger. This time around I didn't want to 'test' the provisioning manually. While I had worked with it before, it was mainly putting some roles together run the script and validate, manually, that it worked. So when I needed to create a new database cluster I looked into a setup that would be reproducible and it should be testable before it was deployed on the actual servers.įor stateless things we can used docker but that wasn't a great fit for the database servers as we need to have persistent storage and scaling and/or changes where not expected that often. Previously infrastructures where created and maintained by hand, which works well until.
#Define vagrant code#
I guess it's a matter of preference at this point? (I'm new to Vagrant, so I can't speak to best practices yet.Infrastructure as Code is getting more and more attention and for good reasons. You now know 3 different options you can set and the effects they have. This would be the output of hostname command in the VM and also this is what's visible in the prompt like here it will look like Code nfigure('2') do |config| Set hostname (BONUS) nfigure(VAGRANTFILE_API_VERSION) do |config|Ĭomments: This sets the hostname inside the VM. Simplifying based on zook's (commenter) input Set Provider Name nfigure('2') do |config|Ĭomments: If you set the name attribute in a provider configuration block, that name will become the entire name displayed in the VirtualBox GUI.Ĭombined Example: Define VM -and- Set Provider Name nfigure('2') do |config|Ĭomments: If you use both methods at the same time, the value assigned to name in the provider configuration block wins. This is the name vagrant outputs on the console. VirtualBox GUI Name: "nametest_foohost_1386347922"Ĭomments: If you explicitly define a VM, the name used replaces the token 'default'. VirtualBox GUI Name: "nametest_default_1386347922"Ĭomments: The name defaults to the format DIRECTORY_default_TIMESTAMP.ĭefine VM nfigure('2') do |config| Then I opened the VirtualBox GUI so I could see what names the boxes I create would show up as.ĭefault Vagrantfile nfigure('2') do |config| I created a directory called nametest and ran vagrant init precise64 I found the multiple options confusing, so I decided to test all of them to see exactly what they do.
0 kommentar(er)
