Bug 5444 – Campaign: Add workspace status service and client

Bug 5444 - Campaign: Add workspace status service and client

Summary:

Campaign: Add workspace status service and client

Status:	RESOLVED FIXED

Product:	Nimbus
Component:	Campaign
Version:	TP1.2.4
Platform:	PC Linux

Importance:	P3 enhancement
Target Milestone:	---
Assigned To:	Kate Keahey

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2007-07-16 18:36 by Tim Freeman
Modified:	2007-10-10 15:21 (History)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description From Tim Freeman 2007-07-16 18:36:11

Campaign: Add workspace status service and client

Campaign Leader: Tim Freeman

Technologies: VWS

Objective:
Provide a remote query mechanism to allow clients to review their past and
current usage of the service.

Benefits:
Gives clients their past and current usage information to allow them to check
for consistency and see what information the service is using for authorization
and charging.

Implementation details/tasks:
1) Add new service WSDL to the workspace collection
2) Implement this server side by querying the accounting reader (see Bug
#5443).
3) Implement the query operation in the reference client
4) In the status service implementation support queries against the same WSRF
resource(s) the Workspace Factory Service has for the create operation.
5) Advertise the charge granularity in the status service RP
6) Return used and reserved time as separate fields in the response

------- Comment #1 From Tim Freeman 2007-07-16 18:36:56 -------

Salient portion of WSDL:

            <!--==================================================-->
            <!--               resource properties                -->
            <!--==================================================-->

            <xs:element name="chargeGranularity" type="xs:int"/>

            <xs:element name="StatusRPSet">
                <xs:complexType>
                    <xs:sequence>
                        <xs:element ref="tns:chargeGranularity" />
                    </xs:sequence>
                </xs:complexType>
            </xs:element>

            <!--==================================================-->
            <!--    Operational input/output type declarations    -->
            <!--==================================================-->

            <xs:element name="queryUsedAndReserved"
                        type="tns:voidType"/>

            <xs:complexType name="voidType"/>

            <xs:element name="usedAndReservedTime"
                        type="tns:usedAndReservedTime_Type" />

            <xs:complexType name="usedAndReservedTime_Type">
                <xs:sequence>
                    <xs:element name="usedTime"
                                type="xs:duration"/>
                    <xs:element name="reservedTime"
                                type="xs:duration"/>
                </xs:sequence>
            </xs:complexType>

            <xs:element name="WorkspaceStatusFault">
                <xs:complexType>
                    <xs:complexContent>
                        <xs:extension base="wsbf:BaseFaultType"/>
                    </xs:complexContent>
                </xs:complexType>
            </xs:element>

------- Comment #2 From Tim Freeman 2007-07-16 18:39:14 -------

New workspace-status program deploys to $GLOBUS_LOCATION/bin

Salient commandline options:

 -q,--queryusage                 Query for used and reserved time
 -r,--queryrp                    Query the status service resource property
information
 -s,--service <url>              Service URL
 -e,--eprFile <file>             Loads EPR from file

------- Comment #3 From Tim Freeman 2007-10-10 15:21:01 -------

Committed to workspace_tp_1_3_0_branch