WO2019121679A1

WO2019121679A1 - Cloud management platform

Info

Publication number: WO2019121679A1
Application number: PCT/EP2018/085489
Authority: WO
Inventors: Johan LOUTER
Original assignee: Atos International B.V.
Priority date: 2017-12-21
Filing date: 2018-12-18
Publication date: 2019-06-27
Also published as: FR3075998B1; FR3075998A1

Abstract

The present invention concerns a Server for managed PaaS comprising in a container-based architecture at least a processor and memories to save data and executable softwares so as to embed Apprenda software into a fully managed PaaS stack, abstracting complex hybrid laaS away.

Description

CLOUD MANAGEMENT PLATFORM

TECHNICAL FIELD OF THE INVENTION

[0001] The invention relates to the field of platform as a service (PaaS).

STATE OF THE PRIOR ART

[0001] Increasingly Computer Systems are being implemented "in the Cloud" and are characterized as Software as Service (SaaS) and Infrastructure as a Service (laaS) and Platform as a Service (PaaS). The Cloud has the potential to adversely affect end-user performance due to the inherent characteristics of Network and Infrastructure technologies.

[0002] Historically applications hosts lived in a data center and where accessed by users behind a corporate firewall easy to monitor, the traffic went from end to end and it was easy to see when something went down fix it, the view was firmly focused on the performance and availability of the infrastructure not the application or the end user.

[0003] Todays focus has shifted now with multiple redundant systems to maintain availability the view has shifted from the infrastructure and is firmly focused on the end user experience.

[0004] But with Super complex application landscapes and hyper scale cloud infrastructures traditional monitoring tools don’t have the reach or visibility into the components that is required to successfully monitor the end to end application delivery chain.

[0005] Without the correct services in place, when a user or customer has a problem it’s difficult if not impossible to quickly find the needle in the haystack particularly if you’re not in control of that part of the haystack.

[0006] As circumstances change, workloads will need to move between clouds.

[0007] Flexibility and ease of migration placement across multiple private and public clouds and devices is vital. [0008] The PaaS Platform Services solution focusses on application cloudification: it is unique in supporting the full application lifecycle: from application development and migration to the cloud, including the runtime on any hybrid infrastructure of your choice.

[0009] It saves application lifecycle cost and increases the time to market through faster application development cycles and quick deployments.

[00010] The present invention is the only one offering Cloudification using PaaS Platform Services platforms with embedded hybrid Infrastructure of the user choice.

[00011] An aim of the invention is that most enterprises shouldn’t have to learn how to run a complex PaaS system in order to derive this benefit. Just consume and focus on the benefits derived from developing and running modern application services.

DISCUSSION OF THE INVENTION

[00012] The present invention therefore has the object of proposing a Server, constituting a managed PaaS giving the possibility of overcoming at least one portion of the drawbacks of the prior art.

[00013] A Server for managed PaaS comprising in a container-based architecture at least a processor and memories to save data and executable softwares so as to embed Apprenda software into a fully managed PaaS stack, abstracting complex hybrid laaS away.

[00014] A server according to claim 1 , wherein it comprises at least one or several of the following services: at least a cloud service processing module (ServiceNow) representing a first layer, executed on at least a processor of a platform configured to parse and orchestrate a cloud service requested to consume from the cloud service user request, to select the cloud computing services and/or resources provided by the cloud service provider and/or a function mode, execute a cloud service operation and make end to end management in the cloud through dialog with a second layer of Apprenda integrated software for application transformation and a third layer of other integrated softwares for infrastructure brockering with the public cloud AWS managed by the integrated softwares such as AWS for a public cloud.

[00015] A server according the invention wherein SNOW executed on the server and displayed on a console adapted to Apprenda by integrating a specific API (Application Programming Interface) configured to interface SNOW language and command to the language and command of Apprenda.

[00016] A server according the invention wherein a second specific API configured to interface with the AWS laaS to transform the language and command generated by Apprenda in language and command adapted to laaS language and command.

[00017] A server according the invention wherein ServiceNow comprises :

• a portal module

• a catalogue and process orchestration module for orchestrating several requests on several server instances with a data protection management functionality, configured to store the information of cloud computing services and/or resources;

• a security module, configured to provide security assurance for the cloud service requester to access a cloud service;

• a monitoring management module, configured to monitor a running status of the cloud service;

• a service level management module providing an interface for determining and saving at least one of the following parameters:

o time window for support availability,

o time window for incident handling depending on priority ,

o time window for change handling,

o virtual server size,

o physical server size,

o initial and minimal storage size,

o data recovery parameter such as RPO recovery point objective, or RTO recovery time objectiveService Level • a catalogue and process orchestration module for orchestrating several requests on several server instances with a data protection management functionality, configured to store the information of cloud computing services and/or resources.

[00018] A server according the invention wherein ServiceNow is configured to:

- receiving a workflow, the workflow defining a flow of discrete activities and paths of execution connecting the activities such that some activities can be executed concurrently, the workflow having a corresponding electronically- stored representation of a service level agreement (SLA), the SLA comprising a set of rules governing execution of the workflow;

- analyzing the workflow to identify sub-workflows that can be executed independently, a sub-workflow comprising a set of one or more of the activities each connected on a path of execution of the workflow;

- obtaining information about a plurality of online service providers, each online service provider comprising one or more computers that together provide an online service;

- selecting different service providers among the providers able to perform the sub-workflows, respectively, where the service providers are selected based on criteria concerning the access time rapidity as applied to the information about the online service providers; and

- transmitting the sub-workflows via a network to the corresponding online service providers to execute the sub-workflows

SHORT DESCRIPTION OF THE FIGURES

[00019] Other features, details and advantages of the invention will become apparent upon reading the description which follows with reference to the appended figures, which illustrate:

- Fig. 1 , illustrates the architecture of the stack of software constituting the server forming when executed by hardware processors and associated memories a PaaS SERVER - Fig. 2 represents the advantages of using the PaaS platform integrating Apprenda;

Fig. 3 represents the advantages of using the PaaS server for user.

- Fig. 4 represents where the APIs are integrated in the stack; - Fig. 5 represents the service components monitoring tools integrated in the PaaS.

DETAILED DESCRIPTION OF DIFFERENT EMBODIMENTS OF THE INVENTION

[00020] Many combinations may be contemplated without departing from the scope of the invention; one skilled in the art will select either one depending on economical, ergonomical, dimensional constraints or others which he/she will have to observe.

[00021] In the following we shall use the following terms the definition each of which is the following. [00022] A container is a class, a data structure, or an abstract data type (ADT) whose instances are collections of other objects. In other words, they store objects in an organized way that follows specific access rules. The size of the container depends on the number of objects (elements) it contains. Underlying (inherited) implementations of various container types may vary in size and complexity, and provide flexibility in choosing the right implementation for any given scenario.

[00023] According to an embodiment, as shown in fig. 1 , the present invention’s server is embedding Apprenda (2) into a fully managed PaaS stack, abstracting complex hybrid laaS away. In product development, the minimal viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future development. Gathering insights from an MVP is often less expansive than developing a product with more features, which increase costs and risk if the product fails, for example, due to incorrect assumptions. [00024] According to an embodiment as shown in figure 4, the starting position of the service design outline managed by Apprenda comprises;

- a Standard Apprenda functionality and roadmap based on Apprenda developments,

- the North Bound API comprise a Customer Service Management via SNOW (3)

(Apprenda Console functionality embedded),

- the South Bound API comprises laaS (AWS Managed Public Cloud) (4) embedded in the Managed Apprenda service.

[00025] Containers can be characterized by the following three properties: - access, that is the way of accessing the objects of the container. In the case of arrays, access is done with the array index. In the case of stacks, access is done according to the LIFO (last in, first out) order and in the case of queues it is done according to the FIFO (first in, first out) order;

- storage, that is the way of storing the objects of the container; - traversal, that is the way of traversing the objects of the container.

[00026] Container classes are expected to implement methods to do the following:

- create an empty container (constructor);

- insert objects into the container; - delete objects from the container;

- delete all the objects in the container (clear);

- access the objects in the container;

- access the number of objects in the container (count).

[00027] Apprenda (2) is a full-service enterprise PaaS stack for .NET and Java applications. Specifically, Apprenda (2) is a "PaaS engine" that can be layered atop any arbitrary infrastructure composed of Windows and Linux OS instances. Apprenda (2) stitches these OS instances into a cross-platform single fabric that is a web- and API-accessible self-service cloud computing platform. Apprenda accepts as guest applications any mission-critical multi-tier .NET and Java applications composed of web services, front ends, and databases (e.g. SQL Server, Oracle).

[00028] Dialog Session or RDP is a session in which a measurement is executed.

[00029] Agent is a Software component installed on Workstation or Server to monitor application traffic and report back to central infrastructure.

[00030] More particularly, according to an embodiment illustrated by fig. 1 , the PaaS server (1 ) comprises at least one or several of the following services in a container-based architecture: at least a cloud service processing module (3) (ServiceNow) representing a first layer, executed on at least a processor of a platform configured to parse and orchestrate a cloud service requested to consume from the cloud service user request, to select the cloud computing services and/or resources provided by the cloud service provider and/or a function mode, execute a cloud service operation and make end to end management in the cloud through dialog with a second layer of Apprenda (2) integrated software for application transformation and a third layer of other integrated softwares for infrastructure brockering with the public cloud AWS (4) managed by the integrated softwares such as AWS for a public cloud.

[00031] ServiceNow (3) can comprise:

• a portal module

• a catalogue and process orchestration module for orchestrating several requests (APP1 , APP2; figure 2) on several server instances with a data protection management functionality, configured to store the information of cloud computing services and/or resources;

• a monitoring management module, configured to monitor a running status of the cloud service; • a service level management module providing an interface for determining any of the following parameters:

o time window for support availability,

o time window for incident handling depending on priority,

o time window for change handling,

o virtual server size,

o physical server size,

o initial and minimal storage size,

o data recovery parameter such as RPO recovery point objective, or RTO recovery time objectiveService Level.

• a catalogue and process orchestration module for orchestrating several requests on several server instances with a data protection management functionality, configured to store the information of cloud computing services and/or resources.

[00032] ServiceNow (3) may be configured to:

• receiving a workflow, the workflow defining a flow of discrete activities and paths of execution connecting the activities such that some activities can be executed concurrently, the workflow having a corresponding electronically-stored representation of a service level agreement (SLA), the SLA comprising a set of rules governing execution of the workflow;

• analyzing the workflow to identify sub-workflows that can be executed independently, a sub-workflow comprising a set of one or more of the activities each connected on a path of execution of the workflow;

• obtaining information about a plurality of online service providers, each online service provider comprising one or more computers that together provide an online service;

• selecting different service providers among the providers able to perform the sub-workflows, respectively, where the service providers are selected based on criteria concerning the access time rapidity as applied to the information about the online service providers; and

• transmitting the sub-workflows via a network to the corresponding online service providers to execute the sub-workflows. [00033] As shown on figure 1 , the server platform is comprising at least a processor and memories to save data and executable softwares so as to embed Apprenda software into a fully managed PaaS stack, abstracting complex hybrid laaS away.

[00034] First layer represents a service software (SNOW) (3) executed on at least a processor of a platform to orchestrate services on behalf of a customer and make end to end management in the cloud through dialog with a second layer of Apprenda integrated software for application transformation and a third layer of other integrated softwares for infrastructure brockering with the public cloud managed by the integrated softwares such as AWS for a public cloud.

[00035] The ServiceNow (SNOW) (3) layer of the stack is adapted to Apprenda software.

[00036] This last layer of Apprenda (2) is adapted and embedded in an AWS laaS (infrastructure as a Software) (4).

[00037] As shown on figure 4 SNOW operated on the server and displayed on a console is adapted to Apprenda by integrating a specific API configured to interface SNOW language and command to the language and command of Apprenda.

[00038] A second specific API configured to interface with the AWS laaS to transform the language and command generated by Apprenda in language and command adapted to laaS language and command.

[00039] From Standard Apprenda functionality and roadmap based on Apprenda developments a North Bound API:

• Customer Service Management via SNOW (Apprenda Console functionality embedded) was developed.

• South Bound API: Atos laaS (AWS Managed Public Cloud) is embedded in the Managed Apprenda service

• When Full stack: SNOW- Apprenda - OS management - laaS - Network is managed

• The stack is Deployed and configured to constitute a PaaS platform on physical/virtual servers. [00040] With the Service Now module (3) the server is Driving Migration to the

Cloud to:

- Improve the efficiency and deployment speed of new applications for the cloud - Monitor Performance across cloud deployments

- Identify where your applications perform best in the public cloud.

- Improve and fine tune the performance of your own SaaS applications

- Generate Fault domain isolation including identifying problems with 3rd parties

[00041] Application Monitoring from the cloud uses agents deployed and managed from either public cloud clusters to monitor the end to end performance of all user actions from the end user to the application server whether they are hosted in the public cloud. Application Monitoring from the cloud delivers full stack monitoring capabilities providing full insights into customer experience, application performance management, and infrastructure monitoring— including servers, containers, and cloud— end-to- end with no blind spots.

[00042] Using PaaS, reduce the process complexity and time to market, by bypass tedious, manual processes. The platform enforces policy and security automatically. Indeed, for example, the application completed and ready to deploy is directly tested and configured to the external monitoring, then release the application to the user, and finally a document release notes and prepare change management. [00043] According to an embodiment, as shown in fig. 2, each application or

API comprises a user interface, a business logic and a Data and all applications are managed by a unique Apprenda platform (2). Contrarily to the prior art, in which an application without using Paas, comprises several services of multitenancy, security, metering or authentication. This configuration of the present invention allows not to worries to the Developers about the difficulties or time consuming or costly issues, because all applications inherit the Apprenda cloud platform characteristics which simplify more the management of the platform.

[00044] Finally, as shown also on figure 3, all applications inherit the Apprenda cloud platform characteristics such as security, multitenancy, authentication, HA/scalability, metering. This configuration allows to increase number of applications per OS, optimize or displace VMs, and reduce parameters of servers (including maintenance and licensing). Without PaaS, all application is used slowly, inefficiently, costly and unnecessary. Thus, using PaaS allows a more efficient of the resources usage.

[00045] Moreover, the resource usage is more efficient with Paas enabling in a container-based architecture shown on figure 3 several applications to run.

[00046] According to an embodiment, an overall technical architecture of the service including monitoring is represented in figure 5. Several services are managed by a ATF Service/System Management Components, such as: Portal and Authentication, Ticket & Kowledge Management, Event Management, Catalog, Configuration & Master Data Management, Evanios, ServiceNow Discovery, Process Orchestration, Apprenda Application, “ATF classic” reporting, reporting, Evanios / ServiceNow AWS Application and MID Server. The others services are managed by a specific component in AWS MPaaS, such as: Apprenda Paas, AWS/EC2 and the CloudWatch.

[00047] The present invention allows to create a simple best in class managed PaaS usage model. Indeed, running, maintaining and operating an enterprise PaaS to ensure that all of the consumer benefits are realized is a complex thing to do and something that will slow the time to become productive. In addition, the business value of an enterprise PaaS is not in the running of it but in the consumption of it. Just consume and focus on the benefits derived from developing and running modern application services: - benefit from the Migration Services and Enterprise Service Levels and integrated Service Management

- simply use embedded Infrastructure as landing place for the applications based on your policies - support the full Application lifecycle for new and existing apps, including transformation

- policy driven, control an increasingly complex hybrid laaS environment

- powerful and flexible out-of-the-box capabilities with a composable service add-on model - align IT with business innovation goals, providing a competitive edge in a software-driven world.

[00048] It will be easily understood upon reading the present application that the particularities of the present invention, as generally described and illustrated in the figures, may be arranged and designed according to a great variety of different configurations. Thus, the description of the present invention and the related figures are not provided for limiting the scope of the invention but simply illustrating selected embodiments.

[00049] One skilled in the art will understand that the technical features of a given embodiment may in fact be combined with features of another embodiment unless the opposite is explicitly mentioned or if it is obvious that these features are incompatible. Further, the technical features described in a given embodiment may be isolated from the other features of this embodiment unless the opposite is explicitly mentioned.

[00050] It should be obvious for persons skilled in the art that the present invention allows embodiments under many other specific forms without departing from the field defined by the scope of the appended claims, these embodiments should be considered as an illustration and the invention should not be limited to the details given above.

Claims

1. A Server for managed PaaS (1 ) comprising in a container-based architecture at least a processor and memories to save data and executable softwares so as to embed Apprenda software (2) into a fully managed PaaS stack, abstracting complex hybrid laaS away, said server also comprising at least one or several of the following services: at least a cloud service processing module (3) (ServiceNow) representing a first layer, executed on at least a processor of a platform configured to:

- parse and orchestrate a cloud service requested to consume from the cloud service user request,

- to select the cloud computing services and/or resources provided by the cloud service provider and/or a function mode,

- execute a cloud service operation, and make end to end management in the cloud through dialog

- with a second layer of Apprenda integrated software for application transformation and

- a third layer of other integrated softwares for infrastructure brockering with the public cloud AWS (4) managed by the integrated softwares such as AWS for a public cloud.

2. A server according claim 1 wherein the at least a cloud service processing module (ServiceNow) is executed on the server and displayed on a console adapted to Apprenda by integrating a specific API configured to interface ServiceNow language and command to the language and command of Apprenda.

3. A server according one of claim 1 to 2 wherein a second specific API is configured to interface with the AWS laaS to transform the language and command generated by Apprenda in language and command adapted to laaS language and command.

4. A server according one of claim 1 to 3 wherein ServiceNow comprises: • a portal module

o time window for support availability,

o time window for incident handling depending on priority,

o time window for change handling,

o virtual server size,

o physical server size,

o initial and minimal storage size,

o data recovery parameter such as RPO recovery point objective, or RTO recovery time objective Service Level

5. A server according one of claim 1 to 4 wherein ServiceNow is configured

• receiving a workflow, the workflow defining a flow of discrete activities and paths of execution connecting the activities such that some activities can be executed concurrently, the workflow having a corresponding electronically-stored representation of a service level agreement (SLA), the SLA comprising a set of rules governing execution of the workflow; • analyzing the workflow to identify sub-workflows that can be executed independently, a sub-workflow comprising a set of one or more of the activities each connected on a path of execution of the workflow;

• transmitting the sub-workflows via a network to the corresponding online service providers to execute the sub-workflows.