Description of problem: At present to deploy gluster block provisioner admin has to do 3 oc commands and 1 command is required to deploy S3 template. This RFE is for an enhancement to cns-deploy tool to do it automatically based on some options or switches mentioned by the admin. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
https://github.com/gluster/gluster-kubernetes/pull/285
https://github.com/gluster/gluster-kubernetes/pull/299 -> S3 deployment.
As per the cns-deploy --help output, following are the newly included features/options to the tool as part of this RFE: ************************************* --no-block Don't deploy a gluster-block container. Default is to deploy. --block-host SIZE Specify the size (in GB) of the GlusterFS volumes which will be automatically created to host gluster-block volumes. Default is to not automatically create host volumes for gluster-block. --no-object Don't deploy a gluster-s3 container. Default is to deploy. --object-account ACCOUNT, --object-user USER, --object-password PASSWORD Required credentials for deploying the gluster-s3 container. If any of these are missing, object container deployment will be skipped. --object-sc STORAGE_CLASS Specify a pre-existing StorageClass to use to create GlusterFS volumes to back the object store. Two volumes are created, one for object data and one for metadata. Default is to create a new StorageClass called 'glusterfs-for-s3'. --object-capacity CAPACITY The total capacity of the GlusterFS volume which will store the object data. Default is '2Gi'. ************************************* We need to ensure that we are documenting this properly with examples in the appropriate section in the guide.
Based on Comment 8, Comment 9 and Comment 10, moving it to Verified.
I have reviewed the doc text. It looks good to me.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:2881
Marking qe-test-coverage as - since the preferred mode of deployment is using ansible