Bug 1636136 - [cee/sd] add ceph_docker_registry to group_vars/all.yml.sample same way as ceph-ansible does allowing custom registry for systems without direct internet access
Summary: [cee/sd] add ceph_docker_registry to group_vars/all.yml.sample same way as ce...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Metrics
Version: 3.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 3.3
Assignee: Zack Cerza
QA Contact: Madhavi Kasturi
Bara Ancincova
URL:
Whiteboard:
Depends On:
Blocks: 1726135
TreeView+ depends on / blocked
 
Reported: 2018-10-04 14:16 UTC by Tomas Petr
Modified: 2023-09-07 19:25 UTC (History)
6 users (show)

Fixed In Version: cephmetricUses-2.0.4-1.el7cp
Doc Type: Enhancement
Doc Text:
.New options to use pre-downloaded container images Previously, it was not possible to install Red Hat Ceph Storage Dashboard and the Prometheus plug-in without access to the Red Hat Container Registry. This update adds the following Ansible options that allow you to use pre-downloaded container images: `prometheus.pull_image`:: Set to `false` to not pull the Prometeheus container image `prometheus.trust_image_content`:: Set to `true` to not contact the Registry for Prometheus container image verification `grafana.pull_image`:: Set to `false` to not pull the Dashboard container image `grafana.trust_image_content`:: Set to `true` to not contact the Registry for Dashboard container image verification Set these options in the Ansible `group_vars/all.yml` file to use the pre-downloaded container images. // See the link:https://access.redhat.com/solutions/3659971[Ceph Metrics: How to get container images when the environment does not have access to registry.access.redhat.com ?] solution for more information.
Clone Of:
Environment:
Last Closed: 2019-08-21 15:10:24 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph cephmetrics pull 234 0 'None' closed Prevent pull images for prometheus and grafana 2021-02-16 18:36:03 UTC
Github ceph cephmetrics pull 238 0 'None' closed Allow skipping image verification 2021-02-16 18:36:04 UTC
Red Hat Issue Tracker RHCEPH-2717 0 None None None 2021-12-10 17:47:29 UTC
Red Hat Knowledge Base (Solution) 3659971 0 None None None 2018-10-19 07:03:48 UTC
Red Hat Product Errata RHSA-2019:2538 0 None None None 2019-08-21 15:10:41 UTC

Description Tomas Petr 2018-10-04 14:16:21 UTC 
Description of problem:
Currently there is not a option for custom docker registry source outside of direct access to registry.access.redhat.com:
grep -irn  ./ -e "registry.access.redhat.com"
./roles/ceph-grafana/defaults/main.yml:8:    container_name: registry.access.redhat.com/rhceph/rhceph-3-dashboard-rhel7
./roles/ceph-prometheus/defaults/main.yml:4:    container_name: registry.access.redhat.com/openshift3/prometheus

The option for custom source should be added similar way it is in ceph-ansible.

Version-Release number of selected component (if applicable):
cephmetrics-ansible-2.0-5.el7cp.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 12 Zack Cerza 2019-06-05 23:56:32 UTC 
We just merged a PR that allows the user to avoid pulling images for prometheus and grafana: https://github.com/ceph/cephmetrics/pull/234
Comment 13 Boris Ranto 2019-06-06 07:01:53 UTC 
btw: That is not enough to make us work without internet access. We also need to set 'trust_image_content' to true in order for that to work (see comment#10).
Comment 16 Boris Ranto 2019-06-20 21:32:23 UTC 
With the latest cephmetrics-ansible build (2.0.4-1), you can use the following ansible options (set in group_vars/all.yml file) to control the pull_image/trust_image_content behaviour for grafana/prometheus:

prometheus.pull_image
prometheus.trust_image_content
grafana.pull_image
grafana.trust_image_content
Comment 22 errata-xmlrpc 2019-08-21 15:10:24 UTC 
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/RHSA-2019:2538
Note You need to log in before you can comment on or make changes to this bug.