From 9fc334bc22bd23c50c911666e99073fd375839e1 Mon Sep 17 00:00:00 2001 From: Lukasz Zajaczkowski Date: Thu, 18 Feb 2016 10:20:23 +0100 Subject: [PATCH 1/7] Add doc on OpenStack provider --- docs/getting-started-guides/index.md | 2 + docs/getting-started-guides/openstack.md | 117 +++++++++++++++++++++++ 2 files changed, 119 insertions(+) create mode 100644 docs/getting-started-guides/openstack.md diff --git a/docs/getting-started-guides/index.md b/docs/getting-started-guides/index.md index 1378e6de11..0f213f5d52 100644 --- a/docs/getting-started-guides/index.md +++ b/docs/getting-started-guides/index.md @@ -82,6 +82,7 @@ These solutions are combinations of cloud provider and OS not covered by the abo - [Vmware](/docs/getting-started-guides/coreos) (uses CoreOS and flannel) - [libvirt-coreos.md](/docs/getting-started-guides/libvirt-coreos) (uses CoreOS) - [oVirt](/docs/getting-started-guides/ovirt) +- [OpenStack](/docs/getting-started-guides/openstack) (uses CentOS and flannel) - [libvirt](/docs/getting-started-guides/fedora/flannel_multi_node_cluster) (uses Fedora and flannel) - [KVM](/docs/getting-started-guides/fedora/flannel_multi_node_cluster) (uses Fedora and flannel) @@ -140,6 +141,7 @@ Bare-metal | custom | Ubuntu | Calico | [docs](/docs/gettin Bare-metal | custom | Ubuntu | flannel | [docs](/docs/getting-started-guides/ubuntu) | | Community ([@resouer](https://github.com/resouer), [@WIZARD-CXY](https://github.com/WIZARD-CXY)) libvirt/KVM | CoreOS | CoreOS | libvirt/KVM | [docs](/docs/getting-started-guides/libvirt-coreos) | | Community ([@lhuard1A](https://github.com/lhuard1A)) oVirt | | | | [docs](/docs/getting-started-guides/ovirt) | | Community ([@simon3z](https://github.com/simon3z)) +OpenStack | Saltstack | CentOS | flannel | [docs](/docs/getting-started-guides/openstack) | | Community ([@FujitsuEnablingSoftwareTechnologyGmbH](https://github.com/FujitsuEnablingSoftwareTechnologyGmbH)) Rackspace | CoreOS | CoreOS | flannel | [docs](/docs/getting-started-guides/rackspace) | | Community ([@doublerr](https://github.com/doublerr)) any | any | any | any | [docs](/docs/getting-started-guides/scratch) | | Community ([@erictune](https://github.com/erictune)) diff --git a/docs/getting-started-guides/openstack.md b/docs/getting-started-guides/openstack.md new file mode 100644 index 0000000000..ccb47d7aef --- /dev/null +++ b/docs/getting-started-guides/openstack.md @@ -0,0 +1,117 @@ +--- +--- + +* TOC +{:toc} + +## Getting started with OpenStack + +Running Kubernetes with Openstack is an easy way to create Kubernetes cluster on the top of OpenStack. Heat OpenStack Orchestration +engine describes the infrastructure for Kubernetes cluster. CentoOS images are used for Kubernetes host machines. + +## Prerequisites + +1. Install latest version OpenStack clients + + heat >= 0.9.0 + + swift >= 2.7.0 + + glance >= 1.2.0 + + nova >= 3.2.0 + + ``` + sudo pip install -U --force python-heatclient + sudo pip install -U --force python-swiftclient + sudo pip install -U --force python-glanceclient + sudo pip install -U --force python-novaclient + ``` +#### Note: +OpenStack CLI clients like python-PROJECTNAMEclient are going to be deprecated soon in favor of universal OpenStack CLI client. +More information you can find here: [deprecate-cli](https://specs.openstack.org/openstack/openstack-specs/specs/deprecate-cli.html) + + +2. Set proper values in configuration files + +Project contains four files with configuration: config-default.sh, config-image.sh, openrc-default.sh and openrc-swift.sh + +**config-default.sh** sets all parameters needed for heat template. +Additionally there is a flag CREATE_IMAGE which indicates if new image must be created. +If 'false' then image with IMAGE_ID will be used. + +**config-image.sh** sets parameters needed to create new OpenStack image if flag CREATE_IMAGE=true. +Use CentOS 7 image for this purpose. You can get image here: [CentOS images](http://cloud.centos.org/centos/7/images/) + +**openrc-default.sh openrs-swift.sh** those files contain credential variables for OpenStack clients. + + +## Setup + +Setting up a cluster: + +```sh +export KUBERNETES_PROVIDER=openstack +cd kubernetes +make clean +make quick-release +./cluster/kube-up.sh +``` + +Alternatively, you can download [Kubernetes release](https://github.com/kubernetes/kubernetes/releases) and extract the archive. To start your local cluster, open a shell and run: + +```sh +cd kubernetes + +export KUBERNETES_PROVIDER=openstack +./cluster/kube-up.sh +``` + +The `KUBERNETES_PROVIDER` environment variable tells all of the various cluster management scripts which variant to use. If you forget to set this, the assumption is you are running on Google Compute Engine. + +## Interacting with your Kubernetes cluster with Openstack + +You can manage the nodes in your cluster with the Openstack WEB UI like Horizon or using heat or nova clients. + +To get all necessary information about cluster execute commands in main kubernetes directory: + +``` +. cluster/openstack/config-default.sh +. cluster/openstack/openrc-default.sh +heat stack-show $STACK_NAME +``` + +You will get cluster status and IP addresses for your master and minion nodes. + +## Authenticating with your master + +Because you added public key to nodes you can easily ssh to them. + +``` +$ ssh minion@IP_ADDRESS +``` + +## Running containers + +Your cluster is running, you can list the nodes in your cluster: + +```console +$ ./cluster/kubectl.sh get nodes +NAME LABELS STATUS AGE +kubernetesstack-node-tc9f2tfr kubernetes.io/hostname=kubernetesstack-node-tc9f2tfr Ready 21h +``` + +Before starting a container there will be no pods, services and replication controllers. + +```console +$ ./cluster/kubectl.sh get pods +NAME READY STATUS RESTARTS AGE + +$ ./cluster/kubectl.sh get services +NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE + +$ ./cluster/kubectl.sh get replicationcontrollers +CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS +``` + +Now you are ready to create you first service and controller. From 0d0459c50f22c9e6fba1a06d9185a0bc8214611b Mon Sep 17 00:00:00 2001 From: Elson O Rodriguez Date: Thu, 14 Apr 2016 15:04:01 -0700 Subject: [PATCH 2/7] Modifying Openstack kube-up provider documentation. --- docs/getting-started-guides/openstack.md | 267 ++++++++++++++++------- 1 file changed, 190 insertions(+), 77 deletions(-) diff --git a/docs/getting-started-guides/openstack.md b/docs/getting-started-guides/openstack.md index ccb47d7aef..8e5f1ef341 100644 --- a/docs/getting-started-guides/openstack.md +++ b/docs/getting-started-guides/openstack.md @@ -6,112 +6,225 @@ ## Getting started with OpenStack -Running Kubernetes with Openstack is an easy way to create Kubernetes cluster on the top of OpenStack. Heat OpenStack Orchestration -engine describes the infrastructure for Kubernetes cluster. CentoOS images are used for Kubernetes host machines. +This guide will take you through the steps of deploying Kubernetes to Openstack using `kube-up.sh`. The primary mechanisms for this are [OpenStack Heat](https://wiki.openstack.org/wiki/Heat) and the [SaltStack](https://github.com/kubernetes/kubernetes/tree/master/cluster/saltbase) distributed with Kubernetes. -## Prerequisites +The default OS is CentOS 7, this has not been tested on other operating systems. -1. Install latest version OpenStack clients +This guide assumes you have a working OpenStack cluster. - heat >= 0.9.0 +## Pre-Requisites +If you already have the OpenStack CLI tools installed and configured, you can move on to the [Starting a cluster](#starting-a-cluster) section. - swift >= 2.7.0 - - glance >= 1.2.0 - - nova >= 3.2.0 - - ``` - sudo pip install -U --force python-heatclient - sudo pip install -U --force python-swiftclient - sudo pip install -U --force python-glanceclient - sudo pip install -U --force python-novaclient - ``` -#### Note: -OpenStack CLI clients like python-PROJECTNAMEclient are going to be deprecated soon in favor of universal OpenStack CLI client. -More information you can find here: [deprecate-cli](https://specs.openstack.org/openstack/openstack-specs/specs/deprecate-cli.html) - - -2. Set proper values in configuration files - -Project contains four files with configuration: config-default.sh, config-image.sh, openrc-default.sh and openrc-swift.sh - -**config-default.sh** sets all parameters needed for heat template. -Additionally there is a flag CREATE_IMAGE which indicates if new image must be created. -If 'false' then image with IMAGE_ID will be used. - -**config-image.sh** sets parameters needed to create new OpenStack image if flag CREATE_IMAGE=true. -Use CentOS 7 image for this purpose. You can get image here: [CentOS images](http://cloud.centos.org/centos/7/images/) - -**openrc-default.sh openrs-swift.sh** those files contain credential variables for OpenStack clients. - - -## Setup - -Setting up a cluster: +#### Install OpenStack CLI tools ```sh -export KUBERNETES_PROVIDER=openstack -cd kubernetes +sudo pip install -U --force 'python-heatclient==1.1.0' +sudo pip install -U --force 'python-swiftclient==3.0.0' +sudo pip install -U --force 'python-glanceclient==2.0.0' +sudo pip install -U --force 'python-novaclient==3.4.0' +``` + +#### Configure Openstack CLI tools + +Please talk to your local OpenStack administrator for an `openrc.sh` file. + +Once you have that file, source it into your environment by typing + +```sh +. ~/path/to/openrc.sh +``` + +This provider will consume the [correct variables](http://docs.openstack.org/user-guide/common/cli_set_environment_variables_using_openstack_rc.html) to talk to OpenStack and turn-up the Kubernetes cluster. + +Otherwise, you must set the following appropriately: + +```sh +export OS_USERNAME=username +export OS_PASSWORD=password +export OS_TENANT_NAME=projectName +export OS_AUTH_URL=https://identityHost:portNumber/v2.0 +export OS_TENANT_ID=tenantIDString +export OS_REGION_NAME=regionName +``` + +#### Set additional configuration values + +In addition, here are some commonly changed variables specific to this provider, with example values. Under most circumstances you will not have to change these. + +```sh +export STACK_NAME=KubernetesStack +export NUMBER_OF_MINIONS=3 +export MAX_NUMBER_OF_MINIONS=3 +export MASTER_FLAVOR=m1.small +export MINION_FLAVOR=m1.small +export EXTERNAL_NETWORK=public +export DNS_SERVER=8.8.8.8 +export IMAGE_URL_PATH=http://cloud.centos.org/centos/7/images +export IMAGE_FILE=CentOS-7-x86_64-GenericCloud-1510.qcow2 +export SWIFT_SERVER_URL=http://192.168.123.100:8080 +export ENABLE_PROXY=false +``` +#### Manually overriding configuration values + +If you do not have your environment variables set, or do not want them consumed, modify the variables in the following files under `cluster/openstack`: + +- **[config-default.sh](http://releases.k8s.io/{{page.githubbranch}}/cluster/openstack-heat/config-default.sh)** Sets all parameters needed for heat template. +- **[config-image.sh](http://releases.k8s.io/{{page.githubbranch}}/cluster/openstack-heat/config-image.sh)** Sets parameters needed to download and create new OpenStack image via glance. +- **[openrc-default.sh](http://releases.k8s.io/{{page.githubbranch}}/cluster/openstack-heat/openrc-default.sh)** Sets environment variables for communicating to OpenStack. These are consumed by the cli tools (heat, glance, swift, nova). +- **[openrc-swift.sh](http://releases.k8s.io/{{page.githubbranch}}/cluster/openstack-heat/openrc-swift.sh)** Some OpenStack setups require the use of seperate swift credentials. Put those credentials in this file. + +Please see the contents of these files for documentation regarding each variable's function. + +## Starting a cluster + +Once you've installed the OpenStack CLI tools and have set your OpenStack environment variables, issue this command: + +```sh +export KUBERNETES_PROVIDER=openstack-heat; curl -sS https://get.k8s.io | bash +``` +Alternatively, you can download a [Kubernetes release](https://github.com/kubernetes/kubernetes/releases) and extract the archive. To start your cluster, open a shell and run: + +```sh +cd kubernetes # Or whichever path you have extracted the release to +KUBERNETES_PROVIDER=openstack-heat ./cluster/kube-up.sh +``` +Or, if you are working from a checkout of the Kubernetes code base, and want to build/test from source: + +```sh +cd kubernetes # Or whatever your checkout root directory is called make clean make quick-release -./cluster/kube-up.sh +KUBERNETES_PROVIDER=openstack-heat ./cluster/kube-up.sh +``` +## Inspect your cluster + +Once kube-up is finished, your cluster should be running: + +```console +./cluster/kubectl.sh get cs +NAME STATUS MESSAGE ERROR +controller-manager Healthy ok +scheduler Healthy ok +etcd-1 Healthy {"health": "true"} +etcd-0 Healthy {"health": "true"} ``` -Alternatively, you can download [Kubernetes release](https://github.com/kubernetes/kubernetes/releases) and extract the archive. To start your local cluster, open a shell and run: +You can also list the nodes in your cluster: + +```console +./cluster/kubectl.sh get nodes +NAME STATUS AGE +kubernetesstack-node-ojszyjtr Ready 42m +kubernetesstack-node-tzotzcbp Ready 46m +kubernetesstack-node-uah8pkju Ready 47m +``` +Being a new cluster, there will be no pods or replication controllers in the default namespace: + +```console +./cluster/kubectl.sh get pods +./cluster/kubectl.sh get replicationcontrollers +``` + +You are now ready to create Kubernetes objects. + +## Using your cluster + +For a simple test, issue the following command: ```sh -cd kubernetes - -export KUBERNETES_PROVIDER=openstack -./cluster/kube-up.sh +./cluster/kubectl.sh run nginx --image=nginx --generator=run-pod/v1 ``` -The `KUBERNETES_PROVIDER` environment variable tells all of the various cluster management scripts which variant to use. If you forget to set this, the assumption is you are running on Google Compute Engine. - -## Interacting with your Kubernetes cluster with Openstack - -You can manage the nodes in your cluster with the Openstack WEB UI like Horizon or using heat or nova clients. - -To get all necessary information about cluster execute commands in main kubernetes directory: +Soon, you should have a running nginx pod: +```console +./cluster/kubectl.sh get pods +NAME READY STATUS RESTARTS AGE +nginx 1/1 Running 0 5m ``` + +Once the nginx pod is running, use the port-forward command to set up a proxy from your machine to the pod. + +```sh +./cluster/kubectl.sh port-forward nginx 8888:80 +``` + +You should now see nginx on [http://localhost:8888](). + +For more complex examples please see the [examples directory](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/). + +## Administering your cluster with Openstack + +You can manage the nodes in your cluster using the OpenStack CLI Tools. + +First, set your environment variables: + +```sh . cluster/openstack/config-default.sh . cluster/openstack/openrc-default.sh +``` + +To get all information about your cluster, use heat: + +```sh heat stack-show $STACK_NAME ``` -You will get cluster status and IP addresses for your master and minion nodes. +To see a list of nodes, use nova: -## Authenticating with your master - -Because you added public key to nodes you can easily ssh to them. - -``` -$ ssh minion@IP_ADDRESS +```sh +nova list --name=$STACK_NAME ``` -## Running containers +See the [OpenStack CLI Reference](http://docs.openstack.org/cli-reference/) for more details. -Your cluster is running, you can list the nodes in your cluster: +## SSHing to your nodes -```console -$ ./cluster/kubectl.sh get nodes -NAME LABELS STATUS AGE -kubernetesstack-node-tc9f2tfr kubernetes.io/hostname=kubernetesstack-node-tc9f2tfr Ready 21h +Your public key was added during the cluster turn-up, so you can easily ssh to them for troubleshooting purposes. + +```sh +ssh minion@IP_ADDRESS ``` -Before starting a container there will be no pods, services and replication controllers. +## Cluster deployment customization examples +You may find the need to modify environment variables to change the behaviour of kube-up. Here are some common scenarios: -```console -$ ./cluster/kubectl.sh get pods -NAME READY STATUS RESTARTS AGE +#### Proxy configuration +If you are behind a proxy, and have your local environment variables setup, you can use these variables to setup your Kubernetes cluster: -$ ./cluster/kubectl.sh get services -NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE - -$ ./cluster/kubectl.sh get replicationcontrollers -CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS +```sh +ENABLE_PROXY=true KUBERNETES_PROVIDER=openstack-heat ./cluster/kube-up.sh ``` -Now you are ready to create you first service and controller. +#### Setting different Swift URL +Some deployments differ from the default Swift URL: + +```sh + SWIFT_SERVER_URL="http://10.100.0.100:8080" KUBERNETES_PROVIDER=openstack-heat ./cluster/kube-up.sh +``` + +#### Public network name. +Sometimes the name of the public network differs from the default `public`: + +```sh +EXTERNAL_NETWORK="network_external" KUBERNETES_PROVIDER=openstack-heat ./cluster/kube-up.sh +``` + +#### Spinning up additional clusters. +You may want to spin up another cluster within your OpenStack project. Use the `$STACK_NAME` variable to accomplish this. + +```sh +STACK_NAME=k8s-cluster-2 KUBERNETES_PROVIDER=openstack-heat ./cluster/kube-up.sh +``` + +For more configuration examples, please browse the files mentioned in the [Configuration](#set-additional-configuration-values) section. + + +## Tearing down your cluster + +To bring down your cluster, issue the following command: + +```sh +KUBERNETES_PROVIDER=openstack-heat ./cluster/kube-down.sh +``` +If you have changed the default `$STACK_NAME`, you must specify the name. Note that this will not remove any Cinder volumes created by Kubernetes. From 853b38cb8604728b271ddc3c1f21b66593b92942 Mon Sep 17 00:00:00 2001 From: OHTAKE Tomohiro Date: Tue, 26 Apr 2016 09:56:31 +0900 Subject: [PATCH 3/7] openstack-heat provider uses Neutron and flannel hostgw --- docs/getting-started-guides/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started-guides/index.md b/docs/getting-started-guides/index.md index 0f213f5d52..fca33f5fa1 100644 --- a/docs/getting-started-guides/index.md +++ b/docs/getting-started-guides/index.md @@ -141,7 +141,7 @@ Bare-metal | custom | Ubuntu | Calico | [docs](/docs/gettin Bare-metal | custom | Ubuntu | flannel | [docs](/docs/getting-started-guides/ubuntu) | | Community ([@resouer](https://github.com/resouer), [@WIZARD-CXY](https://github.com/WIZARD-CXY)) libvirt/KVM | CoreOS | CoreOS | libvirt/KVM | [docs](/docs/getting-started-guides/libvirt-coreos) | | Community ([@lhuard1A](https://github.com/lhuard1A)) oVirt | | | | [docs](/docs/getting-started-guides/ovirt) | | Community ([@simon3z](https://github.com/simon3z)) -OpenStack | Saltstack | CentOS | flannel | [docs](/docs/getting-started-guides/openstack) | | Community ([@FujitsuEnablingSoftwareTechnologyGmbH](https://github.com/FujitsuEnablingSoftwareTechnologyGmbH)) +OpenStack | Saltstack | CentOS | Neutron + flannel hostgw | [docs](/docs/getting-started-guides/openstack) | | Community ([@FujitsuEnablingSoftwareTechnologyGmbH](https://github.com/FujitsuEnablingSoftwareTechnologyGmbH)) Rackspace | CoreOS | CoreOS | flannel | [docs](/docs/getting-started-guides/rackspace) | | Community ([@doublerr](https://github.com/doublerr)) any | any | any | any | [docs](/docs/getting-started-guides/scratch) | | Community ([@erictune](https://github.com/erictune)) From b58988db672efb893c1d1064f1091255bef0fea2 Mon Sep 17 00:00:00 2001 From: OHTAKE Tomohiro Date: Tue, 26 Apr 2016 09:58:32 +0900 Subject: [PATCH 4/7] Complete renaming the provider --- docs/getting-started-guides/index.md | 4 ++-- .../{openstack.md => openstack-heat.md} | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) rename docs/getting-started-guides/{openstack.md => openstack-heat.md} (98%) diff --git a/docs/getting-started-guides/index.md b/docs/getting-started-guides/index.md index fca33f5fa1..8a0e139dba 100644 --- a/docs/getting-started-guides/index.md +++ b/docs/getting-started-guides/index.md @@ -82,7 +82,7 @@ These solutions are combinations of cloud provider and OS not covered by the abo - [Vmware](/docs/getting-started-guides/coreos) (uses CoreOS and flannel) - [libvirt-coreos.md](/docs/getting-started-guides/libvirt-coreos) (uses CoreOS) - [oVirt](/docs/getting-started-guides/ovirt) -- [OpenStack](/docs/getting-started-guides/openstack) (uses CentOS and flannel) +- [OpenStack Heat](/docs/getting-started-guides/openstack-heat) (uses CentOS and flannel) - [libvirt](/docs/getting-started-guides/fedora/flannel_multi_node_cluster) (uses Fedora and flannel) - [KVM](/docs/getting-started-guides/fedora/flannel_multi_node_cluster) (uses Fedora and flannel) @@ -141,7 +141,7 @@ Bare-metal | custom | Ubuntu | Calico | [docs](/docs/gettin Bare-metal | custom | Ubuntu | flannel | [docs](/docs/getting-started-guides/ubuntu) | | Community ([@resouer](https://github.com/resouer), [@WIZARD-CXY](https://github.com/WIZARD-CXY)) libvirt/KVM | CoreOS | CoreOS | libvirt/KVM | [docs](/docs/getting-started-guides/libvirt-coreos) | | Community ([@lhuard1A](https://github.com/lhuard1A)) oVirt | | | | [docs](/docs/getting-started-guides/ovirt) | | Community ([@simon3z](https://github.com/simon3z)) -OpenStack | Saltstack | CentOS | Neutron + flannel hostgw | [docs](/docs/getting-started-guides/openstack) | | Community ([@FujitsuEnablingSoftwareTechnologyGmbH](https://github.com/FujitsuEnablingSoftwareTechnologyGmbH)) +OpenStack Heat | Saltstack | CentOS | Neutron + flannel hostgw | [docs](/docs/getting-started-guides/openstack-heat) | | Community ([@FujitsuEnablingSoftwareTechnologyGmbH](https://github.com/FujitsuEnablingSoftwareTechnologyGmbH)) Rackspace | CoreOS | CoreOS | flannel | [docs](/docs/getting-started-guides/rackspace) | | Community ([@doublerr](https://github.com/doublerr)) any | any | any | any | [docs](/docs/getting-started-guides/scratch) | | Community ([@erictune](https://github.com/erictune)) diff --git a/docs/getting-started-guides/openstack.md b/docs/getting-started-guides/openstack-heat.md similarity index 98% rename from docs/getting-started-guides/openstack.md rename to docs/getting-started-guides/openstack-heat.md index 8e5f1ef341..b7c6727da4 100644 --- a/docs/getting-started-guides/openstack.md +++ b/docs/getting-started-guides/openstack-heat.md @@ -66,7 +66,7 @@ export ENABLE_PROXY=false ``` #### Manually overriding configuration values -If you do not have your environment variables set, or do not want them consumed, modify the variables in the following files under `cluster/openstack`: +If you do not have your environment variables set, or do not want them consumed, modify the variables in the following files under `cluster/openstack-heat`: - **[config-default.sh](http://releases.k8s.io/{{page.githubbranch}}/cluster/openstack-heat/config-default.sh)** Sets all parameters needed for heat template. - **[config-image.sh](http://releases.k8s.io/{{page.githubbranch}}/cluster/openstack-heat/config-image.sh)** Sets parameters needed to download and create new OpenStack image via glance. @@ -160,8 +160,8 @@ You can manage the nodes in your cluster using the OpenStack CLI Tools. First, set your environment variables: ```sh -. cluster/openstack/config-default.sh -. cluster/openstack/openrc-default.sh +. cluster/openstack-heat/config-default.sh +. cluster/openstack-heat/openrc-default.sh ``` To get all information about your cluster, use heat: From 3b35a7a6b7cf682ff6172311dbb5f242fdd8017d Mon Sep 17 00:00:00 2001 From: Lukasz Zajaczkowski Date: Wed, 27 Apr 2016 13:13:20 +0200 Subject: [PATCH 5/7] Replace heat client to openstack client --- docs/getting-started-guides/openstack-heat.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started-guides/openstack-heat.md b/docs/getting-started-guides/openstack-heat.md index b7c6727da4..176e5fac09 100644 --- a/docs/getting-started-guides/openstack-heat.md +++ b/docs/getting-started-guides/openstack-heat.md @@ -18,7 +18,7 @@ If you already have the OpenStack CLI tools installed and configured, you can mo #### Install OpenStack CLI tools ```sh -sudo pip install -U --force 'python-heatclient==1.1.0' +sudo pip install -U --force 'python-openstackclient==2.4.0' sudo pip install -U --force 'python-swiftclient==3.0.0' sudo pip install -U --force 'python-glanceclient==2.0.0' sudo pip install -U --force 'python-novaclient==3.4.0' From a10e81cb63256714aea818ee8f1eb179fa2e9cba Mon Sep 17 00:00:00 2001 From: Elson O Rodriguez Date: Fri, 6 May 2016 15:16:40 -0700 Subject: [PATCH 6/7] Adding a list of OpenStack requirements for provider docs. --- docs/getting-started-guides/openstack-heat.md | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/docs/getting-started-guides/openstack-heat.md b/docs/getting-started-guides/openstack-heat.md index 176e5fac09..753d9eb13b 100644 --- a/docs/getting-started-guides/openstack-heat.md +++ b/docs/getting-started-guides/openstack-heat.md @@ -10,10 +10,17 @@ This guide will take you through the steps of deploying Kubernetes to Openstack The default OS is CentOS 7, this has not been tested on other operating systems. -This guide assumes you have a working OpenStack cluster. +This guide assumes you have a working OpenStack cluster with the following features: + +- Nova +- Neutron +- Swift +- Glance +- Heat +- DNS resolution of instance hostnames ## Pre-Requisites -If you already have the OpenStack CLI tools installed and configured, you can move on to the [Starting a cluster](#starting-a-cluster) section. +If you already have the required versions of the OpenStack CLI tools installed and configured, you can move on to the [Starting a cluster](#starting-a-cluster) section. #### Install OpenStack CLI tools @@ -49,7 +56,7 @@ export OS_REGION_NAME=regionName #### Set additional configuration values -In addition, here are some commonly changed variables specific to this provider, with example values. Under most circumstances you will not have to change these. +In addition, here are some commonly changed variables specific to this provider, with example values. Under most circumstances you will not have to change these. Please see files in the next section for a full list of options. ```sh export STACK_NAME=KubernetesStack From 51e89bff3b7edcd8d597158c74f57de9ff90a21c Mon Sep 17 00:00:00 2001 From: Elson O Rodriguez Date: Sun, 8 May 2016 23:16:29 -0700 Subject: [PATCH 7/7] Revised requirements for OpenStack kube-up provider. --- docs/getting-started-guides/openstack-heat.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/getting-started-guides/openstack-heat.md b/docs/getting-started-guides/openstack-heat.md index 753d9eb13b..033f5ce878 100644 --- a/docs/getting-started-guides/openstack-heat.md +++ b/docs/getting-started-guides/openstack-heat.md @@ -10,14 +10,16 @@ This guide will take you through the steps of deploying Kubernetes to Openstack The default OS is CentOS 7, this has not been tested on other operating systems. -This guide assumes you have a working OpenStack cluster with the following features: +This guide assumes you have access to a working OpenStack cluster with the following features: - Nova - Neutron - Swift - Glance - Heat -- DNS resolution of instance hostnames +- DNS resolution of instance names + +By default this provider provisions 4 m1.medium instances. If you do not have resources available, please see the [Set additional configuration values](#set-additional-configuration-values) section for information on reducing the footprint of your cluster. ## Pre-Requisites If you already have the required versions of the OpenStack CLI tools installed and configured, you can move on to the [Starting a cluster](#starting-a-cluster) section. @@ -56,7 +58,7 @@ export OS_REGION_NAME=regionName #### Set additional configuration values -In addition, here are some commonly changed variables specific to this provider, with example values. Under most circumstances you will not have to change these. Please see files in the next section for a full list of options. +In addition, here are some commonly changed variables specific to this provider, with example values. Under most circumstances you will not have to change these. Please see the files in the next section for a full list of options. ```sh export STACK_NAME=KubernetesStack