1 / 5

ALICE

ALICE. Use of CMF (CC) for the installation of OS and basic S/W OPC servers and other special S/W installed and configured by hand PVSS project provided by sub-detectors and loaded on central FS from where they are downloaded to PC Changes made to PVSS project on PC uploaded back to the FS

marina
Download Presentation

ALICE

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ALICE • Use of CMF (CC) for the installation of OS and basic S/W • OPC servers and other special S/W installed and configured by hand • PVSS project provided by sub-detectors and loaded on central FS from where they are downloaded to PC • Changes made to PVSS project on PC uploaded back to the FS • Fw components installed using fw Installation tool in local project and changes reflected back to config DB (local mode) • Panels, scripts stored locally in a shared directory • Automatic copying of panel/scripts to FS • B/U by taking an image of the application partition to FS (later use of virtual machines and file copy of virtual disk to FS)

  2. ATLAS • Use of CMF (CC) for the installation of OS and basic S/W as well as some specific ATLAS packages, e.g. scripts to mount network drives, start DNS, etc. • OPC servers and other special S/W configured by hand • Projects installed manually from the central FS (TS) – two directories for each project (linked to cvs) • Project panels and scripts only on TS • Fw components (incl. panels and scripts) installed locally by hand by SD using fw Installation Tool (not yet linked to config DB) • SD make 3 types of B/U; file copy to TS, on-line B/U and creating dplist and FSM package

  3. CMS • Complete automated installation to a fully running application under the responsibility of central team • CMF (CC) used for basic applications and CSM specific applications, OPC servers, drivers, scripts, etc. • Sub-detectors provide their applications as fw components to a central FS • All updates installed via new versions of fw components • All fw components, panels and scripts located on FS shared to all PCs – probably two versions (of complete fw component package) • Fw Installation tool used extensively with the config DB as the master • Pre-configured PCs as hot spares • Essentially same process used for restore. Possibly use on-line B/U for quick restore

  4. LHCb • OS and basic S/W installed using SMS (Windows) or QUATTOR (Linux) – no connection to CC • OPC servers installed and configured by central team • Use of a shareware tool to configure services • Central FS visible to all PCs (Linux or Windows) with folder for each project packaged as fw component • SD creates project on PC and installs application/fw components using fw installation tool not linked to config DB (will use later but initially in local mode) • B/U using file copy

  5. Possible Discussion Items • All using CMF from the CC except LHCb • Limitations of SMS versus CMF? • Installation • Automated under control of central team versus performed by SDs • Location of panels and scripts • Local versus central • Issue of many paths in config file • User privileges for starting and stopping OPC servers, etc. • Is this just an LHCb problem? • Setting up of services, tool similar to Serguei’s • Needed? • Local versus central mode of installation tool • Most seem to want to use this in local mode • B/U • Many different strategies

More Related