Bug 1328365 - Display the recommended number of Placement Groups per OSD in the Pool creation workflow of RHSC web UI
Summary: Display the recommended number of Placement Groups per OSD in the Pool creati...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Storage Console
Classification: Red Hat
Component: UI
Version: 2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 2
Assignee: sankarshan
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-19 08:20 UTC by Rakesh
Modified: 2016-05-24 07:17 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-24 07:17:50 UTC
Target Upstream Version:

Attachments (Terms of Use)
Create new Pool (36.17 KB, image/png)
2016-04-19 08:20 UTC, Rakesh 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Rakesh 2016-04-19 08:20:57 UTC 
Created attachment 1148399 [details]
Create new Pool

Description of problem:

In the pool creation workflow(see attached image), I see a slider integrated to optimize the pool creation based on the size and the corresponding number of PGs. Just before the slider, can we code the UI to suggest/display the recommended numbers of PGs per OSD? This will give the users/storage admins an idea of the recommended number of PGs per OSD.


Version-Release number of selected component (if applicable):
Red Hat Storage Console 2.0


Actual results:


Expected results:
UI suggesting recommended number of PGs per OSD.


Additional info:
Comment 2 Nishanth Thomas 2016-05-05 07:13:54 UTC 
Per current design PG num is automatically calculated. If no of OSDs are less than 50, PG num is defaulted to 128. If no of OSDs are > 50 , pg num is auto calculated based on the target allocation size with an option for the user to override.
Is it what you are looking for?
Comment 3 Nishanth Thomas 2016-05-14 13:50:20 UTC 
Bobb, Can you provide the required info?
Note You need to log in before you can comment on or make changes to this bug.