CloudBroker integration to WS-PGRADE/gUSE

Zoltán FarkasMTA SZTAKI LPDSzfarkas@sztaki.hu

gUSE and Cloud support

• No Software as a Service (SaaS) support so far• Google App Engine (Platform as a Service – PaaS)

supported• Grid infrastructure cannot give any QoS support

for running jobs generated from PS applications

• The CloudBroker Platform (CBP) provides access to scientific and technical SaaS, on a pay-per-use basis.

Goals and IssuesMain goal: To enable running CloudBroker applications (SaaS) as workflow nodes. To integrate the SaaS capabilities of CB into the gUSE/WS-PGRADE system and therefore, to provide for users a gUSE/WS-PGRADE -> CB service path.

However, the set of runnable and usable applications is limited only to the SaaS softwares of CloudBroker platform.

CloudBrokerWS-

PGRADE/gUSE

DCI-Bridge

The main concept 1

Gamess GromacsAutodock Open FoamBlast RosettaXtandem ...

API

gUSE

WS-PGRADE Workflow Configuration Portlet CloudBroker UI Portlet

UI

DCI-BRIDGE

Integrate the SaaS capabilities of CB into the gUSE/WS-PGRADE system.

Enable WS-PGRADE users to run softwares (SaaS) exposed by the CB platform.

SaaS (Softwares as a Service)

The two main integration steps: 1. Connect WS-PGRADE users/portals and CB users/organizations. 2. Extend DCI Bridge with CB platform support (CB plugin development).

CloudBroker plugin

Expose the CloudBroker UI through WS-PGRADE interface by proxy.

2

User Mapping Portlet

1 3

The main concept 2• To establish WS-PGRAGE -> CloudBroker path needs to develop a CloudBroker plugin. • User mapping:

– Individual: every WS-PGRADE portal user has to set its own CBP credential– Automatic: CBP credential usage is transparent for WS-PGRADE Portal users

• CloudBroker UI portlet: expose the CloudBroker UI through WS-PGRADE interface by a portlet. The goal is to directly access from WS-PGRADE the CB interface environment for users.

• The three problems should be handled at three levels:– UI level (WS-PGRADE)– DCI-Bridge level– gUSE/WFI level

The main Concept 3: Use Case

• CloudBroker resource administration• CloudBroker credential handling• The Job Configuration• The CloudBroker UI portlet

CloudBroker resource administration

Name

Platform URL

Credential handling type

User mapping: individual concept

For individual user mapping is necessary to develop a user mapping portlet in WS-PGRADE for gUSE users to CB login. This simple portlet exposed through under Security/CloudBroker in WS-PGRADE site for individual user:

User enters the existing CB

username and CB password

User mapping: automatic

• Useful in case of application-specific portals, where we would like to hide the backend infrastructure

• CBP users are created on-demand for WS-PGRADE users

• All such created CBP user resource usages are billed agains an organizational account

UI level – WS-PGRADE: Job Configuration

e.g. DSP 1.0

e.g. Amazon EC2

e.g. Amazon EC2 m1.small i386

e.g. us-east-1

SOFTWARE NAME

RESOURCE NAME

INSTANCE TYPE

REGION

IMPLEMENTATION NAME e.g. DSP 1.0 dsp

ARGUMENTS e.g. -f 22 -i 20 -p 723 -n pools.txt

At job configuration workflow editor gets information from

DCI-Bridge about the mandatory data for job running

in cloud.

software_name executable_name resource_name instance_type_nameregion_namearguments

User can select the appropriate

configuration parameter.

JSDL

Command line parameters

Job configuration II.

XML Schema

contents additional CB-specific details

(to define softwares, resources

and regions)

DCI-Bridge level: CB integration 1

1. SaaS list query: new (CB) plugin queries sofwares (SaaS) list from CloudBroker for job sub – to enable running CB softwares as workflow nodes.

CloudBroker plugin

CB plugin queries software list from CB by XML request

message sending to an URL address.

CB plugin saves in DCI-Bridge the received

response in XML

2

1

by REST API

Over HTTP

DCI-Bridge level: CB integration 2

WFI requests configuration data for CloudBroker-type job

submission from WFS.

From response WFI creates a JSDL

fileJSDL

CloudBroker plugin

1

2

The plugin from JSDL data begins a communication to

CB by XML message request-response sending to an URL

address:1. create job, 2. upload data, 3. submit job 4. check status

5. download data

Over HTTP

3

by REST API

2. Job submission

UI level: CloudBroker UI portletTo directly access the CB interface environment from WS-PGRADE for users.

WS-PGRADE – CB UI Portlet

The implementation would be a JSP-based

work by using the <iframe> HTML tag.

QUESTIONS?

Thank you for your attention!