Tag Archive for vCO

Deploying Orchestrator 6.0.3 into vSphere 6

vRARobot2

Deploying Orchestrator 6.0.3 into vSphere 6

Software versions in my lab environment

  • vCenter v6.0.0, 3018524
  • vSphere Hosts v6.0.0, 3029758
  • VMware-vCO-Appliance-6.0.3.0-3000579_OVF10.ovf

and

screen-shot-2016-11-23-at-11-01-06

Instructions

  • Download and deploy VMware-vCO-Appliance-6.0.3.0-3000579_OVF10.ovf into vCenter – File > Deploy ovf template

screen-shot-2016-11-22-at-20-26-33 screen-shot-2016-11-22-at-20-26-47 screen-shot-2016-11-22-at-20-28-11 screen-shot-2016-11-22-at-20-28-35 screen-shot-2016-11-22-at-20-29-07 screen-shot-2016-11-22-at-20-29-36 screen-shot-2016-11-22-at-20-29-59 screen-shot-2016-11-22-at-20-30-47 screen-shot-2016-11-22-at-20-31-58 screen-shot-2016-11-22-at-20-35-35 screen-shot-2016-11-22-at-20-37-18

  • Power on the VM
  • Log into a web browser using the Orchestrator appliance web address. In my case https://192.168.1.123:5480

screen-shot-2016-11-22-at-20-52-23

  • Change the time zone to Europe/London or whichever your timezone is and click Save Settings

screen-shot-2016-11-22-at-20-53-03

  • Click the Network tab and check the settings on the 3 tabs

screen-shot-2016-11-22-at-20-54-10 screen-shot-2016-11-22-at-20-56-20 screen-shot-2016-11-22-at-20-57-02

  • Click the Admin tab and click Time Settings are correct. I have Use Host Time but you can use Time Server

screen-shot-2016-11-22-at-20-57-49 screen-shot-2016-11-22-at-20-58-59

  • Click Save Settings

NEXT

  • Log into a web browser using the Orchestrator web address. In my case https://192.168.1.123:8283
  • Use the vmware username and the password you set up in the OVF deployment

screen-shot-2016-11-22-at-21-01-17

  • You will reach the below screen

screen-shot-2016-11-22-at-21-02-27

  • Click on the Network tab on the left hand side and select your IP Address and check all other details are correct. Click Apply Changes at the bottom right of the screen

screen-shot-2016-11-22-at-21-03-40

  • Click on Authentication and scroll down the screen until you see a link for SSL Certificates. Click on this link

screen-shot-2016-11-22-at-21-05-05

  • Put in your vCenter server in the following format – techlabvcs001.techlab.local:7444 and click Import

screen-shot-2016-11-22-at-21-08-01 screen-shot-2016-11-22-at-21-21-36

  • Put in your Single Sign On/PSC server in the following format – techlapsc001.techlab.local:7444 and click Import

screen-shot-2016-11-22-at-21-12-04 screen-shot-2016-11-22-at-21-14-28

  • Go back to the Authentication tab
  • Put in your Single Sign On server and click Advanced
  • put in your Admin username and password
  • Click Register Orchestrator

screen-shot-2016-11-22-at-21-23-15

  • It should look like the below with further configuration to do

screen-shot-2016-11-22-at-21-24-52

  • Choose your SSO Domain which can be the local domain, LAN domain or the vsphere.local domain.
  • In my case I chose my main domain techlab.local where I have set up a group called vro-group which contains user accounts I want to use as Admins

screen-shot-2016-11-22-at-21-26-22

  • Click Accept Orchestrator Configuration

screen-shot-2016-11-22-at-21-28-40

  • Click Test login and try one of your users

screen-shot-2016-11-22-at-21-30-20

  • Check your license

screen-shot-2016-11-22-at-21-33-50

  • Check the Plugins are all ok

screen-shot-2016-11-22-at-21-34-50

  • Click Startup options and restart both services
  • Log back in and check everything is green

screen-shot-2016-11-22-at-21-36-17 screen-shot-2016-11-22-at-21-37-48 NEXT

  • Open a web page and navigate to your Orchestrator configuration page which in my case is https://techlaborc001.techlab.local:8281
  • Click on Start Orchestrator Client

screen-shot-2016-11-22-at-23-17-55

  • Click on the drop down to Design
  • Navigate to Library > Microsoft > Active Directory > Configuration > Add an Active Directory server
  • Add in the relevant details for your AD server and add others as necessary

screen-shot-2016-11-22-at-23-19-53 screen-shot-2016-11-22-at-23-17-19

  • Next navigate to Library > vCenter > Configuration > Add a vCenter Instance

screen-shot-2016-11-22-at-23-23-34

  • Click Next and fill in the next screen

screen-shot-2016-11-22-at-23-24-27

  • Next we need to run the workflow Register vCenter Orchestrator as a vCenter extension

screen-shot-2016-11-22-at-23-27-40

  • Next type in the external address to advertise this Orchestrator
  • this needs to be for example https://techlaborc001.techlab.local:8281

screen-shot-2016-11-22-at-23-30-38

  • It should say it has been registered as per below

screen-shot-2016-11-22-at-23-32-04

  • We can check it has been registered by opening a web browser and putting in the vCenter server address as per below
  • https://techlabvcs001.techlab.local/mob
  • Click on Content

screen-shot-2016-11-22-at-23-34-17

  • Click on ExtensionManager

screen-shot-2016-11-22-at-23-34-51

  • Look for extensionList[“com.vmware.vco”] which should only exist when the workflow has run correctly.

screen-shot-2016-11-22-at-23-35-44

  • Click on Client

screen-shot-2016-11-22-at-23-37-23

  • You should see the below in url string. This will also appear in the Web Client which we’ll see further on in the instructions
  • You can put this link into a web browser and it should try and download the zip

screen-shot-2016-11-22-at-23-38-00

  • If you need to remove an extension, follow this useful blog below

Removing extensions link http://blog.mwpreston.net/2014/05/02/to-the-point-removing-stranded-vcenter-orchestrator-servers-from-vcenter

  • You now need to restart the web client
  • When the Web Client has restarted and come up again, Go to the Home screen and select the Orchestrator icon

screen-shot-2016-11-22-at-23-53-49

  • You should now see the vCenter and the Orchestrator server listed and you’ll see the information which we saw in the mob web page

screen-shot-2016-11-22-at-23-56-07

  • If you click on Workflows under Inventory trees, you will see the whole library of workflows

screen-shot-2016-11-22-at-23-57-45

  • You can then use the inbuilt workflows or create your own in Orchestrator
  • If you run the List the vCenter Orchestrator extensions of vCenter server, you will see it will pop up in the Recent Tasks list at the bottom of vCenter

screen-shot-2016-11-22-at-23-59-13

  • Pretty funky stuff 🙂

Next

  • In the vSphere Web Client > Click Home > Orchestrator, click on the Workflow icon and expand vCenter > Virtual Machine Management > Basic

screen-shot-2016-11-28-at-14-24-30

screen-shot-2016-11-28-at-14-25-38

  • Right click “Create simple virtual machine”, here is where you can run a workflow directly from within vSphere Web Client.

screen-shot-2016-11-28-at-14-27-55

 

Installing the Linux Log Insight agent on the vCenter Orchestrator appliance

vRARobot2

Installing the Linux Log Insight agent on vCenter Orchestrator

The Log Insight agent now gets pre-installed on some of the vRealize appliances which is very useful which means there is no need to install agents manually.  Some of the VMware products which have the agent pre-installed:

vRealize Business
vRealize Operations Manager (beginning from 6.1)
vRealize Orchestrator (beginning from 7.0.1)
vRealize Automation (beginning from 7.0.1)
vRealize Log Insight

However this version of Orchestrator is 6.0.3 due to work testing so we need to install the agent manually.

vCO Details

  • Name = techlabvco001.techlab.local
  • IP Address = 192.168.1.123/24
  • SSH enabled
  • vCO Config Page = https://192.168.1.123:8283
  • vCO Getting started page and Orchestrator client download = https://192.168.1.123:8281/vco
  • vCO Appliance login = https://192.168.1.123:5480

Log Insight Details

  • Name = techlabvrl001.techlab.local
  • IP Address = 192.168.1.122/24
  • SSH enabled
  • Log Insight Configuration = https://192.168.1.122

Useful link to Log Insight Documentation Center

http://pubs.vmware.com/log-insight-30/index.jsp#com.vmware.log-insight.agent.admin.doc/GUID-04892000-72C6-4227-BB37-6A2271E03B8C.html

Steps

Note: You may already have Orchestrator installed. If so go from connecting WinScp to the Orchestrator appliance.

  • Download and install the vCenter Orchestrator OVF. In my case this was version 6.0.3 as I was doing some testing for work.
  • Import the OVF into vCenter and follow the wizard to set all the relevant configuration information. Note: You will need to set a root password and a default password for the vmware user account in the wizard in order to access the configuration page
  • Power on the vCO appliance
  • Navigate to the vCO Config Page = https://192.168.1.123:8283 and log in with the account vmware and the password you set during installation
  • In the General Page you can reset the vmware account password if you wish

screen-shot-2016-11-14-at-11-22-37

  • Click on Network and check all the details are correct

screen-shot-2016-11-14-at-11-23-57

  • You will need to put in an authentication source (LDAP, Active Directory etc) This is required as you will need to have authentication sources to log in to the Orchestrator client

screen-shot-2016-11-14-at-11-24-54

screen-shot-2016-11-15-at-09-09-24

  • After configuring an authentication source, you may need to restart the vRO Server and the vRO Configuration Server.

screen-shot-2016-11-14-at-11-26-36

  • Add your license in. Options are below

screen-shot-2016-11-14-at-11-34-05

  • Check all other options and configure as relevant. Basically everything should look green.
  • Next Log into Log Insight

screen-shot-2016-11-14-at-11-38-08

  • Click on the Administration icon (Top right in Log Insight)

screen-shot-2016-11-14-at-11-44-31

  • Click on Agents

screen-shot-2016-11-14-at-13-15-50

  • Click on Download Log Insight Agent Version 3.0.1
  • Choose Linux RPM

screen-shot-2016-11-14-at-13-17-11

  • Using Winscp, log into the vCO appliance

screen-shot-2016-11-14-at-13-21-03

  • We now need to copy the Linux Log Insight agent to a directory on the vCO server
  • Copy the agent to the /tmp folder

screen-shot-2016-11-14-at-13-29-06

  • Putty in to the vCO box
  • Switch to the /tmp folder – cd /tmp
  • To set the target vRealize Log Insight server during installation run the sudo command and replace hostname with the IP address or hostname of the vRealize Log Insight server.
  • sudo SERVERHOST=hostname rpm -i VMware-Log-Insight-Agent-VERSION-BUILD_NUMBER.rpm
  • In my case
  • sudo SERVERHOST=techlabvrl001.techl;ab.local rpm -i VMware-Log-Insight-Agent-3.0.0-2985111.noarch_192.168.1.122.rpm

screen-shot-2016-11-14-at-13-39-25

  • You should see the following

screen-shot-2016-11-14-at-14-03-03

  • Go back into WinSCP and open the file liagent.ini from /etc/liagent.ini
  • Check the LogInsight hostname has been added in and check all other options. We will not be modifying this liagent file as the recommended way to modify these settings is via the Linux Content Pack which needs to be imported into Log Insight and configured from within here. Instructions below in further steps

screen-shot-2016-11-14-at-14-22-57

  • Go back into Log Insight and refresh the page and check the agent has been picked up.

screen-shot-2016-11-14-at-14-24-08

Next we need to install the Linux Content Pack – Linux__v1.0.vlcp currently

  • Go to the Administration icon and click on Content Packs

screen-shot-2016-11-14-at-14-34-25

  • Find the Linux Content Pack

screen-shot-2016-11-14-at-14-36-40

  • When you click on the Content Pack, the below information will come up

screen-shot-2016-11-14-at-14-37-30

  • Click Install and the below message will come up

screen-shot-2016-11-14-at-14-39-31

  • Now that you have installed the content pack you can create groups with specific configurations. Go back to Administration > Agents and create your first group for Linux computers.
  • Select Linux in the pull-down menu and click on the copy template button (2 rectangles). (Note you can’t see the 2 triangles until you hover over the agent)

screen-shot-2016-11-14-at-14-45-06

  • Put a name in for the agent group

screen-shot-2016-11-14-at-14-46-49

  • Adjust the filter to reflect what machine/machines you want to use
  • In this case I have just added a filter for the hostname of my vCO server

screen-shot-2016-11-14-at-14-48-11

  • This adds the following to the Agent Configuration for the agent on your Linux machines.
  • If you want to view the Orchestrator Workflow Information then you need to add another section in the Agent Configuration (

[filelog|vmw-vco-scripting-lo]
directory=/var/log/vmware/vco/app-server
include=scripting.log
parser=syslog_parser

screen-shot-2016-11-14-at-17-07-48

  • Click Save New Group
  • Log into the Orchestrator client and test a Workflow (I used Add an Active Directory Server and Remove an Active Directory Server but you could try anything)

screen-shot-2016-11-15-at-09-17-19

  • You should then see the below Workflow being logged in log Insight if you filter by vCO hostname

screen-shot-2016-11-14-at-17-10-37

  • Voila, you have logging set up for the vCO in Log Insight

Adding queries to Dashboards

  • We were using a Workflow which changed VM vDS Port Groups. Within this Workflow, it is set to output a string to the scripting log called PORTGROUP Change – Update completed successfully
  • We can create a favourite query using this query text contains PORTGROUP Change – Update completed successfully – See highlighted below
  • You can now add this query to a Dashboard. Whilst in the query, you can click on the icon to the right (highlighted in yellow) which means Add current query to dashboard

dashboard

  • Fill in the Dashboard details and then you should be able to view this anytime and adjust the time over which work has taken place

dashboard2