Configuration-based installation of OpenShift and Cloud Pak for Data/Integration/Watson AIOps on various private and public cloud infrastructure providers. Deployment attempts to achieve the end-state defined in the configuration. If something fails along the way, you only need to restart the process to continue the deployment.
Describe the bug
Cloud Pak Deployer setup OpenShift on Self-Managed AWS with an EFS file system. I noticed that the EFS was created with Throughput set to 'Bursting' mode. The CP4D IBM documentation does not specify that. Assuming therefore it should use default settings, then the Throughput should be set to 'Elastic (Recommended)'.
Either the code should be switched to 'Elastic' or enhanced to accept a parameter. If the latter there is a third mode 'Provisioned' which also requires a Throughput value in Mibps.
Note: Please don't default it to 'Provisioned' though as that is very expensive!
To Reproduce
Steps to reproduce the behavior:
Standard Yaml snippet:-
`nfs_server:
Expected behavior
Code is called from automation-roles/30-provision-infra/provision-aws/tasks/aws-file-server.yamlaws efs create-file-system \ --performance-mode generalPurpose \ --throughput-mode bursting \ --encrypted \ --region {{ _current_nfs_server.infrastructure.aws_region }} \ --tags Key=Name,Value={{ _current_nfs_server.name }}
Additional Info
If you run aws efs create-file-system, it selects bursting mode by default anyway. But if you follow the IBM doco instructions here, it actually uses these settings by default:-
Describe the bug Cloud Pak Deployer setup OpenShift on Self-Managed AWS with an EFS file system. I noticed that the EFS was created with Throughput set to 'Bursting' mode. The CP4D IBM documentation does not specify that. Assuming therefore it should use default settings, then the Throughput should be set to 'Elastic (Recommended)'.
Either the code should be switched to 'Elastic' or enhanced to accept a parameter. If the latter there is a third mode 'Provisioned' which also requires a Throughput value in Mibps.
Note: Please don't default it to 'Provisioned' though as that is very expensive!
To Reproduce Steps to reproduce the behavior: Standard Yaml snippet:- `nfs_server:
Expected behavior Code is called from automation-roles/30-provision-infra/provision-aws/tasks/aws-file-server.yaml
aws efs create-file-system \ --performance-mode generalPurpose \ --throughput-mode bursting \ --encrypted \ --region {{ _current_nfs_server.infrastructure.aws_region }} \ --tags Key=Name,Value={{ _current_nfs_server.name }}Additional Info If you run aws efs create-file-system, it selects bursting mode by default anyway. But if you follow the IBM doco instructions here, it actually uses these settings by default:-