For the CS 320 Class at UMass
If the Vagrantfile has been changed since you last ran vagrant up, you should run:
vagrant destroy
The first step is to get the Vagrant virtual machine running. This command will start the Vagrant machine which is configured to be a Cassandra node:
vagrant up
Make sure you have go installed on your machine.
Clone this repository into your Go path. The repository should end up in $GOPATH/src/ratdevelopment.
To get Go package dependencies for the branch you are on run:
go get
After the vagrant machine starts up to run all the tests for the repository, run:
go test ./...
Optionally add -bench . or -bench=. to run the benchmarking tests, or add -v for verbose output, such as:
go test ./... -v -bench .
To compile the local go server run:
go build
To start the local go server after you have compiled run:
go run ratdevelopment
A permission dialog might also pop up, make sure to allow ratdevelopment to access the network.
go run ratdevelopment
On Unix, permissions are normally not needed to access the network.
Make sure you set your line endings properly in git:
git confit core.autocrlf "input"
The Vagrantfile in the repo currently starts a Cassandra node on 10.10.10.31 by default.
If you wish to use cqlsh or other command line tools like nodetool to interact directly with the cassandra instance, use:
vagrant ssh
Cassandra should typically start when your machine starts But if it isnt running, just use the following to start it
service cassandra start
Alternatively, to stop Cassandra use
service cassandra stop
When cassandra is running, use the following to get into the cluster to start messing around with things Do note that you cant use GoCQL to mess with the schema at all, that has to be done through cqlsh
cqlsh 10.10.10.31
This script should be run by vagrant up,
but if it isn't then be sure to vagrant ssh into the virtual machine and run
/vagrant/scripts/migrate.sh 10.10.10.31
which will run the cql in schema.cql on your local cassandra database.
Build and run this, on your host computer, passing in the directory containing the data dump, to load the data dump into cassandra.
go build .\scripts\mouse_upload
mouse_upload.exe <directory_containing_data_dumps>
This section is left for posterity
First your going to have to create is a keyspace I'm going to recommend the following:
CREATE KEYSPACE IF NOT EXISTS keyspace_name WITH replication = {'class': 'SimpleStrategy', 'replication_factor': 1};
replication_factor refers to the number of replicas of data kept on multiple nodes. Make sure this never exceeds your node count, or all operations will fail. (required for SimpleStrategy) Class refers to the replication strategy used, two main types: SimpleStrategy - all node clusters will use the same replication factor NetworkTopologyStrategy - allows you to set the replication factor on a per data center basis (also has some other quirks involving physical location of the nodes)
NetworkTopologyStrategy is typically recommended (easier when expanding in the future), but for the purposes of cassandra on our local machines it wont really matter so its easier to just use SimpleStrategy
Next, need to create a table. It uses the following format
CREATE TABLE IF NOT EXISTS keyspace_name.table_name (
field_name_one datatype,
field_name_two datatype,
field_name_three datatype,
...,
PRIMARY KEY ((field_name_one), field_name_three)
) WITH CLUSTERING ORDER BY (field_name_three DESC);
Now you should be ready to enter data (using GoCQL too) Basic CQL Command formats:
INSERT INTO table_name (field_name_one, field_name_two) VALUES (data_one, data_two);
SELECT * FROM keyspace_name.table_name WHERE primary_key = 'some_value' AND (other key/value relations);
UPDATE table_name SET field_name_one = 'new_data' WHERE primary_key = 'some_value';
DELETE FROM table_name WHERE (some relations);
Refer to http://cassandra.apache.org/doc/latest/cql/dml.html to go more in depth into CQL
Use the following from within cqlsh to see all of your clusters...
SELECT cluster_name, listen_address FROM system.local;
To clear all data from a table, use:
TRUNCATE TABLE keyspace.table_name;
| HTTP Request | Inputs | Outputs |
|---|---|---|
/api/tenants/{tenant}/snapshots |
tenant | Comma Delimited JSON |
/api/tenants/{tenant}/systems/{serNum}/snapshots/{time} |
tenant, time (RFC1123), serNum | Single JSON |
/api/tenants/{tenant}/systems/{serNum}/timestamps |
tenant, serialNumber | Plain-text array of RFC1123 timestamps |
/api/tenants/{tenant}/systems |
tenant | Plain-text array of serial number strings |
/api/tenants |
None | JSON with a key of "tenants" and value of the set of all tenants, expressed as an array |
/api/tenants/{tenant} |
tenant | JSON with keys and values describing the name of the tenant, number of systems, and snapshot count |
/api/teapot |
None | Just says I am a teapot! Have some tea! :). It also ensures total security, usability, and scalability of our microservice, and must not be removed. |
a properly formatted HTTP request will look like /api/tenants/hpe/systems/9996788/timestamps
The output of /api/tenants/{tenant}/systems/{serNum}/timestamps should be used to populate the time field for /api/tenants/{tenant}/systems/{serNum}/snapshots/{time}
If you get this error when doing go run ratdevelopment:
2018/12/07 22:22:12 gocql: unable to dial control conn 10.10.10.31: dial tcp 10.10.10.31:9042: i/o timeout
2018/12/07 22:22:12 gocql: unable to create session: control: unable to connect to initial hosts: dial tcp 10.10.10.31:9042: i/o timeout
exit status 1
This means you have either not started cassandra, need to restart cassandra, or need to change how you run ratdevelopment.
The steps to check whether or not cassandra are working correctly, and to start / restart may vary per operating system.
If you are not using Vagrant, then most likely you will need to start ratdevelopment like this:
go run ratdevelopment --cassandra_ips 127.0.0.1
Or:
go run ratdevelopment --cassandra_ips localhost