|
Post by Venkatesh Periyasamy on May 10, 2017 14:03:42 GMT
I am trying to prepare sample input mockups which are required for the resources that can be created(POST Commands) specific to Swordfish specification 1.0.3.
1. For Storage Pool creation, the client should specify the Name, Class Of Service and required capacity. Here I am not able to get how to pass required capacity? Since Capacity Property of schema talks about the usage and allocated space from the underlying DataStore. How to specify the drives/pools/Volumes that needs to be used to create storage pool.
2. For Storage Group, the client may need to specify the volumes, client point groups and server endpoint groups. But as per storage group schema, those properties are defined as reference to volume collection,ServerEndpointCollection,ClientEndPointCollection as follows
<NavigationProperty Name="ClientEndpointGroups" Type="EndpointGroupCollection.EndpointGroupCollection" ContainsTarget="true"> <NavigationProperty Name="ServerEndpointGroups" Type="EndpointGroupCollection.EndpointGroupCollection" ContainsTarget="true"> <NavigationProperty Name="Volumes" Type="VolumeCollection.VolumeCollection" ContainsTarget="true">
Now how do i need to specify these properties to create new storage group? Do i need to create endpoint group collection and then pass it to the schema or ?
Thanks in advance,
|
|
|
Post by gericson on Aug 16, 2017 16:34:50 GMT
Venkatesh Periyasamy: On StoragePool creation, the idea is to specify one or more ClassOfService entities. That and Capacity data structure specifies the desired amount of storage for Data, Metadata and Snapshots. Also whether storage is to be allocated thin or not. The choice of specific underlying storage is intended to be left to the implementation using that info. You could go farther and specify values for the CapacitySources property, but that is NOT the swordfish intention, since the goal is to push decisions about how the results are provided is intended to be pushed down to the implementation. On StorageGroup creation, there is a change queued up that will change the resource collections into simple collections. We've learned that the use of resource collections for these properties was overkill. The intention is that you can POST to create the StorageGroup as a whole.
|
|