If the ops are deploying a cloud big enough to run into that problem, I think they can deploy a scaled out docker registry of some kind too, that the images can point to? Last I looked, it didn't seem very difficult. The native docker registry has ceph support now, so if your running ceph for the backend, you can put an instance on each controller and have it stateless I think.
Either way you would be hammering some storage service. Either glance or docker registry. Thanks, Kevin ________________________________ From: Guz Egor [guz_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 the best option to deal with public cloud "stability" (e.g. we switched to the same model at AWS and got really good boost in provisioning time and reduce # failures during cluster provisioning). And if application need guarantee "fresh" image, it uses force pull option in Marathon. --- Egor ________________________________ From: "Fox, Kevin M" <kevin....@pnnl.gov> To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Sent: Tuesday, April 19, 2016 1:04 PM Subject: Re: [openstack-dev] [Magnum]Cache docker images I'm kind of uncomfortable as an op with 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: [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 storage drivers. Best regards, Hongbin From: taget [mailto:qiaoliy...@gmail.com] Sent: April-19-16 4:26 AM 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. I think you are on the right way to build docker images but this image could only bootstrap by cloud-init, without cloud-init the container image tar file are not loaded at all, but seems this may not be the best way. I'v suggest that may be the best way is we pull docker images while building atomic-image. Per my understanding, the image build process is we mount the image to read/write mode to some tmp directory and chroot to to that dircetory, we can do some custome operation there. I can do a try on the build progress(guess rpm-ostree should support some hook scripts) On 2016年04月19日 11:41, Eli Qiao wrote: @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 2016年04月19日 10:57, 王华 wrote: Hi all, We want to eliminate pulling docker images over the Internet on bay provisioning. There are two problems of this approach: 1. Pulling docker images over the Internet is slow and fragile. 2. Some clouds don't have external Internet access. It is suggested to build all the required images into the cloud images to resolved the issue. Here is a solution: We export the docker images as tar files, and put the tar files into a dir in the image when we build the image. And we add scripts to load the tar files in cloud-init, so that we don't need to download the docker images. Any advice for this solution or any better solution? Regards, Wanghua __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best Regards, Eli Qiao (乔立勇) Intel OTC China __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best Regards, Eli Qiao (乔立勇) __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org<mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ 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
