Priam

This feature is a first step toward enhancing to perform more management tasks for a cluster.

##Configuration
To flush specific keyspaces, create FP “Priam.flush.keyspaces” and provide a comma delimited list of values (e.g. pappyperftest,dse_system).

If no FP exist, all kespaces (EXCLUDING system) will be flushed.

To specify interval, create FP “Priam.flush.interval”. The value is a name=value where “name” is an enum of hour, daily.
*hour means the flush will run at every hour. The value is an integer representing the minute. E.g. hour=0 will run on the hour, every hour.
*aily means the flush will run once daily at specified time. The value is an integer representing the hour. E.g. daily=10 will run at 10:00 a.m. daily.

##Manually invocation
curl “http://localhost:8080/Priam/REST/v1/cassadmin/flush”.
The result will be a json payload.
*For success, the payload is a list of keyspace(s) flushed. E.g. {"keyspace_flushed":["dse_system","pappyperftest","system_traces"]}
*For failure, the payload will be {“status:ERROR”, “component:flush”}

Support the ability to query more than one ASG while looking for current RacMembership since one RAC(availability zone) members could span across different ASGs

• Added the feature of s3 role assumption while uploading backups, incremental etc.

Adding tombstone_warn_threshold, tombstone_failure_threshold and streaming_socket_timeout_in_ms YAML config options

This will provide support for fetching members from the same zone across multiple accounts which can be leveraged while migrating across accounts.

Determine status of a snapshot with following rest url:

Status check
curl "http://localhost:8080/Priam/REST/v1/backup/status/20160606" will return {"Snapshotstatus":false} or {"Snapshotstatus":true}

curl "http://localhost:8080/Priam/REST/v1/backup/status/20160606/snapshots" will return all snapshots for date of 20160607. E.g.
{"Snapshots":["201606060450","201606060504"]} or "Snapshots":[]}

NOTE: Priam snapshot status is not durable, it’s only in-memory. And we keep state of the last 60 days from current date.

Status check
curl "http://localhost:8080/Priam/REST/v1/backup/status/20160606" will return {"Snapshotstatus":false} or {"Snapshotstatus":true}

curl "http://localhost:8080/Priam/REST/v1/backup/status/20160606/snapshots" will return all snapshots for date of 20160607. E.g.
{"Snapshots":["201606060450","201606060504"]} or "Snapshots":[]}

NOTE: Priam snapshot status is not durable, it’s only in-memory. And we keep state of the last 60 days from current date.