1 / 12

NiceFC and CMF Introduction

NiceFC and CMF Introduction. Custom Windows Services for Controls Applications. Ivan Deloose IT-IS. Agenda. What is NiceFC ? NiceFC Strategy NiceFC Model What is CMF ? CMF Functionality Architecture Demo Questions. What is NiceFC ?.

chelsead
Télécharger la présentation

NiceFC and CMF Introduction

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. NiceFC and CMF Introduction Custom Windows Services for Controls Applications Ivan Deloose IT-IS

  2. Agenda • What is NiceFC ? • NiceFC Strategy • NiceFC Model • What is CMF ? • CMF Functionality • Architecture • Demo • Questions

  3. What is NiceFC ? • Nice For Controls is a “Management Tool”, available to local activities to manage their computers • Activity can be an experiment, control system,… • Eg. AB-CO, DSS System, ATLAS-DCS • NiceFC allows to • define a “named set of computers” (NSC) • perform actions on all the computers member of his set • Security patch, application, policy settings, … • have complete control over the deployment schedule • re-install a computer, identically as before • reuse everything available from the central Windows Desktop Service (NICE), such as • Patch, Service Packs and OS maintenance • Centrally provided application packages • Eg. Phonebook, Office, Exceed, …

  4. NiceFC Strategy • Project split into 2 phases • Improve the Windows installation services • Network based installations of the Operating System • No need for floppy disk or CDs anymore • No need to preload disk images on new computers • See: http://cern.ch/Win/Services/Installation/Diane • Build a “Management Framework” where administrators of local activities can define and manage the exact configuration of computers under their control

  5. NiceFC Model • Distributed Framework which is organized by Activities (NSS) • NSS = Named System Sets • Describes an activity such as a domain, service, experiment, control system • Eg. AB-CO, DSS system, ATLAS-DCS • Defines the responsibility for the activity • Official link man with IT/IS support • A simple container for NSC and PKG collections with no functionality • NSC = Named Set of Computers • PKG = Packages • NSC = Named Set of Computers • Defines a list of computers defining a role • Eg. Control Room Consoles, Front End Systems • Can be fully locally managed and protected from global deployments • NSC responsible decides what should be deployed on the NSC members and when • Allow, Apply and Deny actions • Reboot and user interface level control • PKG = Packages • Defines the actions to perform on the NSCs • Re-use central PKGs or PKGs created by other activities (NSS)

  6. What is CMF ? • NiceFC, but not only for “Controls” • Motivation • Re-use of centrally provided packages • 2 different technologies would require double investment and maintenance on IT-IS side. • Today we provide already some custom support to local administrators using the central desktop technology • Locally managed AB-CO Consoles in the PCR • Application deployment support for CAD PCs • Levels of extension • A general solution for any service provider at CERN, including Public PCs, CAD Workstations, Microcosm, … • A general solution also for the “standard service” (NICE) • NICEFC extended : CERN Computer Management Framework (CERN CMF) • Presented at POW 2006

  7. CMF Principal Functionality • Delegation to Locally Managed computer groups • The NSC administrator decides what and when to deploy • Receives email for centrally deployed packages • Eg. critical updates • Delegation possible on all levels • Packages • A PKG defines the action to perform • Application & patch Management • MSI recommended but can be setup.exe, .vbs items • Support for multiple items/package • Policy Settings • Eg. Logon restrictions, accessibility & control limitations • Execution of Scheduled Tasks

  8. CMF Principal Functionality • Package deployment (cont’d) • Deployment criteria • Postpone, not logon preference, forced • WMI based & custom criteria • Dependencies • Add/Remove web-based interface • “Allowed” packages appear in the web based interface • Can be selected by the user • Will be automatically re-installed after a OS re-installation

  9. CMF Secondary Functionality • Software Metering • Based on a list of executables to monitor • Software Inventory • Dump of all installed software • Hardware Inventory • Based on a list of items to monitor

  10. CMF Architecture • Web based User Interfaces for administration • Except for Policy Settings • Native MS GP Editor but fully integrated in CMF • Central Database • Configuration data from admin UIs • Global & detailed reporting Data • Distributed Client Repository (2 servers at present) • Configuration files and client feedback • Ensures Scalability • Client Service (CMFAgent) • Running on each participating Windows PC • Performs the appropriate actions and sends reports back to repository

  11. Demo • The “Management Framework” is available at http://cern.ch/cmf

  12. Questions ?

More Related