|Trevor Slocum 10efc654b3||4 weeks ago|
|cmd||4 weeks ago|
|LICENSE||2 months ago|
|README.md||1 month ago|
|client.go||2 months ago|
|database.go||1 month ago|
|deployment.go||4 weeks ago|
|go.mod||1 month ago|
|go.sum||1 month ago|
|result.go||2 months ago|
|server.go||4 weeks ago|
|task.go||1 month ago|
|util.go||1 month ago|
|worker.go||4 weeks ago|
Beehive - Simple container orchestration system
Notice: This software is not ready for use in production environments. Here be dragons.
A single queen bee (master node) manages any number of worker bees (worker nodes).
Tasks/jobs are currently submitted by inserting directly into the database the queen bee is connected to. An API for manipulating tasks is planned to be added.
Worker bees communicate only with the queen bee. They perform tasks as instructed by the queen bee and do not have a database of their own. All metadata that allows worker bees to track deployments is stored within the files of each deployment.
Containers are managed by Docker Compose. Beehive copies and interpolates deployment files while Docker Compose takes care of the rest.
Beehive deployment packages are called festoons. They always include a
Docker Compose file
defining at least one service. If a
data directory is present, it is copied to
each target deployment directory.
Example festoons are available here.
Please share issues and suggestions here.