Re: [openstack-dev] [tripleO] appropriate location for docker image uploading

2015-11-05 Thread Brad P. Crochet
On Tue, Nov 3, 2015 at 2:54 PM, Jeff Peeler  wrote:
> I'm looking at introducing the ability for tripleoclient to upload
> docker images into a docker registry (planning for it to be installed
> in the undercloud [1]). I wanted to make sure something like this
> would be accepted or get suggestions on an alternate approach.
> Ultimately may end up looking something like the patch below, which
> I'm still waiting for further feedback on:
> https://review.openstack.org/#/c/239090/
>
>
> [1] https://review.openstack.org/#/c/238238/

Rather than continue on that code path, I would rather see the image
loading be done in tripleo-common similarly to the load-images script
in tripleo-incubator. The image building is already implemented [1],
but not yet merged. We want the yaml to drive the build/load, rather
than hard-code how we handle the images.

[1] https://review.openstack.org/#/c/235569/

-- 
Brad P. Crochet, RHCA, RHCE, RHCVA, RHCDS
Principal Software Engineer
(c) 704.236.9385 (w) 919.301.3231

__
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


Re: [openstack-dev] [tripleO] appropriate location for docker image uploading

2015-11-03 Thread Clint Byrum
Excerpts from Jeff Peeler's message of 2015-11-03 11:54:24 -0800:
> I'm looking at introducing the ability for tripleoclient to upload
> docker images into a docker registry (planning for it to be installed
> in the undercloud [1]). I wanted to make sure something like this
> would be accepted or get suggestions on an alternate approach.
> Ultimately may end up looking something like the patch below, which
> I'm still waiting for further feedback on:
> https://review.openstack.org/#/c/239090/
> 

I'm curious if you could push toward just using Magnum for this, which
would give you all of the power of the k8s registry, for instance.

> 
> [1] https://review.openstack.org/#/c/238238/
> 

__
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