-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS Deployment Enhancements #84
Comments
see changing this: https://github.com/Islandora-Devops/ansible-role-fcrepo/blob/master/templates/jdbc-mysql-repository.json to something closer to this: https://github.com/fcrepo4/fcrepo4/blob/master/fcrepo-configs/src/main/resources/config/jdbc-mysql-s3/repository.json |
ELB provisioning added with asulibraries/islandora-playbook@f728015 |
added a new template at { |
Also worth noting that the keys pointed to by the syn-settings.xml files, such as /opt/keys/claw/public.key must MATCH on the two (or more) servers that are expected to communicate. and that key is proliferated in other places during deployment (ie within crayfish) |
I also had to modify the syn-settings for both crayfish and fedora.
This could potentially be rolled back up into a PR for upstream - it would require using a variable, much like the way it is handled in the fcrepo-syn role here: https://github.com/Islandora-Devops/ansible-role-fcrepo-syn/blob/master/templates/syn-settings.xml |
Eli to do: add and configure https://www.drupal.org/project/flysystem_s3 to write drupal files directly to s3. Ideally we probably need to be using private files for all of the derivatives and such since some of those files will be limited access. |
went the route of https://www.drupal.org/project/s3fs which uses the AWS SDK for communicating with S3 for drupal public and private files instead of have to use s3fuse due to known performance issues |
This issue is still pending for separation of FITS and moving Gemini to RDS |
FITS has been provisioned to the services server. |
in order to accomplish this, due to pending PRs, i applied those prs to local copies of the ansible roles and deployed. |
A follow up from: #77
Goal state: https://www.lucidchart.com/invitations/accept/8a83a394-5cf6-48c8-9434-6803456c283a
still need to watch for:
Islandora-Devops/islandora-playbook#162 (needed to separate FITS from webserver)
islandora-deprecated/ansible-role-crayfish#31 (needed to separate Gemini to RDS)
Need to set up
The text was updated successfully, but these errors were encountered: