review setup of osparc.io

[sanderegg]

git branching schema

• master
• staging
• production

platforms:

• master - (ex-staging) osparc01@z43
• staging @staging.osparc.io
• production @osparc.io
  notes:
• staging and production share the same registry
• staging and production have separate database, separate S3
• registry data shall be in S3
• DB shall be replicated

ToDos:

• add a new name: staging.osparc.io
• deploy stack in staging.osparc.io with autodeployer app
• deploy stack in production.osparc.io with autodeployer app
• rename staging to master in travis scripts
• re-configure autodeployer app in master platform
• add staging, production stages in travis scripts

Workflow (a la Gitlab Flow)

going to master:

1. developpers do PRs to master with new features/bugfixes
2. PRs are built and tested
3. Once PRs accepted, master is rebuilt, tested
4. CI automatically tags and pushes to master
   • itisfoundation/webserver:master-latest
   • itisfoundation/webserver:master-DATE-TRAVIS_BUILD_NUMBER-GIT_SHA
5. CD automatically updates the master platform

going to staging:

1. developers decide
2. pull request master -> staging
3. CI automatically create release notes, tags and pushes to staging
   • itisfoundation/webserver:staging-latest
   • itisfoundation/webserver:staging-DATE-TRAVIS_BUILD_NUMBER-GIT_SHA
4. CD automatically updates the staging platform

going to production:

1. POs decide
2. pull request staging -> production
3. CI automatically create release notes, tags and pushes to production
   • itisfoundation/webserver:production-latest
   • itisfoundation/webserver:production-DATE-TRAVIS_BUILD_NUMBER-GIT_SHA
4. CD automatically updates the production platform