|
Post by Venkatesh on Mar 22, 2017 5:54:30 GMT
We are just exploring the swordfish specification to implement in the stack.
While going through the swordfish specification 1.0.3, I am not able to get the exact difference between the ClientEndPointGroup and ServerEndPointGroup.
Here is the definition from the spec.
The set of client endpoints to which the volumes can be exposed is specified by the ClientEndpointGroupsattribute. The ClientEndpointGroup resource specifies a collection of EndpointGroup resources.
The set of server endpoints to which the volumes can be exposed is specified by the ServerEndpointGroupsattribute. The ServerEndpointGroup resource specifies a collection of EndpointGroup resources.
Thanks in advance for the clarification.
|
|
|
Post by Richelle Ahlvers on Mar 22, 2017 16:53:53 GMT
Client endpoints, sometimes referred to as initiator endpoints, are implemented on the client system.
Server endpoints, sometimes referred to as target endpoints, are implemented on the system supporting the storage.
Does this clarification help?
Note that all of the endpoints will be in the general EndpointCollection.
|
|
|
Post by Richelle Ahlvers on Mar 22, 2017 19:33:54 GMT
An EndpointGroup represents a collection of endpoints that are managed as a unit. By grouping together a collection of Endpoints, the EndpointGroup allows a collection of entities from differing sources or hosts to be manipulated uniformly and efficiently.
For any given EndpointGroup, all of its endpoints act exclusively as either server endpoints or client endpoints, as indicated by the value of the EndpointType property. Similarly, each Endpoint within a group has the same AccessState.
A server or client may define multiple EndpointGroup entities that access the same set of resources or functionality. A group may be designated as preferred, which signifies that access should be directed through its members in preference to the Endpoints listed in other EndpointGroups. If the value of EndpointType is Server, an EndpointGroup entity can be used to represent target port group as defined by SCSI. In that mode, the value of the TargetEndpointGroupIdentifier should correspond to the target port group number. (See clause "Device Identification VPD page" as defined in the SCSI Primary Commands specification.)
|
|
|
Post by Richelle Ahlvers on Mar 22, 2017 19:34:27 GMT
(This section somehow got missed from inclusion in the spec. We're fixing that now.)
Thanks, Richelle
|
|
|
Post by Venkatesh on Mar 23, 2017 5:53:33 GMT
Thanks a lot... If my understanding is correct, then creating ClientEndPoint/ServerEndPointGroup will be issued/called by the Managing/Orchestration Software.
|
|