180 likes | 277 Views
SZTAKI Cloud akadémiai vonatkozása. Kecskeméti Gábor MTA-SZTAKI Párhuzamos és Elosztott rendszerek kutatólaboratórium. Számítási felhő technológiák fejlődése. Para virtualization. x86 virtualization. Hardware Support. PaaS. Web. Service oriented computing. Component
E N D
SZTAKI Cloud akadémiai vonatkozása KecskemétiGábor MTA-SZTAKI PárhuzamosésElosztottrendszerekkutatólaboratórium
Számításifelhőtechnológiákfejlődése Para virtualization x86 virtualization Hardware Support PaaS Web Service oriented computing Component based computing SaaS VPS, VSH Enterprise level virtualization IaaS 2000 2010 1970 1980 1990 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,Xenoserverplatform: 2001-2003 • InVigoProject– till 2005 • RTEFactory(2003)->VirtualWorkspace(2005)Service->Nimbus(2008) • OpenNebula,Eucalyptus2008- • 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 CLC: cloud controller Walrus: storage controller similar to S3 CC: cluster controller NC: node controller Keke Chen
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/ Kate Keahey (keahey@mcs.anl.gov)
The Workspace Service The workspace service publishes information on each workspace as standard WSRF Resource Properties. Pool node Pool node Pool node VWS Service Pool node Pool node Pool node Users can query those properties to find out information about their workspace (e.g. what IP the workspace was bound to) Pool node Pool node Pool node Pool node Pool node Pool node Users can interact directly with their workspaces the same way the would with a physical machine. Trusted Computing Base (TCB) Kate Keahey (keahey@mcs.anl.gov)
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.
Repository Repository VA VA VA VA VA VA Hogyanhasználjuk a felhőt VA Repository VA Host VM Virtual Appliance Virtual Appliance VA Instantiation VA Libs+ OS Libs+ OS Support Support Host Host Host Host Host Host Host Host Host Host Host Host Host Host Host Host Service Service Delivery Infrastructure as a Service Cloud VA VMM VMM VMM VMM VMM VMM VMM VMM VMM VMM VMM VMM VMM VMM VMM VMM Environment Environment VMM VA
Előnyök • Könnyenelérhetőszemélyreszabottgépek • Kísérletiinfrastruktúrákfelállítása • Felhősfelhasználáshelyiellenőrzése • A kutatóksajátgépétnemterhelőszemélyreszabottvirtuálisgépekautomatizáltvirtuálisgépeklétrehozása • Mindig a kutatócsoportaktuálisigényeihezigazodóinfrastruktúra • A felhőmegoldásoksegítségévelkönnyenéstetszőlegesidőrekészíthetőkvirtuáliserőforrások – pl. számításiclusterek • A rendszeradminisztrációsfeladatoktöbbsége (pltűzfal management) automatizáltak, szoftverbőlvezérelhetőek
Federated Cloud Management (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: overview • Top-level brokering • Autonomously manage the interconnected cloud infrastructures • Forms a federation with the help of CloudBrokers 1 Generic Meta-Broker Service FCM Repository Cloud-Broker Cloud-Broker Clouda Cloudb
FCM Architecture: overview • Manages VA distribution among the various cloud infrastructures • Automated federation wide repository content management • Offers current VA availability and estimates its future deployment Generic Meta-Broker Service 2 FCM Repository Cloud-Broker Cloud-Broker Clouda Cloudb
FCM Architecture: overview • Interacts with a single IaaS system • Manages resources and service calls Generic Meta-Broker Service FCM Repository 3 3 Cloud-Broker Cloud-Broker Clouda Cloudb
Köszönöm a figyelmet Továbbiinformáció: https://www.lpds.sztaki.hu/CloudResearch