60% found this document useful (5 votes)
7K views38 pages

Roots of Cloud Computing

The document discusses the technological roots that contributed to the development of cloud computing, including hardware virtualization, distributed computing, internet technologies, and systems management. It traces the evolution from mainframes to modern cloud computing models, covering concepts like utility computing, grid computing, web services, and virtualization. The convergence of these fields allowed computing resources to be delivered over the internet on-demand at lower costs compared to in-house IT infrastructure.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
60% found this document useful (5 votes)
7K views38 pages

Roots of Cloud Computing

The document discusses the technological roots that contributed to the development of cloud computing, including hardware virtualization, distributed computing, internet technologies, and systems management. It traces the evolution from mainframes to modern cloud computing models, covering concepts like utility computing, grid computing, web services, and virtualization. The convergence of these fields allowed computing resources to be delivered over the internet on-demand at lower costs compared to in-house IT infrastructure.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 38

LECTURE: 2

ROOTS OF CLOUD COMPUTING


ROOTS OF CLOUD COMPUTING

• THE CONVERGENCE OF TECHNOLOGY FIELDS THAT SIGNIFICANTLY ADVANCED AND


CONTRIBUTED TO THE ADVENT OF CLOUD COMPUTING
• HARDWARE (VIRTUALIZATION, MULTI-CORE CHIPS)
• INTERNET TECHNOLOGIES (WEB SERVICES, SERVICE-ORIENTED ARCHITECTURES, WEB 2.0)
• DISTRIBUTED COMPUTING (CLUSTERS, GRIDS)
• SYSTEMS MANAGEMENT (AUTONOMIC COMPUTING, DATA CENTER AUTOMATION)
• A SPECIFICATION AND STANDARDIZATION PROCESS FOLLOWED
• LEADING TO MATURITY AND WIDE ADOPTION
ROOTS OF CLOUD COMPUTING

• FROM MAINFRAMES TO CLOUDS


• SOA, WEB SERVICES
• GRID COMPUTING
• UTILITY COMPUTING
• HARDWARE VIRTUALIZATION
• AUTONOMIC COMPUTING
ROOTS OF CLOUD COMPUTING (CONT.)

Hardware

Hardware Virtualization
Multi-core chips

Internet Technologies
Distributed Computing

SOA
Utility & Web 2.0
Cloud
Grid Web Services
Computing
Computing Mashups

Autonomic Computing
Data Center Automation

Systems Management
FROM MAINFRAMES TO CLOUDS

• IN PAST, COMPANIES OFFERED COMMON DATA PROCESSING TASKS


MAINFRAMES WERE USED TO SERVE DOZENS OF APPLICATIONS
• TODAY MAINFRAMES ARE REPLACED BY FAST AND INEXPENSIVE MICROPROCESSORS
• FAST FIBER-OPTICS NETWORKS HAVE HELPED SHARING OF COMPUTER POWER OVER GREAT DISTANCES
• FROM IN-HOUSE GENERATED COMPUTING POWER INTO UTILITY-SUPPLIED COMPUTING RESOURCES
DELIVERED OVER THE INTERNET AS WEB SERVICES
• ON DEMAND DELIVERY OF INFRASTRUCTURE, APPLICATIONS, AND BUSINESS PROCESSES IN A SECURITY-RICH, SHARED,
SCALABLE, AND BASED COMPUTER ENVIRONMENT OVER THE INTERNET FOR A FEE

• CONSUMERS CAN ATTAIN REDUCTION ON IT-RELATED COSTS


• CHOOSING TO OBTAIN CHEAPER SERVICES FROM EXTERNAL PROVIDERS VS. HEAVILY INVESTING ON IT INFRASTRUCTURE
AND PERSONNEL HIRING
FROM MAINFRAMES TO CLOUDS
(CONT.)

• THE “ON-DEMAND” COMPONENT OF THIS MODEL ALLOWS CONSUMERS TO ADAPT THEIR IT USAGE
TO RAPIDLY INCREASING OR UNPREDICTABLE COMPUTING NEEDS

• PROVIDERS OF IT SERVICES ACHIEVE BETTER OPERATIONAL COSTS


• HARDWARE AND SOFTWARE INFRASTRUCTURES ARE BUILT TO PROVIDE MULTIPLE SOLUTIONS AND
SERVE MANY USERS
• INCREASING EFFICIENCY AND ULTIMATELY LEADING TO FASTER RETURN ON INVESTMENT (ROI) AS
WELL AS LOWER TOTAL COST OF OWNERSHIP (TCO)
FROM MAINFRAMES TO CLOUDS
(CONT.)

• THE UNAVAILABILITY OF EFFICIENT COMPUTER NETWORKS CAUSED IT INFRASTRUCTURE


TO BE HOSTED IN PROXIMITY
• PREVENTING THE UTILITY COMPUTING REALITY OF TAKING PLACE ON MODERN COMPUTER SYSTEMS

• NEW TECHNOLOGIES FOR ENABLING SHARING OF COMPUTING POWER OVER GREAT


DISTANCES HAVE APPEARED
• THE POTENTIAL OF DELIVERING COMPUTING SERVICES WITH THE HIGH SPEED AND RELIABILITY TO
OFFER COMPUTING SERVICES WITH A FRACTION OF COSTS FOR A COMPANY TO GENERATE ITS
OWN COMPUTING POWER
SOA, WEB SERVICES, WEB 2.0, AND MASHUPS

• WEB SERVICES (WS) MAKE INFORMATION FROM ONE APPLICATION AVAILABLE TO OTHERS
• CREATION OF WS ON TOP OF COMMON TECHNOLOGIES LIKE HTTP MAKES THEM IDEAL
FOR IMPLEMENTING SERVICE-ORIENTED ARCHITECTURE (SOA)
• SOA ADDRESSES REQUIREMENTS OF STANDARD-BASED AND PROTOCOL-INDEPENDENT
DISTRIBUTED COMPUTING
• IN SOA, SOFTWARE RESOURCES ARE PACKAGED AS SERVICES WHICH ARE INDEPENDENT
FROM CONTEXT OF OTHER SERVICES
SOA, WEB SERVICES, WEB 2.0, AND
MASHUPS

• WEB SERVICES CAN GLUE TOGETHER APPLICATIONS RUNNING ON DIFFERENT MESSAGING


PRODUCT PLATFORMS
• ENABLING INFORMATION FROM ONE APPLICATION TO BE MADE AVAILABLE TO OTHERS
• ENABLING INTERNAL APPLICATIONS TO BE MADE AVAILABLE OVER THE INTERNET

• A RICH WS SOFTWARE STACK HAS BEEN SPECIFIED AND STANDARDIZED


• DESCRIBE, COMPOSE, AND ORCHESTRATE SERVICES
• PACKAGE AND TRANSPORT MESSAGES BETWEEN SERVICES
• PUBLISH AND DISCOVER SERVICES
• REPRESENT QUALITY OF SERVICE (QOS) PARAMETERS
• ENSURE SECURITY IN SERVICE ACCESS
SOA, WEB SERVICES, WEB 2.0, AND
MASHUPS (CONT.)

• WS STANDARDS HAVE BEEN CREATED ON TOP OF HTTP AND XML


• PROVIDING A COMMON MECHANISM FOR DELIVERING SERVICES
• MAKING THEM IDEAL FOR IMPLEMENTING A SERVICE-ORIENTED ARCHITECTURE (SOA)
• SOA ADDRESSES REQUIREMENTS OF LOOSELY COUPLED, STANDARDS-BASED, AND
PROTOCOL-INDEPENDENT DISTRIBUTED COMPUTING
• SOFTWARE RESOURCES ARE PACKAGED AS “SERVICES”
• PROVIDE STANDARD BUSINESS FUNCTIONALITY
• INDEPENDENT OF THE STATE OR CONTEXT OF OTHER SERVICES
• DESCRIBED IN A STANDARD DEFINITION LANGUAGE
• HAVE A PUBLISHED INTERFACE
SOA, WEB SERVICES, WEB 2.0, AND
MASHUPS (CONT.)
• WS ENABLES THE CREATION OF POWERFUL SERVICES THAT CAN BE ACCESSED ON-DEMAND,
IN A UNIFORM WAY
• THEIR TRUE POWER RESIDES IN ITS INTERFACE BEING ACCESSIBLE BY OTHER SERVICES
• AN ENTERPRISE APPLICATION FOLLOWING THE SOA PARADIGM IS A COLLECTION OF SERVICES TO
PERFORM COMPLEX BUSINESS LOGIC TOGETHER
• IN THE CONSUMER WEB, INFORMATION AND SERVICES MAY BE PROGRAMMATICALLY
AGGREGATED
• ACTING AS BUILDING BLOCKS OF COMPLEX COMPOSITIONS, CALLED SERVICE MASHUPS
• MANY SERVICE PROVIDERS MAKE THEIR SERVICE APIS PUBLICLY ACCESSIBLE USING STANDARD
PROTOCOLS LIKE SOAP AND REST
• AMAZON, DEL.ICIO.US, FACEBOOK, AND GOOGLE
• ONE CAN REALIZE A FULLY FUNCTIONAL WEB APPLICATION INTO PRACTICE JUST BY GLUING PIECES
WITH FEW LINES OF CODE
SOA, WEB SERVICES, WEB 2.0, AND
MASHUPS (CONT.)

• SAAS CLOUD APPLICATIONS CAN BE BUILT AS COMPOSITIONS OF OTHER SERVICES FROM


THE SAME OR DIFFERENT PROVIDERS
• SERVICES LIKE USER AUTHENTICATION, E-MAIL, PAYROLL MANAGEMENT, AND CALENDARS ARE
EXAMPLES
• CAN BE REUSED AND COMBINED IN A BUSINESS SOLUTION
• MANY BUILDING BLOCKS AND SOLUTIONS ARE NOW AVAILABLE IN PUBLIC MARKETPLACES
• POPULAR APIS ARE COMBINED TO PRODUCE A VARIETY OF INTERESTING SOLUTIONS
• GOOGLE MAPS, FLICKR, YOUTUBE, AMAZON ECOMMERCE, AND TWITTER
• FROM FINDING VIDEO GAME RETAILERS TO WEATHER MAPS
GRID COMPUTNG

• ENABLES TRANSPARENT ACCESS TO DISTRIBUTED RESOURCES


• FOCUS ON SPEEDING UP A BROAD RANGE OF SCIENTIFIC APPLICATIONS
• WEB SERVICES-BASED PROTOCOLS WHICH HELP DISCOVERING, ALLOCATING DISTRIBUTED
RESOURCES
• MANAGED AS A SINGLE VIRTUAL SYSTEM
• VAILABILITY OF RESOURCES WITH DIVERSE SOFTWARE CONFIGURATIONS
• CAUSES A PORTABILITY BARRIER
GRID COMPUTING

• MOST PRODUCTION GRIDS SHARE COMPUTE AND STORAGE RESOURCES DISTRIBUTED


ACROSS DIFFERENT ADMINISTRATIVE DOMAINS
• E.G., TERAGRID AND EGEE
• FOCUS ON BEING SPEEDING UP A BROAD RANGE OF SCIENTIFIC APPLICATIONS

• BUILD STANDARD WEB SERVICES-BASED PROTOCOLS


• ALLOW DISTRIBUTED RESOURCES TO BE DISCOVERED, ACCESSED, ALLOCATED, MONITORED,
ACCOUNTED FOR, AND BILLED FOR, ETC.
• IN GENERAL MANAGED AS A SINGLE VIRTUAL SYSTEM
• OPEN GRID SERVICES ARCHITECTURE (OGSA) DEFINES A SET OF CORE CAPABILITIES AND BEHAVIORS
THAT ADDRESS KEY CONCERNS IN GRID SYSTEMS
GRID COMPUTING (CONT.)

• GLOBUS TOOLKIT IS A MIDDLEWARE


• IMPLEMENTS SEVERAL STANDARD GRID SERVICES
• AIDED THE DEPLOYMENT OF SEVERAL SERVICE-ORIENTED GRID INFRASTRUCTURES AND
APPLICATIONS
• TOOLS ARE AVAILABLE TO INTERACT WITH SERVICE GRIDS, INCLUDING GRID BROKERS
• FACILITATE USER INTERACTION WITH MULTIPLE MIDDLEWARE
• IMPLEMENT POLICIES TO MEET QOS NEEDS
GRID COMPUTING (CONT.)

• THE DEVELOPMENT OF STANDARDIZED PROTOCOLS FOR SEVERAL GRID COMPUTING


ACTIVITIES HAS CONTRIBUTED
• ALLOW DELIVERY OF ON-DEMAND COMPUTING SERVICES OVER THE INTERNET

• ENSURING QOS IN GRIDS HAS BEEN PERCEIVED AS A DIFFICULT ENDEAVOR


• LACK OF PERFORMANCE ISOLATION HAS PREVENTED GRIDS ADOPTION IN A VARIETY OF
SCENARIOS
• RESOURCES ARE OVERSUBSCRIBED
• USERS ARE UNCOOPERATIVE
GRID COMPUTING (CONT.)

• ACTIVITIES ASSOCIATED WITH ONE USER OR VIRTUAL ORGANIZATION (VO) CAN


INFLUENCE THE PERFORMANCE PERCEIVED BY OTHER USERS USING THE SAME PLATFORM
• THE IMPOSSIBILITY OF ENFORCING QOS AND GUARANTEEING EXECUTION TIME
• ESPECIALLY FOR TIME-CRITICAL APPLICATIONS

• ANOTHER ISSUE IS THE AVAILABILITY OF RESOURCES WITH DIVERSE SOFTWARE


CONFIGURATIONS
• INCLUDING DISPARATE OPERATING SYSTEMS, LIBRARIES, COMPILERS, RUNTIME ENVIRONMENTS, ETC.
GRID COMPUTING (CONT.)

• USER APPLICATIONS WOULD OFTEN RUN ONLY ON SPECIALLY CUSTOMIZED ENVIRONMENTS


• A PORTABILITY BARRIER HAS OFTEN BEEN PRESENT ON MOST GRID INFRASTRUCTURES
• INHIBITING USERS OF ADOPTING GRIDS AS UTILITY COMPUTING ENVIRONMENTS

• VIRTUALIZATION TECHNOLOGY HAS BEEN IDENTIFIED AS THE PERFECT FIT TO ISSUES


• HOSTING MANY DISSIMILAR SOFTWARE APPLICATIONS ON A SINGLE PHYSICAL PLATFORM
• EVOLVING GRIDS TO SUPPORT AN ADDITIONAL LAYER TO VIRTUALIZE COMPUTATION, STORAGE,
AND NETWORK RESOURCES
UTILITY COMPUTING

• USERS ASSIGN A UTILITY VALUE TO THEIR JOBS


• UTILITY IS A FIXED OR TIME-VARYING VALUE CONSTITUTING QOS CONSTRAINTS LIKE
DEADLINE, IMPORTANCE, SATISFACTION ETC.
• VALUE IS THE AMOUNT USERS ARE WILLING TO PAY TO SERVICE PROVIDER TO ACCOMPLISH
THEIR DEMANDS
• PROVIDER CAN CHOOSE TO PRIORITIZE USER JOBS
• USERS COMPETE FOR RESOURCES BASED ON THE VALUE OF THEIR JOBS
UTILITY COMPUTING

• LARGE GRID INSTALLATIONS HAVE FACED NEW PROBLEMS


• EXCESSIVE SPIKES IN DEMAND FOR RESOURCES COUPLED WITH STRATEGIC AND ADVERSARIAL
BEHAVIOR BY USERS
• GRID RESOURCE MANAGEMENT TECHNIQUES DID NOT ENSURE FAIR AND EQUITABLE ACCESS TO
RESOURCES IN MANY SYSTEMS

• IN UTILITY COMPUTING ENVIRONMENTS, USERS ASSIGN A “UTILITY” VALUE TO THEIR JOBS


• UTILITY IS A FIXED OR TIME-VARYING VALUATION THAT CAPTURES VARIOUS QOS CONSTRAINTS
• DEADLINE, IMPORTANCE, SATISFACTION
UTILITY COMPUTING (CONT.)

• THE VALUATION IS THE AMOUNT USERS ARE WILLING TO PAY A SERVICE PROVIDER TO SATISFY THEIR
DEMANDS

• THE SERVICE PROVIDERS ATTEMPT TO MAXIMIZE THEIR OWN UTILITY


• DIRECTLY CORRELATE WITH THEIR PROFIT
• CHOOSE TO PRIORITIZE HIGH YIELD
• I.E., PROFIT PER UNIT OF RESOURCE) USER JOBS

• SHARED SYSTEMS ARE VIEWED AS A MARKETPLACE


• USERS COMPETE FOR RESOURCES BASED ON THE PERCEIVED UTILITY OR VALUE OF THEIR JOBS
HARDWARE VIRTUALIZATION

• HARDWARE VIRTUALIZATION ALLOWS RUNNING MULTIPLE OPERATING SYSTEMS ON A SINGLE PHYSICAL


PLATFORM
• THREE BASIC CAPABILITIES TO MANAGE WORKLOAD IN VIRTUALIZED SYSTEM
• ISOLATION: ALL PROGRAM INSTRUCTIONS FULLY CONFINED IN VM
• CONSOLIDATION: SEVERAL INDIVIDUAL AND HETEROGENEOUS WORKLOAD ON A SINGLE PHYSICAL
PLATFORM
• MIGRATION: TARGETS AT HARDWARE MAINTENANCE, LOAD BALANCING AND DISASTER RECOVERY
• OPEN VIRTUALIZATION FORMAT (OVF)
HARDWARE VIRTUALIZATION

• CLOUD COMPUTING SERVICES ARE USUALLY BACKED BY LARGE-SCALE DATA CENTERS


• COMPOSED OF THOUSANDS OF COMPUTERS
• SERVE MANY USERS
• HOST MANY DISPARATE APPLICATIONS
• HARDWARE VIRTUALIZATION OVERCOME MOST OPERATIONAL ISSUES OF DATA CENTER
BUILDING AND MAINTENANCE
• VIRTUALIZING A COMPUTER SYSTEM’S RESOURCES
• INCLUDING PROCESSORS, MEMORY, AND I/O DEVICES
• AIMING AT IMPROVING SHARING AND UTILIZATION OF COMPUTER SYSTEMS
HARDWARE VIRTUALIZATION (CONT.)

• ALLOWS RUNNING MULTIPLE OPERATING SYSTEMS AND SOFTWARE STACKS ON A SINGLE PHYSICAL
PLATFORM
• A SOFTWARE LAYER MEDIATES ACCESS TO THE PHYSICAL HARDWARE PRESENTING TO EACH GUEST
OPERATING SYSTEM A VIRTUAL MACHINE (VM)
• THE VIRTUAL MACHINE MONITOR (VMM)
• ALSO CALLED A HYPERVISOR,
• VM IS A SET OF VIRTUAL PLATFORM INTERFACES
• SEVERAL TECHNOLOGIES HAVE CONTRIBUTED TO AN INCREASING ADOPTION OF VIRTUALIZATION
• MULTI-CORE CHIPS, PARA-VIRTUALIZATION, HARDWARE-ASSISTED VIRTUALIZATION, AND LIVE MIGRATION
OF VMS
HARDWARE VIRTUALIZATION (CONT.)

Virtual Machine 1 Virtual Machine 2 Virtual Machine N


User software User software User software
Email Server Facebook App App A App X

Data Web Ruby on


Java Rails App B App Y
base Server

Linux Guest OS

Virtual Machine Monitor (Hypervisor)

Hardware
HARDWARE VIRTUALIZATION (CONT.)

• TRADITIONALLY, PERCEIVED BENEfiTS WERE IMPROVEMENTS ON SHARING AND UTILIZATION, BETTER


MANAGEABILITY, AND HIGHER RELIABILITY
• RECENTLY EMPHASIZING THREE BASIC CAPABILITIES REGARDING MANAGEMENT OF WORKLOAD IN A
VIRTUALIZED SYSTEM
• ISOLATION, CONSOLIDATION, AND MIGRATION

• WORKLOAD ISOLATION IS ACHIEVED


• ALL PROGRAM INSTRUCTIONS ARE FULLY CONFINED INSIDE A VM
• LEADS TO IMPROVEMENTS IN SECURITY
• BETTER RELIABILITY IS ALSO ACHIEVED
• SOFTWARE FAILURES INSIDE ONE VM DO NOT AFFECT OTHERS
HARDWARE VIRTUALIZATION (CONT.)

• BETTER PERFORMANCE CONTROL IS ATTAINED


• EXECUTION OF ONE VM SHOULD NOT AFFECT THE PERFORMANCE OF ANOTHER VM

• THE CONSOLIDATION OF SEVERAL INDIVIDUAL AND HETEROGENEOUS WORKLOADS ONTO A


SINGLE PHYSICAL PLATFORM
• LEADS TO BETTER SYSTEM UTILIZATION
• ALSO OVERCOMES POTENTIAL SOFTWARE AND HARDWARE INCOMPATIBILITIES IN CASE OF UPGRADES
• RUN LEGACY AND NEW OPERATION SYSTEMS CONCURRENTLY

• WORKLOAD MIGRATION TARGETS AT FACILITATING HARDWARE MAINTENANCE, LOAD BALANCING,


AND DISASTER RECOVERY
HARDWARE VIRTUALIZATION (CONT.)

• ALSO REFERRED TO APPLICATION MOBILITY


• ENCAPSULATING A GUEST OS STATE WITHIN A VM
• ALLOWING IT TO BE SUSPENDED, FULLY SERIALIZED, MIGRATED TO A DIFFERENT PLATFORM, RESUMED
IMMEDIATELY OR PRESERVED TO BE RESTORED AT A LATER DATE
• A VM’S STATE INCLUDES A FULL DISK OR PARTITION IMAGE, CONFIGURATION FILES, AND AN IMAGE
OF ITS RAM

• VMM PLATFORMS ARE THE BASIS OF MANY UTILITY OR CLOUD COMPUTING ENVIRONMENTS
HARDWARE VIRTUALIZATION (CONT.)

• VMWARE ESXI
• A VMM FROM VMWARE
• A BARE-METAL HYPERVISOR
• INSTALLS DIRECTLY ON THE PHYSICAL SERVER
• OTHERS MAY REQUIRE A HOST OPERATING SYSTEM
• THROUGH MEMORY BALLOONING AND PAGE SHARING, IT CAN OVERCOMMIT MEMORY
• INCREASING THE DENSITY OF VMS INSIDE A PHYSICAL SERVER

• XEN
• PIONEERED THE PARA-VIRTUALIZATION CONCEPT
• THE GUEST OPERATING SYSTEM, BY MEANS OF A SPECIALIZED KERNEL, CAN INTERACT WITH THE HYPERVISOR
• SIGNIFICANTLY IMPROVING PERFORMANCE
HARDWARE VIRTUALIZATION (CONT.)

• CURRENTLY FORMS THE BASE OF COMMERCIAL HYPERVISORS OF A NUMBER OF VENDORS


• MOST NOTABLY CITRIX XENSERVER AND ORACLE VM

• KVM
• A LINUX VIRTUALIZATION SUBSYSTEM
• MEMORY MANAGEMENT AND SCHEDULING ARE CARRIED OUT BY EXISTING KERNEL FEATURES
• MAKING KVM SIMPLER AND SMALLER THAN HYPERVISORS THAT TAKE CONTROL OF THE ENTIRE MACHINE
• LEVERAGES HARDWARE-ASSISTED VIRTUALIZATION
• IMPROVES PERFORMANCE
• SUPPORTS UNMODIFIED GUEST OPERATING SYSTEMS
• SUPPORTS SOME VERSIONS OF WINDOWS, LINUX, AND UNIX
VIRTUAL APPLIANCES AND THE OPEN
VIRTUALIZATION FORMAT

• AN APPLICATION COMBINED WITH THE ENVIRONMENT NEEDED TO RUN IT IS REFERRED TO AS


A VIRTUAL APPLIANCE
• OPERATING SYSTEM, LIBRARIES, COMPILERS, DATABASES, APPLICATION CONTAINERS, ETC.
• EASES SOFTWARE CUSTOMIZATION, CONFIGURATION, PATCHING AND IMPROVES PORTABILITY
• SHAPED AS A VM DISK IMAGE ASSOCIATED WITH HARDWARE REQUIREMENT
• CAN BE READILY DEPLOYED IN A HYPERVISOR
• READY-MADE ONES CONTAIN POPULAR OPERATING SYSTEMS AND USEFUL SOFTWARE
COMBINATIONS
• BOTH COMMERCIAL AND OPEN-SOURCE
VIRTUAL APPLIANCES AND THE OPEN
VIRTUALIZATION FORMAT (CONT.)
• EACH HYPERVISOR SUPPORTS A DIFFERENT VM IMAGE FORMAT
• THE FORMATS ARE INCOMPATIBLE WITH ONE ANOTHER
• INTEROPERABILITY ISSUES ARISES

• THE OPEN VIRTUALIZATION FORMAT (OVF) FACILITATES PACKING AND DISTRIBUTION OF


SOFTWARE TO BE RUN ON VMS
• OPEN, SECURE, PORTABLE, EFFICIENT AND EXTENSIBLE

• AN OVF PACKAGE CONSISTS OF A FILE OR SET OF FILES DESCRIBING:


• THE VM HARDWARE CHARACTERISTICS
• E.G., MEMORY, NETWORK CARDS, AND DISKS
• OPERATING SYSTEM DETAILS, STARTUP, AND SHUTDOWN ACTIONS, THE VIRTUAL DISKS THEMSELVES
• OTHER METADATA CONTAINING PRODUCT AND LICENSING INFORMATION
VIRTUAL APPLIANCES AND THE OPEN
VIRTUALIZATION FORMAT (CONT.)

• OVF ALSO SUPPORTS COMPLEX PACKAGES COMPOSED OF MULTIPLE VMS


• E.G., MULTI-TIER APPLICATIONS

• OVF’S EXTENSIBILITY HAS ENCOURAGED ADDITIONS RELEVANT TO MANAGEMENT OF


DATA CENTERS AND CLOUDS
VIRTUAL APPLIANCES AND THE OPEN
VIRTUALIZATION FORMAT (CONT.)

• VIRTUAL MACHINE CONTRACTS (VMC) AIDS IN COMMUNICATING AND MANAGING THE


COMPLEX EXPECTATIONS THAT VMS HAVE OF THEIR RUNTIME ENVIRONMENT AND VICE VERSA
• A CLOUD CONSUMER COULD SPECIFY MINIMUM AND MAXIMUM AMOUNTS OF A RESOURCE THAT A
VM NEEDS TO FUNCTION
• A CLOUD PROVIDER COULD EXPRESS RESOURCE LIMITS AS A WAY TO BOUND RESOURCE
CONSUMPTION AND COSTS
AUTONOMIC COMPUTING

• LESS HUMAN INVOLVEMENT IN COMPUTING SYSTEMS’ OPERATIONS


• SYSTEMS MANAGE THEMSELVES WITH HIGH-LEVEL GUIDANCE FROM HUMANS
• AUTONOMIC SYSTEMS RELY ON
SENSORS AND AUTONOMIC MANAGER TO COMPUTE OPTIMIZATIONS
EFFECTORS TO CARRY OUT CHANGES ON THE SYSTEM
AUTONOMIC COMPUTING

• AUTONOMIC COMPUTING IMPROVES SYSTEMS BY DECREASING HUMAN INVOLVEMENT IN


THEIR OPERATION
• SYSTEMS SHOULD MANAGE THEMSELVES WITH HIGH-LEVEL GUIDANCE FROM HUMANS

• AUTONOMIC, OR SELF-MANAGING, SYSTEMS RELY ON MONITORING PROBES AND GAUGES


(SENSORS)
• ON AN ADAPTATION ENGINE (AUTONOMIC MANAGER) FOR COMPUTING OPTIMIZATIONS BASED
ON MONITORING DATA
• ON EFFECTORS TO CARRY OUT CHANGES ON THE SYSTEM
AUTONOMIC COMPUTING (CONT.)

• THE FOUR PROPERTIES OF AUTONOMIC SYSTEMS


• SELF-CONFIGURATION, SELF-OPTIMIZATION, SELF-HEALING, AND SELF-PROTECTION

• DATA CENTER AUTOMATION MAY PERFORM TASKS


• MANAGEMENT OF SERVICE LEVELS OF RUNNING APPLICATIONS
• MANAGEMENT OF DATA CENTER CAPACITY
• PROACTIVE DISASTER RECOVERY
• AUTOMATION OF VM PROVISIONING
REFERENCES

1. Luo, X., Zhang, W., Li, H., Bose, R., & Chung, Q. B. (2018). Cloud computing capability: its technological
root and business impact. Journal of Organizational Computing and Electronic Commerce, 28(3), 193-213.
2. Sehgal, N. K., & Bhatt, P. C. P. (2018). Cloud Computing Pyramid. In Cloud Computing (pp. 41-50).
Springer, Cham.
3. Haris, M., & Khan, R. Z. (2018). A Systematic Review on Cloud Computing.
4. Sehgal, N. K., & Bhatt, P. C. (2018). Cloud Computing. Springer, Heidelberg
5. Craig, C. A. (2018). Cloud Anchor: An Exploration of Service Integrity Attestation with Hardware Roots of
Trust.

You might also like