2.7 KiB
Test Systems
List of test nodes and the idea behind.
Core Linux Infrastructure Systems
- sysdb-test.psi.ch aka lx-sysdb-test-01.psi.ch as test Sysdb server
- puppet00-test.psi.ch as test Puppet server
On these systems there is currently only the lxdev sysdb environment available/configured.
To get a node to boot into the test setup, you need a special network boot configuration for grub in the network-boot repo.
Best do in grub.d a symlink from the full qualified hostname to use-sysdb-test.
Then in the root directory you need another symlink from grub.cfg-01-$MAC (use dashes instead of colons to separte the MAC address bytes) to the symlink with your hostname in grub.d. This last file is looked up by grub during network boot. The symlink cascade is to know what MAC address belongs to what host and what is the intend of the special configuration.
Icinga2 Test Server
Here we mostly deal with the master:
- Primary vmonma02a.psi.ch (with Director)
- Secondary vmonma02b.psi.ch
The schema with all nodes of the test setup you find in the Monitoring Environment Slides page 3.
Test RHEL Nodes
This systems are in the lxdev sysdb environment.
Here we have minimal configuration (noconfig) to test the default setup and a more extensive configuration (muchconfig) to have a test bed with more complex settings.
noconfig Servers
lxdev00.psi.chrunning RHEL7lxdev01.psi.chrunning RHEL8 with managed network configuration and static IP automatically read from DNSlxdev02.psi.chrunning RHEL9 with managed network configuration and static IP automatically read from DNS
noconfig Workstations
lxdev03running RHEL7lxdev04running RHEL8lxdev05running RHEL9
muchconfig Workstations
lxdev6running RHEL7lxdev7running RHEL8lxdev8running RHEL9
All of these have a serial port added to the virtual hardware and the output of it is sent to a file which is accessible on lxsup.psi.ch on /data/serial_console/
Then each of these hosts can monitor the network traffic of the two other hosts. The interface ens224 will get a copy of the network traffic from the lower of the other two hosts, whereas the interface ens256 gets the traffic of the node with the bigger number.
Test DMZ Nodes
This system are in the normal production lx sysdb environment in the dmz puppet group:
lx-test-dmz-01.psi.chlx-test-dmz-02.psi.ch