How do we create target groups in XmtremIO? I do not see any CLI/REST API to do so.
Also all the examples I see shows target group name as 'Default' and also the lun mapping samples I see has only one target group as 'Default'.
Does that mean that all the ports on array are available for mapping ? Also what is the purpose of having target group when we cannot create or allocate one.
In the REST API document for 4.0, I see that the lun-map returns something as target group name (tg-name), tg-index (target group index). Also while creating lun-map, it shows that it can accept tg-id.
you cannot Map the LUNs to a specific ports on XtremIO, it should be available on all the ports of the controllers. you need to control the paths on your fabric by zones.
I think he is asking what a target group is (tg-id)? Since all of the targets (iSCSI or FC) are added to the same default target group upon install, it seems you can create different target groups with different collections of target ports in them for the purposes of reporting and performance. Given all LUNs are accessible through all target ports as stated earlier in this thread, it would seem to be a useless function of the REST commands above since you would always want to use the default target group (or a target group that included ALL of the target ports on the array). I haven't tested this, but this is what I surmise from the documents (which I agree are vague and confusing for this product at times). I'm not sure what would happen if you created a target group with a subset of the target ports and tried to map a LUN through rest....my guess is that it would either produce an error or just ignore the target-group ID and map them to all the target ports.....might be a good test
that's my 2 cents....
Yes, i wanted to understand that if there are multiple target-groups are there restrictions that can be applied while lun-mapping. Also if there is no CLI/REST API to create a new target-group how is this functionality used.
There is only one target group in XtremIO - which as you mentioned earlier is the "Default" one. All the ports are included in that default target group. The "tg-name" that you see in an internal construct used to hold all the target ports from the array.
I will check with R&D if there is any specific reason why we need to expose the target groups in RestAPI and update the documentation accordingly.