Appendix A. Installing Metrics Store with Satellite

You can use Satellite to install Metrics Store on a disconnected environment.

Prerequisites

Note

If you encounter a missing image or a reference to an online image (depending on which applications you are using), consider updating the references in the deployment or build configuration of the application, or re-tag Docker images as a temporary measure (just to rule out that the image is not reachable).

  • The following OpenShift component images are synchronized through Docker on your Satellite server: 

    openshift3/oauth-proxy
openshift3/ose-console
openshift3/ose-control-plane
openshift3/ose-deployer
openshift3/ose-docker-registry
openshift3/ose-haproxy-router
openshift3/ose-logging-auth-proxy
openshift3/ose-logging-curator5
openshift3/ose-logging-elasticsearch5
openshift3/ose-logging-fluentd
openshift3/ose-logging-kibana5
openshift3/ose-node
openshift3/ose-pod
openshift3/ose-web-console
openshift3/registry-console
rhel7/etcd

  • Two hosts are created on the Satellite server - one for the Metrics Store Installer virtual machine, and one for the OpenShift virtual machine, as follows:

    1. Create hosts on Satellite - see Creating a Host.
    2. Assign static IP addresses and MAC addresses for the virtual machines. The host for the OpenShift virtual machine should be of the format master-<suffix>0 to match the OpenShift virtual machine hostname.

  • The qcow image is available on the Manager machine.

    1. Go to RHEL product software.
    2. In the Product Software tab, download the Red Hat Enterprise Linux KVM Guest Image to the Manager machine.

Running the Ansible role

  1. On the Manager machine, copy /etc/ovirt-engine-metrics/metrics-store-config-satellite.yml.example to metrics-store-config.yml. 

    # cp /etc/ovirt-engine-metrics/metrics-store-config-satellite.yml.example /etc/ovirt-engine-metrics/config.yml.d/metrics-store-config.yml

  2. Update the values of /etc/ovirt-engine-metrics/metrics-store-config.yml to match the details of your specific environment. 

    # vi /etc/ovirt-engine-metrics/config.yml.d/metrics-store-config.yml

  3. On the Manager machine, copy /etc/ovirt-engine-metrics/secure_vars_satellite.yaml.example to /etc/ovirt-engine-metrics/secure_vars.yaml. 

    # cp /etc/ovirt-engine-metrics/secure_vars_satellite.yaml.example /etc/ovirt-engine-metrics/secure_vars.yaml

  4. Update the values of /etc/ovirt-engine-metrics/secure_vars.yaml to match the details of your specific environment. 

    # vi /etc/ovirt-engine-metrics/secure_vars.yaml

  5. Encrypt the secure_vars.yaml file. 

    # ansible-vault encrypt /etc/ovirt-engine-metrics/secure_vars.yaml

  6. Go to the ovirt-engine-metrics repo. 

    # cd /usr/share/ovirt-engine-metrics

  7. Run the metrics store installation playbook that creates the metrics store installer virtual machine. 

    # ANSIBLE_JINJA2_EXTENSIONS="jinja2.ext.do" ./configure_ovirt_machines_for_metrics.sh \
  --playbook=ovirt-metrics-store-installation.yml --ask-vault-pass -vvv
  8. Log in to the Administration Portal and review the Metrics Store installer virtual machine creation.

  9. Log in to the Metrics Store installer virtual machine. 

    # ssh root@<metrics-store-installer ip or fqdn>

  10. Run the Ansible playbook that deploys OpenShift on the virtual machines that were created. 

    # ANSIBLE_CONFIG="/usr/share/ansible/openshift-ansible/ansible.cfg" \
  ANSIBLE_ROLES_PATH="/usr/share/ansible/roles/:/usr/share/ansible/openshift-ansible/roles" \
  ansible-playbook -i integ.ini install_okd.yaml -e @vars.yaml -e @secure_vars.yaml --ask-vault-pass -vvv