separate ansible playbooks from vagrant deployment about halcyon-kubernetes HOT 4 CLOSED

I can start on the vagrant/ansible split.

from halcyon-kubernetes.

How do you see things like the README and the release notes getting split up? E.g.,

1. have halcyon-*-kube refer back to the main project for the good stuff
2. keep halcyon-kubernetes a skinny dependency w.r.t. docs
3. treat the three as separate projects, and divide up the docs
4. duplicate documentation
   ?

from halcyon-kubernetes.

That would be great! The split would be to just provide the ansible playbook into a single git repository. @aric49 can help with this, if you want/need. Then the Vagrant pieces would use the new Ansible playbook repository as a git submodule. The Docs would be drafted separately for the Vagrant dependancies (config.rb, Vagrantfile) written specifically for Vagrant, and the Ansible playbook would only cover how to run, and variable items in group_vars/all.yml (variable definitions).

from halcyon-kubernetes.

completed. closing issue.

from halcyon-kubernetes.