CN114860377A

CN114860377A - Service processing method, device and equipment for container operation and maintenance

Info

Publication number: CN114860377A
Application number: CN202210451771.7A
Authority: CN
Inventors: 张伟
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Alipay Hangzhou Information Technology Co Ltd
Priority date: 2022-04-24
Filing date: 2022-04-24
Publication date: 2022-08-05

Abstract

The embodiment of the specification discloses a service processing method, a device and equipment for container operation and maintenance, and belongs to the technical field of computer operation and maintenance. The scheme comprises the following steps: determining a physical machine corresponding to a target service container; starting a companion container which shares at least part of a naming space with a target service container for the target service container on the physical machine, and configuring resource restriction information for the companion container; acquiring the resource of the associated container under the limitation indicated by the resource limitation information; and displaying an operation and maintenance control interface containing a view in the target service container through interaction between the companion container and the target service container, and executing an operation and maintenance command for the target service container by using the resource.

Description

Service processing method, device and equipment for container operation and maintenance

Technical Field

The present specification relates to the technical field of computer operation and maintenance, and in particular, to a method, an apparatus, and a device for processing a service for container operation and maintenance.

Background

The container is a technology for isolating an application running environment, and is a common docker container under Linux.

Running certain services in an isolated environment provided by containers, referred to as service containers, helps to improve security and to better manage resources for these services. In practical applications, it is often necessary to perform operation and maintenance operations on a service container, and particularly, the operation and maintenance operations are usually performed in the service container to execute an operation and maintenance command, for example, a grep instruction for regular search in Linux, an rpm instruction for a management packet, and the like.

In the current operation and maintenance mode, the operation and maintenance actions for a service container may interfere with the operation of normal services in the service container. For example, if an operation and maintenance person executes an operation and maintenance command that consumes a large amount of memory, the occurrence of insufficient memory in a service container may be triggered, which may cause a service process in the service container to be killed (kill), which may further cause a service application to crash, resulting in a serious result.

Based on this, a more reliable operation and maintenance scheme for the traffic container is needed.

Disclosure of Invention

One or more embodiments of the present specification provide a method, an apparatus, a device, and a storage medium for service processing for container operation and maintenance, so as to solve the following technical problems: a more reliable operation and maintenance solution for the traffic container is needed.

To solve the above technical problem, one or more embodiments of the present specification are implemented as follows:

one or more embodiments of the present specification provide a service processing method for container operation and maintenance, including:

determining a physical machine corresponding to a target service container;

starting a companion container which shares at least part of a naming space with a target service container for the target service container on the physical machine, and configuring resource restriction information for the companion container;

acquiring the resource of the associated container under the limitation indicated by the resource limitation information;

and displaying an operation and maintenance control interface containing a view in the target service container through interaction between the companion container and the target service container, and executing an operation and maintenance command for the target service container by using the resource.

One or more embodiments of the present specification provide a service processing apparatus for container operation and maintenance, including:

the container physical machine determining module is used for determining a physical machine corresponding to the target service container;

a companion container starting configuration module, configured to start, on the physical machine, a companion container that shares at least part of a namespace with a target service container for the target service container, and configure resource restriction information for the companion container;

a resource obtaining module of the companion container, configured to obtain the resource of the companion container under the restriction indicated by the resource restriction information;

and the operation and maintenance control interaction execution module displays an operation and maintenance control interface containing a view in the target service container through interaction between the companion container and the target service container, and executes an operation and maintenance command for the target service container by using the resource.

One or more embodiments of the present specification provide a service processing device for container operation and maintenance, including:

at least one processor; and the number of the first and second groups,

a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,

the memory stores instructions executable by the at least one processor to cause the at least one processor to:

determining a physical machine corresponding to a target service container;

One or more embodiments of the present specification provide a non-transitory computer storage medium storing computer-executable instructions configured to:

determining a physical machine corresponding to a target service container;

At least one technical scheme adopted by one or more embodiments of the specification can achieve the following beneficial effects: on one hand, an available companion container is dynamically provided for a service container, the operation and maintenance command for the service container is executed by using the resource of the companion container without occupying the resource of the service container, and corresponding resource limitation is imposed on the companion container, so that if the operation and maintenance command occupies too much resource, the operation and maintenance command is only influenced under the limitation, and the service process in the service container is not threatened; on the other hand, although the resource of the companion container is utilized, the view in the service container can be switched to through the interaction between the companion container and the service container, the view is displayed in the operation and maintenance control interface, and the operation and maintenance command is executed in the service container, so that the user is prevented from being confused and inconsistent by the view in the companion container, and the interface interaction experience of the user in the operation and maintenance behavior implementation is improved.

Drawings

In order to more clearly illustrate the embodiments of the present specification or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present specification, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative effort.

Fig. 1 is a schematic flowchart of a service processing method for container operation and maintenance according to one or more embodiments of the present disclosure;

FIG. 2 is a schematic flow chart illustrating an embodiment of obtaining and using container resources in an application scenario according to one or more embodiments of the present disclosure;

FIG. 3 is a schematic flow diagram illustrating an embodiment of the method of FIG. 1 in an application scenario according to one or more embodiments of the present disclosure;

fig. 4 is a schematic structural diagram of a service processing apparatus for container operation and maintenance according to one or more embodiments of the present disclosure;

fig. 5 is a schematic structural diagram of a service processing device for container operation and maintenance according to one or more embodiments of the present disclosure.

Detailed Description

The embodiment of the specification provides a service processing method, a device, equipment and a storage medium for container operation and maintenance.

In order to make those skilled in the art better understand the technical solutions in the present specification, the technical solutions in the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without making any inventive step based on the embodiments of the present disclosure, shall fall within the scope of protection of the present application.

In the background art, an example of an operation and maintenance command under Linux is mentioned, and in practical applications, many container operation and maintenance behaviors are performed under Linux, so for better understanding of the present solution, some embodiments below will also use a container operation and maintenance scene under Linux as an example for detailed description.

In one or more embodiments of the present description, kubernets, which is an open-source container cluster orchestration scheduling software, is used. Pod is the smallest unit of scheduling under Kubernetes, and a group of containers share a partial Namespace (Namespace) to constitute a Pod. Initially, consider using a kubecect exec api as an operation and maintenance command channel, on a physical machine node (in a cluster, one node may correspond to one or more physical machines), by calling a docker exec, to enter a service container, and then an operation and maintenance person may execute some operation and maintenance commands, such as yum install, maven install, grep, etc., which may cause the problems mentioned in the background.

Therefore, when an operation and maintenance person executes an operation and maintenance command occupying a lot of resources (such as a memory), the operation and maintenance command is possibly abnormal (such as by kill) at most, and a service process cannot be triggered and is also abnormal, so that the normal operation of the service can be protected, and the service reliability is improved.

Based on such a concept, the following description will be made in further detail.

Fig. 1 is a schematic flowchart of a service processing method for container operation and maintenance according to one or more embodiments of the present disclosure. The method can be applied to different business fields, such as the electric business field, the financial business field, the electronic payment business field, the instant messaging business field, the robot business field, the video service business field, the game business field, the public business field and the like. The process can be executed by computing equipment in the corresponding field (such as an operation and maintenance server corresponding to the e-commerce business, and the like), and certain input parameters or intermediate results in the process allow manual intervention and adjustment to help improve the accuracy.

The process in fig. 1 may include the following steps:

s102: and determining a physical machine corresponding to the target service container.

In one or more embodiments of the present specification, an operation and maintenance person wants to perform a round of operation and maintenance activities on a certain service container, and then the service container is used as a target service container. In a round of operation and maintenance behaviors, an operation and maintenance person can issue one or more operation and maintenance commands, and each operation and maintenance command may correspond to a plurality of specific operation and maintenance operation steps.

A container is a logical concept that requires a physical device to carry, i.e., the physical machine.

The physical machine corresponding to the target service container may include the physical machine where the target service container is located, and the main purpose of step S102 is to interact with the target service container more conveniently based on the physical machine subsequently, so as to assist the operation and maintenance behavior to be completed more efficiently and reliably. Of course, other physical machines capable of achieving the purpose may also be used as the physical machine corresponding to the target service container, for example, other physical machines which belong to the same cluster as the physical machine where the target service container is located and have an available operation and maintenance command channel therebetween, and the like.

S104: and starting a companion container which shares at least part of the naming space with the target service container for the target service container on the physical machine, and configuring resource restriction information for the companion container.

The execution of the operation and maintenance command requires corresponding resources, and the memory is one of basic resources, and in addition, may also require other resources such as a processor, a network bandwidth, a time slot, a token, and the like.

In one or more embodiments of the present description, the resources required to execute the operation and maintenance command are provided by the container, but not by the target traffic container itself, but by a companion container of the target traffic container. The companion container and the service container corresponding to the companion container run in the same minimum scheduling unit, share part or all of the namespace, and are used for assisting the service container to execute some operations.

For the present solution, the operation and maintenance command may be executed through a corresponding process, in which case, the resource restriction configuration may be specifically used to restrict resources required by the process, and in addition, the target service container and the companion container may be interacted subsequently through the process. The flexible use of the process can help the scheme to be better realized, and based on this, the target service container can start a namespace, such as a Process Identification (PID) namespace, related to at least a shared process with the companion container, so as to prevent the process from being isolated between the two, and besides, the target service container can also share other types of namespaces, such as a network namespace, a user namespace, and the like, for the two according to requirements.

The companion container and the corresponding service container respectively have independent resources which can be used for executing the operation and maintenance command. Under the resource support of the companion container, the operation and maintenance command does not need to occupy the resource of the target service container, thereby preventing threatening the resource requirement of normal service operation in the target service container.

The companion container may be started with the corresponding service container, with the life cycles of the two being consistent for better coordination of work. However, in one or more embodiments of the present specification, the companion container is dynamically triggered and started by an operation and maintenance command to be executed, after the operation and maintenance command or the operation and maintenance action is finished, the companion container is disabled, and a valid and available companion container is obtained again when the companion container needs to be used next time, so that resources of the companion container can be released in time and pressure on the entire system can be reduced by such a "disposable" flexible and dynamic processing manner; furthermore, it helps to reduce the risk of attacking traffic containers indirectly through companion containers.

It should be noted that, in the above paragraph, it is emphasized that, after the phased operation and maintenance is finished, automatic intervention is performed in time to reduce the influence of the companion container on the whole system. In actual implementation, the appropriate specific intervention time and intervention means are selected according to requirements. For example, whether the current round of operation and maintenance behavior is ended or not may be determined according to the operation and maintenance management and control interface, and if it is detected that the user closes the corresponding container inside view or clicks a control for explicitly confirming the ending of the operation and maintenance behavior in the operation and maintenance management and control interface, the ending may be determined, and then, automatic intervention may be performed in time, for example, automatically converting the companion container into a non-running state, or automatically deleting the companion container, and the like.

In one or more embodiments of the present description, use of resources of a companion container is restricted by configuring resource restriction information for the companion container.

And particularly, the scenario of the scheme can at least limit the operation and maintenance command from excessively using and even exploding the resources of the companion container. If the resources of the companion container are basically all provided for the operation and maintenance command, the specific content of the resource restriction information may be relatively simply set, for example, defined as 1-core 500M memory, and the resources that can be obtained by the operation and maintenance command may not exceed 1-core 500M memory. Of course, according to actual needs, resource limitations may also be set at a finer granularity, for example, how much memory is maximally occupied by operation and maintenance operation steps of a specified type, how much memory is maximally occupied by a process for interacting with a target service container according to an operation and maintenance command, a maximum allowable thread number for serving an operation and maintenance instruction, and the like.

S106: and acquiring the resources of the companion container under the limitation indicated by the resource limitation information.

In one or more embodiments of the present specification, after the operation and maintenance personnel issue the operation and maintenance command, the operation and maintenance personnel acquires the resource of the companion container according to the operation and maintenance command, so as to execute the operation and maintenance command. The restriction indicated by the resource restriction information is also effective in the execution process of the operation and maintenance command, in the execution process, the resource occupied by the operation and maintenance command may be dynamically changed, and if the resource is changed to break through the restriction, the operation and maintenance command may be restricted or even terminated by the companion container, so that the operation of the service container is not affected.

Specifically, for example, no matter before the operation and maintenance command is executed, the resource of the companion container is prefetched, or the resource of the companion container is dynamically acquired in the execution process, the companion container may monitor the operation and maintenance command according to the resource restriction information, and determine whether the resource required by the operation and maintenance command to be executed or being executed will or will not cause the restriction indicated by the resource restriction information to be broken through, if so, corresponding defense measures may be taken in time to protect the service operation in the target service container, for example, the companion container is suspended to wait for allocation and use of redundant resources, and then the operation and maintenance command is restarted, or the operation and maintenance command is directly terminated, so as to preferentially guarantee the service.

S108: and displaying an operation and maintenance control interface containing a view in the target service container through interaction between the companion container and the target service container, and executing an operation and maintenance command for the target service container by using the resource.

In one or more embodiments of the present specification, an operation and maintenance management and control interface of the target service container is displayed according to the companion container and the resource, and an operation and maintenance command for the target service container is executed. For example, in the companion container, the operation and maintenance command is started and interacted with the target service container by using the above-mentioned resource, the operation and maintenance command is executed in the target service container by using the resource again, and the view can be automatically switched from the companion container to the target service container.

Operation and maintenance personnel issue operation and maintenance commands through an operation and maintenance control interface, and consider that the operation and maintenance commands aiming at the target service container are directly executed in the associated container, so that not only is the resources of the target service container not occupied, but also the environment of the target service container is not occupied, and the reliability is higher. However, this solution also has a problem in that the operation and maintenance command is directly executed in the companion container, and the operation and maintenance personnel can see the root directory file and the execution environment of the companion container in the operation and maintenance management and control interface. The operation and maintenance object is a target service container, and in this case, a confusing and inconsistent experience is caused to the user.

The scheme is further improved in view of the problems of the previous paragraph. The operation and maintenance command can not be executed in the associated container, the associated container is mostly responsible for starting the operation and maintenance command, the actual operation and maintenance command is executed in the target service container, in order to improve the consistency experience of the user, the associated container and the target service container can interact, the view is switched into the target service container, then, the operation and maintenance management and control interface is convenient for the operation and maintenance personnel to see the data and the environment which are directly operated, and the interaction experience is better.

More specifically, the specific content (referred to as target content) presented in the above-described view is determined according to the demand. More critical content, such as a root file system, may be preferentially displayed, and in addition, if desired, other content, such as at least a portion of the namespace, may be displayed.

Through the method of fig. 1, on one hand, an available companion container is dynamically provided for a service container, an operation and maintenance command for the service container is executed by using resources of the companion container without occupying resources of the service container, and a corresponding resource restriction is imposed on the companion container, so that if the operation and maintenance command occupies too many resources, only the operation and maintenance command itself is affected under the restriction without threatening a service process in the service container; on the other hand, although the resource of the companion container is utilized, the view in the service container can be switched through the interaction between the companion container and the service container, the view is displayed in the operation and maintenance control interface, and the operation and maintenance command is executed in the service container, so that the user is prevented from being confused and inconsistent by the view in the companion container, and the interface interaction experience of the user in the operation and maintenance behavior implementation is improved.

Based on the process of fig. 1, some specific embodiments and embodiments of the process are also provided in the present specification, and the description is continued below.

In one or more embodiments of the present specification, it has been mentioned above that the present solution is intended to use the resources of the companion container to execute the operation and maintenance command, but it is considered that in some application scenarios, if only the companion container is used to serve the operation and maintenance command, it is not appropriate to allocate or reserve too many resources for the companion container, because in practical applications, the specific operations in a round of operation and maintenance activities are not necessarily compact and timely, and there may even be a long idle waiting time, in which case some resources may be occupied by the companion container for a long time without effective use.

Based on this, it is considered that the associated container is used as a main part, and the target service container is used as an auxiliary part to guarantee resources for the operation and maintenance command, so as to help reduce resources occupied by the associated container and make full use of idle resources.

More intuitively, based on the idea in the previous paragraph, one or more embodiments of the present specification provide a flow chart of a specific implementation of acquiring and using container resources in an application scenario, as shown in fig. 2.

The flow of fig. 2 may include the following steps:

s202: and decomposing the operation and maintenance command to be executed into a first operation and maintenance sub-command set and a second operation and maintenance sub-command set.

In one or more embodiments of the present specification, the operation and maintenance subcommands have an execution order, and the execution order of the first operation and maintenance subcommand set precedes the execution order of the second operation and maintenance subcommand set.

S204: and acquiring the resource of the companion container for executing the first operation and maintenance sub-command set, and applying for the resource for executing the second operation and maintenance sub-command set from the target service container.

In one or more embodiments of the present description, the first operation and maintenance subcommand set may be planned to be relatively small (occupying relatively few resources), and the resource provisioning capability of the companion container may be explored first. The resource needed for executing the first operation and maintenance sub-command set is less than the resource needed for completely executing the operation and maintenance command, and the step-by-step requirement on the resource is more clear and specific by decomposing the operation and maintenance command instead of requesting sufficient or even excessive resource aiming at the whole operation and maintenance command, so that the resource allocation pressure is reduced.

S206: if the application is successful, after the first operation and maintenance subcommand set is executed, the resource of the companion container is utilized to continue executing the second operation and maintenance subcommand set, and the termination risk of terminating the operation and maintenance command based on the resource limit information is monitored.

In one or more embodiments of the present specification, even after the application is successful, the target service container may temporarily not allocate the resource that the application of the other party is successful, but waits for reallocation when the other party actually uses the resource, that is, the part of the resource is kept in the hands of the other party as much as possible, and may be temporarily used for service operation, so that disturbance to the service can be reduced as much as possible.

In the process of operating the second operation and maintenance subcommand set, the resource requirement changes, so that the resource limitation may be broken through, and the termination risk reflects the risk that the resource limitation is broken through.

S208: and if the termination risk is greater than a set threshold value, acquiring the resource applied from the target service container for executing the unexecuted part in the second operation and maintenance subcommand set.

In one or more embodiments of the present description, if the termination risk is greater than the set threshold, this means that the resources of the companion container alone may not be sufficient to support the continued execution of the second operation and maintenance subcommand set. And if the result is negative, the target service container can detect whether the target service container is suitable for providing the part of resources currently, and if the result is negative, the target service container can refuse to provide the resources even if the previous application is successful, so that the service is guaranteed preferentially.

According to a similar idea, the operation and maintenance command can be decomposed into more subsets, so that the resource contradiction is buffered, and more resource coordination space is provided between the associated container and the target service container.

Through the scheme in fig. 2, on the premise that the associated container is enabled, the resources of the target service container are released, but the resources of the target service container are used as auxiliary candidates in an emergency without being completely released, and the additional influence of the auxiliary candidates on the target service container is reduced as much as possible by dividing the resource requirements in stages at a fine granularity, so that the experiences of normal services and operation and maintenance personnel are taken into consideration, and the container resources are utilized more fully.

In one or more embodiments of the present specification, in the above case, the target service container and the companion container not only share a namespace, but also have a partially collaborative scenario in resources. For the operation and maintenance personnel, the instantaneous relationship and cooperation between two containers may need to be mastered, and then if only the view in the target service container is available, the operation and maintenance personnel can only master the relevant conditions of the result, but the data of the cause and the process are not well known, which is not beneficial to finding and locating the relevant problems generated in the operation and maintenance process. To solve this problem, the relationship between the two can be presented on the interface in time.

Specifically, for example, a view of the target content in the associated container is acquired, a mapping relationship between the target content in the target service container and the target content in the associated container is established according to the acquired view, a corresponding mapping relationship view is generated, and the mapping relationship view is displayed and dynamically updated in a current default operation and maintenance management and control interface. Taking resources as an example, when a target service container intervenes to perform resource assistance, mapping resources of an associated container used for partially executing the second operation and maintenance sub-command set with resources successfully applied from the target service container in time so as to dynamically reflect real-time resource pressure borne by the two containers in response to operation and maintenance behaviors.

In one or more embodiments of the present specification, the operation and maintenance manager often operates the physical machine corresponding to the target service container through another device, and in order to better interface with the operation and maintenance manager, a special agent may be constructed on the physical machine, and is configured to receive, forward, process, or respond to an operation and maintenance command issued by the operation and maintenance manager, and to uniformly manage the companion container. Based on such a concept, one or more embodiments of the present disclosure provide a flowchart and an architecture diagram of a specific implementation of the method in fig. 1 in an application scenario, as shown in fig. 3.

In fig. 3, the corresponding physical machine is a physical machine where the target service container is located. The operation and maintenance management and control interface is, for example, a web user interaction interface, and is displayed on certain operation and maintenance equipment outside the physical machine for operation of operation and maintenance personnel, and an operation and maintenance agent is arranged on the physical machine, and the operation and maintenance management and control interface can establish an operation and maintenance command channel with the operation and maintenance agent. Based on the scheme, in a round of operation and maintenance behaviors, the framework can work in the following mode.

The operation and maintenance personnel operate to enable the operation and maintenance equipment to display a current default operation and maintenance management and control interface, on the default interface, the operation and maintenance personnel can specify a target service container which the operation and maintenance personnel want to operate, and at the moment, some specific views in the target service container cannot be displayed on the interface, such as views of contents such as a root file system, a name space and the like. The operation and maintenance personnel issues operation and maintenance commands for the target service container through the interface, specifically, the operation and maintenance commands are represented as instructions for the target service container to execute programs in directories such as/bin,/bash and the like.

And the operation and maintenance agent on the physical machine receives the operation and maintenance command through the operation and maintenance command channel. Then, the operation and maintenance agent may pull up the dynamic companion container for the target service container through the docker run command, so that the companion container and the target service container may share all namespaces. Resource restriction information is provided for an associated container individually, which herein individually means: the companion container has the resource, the resource does not belong to the target service container, and the use of the resource is limited, and the limitation does not directly act on the target service container.

After the associated container is started, operation and maintenance personnel can check the view in the associated container through the operation and maintenance control interface, and in consideration of better experience, the associated container can start an operation and maintenance command, acquire resources of the associated container for the operation and maintenance command to be executed, automatically start a set inter-container access program, and access the target service container from the associated container through the inter-container access program to acquire the view of target content (such as a root file system, a name space and the like) in the target service container, so that the view in the associated container is switched to the view in the target service container through the operation and maintenance control interface. If the resource needed by the operation and maintenance command is judged to break through the limit, the operation and maintenance command can be directly terminated.

Under the view in the target service container, the operation and maintenance command is actually executed in the target service container by using the resources of the companion container, and in the execution process, if the risk of resource breakthrough limitation occurs, the operation and maintenance command can also be directly terminated.

Through the scheme in fig. 3, based on the dynamic companion container, a resource limitation is explicitly added to the operation and maintenance command to limit the operation and maintenance command to take the inverse customers as the main resources and unreasonably seize too many resources, and furthermore, an inter-container access program is used for timely switching the view of the target content between containers to achieve the expectation of visual feedback of the operation and maintenance personnel on the operation target service container. The final achieved effects include: in terms of user experience, operation and maintenance personnel see the view of the target service container, which is obtained as seen, so that the next operation and maintenance behavior is facilitated, and meanwhile, resources consumed by all the operation and maintenance behaviors are controllable, so that a normal service process cannot be damaged due to resource breakthrough limitation, and the overall reliability of the system is improved.

Based on the same idea, one or more embodiments of the present specification further provide apparatuses and devices corresponding to the above-described method, as shown in fig. 4 and 5.

Fig. 4 is a schematic structural diagram of a service processing apparatus for container operation and maintenance according to one or more embodiments of the present specification, where the apparatus includes:

a container physical machine determining module 402, configured to determine a physical machine corresponding to the target service container;

a companion container starting configuration module 404, configured to determine resource restriction information related to a namespace of the target service container, start, on the physical machine, a companion container sharing the namespace with the target service container for the target service container, and configure the resource restriction information for the companion container;

a resource obtaining module 406 of the companion container, configured to obtain resources of the companion container under the restriction indicated by the resource restriction information;

the operation and maintenance management and control interaction execution module 408 displays an operation and maintenance management and control interface including a view in the target service container through interaction between the companion container and the target service container, and executes an operation and maintenance command for the target service container by using the resource.

Optionally, the companion container resource obtaining module 406 determines whether the resource required by the operation and maintenance command to be executed causes the limitation to be broken;

if so, terminating the operation and maintenance command through the companion container.

Optionally, the companion container starts a configuration module 404, which determines an operation and maintenance agent set on the physical machine;

establishing an operation and maintenance command channel with the operation and maintenance agent;

and receiving the operation and maintenance command to be executed through the operation and maintenance command channel so that the operation and maintenance agent starts a companion container sharing the namespace with a target service container.

Optionally, the resource limitation is configured to limit resources required to be used by a process through which the operation and maintenance command is executed;

the companion container starting configuration module 404 starts a companion container sharing a namespace of a process identifier with a target service container for the target service container.

Optionally, the companion container resource obtaining module 406 is configured to decompose the operation and maintenance command to be executed into a first operation and maintenance sub-command set and a second operation and maintenance sub-command set;

acquiring resources of the companion container for executing the first operation and maintenance sub-command set, and applying for resources for executing the second operation and maintenance sub-command set from the target service container;

if the application is successful, the operation and maintenance management and control interaction execution module 408 continues to execute the second operation and maintenance sub-command set by using the resource of the associated container after the execution of the first operation and maintenance sub-command set is completed, and monitors a termination risk of terminating the operation and maintenance command based on the resource restriction information;

and if the termination risk is greater than a set threshold value, acquiring the resource applied from the target service container for executing the unexecuted part in the second operation and maintenance subcommand set.

Optionally, the target service container is started earlier than the companion container;

the companion container starts the configuration module 404, after the operation and maintenance management and control interaction execution module 408 displays the operation and maintenance management and control interface including the view in the target service container, and executes the operation and maintenance command for the target service container using the resource, further executes:

determining whether the operation and maintenance behavior of the current round is finished according to the operation and maintenance control interface;

if yes, automatically converting the associated container into a non-operation state, or automatically deleting the associated container.

Optionally, the operation and maintenance management and control interaction executing module 408, before displaying the operation and maintenance management and control interface including the view in the target service container, further executes:

displaying a current default operation and maintenance control interface so as to issue the operation and maintenance command to be executed through the current default operation and maintenance control interface;

the operation and maintenance management and control interaction execution module 408 starts a set inter-container access program in the companion container;

accessing the target service container through the inter-container access program to acquire a view of target content in the target service container;

and displaying a view of the target content in the target service container in the current default operation and maintenance control interface to obtain the operation and maintenance control interface of the target service container.

Optionally, the operation and maintenance management and control interaction execution module 408 enters the target service container through the access of the inter-container access program to the target service container;

and executing an operation and maintenance command aiming at the target service container by utilizing the resources of the companion container in the target service container.

Optionally, the operation and maintenance management and control interaction executing module 408 acquires a view of the target content in the companion container;

according to the obtained view, establishing a mapping relation between target content in the target service container and target content in the associated container, and generating a corresponding mapping relation view;

and displaying the mapping relation view in the current default operation and maintenance management and control interface.

Optionally, the target content includes a namespace and a root file system.

Fig. 5 is a schematic structural diagram of a service processing device for container operation and maintenance according to one or more embodiments of the present specification, where the device includes:

at least one processor; and the number of the first and second groups,

a memory communicatively coupled to the at least one processor; wherein, the first and the second end of the pipe are connected with each other,

determining a physical machine corresponding to a target service container;

determining resource limitation information related to a namespace of the target service container, starting a companion container sharing the namespace with the target service container for the target service container on the physical machine, and configuring the resource limitation information for the companion container;

The processor and the memory may communicate via a bus, and the device may further include an input/output interface for communicating with other devices.

Based on the same idea, one or more embodiments of the present specification further provide a non-volatile computer storage medium corresponding to the above method, and storing computer-executable instructions configured to:

determining a physical machine corresponding to a target service container;

In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: the ARC625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

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.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the various elements may be implemented in the same one or more software and/or hardware implementations of the present description.

As will be appreciated by one skilled in the art, the present specification embodiments may be provided as a method, system, or computer program product. Accordingly, embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and so forth) having computer-usable program code embodied therein.

The description has been presented with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement 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 phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

This description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

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 embodiments of the apparatus, the device, and the nonvolatile computer storage medium, since they are substantially similar to the embodiments of the method, the description is simple, and for the relevant points, reference may be made to the partial description of the embodiments of the method.

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.

The above description is merely one or more embodiments of the present disclosure and is not intended to limit the present disclosure. Various modifications and alterations to one or more embodiments of the present description will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement or the like made within the spirit and principle of one or more embodiments of the present specification should be included in the scope of the claims of the present specification.

Claims

1. A business processing method for container operation and maintenance comprises the following steps:

determining a physical machine corresponding to a target service container;

2. The method of claim 1, said obtaining resources of said companion container under the restriction indicated by said resource restriction information, further comprising:

judging whether the resources required by the operation and maintenance command to be executed cause the limitation to be broken through;

and if so, terminating the operation and maintenance command through the companion container.

3. The method according to claim 1, wherein the starting, on the physical machine, a companion container that shares at least a part of a namespace with a target service container for the target service container specifically includes:

determining an operation and maintenance agent arranged on the physical machine;

an operation and maintenance command channel is established between the operation and maintenance agent and the network;

and receiving the operation and maintenance command to be executed through the operation and maintenance command channel so that the operation and maintenance agent starts a companion container which shares at least part of the name space with a target service container.

4. The method of claim 2, wherein the resource restriction is configured to restrict resources required to be used by a process through which the operation and maintenance command is executed;

the starting of the companion container sharing at least part of the name space with the target service container for the target service container specifically includes:

and starting a companion container of the namespace sharing the process identifier with the target service container for the target service container.

5. The method according to claim 2, wherein the acquiring resources of the companion container specifically comprises:

decomposing the operation and maintenance command to be executed into a first operation and maintenance sub-command set and a second operation and maintenance sub-command set;

the executing the operation and maintenance command for the target service container specifically includes:

if the application is successful, after the first operation and maintenance sub-command set is executed, the resource of the associated container is utilized to continue executing the second operation and maintenance sub-command set, and the termination risk of terminating the operation and maintenance command based on the resource limit information is monitored;

6. The method of claim 1, the target service container being started earlier than the companion container;

after the displaying an operation and maintenance management and control interface including the view in the target service container and executing the operation and maintenance command for the target service container by using the resource, the method further includes:

7. The method of claim 1, prior to said exposing an operation and maintenance management interface comprising a view within the target business container, the method further comprising:

the displaying of the operation and maintenance management and control interface including the view in the target service container specifically includes:

starting a set inter-container access program in the companion container;

and displaying the view of the target content in the target service container in the current default operation and maintenance management and control interface.

8. The method of claim 7, wherein the executing the operation and maintenance command for the target service container using the resource specifically comprises:

accessing the target service container through the inter-container access program to enter the target service container;

9. The method of claim 7, wherein the displaying the view of the target content in the target service container in the current default operation and maintenance management interface further comprises:

obtaining a view of target content within the companion container;

10. The method of claim 7 or 9, the target content comprising the at least part of the namespace and a root file system.

11. A service processing apparatus for container operation and maintenance, comprising:

12. The apparatus of claim 11, the companion container resource obtaining module determines whether the resource required by the operation and maintenance command to be executed causes the limitation to be broken;

13. The apparatus of claim 11, the companion container initiates a configuration module that determines an operation and maintenance agent disposed on the physical machine;

14. The apparatus of claim 12, the resource restriction is configured to restrict resources required for a process by which the operation and maintenance command is executed;

and the companion container starting configuration module is used for starting a companion container sharing a process identifier namespace with the target service container for the target service container.

15. The apparatus of claim 12, the companion container resource obtaining module is configured to decompose the operation and maintenance command to be executed into a first operation and maintenance subcommand set and a second operation and maintenance subcommand set;

if the application is successful, after the first operation and maintenance subcommand set is executed, the operation and maintenance management and control interaction execution module continues to execute the second operation and maintenance subcommand set by using the resources of the companion container, and monitors the termination risk of terminating the operation and maintenance command based on the resource limit information;

16. The apparatus of claim 11, the target service container being started earlier than the companion container;

the companion container starts a configuration module, and after the operation and maintenance management and control interaction execution module displays an operation and maintenance management and control interface including a view in the target service container and executes an operation and maintenance command for the target service container by using the resource, the configuration module further executes:

17. The apparatus of claim 11, wherein the operation management interaction execution module, before displaying the operation management interface including the view in the target service container, further executes:

the operation and maintenance management and control interactive execution module starts a set inter-container access program in the companion container;

18. The apparatus of claim 17, wherein the operation and maintenance management interaction execution module accesses the target service container through the inter-container access program to enter the target service container;

19. The apparatus of claim 17, the operation and maintenance administration interaction execution module to obtain a view of target content within the companion container;

20. The apparatus of claim 17 or 19, the target content comprising the at least part of the namespace and a root file system.

21. A business processing device for container operation and maintenance, comprising:

at least one processor; and the number of the first and second groups,

the memory stores instructions executable by the at least one processor to enable the at least one processor to:

determining a physical machine corresponding to a target service container;