VSAN 6.2 extends vSphere API to include new VSAN Management APIs

In addition to all the new capabilities and enhancements included in the release of VSAN 6.2 (vSphere 6.0 Update 2) which you can read more about here and here; VSAN 6.2 also introduces a new VSAN Management API which extends the existing vSphere APIs that our customers are quite familiar with.

This new VSAN Management API will allow developers, partners and administrators to automate all aspects of VSAN functionality including: complete lifecycle (install, upgrade, patch), monitoring (including VSAN Observer capabilities), configuration and troubleshooting. There will be two new service endpoints /vsan for an ESXi host and /vsanHealth for vCenter Server respectively which will provide access to the new VSAN Management API interfaces.

UPDATE: (03/17/16) - Check out this article here on how to quickly get started with the new VSAN Management API.

For customers interested in consuming this new VSAN Management API, there will be initially five language specific bindings also known as an SDK (Software Development Kit) that will be available for download when VSAN 6.2 is generally available:

Reader Interactions

Comments

Not sure if this relates to what you posted but in my environment, I have a few monitoring tools (run by other IT folk) that have native integrations capabilities with VMware virtual environments (vSphere API). They’ve made it known that their tools (infovista, netcool, etc.) cannot see all vSAN metrics like IOPs, latency, etc.. We’re running vROPs with the MPSD (storage) solution in place. So vROps natively can see all those metrics but the external tools using the vSphere API inetgrations cannot see all vSAN metrics. Additionally, vROps reports like [Virtual Machine Inventory – Datastore I/O] are able to pull metrics for all non-vSAN datastores but cannot pull all metrics from vSAN. Thoughts?

What version of VSAN are you guys running? I only ask as this new VSAN Management API was just released with vSphere 6.0 Update 2 and I’m not sure how many of our partners out there have actually had a chance to consume the new APIs which does provide much more information performance metrics for VSAN which was not available with the vSphere APIs.

vSAN version 6u1 (esxi and vcenter) … I guess to better understand the situation, is the issue with reaching the new vSAN metrics stemming from the 3rd party tools needing to update their tools OR is it because we haven’t upgraded to ESXi 6u2 OR is it because vCenter needs to be upgraded to 6u2?

As much as I would like to fix the problem, at the end of the day, I just need to be able to give higher ups an answer as to why vSAN metrics aren’t visible:

1. ESXi needs to be updated
2. vCenter needs to be updated
3. 3rd party tools need to be updated to see the new/detailed vSAN metrics

One last thing I forgot to mention….so using vROps, the Virtual Machine: Datastore IOPs report doesn’t provide much vSAN metrics but vROps does provide all metrics when using the vSAN Solution Management Pack dashboards. Would that have to do with vROps needing to be updated (currently running vROps 6.1) so that the generic vROps reports include vSAN metrics?

Hi William
is there any way to know from the MOB what is the datastore vSan version ?
the only why i can think of right now is the look on the related hosts versions , but i am not sure that it is the right way

Primary Sidebar

Search this website

Author

William Lam is a Staff Solutions Architect working in the VMware Cloud on AWS team within the Cloud Platform Business Unit (CPBU) at VMware. He focuses on Automation, Integration and Operation of the VMware Software Defined Datacenter (SDDC).