Commit 3f75620c authored by David Johnson's avatar David Johnson

Another round of documentation.

parent 88de2a48
......@@ -12,7 +12,8 @@ GENI XMLRPC methods must be called with appropriate credentials, and for
you that means your certificate and its passphrase. By default,
elasticslice looks for your certificate in `~/.ssl/encrypted.pem`, and it
looks for the passphrase for that certificate in `~/.ssl/password`. If
you don't specify your passphrase,
you don't specify your passphrase, you'll be prompted for it on
``stdin`` for each RPC!
Finally, copy `etc/main.conf` from the elasticslice source repository
to `~/.protogeni/elasticslice.conf`, and modify it as necessary (i.e.,
This diff is collapsed.
......@@ -10,7 +10,7 @@ or
``$ python install --prefix=/usr/local``
or similar. If you use the ``--user`` option, elasticslice will be
installed in ``$HOME/.local/{bin,lib} or thereabouts.
installed in ``$HOME/.local/{bin,lib}`` or thereabouts.
You can build the `elasticslice` documentation via
......@@ -11,17 +11,43 @@ which a client submits a ticket to an AM or CM to obtain the resources
provided for in the ticket --- and then is guaranteed to have those
resources until the ticket expires.
If you're coming from the Emulab model of projects and experiments, the
new slice and sliver terminology may be confusing. You can read to get started --- but the
main thing is to understand that a *slice* is a container for resources.
Creating a slice just creates an object at a *Slice Authority*, to which
a set of users is bound (these users can modify the slice and its
resources). You get a slice and a slice credential from a *Slice
Authority*, a GENI component. When you present a slice credential to a
*Component Manager* (or an *Aggregate Manager*), along with a request
for resources, that CM may honor that request, and if it does, gives you
resources in a collection of *slivers* bound to your slice at that CM.
In the ProtoGENI world, each sliver is a node, or a LAN, or some other
resource. However, we often refer to the collection of slivers
associated with a slice at the CM as the *sliver* itself. Said another
way, a slice is a portion of a federated testbed with multiple,
mutually-trusting clusters, each providing a set of resources. You
request resources at a cluster, bound to your slice, and the resources
are called slivers. In the ProtoGeni world, the ProtoGeni SA will give
you a slice and a credential for that slice, and that credential can be
used to get you slivers at any of the ProtoGeni CMs (in the ProtoGeni
world, a CM arbitrates resource allocation for a whole cluster). At
other GENI testbeds, a sliver might be a single node. In the ProtoGENI
world, a sliver is a lot like an Emulab experiment. It's just that in
ProtoGENI, you might have multiple slivers, one at each of the ProtoGENI
CMs, all associated with one slice!
(Note: in the ProtoGENI world, each XMLRPC server serves one or more
endpoints. For instance, if you are invoking a GENI "slice authority"
method, you call Resolve(slice_urn) at -- and thus you are
method, you call ``Resolve(slice_urn)`` at
```` -- and thus you are
using the "sa" endpoint, which provides the slice authority GENI
interface. Thus, the "elasticslice" API is available at
/protogeni/xmlrpc/dynslice (dynslice is the legacy name). Its methods
``/protogeni/xmlrpc/dynslice`` (dynslice is the legacy name). Its methods
are described below.)
In this model, the client may call the new CMv2 methods AddNodes and
DeleteNodes to add and delete nodes from an existing sliver; the
In this model, the client may call the new CMv2 methods ``AddNodes`` and
``DeleteNodes`` to add and delete nodes from an existing sliver; the
manifest and ticket are adjusted accordingly. If nodes are added, they
are allocated to the user for the duration of the ticket.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment