Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

specification for RBDs list view #108

Closed

Conversation

kamleshverma1
Copy link
Contributor

specification for RBDs list view

@kamleshverma1
Copy link
Contributor Author

@gnehapk @brainfunked @anivargi @shtripat @nthomas-redhat Please review it.

@kamleshverma1
Copy link
Contributor Author

Addresses #75 .

Required from API -

* Response format for the API call
* If "GetClusterList" contain RBDs list . than "parameter name" should be known which is holding the RBDs list.
Copy link
Contributor Author

@kamleshverma1 kamleshverma1 Dec 29, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@anivargi @shtripat @brainfunked If "GetClusterList" contain RBDs list . so Can i have "parameter name" which is holding the RBDs list ? or Is there any other APi for RBDs list ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kamleshverma1 I feel rbd listing should be a separate api like /clusters/{id}/GetRbdList. @anivargi can you confirm please?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with @shtripat RBD list should be separated API call.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@shtripat @mkudlej Currently the API responds with all cluster related objects in 1 API call like for ex: for Ceph we have pools, but we surely have individual API calls for all storage objects like pools, RBD's in the future.

@kamleshverma1 The info will be present in the GetClusterList API call, currently I am not aware of the structure of how the details are stored in etcd and what the attributes are called, so if @shtripat or @nthomas-redhat can have a instance which has the details populated then the API will automatically respond with the desired response.

@kamleshverma1
Copy link
Contributor Author

@gnehapk @cloudbehl @anivargi @nthomas-redhat @shtripat Please review this spec . i have updated this.


Required from API -

* status
Copy link
Contributor Author

@kamleshverma1 kamleshverma1 Feb 8, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@anivargi @nthomas-redhat @shtripat according to UX mockup (https://redhat.invisionapp.com/share/BR8JDCGSQ#/screens/198417119) , missing these fields for RBDs in given response format by anup

  1. status
  2. utilization
  3. alert count

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kamleshverma1 utilization and alert count would be done as part of monitoring I feel. I dont see a status field as such for rbds in cli output from ceph.

@r0h4n r0h4n closed this Apr 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants