|
Post by Venkatesh Periyasamy on May 4, 2017 11:48:24 GMT
I am just trying to represent iSCSI target and initiator in EndPoint resource schema. I assume(based on the understanding), that iSCSI target name will be specified in the identidfiers property of EndPoint schema and the same for iSCSI initiator. Is that correct?
I have also noticed that EndPoint has another property called ConnectedEntity which describes the other end of the end point. ConnectedEntity has the property called 'EntityRole' which describes the role of the endpoint. But main EndPoint does not have any role like this. Is it correct?
Correct me if my understanding is wrong.
Do we have any simple mockup to represent end points with respect to iSCSI?
|
|
|
Post by Venkatesh Periyasamy on Apr 26, 2017 11:54:25 GMT
As per the specification document(1.0.3), Some of the classes(Chassis,Systems,EndPoints) are referred from redfish. But it does not describes which version of redfish specification to refer? Is it ok to use any version of the redfish version? or As per mockup , it is referring 1.0.2 version? Is there way to mention the REST client that the version of redfish specification used by the service?
|
|
|
Post by Venkatesh Periyasamy on Apr 21, 2017 12:43:54 GMT
In the capacity properties, As per the specification, ProvisionedBytes: The value shall be the maximum number of bytes that can be allocated in this data store for this data type GuaranteedBytes: The value shall be the number of bytes the storage system guarantees can be allocated in this data store for this data type.
From my understanding, Typical storage servers provisioned to create pool/volume with supported max size irrespective of the maximum capacity that can provided with the current disks. This is with the assumption that later on pool can be expanded with the additional bunch of disks. Here ProvisionedBytes denotes the maximum size the pool/volume can support (Irrespective of the current capacity) and GuaranteedBytes denotes the maximum capacity that can be used based on the current disks capacity.
Is this understanding is correct? Correct me if i am wrong.
Thanks in advance.
|
|
|
Post by Venkatesh Periyasamy on Apr 21, 2017 12:07:43 GMT
Which class/schema represents snapshot related information like 1. Creating snapshot 2. How to expose the snapshot volume 3. Scheduling snapshots( This i am seeing for replicas). How to do configure snapshot for the volumes without replica?
Thanks in advance.
|
|
|
Post by Venkatesh Periyasamy on Apr 21, 2017 11:50:10 GMT
I have the following query on the EndPoint resource schema.
1. PciId ,HostReservationMemoryBytes -- I assume this is not applicable to the iSCSI intiator and targets 2. ConnectedEntities -- Looks like Storage initiator refers to the initiators and Storage expander refers to the physical device. What will be the entity type for the iSCSI storage target endpoint ? -- I assume EntityPciId,PciFunctionNumber and PciClassCode is not applicable to iSCSI storage 3. Links to Ports -- As per specification, it is specific to physical ports. So i assume this also not applicable to iSCSI Storage servers.
I am not able to find mockup which represents iSCSI storage and initiator. Do we have any mockups for the same? Which will be helpful to understand better.
And also which property of EndPoint resource specifies about the iSCSI Target Portal Groups?
Thanks.
|
|
|
Post by Venkatesh Periyasamy on Apr 20, 2017 12:20:20 GMT
I have the following query on the EndPoint resource schema. 1. PciId ,HostReservationMemoryBytes -- I assume this is not applicable to the iSCSI intiator and targets 2. ConnectedEntities -- Looks like Storage initiator refers to the initiators and Storage expander refers to the physical device. What will be the entity type for the iSCSI storage target endpoint ? -- I assume EntityPciId,PciFunctionNumber and PciClassCode is not applicable to iSCSI storage 3. Links to Ports -- As per specification, it is specific to physical ports. So i assume this also not applicable to iSCSI Storage servers.
I am not able to find mockup which represents iSCSI storage and initiator. Do we have any mockups for the same? Which will be helpful to understand better.
Thanks.
|
|
|
Post by Venkatesh Periyasamy on Apr 20, 2017 10:11:36 GMT
As per the specification(1.0.3),Under Storage Group Resource(5.9), ServerEndPointGroup is defined as follows.
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.
Here the ServerEndPointGroup may contain more than one endpoints through which the volume/LUN can be exposed. i.e one LUN/Volume can be exposed to multiple iSCSI targets(EndPoints). This may lead to data corruption also.
Is there any other reason behind defining multiple server endpoints to single LUN/Volume? Is there any attribute/class maps LUN to specific ServerEndPoint (One-To-One) rather than doing it as a group?
|
|