ANSE: Advanced Network Services for Experiments
• Institutes:– Caltech (PI: H. Newman, Co-PI: A. Barczyk)– University of Michigan (Co-PI: S. McKee)– Vanderbilt University (Co-PI: P. Sheldon)– University of Texas in Arlington (Co-PI: K. De)
• Presented by: Artur Barczyk [email protected], or [email protected] • “Network Integration and Applied Innovation” program area
– Integration of advanced network developments from previously funded projects with the mainstream applications in use in the LHC and other research communities
• Focus on LHC, pave way for others to use same/similar approach• Main thrust: integrate advanced networking tools and services with the software
stacks of the LHC experiments– LHC software: PanDA in ATLAS, PhEDEx in CMS– Networking services/tools:
Dynamic circuits (DYNES, ION, OSCARS) and Monitoring (perfSONAR and MonALISA)• Strategic planning of workflow including network capacity, as well as CPU and
storage capacity as a co-scheduled resource• Working with the main workflow management developers and operations staff for
deterministic, worldwide distributed workflow in both CMS and ATLAS, in ANSE
ANSE - Relation to DYNES• In brief, DYNES is an NSF funded project to deploy a ‘cyberinstrument’
linking up to 50 US campuses through Internet2 dynamic circuit backbone– based on ION service, using OSCARS technology– Use of OpenFlow, through Internet2’s OS3E network, being
considered/tested• DYNES instrument is intended as a production-grade ‘starter-kit’
– comes with a disk server, inter-domain controller (server) and FDT (transfer application) installation
– FDT code includes OSCARS IDC API -> reserves bandwidth, and moves data through the created circuit• “Bandwidth on Demand”
• The DYNES system is naturally capable of advance reservation– But we need the right agent code inside CMS/ATLAS to call the API
whenever transfers involve two DYNES sites
• Btw - DYNES is entering production-readiness in 2013 (now)
SDN Deployment at Caltech• ANSE is a SW development project, but will make use of infrastructure
deployed as part of the DYNES instrument– This slide shows Caltech installation only! – Installation at other DYNES campuses varies
• see http://dynes.internet2.edu for details• DYNES/ANSE @ Caltech:
– 1 IDC server– 1 data server– 1 switch (future: OF-capable)
• earlier SDN installation, aka DCN testbed
Outlook etc.• Currently, there is no GENI deployment at Caltech• The HEP group is investigating potential installation of a GENI rack
– Intended use case: network R&D for HEP data distribution
• The HEP Networking group at Caltech is active in SDN R&D: – OLiMPS (Openflow Link-layer Multipath Switching) project
funded by DOE-OASCR
• Contact:– Artur Barczyk (HEP networking group), [email protected]– Harvey Newman, [email protected]
Recommended
