External Layer2 Connections (Stitching)¶
Chameleon provides support for sophisticated networking experiments by providing GENI-style stitching. This capability enables users to deploy networking experiments (layer 2 and layer 3) that extend across Chameleon, potentially other testbeds such as GENI, and into physical resources on their own campus networks. Users can create a dedicated network associated with a dynamic VLAN, subnet with own DHCP server, and router for external connections.
Currently, it is possible to connect user-configured networks to other domains (e.g. GENI) over circuits created on Internet2’s Advanced Layer 2 Service (AL2S). In this setup, a pool of VLANs is extended from Chameleon CHI@UC racks to the AL2S endpoint at StarLight. Currently, 10 VLAN tags (3290-3299) are dedicated to this AL2S endpoint, although 3290 is reserved for system use. A user-configured network that is associated with one of the dedicated AL2S VLAN tags (segmentation ID must be the same as AL2S VLAN tag) can be stitched to external domains (e.g. GENI). A circuit on AL2S needs to be created.
This document describes how to stitch Chameleon experiments to external resources including ExoGENI and Internet2 connected campuses. You will need to know how to create stitchable dynamic VLANs as described in the networks documentation. After you have created such VLAN this document will describe how to create a slice in three cases: connect to ExoGENI, connect to other domains using ExoGENI as an intermediary, or connect to other domains directly.
Chameleon has the capability to create dynamically managed VLANs associated with user-configured private IP subnets as described on networks. Users can create a dedicated network associated with a dynamic VLAN, subnet with own DHCP server, and router for external connections. These networks can be created through the web as well as command line interface. User-configured networks (isolated networks) are associated with VLANs by Segmentation IDs.
In the following sections, this workflow is described for different settings.
Configuring a Stitchable Network¶
Follow the technical documentation for Creating a Network using the CLI, but replace the provider network with the appropriate external testbed (e.g. replace
In this documentation, we will describe how to stitch to the ExoGENI testbed:
openstack network create --provider-physical-network exogeni <network_name>
If you made a reservation for a stitchable VLAN segment, the network will have been created automatically.
Connecting Chameleon to ExoGENI¶
ExoGENI is one of the two primary GENI testbeds. ExoGENI allows users to create isolated experimental environments with compute and network resources distributed across 20 sites. ExoGENI has a special type of connection called “stitchport” which is a formally defined meeting point between VLANs dynamically provisioned within Chameleon and ExoGENI slices. Users can create slices on ExoGENI testbed, and connect these slices with Chameleon nodes by using a stitchport.
Stitchports that exist in ExoGENI topology are listed on ExoGENI Wiki (ExoGENI Resource Types: Stitchport Identifiers). URLs for port locations and corresponding VLAN tags are used to create a stitchport connection. Stitchport information for Chameleon is listed as below:
Allowed VLANs: 3291-3299
Allowed VLANs: 3501-3509
Layer 2 connections on ExoGENI are provisioned on AL2S by an agent that submits requests to OESS on behalf of the user slice. Users do not need to have an OESS account. An ExoGENI slice with a stitchport can be created as below. (Information for using ExoGENI and creating slices can be found at http://www.exogeni.net)
Connect the node to a stitchport:
Supply the URL and VLAN tag to the stitchport properties. VLAN 3299 will be used for Chameleon connection. The user-configured network on Chameleon must have segmentation ID: 3299.
Submit request. A manifest for the reservations will be returned.
After the slice creation is completed, nodes in the slice will be able to connect to the Chameleon nodes that are connected to the user-configured network with segmentation ID: 3299.
Connecting Chameleon to user owned domains via ExoGENI¶
Using ExoGENI to connect to Chameleon can be further extended by using ExoGENI as an intermediary domain.
In this use case, a local site can be connected to ExoGENI via stitchports, and an ExoGENI slice can be created to route traffic to Chameleon. In the example below, a stitchport connects the local site (NCBI) to an ExoGENI slice which is connected to Chameleon. Nodes on the ExoGENI slice can be used to route traffic from NCBI nodes to Chameleon nodes. In this case, all layer 2 circuits will be provisioned by ExoGENI.
Connecting a local site to ExoGENI via stitchports is a process that requires multiple steps involving site owners, regional network providers, and ExoGENI.
ExoGENI racks are located on campuses across the US. Campuses are connected to Internet2 AL2S via regional provider networks. A set of VLAN tags is reserved for ExoGENI from the pool of available VLAN tags by the regional providers and campus administrations. These VLANs are plumbed on both regional provider and campus networks all the way from AL2S endpoint to the rack or server(s). Some campuses/institutions are directly connected to AL2S nodes without a regional provider (e.g. Pittsburgh Supercomputing Center, George Washington University (CAREEN)).
Stitchports can be used to connect a specific location to ExoGENI racks.
- VLAN(s) from the local site should be extended through the campus network all the way to the AL2S endpoint.
- ExoGENI must update the topology to activate the stitchport.
ExoGENI administrators can provide assistance and can be contacted at email@example.com
Connecting Chameleon to user owned domains¶
Users can connect their local domains to Chameleon over manually created layer-2 circuits on AL2S. Local domains need to be connected to the other AL2S endpoint of the circuit by users.
Circuits on AL2S are created through the Internet2 AL2S OESS portal. The OESS (Open Exchange Software Suite) is a set of software used to configure and control dynamic layer 2 virtual circuit (VLAN) networks on OpenFlow enabled switches. It includes a web-based user interface as well as a web services API.
Chameleon is connected to the AL2S endpoint at StarLight:
Node: sdn-sw.star.net.internet2.edu Interface: et-8/0/0 VLAN range: 3290-3299
A user can log into the AL2S OESS portal and create a circuit connecting the Chameleon endpoint to the user-owned endpoint. The user should have an account to log in to the AL2S OESS portal. On OESS, users are members of workgroups. After logging in to the portal, a user can see the workgroups that he/she is a member of.
Network resources on AL2S are granted access to the workgroups. This access is granted by the owner of the AL2S network resource (campus network administrators or network engineers at regional providers). After granting access to the resources, they become available for the workgroup and start showing up in the “Available Resources” section. For the user to create such a circuit on AL2S with Chameleon endpoint, the workgroup that the user has membership should be granted access for this endpoint. This can be requested from Chameleon by opening a ticket with our help desk.
As an example, Chameleon resources can be seen in “Available Resources” section for a user in the “ExoGENI” workgroup after access to the workgroup is granted.
The user in the ExoGENI workgroup can create a circuit with two endpoints to connect a local site to Chameleon.
Endpoint 1 (Local site): Node: sdn-sw.rale.net.internet2.edu Interface: et-9/0/0 VLAN: 3998 Endpoint 2 (`CHI@UC <https://chi.uc.chameleoncloud.org>`_): Node: sdn-sw.star.net.internet2.edu Interface: et-8/0/0 VLAN: 3290
To create a circuit, follow these instructions:
Create a new VLAN
Submit circuit request
When the circuit is provisioned, you should see this:
In addition, the Path can be seen on the map. Utilization data becomes available after 3 hours.
At this point, a layer-2 circuit is created on AL2S. The user-configured network with segmentation ID 3290 can be connected to the local servers. The user needs to extend the VLANs at the local site (3998 in this case) to the AL2S endpoint.
To obtain an account to access AL2S OESS portal, users should contact Internet2. Information can be found from the links below: