Changes between Version 70 and Version 71 of instructions

Show
Ignore:
Timestamp:
09/01/10 15:02:58 (9 years ago)
Author:
anirban (IP: 152.54.9.209)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • instructions

    v70 v71  
    1341345. If the app did not come up as expected, then the container (ORCA_HOME) and actors (ORCA_LOCAL) are likely misconfigured.  There is no easy way to debug configuration errors.  Check the container logs in tomcat/logs/orca*.log.   You can add more information to these logs by editing the log4j properties in ORCA_HOME/config/container.properties, e.g., to add "%C %M %L" to the ConversionPattern to print the class, method, and line number for each log message.  It is also possible to load config.xml directives into the running web GUI, under the admin tab, which gives additional error reporting through the GUI.  Config processing is not atomic or idempotent: if config processing fails, some directives may have completed successfully. 
    135135 
    136 '''Feature:''' 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). In short, Click Site tab -> View Exported Resources -> manage -> Copy the guid of the ticketd 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". 
     136'''Feature:''' 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). In short, Click Site tab -> View Exported Resources -> manage -> Copy the guid of the ticketd 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. 
    137137 
    138138'''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.