Skip to content
Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Blacksmith, Bare-Metal CoreOS Cluster Manager

Travis widget wercker widget Quay widget Status

Blacksmith is a collection of DHCP, PXE, TFTP, and HTTP servers, created with the purpose of booting CoreOS on bare-metal machines, configuring them by serving generated cloud-config and ignition files, and maintaining the cluster over time. Blacksmith uses etcd to store the states, and to elect a leader. So you can run multiple instances of Blacksmith to provide a high available CoreOS over bare-metal infrastructure.

Warning: This project is under development. To be notified about the project becoming more stable, please subscribe to this issue.

Screenshot of Nodes List page - Blacksmith

Workspace and Templating

The cloud-config and ignition files, and the bootparams string which is passed to the kernel at boot time, are provided by executing templates for each machine. These templates, along with CoreOS images and other binary files, form the runtime environment of your cluster. In Blacksmith, we call this folder Workspace. For more information on the structure of a workspace, check the workspace doc.

Running in Docker

Blacksmith is available as a Docker image called cafebazaar/blacksmith.

Because Blacksmith needs to listen for DHCP traffic, it has to run with the host network stack. You can use to run blacksmith as a docker container. The script has made some assumptions to provide some of the required arguments of the blacksmith command. To customize it according to your network layout, currently you have to edit the script.

$ sudo ./ <workspace-path> <etcd-endpoints> <network-interface>


In some IaaS environments, machine names are resolvable in the internal network. Some software (Kubernetes?) count on it. To provide similar functionality, you need to run SkyDNS on the same instances you run Blacksmith on. Blacksmith will configure them through etcd.


Check this.


For test you can use our blacksmith-kubernetes workspace.

Cluster Setup

# Get the packages (ignore the warnings):
go get -v
go get -v

# Download the needed binaries of kubernetes workspace of blacksmith:
cd $GOPATH/src/

cd $GOPATH/src/
# Edit there and make it to suit your needs,
# If you happen to need a proxy config, you should edit the following lines:
# export CONTAINER_HTTP_PROXY=http://<your http proxy ip>:<port>
# export CONTAINER_HTTPS_PROXY=http://<your https proxy ip>:<port>
# Note: Referring localhost and won't work here, good idea
# would be to make your local proxy server to listen on and
# use your LAN IP here.
# You need to edit internal/external interface names to this:
# (or a real cluster scenario, according to your machines)

# put your ssh keys into the cluster
echo "  - $(cat ~/.ssh/" > ssh-keys.yaml

# Build workspace:

# Enter blacksmith
cd $GOPATH/src/
mkdir workspaces

# Initialize the cluster using VirtualBox

# On blacksmith-kubernetes, once machines reached "installed" state, (click
# you can terminate BoB (local instance of blacksmith that has provisioned
# master machines with blacksmith-kubernetes workspace)

# Once download of blacksmith container and its requironments finished which
# takes minutes of even hours, for poor Internet connections
# (login with IP of third interface of boostrapper1 with `ssh core@IP`
# and enter `journalctl -f` to check that) you can add 5 workers to your
# just created virtual cluster. 
./ worker 5

# Append this line to your /etc/hosts
# <bootstrapper1 ip address>  test.cafecluster
kubectl --kubeconfig $GOPATH/src/ get nodes