1 / 14

FIO/OPT in LCG project

FIO/OPT in LCG project. Bill Tomlin (LCG post) re-enforcing the section Analysis, design and architecture background Windows skills State Management project Administration of FIO/LCG Web site http://cern.ch/it-div-fio-lcg/. State Management. What are our goals ? What is our approach ?

briar-maldonado
Download Presentation

FIO/OPT in LCG project

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. FIO/OPT in LCG project • Bill Tomlin (LCG post) re-enforcing the section • Analysis, design and architecture background • Windows skills • State Management project • Administration of FIO/LCG Web site • http://cern.ch/it-div-fio-lcg/

  2. State Management • What are our goals ? • What is our approach ? • Where are we now ?

  3. What are our goals (1) ? • Easy Control of every system installed in the Computer Center (hw and sw) • Automatic installation procedures and tools. Will rely on well-defined workflows to trigger and follow changes for machines in the CC : • Hw installation (from order to production), move and de-installation • Sw configuration, installation and changes • Visualisation tools to • Get machine individual parameters : location, hw status, sw configuration, etc • Display current and planned snapshots of (part of) the CC • Track progress trough workflows

  4. What are our goals (2) ? • High-level and easy-to-use tools • Able to cope with large number of systems • Based (when possible) on existing technology (Web interface ?) • Benefiting from our installation/configuration experience • What can we valuably re-use from our current procedures/tools ? • What will or will not scale ? • What should be replaced/improved in view of automation and massive installations ?

  5. Strategy • High Level Tasks: • Analyze existing workflows • Identify issues • Establish requirements for improved workflows, tools • Prototype • Implement • Test • Project Lifecycle • Incremental and iterative - not waterfall • Activities in parallel • Expect prototyping to overlap high level analysis

  6. Analysis • Top-down use case driven approach • A use case diagram shows interactions between external users and a system • Identify high level use cases • For each use case • Describe high level workflow • Describe each activity in detail • Describe alternate workflows • In parallel • Record issues • Record ideas for improvement

  7. H/W Use Cases

  8. Order PCs workflow

  9. Order PCs workflow - detail

  10. Responsibility User Preconditions ·User has budget authorisation Basic Flow 1.User logs in to EDH (Electronic Document Handling system) 2.User completes a material request form 3. clicks ‘Send’ Alternatives 1a Web Request Form Used: 1.User accesses the FIO/CH web site 2.User selects online catalog and ordering system 3.User selects Farm PC (TODO: disk server ? engineering PC ? network printers in Computer Centre ?) and adds to shopping basket 4.User clicks ‘Creates Order’ 5.User logs in to EDH and a pre-populated EDH material request form appears 1b User orders hardware directly: 1.User requires non-standard equipment (possibly routers, tape drives, disk trays) or is unaware of the ordering process so proceeds directly to order through a supplier or thro SPL  FIO unaware Activity Detail:

  11. Progress • Familiarization of activities in FIO • Decided overall strategy • Hardware use case analysis • Hardware high level workflows for • Order PCs • Request Hardware Repair • Request Hardware Disposal • Begun writing H/W requirements • S/W analysis has started – early days

  12. Next Steps • Complete hardware high level workflows • Complete detailed analysis for Order PCs • Requirements and prototyping for hardware installation • Complete H/W detailed analysis • Software analysis – in discussion with IS • Put analysis on FIO LCG web site

  13. When ? Good Question… …don’t quote me

  14. Final Comments • Early stages – still many questions • Current work needs verifying – must be accurate • Analysis will be available on FIO LCG web site • http://it-div-fio-lcg.web.cern.ch/it-div-fio-lcg/ • Welcome ideas, constructive criticism, input and feedback on any aspect

More Related