KR20210116005A - Cloud-based platform building system and application service providing method - Google Patents

Abstract

Disclosed are a cloud-based platform building system and an application service provision method. According to an embodiment of the present invention, a cloud-based platform building system includes: an infrastructure control and management module which manages a lifecycle of large-scale distributed services and provides integrated services for managing release and distribution services; an execution environment module which provides an application platform for application development and distribution, execution and operation management; an operating environment module which provides infrastructure control and interworking and management services for the application platform; a development environment module which provides a portal and a development tool for developing, distributing and operating the application; and a service environment module which provides API management service when the application is executed. Therefore, the present invention can provide convenience to PaaS users and support to smoothly perform the application development.

Description

Cloud-based platform building system and application service providing method

The present invention relates to a cloud-based platform building system and a method for providing an application service.

Cloud computing is a technology that integrates and provides resources of computers in different physical locations with virtualization technology, and corresponds to a user-centered computer environment.

Cloud computing technology can be largely divided into IaaS (Infrastructure as a Service), PaaS (Platform as a Service), and SaaS (Software as a Service). SaaS refers to application services operated in a cloud environment. IaaS refers to a service that can borrow data center resources such as servers and storage through the Internet. PaaS is a service that provides a platform necessary for developing software services.

PaaS service users develop and distribute new applications by receiving platforms and services related to development, testing, distribution and hosting.

Korean Patent Laid-Open Patent No. 10-2016-0000604 (published on Jan. 5, 2016) - Development tool distribution method using GPU virtualization technique in PaaS cloud system

An object of the present invention is to provide a cloud-based platform building system and an application service providing method in which a solution architecture for building a cloud-based platform is defined, and a technology structure analyzed and designed to meet the cloud platform requirements is provided. .

An object of the present invention is to provide a cloud-based platform building system and an application service providing method that can provide convenience to PaaS users by building a cloud platform (application platform) and support to smoothly perform application development.

Objects other than the present invention will be easily understood through the following description.

According to one aspect of the present invention, there is provided a cloud-based platform building system, comprising: an infrastructure control and management module for managing the lifecycle of large-scale distributed services and providing an integrated service for managing release and distribution services; an execution environment module that provides an application platform for application development and distribution, execution and operation management; an operating environment module that provides infrastructure control and interworking and management services for the application platform; a development environment module that provides a portal and a development tool for developing, distributing and operating the application; And there is provided a cloud-based platform building system comprising a service environment module that provides an API management service when the application is executed.

The execution environment module provides an application platform configured based on a cloud foundry open source, the application platform comprising: a router for routing user request traffic to a destination; a receptor for receiving task and target LRP requests and providing status information on currently running tasks and LRP instances; a route emitter that monitors the actual LRP status from the receptor, and sends a route information registration/release request message to the router when a change occurs compared to the target LRP; a cloud controller that provides an API for application staging and execution; a CC bridge that communicates with the cloud controller and converts the application-specific message of the cloud controller into a general task and an LRP and delivers it to the receptor; a BBS that uses a distributed key value storage message service and encodes communication information; an intermediary unit representing a cell and performing a predetermined service through the BBS; an executor providing an HTTP API for container creation, action execution, and deletion; Garden, which provides platform-independent server and client interfaces for managing garden containers; an app lifecycle module that provides a binary for managing the lifecycle of the application; an auctioneer module for storing auctions for the task and the actual LRP instance; a converger for performing actions to ensure eventual consistency and fault tolerance between the task and the LRP; It may include one or more of the service brokers that create a service instance for a service used in conjunction with the application execution.

The CC bridge includes: a stager that receives a staging request from the cloud controller, converts it into a general task, and makes a request to the receptor; An N-Sync module for generating, updating, and deleting a target LRP through the receptor in response to a request for an application state; A TPS for providing information about the currently running LRP to the cloud controller; and at least one of a file server that converts a simple HTTP POST request of the executor into a multipart-form upload of the cloud controller.

The intermediary unit may check whether the task and the actual LRP information of the BBS match the container actually being in the cell, and keep the cell present in the BBS.

Alternatively, when a specific cell fails, the intermediary causes the converger to automatically transfer the corresponding instance to another cell, participates in an auction to receive a task or LRP, and executes the task or the LRP at the request of the executor. You can create a container and execute an action to be performed within the container.

The app lifecycle module may include: a builder performing staging of the application; a launcher for executing the application; It may include one or more binaries of a health check unit that performs a status check of the application running in the container.

Meanwhile, according to another aspect of the present invention, there is provided a method for providing an application service of a cloud-based platform built in a cloud-based platform construction system, the method comprising: generating an application service; and binding the application service, wherein the generating of the application service includes: a PaaS user requesting a service creation to a router; forwarding, by the router, a service creation API request to a cloud controller; requesting, by the cloud controller, provisioning to a service broker; creating, by the service broker, a service instance; The cloud controller may include storing the generated service information in a cloud controller database and then replying, and the binding of the application service may include: the PaaS user requesting service binding to the router; forwarding, by the router, a service binding API request to the cloud controller; requesting, by the cloud controller, binding to the service broker; returning, by the service broker, credential information of the service instance; There is provided an application service providing method of a cloud-based platform, comprising the step of storing the service credential information generated by the cloud controller in a cloud controller database and then replying.

generating and uploading an application for storing the distribution target application binary in the server and storing the application information in metadata; a distribution staging step of packaging the distribution target application binary into a single binary set capable of independent execution; And it may further include a deployment execution step of running the droplet generated in the deployment staging step according to the instance type and number requested by the PaaS user, and running a container and providing a service.

The step of creating and uploading the application may include: requesting, by the PaaS user, to create an application; forwarding, by the router, an application creation API request to the cloud controller; storing, by the cloud controller, application information in the cloud controller database; requesting the PaaS user to store the application; forwarding, by the router, an application storage API request to the cloud controller; The cloud controller may include storing the application source and the binary in a file storage.

The distribution staging step may include: requesting the PaaS user to start an application; forwarding, by the router, an application start API request to the cloud controller; checking, by the cloud controller, an application droplet creation state in the cloud controller database; requesting, by the cloud controller, execution of application staging to the CC bridge; generating, by the CC bridge, a task for performing staging and requesting it from a receptor; requesting the BBS after the receptor changes the requested task to a pending state; storing the task information in the distributed key value storage by the BBS and requesting the auction house module; selecting, by the auctioneer module, an optimal cell for performing the task by requesting and receiving the information on the running cell from the BBS, requesting an available resource for each cell, and performing an auction on the task based on the request; requesting, by the auctioneer module, a task processing unit to an intermediary corresponding to a cell transferred through an auction; converting the task into an action by the mediation unit and requesting an executor; requesting, by the executor, to create a garden container and perform an action according to an action request specified in the task; after the garden container performs application staging according to the procedure requested as the action, requesting the execution result droplet to the CC bridge and storing it in the file storage; The intermediary may include transmitting the task execution result to the receptor, and the receptor transmitting the task execution result to the cloud controller through the CC bridge.

The distribution execution step may include: requesting, by the cloud controller, execution of a staging application to the CC bridge; generating, by the CC bridge, a target LRP for application execution and requesting the receptor; changing the status of the requested LRP by the receptor and making a request to the BBS; storing the LRP information in the distributed key value storage by the BBS and requesting the auction house module; selecting, by the auctioneer module, an optimal cell for performing the task by requesting and receiving the information on the running cell from the BBS, requesting an available resource for each cell, and performing an auction on the task based on the request; requesting, by the auctioneer module, LRP processing to an intermediary unit corresponding to a cell transformed through an auction; changing the BBS information for the requested LRP to a claim state by the intermediary unit, converting the LRP into an action, and requesting the executor; requesting, by the executor, to create a garden container according to a specified action request; It may include the step of the garden container downloading the droplet from the cloud controller according to the requested procedure as the action, and then executing the application.

Other aspects, features and advantages other than those described above will become apparent from the following drawings, claims, and detailed description of the invention.

According to an embodiment of the present invention, a solution architecture for building a cloud-based platform is defined, and there is an effect that a technology structure designed and analyzed to meet the cloud platform requirements can be provided.

By defining a solution architecture for building a cloud-based platform and providing the corresponding technical structure, it is possible to build a cloud platform (application platform) to provide convenience to PaaS users and support smooth application development.

1 is a view showing a business context model of a cloud-based platform building system according to an embodiment of the present invention;
2 is a view showing an application platform component of a cloud-based platform building system according to an embodiment of the present invention;
3 is a view showing an application platform service access execution procedure of a cloud-based platform building system according to an embodiment of the present invention;
4 is a view showing an application service creation and binding procedure of a cloud-based platform building system according to an embodiment of the present invention;
5 is a view showing an application creation and upload procedure of a cloud-based platform building system according to an embodiment of the present invention;
6 is a diagram showing an application distribution (staging step) procedure;
7 is a diagram showing an application distribution (execution step) procedure;
8 is a view showing a procedure for performing automatic recovery of an application instance failure of a cloud-based platform building system according to an embodiment of the present invention;
9 is a view showing a cloud controller data model of a cloud-based platform building system according to an embodiment of the present invention;
10 is a view showing a service architecture related to a service environment of a cloud-based platform building system according to an embodiment of the present invention;
11 is a diagram illustrating a service broker API architecture;
12 is a diagram showing the API platform architecture;
13 is a view showing a platform interworking plug-in architecture related to a development environment of a cloud-based platform building system according to an embodiment of the present invention;
14 is a view showing an administrator dashboard architecture related to the operating environment of the cloud-based platform building system according to an embodiment of the present invention;
15 is a diagram illustrating a Bosch architecture related to an infrastructure control and management environment of a cloud-based platform building system according to an embodiment of the present invention.

Since the present invention can have various changes and can have various embodiments, specific embodiments are illustrated in the drawings and described in detail. However, this is not intended to limit the present invention to specific embodiments, and it should be understood to include all modifications, equivalents and substitutes included in the spirit and scope of the present invention.

When a component is referred to as being “connected” or “connected” to another component, it is understood that the other component may be directly connected or connected to the other component, but other components may exist in between. it should be On the other hand, when it is said that a certain element is "directly connected" or "directly connected" to another element, it should be understood that no other element is present in the middle.

Terms such as first, second, etc. may be used to describe various elements, but the elements should not be limited by the terms. The above terms are used only for the purpose of distinguishing one component from another.

The terms used herein are used only to describe specific embodiments, and are not intended to limit the present invention. The singular expression includes the plural expression unless the context clearly dictates otherwise. In this specification, terms such as "comprises" or "have" are intended to designate that the features, numbers, steps, operations, components, parts, or combinations thereof described in the specification exist, but one or more other features It should be understood that this does not preclude the existence or addition of numbers, steps, operations, components, parts, or combinations thereof.

In addition, the components of the embodiment described with reference to each drawing are not limitedly applied only to the embodiment, and may be implemented to be included in other embodiments within the scope of maintaining the technical spirit of the present invention, and also Even if the description is omitted, it is natural that a plurality of embodiments may be re-implemented as a single integrated embodiment.

In addition, in the description with reference to the accompanying drawings, the same components regardless of the reference numerals are given the same or related reference numerals, and the overlapping description thereof will be omitted. In describing the present invention, if it is determined that a detailed description of a related known technology may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. In the drawings attached to this specification, colors are given to help distinguish the components. However, even the same component may have different colors in the perspective view and the cross-sectional view. In addition, the same or similar color may be assigned to different components.

In addition, terms such as “…unit”, “…unit”, “…module”, “…group”, etc. described in the specification mean a unit that processes at least one function or operation, which is hardware or software or hardware and software. It can be implemented by combining

1 is a diagram illustrating a business context model of a cloud-based platform building system according to an embodiment of the present invention.

A cloud-based platform (cloud platform) is a cloud computing service that supports the development and operation of web applications without the complexity of infrastructure construction and maintenance required for application development and operation.

The cloud platform is built and operated based on infrastructure services (IaaS). For example, application services are provided to end users through distribution and execution of application applications developed in various languages such as Java, Ruby, Phyton, PHP, and Go.

The infrastructure control and management environment of the cloud platform excludes dependencies on infrastructure services, and supports various infrastructure services such as AWS, OpenStack, and VMWare, for example.

Cloud platform users can provide application services to end users by simply requesting deployment and execution of application applications through the development environment instead of complex control and management of infrastructure services.

The cloud platform supports connection with various external backend platform services such as RDBMS, NoSQL, and messaging services when running applications.

The cloud platform operating environment enables PaaS administrators to perform resource monitoring and control of the entire cloud platform.

Referring to FIG. 1 , the cloud-based platform building system 10 includes an infrastructure control and management module 11 , an execution environment module 12 , a development environment module 14 , a service environment module 13 , and an operating environment module 15 . ) may be included.

The infrastructure control and management module 11 manages the lifecycle of distributed services of a large scale, and provides an integrated service for managing release and deployment services. This service can provide interworking with various cloud infrastructures.

The execution environment module 12 provides services for application development and distribution, and execution/operation management. This service can provide a container for application execution by supporting various language packs such as Java, PHP, Ruby, and Go, for example. And in connection with the service environment module 13, it is possible to support the use of PaaS internal and external services such as a database and message queue.

In addition, it is possible to provide account registration and access authentication for using PaaS functions, permission management to control APIs or controllable resources that can be used after authentication, and access management services for accessing applications.

The operating environment module 15 provides management services for infrastructure control and interworking and application platforms. It can provide an operation dashboard for administrators, a monitoring dashboard for individual tenants and administrators, log management, and metering plug-in services.

The development environment module 14 provides a self-service portal and development tools for developing, deploying, and operating application applications by utilizing the PaaS platform.

The service environment module 13 provides an external service broker for linking with various external back-end platform services such as RDBMS, NoSQL, and messaging services when executing application applications, and can provide API management services for managing and linking internal and external APIs. .

2 is a diagram illustrating an application platform component of a cloud-based platform building system according to an embodiment of the present invention.

The application platform corresponds to the execution environment module 12 and provides API services for distributing, managing, and monitoring the application by interacting with the user portal, the development tool, and the management portal. In addition, it is possible to provide an external API service by providing API management for an application application distributed on the application platform, or provide an API service of the application application to the outside. The application platform is operated and managed based on sub-infrastructure control and management components that support various types of IaaS and perform resource management.

Referring to FIG. 2 , the application platform may be configured based on a Cloud Foundry (CF) open source.

The router 21 serves to route user request traffic to a destination. The main destination is the cloud controller 23 or the garden container 34 running the application. The router information of the router 21 receives the application instance information serviced by the backend execution unit 30 (eg, Diego) from the receptor 31 and passes through the route emitter 22 . get updated The router 21 and the route emitter 22 may be implemented as an integrated module.

The route emitter 22 monitors the actual LRP (Long-Running Processes) status from the receptor 31, and compares it with the target LRP (Desired LRP) when a change occurs, the router 21 ) to send route information registration/removal request message. In addition, it periodically sends the entire routing table to the router 21 .

The cloud controller 23 provides an API for staging and executing the application. It is in charge of overall management of the application, such as build pack selection, service and binding, and access authorization processing.

When a developer transmits an application to the cloud foundry through a command line interface (CLI), the cloud controller 23 receives it. The cloud controller 23 stores the application binary, creates an application metadata record, and communicates with the backend execution unit 30 to instruct stage state preparation and application execution. The cloud controller 23 may maintain a database for maintaining information such as an organization, a space, a service, a service instance, and a user role for a service, and a file storage (Blobstore) for storing application codes and build packs.

The CC bridge (CC-Bridge) 24 communicates with the cloud controller 23 , and converts the application-specific message of the cloud controller 23 into a general task (Task) and LRP and delivers the mediation role to the receptor 31 . is responsible for

The CC bridge 24 may include the following four sub-modules (Stager, Nsync module, TPS and File-Server).

The stager receives a staging request from the cloud controller 23 , converts it into a general task, and requests the receptor 31 . By instructing the cell of the backend execution unit 30 through the task action, the platform-specific binary is injected during the actual staging process. When the task is completed, the result is transmitted to the cloud controller 23 .

The Nsync module (Nsync) may generate, update, or delete a target LRP through the receptor 31 in response to a request for an application state. In addition, it is possible to periodically request the cloud controller 23 to compare the overall target state of the application with the target state (the Diego target state) of the backend execution unit 30 and maintain the same.

The TPS provides information about the currently running LRP to the cloud controller 23 . The cloud controller 23 can use this information to respond to "cf apps" and "cf app X" requests.

The file server (File-Server) serves to convert a simple HTTP POST request of the executor 33 into a multipart-form upload of the cloud controller 23 . It serves static resources used by multiple components, and in particular can provide binaries of the application life cycle.

The authentication management module (UAA) 25 operates as an authentication server (eg, OAuth2 server) and a login server to provide user authentication management.

The receptor 31 may receive the task and target LRP request, and may provide the currently running task and LRP instance status information to the Diego client.

The intermediary unit (Rep) 32 represents a cell and performs various services through the BBS (40). For example, it is possible to check whether the task and actual LRP information of the BBS 40 matches the container that is actually in the cell, and maintain the cell in the BBS 40 to exist. When a specific cell fails, the converger 53 may automatically transfer the corresponding instance to another cell. In addition, it participates in an auction to receive the task/LRP, and the executor 33 requests and executes the task/LRP to create a container and execute an action to be performed in the container.

The executor 33 may provide an HTTP API for creating a container, performing an action within the container, and deleting the container. It does not distinguish between tasks and LRPs, and an action API for performing actions can be implemented. The executor 33 transmits streams (Stdout and Stderr streams) related to output and error messages to the Metron-agent running in the cell, and the corresponding streams can be delivered to the Loggregator. .

Garden 34 may provide a platform independent server and client interface for garden container management. Interfaces can define methods for performing actions. Actions for which methods are defined include creating and deleting containers, applying resource constraints of containers, connecting and developing network ports to containers, copying files into and out of containers, running processes in containers and handling Stdout and Stderr data streaming, arbitrary meta of containers This can include creating snapshots of data, containers for redistribution without downtime, and so on.

The App Lifecycle module 35 provides three binaries: Builder, Launcher, and Healthcheck for managing the lifecycle of an application (CF application) to be executed in the Cloud Foundry. can do.

The builder can perform the staging of the CF application. The CC bridge 24 requests a staging request as a task, and the builder can perform code correction analysis and necessary pre-work before running the application.

The launcher can run CF applications. The CC bridge 24 requests the application target LRP as an action, and the launcher may perform a user-specified system environment setting and start command.

The health check unit may perform a status check of the CF application running in the container. CC bridge 24 may add a monitoring action for health check to the application target LRP.

The auctioneer module (Auctioneer) 51 stores auctions for tasks and actual LRP instances. The auction between the auction house module 51 and the intermediary unit 32 of the cell may be communicated through HTTP.

Converger 53 is a part for ensuring eventual consistency and fault tolerance between the task and the LRP. When adjusting the LRP, the converger 53 may perform necessary actions to match the target LRP and the actual LRP state. If there are not enough instances, a start auction is sent. If the instance is exceeded, it sends a stop message to the intermediary 32 of the cell hosting the instance.

The metrics server (Metrics-Server) 54 reads metrics from the BBS 40 and transmits them to Doppler.

The auction module (Auction) 52 stores detailed information on the action during the auction. The auctioneer module 51 and the intermediary 32 may use the auction package to participate in the auction. It may include simulation tests to verify the accuracy and performance of the algorithm.

The BBS 40 uses a distributed key-value storage (Etcd) message service, and can encode communication information between the components (Diego component) of the backend execution unit 30 and Etcd. The receptor 31 , the mediator 32 , and the converger 53 can be used.

Service Brokers can create service instances for services that are used in conjunction with application execution such as message queues and databases. A company that provides services in the form of SaaS needs to implement a service broker and provide it as a server to provide services to applications.

The Buildpacks module detects languages and frameworks, downloads necessary libraries, compiles the source code into an executable file, and can create buildpacks together with the runtime environment.

NATS is a system that supports the distributed message queue of the Pub-Sub pattern, and can be used for communication between Cloud Foundry components.

Doppler can provide application logs to developers as a stream. Metron can deliver application log and application/diego metric information to Doppler.

The cloud-based platform building system according to the present embodiment may perform an application service providing method, and hereinafter, an application platform service access execution procedure, an application service creation and binding procedure, an application creation and upload procedure, which are included in the application service providing method, An application distribution (staging step) procedure and an application distribution (execution step) procedure will be described with reference to related drawings.

3 is a diagram illustrating an application platform service access execution procedure of a cloud-based platform building system according to an embodiment of the present invention.

There are two main types of access to application platform services: when application developers access CLI (Command Line Interface) and web console for development and operation in PaaS, and general users (end-users, service users) provide services in PaaS It is divided into the case of accessing the application in progress. In both cases, the internal processing procedure of the application platform is as follows.

First, the case where the service user accesses the application is as follows. The user requests the application access URL to the router 21 (①). The router 21 forwards the request to the application in the garden container 34 in which the application mapped to the request domain is placed (②).

Next, PaaS users develop and distribute applications as follows. The user requests an application management command to the router 21 (③). The router 21 forwards the application management command to the cloud controller 23 (④). The cloud controller 23 checks the user's authentication and authorization, and executes a request command.

4 is a diagram illustrating an application service creation and binding procedure of a cloud-based platform building system according to an embodiment of the present invention.

According to the cloud-based platform building system according to the present embodiment, services such as a database and message queue required for application operation can be created and bound to the application.

The application service creation procedure is as follows.

The user requests service creation to the router 21 (①). The router 21 forwards the API request to the cloud controller 23 (②). The cloud controller 23 requests provisioning to the service broker 63 (③). The service broker 63 creates a service instance 64 (④). The cloud controller 23 stores the generated service information (Dashboard URL, etc.) in the CCDB (cloud controller database) 61 and returns it (⑤).

The binding procedure to prepare for use in applications after service creation is as follows.

The user requests a service binding to the router 21 (⑥). The router 21 forwards the API request to the cloud controller 23 (⑦). The cloud controller 23 requests binding to the service broker 63 (⑧). The service broker 63 returns credential information of the service instance (⑨). The cloud controller 23 stores the generated service credential information in the CCDB 61 and returns it (⑩).

5 is a diagram illustrating an application creation and upload procedure of a cloud-based platform building system according to an embodiment of the present invention, FIG. 6 is a diagram illustrating an application distribution (staging step) procedure, and FIG. 7 is an application distribution (execution step) ) is a diagram showing the procedure.

According to the cloud-based platform building system according to the present embodiment, application distribution includes the steps of generating and uploading an application, staging distribution, and executing distribution.

In the step of creating and uploading an application, the distribution target application binary is stored in the server, and application information is stored in metadata.

The distribution staging step uses the binary of the target application and packages it into a single set of binaries that can independently execute the application, such as the development language, framework, middleware, and application dependency library. Cloud Foundry defines the final executable binary generated in the staging phase as a Droplet.

The deployment execution phase is a phase in which the droplet created in the staging phase is used to run containers and provide services according to the instance type and number requested by the user.

Referring to FIG. 5 , a creation procedure in application distribution is as follows.

A user requests to create an application (①). The router 21 forwards the API request to the cloud controller 23 (②). The cloud controller 23 stores the application information in the CCDB 61 (③).

The application upload procedure is as follows.

The user requests to save the application (④). The router 21 forwards the API request to the cloud controller 23 (⑤). The cloud controller 23 stores the application source/binary in the file storage (Blobstore) 62 (⑥).

Referring to FIG. 6 , the procedure of the application distribution staging step is as follows.

The user requests to start the application (①). The router 21 forwards the API request to the cloud controller 23 (②). The cloud controller 23 checks the application droplet creation state in the CCDB 61 (③). Since this is the first deployment, the application droplet has not been created.

The cloud controller 23 requests the CC bridge 24 to execute the application staging (④). The CC bridge 24 generates a task for performing staging and requests the receptor 31 (⑤). The receptor 31 requests the BBS 40 after changing the request task to a pending state (⑥). The BBS 40 stores the task information in the distributed key value storage (etcd) and requests the auction house module 51 (⑦).

The auctioneer module 51 requests and receives information on the running cell from the BBS 40, requests available resources for each cell, and conducts an auction for the task based on the request for optimal task performance. Select the cell of (⑧). The auctioneer module 51 requests task processing to the intermediary unit 32 corresponding to the cell selected through the auction (⑨).

After changing the BBS information for the requested task to the running state, the mediation unit 32 requests the executor 33 (⑩). The mediation unit 32 converts the task into an action and makes a request to the executor 33 .

The executor 33 requests to create a garden container and perform an action according to the action request specified in the task (⑪). After performing application staging according to the procedure requested as an action, the garden container 34 requests the CC bridge 24 for the execution result droplet and stores it in the cloud controller file storage 62 (⑫). The mediation unit 32 transmits the task execution result to the receptor 31, the receptor 31 transmits the execution result to the CC bridge 24 (particularly, the stager), and the stager transmits the execution result to the cloud controller 23 ( ⑬).

Referring to FIG. 7 , the procedure of the application distribution execution step is as follows.

The cloud controller 23 requests the CC bridge 24 to execute the staging application (①). CC bridge 24 generates a target LRP (Desired LRP) for application execution and requests the receptor 31 (②). The receptor 31 makes a request to the BBS 40 after changing the requested LRP to an ARP (Actual-Running Processes) state (③). The BBS 40 stores the LRP information in the distributed key value storage (etcd) and requests the auction house module 51 (④).

The auctioneer module 51 requests and receives information on the cell that is running from the BBS 40, requests the available resources for each cell, and conducts an auction for the task based on this to find the optimal cell for performing LRP Select (⑤). The auction company module 51 requests the LRP processing to the intermediary unit 32 corresponding to the cell selected through the auction (⑥).

The mediation unit 32 changes the BBS information for the requested LRP to the claimed state, and then requests the executor 33 (⑦). The mediation unit 32 converts the LRP into an action and makes a request to the executor 33 .

The executor 33 requests creation of a garden container according to the specified action request (⑧). The garden container 34 downloads the droplet from the cloud controller 23 according to the procedure requested as an action and then executes the application (⑨).

8 is a diagram illustrating a procedure for automatically recovering an application instance failure in a cloud-based platform building system according to an embodiment of the present invention.

In the automatic recovery of existing application instance failures, when the health manager detects the failure of the Droplet Execution Agent (DEA) of the cloud controller and requests the cloud controller to create a new container, the cloud controller commands the DEA to create a new It was a way to create a container and deploy an application to restore it.

In this embodiment, the converger 53 performs a function similar to that of the health manager, and directly requests a recovery command for a failure from the related component. The converger 53 may periodically review the target LRP, the running LRP, and the task to delete or update information about the task and LRP to be expired or adjusted as well as failover.

The procedure for performing application instance failure recovery is as follows.

The converger 53 collects task, target LRP, execution LRP information and actual running cell information from the BBS 40 periodically by a timer or when a cell change event of the BBS 40 occurs. (①).

If the task and LRP exceeding the standard time are not being processed, the completion or deletion or creation is processed with a standard time exceeded error message according to the status information (②).

When a container failure occurs and a number of instances smaller than the number of instances of the requested LRP are running, the auction house module 51 may be called to request LRP generation.

Alternatively, if a number of containers greater than the number of requested LRPs are being executed, the intermediary unit 32 may be called to request container stop.

Alternatively, when the task exceeds the reference time in the complete state, the callback URL of the receptor 31 may be called to complete the task execution and delete the corresponding task.

9 is a diagram illustrating a cloud controller data model of a cloud-based platform building system according to an embodiment of the present invention.

The application platform has respective data models for the cloud controller and the authentication management module (UAA), and may maintain file storage in the cloud controller.

The application platform user defines the top-level organization name of the tenant as a meta object. Define the space according to the application development environment requirements under the operation, and register the user with authority for each space and the domain for application access.

One application distributed on the application platform belongs to a specific space, can be linked with the service defined in the space, and can provide application services to users through the domain registered in the organization according to route settings.

The cloud controller can manage four file stores including resources (cc-resources), packages (cc-packages), drops (cc-droplets), and buildpacks (cc-buildpacks).

The cloud controller stores the resources of the application, that is, unpackaged upload files in the resource file storage. You can use the resource file store to skip uploading duplicate resources. When uploading an application's resource, first check whether the resource to be uploaded is in the resource file storage. Resources are stored in a file store with a SHA1 hash value for each resource. The first 4 digits of the hash value are used as the subdirectory PATH of the resource file storage, and the hash value is stored in that location as a file name without an extension.

The cloud controller stores the uploaded application file, that is, the file before the stage in the package file storage. Uploaded application files are bundled in package.zip and stored in the file storage through the GUID assigned to the application. GUID is automatically generated through the uuid() method of the SecureRandom module when the application is deployed. The first 4 digits of the GUID are used as the PATH sub-directory of the package file storage, and the GUID is stored in that location as a file name without extension.

The cloud controller makes the application executable through packaging and compilation, and it is stored in the droplet file storage. The staged application is bundled with droplet.tgz and stored in the file store through the GUID assigned to the application. GUID is used as the PATH sub-directory of the droplet file storage, and the SHA1 hash value of droplet.tgz is stored in that location as a file name without extension.

The cloud controller stores the system-provided admin buildpack and added or modified custom buildpacks in the buildpack file storage. Each fieldpack is stored in a file storage with a GUID and SHA1 hash value. Obtain the SHA1 hash value of the buildpack file, and use the first 4 digits of the GUID as the PATH subdirectory of the buildpack file storage. Save without extension with ‘GUID_hash value’ as the file name.

The node configuration of the application platform is affected by the installation method of the sub-infrastructure control and management (Bosh) module 11 .

In the case of the operating system, the application platform (cf_release) is distributed based on Bosh. In this case, a virtual machine (VM) for each individual component of the application platform can be allocated and configured to be redundant for high availability (HA).

In the case of development and unit test systems, the application platform can be deployed based on Bosh-lite, and in this case, the application platform can be deployed as multiple Warden containers on one virtual machine (VM).

10 is a diagram showing a service architecture related to a service environment of a cloud-based platform building system according to an embodiment of the present invention, FIG. 11 is a diagram showing a service broker API architecture, and FIG. 12 is a diagram showing an API platform architecture .

10 and 11 , a service pack architecture is illustrated in relation to a service environment.

The Cloud Foundry Service API defines the protocols (catalog, provision, deprovision, updateprovision, bind, unbind) between the cloud controller and the service broker. A broker can be implemented as a RESTful API in the form of an HTTP (or HTTPS) endpoint URI. One or more services may be provided by one broker, and may be provided with horizontal scalability to enable load balancing. Additionally, multiple Cloud Foundry instances can be supported by a single broker using different URL prefixes and credentials.

Referring to FIG. 12 , an API platform architecture is illustrated in relation to a service environment.

The API platform is a framework for managing APIs and supporting authentication processing to make common components a cloud service. You can manage/control/authenticate APIs in the API Manager, and collect/analyze statistics on API usage in the Business Activity Monitor (BAM). The data collected and analyzed by BAM is periodically stored in the MySQL database and can be checked in the statistics of the API manager.

As shown in FIG. 12, the API platform is divided into five areas. API manager registers and manages API, Publisher, API user checks API information and applies for use, Gateway applies various policies (SLA) when using API, API may include a key manager (Key Manager) that manages keys for using. BAM can collect and analyze events that occur in the API manager's gateway and store.

The API platform may be provided as a service in the Open PaaS platform. Therefore, the service pack architecture is configured for connection with the Open PaaS platform. The architecture for the API platform and service pack configuration can be included in the service pack technical architecture.

13 is a diagram illustrating a platform interworking plug-in architecture related to a development environment of a cloud-based platform building system according to an embodiment of the present invention.

Referring to FIG. 13 , the platform interworking plug-in is provided as a plug-in of the Eclipse IDE. The development environment is maintained using the existing Eclipse IDE, and the application being developed can be managed by interworking with the platform within the Eclipse IDE.

The platform interworking plug-in is implemented by extending the functions of WST (Web Standard Tool) and JST (J2EE Standard Tool), which are Eclipse IDE web development support plug-ins, and is linked with the execution environment using cf-java-client written in Java language.

The platform integration plug-in operates on the Eclipse platform as a plug-in (eclipse-integration-cloudfoundry) for interworking with Cloud Foundry through Eclipse. The Cloud Foundry Server is implemented so that the components provided by WST and JST can be extended to connect to the Cloud Foundry Server to manage applications. The Cloud Foundry Server has server connection information, not the actual server, and is synchronized with the organization and target space of the account authenticated through the server instance. , environment variables can be managed within Eclipse, and service pack instance management and binding functions in the target space are provided.

The components composing the platform interworking plug-in and the functions provided by each component are as follows.

The platform connection information management module creates platform server connection information composed of cloud controller URL, user authentication information, and target space information, and is expressed as a server instance in the platform interworking plug-in. Management functions for applications, service packs, environment variables, etc. in the target space can be provided through the server instance.

The application distribution module distributes the distributable web application project in the workspace of the Eclipse IDE to the set target space to run it on the platform. For application distribution, a web application project can be compressed into a web archive format, WAR (Web application archive) format, and uploaded through the cloud controller API.

The application management module provides a function to inquire the application distributed in the target space and to check and modify the application settings. You can control the number of instances, instance memory, and application status for horizontal expansion of the application, and you can check the service pack instance and instance list bound to the application.

The service pack instance management module provides the service pack instance management function in the target space. Inquires the list of service packs that can be created from the platform server, creates a service pack instance in the target space, and enables the application to use the service pack instance through binding and unbinding of the application and service pack instance.

The route management module provides a route management function for setting the application access URL. Select the public domain set in the platform and the private domain of the organization set by the organization administrator, configure the subdomain to configure and create route information, and map it to the application so that the application can be accessed through the set route.

The environment variable management module provides the management function of environment variables of the application. Environment variables consist of a pair of environment variable names and values, and the set environment variables are loaded and used while the application is running.

The instance logging module streams the log output from the application instance and outputs it to the Eclipse console view. As for the application instance, the list of instances for each application can be checked in the application management, and the log can be checked by selecting the instance from the list.

Eclipse operates on various platforms and was implemented for the purpose of a programming integrated development environment that supports various languages including Java. Currently, OSGi is introduced to provide a platform for general-purpose application software.

The basis of Eclipse is the Rich Client Platform (RCP), which consists of the following components.

- Core platform: the base of Eclipse running plugins

- OSGi: standard bundling framework

- SWT (Standard Widget Toolkit): Portable GUI widget toolkit

- JFace: support to simplify the task of configuring advanced components using SWT

- Eclipse Workebench: Consists of View, Editor, Perspective, and Wizard to provide an efficient GUI to enhance usability.

The Eclipse plug-in provides an extension point and can be implemented by extending the functionality of the plug-in by using other plug-ins. .

WST (Web Standard Tools) plug-in is a sub-project of the Eclipse Web Tools project and provides extensible tools that support testing and debugging in various server groups in web application development.

Server management tools, Internet properties, TCP/IP monitoring can be performed in Eclipse through WST plug-in, editor for web language (HTML, CSS, XML, Javascript) editing, SQL query editor, XML/DTD/XSD utility, etc. can be used

The platform interworking plug-in provides a server management instance for interworking with the cloud foundry server by extending the server runtime type, server type, and facet (project property) of WST.

JST (J2EE Standard Tools) plug-in is a sub-project of the Eclipse Web Tools project and provides extensible tools that support development, testing and debugging of J2EE applications for a wide range of J2EE server groups. Through this, it supports development, testing, and debugging of web applications, enterprise Java beans, and Java web services based on Eclipse.

The platform interworking plugin implements functions for interworking with the cloud foundry server by extending the runtime facet mapping of JST, classpath provider, and wizard (wizard).

The Cloud Foundry Client Library can be used in conjunction with Cloud Foundry's Cloud Controller REST API through the Java language, and interacts with the Cloud Foundry service in applications written in Groovy and Scala, including Java, a JVM-based language.

The platform interworking plugin implements GUI and logic for interworking with Cloud Foundry in Eclipse through the extension of WST and JST, and indirectly calls the REST API provided by the cloud controller through the Cloud Foundry client library to create applications and services within Eclipse. Provides management functions for pack instances.

14 is a diagram illustrating an architecture of an administrator dashboard related to an operating environment of a cloud-based platform building system according to an embodiment of the present invention.

The admin dashboard (admin-ui) inquires data from CCDB and UAADB, interacts through REST API calls provided by the cloud controller, and enables platform management in a web user interface environment.

The admin dashboard is a web application that allows you to manage data in Cloud Foundry through a web interface. It consists of a back-end application written in Ruby language and a front-end application that provides data and web user interface through AJAX communication through REST API provided by the back-end application.

When searching for data, the manager dashboard directly queries CCDB and UAADB to inquire data, and functions other than the query are handled by calling the REST API of the cloud controller.

After periodically reading UAADB user data and CCDB platform data (organization, space, application, service pack, service pack broker, service pack instance, route, domain, etc.) However, there are restrictions on real-time data inquiry due to scheduling tasks.

Cloud Foundry requires a database to collect usage statistics data, stores statistical data by defining columns for each data in the statistics table, and provides data through the statistics page of the administrator dashboard.

15 is a diagram illustrating a Bosch architecture related to an infrastructure control and management environment of a cloud-based platform building system according to an embodiment of the present invention.

Developed for cloud foundry management and deployment, BOSH is an open software for managing the lifecycle of deployment and service targeting large-scale distributed systems. It provides the ability to create virtual machines and install software for multiple IaaS environments. do.

BOSH is an abbreviation of Bosh Outter SHell. Systems related to BOSH distribution are called "Outter Shell", and on the other hand, systems deployed and managed by BOSH are called "Inner Shell". Definition and roles of major components of BOSH are as follows.

The Command Line Interface (CLI) is an operating tool that allows you to deploy services in the cloud or execute specific commands while interacting with the BOSH Director.

Director controls the life cycle of software and services as well as creation and deployment of virtual machines.

Health Monitor collects cloud status information from the agent. When a specific Alert is generated from the cloud, a Resurrector can be performed or a warning message can be transmitted through a Notification Plug-in.

The database is a Postgres database used by the director and stores meta information of Stemcell / Release / Deployment required for deployment.

The file storage (Blobstore) is used as a place to store release information (in addition to the Compiled Image of BOSH Package, self-made S/W Packages). These releases are uploaded by the CLI and stored in a file repository by the Director. When the operator distributes, the agent brings the job specified in the currently set release and package information related to the job from the file repository.

The agent is installed on all virtual machines deployed in the cloud and plays a role in receiving and executing specific commands from the director. From the job specification (package to be installed and configuration method) information received from the director, the agent installs the designated package in the virtual machine according to the director's instructions, and sets the necessary configuration information.

The Message Bus (NATS) is a publish-subscribe message system for communication between a director and an agent, and is used to monitor virtual machines and perform specific commands.

The registry stores configuration information when a director creates or modifies a virtual machine. The stored registry information is used in the bootstrap stage of the virtual machine.

The above-described cloud-based platform building method and service providing method through the cloud-based platform may also be implemented in the form of a recording medium including instructions executable by a computer, such as an application or program module executed by a computer. Computer-readable media can be any available media that can be accessed by a computer and includes both volatile and nonvolatile media, removable and non-removable media. In addition, computer-readable media may include computer storage media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data.

The above-described cloud-based platform construction method and service provision method through the cloud-based platform may be executed by an application basically installed in the terminal (which may include a program included in the platform or operating system, etc., which is basically installed in the terminal) , may be executed by an application (ie, a program) directly installed in the master terminal by a user through an application providing server such as an application store server, an application, or a web server related to the corresponding service. In this sense, the above-described cloud-based platform construction method and service provision method through the cloud-based platform are implemented as an application (ie, program) installed by default in a terminal or directly installed by a user, and a computer-readable record such as a terminal may be recorded on the medium.

Although the above has been described with reference to the embodiments of the present invention, those of ordinary skill in the art can variously modify and change the present invention within the scope without departing from the spirit and scope of the present invention described in the claims below. You will understand that it can be done.

10: Cloud-based platform building system 11: Infrastructure control and management module
12: Execution environment module 13: Service environment module
14: development environment module 15: operating environment module
21: router 22: route emitter
23: Cloud Controller 24: CC Bridge
25: authentication management module 26: doppler
31: receptor 32: intermediary
33: Executor 34: Garden
35: App Lifecycle Module 36: Metron Module
40: BBS 41: Auctioneer Module
42: auction module 43: converger
44: Metric Server 61: CCDB
62: file store 63: service broker
64: service instance

Claims (11)

As a cloud-based platform building system,
an infrastructure control and management module that manages the lifecycle of large-scale distributed services and provides integrated services for managing release and distribution services;
an execution environment module that provides an application platform for application development and distribution, execution and operation management;
an operating environment module that provides infrastructure control and interworking and management services for the application platform;
a development environment module that provides a portal and a development tool for developing, distributing and operating the application; and
A cloud-based platform construction system including a service environment module that provides API management services when the application is executed.
According to claim 1,
The execution environment module provides an application platform configured based on cloud foundry open source,
The application platform is
a router for routing user request traffic to a destination;
a receptor for receiving task and target LRP requests and providing status information on currently running tasks and LRP instances;
a route emitter that monitors the actual LRP status from the receptor, and sends a route information registration/removal request message to the router when a change occurs compared to the target LRP;
a cloud controller that provides an API for application staging and execution;
a CC bridge that communicates with the cloud controller and converts the application-specific message of the cloud controller into a general task and an LRP and delivers it to the receptor;
a BBS that uses a distributed key value storage message service and encodes communication information;
an intermediary unit representing a cell and performing a predetermined service through the BBS;
an executor providing an HTTP API for container creation, action execution, and deletion;
Garden, which provides platform-independent server and client interfaces for managing garden containers;
an app lifecycle module that provides a binary for managing the lifecycle of the application;
an auctioneer module for storing auctions for the task and the actual LRP instance;
a converger for performing actions to ensure eventual consistency and fault tolerance between the task and the LRP;
Cloud-based platform building system, characterized in that it comprises one or more of the service brokers for creating a service instance for the service used in conjunction with the application execution.
3. The method of claim 2,
The CC bridge is
a stager receiving a staging request from the cloud controller, converting it into a general task, and requesting the receptor;
an n-sync module for generating, updating, and deleting the target LRP through the receptor in response to a request for the application state;
a TPS that provides information about the currently running LRP to the cloud controller;
and at least one of a file server for converting a simple HTTP POST request of the executor into a multipart-form upload of the cloud controller.
3. The method of claim 2,
The intermediary unit confirms that the task of the BBS and the actual LRP information match the container that is actually in the cell, and maintains the cell to exist in the BBS.
3. The method of claim 2,
When a specific cell fails, the intermediary causes the Converger to automatically transfer the instance to another cell, participates in an auction to receive a task or LRP, and executes the task or LRP at the request of the executor to execute the container A cloud-based platform building system, characterized in that it creates and executes an action to be performed in the container.
3. The method of claim 2,
The app lifecycle module is
a builder performing staging of the application;
a launcher for executing the application;
Cloud-based platform building system, characterized in that it includes one or more binaries of a health check unit for performing a status check of the application running in the container.
A method for providing application services of a cloud-based platform built in a cloud-based platform construction system, the method comprising:
creating an application service; and
Including binding the application service,
The step of creating the application service includes:
a PaaS user requesting service creation to a router;
forwarding, by the router, a service creation API request to a cloud controller;
requesting, by the cloud controller, provisioning to a service broker;
creating, by the service broker, a service instance;
The cloud controller includes the step of storing the generated service information in a cloud controller database and then replying;
The step of binding the application service includes:
requesting, by the PaaS user, a service binding to the router;
forwarding, by the router, a service binding API request to the cloud controller;
requesting, by the cloud controller, binding to the service broker;
returning, by the service broker, credential information of the service instance;
and storing the service credential information generated by the cloud controller in a cloud controller database and then replying.
8. The method of claim 7,
generating and uploading an application for storing the distribution target application binary in the server and storing the application information in metadata;
a distribution staging step of packaging the distribution target application binary into a single binary set capable of independent execution; and
The method of providing an application service of a cloud-based platform further comprising a distribution execution step of running a container according to the instance type and number requested by the PaaS user and providing the service using the droplet generated in the distribution staging step.
9. The method of claim 8,
The step of creating and uploading the application is,
requesting the PaaS user to create an application;
forwarding, by the router, an application creation API request to the cloud controller;
storing, by the cloud controller, application information in the cloud controller database;
requesting the PaaS user to store the application;
forwarding, by the router, an application storage API request to the cloud controller;
The method of providing an application service of a cloud-based platform comprising the step of the cloud controller storing an application source and a binary in a file storage.
10. The method of claim 9,
The distribution staging step is
requesting the PaaS user to start an application;
forwarding, by the router, an application start API request to the cloud controller;
checking, by the cloud controller, an application droplet creation state in the cloud controller database;
requesting, by the cloud controller, execution of application staging to the CC bridge;
generating, by the CC bridge, a task for performing staging and requesting it from a receptor;
requesting the BBS after the receptor changes the requested task to a pending state;
storing the task information in the distributed key value storage by the BBS and requesting the auction house module;
selecting, by the auctioneer module, the optimal cell for performing the task by requesting and receiving the information on the running cell from the BBS, requesting an available resource for each cell, and performing an auction on the task based on the request;
requesting, by the auctioneer module, a task processing unit to an intermediary corresponding to a cell transferred through an auction;
converting the task into an action by the mediation unit and requesting an executor;
requesting, by the executor, to create a garden container and perform an action according to an action request specified in the task;
after the garden container performs application staging according to the procedure requested as the action, requesting a droplet of the execution result to the CC bridge and storing it in the file storage;
and transmitting, by the intermediary unit, a task execution result to the receptor, and the receptor transmitting the task execution result to the cloud controller through the CC bridge.
11. The method of claim 10,
The distribution execution step is
requesting, by the cloud controller, to execute a staging application to the CC bridge;
generating, by the CC bridge, a target LRP for application execution and requesting the receptor;
changing the status of the requested LRP by the receptor and making a request to the BBS;
storing the LRP information in the distributed key value storage by the BBS and requesting the auction house module;
selecting, by the auctioneer module, the optimal cell for performing the task by requesting and receiving the information on the running cell from the BBS, requesting an available resource for each cell, and performing an auction on the task based on the request;
requesting, by the auctioneer module, LRP processing to an intermediary unit corresponding to a cell that has been transformed through an auction;
changing the BBS information for the requested LRP to a claim state by the intermediary unit, converting the LRP into an action and requesting the executor;
requesting, by the executor, to create a garden container according to a specified action request;
The method of providing an application service of a cloud-based platform comprising the step of the garden container downloading a droplet from the cloud controller according to the procedure requested as the action and then executing the application.

Images