Home > Blogs > VMware vCenter Orchestrator Blog > Tag Archives: integration

Tag Archives: integration

vCO Spring Plug-in season is here!

vco-plug-ins

The Spring is here along with the season gifts from vCenter Orchestrator Team just in time for Easter.  The holiday plug-in bundle comes with quite a few new integrations and major updates.

  1. vCenter Orchestrator Plug-In for vCloud Automation Center 6.0.1
    vCenter Orchestrator  became  an integral part of vCloud automation center since version 6.0, playing a major role of an unified integration layer and XaaS engine.  In order to better serve the extensibility story of vCAC VMware released  vCenter Orchestrator Plug-In for vCloud Automation Center 6.0.1.vcac-plug-in By using the new plug-in you are now able to automate variety of management and end user operations within vCAC related to service provisioning and XaaS, catalog management, policy based management and authorization. For more information you can refer to vCAC blog.

2. vCenter Orchestrator AWS Plug-in 1.0:  vCO is now able to automatically manage and integrate your Datacenter resources residing at Amazon public cloud space. The Orchestrator Plug-In for Amazon Web Services (AWS) 1.0. exposes the functionality of the Amazon Elastic Cloud. The plug-in’s API exposes the AWS API and lets workflow developers create content similar to the content created through the AWS Java SDK.

3. The long awaited vCO Powershell plug-in 1.0.4 is updated to support Powershell 4.0 inventory and is fully backward compatible with your existing scripts.

Following VMware plug-ins has also been updated to support new vCO Configuration API and platform versions:

  • vCenter Orchestrator Auto-Deploy Plug-in 1.0.3
  • vCenter Orchestrator Multi-Node Plug-In 5.5.1
  • vCenter Orchestrator AMQP Plug-in 1.0.3

For additional information on these materials, please visit the plug-in release notes sites listed below:

vCenter Orchestrator Plug-In for vCloud Automation Center 6.0.1
vCenter Orchestrator AWS Plug-in 1.0
vCenter Orchestrator Powershell plug-in 1.0.4
vCenter Orchestrator Auto-Deploy Plug-in 1.0.3
vCenter Orchestrator Multi-Node Plug-In 5.5.1
vCenter Orchestrator AMQP Plug-in 1.0.3

Happy Spring and enjoy the new vCO Plug-ins!

 

vCenter Orchestrator Holiday Gifts

 

The vCenter Orchestrator gifts season started a few months ago with the general availability of vCO 5.5. The compelling release was announced just in time to share the vCO momentum at VMworld.  Along with the amazing new features introduced, VMware continues with a lot more presents.

This year the holiday magic brings to vCenter Orchestrator users several updates, product integrations and learning gadgets that make automation with vCO more powerful than ever.

1. VMware has just announced the GA of VMware vCloud Automation Center 6.0(vCAC 6.0). The extension and creation of XaaS is done using the vCAC Advanced Service Designer which allows you to seamlessly leverage any vCO workflow and convert it to a catalog item or day 2 operation, available as a service in the vCAC Self-service portal.

 2. vCO CLI is the code name of the new debugging extension which will not only facilitate all experienced vCenter Orchestrator users and also helps the newcomers to programmatically explore the rich vCO ecosystem through interactive command shell. Access to the vCO plug-in’s inventory is integrated into the tool UI for easy navigation to the integrated solution objects.

3. Our super powerful and generic HTTT- REST and SOAP plug-ins are now able to support proxy configurations and assure security compliance of your automated solutions.

4. The long awaited vCO Powershell plug-in 1.0.3 is updated to support Powershell 3.0 inventory and is fully backward compatible with your existing scripts.

5. In vCenter Orchestrator plug-in for Microsoft Active Directory 1.0.4 the old configuration mode is removed and you are now able to configure the plug-in automatically through native vCO workflows.

For additional information on these materials, please visit the following sites:

The entire vCO team wishes you the very best for the holidays and 2014.

Cheers!

VMware vCenter Orchestrator 5.5 is now GA!

As part of the of the vSphere 5.5 announcement, we are extremely glad to share the general availability of vCenter Orchestrator 5.5 !

Large organization will greatly benefit from the enhanced cloud-scale architecture, out-of-the box high availability of the platform, and major improvements to the REST API.

Additionally, workflow developers can enjoy a more efficient development experience thanks to the new debugging and failure diagnostic capabilities in the vCenter Orchestrator client.

We continue enriching the vCO plug-in intelligences and number of integrations with variety of partner applications, including management systems from EMC, F5 Networks and NetApp. Please, refer to the VMware Solution Exchange for a complete listing of the available vCenter Orchestrator plug-ins.

 Optimized for growing clouds

vCenter Orchestrator 5.5 is greatly optimized for growing clouds thanks to significant improvements in scalability and high availability. The cluster mode configuration enables a collection of vCO orchestration nodes to work together, sharing a common database and provides high availability of the workflow execution in case of orchestration node failure. In addition, our extended REST API allows automatic installation and configuration of the necessary vCO server nodes. It also provides dynamic scale-up and scale-down of the orchestration capacity when vCenter Orchestrator is being used in conjunction with an external load balancer.

Workflow Debugging

The vCenter Orchestrator 5.5 client is fully equipped with a workflow debugger, allowing vCO workflow developers to easily test and fix their custom workflows. In case you want to re-run an extensive workflow from a common point of failure, you are able to configure and resume the execution from the last failed state of the workflow.

Security Enhancements:

The vCenter Orchestrator 5.5 appliance contains a complete set of security improvements, including Operating System updates and security hardening script enhancements, which seamlessly secure your orchestration deployment and reduces the platform surface of vulnerability.

Last but not least, you’ll still be able to leverage all of the workflow you’ve already created in the previous release and be able to run them seamlessly in version 5.5.

These are just the major new capabilities but you’ll find plenty of additional enhancements that make the automation and integration of your software-defined datacenter easier than ever before. For a full list of new features and capabilities, please refer to the detailed overview or the release notes.

As a reminder, in 2013, we continued to integrate vCO with the products from VMware Cloud Suite. Cloud administrators are now able to establish a self-healing datacenter and automatically remediate any infrastructure failure by simply leveraging the vCenter Operations remediation workflow package.

Additionally, vCenter Orchestrator offers bi-directional integration with vCloud Automation Center (vCAC). vCO workflows can be coupled with resources managed by vCAC, either as part of the provisioning and decommissioning process, or as a Day-2 operation available in the  vCAC self service portal.

So don’t hesitate to try it today and let us know what you think via blog comments, Twitter (#vCO) or the vCO Community.

Cheers!

The vCO Team

The More vCO @ VMworld 2013 – The Better: vOTING Guide

Dear vCO Fans,

The best season of the year is just few months away. Yes, it is real – It is VMwolrd season of 2013. Please, be aware that there is a Public Session voting process in place at www.vmworld.com.

It is pretty easy to get lost while browsing so many great ideas available for voting. There is no need to worry – the usual suspects are also in place with creative abstracts (Christoph, Joerg, William , James Bowling …). Beside this, there are lot of new folks proposing catchy titles, revealing the power of vCO.

Please, take your time to review through the list of vCO related ideas.

4875 vCenter Orchestrator: A Beginner’s Guide – James Bowling, iland

5242 Extending vCloud Automation Center with vCenter Orchestrator; Rich Bourdeau, VMware

5287 Open up the vCloud hood using PowerCLI, Hyperic, vCenter Operations Manager and vCenter Orchestrator to reveal the inner cloud; Phil Ditzel, VMware;Cathal Cleary, VMware

5352 Automating the Software Defined Datacenter with vCAC, vCO and Storage Automation, Jeremy Goodrum, NetApp; Joerg Lew, VMware

5360 vCenter Orchestrator Best-Practices – Joerg Lew, Christophe Decanini, VMware

5365 “7 Design Patterns for vCenter Orchestrator Workflows” – Joerg Lew, VMware

5472 vCO – Say hi to Razor and Software Defined Storage, Magnus Nilsson, EMC; Jonas Rosland, EMC

5586 Optimize Application deployment time and lifecycle management via vCloud automation Center (vCAC) and vCenter Orchestrator (vCO), Boskey Savla, iGate Technologies, Inc. Indranil Bal, iGate Technologies, Inc.

5695 How to Build a Self – Healing Data Center with vCenter Orcestrator (vCO), Dan Mitchel, VMware

5703 Supercharging vSphere Web Client with vCenter Orchestrator (vCO) Dan Mitchell, VMware, James Bowling, vSential

5717 How to Automate ANYTHING with vCenter Orchestrator (vCO): Dan Mitchell

5731 Become a Rock Star with PowerCli and vCenter Orchestrator; Josh Atwell, VCE

5923 vCenter Orchestrator: Customize Your vSphere Web Client Experience – James Bowling, vSential

So be sure to go to www.vmworld.com to review submissions and vote before 6 May 2013.

And to all submitters… thank you and best of luck!

Cheers,

The vCO Team

 

 

VMware Releases vCenter Orchestrator Gifts in Time for the Holidays

As 2012 comes to a close, we thought it would be a great time to end the year with some gifts to put under your (virtual) holiday tree!

2012 was a great year for automation in general, with the launch of the vCloud Suite 5.1, and orchestration in particular, with the release of vCenter Orchestrator 5.1.  Our team was extremely happy to see a tremendous increase in vCO adoption, and a growing list of integrations with other management systems.

In that spirit, we are very glad to announce the availability of several integrations and learning tools to make your automation projects easier than ever before.

1. vCloud Automation Center 5.1, which was just released, provides the ability to extend pre-built processes and post-provisioning actions by invoking vCO workflows. This means that any technical integration or logic built in vCO can be leveraged by vCAC’s lifecycle-management platform, thereby broadening the realm of self-service provisioning and basic administration for consumers of IT services.

2. Reversely, the new vCenter Orchestrator Plug-in for VMware vCloud Automation Center allows organizations to automate vCAC provisioning and post-provisioning tasks. With these two components, customers can leverage full bi-directional integration capabilities between vCloud Automation Center and vCenter Orchestrator.

3. Another new offering is the vCenter Orchestrator Elastic Service Plug-in. This plug-in provides a foundation for the self-scaling virtual datacenter, by automatically balancing the physical resources between virtual datacenters in VMware vCloud environments. This plug-in contains a rules engine that can analyze resource usage metrics (for instance, metrics captured by vCenter Operations Manager) and make scale-up or scale-down decisions automatically.

4. The vCenter Orchestrator Plug-in for VMware Service Manager enables organizations to automate operations around Configuration, Incident, Task and Service Request management.  Thanks to this plug-in, repetitive tasks such as updating an Incident or creating a Configuration Item when a new virtual machine is provisioned can now be fully automated.

5. And to help you take advantage of all of the above gifts, the VMware Training department just released over 10 self-paced vCO training videos available for free!

For additional information on these materials, please visit the following sites:

 

The entire vCO team wishes you the very best for the holidays and 2013.

Cheers!

Important vCenter Orchestrator Plug-in Updates

With the recent vCenter Orchestrator 5.1 and vSphere 5.1 availability, it’s obviously important to ensure that not just individual products but all of your integrations are up-to-date.

Besides the already released plug-ins for vCenter Server 5.1 (built-in) and vCloud Director 5.1, we are are glad to announce the availability of several plug-in updates to make your entire vCloud suite up-to-date:

1. The vCenter Update Manager plug-in has been updated to support version 5.1 and vCenter Single Sign On. This plug-in is essential for scanning and remediating vSphere inventory objects against baselines.

2. The vCO Multi-Node plug-in has been updated to support vCO 5.1, vCenter Single Sign On, and the new vCO REST API capabilities to leverage the remote invocation of new systems types such as actions and packages.  What’s more, this new version also provides better performance and corrects some previous defects.

3. The vCO Plug-in for vSphere Auto Deploy 5.1 supports… vSphere Auto Deploy 5.1!  Need we say more?

4. The vCO Plug-in for Microsoft Active Directory 1.0.2 provides support for vCenter Single Sign On and contains an import fix for concurrent workflow execution.

5. The vCO AMQP Plug-in 1.0.2 offers significant performance improvements and fixes a known issue with the vCO server restart.

6. The vCO Plug-in for vCenter Server 5.0.2 contains important performance improvements for customers who are running vCO with vCenter Server 5.0.

  • vCO Plug-in for vCenter Update Manager 5.1: download
  • vCO Multi-Node Plug-in for 5.1: download
  • vCO Plug-in for vSphere Auto Deploy 5.1: download
  • vCO Plug-in for Microsoft Active Directory 1.0.2: download
  • vCO AMQP Plug-in 1.0.2: download
  • vCO Plug-in for vCenter Server 5.0.2: download

As always, be sure to check VMware Solution Exchange for a complete list of plug-ins available from VMware and our partners.  That’s your best place to find the latest integration solutions such as the ServiceNow plug-in recently published by InterraIT.

Cheers!

The vCO Team

SNMP plug-in – integration with vCenter Server

In this post we will show how you can use the SNMP plug-in to receive various vCenter Server alarms in vCO and include these events as part of more complex orchestration logic.

vCenter Server configuration

First, you must register the vCO server in the list of SNMP trap receivers in vCenter Server. This list is accessible in the vSphere client, in vCenter Server Settings, which is accessible from the Administration menu.

Snmp-vc-01-ServerSettings

You can have up to four different receivers, one of which must link to the address of your vCO server and the port defined in the Trap Host node in the SNMP inventory in vCO.

Configure Alarms

After you have registered the vCO server, vCenter Server can send SNMP traps to it. Some traps will start to be sent immediately. Many alarms in vCenter Server are configured to send traps by default.

Some default alarms are defined on the root of the vCenter Server inventory (1), from where they propagate to all child objects. If you go to the Alarm management tab (2), you can check the definitions (3) of the default alarms. Selecting a specific alarm (4), you can check on its Actions tab (5) if sending SNMP traps is active for this specific alarm (6).

Snmp-vc-02-DefaultTraps

These settings can be changed on the object where the alarm is defined. If the fields are not editable, then this is an inherited alarm, and you need to find the parent object that defines the alarm to change the settings.

Create custom alarms

Sometimes you may need to monitor something specific that is not part of the default alarms, or you only want to monitor it for a certain host, virtual machine or other object. Then you need to add a custom alarm to the object (a datastore in this example).

Snmp-vc-03-AddAlarm

Then, you need to add some triggers which define under what conditions this alarm should be triggered.

Snmp-vc-04-AddTrigger

Finally, you need to add an action that will send a trap. Note that you may need to add handlers to state changes. For example, the green to yellow state change does not send a trap, as by default only the yellow to red state change is defined to send a trap.

Snmp-vc-05-AddAction

After this, the vCenter Server instance is ready and is sending traps to vCO.

Configure vCO to receive traps

On the receiving end, you first need to add the vCenter Server instance to your inventory with the “Register an SNMP device” workflow.

Snmp-vc-06-AddDevice

Then you can either apply a policy, which will be receiving all kinds of traps and running scripts on each of them, or start a workflow, which will be waiting for a specific trap.

The policy is applied from the Policy Template “SNMP Trap”, and takes as a parameter the SNMP device that you just registered.

Snmp-vc-07-policy

This exact policy is only printing the trap data to the system log, but it could do other tasks, such as, call actions or workflows that should handle the received traps.

You must start the policy after it is created, or set it to auto-start if you need it to work after server restart.

You can leave this policy to be listening for traps for the moment, and check the other possibility to receive traps – the “Wait for a trap on an SNMP device” workflow.

Snmp-vc-08-waitTrap

After you enter the device and OID parameters and run the workflow it reaches a trigger where it suspends and starts waiting. It can be resumed only by the specified SNMP trap.

Snmp-vc-09-trapWaiting

If the OID field from the workflow presentation was left empty, then the workflow will be resumed by any trap, just like the the policy. Any trap filtering on the policy must be done programatically, after the trap is received. Listening to all incoming traps can help you easily get the correct OID that will be sent from vCenter Server for a specific alarm. These OIDs are also listed in the MIBs that are described in vSphere Datacenter Administration Guide, in the “Monitoring Your Virtual Infrastructure” section, chapter “SNMP and vSphere”.

If everything is configured correctly, vCO should start receiving SNMP traps and trap data will be logged from the policy, like in this example, which is monitoring datastore space usage.

Snmp-vc-10-trapReceived

The SNMP plug-in is not limited only to use with vCenter Server. It can be used with any SNMP-enabled system or device. This is just one scenario that shows how the SNMP plug-in, together with the workflow library from the vCenter Server plug-in, can be used as the basis for the automation of various datacenter administration tasks.