CN114745418A

CN114745418A - Task access method, device, equipment and storage medium

Info

Publication number: CN114745418A
Application number: CN202210390556.0A
Authority: CN
Inventors: 张舜晨; 杨吉明
Original assignee: Beijing ByteDance Network Technology Co Ltd
Current assignee: Beijing ByteDance Network Technology Co Ltd
Priority date: 2022-04-14
Filing date: 2022-04-14
Publication date: 2022-07-12

Abstract

The present disclosure provides a method, an apparatus, a device and a storage medium for accessing tasks, wherein after a container is started, a remote call service is run in the container to generate an access port of the remote call service, thereby implementing a mapping relationship between the access port and a task port corresponding to each task run in the container, after two containers establish a communication connection, a task in any one of the containers can initiate a joint call access request to a task in the other container through the communication connection, thereby generating a joint call access link between two tasks based on the remote call service run in each container and port access mapping configuration information between the two tasks indicated by the joint call access request, so as to implement access and call between the tasks, and can rapidly implement access between the tasks in different containers, and has the advantages of simple operation, time saving and strong universality, the use convenience of the user is improved.

Description

Task access method, device, equipment and storage medium

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a task access method, apparatus, device, and storage medium.

Background

With the rapid Development of the internet, the network has gradually become an indispensable assistant for people, great convenience is brought to the work and life of people through the network, various applications depending on the internet are used by people, especially an Integrated Development Environment (IDE), the display of a program can be realized on a computer, a code compiling function, an analyzing function, a compiling function and a debugging function are Integrated, and the program Development is more convenient, rapid and efficient.

When a user develops in an integrated development environment, for a task in a container to be called, after the container is started, the user needs to repeatedly search information such as container addresses and port numbers corresponding to the container, the task and the like to realize access configuration, so that a large amount of time is consumed, the workload is large, the bottom code amount is large, and the configuration needs to be performed in a targeted manner, the development cost is high, and the development speed of the user is influenced.

Disclosure of Invention

The embodiment of the disclosure at least provides a task access method, a task access device, a task access equipment and a task access storage medium.

The embodiment of the disclosure provides a task access method, which comprises the following steps:

running a first container, wherein a first target task and a first remote calling service run in the first container;

establishing a communication connection between the first container and a second container remotely co-tuned with the first container;

and in response to a joint debugging access request initiated through the communication connection, generating a joint debugging access link between the first target task and the second target task based on the first remote calling service, a second remote calling service operated by the second container and port access mapping configuration information indicated by the joint debugging access request and between the first target task and a second target task operated by the second container.

In an optional implementation manner, after generating the coherent access link between the first target task and the second target task, the method further includes:

storing the port access mapping configuration information, the task information of the first target task and the task information of the second target task;

after the second container is disconnected and communication connection is established with the first container again, updating a joint debugging access link between the first target task and the second target task based on the port access mapping configuration information, the task information of the first target task and the task information of the second target task, and the first remote calling service and the second remote calling service.

In an alternative embodiment, the reestablishing the communication connection with the first container after the disconnection of the second container by the steps of:

querying a second access port of the second container from a database based on task information of the second target task;

and controlling the first container and the second container to establish communication connection again based on the second access port.

In an alternative embodiment, the executing a first container, in which a first target task and a first remote invocation service are executed, includes:

starting a first container, and starting a first remote calling service in the first container;

generating a first access port of the first remote invocation service and a first connection key for connecting to the first access port, so that after the first connection key and the first access port are exposed, other containers except the first container in the IDE (integrated development environment) are connected with the first container through the first connection key and the first access port;

executing at least one first task in the first container, the at least one first task including the first target task;

generating a first connection mapping between the first access port and the task port of each first task, so that other containers connected with the first container inquire and/or connect any first task through the first access port and the first connection mapping.

In an optional embodiment, the generating, in response to a joint call access request initiated through the communication connection, a joint call access link between the first target task and the second target task based on the first remote call service, a second remote call service executed by the second container, and port access mapping configuration information indicated by the joint call access request and between the first target task and a second target task executed by the second container includes:

responding to a joint debugging access request initiated through the communication connection, and acquiring a second connection mapping corresponding to a second remote calling service operated by the second container, wherein the second connection mapping comprises a mapping relation between a task port of each second task and a second access port of the second remote calling service;

establishing a joint debugging channel between the first container and the second container based on the first connection mapping and the second connection mapping corresponding to the first remote call service, wherein the joint debugging channel represents bidirectional mapping between each first task and each second task;

and generating a joint debugging access link between the first target task and a second target task operated by the second container through the joint debugging channel and port access mapping configuration information between the first target task and the second target task indicated by the joint debugging access request.

In an alternative embodiment, the establishing a communication connection between the first container and a second container remotely associated with the first container:

querying a second access port of a second remote invocation service in the second container and a second connection key for connecting the second access port from a database;

and controlling the first container and a second container which is remotely associated with the first container to establish communication connection based on the second access port and the second connection key.

In an alternative embodiment, after establishing a communication connection between the first container and a second container remotely co-tuned to the first container, the second target task is determined by:

acquiring at least one active port running in the second container based on the second access port and the second connection key, and displaying the at least one active port to a user, wherein the active port is a task port of a second task in a running state in the second container;

and responding to preset operation of the user for a target port in the at least one active port, and determining a second task corresponding to the target port as a second target task to be accessed.

In an alternative embodiment, the second target task is determined by:

responding to the input operation of the user, determining an input container and an input port input by the user, wherein the second task corresponding to the input port comprises a task in a running state and a task in a non-running state;

and determining the input container as a second container remotely associated with the first container, and determining a second task corresponding to the input port as a second target task to be accessed.

In an optional embodiment, in a case that the second target task is a task in a non-running state, the generating a joint debugging access link between the first target task and the second target task based on the first remote call service, the second remote call service run by the second container, and the port access mapping configuration information between the first target task and the second target task run by the second container, where the port access mapping configuration information is indicated by the joint debugging access request includes:

and under the condition that the second target task runs, generating a joint debugging access link between the first target task and the second target task based on the first remote calling service, the second remote calling service run by the second container and port access mapping configuration information between the first target task and the second target task run by the second container, wherein the port access mapping configuration information is indicated by the joint debugging access request.

An embodiment of the present disclosure further provides a task access device, where the task access device includes:

the system comprises a container operation module, a first remote calling module and a second remote calling module, wherein the container operation module is used for operating a first container, and a first target task and a first remote calling service are operated in the first container;

the connection establishing module is used for establishing communication connection between the first container and a second container remotely joint-adjusted with the first container;

a first link generating module, configured to generate, in response to a joint call access request initiated through the communication connection, a joint call access link between the first target task and the second target task based on the first remote call service, a second remote call service executed by the second container, and port access mapping configuration information indicated by the joint call access request and between the first target task and a second target task executed by the second container.

In an optional implementation manner, the apparatus further includes a second link generation module, where the second link generation module is configured to:

In an optional implementation manner, when the second link generation module is configured to re-establish a communication connection with the first container after the second container is disconnected, the second link generation module is specifically configured to:

In an optional embodiment, the container operation module is specifically configured to:

In an optional implementation manner, the first link generating module is specifically configured to:

establishing a joint debugging channel between the first container and the second container based on the first connection mapping and the second connection mapping corresponding to the first remote calling service, wherein the joint debugging channel represents bidirectional mapping between each first task and each second task;

In an optional implementation manner, the connection establishing module is specifically configured to:

In an optional implementation manner, the apparatus further includes a task determination module, and the task determination module is configured to:

In an optional implementation manner, the task determining module is specifically configured to:

In an optional implementation manner, in a case that the second target task is a task in a non-running state, the first link generation module is specifically configured to, when the first link generation module is configured to generate the joint access link between the first target task and the second target task based on the first remote invocation service, the second remote invocation service run by the second container, and the port access mapping configuration information between the first target task and the second target task run by the second container, which is indicated by the joint access request, specifically:

and under the condition that the second target task runs, generating a joint debugging access link between the first target task and the second target task based on the first remote calling service, the second remote calling service run by the second container and port access mapping configuration information indicated by the joint debugging access request and between the first target task and the second target task run by the second container.

An embodiment of the present disclosure further provides an electronic device, including: the system comprises a processor, a memory and a bus, wherein the memory stores machine readable instructions executable by the processor, the processor and the memory are communicated through the bus when the electronic device runs, and the machine readable instructions are executed by the processor to execute the steps of the task access method.

Embodiments of the present disclosure also provide a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to perform the steps of the above task access method.

After the container is started, the remote call service is operated in the container to generate an access port of the remote call service, so that the mapping relation between the access port and the task port corresponding to each task operated in the container is realized, after the two containers are established with communication connection, the task in any one container can initiate a joint call access request to the task in the other container through the communication connection, so that a joint call access link between the two tasks is generated based on the remote call service operated in each container and port access mapping configuration information between the two tasks indicated by the joint call access request to realize the access and call between the tasks, the access between the tasks in different containers can be quickly realized, the operation is simple and convenient, the time is saved, the universality is strong, the use convenience of the user is improved.

Furthermore, under the condition that communication connection between two containers is interrupted due to container refreshing or restarting and the like, the communication connection between the containers can be realized again based on the stored task information, and then a joint debugging access link between the two tasks is updated, so that the method is convenient and quick, a user does not need to re-determine the current task information, the workload of code modification is reduced, and the development speed of the user is improved.

In order to make the aforementioned objects, features and advantages of the present disclosure more comprehensible, preferred embodiments accompanied with figures are described in detail below.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the technical aspects of the disclosure.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings required for use in the embodiments will be briefly described below, and the drawings herein incorporated in and forming a part of the specification illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the technical solutions of the present disclosure. It is appreciated that the following drawings depict only certain embodiments of the disclosure and are therefore not to be considered limiting of its scope, for those skilled in the art will be able to derive additional related drawings therefrom without the benefit of the inventive faculty.

Fig. 1 is a schematic view illustrating a scenario of a task access method provided by an embodiment of the present disclosure;

FIG. 2 is a flow chart illustrating a task access method provided by an embodiment of the present disclosure;

FIG. 3 is a flow chart illustrating another task access method provided by an embodiment of the present disclosure;

FIG. 4 is a diagram illustrating one example of a task access device provided by an embodiment of the present disclosure;

fig. 5 shows a second schematic diagram of a task access device provided in the embodiment of the present disclosure;

fig. 6 shows a schematic diagram of an electronic device provided by an embodiment of the present disclosure.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present disclosure more clear, the technical solutions of the embodiments of the present disclosure will be described clearly and completely with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, not all of the embodiments. The components of the embodiments of the present disclosure, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present disclosure, presented in the figures, is not intended to limit the scope of the claimed disclosure, but is merely representative of selected embodiments of the disclosure. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the disclosure without making creative efforts, shall fall within the protection scope of the disclosure.

It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined or explained in subsequent figures.

The term "and/or" herein merely describes an associative relationship, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the term "at least one" herein means any one of a plurality or any combination of at least two of a plurality, for example, including at least one of A, B, C, and may mean including any one or more elements selected from the group consisting of A, B and C.

In the application development process, in the existing implementation method for accessing and joint debugging of tasks in a container in the industry, a common mode is to operate locally, and joint debugging can be implemented only by selecting and designating a local port number. However, when application development is complex, a team of multiple persons is mostly needed to perform the application development, and a cross-region remote call, such as a call between a front end and a back end, is faced at this time. In order to access the task in the container, after the container is started, a user needs to repeatedly search the container address, the port number and other information corresponding to the container, the task and the like to realize access configuration, the workload is large, the development cost is high, in addition, after the container is refreshed or restarted, relevant information corresponding to the task in the container possibly changes, so that the user needs to re-determine the current task information corresponding to the task in the current container, the operation is complex, for the changed task information, the user also needs to correspondingly adjust and modify the bottom layer code, a large amount of time is consumed, and the development speed of the user is influenced.

Based on this, the disclosed embodiment provides a task access method, after a container is started, a remote call service is run in the container to generate an access port of the remote call service, thereby realizing the mapping relation between the access port and the task port corresponding to each task operated in the container, after the two containers are connected in a communication mode, a task in any one container can initiate a joint debugging access request to a task in the other container through the communication connection, thereby generating a joint call access link between the two tasks based on the remote call service running in each container and the port access mapping configuration information between the two tasks indicated by the joint call access request to realize the access and call between the tasks, the method can quickly realize access among tasks in different containers, is simple and convenient to operate, saves time, has strong universality and is beneficial to improving the use convenience of users.

The defects existing in the above solutions and the proposed solutions are the results obtained after the inventor has made practice and careful study, therefore, the discovery process of the above problems and the solutions proposed by the present disclosure in the following problems should be the contribution of the inventor to the present disclosure in the process of the present disclosure.

To facilitate understanding of the present embodiment, first, a task access method disclosed in the embodiments of the present disclosure is described in detail, where an execution main body of the task access method provided in the embodiments of the present disclosure may be a task access device, for example, the task access method may be executed by a terminal device, a server, or other processing devices, where the terminal device may be a User Equipment (UE), a mobile device, a User terminal, a computing device, and the like. In some possible implementations, the task access method may be implemented by a processor calling computer readable instructions stored in a memory.

The following describes a task access method provided by the embodiments of the present disclosure.

Referring to fig. 1, fig. 1 is a schematic view of a scenario of a task access method according to an embodiment of the present disclosure. The scene is mainly communication connection between containers, and for two containers after connection communication is established, tasks in each container can be mutually called. As shown in fig. 1, a user may develop a container by means of an integrated development environment IDE, which may include a server and a user terminal, and it is understood that the server and the terminal are communicatively connected, it should be noted that at least one container may be generated in the server, and at least one container may also be generated in the user terminal, where 3 containers in the figure are merely examples, at least one task may run in each container, and the task in each container corresponds to a respective task port.

Further, when a user develops at a user terminal, after the container is started, the container can run a remote call service, and then an access port of the remote call service is generated, so that the access port can be exposed to other containers, and the other containers can establish communication connection with the container. In addition, a mapping relationship between the access port and each task port may also be generated. In the case that the two containers establish communication connection, a task in any one container can initiate a joint debugging access request to a task in the other container through the communication connection, so that calling between the tasks is realized.

For example, after the container a and the container B establish a communication connection, a task a in the container a may initiate a joint call access request to a task B in the container B through the communication connection, where the joint call access request carries specific port access mapping configuration information, and at this time, based on a remote call service operated by the container a, a remote call service operated by the container B, and the port access mapping configuration information, a joint call access link between the task a and the task B may be generated, thereby implementing access call of the task a to the task B. Similarly, the task in container B may also initiate a joint access request to the task in container a through the communication connection.

The embodiment of the disclosure can enable a container developed by a user to be communicated with the designated ports of a plurality of other containers in a form of embedding plug-ins and the like in an integrated development environment IDE, and all the communicated containers can map the access ports to the local host port, so that other containers can be accessed through the local host port, and the development experience completely consistent with the local is realized.

Referring to fig. 2, fig. 2 is a flowchart of a task access method according to an embodiment of the present disclosure, and it can be understood that the method shown in fig. 2 can be applied to the terminal device in fig. 1. As shown in fig. 2, a task access method provided by an embodiment of the present disclosure includes:

s201: and running a first container, wherein a first target task and a first remote calling service run in the first container.

In this step, after it is detected that a first container is operated, at least one first task may be operated in the first container, where the at least one first task includes a first target task, the first target task is a first task that subsequently initiates a joint call access request to another task, and a first remote invocation service is operated in the first container.

It should be noted that each container may run its own remote invocation service after it is started. The remote call (secure shell, shell) service is executed by a secure shell protocol, is specially used for providing a secure call service for a remote login session and other network services, can effectively prevent data in a transmission process from being intercepted, and guarantees data security.

Specifically, in some possible embodiments, the running a first container in which a first target task and a first remote invocation service are running includes:

In this step, after a first container is started, a first remote invocation service is started in the first container, at this time, a first access port of the first remote invocation service may be generated, and a first connection key for connecting to the first access port may be generated at the same time, and further, the first connection key and the first access port may be exposed so that other containers except the first container in the integrated development environment IDE may be connected to the first container through the first connection key and the first access port.

Here, the first connection key may be randomly generated, may be generated based on a container characteristic of the first container, may be set by a user of the first container, and is not limited herein.

Optionally, the first connection key and the first access port may be uploaded to a cloud-side database and/or a server database in the IDE for lookup and use by users of other containers.

After the first container is started, the first task may be pulled up in the first container, and it may be understood that at least one first task is executed in the first container, the at least one first task includes the first target task, and a first connection mapping between the first access port and a task port of each first task may be generated. Any first task may be queried and/or connected through the first access port and the first connection map for other containers to establish a connection with the first container.

Here, based on the first connection mapping corresponding to the first remote call service, the first access port may be mapped to a task port of each first task of the first container, and when the first task is subsequently accessed and called through the first access port, a development process consistent with local development may be implemented, which avoids a user modifying a code, is simple and convenient to operate, and improves development convenience of the user.

It should be noted that, in order to facilitate call access between subsequent tasks, the task information of the first task may be stored in a database, where the task information of the first task includes, but is not limited to, a task name, a task identifier, a task port, a user name, a team name, a code warehouse, a node where the first container is located, and the like.

S202: establishing a communication connection between the first container and a second container remotely co-tuned to the first container.

In practical applications, if a task in a certain container is to be associated with a task in another container, first, two containers need to be communicatively connected.

That is, if the first target task in the first container is to be associated with the second target task in the second container, first, the first container and the second container need to establish a communication connection.

It will be appreciated that a first remote invocation service may be executed in the first container to generate a first access port for the first remote invocation service, and the first access port may be exposed to a container other than the first container, such that the first access port may be used by the first container to establish a communication connection with a container other than the first container, and similarly, a second remote invocation service may be executed in the second container to generate a second access port for the second remote invocation service, such that the second access port may be exposed to a container other than the second container, such that the second access port may be used by the second container to establish a communication connection with a container other than the second container. Meanwhile, the first container and the second container also respectively have a first task port and a second task port which originally exist, and the first task port and the second task port can also be used for establishing communication connection between the containers.

Therefore, the method for establishing a communication connection between the first container and the second container may be based on the first access port of the first container and the second access port of the second container, may be based on the first access port of the first container and the second task port of the second container, may be based on the first task port of the first container and the second access port of the second container, and may be based on the first task port of the first container and the second task port of the second container.

Accordingly, for a method of establishing based on the second access port of the second container, in some possible embodiments, the establishing a communication connection between the first container and a second container remotely co-tuned with the first container:

Based on the above analysis, after the remote invocation service is started, each container generates a corresponding access port and a connection key for connecting the access port, and uploads the access port and the connection key to the database for storage. Therefore, for a second container to be remotely co-tuned with the first container, a second access port and a second connection key of a second remote call service in the second container may be queried from a database, so that the second access port and the first access port or the first task port of the first container are connected by using the connection key based on the second access port and the second connection key, thereby establishing a communication connection between the first container and the second container.

If the first target task in the first container is to be jointly adjusted with the second target task in the second container, first, the first container and the second container need to establish communication connection. After the communication connection between the first container and the second container is established, a first target task in the first container may initiate an associative modulation access request to any second task in the second container through the communication connection, and for this purpose, a second target task that is associative-modulated with the first target task needs to be determined from at least one second task.

Accordingly, in some possible embodiments, after establishing a communication connection between the first container and a second container remotely co-tuned to the first container, the second target task is determined by:

In this step, based on the second access port and the second connection key, the second container may be connected to, and further, at least one active port running in the second container may be obtained, where the active port is a task port of a second task in a running state in the second container, and the at least one active port is displayed to a user.

Optionally, a user development interface may be displayed on the user terminal, and at least one active port is listed in the user development interface so that the user can determine a target port from the at least one active port.

Here, in order to facilitate the user to determine the target port, task information of the second task corresponding to each active port may be displayed together.

Then, whether a preset operation of the user for the at least one active port is received or not may be detected in real time, where the preset operation may be that the user selects a target port from the at least one active port, and in a case that it is determined that the preset operation of the user is received, the target port may be obtained in response to the preset operation, so that a second task corresponding to the target port is determined as a second target task to be accessed.

In this embodiment, the task port of the second task in the running state in the second container is displayed, and the user selects the second target task from the task port, and in practical applications, there is also a case where the second target task to be called is a task in a non-running state, or a case where the task port corresponding to the second target task to be called is not displayed, and at this time, the user needs to manually add the second target task.

It should be noted that, in order to facilitate call access between subsequent tasks, task information of the second task may be stored in the database, where the task information of the second task includes, but is not limited to, a task name, a task identifier, a task port, a user name, a team name, a code repository, a node where the second container is located, and the like.

Accordingly, in some possible embodiments, the second target task is determined by:

In this step, an input operation of the user may be received, specifically, an input container and an input port input by the user are determined according to the input operation of the user, where the second task corresponding to the input port includes a task in an operating state and a task in a non-operating state, and then the input container may be determined as a second container remotely associated with the first container, and the second task corresponding to the input port is determined as a second target task to be accessed, so as to perform subsequent association between the first target task and the second target task.

S203: and in response to a joint debugging access request initiated through the communication connection, generating a joint debugging access link between the first target task and the second target task based on the first remote calling service, the second remote calling service operated by the second container and port access mapping configuration information indicated by the joint debugging access request and between the first target task and the second target task operated by the second container.

In this step, when a communication connection is established between the first container and the second container, the first target task executed by the first container may initiate a joint debugging access request to the second target task executed by the second container through the communication connection, and the second target task may also initiate a joint debugging access request to the first target task through the communication connection, where, to clarify a data flow direction of the joint debugging access request, the joint debugging access request carries port access mapping configuration information between the first target task and the second target task, the port access mapping configuration information indicates a data flow direction of the joint debugging access request, so that the port access mapping configuration information indicated by the joint debugging access request may be based on the first remote invocation service, the second remote invocation service, and the port access mapping configuration information indicated by the joint debugging access request, and generating a joint debugging access link between the first target task and the second target task.

Optionally, the port access mapping configuration information may be automatically generated, or may be set by a user, which is not limited herein.

For example, if the port access mapping configuration information is automatically generated, the port access mapping configuration information may be > portA: portA, which indicates that the portA port of the other party is mapped to the current container. If the port access mapping configuration information is set by the user, the port access mapping configuration information may be > portA: portB, which indicates that the current container will access the portB port of the opposite container through the portA port, and the port access mapping configuration information may also be < portA: portB, which indicates that the opposite container will access the portB port of the current container through the portA port.

Here, since the first container already runs the first remote invocation service and generates the first connection mapping between the first access port and the task port of the first target task, the first target task can be quickly located from at least one first task in the first container, and similarly, the second container can also obtain the second connection mapping between the second access port and the task port of the second target task in the same manner, thereby forming the bidirectional mapping between the first target task and the second target task.

Specifically, in some possible embodiments, the generating, in response to a joint call access request initiated through the communication connection, a joint call access link between the first target task and the second target task based on the first remote call service, the second remote call service executed by the second container, and port access mapping configuration information indicated by the joint call access request and between the first target task and the second target task executed by the second container includes:

In this step, after receiving a joint debugging access request initiated through the communication connection, a second connection map corresponding to a second remote invocation service run by the second container may be obtained, where the second connection map includes a mapping relationship between a task port of each second task and a second access port of the second remote invocation service, so that the second target task may be quickly located from at least one second task in the second container, and then a joint debugging channel between the first container and the second container is established based on the first connection map and the second connection map corresponding to the first remote invocation service, where the joint debugging channel represents a bidirectional mapping between each first task and each second task.

Here, based on the second connection mapping corresponding to the second remote invocation service, the second access port may be mapped to the task port of each second task of the second container, and when subsequently accessing and invoking the second task through the second access port, a development process consistent with local development may be implemented, which avoids a user modifying a code, is simple and convenient to operate, and improves development convenience of the user.

And then, a joint debugging access link between the first target task and the second target task can be generated through the joint debugging channel and port access mapping configuration information between the first target task and the second target task, which is indicated by the joint debugging access request.

It is to be understood that the coherent modulation channel is established based on the first access port and the second access port, and therefore, if the previous communication connection between the first container and the second container is established based on the first access port and the second access port, the coherent modulation access link is generated without repeatedly establishing the coherent modulation channel, and only the first target task and the second target task need to be determined through the first connection map and the second connection map; if the communication connection between the first container and the second container is established based on the first access port and the second access port, the joint debugging channel needs to be established and generated based on the first access port and the second access port, and then the joint debugging access link is generated.

In some possible embodiments, in a case that the second target task is a task in a non-running state, it is not possible to generate a joint debugging access link between the first target task and the second target task, and in a case that the second target task is running, it is necessary to generate the joint debugging access link between the first target task and the second target task based on the first remote call service, the second remote call service run by the second container, and the port access mapping configuration information between the first target task and the second target task run by the second container, which is indicated by the joint debugging access request.

The task access method provided by the embodiment of the disclosure runs the remote call service in the container after the container is started to generate the access port of the remote call service, thereby realizing the mapping relation between the access port and the task port corresponding to each task operated in the container, after the two containers are connected in a communication mode, a task in any one container can initiate a joint debugging access request to a task in the other container through the communication connection, thereby generating a joint call access link between the two tasks based on the remote call service running in each container and the port access mapping configuration information between the two tasks indicated by the joint call access request to realize the access and call between the tasks, the method can quickly realize access among tasks in different containers, is simple and convenient to operate, saves time, has strong universality and is beneficial to improving the use convenience of users.

Referring to fig. 3, fig. 3 is a flowchart of another task access method according to an embodiment of the disclosure. As shown in fig. 3, a task access method provided by the embodiment of the present disclosure includes:

s301: and running a first container, wherein a first target task and a first remote calling service run in the first container.

S302: establishing a communication connection between the first container and a second container remotely co-tuned to the first container.

S303: and in response to a joint debugging access request initiated through the communication connection, generating a joint debugging access link between the first target task and the second target task based on the first remote calling service, the second remote calling service operated by the second container and port access mapping configuration information indicated by the joint debugging access request and between the first target task and the second target task operated by the second container.

The descriptions of step S301 to step S303 may refer to the descriptions of step S201 to step S203, and the same technical effect and the same technical problem may be achieved, which are not described herein again.

S304: and storing the port access mapping configuration information, the task information of the first target task and the task information of the second target task.

In this step, after the joint debugging access link is generated, the port access mapping configuration information indicated by the joint debugging access request, and the task information of the first target task and the task information of the second target task corresponding to the joint debugging access link may be uploaded to a database.

S305: after the second container is disconnected and communication connection is established with the first container again, updating a joint debugging access link between the first target task and the second target task based on the port access mapping configuration information, the task information of the first target task and the task information of the second target task, and the first remote calling service and the second remote calling service.

In this step, after the first container and the second container are disconnected due to restart or refresh of the first container and/or the second container, in order to ensure stability and integrity of task access, the second container may establish communication connection with the first container again, and then regenerate a joint debugging access link between the first target task and the second target task based on the port access mapping configuration information, the task information of the first target task and the task information of the second target task, and the first remote invocation service and the second remote invocation service.

Specifically, in some possible embodiments, after the second container is disconnected, the communication connection is established again with the first container by the following steps:

Based on the above analysis, it can be known that each container uploads the access port of its respective container and task information of tasks in the container to the database for storage, so that based on the task information of the second target task, the second access port of the second container may be queried from the database, and further based on the second access port, the first container and the second container are controlled to establish a communication connection again.

For example, the second access port to the second container may be queried from a database based on a task identity indicated by the task information of the second target task.

It may be understood that, after the second container and the first container are re-established with each other to establish a communication connection, based on the first connection mapping and the second connection mapping corresponding to the first remote invocation service, the joint debugging channel between the first container and the second container may be re-established, and then the joint debugging access link between the first target task and the second target task is updated through the re-established joint debugging channel and the stored port access mapping rule, the task information of the first target task, and the task information of the second target task.

The task access method provided by the embodiment of the disclosure can run the remote call service in the container after the container is started to generate the access port of the remote call service, thereby realizing the mapping relation between the access port and the task port corresponding to each task operated in the container, after the two containers are connected in a communication mode, a task in any one container can initiate a joint debugging access request to a task in the other container through the communication connection, thereby generating a joint debugging access link between two tasks based on the remote calling service operated in each container and the port access mapping configuration information between the two tasks indicated by the joint debugging access request so as to realize the access and the calling between the tasks, the method can quickly realize access among tasks in different containers, is simple and convenient to operate, saves time, has strong universality and is beneficial to improving the use convenience of users.

Furthermore, under the condition that communication connection between two containers is interrupted due to container refreshing or restarting and the like, the communication connection between the containers can be realized again based on the stored task information, and then a joint debugging access link between the two tasks is updated, so that the method is convenient and fast, a user does not need to re-determine the current task information, the workload of code modification is reduced, and the development speed of the user is improved.

It will be understood by those of skill in the art that in the above method of the present embodiment, the order of writing the steps does not imply a strict order of execution and does not impose any limitations on the implementation, as the order of execution of the steps should be determined by their function and possibly inherent logic.

Based on the same inventive concept, a task access device corresponding to the task access method is also provided in the embodiments of the present disclosure, and as the principle of solving the problem of the device in the embodiments of the present disclosure is similar to the task access method described above in the embodiments of the present disclosure, the implementation of the device may refer to the implementation of the method, and repeated details are not described again.

Referring to fig. 4 and 5, fig. 4 is a first schematic diagram of a task access device according to an embodiment of the disclosure, and fig. 5 is a second schematic diagram of a task access device according to an embodiment of the disclosure.

As shown in fig. 4, a task access device 400 provided by an embodiment of the present disclosure includes:

a container operation module 410, configured to operate a first container, where a first target task and a first remote invocation service are operated in the first container;

a connection establishing module 420, configured to establish a communication connection between the first container and a second container remotely associated with the first container;

a first link generating module 430, configured to generate, in response to a joint call access request initiated through the communication connection, a joint call access link between the first target task and the second target task based on the first remote call service, the second remote call service executed by the second container, and port access mapping configuration information between the first target task and the second target task executed by the second container, where the port access mapping configuration information is indicated by the joint call access request.

In an optional implementation manner, as shown in fig. 5, the apparatus further includes a second link generating module 440, where the second link generating module 440 is configured to:

after the second container is disconnected and communication connection with the first container is established again, updating a joint debugging access link between the first target task and the second target task based on the port access mapping configuration information, the target task information of the first task and the task information of the second target task, and the first remote calling service and the second remote calling service.

In an optional implementation manner, when the second link generating module 440 is configured to establish a communication connection with the first container again after the second container is disconnected, specifically, to:

In an alternative embodiment, the container operation module 410 is specifically configured to:

In an optional implementation manner, the first link generating module 430 is specifically configured to:

In an optional implementation manner, the connection establishing module 420 is specifically configured to:

In an alternative embodiment, as shown in fig. 5, the apparatus further includes a task determination module 450, and the task determination module 450 is configured to:

In an optional implementation manner, the task determining module 450 is specifically configured to:

In an optional implementation manner, in a case that the second target task is a task in a non-running state, the first link generating module 430 is specifically configured to, when the first link generating module is configured to generate the joint access link between the first target task and the second target task based on the first remote invocation service, the second remote invocation service run by the second container, and the port access mapping configuration information between the first target task and the second target task run by the second container, which is indicated by the joint access request, specifically:

The description of the processing flow of each module in the device and the interaction flow between the modules may refer to the related description in the above method embodiments, and will not be described in detail here.

The task access device provided by the embodiment of the disclosure runs the remote call service in the container after the container is started to generate the access port of the remote call service, thereby realizing the mapping relation between the access port and the task port corresponding to each task operated in the container, after the two containers are connected in a communication mode, a task in any one container can initiate a joint debugging access request to a task in the other container through the communication connection, thereby generating a joint call access link between the two tasks based on the remote call service running in each container and the port access mapping configuration information between the two tasks indicated by the joint call access request to realize the access and call between the tasks, the method can quickly realize access among tasks in different containers, is simple and convenient to operate, saves time, has strong universality and is beneficial to improving the use convenience of users.

Corresponding to the task access method in fig. 2 and fig. 3, an embodiment of the present disclosure further provides an electronic device 600, as shown in fig. 6, a schematic structural diagram of the electronic device 600 provided in the embodiment of the present disclosure includes:

a processor 610, a memory 620, and a bus 630; the storage 620 is used for storing execution instructions and includes a memory 621 and an external storage 622; the memory 621 is also referred to as an internal memory, and is used for temporarily storing operation data in the processor 610 and data exchanged with an external memory 622 such as a hard disk, the processor 610 exchanges data with the external memory 622 through the memory 621, and when the electronic device 600 operates, the processor 610 and the memory 620 communicate through the bus 630, so that the processor 610 can execute the steps of the task access method.

The embodiments of the present disclosure also provide a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, performs the steps of the task access method described in the above method embodiments. The storage medium may be a volatile or non-volatile computer-readable storage medium.

An embodiment of the present disclosure further provides a computer program product, where the computer program product includes computer instructions, and when the computer instructions are executed by a processor, the steps of the task access method in the foregoing method embodiment may be executed.

The computer program product may be implemented by hardware, software or a combination thereof. In an alternative embodiment, the computer program product is embodied in a computer storage medium, and in another alternative embodiment, the computer program product is embodied in a Software product, such as a Software Development Kit (SDK), or the like.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described apparatuses and devices may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again. In the several embodiments provided in the present disclosure, it should be understood that the disclosed apparatus, device and method may be implemented in other manners. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and there may be other divisions when actually implemented, and for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some communication interfaces, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a non-volatile computer-readable storage medium executable by a processor. Based on such understanding, the technical solutions of the present disclosure, which are essential or part of the technical solutions contributing to the prior art, may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present disclosure. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

Finally, it should be noted that: the above-mentioned embodiments are merely specific embodiments of the present disclosure, which are used for illustrating the technical solutions of the present disclosure and not for limiting the same, and the scope of the present disclosure is not limited thereto, and although the present disclosure is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: those skilled in the art can still make modifications or changes to the embodiments described in the foregoing embodiments, or make equivalent substitutions for some of the technical features, within the technical scope of the disclosure; such modifications, changes or substitutions do not depart from the spirit and scope of the embodiments of the present disclosure, and should be construed as being included therein. Therefore, the protection scope of the present disclosure shall be subject to the protection scope of the claims.

Claims

1. A method for task access, the method comprising:

and in response to a joint debugging access request initiated through the communication connection, generating a joint debugging access link between the first target task and the second target task based on the first remote calling service, the second remote calling service operated by the second container and port access mapping configuration information indicated by the joint debugging access request and between the first target task and the second target task operated by the second container.

2. The method of claim 1, further comprising, after generating the coherent access link between the first target task and the second target task:

after the second container is disconnected and communication connection with the first container is established again, updating a joint debugging access link between the first target task and the second target task based on the port access mapping configuration information, the task information of the first target task and the task information of the second target task, and the first remote calling service and the second remote calling service.

3. The method of claim 2, wherein the communication connection is re-established with the first container after the second container is disconnected by:

4. The method of claim 1, wherein the executing a first container having a first target task and a first remote invocation service running therein comprises:

running at least one first task in the first container, the at least one first task comprising the first target task;

5. The method of claim 4, wherein generating, in response to a joint call access request initiated through the communication connection, a joint call access link between the first target task and the second target task based on the first remote call service, a second remote call service run by the second container, and port access mapping configuration information indicated by the joint call access request and between the first target task and a second target task run by the second container comprises:

6. The method of claim 1, wherein establishing the communicative connection between the first container and a second container remotely co-tuned to the first container:

7. The method of claim 5, wherein the second target task is determined after establishing a communication connection between the first container and a second container remotely co-tuned to the first container by:

8. The method of claim 1, wherein the second target task is determined by:

9. The method according to claim 1, wherein in a case that the second target task is a task in a non-running state, the generating a joint call access link between the first target task and the second target task based on the first remote call service, a second remote call service run by the second container, and port access mapping configuration information indicated by the joint call access request and between the first target task and the second target task run by the second container comprises:

10. A task access apparatus, characterized in that the apparatus comprises:

11. An electronic device, comprising: a processor, a memory and a bus, the memory storing machine-readable instructions executable by the processor, the processor and the memory communicating over the bus when the electronic device is running, the machine-readable instructions when executed by the processor performing the steps of the task access method according to any one of claims 1 to 9.

12. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, performs the steps of the task access method according to any one of claims 1 to 9.