Unsolved
This post is more than 5 years old
2 Posts
0
2778
XtremIO RESTful API - number of initators per storage controller
Hello
Looking through the XtremIO RESTful API guide, there does not appear to be a way to determine the number of initiators connected to a storage controller or (even better) storage controller port. Is there an API call on any object that will provide this information?
NOTE - this needs to be per storage controller, NOT cluster or XMS.
We are automating the zoning of initiators to XtremIO ports and need this information to select the best brick to zone hosts to on our multi-brick clusters (choose brick with least initiators zoned etc).
We could probably achieve this by tagging initiators with the storage controller ID when they are zoned and connected, however it would be better if this could be achieved by using the native data for connection stats on an object.
Thanks.
Kumar_A
727 Posts
0
February 4th, 2016 18:00
This is a valid ask and we will investigate it.
However, shouldn't the initiator balancing on the XtremIO side be done based on the workload being driven on each port (by the initiators that are connected on that port) instead of the count of the number of initiators only? For example, it might be okay to have a high number of low workload initiators connected on one port, while only a limited number of higher workload imitators should be connected on the other ports. Just a thought.
thephantom1
2 Posts
0
February 5th, 2016 01:00
Avi - thanks. Yes we will also be looking at the performance on SC ports as part of the selection logic. Given the performance of these arrays, this is less of a concern than would be on another type of array, however it will be part of the weighting when choosing candidate ports.
We are also looking at host environment type and capacity utilization as part of this process (although the latter will obviously be on a cluster basis, not Brick).
Looking forward to any updates on when the initiator count per SC port will be provided as part of the RESTful API object query - it is available on the GUI from the Initiator view under Configuration, but clearly this is no good for programmatic purposes.
Thanks.
Kumar_A
727 Posts
0
February 5th, 2016 12:00
You had mentioned earlier that you were seeing the information in GUI, but not in RestAPI. Can you share a screenshot of what you are referring to?
scotthoward
64 Posts
1
February 5th, 2016 20:00
I've got some good news, and some bad news.
The bad news is that you can't do it today. There's no REST API call that will return that information.
The good news is that we've already got a feature request for this, and it's already been implemented! Unfortunately you'll need to wait until the next release which is due sometime around mid-year to get it. Until then there's really no workaround other than to use the CLI, which may or may not be a workable option for you.
Depending on what you're trying to achieve you may also be able to use the "num-of-conn-tars" that is returned by the initiator object. This wont tell you how things are connected, but it'll at least give you a count which might be enough to determine that something is broken (ie, if you expect 4 connections and it's showing <4 then you've got an issue)