From fcd2156b29473d14a05f6b02ac3d8d6a4656240c Mon Sep 17 00:00:00 2001 From: Nirdesh Shukla Date: Fri, 28 Apr 2017 06:47:55 -0700 Subject: [PATCH] VUM based installation steps (fixes #555) [SKIP CI] (#1206) --- jekyll-docs/install.md | 25 +++++++++++++++++++++---- 1 file changed, 21 insertions(+), 4 deletions(-) diff --git a/jekyll-docs/install.md b/jekyll-docs/install.md index ae12d5364..e02e996fd 100644 --- a/jekyll-docs/install.md +++ b/jekyll-docs/install.md @@ -3,10 +3,27 @@ title: Installation --- The installation has two parts – installation of the vSphere Installation Bundle (VIB) on ESXi and installation of Docker plugin on the hosts where you plan to run containers with storage needs. - -## Installation on ESXi -ESXi component for vDVS is available in the form of a [VIB](https://blogs.vmware.com/vsphere/2011/09/whats-in-a-vib.html). VIB stands for vSphere Installation Bundle. At a conceptual level a VIB is somewhat similar to a tarball or ZIP archive in that it is a collection of files packaged into a single archive to facilitate distribution. +## Installation on ESXi + +[VIB](http://blogs.vmware.com/vsphere/2011/09/whats-in-a-vib.html) and [Offline Depot](https://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.install.doc/GUID-29491174-238E-4708-A78F-8FE95156D6A3.html?resultof=%2522%256f%2566%2566%256c%2569%256e%2565%2522%2520%2522%256f%2566%2566%256c%2569%256e%2522%2520%2522%2564%2565%2570%256f%2574%2522%2520) are the packages built to install the backend for the service on ESX. The backend can be installed using esxcli or vmware tools such as [VUM](http://pubs.vmware.com/vsphere-60/topic/com.vmware.ICbase/PDF/vsphere-update-manager-601-install-administration-guide.pdf) + +### VUM based VIB installation +ESXi component for vDVS is available in the form of an [Offline Depot](http://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.install.doc/GUID-29491174-238E-4708-A78F-8FE95156D6A3.html) and available to download latest release as [ZIP archive](https://bintray.com/vmware/vDVS/VIB/_latestVersion). + +After downloading VIB bundle as zip format, installation is performed using VUM using the following steps. + +1. Go to *admin view* in update manager tab. +2. Import zip bundle using *import zip* option. +3. Create a baseline and include zip bundle. +4. Scan your host against baseline. +5. *Remediate* host. + +More information can be found at [VUM User guide](https://featurewalkthrough.vmware.com/#!/vsphere-6-5/vsphere-update-manager-overview-cluster-upgrade/1). + +### VIB installation through esxcli/localcli + +ESXi component for vDVS is available in the form of a [VIB](https://blogs.vmware.com/vsphere/2011/09/whats-in-a-vib.html). VIB stands for vSphere Installation Bundle. At a conceptual level a VIB is similar to a tarball or ZIP archive in that it is a collection of files packaged into a single archive to facilitate distribution. Log into ESXi host and download the [latest release](https://bintray.com/vmware/vDVS/VIB/_latestVersion) of vDVS driver VIB on the ESXi. Assuming that you have downloaded the VIB at /tmp location you can run the below command to install it on ESXi @@ -22,7 +39,7 @@ Installation Result ## Installation on Docker Hosts -vDVS plugin can be installed on Docker hosts like any docker plugin installation. You will need docker version **1.13/17.03 or above** on the VM. In a large pool of nodes, you can push the plugin installation to multiple VM through a configuration management tool such as Ansible/Salt or using a remote shell session. The installation of plugin is really simple and we will walk through the steps to install/uninstall, enable and verify the plugin installation. +vDVS plugin can be installed on Docker hosts like any docker plugin installation. You will need docker version **1.13/17.03 or above** on the VM. In a large pool of nodes, you can push the plugin installation to multiple VM through a configuration management tool such as Ansible/Salt or using a remote shell session. The installation of plugin is really simple and we will walk through the steps to install/uninstall, enable and verify the plugin installation. The plugin is available as a docker image on the public docker registry but if you are using a private registry, you will have to point to the appropriate URL of the image.