internal_setup.md

Microcloud internal setup

To run microcloud, you need following dependencies

• Microcloud node with broker
• IaaS/hypervisor providers and associated services
• Hostnode binary toolchain distribution
• EC2 setup - security groups, AMIs

EC2 Setup

Existing AMIs:

• eu-west-1: ami-19eeea6d
• ap-southeast-1: ami-2a430278
• us_east-1: NA

LXC/Ubuntu Hostnode toolchain distribution is done via S3 (origin is bucket tenxlabs-dev)

---

To setup AWS account/individual region you need to

• create security zone tenxlab_node - allow access to ports 22, 80, 443, 8080, 8443
• export AWS_ACCESS_KEY_ID=xxx
• export AWS_SECRET_ACCESS_KEY=...
• run cd ami_builder && bundle install && bundle exec ./ami_builder.rb region_name key_to_use
• wait for instance to terminate / AMI to get become available
• remove instance and it's backing EBS

Hostnode distribution

Hostnode distribution is compiled using ./hostnode-dist.sh. To run it you need to have s3cmd configured to access appropriate buckets (see TARGET).

TODO Use CloudFront and it's Signed URLs to serve private content for unified distribution.

TODO due to issues with s3cmd in APAC regions binary setup is pretty much manual.