CN111026502B - Business debugging architecture creating method and device, electronic equipment and storage medium - Google Patents
Business debugging architecture creating method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN111026502B CN111026502B CN201911149183.2A CN201911149183A CN111026502B CN 111026502 B CN111026502 B CN 111026502B CN 201911149183 A CN201911149183 A CN 201911149183A CN 111026502 B CN111026502 B CN 111026502B
- Authority
- CN
- China
- Prior art keywords
- debugging
- pod
- container
- service
- mirror image
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements 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/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements 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/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45562—Creating, deleting, cloning virtual machine instances
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements 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/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45591—Monitoring or debugging support
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
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)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a method and a device for creating a service debugging architecture, electronic equipment and a storage medium, and relates to the technical field of service debugging. Inquiring a service container in the Pod to be debugged and a node where the Pod to be debugged is located; creating a debugging Pod in the node according to preset Pod description information; the debugging Pod pulls a preset debugging tool mirror image according to a preset container mirror image address, and a debugging container sharing resources and permissions with the service container is established according to the debugging tool mirror image; and establishing communication connection between the debugging container and the user terminal through the interface of the container management application and the debugging Pod to complete the creation of the service debugging framework. The user only needs to send out the debugging instruction, can accomplish debugging to the debugging container, because debugging container and business container share resource and authority, debug the debugging container and wait to debug the business container, need not complicated operation, saved a large amount of time, because operate the debugging container, do not influence the operation of business container completely.
Description
Technical Field
The present application relates to the field of service debugging technologies, and in particular, to a method and an apparatus for creating a service debugging framework, an electronic device, and a storage medium.
Background
Kubernets (K8 s) is an open source Container cluster management system based on Docker, and kubernets can construct a scheduling service of a Container (Container) to allow a user to manage a Container cluster through the kubernets system. A Pod is the most basic deployment and scheduling unit of the Kubernetes system, and one Pod may include multiple containers, where the containers in the same Pod have the same Internet namespace network Protocol (IP) address and storage quota. Generally, after the Pod is created, the service container in the Pod needs to be debugged.
In the prior art, the service mode in the Pod debugging is as follows: firstly logging in a first physical server and a Node (Node), calling a Kubernetes command line tool to find a corresponding Pod, then finding a second physical server and a Node corresponding to the Pod, logging in the corresponding second physical server and the Node, using a Docker command line tool to log in a console corresponding to a container, and manually installing a corresponding debugging tool (in order to ensure that a container mirror image is as small as possible, the container mirror image cannot carry any debugging tool, and the debugging tool cannot be installed necessarily due to the limitation of the mirror image), wherein the debugging preparation work is complex, a large amount of time is consumed, and the service environment in the Pod is damaged.
Disclosure of Invention
In a first aspect, an embodiment of the present application provides a method for creating a service debug architecture, including:
receiving a construction request aiming at a service debugging framework sent by a user terminal through an interface of a container management application, and inquiring a service container in the Pod to be debugged and a node where the Pod to be debugged is located;
establishing a debugging Pod in the node according to preset Pod description information;
pulling a preset debugging tool mirror image according to a preset container mirror image address through the debugging Pod, and creating a debugging container sharing resources and permissions with the service container according to the debugging tool mirror image;
and establishing communication connection between the debugging container and the user terminal through the interface of the container management application and the debugging Pod.
In a second aspect, an embodiment of the present application further provides a service debug architecture creating apparatus, including:
the information inquiry unit is configured to receive an architecture construction request sent by a user terminal through an interface of the container management application, and inquire a service container in the Pod to be debugged and a node where the Pod to be debugged is located;
a Pod creation unit configured to create a debug Pod in the node according to preset Pod description information;
a container creating unit configured to pull a preset debugging tool mirror image according to a preset container mirror image address via the debugging Pod, and create a debugging container sharing resources and permissions with the service container according to the debugging tool mirror image;
a communication connection unit configured to establish a communication connection between the debugging container and the user terminal via the debugging Pod via an interface of the container management application.
In a third aspect, an embodiment of the present application further provides an electronic device, including:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the service debug architecture creation method according to the first aspect of the embodiment of the present application.
In a fourth aspect, an embodiment of the present application further provides a storage medium, where instructions in the storage medium, when executed by a processor of an electronic device, enable the electronic device to execute the service debug architecture creation method according to the first aspect of the embodiment of the present application.
The embodiment of the application adopts at least one technical scheme which can achieve the following beneficial effects: inquiring a service container in the Pod to be debugged and a node where the Pod to be debugged is located; then, creating a debugging Pod in the node according to preset Pod description information; pulling a preset debugging tool mirror image according to a preset container mirror image address through the debugging Pod, and creating a debugging container sharing resources and authority with the service container according to the debugging tool mirror image; and finally establishing communication connection between the debugging container and the user terminal through the interface of the container management application and the debugging Pod, thereby completing the establishment of the service debugging architecture. When the service container needs to be debugged, a user only needs to send out a debugging instruction through debugging application of a user terminal, and the debugging of the debugging container can be completed.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1 is a schematic diagram of interaction between a server and a user terminal according to an embodiment of the present application;
fig. 2 is a flowchart of a method for creating a service debugging framework according to an embodiment of the present application;
fig. 3 is a flowchart of a method for creating a service debugging framework according to an embodiment of the present application;
fig. 4 is a flowchart of a method for creating a service debugging framework according to an embodiment of the present application;
fig. 5 is a flowchart of a method for creating a service debugging framework according to an embodiment of the present application;
fig. 6 is a functional module schematic diagram of a service debugging architecture creating device according to an embodiment of the present application;
fig. 7 is a schematic functional module diagram created by a service debugging framework according to an embodiment of the present application;
fig. 8 is a circuit connection block diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.
A container: is a widely accepted standard and there are already many pre-built images that can be deployed on kubernets. Containerization creates a self-contained Linux execution environment. Any program and all its dependent items can be packaged into one file and then shared over the network. Anyone can download a container and deploy it on its infrastructure, creating one container can be done programmatically, creating a powerful CI and CD pipeline, multiple programs can be added to a single container.
Pod: kubernets do not operate the vessel directly; instead, it packages one or more containers into a high-level structure called Pod. Any container in the same Pod will share the same namespace and local network. Communication may be made between containers in the same Pod.
Kubernetes (k 8 s): the method is an open-source platform for automatic container operation, and the operation comprises deployment, scheduling and node inter-cluster expansion. Kubernets supports not only Docker (a low-level component used inside kubernets), but also socket container technology. Kubernetes specifies the following functions: automating the deployment and replication of containers, expanding or contracting container sizes over time, organizing containers into groups, and providing load balancing among containers, easily upgrading new versions of application containers, providing container resiliency, replacing containers if they fail, and so forth.
Node (node): is the smallest unit of computing hardware in Kubernetes. It is a representation of a single machine in a cluster, with the node KEY1WEI1 hosted on a node of the cloud platform.
Referring to fig. 1, an embodiment of the present application provides a method for creating a service debugging framework, which is applied to an electronic device, where the electronic device may be a server 200. As shown in fig. 2, the server 200 interacts with the user terminal 100 through a network 300. The user terminal 100 is installed with an application for debugging, which may be, for example, but not limited to, a web page browser. The method comprises the following steps:
s11: and receiving a building request aiming at a service debugging architecture sent by the user terminal 100 through an interface of the container management application, and inquiring a service container in the Pod to be debugged and a node where the Pod to be debugged is located.
The Interface of the container management Application may be a Kubernetes API (Application Programming Interface), and the Pod and the container are deployed and managed through the Kubernetes API. For example, the user may click a "debug" button on an operation interface of an application program installed in the user terminal 100 for debugging, at which time, the user terminal 100 transmits a framework building request to the electronic device, and causes the interface of the container management application to receive the framework building request. Specifically, the architecture building request may include a container building request, and it is understood that, in order to facilitate query, the container building request carries an identifier of a Pod to be debugged, and an ID of a service container in the Pod to be debugged and an ID of a node where the Pod to be debugged is located may be queried according to the identifier of the Pod to be debugged.
S12: and creating a debugging Pod in the node according to the preset Pod description information.
In order to realize the debugging operation of the Pod to be debugged, the created debugging Pod must be located in the same node as the Pod to be debugged, and the debugging Pod is used for debugging the Pod to be debugged. In addition, the debugging Pod can mount the volume on a/var/run/docker.sock volume of the node where the debugging Pod is located, so that the functions of obtaining the container operation authority and debugging the Pod specific management container can be realized. For example, the Debug Pod is created by including a Debug program, a main program, and an attach program, which are respectively used to create a Debug container, keep the Debug Pod running, and connect to the TTY of the Debug container.
S13: and the debugging Pod pulls a preset debugging tool mirror image according to a preset container mirror image address and creates a debugging container sharing resources and permissions with the service container according to the debugging tool mirror image.
The kubernetese api may transmit parameters "preset container mirror address, service container ID, debug container start command" to the environment variables of the debug container, in preparation for creating the debug container. For example, images carrying various debugging tools are pulled at a preset image address through debug program execution/usr/local/bin/debug, and a debugging container is created according to a service container ID and a debugging container starting command. The resources and permissions of the debug container sharing the service container may include, but are not limited to, networkMode, usernmode, ipcMode, pidMode, capAdd, and the like.
S14: the debug container is communicatively connected to the user terminal 100 via the interface of the container management application, the debug Pod.
It can be understood that the architecture building request may further include a Web Socket request (WebSocket is a protocol for performing full duplex communication on a single TCP connection), after the debug container is created, the interface of the container management application receives the Web Socket request, and establishes a communication connection between the debug container and the user terminal 100 through the debug Pod.
In the method for creating the service debugging architecture provided by the embodiment of the application, the service container in the Pod to be debugged and the node where the Pod to be debugged is located are inquired; then, creating a debugging Pod in the node according to preset Pod description information; pulling a preset debugging tool mirror image according to a preset container mirror image address through the debugging Pod, and creating a debugging container sharing resources and authority with the service container according to the debugging tool mirror image; and finally establishing communication connection between the debugging container and the user terminal 100 through the interface of the container management application and the debugging Pod, thereby completing the establishment of the service debugging architecture. When the service container needs to be debugged, a user can debug the debugging container only by sending a debugging instruction through the debugging application of the user terminal 100, the debugging container and the service container share resources and permission, the debugging container is debugged and the service container is debugged equivalently, complex operation is not needed, a large amount of time is saved, the operation of the service container is not influenced completely due to the fact that the debugging container is operated, the operation environment of the service container is not damaged, and online debugging can be achieved.
Specifically, as shown in fig. 3, the Pod description information includes naming information, pod operation description information, and a Pod mirror address, and S12 includes:
s31: and pulling the Pod mirror according to the Pod mirror address.
The Pod image may include the debug program, the main program, and the attach program.
S32: and creating a debugging Pod according to the naming information, the Pod operation description information and the Pod image.
The naming information can comprise debugging Pod names and container names in the debugging pods, and component names related to the debugging pods to be created can be set through the naming information; the Pod operation description information comprises a mount volume, a command executed before the debugging Pod is started, and a command executed before the debugging Pod is deleted, and the debugging Pod operation condition or the executable function can be set through the Pod operation description information.
Alternatively, as shown in fig. 4, S14 includes:
s41: and establishing TTY connection between the interface of the container management application in communication connection with the user terminal and the debugging Pod.
S42: and establishing TTY connection between the debugging Pod and the debugging container.
The user terminal 100 is communicated with the debugging container because the Kubernetes API can interact, and the user can use a command line to debug at the moment.
Optionally, as shown in fig. 5, the method further includes:
s51: and receiving a deletion request sent by the user terminal 100 through an interface of the container management application, and calling the debugging Pod to delete the debugging container.
S52: and deleting the debugging Pod after the debugging container is determined to be deleted successfully.
For example, a user may click a "delete" button on an operation interface of an application installed in the user terminal 100 for debugging, at this time, the user terminal 100 sends a delete request to the electronic device, so that the kubernets API receives the delete request, invokes an attach program execution/usr/local/bin/attach destroy command in a debug Pod to delete the debug container, and after the debug container is successfully deleted, the delete debug Pod is also deleted, thereby completing the whole delete operation, and releasing various resources of the node.
After the service debugging framework is established, a user can debug the service container through the debugging application, and after the debugging is finished, the debugging Pod and the debugging container can be reserved. When debugging is needed again, debugging can be directly carried out again, the process of creating a service debugging framework is omitted, and time is further saved.
Referring to fig. 6, an embodiment of the present application further provides a service debugging framework creating apparatus 600, which is applied to an electronic device, where the electronic device may be the server 200. As shown in fig. 2, the server 200 interacts with the user terminal 100 through a network 300. The user terminal 100 is installed with an application for debugging, for example, the application may be, but is not limited to, a web page browser. It should be noted that, the basic principle and the generated technical effect of the service debugging framework provided by the embodiment of the present application are the same as those of the embodiment described above, and for the sake of brief description, no part of the embodiment of the present application is mentioned, and reference may be made to the corresponding contents in the embodiment described above. The apparatus 600 includes an information inquiry unit 601, a pod creation unit 602, and a communication connection unit 604, wherein,
the information query unit 601 is configured to receive, through an interface of the container management application, a building request for a service debugging framework sent by a user terminal, and query a service container in the Pod to be debugged and a node where the Pod to be debugged is located.
A Pod creating unit 602 configured to create a debug Pod in a node according to preset Pod description information.
A container creating unit 603 configured to pull a preset debugging tool image according to a preset container image address via the debugging Pod, and create a debugging container sharing resources and permissions with the service container according to the debugging tool image.
The communication connection unit 604 is configured to establish a communication connection between the debug container and the user terminal 100 via the interface of the container management application and the debug Pod.
The service debug architecture creating apparatus 600 provided in this embodiment of the present application may implement the following functions when executed: inquiring a service container in the Pod to be debugged and a node where the Pod to be debugged is located; then, creating a debugging Pod in the node according to preset Pod description information; the debugging Pod pulls a preset debugging tool mirror image according to a preset container mirror image address, and a debugging container sharing resources and permissions with the service container is established according to the debugging tool mirror image; and finally, establishing communication connection between the debugging container and the user terminal 100 through the interface of the container management application and the debugging Pod, thereby completing the establishment of the service debugging architecture. When the service container needs to be debugged, a user can debug the debugging container only by sending a debugging instruction through the debugging application of the user terminal 100, the debugging container and the service container share resources and permission, the debugging container is debugged and the service container is debugged equivalently, complex operation is not needed, a large amount of time is saved, the operation of the service container is not influenced completely due to the fact that the debugging container is operated, the operation environment of the service container is not damaged, and online debugging can be achieved.
Specifically, the Pod description information includes naming information, pod operation description information, and a Pod mirror address, and optionally, the Pod creating unit 602 is specifically configured to pull a Pod mirror according to the Pod mirror address; and creating a debugging Pod according to the naming information, the Pod operation description information and the Pod image.
Optionally, the communication connection unit 604 is specifically configured to establish a TTY connection between the interface of the container management application and the debug Pod; a TTY connection is established with the debug container via the debug Pod.
Optionally, as shown in fig. 7, the apparatus 600 further includes:
a resource deleting unit 701 configured to receive a deletion request sent by the user terminal 100 via an interface of the container management application, and invoke the debug Pod to delete the debug container; and deleting the debugging Pod after the debugging container is determined to be deleted successfully.
It should be noted that the execution subjects of the steps of the methods provided in the above embodiments may be the same device, or different devices may be used as the execution subjects of the methods. For example, the execution subject of steps 21 and 22 may be device 1, and the execution subject of step 23 may be device 2; for another example, the execution subject of step 21 may be device 1, and the execution subjects of steps 22 and 23 may be device 2; and so on.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
Fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present application. Referring to fig. 8, at a hardware level, the electronic device includes a processor, and optionally further includes an internal bus, a network interface, and a memory. The Memory may include a Memory, such as a Random-Access Memory (RAM), and may further include a non-volatile Memory, such as at least 1 disk Memory. Of course, the electronic device may also include hardware required for other services.
The processor, the network interface, and the memory may be connected to each other via an internal bus, which may be an ISA (Industry standard architecture) bus, a PCI (Peripheral Component Interconnect) bus, an EISA (Extended Industry standard architecture) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one double-headed arrow is shown in FIG. 8, but this does not indicate only one bus or one type of bus.
And the memory is used for storing programs. In particular, the program may include program code comprising computer operating instructions. The memory may include both memory and non-volatile storage and provides instructions and data to the processor.
The processor reads the corresponding computer program from the nonvolatile memory into the memory and then runs the computer program, and the service debugging architecture creating device is formed on the logic level. The processor is used for executing the program stored in the memory and is specifically used for executing the following operations:
receiving a construction request aiming at a service debugging framework sent by a user terminal through an interface of a container management application, and inquiring a service container in the Pod to be debugged and a node where the Pod to be debugged is located;
creating a debugging Pod in the node according to preset Pod description information;
pulling a preset debugging tool mirror image according to a preset container mirror image address through the debugging Pod, and creating a debugging container sharing resources and authority with the service container according to the debugging tool mirror image;
and establishing communication connection between the debugging container and the user terminal through an interface of a container management application and a debugging Pod.
The method executed by the service debugging architecture creating device according to the embodiment shown in fig. 1 of the present application can be applied to a processor, or implemented by a processor. The processor may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules may be located in ram, flash, rom, prom, or eprom, registers, etc. as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.
The electronic device may also execute the method in fig. 1, and implement the function of the service debugging architecture creating device in the embodiment shown in fig. 1, which is not described herein again in this embodiment of the present application.
Of course, besides the software implementation, the electronic device of the present application does not exclude other implementations, such as a logic device or a combination of software and hardware, and the like, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or a logic device.
Embodiments of the present application also provide a computer-readable storage medium storing one or more programs, where the one or more programs include instructions, which when executed by a portable electronic device including a plurality of application programs, enable the portable electronic device to perform the method of the embodiment shown in fig. 1, and are specifically configured to:
receiving a construction request aiming at a service debugging framework sent by a user terminal through an interface of a container management application, and inquiring a service container in the Pod to be debugged and a node where the Pod to be debugged is located;
establishing a debugging Pod in the node according to preset Pod description information;
pulling a preset debugging tool mirror image according to a preset container mirror image address through the debugging Pod, and creating a debugging container sharing resources and permissions with the service container according to the debugging tool mirror image;
and establishing communication connection between the debugging container and the user terminal through the interface of the container management application and the debugging Pod.
In short, the above description is only a preferred embodiment of the present application, and is not intended to limit the scope of the present application. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
Computer-readable media, including both permanent and non-permanent, removable and non-removable media, may implement the information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising one of 8230; \8230;" 8230; "does not exclude the presence of additional like elements in a process, method, article, or apparatus that comprises that element.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
Claims (10)
1. A method for creating a service debugging architecture is characterized by comprising the following steps:
receiving a creation request aiming at a service debugging framework sent by a user terminal through an interface of a container management application, and inquiring a service container in the Pod to be debugged and a node where the Pod to be debugged is located;
establishing a debugging Pod for debugging the POD to be debugged in the inquired node according to the preset Pod description information;
pulling a preset debugging tool mirror image according to a preset container mirror image address through the debugging Pod, and creating a debugging container sharing resources and authority with the service container according to the debugging tool mirror image;
and establishing communication connection between the debugging container and the user terminal through the interface of the container management application and the debugging Pod.
2. The method of claim 1, wherein the Pod description information includes naming information, pod operation description information, and a Pod mirror address, and wherein creating a debug Pod according to the preset Pod description information includes:
pulling a Pod mirror image according to the Pod mirror image address;
and creating a debugging Pod according to the naming information, the Pod operation description information and the Pod mirror image.
3. The method of claim 1, wherein the establishing the communication connection between the debug container and the user terminal via the debug Pod comprises:
establishing TTY connection between an interface of a container management application which is in communication connection with the user terminal and the debugging Pod;
and establishing TTY connection between the debugging Pod and the debugging container.
4. The method of claim 1, wherein after the debugging Pod establishes a communication connection with the user terminal via an interface of a container management application and the debugging Pod, the method further comprises:
receiving a deletion request sent by the user terminal through an interface of a container management application, and calling the debugging Pod to delete the debugging container;
and deleting the debugging Pod after the debugging container is determined to be deleted successfully.
5. A service debug architecture creation apparatus, comprising:
the information inquiry unit is configured to receive a creation request aiming at a service debugging framework sent by a user terminal through an interface of the container management application, and inquire a service container in the Pod to be debugged and a node where the Pod to be debugged is located;
the Pod creating unit is configured to create a debugging Pod for debugging the POD to be debugged in the inquired node according to preset Pod description information;
a container creating unit configured to pull a preset debugging tool mirror image according to a preset container mirror image address via the debugging Pod, and create a debugging container sharing resources and permissions with the service container according to the debugging tool mirror image;
a communication connection unit configured to establish a communication connection between the debugging container and the user terminal via the debugging Pod via an interface of the container management application.
6. The apparatus of claim 5, wherein the Pod description information comprises naming information, pod operation description information, and Pod mirror address,
the Pod creating unit is specifically configured to pull a Pod mirror image according to the Pod mirror image address; and creating a debugging Pod according to the naming information, the Pod operation description information and the Pod mirror image.
7. The apparatus according to claim 5, wherein the communication connection unit comprises:
the communication connection unit is specifically configured to establish a TTY connection between an interface of a container management application having a communication connection with the user terminal and the debug Pod; and establishing TTY connection between the debugging Pod and the debugging container.
8. The apparatus of claim 5, further comprising:
a resource deleting unit configured to receive a deletion request sent by the user terminal through an interface of a container management application, and call the debugging Pod to delete the debugging container; and deleting the debugging Pod after the debugging container is determined to be deleted successfully.
9. An electronic device, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the traffic debug architecture creation method of any of claims 1 to 4.
10. A storage medium in which instructions, when executed by a processor of an electronic device, enable the electronic device to perform the business commissioning architecture creation method of any of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911149183.2A CN111026502B (en) | 2019-11-21 | 2019-11-21 | Business debugging architecture creating method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911149183.2A CN111026502B (en) | 2019-11-21 | 2019-11-21 | Business debugging architecture creating method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111026502A CN111026502A (en) | 2020-04-17 |
| CN111026502B true CN111026502B (en) | 2023-04-07 |
Family
ID=70206282
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911149183.2A Active CN111026502B (en) | 2019-11-21 | 2019-11-21 | Business debugging architecture creating method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111026502B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112650553B (en) * | 2020-12-09 | 2023-07-14 | 湖南麒麟信安科技股份有限公司 | Universal container management method and system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101119526A (en) * | 2007-09-13 | 2008-02-06 | 中兴通讯股份有限公司 | Message interface entire configurable framework device in mobile communication system and method therefor |
| CN108337146A (en) * | 2018-01-29 | 2018-07-27 | 深圳创维数字技术有限公司 | Terminal debugging apparatus, system and method |
| CN109582441A (en) * | 2018-11-30 | 2019-04-05 | 北京百度网讯科技有限公司 | For providing system, the method and apparatus of container service |
| US10459823B1 (en) * | 2016-06-29 | 2019-10-29 | EMC IP Holding Company LLC | Debugging using dual container images |
-
2019
- 2019-11-21 CN CN201911149183.2A patent/CN111026502B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101119526A (en) * | 2007-09-13 | 2008-02-06 | 中兴通讯股份有限公司 | Message interface entire configurable framework device in mobile communication system and method therefor |
| US10459823B1 (en) * | 2016-06-29 | 2019-10-29 | EMC IP Holding Company LLC | Debugging using dual container images |
| CN108337146A (en) * | 2018-01-29 | 2018-07-27 | 深圳创维数字技术有限公司 | Terminal debugging apparatus, system and method |
| CN109582441A (en) * | 2018-11-30 | 2019-04-05 | 北京百度网讯科技有限公司 | For providing system, the method and apparatus of container service |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111026502A (en) | 2020-04-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109547570B (en) | Service registration method, device, registration center management equipment and storage medium | |
| CN110187912B (en) | Node selection method and device | |
| CN111897623B (en) | Cluster management method, device, equipment and storage medium | |
| CN108322490B (en) | Method, device and server for configuring and deploying distributed cloud service system by virtual machine | |
| US9274843B2 (en) | Multi-redundant switchable process pooling for cloud it services delivery | |
| CN108964968B (en) | Service access management method and system in container cloud environment | |
| CN106886434B (en) | Distributed application installation method and device | |
| CN106990960B (en) | Code deployment method and device | |
| CN111786984B (en) | Pod communication connection method and device, electronic equipment and storage medium | |
| CN110968331B (en) | Method and device for running application program | |
| CN106569880B (en) | Method and system for dynamically sharing resources between Android applications | |
| CN109062714B (en) | Method and device for remotely controlling android device and electronic device | |
| CN116303309A (en) | File mounting method and device and electronic equipment | |
| CN111694639A (en) | Method and device for updating address of process container and electronic equipment | |
| CN109343970B (en) | Application program-based operation method and device, electronic equipment and computer medium | |
| CN110083366B (en) | Application running environment generation method and device, computing equipment and storage medium | |
| CN111026502B (en) | Business debugging architecture creating method and device, electronic equipment and storage medium | |
| CN111949297B (en) | Block chain intelligent contract upgrading method and device and electronic equipment | |
| US11071151B2 (en) | Methods and apparatuses for connecting a wireless access point through an application in a user equipment | |
| CN110489090B (en) | Application software development method and system based on application model | |
| CN107948337B (en) | Electronic file transmission method, device and system and computer readable storage medium | |
| CN113485908B (en) | Coverage rate obtaining method and device and electronic equipment | |
| CN113835827A (en) | Application deployment method and device based on container Docker and electronic equipment | |
| CN113010206A (en) | Containerization method, system and device for WEB application system | |
| CN113805878B (en) | Plug-in engineering method, device, computer system and medium |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20230309 Address after: Room 501-502, 5/F, Sina Headquarters Scientific Research Building, Block N-1 and N-2, Zhongguancun Software Park, Dongbei Wangxi Road, Haidian District, Beijing, 100193 Applicant after: Sina Technology (China) Co.,Ltd. Address before: 100193 7th floor, scientific research building, Sina headquarters, plot n-1, n-2, Zhongguancun Software Park, Dongbei Wangxi Road, Haidian District, Beijing, 100193 Applicant before: Sina.com Technology (China) Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |