diff options
| author |   J. F. Lucas <jflucas@research.att.com> | 2017-08-30 13:21:43 +0000 |
|---|---|---|
| committer | Jack Lucas <jflucas@research.att.com> | 2017-08-30 13:25:09 +0000 |
| commit | d3e469ac48efd931580e89021b78e3273e814698 (patch) | |
| tree | 60a06d857f634d40b82b27162352d6fb0db5b735 /platform_base_installation/consul.md | |
| parent | 15bf6c62563a21b223d078c31305525b9f51b0cd (diff) | |
Fix extraneous white space
Change-Id: Iba30a13be4c6973f7d9aaec690e6ef738f8bd2b4
Issue-Id:CCSDK-73
Signed-off-by: Jack Lucas <jflucas@research.att.com>
Diffstat (limited to 'platform_base_installation/consul.md')
| -rw-r--r-- | platform_base_installation/consul.md | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/platform_base_installation/consul.md b/platform_base_installation/consul.md index 82f2f61..d092f92 100644 --- a/platform_base_installation/consul.md +++ b/platform_base_installation/consul.md @@ -6,10 +6,9 @@ This installation uses Consul 0.8.3. Consul is an open source project, and it can be built from source. For this project, however, we are using a binary distribution provided by Hashicorp (the company responsible for Consul development), pulled from https://releases.hashicorp.com/consul/0.8.3/consul_0.8.3_linux_amd64.zip. The zip file contains a single file, the consul binary executable. - #### How the installation works The installation is driven by a Cloudify blueprint ([`consul_cluster.yaml`](./consul_cluster.yaml)) with a set of inputs describing the OpenStack environment (typically generated by running the `configure-dcae` command as described in -the [installation instructions](./install.md)). +the [installation instructions](./install.md)). The blueprint creates three virtual machines, each running Ubuntu 16.04. The blueprint includes an initial shell script that runs when the VM is first booted (the so-called `cloud-init` script). This shell script: - creates the `/opt/consul/bin`, `/opt/consul/data`, and `/opt/consul/config`, and `/opt/consul/data` directories @@ -27,7 +26,7 @@ The initialization script for the third VM has one additional step, at the very After Cloudify finishes with the installation, the [`installer` script](./installer) waits for the Consul API to become available on the first Consul server, and then attempts to register Cloudify Manager as an [external service](https://www.consul.io/docs/guides/external.html) in Consul. It also puts the address of the first server into the `/opt/env.ini` file on the Cloudify Manager host. (It puts in one address to maintain consistency with the earlier installation process that installed a single Consul server in a Docker container. Certain plugins rely on this entry in `/opt/env.ini`, and they expect a single address. This will eventually change.) #### Managing Consul -We don't anticipate a need for hands-on management of Consul. When a Consul VM is rebooted, Consul will start automatically and will rejoin the Consul cluster. +We don't anticipate a need for hands-on management of Consul. When a Consul VM is rebooted, Consul will start automatically and will rejoin the Consul cluster. If there's a need to look more closely at what's going on with a Consul VM, logging in and becoming root provides access to the `systemd` tools. In particular: |