physical nodes that are not shared (permentantly allocated).

a missing url in the certificate for component (node). Why was that?
Well, when I create a sliver, I use the same uuid as the node, and
then later when I need to find the node for that sliver, I look for it
in the nodes table using the that uuid. This was bad cause for each
sliver I create a new certificate pair, and thus a new uuid. This
overwrites the original certificate bound to that node, only the new
certificate is not created with a URL. This is bad all around, but
with uuids being replaced by URNs and so close to the demo, I am not
going to fix this properly, but rather just avoid the problem by
reusing the existing certificate for the node when creating a sliver.
Revisit later this week.

same physical interface, generate a new uuid for every interface
sliver. This is okay since we do not use those slivers anyway, to
access the interface.

1. Allow use of the shared nodes via the "exclusive" tag in the rspec.

2. Switch to using the mapper in GetTicket() and in RedeemTicket() as
   per this email I sent:

* GetTicket(): New rspec comes in and I build a virtual topology as I
 parse the rspec. Basically, virt_nodes and virt_lans table entries,
 which are stored into the DB. The rspec can include wildcards or
 specific nodes; I use the "fixed" slot of the virt_nodes table. Note
 that I am not yet handling fixed ifaces. Nice thing about this is
 that all of the show exp tools work.

 I run the (new) mapper on it in "solution" mode. This does two
 things; wildcards are mapped, and 2) it verifies that the rspec is
 mappable on the local hardware. Solution mode does not actually
 change the DB, but rather it spits out an XML file that I parse
 (note, we eventually will pass the rspec through, but I am not ready
 for that yet). I then allocate the nodes to the holding area, update
 the rspec, create a ticket, and return it.

* RedeemTicket(): I run the new mapper again, only this time in real
 mode with -update. This is basically a redo of the run above since
 all the nodes are reserved already, but the DB is actually filled
 out this time. I then create the slivers and such.

 The other difference is that instead of creating the vlans by hand,
 I can now run snmpit -t to do the work for me. Ditto for tear down
 with snmpit -r.

 Another bonus is that I can add (missing) IP addressess during the
 initial rspec parse, and the nodes now boot and have their
 interfaces configured. Virtual interfaces too, including the ones
 inside of virtual nodes.

* All of the above works with shared nodes too:

"<rspec xmlns=\"http://protogeni.net/resources/rspec/0.1\"> " +\
" <node virtual_id=\"geni1\" "+\
"       virtualization_type=\"emulab-vnode\" " +\
"       virtualization_subtype=\"emulab-openvz\" " +\
"       exclusive=\"0\"> " +\
"   <interface virtual_id=\"virt0\"/> " +\
" </node>" +\
" <node virtual_id=\"geni2\" "+\
"       virtualization_type=\"emulab-vnode\" " +\
"       virtualization_subtype=\"emulab-openvz\" " +\
"       exclusive=\"0\"> " +\
"   <interface virtual_id=\"virt0\"/> " +\
" </node>" +\
" <link virtual_id=\"link0\"> " +\
"  <interface_ref " +\
"            virtual_interface_id=\"virt0\" " +\
"            virtual_node_id=\"geni1\" " +\
"            /> " +\
"  <interface_ref " +\
"            virtual_interface_id=\"virt0\" " +\
"            virtual_node_id=\"geni2\" " +\
"            /> " +\
" </link> " +\
"</rspec>"

The shared nodes boot, and you can ping on the experimental networks.

Caveats:

* UpdateTicket and UpdateSliver need work as per the mail I sent the
 other day about the state of the sliver between the ticket and the
 sliver operations.

* Collocation specifications are ignored since we do not have any way
 to specify this to assign when wildcards are used. Rob, I am
 wondering if assign has any tricks we can take advantage of.

* Still need to commit all the snmpit changes and get that hooked into
 the CM.

https://www.protogeni.net/trac/protogeni/wiki/ComponentManagerAPI

support. Can even create multiple jailed nodes on the same physical
node. Sorry, no sharing of physical nodes yet (between slices).
Also no link support yet; coming later.

The syntax is an extension of the current hack syntax:

        " <node uuid=\"" + node_uuid + "\" " +\
        "       nickname=\"geni1\" "+\
        "       phys_nickname=\"geni1\" "+\
        "       virtualization_type=\"emulab-vnode\" " +\
        "       virtualization_subtype=\"emulab-jail\"> " +\
        " </node>"

This only works on sites that already can do jails.

to the Geni Public License at http://www.geni.net/docs/GENIPubLic.pdf,
whose expansion at this time is:

-----
Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and/or hardware specification (the "Work") to
deal in the Work without restriction, including without limitation the
rights to use, copy, modify, merge, publish, distribute, sublicense,
and/or sell copies of the Work, and to permit persons to whom the Work
is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Work.

THE WORK IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE WORK OR THE USE OR OTHER DEALINGS
IN THE WORK.

its really a hugely stripped down Emulab boss install, using a very
short version of install/boss-install to get a few things into place.

I refactored a few things in both the protogeni code and the Emulab
code, and whacked a bunch of makefiles and configure stuff. The result
is that we only need to install about 10-12 files from the Emulab
code, plus the protogeni code. Quite manageable, if you don't mind
that it requires FreeBSD 6.X ... Still, I think it satisfies the
requirement that we have a packaged clearinghouse that can be run
standalone from a running Emulab site.

slivers and tickets. There is no way to look into these tables yet.
Need to do something about a web interface to Geni before too long.

code.

Also, as a debugging aid, if you request a ticket for a slice, and
that slice already has a ticket, delete the ticket and generate a new
one.

a good thing in production.

working program agents! Yippie.

for a while). I am still not using the actual rspec definition yet, still
using my adhoc one.

vlans.

Checkpoint working swapin of experiments using multiple federated nodes with vlans between them. Now I need to figure out how to swap the experiment out

program protogeni/xmlrpc/client.py ... it is much easier to get a
simple python client running on your desktop then a perl client. Only
package you need to install is M2Crypto, which is easy. Perl needs
about 10 packages installed to xmlrpc over ssl. Sheesh.

completely raw links; just a vlan between two interfaces. No traffic
shaping or anything like that.