As a storage admin, I want to deploy RHGSWA in a manner as close to automated as possible by using the tendrl-ansible installation available method in Tendrl 1.6.3. Additional info: https://github.com/Tendrl/tendrl-ansible/blob/release/1.6.3/README.md https://github.com/Tendrl/documentation/wiki/Tendrl-release-latest
Adding missing qe ack.
I have rechecked the text again, see my feedback below. 1) The text states (3.2. Installation Workflow, Ansible Groups) > The sample site.yml playbook from tendrl-ansible package expects ... but should be: > The site.yml playbook from tendrl-ansible package expects ... Because the site.yml playbook is no longer just an example. 2) Text states (3.3. Web Administration Installation, Procedure. Installing Web Administration, step 4): > Enable or disable features by specifying values to the variables such > as etcd-tls client authentication This etcd-tls client authentication is described in a separate chapter (Chapter 5. TLS Encryption Configuration), it would be nice to point this out and link it (so that customer will connect the dots). 3) Text states (3.3. Web Administration Installation, Procedure. Installing Web Administration, step 5): > For detailed inventory file configuration, see the README.md file > provided with the installation > # less /usr/share/doc/tendrl-ansible-1.6.3/README.md I feel that this step would be better converted into note of previous step. Would it make sense? 4) Text states (3.3. Web Administration Installation, Procedure. Installing Web Administration, step 6): > If you use tendrl-ansible from the rpm package, copy the site.yml playbook > into the ... Should be: > Copy the site.yml playbook into the ... As we support tendrl-ansible from rpm package only. 5) Text states (3.3. Web Administration Installation, Procedure. Installing Web Administration, step 9): > To check if Web Administration minimal requirements and setup are > satisfied, run the prechecks playbook To make purpose of this prechecks playbook absolutely clear, I would suggest to add the following note here: ``` Any problem with the pre checks will make the playbook run fail immediately, pointing you to a particular requirement or problem with configuration before the installation itself (preventing you to spend time with unnecessary debugging after installation). ```
I think that this can be verified after Martin's notes are incorporated.