Initial implementation #1
Conversation
Dockerfile
Outdated
|
|
||
| # Add Containerpilot and set its configuration | ||
| ENV CONTAINERPILOT /etc/containerpilot.json5 | ||
| ENV CONTAINERPILOT_VERSION 3.3.3 |
There was a problem hiding this comment.
Thanks for calling that out, the majority of this Dockerfile was plundered from autopilotpattern/postgres but I hadn't gotten the change to review versions. Fixing this in the next commit.
| # Start with a single host which will bootstrap the cluster. | ||
| # In production we'll want to use an HA cluster. | ||
| consul: | ||
| image: autopilotpattern/consul:0.7.2-r0.8 |
There was a problem hiding this comment.
We've qualified Consul 1.0 support with the latest version of ContainerPilot and autopilotpattern/consul:1.0.0r43.
There was a problem hiding this comment.
This file has been neglected since I've been iterating on examples/compose/local-compose.yml while figuring stuff out.
I've actually been working against a locally built 1.0.0r47 that incorporates autopilotpattern/consul#46 and autopilotpattern/consul#47 in an effort to make this multi-DC capable from the start.
I will definitely revisit this file once local-compose.yml stabilizes
|
So far this looks like a great addition to the autopilot library. |
…e seeds lock at a time and all others will render their configs to include the seed node (even if it is still bootstrapping)
Replication is working. JMX monitoring was working before, but no longer (and is probably not in scope).
Backups to Manta might be in scope? Still studying https://docs.datastax.com/en/cassandra/3.0/cassandra/operations/opsBackupRestore.html