MoltenCore by Stark & Wayne
This project should not be used for production systems as we still need to tackle:
- Backup & Restore
- Disaster Recovery
- Drain bosh instances on host shutdown
- Re-enable Container Linux Auto Updates
For more details about what we are planning for Phase 3 read the blog post.
Use one of the following terraform projects to deploy a MoltenCore Cluster:
- Packet MolteCore
- More to come
Once your cluster is deployed you can check on the status the embedded BUCC service.
MoltenCore nodes have expect to be given a unique zone index (via
This should be taken care of by the infrastructure specific terraform project
(by passing on
count.index). The zone index is used for naming the BOSH
availability zones (z0, z1, z2, etc).
The first node (z0) will host BUCC, and will be used for all management tasks.
But before we can interact with BUCC we need to make sure it is up and running.
bucc.service will be started by systemd on the node with the first
Once you have sshed into node z0 systemd can be used to check the status and the
progress of the
systemctl status bucc.service journalctl -f -u bucc.service
Make sure to locate your BUCC first (using the above paragraph), and make sure it is running. Now from node z0 you can start an interactive management shell with:
To find the Concourse login credentials run:
The following cli's have been pre-configured:
The bosh cli usage docs.
The credhub cli
credhub get -n /concourse/main/moltencore
The concourse cli, named fly
fly -t mc workers