action #135191
closed
QA (public) - coordination #121720: [saga][epic] Migration to QE setup in PRG2+NUE3 while ensuring availability
QA (public) - coordination #123800: [epic] Provide SUSE QE Tools services running in PRG2 aka. Prg CoLo
Migration of o3 VM to PRG2 - Use direct zabbix connection size:M
Added by okurz over 1 year ago.
Updated over 1 year ago.
Description
Motivation¶
The openQA webUI VM for o3 was moved to PRG2 but for zabbix we still use an "over old-ariel" connection. We should use a direct zabbix connection
Acceptance criteria¶
- AC1: o3 can monitor without relying on old-ariel
Suggestions¶
# grep -v '^#' /etc/zabbix/zabbix_agentd.conf | grep Server
Server=172.17.0.1
ServerActive=zabbix-proxy-opensuse
- Copied from action #133364: Migration of o3 VM to PRG2 - Decommission old-ariel in NUE1 as soon as we do not need it anymore added
- Subject changed from Migration of o3 VM to PRG2 - Use direct zabbix conection to Migration of o3 VM to PRG2 - Use direct zabbix connection
- Subject changed from Migration of o3 VM to PRG2 - Use direct zabbix connection to Migration of o3 VM to PRG2 - Use direct zabbix connection size:M
- Description updated (diff)
- Status changed from New to Workable
- Status changed from Workable to In Progress
- Status changed from In Progress to Blocked
Currently there is a tunnel (tunX interface) between old-ariel and new-ariel using ssh.
There is an iptables rule on old-ariel to redirect incoming connections to port 10049 on old-ariel to new-ariel via the tunnel.
The zabbix-agent on new-ariel is configured to listen on that port.
So on old-ariel you can reach old-ariel zabbix agent on the 10050 default port and new-ariel on 10049.
There doesn't seem to be a proxy reachable from new-ariel at the moment.
So requesting assistance from infra:
https://sd.suse.com/servicedesk/customer/portal/1/SD-134603
- Status changed from Blocked to In Progress
Infra is done:
firewall rules implemented. use proxy zabbix-proxy.dmz-prg2.suse.org.
As the default route on new-ariel goes via extern facing eth0, there is a static route needed to reach zabbix-proxy.dmz-prg2.suse.org. via eth1 (as it (10.151.15.2) is not part of the network attached to eth1, connection needs to go via gw at 10.150.1.254)
/etc/sysconfig/network/routes:
10.151.15.2/32 10.150.1.254 - -
- Status changed from In Progress to Resolved
Host reconfigured for prg2-dmz proxy.
Also available in: Atom
PDF