Bug 1481693
Summary: | overcloud container image upload is unefficient | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Attila Fazekas <afazekas> |
Component: | openstack-tripleo-common | Assignee: | Steve Baker <sbaker> |
Status: | CLOSED ERRATA | QA Contact: | Artem Hrechanychenko <ahrechan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 13.0 (Queens) | CC: | emacchi, hbrock, jschluet, jslagle, m.andre, mburns, mcornea, ohochman, rhel-osp-director-maint, sbaker, slinaber |
Target Milestone: | beta | Keywords: | Triaged |
Target Release: | 13.0 (Queens) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-tripleo-common-8.3.1-0.20180123050219.el7ost | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-06-27 13:33:53 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Attila Fazekas
2017-08-15 13:15:01 UTC
Steve can it be improved by removing containers that are not going to be use during the overcloud deployment ? Omri, sure, using the --service-environment-file and --roles-file arguments is always recommended when calling "openstack overcloud container image prepare" to minimise uploads to the containers actually used. However this change is more about parallelising the uploads, and avoiding the unnecessary transfer to the local docker cache. I have a change upstream to switch to skopeo to do the transfers, which avoids the local docker cache. I'll use this bz to track skopeo landing, and also adding some concurrency to the transfers. the used of skopeo seems to improve the process times, please re-open if discover other inefficiencies And using -e in the prepare command can assure to download only 'to be used' containers Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:2086 |