Thanks for starting this, Gourav!
I'm inclined to vote for a separate DevOps repo, to keep things more modular.
I know Marcus and I have done some work/testing starting from scripts that I
think Shameera created in dev-tools/ansible. I've got a side-repo up which
contains playbooks for provisioning and deploying the PGA from scratch as a
proof of concept, using dynamic inventory instead of a static file (so, on an
empty jetstream allocation, you get working instance running the PGA, with
router, public ip with a single ansible-playbook command). Next step there is
to add provisioning for VMs to run airavata, etc.
Script location
Branch
Purpose of Script
modules/cloud/ansible-playbooks???
develop
1. Provisions instances on EC2 and OpenStack (Jetstream)
2. Deploys a Mesos/Marathon cluster on the provisioned i?nstances
?
?dev-tools/ansible/
?develop
?1. Deploy/update airavata services on existing machines?/instances
2. todo - include provisioning scripts for cloud resources
https://github.com/ECoulter/airavata-vms
?
?1. POC for provisioning and deployment of PGA on Jetstream, with
dynamic inventory. (intended to merge with dev-tools/ansible when
complete/tested by others)
---------------
Cheers,
---------------------
Eric Coulter [email protected]
XSEDE Capabilities and Resource Integration Engineer
IU Campus Bridging & Research Infrastructure
RT/PTI/UITS
812-856-3250
