Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Currently, a large portion of our ansible scripts are handled via a submodule called ansible-hydra.

This is maintained on github by Digital Curation Experts (DCE) and can be found here: https://github.com/curationexperts/ansible-hydra

Currently, Alicia Cozine (acozine) is the primary contributor and if something does not make sense she is an excellent person to ask. She can be found on the Samvera Slack (@acozine).


Need to Knows:

Updating create_ec2.yml

Since create_ec2.yml is called at the ansible-inventory level, it must be copied from ansible-hydra into ansible-inventory. If changes to the create_ec2.yml file are made upstream, when updating the submodule also change the create_ec2.yml file at the ansible-inventory repo to make it match the new roles or tasks added in the submodule.

Updating the submodule

As a reminder, updates at ansible-inventory level will pull the submodule up to the last pinned point. If you need to update further, to test the compatibility of major changes to our scripts. Update the submodule directly.

Current issues

  • AWS build scripts are well defined, Vagrant scripts are still in progress
  • Support for Ubuntu 14.04 and 16.04 is baked in, CentOS support is there but runs into occasional issues
  • The 14.04 to 16.04 switch from init to systemd in Ubuntu has caused some service issues, most have been fixed but confirm those before 16.04 boxes are used outside of test builds
  • CHF builds make some notable divergences from ansible-hydra which are handled by additional playbooks to customize our machines. Changes to ansible-hydra may cause issues with our customizations.
  • When testing ansible-hydra, do not use ansible-inventory's build scripts due to the aforementioned customizations.

Future Plans

  • More support for building out networks of Sufia/Hyrax boxes in groups
  • No labels