...
SDN met at the Annual Meeting. They continue regular calls.
Topics included:
1) Recap of the Open Networking Summit.
- Intel announced a reference Switch design.
- Switchlight linus for switches. Firmware to run on broadcom based switches.
- Open Daylight discussion. Question comes up how should our community be involved in Open Daylight?
2) Overall the working group is still missing the research community. Perhaps they will have a WG meeting at GEC. Heidi agreed it was a good idea.
I2 Updates:
- There was a change freeze during the Annual Meeting.
- The NY router was swapped after the Annual Meeting.
- There is a bad slot in the chassis in Houston, requires a site revisit. Not sure when this will occur.
- Amazon NET+ connectivity was brought up. There had been an issue with those routes, but it was corrected. Related to prepends.
- Ashburn AL2S node install was done prior to Annual Meeting. Its a Juniper Node, does backhaul for Amazon.
- AL2S installs Planned:
-Portland
-Phoenix - Boston
- Albany
- Columbia
- Jackson, MS
- Minneapolis.
- NTNC is being finalized. There are 3 100G's. All three are being tested though only one will be brought into service for now. There will be some 10G's as well.
- Corrected the two maintenances in the Southwest so they were not overlapping. Asked Level(3) to push back 1 of them.
Michael asked about an issue in DC prior to the call.
- The Primary RE failed.
- The backup RE took over.
- Had to replace the failed one.
- This was an isolated event.
- The Singapore Launch event went very well. It was a virtual launch event to start up and officially open the Singapore Colo facility.
Grover discussed the 6 month report he sent out.
It goes over:
- Timeline of the project
- Discussion of maintenance and availability
- Some unedited comments and thoughts from AL2S users.
- Future Plans section:
- The availability figures are not all that helpfull.
- They are not really actionable.
- Tends to report converged L1, L2 and software issues.
- Needs to be more granular.
- Needs for instance to relate L1 events as they impact L2.
- The report needs to cover both scheduled and unscheduled outages.
- Overall the report should look at the availability of services not just infrastructure.
- Dual homing or sites will affect service availability for the sites.
- Really there is no easily accessible project history.
- It would be good to have such a network history/timeline in an accessible form.
David asked if it would be possible to have a Quarterly Report? Grover agreed that would be possible. Chris also agreed that having quarterly reports matches better the general approach for other services.
David then said it would be good to have the next report in place before the August timeframe review of the overall architecture discussion.
Grover: The report also did not include capacity planning in this version.
- This is a somewhat more tactical then strategic issues.
- It does not have as much value.
Darrell agreed that simple capacity planning questions were not that important. - Having an assessment of the time involved in the availability reports would be valuable.
- This can be added.
Grover: We should probably also look at some measure about impairment. It is not just an binary up/down issue most of the time.
L(3) architecture:
The gear needed to install the interconnects between AL2S and the routers has been arriving and is being positioned.
We are still waiting on hybrid mode from Juniper.
- Looking for a code drop later this month.
- Still need to evaluate the release.
It is still necessary to have the conversation in the WG's about restoration technique. The paper describing the alternatives should be out soon.
Grover Browning, Ken Miller, P.J. Clayton, Shannon Spurling, Michael Lambert, Brian Cashman, Alan Whinery, Bill Owens, David Wood, David Crowe, Dan Schmidt, Dave Pokorny, Dale Carder, Chris Robb, Dave Hunter, Jay Ford, Linda WInkler, Darrell Newcomb, Jeff Bartig, Scott Brim, Akbar Kara, Allison Ferreira