Plastic Slices MyPLC Status

The Plastic Slices project uses small MyPLC-controlled installations of PlanetLab nodes at several participating campuses, to provide compute resources with network interfaces on the OpenFlow-controlled backbone.

MyPLC configuration requirements

The MyPlc/NetworkCoreRecommendations page details the common configuration for MyPLCs participating in Plastic Slices, and links to instructions for how to implement each step. In brief, the necessary configuration items are:

AM: Install and configure the SFA software which implements the GENI AM API

Verified all items as of 2011-04-27 (except public site persistence across plc restart)

Rutgers

2011-05-02

2

https://plc.orbit-lab.org:12346

Y

Y

Y

Y

As of 2011-04-27, site appears public (but refresh behavior is unknown). Secondary interfaces are not yet configured, and QS behavior is uncertain (i got both my nodes in 2-4 minutes, which seems less than 15, but not quick).

Washington

2011-05-02

2

https://of.cs.washington.edu:12346

1750?

Y

Y

Y

?

Y

Y

Y

Y

As of 2011-04-27, everything is configured, but we are not yet sure that the OF VLAN will be 1750, and pl02[eth1] may not be physically connected yet.

Wisconsin

2011-05-02

2

https://wings-openflow-1.wail.wisc.edu:12346

Y

Y

Y

Y

As of 2011-04-28, the AM is responsive, a sliver can be created, the nodes become available for login, and plnet.py is patched on wings-openflow-2 (but not on -3), but eth1 is not configured at all.

Gatech

2011-05-09

2

https://myplc.cip.gatech.edu:12346

Y

Y

Y

Y

As of 2011-04-28, the AM is responsive, a sliver can be created, and QS appears to be present. The interface configuration is still the G4E one, and the nodes are firewalled to specific subnets.