Cache required docker images in the Cloud image

Registered by hongbin on 2016-04-05

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. We currently added support for disk-imagebuilder to build an Atomic image [1]. We can customize the image build process to allow users to input a list of docker images that will be built into the image.

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

Blueprint information

Status:
Complete
Approver:
hongbin
Priority:
Medium
Drafter:
hongbin
Direction:
Approved
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Spyros Trigazis on 2018-02-23

Related branches

Sprints

Whiteboard

Addressed by http://git.openstack.org/cgit/openstack/magnum/commit/doc/source/user/index.rst?id=69bb03fcbe87489ab3179d73bc7fc26d4a7befeb

Operators can mirror the required containers in a local registry and pass the appropriate label.

@Hongbin: If we modify the dib script to pull the images list (that grep from env config in environment.d folder), is this OK?

The images list requires user manual input the list of desired cached image.

See also: https://blueprints.launchpad.net/magnum/+spec/alternative-infra-images-registry

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.