The network group plans to create a 'cloud' named PDAQ
PDAQ is a layer-3 entity, routing
the first member of PDAQ will be the Eiger2 (100GE) of P11,
this device will be connected to the access switch named: SW-PDAQ-AL001,
the access switch will be connected to2 routers named RT-PDAQ
the network group proposes that all experiment-related nodes
should eventually be moved to PDAQ because
- certain network problems can be avoided (loops)
- monitoring/trouble shooting becomes easier
- a separate category for experiment related HW is useful
- such a structure exists already for X-FEL and FLASH
One restriction: a subnet/VLAN cannot appear
inside and outside PDAQ.
Nodes within PDAQ can have internet access.
To move nodes to PDAQ: ask the network group to create a VLAN within PDAQ,
move all nodes connected to an arista to this VLAN
the transition work can be organized as we like
Discussions are still ongoing.
new packages distributed: hasyutils, pySpectra, tngGui:
python2 and python3 modules are installed. Scripts are
distinguished by '3', e.g.: TngGui.py and TngGui3.py.
Debian-10 upgrade
Debian-10 is ready, tests passed
Install Tango 9.3, tests passed
Install python3-sardana, done
python2/python3 compliance, new packages for hasyutils, pyspectra, tnggui, done
one BL after the other: Debian-10 then Tango 9.3 then SardanaPython3, ongoing,
haspp08dev has been updated, other candidates?