It seems like everyone these days wants to use ServiceNow as their catalog for vRA. It use to be that everyone just wanted to create or update CI records. Before I get into the weeds on how to get vRA and ServiceNow talking together I wanted to take a few minutes to discuss the integration, the pros, the cons, and it’s limitation.
There are lots of reasons to want to export and import blueprints from one vRA instance to another. My current motives are to move blueprints from my vRA 7.2 environment to my newly deployed vRA 7.3 environment. In vRA 7.3 their is a great new free feature available, the Code Stream Management Pack for IT Devops that is free. However if you are running a pre vRA 7.3 environment you may want to get that content from that environment backed up so you can use it in another instance. Cloud Client is a great option.
Some of you may have attended the vRA and ServiceNow presentation at VMworld 2017 yesterday. I regret not being able to attend and present it myself, however I’m certain that Chris Smith and Ian Smith did a fantastic job. Here I want to recap some of what was presented during that session.
It’s important to understand what options are available and what features they offer in order to understand what you really need when integrating with ServiceNow. To start do you need what is referred to as North/South integration, East/West Integration, or both. Below is a list of what capabilities fall under each classification.
|ServiceNow used as Catalog||vRA used as Catalog|
|VMware vRealize Automation handles automation and orchestration.||VMware vRealize Automation handles automation and orchestration.|
|Create or update CI records||Create or update CI records|
|Available via VMware ITSM plugin, AVNet Plugin, or Custom REST API integration.||Available via VMware ITSM plugin, SovLabs plugin, Avnet Plugin, or custom vRealize Orchestrator workflows.|
If you have been to the VMware Solutions Exchange you most certainly have seen the name SovLabs. Although their solutions are regularly called plug-ins, I assure you they offer more than just orchestrator-based plug-ins. I first started working with their solutions earlier this year and I was instantly hooked. Many of you have used vRO extensions that were made available by Tom Bonanno or myself posted here on Dailyhypervisor. One in particular is the custom hostname extension for vRA. While that extension has helped hundreds if not more of you, many of you quickly discovered the downside of using it. That downside being management overhead and lack of support. As much as we would have liked to offer support to those in need we simply don’t have the bandwidth to do so. Even upgrading the extension we put out for new versions of vRA in a timely manner had its challenges for us.
Still running vRA 6.x, then you will be happy to hear vRA 6.2.5 is now GA and boast some great performance improvements. See blow for more details.
Whew the last few days have been full of new releases and VMware is not done yet. I’m not going to spoil anything but I will tell you that the release of vRealize Orchestrator 6.0.5 is not the last announcement you will be seeing from me. I anticipate some other exciting news next week. FOr now check out what’s new in vRO and stay tuned.
vRealize Orchestrator 6.0.5 is a patch release that introduces a number of improvements and bug fixes.
- Enhanced workflow logging, including messages that mark the start and the end of the workflow run. In case of failure, the log captures the workflow ID, the request ID, and the exception.
- Added ability to run a Debugger in the Orchestrator client when the request is generated by an external system, such as vRealize Automation, the vCenter Web Client, or a REST endpoint.
- Introduced Spanish locale support for the Orchestrator plug-in for vSphere Web Client.
vRealize Orchestrator 6.0.5 also introduces Control Center, which delivers a more flexible configuring, monitoring, and troubleshooting experience. Control Center contains multiple built-in capabilities:
- Cancel workflow runs
- vRealize Orchestrator runtime dashboard
Unveiling Project Clarity – VMware CTO Blog
Today we’re ecstatic to announce Project Clarity, a design system that combines UX guidelines, patterns, and front-end code in one solution. Clarity is for the designer and developer in each of us.
It’s no secret that this is a feature that I’m very excited about. This feature although very useful on it’s own is going to open up the door for many new exciting capabilities with out VMware products in the future.
Resource contention is one of the most critical issues in any virtualized environment. When contention occurs, applications slow down and your users are affected. Up until now two different methodologies have been employed to mitigate the risk of contention, with varied results. But now I want to introduce you to the new “game changing” method available from VMware: Predictive DRS! But first a bit of a history lesson on the original two methods.
The first of these is the Reactive Method which focuses on resolving unexpected resource demand. The most widely used example of a reactive solution is VMware’s Distributed Resource Scheduler, or DRS. As the day progresses, workloads may need more resources, which can lead to contention on the host. The reactive method moves VMs around to ensure all workloads get the resources they need and applications remain healthy. Note this method needs only a minimal amount of VMs to be moved in order to be effective, which means minimal overhead. The reactive method only moves VMs when contention approaches, so it’s possible (however remote) for users to feel some effects of the contention before it’s resolved.
Learn more about the other methods available with predictive DRS in the original article on VMware Cloud Management blog site.
Loving the list of new features in vSPjere 6.5? Thinking about digging in and upgrading your lab or other environment? Well if that environment is running NSX you will want to wait just a little longer. vSphere 6.5 is currently not compatible with NSX including 6.1.x and 6.2.x. See KB 2147548 for more details.
Now I have nothing official to say on this, but as you might expect I’m sure this will be resolved once a new version of NSX drops. We have all been there before where we just got the GA announcement of vSphere and rushed to upgrade our virtual labs and oh wait crap, NSX is not supported. This is nothing new this has been the case for last few releases if you recall. You may remember reading this article about vSPhere 6.
GA Date: November 15, 2016
- vSphere 6.5 compatibility.
- System notification enhancements.
- Support for custom SSL certificates in the vCenter Server edition.
- Support for Spanish locale(ES).
- UI Features
- New overall User Interface based on the VMware Clarity standard.
- New speedometer-like Gauge Chart type for event count visualizations.
- New Admin Alert Management tool and UI to view and manage all user alerts.
- New filter called Does Not Exist to find events that do not contain some specified field.
- Support for Datastore Device ID-to-name aliasing in event queries and results.
- New “blur” on session timeout.
- Server Features
- Support for Syslog octet-framing over TCP.
- Defined REST APIs for installing Log Insight servers and clusters.
- Support for time ranges with Event Type alert queries.
- Agent and Importer Features
- SLES 11 SP3 and SLES 12 SP1 are supported for Linux agents.
- The dateext (daily extension) option of logrotate is now supported.
- SSL for the vRealize Log Insight agent is now enabled by default.
- Content Pack Features
- Users can now subscribe to content pack alerts that allow automated updates inline with the associated content pack.
- Changed Behavior
- New Agent installations have SSL enabled by default. Previously, Agent installs defaulted to SSL off. Upgrading does not affect current SSL settings.
- New event forwarder destinations now default to verifying SSL certificates. Previously, SSL certificates were not verified by default. Upgrading does not affect current settings.
- vRealize Log Insight for vCenter now allows you to change SSL settings.
- For content pack alerts instantiated in 4.0, content pack updates now automatically update alert definitions. If needed, you can preserve customizations by exporting them and then importing them back into the user profile after the update is applied.