Page History
...
- collection manager (CM) alive (long lived)
- restart .cnf
- python-proxies comes up
- proxies reports existence/identity (Detector/DRP, EB, monshmserverAMI, monshmserverPsana, DTI, XPM, Control) to CM
- control level queries CM for list of all processes in the platform
- control level notifies CM of processes it wants for partition
- CM tells all processes about all the nodes in the partition
- processes figure out how many "ports" (an abstract idea, could be q-pair for IB) they need given the nodes in the partition and report back their ports to CM
- CM treats ports as opaque information
- CM also manages connection information for detector-to-dti-link-to-drp-node mapping table (connection information) which is used by the DTI-proxy to compute a dti-link-mask.
- after gathering all port information, CM broadcasts all ports, as well as CM-assigned "id" to proxies
- proxies are specialized for particular levels (DRP, EB, DTI) and select ports they are interested in
- proxies make appropriate connections based on their CM-assigned ID number
- proxies report that they are connected, or failure (e.g. if DTI-link-mask is already allocated, or IB connection fails)
- after all proxies report in, manager notifies control level that transitions can be sent
- control level starts to send transitions
- graceful teardown: unconfigure/unmap transitions complete. CM sends disconnect message to proxies
- ungraceful teardown: feels like we need to restart, since things can be broken in various ways
...
Overview
Content Tools