Re: [openstack-dev] [Magnum]Cache docker images

_e...@yahoo.com] > Sent: Tuesday, April 19, 2016 7:20 PM > To: OpenStack Development Mailing List (not for usage questions) > Cc: Fox, Kevin M > Subject: Re: [openstack-dev] [Magnum]Cache docker images > > Kevin, > > I agree this is not ideal solution, but it's probably t

Re: [openstack-dev] [Magnum]Cache docker images

From: Adrian Otto [mailto:adrian.o...@rackspace.com] Sent: April-20-16 9:39 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Magnum]Cache docker images Hongbin, Both of approaches you suggested may only work for one binary format. If you try

Re: [openstack-dev] [Magnum]Cache docker images

To: OpenStack Development Mailing List (not for usage questions) Cc: Fox, Kevin M Subject: Re: [openstack-dev] [Magnum]Cache docker images Kevin, I agree this is not ideal solution, but it's probably the best option to deal with public cloud "stability" (e.g. we switched to the same mo

Re: [openstack-dev] [Magnum]Cache docker images

ct: Re: [openstack-dev] [Magnum]Cache docker images hi hello again I believe you are talking about this bp https://blueprints.launchpad.net/magnum/+spec/cache-docker-images then ignore my previous reply, that may another topic to solve network limited problem. I think you are on the right w

Re: [openstack-dev] [Magnum]Cache docker images

the prebundled stuff. how do you upgrade things when needed if there is no way to pull updated images from a central place? Thanks, Kevin From: Hongbin Lu [hongbin...@huawei.com] Sent: Tuesday, April 19, 2016 11:56 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [

Re: [openstack-dev] [Magnum]Cache docker images

To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Magnum]Cache docker images Eli, The approach of pre-pulling docker images has a problem. It only works for specific docker storage driver. In comparison, the tar file approach is portable across different

Re: [openstack-dev] [Magnum]Cache docker images

: Hongbin Lu [hongbin...@huawei.com] Sent: Tuesday, April 19, 2016 11:50 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Magnum]Cache docker images Yes, that is an alternative. The complication is how to secure the communication between Magnum bays

Re: [openstack-dev] [Magnum]Cache docker images

To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Magnum]Cache docker images hi hello again I believe you are talking about this bp https://blueprints.launchpad.net/magnum/+spec/cache-docker-images then ignore my previous reply, that may another topic to solve network limited problem

Re: [openstack-dev] [Magnum]Cache docker images

] Sent: April-19-16 1:12 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Magnum]Cache docker images why not just allow a prefix to be added to the container name? you can then have a container named: foo/mycontainer and the prefix could be set

Re: [openstack-dev] [Magnum]Cache docker images

why not just allow a prefix to be added to the container name? you can then have a container named: foo/mycontainer and the prefix could be set to mylocalserver.org:8080: mylocalserver.org:8080/foo/mycontainer Then if the site needs local only containers, they can set up a local repo. Be it a

Re: [openstack-dev] [Magnum]Cache docker images

hi hello again I believe you are talking about this bp https://blueprints.launchpad.net/magnum/+spec/cache-docker-images then ignore my previous reply, that may another topic to solve network limited problem. I think you are on the right way to build docker images but this image could only

Re: [openstack-dev] [Magnum]Cache docker images

@wanghua I think there were some discussion already , check https://blueprints.launchpad.net/magnum/+spec/support-private-registry and https://blueprints.launchpad.net/magnum/+spec/allow-user-softwareconfig On