Abstract

Current cloud service offerings, i.e., Software-as-a-service (SaaS), Platform-as-a-service (PaaS) and Infrastructure-as-a-service (IaaS) offerings are often provided as monolithic, one-size-fits-all solutions and give little or no room for customization. This limits the ability of Service-based Application (SBA) developers to configure and syndicate offerings from multiple SaaS, PaaS, and IaaS providers to address their application requirements. Furthermore, combining different independent cloud services necessitates a uniform description format that facilitates the design, customization, and composition. Cloud Blueprinting is a novel approach that allows SBA developers to easily design, configure and deploy virtual SBA payloads on virtual machines and resource pools on the cloud. We propose the Blueprint concept as a uniform abstract description for cloud service offerings that may cross different cloud computing layers, i.e., SaaS, PaaS and IaaS. To support developers with the SBA design and development in the cloud, this paper introduces a formal Blueprint Template for unambiguously describing a blueprint, as well as a Blueprint Lifecycle that guides developers through the manipulation, composition and deployment of different blueprints for an SBA. Finally, the empirical evaluation of the blueprinting approach within an EC’s FP7 project is reported and an associated blueprint prototype implementation is presented.

Highlights

  • The cloud abstraction model delivers a shared pool of configurable computing resources that can be dynamically and automatically provisioned and released

  • 4 we elaborate the Blueprint concept, its fundamental structure and different types of blueprint; in Section 5 we propose the Blueprint Template to capture cross-layer cloud service offerings; Section 6 proposes a six-step lifecycle for the blueprinting approach that supports the engineering of Service-based Application (SBA) in the cloud; in Section 7 we present our empirical evaluation approach and blueprint prototype implementation; Section 8 summarizes the paper and discusses future issues

  • Developers can create sophisticated SBAs from applications, platforms and infrastructures offered by different providers in the cloud to achieve end-to-end business requirements

Read more

Summary

Introduction

The cloud abstraction model delivers a shared pool of configurable computing resources (processors, storage, etc.) that can be dynamically and automatically provisioned and released. From the preceding discussion it is apparent that the current cloud solutions are fraught with problems: They introduce a monolithic SaaS/PaaS/IaaS stack architecture where a one-size-fits-all mentality prevails They do not allow developers to mix and match functionality and services from multiple application, platform and infrastructure providers and configure it dynamically to address application needs. Cloud Blueprinting seeks to simplify deployment by hiding away the complexity of deploying a SBA by helping to manage all configuring of the underlying middleware and integrating with optimal PaaS and IaaS options It achieves portability across clouds and cloud providers to leverage the benefits of elasticity and scale. 4 we elaborate the Blueprint concept, its fundamental structure and different types of blueprint; in Section 5 we propose the Blueprint Template to capture cross-layer cloud service offerings; Section 6 proposes a six-step lifecycle for the blueprinting approach that supports the engineering of SBAs in the cloud; in Section 7 we present our empirical evaluation approach and blueprint prototype implementation; Section 8 summarizes the paper and discusses future issues

Motivating Scenario
Related Work
The Blueprint Concept
Fundamental Blueprint Structure
Types of Blueprints
Blueprint Template
Basic Properties
Offering Section
Implementation Artifacts Section
Resource Requirements Section
Policy Section
Blueprint Lifecycle Support for Engineering Cloud-Based Applications
Phase 1
Phase 2
Phase 3
Phase 4
Phase 5
Phase 6
Empirical Evaluation and Prototype Implementation
Conclusion and Future Work
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.