Request access to a testbed. The request includes the various resources needed (loosely), the identity of the requester, access credentials andscheduling information. A successful response includes enough information for the federation system to access the testbed and actually request resources.

Release an allocation of access to a testbed. This informs the testbed that it is no longer necessary to allow the access mthods negotiated by a RequestAccess cal.

A request to create a federated experiment from the included description. Credentials and access information is also provided. On success a logical description of the experiment is returned as well as the information about federated testbeds needed to access local services.

A request for the virtual topology of the experiment. Requesters with different access rights may receive different information.

A request for the visualization of the experiment. This is really a legacy interface for visual tools that cannot generate their own visualization. Requesters with different access rights may receive different information.

A one-stop request for meta-data on the experiment. Includes all the info from a Vtopo and a Vis request.

Stop this experiment and deallocate its resources.

These are really very straight ahead SOAP RPC bindings. They're 1.1 SOAP and not much outside the defaults. No interesting header packing or fault configuration yet. The bindings of this operation are straightforward SOAP RPC 1.1.

The bindings of this operation are straightforward SOAP RPC 1.1.

The bindings of this operation are straightforward SOAP RPC 1.1.

The bindings of this operation are straightforward SOAP RPC 1.1.

The bindings of this operation are straightforward SOAP RPC 1.1.

The bindings of this operation are straightforward SOAP RPC 1.1.

The bindings of this operation are straightforward SOAP RPC 1.1.

Fedd resource access service