Permalink
Browse files

Merge pull request #48 from scottfrederick/vsphere

Polish BOSH deploy to vSphere pages.
  • Loading branch information...
2 parents b481d5b + d206852 commit 50313119ed530cdc567f5cdb253d7fd9c56d58e1 @scottfrederick scottfrederick committed Mar 7, 2013
@@ -1,93 +0,0 @@
-# Install and prepare vSphere Cluster#
-
-Before we start the cloudfoundry deployment we need to setup a vsphere cluster. In this guide we will be using minimal configuration to setup the cluster:
-
-1. 2 servers to install ESXi ( x core processor , y GB Ram : x and y depend on the hardware config chosen)
-2. 1 server to install vcenter(this can also be a vm in any of the esxi server)
-3. Storage server (SAN is recommended but you can also use other storages like openfiler)
-4. Switch
-5. Network : IP Ranges atleast 100 IPs
-
-##Install ESXi and vCenter##
-
-Cloud Foundry can be deployed on top of variety of Infrastructures, ESXi and vCenter happen to be one of them.
-There is no difference from the standard installation. After installation your ESXi will look like the image below
-
-![esxi] (/images/esxi5.png)
-
-##Prepare vCenter for Cloud Foundry Deployment##
-
-
-##Create the Datacenter##
-
-In vCenter, go to `Hosts and Clusters` then click on `Create a Datacenter`. A new datacenter will be created in the left panel. Give a suitable name and press the enter key.
-
-![datacenter](/images/datacenter.png)
-
-##Create a Cluster##
-
-Now the datacenter is created. Next task to create a Cluster and add ESXi hosts to the cluster.
-
-1. Select the datacenter we created in the above step.
-2. Click on `Create a cluster` link.
-3. `New cluster wizard` will open. Give a suitable name to the cluster, Click next and follow the wizard
-
-Once you finish, you can see the new cluster created in the left panel
-
-![cluster1] (/images/cluster1.png)
-
-
-###Create the resource pool###
-
-Create a resource pool.
-
-###Add the ESXi hosts to the cluster###
-
-1. Select the cluster we have created in the above step.
-2. Click on the `Add a Host` link
-3. `Add host wizard` will appear. Give the ip address/hostname and login credentials for the ESXi host. click next and follow the wizard
-
-Once you finish You can see the newly added host in the left panel
-
-![host1](/images/add_host.png)
-
-
-
-
-##Create the required folders for vms, templates and disk path##
-
-Micro BOSH and BOSH uses predefined locations for vms, template and disk_path that you will define in the deployment manifest.
-
-###Create the vm and template folder###
-
- 1. Click on Inventory, `Select Vms and Templates`
- 2. Select the datacenter we have created in the above steps.
- 3. Click on the `New folder` icon on the top of the left panel to create new folder
- 4. Create 4 folders as follows:
-
- + MicroBOSH\_VMs , MicroBOSH\_Templates (for micro bosh)
- + CF\_VMs, CF\_Templates ( for bosh)
-
-![vms_and_folders](/images/vms_templates.png)
-
-###Create the disk path###
-
-1. Click on Inventory, `Datastore and Datastore Clusters`
-2. Right clik the datastore in which you want to store the disks of vms, Select `Browse Datastore` . The Datastore will open in a new window.
-3. Click on the `Create new folder` on the top the window to create new folder.
-4. Create 2 folders as follows:
-
-MicroBOSH\_Disks ( for micro bosh)
-CF\_Disks( for bosh)
-
-![datastore1] (/images/datastore.png)
-
-
-###Summary. ###
-vSphere 5.x cluster is ready for Cloud Foundry deployment
-
-
-
-
-
-

Large diffs are not rendered by default.

Oops, something went wrong.
@@ -2,142 +2,161 @@
title: Deploying BOSH with Micro BOSH
---
-# Deploy BOSH as an application using micro BOSH. #
+This guide describes the process for deploying BOSH as an application using micro BOSH.
-1. Deploy micro BOSH. See the steps in the [previous section](deploying_micro_bosh.html)
+## <a id="prerequisites"></a>Prerequisites ##
-1. Once your micro BOSH instance is deployed, you can target its Director:
+* Micro BOSH should be deployed. See the steps in the [previous section](deploying_micro_bosh.html)
- $ bosh micro status
- ...
- Target micro (http://11.23.194.100:25555) Ver: 0.3.12 (00000000)
+## <a id="target"></a>Target Micro BOSH ##
- $ bosh target 11.23.194.100
- Target set to 'your-micro-BOSH'
- Your username: admin
- Enter password: *****
- Logged in as 'admin'
+Once your micro BOSH instance is deployed, you can target its Director:
- $ bosh status
- Updating director data... done
+<pre class="terminal">
+$ bosh micro status
+...
+Target micro (http://11.23.194.100:25555) Ver: 0.3.12 (00000000)
- Director
- Name your-micro-BOSH
- URL http://11.23.194.100:25555
- Version 0.5.2 (release:ffed4d4a bosh:21e0b0bc)
- User admin
- UUID 729b6100-4035-4b35-ab9a-cf8299719fe3
- CPI vsphere
+$ bosh target 11.23.194.100
+Target set to 'your-micro-BOSH'
+Your username: admin
+Enter password: *****
+Logged in as 'admin'
- Deployment
- not set
+$ bosh status
+Updating director data... done
-_Note: Create a new user using `bosh create user` which overrides the default username / password_
+Director
+ Name your-micro-BOSH
+ URL http://11.23.194.100:25555
+ Version 0.5.2 (release:ffed4d4a bosh:21e0b0bc)
+ User admin
+ UUID 729b6100-4035-4b35-ab9a-cf8299719fe3
+ CPI vsphere
-### Download a BOSH stemcell
+Deployment
+ not set
+</pre>
-1. List public stemcells with bosh public stemcells
+*Note*: Create a new user using `bosh create user` which overrides the default username and password.
- $ mkdir -p ~/stemcells
- $ cd ~/stemcells
- $ bosh public stemcells
+## <a id="download-stemcell"></a>Download a BOSH Stemcell ##
- +---------------------------------------+------------------------+
- | Name | Tags |
- +---------------------------------------+------------------------+
- | bosh-stemcell-aws-0.6.4.tgz | aws, stable |
- | bosh-stemcell-vsphere-0.6.4.tgz | vsphere, stable |
- | bosh-stemcell-vsphere-0.6.7.tgz | vsphere, stable |
- | micro-bosh-stemcell-aws-0.6.4.tgz | aws, micro, stable |
- | micro-bosh-stemcell-vsphere-0.6.4.tgz | vsphere, micro, stable |
- +---------------------------------------+------------------------+
- To download use `bosh download public stemcell <stemcell_name>'. For full url use --full.
+List public stemcells with the `bosh public stemcells` command:
+<pre class="terminal">
+$ mkdir -p ~/stemcells
+$ cd ~/stemcells
+$ bosh public stemcells
-1. Download a public stemcell. *NOTE, in this case you do not use the micro bosh stemcell.*
++---------------------------------------+------------------------+
+| Name | Tags |
++---------------------------------------+------------------------+
+| bosh-stemcell-aws-0.6.4.tgz | aws, stable |
+| bosh-stemcell-vsphere-0.6.4.tgz | vsphere, stable |
+| bosh-stemcell-vsphere-0.6.7.tgz | vsphere, stable |
+| micro-bosh-stemcell-aws-0.6.4.tgz | aws, micro, stable |
+| micro-bosh-stemcell-vsphere-0.6.4.tgz | vsphere, micro, stable |
++---------------------------------------+------------------------+
+To download use `bosh download public stemcell <stemcell_name>'. For full url use --full.
+</pre>
- $ bosh download public stemcell bosh-stemcell-vsphere-0.6.7.tgz
+Download a public stemcell. *Note*: in this case you do not use the micro bosh stemcell.
-1. Upload the downloaded stemcell to micro BOSH.
+<pre class="terminal">
+$ bosh download public stemcell bosh-stemcell-vsphere-0.6.7.tgz
+</pre>
- $ bosh upload stemcell bosh-stemcell-vsphere-0.6.7.tgz
+Upload the downloaded stemcell to micro BOSH.
-1. You can see the uploaded stemcells (on your Micro BOSH) by using `bosh stemcells`
+<pre class="terminal">
+$ bosh upload stemcell bosh-stemcell-vsphere-0.6.7.tgz
+</pre>
- $ bosh stemcells
+You can see the uploaded stemcells (on your Micro BOSH) by using `bosh stemcells`:
- +---------------+---------+-----------------------------------------+
- | Name | Version | CID |
- +---------------+---------+-----------------------------------------+
- | bosh-stemcell | 0.6.7 | sc-1033810d-f3ff-42b5-8d39-58cb035638fc |
- +---------------+---------+-----------------------------------------+
+<pre class="terminal">
+$ bosh stemcells
-### Upload a BOSH release ###
++---------------+---------+-----------------------------------------+
+| Name | Version | CID |
++---------------+---------+-----------------------------------------+
+| bosh-stemcell | 0.6.7 | sc-1033810d-f3ff-42b5-8d39-58cb035638fc |
++---------------+---------+-----------------------------------------+
+</pre>
-1. Rather than creating a new release, we will use the public release from in the [local setup instructions](../bosh/setup/index.html).
+## <a id="upload-release"></a>Upload a BOSH release ##
- $ cd ~/bosh-release
- $ bosh upload release releases/bosh-11.yml
+Rather than creating a new release, we will use the public release from in the [local setup instructions](../../bosh/setup/index.html).
+<pre class="terminal">
+$ cd ~/bosh-release
+$ bosh upload release releases/bosh-11.yml
+</pre>
-### Setup a BOSH deployment manifest and deploy ###
+## <a id="deploy"></a>Setup a BOSH Deployment Manifest and Deploy ##
-1. Create and setup a BOSH deployment manifest. Look at the [BOSH example manifest](./bosh-example-manifest.html).
+Create and setup a BOSH deployment manifest. Look at the [BOSH example manifest](./bosh-example-manifest.html).
-1. Deploy bosh. (the following assumes your manifest is named `bosh.yml` in `/home/bosh_user`).
+Deploy BOSH. (the following assumes your manifest is named `bosh.yml` in `/home/bosh_user`).
- $ cd /home/bosh_user
- $ bosh deployment bosh.yml
+<pre class="terminal">
+$ cd /home/bosh_user
+$ bosh deployment bosh.yml
- Deployment set to `/home/bosh_user/bosh.yml'
-
- $ bosh deploy
-
- Getting deployment properties from director...
- Unable to get properties list from director, trying without it...
- Compiling deployment manifest...
- Cannot get current deployment information from director, possibly a new deployment
- Please review all changes carefully
- Deploying `bosh.yml' to `your-micro-BOSH' (type 'yes' to continue): yes
-
- Director task 5
-
- Preparing deployment
- binding deployment (00:00:00)
- binding releases (00:00:00)
- binding existing deployment (00:00:00)
- binding resource pools (00:00:00)
- binding stemcells (00:00:00)
- binding templates (00:00:00)
- binding unallocated VMs (00:00:00)
- binding instance networks (00:00:00)
- Done 8/8 00:00:00
-
- Preparing package compilation
- finding packages to compile (00:00:00)
- Done 1/1 00:00:00
-
- Preparing DNS
- binding DNS (00:00:00)
- Done 1/1 00:00:00
-
- Creating bound missing VMs
- small/0 (00:00:50)
- small/4 (00:01:02)
- small/1 (00:01:19)
- small/2 (00:01:22)
- small/3 (00:01:24)
- director/0 (00:01:26)
- Done 6/6 00:01:26
-
-_Note: There will be a lot of status information in addition to the above output_
-
-### Verification
-
-1. The example bosh director has the ip address 172.20.134.52. Targeting this director with `bosh target 172.20.134.52` will verify a successful installation.
-
- bosh target 172.20.134.52
- Target set to 'your-director'
- Your username: admin
- Enter password: *****
- Logged in as `admin'
+Deployment set to `/home/bosh_user/bosh.yml'
+
+$ bosh deploy
+
+Getting deployment properties from director...
+Unable to get properties list from director, trying without it...
+Compiling deployment manifest...
+Cannot get current deployment information from director, possibly a new deployment
+Please review all changes carefully
+Deploying `bosh.yml' to `your-micro-BOSH' (type 'yes' to continue): yes
+
+Director task 5
+
+Preparing deployment
+ binding deployment (00:00:00)
+ binding releases (00:00:00)
+ binding existing deployment (00:00:00)
+ binding resource pools (00:00:00)
+ binding stemcells (00:00:00)
+ binding templates (00:00:00)
+ binding unallocated VMs (00:00:00)
+ binding instance networks (00:00:00)
+Done 8/8 00:00:00
+
+Preparing package compilation
+ finding packages to compile (00:00:00)
+Done 1/1 00:00:00
+
+Preparing DNS
+ binding DNS (00:00:00)
+Done 1/1 00:00:00
+
+Creating bound missing VMs
+ small/0 (00:00:50)
+ small/4 (00:01:02)
+ small/1 (00:01:19)
+ small/2 (00:01:22)
+ small/3 (00:01:24)
+ director/0 (00:01:26)
+Done 6/6 00:01:26
+</pre>
+
+*Note*: There will be a lot of status information in addition to the above output.
+
+## <a id="verify"></a>Verification ##
+
+The example BOSH director has the IP address `172.20.134.52`. Targeting this director with `bosh target 172.20.134.52` will verify a successful installation.
+
+<pre class="terminal">
+$ bosh target 172.20.134.52
+Target set to 'your-director'
+Your username: admin
+Enter password: *****
+Logged in as `admin'
+</pre>
+
Oops, something went wrong.

0 comments on commit 5031311

Please sign in to comment.