SZTAKI Cloud akadémiai vonatkozásaKecskeméti Gábor

MTA-SZTAKIPárhuzamos és Elosztott rendszerek

kutatólaboratórium

Számítási felhő technológiák fejlődése

Enterprise level virtualization

Component based computing

x86 virtualization

1970 1980 1990 2000

Serviceorientedcomputing

2010

Para virtualization

HardwareSupport

Web

IaaS

SaaS

PaaS

VPS, VSH

Legend: PaaS – Platform as a Service, SaaS – Software as a Service, VPS – Virtual private server,VSH - Virtual server hosting, IaaS – Infrastructure as a Service

Brief history of Academic Clouds• Xen, Xenoserver platform: 2001-2003• In Vigo Project – till 2005• RTEFactory (2003) -> Virtual Workspace (2005)

Service -> Nimbus (2008)• OpenNebula, Eucalyptus 2008-• OpenStack 2010-• Apache Tashi 2009-• Clever 2010-

Eucalyptus overview

• Eucalyptus is an open source software mimicking AWS– How VM instances are managed– How to provide virtual network (like elastic IP)– How to provide data storage (like S3)– A very brief description, but we can get something

• Use the same user interface AWS provided (EC2, S3, mainly)– Boto library can be used, too

Keke Chen

Eucalpytus

Keke Chen

CLC: cloud controller Walrus: storage controller similar to S3CC: cluster controller NC: node controller

Nimbus Overview• Goal: open source, extensible, IaaS implementation and tools

– Specifically targeting scientific community– A platform for experimentation with features for scientific needs– Set up private clouds (privacy, expense considerations)

• Tools – IaaS layer (Workspace Service)– Orchestration layer (Context Broker, gateway)

• http://workspace.globus.org/

10/20/08 The Nimbus Toolkit: http//workspace.globus.org Kate Keahey (keahey@mcs.anl.gov)

The Workspace Service

10/20/08 The Nimbus Toolkit: http//workspace.globus.org

Poolnode

Trusted Computing Base (TCB)

Poolnode

Poolnode

Poolnode

Poolnode

Poolnode

Poolnode

Poolnode

Poolnode

Poolnode

Poolnode

Poolnode

The workspace service publishesinformation on each workspace

as standard WSRF ResourceProperties.

Users can query thoseproperties to find out

information about theirworkspace (e.g. what IP

the workspace was bound to)

Users can interact directly with their

workspaces the same way the would with a

physical machine.

VWSService

Kate Keahey (keahey@mcs.anl.gov)

OpenNebula

OpenStack

Apache Tashi

CLoud-Enabled Virtual EnviRonment (CLEVER)• CLEVER components:

– Host Manager – manages virtual environments– Cluster Manager – intermediary between the clients and the

host managers• CLEVER communication:

– Distributed database – for the state of the middleware– XMPP Communication System – for the interaction between

middleware compinents• Federation awareness:

– A CLEVER Cluster Manager of an administrative domain is able to control one or more Host Managers belonging other administrative domains.

RepositoryRepository

VAVAVAVAVAVA

RepositoryRepository

VAVAVAVAVAVA

RepositoryRepository

VAVAVAVA

Virtual Appliance

Virtual Appliance

ServiceServiceLibs

+OS

Support

Environment

Infrastructure as a Service CloudInfrastructure as a Service Cloud

HostHostVMM

HostHostVMM

HostHostVMM

HostHostVMM

HostHostVMM

HostHostVMM

HostHostVMM

HostHostVMM

HostHostVMM

HostHostVMM

HostHostVMM

HostHostVMM

HostHostVMM

HostHostVMM

HostHostVMM

HostHostVMM

VAVA

VAVAVAVA

Delivery

HostHostVMM

VAVA

Hogyan használjuk a felhőt

VMVM

Virtual Appliance

Virtual Appliance

ServiceServiceLibs

+OS

Support

Environment

Előnyök• Könnyen elérhető személyre szabott gépek

– Kísérleti infrastruktúrák felállítása– Felhős felhasználás helyi ellenőrzése– A kutatók saját gépét nem terhelő személyre szabott virtuális

gépek automatizált virtuális gépek létrehozása• Mindig a kutatócsoport aktuális igényeihez igazodó

infrastruktúra– A felhő megoldások segítségével könnyen és tetszőleges

időre készíthetők virtuális erőforrások – pl. számítási clusterek

– A rendszer adminisztrációs feladatok többsége (pl tűzfal management) automatizáltak, szoftverből vezérelhetőek

Federated Cloud Management Federated Cloud Management (FCM)(FCM)• An autonomic resource management solution

• Provides an entry point to a cloud federation• Provides transparent service execution for users• Following challenges are considered:

– Varying load of user requests– Enabling virtualized management of applications– Establishing interoperability – Minimizing Cloud usage costs– Enhancing provider selection

• Layered architecture– Meta broker– Cloud brokers– Cloud providers

FCM Architecture: overviewFCM Architecture: overview

Cloud-Broker

Clouda

FCM Repository

Cloudb

• Top-level brokering• Autonomously

manage the interconnected cloud infrastructures

• Forms a federation with the help of CloudBrokers

Generic Meta-Broker Service

Cloud-Broker

1

FCM Architecture: overviewFCM Architecture: overview

Cloud-Broker

Clouda

FCM Repository

Cloudb

• Manages VA Manages VA distribution among distribution among the various cloud the various cloud infrastructuresinfrastructures

• Automated Automated federation wide federation wide repository content repository content managementmanagement

• Offers current VA Offers current VA availability and availability and estimates its estimates its future deploymentfuture deployment

Generic Meta-Broker Service

Cloud-Broker

2

FCM Architecture: overviewFCM Architecture: overview

Cloud-Broker

Clouda

FCM Repository

Cloudb

• Interacts with a Interacts with a single IaaS single IaaS systemsystem

• Manages Manages resources and resources and service callsservice calls

Generic Meta-Broker Service

Cloud-Broker

3 3

Köszönöm a figyelmet

További információ:https://www.lpds.sztaki.hu/CloudResearch