On Fri, Nov 17, 2017 at 4:43 AM, Steven Hardy <sha...@redhat.com> wrote: > > > In the ansible/kubernetes model, it could work like: > > 1. Ansible role makes k8s API call creating pod with multiple containers > 2. Pod starts temporary container that runs puppet, config files > written out to shared volume > 3. Service container starts, config consumed from shared volume > 4. Optionally run temporary bootstrapping container inside pod > > This sort of pattern is documented here: > > https://kubernetes.io/docs/tasks/access-application-cluster/communicate- > containers-same-pod-shared-volume/ > > > Regarding the use of the shared volume I agree this is a nice iteration. We considered using it within Pike as well but due to the Hybrid nature of the deployment, and the desire to have config files easily debug friendly on the host itself we ended up not going there.
In Queens however we are aiming for more or less full containerization so we could consider the merits of this approach again. Just pointing out that I don't think Kubernetes is a requirement in order to be able to proceed with some of this improvement. Dan
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
