Changes between Version 8 and Version 9 of deploy-sm

Show
Ignore:
Timestamp:
05/09/11 17:30:11 (8 years ago)
Author:
ibaldin (IP: 152.54.9.21)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • deploy-sm

    v8 v9  
    2222== Using GENI AM API controller plugin == 
    2323 
    24 This plugin exports a GENI AM API-compliant XMLRPC API that can be exercised using Python scripts located under $ORCA_SRC/controllers/xmlrpc/resources/scripts.  
     24This plugin exports a GENI AM API-compliant XMLRPC API that can be exercised using Python scripts shipped with ORCA source distribution.  
    2525 
    26  1. Open a terminal and navigate to the directory, ORCA_HOME/controllers/xmlrpc/resources/scripts, which has simple python client scripts that invoke methods to list resources, create slivers, check sliver status, delete slivers etc. Relative to ORCA_HOME, do 
    27 {{{ 
    28 $ cd controllers/xmlrpc/resources/scripts 
    29 }}} 
     26 1. Open a terminal and navigate to the directory, $ORCA_HOME/controllers/xmlrpc/resources/scripts, which has simple python client scripts that invoke methods to list resources, create slivers, check sliver status, delete slivers etc.  
    3027 1. To list the available resources, run the following command. This should output the available resources in the form of abstract NDL description of the Eucalyptus substrate. 
    3128{{{ 
    32 $ python ListResources.py 
     29$ python ListResources.py -s http://hostname:11080/orca/xmlrpc  
    3330}}} 
    34  1. To create a sliver, run the 'createSliver' script. The provided script reads in a NDL resource request from a file called 'id-mp-Request2.rdf'. The example request corresponds to creating 3 virtual machines connected by 3 internal vlans in a triangle topology, with each vm having two interfaces and talking to the other two vms on a separate interface. 
     31 1. To create a sliver, run the 'createSliver' script. The script needs the name of the file containing resource request in NDL. A number of examples are available under [source:orca/network/trunk/src/main/resources/orca/network]. The response to the script will look approximately as shown (UUIDs and Reservation IDs will be different. 
    3532{{{ 
    36 $ python createSliver.py 
     33$ python createSliver.py -s http://hostname:11080/orca/xmlrpc -k ~/.ssh/id_dsa.pub -i some-slice-name-no-spaces -r /path/to/request/file/in/NDL 
    3734... 
    3835[   Slice UID: 05d30971-2b1c-4a52-817c-bc192a878a8b | Reservation UID: 5063cd58-75cf-4c58-8824-cf86d329b9d9 | Resource Type: unc.vm | Resource Units: 1 ]  
     
    4441... 
    4542}}} 
    46  1. Once createSliver returns, it outputs the slice UID. You should use the slice UID to operate on the instantiated sliver - to check status, delete etc. Open a file called 'sliceID.txt' and paste the slice UID into it. For the above example, 
     43 1. To check the status of the sliver, run the 'sliverStatus' script (use the same slice name as used in the createSliver step) 
    4744{{{ 
    48 $ cat sliceID.txt 
    49 05d30971-2b1c-4a52-817c-bc192a878a8b 
    50 $ 
     45$ python sliverStatus.py -s http://hostname:11080/orca/xmlrpc -i some-slice-name-no-spaces 
    5146}}} 
    52  1. To check the status of the sliver, run the 'sliverStatus' script. This script assumes that the slice UID is in the file 'sliceID.txt'. This should output the status of each individual resource and the overall sliver status. 
     47 1. To delete the sliver, run the 'deleteSliver' script.  
    5348{{{ 
    54 $ python sliverStatus.py 
     49$ python deleteSliver.py -s http://hostname:11080/orca/xmlrpc -u some-slice-name-no-spaces 
    5550}}} 
    56  1. To delete the sliver, run the 'deleteSliver' script. This script assumes that the slice UID is in the file 'sliceID.txt'. 
    57 {{{ 
    58 $ python deleteSliver.py 
    59 }}}