Conference Paper

Model Driven Provisioning: Bridging the Gap Between Declarative Object Models and Procedural Provisioning Tools.

DOI: 10.1007/11925071_21 Conference: Middleware 2006, ACM/IFIP/USENIX 7th International Middleware Conference, Melbourne, Australia, November 27-December 1, 2006, Proceedings
Source: DBLP

ABSTRACT Today’s enterprise data centers support thousands of mission-critical business applications composed of multiple distributed
heterogeneous components. Application components exhibit complex dependencies on the configuration of multiple data center
network, middleware, and related application resources. Applications are also associated with extended life-cycles, migrating
from development to testing, staging and production environments, with frequent roll-backs. Maintaining end-to-end data center
operational integrity and quality requires careful planning of (1) application deployment design, (2) resource selection,
(3) provisioning operation selection, parameterization and ordering, and (4) provisioning operation execution. Current data
center management products are focused on workflow-based automation of the deployment processes. Workflows are of limited
value because they hard-code many aspects of the process, and are thus sensitive to topology changes. An emerging and promising
class of model-based tools is providing new methods for designing detailed deployment topologies based on a set of requirements
and constraints. In this paper we describe an approach to bridging the gap between generated “desired state” models and the
elemental procedural provisioning operations supported by data center resources. In our approach, we represent the current
and desired state of the data center using object models. We use AI planning to automatically generate workflows that bring
the data center from its current state to the desired state. We discuss our optimizations to Partial Order Planning algorithms
for the provisioning domain. We validated our approach by developing and integrating a prototype with a state of the art provisioning
product. We also present initial results of a performance study.


Available from: Kaoutar El Maghraoui, Feb 11, 2014
1 Follower
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: On the one hand, ACME is a language designed in the late 90s as an interchange format for software architectures. The need for recon guration at runtime has led to extend the language with speci c support in Plastik. On the other hand, PDDL is a predicative language for the description of planning problems. It has been designed in the AI community for the International Planning Competition of the ICAPS conferences. Several related works have already proposed to encode software architectures into PDDL. Existing planning algorithms can then be used in order to generate automatically a plan that updates an architecture to another one, i.e., the program of a recon guration. In this paper, we improve the encoding in PDDL. Noticeably we propose how to encode ADL types and constraints in the PDDL representation. That way, we can statically check our design and express PDDL constraints in order to ensure that the generated plan never goes through any bad or inconsistent architecture, not even temporarily.
  • [Show abstract] [Hide abstract]
    ABSTRACT: The business process literature has proposed a multitude of business process modelling approaches or paradigms, each in response to a different business process type with a unique set of requirements. Two polar paradigms, i.e. the imperative and the declarative paradigm, appear to define the extreme positions on the paradigm spectrum. While imperative approaches focus on explicitly defining how an organisational goal should be reached, the declarative approaches focus on the directives, policies and regulations restricting the potential ways to achieve the organisational goal. In between, a variety of hybrid-paradigms can be distinguished, e.g. the advanced and adaptive case management.This article focuses on the less-exposed declarative approach on process modelling. An outline of the declarative process modelling and the modelling approaches is presented, followed by an overview of the observed declarative process modelling principles and an evaluation of the declarative process modelling approaches.
    Enterprise Information Systems 06/2013; 9(2):161-185. DOI:10.1080/17517575.2013.830340 · 9.26 Impact Factor
  • [Show abstract] [Hide abstract]
    ABSTRACT: The software defined environment (SDE) provides a powerful programmable interface to a cloud infrastructure through an abstraction of compute, network, and storage resources. A workload refers to the application to be deployed in such an infrastructure. To take advantage of the SDE interface, the workload is described using a declarative workload definition language and is then deployed in the infrastructure through an automated workload orchestration and optimization layer. This paper describes the architecture and algorithms that make up this layer. Given a definition of the workload, including the virtual components of the application and their resource needs, as well as other meta-information relating to factors such as performance, availability, and privacy, the function of the workload orchestration and optimization layer is to map virtual resources to physical resources and realize such a mapping in the infrastructure. This mapping, known as placement, is optimized so that the infrastructure is efficiently utilized, and the workload requirements are satisfied. We present the overall architecture of the workload orchestration and optimization runtime. We focus on the workload placement problem and describe our optimization framework. Then, we consider a real application, IBM Connections, as a use-case to demonstrate the orchestration and optimization functionalities.
    Ibm Journal of Research and Development 03/2014; 58(2):1-12. DOI:10.1147/JRD.2014.2304864 · 0.50 Impact Factor