Changes between Version 102 and Version 103 of instructions

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

--

Legend:

Unmodified
Added
Removed
Modified
  • instructions

    v102 v103  
    181181'''BIG FAT NOTE:''' Starting with Camano 3.0 the Python tools have been revised to take command line parameters like server URL, slice ID etc. These are no longer hard-coded or saved into files. With any of the scripts execute it with -h option to find out all possible command line parameters. The semantics of the scripts remain unchanged. 
    182182 
    183  1. Login to the ORCA portal  
    184  2. Go to Admin tab and click 'View Actors'. Verify that 3 actors are Online. Go to Broker tab and click 'View Inventory'. Verify that there are 10 virtual machines and 1000 internal vlans. 
    185  3. Go to User tab (Slice Manager). Click on 'Start Controller'. Select 'XML-RPC Controller' from the drop-down menu corresponding to 'Controller'.  
    186  4. Click 'Create' button. This should start the xml-rpc controller and the xml-rpc server that responds to xml-rpc clients on a port (default: 20001)  
    187  5. 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 
    188 {{{ 
    189 $ cd controllers/xmlrpc/resources/scripts 
    190 }}} 
    191  6. 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. 
    192 {{{ 
    193 $ python ListResources.py 
    194 }}} 
    195  7. 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. 
    196 {{{ 
    197 $ python createSliver.py 
    198 ... 
    199 [   Slice UID: 05d30971-2b1c-4a52-817c-bc192a878a8b | Reservation UID: 5063cd58-75cf-4c58-8824-cf86d329b9d9 | Resource Type: unc.vm | Resource Units: 1 ]  
    200 [   Slice UID: 05d30971-2b1c-4a52-817c-bc192a878a8b | Reservation UID: 7c1185e0-337b-490d-92f2-119d7f96a367 | Resource Type: unc.vm | Resource Units: 1 ]  
    201 [   Slice UID: 05d30971-2b1c-4a52-817c-bc192a878a8b | Reservation UID: b9550c8e-de60-4504-8eb2-563d96f18c35 | Resource Type: uncEuca.vlan | Resource Units: 1 ]  
    202 [   Slice UID: 05d30971-2b1c-4a52-817c-bc192a878a8b | Reservation UID: 4f0ddc63-6e1a-4b55-8547-c2522abd7be1 | Resource Type: uncEuca.vlan | Resource Units: 1 ]  
    203 [   Slice UID: 05d30971-2b1c-4a52-817c-bc192a878a8b | Reservation UID: c7816bf2-0555-4e59-8502-6ed203dede9d | Resource Type: unc.vm | Resource Units: 1 ]  
    204 [   Slice UID: 05d30971-2b1c-4a52-817c-bc192a878a8b | Reservation UID: 33f84b75-0874-444c-9809-a017b799a868 | Resource Type: uncEuca.vlan | Resource Units: 1 ] 
    205 ... 
    206 }}} 
    207  8. 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, 
    208 {{{ 
    209 $ cat sliceID.txt 
    210 05d30971-2b1c-4a52-817c-bc192a878a8b 
    211 $ 
    212 }}} 
    213  9. 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. 
    214 {{{ 
    215 $ python sliverStatus.py 
    216 }}} 
    217  10. To delete the sliver, run the 'deleteSliver' script. This script assumes that the slice UID is in the file 'sliceID.txt'. 
    218 {{{ 
    219 $ python deleteSliver.py 
    220 }}} 
    221