1 / 5

OIS Module Responsibilities Feedback Insights

Feedback and concerns regarding responsibilities in managing central services - addressing staff knowledge gaps, testing environments, migration issues, and client support.

henrietta-jordan
Download Presentation

OIS Module Responsibilities Feedback Insights

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. OIS Feedback on Module Responsibilities Tim Bell 18th December 2013

  2. Understanding • Central services are responsible for the client configuration in the computer centre independent of operating system or technology • Based off the tables in https://twiki.cern.ch/twiki/bin/viewauth/AgileInfrastructure/ModuleOwnershipProposal OIS Module Responsibilities Feedback

  3. Concerns • Staff running a central service run on Windows don’t have the knowledge of Linux • And vice versa • Example: Shibboleth on Linux • Example: TSM client on Windows • Responsibilities increase for some of the central services .. Staff relocation from where there are savings ? • Example: Authentication and Authorization now has to look after 5 modules compared to 0 previously OIS Module Responsibilities Feedback

  4. Concerns (II) • Is the QA environment strong enough ? • Can we model all variants of usage of Apache in the QA environment and continuously test it frequently enough ? • Who is responsible for gaps ? Bad testing by configuration responsible or missing QA by service manager • Some configurations are really complicated and sensitive (e.g. Drupal).. can we have our own module if we wish? • Major version transitions still a problem • Simultaneous change of client and server with code may be needed for incompatible upgrades OIS Module Responsibilities Feedback

  5. Concerns (III) • Handling the dynamic clients • Example: ‘Bob’wants Postfix not Sendmail as her mail agent so Mail teams needs to support Postfix if ‘Bob’find someone else who wants it too • Example: Bob want to use rsyslog on Windows, now Linux support has to enhance the module ? • Who is responsible for migrations if a total module change is needed ? • Example: Find out that we chose the wrong one on puppetforge and all clients need to migrate • Client Support is implied by Client Configuration • Example: Service manager says it is a configuration problem and hands it over • Responsibilities aren’t so clear cut • Example: nscd? Httpd? • Example: sendmail? • Example: Everything in Linux ? OIS Module Responsibilities Feedback

More Related