Open Stack

On 30/11/17 10:23 -0500, Dan Prince wrote:
>On Fri, Nov 17, 2017 at 4:43 AM, Steven Hardy <shardy at 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.

Agreed! The sooner we can move things out of "host paths" the better! Kubernetes
is not a requirement for these improvements but, I would say they are a
requirement for a k8s based deployment.

That is to say, a k8s based deployment should not depend on hostpaths :)

Flavio


--
@flaper87
Flavio Percoco
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 862 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171130/bd6bd0c4/attachment.sig>