Changes between Version 90 and Version 91 of instructions

Show
Ignore:
Timestamp:
11/23/10 16:47:40 (8 years ago)
Author:
anirban (IP: 152.54.6.35)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • instructions

    v90 v91  
    190190 12. Validate that the claim succeeded by clicking on 'View Inventory'  
    191191 13. Follow steps 3, 4 and 5 of the previous example to create a user reservation. 
     192 
     193=== Testing the sample XML-RPC controller in emulation mode === 
     194 
     195This section summarizes how to test the xml-rpc controller in emulation mode. It assumes that you have already deployed the orca webapp into a running tomcat container using the above instructions. The steps are the following. 
     196 
     197 1. Login to the ORCA portal  
     198 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. 
     199 3. Go to User tab (Slice Manager). Click on 'Start Controller'. Select 'XML-RPC Controller' from the drop-down menu corresponding to 'Controller'.  
     200 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)  
     201 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 
     202{{{ 
     203$ cd controllers/xmlrpc/resources/scripts 
     204}}} 
     205 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. 
     206{{{ 
     207$ python ListResources.py 
     208}}} 
     2097. 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. 
     210{{{ 
     211$ python createSliver.py 
     212... 
     213[   Slice UID: 05d30971-2b1c-4a52-817c-bc192a878a8b | Reservation UID: 5063cd58-75cf-4c58-8824-cf86d329b9d9 | Resource Type: unc.vm | Resource Units: 1 ]  
     214[   Slice UID: 05d30971-2b1c-4a52-817c-bc192a878a8b | Reservation UID: 7c1185e0-337b-490d-92f2-119d7f96a367 | Resource Type: unc.vm | Resource Units: 1 ]  
     215[   Slice UID: 05d30971-2b1c-4a52-817c-bc192a878a8b | Reservation UID: b9550c8e-de60-4504-8eb2-563d96f18c35 | Resource Type: uncEuca.vlan | Resource Units: 1 ]  
     216[   Slice UID: 05d30971-2b1c-4a52-817c-bc192a878a8b | Reservation UID: 4f0ddc63-6e1a-4b55-8547-c2522abd7be1 | Resource Type: uncEuca.vlan | Resource Units: 1 ]  
     217[   Slice UID: 05d30971-2b1c-4a52-817c-bc192a878a8b | Reservation UID: c7816bf2-0555-4e59-8502-6ed203dede9d | Resource Type: unc.vm | Resource Units: 1 ]  
     218[   Slice UID: 05d30971-2b1c-4a52-817c-bc192a878a8b | Reservation UID: 33f84b75-0874-444c-9809-a017b799a868 | Resource Type: uncEuca.vlan | Resource Units: 1 ] 
     219... 
     220}}} 
     2218. 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, 
     222{{{ 
     223$ cat sliceID.txt 
     22405d30971-2b1c-4a52-817c-bc192a878a8b 
     225$ 
     226}}} 
     2279. 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. 
     228{{{ 
     229$ python sliverStatus.py 
     230}}} 
     23110. To delete the sliver, run the 'deleteSliver' script. This script assumes that the slice UID is in the file sliceID.txt. 
     232{{{ 
     233$ python deleteSliver.py 
     234}}}