These instructions explain how to install DataStax Enterprise on a set of Digital Ocean droplets. DataStax provides instructions for Installing on cloud providers, but currently only Amazon EC2 and HP Cloud are described specifically.
The steps below can be used for Digital Ocean, or more generally for any other cloud provider. We’ll create a set of Ubuntu droplets and install DataStax Enterprise (DSE) on them to create a Cassandra cluster.
Update: Scroll to the bottom for a video demo of these install steps.
These are the relevant DataStax documentation pages if you want to learn more details behind each step:
- Register for DataStax Enterprise (free, allows use of DataStax Enterprise in dev/test environments)
- An active Digital Ocean account (referral link if you don’t have an account yet)
Creating Digital Ocean Droplets
- Login to the Digital Ocean and navigate to the control panel
- On your local system create an SSH key and store it in the Digital Ocean control panel (help)
- On the control panel click Create with settings like:
- Hostname: node0
- Size: 4 GB / 2 CPU
- Region: default
- Image: Linux Ubuntu 14.04 64-bit
- SSH key: Select the one created previously
- Settings: default
- Repeat for node1, node2, etc. (as many nodes as desired)
- As the nodes are coming up make note of the IP addresses
Installing DataStax Enterprise
For a faster install, see Parallel Installs below.
- SSH into the first node
- Confirm whether Java is already installed (it may be, depending on the Linux image); if not, install either OpenJDK Java or Oracle Java
Add the DataStax repository using the username and password from your registration:
echo "deb http://username:firstname.lastname@example.org/enterprise stable main" | sudo tee -a /etc/apt/sources.list.d/datastax.sources.list
Add the DataStax repository key:
curl -L --silent https://debian.datastax.com/debian/repo_key | sudo apt-key add -
Update the local package cache:
sudo apt-get update
(if you see any “403 Not Authorized” errors here, stop and make sure your username and password are correct)
Install DataStax Enterprise:
sudo apt-get install dse-full
/etc/hosts and add an entry for the host with its public IP address (replacing the 127.0.1.1 entry if it exists)
/etc/dse/cassandra/cassandra.yaml and change a couple of settings:
cluster_name as desired
- In the
seeds field, list the IP address of node0 (the first server will be the seed for the cluster)
listen_address to blank
num_tokens to 256
Start the DSE service:
sudo service dse start
Repeat the above steps for the remaining nodes (node1, node2, etc.)
SSH to any of the nodes and check the status of the DSE cluster:
You can run the above install commands in parallel for a much faster setup time. On the Mac I use i2cssh which powers several iTerm2 consoles in parallel.
This technique is borrowed from Jake Luciani’s video How to set up a 4 node Cassandra cluster in under 2 minutes.
- Install i2cssh and iTerm2
Create a file
~/.i2csshrc with the server IP addresses. For example this file defines 3 servers included in a cluster named ‘digdemo’:
Launch parallel terminal sessions:
i2cssh -c digdemo
Enable broadcast mode in iTerm2 with Cmd-Opt-I
Type commands from the install procedure above; they should be echoed on all sessions in parallel
Twitter users should periodically review their application permission settings to clean out any old applications they have authorized. Over time these can pile up and it’s good to clean them out.
The steps are simple:
- Login to Twitter and navigate to the Application Settings page
- Review the list of applications and click Revoke Access for any you no longer need or don’t remember authorizing
Twitter App Permissions
In April I joined DataStax as a director of engineering on the DataStax Enterprise engineering team. I meant to post something here during my first week, but have been kind of busy since I started (understatement!). We sell an enterprise-class version of the open-source Cassandra database, along with service, support, and training. We also support the Cassandra community and the open-source project itself (the Apache Cassandra committee chair and many committers are all DataStax employees).
My first five week have been both busy and exciting. Here are some observations and highlights so far:
- It’s great to work for a smaller company once again – everyone is very motivated and focused on the mission, and it’s a very small circle of decision-makers.
- I’ve worked for companies with remote workers before (especially Citrix), but here we take it to a whole new level. We just call it a “distributed” workforce. In particular the engineering team is spread literally around the world. Many of our job postings list the location as “Anywhere, World” which is quite appropriate.
- We really like using SaaS based products, and have hardly any “infrastructure” hardware/servers of our own (just a few systems for Engineering & QA). Everything else is “in the cloud”.
- I’ve had a big learning curve on distributed NoSQL databases in general, Cassandra, and all of the DataStax products.
DataStax is really growing quickly and we’re looking for strong people in a variety of areas. Check out the DataStax Careers page for current openings and let me know if I can help make a referral for you.
In particular these are some key open positions in my group:
- Driver & Tools Engineer
- Java Engineer
- Software Engineer in Test
This Jobvite link will take you to the details page for those 3 positions.
From the Twilio Customer Stories page I learned about Remind101, a free service designed for teachers to keep students and parents up to date via text messaging or email. From their website you can learn more about the service, or about the team.
This is a very useful service. While it was primarily designed for classrooms, it could also be used for sports teams or anywhere else you need a 1:Many text messaging system.
Remind101 designed their system to be very focused for this type of communication. By keeping with a narrow focus, they’ve got a strong set of features like:
- Privacy – no one participating (teacher, student, parent) has anyone else’s phone numbers; this would be very important for younger kids in particular
- Only Group Messaging – there is no support for 1:1 messages; instead everything is sent to the entire group/class
- One-way Messaging – students and parents cannot reply to any teacher message; I would like to see the ability to reply as well, in order to make it a better communication channel for the students back to the teacher
- Mobile Apps – for the teacher side, they have apps for both Android and iOS
- Email – as an alternative to text messaging, students/parents can receive messages via email
As a sport coach or manager, you could set up individual teams (“classes”), and connect with each of your teams separately as needed. For example, “16U Red”, “16U White”, and so on. This app could be used for a whole season, or just for a tournement weekend. (Just delete the group when the weekend is over.)
Here’s a screenshot of the web interface for sending a message:
Using Remind101 to send text messages to a sports team
I successfully migrated this website from MovableType 4.35 to WordPress 3.8.1. These are my notes from the migration in case they are helpful for anyone else. The good news is this is pretty straightforward, and there are plenty of notes out there (just search the internet for “WordPress MovableType import”). The tricky parts are the custom or special areas of your MovableType installation, and mine was no exception.
First, why switch to WordPress? I wanted something more current with a stronger platform of plugins and themes. I’ve been happy with MovableType and stuck through it over many versions and changes. It just started to look and feel a bit dated and it was time for something new. WordPress isn’t exactly “new” (having just passed its 10-year anniversary), but it continues to evolve and improve. I’ve also used it for a couple of sports team websites which turned out well.
As part of any migration , you need to identify the aspects of your site which are customized, unique, or which will potentially cause problems. In my case I had the following to deal with:
- About 600 posts dating back 12 years
- Individual post links were based on year/month/day, a custom slug name (saved in the Keywords field), and no extension; for example: http://www.cantoni.org/2013/12/05/tech-advent-calendars-2013
- Posts written in different markup (plain text, HTML, Textile and Markdown)
- Comments (which I did not migrate)
- Categories, but no tags
- Three different syntax-highlighting scripts/styles used over the years
These were the migration steps to import MovableType into WordPress:
- Installed WordPress
- Installed movabletype-importer plugin and activate it
- Configured the timezone and permalink settings (permalink matching what I used for MovableType)
- In MovableType modified
ImportExport.pm to omit comments and tags, and set the proper basename for posts (gist)
- Performed the export of all entries to a text file
- Converted Textile and Markdown to HTML markup (gist, original script from Mark Shroyer)
- Imported into WordPress
- Moved old static directories (./2014, ./2013, etc.) so that WordPress would start serving those pages
- Installed wp-markdown plugin, activate it, and enable for posts and pages
I also found the suicide plugin very helpful as I iterated on the steps above. You can erase all posts and metadata in a single step. Make sure to remove after your migration is complete!
After everything was migrated and permalinks working correctly, I finished the initial setup:
- Installed disable-comments, activate it, and disable all comments site-wide
.htaccess to redirect from old
rss.xml to new feed link
.htaccess to redirect from old category pages to new links
- Updated FeedBurner to use new feed link
- Installed google-analytics-for-wordpress, activate it, and configure my ID number
- Configured twenty-thirteen theme with a child theme, a few custom header images, and the sidebar widgets
Still on my to-do list:
- Finish bringing over any static pages that are still useful
- Fix syntax highlighting and consolidate to a single solution
- Monitor Google Webmaster Tools for any crawler errors (page not found)
- Clean up links to comment feeds (and other extra junk in HTML head)
- Add more redirects from old archives pages where needed