Hello, I'm glad to hear you want to develop the AMI further!
All of the source code for this version of the AMI is currently here: https://github.com/riptano/TempBrisk.
You can look at my projects as this will github project will be killed very soon in the near future and we will have a new address for it.
Why would you want to use EBS instances over Instance Stores? Instances Stores have better performance and are more reliable without random lag times making them better for production use and benchmarking. If there is a not a strict reason, then you can just use this script to create your own S3 backed AMI:
sudo mv *.pem /mnt
sudo su
cd
curl http://s3.amazonaws.com/ec2-downloads/ec2-ami-tools.zip > ec2-ami-tools.zip
mkdir ec2
cp ec2-ami-tools.zip ec2
cd ec2
unzip ec2-ami-tools.zip
ln -s ec2-ami-tools-* current
sudo cat >> ~/.bashrc << EOF
export EC2_AMITOOL_HOME=~/ec2/current
export PATH=${PATH}:~/ec2/current/bin
EOF
source ~/.bashrc
ec2-bundle-vol --help
VERSION=$(head -1 /home/ubuntu/.presetup/VERSION)
rm -rf ~/.bash_history && history -c && ec2-bundle-vol -p brisk_1.0_beta1-ami_$VERSION -d /mnt -k /mnt/pk-xxxxxxx.pem -c /mnt/cert-xxxxxxx.pem -u xxxxx -r x86_64
yes | ec2-upload-bundle -b datastax-brisk-cluster-ami-use -m /mnt/brisk_1.0_beta1-ami_$VERSION.manifest.xml -a xxxxxxx -s xxxxxxx --location US
echo """
cd ~/.ec2/
ec2-register datastax-brisk-cluster-ami-use/brisk_1.0_beta1-ami_$VERSION.manifest.xml --region us-east-1 -n 'DataStax Brisk 1.0 Beta-1 Cluster - AMI $VERSION' -d 'Provides a way to automatically launch a Brisk cluster by simply starting the instance.'
ec2-register datastax-brisk-cluster-ami-usw/brisk_1.0_beta1-ami_$VERSION.manifest.xml --region us-west-1 -n 'DataStax Brisk 1.0 Beta-1 Cluster - AMI $VERSION' -d 'Provides a way to automatically launch a Brisk cluster by simply starting the instance.'
ec2-register datastax-brisk-cluster-ami-eu/brisk_1.0_beta1-ami_$VERSION.manifest.xml --region eu-west-1 -n 'DataStax Brisk 1.0 Beta-1 Cluster - AMI $VERSION' -d 'Provides a way to automatically launch a Brisk cluster by simply starting the instance.'
ec2-register datastax-brisk-cluster-ami-aps/brisk_1.0_beta1-ami_$VERSION.manifest.xml --region ap-southeast-1 -n 'DataStax Brisk 1.0 Beta-1 Cluster - AMI $VERSION' -d 'Provides a way to automatically launch a Brisk cluster by simply starting the instance.'
ec2-register datastax-brisk-cluster-ami-apn/brisk_1.0_beta1-ami_$VERSION.manifest.xml --region ap-northeast-1 -n 'DataStax Brisk 1.0 Beta-1 Cluster - AMI $VERSION' -d 'Provides a way to automatically launch a Brisk cluster by simply starting the instance.'
ec2-modify-image-attribute -l --region us-east-1 -a EMPLOYEEAWSID \$(ec2-describe-images --region us-east-1 | grep 'DataStax Brisk 1.0 Beta-1 Cluster - AMI $VERSION' | cut -f2)
""" && rm -rf ~/.bash_history && history -c
That's the exact same code, minus a few changes, that I use to build the image. You would then copy the output of the echo into your computer where you have the ec2-tools installed, and register the AMI and open permissions. This entire step takes 20 minutes minimum, but 30 on a relaxed schedule. (There is a bit of waiting.)
For both EBS backed instances and Instance-Stores you setup the image by:
copy/pasting pre-setup.sh
That will run the entire install process, then you would just create the backup via the normal EBS way. On boot, you will have all of your settings and configurations occur. However, if using the EBS volumes and this exact same source code, you're not guaranteed to be able to reconnect if the cluster was shut down then started back up.
I was planning on doing a writeup soon on how exactly to branch off the code and since you've shown interest, I'll definitely try to make it sooner than later.
Sorry if the code isn't as easy to follow, I've made quite a few changes to it soon, but really the bulk of your coding should occur in .configurebrisk and the .pre-setup folder.
If you wish to start playing with the code feel free to start getting ideas. My next version will cleanup the .files and compile that all into a config file. If you wish, send me an email with your AWSID and I'll add you to this exact versions beta so you can see the new dev features.
Sorry this was all done over the forum format, but I'll be sure to have something cleaner sooner, than later.
Thanks again for showing interest in the AMI and let me know if you want any small changes or software added to the official project. I'd be more than happy in making this product better for everyone!
