https://github.com/jonmosco/ansible-atomic_nodes
Ansible playbook to configure an Atomic Host to be a member of a cluster
https://github.com/jonmosco/ansible-atomic_nodes
Last synced: 5 months ago
JSON representation
Ansible playbook to configure an Atomic Host to be a member of a cluster
- Host: GitHub
- URL: https://github.com/jonmosco/ansible-atomic_nodes
- Owner: jonmosco
- Created: 2016-04-25T19:50:28.000Z (over 10 years ago)
- Default Branch: master
- Last Pushed: 2016-05-12T19:26:08.000Z (about 10 years ago)
- Last Synced: 2025-03-11T01:50:00.149Z (over 1 year ago)
- Size: 14.6 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Ansible role for Atomic Cluster configuration and deployment
### About
This follows Project Atomics getting started guide:
http://www.projectatomic.io/docs/gettingstarted/
I will try to maintain this as the document gets updated. Please feel free to submit pull requests
###Vagrant environment
This repository contains a Vagrant environment as a test environment with one master, and one node,
and more can be added easily.
To change the IP Address of each Vagrant node, modify:
```
MASTER_IP="192.168.60.2"
NODE01_IP="192.168.60.3"
```
In order to use the role with Vagrant, there is a site.yml in the top level directory. Add the correct
addresses from your Vagrant env in this file, and simply `vagrant up`
### Requirements
This playbook has been tested with Ansible 1.9+
### Usage
###Variables:
Address of the primary Atomic Master:
* atomic_master:
Address of ETCD master (same address as the Atomic Master in the docs):
* etcd_master:
Interface name of the externally available network adapter. This is a variable
because it can change based on underlying hardware:
* primary_interface:
###Bugs
Please submit pull requests