Specification for storage system detection

Tendrl / specifications

Tendrl specs go here

GNU Lesser General Public License v3.0

6 stars 16 forks source link

Specification for storage system detection #117

Closed shtripat closed 7 years ago

shtripat commented 7 years ago

Signed-off-by: Shubhendu shtripat@redhat.com

shtripat commented 7 years ago

@Tendrl/tendrl-core @Tendrl/tendrl_api please review

mkudlej commented 7 years ago

Do I understand it right that after implementing this spec there is no need to add sds_version(and sds_name) parameter to API function calls? You can find sds_version and sds_name as parameters here https://github.com/anivargi/documentation/blob/c26ccba15091efd70de41c54929f5f710626b8ec/api/ceph-pool-examples.adoc and https://github.com/Tendrl/documentation/blob/master/api/gluster-create-volume-example.adoc

If yes, then there is API impact and it should be mentioned in spec.

shtripat commented 7 years ago

@mkudlej These values get tagged with storage nodes. I feel still jobs need to provide sds_type and sds_version fields fetched from nodes list while import cluster flows.

@brainfunked comments?

mkudlej commented 7 years ago

@shtripat My question was not just about cluster import but more about all other functions for managing clusters and other cluster atoms.