From 282c8dccf075cbdfcd7a638507a94912db884e5f Mon Sep 17 00:00:00 2001 From: Daniel Nephin Date: Mon, 29 Nov 2021 17:56:57 -0500 Subject: [PATCH 01/98] Remove demo directory This demo setups are no longer maintained. See https://github.com/hashicorp/demo-consul-101 for a maintained demo. --- .../docker-compose-cluster/docker-compose.yml | 34 ----------- demo/vagrant-cluster/README.md | 57 ------------------- demo/vagrant-cluster/Vagrantfile | 56 ------------------ 3 files changed, 147 deletions(-) delete mode 100644 demo/docker-compose-cluster/docker-compose.yml delete mode 100644 demo/vagrant-cluster/README.md delete mode 100644 demo/vagrant-cluster/Vagrantfile diff --git a/demo/docker-compose-cluster/docker-compose.yml b/demo/docker-compose-cluster/docker-compose.yml deleted file mode 100644 index d9b022b3b9..0000000000 --- a/demo/docker-compose-cluster/docker-compose.yml +++ /dev/null @@ -1,34 +0,0 @@ -version: '3' - -services: - - consul-agent-1: &consul-agent - image: consul:latest - networks: - - consul-demo - command: "agent -retry-join consul-server-bootstrap -client 0.0.0.0" - - consul-agent-2: - <<: *consul-agent - - consul-agent-3: - <<: *consul-agent - - consul-server-1: &consul-server - <<: *consul-agent - command: "agent -server -retry-join consul-server-bootstrap -client 0.0.0.0" - - consul-server-2: - <<: *consul-server - - consul-server-bootstrap: - <<: *consul-agent - ports: - - "8400:8400" - - "8500:8500" - - "8600:8600" - - "8600:8600/udp" - command: "agent -server -bootstrap-expect 3 -ui -client 0.0.0.0" - -networks: - consul-demo: diff --git a/demo/vagrant-cluster/README.md b/demo/vagrant-cluster/README.md deleted file mode 100644 index 6b5405861b..0000000000 --- a/demo/vagrant-cluster/README.md +++ /dev/null @@ -1,57 +0,0 @@ -# Vagrant Consul Demo - -This demo provides a very simple `Vagrantfile` that creates two Consul -server nodes, one at *172.20.20.10* and another at *172.20.20.11*. Both are -running a standard Debian * distribution, and *the latest version* of Consul -is pre-installed. - -To get started, you can start the nodes by just doing: - -``` -vagrant up -``` - -> NOTE: If you prefer a different Vagrant box, you can set the `DEMO_BOX_NAME` -> environment variable before starting `vagrant` like this: -> `DEMO_BOX_NAME="ubuntu/xenial64" vagrant up` - -Once it is finished, you should be able to see the following: - -``` -vagrant status -Current machine states: - -n1 running (virtualbox) -n2 running (virtualbox) -``` - -At this point the two nodes are running and you can SSH in to play with them: - -``` -vagrant ssh n1 -consul version -Consul v0.7.5 -Protocol 2 spoken by default, understands 2 to 3 (agent will automatically use protocol >2 when speaking to compatible agents) -exit -``` - -and - -``` -vagrant ssh n2 -consul version -Consul v0.7.5 -Protocol 2 spoken by default, understands 2 to 3 (agent will automatically use protocol >2 when speaking to compatible agents) -exit -``` - -> NOTE: This demo will query the HashiCorp Checkpoint service to determine -> the latest Consul release version and install that version by default, -> but if you need a different Consul version, set the `CONSUL_DEMO_VERSION` -> environment variable before `vagrant up` like this: -> `CONSUL_DEMO_VERSION=0.6.4 vagrant up` - -## Where to Next? - -To learn more about starting Consul, joining nodes into a cluster, and -interacting with the agent, check out the [Getting Started guide](https://www.consul.io/intro/getting-started/install.html). diff --git a/demo/vagrant-cluster/Vagrantfile b/demo/vagrant-cluster/Vagrantfile deleted file mode 100644 index 0ac0f199c3..0000000000 --- a/demo/vagrant-cluster/Vagrantfile +++ /dev/null @@ -1,56 +0,0 @@ -# -*- mode: ruby -*- -# vi: set ft=ruby : - -$script = <