-
Notifications
You must be signed in to change notification settings - Fork 96
doc: Add management requirements #701
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
base: master
Are you sure you want to change the base?
Conversation
doc/requirements/management
Outdated
| title: Remove active cache volume with dirty data with flush | ||
| id: remove_cache_volume_active_flush | ||
| --- | ||
|
|
||
| While cache volume is active and contains dirty data, the management tool shall | ||
| allow to remove cache volume with flush. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like the requirements are over specified. You added requirements for removing active&dirty and inactive core but you missed one for active&clean.
I would start with the requirement for removing core (without mentioning about any particular state) because that's the feature that CAS shall be able to handle. After this general statement I would add the requirements for flushing a dirty core before its removal, for optional skipping that step by giving additional confirmation and for interrupting the flushing.
doc/requirements/management
Outdated
| When active cache volume that contains dirty data is removed without flush, | ||
| the management tool shall not allow to interrupt the removal operation and the | ||
| cache volume shall be successfully removed with proper warning about displayed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it is about management operations I would focus on writing requirements for what CAS shall support rather than what it shall not support. Btw with When active cache volume that contains dirty data is removed without flush (...) the cache volume shall be successfully removed you are implying that removing dirty core shall always succeed. I think it would be hard to implement
|
comment regarding the title: "add a few management requirements" |
Signed-off-by: Slawomir Jankowski <slawomir.jankowski@intel.com>
Signed-off-by: Slawomir Jankowski <slawomir.jankowski@intel.com>
Signed-off-by: Slawomir Jankowski <slawomir.jankowski@intel.com>
Signed-off-by: Slawomir Jankowski <slawomir.jankowski@intel.com>
Signed-off-by: Slawomir Jankowski <slawomir.jankowski@intel.com>
Signed-off-by: Slawomir Jankowski <slawomir.jankowski@intel.com>
|
Can one of the admins verify this patch? |
Add the requirements for the
casadmcommands (including the script commands):Signed-off-by: Slawomir Jankowski slawomir.jankowski@intel.com