Models@runtime (models at runtime) are based on computation reflection. Runtime models can be regarded as a reflexive layer causally connected with the underlying system. Hence, every change in the runtime model involves a change in the reflected system, and vice versa. To the best of our knowledge, there are no runtime models for Python applications. Therefore, we propose a formal approach based on Petri Nets (PNs) to model, develop, and reconfigure Python applications at runtime. This framework is supported by a tool whose architecture consists of two modules connecting both the model and its execution. The proposed framework considers execution exceptions and allows users to monitor Python expressions at runtime. Additionally, the application behavior can be reconfigured by applying Graph Rewriting Rules (GRRs). A case study using Service-Level Agreement (SLA) violations is presented to illustrate our approach.
In the last decade, cloud computing has emerged as one of the most popular computing models. This model delivers a pool of computing resources as on-demand services to different categories of users. As the number of cloud services available on the Internet is increasing and owing to the users' complicated requirement, the composition of cloud services has become more and more challenging. In this work, we are interested in the vertical composition that represents the collaboration of services from different cloud layers to offer a complete solution to end-users. This paper proposes the Bigraphical Reactive Systems (BRS) to model the service composition. We use bigraphs to describe the different actors and services evolving in the composition. In addition, we define a set of bigraphical reactive rules to express the dynamic behaviors of these services and actors and to show the direct and indirect dependencies between them.
23 September 2020 in Computer Standards & Interfaces
The service computing paradigm has been widely adopted in various domains, such as in Web applications, Cloud computing and Internet of Things (IoT). Service providers offer services to their clients depending on their functional and non-functional requirements. Generally, the process of using a service consists of three steps discovery, selection, and invocation. This process is subject to many variables. For instance, no service with the required properties was found implying a requirement update, or just the invocation does not work. Therefore, the service monitoring is a necessary feature to be included by service providers. In this paper, we propose a model at-runtime approach to monitor this three-steps-process. We specify the proposed model using the Petri net formalism and the Flexible framework. Our approach allows service managers to monitor the three steps, change requirements when no service can satisfy the current requirements, and select other services when invocations fail. The monitoring system notifies service managers about the request state, the requirement changes required, and the invocation failures based on the Petri net marking. In addition, Python expressions can be used at runtime. Finally, a case study illustrates the approach by the implementation of a compression service.