Changes between Version 1 and Version 2 of GENIRacksHome/InstageniPlanetLab


Ignore:
Timestamp:
10/03/13 14:03:45 (6 years ago)
Author:
acb@cs.princeton.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIRacksHome/InstageniPlanetLab

    v1 v2  
    3939}}}
    4040
     41Currently on VICCI (http://www.vicci.org) we allow users to login with their PlanetLab passwords.  When they do so, their existing PlanetLab slices are mirrored on VICCI so that they can easily add VICCI nodes to their PlanetLab experiments.  If we decide that offering a similar sign-in for PlanetLab users on IG-PL would be attractive, we can easily enable this functionality.
    4142
    4243== Node Features ==
    4344
     45The nodes are running a recent PlanetLab build based on LXC and Open vSwitch, i.e., the same software as the VICCI testbed.
     46
     47The software running on the nodes supports connecting containers to VLANs and GRE tunnel topologies as well as dedicated public IP addresses.  However we need to do a bit more work to expose this functionality via the SFA and RSpecs.  Currently containers created via the SFA can only connect to the public network via NAT (i.e., “PlanetLab” mode).
     48
     49Right now the !PlanetFlow traffic monitoring service is '''not''' running on the nodes.  This will need to be fixed before these nodes are opened to users. 
     50
    4451== Integration with ProtoGENI ==
    4552
     53Below we describe some of the steps we took to integrate the PlanetLab and ProtoGENI models of managing nodes.
     54
     55=== Installing PlanetLab ===
     56
     57PlanetLab expects that a node is always booted from detachable boot media.  The first challenge was to boot a ProtoGENI node from the PlanetLab Boot CD.  One option we considered was to boot the node from a remote ISO file using the HP iLO’s Virtual Media function.  Leigh and Rob convinced us that it would be better to boot from the hard drive, in order to not interfere with the normal operations of the InstaGENI racks.
     58
     59Here is the procedure currently used to bring up an IG-PL node:
     60
     61 * Boot an InstaGENI node using ProtoGENI’s standard Fedora 15 image
     62 * Once the node comes up, copy the PlanetLab BootCD ISO image for the node to ''/boot/iso/''
     63 * Configure GRUB to use memdisk to boot the ISO directly
     64 * Use a modified PlanetLab installer to:
     65   * Create a new partition from the 986GB unused space on the disk
     66   * Install PlanetLab into the new partition without changing the existing ones
     67
     68This method leaves us 848GB of disk space to host PlanetLab slices.  A nice feature is that the node can then be “dual booted” as a ProtoGENI node (i.e., using the original F15 image) or a PlanetLab node simply by modifying ''/etc/grub.conf'' in the ProtoGENI partition.
     69
     70=== ProtoGENI Node Status ===
     71
     72In order to make the ProtoGENI node monitoring software see the PlanetLab node as "booted", it is necessary to do the following when the node boots (thanks to Leigh for this insight):
     73
     74 * Mount the ProtoGENI partition on the PlanetLab node
     75 * chroot into the ProtoGENI partition
     76 * Run ''/usr/local/etc/emulab/tmcc.bin ISUP''
     77
    4678== Still To Do ==
     79
     80 * Enable GENI-style networking in SFA.  We need an example RSpec that has VLANs in it.
     81 * Bring up more nodes
     82 * Better integrate with ProtoGENI node status monitoring
     83 * Enable PlanetFlow on the nodes
     84 * Enable sign-on with PlanetLab credentials
     85 * Announce to PlanetLab users
     86 * Integrate with GMOC monitoring