Sketch of the Network Topology.

Contexts in source publication

Context 1

... is developed in a standard desktop environmen- t configured around a file server in an easily accessible Internet domain (stage 0 in fig. 1). Here functionalities are tested for the first time at test stands. In contrast to that relatively open environment the control system in pro- duction runs on a highly protected, non-routable Intranet with autonomous file server, consoles and front end com- puters (IOCs). Independent network components as well as fail over ...

Context 2

... a new software module or version is scheduled for go- ing into operation it first has to be installed on the test ma- chine either in the boot area of the IOC computers or into the tree of console applications (stage 1 in fig. 1). As soon as a time slot for tests becomes available the new versions are tested by running console applications on the test ma- chine or booting the IOCs from the test area. Discovered bugs are fixed, the improved version reinstalled and retest- ed. Whenever a test time slot ends the switch back to the settled productional version ...

Context 3

... and retest- ed. Whenever a test time slot ends the switch back to the settled productional version requires in its worst case the reboot of the affected IOCs. If the new modules appear to be sufficiently mature the version repository is updated, the modules are installed on the file server and become the new productional version (stage 2/3 in fig. ...

Context 4

... the beamline area are needed by the orbit sta- bility control modules within the accelerator segment. The data transfers between the networks is provided by gate- way programs that control transfer of access security and impact on network bandwidth. It is foreseen to run these gateway processes on dedicated multi-homed communica- tion facilities (Fig. ...

Context 5

... it be- comes essential to replace this error-prone and inflexible procedure and maintain a uniform and transparent version- ing of all production quality software that allows an easy roll-back to preceding versions. The central communica- tion facility will provide the required file server functional- ity for this common repository (stage 2 in fig. ...