Ansible Deployment

Ansible Deployment

Target release

2.2

Epic

https://gobiiproject.atlassian.net/browse/GDM-326

Document status

DRAFT

Document owner

@Yaw Nti-Addae

Designer

@Yaw Nti-Addae

Tech lead

@Roy Petrie

Technical writers

@Roy Petrie

QA

@Deb Weigand

Objective

  1. Unify deployment to environments within and outside of Cornell

  2. Streamline deployment scripts to make it easy for system administrators to install GDM

  3. Clear separation of Continuous Integration and Deployment pipelines to make then more modular

Success metrics

Goal

Metric

Goal

Metric

Continuous Deployment

  • Convert all deployment scripts to deployment pipeline

  • Create configurable playbooks

  • Test deployment pipeline by deploying GOBii-GDM to QA-test and AWS environments

Deployment Integration

  • Work with GOBii personnel to connect Bamboo to deployment pipeline

  • Develop Web UI to allow users to configure deployment pipeline, and if possible run deployment (Phase II - new req needed for this)

  • Provide documentation of scripts and tools

  • Train GOBii personnel on how to extend Ansible and use tools

Deployable tools

  • GOBii-GDM

  • Portal

  • Timescope

  • KDCompute (optional)

  • ownCloud (optional)

  • Portainer (optional)

    • Sherpa (optional)

  • User manager (optional)

Assumptions

  1. Packing of the artifacts will be done by Bamboo

  2. This deployment pipeline is for vanilla GDM deployment 

    1. other technologies may be deployed for other hotfixes

  3. System Administrators will manually provide configuration variables before executing deployment pipeline

Requirements

Requirement

User Story

Importance

Jira Issue

Notes

Requirement

User Story

Importance

Jira Issue

Notes

1

HIGH





2











User interaction and design

Open Questions

Question

Answer

Date Answered

Question

Answer

Date Answered



Out of Scope