vRealize Code Stream – vRCS 1.x – Installation and Configuration

For those of you who are fortunate enough to be able to get a trial for Code Stream this article will walk you through the installation and initial configuration of the product.  Code stream as the name suggest is part of the vRealize product line and shares the same identity appliance and virtual appliance as vRealize Automation.  Because of this I will be referring to articles I have already written for portions of the installation in an effort to not re-invent the wheel.

Installing vRealize Code Stream

1. For instructions on how to install the vRealize Code Stream Identity Appliance please see Installing the vCAC 6.0 Identity Server.

*Note – The instructions in the above referenced article may vary slightly from vRCS 6.0 identity appliance, however it should be close enough that you should not have any issues following along.

It is recommended that you configure the Active Directory settings in the Identity Applaince which is not covered in the above post, but is straight forward.

2. For instructions on how to install the vRealize Code Stream Virtual Appliance please see Installing the vCAC 6.0 Virtual Appliance.

*Note – The instructions in the above referenced article may vary slightly from the vRCS Virtual Appliance, however it should be close enough that you should not have any issues following along.

On step 21 input the Code Stream License Key instead of the vRA license key, or both if you like.

3. For instructions on how to setup Tenants in vRealize Code Stream please see Adding Tenants in vRealize Autoamtion 6.x.

On step 7 you will not be able to add a user to the “Infrastructure Administrator” role as that is a construct of vRealize Automation.  If you are running code stream and vRealize Automation on the same virtual appliance you can add users/groups to this role.

[Read more…]

vRealize Automation – vCAC 6.1 – Ultimate Multi-Machine Blueprint Extension v1.0.2 – Updated

Have you ever needed more control over what custom properties get assigned to specific component machines of a multi-machine blueprint, or want to use the same component blueprints for all component machine of a multi-machine blueprint?  The Ultimate Multi-Machine Blueprint Extension aims to help with that.

The Ultimate Multi-Machine Blueprint Extension allows you to utilize the same source component blueprint for multiple component machines while at the same time controlling which custom propertied get assigned to each of the components.  This allows you customize each of them differently during deployment.

This extension works well with the Custom Hostname and the Custom vCenter Folders extension to round out the use of Multi-Machine Blueprints.

Example Use Cases:

  1. Use a single machine blueprint for all components of a multi-tiered multi-machine blueprint and customize the name of each component.
  2. Use a single machine blueprint for all components of a multi-tiered multi-machine blueprint and customize the guest agent actions of each component machine.
  3. Use a single machine blueprint for all components of a multi-tiered multi-machine blueprint and override the template for each component to deploy from a different source vCenter template for each component.

The goal of this extension is to limit blueprint sprawl and leverage the multi-machine construct to customize the component machines and rely less on customizing the single machine blueprints making them more re-usable.

This extension was designed and built as a collective effort by Tom Bonanno and Sid Smith.  If you have any feedback please let us know.

Features

  • Define which component machines to apply custom properties to in a multi-machine blueprint.
  • Utilize a singular blueprint for all component machines in a multi-machine blueprint.

Change Log

v1.0.2

  • Fixed bug that caused properties with Multiple periods not to be processed properly.

v1.0.1

  • Initial Release

Remember we have performed a large amount of testing, but this is a v1.0 extension so please test and let us know if you find any issues.

[Read more…]

VMware vCenter Orchestrator 5.1.3 is released.

This release of vCenter Orchestrator fixes a number of issue from the previous release.  Mainly a maintenance release, so when you can find the time I would recommend getting it installed and putting some of these issues in the past.  If for no other reason you will want to get this installed to resolve the issue where nested workflow don’t resume properly when rebooting the vCO server. Issues resolved in this release:

 

Active Directory account gets locked when connecting to Microsoft SQL database
If you set up a connection to a Microsoft SQL database with a Windows Active Directory account, the account gets locked from the domain.

vCenter Server inventory disappears from the Orchestrator client
If there is an outage of the connectivity to vCenter Server, the vCenter Server inventory disappears from the Orchestrator client and cannot be accessed until you restart the vCenter Orchestrator server.

Purging operations might cause a Microsoft SQL database deadlock
Orchestrator’s purging operations for events might cause a deadlock in a Microsoft SQL database.

VcAuthorizationRole.roleId does not provide the correct role ID and always returns 0
When you use the vCenter Server plug-in VcAuthorizationRole.roleId attribute, the correct role ID is not provided. Instead, the role ID of every object is displayed as 0.

Nested workflows not resuming properly when rebooting
If there are nested workflows still running when you reboot an Orchestrator server, the nested workflows do not resume from the last workflow element that was running at the time of reboot. After the Orchestrator server starts again, the nested workflows resume from the begining.

Import Package dialog responding slowly
The Import Package dialog might respond slowly when importing a package with content that is already available in Orchestrator.

Problematic releasing of locks
If you create a lock with LockingSystem.lockAndWait(lockName,””) and try to release it by running the Release all locks workflow, the LockingSystem.unlockAll() method does not release all locks.

Release Notes can be found here.

Download can be found here.

vRealize Automation – vCAC 6.1 – Custom Property Toolkit for vCO

For those of you who have not seen this yet, it is a must have for anyone writing vCO workflows for vCAC.  VMware’s own Dan Linsey build a set of pre-built workflows to help aid you in your own development efforts.  The toolkit includes workflows for performing Create, Read, Update, & Delete Operations for vCAC custom properties for more than just virtual machine objects.  IT includes support for the following:

 

  • Blueprints
  • Build Profiles
  • Business Groups
  • Endpoints
  • Property Dictionary
  • Virtual Machines
  • and more

Top check out this incredibly useful toolkit head over to the VMware Communities and download it.