Deploying tmpnb nodes
Python Shell
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
roles
script
.gitignore
.travis.yml
README.md
ansible.cfg
inventory.example
inventory.redirector
site.yml
statuspage-nature-env
statuspage-tmpnb-env
update.yml
vars.yml

README.md

tmpnb deployment

This repository contains an Ansible playbook for launching assets to *.tmpnb.org.

Single tmpnb setup is currently:

  • nginx on one server for SSL termination, has a DNS record associated
  • tmpnb on another server

Outside of those, we use the tmpnb-redirector to redirect to these nodes.

This is also set up for our own use, which means it may not work well for your own deployment (until we abstract it a bit further).

Launching with Ansible

"Easy" mode

source ./novarc
./script/new-instance <N>

This will:

  • allocate new servers (./script/launch.py)
  • add them to the redirector (./script/add-redirect)
  • deploy tmpnb (./script/deploy)

Updating images on a running instance

 ./script/image-update <N>

Status page

The status page daemon for tmpnb availability is run on the tmpnb-status carina cluster.

You will need to get the API key from statuspage.io, and create statuspage-env with:

STATUS_PAGE_API_KEY=<the-api-key>

Run:

eval $(carina env tmpnb-status)
./script/launch-statuspage

To launch the statuspage daemons.