IT Team and IT Related Meetings Jeffrey Kantor LSST IT Sr. Manager LSST Project and Community Workshop 2018 August 13, 2018 #lsst2018 #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 1
Agenda IT Team Background and Context • IT-related coordination Teams and Meetings • Summit – Base Information Technology and Communications Tiger Team (SBTT) • Information Technology Services Committee (ITSC) • Information Technology Security Team (ITSec) • LSST Network Engineering Team (NET) • NCOA IT Working Group (NCOA ITWG) • Slides cover (not all will be presented): • Charter and members • Accomplishments • Future • Ways to interact with the team • #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 2
IT Team Integration – Steve Kahn email 20180409 “We are therefore evolving the existing IT reporting structure so that the teams in Tucson and in La Serena report to a single manager who will • report to Victor Krabbendam. This new IT manager will be responsible for the traditional Project IT services in both the North and South as well as the IT development work for both the Telescope and Site and the Data Management groups. This single IT group will be well positioned to transition into operations and to interface efficiently with the NCOA IT department forming soon. Jeff Kantor will be appointed the Interim Manager of the LSST IT group. Iain Goodenow will continue to lead the group in Tucson and Luis Corral will lead the group in La Serena.” Single functional organization, process, standards • Consult/Consent, Inform/Act process • JIRA (IT Support (Help Desk), IT Projects) • Confluence (documentation …) • Consistent execution of LSST/AURA processes with IT tasks (onboarding, IT • Security, …) irrespective of site Responsible for all LSST project office-provided, supported services irrespective • of site Weekly coordination meetings on Fridays 9am PT • #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 3
PMO Task – Victor Krabbendamemail 20160524 Need vehicle(s) to support LSST MREFC Project on “all things ITC” • Act as “consultant” to PMO and project (hardware and software • deliverables remain responsibility of subsystems) Task 1: Ensure Summit – Base Complex is optimally designed/engineered • to avoid ITC gaps, redundancies, inefficiencies (SBTT) Task 2: Ensure consistency of life cycle management and support of all IT • Services during MREFC project and as foundation for operations (ITSC) Address IT Security • #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 4
Task 1: Summit – Base Complex Integrity We need to engineer the Summit – Base Complex as one ITC entity, with • a consistent, coherent design This cuts across subsystems that contribute facilities, equipment, • software, operational policies and procedures Many point-to-point communications and some workshops had tried to • address various aspects of this as the subsystems have tried to do the work required in their “silos”, but… We needed a more integrated approach to achieve the goal in time for • early integration and through end of commissioning. This was chartered in the form of a cross-subsystem “tiger team”, with a • defined set of deliverables, a plan/schedule to provide them, and a T/CAM to track this and report on it #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 5
Summit – Base ITC Design We agreed we need Summit – Base ITC Design document(s) that are • subsystem agnostic in terms of who delivers what and where it resides, and focus on: End-to-end data flows and processes • Partitioning/allocation of responsibilities for above into logical nodes (e.g. • “commissioning cluster, diagnostic cluster, image buffer, etc.) Full definition of interfaces between nodes (expand ICDs as necessary) • Mapping of logical nodes to physical ITC infrastructure(DAQ, DWDM switch, • etc.) and location (Summit, Base, both) Designs for cross-cutting services (e.g. System Time, Security, Network(s), etc.) • AND ONLY AFTER THAT • Mapping of the above to WBS elements and subsystems providing the • implementation of the design #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 6
SBTT Charter and members The SBTT is a cross-subsystem team empowered to make technical decisions to optimize • Summit Base ITC as an integrated system, i.e. not silo'ed by WBS. Members: • • Gregory Dubois-Felsmann(DM/SE) • Mike Huffer (Camera DAQ) • Tony Johnson (Camera CCS) • Jeff Kantor (PMO TCAM) • Ron Lambert (DM/TS) • German Schumacher (TS OCS/TCS/Integration) • Kian-Tat Lim (DM/SE) • Michelle Butler (DM) • Alexander Withers (ISO) • Iain Goodenow (PMO/ITS) • Chuck Claver (SE/Commissioning) • Dave Mills (TS OCS/TCS) • Andres Villalobos (DM/TS) • Luis Corral (DM/TS) - Note: Members are the only people who are given assignments; they are expected to reach out to others on the project as necessary to achieve their assignments. #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 7
SBTT Accomplishments • A wide range of design elements of the Summit – Base ITC design have been addressed as captured in Confluence, JIRA, and numerous documents • Many active development tasks (configuration management with Puppet for SB complex and Pathfinders, integration with IT Security and Identity Management, …) • All of the TT proceedings are captured in weekly meeting minutes • The overall design decisions/recommendations are documented in LSE-309 Summit – Base ITC Design Document • LSE-309 was approved to establish initial baseline version • The current version is stable with respect to the overall complex, the Summit, and the Summit – Base Network, which are already in construction/equipment procurement and deployment • An LCR will be prepared by the end of CY18 to expand to full coverage of the Base, to support FY18 -19 construction/equipment procurement and deployment • LSE-299 Summit Computer Room Requirements was developed, imported into Magic Draw, updated, and baselined • Subsequent LCRs approved to update LSE-299 based on construction experience, events • LSE-239 Base Facility Data Center Requirements was imported into Magic Draw, updated, and baselined • Subsequent LCRs approved to update LSE-239 based on construction experience, events #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 8
SBTT Future The Tiger Team started in the last quarter of FY16, and has continued • through FY18 to accomplish Task 1 The Tiger Team has fulfilled its primary mission when: • LSE-309 is baselined with the entire complex covered • The methods and timeline for implementation and verification are • defined and accepted by the PMO, SE, and the subsystems The current intent is to disband the Tiger Team at that time and transfer • responsibility to System Engineering and Commissioning Teams Any future architecture and design work and modifications to this • document are expected to be a function of the LSST System Engineering team. #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 9
Ways to interact with the SBTT • We have a slack channel • We publish weekly meeting agendas and minutes in confluence • We invite topical experts to meetings when something of broad interest is covered • You can contact us via any project-standard vehicle, including JIRA issues, weekly management meetings, etc. • We all represent our respective project organizations, feel free to contact your SBTT member by any means you find convenient #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 10
Task 2: IT Services Life Cycle Management We have many entities (subsystems, SE, SQuARE, PMO) selecting, • purchasing, deploying, supporting, upgrading, and retiring IT Services for the MREFC project We don’t have good vehicles for keeping everyone informed about all the • services: who provides them, how to get support, are other groups planning something similar or have done something that can be leveraged, etc. There are no internal “service levels” defining what level of service and • support can be expected Many point-to-point communications and “local” channels have been set up • to to address various aspects, but… We needed a more integrated approach to achieve the goal of optimal • management and support This was chartered in the form of a broad representative committee and a • process #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 11
ITSC Ecosystem and Roles Service Users LSST PO LSST Subsystems LSST Corporation LSST Science Collaborations LSST Community Strategy Governance Coordination Service Providers LSST ITS LSST SQuaRE NCSA -------------------------------------------------------------------- NOAO (N & S) University of Arizona Commercial Service Providers #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 12
Recommend
More recommend
