Ansible : Playbook Halyard

The aim of this project is to deploy a Halyard instance on Vagrant instances.

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes.

Prerequisites

What things you need to run this Ansible playbook :

• Vagrant must be installed on your computer
• Update the Vagrant file based on your computer (CPU, memory), if needed
• Update the operating system to deploy in the Vagrant file (default: Ubuntu)
• Download the Ansible requirements:

$ ansible-galaxy install -r requirements.yml

Usage

A good point with Vagrant is that you can create, update and destroy all architecture easily with some commands.

Be aware that you need to be in the Vagrant directory to be able to run the commands.

Deployment

To deploy Halyard on Vagrant instance, just run this command :

$ vagrant up

If everything run as expected, you should be able to list the virtual machine created :

$ vagrant status

Current machine states:

halyard01                   running (virtualbox)

If everything run has expected, you should have Halyard installed on the Vagrant instance:

$ hal -v
1.12.0-20181024113436

Destroy

To destroy the Vagrant resources created, just run this command :

$ vagrant destroy

How-To

This section list some simple command to use and manage the playbook and the Vagrant hosts.

Update with Ansible

To update the Halyard instance configuration with Ansible, you just have to run the Ansible playbook halyard.yml with this command :

$ ansible-playbook halyard.yml

Update with Vagrant

To update the Halyard instance configuration with Vagrant, you just have to run provisioning part of the Vagrant file :

$ vagrant provision

Connect to Vagrant instance

To be able to connect to a Vagrant instance, you should use the CLI which is configured to automatically use the default SSH key :

$ vagrant ssh halyard01

Author

Member of Wikitops : https://www.wikitops.io/

Licence

This project is licensed under the Apache License, Version 2.0. For the full text of the license, see the LICENSE file.