Running DataStax Community AMI on EBS-backed EC2 instance

(3 posts) (2 voices)

• Started 1 year ago by
• Latest reply from joaquin
• This topic is not resolved

Tags:

No tags yet.

1. 

   Anonymous
   Unregistered

   Hello,

   Sorry for a somewhat duplicate posting - I see you've answered this elsewhere on the forums. But I'd like to run an instance of Cassandra on an EBS-backed EC2 instance. This is for development purposes and we'd like to be able to turn on/off the instance in order to save money (we only need it to run during office hours [~200 hours/month]).

   I've been able to use the existing DataStax AMI's successfully (thanks!), but I'd like to create a new instance which is EBS-backed. I understand the various caveats regarding performance and potential reliability, but - again - these are just Developer instances.

   Reading the other posts (http://www.datastax.com/dev/blog/personalizing-your-own-brisk-ami) on this subject, I see that a critical link to some command line scripts is no longer valid: https://github.com/riptano/BriskClusterAMI/blob/master/.presetup/pre-setup.sh. This returns a 404 error.

   Can you update any documentation (or forward any other applicable postings) on how to do this? I'm a Lunix and EC2 newbie (I'm a .NET developer by history [gasp!]), so any "dumbing-down" would be appreciated.

   Thanking you in advance,

   Chris Dodge

   Posted 1 year ago #
2. 

   joaquin
   Administrator

   Hi Chris,

   No worries. I'll respond in both places.

   The new scripts are located here: https://github.com/riptano/ComboAMI/tree/2.2/presetup.

   There are now two scripts: pre_1.sh and pre_2.sh. Copy and paste pre_1.sh into your console and pre_2.sh will come through automatically.

   You will also probably want to fork the project for adding the EBS features. Then you'll modify pre_1.sh to get your git fork. Everything else should be left the same, except for ds1_launcher.py. You will need to modify ds1 to have methods like ds2 to calculate and edit your conf with the appropriate seeds. This is important since ds2 only runs once and will delete itself.

   This should give you a full overview of what happens:
   https://github.com/riptano/ComboAMI/blob/2.2/FILES.md

   Hope this helps!
   Joaquin

   Posted 1 year ago #
3. 

   joaquin
   Administrator

   After looking at it a bit more, you will also need to modify your listen_address along with your seeds.

   It may be best to perhaps not have ds2 delete itself and run something like:
   if conf.get_config("AMI", "CurrentStatus") != "Complete!":
   # Run ds2
   else:
   # Else run ds2_ebs.run()

   Where ds2_ebs.py performs a subset of ds2_configure.py's commands (like getting ec2 data, getting the seeds and setting up the confs.)

   Hope this helps even further!
   Joaquin

   Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.