Announcing #vROps Webinar Series 2017 – Part 1 – What’s new in 6.5
Welcome to the vRealize Operations Manager Webinar Series 2017. With the huge success of the series back in 2016, we wanted to take a break, enjoy the success and come back with full rigor for this series in 2017. We are here and we are charged up to give you some more dope on vRealize Operations manager in the year 2017.
The delivery mechanism would be same as last year. We will start with talking about a topic and then jump into a live environment to see what happens when the rubber hits the road…
To begin the series, we will start with the latest edition of vROps to see the enhancements VMware has done in the product and how customers can operationalize these features to make their operations simple and effective.
Here are the details!
Session title – What’s New with vRealize Operations 6.5
Date – Tuesday, 28th March 2017
Time – 13:00 PST
Speakers – Sunny Dua and Simon Eady
Webinar Link – Click here to join the meeting
Save invite – Click to save invite
The vROps HA conundrum
I have had several discussions with my colleagues on the subject about whether you should or should not enable it in any given deployment of a vROps cluster.
So the following are my thoughts and bullet points for you to consider when faced with same dilemma.
By its very name, I assumed wrongly that it could be used as a way to tackle BC/DR concerns, it turns out the HA feature cannot span multiple logical datacenters – KB article – Forum discussion. I am hoping in future editions this gets resolved as it would be -very- handy.
So what other things do I need to take into account?
- The Master node behaves like an index for your cluster, lose it and lose your cluster, so HA can protect it although is no substitute for a proper backup solution. “.. Global xDB is used for data that cannot be sharded, it is solely located on the master node (and master replica if high availability is enabled)“
- HA takes several minutes to “kick in” so one could argue why not rely on vSphere HA (especially if your management cluster is tight on resources)
- HA would protect you against a LUN/Datastore failure assuming you had sensibly separated your nodes.
- HA adds an additional node so if you are tight on resources it might not be an option for you.
- Removal of data nodes (if you need to downsize your cluster) will result in data loss unless you have HA enabled.
The bullet points are by no means exhaustive but they are essential information while you muse your design choice for you next vROps cluster.
vROps – first look – part 1 – installation
For several months now we have seen glimpses of vROps by way of limited blog posts and the HOL demo’s so it was great to see it finally released.
So what is it like out of the box?
The first clear change is the move away from 2 VMs in a vAPP and consolidation down to 1 VM which is then easily scalable to more as you require.
The UI has been completely reworked and the install process has also completely changed, so lets take a look.
Deploying from the ovf is very straight forward (you no longer need to worry about IP Pools either!)
Once you have deployed the OVF start up the VM and wait for it to complete its boot process then navigate to the IP you gave vROps to begin the deployment/configuration. As you can/will see below a lot of time has been invested to simplifying the configuration process.
I Opted to do a new a new installation upon which I was then presented with a 5 step process to deploy vROps