API for Nimble vCenter plugin tasks?

[k_erik]

Hello,

I found this post from 2016; https://community.hpe.com/t5/Application-Integration/Clone-volume-through-vcenter-API/td-p/6982635
"The vCenter Plugin uses an internal REST API on the Nimble OS. Those APIs are currently not documented for customer use."
Is there any change to this?

I'm looking to automate cloning or claiming of VVol VMs. Both are easily done through the GUI of Nimble vCenter plugin, but I would like to put it into an automated process.

[k_erik]

Guess the plug-in API is still internal use only. Have anyone automated claim/failover of VMs through a script?

I found someone else also working on it a few years ago but little code, https://community.hpe.com/t5/Application-Integration/Use-Rest-API-to-claim-volume-on-downstream-partner-after/td-p/7009959
I could start from scratch, but always nice to save some time if possible. It is not a lack of things to do in this business

Fully understand that this is not officially supported, but HPE with SPBM failover were nice and published the script used at https://blogs.vmware.com/virtualblocks/2017/08/07/vvol-test-failover-power-cli-6-5-1/
I would prefer to use Nimble native replication instead of vCenter SPBM failover.

[mamatadesaiNim]

Hello again k_erik,

We are working on your case for snaps not deleted from upstream and downstream.  Hang on tight.

Yes the vCenter plugin APIs are not public.

Yes the Nimble array REST API are public and can be used.

WRT failover: Nimble native replication is used under our vVols implementation.  SPBM is already tied into it when you configure vasa3 vVol VMs.  All VMware PowerCLI for vasa3 vVols failovers should work.  Let us know if you run into any issues other than the one you've already reported.

Another good news: The upcoming VMware SRM release will have full support for vVols replication and related recovery.  Our team has been working closely with VMware to run the related tests and certifications.  Expect to hear from us closer to release, with a blog post.

--m

[k_erik]

Hello again Mamata,

Great, thank you!

The problem with SPBM, at least when I tried it last year, is that the VMs disappear from the Nimble vCenter plugin as they are mutually exclusive setups.
I really like the Nimble vCenter plugin, except the lack of the option to select multiple VMs. Very user friendly to clone a VM from a Nimble snapshot through the plugin, anyone can do it. Having co-workers run SPBM scripts which they don't understand is far from fun, and the risk of a PowerCLI upgrade breaking something.

Cool. Though at the moment we have no requirement to have a SRM certification. Having a plan for DR and test it on a few VMs every 6 months is acceptable for us. We save a nice sum of money if we avoid using SRM, more to spend on HPE hardware instead!

[mamatadesaiNim]

k_erik,

Nimble vCenter plugin should be used to manage vVol VMs that are NOT using vasa3

If you go the vasa3 route (vVols using replication and need DR), let vCenter manage everything via SPBM.  Use PowerCLI or vSphere SDK, or wait for the upcoming SRM release.

Apologies if my earlier post confused you.  And thank you for the additional context.

--m

[k_erik]

Thanks, it is a topic than can be confusing. As my post back in 2019 showed I didn't grasp the differences in the beginning.

I know the documentation states that Nimble vCenter plugin should not be used for DR. Is there any technical reason for that? Except that it is not possible to select multiple VMs so it scales rather badly.
What is your recommendation for DR when NOT using vasa3? Scripting at the array API?

[mamatadesaiNim]

k_erik,

vCenter Plugin brings up cloned volumes on the replica site ... so it can't technically be considered DR ... it can only be considered "Testing DR" or "Running Test workload in DR site".

For vasa3 VMs, VMware would be the DR solution for that.  PowerCLI works nicely even at scale, we've tested using the same internally for the last 3 years.

"Technical reason" - not exactly.  But if this is something you need, you should definitely have a chat with our Product management.  Let me PM you.

--m