Managing Work in the New Computing Environment March 14, 2003 Will Dower Implementation Review

Implementation Review Overview Workgroup Access Control Philosophy Introduce workgroups moving to the new backend architecture Map workgroup interactions on the current system Map workgroup interactions onto Sun Fire 15K domains Workgroup Implementation Challenges Prescription for Meeting Workgroup Challenges Implementation Review

Workgroup Access Control Philosophy Access to Server and SAN resources should maximize the useful work accomplished irrespective of artificial organizational boundaries. Access to Server and SAN resources should minimize risk to all users of the entire system and to the STScI and its computing partners. Implementation Review

STScI Data Processing Work Groups Operations and Data Management Division (ODM) Science Data Processing (OPUS) Engineering Data Processing System (OPUS) Data Distribution (DADS & OTFR – database server ZEPPO) Archive Ingest (OPUS & NSA – database server CATLOG) Engineering and Software Services (ESS) Software development and testing (database server ROBBIE) Database development and management Instruments Division (INS) Calibration plan development and execution Data analysis and calibration reference data production Center for Process and Technology (CPT) Computer infrastructure support System administration Security These are organizational groups within STScI that have functional aspects that will be moved to the Sun Fire 15K. Implementation Review

Implementation Review ODM functionality from previous slide superimposed on current operations environment slide INS functionality is in upper right of slide. Current Architecture Implementation Review

Implementation Review Functionality from ESS from previous slide superimposed on current diagram of testing/development environment. INS functionality is in the upper right of slide. Implementation Review

Sun Fire 15K Nominal Domain Layout Function Division CPUs Memory/ I/O A Development, Calibration Reference Data ESS 8 32/1 B DADS,OPUS,OTFR ODM 20 80/2 C I&T 80/1 D CATLOG DB 16/2 E ZEPPO DB 4 8/2 F Development DB 8/1 G Upgrades, Patches CPT 16/1 Slide showing how functions and owners relate to 15K domains. Implementation Review

Workgroup Implementation Challenges – Sun Fire 15K Resources within a domain are shared by tasks in the domain Processors and memory within a domain can be reserved for high priority tasks Operations can suspend or modify data flow within a domain to fine tune performance of various systems. CPT can reallocate resources between domains to clear bottlenecks and for pre-scheduled activities. Upgrades and build deployments Performance Testing Clearing Backlogs Establish a working-level group to oversee transitions Resource utilization within each domain must be shared. Items in green represent work practices that are analogous to current practices established to share a “single domain” server. The item in red represents new work practices made possible by 15K architecture. Utilizing these 15K features are important to improving uptime and to accurate performance testing, Implementation Review

Clearing Backlogs Domain Layout Function Division CPUs Memory/ I/O A Development ESS 4 16/1 B DADS,OPUS,OTFR ODM 40 160/2 C I&T D CATLOG DB 8 16/2 E ZEPPO DB 8/2 F Development DB 8/1 G Upgrades, Patches CPT Slide showing domain resources to support clearing an operational backlog. Develop/modify work practices as part of the requirements development process for this project. Implementation Review

Workgroup Implementation Challenges – EMC SAN EMC disk storage is mounted to particular domain (each domain has its own set of HBAs) and available to accounts within that domain. Clustered volumes (Sun Disk Suite, Veritas, NFS) can be set up for shared access between domains, providing simple, reliable data interfaces. Movement of new software from development, to testing, to operations is accomplished via tightly controlled configuration management accounts. Use of business continuity volumes to increase database and system uptime. Automated Backups, mirroring. Items in green represent work practices that are analogous to current practices established to share a “single domain” server with local attached storage. Item in red represent new work practice made possible by the BCV and point-in-time backup features of the EMC. Work practices will be developed as part of the requirements development process. Implementation Review

Meeting New Workgroup Challenges Strong systems engineering approach System Requirements Analysis: any combination of: Operations Concept Document Architecture Document Requirements Document System Design/Project Management Plan Development and System Testing User Acceptance Testing Operational Readiness/Deployment Review Lessons Learned Standardized process that can be tailored and applied to software development as well as development of new work practices. Implementation Review

Sun Fire/EMC Workgroup Practices Development Reviews Review Panel Consists of Division Management, CIO, CPT Management, HST Mission Office, & key technical personnel. Following Reviews will be completed: Workgroup Management Design Review Workgroup Practices Test Readiness Review Acceptance Review Bi-Weekly Status Reviews Implementation Review

Requirements Development Requirements Analysis leads to Operations Concept Document based on Use Case scenarios for the new hardware architecture; e.g. Reconfiguration of domains to support performance testing Performance of database upgrades with zero operational downtime Software build delivery to operations domain and subsequent activation. Multi-disciplinary team based approach used for OCD development. Implementation Review

Use Case Development Team Formation Members selected based on skill sets from divisions within the Institute that will be working on the server. In many cases team members have cross-divisional experience. The team was reviewed and approved by Division Management. Methodology: Online Survey for Stakeholders in each Division Conduct Use Case interviews with survey participants (where needed) to clarify responses and resolve conflicts. Use Operations Concept Document as input for Sun Fire 15K Application Readiness Service. Implementation Review