ran ./hack/update-generated-docks.sh

This commit is contained in:
Vallard Benincosa 2015-08-13 22:59:39 -07:00
parent 1419806ca8
commit 964d4c7111

View File

@ -137,12 +137,14 @@ In one terminal, run `gcloud compute ssh master --ssh-flag="-L 8080:127.0.0.1:80
run `gcloud compute ssh master --ssh-flag="-R 8080:127.0.0.1:8080"`. run `gcloud compute ssh master --ssh-flag="-R 8080:127.0.0.1:8080"`.
### OpenStack ### OpenStack
These instructions are for running on the command line. Most of this you can also do through the Horizon dashboard. These instructions are for running on the command line. Most of this you can also do through the Horizon dashboard.
These instructions were tested on the Ice House release on a Metacloud distribution of OpenStack but should be similar if not the same across other versions/distributions of OpenStack. These instructions were tested on the Ice House release on a Metacloud distribution of OpenStack but should be similar if not the same across other versions/distributions of OpenStack.
#### Make sure you can connect with OpenStack #### Make sure you can connect with OpenStack
Make sure the environment variables are set for OpenStack such as: Make sure the environment variables are set for OpenStack such as:
```sh ```sh
OS_TENANT_ID OS_TENANT_ID
OS_PASSWORD OS_PASSWORD
@ -150,7 +152,9 @@ OS_AUTH_URL
OS_USERNAME OS_USERNAME
OS_TENANT_NAME OS_TENANT_NAME
``` ```
Test this works with something like: Test this works with something like:
``` ```
nova list nova list
``` ```
@ -186,6 +190,7 @@ nova boot \
--user-data files/master.yaml \ --user-data files/master.yaml \
kube-master kube-master
``` ```
```<image_name>``` is the CoreOS image name. In our example we can use the image we created in the previous step and put in 'CoreOS723' ```<image_name>``` is the CoreOS image name. In our example we can use the image we created in the previous step and put in 'CoreOS723'
```<my_key>``` is the keypair name that you already generated to access the instance. ```<my_key>``` is the keypair name that you already generated to access the instance.
@ -195,13 +200,17 @@ kube-master
The important part is to ensure you have the files/master.yml as this is what will do all the post boot configuration. This path is relevant so we are assuming in this example that you are running the nova command in a directory where there is a subdirectory called files that has the master.yml file in it. Absolute paths also work. The important part is to ensure you have the files/master.yml as this is what will do all the post boot configuration. This path is relevant so we are assuming in this example that you are running the nova command in a directory where there is a subdirectory called files that has the master.yml file in it. Absolute paths also work.
Next, assign it a public IP address: Next, assign it a public IP address:
``` ```
nova floating-ip-list nova floating-ip-list
``` ```
Get an IP address that's free and run: Get an IP address that's free and run:
``` ```
nova floating-ip-associate kube-master <ip address> nova floating-ip-associate kube-master <ip address>
``` ```
where ```<ip address>``` is the IP address that was available from the ```nova floating-ip-list``` command. where ```<ip address>``` is the IP address that was available from the ```nova floating-ip-list``` command.
#### Provision Worker Nodes #### Provision Worker Nodes
@ -217,6 +226,7 @@ nova boot \
--user-data files/node.yaml \ --user-data files/node.yaml \
minion01 minion01
``` ```
This is basically the same as the master nodes but with the node.yaml post-boot script instead of the master. This is basically the same as the master nodes but with the node.yaml post-boot script instead of the master.
### VMware Fusion ### VMware Fusion