Changes between Version 81 and Version 82 of instructions

Show
Ignore:
Timestamp:
11/17/10 17:50:15 (8 years ago)
Author:
ibaldin (IP: 152.54.9.21)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • instructions

    v81 v82  
    11== Prerequisites == 
     2 
    23[wiki:Prerequisites Software prerequisites] 
    34 
     
    143144'''Feature:''' in multi-container configurations claim processing for exported tickets (advertisements/delegations) must be done manually after the container stands up, since it requires inter-actor communication.  Go to the broker tab, create an inventory slice, and claim the delegation, using the GUID for the exported ticket, which is visible under the site tab (view exported resources). '''This does not apply to emulation mode example''' 
    144145 
    145 '''Quick-start for testing emulation mode''' Click Site tab -> View Exported Resources -> manage -> Copy the guid of the ticketed reservation; Click Broker tab -> Claim Resources -> Paste the guid -> Click Claim . To further test whether you can create reservations, go to the user tab, click on "Create Reservation", enter number of units of vm (< 100), and then click "Create". Click on "View All Reservations" to see the status of the reservation you created. The status should turn "Active" after a few seconds. To test whether you can close the reservation you created, select the reservation in the same screen, and select "Close" from the drop-down menu next to Action:. Confirm the close, and now if you click on "View All Reservations", you will see the state of the reservation transitioning to "Closed". This should test the basic features of the Emulation mode. 
     146'''Feature:''' if you restart tomcat, it will recover your previous container state.  If you redeploy, or undeploy and redeploy, it will reinitialize the container to its fresh state, and delete state about existing slices and reservations from the database.  Note also that tomcat does not always stop cleanly: sometimes it is necessary to kill the process.  This case may lead to problems on recovery due to an unidentified bug.  If you don't need to recover, then re-deploy.  If you want to be sure your tomcat is clean, you might first remove the tomcat/webapps/orca* directories before restarting the server and redeploying. 
    146147 
    147 '''Feature:''' if you restart tomcat, it will recover your previous container state.  If you redeploy, or undeploy and redeploy, it will reinitialize the container to its fresh state, and delete state about existing slices and reservations from the database.  Note also that tomcat does not always stop cleanly: sometimes it is necessary to kill the process.  This case may lead to problems on recovery due to an unidentified bug.  If you don't need to recover, then re-deploy.  If you want to be sure your tomcat is clean, you might first remove the tomcat/webapps/orca* directories before restarting the server and redeploying. 
     148=== Quick Start emulation mode test === 
     149 
     150Videos attached to this page show how the system works once it is installed. A simple test with the default actor configuration described above is to 
     151 
     152 1. Login to the ORCA portal  
     153 2. Go to Admin tab and click 'View Actors'. Verify that 3 actors are Online. 
     154 3. Go to User tab (Slice Manager). Click on 'Create Reservation'. Change the number of Units from 1 to something else (for anything greater than 10 you will receive only 10 units as that is the size of the initial delegation) 
     155 4. Click 'Create' button 
     156 5. Click 'View Reservations'. Click refresh button of your browser until the reservation goes into 'Active' state. 
     157 6. You can optionally close the reservation by selecting a check-box next to it and selecting 'Close' from the menu. 
     158 
     159 1. Click Site tab -> View Exported Resources -> manage -> Copy the guid of the ticketed reservation; Click Broker tab -> Claim Resources -> Paste the guid -> Click Claim . To further test whether you can create reservations, go to the user tab, click on "Create Reservation", enter number of units of vm (< 100), and then click "Create". Click on "View All Reservations" to see the status of the reservation you created. The status should turn "Active" after a few seconds. To test whether you can close the reservation you created, select the reservation in the same screen, and select "Close" from the drop-down menu next to Action:. Confirm the close, and now if you click on "View All Reservations", you will see the state of the reservation transitioning to "Closed". This should test the basic features of the Emulation mode.