VMware vCenter Appliance 6.0 can be deployed in two different manners. Through the GUI as I detailed that in my post here, or second way – by using scripted installation. Scripted installation allows you to stay consistent when deploying multiple isolated sites with multiple vCenter Appliances and PSC for example.
Now if you’re not a scripting guy it’s ok, because VMware has done a good job providing templates allowing just to modify them. Additionaly the help file explains all the options. There is 5 different templates available.
If you have read my detailed post about vCenter Server 6 where I’m detailing this you would be able to see that a new component called Platform Service Component (PSC) was introduced in vCenter Server 6. It’s important to know that PSC contains different important vCenter services like SSO , Certificate or Licensing services…. but from the deployment standpoint it’s single component.
The Platform service controller can be deployed as internal (embedded within vCenter) or it can run as an external component to vCenter. The guidelines from VMware says to use PSC as internal for up to 8 vCenter servers.
Five Templates for vCenter Appliance 6.0 Scripted Installation are available
Those 5 Examples are:
Embedded – this one deploys VCSA with an embedded PSC (All-in-One VM)
Full Conf – this one is used by the VCSA CLI installer
PSC – this one deploys a PSC only.
PSC Replication – this one deploys a PSC (only) and joins an existing SSO domain.
VC – deploys a vCenter Server as an option only (without SSO)
Now Let’s open the Embedded.example.JSON to see what’s in and how to personalize:
Shop for vSphere licenses at VMware Store:
- vSphere Essentials Plus – vMotion, HA… 3 Hosts, vCenter
- vSphere Essentials – 3 Hosts, vCenter
- vSphere Standard – Per Physical CPU license
As you can see the left image shows the personalized version where the right one shows the “clean” not personalized one. No need to explain, really. Just replace the example values by your values of your environment… Note that I just added the networking section the example file does not contain it. (copy paste from Full Conf does the job).
Step 1. Before starting the deployment you must assure that on your DNS server you have created DNS records (forward and reverse)… You can do so when you Go to the Control panel > Administrative Tools > DNS > Expand the Forward lookup zones > Right click your zone > New Host ( A or AAAA).
Step 2: Modify your JSON file (as on my example – get it here) and save a copy to some folder on your system. (In my case I saved the file to c:vcsa with a name vladan_embedded.json )
Step 3: Open command prompt (with admin rights) > go to the vcsa deployment directory on the mounted ISO, if you’re running Windows workstation or laptop (in my case it is the drive letter “I”, so in my case it is I:vcsa-cli-installerwin32 ) > run this command:
so in my case:
and let the installer do its work…
In my case, it took about 20 min to fully deploy the appliance so it’s not much faster than when using the GUI, but to get through the GUI it takes you perhaps few min more to enter all the details. So at the end the scripted installer finishes faster and also it check for errors in the JSON file (I had some). Get my JSON config file if you want from here.
Get Help with an Online Help File
There is an online help which might be useful. When you are in the command line just type:
to get help. Those help command can be more helpful, for example, you can type
vcsa-deploy –template -h
to get just more detailed help as the –template -h is help for the vCenter server appliance CLI installer template. Each of the sections is explained. There are six sections in total:
For example, the database section looks like this:
database: This list of parameters describes the database that vCenter Server Appliance will use.
It contains the following keys:
type: The database type. Available options are ’embedded’ and ‘external’. The default is ’embedded’.
user: The external database user account name. Ignored if the parameter db.type is ’embedded’.
password: The external database user password. Ignored if the parameter db.type is ’embedded’.
servername: The external database server host name. Ignored if the parameter db.type is ’embedded’.
serverport: The port number on which the external database is running. Ignored if the parameter db.type is ’embedded’.
provider: The external database provider. The available option is ‘oracle’. Ignored if the parameter db.type is ’embedded’.
instance: The external database instance name. Ignored if the parameter db.type is ’embedded’.
Note that I did speed up the video after entering the initial command and start of the deployment otherwise, it took 11 min to fully deploy the appliance. I used local SSD as target datastore.
I was quite nicely surprised that the work with the deployment template is quite without a problem and easy. The online help file can certainly be helpful when preparing larger deployments and needs to use an external database for each site. As I said for me it’s been a nice surprise as being not really a scripting guy I found it quite easy to follow. The fact that scripted installer can use a simple JSON file for deployment has an advantage over manual one because admin does fewer mistakes during deployment and homogenization of larger environment shall be easier.
More on vSphere 6 can be found on my dedicated vSphere 6.0 page.
- VMware VCSA – 3 Ways to Activate SSH
- VMware VCSA – How to check running services?
- VMware VCSA – How to Join Domain