From e0853c9856403febc0d8ef1e410bfabbfd8a4de5 Mon Sep 17 00:00:00 2001 From: Scott Lowe Date: Wed, 20 Dec 2017 08:04:31 -0700 Subject: [PATCH] Remove references to personally-built boxes Remove references to Vagrant boxes that I personally built and (did not) maintain, replacing them with more regularly-maintained boxes Signed-off-by: Scott Lowe --- openstack/cli/README.md | 8 ++++---- openstack/cli/machines.yml | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/openstack/cli/README.md b/openstack/cli/README.md index 5444aab..6d8292f 100644 --- a/openstack/cli/README.md +++ b/openstack/cli/README.md @@ -8,9 +8,9 @@ These files were created to allow users to use Vagrant ([http://www.vagrantup.co * **config.sh**: This shell script performs the final configuration tasks on the Vagrant box to install the OpenStack CLI clients. It is called by the Vagrant file provisioner in `Vagrantfile`. -* **README.md**: This file you're currently reading. +* **machines.yml**: This YAML file contains a list of VM definitions and associated configuration data. It is referenced by `Vagrantfile` when Vagrant instantiates the VMs. -* **servers.yml**: This YAML file contains a list of VM definitions and associated configuration data. It is referenced by `Vagrantfile` when Vagrant instantiates the VMs. +* **README.md**: This file you're currently reading. * **Vagrantfile**: This file is used by Vagrant to spin up the virtual machines. This file is fairly extensively commented to help explain what's happening. You should be able to use this file unchanged; all the VM configuration options are stored outside this file. @@ -22,9 +22,9 @@ These instructions assume you've already installed VMware Fusion, Vagrant, and t 1. Edit the `adminrc` file to provide the specific details to authenticate against your existing OpenStack installation. Specifically, you'll need the URL for authenticating against Keystone (typically looks something like `http://192.168.1.100:5000/v2.0`), the project/tenant against which the commands should run, and the username and password for a user with permissions in that project/tenant. -2. Use `vagrant box add` to add an Ubuntu 14.04 base box to be used by this `Vagrantfile`. You can use my base box (`slowe/ubuntu-trusty-x64`), which provides support for the `vmware_desktop` provider (it should work with either VMware Workstation or VMware Fusion). +2. Use `vagrant box add` to add an Ubuntu 14.04 base box to be used by this `Vagrantfile`. The `machines.yml` file contains some suggested boxes you can use. -3. If you are using a box other than my Ubuntu 14.04 base box, or if you want to change the default amount of RAM or number of vCPUs assigned to the VM, edit the `servers.yml` file and make the desired changes. +3. If you are using a box other than those listed in `machines.yml`, or if you want to change the default amount of RAM or number of vCPUs assigned to the VM, edit the `machines.yml` file and make the desired changes. 4. Run `vagrant up`, and when the VM is done provisioning (note that Internet access is required) use `vagrant ssh` to enjoy CLI access to the configured OpenStack installation. diff --git a/openstack/cli/machines.yml b/openstack/cli/machines.yml index efb4f6d..220e6d4 100644 --- a/openstack/cli/machines.yml +++ b/openstack/cli/machines.yml @@ -1,6 +1,6 @@ --- - name: openstack-cli - vmw_box: slowe/ubuntu-trusty-x64 + vmw_box: bento/ubuntu-14.04 vb_box: ubuntu/trusty64 ram: 512 vcpu: 1