CN114996039A - Cloud native system joint debugging method, system and medium based on third-party system docking - Google Patents

Cloud native system joint debugging method, system and medium based on third-party system docking Download PDF

Info

Publication number
CN114996039A
CN114996039A CN202210895838.6A CN202210895838A CN114996039A CN 114996039 A CN114996039 A CN 114996039A CN 202210895838 A CN202210895838 A CN 202210895838A CN 114996039 A CN114996039 A CN 114996039A
Authority
CN
China
Prior art keywords
interface
service
information
cloud
party system
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202210895838.6A
Other languages
Chinese (zh)
Inventor
邹理贤
叶立新
刘建平
纪诗琦
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Winhong Information Technology Co ltd
Original Assignee
Winhong Information Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Winhong Information Technology Co ltd filed Critical Winhong Information Technology Co ltd
Priority to CN202210895838.6A priority Critical patent/CN114996039A/en
Publication of CN114996039A publication Critical patent/CN114996039A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/54Interprogram communication
    • G06F9/547Remote procedure calls [RPC]; Web services
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3664Environments for testing or debugging software
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Debugging And Monitoring (AREA)
  • Stored Programmes (AREA)

Abstract

The invention relates to the field of cloud computing, in particular to a cloud native system joint debugging method based on third-party system docking, a computer-readable storage medium and a computer-readable storage system. A cloud native system identification step: acquiring system service information of a cloud native system; interface definition step: calling an API document of the cloud native system, and identifying interface information of a service corresponding to the acquired system service information according to the called API document; a data table construction step: constructing a data table frame corresponding to the service according to the interface information of the service; a system construction step: constructing a third-party system, setting each interface according to the interface information, and linking a data table for each interface; third-party system joint debugging: and communicating the constructed third-party system to the cloud management platform in a restful interface calling mode. Through the steps, the testing function that the third-party system is used as the simulation system to replace the cloud native system of the client is achieved, and the efficiency of joint debugging testing of development testing personnel is improved.

Description

Cloud native system joint debugging method, system and medium based on third-party system docking
Technical Field
The invention relates to the field of cloud computing, in particular to a cloud native system joint debugging method and system based on third-party system docking and a computer readable storage medium.
Background
A Cloud Management Platform (CMP) is a console for running Cloud computing services, is an important tool for monitoring, managing, analyzing and optimizing the Cloud computing services, and can manage multiple open-source or heterogeneous Cloud computing systems or other virtualization Platform products, such as simultaneously managing cloudstock, OpenStack, VMware, Docker and the like. Today, the technology of the cloud management platform is approved by various industries due to the rapid development of information technology. In the cloud management platform, the third-party heterogeneous resource systems are more and more interfaced, for example, the cloud management platform can also interface a private cloud native system (see fig. 2) already constructed by an enterprise, and the project modules are driven to operate various resources in the resource layer by calling API interfaces of various projects of the cloud native system.
At present, when a cloud management platform needs to realize docking of a cloud native system, a problem of difficult joint debugging may be encountered. For customers with extremely strict requirements on internal network isolation and safety, such as banks and the like, the cloud management platform only has a built cloud native system without an external network environment, and can only be used in the internal network of the customer after being docked with the cloud native system, so that the network of the cloud native system is not communicated with the network of a cloud management platform development tester. For safety, the user does not allow development testers to duplicate and build the same cloud management platform as the cloud native system in the external network. However, the cloud management platform needs to update the service of the cloud native system, so that development and test personnel can only compile, construct and package the written code and update the written code to the cloud management platform inside the customer in a local transmission manner and establish a test environment, and then can jointly test the docking and interaction functions of the cloud native system. These steps are time consuming, and as long as there is a problem with currently processing code packets, the steps need to be repeated, which greatly reduces the efficiency of joint debugging tests for development testers.
Disclosure of Invention
The invention aims to provide a method for improving the joint debugging efficiency of a cloud native system.
Usually, when a cloud management platform is used for butting a network-error-free cloud native system, development testers only need to build an environment of a set of third-party system at a joint debugging place to keep the network open, and then the joint debugging test can be performed on the cloud native system on own development tools in a real-time restful interface calling (as shown in fig. 1). The inventor finds out in the development process that: an API document can be formed in the restful interface calling process, information such as interface paths, input parameters and output parameters can be obtained from interface information recorded in the API document, and accordingly, table data such as a data table framework and the like associated with the interface can be constructed, so that a simulation system capable of achieving functions required by the target cloud native system can be built under the local environment of development testers of a cloud management platform, and the simulation system can directly replace the testing function of the cloud native system of a client.
Therefore, the cloud native system joint debugging method based on third-party system docking is provided, and comprises the following steps:
cloud native system identification: acquiring system service information of the cloud native system;
interface definition step: calling an API document of the cloud native system, and identifying interface information of a service corresponding to the obtained system service information according to the called API document;
a data table construction step: constructing a data table frame corresponding to the service according to the interface information of the service;
the system construction step: establishing a third-party system, setting each interface according to the interface information, and linking the data table under the corresponding data table frame for each interface;
third-party system joint debugging: and communicating the constructed third-party system to the cloud management platform in a restful interface calling mode.
The third-party system joint debugging step comprises a service execution step, wherein a service program corresponding to the system service information is executed, whether the called interface information is matched with the API document or not is judged, and if the called interface information is matched with the API document, the revision step is executed: and modifying the interface information or the data table frame according to the input adjusting instruction.
Wherein, the method comprises an incremental business step executed after the third-party system joint debugging step: and establishing new service information according to an input setting instruction, establishing an association relation between the established service information and interface information, and executing a service program corresponding to the established service information.
Wherein, the method comprises a packing step executed after the incremental business step: and packaging the test system with the incremental business and updating the test system with the incremental business to a local test environment of the cloud native system in a local transmission mode.
Wherein the interface information comprises one or more of interface path, input parameter and output parameter.
Wherein the interface defining step further comprises an interface verifying step: and verifying the interface information in the API document by using a postman interface debugging tool or a curl command in the environment where the cloud native system is located.
A computer-readable storage medium is further provided, which stores a computer program, and the computer program can implement the above cloud native system joint debugging method based on third-party system docking when being executed by a processor.
The cloud native system joint debugging system based on third-party system docking comprises a processor, a cloud management platform and a third-party system which are connected with the processor respectively, and the computer readable storage medium.
Has the beneficial effects that: for the situation that a cloud native system of a client is inconvenient to build in an internal test environment and can only be packaged into a local test environment of a client company to perform joint debugging test after codes are modified every time, a third-party system is built through the cloud native system joint debugging method based on the third-party system joint debugging, each interface of the third-party system is set according to interface information of a system service information service acquired from the cloud native system, a data table frame corresponding to the interface information of the service is built according to the interface information of the service, then each interface is linked with a data table under the corresponding data table frame, and the built third-party system is communicated to a cloud management platform in a restful interface calling mode so that the cloud management platform can call the interface of the third-party system corresponding to the interface information of the service in the service running process, and the cloud native system is simulated and developed in a self-coding mode, the cloud native system joint debugging system in the internal test environment of the company is realized based on the third-party system butt joint cloud management platform, the code does not need to be modified each time and then packaged to the local test environment of the client company for joint debugging test, and the joint debugging test efficiency of development testers is greatly improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly introduced below.
Fig. 1 is a flowchart of a cloud native system joint debugging method based on third-party system docking.
Fig. 2 is a schematic diagram of a prior art docking of a cloud management platform with a cloud native system.
Fig. 3 is a schematic diagram of the docking of the cloud management platform and the third-party system of the embodiment.
Detailed Description
The invention is described in further detail below with reference to specific embodiments.
The cloud native system joint debugging system based on third-party system docking of the embodiment comprises a processor, and a cloud management platform and a third-party system (see fig. 3) which are respectively connected with the processor. The construction of the third-party system is detailed by the following cloud native system joint debugging method based on third-party system docking, and is shown in fig. 1.
A cloud native system identification step: and acquiring system service information of the cloud native system. Firstly, service information of a cloud native system of a client is confirmed, wherein the service information is manually input by a development tester after being provided by the client, or is automatically extracted by calling a test development log of the cloud native system of the client.
An interface definition step: and calling the API document of the cloud native system, and identifying interface information of the service corresponding to the acquired system service information, such as interface path, access parameter and access parameter, according to the called API document. The API document is provided by the cloud native system developer, and the test developer extracts API information required during docking. Wherein, the step of carrying out artificial interface verification on the called interface information comprises the following steps: and verifying the interface information in the API document by using a postman interface debugging tool or a curl command in the environment where the cloud native system is located, and mainly checking whether the interface path, the input parameter and the output parameter are consistent with those described in the API document.
A data table construction step: and constructing a data table frame corresponding to the service according to the interface information of the service. And the development tester considers or builds a data table framework according to the table structure matched with the interface information of the service and newly builds a data table for the system to use.
The system construction step: and constructing a third-party system, setting each interface according to the interface information, and linking the data table under the corresponding data table frame for each interface. A development tester builds a third-party system (i.e., a new project in the prior art, which is not described herein) by using a springboot technology or other technologies, and compiles a corresponding interface according to a path, a parameter, and a parameter of the interface defined in the API document.
Third-party system joint debugging: and communicating the constructed third-party system to the cloud management platform in a restful interface calling mode, so that the cloud management platform can call an interface of the third-party system, corresponding to the interface information of the operated service, in the service operation process. The development tester starts the springboot project, which is equivalent to a third-party system needing docking, and can be used for internal docking and debugging. The internal butt joint and debugging comprises a service execution step, a service program corresponding to system service information is executed, whether the called interface information is matched with the API document or not is judged, and if the called interface information is matched with the API document, a revision step is executed: and modifying the interface information of the service identified in the interface definition step or modifying the data table frame corresponding to the interface information of the service constructed in the data table construction step according to the input adjustment instruction.
After the internal butt joint and the debugging are completed, the incremental business steps are also executed: the method comprises the steps of creating service information according to an input setting instruction, obtaining interface associated information in the created service information, executing a service program corresponding to the created service information, reading a data table generated by executing the service program under a data table frame, and linking an interface corresponding to the interface associated information to the data table. Finally, after the incremental business step, a packing step is executed: and packaging the newly-built service information, the interface correlation information and the data table information linked to the corresponding interface obtained in the incremental service step as an incremental test packet, and updating the incremental test packet to a local test environment of the cloud native system in a local transmission manner to complete the internal joint debugging of the third-party system.
According to the cloud native system joint debugging method based on third-party system butt joint, when a cloud native system of a client is inconvenient to build in an internal test environment, and only after codes are modified at each time, the cloud native system can be packaged in the internal test environment of a client company to perform joint debugging test, the third-party system developed through self-coding simulation can be used for realizing butt joint in the internal environment of the company, and is not required to be packaged in the internal test environment of the client company to perform joint debugging test after the codes are modified at each time, so that the efficiency of the joint debugging test of development and test personnel is greatly improved.
The above embodiments are only embodiments of the present invention, and the scope of protection is not limited thereto. The insubstantial changes or substitutions will now be made by those skilled in the art based on the teachings of the present invention, which fall within the scope of the claims.

Claims (8)

1. The cloud native system joint debugging method based on third-party system docking is characterized by comprising the following steps of:
a cloud native system identification step: acquiring system service information of the cloud native system;
interface definition step: calling an API document of the cloud native system, and identifying interface information of a service corresponding to the acquired system service information according to the called API document;
a data table construction step: constructing a data table frame corresponding to the service according to the interface information of the service;
the system construction step: establishing a third-party system, setting each interface of the third-party system according to the interface information of the service, and linking a data table under a data table frame corresponding to each interface;
third-party system joint debugging: and the constructed third-party system is communicated to the cloud management platform in a restful interface calling mode, so that the cloud management platform can call an interface of the third-party system, corresponding to the interface information of the operated service, in the service operation process.
2. The cloud native system joint debugging method based on third-party system docking of claim 1, wherein the third-party system joint debugging step comprises a service execution step of operating each service program corresponding to the system service information on a cloud management platform, judging whether the called interface information is matched with an API document, and if not, executing a revision step: and modifying the interface information of the service identified in the interface definition step or modifying the data table frame corresponding to the interface information of the service constructed in the data table construction step according to the input adjustment instruction.
3. The cloud native system joint debugging method based on third-party system docking according to claim 1, comprising an incremental business step executed after the third-party system joint debugging step: the method comprises the steps of creating service information according to an input setting instruction, obtaining interface associated information in the created service information, executing a service program corresponding to the created service information, reading a data table generated by executing the service program under a data table frame, and linking an interface corresponding to the interface associated information to the data table.
4. The cloud native system joint debugging method based on third-party system docking according to claim 3, comprising a packaging step performed after the incremental business step: and packaging the newly-built service information, the interface association information and the data table information linked to the corresponding interface obtained in the incremental service step to be used as an incremental test packet, and updating the incremental test packet to the local test environment of the cloud native system in a local transmission mode.
5. The cloud-native system joint debugging method based on third-party system docking according to claim 1, wherein the interface information comprises one or more of interface path, entry parameter and exit parameter.
6. The cloud native system joint debugging method based on third-party system docking according to claim 1, wherein the interface defining step further comprises an interface verifying step: and verifying the interface information in the API document by using a postman interface debugging tool or a curl command in the environment where the cloud native system is located.
7. The computer readable storage medium, which stores a computer program, wherein the computer program, when executed by a processor, can implement the cloud native system joint debugging method based on third-party system docking according to any one of claims 1 to 6.
8. The cloud native system joint debugging system based on third-party system docking is characterized by comprising a processor, and a cloud management platform and a third-party system which are respectively connected with the processor, and further comprising a computer readable storage medium according to claim 7, wherein a computer program on the computer readable storage medium can be executed by the processor.
CN202210895838.6A 2022-07-28 2022-07-28 Cloud native system joint debugging method, system and medium based on third-party system docking Pending CN114996039A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210895838.6A CN114996039A (en) 2022-07-28 2022-07-28 Cloud native system joint debugging method, system and medium based on third-party system docking

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210895838.6A CN114996039A (en) 2022-07-28 2022-07-28 Cloud native system joint debugging method, system and medium based on third-party system docking

Publications (1)

Publication Number Publication Date
CN114996039A true CN114996039A (en) 2022-09-02

Family

ID=83021924

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210895838.6A Pending CN114996039A (en) 2022-07-28 2022-07-28 Cloud native system joint debugging method, system and medium based on third-party system docking

Country Status (1)

Country Link
CN (1) CN114996039A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117472367A (en) * 2023-12-27 2024-01-30 中电数据产业有限公司 Heterogeneous resource intelligent identification and access method, device, equipment and storage medium

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180157532A1 (en) * 2016-12-01 2018-06-07 Vmware, Inc. Methods and apparatus to manage workload domains in virtual server racks
CN110704164A (en) * 2019-09-30 2020-01-17 珠海市新德汇信息技术有限公司 Cloud native application platform construction method based on Kubernetes technology
US10601856B1 (en) * 2017-10-27 2020-03-24 EMC IP Holding Company LLC Method and system for implementing a cloud native crowdsourced cyber security service
CN111949526A (en) * 2020-08-04 2020-11-17 上海金仕达软件科技有限公司 Cloud-protogenesis-based automated regression testing method
CN113852939A (en) * 2021-07-29 2021-12-28 浪潮软件科技有限公司 Cloud-native-oriented user plane function micro-service system
CN114064475A (en) * 2021-11-11 2022-02-18 中国联合网络通信集团有限公司 Cloud native application testing method, device, equipment and storage medium
WO2022045700A1 (en) * 2020-08-26 2022-03-03 Samsung Electronics Co., Ltd. Method and apparatus for autoscaling containers in a cloud-native core network
CN114564404A (en) * 2022-03-04 2022-05-31 中信银行股份有限公司 System and method for joint debugging simulation of third-party system

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180157532A1 (en) * 2016-12-01 2018-06-07 Vmware, Inc. Methods and apparatus to manage workload domains in virtual server racks
US10601856B1 (en) * 2017-10-27 2020-03-24 EMC IP Holding Company LLC Method and system for implementing a cloud native crowdsourced cyber security service
CN110704164A (en) * 2019-09-30 2020-01-17 珠海市新德汇信息技术有限公司 Cloud native application platform construction method based on Kubernetes technology
CN111949526A (en) * 2020-08-04 2020-11-17 上海金仕达软件科技有限公司 Cloud-protogenesis-based automated regression testing method
WO2022045700A1 (en) * 2020-08-26 2022-03-03 Samsung Electronics Co., Ltd. Method and apparatus for autoscaling containers in a cloud-native core network
CN113852939A (en) * 2021-07-29 2021-12-28 浪潮软件科技有限公司 Cloud-native-oriented user plane function micro-service system
CN114064475A (en) * 2021-11-11 2022-02-18 中国联合网络通信集团有限公司 Cloud native application testing method, device, equipment and storage medium
CN114564404A (en) * 2022-03-04 2022-05-31 中信银行股份有限公司 System and method for joint debugging simulation of third-party system

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117472367A (en) * 2023-12-27 2024-01-30 中电数据产业有限公司 Heterogeneous resource intelligent identification and access method, device, equipment and storage medium
CN117472367B (en) * 2023-12-27 2024-03-26 中电数据产业有限公司 Heterogeneous resource intelligent identification and access method, device, equipment and storage medium

Similar Documents

Publication Publication Date Title
US8572437B2 (en) Multi-platform test automation enhancement
US7895565B1 (en) Integrated system and method for validating the functionality and performance of software applications
CN111414172B (en) Automatic deployment and release system and method for application software
US20180285247A1 (en) Systems, methods, and apparatus for automated code testing
WO2016177124A1 (en) Method and device for implementing continuous integration test
US10169203B2 (en) Test simulation for software defined networking environments
CN113760704A (en) Web UI (user interface) testing method, device, equipment and storage medium
CN106612204B (en) Service checking method and device
CN105117346A (en) Automatic testing method and system for distributed system of virtualization platform
CN103186463B (en) Determine the method and system of the test specification of software
CN109344053A (en) Interface coverage test method, system, computer equipment and storage medium
KR20210042713A (en) Test apparatus to test interoperability of nfv system
CN110990289B (en) Method and device for automatically submitting bug, electronic equipment and storage medium
CN109766278A (en) The backstage gateway WEB automatic test approach based on OSGI frame
CN114996039A (en) Cloud native system joint debugging method, system and medium based on third-party system docking
CN112817853A (en) Automatic test method, system and electronic equipment
CN115576817A (en) Automatic test system, method, electronic equipment and storage medium
CN112506772B (en) Web automatic test method, device, electronic equipment and storage medium
CN114047949A (en) Application system domestic platform migration adaptation method
CN111881056A (en) Automatic test framework and test method
US20230297496A1 (en) System and method for serverless application testing
US20230325298A1 (en) System and method for cloud infrastructure test automation
KR102242622B1 (en) Method and system of providing solution for smart factory
CN114968819A (en) Code quality problem detection and repair method for micro-service continuous integration
CN112445692B (en) Case testing method and terminal

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20220902