1 / 9

IT Services Meeting 24-Mar-2014

IT Services Meeting 24-Mar-2014. Helge Meinhard AI weekly topical meeting 27 March 2014. Summary. About 1 hour on AI Configuration (Gavin) Monitoring (Pedro) Cloud (Tim replacing Jan) Report from Thu pm meetings (HM) Details : https://indico.cern.ch/event/302049/. Area Reports.

hyatt-levine
Download Presentation

IT Services Meeting 24-Mar-2014

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. IT Services Meeting24-Mar-2014 Helge Meinhard AI weekly topical meeting27 March 2014

  2. Summary • About 1 hour on AI • Configuration (Gavin) • Monitoring (Pedro) • Cloud (Tim replacing Jan) • Report from Thu pm meetings (HM) • Details: https://indico.cern.ch/event/302049/

  3. Area Reports • Most Q1 milestones met • (Small) backlog being worked on • AI and WLCG monitoring to be discussed in forthcoming ISM meeting • Investigating alignment of security data collection with monitoring infrastructure • Security team collecting 600 GB/day now, will grow to 1 TB/day • See slides and notes for details

  4. QA for software packages (1) • Vivid discussion, summary by Arne Wiebalck • Scope: shared packages – written at CERN, used outside maintainer’s control (OpenAFS, Lemon, Puppet, …) • Same principle as with shared modules • Common QA process, supported by Koji • Packages go from test to QA with CRM ticket • Can move to production after a week if no problem found

  5. QA for software packages (2) • Responsibilities • Package providers to ensure process is followed • Puppet module owners to ensure proper repository structure to support QA process • Service managers to ensure testing during QA • No technical enforcement • Exceptions possible for emergency updates • Snapshots to be supported, Puppet module providers to ensure yum repositories are set up correctly

  6. QA for software packages (3) • RHEL and EPEL out of scope • RHEL: Strict QA process at Red Hat • One CRM ticket per week • EPEL: We have no control over process • Depend on maintainers to move from QA (testing) to production

  7. Koji and SWREP (1) • SWREP: Quattor world; users build rpms by hand and upload • Koji: compile/package for AI; supports signatures, signs by default • Koji-built rpms for SL6 fail upload to SWREP – signature format not supported • Manual builds and uploads still work for SL6

  8. Koji and SWREP (2) • Options: • Upgrade SWREP to SL6 – lots of work • Support adequate signatures in Koji – lots of work • Disable signature check for SWREP upload • Do nothing – Koji and SWREP not designed to work together • Consensus: option 3 – disable signature check • Very limited effort

  9. ISM Decision Both proposals approved

More Related