Changes between Version 10 and Version 11 of GeniNetworkStitching

Timestamp:

09/20/13 16:38:31 (11 years ago)

Author:

Aaron Helsinger

Comment:

--

GeniNetworkStitching

@@ -3 +3 @@
 A key architectural question for GENI has been how to connect the resources provided by multiple aggregates into a coherent network. The key objective is to enable automated and realtime network stitching for slices which span multiple aggregates. Ethernet VLANs have been identified as the initial network technology to provide slice level inter-aggregate connections and isolation. 
 
-Currently there is an [http://geni.maxgigapop.net/twiki/bin/view/GENI/NetworkStitching Stitching Architecture adopted architecture], including an RSpec schema for describing stitching resources and requests.
+Currently there is an [http://wiki.maxgigapop.net/twiki/bin/view/GENI/NetworkStitching Stitching Architecture adopted architecture], including an RSpec schema for describing stitching resources and requests.
 
 Current efforts involve specifying and implementing a topology service and a computation service (per the stitching architecture), and fielding this architecture at more GENI aggregates.
@@ -13 +13 @@
 [wiki:GEC10Stitching GEC10 meeting]
 
-The session concluded by adopting a specific stitching architecture: [http://geni.maxgigapop.net/twiki/bin/view/GENI/NetworkStitching Stitching Architecture as adopted at GEC10]. Next steps centered around developing a schema for describing interconnections, and continued API discussions.
+The session concluded by adopting a specific stitching architecture: [http://wiki.maxgigapop.net/twiki/bin/view/GENI/NetworkStitching Stitching Architecture as adopted at GEC10]. Next steps centered around developing a schema for describing interconnections, and continued API discussions.
 
 The topic was re-visited at GEC11.
@@ -20 +20 @@
 
 At this session, we
- - described and adopted a schema for describing stitching resources and requests, as a GENI RSpec extension: [https://geni.maxgigapop.net/twiki/bin/view/GENI/NetworkStitchingRpecsandWorkFlow Proposed Stitching schema and workflow]
+ - described and adopted a schema for describing stitching resources and requests, as a GENI RSpec extension: [https://wiki.maxgigapop.net/twiki/bin/view/GENI/NetworkStitchingRpecsandWorkFlow Proposed Stitching schema and workflow]
  - demonstrated a tree mode VLAN stitch across PG, ION and MAX aggregates using the Omni client
 
@@ -30 +30 @@
 
 == Links ==
- * [http://geni.maxgigapop.net/twiki/bin/view/GENI/NetworkStitching Stitching Architecture as adopted at GEC10]
- * [https://geni.maxgigapop.net/twiki/bin/view/GENI/NetworkStitchingRpecsandWorkFlow Proposed Stitching schema and workflow]
- * [http://geni.maxgigapop.net/twiki/bin/view/GENI/NetworkStitchingWorkFlowExamples Stitching Workflow examples]
+ * [http://wiki.maxgigapop.net/twiki/bin/view/GENI/NetworkStitching Stitching Architecture as adopted at GEC10]
+ * [https://wiki.maxgigapop.net/twiki/bin/view/GENI/NetworkStitchingRpecsandWorkFlow Proposed Stitching schema and workflow]
+ * [http://wiki.maxgigapop.net/twiki/bin/view/GENI/NetworkStitchingWorkFlowExamples Stitching Workflow examples]
  * [https://geni-orca.renci.org/trac/wiki/Stitching Orca stitching thoughts]
 
@@ -42 +42 @@
 architecture. We agreed that many details are left to discuss, and we hope to formally accept a stitching API at GEC11.
 
-The architecture is based on a common schema and 6 functions, fully described here: http://geni.maxgigapop.net/twiki/bin/view/GENI/NetworkStitching. Tom Lehman also outlined various deployment choices. Each alternative would locate those functions in ways that map the architecture to how things are currently done in ProtoGENI, Orca, and !OpenFlow.
+The architecture is based on a common schema and 6 functions, fully described here: http://wiki.maxgigapop.net/twiki/bin/view/GENI/NetworkStitching. Tom Lehman also outlined various deployment choices. Each alternative would locate those functions in ways that map the architecture to how things are currently done in ProtoGENI, Orca, and !OpenFlow.
 
 === Community Agreement ===