1 / 12

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

ARCHSTONE MX- TCE Development Update The ARCHSTONE Project Meeting January 28 th , 2011. 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

feivel
Download Presentation

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

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. ARCHSTONE MX-TCE Development Update The ARCHSTONE Project Meeting January 28th, 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 Topology Bridge LookupService AuthN 3: Get Topology 2: PCE Request withConstraints • Coordinator 1: User Request MX-TCE PCE WBUI 4. ARCHSTONE NSI via MX-TCE Binary API 6. Result Topology (Path) Conversion and Setup AuthZ MX-TCE Core 5. Path Computation and Reply to Coordinator PSS Resource Manager IDCP API 3

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

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

  6. MX-TCE Implementation Overview 6

  7. Current Status • mxtce-sw svn: http://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 Topology Bridge LookupService AuthN • Coordinator PCE WBUI AuthZ PSS Resource Manager IDCP API 9

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

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

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

More Related