I have not yet tested this, but since we have moved forward with the next development phase with IGBF-2403, moving this to "Closed."

We will do testing for this ticket (IGBF-2382) as part of testing IGBF-2403.

PR: https://bitbucket.org/lorainelab/bioviz-connect-playbooks/pull-requests/2/igbf-2382/diff

Testing Results:

I was able to install Ansible on my ec2 installed and cloned IGBF-2832 changes and ran the playbook to generate an ec2 instance.
I have compared chaitanya.bioviz.org's apache settings with the newly created ec2 and apache settings are intact.

1) Servername is configurable in common.yml
2) Certificate names are configured in defaults
3) The necessary config files such as 00-default and SSL config are in the apache2 folder with appropriate configurations.
4) default conf and SSL rewrite are enabled.
5) The playbook deployment stops at moving certificates to the specific folder since, the certificates are not yet created, which I guess is work in progress.

Moving to Ready for Pull Request

Below is a summary of all the changes
1. Servername is configurable in common.yml
2. certificate names are configurable in defaults of the deploy_certificates role
3. apache2 installer and additional packages are setup.
4. https is configured according to the https://docs.google.com/document/d/1_-TZr2UJBs9vbqR2wfRifCkjgp-wi6KSXtSX5ozaiYE/edit#
5. default conf and ssl conf templates are added.
6. older httpd role is removed
7. OS is changed to a newer AMI of ubuntu

Hi Dr. Loraine,
I Made the requested changes.
Certificate names are changed in the defaults folder of the certificates role
server name has 2 parts server name and domain name both are user defined.
bioviz-connect repo is cloned instead of bioviz as in earlier

Additional correction
OS is changed to ubuntu and path changes are amended.
https changes are added and removed httpd role from earlier

Review: https://bitbucket.org/chesterdias/chester-local-bioviz-connect-playbooks/branch/IGBF-2382#diff

Change requests:

• Do not hard-code the names of the certificates but instead get them from user-supplied variables

• Do not hard-code the domain "bioviz.org" but instead require the user to set it (re: ServerName: "{{ ec2_name }}.bioviz.org")

• bioviz repo should not be cloned as it is deployed independently from bioviz-connect

• bioviz-connect repo should be cloned - address is: https://bitbucket.org/lorainelab/bioviz-connect

• check with Nowlan Freese or Chaitanya Kintali as to what the document root is being used for connect.bioviz.org

To see bioviz-connect in action, go to:

• https://bioviz.org
• click the link labeled "BioViz Connect" in the title bar

You will need to sign up for an account at CyVerse - follow the links for that.
Once you do that, you can try it out by following the use case scenario described in this paper draft:

https://www.dropbox.com/s/3l72dgkxkbbjx3n/2020-05-14-biovizconnect.docx?dl=0

I have made the required changes.
Please Review: https://bitbucket.org/chesterdias/chester-local-bioviz-connect-playbooks/branch/IGBF-2382#diff

let me know if any more changes are needed.

As part of this ticket, let us modify role and playbook names to match up better with conventions used by others in the ansible community, for example, in the n "ansible-examples" repository https://github.com/ansible/ansible-examples (linked to from ansible documentation itself) and also the ansible book by Jeff Geerling (https://leanpub.com/ansible-for-devops)

Changes:

• Instead of camelCase use snake_case

• Use nouns instead of verb/object constructions as role names, for example: ec2 instead of provision_ec2

For task (play) names, we will continue using the same "verb-direct object" construction like we do with git commit messaes, e.g.,

• Install Node.js (npm plus all its dependencies)

or

• Restart Apache