没有合适的资源?快使用搜索试试~ 我知道了~
基于运行时模型的混合PaaS服务使用方法
0 下载量 149 浏览量
2021-04-11
11:29:42
上传
评论
收藏 1.11MB PDF 举报
温馨提示
云计算已成为通过Internet交付服务的新范例。 在这个不断增长的市场中,PaaS(平台即服务)云已经成为一种重要的模型,它允许简单,灵活地部署应用程序,而无需专用的网络,服务器,存储和其他服务。 在过去的几年中已经提供了许多PaaS服务,并且需要使用混合PaaS服务来满足管理要求,例如遗留系统集成和动态资源扩展。 但是,PaaS云之间存在各种管理接口和不同的管理机制,这给混合云中的应用程序部署带来了很大的难度和复杂性。 在本文中,我们提出了一种基于运行时模型的方法来使用混合PaaS服务。 首先,PaaS服务的可管理性被抽象为与相应系统自动连接的运行时模型。 其次,根据当前PaaS云的领域知识,我们提供一个统一的PaaS服务模型。 第三,通过模型转换确保统一模型与运行时模型之间的同步。 因此,管理员能够以统一的方式使用混合PaaS服务,并且还可以通过在统一模型上执行程序来执行管理逻辑,从而降低了混合云管理的难度和复杂性。
资源推荐
资源详情
资源评论
Runtime Model based Approach to Using Hybrid PaaS
Services
Yizhou Wang
1,2
, Aipeng Li
1,2
, Xing Chen
1,2,+
, Ying Zhang
3,4
, Gang Huang
3,4
1 College of Mathematics and Computer Science, Fuzhou University, Fuzhou 350108, China
2 Fujian Provincial Key Laboratory of Networking Computing and Intelligent Information Processing
3 Key Laboratory of High Confidence Software Technologies (Ministry of Education)
4 School of Electronics Engineering and Computer Science, Peking University, Beijing, 100871, China
+ E-mail: chenxing@fzu.edu.cn
ABSTRACT
Cloud computing has emerged as a new paradigm for services
delivering over the Internet. In this growing market, PaaS
(Platform-as-a-Service) cloud has been an important model
allowing a simple and flexible deployment of applications,
without the need for dedicated networks, servers, storage and
other services. Many PaaS services have been provided in the past
few years and it is required to use hybrid PaaS services in order to
satisfy management requirements such as legacy system
integration and dynamic resource scaling. However, there are
various management interfaces and different management
mechanisms among PaaS clouds, which cause great difficulty and
high complexity to application deployment in a hybrid cloud. In
this paper, we present a runtime model based approach to using
hybrid PaaS services. First, the manageability of PaaS services is
abstracted as runtime models that are automatically connected
with the corresponding systems. Second, we provide a unified
model of PaaS services, according to the domain knowledge of
current PaaS clouds. Third, the synchronization between the
unified model and runtime models is ensured through model
transformation. Thus, administrators are able to use hybrid PaaS
services in a unified manner and management logic can be also
carried out by executing programs on the unified model, which
decreases the difficulty and complexity of hybrid cloud
management.
Keywords
PaaS Service, Hybrid Cloud Management, Models at Runtime.
1. INTRODUCTION
With the development of cloud computing, many PaaS(Platform
as a Service) services and products have been provided in the past
few years, including public cloud services like Google App
Engine [1], and open source PaaS products like Cloud Foundry
[2]. These PaaS clouds can support different types of applications
such as Java and PHP, and provide some extended services such
as database and mail. In order to satisfy management requirements
such as cross-domain resource provision, legacy system
integration and dynamic resource scaling, it is required to use
hybrid PaaS services in some scenarios. However, there are
various management interfaces and different management
mechanisms among PaaS clouds, which may cause great difficulty
and high complexity to application deployment in a hybrid cloud.
This obstacle can be broken into two parts.
On one hand, there are various management interfaces among
PaaS services. Their method names, input parameters and
execution effects are different from each other, which increases
the complexity of using hybrid PaaS services.
On the other hand, each of PaaS services has its own management
mechanism. There are differences in resource classification,
organization and features among PaaS clouds. Administrators
have to be familiar with these management mechanisms which
increases the difficulty of application deployment in a hybrid
cloud.
Actually, using hybrid PaaS services is aimed to construct and
manage a hybrid PaaS cloud through invoking management
interfaces provided by different PaaS clouds. For instance,
administrators deploy the application on both a private PaaS cloud
based on Cloud Foundry and Baidu App Engine [3]; in order to
satisfy the requirement of dynamic resource scaling, they need to
develop management programs to ensure that extra resources will
be automatically added when the application load is high.
However, these management programs can cause high
programming efforts and costs. Administrators first have to be
familiar with the APIs provided by PaaS clouds and then build
programs upon them, which is not easy due to diversity of PaaS
services. In these management programs, proper APIs have to be
chosen for use and different types of APIs must be interoperable
with each other. Such tedious work is not the core of the
management logic compared with the analyzing and planning
related codes, but it has to be done to make the whole
management program run effectively. During this procedure, the
underlying APIs as well as the collected low-level data can
sometimes exhaust and frustrate developers. Furthermore, as the
programs are built on code that directly connects to PaaS services,
they are not easy to reuse.
Software architecture acts as a bridge between requirements and
implementations [4]. It describes the overall structure of a
software system with a collection of managed elements and can be
used to reduce the complexity and cost resulting from the
difficulties faced by understanding large-scale complex software
systems [5]. Modeling the system architecture is a natural
Permission to make digital or hard copies of all or part of this work for
personal or classroom use is granted without fee provided that copies are
not made or distributed for profit or commercial advantage and that copies
bear this notice and the full citation on the first page. Copyrights for
components of this work owned by others than ACM must be honored.
Abstracting with credit is permitted. To copy otherwise, or republish, to
post on servers or to redistribute to lists, requires prior specific permission
and/or a fee. Request permissions from Permissions@acm.org.
Internetware '16, September 18 2016, Beijing, China
© 2016 ACM. ISBN 978-1-4503-4829-4/16/09…$15.00
DOI: http://dx.doi.org/10.1145/2993717.2993719
19
approach to getting a better understanding of the problem domain.
Runtime architecture based model is a dynamic and structural
abstract of the running system, which describes the elements of
current system, the state of these elements, and the relation
between them. With the help of runtime models, administrators
can obtain a better understanding of their systems and write
model-level programs for management. In order for system
administrators to monitor and control the system through reading
and editing the architecture, runtime model has a causal
connection with the running system: any states of the running
system can be monitored by the runtime model, and any changes
to the runtime model can be applied on the running system [6][7].
This has been adopted in the runtime management of software
systems [8][9][10].
In this paper, we present a runtime model based approach to using
hybrid PaaS services, in order to deploy the application onto the
hybrid PaaS cloud and manage the runtime environment more
efficiently, as shown in Figure 1. First, the manageability of PaaS
services is abstracted as runtime models. The runtime models of
PaaS services can be used in different management scenarios, but
its construction is a one-off work. Second, a unified model of
PaaS services is provided according to the domain knowledge of
current PaaS clouds platforms, such as Cloud Foundry, Google
App Engine and Baidu App Engine. Third, the synchronization
between the unified model and runtime models is ensured through
model transformation. In our approach, administrators are able to
use hybrid PaaS services in a unified manner and develop model-
level management programs, so the workload of hand coding can
be greatly reduced. As an additional contribution, we apply the
runtime model-based framework to a real hybrid cloud.
Figure 1. view of the runtime model based to using hybrid
PaaS services
The rest of this paper is organized as follows: Section 2 introduces
runtime models of PaaS services. Section 3 presents the united
model of PaaS services. Section 4 describes model transformation
from the unified model to runtime models. Section 5 illustrates a
case study and reports the evaluation. Section 6 discusses related
works. Section 7 concludes this paper and indicates our future
work.
2. RUNTIME MODEL OF PAAS SERVICES
There are various management interfaces among PaaS services.
Thus, we construct runtime models of PaaS services in order to
use them at model level. This is done easily with the help of
SM@RT (Supporting Models at Run Time) [11][12], which is a
model-driven framework that supports model-based runtime
system development.
SM@RT consists of a domain-specific modeling language
(SM@RT language) and a code generator (SM@RT generator).
SM@RT language allows developers to specify: (1) the structure
of the target system and the manageable elements using a meta-
model; (2) how to manipulate system elements and invoke the
system API via an access model. Using these two models, the
SM@RT generator can automatically generate the
synchronization engine to reflect PaaS resources to the runtime
model. The synchronization engine not only enables any states of
PaaS resources to be monitored by the runtime model, but also
enables any changes to the runtime model to be applied on PaaS
resources. Thus we can manage PaaS resources through
operations on the runtime model, and these operations will
propagate to underlying systems.
3. A UNIFIED MODEL FOR PAAS
SERVICES
In order to use hybrid PaaS services in a unified manner, we
propose a unified model of PaaS services according to the domain
knowledge of current PaaS clouds. PaaS users need to control
over the deployed applications and possibly configuration setting
for the application-hosting environment. The unified model
provides a management view to them. The model elements
describe runtime information about different types of PaaS
resources, and the model operations describe different types of
management operations upon the resources. Figure 2 shows the
main elements in the unified model. There are generally two types
of resources provided by PaaS clouds, including services and
appliances [13].
On one hand, element Services describes the list of PaaS services
such as cluster services and database services, which provide
configurable advanced functions. The most important one is the
cluster service. Element CService describes the basic information
about the cluster service and it contains several types of elements
which are used to create a application cluster. Element Domain
describes the domain names which can be used by the cluster.
Element Image describes the software stack of instance in the
cluster including operating systems, language packages and
middleware software components. Element Flavor describes the
hardware resources of instance in the cluster, such as CPU,
memory and disk. Element Cluster describes information about
the created cluster and it contains a list of Instance elements
which describe runtime information about the instances of the
cluster. Another important service is the database service. Element
DBService describes the basic information about the database
service and it contains two types of elements which are used to
create a database. Element DBPlan describes configuration
parameters of the database. Element DB describes information
about the created database such as resource utilization. There are
other alternative services such as the mail service and the map-
reduce service, which can be added to the unified model
according to requirements.
On the other hand, element Appliances describes the list of PaaS
appliances which provide configurable system containers with
middleware software components. Element Image and ServerType
describe configurations of software stack and hardware resources
of appliances. Element Network describes information about the
subnet and it contains a list of public IP addresses which can be
mapped to internal IP addresses in the subnet. Element Nic
describes the virtual network card which can be added to the
appliance. There are different types of appliance elements and all
20
剩余7页未读,继续阅读
资源评论
weixin_38681286
- 粉丝: 1
- 资源: 898
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
最新资源
- 【创新未发表】基于人工蜂鸟优化算法AHA-ELM实现北半球光伏数据预测附Matlab代码.rar
- 【创新未发表】基于人工蜂鸟优化算法AHA-ESN实现北半球光伏数据预测附Matlab代码.rar
- 【创新未发表】基于人工蜂鸟优化算法AHA-CNN实现交通量预测附Matlab代码.rar
- 【创新未发表】基于人工蜂群优化算法ABC-ELM实现北半球光伏数据预测附Matlab代码.rar
- 【创新未发表】基于人工蜂群优化算法ABC-ESN实现北半球光伏数据预测附Matlab代码.rar
- 【创新未发表】基于人工蜂群优化算法ABC-CNN实现交通量预测附Matlab代码.rar
- 【创新未发表】基于人工鱼群算法ASFO-ESN实现北半球光伏数据预测附Matlab代码.rar
- 【创新未发表】基于人工鱼群算法ASFO-ELM实现北半球光伏数据预测附Matlab代码.rar
- 【创新未发表】基于三角测量拓扑聚合优化器TTAO-ELM实现北半球光伏数据预测附Matlab代码.rar
- 【创新未发表】基于三角测量拓扑聚合优化器TTAO-CNN实现交通量预测附Matlab代码.rar
- 【创新未发表】基于三角测量拓扑聚合优化器TTAO-ESN实现北半球光伏数据预测附Matlab代码.rar
- 【创新未发表】基于人工鱼群算法ASFO-CNN实现交通量预测附Matlab代码.rar
- 【创新未发表】基于沙猫群优化算法SCSO-CNN实现交通量预测附Matlab代码.rar
- 【创新未发表】基于沙猫群优化算法SCSO-ELM实现北半球光伏数据预测附Matlab代码.rar
- 【创新未发表】基于沙猫群优化算法SCSO-ESN实现北半球光伏数据预测附Matlab代码.rar
- 【创新未发表】基于蛇群优化算法SO-ESN实现北半球光伏数据预测附Matlab代码.rar
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功