Preparations for SLC5: 2nd meeting

Friday 23 May 2008, 11:00 → 12:30 Europe/Zurich

513/1-024 (CERN)

Here is a status report on the preparation for slc5 progress. TSI: please use lxdev32,33 for your developments on the hardware domain. Other: please use lxdev30 (64) and lxdev31 (32bits) for tests and dev. (login as root with installation passwd for now) I propose to have a second meeting Friday 23 May 11am. STATUS ------------ - core installation OK - AIMS ok - PrepareInstall OK - Quattor OK - SSH OK (login as root with installation passwd) - Sindes OK (Sebastian to upate ncm-sindes to the new template structure) - Console service : to be checked by Andras Horvath - iptables-related stuff : to be checked by Jan Iven (cdispd to be updated by Veronique) - new filepartition schema to be tested (Andras H.) and PrepareInstall to then be updated (Jan I) - minimal installation = - core installation plus: - + zuul - need to setup user access with ncm-useraccess (Miro to provide an example) - Didi to understand why ncm-authconfig (nscd) fails at installation and not after. - + lemon - final tuning in progress by Miro - with monitoring of hardware :to be done by TSI - with monitoring of Quattor: need lemon-sensor-fio to be ported to slc5 (Jan vE) - with monitoring of base system - + many missing things (krb5, srvtab,sysctl,cheklines,cron,modprobe,notdconf,ntpd,sendmail,pacct etc) to be reviewed. - Swrep mirroring and updates of defaults: - to be investigated by Jan and Veronique CDB template structure ---------------------------------- See profiles/profile_lxdev30,1,2,3 for examples. /prod/monitoring/lemon created for Miro to continue. Please do not touch anything there. /prod/hardware created to be touched by TSI only /prod/os created should not need to be touch except for updating defaults until it is automatised /prod/site/cern_cc created please contact me for changing or adding anything there. /prod/cluster created please feel free to populate with your own cluster. Look at /cluster/lxdev for examples. /prod/components there since some time. This is the place to put the components with the new schema and tpl organisation /prod/services there since some time. Create your service templates there. Take /services/nscd/config.tpl as example /prod/pan and /prod/quattor do not touch. Contact me if needed /netinfo created to be populated by me, tools to be updated in consequence IMPORTANT: For your new developments, please follow PAN syntax new coding rules, to easy migrating to the next PAN version. See https://twiki.cern.ch/twiki/bin/view/ELFms/NewPanSyntax

Present: Alex I., Ricardo S., Tim B., Uli S., Jan vE, Veronique L, Matthias S., Jan I.

Review of actions from last meeting

• stop support 32bit compatible libs on 64 bit arch systems:
  • VL contacted CMS: They need to test.
  • TB: needed for hardware monitoring
  • memory usage problemscon 64bit has been observed by VOs
• RHES5 support in Quattor:
  • not before next year for DB's
  • not before next year fo TSM
  • AFS may need it, but, if alone, they would contribute to the creation of the needed CDB templates
• Tests machines:
  • lxdev30,31: for tests (lxdev cluster)
  • lxdev32,33: for builds (--> VL to create an lxbuild cluster)
  • lxb6641: for installation tests by Jan vE
• SElinux ON by default now on slc5: safer
  • TB: it will cause a lot of trouble for Apache for ex.
    • JI: Linux team will help configuring webservices
  • TB: has castor been tested with selinux on ?
    • JI: selinux is verbose enough: if it causes problems to castor, it should be straightforward to identify that the root cause is selinux
  • ncm-iptables: new release available soon from JI
  • ncm-cdispd to be updated by VL (iptables tries to right to its log)
  • iptables configuration, to be reviewed by VL, with help from JI.
• zuul: sin2pwd to be deployed by Didi (use of passd header files from sindes)
  • Until then, root installation passwd to be used
  • useraccess and sudo components to be used to replace ncm-access_control
• diskinfo will be moved to /prod/vpd/<host>.tpl: vpd = Vital Product Data </host>
  • Will also contain MAC address and Serial number (will be removed from the profile)

New item of discussion:

• rackinfo: do we need to keep it in CDB ? why not CDBW?
  • VL to check what are the implications on all tools
  • can we link rack name with Net switch info from LANDB ? not a 1-1 mapping.
• oldnames: do we still need them ? Could Remedy has the Serial number stored ?
  • VL to check
• cpu configuration:
  • si2k and ncpu fields will be removed
  • cores will be added
• harddisks configuration in CDB:
  • Andras H. has proposed a solution. General enough according to TB
  • What does Quattor say ? VL to check.
  • needed by PrepareInstall
• slc5 swrep synchronisation:
  • to be put in production by JI and VL
• Review of TWiki (see https://twiki.cern.ch/twiki/bin/view/ELFms/ScientificLinux5Port )
  • top priority now: krb5clt, srvtab, useraccess, sudo