{"id":4041,"date":"2016-11-16T20:00:38","date_gmt":"2016-11-17T02:00:38","guid":{"rendered":"http:\/\/www.jasemccarty.com\/blog\/?p=4041"},"modified":"2020-02-16T19:44:53","modified_gmt":"2020-02-17T01:44:53","slug":"vsan-witness-in-vca-p4","status":"publish","type":"post","link":"https:\/\/www.jasemccarty.com\/blog\/vsan-witness-in-vca-p4\/","title":{"rendered":"The vSAN Witness Appliance in vCloud Air: Part 4 (Deployment)"},"content":{"rendered":"

In Part 2<\/a>, the process of uploading a vSAN Witness Appliance to an organization’s Catalog was detailed. Part 3<\/a> covered the process of creating networks for the vSAN Witness Appliance.<\/p>\n

What’s Next?<\/strong><\/p>\n

With the vSAN Witness Appliance OVA converted and uploaded to vCloud Air, and connectivity in place to the networks that will be used, the next step is to deploy an appliance.<\/p>\n

This can be done from the normal vCloud Air interface, but we won’t be able to power on our Witness Appliance due to a password missing. It will be easier to accomplish this using the vCloud Director interface of vCloud Air.<\/p>\n

From the vCloud Air Dashboard, select Manage Catalogs in vCloud Director.<\/p>\n

<\/a><\/p>\n

This will open up the vCloud Director interface in the Catalog section and select a catalog. The catalog the Witness Appliance was uploaded to in Part 1<\/a> was VSAN_WITNESS.<\/p>\n

<\/span>A catalog can contain multiple vApps, which can have one or more virtual machines in it.<\/p>\n

\"vsancd3\"<\/a><\/p>\n

After choosing the vSAN_WITNESS_6.5 that was uploaded in Part 1 and selecting Add to My Cloud<\/strong> wizard will start the process of deploying this vApp.<\/p>\n

<\/center><\/p>\n
<\/div>\n