We advise to use the official release in the OpenSource Registry of Zalando. You can find out the latest here (pierone-cli must be installed):
DOCKER_BASE_IMAGE="registry.opensource.zalan.do/aruha/exhibitor-appliance" DOCKER_IMAGE_VERSION=$(pierone latest aruha exhibitor-appliance --url registry.opensource.zalan.do)"
If you want to build your own image see here: http://docs.stups.io/en/latest/user-guide/deployment.html#prepare-the-deployment-artifact
Create S3 bucket
S3_BUCKET="exhibitor-bucket" aws s3 mb s3://$S3_BUCKET
Register appliance in YOUR TURN
Make sure that your got an unique
Deploy with Senza
senza create exhibitor-appliance.yaml <STACK_VERSION> \ DockerBaseImage=$DOCKER_BASE_IMAGE \ DockerVersion=$DOCKER_IMAGE_VERSION \ HostedZone=<HOSTED_ZONE> \ ExhibitorBucket=$S3_BUCKET \ ApplicationID=<APPLICATION_ID> \ [--region AWS_REGION]
A real world example would be:
senza create exhibitor-appliance.yaml acid-exhibitor \ DockerBaseImage=registry.opensource.zalan.do/acid/exhibitor \ DockerVersion=3.4-p9 \ HostedZone=example.org. \ ExhibitorBucket=exhibitor-bucket \ ApplicationID=exhibitor \ --region eu-west-1
Cloudformation stack will start 3 EC2 instances in autoscaling group and create internal load balancer in front of EC2 instances. Also it will create DNS record
"<APPLICATION_ID>-<STACK_VERSION>.<HOSTED_ZONE>" which points to a load balancer.
Exhibitor provides rest-api which could be accessd via:
The provided Yaml file creates only a internal LoadBalancer. For security reasons you should not expose freely the exhibitor interface, since it has by default not authorization. For access you should look into this script: https://github.com/zalando-stups/ssh-tunnels