OneView Hypervisor profiles

[CadenLange]

Hi

Is it possible to set up OneView Hypervisor manager and cluster profiles for an existing environment or does it need to be configured before the clusters are created?

I have multiple VMware 7.x clusters where the hosts are managed by OneView 6.2 and I now want to use the OneView Hypervisor functionality. Is configuring this within OneView a disruptive operation for an existing cluster? 

Does it require the hosts to be rebooted at all or does OneView need to change\reapply any configurations on the host or on vCenter?

thanks Caden

[support_s]

System recommended content:

1. HPE OneView 6.4 User Guide for VMs | Hypervisor cluster profile consistency validation

2. HPE OneView 6.4 User Guide for HPE Synergy | Hypervisor cluster profile consistency validation

If the above information is helpful, then please click on "Thumbs Up/Kudo" icon.

Thank you for being a HPE community member.

[Doug de Werd]

Yes, you can import an existing cluster to be managed with OneView Hypervisor Cluster Profiles (HCP)

https://support.hpe.com/hpesc/public/docDisplay?docId=sd00001152en_us&docLocale=en_US&page=s_hypervisor-cluster-profiles-about-external-deployment.html

I would also strongly suggest that you try this in a dev/test environment first so that you fully understand how HCP works

https://support.hpe.com/hpesc/public/docDisplay?docId=sd00001152en_us&docLocale=en_US&page=s_planning-to-use-hcp.html

For example, if you decide that HCP is not right for you, you can delete it. However, it is very important to note that there are 2 options -

• HPE OneView and the hypervisor manager

  Removes the hypervisor cluster profile, the associated hypervisor profiles, and the server profiles from HPE OneView. This option also deletes the managed hypervisor cluster, as it removes the associated hypervisor cluster and its cluster members from the hypervisor manager. The server hardware returns to No Profile Applied state, and is available for scheduling the server profile creation.

• HPE OneView only

  Removes the hypervisor cluster profile and the associated hypervisor profiles from HPE OneView. The associated server profiles are left unaltered in HPE OneView. This operation does not disrupt the workloads running on the cluster and leaves the hypervisor cluster intact in the hypervisor manager.

  As the associated hypervisor cluster profile is no longer managed from HPE OneView, the configurations on the physical server and the associated hypervisor must be managed manually. The cluster remediation and rolling update features are no longer applicable in HPE OneView with this option

  If you select the first one (HPE OneView and the hypervisor manager), it will totally wipe out your cluster by removing the server profiles and returning each host to bare metal.  The second option (HPE OneView only)  will only remove it from being managed with HCP and will not destroy the cluster.

  I would also suggest playing around with the remediation options to make sure you fully understand how they work before putting it into production.  https://support.hpe.com/hpesc/public/docDisplay?docId=sd00001152en_us&docLocale=en_US&page=GUID-F20F9D54-6942-4D1F-9BCC-0B9EA86C07B0.html

[CadenLange]

Hi Doug

Many thanks for that

So the act of importing an existing cluster to be managed by a Synergy OneView composer is low risk and non-disruptive (I agree about trying this on a test\dev cluster first). I found the following - I just want to make sure I'm interpreting this correctly. Our clusters have already been installed and configured on the Synergy compute modules just simply installing via mounting the ISO within iLO and manually configuring all the VMware networking through vCenter. The storage is a Nimble and so the storage has been configured via the Nimble plugin

You can deploy the hypervisor cluster using external tools of your choice and import the hypervisor cluster profile into HPE OneView to manage the hypervisor cluster. When you import the hypervisor cluster profile, HPE OneView discovers the configurations of the hypervisor cluster and the hypervisors in the cluster. The import operation does not disrupt the workloads that are running on the cluster.

Is it the case that, once imported, the Hypervisor cluister profile must then be used for all further changes? eg if a VMware administrator were to make changes to the VM networking configuration (using vCenter), would this show up as an inconsistency alert within the Hypervisor profile in OneView? 

thanks

[ChrisLynch]

Is it the case that, once imported, the Hypervisor cluster profile must then be used for all further changes? eg if a VMware administrator were to make changes to the VM networking configuration (using vCenter), would this show up as an inconsistency alert within the Hypervisor profile in OneView? 

If a vSphere admin where to add a new network to the vSwitch configuration, that does not mean the physical infrastructure has it configured.  Yes, a compliance alert would be generated, but would allow you to remediate.