1 / 15

Update on GÉANT BoD / AutoBAHN LHCONE Workshop: Networking for WLCG - CERN

Update on GÉANT BoD / AutoBAHN LHCONE Workshop: Networking for WLCG - CERN. Tangui Coulouarn, DeIC 11 February 2013. AutoBAHN and the GÉANT BoD Service. AutoBAHN is a provisioning system used in the GÉANT BoD Service

merrill
Download Presentation

Update on GÉANT BoD / AutoBAHN LHCONE Workshop: Networking for WLCG - CERN

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. Update on GÉANT BoD/AutoBAHNLHCONE Workshop: Networking for WLCG - CERN Tangui Coulouarn, DeIC 11 February 2013

  2. AutoBAHN and the GÉANT BoD Service • AutoBAHN is a provisioning system used in the GÉANT BoD Service • Some NRENs co-offering the GÉANT BoD service use other provisioning systems • The software provisioning circuits is one component of the service along with: • Monitoring • Multi-domain technical support • Procedures • AAI • Cost-sharing and billing • User outreach and support, etc.

  3. Agenda • Update on AutoBAHN • Update on the GÉANT BoD Service

  4. AutoBAHN basics • AutoBAHN allocate network bandwidth to users/applications both immediately and in advance. • 3 modules in AutoBAHN: InterDomain Manager (IDM), Domain Manager (DM) and Technology Proxy (TP) • Supported networking equipment: • Equipment working under Bluenet Tool/Ans Tool (Cisco routers supporting AToM - 760x, 3750, 3500) • Brocade (Foundry) Network NetIron 8000 (EoMPLS) • Juniper MX80, EX4200 (Eth, EoMPLS) • Equipment working with Junos Space (currently used with Juniper Networks MX Series 3D Universal Routers) • Alcatel MCC 1678 (SDH) • IntuneNetworksVerisma iVX8000 (OPST - OpticalPacketSwitched Transport) • DLink3450 (Eth)

  5. NSI v2.0 compliance • AutoBAHN, apart from its native protocol, can also handle other BoDprotocols. • IDM in AutoBAHN was IDCP compliant and we had a translator to NSI v1.0 • IDM rewritten so AutoBAHN 3.0 natively supports NSI v2.0 (r117) and no longer supports IDCP • Release date of AutoBAHN 3.0 planned for 17 March 2014 • Alpha2 was released yesterday • Beta 17 February • Early testing with different NRENs • Only IDM module modified (not DM and TP)

  6. Access to AutoBAHN • Web GUI • API • User Access Point (UAP) interface which allows sending of requests, the retrieval of available ports, the retrieval of reservations status, etc. WebGUI uses this method to communicate with IDMs • Administration interface has methods for retrieving logs, services/reservations lists, configuration properties and intradomaintopology information. So Administration is needed in addition to UAP for more advanced Client Platforms (for example the BoD Portal uses both interfaces) • NSI CS v2.0 interface IDMs communicate via this interface as may other clients/apps

  7. API Access

  8. API Access with NSI v2

  9. JIRA to follow development process:https://issues.geant.net/jira/browse/ABAHN • FORGE for technical documentation:https://forge.geant.net/forge/display/autobahn/Home

  10. Update on GÉANT BoD Service • Essential elements in scope for this presentation • Footprint • Monitoring • Procedures, trouble-shooting • Essential elements but not in scope for this presentation • Cost-sharing • AAI • User outreach

  11. Footprint • ESNet/Internet2 • Peering up since August 2013 • Need to work on procedures for trouble shooting • NSI opens perspectives as shown by AutoGOLE/GLIF demos

  12. Monitoring • Control plane solutions already working (NagiosPythonSOAP client plugin, Nagios Service Check Acceptor (NSCA), Nagios Remote Plugin Executor (NRPE), Icinga) • cMON developed as an extension of PerfSONAR to monitor circuits • cMON works already for static circuitsFor dynamic circuits, it is currently being piloted by HEAnet, GRnet and GÉANT • SNMP traps or polling sent by cMON agents to HQ • Communication between cMON and AutoBAHN

  13. cMON D Pilot

  14. Procedures and trouble-shooting • Provisioning of circuits within the framework of the service • Multi-domain Service Desk for troubleshooting and procedures to follow • Still very much ad hoc solutions with other services: need to progress

  15. Thank you!

More Related