Skip to content
The base Amazon Machine Image (AMI) allowing dockerized applications to run with STUPS
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
build
images
runtime
scripts
secret
tests
.gitignore
.travis.yml
.zappr.yaml
CONTRIBUTING.md
LICENSE
MAINTAINERS
README.md
config-stups-example.sh
create-ami.sh
run-tests.sh
share-ami.sh
test-batchdata.yaml
test-gpudata.yaml
test-userdata.yaml
test.sh
tox.ini
volume_testing.sh

README.md

Zalando AMI generation tooling

Build Status Join the chat at https://gitter.im/zalando-stups/taupage

NOTE

While we do not consider Taupage to have reached its end of life, we are currently not planning to add new features or extend its functionalities. We will consider any pull request, but we do not plan to directly work on enhancements.

Prerequisites

You need to have jq and AWS CLI preinstalled.

Build a new AMI

You need to be logged in (mai login). (As a configuration example, you can find the file config-stups-example.sh in the code base. You should modify it to suit it to your needs.)

$ ./create-ami.sh ./config-stups.sh <version>

This will spin up a new server, configure it, create an AMI from it, terminate the server and share the AMI. If you want to debug the server after setup, you can add a --dry-run flag: AMI generation, terminating and sharing will be skipped.

$ ./create-ami.sh --dry-run ./config-stups.sh

See the STUPS documentation for more information.

Directory structure

  • /build/ (scripts and files for the initial setup)
    • setup.d/ (all setup scripts that get executed on the server)
  • /runtime/ (everything, that has to be present during runtime)
  • /tests/ (contains various tests, such as python, serverspec and shell script tests)
You can’t perform that action at this time.