search

pandastrike / huxley

API and CLI for Docker Deployment
9 stars 1 forks source link

Move Deployment Specifics to Bash Script, not *.service files #73

Open freeformflow opened 9 years ago

freeformflow commented 9 years ago

In principle, nothing about our model is dependent on CoreOS. We need a set of instances and a management system to decide where to put containers once they are brought online. CoreOS is fine, but it's not the only system we could have used.

For each mixin, move the any deployment specifics to bash scripts that will live outside the .service file. We can then move to a single .service file that we just reuse.

PandaWhisperer commented 9 years ago

Not sure if relevant, but I just created a bash script for the kick server that sets a DNS name and waits for the changes to be synchronized before exiting: https://github.com/pandastrike/panda-kick/blob/master/examples/poll.sh

Is that what you're thinking of?

freeformflow commented 9 years ago

Actually, it's not a bad start. We'd like to look at the possibility of decoupling our model from CoreOS. We need job management on the cluster, but that doesn't have to be fleetctl. In principle, we could deploy a cluster of Arch instances and deploy containers if we had an adequate job manager.

This ticket is asking for us to move in that direction by moving functionality out of the *.service files. We will rely on them generically to trigger jobs, but we can put specifics into bash scripts, which are universal for Linux distributions.

freeformflow commented 9 years ago

This is more of a future goal. Maybe Alpha 05 or beyond. Right now, we can just focus on blowing out the features available to the user.