Custom Query (1408 matches)

This effort is underway. Please update this ticket with expected timeline for completion and pointers to any documentation.

See also ticket #142.

Per 2Q09 QSR:

2. Adding DOME-specific functionality to ORCA.

In order for ORCA to schedule DOME resources, we needed to implement two components and integrate them into ORCA. The first component was the DOME controller. The controller provides an XML-RPC interface for requesting leases. Once the controller has received an external lease request, it makes a request of ORCA to reserve the resources. The controller also handles events from ORCA regarding the state of the ticket. The second component is the handler. The handler is responsible for notifying the DOME resource pool of the lease activation ("join") and termination ("leave"). ORCA instigates these events by executing DOME ant scripts, which invoke tasks that initiate XML-RPC calls.

3. Integrating ORCA with the DOME GENI portal.

We have added an ORCA component to the DOME portal that we are developing for GENI. The portal is the interface a researcher uses for reserving DOME resources; it shields end users from the specifics of ORCA. The portal makes XML-RPC calls to the DOME ORCA controller to request leases. The portal additionally makes calls into the controller to get the status of tickets. The portal exports XML-RPC interfaces to be called by the DOME ORCA handler when leases are initiated or terminated. The portal maintains information about pending and active leases, and updates state when notified by ORCA. Besides providing the user interface for researchers, the portal is accessed by the DOME nodes located on the buses. One interaction between the bricks and portal is to download experiment to the buses. The portal uses its knowledge of active and pending leases to assign download priorities to experiments. The bricks query the portal to find out if a lease has been granted or revoked in order to schedule experiments.

4. Adding ORCA lease support to the mobile nodes.

We have developed software for the bricks to make use of the download priorities assigned by the portal. The priorities are used for choosing an experiment to download, and for garbage collection if available disk space falls below a threshold. We have also developed software for the bricks to launch and terminate experiments as leases are granted or revoked. The bricks also provide information to the portal that can be used by end users, such as what experiments have been successfully downloaded and launched.

Sorry for the delay,

1. Table for 1 laptop
2. projector or large format display + cable
3. two power outlets (laptop+projector)
4. Wired network connection (preferred, wireless if only option)

Also if you are looking for equipment, I can provide network switches, cables, power distribution.

Mike Blodgett ​mblodget@cs.wisc.edu