Sameer Shanbhag - please take a look

Hi Professor,

I have updated the Bioviz Playbook to point to my feature branch, Pull Request:
Updated PR

• https://bitbucket.org/lorainelab/bioviz-playbooks/pull-requests/7/igbf-2545-add-feature-branch-to-bioviz

Improvement to deal with unavailable Quickload website has been added to the following commit:

• https://bitbucket.org/sshanbh1/genome-dashboard/commits/07734cd8ee1a8c609c0e2bf015fd90bbde02234f

c.c. Prof. [~aloraine] Please have a look at the update PR for Bioviz playbook and let me know if that looks right

Please do not add bioviz_vars.yml to the repository. This actually should never be checked in because once properly configured the file contains AWS secret keys and whatnot.

What we actually need to do is add a configuration to bioviz-playbooks that ensures that the IGB preferences file for the current release branch of Integrated Genome Browser is used and not the latest master branch.

The bioviz-playbooks have a configuration that specifies the IGB release version being used. When deploying genome dashboard code, we can include a play that edits deployed genome dashboard code to ensure that the release branch specified in the playbooks is also the same version of the IGB preferences file being used to retrieve the igbquickload sites and their backups. This can be done using the "file" module in ansible.

I will show how this works tomorrow. It is a bit easier to show how it works than explain it. So let's hold off on this until then.

Thank you Sameer Shanbhag! Have a great rest of your day!

Hi, Prof. [~aloraine],

I have updated the pull request:

• https://bitbucket.org/lorainelab/bioviz-playbooks/pull-requests/8/igbf-2545-implement-a-play-to-replace

Please let me know if the changes look good.

To test:

• Run the playbooks and confirm the site is properly deployed.
• Make a branch of IGB and modify the preferences JSON file to include a new quickload repository with species and/or genome version not present in the current release of IGB; confirm the new QL species appears in Genome Dashboard deployed on the test site
• Include non-functional primary, non-functional secondary pairs in the JSON file to check that Genome Dashboard still works and also that it can use a working secondary site when its primary site is non-functional

Keep good note on exactly what you tested. Ask Sameer for clarification if any of this does not make sense.

Message from Noor Zahara:

I am getting an error - "msg": "Instance creation failed: Value (Bioviz) for parameter iamInstanceProfile.name is invalid. Invalid IAM Instance Profile name" Is there something that I am missing?

Yes, this needs to be set up in your AWS account. The setup for this ought to be should be included in the bioviz playbook, but it might not be.

Please ask Sameer Shanbhag - Did he encounter the same problem?