wiki:PlasticSlices/MyplcStatus

Version 23 (modified by chaos@bbn.com, 9 years ago) (diff)

--

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
  • SA: Configure SFA to trust participating GENI slice authorities
  • Pub: Ensure that the site containing your nodes is public (and will remain public across plc service restarts)
  • Conn: Connect node secondary interface to OpenFlow-controlled VLANs usable by experimenters
  • IF: Configure subinterfaces on secondary interfaces
  • ARP: Configure static arp tables for Plastic Slices IPs (and use /etc/rc.local to re-apply ARP entries after a node reboot)
  • Vis: Ensure all IP addresses on a node are visible to slivers
  • FW: Ensure MyPLC and its nodes are reachable through firewalls
  • QS: Configure fast nodemanager response to MyPLC changes

MyPLC configuration status

This table lists the participating campuses. Use it to record configuration that has been verified. The column names use the abbreviations above, plus the following additional information:

  • Nodes: the number of MyPLC-controlled planetlab nodes in the testbed (this count includes only nodes which are available for Plastic Slices use, and have been verified as operational)
  • URL: the URL at which the GENI Aggregate Manager for this aggregate can be reached
  • OF VLAN: The VLAN used at this campus to implement Port-based physical VLAN translation. This is VLAN 1750 in the example on that page.

The deadlines are from PlasticSlices/ProjectPlan.

CampusDeadlineNodesURL OF VLANAMSAPubIFARPVisFWQSComments
BBN 2011-04-25 5 https://myplc.gpolab.bbn.com:12346 1750 Y Y Y Y Y Y Y Y
Clemson 2011-04-25 2 https://planetlab3.clemson.edu:12346 1750 Y Y Y Y Y Y Y Y Verified all items as of 2011-04-26.
Stanford 2011-04-25 4 https://nfcm13.stanford.edu:12346 901 Y Y Y Y Y Y Y Y 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 1750 Y Y Y Y Y Y Y Y Verified all items as of 2011-04-28 (except public site persistence across plc restart)
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.
Indiana 2011-05-09 `https://myplc.grnoc.iu.edu:12346 Y Y As of 2011-04-28, the AM is responsive and a sliver can be created, but the nodes do not allow access even after many minutes.

Some other pages containing relevant information about participating MyPLC installations:

  • HelloGENI: Description of the Hello GENI experiment. This page records a last IP octet and eth1 MAC address used by each participating MyPLC-controlled PlanetLab node.