Version 34 (modified by, 13 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.

Current outages

  • 2011-05-11: Clemson's myplc is having an outage caused by a disk corruption issue on 2011-05-01. Aaron Rosen is rebuilding the site.
  • 2011-05-11: The Washington myplc is in a strange state, in which it thinks it should control Clemson's nodes rather than its own. Srini is investigating.

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:

  • OS: the OS version installed on each MyPLC-controlled planetlab node, which is available to slivers created on that node. This is not necessarily the same as the OS version running on the MyPLC itself, though in practice these do match at most sites.
  • 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.

All resources should be available by 2011-05-09, according to PlasticSlices/ProjectPlan. This table tracks when the site was initially verified to be operational. Current issues are listed above under #Currentoutages.

BBN Fedora 8 5 1750 Y Y Y Y Y Y Y Y
Clemson Fedora 12 2 1750 Y Y Y Y Y Y Y Y Verified all items as of 2011-04-26.
Stanford Fedora 12 4 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 Fedora 8 2 1750 Y Y Y Y Y Y Y Y Verified all items as of 2011-05-11, except testing with other sites because VLAN 1750 is not yet connected to the OF core
Washington Fedora 12 2 1750 Y Y Y Y Y Y Y Y Verified all items as of 2011-05-02 (except public site persistence across plc restart)
Wisconsin Fedora 12 2 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 Fedora 8 2 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 Fedora 8 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.