Custom Query (98 matches)

This test scenario uses two user accounts:

• lnevers1 urn:publicid:IDN+pgeni.gpolab.bbn.com+user+lnevers1
• lnevers urn:publicid:IDN+pgeni.gpolab.bbn.com+user+lnevers

The user "lnevers" binds the user "lnevers1" to a slice. User "lnevers1" gets slice credentials and creates a sliver. User "lnevers" with the lnevers1 slice credentials executes various operations which work and should not.

Here is the test sequence:

1. As user "lnevers", used the protogeni-tests script registerslice.py to bind user "lnevers1" to a slice. The command executed:

   lnevers@sendaria:~/protogeni-tests$ ./registerslice.py --certificate=/home/lnevers/.ssl/pgeni/encrypted.pem --sa=https://www.pgeni.gpolab.bbn.com:443/protogeni/xmlrpc/sa -n bindslice lnevers1
   Got my SA credential
   No such slice registered here:Creating new slice called bindslice
   New slice created: urn:publicid:IDN+emulab.net+slice+bindslice
   Found other user record at the SA, binding to slice ...
   Bound other user to slice at the SA
   

2. User "lnevers1" gets slice credentials:

   lnevers1@sendaria:~/gcf-1.6.2$ omni.py getslicecred bindslice -o
   Result Summary: Saved slice bindslice cred to file bindslice-cred.xml
   

3. User "lnevers1" creates a sliver:

   lnevers1@sendaria:~/gcf-1.6.2$ omni.py createsliver -a insta-utah  bindslice insta.rspec --slicecredfile ./bindslice-cred.xml --api-version 2 -t GENI 3
   Result Summary: Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+bindslice expires 
   on 2012-08-05 00:00:00 UTC
   Reserved resources on https://boss.utah.geniracks.net/protogeni/xmlrpc/am/2.0. 
   

4. Use "lnevers" uses lnevers1 slice credentials to execute various commands which should not work. Note the credential file is renamed "lnevers1-bindslice-cred.xml" to make this capture clearer:

   lnevers@sendaria:~/gcf-1.6.2$ omni.py -a insta-utah listresources bindslice --slicecredfile ./lnevers1-bindslice-cred.xml --api-version 2 -t GENI 3 -o
   Result Summary: Retrieved resources for slice bindslice from 1 aggregates.
   Wrote rspecs from 1 aggregates to 1 files
   Saved listresources RSpec at 'unspecified_AM_URN' to file 
   bindslice-rspec-boss-utah-geniracks-net-protogeni-xmlrpc-am-2-0.xml; . 
   
   
   lnevers@sendaria:~/gcf-1.6.2$ omni.py -a insta-utah sliverstatus bindslice --slicecredfile ./lnevers1-bindslice-cred.xml --api-version 2 -t GENI 3 -o
   Result Summary: Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+bindslice expires 
   on 2012-08-05 00:00:00 UTC
   Saved sliverstatus on bindslice at AM https://boss.utah.geniracks.net/protogeni/xmlrpc/am/2.0 
   to file bindslice-sliverstatus-boss-utah-geniracks-net-protogeni-xmlrpc-am-2-0.json. 
   
   
   lnevers@sendaria:~/gcf-1.6.2$ omni.py -a insta-utah renewsliver bindslice --slicecredfile ./lnevers1-bindslice-cred.xml --api-version 2 -t GENI 3 -o
   Result Summary: Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+bindslice expires on
    2012-08-05 00:00:00 UTC
   Renewed sliver urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+bindslice at unspecified_AM_URN (https://boss.utah.geniracks.net/protogeni/xmlrpc/am/2.0) until 
   2012-08-04T00:00:00+00:00 (UTC)
   
   lnevers@sendaria:~/gcf-1.6.2$ omni.py -a insta-utah deletesliver bindslice --slicecredfile ./lnevers1-bindslice-cred.xml --api-version 2 -t GENI 3 
   Result Summary: Deleted sliver urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+bindslice on unspecified_AM_URN at https://boss.utah.geniracks.net/protogeni/xmlrpc/am/2.0 
   

Attaching the lnevers1 slice credentials file used by lnevers.

This ticket will capture the process followed to build a VM custom image for OpenVZ containers. Using the existing instructions, the following steps will be completed:

1. Create an Experiment with an existing image
2. Login to node and customize
3. Create a new Image Descriptor and snapshot
4. Wait for the email saying the image creation is done
5. Verify new customized image
6. Make image available

Background: The following email exchange kicked off this effort:

On 8/30/12 11:50 AM, Robert Ricci wrote:

2) We have support for making disk images of VMs (OpenVZ containers) - from a user perspective, it looks basically the same as making an image from a bare metal node. We have our first guinea pig^HH^HH^HH^HH^HH user trying it out right now.

On 8/30/12 12:44 PM, Luisa Nevers wrote:

If you need a 2nd guinea pig... just point me to the instructions.

On 8/30/12 12:54 PM, Robert Ricci wrote:

There are no instructions it looks the same as doing it for a bare metal node.

On 8/30/12 1:07 PM, Luisa Nevers wrote:

So the existing instructions now needd to be modified to remove all instances on "physical nodes"? Sounds good, I will use the existing instructions.

The sliver named "lninsta" was created to request 4 VMs. Two of the requested VMs have been in geni_status "notready" for over 1 hour. The two nodes are:

pc3.utah.geniracks.net port 32826 
pc3.utah.geniracks.net -p 32827

A second sliver named "lninsta-3" was created to request 3 VMs. One of the VMs has also been in geni_status "notready" for over 1 hour. The node is:

pc1.utah.geniracks.net -p 33340