whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Spelling and other formatting changes.

Browse Source
This commit is contained in:
Matt Bruzek
2016-03-30 08:38:23 -05:00
parent a0dc91ccb5
commit 8ac73e38a1
1 changed files with 24 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/getting-started-guides/juju.md
+17 -16
View File
@@ -19,14 +19,14 @@ and tag the issue with "juju" so we can find them.
> Note: If you're running kube-up, on Ubuntu - all of the dependencies > Note: If you're running kube-up, on Ubuntu - all of the dependencies
> will be handled for you. You may safely skip to the section: > will be handled for you. You may safely skip to the section:
> [Launch Kubernetes Cluster](#launch-kubernetes-cluster) > [Launch a Kubernetes Cluster](#launch-a-kubernetes-cluster)
### On Ubuntu ### On Ubuntu
[Install the Juju client](https://jujucharms.com/get-started) [Install the Juju client](https://jujucharms.com/get-started)
> This documentation focuses on the juju 2.0 release which will be > This documentation focuses on the Juju 2.0 release which will be
> promoted to stable during its release cycle in April > promoted to stable during the April 2016 release cycle.
To paraphrase, on your local Ubuntu system: To paraphrase, on your local Ubuntu system:
@@ -46,9 +46,9 @@ If you are not using Ubuntu or prefer the isolation of Docker, you may
run the following: run the following:
> While this is a common target, the charmbox flavors of images are > While this is a common target, the charmbox flavors of images are
> unofficial, and should be treated as Experimental. If you encounter any issues > unofficial, and should be treated as experimental. If you encounter any issues
> turning up the Kubernetes cluster with charmbox, please file a bug on the > turning up the Kubernetes cluster with charmbox, please file a bug on the
> respective issue tracker [here](https://github.com/juju-solutions/charmbox/issues) > [charmbox issue tracker](https://github.com/juju-solutions/charmbox/issues).
```shell ```shell
mkdir ~/.juju2 mkdir ~/.juju2
@@ -69,7 +69,7 @@ command:
`juju bootstrap $cloudname $cloudtype` you are ready to launch the `juju bootstrap $cloudname $cloudtype` you are ready to launch the
Kubernetes cluster. Kubernetes cluster.
## Launch Kubernetes cluster ## Launch a Kubernetes cluster
You will need to export the `KUBERNETES_PROVIDER` environment variable before You will need to export the `KUBERNETES_PROVIDER` environment variable before
bringing up the cluster. bringing up the cluster.
@@ -82,9 +82,8 @@ cluster/kube-up.sh
If this is your first time running the `kube-up.sh` script, it will attempt to If this is your first time running the `kube-up.sh` script, it will attempt to
install the required dependencies to get started with Juju. install the required dependencies to get started with Juju.
Next it will deploy the kubernetes application, 3 units of etcd, and network Next it will deploy two nodes of Kubernetes, 1 unit of etcd, and network
the units with flannel based Software Defined Networking (SDN) so containers the units so containers on different hosts can communicate with each other.
on different hosts can communicate with each other.
## Exploring the cluster ## Exploring the cluster
@@ -187,7 +186,8 @@ CONTAINER IDIMAGE COMMAND CREATED STATUS PORTS NAMES
02beb61339d8quay.io/kelseyhightower/hello:latest /hello About an hour ago Up About an hourk8s_hello.... 02beb61339d8quay.io/kelseyhightower/hello:latest /hello About an hour ago Up About an hourk8s_hello....
``` ```
We see "kubernetes/1" has our container, we can open port 80: We see "kubernetes/1" has our container, expose the kubernetes charm and open
port 80:
```shell ```shell
juju run --unit kubernetes/1 "open-port 80" juju run --unit kubernetes/1 "open-port 80"
@@ -204,12 +204,13 @@ kubectl delete pods hello
``` ```
## Scale up cluster ## Scale up cluster
Whant larger kubernetes nodes? It is easy to request different sizes of cloud Want larger Kubernetes nodes? It is easy to request different sizes of cloud
resources from Juju by using **constraints**. You can increase the amount of resources from Juju by using **constraints**. You can increase the amount of
CPU or memory (RAM) in any of the systems requested by Juju. This allows you CPU or memory (RAM) in any of the systems requested by Juju. This allows you
to fine tune th Kubernetes cluster to fit your workload. Use the boostrap to fine tune th Kubernetes cluster to fit your workload. Use flags on the
command or as a seperate `juju constraints` command. Look to the bootstrap command or as a separate `juju constraints` command. Look to the
[Juju documentation for machine constraints](https://jujucharms.com/docs/devel/charms-constraints). [Juju documentation for machine constraints](https://jujucharms.com/docs/devel/charms-constraints)
details.
## Scale out cluster ## Scale out cluster
@@ -235,8 +236,8 @@ build directories.
./kube-down.sh ./kube-down.sh
``` ```
Alternately if you want stop the servers you can destroy your current Juju environment. Alternately if you want stop the servers you can destroy your current Juju
Use the `juju env` command to get the current environment name: environment. Use the `juju env` command to get the current environment name:
```shell ```shell
juju kill-controller `juju env` juju kill-controller `juju env`