openstack
/
openstack-chef-repo
Code Issues Proposed changes

Update README to reflect test kitchen commands 

Change-Id: I13dd84fb03f23f7768a87fccfd25202bee7bf4a6
This commit is contained in:
Samuel Cassiba 2018-03-21 10:14:16 -07:00
parent 4f374d32b9
commit f851a35303
1 changed files with 22 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

46
README.md
View File

@ -20,15 +20,15 @@ Architectures and a sane example on how to start with OpenStack using Chef.
With the `master` branch of the cookbooks, which is currently tied to the base With the `master` branch of the cookbooks, which is currently tied to the base
OpenStack Ocata release, this supports deploying to Ubuntu 16.04 and CentOS 7 OpenStack Ocata release, this supports deploying to Ubuntu 16.04 and CentOS 7
in monolithic, or allinone, and non-HA multinode configurations with Neutron. The cookbooks support a fully in monolithic, or allinone, and non-HA multinode configurations with Neutron.
HA configuration, but we do not test for that as there are far numerous paths to The cookbooks support a fully HA configuration, but we do not test for that as
there are far numerous paths to
HA. HA.
## Prerequisites ## Prerequisites
- [ChefDK](https://downloads.chef.io/chef-dk/) 1.0 or later for a relatively - [ChefDK](https://downloads.chef.io/chef-dk/) 2.0 or later
recent Berkshelf - [Vagrant](https://www.vagrantup.com/downloads.html) 2.0 or later with
- [Vagrant](https://www.vagrantup.com/downloads.html) 1.9 or later with
[VirtualBox](https://www.virtualbox.org/wiki/Downloads) or some other provider [VirtualBox](https://www.virtualbox.org/wiki/Downloads) or some other provider
### Getting the Code (this repo) ### Getting the Code (this repo)
@ -50,7 +50,7 @@ For each deployment model, there is a corresponding file in the doc/ directory.
Please review that for specific details and additional setup that might be Please review that for specific details and additional setup that might be
required before deploying the cloud. required before deploying the cloud.
## Rake Deploy Commands ## Kitchen Deploy Commands
These commands will produce various OpenStack cluster configurations, the These commands will produce various OpenStack cluster configurations, the
simplest being a monolithic Compute Controller with Neutron (allinone). These simplest being a monolithic Compute Controller with Neutron (allinone). These
@ -58,41 +58,39 @@ deployments are not intended to be production-ready, and will need adaptation
to your environment. This is intended for development and proof of concept to your environment. This is intended for development and proof of concept
deployments. deployments.
For CentOS, set the environment variable REPO_OS=centos7. Ubuntu is the default. ## Kitchen Test Scenarios
### Initialize the ChefDK
```bash
$ eval "$(chef shell-init bash)"
```
### Everything self-contained (allinone) ### Everything self-contained (allinone)
```bash ```bash
# allinone with Neutron # allinone with Neutron
$ chef exec rake allinone $ kitchen test [centos|ubuntu]
``` ```
### Access the machine ### Access the machine
```bash ```bash
$ cd vms $ kitchen login [centos|ubuntu]
$ vagrant ssh controller
$ sudo su - $ sudo su -
``` ```
### Multiple nodes (non-HA) ### Multiple nodes (non-HA)
```bash ```bash
# Multinode with Neutron (1 controller + 1 network + 2 compute nodes) # Multinode with Neutron (1 controller + 2 compute nodes)
$ chef exec rake multi_node $ export KITCHEN_YAML=.kitchen.multi.yaml
$ kitchen converge [centos|ubuntu|all]
$ kitchen verify [centos|ubuntu|all]
$ kitchen destroy [centos|ubuntu|all]
``` ```
### Access the Controller ### Access the Controller
```bash ```bash
$ cd vms $ kitchen login controller-[centos|ubuntu]
$ vagrant ssh controller
$ sudo su -
```
### Access the Network Node
```bash
$ cd vms
$ vagrant ssh network
$ sudo su - $ sudo su -
``` ```
@ -100,9 +98,9 @@ $ sudo su -
```bash ```bash
$ cd vms $ cd vms
$ vagrant ssh compute1 $ kitchen login compute1
# OR # OR
$ vagrant ssh compute2 $ kitchen login compute2
$ sudo su - $ sudo su -
``` ```