Yes, you can do this.
In general, you should edit the membership of your slice before
reserving resources, to be sure that all users can log in to all the
compute resources that you reserve. But in some cases, you can add
members after your reservation.
Here are some instructions for doing these things with Omni. This
message largely repeats instructions listed on the Omni wiki here:
http://trac.gpolab.bbn.com/gcf/wiki/HowTo/UseCHAPIInOmni
----
Adding members to a slice and to existing slivers:
If you have not already done so, update to Omni 2.5, and
re-configure your omni by re-downloading your Omni bundle from the
GENI Portal and re-running omni-configure. If you need help doing
this, ask.
Once you have done that, you can do a number of things:
1) You can add a new member to your slice (just like the operation
at the portal).
Example:
You have a project MyProject.
JoeSmith is in MyProject (and has at least 1 SSH key registered),
but Joe is not in your slice MySlice.
The omni command "addslicemember <slicename> <member
username>" will add Joe as a member of the slice.
Note that this does NOT install Joe's SSH keys on any existing
sliver reservations/ nodes in your slice.
To confirm that this did what you expect, you can list the members
of your slice:
omni listslicemembers <slicename>
2) Once you have re-configured Omni for Omni2.5, all members of your
Portal slice will have their SSH keys installed on NEW slivers/nodes
that you reserve using Omni.
So for example, if you added Joe using "addslicemember" per step 1,
then Joe cannot yet log in to the nodes you already have reserved.
But if you then reserve resources at a new aggregate, Joe's SSH keys
will be installed on that new node, and Joe can log in.
3) At InstaGENI racks, it is possible to update the SSH keys that
are installed on existing nodes/slivers.
So assume you added Joe to MySlice per step 1 above. You want Joe to
be able to log in to your existing nodes (not just new nodes).
You can do the following:
omni -V3 --useSliceAggregates --useSliceMembers poa
<slicename> geni_update_users
This command, while it may take a while, will ensure that all
members of your slice as listed at the portal have their registered
SSH keys installed on all your existing InstaGENI nodes (include
anyone you added with 'addslicemember' per step 1).
4) You can combine steps 1 and 3, to both add a new member to your
slice and install their keys on existing slivers, using a simple
script that just calls both functions for you. This script is
available for Linux users of Omni as
examples/addMemberToSliceAndSlivers.py. Usage:
addMemberToSliceAndSlivers <slicename> <username>
I hope this helps,
Aaron