JorgeAndrade
Flight Engineer Flight Engineer
Flight Engineer
  • 1,639 Views

Disconnected Installation OCP 3.10 - improvements

Official Documentation:
https://docs.openshift.com/container-platform/3.10/install/disconnected_install.html
Does anyone else thinks that this procedure could be improved setting up a docker-ditribution service and not just pulling the images, export and then import them into the cluster nodes ?
5 Replies
flozano
Moderator
Moderator
  • 1,600 Views

Re: Disconnected Installation OCP 3.10 - improvements

Hi Jorge,

This is exactly what we do in Red Hat's certification training for OpenShift, such as DO180, DO280, and DO288. Instead of having to pre-pull all required container images into each node before starting instalation, we run a docker-distribution server pre-loaded with all container images and let each node pull the images on-demand. This is actually supported by the OpenShift installer playbooks.

The registry does not need to be a docker-distribution server: it could be Nexus, Artifactory, etc. I am eager to experiment with Quay (now Red Hat Container Registry) and some day using it in future courses.

Reply
Loading...
debianmaster
Cadet
Cadet
  • 1,594 Views

Re: Disconnected Installation OCP 3.10 - improvements

what kind of inventory params are you using for pulling image during installation on demand?

0 Kudos
Reply
Loading...
oldbenko
Moderator
Moderator
  • 1,585 Views

Re: Disconnected Installation OCP 3.10 - improvements

hey, @debianmaster, as @flozano said, we do not pull images during the installation. they are simply made available in a private registry running in a separate virtual machine (as they would be in any enterprise-grade cluster installation).

the two settings that must be present in the inventory are oreg_url (to get the control plane images pulled from a private registry as nodes, masters and backend services are being started) and then additionally, openshift_examples_modify_imagestreams (to have the default image streams fixed by the installer to point to the private registry as well).

A black cat crossing the street signifies that the animal is going somewhere.
[don't forget to kudo a helpful post or mark it as a solution!]
0 Kudos
Reply
Loading...
JorgeAndrade
Flight Engineer Flight Engineer
Flight Engineer
  • 1,559 Views

Re: Disconnected Installation OCP 3.10 - improvements

Exactly the official documentatino should be something like we do on our courses!! It's a better resources usage that downloading images on all nodes.

 

Regards,

0 Kudos
Reply
Loading...
beelandc
Flight Engineer Flight Engineer
Flight Engineer
  • 1,533 Views

Re: Disconnected Installation OCP 3.10 - improvements

In addition to the two settings @oldbenko listed, there are a number of other variables available (at least in v3.9) for use in disconnected environments. Many of which are necessary to pull from non-standard registries if you are installing the given component. Here are the settings relating to images and private registries that come to mind, with some sample values:

openshift_docker_additional_registries=repo.home.example.net
openshift_docker_insecure_registries=repo.home.example.net
openshift_docker_blocked_registries=registry.access.redhat.com,docker.io
oreg_url=repo.home.example.net/openshift3/ose-${component}:${version}
openshift_examples_modify_imagestreams=true
openshift_metrics_image_prefix=repo.home.example.net/openshift3/
openshift_metrics_image_version=v3.9.40
openshift_logging_image_prefix=repo.home.example.net/openshift3/
openshift_logging_image_version=v3.9.40
ansible_service_broker_image_prefix=repo.home.example.net/openshift3/ose-
ansible_service_broker_image_tag=v3.9.40
ansible_service_broker_etcd_image_prefix=repo.home.example.net/rhel7/
ansible_service_broker_etcd_image_tag=latest
openshift_service_catalog_image_prefix=repo.home.example.net/openshift3/ose-
openshift_service_catalog_image_version=v3.9.40
openshift_cockpit_deployer_prefix=repo.home.example.net/openshift3/
openshift_web_console_prefix=repo.home.example.net/openshift3/ose-
openshift_web_console_version=v3.9.40
openshift_prometheus_image_prefix=repo.home.example.net/openshift3/
openshift_prometheus_image_version=v3.9.40
openshift_prometheus_alertmanager_image_prefix=repo.home.example.net/openshift3/
openshift_prometheus_alertmanager_image_version=v3.9.40
openshift_prometheus_alertbuffer_image_prefix=repo.home.example.net/openshift3/
openshift_prometheus_alertbuffer_image_version=v3.9.40
openshift_prometheus_node_exporter_image_prefix=repo.home.example.net/openshift3/
openshift_prometheus_node_exporter_image_version=v3.9.40
openshift_prometheus_proxy_image_prefix=repo.home.example.net/openshift3/
openshift_prometheus_proxy_image_version=v3.9.40
template_service_broker_prefix=repo.home.example.net/openshift3/ose-
template_service_broker_version=v3.9.40
openshift_storage_glusterfs_image=repo.home.example.net/rhgs3/rhgs-server-rhel7
openshift_storage_glusterfs_version=latest
openshift_storage_glusterfs_heketi_image=repo.home.example.net/rhgs3/rhgs-volmanager-rhel7
openshift_storage_glusterfs_heketi_version=latest
Reply
Loading...
Join the discussion
You must log in to join this conversation.