Building a Resource Request

You can request resources on the w-iLab.t via the Aggregate Manager API as used in the Fed4FIRE or GENI federations.

This can be done either via the imec jFed GUI, or by manually creating a request RSpec and submitting this via a CLI tool like the imec jFed CLI or omni

Normally, an experimenter tool as jFed will hide these RSpecs from you the experimenter, but if you need special features or want to use other tools, you might need these Request RSpecs. If you want other configurations, you can also start up jFed and go into the Raw RSpec view, to have a look at the RSpecs.

The RSpecs for w-iLab.t are very similar to these of the Virtual Wall, with the following remarks:

  • in w-iLab.t you typically want to use specifc nodes as in wireless experimenters the location plays a role
  • impairment nodes are not supported in w-iLab.t
  • the URN of the component manager is different

Requesting a Bare Metal Server

Simple unbound RSpec

Unbound means that the testbed chooses a node for you. You tyically do not want this.

node0 is the name of the node.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<rspec type="request" xsi:schemaLocation="http://www.geni.net/resources/rspec/3 http://www.geni.net/resources/rspec/3/request.xsd"
xmlns="http://www.geni.net/resources/rspec/3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <node client_id="node0" component_manager_id="urn:publicid:IDN+wilab2.ilabt.iminds.be+authority+cm" exclusive="true">
      <sliver_type name="raw-pc"/>
  </node>
</rspec>

Bound RSpec

This means that you choose a specific node, which you specify in the component_id-attribute of the <node>-tag. The node names should be mentioned in the listresources call, e.g. zotacB1 (they are numbered according a grid) in the example below:

Using specific images, installing software or running a script

Installing software, running scripts and using specific disk images is the same as for the Virtual Wall. The following images are supported on w-iLab.t:

  • the default image is an Ubuntu 12.04 LTS 64 bit image with OMF5.4 installed (UBUNTU12-64-OMF54)
  • FreeBSD 8.3 32 bit: urn:publicid:IDN+wilab2.ilabt.iminds.be+image+emulab-ops//FBSD83-STD
  • Debian 6.0 64 bit: urn:publicid:IDN+wilab2.ilabt.iminds.be+image+emulab-ops//DEB60_64-STD
  • Fedora 15 64 bit: urn:publicid:IDN+wilab2.ilabt.iminds.be+image+emulab-ops//FEDORA15-64-STD
  • OpenWRT: urn:publicid:IDN+wilab2.ilabt.iminds.be+image+emulab-ops//openWRT

Note on OpenWRT: this image has less functionality then the others, e.g. no mount of your homedir, no installed ssh keys, just use login: root, password: root

Request URL’s and URN’s

w-iLab.2

The AM of w-iLab.t is accessible through:

  • GENI AM v2: https://www.wilab2.ilabt.iminds.be:12369/protogeni/xmlrpc/am/2.0
  • GENI AM v3: https://www.wilab2.ilabt.iminds.be:12369/protogeni/xmlrpc/am/3.0

The URN of the componentmanager is: urn:publicid:IDN+wilab2.ilabt.iminds.be+authority+cm

w-iLab.1

The AM of w-iLab.t is accessible through:

  • GENI AM v2: https://www.wilab1.ilabt.iminds.be:12369/protogeni/xmlrpc/am/2.0
  • GENI AM v3: https://www.wilab1.ilabt.iminds.be:12369/protogeni/xmlrpc/am/3.0

The URN of the componentmanager is: urn:publicid:IDN+wilab1.ilabt.iminds.be+authority+cm