This repository contains scripts to manage the PhenoMeNal cloud VRE.
Shell
Permalink
Failed to load latest commit information.
KubeNow @ 4024dab added luigi, changed jupyter mount to subpath, remove gce credentials… Feb 3, 2017
bin added ansible playbooks waiting until HTTP service is up for jupyter … Feb 2, 2017
cloud_portal added image upload playbook if google cloud Feb 16, 2017
phenomenal-cloudflare @ 29f0745 updated private credentials repo version Jan 15, 2017
playbooks
.gitignore update readme, refactoring Dec 19, 2016
.gitmodules update readme, refactoring Dec 19, 2016
LICENSE Initial commit Dec 16, 2016
README.md Update README.md Feb 3, 2017
manifest.json restored jupyter deployment added parameters to galaxy deployment Jan 29, 2017
test_env_vars_for_aws.sh Update test_env_vars_for_aws.sh Jan 29, 2017
test_env_vars_for_embassy.sh added dns variable in embassy test_env_file AND updated KubeNow repo … Jan 31, 2017
test_env_vars_for_gcp.sh Update test_env_vars_for_gcp.sh Jan 29, 2017

README.md

cloud-deploy-kubenow

This repository contains one-click-deploy-scripts to setup the PhenoMeNal cloud VRE. The scripts are designed to work with the EMBL-EBI-TSI - Phenomenal Web-UI.

This repository contains submodules so use the --recursive parameter when cloning e.g.

git clone --recursive https://github.com/phnmnl/cloud-deploy-kubenow.git

Note: You might get an error message: fatal: clone of 'git@github.com:EMBL-EBI-TSI/phenomenal-cloudflare.git' into submodule path 'phenomenal-cloudflare' failed. This is because you don't have the access rights to read the private repository containing secret api keys.

If you later want to pull latest version and also pull latest submodule updates:

git pull --recurse-submodules
git submodule update --recursive --remote

Directories and files

├── cloud_portal            # This is where the cloud portal deploy.sh, destroy.sh and state.sh scripts 
│   │                       # are stored in subdirectories per cloud provider
│   │
│   ├── aws                 # Sub directories per cloud provider
│   ├── gcp
│   ├── ostack
│   └── shared              # The bulk part of the deploy.sh, destroy.sh and state.sh are identical between
│                           # provides and is residing in a shared version of the scripts called from the
│                           # provider speciffic scripts
│
│
├── KubeNow                 # This is the standard KubeNow git repo included as a git sub-module and this is
│                           # where the terraform and default KubeNow ansible scripts reside (called from the
│                           # deploy.sh, destroy.sh and state.sh scripts)
│                            
│                            
├── playbooks               # Ansible playbooks that are Phenomenal release speciffic and not included in the
│                           # default KubeNow repository    
│
│
├── bin                     # Utility script that are used in the deploy.sh, destroy.sh and state.sh scripts
│
│
├── phenomenal-cloudflare   # This is a private git repository as a submodule storing cloudflare secret token
│
│
│
├ manifest.json             # This is the TSI parameter file used to describe the setup
│
│
├ test_env_vars_for_embassy.sh     # Includes vars expected to be provided from web-ui and only used for local
│                                  # testing purposes
│
├ test_env_vars_for_aws.sh         # Amazon version of testing vars       
│
│
└ test_env_vars_for_gcp.sh         # Google cloud version of testing vars                                     

If you want to test the deployment:

First, If you don't have a "kubenow-v020a1" image available in your cloud teenancy then you need to upload or build one.

Latest images are availabe for upload into your teenancy from: https://github.com/kubenow/KubeNow/releases

Or if you want to build one, please enter the KubeNow subdirectory:

cd KubeNow

and follow the instructions: http://kubenow.readthedocs.io/en/stable/getting_started/bootstrap.html#bootstrap-on-openstack (name your image kubenow-cloudportal-01).

# When you have a kubenow-v020a1 in your repo, step back to cloud-deploy directory
cd ..

# Now edit the test_env_vars... file

# Then 
source test_env_vars...sh

# Deploy (openstack)
cloud_portal/ostack/deploy.sh

# Status
cloud_portal/ostack/state.sh

Access services:

Destroy cluster:

# Destroy
cloud_portal/ostack/destroy.sh