Richard Wall

Pilot executes `cassandra` directly, bypassing the container image entry point

2

* Cassandra Pilot now executes `cassandra` directly, bypassing the Docker image entrypoint * Added a configuration API with which to override configuration values in yaml and properties config files. *...

Standalone API server with integration tests

2

* Tried to separate out the API server options that require kubernetes API configuration options. * Don't apply those command line options if `--standalone-mode` has been supplied. * Added a...

Add a Cassandra upgrade mechanism

1

* Add a NodePool.Status.Version attribute which has the lowest reported version from all the pilots in the pool. * Or nil, if the pilot failed to query its Cassandra database...

Feed the stdout and stderr of the Pilot subprocess into glog

12

Fixes: #166 **Release note**: ```release-note NONE ```

WIP: Add a Cassandra Demo

3

**Release note**: ```release-note NONE ```

Trying to run the navigator API server locally but found that even with the `--standalone-mode` flag, it still requires Kubernetes API host, port and token. ``` ./navigator-apiserver_linux_amd64 --etcd-servers http://127.0.0.1:38501 --standalone-mode...

In https://github.com/jetstack/navigator/pull/244#discussion_r170941157 @kragniz asked: > should this now be marked +optional? I'm not sure. Perhaps we should: * Check that our APIs are fully and consistently documented. * Maybe add...

* https://github.com/apache/cassandra-dtest > Cassandra Distributed Tests (or better known as "DTests") are a set of Python-based tests for Apache Cassandra clusters. DTests aim to test functionality that requires multiple Cassandra...

Spurious test failure: Data was not replicated to second node

1

https://jetstack-build-infra.appspot.com/build/jetstack-logs/pr-logs/pull/jetstack_navigator/336/navigator-e2e-v1-9/722/ ``` W0427 14:56:41.930] + retry stdout_matches testvalue1 cql_connect test-cassandra-1524840199-15915 cass-test-nodes 9042 --debug '--execute=CONSISTENCY ALL; SELECT * FROM space1.testtable1' W0427 14:56:41.930] + local TIMEOUT=60 W0427 14:56:41.930] + local SLEEP=10 W0427...

There ought to be some tests for the cluster pausing feature introduced in #301 Otherwise we might not notice if the feature stops working. See https://github.com/jetstack/navigator/pull/301#pullrequestreview-118692694 /kind bug