Skip to end of metadata
Go to start of metadata

Purpose of LSST Long-Haul Networks

Provide reliable connectivity of sufficient bandwidth between all LSST Observatory sites (Base, Archive, Headquarters, Data Access Center, Satellite Processing, and Camera sites) to meet operational requirements.


Network Engineering Team

Per the LSST Network Operations and Management Plan, the overall architecture, engineering, testing, operations and maintenance of the LSST Networks are assigned to the Network Engineering Team (NET) under the direction of the LSST Network Architects and LSST Management.  The NET is formed of project/observatory and network provider technical staff.  The current members of the NET are:

Members:


Guests

Network Engineering and Testing Mailing List

The LSST networks are being engineered and tested via a distributed team with representatives from the LSST project, as well as the sub-award partners providing networks, and their subcontractors.  In order to facilitate communications among this team, a mailing list has been created and all people working on LSST Networks should subscribe to this list:

LSST-End-To-End mailing list

The Network Engineering Team is a subset of this list, and has a dedicated NET list:

LSST NET mailing list


Network Engineering Team Meetings

The NET meets monthly at 0800 PT in an online meeting on Blue Jeans Meeting ID: (varies with meeting, see meeting page.

Past meeting notes are linked below.


Specifications and Design Documents

Note: due to historical reasons, access to the baseline versions of linked documents below requires an LSST login to get into docushare.  Jeff Kantor will keep the most current baselined versions linked.

Data Management System-level network specifications (extracted from LSE-61 Data Management Subsystem Requirements)

180 days MTBF/year

48 hours MTTR/year

Base to Archive nightly data volume (science images and meta-data): 15TB

        Amount of time available to transfer data from Mountain to Base to Archive:

                 Crosstalk-corrected images for Alert Production: 6 seconds to move (between 2.6 - 12.4 Gbytes depending on compression)

                 Raw images: 24 hours

Note, there is also Observatory Control System and other operational data transferred at night, and there is daytime engineering and calibration traffic potentially at the same volume.  Finally, there is periodic data transfer from the Archive to the Base, primarily as a result of annual Data Release Processing.  All the data flows and allocated bandwidths are defined in the following documents.

A grouping of this traffic for purposes of network design, QoS, prioritization etc. is on the LSST Network Traffic Types.

A bandwidth allocation by link of this traffic for purposes of network design, QoS, prioritization etc. is on the LSST Bandwidth Allocation.

The LSST Long-Haul Networks are further specified in LSE-78 LSST Observatory Network Design

The budgeted cost and schedule of deployment of links and bandwidth, and their utilization is documented in LDM-142 Network Sizing Model

The requirements for the Summit Network are in LTS-577 Summit Network Specification

In addition to the top-level documents above, there are documents describing how the LSST Networks are to be tested, verified, and managed:

The LSST Network End-to-End Test Plan defines the plan for development testing and monitoring the LSST networks.

The Vera C. Rubin Network Verification Baseline defines the plan for formal verification of the LSST Networks

The LSST Observatory Network Verification Plan defines plan for formal verification of the LSST networks.  OBSOLETE, SUPERCEDED BY LDM-732 and JIRA LVV Project

The LSST Observatory Network Verification Matrix defines requirements and methods for formal verification of the LSST networks. OBSOLETE, SUPERCEDED BY LDM-732 and JIRA LVV Project

The LSST Network Operations and Management Plan  defines the plan for operating and maintaining the LSST networks as a single integrated process.

Pages and other documents related to LSST Long-Haul Networks

Quick Display Action Items

DescriptionDue dateAssigneeTask appears on
  • Julio Ibarra , Aluizio Hazin - Define where back to back transponders will be, describe abbreviations, addresses, etc. on RNP terrestrial Santiago - Sao Paolo  
21 May 2019Julio Ibarra2019-04-18 Network Engineering Team Meeting notes
  • Julio Ibarra , Aluizio Hazin - Provide physical address, who is responsible for cross connects for infrastructure for LSST outside RNP network  
21 May 2019Julio Ibarra2019-04-18 Network Engineering Team Meeting notes
  •  Matt Kollross , Vincenzo Capone Lead development of documentation of Disaster Recovery and distributed Data Release processing-driven network requirements and NCSA - CC-IN2P3 implementation for LSE-78 (or new LSE-xx document   
10 Oct 2019Matt Kollross2019-09-12 Network Engineering Team Meeting notes
  • Albert Astudillo , Julio Ibarra , Matt Kollross , Vicenzo Capone - Impact analysis if we adopt IETF standard for VNOC.  Can you produce this format?  If not, what can you produce that could be transformed to this format? Look at all active resources supporting LSST, how to report in human-readable format  
14 Nov 2019Albert Astudillo2019-10-22 Network Engineering Team Meeting notes
  • Matt Kollross Work with IN2P3, RENATER, GEANT on default plan going via CANARIE - Amsterdam, produce diagram of paths (primary, secondary).  Define: What MOUs do we need in place?  Is this addition to LSST - IN2P3 MOU?  Do we need to pay CANARIE ($ or other)  
14 Nov 2019Matt Kollross2019-10-10 Network Engineering Team Meeting notes
  •  Matt Kollross, Stuart McLellan Memo that NCSA and RENATER as members of internet2/GEANT can use all ANA circuits with no cost.  
12 Dec 2019Matt Kollross2019-11-14 Network Engineering Team Meeting notes
09 Jan 2020Ron Lambert2019-12-19 Network Engineering Team Meeting notes
  •  Albert AstudilloSend network configuration to Stuart McLellan, Richard Hughes-Jones for comparison/debugging Coriant/Infinera 100G issue  
16 Jan 2020Albert Astudillo2020-01-09 Network Engineering Team Meeting notes
  •  Richard Hughes-Jones read LSE-78, schedule meeting with Matt Kollross, Stuart McLellan to get up to speed on NCSA - CC-IN2P3 plan  
16 Jan 2020Matt Kollross2020-01-09 Network Engineering Team Meeting notes
16 Jan 2020Jeronimo Bezerra2020-01-09 Network Engineering Team Meeting notes
  • Jeronimo Bezerra , Paul Wefel confirm implementation of 2 x 100G in October, 2020 (without dedicated wave from Boca - Atlanta)  
26 Mar 2020Jeronimo Bezerra2020-03-12 Network Engineering Team Meeting notes
26 Mar 2020Julio Ibarra2020-03-12 Network Engineering Team Meeting notes
  • Jeff Kantor Provide DRP size curve from DM sizing model to GEANT/RENATER.   
26 Mar 2020Jeff Kantor2020-03-12 Network Engineering Team Meeting notes
  •   Julio Ibarra circulate GlobalNOC questionnaire to other operators to add their responses.  Jeff Kantor collect responses, notify GlobalNOC about meeting in June (after review).   
16 Apr 2020Julio Ibarra2020-04-09 Network Engineering Team Meeting notes
  •  Jeronimo Bezerrawill add description of nightly testing to E2E Test Plan (we will refer to it in Tech document).   
23 Apr 2020Jeronimo Bezerra2020-04-09 Network Engineering Team Meeting notes

  • No labels