CLI install of PSC and VCSA 6.5 Update 1

With the release of vSphere 6, VMware has introduced CLI install of PSC and VCSA for all types of architecture designs like Embedded PSC, External PSC install and good thing is you can also migrate the existing Windows based instances of PSC and vCenter to Appliances. In this post i will first try a green field install of Appliances using CLI and next work on the migration, i believe its almost similar.

VCSA installer ISO has a set of predefined templates for everyone’s architecture to help with PSC install or migration to appliance. To be able to install a vCenter Appliance with an External PSC, like with any other topology, you first have to install PSC so choose the json file PSC_first_instance_on_ESXi.json from the templates folder in ISO.

Note: Ensure you have created the necessary DNS records for the name and IP resolution of the PSC and VSCA appliances

2017-08-15 20_25_03-install

Modify the json file with a IDE and fill in all the details needed. Below is a sample of the modified file for my lab environment.

2017-08-15 20_30_32-C__Users_CHIN2_Desktop_PSC_first_instance_on_ESXi.json - Notepad++

Once saved, use a Powershell or cmd to navigate to the mounted ISO, from there run the below commands by pointing the modified json file. In my case, i saved the json file on my Desktop.

Use the switch –verify-only to perform validation of the given parameters.

.\vcsa-deploy.exe install --accept-eula --verify-only --no-esx-ssl-verify <path to json file>

2017-08-02 21_56_19-AD - VMware Workstation

You should see the installer perform validations as below.

2017-08-02 21_58_15-AD - VMware Workstation

Once all the validations are successfull, remove the verify-only switch and run the command again to perform the actual deploy.

2017-08-02 21_58_55-AD - VMware Workstation

Similar to the GUI install, CLI also performs the install in two steps, deploys the OVF and then configures with the settings in json file. Ensure you receive a successfull deployed message.

2017-08-02 22_17_15-AD - VMware Workstation

Now its time to deploy the VCSA appliance. To do that we make use of the json file vCSA_on_ESXi.json, edit the json file as per the network requirements. Similar to the PSC deploy, run the below command to install the VCSA after doing a –verify-only

.\vcsa-deploy.exe install --accept-eula --no-esx-ssl-verify <path to json file>

2017-08-02 22_04_58-AD - VMware Workstation

Make sure you see the below message, indicating the successful install of vCSA

2017-08-02 22_38_30-AD - VMware Workstation

Once the Applianes are installed you should be able to verify the sae by logging into the web-client or the HTML 5 client, now called as vSphere Client



#cli-install, #external-psc, #json, #psc, #vcsa-6-5-update-1-cli, #vcsa-cli

Part 9 – Ansible Roles

As of now we have written playbooks that include all the details like hosts, variables, tasks and plays. This is not an ideal way if we have many tasks and lots and lots of plays to be included, the best way to do it is to separate each item into its own directory and this is how its done in prodution especially if a organization use cloud. So let’s do some Role things. Continue reading

#include, #main-yml, #roles, #roles-structure

Part 8 – Ansible Play Recap, vars, Notify, Handlers

PlayBooks are a great thing, but how are we going to handle exceptions, what about errors during the tasks? what if we want to specify a condition before executing the task? How are we going to declare variables? This post is for those things. Continue reading

#handlers, #limit, #notify, #recap, #vars, #when

Part 7 – Ansible Tasks, Plays, PlayBooks

PlayBooks is the term used in Ansible to represent a configuration management scripts written in YAML. Tasks are the operations that needs to be done on the remote machines, hosts are the remote machines on which the tasks are to be executed. Tasks are always associated with hosts and this together is called a Play. PlayBook is a collection of such Plays. Continue reading

#gather_facts, #play, #playbooks, #tasks

Part 6 – Ansible Modules

Modules are packages that can perform a set of operations on remote hosts based on the arguments given. Without knowing much about modules, we have already used a “ping” module to test our ansible lab configuration. Without any further do, let’s understand Ansible modules in a bit detail. Continue reading

#ansible-doc, #copy, #modules, #service, #yum

Part 5 – Ansible Config

Ansible config file has the default settings that most users are ok to run with. However the settings can be modified like the number of parallel tasks to run at a time, default location of inventory, jinja2 extensions, log_path, private key file and so on. Continue reading

#etcansible, #ansible-cfg, #host_key_checking

Part 4 – More about Inventory File

We know a little about inventory file as of now, like, it has the list of hostnames that a controller node could communicate with. But, there is a lot a inventory file can do and we in this post will touch a bit on some of the features. Continue reading

#group_vars, #host_vars, #inventory-file, #variable-scope-and-precedence