Download presentation
Presentation is loading. Please wait.
Published byKelsey Hughston Modified over 10 years ago
1
SZTAKI Cloud akadémiai vonatkozása Kecskeméti Gábor MTA-SZTAKI Párhuzamos és Elosztott rendszerek kutatólaboratórium
2
Számítási felhő technológiák fejlődése Enterprise level virtualization Component based computing x86 virtualization 197019801990 2000 Service oriented computing 2010 Para virtualization Hardware Support 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
3
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-
4
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
5
Eucalpytus Keke Chen CLC: cloud controller Walrus: storage controller similar to S3 CC: cluster controllerNC: node controller
6
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)
7
The Workspace Service 10/20/08 The Nimbus Toolkit: http//workspace.globus.org Pool node Trusted Computing Base (TCB) Pool node Pool node Pool node Pool node Pool node Pool node Pool node Pool node Pool node Pool node Pool node The workspace service publishes information on each workspace as standard WSRF Resource Properties. Users can query those properties to find out information about their workspace (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. VWS Service Kate Keahey (keahey@mcs.anl.gov)
8
OpenNebula
9
OpenStack
10
Apache Tashi
11
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.
12
Repository VA Repository VA Repository VA Virtual Appliance Service Libs + OS Support Environment Infrastructure as a Service Cloud Host VMM Host VMM Host VMM Host VMM Host VMM Host VMM Host VMM Host VMM Host VMM Host VMM Host VMM Host VMM Host VMM Host VMM Host VMM Host VMM VA Delivery Host VMM VA Instantiation Hogyan használjuk a felhőt VM Virtual Appliance Service Libs + OS Support Environment
13
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
14
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
15
FCM Architecture: overview Cloud-Broker Cloud a FCM Repository Cloud b Top-level brokering Autonomously manage the interconnected cloud infrastructures Forms a federation with the help of CloudBrokers Generic Meta-Broker Service Cloud-Broker 1
16
FCM Architecture: overview Cloud-Broker Cloud a FCM Repository Cloud b Manages VA distribution among the various cloud infrastructures Manages VA distribution among the various cloud infrastructures Automated federation wide repository content management Automated federation wide repository content management Offers current VA availability and estimates its future deployment Offers current VA availability and estimates its future deployment Generic Meta-Broker Service Cloud-Broker 2
17
FCM Architecture: overview Cloud-Broker Cloud a FCM Repository Cloud b Interacts with a single IaaS system Interacts with a single IaaS system Manages resources and service calls Manages resources and service calls Generic Meta-Broker Service Cloud-Broker 33
18
Köszönöm a figyelmet További információ: https://www.lpds.sztaki.hu/CloudResearch
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.