OPTIMIS Open Call Information Package

8/6/2019 OPTIMIS Open Call Information Package

http://slidepdf.com/reader/full/optimis-open-call-information-package 1/22

Project Acronym: OPTIMIS

Project Title: Optimized Infrastructure ServicesProject Number: 257115

Instrument: Integrated Project

Thematic Priority: ICT-2009.1.2 – Internet of Services, Software and

Virtualisation

OPTIMIS Open Call Information

Package



OPTIMIS Open Call Information Package

© OPTIMIS Consortium Page 1 of 1

Table of Contents

1 OPTIMIS IN A NUTSHELL ................................................................................................................ 1

2 OPEN CALL USE CASES DESCRIPTIONS ........................................................................................... 3

2.1 CLOUD BURSTING ....................................................................................................................... 3 2.1.1 Functional Description .................................................................... ........................................ 3 2.1.2 Analysis of needs and requirements ....................................................................................... 3 2.1.3 Actors involved. ...................................................................................................................... 4 2.1.4 OPTIMIS Components Demonstrated .................................. ................................................... 4 2.1.5 Novelty of the solution with OPTIMIS ........................................................................... .......... 4

2.2 CLOUD BROKERAGE .................................................................................................................... 4 2.2.1 Functional Description .................................................................... ........................................ 4 2.2.2 Analysis of needs and requirements ....................................................................................... 6 2.2.3 Actors involved ....................................................................................................................... 6 2.2.4 OPTIMIS Components Demonstrated .................................. ................................................... 6 2.2.5 Novelty of the solution with OPTIMIS ........................................................................... .......... 7

3 TIME TABLE ................................................................................................................................... 1

4 WORK PACKAGE DESCRIPTIONS .................................................................................................... 1

4.1 WORK PACKAGE DESCRIPTION – WP1.1 REQUIREMENTS ELICITATION ....................................................... 1 4.2 WORK PACKAGE DESCRIPTION – WP6.3 CLOUD BURSTING............................................................... ....... 5 4.3 WORK PACKAGE DESCRIPTION – WP6.4: CLOUD BROKERAGE........................................................... ....... 7 4.4 WORK PACKAGE DESCRIPTION – WP 7.3 EXPLOITATION........................................................ .................. 9

ANNEX A. LICENSE CONDITIONS. ..................................................................................................... 11





1 OPTIMIS in a nutshell

OPTIMIS vision is that the hybrid cloud model will become a commonplace in the future,

realized by private clouds interacting with a wide ecosystem of cloud providers. In order to

make reality this vision, OPTIMIS identifies needs to be addressed in the complete Cloud

Service life-cycle. It envisions providing optimized tools for Service Construction, CloudDeployment and Cloud Operation based on Trust, Risk, Eco-efficiency and Cost that enables a

variety of Cloud scenarios such as hybrid Cloud and Cloud brokerage.

OPTIMIS vision is centered on the following innovations:

1.

Optimized Service Construction, Deployment, and Execution for Cloud Infrastructures byoffering tools to efficiently manage the full life cycle of services. These tools will provide

for simplified construction of services, and for making informed deployment and runtime

management decisions based on risk assessment models for evaluation of providers and

will permit the appropriate establishment of fault tolerance mechanisms.

2. Dependable Sociability = Trust + Risk + Eco + Cost. This equation captures the essence of

the optimized cloud ecosystem generated by the mutual trust between consumers and

providers in a secure environment and the risk of not accomplishing specific ecological or

economical goals.

3. Adaptive and Eco-Aware Self-Preservation for dynamic and pro-active management of

cloud infrastructures. This type of management provides for seamless adaptability,

reliability, and scalability of infrastructures according to predicted and unforeseen

changes in services and hence leads to optimized use of resources with regard of

economical and ecological factors.

4. Provisioning on Multi-Cloud Architectures and on Federated Cloud Providers enabling

novel and complex composition of clouds considerably extending the limited support for

utilizing resources from multiple providers in a transparent, interoperable, and

architecture independent fashion.

5. Cloud-nomics: Foreseeing New Market Roles and Value Activities for further

development of the economics of Cloud Computing by predicting market evolution,

investigating new business models, as well as investigating and proposing legal and

regulatory aspects that govern cloud operation.





The primary deliverable of the project will be an open specification and a toolkit that supports

the construction of the multiple coexisting architectures that make up the next generation

Cloud Service Ecosystem.

The OPTIMIS toolkit will provide a set of independent components that can be adopted, in

either full or in part, by Infrastructure Providers (IPs) that offer the capacity required by

services, and by Service Providers (SPs) that use this capacity to deliver services. These

components spread all over the Service Life-cycle.

The toolkit will provide a set of independent components that can be adopted, in either full or

in part, by Infrastructure Providers (IPs) that offer the capacity required by services, and by

Service Providers (SPs) that use this capacity to deliver services. The IPs and SPs may, forexample, use the toolkit for developing new infrastructure-as-a-service or platform-as-a-

service offerings, or to simply enable more efficient delivery of services running on local or

remote resources. There is, thus, a unique opportunity for Small and Medium Enterprises

(SMEs) to act either as IPs or SPs, or join these two roles into one and create their own private

clouds, with the possibility to move part of their operations to public clouds (commercial IPs).

In addition to the main beneficiaries of the results of this project (the Service Providers and

Infrastructure Providers), we foresee that also brokers, independent software vendors (ISVs),

and service consumers (end-users) will benefit from these results.





2 Open Call Use Cases Descriptions

2.1 CLOUD BURSTING

2.1.1 Functional Description

A company owning their own Cloud infrastructure “private Cloud” and willing to, duringcertain time elapses and given certain circumstances use resources from an external Cloud

provider. This use case plan to show how an organization has the possibility to scale out their

infrastructures and rent the resources to a third-party provider. The renting of the resources

provides elasticity to infrastructure and let the organization to confront dynamically the

fluctuations on demand.

The internal Cloud has to provide mechanisms to detect and determine their own-status: this

is, to verify the degree in which the services it is providing are fulfilling its established service

agreements and energy consumption requirements. But also it has to determine for the

services running in the internal Cloud how critical they are, as well as, privacy or specific

requirements for being migrated to an external Cloud provider. It will be policy-driven by a set

of policies that could identify i.e. a service as non-critical and with low degree of privacy, so a

perfect candidate for automatically migrating to a public Cloud with the minimum cost for the

private Cloud owner. But also, it can be the case of services not allowed to migrate under any

circumstance to a public Cloud, whatever degree of trust and security it offers.

The external Cloud has to satisfy the over-capacity needed by the internal Cloud and execute

dynamically the workloads billing the resources by usage.

2.1.2 Analysis of needs and requirements

A service policy mechanism allows cloud infrastructure to scale out selecting resources

according to the customer’s requirements without human intervention. The internal Cloud will

be able to take this decisions both at service level, but also in an aggregated view, taking

decisions in order to guarantee the self-preservation of the internal Cloud: an example could

be to force the migration of non-critical services that are satisfying theirs SLAs in order to

assure that a critical service that cannot be migrated achieves all resources it requires to fulfill

its SLA.

Once the internal infrastructure has taken the decision of migrate a service from the private

cloud to an external provider, several factors can influence this election:





- Cost: A usual case for non-critical applications would be to minimize costs while the provider

is able to satisfy the SLAs.

- Risk Assessment: As the degree of criticity of applications grows the common behavior is to

try to minimize the risk.

- Environmental impact: The increasing concern for eco-efficient IT, makes the degree in witha provider will consolidate servers, as well as, the energy consumption reports of services

running in a external cloud and important selection criteria .

- Degree of Trust: Externalize to an external provider implies a high degree of reliability and

dependability between the internal cloud manager and its providers. Different services will

have different trust requirements among them in order to externalize a service to its premises.

To ensure the desired functionality in our environment it is necessary to perform the correct

management of license instances in the external cloud, and otherwise the service provider has

to use tools that ensure the integrity of the data between internal and external perspective.

2.1.3 Actors involved.

The cloud tiered architecture model provides specific roles to decide the access privilege of

different actors that interact with the service and the infrastructure.

Service provider: The organization providing the final cloud service; in this particular

situation there are two actors: the internal organization providing a service interface for

customers, and the external organization providing resources to confront the capacity

demand for correct delivery of the encapsulated service.

Service consumer: The organization accessing the hybrid cloud service. This service may be

accessed through friendly interface.

Service procurer: The cloud user obtaining the service on behalf of the consumer.

2.1.4 OPTIMIS Components Demonstrated

OPTIMIS base toolkit: used by the internal cloud to decide when and which resources need

the service to accomplish its functionality.

Cloud Optimizer, used to take the decisions in order to guarantee the self-preservation of

service behavior between the providers.

Service Optimizer, a mechanism to provide the correct interaction between actors to reach

the capacity needs.

2.1.5 Novelty of the solution with OPTIMISTwo scenarios enabled: Multi-cloud and Federated Cloud

Selection of providers based on cost, trust and energy efficiency

Reliable and Secure Cloud providers environment

Support for execution of licensed software

2.2 CLOUD BROKERAGE

2.2.1 Functional Description

The inability to perform cloud brokerage and federation involving the use of multiple cloud

providers is a major hurdle in the use of cloud services by enterprises. Work package 6.4 will





focus on a case study for implementing the infrastructure and framework needed to power

such a service. The different scenario setups that make up the use case, in order of their

orchestration complexity, are as follows:

Enterprise use of multiple cloud providers: in this scenario, an enterprise organisation makes

use of services provided by various cloud providers to fulfil an internal process. For examples

the process could be an one-off marketing initiative that uses CRM data from a SaaS provider

like SAP exposed through their API, data captured within internal systems and data stored in

cloud storages like S3 or databases like SimpleDB. In addition, the enterprise also decides to

use an IaaS service from Sun or Google App Engine to perform the necessary processing of the

gathered data. We will examine the generic requirements of such a process composition from

the enterprise’s view point and the necessary technical resources necessary to realise such an

orchestration. From the point of view of the cloud service providers, we will investigate the

extra capabilities that need to be exposed to enable the enterprise to tie together the full

orchestration requirements. This includes the common requirements such as trust

establishment, identity management; Web Service based API calls for accessing the data etc.

Cloud provider to broker multiple providers to provide a SLA-based tiered pricing model: inthis, an enterprise approaches a cloud broker with a given set of functional and SLA-based

requirements and the cloud broker then picks up the best match in terms of the functions as

well as variables like pricing, SLA parameters and other non-functional requirements like

compliance and certification capabilities. The cloud broker could be just a broker or it could

use its status to provide seamless and federated identity management, access management

and audit capabilities to the enterprise, as shown in the illustration below.

Cloud aggregation ecosystem (CAE): this scenario offers the potential to treat both IT and

business functions as a series of interconnected cloud services. CAE offers a means to architect

a Service Oriented Infrastructure (SOI) on the cloud that is built on the fusion of: (a)

Composition of loosely coupled services based on an evolution of Service Oriented

Architecture (SOA) principles applied to services that reside on cloud platforms (b) Distributed

management of ICT resources applied on federations of cloud platforms (c) network resource

management based on a federated Operational Support System (OSS) architecture built on top

of an in-cloud Network as a Service (NaaS) offering. This scenario adds the capability to

incrementally build new service offerings by mixing together reusable functions (commoncapabilities) provided by off the shelf components and 3rd party cloud platforms in a new

User

BT Broker

ID2amz

ID2sun

Amazon

User

User

User

Identity Brokerage

Entitlement M mt.

Policy Enforcement

Usage Monitoring,

Reporting

Admin

Enterprise

FlexiScale

Network defence,

Platform security





offering. More specifically CAE refers to the federation of a set of distributed virtual hosting

environments for the execution of an application, integrating value-adding services (VAS) with

these hosting environments, and providing a single (logical) access point to this aggregation.

From the perspective of the application consumer, these federations are transparent and

constitute an integral part of the service being offered.

2.2.2 Analysis of needs and requirements

- Comprehensive risk analysis of using a brokerage based federated cloud setup from an

enterprise’s point of view.

- Ability to perform SLA based choosing of cloud services and the need to measure SLAs

and take remedy action against deviations.

- Ability to perform identity and access management for cloud based services using

enterprise and a federation of multiple cloud providers.

- Ability to ensure data confidentiality and information leakage prevention.

- Ability to enforce policy decision uniformly across multiple cloud platforms.

- Ability to programmatically manage cloud platforms and the deployment of serviceson these platforms.

2.2.3 Actors involved

OPTIMIS programming model: used by the service programmer to implement the business

process and bundling service in cloud images.

OPTIMIS toolkit: optimize the execution of the process in the cloud.

Infrastructure provider: acts as cloud broker, provides the infrastructure to execute the

services as well as provide external services that can be used by the programmed service

2.2.4 OPTIMIS Components Demonstrated

- Programming model and runtime environment

Cloud Aggregation Gateways

Value-Adding (CAE platform) Services

In-Cloud Hosting Environment

Cloud Federation Management Service

CAE: key concepts

VPNaaS

In-Cloud Virtual Private Network





- Service Deployment Optimization module

- Internal Cloud Operation Optimization module

- VM Placement

- Data Management

- Inter-Cloud Security Model

2.2.5 Novelty of the solution with OPTIMIS

- A major contribution to the future Internet in terms of service development,

management and interoperability in an environment of converged IT, telecom and

service provider.

- Deep technological methodological advances in software/service engineering. New

software technologies and best practice for improving end to end service delivery,

capability and predictability.

- Methods, tools and approaches specifically supporting the development, deployment

and evolution of Services.

- Service Oriented Architecture (SOA) approach to providing services using clouddelivery model.

- Overall improvement in service life cycle responsiveness and risk management within

cloud environment. A more competitive environment including a deeper involvement

of the actors of the value chain with innovative service offerings on scalable

infrastructure.

- Lowered barriers for service providers, in particular SMEs, to leverage and participate

in cloud services through standardized service delivery framework.

- A strengthened industry in Europe for software, software services and Web services,

offering more reliable and affordable end to end services, enabled by flexible and

resilient platforms for software/service runtime management.





3 Time table

OPTIMIS project duration is 36 months. The following picture depicts the main interactions among the Use Cases and the rest of technical developments in the

project. Use Cases deliverables and timing of the rest of activities in which we expect new partner organization to be involved are describer on Section 4.

Use Cases have already started in M7 (December 2010)





4 Work Package Descriptions

The OPTIMIS project has already determined the WPs in which new partner organizations are

expected to contribute. They are the following:

WP 1.1 Requirements Elicitation: The aim of this WP is to clearly define therequirements of identified stakeholders (end-user, provider) in order to build a system

corresponding to their requirements/capabilities, including the support of trust,

economic effective and ecological efficient management of the full life cycle of

services.

WP6.3 Cloud Bursting: Its objective is to demonstrate the use of the OPTIMIS toolkit in

a real case scenario of hybrid-cloud. Atos Origin, as infrastructure provider, offers to its

customers the possibility to host their applications in its internal cloud environment,

by means of OPTIMIS we want to demonstrate how those applications will be derived

to a third party in peak demand situations.

WP6.4: Cloud Brokerage: The inability to perform cloud brokerage and federation

involving the use of multiple cloud providers is a major hurdle in the use of cloud

services by enterprises. Three different scenario of cloud based brokerage with varying

orchestration complexity will be considered in this workpackage. Each showcase the

ability of enterprise to orchestrate an internal workflow through the use of a

federation of cloud services of the use cloud based services through a brokerage-based

cloud provider.

WP 7.3 Exploitation: The objective of WP7.3 is to build a sound strategy for OPTIMIS

result exploitation. The work of WP7.3 starts with the in-depth exploitation context

analysis focusing on target market identification and competition. The work continues

with the exploitable result identification, which forms based for the detailed

exploitation strategy analysis (e.g. product and distribution strategy, economic analysis

etc.) The final exploitation strategies will be presented in the individual (and in the

case necessary) joint exploitation plans.

The complete work package descriptions are provided hereby:

4.1 Work package description–

WP1.1 Requirements Elicitation

Work package

description

WP1.1 Start date or starting

event:

M1

Work package title Requirements Elicitation

Activity type RTD

Participant number 1 2 3 4 5 6 7

Participant short

name

ATOS UMU 451G USTUTT

-HLRS

ICCS/N

TUA

BSC SAP





Person-months per

participant

Participant number 8 9 10 11 12 13

Participant short

name

SCAI ULEEDS LUH FLEX BT CITY

Person-months per

participant

Objectives

- Analysis of goals and requirements of the OPTIMIS system based on the end-user and

provider requirements, scenarios, and case studies;

- Definition of product quality model with relevant metrics to measure product internal

quality;

- Derivation of verification and validation test cases from identified requirements andscenarios

Description of work

Leader: UMU, Contributors: ALL

Task 1.1.1: Requirement Analysis

This task aims to clearly define the requirements of identified stakeholders (user, system) in

order to build a system corresponding to their requirements/capabilities, including the support

of economic effective and ecological efficient management of the full life cycle of services.

The objectives of the user and the cloud provider (from the system’s perspective) will beestablished as well as how the success of these objectives is measured. This will lead to the

identification of the major factors for the service architecture components. As a result, the

following models will be produced:

- User’s model for translating the user’s requirements into actual demand for resources,

considering the list of providers as well as resources status information;

- System’s model for identifying available resources (computational, storage, network, service)

that can be accessed. This will emphasize on the operations supported by cloud platforms,

including data management, message queues and other middleware.

From a methodological point of view, the requirement analysis task will use the goal-oriented

Knowledge Acquisition in automated specification (KAOS) methodology. The structure of the

System Requirements Specification Document will be adapted from existing standards such as

the Recommended Practice for Software Requirements Specifications IEEE.830.

Therefore this approach will combine (1) requirements gathering through case studies,

working closely with project partners, especially SAP, BT (2) and CITY requirements gathering

through interviews and questionnaires, and (3) requirements specification, i.e. creation of a

System Requirements Specification Document.

The global methodology followed to create this requirement document will involve the

following steps:

Identify user requirements: this involves identifying OPTIMIS potential end users and

examining how they could benefit from the project outcomes within cloud platforms.A questionnaire will be elaborated in order to facilitate the collection of end user





needs and requirements, emphasising on services, trust, and risk.

Build a rich set of scenarios (internal and external clouds) and to provide a precise

description of the expected functionalities of the system and its requirements,

emphasizing on multi-optimization that considers risk, trust, energy consumption, and

costs;

Build a goal-oriented requirements model of the high-level objectives by using KAOSgoal oriented methodology

Deriving the requirements document from the model.

The resulting System Requirements Specification Document will contain an analysis of

identified goals using the KAOS methodology and a presentation of fine grained user/system

requirements that will be derived from goals, analysed, and clearly identified in order to

facilitate implementation and testing phases.

Leader: ATOS, Contributors: BSC, SAP, FLEX, BT, CITY

Task 1.1.2: Case study analysis and specification

In cloud environments services define the business and technical framework that allows for

registration, discovery, invocation, delivery, usage and accounting of resources owned,

provided and managed by various organisations. The resources are made available through

well-defined service interfaces (e.g. in the form of Web services).

For each stage of a service delivery life-cycle in OPTIMIS (construction, deployment,

monitoring), the following issues for optimization need addressing:

1. Registration: description of what/how end-users and providers need to express in

terms of capability requirements at registration time;

2. Discovery: description of how the discovery process and protocols are altered when

optimization constraints are expressed by the end-user searching for the best services,as well as how they are delivered by the service configuration manager;

3. Invocation: description of the ways of classifying variations in trust, cost, energy

consumption, and risk to connect end-users to services;

4. Delivery: how can trust, risk, cost and energy consumption constraints be effectively

monitored and controlled during ongoing service delivery? Hence a description of the

protocols required from the end-user and provider perspectives in order to respond to

detection of services that do not comply with the usage agreements and optimization

constraints. Also a description of the strategies and options that are available for end-

users and providers;

5. Usage: how to ensure compliance of the resource usage of a service on shared

infrastructures (e.g. in terms of licenses)?6. Accounting: how can the requirements of an end-user be monitored and accounted?

For cases where the provider cannot or does not deliver with the expected level of

QoS, how can this be systematically resolved?

The aim of this task is hence to explore these questions in a comprehensive case study, such

that the requirements for addressing them can be used to evaluate the service construction,

deployment, and monitoring.

Leader: ULEEDS, Contributors: UMU, ATOS

Task 1.1.3: Product Quality Model

The main objective of this task is to select within the ISO/IEC9126 quality model the most

appropriate internal quality characteristics in order to produce an adequate quality model for





OPTIMIS outcomes. Other metrics coming from the state of the art will be used to complete

the set of metrics proposed by the standard. This task will also consist in identifying

appropriate measurement tools that will be used during the project to measure the software

product. The Product Quality Model will describe the selected quality model, its quality

characteristic, and their metrics. It will also explain the measurement process that will be

implemented during the project to measure and analyse selected quality characteristics.

Leader: ULEEDS, Contributors: UMU, ATOS

Task 1.1.4: Verification and Validation Cases

Definition of verification and validation cases for the quality and correctness evaluation

according to IEEE/ANSI standards. The verification stage checks whether the requirements are

correctly formulated. Additionally, verification checks whether the product was constructed in

accordance with these correctly formulated requirements. The validation stage refers to the

"test phase" of the lifecycle which assures that the end product (e.g., system, application, etc.)

meets stated specifications.

At the end of activities 2-4 it will be necessary to show that the software developed fulfils the

project achievements and conforms to the specifications of each activity.

Leader: ULEEDS, Contributors: UMU, BSC

Task 1.1.5 Risk Assessment Framework

The risk assessment framework will focus on the creation of a risk inventory for OPTIMIS and

enables: 1) the assessment of risk for service deployment, and 2) the providers to identify

infrastructure bottlenecks and mitigate risk to prevent SLA violation. This will include risk

identification, assessment, treatment, and monitoring for systematic risk, uncertainty or non-systematic risk, as well as probabilistic risk. It will:

- Be populated with assets (namely services), scenarios, and impact. Asset

characteristics relating to service provision will be decomposed into areas of interest

and those areas will be described in terms of indicators in order to be able to

understand the weaknesses of the asset and its impact on the risk profile of the entire

cloud platform. Potential risk events will be assessed in terms of these. Incidents are

composed of vulnerabilities, threats and adaptive capacity. Their impact is defined

using a degraded performance, loss of data, increase in cost/energy consumption,

security breach etc. These will be evaluated according to the indicators selected to

describe assets. Single cloud, multi-cloud and cloud federation scenarios for

deployment will be considered.

- Provide risk assessment mechanisms for systematic risk and uncertainty or non-

systematic risk. This requires to identify risk categories for different scenarios and to

work out the data needed for each category;

- Provide risk management mechanisms to define a response/mitigation strategy for the

identified risk. Typical strategies include retention, avoidance, reduction and transfer;

- Be responsible for Static/dynamic data provision for risk assessment and management.





Deliverables

Milestone 1: Initialized

D1.1.1.1 Requirements Analysis (M4)

Milestone 2: Established

D1.1.2.1 Verification and Validation Cases ( M5)

Milestone3: Refined

D1.1.1.2 Requirements Analysis ( M16)


Milestone 4: Matured

D1.1.1.3 Requirements Analysis (M28)


4.2 Work package description – WP6.3 Cloud Bursting

Work package

number

6.3 Start date or starting

event:

M7 (December 2010)

Work package title Cloud Bursting

Activity type RTD

Participant number 1 11

Participant short

name

ATOS FLEX

Person-months per

participant

Objectives

- Ensure the selection of provider based on cost, trust and energy efficiency.

- To combine the results produced in other WP to compose a reliable and secure Cloud

provider environment.

- Provide a mechanism to support the execution of licensed software.

- To avoid the vendor lock-in thought the inter-operability between providers

Description of work

The work package is based on a use case scenario where a company owning their own Cloud

infrastructure “private Cloud” and willing to, during required periods and a given set of

circumstances, use resources from an external Cloud provider. This use case plan will show

how an organization has the ability to scale out their infrastructures and rent the resources to

a third-party provider. The renting of the resources provides elasticity to infrastructure and

allows the organization to confront dynamically the fluctuations on demand.





FlexiScale can be presented to an internal organization as an external provider which can be

utilized as a metered service. The combination of utility style on a public cloud gives end users

scalability options while on a pay-as-you-go self-service platform.

Leader:FLEX; Contributors: ATOS

Task 6.3.1 A use case requirements and functional description.

This task will analyse the main requirements needed to build the scenario described in the use

case. This initial study allows contributors to describe the functional behaviour of the use case,

focused on ensuring the interoperability between the internal and external cloud and metering

the benefits of renting the extra resources externally.

Leader:ATOS; Contributors: FLEX,

Task 6.3.2 Define prototype architecture according with OPTIMIS model.

This task aims to design the prototype architecture according to the objectives of the use case.

This design will combine the perspective produces in other OPTIMIS WPs.

Leader:FLEX; Contributors: ATOS,

Task 6.3.3 Prototype implementation enabling interoperability between providers

In this task, an implementation of an application that dynamically scales out over external

resources, a SLA negotiation is used to ensure the correct terms of this renting, according with

the particular needs of the application and the final functionality of the service.

Leader:ATOS; Contributors: FLEX

Task 6.3.4 Prototypes testing to evaluate the interaction and the encapsulated cloud service.

Finally, in this task the use case have to guarantee the selection of provider based on costs,

trust and energy efficiency and ensure the interoperability between two service providers

(internal, external) to provide enough capacity to solve the cloud service needs

Deliverables (brief description) and month of delivery


D6.3.1 Use case requirements and functional description. (M12)

D6.3.2 Prototype architecture according with OPTIMIS model. (M12)

Milestone 3: Refined

D6.3.3 Prototype implementation enabling interoperability between providers. (M24)

Milestone 5: Finalised

D6.3.4 Prototypes testing to evaluate the encapsulated cloud service. (M34)





4.3 Work package description – WP6.4: Cloud Brokerage

Work package

number

6.4 Start date or starting

event:

M7 (December 2010)

Work package title Cloud Brokerage

Activity type RTD

Participant number 11 12 9 13

Participant short

name

FLEX BT ULEEDS CITY

Person-months per

participant

Objectives

- To investigate and develop requirements in order to enable brokerage based cloud

federation.

- To showcase the feasibility of providing brokerage, federation-based ecosystem for

cloud services.

- To validate and utilise work done in other work packages in the area of cloud security,

policy enforcement, service deployment optimisation, service management etc.

Description of work

Leader: BT

The inability to perform cloud brokerage and federation involving the use of multiple cloudproviders is a major hurdle in the use of cloud services by enterprises. Work package 6.4 will

focus on a case study for implementing the infrastructure and framework needed to power

such a service. Such an effort will showcase the maturity of the cloud delivery model to handle

complicated business processes involving multiple parties. .The different scenario setups that

make up the use case, in order of their orchestration complexity, are as follows:

Enterprise use of multiple cloud providers: in this scenario, an enterprise organisation makes

use of services provided by various cloud providers to fulfil an internal process.

Cloud provider to broker multiple providers to provide a SLA-based tiered pricing model: in

this, an enterprise approaches a cloud broker with a given set of functional and SLA-based

requirements and the cloud broker then picks up the best match in terms of the functions as

well as variables like pricing, SLA parameters and other non-functional requirements likecompliance and certification capabilities.

Cloud aggregation ecosystem (CAE): this scenario offers the potential to treat both IT and

business functions as a series of interconnected cloud services. CAE offers a means to architect

a Service Oriented Infrastructure (SOI) on the cloud that is built on the fusion of: (a)

Composition of loosely coupled services based on an evolution of Service Oriented

Architecture (SOA) principles applied to services that reside on cloud platforms (b) Distributed

management of ICT resources applied on federations of cloud platforms (c) network resource

management based on a federated Operational Support System (OSS) architecture built on top

of an in-cloud Network as a Service (NaaS) offering.

The baseline for the WP is individual cloud infrastructures that have been developed and

implemented by various cloud providers. In addition there have been efforts by Eucalyptus EEto provide hybrid cloud and cloudbursting support but these do not cover the scenarios





mentioned above.

T 6.4.1: Architectural requirements analysis

Leader: BT; Contributors: FLEX,, CITY

This task will analyse the architectural requirements needed to realise the scenarios described

in this use case, with specific emphasis on security, identity and access management, SLAbased service optimisation and policy enforcement.

T 6.4.2: IdAM capability implementation


This task will implement the identity federation and access management capability across

multiple cloud based service providers taking into account the various functional requirements

identified in T 6.4.1

T 6.4.3: SLA based cloud brokerage implementation


This task will implement the SLA driven cloud brokerage mechanism that not only considers

the brokerage-biased second scenario but also feeds into the collaboration-biased service

composition and lifecycle management.T 6.4.4: Comprehensive architecture implementation

Leader: BT; Contributors: FLEX, CITY

This task will combine all the work performed in the earlier tasks to implement a

comprehensive architecture capable of powering the cloud aggregation scenario explained

earlier.


Milestone 2:Established

D 6.4.1 An architectural design for a brokerage-based collaboration oriented multiple cloud

provider usage scenarios(M12)

Milestone 3:Refined

D6.4.2 Prototype implementations of a system showcasing federated identity management

across multiple cloud services / service providers and another performing SLA-driven cloud

brokerage ecosystem. (M24)Milestone 5: Finalised

D6.4.3 Prototype implementation of a comprehensive brokerage based cloud ecosystem that

enables the composition of loosely coupled services based on an evolution of Service Oriented

Architecture. (M34)





4.4 Work package description – WP 7.3 Exploitation

Work package

number

WP7.3 Start date or starting

event:

M4 (September 2010)

Work package title Exploitation

Activity type RTD

Participant number 1 3 7 8 11 12

Participant short

name

ATOS 451G SAP SCAI FLEX BT

Person-months per

participant

Objectives

- To analyse the exploitation context in terms of potential target markets, competition,

and competitive solutions

- To identify the exploitable results from the business point of view

- To analyse the relevant exploitation strategy elements for OPTIMIS and position the

results in the market context. This analysis form base for the exploitation plans

- To develop exploitation plans

- To study IPR issues

Description of work

Task 7.3.1 Exploitation context and strategy

Leader: SAP; Contributors: ATOS, 451G, SCAI, FLEX, BT,

This task builds an in-depth understanding of the OPTIMIS market and exploitation context,

and it aims at providing a sound base for the further exploitation actions. This task can be

divided into main activities:

a) Exploitation context analysis will be carried out in order to find out what is the actual

market situation. The potential target market (or target users) and the early adopters

will be identified and analysed. Also the competitive situation and the main market

player and their solutions will be studied.

This task is closely related to WP7.1, and it receives important input especially fromTasks 7.1.1 and 7.1.2.

b) Exploitation strategy is based on the exploitation context analysis, and it first clearly

identifies the exploitable project results. It takes steps further by providing detailed

analysis of different strategy elements (e.g. product and distribution strategy, price

and cost estimations etc.) relevant for OPTIMIS result exploitation. The specificity level

of this analysis depends strongly on the nature of the exploitable results (e.g Toolkit

vs.individual components or set of components, open source vs commercial

software).Also SWOT analysis, competitive positioning and UPS will be defined.





Task 7.3.2 Exploitation plans

Leader: SAP; Contributors: ATOS, 451G, SCAI, FLEX, BT,

This task consists of exploitation plans of the project partners. These exploitation plans clarifies

both research oriented and commercial exploitation activities, and includes realistic

expectations regard to revenue generation possibilities. The Exploitation plans will cover twomodalities depending on the partners’ final exploitation intentions:

1) Individual Exploitation Plans: Each partner is in charge of its exploitation plan, and it

refers the each partner exploits the results.

2) Joint Exploitation Plans: Depending on the project results and partners’ exploitation

intentions also joint exploitation is possible. In this case the partners will provide a

shared exploitation plan which clarifies how they together will exploit the results.

Exploitation plans will be elaborated in three iterations (preliminary, intermediate, and final

versions).


The Exploitation Plans deliverable is a live document that has 4 versions.


D7.3.1.1 Preliminary Exploitation Plans (M6)

This deliverable includes product description, market context analysis and a first version of

exploitation plans.

Milestone 3: Refined

D7.3.1.2 Intermediate Exploitation Plans (M12).

This deliverable includes a preliminary exploitation strategy and a refined version of

exploitation plans.

D7.3.1.3 Intermediate Exploitation Plans (M24)

This deliverable includes an updated version of product description, market context analysis,

exploitation strategy and exploitation plans.

Milestone 4: Matured

D7.3.1.4 Final Exploitation Plans (M32).

This deliverable describes the final joint and individual exploitation plans of the OPTIMISpartners, and includes a matured version of product description, market context analysis and

exploitation strategy.





Annex A. License conditions.This is a public deliverable that is provided to the community under the license Attribution-NoDerivs 2.5 defined by creative

commons http://www.creativecommons.org

This license allows you to

to copy, distribute, display, and perform the work

to make commercial use of the work

Under the following conditions:

Attribution. You must attribute the work by indicating that this work originated from the IST-

OPTIMIS project and has been partially funded by the European Commission under contract

number IST - 257115

No Derivative Works. You may not alter, transform, or build upon this work without explicit

permission of the consortium

For any reuse or distribution, you must make clear to others the license terms of this work.

Any of these conditions can be waived if you get permission from the copyright holder.

This is a human-readable summary of the Legal Code below:

License

THE WORK (AS DEFINED BELOW) IS PROVIDED UNDER THE TERMS OF THIS CREATIVE COMMONS PUBLIC LICENSE ("CCPL" OR

"LICENSE"). THE WORK IS PROTECTED BY COPYRIGHT AND/OR OTHER APPLICABLE LAW. ANY USE OF THE WORK OTHER THAN AS

AUTHORIZED UNDER THIS LICENSE OR COPYRIGHT LAW IS PROHIBITED. BY EXERCISING ANY RIGHTS TO THE WORK PROVIDED

HERE, YOU ACCEPT AND AGREE TO BE BOUND BY THE TERMS OF THIS LICENSE. THE LICENSOR GRANTS YOU THE RIGHTS

CONTAINED HERE IN CONSIDERATION OF YOUR ACCEPTANCE OF SUCH TERMS AND CONDITIONS.

1. Definitions

"Collective Work" means a work, such as a periodical issue, anthology or encyclopedia, in which the Work in its entirety in

unmodified form, along with a number of other contributions, constituting separate and independent works in themselves, are

assembled into a collective whole. A work that constitutes a Collective Work will not be considered a Derivative Work (as defined

below) for the purposes of this License.

"Derivative Work" means a work based upon the Work or upon the Work and other pre-existing works, such as a translation,

musical arrangement, dramatization, fictionalization, motion picture version, sound recording, art reproduction, abridgment,

condensation, or any other form in which the Work may be recast, transformed, or adapted, except that a work that constitutes a

Collective Work will not be considered a Derivative Work for the purpose of this License. For the avoidance of doubt, where the

Work is a musical composition or sound recording, the synchronization of the Work in timed-relation with a moving image

("synching") will be considered a Derivative Work for the purpose of this License.

"Licensor" means all partners of the OPTIMIS consortium that have participated in the production of this text

"Original Author" means the individual or entity who created the Work.

"Work" means the copyrightable work of authorship offered under the terms of this License.

"You" means an individual or entity exercising rights under this License who has not previously violated the terms of this License

with respect to the Work, or who has received express permission from the Licensor to exercise rights under this License despite a

previous violation.

2. Fair Use Rights. Nothing in this license is intended to reduce, limit, or restrict any rights arising from fair use, first sale or otherlimitations on the exclusive rights of the copyright owner under copyright law or other applicable laws.

3. License Grant. Subject to the terms and conditions of this License, Licensor hereby grants You a worldwide, royalty-free, non-

exclusive, perpetual (for the duration of the applicable copyright) license to exercise the rights in the Work as stated below:

to reproduce the Work, to incorporate the Work into one or more Collective Works, and to reproduce the Work as incorporated in

the Collective Works;

to distribute copies or phonorecords of, display publicly, perform publicly, and perform publicly by means of a digital audio

transmission the Work including as incorporated in Collective Works.

For the avoidance of doubt, where the work is a musical composition:

Performance Royalties Under Blanket Licenses. Licensor waives the exclusive right to collect, whether individually or via a

performance rights society (e.g. ASCAP, BMI, SESAC), royalties for the public performance or public digital performance (e.g.

webcast) of the Work.

Mechanical Rights and Statutory Royalties. Licensor waives the exclusive right to collect, whether individually or via a music rights

society or designated agent (e.g. Harry Fox Agency), royalties for any phonorecord You create from the Work ("cover version") and

http://www.creativecommons.org/







distribute, subject to the compulsory license created by 17 USC Section 115 of the US Copyright Act (or the equivalent in other

jurisdictions).

Webcasting Rights and Statutory Royalties. For the avoidance of doubt, where the Work is a sound recording, Licensor waives the

exclusive right to collect, whether individually or via a performance-rights society (e.g. SoundExchange), royalties for the public

digital performance (e.g. webcast) of the Work, subject to the compulsory license created by 17 USC Section 114 of the US

Copyright Act (or the equivalent in other jurisdictions).

The above rights may be exercised in all media and formats whether now known or hereafter devised. The above rights includethe right to make such modifications as are technically necessary to exercise the rights in other media and formats, but otherwise

you have no r ights to make Derivative Works. All rights not expressly granted by Licensor are hereby reserved.

4. Restrictions. The license granted in Section 3 above is expressly made subject to and limited by the following restrictions:

You may distribute, publicly display, publicly perform, or publicly digitally perform the Work only under the terms of this License,

and You must include a copy of, or the Uniform Resource Identifier for, this License with every copy or phonorecord of the Work

You distribute, publicly display, publicly perform, or publicly digitally perform. You may not offer or impose any terms on the Work

that alter or restrict the terms of this License or the recipients' exercise of the rights granted hereunder. You may not sublicense

the Work. You must keep intact all notices that refer to this License and to the disclaimer of warranties. You may not distribute,

publicly display, publicly perform, or publicly digitally perform the Work with any technological measures that control access or

use of the Work in a manner inconsistent with the terms of this License Agreement. The above applies to the Work as

incorporated in a Collective Work, but this does not require the Collective Work apart from the Work itself to be made subject to

the terms of this License. If You create a Collective Work, upon notice from any Licensor You must, to the extent practicable,

remove from the Collective Work any credit as required by clause 4(b), as requested.

If you distribute, publicly display, publicly perform, or publicly digitally perform the Work or Collective Works, You must keep

intact all copyright notices for the Work and provide, reasonable to the medium or means You are utilizing: (i) the name of the

Original Author (or pseudonym, if applicable) if supplied, and/or (ii) if the Original Author and/or Licensor designate another party

or parties (e.g. a sponsor institute, publishing entity, journal) for attribution in Licensor's copyright notice, terms of service or by

other reasonable means, the name of such party or parties; the title of the Work if supplied; and to the extent reasonably

practicable, the Uniform Resource Identifier, if any, that Licensor specifies to be associated with the Work, unless such URI does

not refer to the copyright notice or licensing information for the Work. Such credit may be implemented in any reasonable

manner; provided, however, that in the case of a Collective Work, at a minimum such credit will appear where any other

comparable authorship credit appears and in a manner at least as prominent as such other comparable authorship credit.

5. Representations, Warranties and Disclaimer. UNLESS OTHERWISE MUTUALLY AGREED TO BY THE PARTIES IN WRITING,

LICENSOR OFFERS THE WORK AS-IS AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND CONCERNING THE

MATERIALS, EXPRESS, IMPLIED, STATUTORY OR OTHERWISE, INCLUDING, WITHOUT LIMITATION, WARRANTIES OF TITLE,

MERCHANTIBILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT, OR THE ABSENCE OF LATENT OR OTHER DEFECTS,

ACCURACY, OR THE PRESENCE OF ABSENCE OF ERRORS, WHETHER OR NOT DISCOVERABLE. SOME JURISDICTIONS DO NOT ALLOW

THE EXCLUSION OF IMPLIED WARRANTIES, SO SUCH EXCLUSION MAY NOT APPLY TO YOU.

6. Limitation on Liability. EXCEPT TO THE EXTENT REQUIRED BY APPLICABLE LAW, IN NO EVENT WILL LICENSOR BE LIABLE TO YOU

ON ANY LEGAL THEORY FOR ANY SPECIAL, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES ARISING OUT OF

THIS LICENSE OR THE USE OF THE WORK, EVEN IF LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

7. Termination

This License and the rights granted hereunder will terminate automatically upon any breach by You of the terms of this License.

Individuals or entities who have received Collective Works from You under this License, however, will not have their licenses

terminated provided such individuals or entities remain in full compliance with those licenses. Sections 1, 2, 5, 6, 7, and 8 will

survive any termination of this License.

Subject to the above terms and conditions, the license granted here is perpetual (for the duration of the applicable copyright in

the Work). Notwithstanding the above, Licensor reserves the right to release the Work under different license terms or to stop

distributing the Work at any time; provided, however that any such election will not serve to withdraw this License (or any other

license that has been, or is required to be, granted under the terms of this License), and this License will continue in full force and

effect unless terminated as stated above.

8. Miscellaneous

Each time You distribute or publicly digitally perform the Work, the Licensor offers to the recipient a license to the Work on the

same terms and conditions as the license granted to You under this License.

If any provision of this License is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of

the remainder of the terms of this License, and without further action by the parties to this agreement, such provision shall be

reformed to the minimum extent necessary to make such provision valid and enforceable.

No term or provision of this License shall be deemed waived and no breach consented to unless such waiver or consent shall be in

writing and signed by the party to be charged with such waiver or consent.

This License constitutes the entire agreement between the parties with respect to the Work licensed here. There are no

understandings, agreements or representations with respect to the Work not specified here. Licensor shall not be bound by any

additional provisions that may appear in any communication from You. This License may not be modified without the mutual

written agreement of the Licensor and You.

Documents

OPTIMIS Open Call Information Package