From 653d180ec054b1ab911b8d99a911340bc98bea95 Mon Sep 17 00:00:00 2001 From: Guillaume Abrioux Date: Fri, 26 Mar 2021 18:05:48 +0100 Subject: [PATCH] defaults: add a comment about `igw_network` This add a quick documentation in ceph-defaults about `igw_network` Signed-off-by: Guillaume Abrioux (cherry picked from commit c5728bdc6351fe985e17b095cbd5871ef673dc29) --- group_vars/all.yml.sample | 8 ++++++++ group_vars/rhcs.yml.sample | 8 ++++++++ roles/ceph-defaults/defaults/main.yml | 8 ++++++++ 3 files changed, 24 insertions(+) diff --git a/group_vars/all.yml.sample b/group_vars/all.yml.sample index 007bb26a0..b515a258a 100644 --- a/group_vars/all.yml.sample +++ b/group_vars/all.yml.sample @@ -810,6 +810,14 @@ dummy: #alertmanager_port: 9093 #alertmanager_cluster_port: 9094 # igw +# +# `igw_network` variable is intended for allowing dashboard deployment with iSCSI node not residing in the same subnet than what is defined in `public_network`. +# For example: +# If the ceph public network is 2a00:8a60:1:c301::/64 and the iSCSI Gateway resides +# at a dedicated gateway network (2a00:8a60:1:c300::/64) (With routing between those networks). +# It means "{{ hostvars[item]['ansible_facts']['all_ipv4_addresses'] | ips_in_ranges(public_network.split(',')) | last | ipwrap }}" will be empty. +# As a consequence, this prevent from deploying dashboard with iSCSI node when it reside in a subnet different than `public_network`. +# Using `igw_network` make it possible, set it with the subnet used by your iSCSI node. #igw_network: "{{ public_network }}" diff --git a/group_vars/rhcs.yml.sample b/group_vars/rhcs.yml.sample index d9118624f..020b06cd4 100644 --- a/group_vars/rhcs.yml.sample +++ b/group_vars/rhcs.yml.sample @@ -810,6 +810,14 @@ alertmanager_container_image: registry.redhat.io/openshift4/ose-prometheus-alert #alertmanager_port: 9093 #alertmanager_cluster_port: 9094 # igw +# +# `igw_network` variable is intended for allowing dashboard deployment with iSCSI node not residing in the same subnet than what is defined in `public_network`. +# For example: +# If the ceph public network is 2a00:8a60:1:c301::/64 and the iSCSI Gateway resides +# at a dedicated gateway network (2a00:8a60:1:c300::/64) (With routing between those networks). +# It means "{{ hostvars[item]['ansible_facts']['all_ipv4_addresses'] | ips_in_ranges(public_network.split(',')) | last | ipwrap }}" will be empty. +# As a consequence, this prevent from deploying dashboard with iSCSI node when it reside in a subnet different than `public_network`. +# Using `igw_network` make it possible, set it with the subnet used by your iSCSI node. #igw_network: "{{ public_network }}" diff --git a/roles/ceph-defaults/defaults/main.yml b/roles/ceph-defaults/defaults/main.yml index 6e566b458..6d23f54c4 100644 --- a/roles/ceph-defaults/defaults/main.yml +++ b/roles/ceph-defaults/defaults/main.yml @@ -802,6 +802,14 @@ alertmanager_conf_dir: /etc/alertmanager alertmanager_port: 9093 alertmanager_cluster_port: 9094 # igw +# +# `igw_network` variable is intended for allowing dashboard deployment with iSCSI node not residing in the same subnet than what is defined in `public_network`. +# For example: +# If the ceph public network is 2a00:8a60:1:c301::/64 and the iSCSI Gateway resides +# at a dedicated gateway network (2a00:8a60:1:c300::/64) (With routing between those networks). +# It means "{{ hostvars[item]['ansible_facts']['all_ipv4_addresses'] | ips_in_ranges(public_network.split(',')) | last | ipwrap }}" will be empty. +# As a consequence, this prevent from deploying dashboard with iSCSI node when it reside in a subnet different than `public_network`. +# Using `igw_network` make it possible, set it with the subnet used by your iSCSI node. igw_network: "{{ public_network }}"