CN111355620A

CN111355620A - Cloud service testing and publishing automation system

Info

Publication number: CN111355620A
Application number: CN201811562619.6A
Authority: CN
Inventors: 方诚仪
Original assignee: Gemini Open Cloud Computing Inc
Current assignee: Gemini Open Cloud Computing Inc
Priority date: 2018-12-20
Filing date: 2018-12-20
Publication date: 2020-06-30

Abstract

The invention discloses a cloud service testing and releasing automation system which can manage API description files of different versions by using a manager instrument board so as to perform testing. If the test is passed, the cloud service is automatically registered on the service login element, and if the test is not passed, the cloud service is reported back to the manager dashboard. Therefore, by the version of the API description file, the cloud service can be tested, updated and stopped, the operation of the published cloud service is not influenced, and a test failure message is provided for a manager or a developer to modify the registration content of the cloud service.

Description

Cloud service testing and publishing automation system

[ technical field ] A method for producing a semiconductor device

The invention relates to a cloud service test management system, in particular to a cloud service test and release automation system.

[ background of the invention ]

In order to avoid exposing a system providing services to the internet, an API gateway (API gateway) is installed in a demilitarized zone (DMZ), and a user interacts with the services through the API gateway, thereby reducing coupling strength between the user and the services, improving security of the services, and providing a service provider with a pipeline for establishing, publishing, maintaining, monitoring, and protecting the services.

However, the service update release cannot affect the operation of the service, and the service needs to be subjected to unit test, integration test, and preparation system test before the release, if a problem occurs after the release, the service can return to the mode of the previous version to operate, which is a great burden for the service provider to manage.

The invention solves the problem of the automatic system for testing and issuing management, reduces the burden of service provider for maintaining service, and improves the efficiency of service issuing and updating.

[ summary of the invention ]

An object of the present invention is to provide a cloud service testing and publishing automation system, which ensures that cloud service is not interrupted by update publishing.

The invention aims to enable developers to directly open the cloud service to the outside through a cloud service testing and releasing automation system, and the developers can test the actually operated system without preparing a preparation environment, thereby reducing the risk of releasing failure caused by different test system environments.

An object of the present invention is to provide a cloud service test and release automation system that supports version management of cloud services and allows test items to be expanded at any time.

The cloud service test and release automation system comprises a manager dashboard, a message queue, a multi-process module, an API description parser, an API gateway and a cloud service login element, and is characterized in that the manager dashboard provides functions of receiving an API description, editing the API description, sending a test message to the message queue, retrieving a cloud service element list from the API gateway, and providing an operation interface, wherein the API description corresponds to registration data of a cloud service; the message queue receives the test message, converts the test message into a test command and uses the test command as a buffer area of the test command; the multi-process module fetches the test instruction from the message queue and provides the API file parser with the API description file; the API file parser sends an API request to a cloud service of a cloud service system according to the API description file, and the cloud service returns the result of the API request to the API file parser and forwards the result to the multi-process module after receiving the API request; the multi-process module receives the result of the API request to make a test report, and determines whether to inform the API gateway to open the cloud service according to the test result; and the API gateway registers the verified cloud service in the service login element and issues the cloud service, or transmits the test report of the failed cloud service to the manager dashboard.

A cloud service testing and issuing automation method comprises the steps of deploying a cloud service in a cloud service system; uploading an API description file through a manager dashboard, wherein the API description file corresponds to registration data of the cloud service; sending a test message to a message queue through the manager dashboard; converting the test message into a test instruction through the message queue and scheduling; reading the test instruction and the API description file from the message queue through a multi-process module, and triggering an API description file resolver to test the cloud service; sending a plurality of API requests to the cloud service of the cloud service system through the API description file parser, and sending a return result of the API requests of the cloud service to the multi-process module; if the cloud service passes the test, the multi-process module informs the API gateway, the API gateway logs the registration data of the cloud service in a service login element and issues the cloud service, or the cloud service fails the test, and the multi-process module transmits the test report of the cloud service to the manager dashboard.

[ description of the drawings ]

The drawings are for illustrative purposes and are not intended to limit the scope of the present disclosure, and are not intended to be exhaustive or to indicate that a component or step of the drawings is essential to the present disclosure. In a particular environment, the invention can be modified to achieve the same functionality in accordance with the spirit of the invention, and the scope of the invention is defined by the appended claims.

Fig. 1 is a system architecture diagram of a cloud service test and release automation system.

Fig. 2 is a flow diagram of the interaction operations of the elements of the cloud service test and release automation system.

[ notation ] to show

100 API profile

200 users

300 cloud service test and release automation system

310 manager dashboard

320 message queue

330 multi-process module

340 API description parser

350 API gateway

360 service login element

370 service discovery mechanism

371 service end

372 client

400 cloud service system

410 cloud service

S100, S110, S120, S130, S140, S150, S160, S170, S180, S190, S195, S200, S210, S300, S310, S320, S330, S400

[ detailed description ] embodiments

Referring to fig. 1, the cloud service test and release automation system 300 is integrated with the API gateway 350 and disposed in the DMZ. The cloud service test and distribution automation system 300 reads the API description file 100(API description document), and performs management such as testing, reporting of a test result, registration, distribution, and the like according to the content of the API description file 100. The present invention provides a cloud service test and release automation system 300, which implements cloud service API management, and the cloud service test and release automation system 300 includes a manager dashboard 310, a message queue 320, a multi-process module 330, an API profile parser 340, an API gateway 350, and a service login element 360.

By loading the API profile 100 through the manager dashboard 310 of the cloud service test and release automation system 300, the cloud service test and release automation system 300 and the cloud service 410 of the cloud service system 400 start a test process and log in a service, and after completion, the cloud service related to the user 200 can be provided through the API gateway 350. The invention can automatically complete the test and release of the cloud service by using the API description file, and has the function of automation of the test and release.

Further, the cloud service test and release automation system 300 of fig. 1, in conjunction with the service discovery mechanism 370, has the function of actively discovering services, completing the test and logging in the services. The service discovery mechanism 370 is divided into a server 371 and a client 372. Once the cloud service 410 is started, the client 372 communicates with the server 371 of the service discovery mechanism 370 through the client 372, if the service discovery mechanism is not logged in the service login element 360, a test operation is started, and after the test is completed, the service is logged in and the service is provided. It is specifically stated that the cloud service system 400 is also referred to herein as a cloud, which may be a distributed or a single cloud service system, without limitation.

First, the architecture of the API description file 100 basically includes information such as a cloud service name, a version, a service host address, a cloud service path, cloud service contents, a data type of cloud service parameters, a cloud service test instruction, a cloud service test item, and a cloud service test result report storage location. Of course, the API profile 100 can be customized for different services, providing more information content, and ensuring extensibility and compatibility of the API profile. In practice, the API profile 100 may follow a JSON or YAML data serialization format, which may provide higher readability than the traditional deployment and test instructions in the past.

Second, the main functions of the manager dashboard 310 are explained as follows:

(1) provide an interface for editing of the API profile 100 and verify that the format of the API profile 100 is correct. The API profile 100 is written according to a specified syntax, and the manager dashboard 310 provides for editing, modifying, and verifying that the API profile 100 complies strictly with the written syntax.

(2) An interface for test management is provided. After the developer transmits the publishing request through the manager dashboard 310, the developer sends a test message and stores the message in the message queue 320.

(3) An interface for test management is provided. The API gateway 350 obtains the test result report and refers to the past version test record, the test result, the test performance, and other information, so as to provide the strong management function for the administrator, provide the basis for program modification or element deployment improvement, and improve the cloud service quality.

(4) Providing API list publishing status of the cloud service 410 and cloud service registration, update, and deregistration management functions. Through the API gateway, the published cloud service data is obtained, so that an operator can immediately master operation data, the situation of the cloud service and the like. Once the cloud service test is completed, the started cloud service can be released and the service can be provided, and the cloud service can be dismounted from the system and the service can be stopped.

Third, the multi-process module 330 is used to manage the test process, take out the information of the test items from the message queue 320, trigger the API descriptor parser 340 to perform the test according to the content of the API descriptor 100, and after retrieving the test result, determine whether the test is passed according to the API descriptor 100. If the test fails, the multi-process module 330 provides the version of the API profile 100 and the test results to the manager dashboard 310 for the developer or manager to modify the basis of the API profile 100. If tested, the multi-process module 330 notifies the API gateway 350 and provides relevant messages for the API gateway to perform actions related to registration and publication.

Fourth, the API gateway 350 is illustrated. If tested, the API gateway 350 receives a notification from the multiprocess module 330, including relevant information in the API profile 100, such as cloud service name, service host address, cloud service path, and cloud service content. The API gateway 350 registers the cloud service with the cloud service registration element 360 and opens the cloud service to the outside.

Fifth, the message queue 320 is described. The front-end recipient manager dashboard 310 transmits test request messages and schedules them as a buffer for cloud services test scheduling.

Sixth, API profile parser 340 is illustrated. The multi-process module 330 receives the instruction, parses the API description file 100 according to the syntax of the configuration file, converts the API description file into a test instruction according to a certain format, and transmits the test instruction to the cloud service system 400 to obtain the return result of the cloud service 410. Typically, the test instructions include create, delete, update, and fetch categories, which may be extended as needed. When converting into an instruction according to a certain format, the RESTful instruction format of HTTP can be used, but not limited to, so that the instruction can be dispatched by using HTTP. The API profile parser 340 interacts with the cloud services 410 in the cloud service system 400, first requests a service from a certain cloud service 410 in the cloud service system 400 according to the content of the API profile 100, and the cloud service 410 returns the operation result to the API profile parser 340 and then transfers the operation result to the multi-process module 330.

Fig. 2 is a process diagram of automated operation of cloud service testing and distribution, and interaction between elements of the system.

Step S100 (not shown in fig. 2): deploying cloud services in a cloud service system;

step S110: loading the API description file, which uploads the API description file 100 to the cloud service test and release automation system 300 through the manager dashboard 310;

step S120: sending a test request, and after receiving the API description 100, the manager dashboard 310 converts the test request into a test instruction and temporarily stores the test instruction in the message queue 320;

step S130: reading the test message, the multi-process module 330 reads the test command from the message queue 320;

step S140: initiating a test, the multiprocessing module 330 upgrading the API profile to the API profile parser 340;

step S150: a request is made to a cloud service, and the API description file parser 340 sends an API request to a certain cloud service 410 of the cloud service system 400 according to the API description file;

step S160: obtaining the reply of the cloud service, and reading the result returned by the cloud service 410 by the API profile resolver 340;

step S170: returning the test result, the multi-process module 330 receives the test result of the API profile parser 340 and makes a test report;

step S180: transmitting the test result to the API gateway 350, if the test is passed, the multi-process module 330 transmits the cloud service related information to the API gateway 350; and

step S190: registering the cloud service with the service login element 360, the API gateway 350 notifying the service login element 360 and starting the service; or

Step S195: reporting the test result to the manager dashboard 310. if the test fails, the multi-process module 330 provides the test result to the manager dashboard 310 as a basis for the developer or manager to modify the API profile 100.

The cloud Service testing and publishing automation system further utilizes an automatic Discovery mechanism and has a Service Discovery function, so that the API management platform can automatically detect that a Service is to be registered and perform testing and publishing. The automatic service discovery mechanism comprises a server and a client, and realizes automatic discovery of cloud services through a service registration (service registration) element. The service registration element includes a database for storing a network address of each cloud service instance. The server side of the automatic discovery mechanism is installed in the cloud service testing and releasing automation system, and the client side of the automatic discovery mechanism is installed in the cloud service system. The server side of the automatic discovery mechanism can look up the cloud service registered by the service login element, and the client side of the automatic discovery mechanism is triggered by the cloud service and sends a registration request to the server side. When the cloud service is started, the client provides registration information, such as a host name (hostname), an IP address (IP address), a port number (port number), a status page (status page), a health check (health check) …, and sends a request for registration to the server. The server of the service registration element finds that the service is not registered, and sends a message of the test request to the message queue, and the multi-process module starts the test operation, for example, the registration is completed through the test, and the issue is completed, as described above. When the cloud Service is stopped, the automatic discovery mechanism is also triggered to acquire the registration data from the Service Registry (Service Registry), and if the registration data is found, the registration data is deleted. If the automatic discovery mechanism is not used, the test can still be carried out through the manager dashboard, the cloud service is logged in, and the registration data of the stopped cloud service is deleted.

The operation flow of the auto discovery service mechanism is described as follows:

step S100 (not shown in fig. 2): deploying cloud services 410 in cloud services system 400;

step S300: requesting service registration, when the cloud service 410 is started, the client 372 of the auto discovery service mechanism 370 provides the API profile 100 to the server 371 and requests registration;

step S310: referring to the registration of the cloud service, the server 371 of the auto discovery service mechanism 370 inquires the service login element 360 about the registration of the cloud service;

step S320: returning the registration, the service login element 360 returns the registration of the cloud service to the server 371 of the auto discovery service mechanism 370;

step S330: sending a test request, such as the cloud service is not registered, the server 371 of the auto discovery service mechanism 370 sends the test request carrying the API profile 100 to the message queue 320; and

and executing the steps S140-S195, testing the cloud service and completing login and release.

If the auto discovery mechanism is not used, the administrator dashboard 310 may still be utilized to manually test and log in by querying the service log-in component 360 through the API gateway 350. The operation flow is as follows:

step S200: looking up the cloud service registration condition, and inquiring a service login element 360 through an API gateway 350 to obtain a cloud service login list; and

step S210: returning to the cloud service registration list, the API gateway 350 transmits the cloud service registration list to the manager dashboard 310, if not, the API profile 100 may be loaded, and steps S100-S195 are performed to perform cloud service testing and complete the login and release.

It is emphasized that the cloud service testing and publishing automation system can test for API description files of different versions, and at this time, the published cloud service is not affected.

Claims

1. An automated system for testing and publishing cloud services, the system comprising:

a manager dashboard, a message queue, a multi-process module, an API descriptor parser, an API gateway, and a cloud service registry element,

the manager dashboard provides functions of receiving an API description, editing the API description, sending a test message to the message queue, retrieving a cloud service element list from the API gateway, and providing an operation interface, wherein the API description corresponds to registration data of a cloud service;

the message queue receives the test message, converts the test message into a test command and uses the test command as a buffer area of the test command;

the multi-process module fetches the test instruction from the message queue and provides the API file parser with the API description file;

the API file parser sends an API request to a cloud service of a cloud service system according to the API description file, and the cloud service returns the result of the API request to the API file parser and forwards the result to the multi-process module after receiving the API request;

the multi-process module receives the result of the API request to make a test report, and determines whether to inform the API gateway to open the cloud service according to the test result; and

the API gateway registers the verified cloud service in the service login element and issues the cloud service, or transmits the test report of the failed cloud service to the manager dashboard.

2. The automated cloud service testing and publishing system of claim 1, further comprising a service discovery mechanism, the service discovery mechanism comprising a server and a client, wherein the server is installed in the automated cloud service testing and publishing system, the client is installed in the cloud service system, the cloud service provides the registration data of the cloud service when it is started and triggers the server to query the service registration component for registration, and if the cloud service is not registered, a test message is sent to the message queue.

3. The cloud services test and release automation system of claim 1, wherein the API profile includes an API registration data.

4. The cloud services testing and release automation system of claim 3, wherein the API profile is compiled in JSON or YAM format.

5. A method for automating cloud service testing and publishing is characterized by comprising the following steps:

deploying a cloud service in a cloud service system;

uploading an API description file through a manager dashboard, wherein the API description file corresponds to registration data of the cloud service;

sending a test message to a message queue through the manager dashboard;

converting the test message into a test instruction through the message queue and scheduling;

reading the test instruction and the API description file from the message queue through a multi-process module, and triggering an API description file resolver to test the cloud service;

sending a plurality of API requests to the cloud service of the cloud service system through the API description file parser, and sending a return result of the API requests of the cloud service to the multi-process module; and

if the cloud service passes the test, the multiprocessing module notifies the API gateway, and the API gateway logs the registration data of the cloud service in a service login element and publishes the cloud service, or

The cloud service fails the test, and the multi-process module transmits the test report of the cloud service to the manager dashboard.

6. The method as claimed in claim 5, further comprising a step of discovering a service, wherein the step of discovering the service sends a test message to a message queue through a service discovery mechanism, such as discovering an unregistered cloud service, and performs the test and service login operations of the unregistered cloud service.

7. The method as claimed in claim 6, wherein the service discovery mechanism comprises a server installed on the cloud service test and release automation system and a client installed on the cloud service system, the server providing the registration data of the cloud service when the cloud service is started and triggering the server to inquire registration information from the service registration element, and if the cloud service is not registered, transmitting the test message to the message queue.