You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because ibm_svc_manage_volume.py uses mkvolume, as opposed to mkvdisk, it does not allow users to create volumes without formatting them. This can cause a problem in large customer environments where many volumes are being created at once. It drains memory through the format process and also creates a situation where the format process is estimated to take an extremely long time (days to weeks)
ISSUE TYPE
Feature Idea
Add a format parameter as optional. When format is used then the command will be mkvidsk instead of mkvolume
COMPONENT NAME
ibm_svc_manage_volume
ADDITIONAL INFORMATION
This would be used as it is now. However the current code automatically formats all volumes which causes problems in large new environments.
as mentioned, this would be any normal playbook. It would simply add a format parameter. I have no example playbooks at this time.
The text was updated successfully, but these errors were encountered:
SUMMARY
Because ibm_svc_manage_volume.py uses mkvolume, as opposed to mkvdisk, it does not allow users to create volumes without formatting them. This can cause a problem in large customer environments where many volumes are being created at once. It drains memory through the format process and also creates a situation where the format process is estimated to take an extremely long time (days to weeks)
ISSUE TYPE
Add a format parameter as optional. When format is used then the command will be mkvidsk instead of mkvolume
COMPONENT NAME
ibm_svc_manage_volume
ADDITIONAL INFORMATION
This would be used as it is now. However the current code automatically formats all volumes which causes problems in large new environments.
as mentioned, this would be any normal playbook. It would simply add a format parameter. I have no example playbooks at this time.
The text was updated successfully, but these errors were encountered: