1 / 10

DCS Software Installation Procedure

DCS Software Installation Procedure. infrastructure recap guidelines, procedures Peter Rosinsky, Peter Chochula, ACC team. ALICE DCS Workshop, CERN, 9-10 October 2006. DCS computing. CR3 Central services Application gateways (GW)

rosa
Download Presentation

DCS Software Installation Procedure

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. DCS SoftwareInstallation Procedure infrastructure recap guidelines, procedures Peter Rosinsky, Peter Chochula, ACC team ALICE DCS Workshop, CERN, 9-10 October 2006

  2. DCS computing • CR3 Central services • Application gateways (GW) • Fileservers (FS), databases (DB), admin nodes (AN), other (DNS, DHCP, …) Detector computers • Operator nodes (ON), worker nodes (WN) • CRx, SG, Cavern • Computers, DCS boards, Power supplies, PLCs • CNIC – ALICE network domain • Trusting, Exposing – IT central services (GPN), ALICE-TN communication • Control sets – protect PLCs Peter Rosinsky, DCS Workshop

  3. Status • Network • CR3 – cabled, connected to starpoint, working • DHCP workaround – relay (to be solved by new router) • Other CRs and cavern – mostly cabled, services defined, connection to starpoint soon (~week) • Computers - CR3 • mounted ~100 (90%) • installed: 3xGW, 2xAN, 1xFS, 2xDB, 20xON, 60xWN, • DCS SW (PVSS) – TOF, TRD, HMP, services, (as demanded) • Other – 4x TOF Linux control nodes • Computers in other locations - CRx, SG, Cavern • network installation in progress, GPN available in CRs/SG Peter Rosinsky, DCS Workshop

  4. Software Installation Detector’s point of view: • Upload to DCS LAB fileserver • Install from CR3 fileserver (together with ACC team) ACC: • Checks the SW uploaded to the LAB server • Transfer: DCS LAB fileserver  CR3 fileserver Prerequisites • Permissions – ask DCS admin • Send NICE usernames to alice-dcs-admin@cern.ch • Detector expert group – e.g. “ALICE DCS TOF EXP” Peter Rosinsky, DCS Workshop

  5. Installation procedure Extract from http://alice-dcs.web.cern.ch/alice-dcs/public/installation.html • Check out your D date not to miss the D-4 weeks deadline. • Contact DCS admin - Peter Rosinsky - (alice-dcs-admin@cern.ch) prior to D-4 if you need to clarify the procedure. • Send the DCS admin a list of common software you are going to use. • Ask DCS admin to get the permissions on our installation fileserver. • Go to your installation site – e.g. \\aldcsfs001\DCS\agd • Create a subdirectory named after the current date in a format YYYY-MM-DD every time you bring a new version. • Make a link (shortcut) named "production" to the directory containing the current production version of your installation. • Unpack your archives to a simple and convenient logical structure, e.g. one directory per package. • Describe this structure (what's where) in a text file named "readme.txt" together with version info and short description. • Set the date (based on D) and time with the ACC team (DCS admin) for the installation session in CR3. In the meantime, the ACC team will perform basic checks and will transfer your installation site onto a production fileserver. • For the installation in CR3 you will use a copy of your installation site residing on a production fileserver, e.g \\alidcsfs001\DCS\agd. • Computers in CR3 will be pre-installed with several commonly used software packages including the current version of PVSS. Peter Rosinsky, DCS Workshop

  6. Fileserver directory structure • Fileserver share: • DCS LAB (upload): \\aldcsfs001\DCS - visible from GPN • CR3: \\alidcsfs001\DCS - visible only from ALICE net (CR3) directories for • Subdetectors • three-letter code, small letters • e.g. \tof, \trd, \hmp • Projects • rack control (\rck), central DCS (\dcs) • Common software • \software Peter Rosinsky, DCS Workshop

  7. Detector’s subdirectory • Detector PVSS projects, databases, scripts • Versioning – date • Subdirectory: \YYYY-MM-DD • e.g. \\aldcsfs001\DCS\rck\2006-06-21 • Shortcuts: production (mandatory), other (detector-specific), common SW pointers • readme.txt • description field: additions, improvements, bug fixes, comments \agd \production - shortcut to the production version, \2006-08-24 \2006-08-24 - production description: added databases, improved ramp-up \agd_hvControl - main PVSS project \agd_hvControl _fw - framework for agd_hvControl \database Peter Rosinsky, DCS Workshop

  8. Common software Subdirectory \software • OPC servers • ELMB, CAEN, ISEG, Schneider, Wiener, … • Drivers • DIGI, USB CANbus, MXI, FalconFG, … • Tools • DB tools, OPC explorer, CAN explorer, … • Libraries, ActiveX controls, … Peter Rosinsky, DCS Workshop

  9. … • … • … • … Peter Rosinsky, DCS Workshop

  10. DCS Devices Network registration • Individual devices – use CERN NETOPS form • http://www.cern.ch/network • check availability using the form • follow ALICE naming convention – we’ll check/approve • Groups of devices – contact DCS admin • power supplies, DCS boards, … • name-space reservation • MAC address pre-registration • Network services for the DCS • http://www.cern.ch/alice-dcs/public/networkP2user.txt Peter Rosinsky, DCS Workshop

More Related