Information Technology Reference
In-Depth Information
Application on the selected resource. Beside accesses, visibility of resources,
applications, and storages can be multiple: private (only the user who de
ned the
entity may use it), protected (users belonging to the organization of the user who
de
ned the entity may use it), and public (every user of the CBP may use it).
In the CBP it is possible to de
ne prices for the usage of the different entities, for
example, the execution cost of one Gromacs job may include a $1 one-time fee and
$0.25 for each CPU hour consumed by the job. All these costs appear at the
organization level, meaning every user
s spending will be charged against the
balance of the organization to which he or she belongs. The operators of the CBP
ask for a
'
fixed percentage of these prices. Of course, in case of academic or local
cloud infrastructures, de
ning such prices is not necessary at all; thus using such
resources can be completely free for the users.
Access to the CBP is possible at different levels: the web interface, a Java API, and
a REST API. The web interface (a sample job submission shown in Fig.
7.1
) offers the
most convenient way for users to run jobs, and exposes all the functionalities of the
CBP, like resource editing, invoicing, and user management (given that suf
cient
roles are available). The Java API offers a convenient way to access most of the CBP
functionalities from software written in Java, like WS-PGRADE/gUSE. Finally, the
REST API can be used to access all CBP functionalities through a RESTful [REST]
interface, basically providing a programming language-independent way to access
the CBP services.
As already mentioned, CloudBroker offers the SaaS service model: clients
invoking the CBP can select any of the preregistered applications to run, and
provide input
files. However, it is possible to achieve an IaaS-like operation with
the help of wrapper software: the task of the wrapper software is simply to run one
Search WWH ::
Custom Search