Dimensions for Evaluating Cloud Resource Orchestration Frameworks
Total Page:16
File Type:pdf, Size:1020Kb
qM qMqM Computer Previous Page | Contents |Zoom in | Zoom out | Front Cover | Search Issue | Next Page qMqM Qmags THE WORLD’S NEWSSTAND® COVER FEATURE CLOUD COMPUTING Dimensions for Evaluating Cloud Resource Orchestration Frameworks Alireza Khoshkbarforoushha, Australian National University and Commonwealth Scientific and Industrial Research Organisation Meisong Wang, Australian National University Rajiv Ranjan, Newcastle University Lizhe Wang, Chinese Academy of Sciences Leila Alem, Commonwealth Scientific and Industrial Research Organisation Samee U. Khan, North Dakota State University Boualem Benatallah, University of New South Wales Despite the proliferation of cloud resource orchestration frameworks (CROFs), DevOps managers and application developers still have no systematic tool for evaluating their features against desired criteria. The authors present generic technical dimensions for analyzing CROF capabilities and understanding prominent research to refine them. loud computing assembles a large network set of cloud resources to fit application architecture opti- of virtualized services—from storage and mized for the desired quality of service (QoS) remains a networking to databases and workload- challenging technical problem. In simple terms, cloud Cbalancing software—and enables instant resource orchestration is the selection, deployment, access to virtually unlimited software and hardware monitoring, and runtime management of software and resources. It offers a number of considerable advantages, hardware resources to ensure that applications meet including no upfront investment, lower operating costs, QoS targets, such as availability, throughput, latency, and infinite scalability. However, orchestrating the right security, cost, and reliability under uncertainties.1 24 COMPUTER PUBLISHED BY THE IEEE COMPUTER SOCIETY 0018-9162/16/$33.00 © 2016 IEEE qM qMqM Computer Previous Page | Contents |Zoom in | Zoom out | Front Cover | Search Issue | Next Page qMqM Qmags THE WORLD’S NEWSSTAND® qM qMqM Computer Previous Page | Contents |Zoom in | Zoom out | Front Cover | Search Issue | Next Page qMqM Qmags THE WORLD’S NEWSSTAND® SaaS Email CRM Crowdsourcing Since the inception of cloud com- CloudFormation puting in mid-2000, academic groups PaaS and industry vendors have developed various cloud resource orchestration frameworks (CROFs) to simplify appli- Web server Database Load App server Monitoring cation management. A CROF aids soft- appliance appliance balancer appliance appliance ware engineers, DevOps managers, and infrastructure administrators in migrating to and managing in-house IaaS applications in cloud environments. Elastic IP Figure 1 shows how a CROF fits into CPU Cache memory VPN EBS the cloud computing ecosystem. Amazon Web Services (AWS) Elas- FIGURE 1. Cloud resource orchestration framework’s (CROF’s) position in the cloud tic Beanstalk is an example of an ecosystem. Despite the many cloud-standardization projects, the community has not yet easy-to-use CROF for deploying and defined a comprehensive standard to cover all cloud layers including infrastructure as a scaling multitier Web applications service (IaaS), platform as a service (PaaS), and software as a service (SaaS). CRM: cus- developed with popular program- tomer relationship management; EBS: elastic block store; VPN: virtual private network. ming languages, including Java, .NET, PHP, Node.js, Python, and Ruby. Another example is Ooyala’s CROF administration overhead. Moreover, simplicity of comprehension, which for delivering multimedia content migration from one cloud provider to are essential to successful practical online. At the infrastructure layer, another is nontrivial, if not impossible. use. Resource orchestration in cloud Ooyala’s CROF leverages AWS Elas- Despite the many cloud standardiza- environments must also contend tic Compute Cloud (EC2) and Simple tion projects (http://cloud-standards with the scale and variety of resource Storage Solution (S3) resources for .org),___ the community has no compre- types and the uncertainties inherent content distribution and storage. hensive standard.2 in a cloud environment. Finally, inte- From the service provider’s per- gration and interoperational depen- PROLIFERATION WITHOUT spective, the lack of standardiza- dencies intensify the challenge of STANDARDIZATION tion among resource-orchestration building application architecture With the proliferation of CROFs from techniques is no accident. Most over the cloud.1 competing vendors and academic approaches aim to improve productiv- groups has come an often bewilder- ity by automating the structured pro- EVALUATING CROFs ing array of frameworks with simi- cesses that IT departments or profes- The variety of CROFs offered can lar (if not identical) functionalities. sional programmers handle—those make selection challenging for soft- For example, any of the CROFs from more equipped for the hardware and ware engineers, solution architects, or RightScale, Bitnami, EngineYard, and software resource coordination that DevOps managers who want to migrate CloudSwitch are suitable for man- orchestration requires. their applications to the cloud. To aid aging Web applications over AWS In addition to traditional con- that process, we developed technical and other public cloud infrastruc- trol and dataflow programming dimensions for CROF analysis that tures. Similarly, CloudFront, Ooyala, constructs, there is a need for rich provide insights into existing frame- MetaCDN, or RackSpace Cloud Files abstractions to support consistency works by answering why, what, and could be used to manage content across physical and logical layers; how frameworks complete resource delivery–network (CDN) applications. exception handling; and flexible, orchestration. We then analyzed the This diversity makes selection a risky efficient resource coordination and strengths and weaknesses of popular task, as wrong decisions could lead management. All these supporting frameworks in light of these dimen- to vendor lock-in, poor application mechanisms must balance the ten- sions and surveyed recent research QoS, excessive costs, and unwanted sions between the rich semantics and work pertinent to each dimension. FEBRUARY 2016 25 qM qMqM Computer Previous Page | Contents |Zoom in | Zoom out | Front Cover | Search Issue | Next Page qMqM Qmags THE WORLD’S NEWSSTAND® qM qMqM Computer Previous Page | Contents |Zoom in | Zoom out | Front Cover | Search Issue | Next Page qMqM Qmags THE WORLD’S NEWSSTAND® CLOUD COMPUTING Application domain reinforced by parallelizing subtasks administrator or DevOps manager This dimension refers to the type of in a cluster. manipulates cloud resources. applications that the frameworks have been targeted and customized Resource type Command line. The command-line to, including multitier Web applica- This dimension refers to the resource interface wraps cloud-specific API tions, CDN, and large-scale data process- type the framework can orchestrate. actions as commands or scripts that ing (also known as big data). Multitier Infrastructure resources, which include are executable through Linux (bash Web applications refers to migrat- network, CPU, and blob storage, or sh) or Windows-based (command. ing in-house Web, mobile, or gaming require looking at aspects such as IP com or cmd.exe) shell environments. applications to public or private clouds type or ports, cores or addressing bit, Although command-line orches- for improved scalability, availability, and storage size and format. Platform tration frameworks can be easier to implement, their use requires sophis- ticated technical expertise and a deep understanding of cloud resources and CROFs WITH CLOUD INTEROPERABILITY— related orchestration operations. TO PORT APPLICATIONS TO OR USE RESOURCES FROM MULTIPLE CLOUDS— Web portal. The portal presents cloud resources as user-friendly artifacts, ARE MORE LIKELY TO BE ADOPTED. such as buttons and checkboxes, and resource catalogs. Visual artifacts and catalogs aim to simplify resource selection, assembly, and deployment. and so on, as well as for conducting resources include application servers A catalog manages resource-entity development and test activities in the (such as the Java application server), sets that can be instantiated to create cloud environment. monitoring services, database servers, CPU, storage, and network objects. CROFs that target CDN applications and the like. Software components and The portal also features an editor give businesses and Web application subprocesses include customer rela- that lets users assemble and deploy developers an easy and cost-effective tionship management (CRM) business applications by dragging appliance way to distribute content (including processes that are formed and exe- entities from the catalog, and integrat- images, videos, and webpages) to spo- cuted through software-component ing and configuring them through cus- radic geographical locations with low orchestration to deliver a business ser- tomized configuration-management latency and high data-transfer speeds. vice to end users. An example is the interfaces. CDN offerings normally use edge com- Salesforce CRM platform. These features make the Web puting, which pushes the frontier of All three resource categories (infra- portal simpler and more flexible for computing applications, data, and ser- structure, platform, and software) are the administrator to use than the vices away from centralized nodes to mapped to the so-called cloud service command-line tool. servers