ScaleIO REST API Questions/Issues?

Question

We are running: EMC ScaleIO R1_32.2451.4 on a (4) node ESX 6.0 environment the deployment leverages 2 data networks there are (2) VMKernel adapters for the SDC's the SVM's are using VMNIC1 for management and VMNIC2 and VMNIC3 for data. 1) When I query the REST API for Sdc's the sdcIp field is only populated with a single IP address. I would have expected 2 SDC IP's to be reported when two data networks are used? The IP's reported are also a mixture of the two data networks instead of all being from a single VMKernel adapter? Example:      'sdcIp': u'192.168.2.153',      'sdcIp': u'192.168.2.152',      'sdcIp': u'192.168.1.150',      'sdcIp': u'192.168.1.151', 2) When I query the REST API for Sdc's the onVmWare field reports None instead of True since the SDC's are running embedded in the ESX kernel. The onVmWare field is correctly reporting True for the SDS's. Example:      u'onVmWare': None,      u'onVmWare': None,      u'onVmWare': None,      u'onVmWare': None, 3) What is the state of the ScaleIO python bindings being built out of the EMC CTO Office found here:      https://github.com/swevm/scaleio-py Does EMC recommend usage of these? 4) There's a typo in the 1.32 REST API Guide. The SDC object section lists a property called sdsApproved that should really be sdcApproved. What does this field indicate? Thanks,Andrew

tomer__engineer · Answer

1. The MDM do not know all the SDC IPs -> It only know the IP the SDC used to reach the MDM.

2. After looking into this issue, SDC cannot identify and fill this property anymore. It should be deprecated from the REST API as well. We will update our REST-API documentation for future versions.

3. I am not familiar with this - can someone else in the community answer it?

4. Thanks, we will update our REST-API documentation for future versions.

regana · Answer

As a consumer of the ScaleIO API it would be useful to be able to discover all SDC IP's and whether the SDC's are running on VMware or not.

tomer__engineer · Answer

You cannot know all SDC IPs also from the SCLI, as I explained above. Here are 2 examples of --query_all_sdc on Physical + VMware SIO system

VMware example (with same network configuration as you described - 1 Mgmt + 2 Data)

As you can see the SDC name appears with ESX prefix (name is assigned upon deploying via the vSphere plugin), that indicates it's on ESX.

scli --query_all_sdc

MDM restricted SDC mode: Disabled

Query all SDC returned 1 SDC nodes.

SDC ID: [ID] Name: ESX-[Mgmt_IP] IP: [SDC_IP] State: Connected GUID: [GUID] Version: 2.0.610

Read band 0 IOPS 0 Bytes per-second

Write band 0 IOPS 0 Bytes per-second

Physical example (with 1 Mgmt + 1 Data)

SDC has no name, when deploying via IM, unless you request it specifically, or name it post deployment

scli --query_all_sdc

MDM restricted SDC mode: Disabled

Query all SDC returned 1 SDC nodes.

SDC ID: [ID] Name: N/A IP: [SDC_IP] State: Connected GUID: [GUID] Version: 2.0.598

Read band 0 IOPS 0 Bytes per-second

Write band 0 IOPS 0 Bytes per-second

PowerFlex

Was this post helpful?