1. ARCHSTONE MX-TCE Development Update The ARCHSTONE Project Meeting January 28 th, 2011

2. Development Goals Targeted timeframe: Now through end of May 2011 (4 months). Develop capabilities for MX-TCE to integrate into OSCARS 0.6 as a PCE Service. – Fully compatible with OSCARS 0.6 PCE-WS API – Capability to take topology feed from OSCARS 0.6 Coordinator Service and compute an end-to-end path under connectivity, bandwidth and VLAN etc. constraints Develop capabilities for MX-TCE, as a standalone topology computation engine, to have initial advanced features – Capability to retrieve topology and scheduling data from external sources (initially the OSCARS 0.6 services) – Capability to answer simple What-If questions from applications such as TeraPaths. For example, what schedules are available for a 2-hour, 1Gbps circuit between A and Z in next 24 hours? What other time-bandwidth combinations will give me 2 Gbps-hours total capacity? 2

3. OSCARS 0.6 PCE Compliance Demo Notification Broker AuthN Resource Manager Coordinator MX-TCE PCE Topology Bridge IDCP APIPSS Lookup Service AuthZ 3 WBUI 1: User Request 3: Get Topology 2: PCE Request with Constraints MX-TCE Core 4. ARCHSTONE NSI via MX-TCE Binary API 5. Path Computation and Reply to Coordinator 6. Result Topology (Path) Conversion and Setup

4. Advanced Feature Demo Topology Bridge AuthZ ? MX-TCE Core Resource Manager Lookup Service TEDBMan PolicyMan ResvMan OSCARS 0.6 SOAP Services 1: RT { A-Z; bw=500M~1G; vlan=any, time:0-24hr} Give me the best 5 schedule. 4: ST {list of 5 path options} bw high-low: nearest time first 2: Assign to ComputeThread X 3. Return results via NSI API 4 NSI API

5. Advanced Feature Demo Topology Bridge AuthZ MX-TCE Core Resource Manager Lookup Service TEDBMan PolicyManResvMan OSCARS 0.6 SOAP Services 5: RT {path option #1} and {path option #2} are both acceptable. Reserve either for me. 8: Your reservation has been made. Here is detailed ST{…}. 6: Assign #1 to ComputeThread Y and #2 to ComputeThread Z 7: Reserve path #1 if successful, otherwise #2, or return failure 5 NSI API

6. MX-TCE Implementation Overview 6

7. Current Status mxtce-sw svn: http://hpn.east.isi.edu/svn/mxtce-swhttp://hpn.east.isi.edu/svn/mxtce-sw Software infrastructure in place: logging, exception, event handling, multi- threading, message routing, action and workflow base classes. Binary API server done testing of message routing with core thread. Message formats implemented. Realistic contents TBD. Straw-man TEDB manager, Resv Manager and Policy Manager threads started. Only for testing multi-thread messaging. An example ComputeWorker (thread) has been implemented for testing multi- thread messaging and workflow prototyping. Workflow has straw-man Actions: Process_RequestTopology, Create_TEWG, Compute_KSP, Finalize_ServiceTopology. Feng Gu is working on the MX-TCE WS process. An OSCARS 0.6 PCE compatible module is ready for testing. Need to modify to keep up with latest OSCARS code changes. 7

8. February-May 2011 Work Plan Feng will finish PCE WS module. Convert OSCARS request/reply to/from MX-TCE API messages. Then move on to finish the Binary API Server to get proper internal messages sent to core thread. Xi will implement an OSCARS-PCE-alike ComputeWorker thread. It parses topology and constraints fed from PCE WS and run path computation. Xi will also implement a proof-of-concept advanced-feature ComputeWorker thread with workflow to pull topology and scheduling data from OSCARS services and run more sophisticated path computation. Implementation of TEDB Manager and Reservation Manager that retrieve data from OSCARS topologyBridge and resourceManager respectively. They also preprocess the data and provide TEWG to computeWorker threads upon request via inter-thread message routing. -- Xi (and Feng?) The above should be done by early May and then we can test the code with demo applications. 8

9. OSCARS 0.6 Architecture Notification Broker AuthN Resource Manager Coordinator PCE Topology Bridge IDCP APIPSS Lookup Service AuthZ WBUI 9

10. Basic OSCARSv6 PCE Functions Coordinator Connectivity PCE Connectivity PCE Bandwidth PCE Bandwidth PCE Dijkstra PCE Dijkstra PCE VLAN PCE VLAN PCE Topology Bridge 1,6 2 3 4 5 10

11. Extended OSCARSv6 PCE Functions Notification Broker AuthN Resource Manager Coordinator Topology Bridge IDCP API PSS Lookup Service AuthZ WBUI 11 Additional Study Needed ??? PCE ??? PCE ??? PCE ??? PCE ??? PCE ??? PCE ??? PCE ??? PCE NSI API MX-TCE PCE MX-TCE PCE

12. Extended OSCARSv6 PCE Functions Notification Broker AuthN Resource Manager Coordinator Topology Bridge IDCP API PSS Lookup Service AuthZ WBUI 12 Additional Study Needed ??? PCE ??? PCE ??? PCE ??? PCE ??? PCE ??? PCE ??? PCE ??? PCE NSI API