Information Technology Reference
In-Depth Information
submission requests in the form of OGSA-BES standard JSDL documents and
ensures their execution in the selected DCI. These two aspects can be accessed
concurrently; that is, it is possible to con
gure the DCI Bridge while it accepts and
processes jobs. The con
guration aspect is reachable through a simple web inter-
face, whereas the job execution aspect can be used through a web service interface.
7.4.2.3 Con
guration Aspect
One gateway may be connected to a number of CBP services. In the con
guration
view the DCI Bridge administrators may enable or disable the CBP plugin
(resulting in disabling access to all the CBP services con
gured), and may add or
modify existing CBP services. Figure 7.6 shows the con
guration of a CBP service.
Different properties can be set for a given CBP service, like the name of the
service, the API URL of the targeted CBP service, the user management type (the
only available option is
, meaning every WS-PGRADE user has to
provide its own credentials to use the speci
Individual
cate
extension should be used), and CBP application for running own executable
(enabling the IaaS working model). Description of other properties is available in the
DCI Bridge admin manual [DCIBRIDGE]. A properly con
ed CBP service, or the robot certi
gured DCI Bridge CBP
service can be used to run jobs.
7.4.2.4 Job Management Aspect
DCI Bridge accepts job submission requests through its OGSA-BES interface in the
form of JSDL documents. Notice that the WFI, when using WS-PGRADE, auto-
matically generates this JSDL document; thus this is completely hidden from the
users. In the JSDL, gUSE makes use of a few extensions to the original JSDL
Fig. 7.6 Settings of a CloudBroker Platform service in the DCI Bridge
Search WWH ::




Custom Search