tslocum
/
beehive
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Simple container orchestration system
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
9 Commits
2 Branches
0 Tags
89 KiB
Go 100%
 
main
wip
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'main'
${ noResults }
Go to file
Trevor Slocum 10efc654b3 Reconnect automatically to queen bee 4 weeks ago
cmd Reconnect automatically to queen bee 4 weeks ago
LICENSE Initial commit 2 months ago
README.md Update README 1 month ago
client.go Subscribe to container events 2 months ago
database.go Add initial database framework 1 month ago
deployment.go Reconnect automatically to queen bee 4 weeks ago
go.mod Add initial database framework 1 month ago
go.sum Add initial database framework 1 month ago
result.go Subscribe to container events 2 months ago
server.go Reconnect automatically to queen bee 4 weeks ago
task.go Add initial database framework 1 month ago
util.go Handle worker restarts without stopping deployments 1 month ago
worker.go Reconnect automatically to queen bee 4 weeks ago

README.md

Beehive - Simple container orchestration system

Donate via LiberaPay Donate via Patreon

Notice: This software is not ready for use in production environments. Here be dragons.

Design

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.

Festoons

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.

Support

Please share issues and suggestions here.