Starting Time: Nov 5, 2009 at 1:00 PM, US/Eastern
If you only want to participate in the audio conference, you may dial in with the following numbers:
Call: +1-734-615-7474 (Please use if you do not pay for Long Distance) or +1-866-411-0013 (toll free US/Canada Only)
Enter access code: 0187242
New meeting time: Thursdays at 1PM Eastern. Will aim for bi-weekly, but calls will be sporadic till the end of the year.
Not a lot in attendance (Martin, Jason, Aaron, Andy, Chet, Takatoshi, Jin, Phil DeMar, some tourists). Presentation on the normal issues of the group:
New project (Fermilab, UDel), ESCPS, that will be using the topology model. Proposal is to use what was started in OSCARS/DCN and extend.
Martin/Jason/John V in Banff. NSI/NML only (no NM/NMC). Same people, same room for the 4 days. Hard to tell the difference between the two since there is so much group bleed. Important topics:
Aaron: How does the defn of a network related to the concept of a domain?
Martin: Domain is an arbitrary/administrative grouping. At the highest level network:domain is 1:1, but as you get close to the lower level they are not that similar.
SC/GENI activities are going to suck a lot of people away from this group. Proposal is to have two more meetings this year:
SCinet will be using perfSONAR tools to export monitoring data (as usual). IDC will also be used to manage the Layer 2 infrastructure to all booths. Note that its not a full IDC, can't signal to it from the outside and automatically get your circuit. Will have some controls in place so SCinet gets to control who does what.
Will be a pS Lookup Service that will register all information about pS/IDC services in SCinet.
Internet2 Booth will demo pSPT and GUIs.
Jason wrote some GUIs for REDDnet:
These will be on display at SC09 for the BWC.
Worked has stalled for now. Expected to pick up after the new year
Meet at Winter/Summer JTs, Fall/Spring MM. Target is to have drafts of the Topolgy and Use Case documents by Spring MM.
Marcos is doing LS scalability testing for the pS PS group. The IS-WG will get input into any LS design changes.
Considering a new service, the Index Service, that helps take load off of the hLS/gLS. Stores the results of common queries (needs to identify common queries) and acts as a cache for the entire system.