Separate artifacts - Githubissues

PacketFire / gemini

Cluster container orchestration tool

Apache License 2.0

0 stars 0 forks source link

Separate artifacts #3

Closed RaasAhsan closed 5 years ago

RaasAhsan commented 5 years ago

There are going to be two artifacts:

Gemini master that is responsible for performing health checks, scheduling activity
Gemini node that is responsible for reporting status, running Docker containers

JosephMoniz commented 5 years ago

The alternative to consider is one artifact for both. Docker does this in the sense that the binary for the docker client is also the same binary for the docker daemon

RaasAhsan commented 5 years ago

Ahh, thats a good point. Can we achieve that with two different main files (e.g. we have gemini_node.py and gemini_master.py right now), or would it be a single main?

JosephMoniz commented 5 years ago

Probably a single main. Consul does this by making console agent a command of the console binary