Network Rspecs in PlanetLab and VINI Andy Bavier PL Developer's Meeting May 13-14, 2008

Adding Networks to PL / VINI How to store and represent network information in PlanetLab and VINI? o Currently: only information for physical hosts VINI needs to represent information about: o Physical network topologies o Virtual links connecting virtual hosts Distinguish between o Topologies: Physical vs. virtual o Information: Storing (in DB) vs. representing (rspec) Other work in this space? (e.g., Wireless in OneLab)

Control Flow Topology creation/modification tool o Extracts physical topology info from PLC DB o Extracts existing virtual topology for slice o User manipulates slice's virtual topo o Saves changes to PLC DB o Optional: pushes virtual topology to nodes Requirement: support many such tools Topology creation vs. binding resources o Best-effort topologies? o Add/subtract resources to an existing topology

Storing Physical Topologies At each VINI site: two nodes -> switch -> core router Abstractions: o sites connected by bit-pipes o allocated vs. free capacity Other network abstractions? Proposal: o

Physical Topology Rspec Communicate physical topology (e.g., to Emulab) New API call: GetLinks()? Suggestions: o Leverage others' work o GENI compliance if possible

Storing Virtual Topologies Virtual links are tunnels between virtual interfaces o Physical interfaces o Demux protocol, key o Other implementation details Proposal: o o Type can hint at implementation  EGRE_BRIDGE_ETUN o Add to slice: list of VirtLinkIDs

Virtual Topology Rspec Need to communicate to NodeManager how to set up a virtual link Incorporate into the Ticket? Create a parallel mechanism?