Pages

Showing posts with label vCAC. Show all posts
Showing posts with label vCAC. Show all posts

Thursday, February 12, 2015

Creating a Fabric Group and Assigning a Compute Resource - Part 4

Now we have our tenant created, identity source assigned and roles assigned we can now create a fabric group to assign access to the underlying computer resources.

1. The first step is to change the context of which we are connecting to the vRealize Automation system, this involves connecting to our newly created tenant instead of the system. Enter the following command-line syntax to authenticate to the tenant and the IaaS system.



In this example we used the 'vra login userpass' command. For easy reference here are the parameters explained. Notice in the example above we are specifying the same credentials for both the tenant and the IaaS Service, this is because we assigned both the 'Tenant Admin' and Infrastructure Admin' roles to the account in my previous post.

 

 2. Now we are authenticated we can create the fabric group, enter the following command-line syntax:


In this example we used the 'vra fabricgroup add' command. For easy reference here are the parameters explained. Notice when you issue the command a hexadecimal value is returned, make a note of this value as we will need it later.



3. The previous step created the fabric group, but in order to allocate compute resources we need to perform a second step to tie the fabric group and compute resource together. For this we need to establish the unique identifier or Id for the compute resource. Enter the following command-line syntax to list all compute resources and make a note of the Id associated with the compute resource you want to assign.

 

4. Finally we need to issue an update command to the fabric group to link the compute resource, for this process we need to supply the Id of the fabric group (the hexadecimal value displayed on completion of step 2) and the Id of the compute resource from the table in step 3. For the purpose of this we are going to assign the compute resource Id associated with the Payload-01 friendly name which relates to my vSphere Cluster. Enter the following command-line syntax:

 
 
In this example we used the 'vra fabricgroup update' command. For easy reference here are the parameters explained.



Once complete this is what it look likes inside the vRealize Automation UI.










Wednesday, January 28, 2015

Launching CloudClient and Authenticating to vRealize Automation - Part 1

Before you can start using the CloudClient to perform command-line actions against your vRealize Automation (vRA) platform you have to authenticate to it. Whilst complete documentation is provided with the CloudClient download it does lack some examples of how to use the syntax, this post and others I'm yet to write will look to provide some of these examples based on my specific use cases.

The first step is to launch CloudClient, there are a couple of things to note here: 

a) you will need a Java Runtime Environment installed on the system where you re running the command-line too from.
b) the tool has two start-up scripts provide, one for Windows and one for Linux and these are now located in the /bin folder

1. Execute the correct start-up script, for my scenario I'm using a Windows server so we need to run C:\CloudClient\bin\cloudclient.bat. Assuming you have JVM installed correctly the CloudClient command-line tool will load and you will be presented with the following screen.


2a. Next we need to run the following command-line syntax to authenticate to the default tenant of the vRealize Automation system, from there we can run many commands against the platform.



2b. If you wanted to connect to a specific tenant and not the default tenant, then you can use the '--tenant' parameter as follows.



In the examples above we used the 'vra login userpass' command, but the tool also provides the ability to use a keyfile with the 'vra login keyfile' command. Now lets look at each of the parameters used in this example.