Skip to content
forked from tinkerbell/tink

A workflow engine for provisioning bare metal.

License

Notifications You must be signed in to change notification settings

packethost/tink

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Tinkerbell

Build Status codecov

This repository is Experimental meaning that it's based on untested ideas or techniques and not yet established or finalized or involves a radically new and innovative style! This means that support is best effort (at best!) and we strongly encourage you to NOT use this in production.

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.

Workflow

A workflow is a framework responsible for handling flexible, bare metal provisioning, 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

Website

For complete documentation, please visit the Tinkerbell project hosted at tinkerbell.org.

About

A workflow engine for provisioning bare metal.

Topics

Resources

License

Code of conduct

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Go 91.8%
  • Shell 7.2%
  • Other 1.0%