Tinkerbell

It is comprised of following five major components:

1. A DHCP server (boots)
2. A workflow engine (tink, this repository)
3. A metadata service (hegel)
4. An in-memory installation environment(osie)
5. A controller/handler of BMC interactions(pbnj)

The workflow engine is comprised of a server and a CLI, which communicates over gRPC. The CLI is used to create a workflow and its building blocks: templates and targeted hardware.

Packet Workflow

A Packet Workflow is an open-source microservice that’s responsible for handling flexible, bare metal provisioning workflows, that is...

• standalone and does not need the Packet API to function
• contains Boots, Tink, Hegel, OSIE, PBnJ and workers
• can bootstrap any remote worker using Boots + Hegel + OSIE + PBnJ
• can run any set of actions as Docker container runtimes
• receive, manipulate, and save runtime data

Content

• Setup
• Components
  • Boots
  • OSIE
  • PBnJ
  • Tink
  • Hegel
  • Database
  • Image Registry
• Architecture
• Say "Hello-World!" with a Workflow
• Concepts
  • Template
  • Provisioner
  • Worker
  • Ephemeral Data
• Writing a Workflow
• Tinkerbell CLI Reference
• Troubleshooting

Website

The Tinkerbell project is hosted at tinkerbell.org.