| 2017-05-29 10:37:33 |
Bogdan Dobrelya |
bug |
|
|
added bug |
| 2017-05-29 10:37:49 |
Bogdan Dobrelya |
tripleo: importance |
Undecided |
High |
|
| 2017-05-29 10:37:52 |
Bogdan Dobrelya |
tripleo: milestone |
|
pike-2 |
|
| 2017-05-29 10:38:15 |
Bogdan Dobrelya |
description |
Like k8s provides for apps imagePullPolicy https://kubernetes.io/docs/concepts/containers/images/ , we need to make services configurable to pull (or not) its docker images on startup.
Related docker (moby) issue https://github.com/moby/moby/issues/13331 blocks us with managing this runtime for docker daemon. So runtime policy seems can't be implemented w/o COEs like k8s.
But at least we could implement this for deployments configuration management steps, with heat docker agent hooks and templating wanted imagePullPolicy for t-h-t. |
Like k8s provides for apps imagePullPolicy https://kubernetes.io/docs/concepts/containers/images/ , we need to make services configurable to pull (or not) its docker images on startup.
Related docker (moby) issue https://github.com/moby/moby/issues/13331 blocks us with managing this runtime for docker daemon. So runtime policy seems can't be implemented w/o COEs like k8s.
But at least we could implement this for deployments configuration management steps, with heat docker agent hooks and templating wanted imagePullPolicy for t-h-t.
This impacts in-place upgrade/update stories for containerized services |
|
| 2017-05-29 10:38:22 |
Bogdan Dobrelya |
tags |
|
containers upgrade |
|
| 2017-05-29 10:38:29 |
Bogdan Dobrelya |
tripleo: status |
New |
Triaged |
|
| 2017-05-29 10:41:35 |
Bogdan Dobrelya |
description |
Like k8s provides for apps imagePullPolicy https://kubernetes.io/docs/concepts/containers/images/ , we need to make services configurable to pull (or not) its docker images on startup.
Related docker (moby) issue https://github.com/moby/moby/issues/13331 blocks us with managing this runtime for docker daemon. So runtime policy seems can't be implemented w/o COEs like k8s.
But at least we could implement this for deployments configuration management steps, with heat docker agent hooks and templating wanted imagePullPolicy for t-h-t.
This impacts in-place upgrade/update stories for containerized services |
Like k8s provides for apps imagePullPolicy https://kubernetes.io/docs/concepts/containers/images/ , we need to make services configurable to pull (or not) its docker images on startup.
Related docker (moby) issue https://github.com/moby/moby/issues/13331 blocks us with managing this runtime for docker daemon. So runtime policy seems can't be implemented w/o COEs like k8s.
But at least we could implement this for deployments configuration management steps, with heat docker agent hooks or t-h-t host prep steps to ensure the wanted policy for services, then templating the imagePullPolicy for t-h-t services.
This impacts in-place upgrade/update stories for containerized services |
|
| 2017-05-29 14:14:45 |
Bogdan Dobrelya |
bug |
|
|
added subscriber Steven Hardy |
| 2017-06-07 11:42:39 |
Bogdan Dobrelya |
tripleo: status |
Triaged |
Won't Fix |
|
