November 2011 - Nsi-wg - lists.ogf.org

call today
by Tomohiro Kudoh 09 Nov '11

09 Nov '11

Hi all, We will have a quick call today to check status of NSAs. The following is dial-in information for Wednesday's NSI call, time: 7:00 PST 10:00 EST, 15:00 GMT, 16:00 CET, 24:00 JST 1. Dial Toll-Free Number: 866-740-1260 (U.S. & Canada) 2. International participants dial: Toll Number: 303-248-0285 Or International Toll-Free Number: http://www.readytalk.com/intl 3. Enter 7-digit access code 8937606, followed by "#" Agenda: NSI SC demo preparation

1 0

Interesting state machine issue with provision command.
by John MacAuley 08 Nov '11

08 Nov '11

State machine is in the reserved state. It is before startTime. I receive a prov.rq but encounter a processing failure. At the moment the state machine says I can only send a prov.fl after startTime and can only transition back to the Scheduled state. How should I handle this scenario? My first instinct is to transition back to Reserved since it is still before startTime. Comments? john.

2 1

Please begin testing
by Jerry Sobieski 03 Nov '11

03 Nov '11

Hi all- I just circulated the most recent global NSI topology for the Supercomputing demos. It is now time to begin testing again. Please get started asap, and monitor the nsi-wg chat room on Skype. For those of you with uRA clients that do not perform any segmentation, please select an aggregator NSA and begin testing to that network NSA. For the Aggregator NSAs, please verify that you are able to interop with each other implementation, then to each network. start with your direct data plane neighbors and work your way outward. (TK: do you have some thoughts on this verification process...?) I think the key issues we need to work thru are a) HTTPS interop, b) SC WSDL consistency, c) Query result consistency, and then just coordination among the whole group so we do not get too many requests interfering with one another. All NSI implementations should be able to successfully talk to all the other implementations by now with all primitives. If we need additional VLANs, let me know and I can add more to the topology. We will want to develop a looping script at some point this week or early next. This script will issues a sequence of Reservation Requests and walk the connection(s) through their lifecycle while the viz tools track the state transitions. _/This will be the fundamental demo during the conference. /_ We probably need some simple orchestration tools: An end system daemon that will configure an particular IPaddr on the VLAN subinterface when a connection is provisioned and then issue/respond to pings. Any idle hands out there want to work on some code? Thanks! Jerry

6 9

Note: no more topo updates to this NSI-WG list
by Jerry Sobieski 03 Nov '11

03 Nov '11

In the interest of reducing demo spam to this list, I am only going to forward the demo topology updates to the plugfest list and the automatedGOLE list. If you are not on one of those lists and still want to receive it, please subscribe to those lists... Thanks Jerry

1 0

Mailing lists
by Radek Krzywania 02 Nov '11

02 Nov '11

Hi, By now I get each email in three copies as they are sent to three mailing lists. Could we agree on just one? Or make new one dedicated to SC demo maybe? Best regards Radek ________________________________________________________________________ Radoslaw Krzywania Network Research and Development Poznan Supercomputing and radek.krzywania(a)man.poznan.pl Networking Center +48 61 850 25 26 http://www.man.poznan.pl ________________________________________________________________________ > -----Original Message----- > From: Tomohiro Kudoh [mailto:t.kudoh@aist.go.jp] > Sent: Wednesday, November 02, 2011 5:36 AM > To: Jerry Sobieski > Cc: t.kudoh(a)aist.go.jp; nsi-plugfest(a)m.aist.go.jp; automatedgole- > pilot(a)internet2.edu; nsi-wg(a)ogf.org > Subject: Re: [Nsi-wg] Please begin testing > > Hi Jerry, > > Again, I think not all the NSA should support https, but only > aggregaters are required to do so. > > Considering the time we have before SC, making https madatory may have too > much risk for success of SC demonstration. > > Tomohiro > > > On Wed, 02 Nov 2011 00:12:44 -0400 > Jerry Sobieski <jerry(a)nordu.net> wrote: > > > Hi all- > > > > I just circulated the most recent global NSI topology for the > > Supercomputing demos. > > > > It is now time to begin testing again. Please get started asap, and > > monitor the nsi-wg chat room on Skype. > > > > For those of you with uRA clients that do not perform any segmentation, > > please select an aggregator NSA and begin testing to that network NSA. > > > > For the Aggregator NSAs, please verify that you are able to interop with > > each other implementation, then to each network. start with your direct > > data plane neighbors and work your way outward. (TK: do you have some > > thoughts on this verification process...?) > > > > I think the key issues we need to work thru are a) HTTPS interop, b) SC > > WSDL consistency, c) Query result consistency, and then just > > coordination among the whole group so we do not get too many requests > > interfering with one another. All NSI implementations should be able > > to successfully talk to all the other implementations by now with all > > primitives. > > > > If we need additional VLANs, let me know and I can add more to the > topology. > > > > We will want to develop a looping script at some point this week or > > early next. This script will issues a sequence of Reservation Requests > > and walk the connection(s) through their lifecycle while the viz tools > > track the state transitions. _/This will be the fundamental demo during > > the conference. > > /_ > > We probably need some simple orchestration tools: An end system > daemon > > that will configure an particular IPaddr on the VLAN subinterface when > > a connection is provisioned and then issue/respond to pings. Any idle > > hands out there want to work on some code? > > > > Thanks! > > Jerry >

2 1

Re: [Nsi-wg] Query status
by Jeroen van der Ham 02 Nov '11

02 Nov '11

Hello all, The current implementation of query in most NSAs provides global information regarding a reservation request. It provides the status, source and destination, et cetera. For visualization purposes, it would be better if we could also get some path information. Currently the OpenNSA implementation provides this by using an stpList in the result. This is completely in line with the CS protocol. Could the other implementations please consider doing that as well? Jeroen. On 2 Nov 2011, at 14:14, Jeroen van der Ham wrote: > Hello, > > My weatherreport on the NSAs is changing to the query status and SC topology support. > >> Starlight > Query: ok[1] > Topology: failed > >> KDDI > Query: ok > Topology: failed? > >> Geant > Unable to connect > >> Jgnx > Unable to connect > >> Northernlight: > Query: ok (aka "panic before sc demo") > Topology: no change > >> Pionier: > Query: ok [2] > Topology: no change > >> Netherlight: > Unable to connect (client does not support https) > > Regards, > Jeroen. > > [1]: Note for Starlight, there is a reservation in Provisioned with schedule: 2011-10-28T09:38:30Z -- 2011-10-30T17:11:30Z > > [2]: Note for Pionier, there is a reservation stuck in "Provisioning" state with schedule: 2011-10-28T15:35:06.607+02:00 -- 2011-10-28T15:37:06.607+02:00 > > > > >

1 0

Call Tomorrow - Agenda: Security
by Inder Monga 02 Nov '11

02 Nov '11

Hi All I hope the team has rested after the FIA demos. We will be having the discussion on security tomorrow morning. Looking forward to the discussion tomorrow, The following is dial-in information for Wednesday's NSI call, time: 7:00 PDT 10:00 EDT, 15:00 GMT, 16:00 CET, 24:00 JST Dial Toll-Free Number: 866-740-1260 (U.S. & Canada) 2. International participants dial: Toll Number: 303-248-0285 Or International Toll-Free Number: http://www.readytalk.com/intl 3. Enter 7-digit access code 8937606, followed by "#" Best Regards Inder -- Inder Monga 510-486-6531 http://www.es.net Follow us on Twitter: ESnetUpdates/Twitter <http://bit.ly/bisCAd> Visit our blog: ESnetUpdates Blog <http://bit.ly/9lSTO3><http://bit.ly/d2Olql>

2 2

SC2011 Topo v2
by Jerry Sobieski 02 Nov '11

02 Nov '11

Hi all- Here is SC Topo version 2. Changes: - Added jgnx.ets network running G-LAMBDA-K (required modifications to adjacent networks also to reflect the new neighbor) Note: There is no csProviderEndpoint yet for jgnx.ets...I will send an update as soon as this is idenitfied. - Restored all interdomain SDPs to vlans 1780-1783 (Removed the direct peerings from Pionier to StarLight and AIST) - For consistency, all NSI networks explicitly define STPs ps-80 thru ps-81 (even though they are not strictly required in inter-domain topo since they do not form SDPs) - Modified some comments This was a rather extensive change to the global topology so please check your respective network information to make sure it is correct. Thanks Jerry

1 0

NSI demos for Supercomputing
by Jerry Sobieski 01 Nov '11

01 Nov '11

Hi All- I hope you all had a nice well deserved and relaxing weekend. Alas, we must get started on the final stretch this year and prepare for the Supercomputing demos... (there must be some cosmic justice to the fact that "demonstration" begins with "demons"...) The focus for SC will be to consolidate, stabilize, and demonstrate our existing capabilities. So, our target topology will be the topology we used last week for FIA, plus any added GOLEs or Networks that participate. There are two ways to participate: a) as an NSI network running an NSA, or b) as a supporting organization that is willing to lend transport resources between these NSI networks or is willing to help write software tools, etc. I will acknowledge all organizations on the posters/handouts. ---> I want to freeze the topology by November 7th so that applications building off the diagrams don't have to keep fixing their graphics everytime someone realizes they want to participate...So if you want to be part of this, let me know ASAP. (That means yesterday!:-)) The fundamental objective of the SC demo is to set up circuits using NSI-CS across multiple domains and over real hardware. So each network will need to verify their 1) control plane interoperability with the other NSAs, and 2) insure that their data plane is properly configured between your network and your adjacent peer. Attached is the initial topology diagram and the associated .owl file for SC - SC2011-Topo-v1.0 Changes from latest FIA topo: - Added STPs for USLHCnet between NL and SL. For SC, we will again use only four VLANs on each link: 1780 to 1783. In some locations we may need to only use a subset of these depending upon how the NSAs are resolved by next week. Tasks: For the GOLE/network operators: pursue the following tasks: 1) Every network should have at least one end system that can be used to terminate circuits and that can issue and respond to IP layer Pings. This could be a perfSonar host with apropriate access provided to the demo team, or a small Linux or Mac, or possibly the switch processor itself. But we need something we can use to test to, and access to configure and verify the circuit. 2) Control plane: Begin testing immediately from your NSA to your neighbor's NSA to set up simple intra-domain Reservation Requests across your neighbor's network, and then progress to test inter-domain reservations across your network *and* your neighbor. THis is to insure proper and reliable interoperability between NSAs. Coordinate with your neighbor network (you all know the PoCs by now) to test. 3) Data plane: Ping test the connections to your neighbors' networks to insure the VLANs are clear channels between the NSI Networks. The crossconnects within your networks will never work if the static VLANs between networks are not operational first. So _/verify these VLANs/_ by manually placing an end system from each network on each VLAN, configuring the IP subnet, and pinging one another. For the code developers: 1) Make sure your hardware/NRM interfaces are working reliably. 2) Make sure you are able to deal with SOAP/HTTPS messaging. If you need to implement it - now is the time. If there are issues doing so, lets get those exposed so that we can resolve them. Monitor the nsi-wg chat on Skype... 3) Make sure the Query command is working properly. 4) Lets get the Query Agent, the MotherEarth (autoEarth) vizualizer, and the AIST-vizualizer working *RELIABLY*. You all should dive into this as soon as the SC WSDL interop, query interop, and HTTPS is working. This is the capstone task for this year!!! These visualizers will exercise and demonstrate all of the other great work we've accomplished. So let make these look good! Thanks all.... Any additions, corrections, thoughts, or comments, please post or send them to me and we'll integrate them into the task tracking... Two weeks till Showtime! Jerry

2 1