WO2020232887A1 - 容器应用的配置修改方法、装置、计算机设备及存储介质 - Google Patents

容器应用的配置修改方法、装置、计算机设备及存储介质 Download PDF

Info

Publication number
WO2020232887A1
WO2020232887A1 PCT/CN2019/103175 CN2019103175W WO2020232887A1 WO 2020232887 A1 WO2020232887 A1 WO 2020232887A1 CN 2019103175 W CN2019103175 W CN 2019103175W WO 2020232887 A1 WO2020232887 A1 WO 2020232887A1
Authority
WO
WIPO (PCT)
Prior art keywords
container
modified
application
instance
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2019/103175
Other languages
English (en)
French (fr)
Inventor
黄桂钦
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Technology Shenzhen Co Ltd
Original Assignee
Ping An Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ping An Technology Shenzhen Co Ltd filed Critical Ping An Technology Shenzhen Co Ltd
Publication of WO2020232887A1 publication Critical patent/WO2020232887A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45562—Creating, deleting, cloning virtual machine instances
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Definitions

  • This application relates to the field of cloud computing technology, and in particular to a method, device, computer equipment, and storage medium for modifying the configuration of a container application.
  • PaaS Platform-as-a-Service, platform-as-a-service
  • PaaS Platform-as-a-service
  • the processing method It is to delete the original container application, and then create a new container application. This requires tedious work such as deletion and creation to allow the new container application to provide services.
  • some configurations of the container application may need to be modified. For example, as the user traffic increases, the memory capacity of the container application may not be enough to use, and the memory capacity of the container application needs to be modified.
  • the relevant personnel need to log in to each container instance of the container application, and then modify the corresponding configuration one by one. In this way, the process of modifying the configuration is more cumbersome and requires the relevant personnel to have a higher level of expertise. It requires more labor cost and time cost.
  • the embodiment of the application provides a method, device, computer equipment, and storage medium for modifying the configuration of a container application.
  • the service of the container application can be changed by modifying the configuration, which achieves the effect of quickly replacing the service.
  • the instance modifies the corresponding configuration at one time, and the process of modifying the configuration is completed automatically, which speeds up the configuration modification of the container application.
  • an embodiment of the present application provides a configuration modification method of a container application, including:
  • the preset modification interface is called according to the configuration modification instruction to receive the configuration information to be modified of the container application set through the preset modification interface; if the setup completion instruction is received , Obtain the configuration information to be modified of the container application; detect whether the image information to be modified in the configuration information to be modified is consistent with the image information of the container application; if the image information to be modified is the same as the The image information of the container application is inconsistent, release the binding relationship between all container instances of the container application and the corresponding container instance IP, and destroy all container instances; according to the resource information to be modified and the resource information to be modified in the configuration information to be modified For the modified image information, a new container instance is created, and the created new container instance is bound to the corresponding container instance IP to complete the modification and replacement of the image information of the container application.
  • an embodiment of the present application provides a configuration modification device of a container application, and the configuration modification device of the container application includes a unit corresponding to the method described in the first aspect.
  • an embodiment of the present application provides a computer device, the computer device includes a memory, and a processor connected to the memory;
  • the memory is used to store a computer program
  • the processor is used to run the computer program stored in the memory to execute the method described in the first aspect above.
  • an embodiment of the present application provides a computer-readable storage medium that stores a computer program that, when executed by a processor, implements the method described in the first aspect.
  • the method for modifying the configuration of the container application disclosed in the embodiment of the present application accelerates the speed of modifying the configuration of the container application, and at the same time, there is no requirement for the professional degree of the user, which improves the user experience and reduces the labor cost and time cost.
  • FIG. 1 is a schematic flowchart of a method for modifying the configuration of a container application provided by an embodiment of the present application
  • FIG. 2 is a schematic diagram of a sub-flow of a method for modifying the configuration of a container application provided by an embodiment of the present application
  • FIG. 3 is a schematic diagram of a sub-flow of a method for modifying the configuration of a container application provided by an embodiment of the present application
  • FIG. 4 is a schematic block diagram of a device for modifying the configuration of a container application provided by an embodiment of the present application
  • FIG. 5 is a schematic block diagram of a destruction unit provided by an embodiment of the present application.
  • Fig. 6 is a schematic block diagram of a creation unit provided by an embodiment of the present application.
  • Fig. 7 is a schematic block diagram of a computer device provided by an embodiment of the present application.
  • FIG. 1 is a schematic flowchart of a method for modifying the configuration of a container application provided by an embodiment of the present application. As shown in Figure 1, the method includes S101-S107.
  • the configuration modification instruction of a container application can be triggered in many ways, such as by the user clicking or triggering a button or image. For example, in the list of container applications, clicking the configuration modification button corresponding to a container application will trigger the container application Configuration modification instruction; for example, the corresponding configuration modification instruction is triggered by receiving a user's voice configuration modification message.
  • the configuration modification instruction includes information of the container application, such as identification information of the container application.
  • the identification information of the container application may be the name of the container application or the number of the container application, etc., which can determine the specific container application.
  • the preset modification interface is called according to the configuration modification instruction.
  • the preset modification interface is developed by the developer and can exist in the form of a setting interface.
  • the configuration information to be modified for the container application can be set through the preset modification interface. Understandably, the configuration information to be modified for the container application can be set through the preset modification interface. In this way, the configuration information to be modified is very transparent, and the configuration information to be modified can be seen intuitively, which improves the user experience. Moreover, only simple selection/input operations are required for setting, without the user having high professional knowledge, and labor costs and time costs are reduced.
  • the configuration information to be modified by the container application includes resource information to be modified by the container application, image information to be modified by the container application, and so on.
  • the resource information to be modified by the container application includes CPU resources (such as the number of CPU cores) and memory resources (such as memory capacity) occupied by each container instance of the container application.
  • the resource information of the container application can be determined in the following two ways: (1) Obtain the past traffic of the container application; estimate the resource information required by the container application based on the past traffic and current traffic of the container application ; Determine the estimated resource information as the resource information of the container application. Or, determine the resource information of the container application according to the previous process peak of the container application. For example, based on the past traffic peaks of the container application, the approximate resources required by the container application can be estimated.
  • the past process peaks require 2 cores 4G memory, etc., then the resource information of the container application includes 2 cores 4G memory.
  • the resource information of the container application includes 2 cores 4G memory.
  • weblogic applications generally require 2 cores 4G memory, so 2 cores 4G memory is a common configuration for weblogic applications. That is, under normal circumstances, weblogic applications will be set to 2-core 4G memory.
  • the common configuration of the container application is set by the user according to the company's business scenario, that is, the common configuration meets the company's business scenario.
  • the resource information of the container application is displayed on the preset setting interface, so that the user can set the resource information of the container application to be modified according to the displayed resource information of the container application.
  • the user can directly set the displayed resource information of the container application as the resource information to be modified by the container application.
  • the displayed resource information of the container application is set as the resource information of the default container application; if a user modification of the resource information of the default container application is received, the resource information modified by the user is obtained; The resource information modified by the user is used as the resource information to be modified.
  • the resource information of the container application also includes DNS server information.
  • the DNS server information is generally determined by the enterprise's architecture and is generally not modified.
  • the image information of the container application includes the image type and image name of the container application.
  • the mirror information of the container application can be determined as follows: determine a mirror type, for example, obtain multiple candidate mirror types from the database, receive a mirror type selected by the user from the multiple candidate mirror types; determine a specific mirror according to the mirror type For example, according to the mirror type, all the candidate mirrors under the mirror type are obtained from the database (it can be understood that there are multiple different mirror versions under the mirror type); a mirror selected by the user from the candidate mirrors is received as the specific Mirror, and get the mirror name of the specific mirror.
  • the image type and specific image selected by the user are used as the image information to be modified. It should be noted that if the image information of the container application to be modified is empty, then it can be considered that the image information of the container application is not modified.
  • the set configuration information of the container application to be modified may only include one of the configuration information, such as only the image information to be modified, or only the resource information to be modified, or only the resource information to be modified. CPU or only the memory in the resource information to be modified.
  • the setting completion instruction can be triggered in many ways, such as by the user clicking or triggering a button or image, such as the user clicking the corresponding button or image, such as "submit” button, "OK” image, etc.; such as receiving user's voice confirmation Message to trigger the corresponding setting completion instruction.
  • a button or image such as the user clicking the corresponding button or image, such as "submit” button, "OK” image, etc.; such as receiving user's voice confirmation Message to trigger the corresponding setting completion instruction.
  • After receiving the setting completion instruction obtain the configuration information to be modified of the container application.
  • all the information of all container applications is stored in the database.
  • the container application is determined according to the identification information of the container application in the configuration modification instruction, and various information of the container application is obtained from the database according to the identification information of the container application. For example, obtaining the image information of the container application stored in the database.
  • the acquired image information of the container application is matched with the modified image information in the configuration information to be modified to determine whether the image information to be modified is consistent with the image information of the container application stored in the database.
  • the image information to be modified is empty, it is determined that the image information to be modified is consistent with the image information of the container application; if the image information to be modified is not empty, but the image information to be modified is the same as the image information of the container application If they are the same, determine that the image information to be modified is consistent with the image information of the container application; otherwise, if the image information to be modified is not the same as the image information of the container application, determine the image information to be modified and the image information of the container application Inconsistent.
  • the image information to be modified is the same as the image information of the container application, which can be understood as the same image type and image name. If one piece of information in the image type and the image version is different, it is considered different, that is, the image information to be modified is inconsistent with the image information of the container application.
  • step S104 is executed; if the image information to be modified is consistent with the image information of the container application, step S106 is executed.
  • S104 Release the binding relationship between all container instances of the container application and the corresponding container instance IP, and destroy all container instances.
  • step S104 includes the following steps S1041-S1043.
  • S1041 Determine the host where all container instances of the container application are located.
  • the information of the host where all the container instances of the container application are located is stored in the database, and the host where all the container instances of the container application are located are obtained from the database.
  • the information of the container application is obtained from the database according to the identification information of the container application, and the host where all the container instances of the container application are located are obtained from the database according to the information of the container application.
  • a container instance corresponds to a host. If there are multiple container instances, then obtain the host machines corresponding to the multiple container instances. It should be noted that the host may also include multiple container instances of other applications.
  • S1042 Release the binding relationship between the container instance of the container application on the host machine and the corresponding container instance IP.
  • Information such as the IP of the container instance of the container application is stored in the database.
  • the container instance can only access the container application through the IP after the container instance IP is set.
  • the container instance IP information of the container application is obtained from the database, and the container instance of the container application on the host computer is determined according to the container instance IP information of the container application.
  • Unlocking the binding relationship between the container instance of the container application on the host machine and the corresponding container instance IP can be achieved by the following way: connect the container instance of the container application through an automated operation and maintenance tool, and remove the container instance of the container application from The binding relationship of the container instance IP.
  • the container instance of the container application is connected through an automated operation and maintenance tool, and an instruction to delete the network card is issued to delete the network card of the container instance of the container application.
  • the automated operation and maintenance tool can be an ansible tool, or other tools that can achieve the same function.
  • the IP status of the container instance will also change, such as being changed from a used state to a disabled state.
  • the binding relationship between the container instance of the container application on the host machine and the corresponding container instance IP can also be solved in other ways.
  • the method further includes: stopping the container application on the host machine.
  • the operation of the container instance For example, the operation of the container instance can be stopped by executing instructions, such as the docker stop instruction.
  • S1043 Destroy the container instance of the container application on the host machine and reclaim the resource of the container instance.
  • a destruction instruction is issued through a container orchestration tool to the host computer where the container instance of the container application is located, so as to destroy the container instance of the container application on the host computer and recover the resources of the container instance.
  • destroying the container instance will release and reclaim all the resources occupied by the container instance, including CPU resources, memory resources, environmental information corresponding to the container instance, file input and output streams (closed), and connection to the database (closed) Wait.
  • orchestration tools such as marathon and so on.
  • destroying the resources of the container instance can be understood as stopping the process of the container instance on the corresponding host machine (kill operation). Once the process is killed, it means that the container instance no longer exists on the host, and it will not occupy any resources on the host. Understandably, a container instance corresponds to a process.
  • This embodiment realizes the automatic realization of releasing the binding relationship between all container instances of the container application and the corresponding container instance IP and destroying all container instances, and provides the speed of releasing the corresponding binding relationship and destroying the container instance.
  • S105 Create a new container instance according to the resource information to be modified and the image information to be modified in the configuration information to be modified, and bind the created new container instance with the corresponding container instance IP, so as to Complete the modification and replacement of the image information of the container application.
  • the corresponding container instance IP is the IP bound to the destroyed container instance.
  • the number of new container instances created is equal to the number of container instances destroyed. Create a new container instance, and bind the created new container instance with the corresponding container instance IP. In this way, there is no need to assign a container instance IP to a new container instance, and the IP bound to the destroyed container instance is directly used, which improves the speed of modification and replacement of the image information of the container application.
  • step S105 includes the following steps S1051-S1054.
  • S1051 Determine a mirror warehouse in the region where the container application is located, and obtain a specific mirror image from the determined mirror warehouse according to the mirror information to be modified.
  • the application environment of the container application and the area of the container application are stored in the database.
  • the mirror warehouse under the area where the container application is located is searched from the database.
  • each application environment and each region determines a mirror warehouse.
  • Each area in each application environment corresponds to a mirror warehouse that stores mirror resources, and all the mirror resources needed to be used in the area in the application environment are stored in the mirror warehouse.
  • the application environment includes production environment, test environment, development environment, etc.
  • the image warehouse in the region where the container application is located can be directly obtained from the database according to the identification information of the container application.
  • S1052 Determine a host for creating a new container instance of the container application according to the image information to be modified and the resource information to be modified.
  • the application environment of the container application and the area of the container application can be obtained in the database, and the host cluster is determined according to the application environment of the container application and the area of the container application, such as obtaining from the database according to the application environment of the container application and the area of the container application The host cluster under the area where the container application is located.
  • the host cluster in the region where the container application is located can be directly obtained from the database according to the identification information of the container application. After obtaining the host cluster, determine the host that creates the new container instance of the container application according to the image information to be modified and the resource information to be modified. Creating a container instance needs to occupy the resources of the host.
  • the resources needed to create a new container instance are determined; according to the resources needed to create a new container instance, start with the container application. Determine the host for creating a new container instance in the host cluster under the area.
  • the determined host for creating a new container instance is randomly allocated, and not necessarily the host where the destroyed container instance is located. It can be understood that the image information used to create the container application has changed, so the resources needed to create the container instance may have also changed. If a new container instance is created on the host where the destroyed container instance is located, it is likely to exist The resource of the host machine where the destroyed container instance is located is insufficient, causing the creation of a new container instance to fail. Therefore, the host that creates a new container instance is randomly allocated based on the resources that need to be taken up to create the new container instance. In this way, the resources of the randomly allocated host are not insufficient.
  • the resource information to be modified in this step is all empty, the resource information of the container application is directly obtained, and the resource information of the container application is used as the resource information to be modified, which means that only the image information of the container application is modified.
  • the resource information of the created new container instance is the same as the resource information of the destroyed container instance; if part of the resource information to be modified is empty, the empty part will directly use the corresponding resource of the container application.
  • the empty part uses the information in the resource information to be modified; if all the resource information to be modified is not empty, the resource information to be modified is directly used.
  • S1053 Create a new container instance on the determined host machine according to the specific image and the resource information to be modified.
  • the container orchestration tool can be a Marathon tool or other container orchestration tools. It should be noted that as many container instances as the container application destroys, then how many container instances are created there.
  • the automated operation and maintenance tools may be ansible tools and the like.
  • the status of the IP will also be modified, such as changing the status of the IP from the disabled state to the in-use state.
  • the container application has multiple container instances, then the container instances on the multiple host machines are obtained, and each container instance performs application image replacement. In this way, the application images of all container instances of the container application can be replaced at one time, without the need to replace each container instance.
  • This embodiment is directly based on the container application, and quickly replaces the service of the container application by modifying the mirror information of the container application, and provides a brand-new technical idea and technical solution to quickly replace the service of the container application. Realized in seconds, achieving unexpected technical effects.
  • this embodiment creates a new container instance based on the image information to be modified and the resource information to be modified, and binds the new container instance to the destroyed container instance IP. This process is automated and improves the container application image. Speed and efficiency of replacement.
  • the service of container application can be replaced by modifying the configuration, which achieves the effect of rapid service replacement and improves the speed of service construction.
  • Steps S104-S105 can implement modification of the application image of the container application, that is, replacing the image information of the container application with the image information to be modified, which can achieve rapid switching or building services while keeping the IP of the container instance unchanged. Or it can also be understood as only replacing the application image or application service of the container application, and the other is unchanged. Service replacement can be realized quickly, which can be realized in seconds.
  • the resource information to be modified is consistent with the image information of the container application, it is determined that the image information of the container application has not changed, and then it is detected whether the resource information to be modified is consistent with the resource information of the container application.
  • the resource information of the container application is obtained from the database according to the identification information of the container application, and the obtained resource information of the container application is matched with the resource information to be modified to determine whether the resource information to be modified is consistent with the resource information of the container application .
  • the resource information to be modified is empty, it is determined that the resource information to be modified is consistent with the resource information of the container application; if the resource information to be modified is not empty, but the resource information to be modified is the same as the resource information of the container application If they are the same, determine that the resource information to be modified is consistent with the resource information of the container application; otherwise, if the resource information to be modified is different from the resource information of the container application, determine the resource information to be modified and the resource information of the container application Inconsistent.
  • the resource information to be modified is the same as the resource information of the container application. It can be understood that all the information in the resource information to be modified is the same. If one of the information is different, it is considered to be different, that is, to be modified The resource information of is inconsistent with the resource information of the container application.
  • step S107 is executed; if the resource information to be modified is consistent with the resource information of the container application, that is, the image information to be modified is consistent with the image information of the container application, and The resource information to be modified is also consistent with the resource information of the container application, which means that the configuration information of the container application has not been modified, and the process ends.
  • S107 Modify the resource of the container application according to the resource information to be modified to complete the modification of the resource information of the container application.
  • the resource information of the container application is acquired from the database, and the resource information of the container application is modified on the corresponding host computer according to the acquired resource information of the container application and the set resource information to be modified. For example, according to the difference between the resource information to be modified and the obtained resource information of the container application, the resource information that needs to be added/deleted for the container application is determined. If the memory in the original resource information is 2G, and the memory set in the resource information to be modified is 4G, then it is determined that 2G of memory resources need to be added to the container application, that is, to add 2G to the container application on the corresponding host Memory resources 2G.
  • the container application deletes the memory resource 2G, that is, the memory resource corresponding to the container application on the corresponding host is released 2G. In this way, the resource information of the container application is updated to ensure that the resource of the container application is sufficient for the use of the container application.
  • the container application has multiple container instances, then obtain multiple container instances on the host, and modify each container instance.
  • Step S107 realizes the modification of the resource information of the container application, which can modify the resources of all container instances at one time, without modifying the resource information one by one, and the resource information when modifying the container is automatically completed, which improves the speed and efficiency of modifying the resource information of the container application.
  • the method further includes:
  • the modified resource information and/or the modified application mirroring information are updated to the database to ensure that the data in the database is synchronized in real time.
  • the method further includes:
  • the above method embodiment can modify the corresponding configuration of all container instances of the container application at one time, and the process of modifying the configuration is automatically completed, which speeds up the configuration modification of the container application, and at the same time, does not require the user's professional level to be required, which improves User experience reduces labor costs and time costs.
  • the application image of the container application can be replaced, so that the service of the container application can be replaced, and the speed of building the service is increased; for example, the resource information of the container application can be quickly modified.
  • the configuration information to be modified can be set intuitively, making the setting of the configuration information to be modified very transparent, and at the same time, there is no requirement for the professional degree of the user, which improves the user experience.
  • Fig. 4 is a schematic block diagram of an apparatus for modifying a configuration of a container application provided by an embodiment of the present application.
  • the device includes a unit corresponding to the configuration modification method for executing the container application.
  • the configuration modification device 100 of the container application includes a setting unit 101, an information acquisition unit 102, an image detection unit 103, a destruction unit 104, a creation unit 105, a resource detection unit 106, and a resource modification unit 107.
  • the setting unit 101 is configured to, if a configuration modification instruction of the container application is received, call a preset modification interface according to the configuration modification instruction to receive the configuration information to be modified of the container application set through the preset modification interface.
  • the information obtaining unit 102 is configured to obtain the configuration information to be modified of the container application if the setting completion instruction is received.
  • the image detection unit 103 is configured to detect whether the image information to be modified in the configuration information to be modified is consistent with the image information of the container application.
  • the destruction unit 104 is configured to, if the image information to be modified is inconsistent with the image information of the container application, release the binding relationship between all container instances of the container application and the corresponding container instance IP, and destroy all container instances.
  • the destruction unit 104 includes an original host determination unit 1041, a cancellation unit 1042, a container destruction unit 1043.
  • the original host determining unit 1041 is used to determine the host where all container instances of the container application are located.
  • the releasing unit 1042 is configured to release the binding relationship between the container instance of the container application on the host machine and the corresponding container instance IP.
  • the container destruction unit 1043 is configured to destroy the container instance of the container application on the host computer and recover the resource of the container instance.
  • the creating unit 105 is configured to create a new container instance according to the resource information to be modified and the mirroring information to be modified in the configuration information to be modified, and perform the connection between the created new container instance and the corresponding container instance IP Binding to complete the modification and replacement of the image information of the container application.
  • the creation unit 105 includes a mirror image determination unit 1051, a new host determination unit 1052, a container creation unit 1053, and a binding unit 1054.
  • the image determining unit 1051 is used to determine the image warehouse in the region where the container application is located, and obtain a specific image from the determined image warehouse according to the image information to be modified.
  • the new host determining unit 1052 is configured to determine a host for creating a new container instance of the container application according to the image information to be modified and the resource information to be modified.
  • the container creation unit 1053 is configured to create a new container instance on the determined host computer according to the specific image and the resource information to be modified.
  • the binding unit 1054 is used to bind the created new container instance with the corresponding container instance IP.
  • the new host determining unit 1052 includes an area acquiring unit, a host cluster determining unit, and a container host determining unit.
  • the area obtaining unit is used to obtain the application environment of the container application and the area of the container application.
  • the host cluster determining unit is used to determine the host cluster according to the application environment of the container application and the region of the container application.
  • the container host determining unit is configured to determine a host for creating a new container instance from the host cluster according to the image information to be modified and the resource information to be modified.
  • the resource detection unit 106 is configured to, if the image information to be modified is consistent with the image information of the container application, detect whether the resource information to be modified in the configuration information to be modified is consistent with the resource information of the container application .
  • the resource modification unit 107 is configured to, if the resource information to be modified is inconsistent with the resource information of the container application, modify the resource of the container application according to the resource information to be modified to complete the resource information of the container application Modifications.
  • the device 100 for modifying the configuration of the container application further includes:
  • the database update unit 108 is used to update the configuration information modified by the container application to the database.
  • the device 100 for modifying the configuration of the container application further includes:
  • the restarting unit 109 is configured to restart the container application to make the configuration modification of the container application take effect.
  • the above-mentioned device may be implemented in the form of a computer program, and the computer program may run on the computer device as shown in FIG. 7.
  • FIG. 7 is a schematic block diagram of a computer device provided by an embodiment of the application.
  • the equipment is a terminal and other equipment, such as a server in the PaaS platform.
  • the device 100 includes a processor 102, a memory, and a network interface 103 connected through a system bus 101, where the memory may include a non-volatile storage medium 104 and an internal memory 105.
  • the non-volatile storage medium 104 can store an operating system 1041 and a computer program 1042.
  • the computer program 1042 stored in the non-volatile storage medium is executed by the processor 102, the method for modifying the configuration of the container application described in the server can be implemented.
  • the processor 102 is used to provide computing and control capabilities and support the operation of the entire device 100.
  • the internal memory 105 provides an environment for the operation of the computer program in the non-volatile storage medium.
  • the processor 102 can make the processor 102 execute the configuration modification method of the container application described in the server.
  • the network interface 103 is used for network communication.
  • the structure shown in the figure is only a block diagram of part of the structure related to the solution of the present application, and does not constitute a limitation on the device to which the solution of the present application is applied.
  • the specific device may include a diagram More or fewer components are shown in, or some components are combined, or have different component arrangements.
  • the processor 102 is configured to run a computer program stored in a memory to implement any embodiment of the method for modifying the configuration of a container application.
  • the processor 102 may be a central processing unit (Central Processing Unit, CPU), and the processor may also be other general-purpose processors or digital signal processors (DSP). , Application-specific integrated circuit (application license Specific Integrated Circuit, ASIC), ready-made programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the computer program may be stored in a storage medium, and the storage medium may be a computer-readable storage medium.
  • the computer program is executed by at least one processor in the computer system to implement the process steps of the foregoing method embodiment.
  • the storage medium may be a computer-readable storage medium.
  • the storage medium stores a computer program that, when executed by a processor, implements any embodiment of the method for modifying the configuration of the container application.
  • the storage medium is a physical, non-transitory storage medium, such as a U disk, a mobile hard disk, a read-only memory (Read-Only Memory, ROM), a magnetic disk, or an optical disk that can store program codes. medium.
  • a physical, non-transitory storage medium such as a U disk, a mobile hard disk, a read-only memory (Read-Only Memory, ROM), a magnetic disk, or an optical disk that can store program codes. medium.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

本申请实施例提供一种容器应用的配置修改方法、装置、计算机设备及存储介质，其涉及云计算技术领域，可应用于PaaS平台中。所述方法包括：获取所设置的容器应用的待修改的配置信息；若待修改的配置信息中的待修改的镜像信息与容器应用的镜像信息不一致，解除容器应用的所有容器实例与相应的容器实例IP的绑定关系，并销毁所有容器实例；根据待修改的配置信息中的待修改的资源信息和待修改的镜像信息，创建新的容器实例，并将所创建的新的容器实例与相应的容器实例IP进行绑定，以完成容器应用的镜像信息的修改和更换。

Description

容器应用的配置修改方法、装置、计算机设备及存储介质
本申请要求于2019年05月17日提交中国专利局、申请号为201910413908.8、申请名称为“容器应用的配置修改方法、装置、计算机设备及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及云计算技术领域，尤其涉及一种容器应用的配置修改方法、装置、计算机设备及存储介质。
背景技术
在云平台中，如在PaaS(Platform-as-a-Service，平台即服务)平台中，一般情况下，当一个容器应用不再使用，而又需要创建另一个新的容器应用时，处理方式是将原容器应用进行删除，然后再创建新的容器应用，如此需要进行删除和创建等繁琐的工作，才能让新的容器应用提供服务。另外，当容器应用创建完成后，有可能需要修改容器应用的一些配置。如随着用户流量的增多，可能容器应用的内存容量已经不够使用，则需要修改容器应用的内存容量等。当一个容器应用需要修改配置时，需要相关人员登陆到容器应用的每个容器实例，然后再一个一个的修改对应的配置，如此，修改配置的过程比较繁琐，同时需要相关人员具有较高的专业度，需要较多的人力成本和时间成本。
发明内容
本申请实施例提供一种容器应用的配置修改方法、装置、计算机设备及存储介质，可通过修改配置的方式来更换容器应用的服务，达到了快速更换服务的效果，同时对容器应用的所有容器实例一次性修改对应的配置，且修改配置的过程自动完成，加快了容器应用的配置修改的速度。
第一方面，本申请实施例提供了一种容器应用的配置修改方法，包括：
若接收到容器应用的配置修改指令，根据所述配置修改指令调用预设修改接口，以接收通过所述预设修改接口设置的所述容器应用的待修改的配置信息； 若接收到设置完成指令，获取所述容器应用的待修改的配置信息；检测所述待修改的配置信息中的待修改的镜像信息与所述容器应用的镜像信息是否一致；若所述待修改的镜像信息与所述容器应用的镜像信息不一致，解除所述容器应用的所有容器实例与相应的容器实例IP的绑定关系，并销毁所有容器实例；根据所述待修改的配置信息中的待修改的资源信息和待修改的镜像信息，创建新的容器实例，并将所创建的新的容器实例与相应的容器实例IP进行绑定，以完成所述容器应用的镜像信息的修改和更换。
第二方面，本申请实施例提供了一种容器应用的配置修改装置，该容器应用的配置修改装置包括用于执行上述第一方面所述的方法对应的单元。
第三方面，本申请实施例提供了一种计算机设备，所述计算机设备包括存储器，以及与所述存储器相连的处理器；
所述存储器用于存储计算机程序，所述处理器用于运行所述存储器中存储的计算机程序，以执行上述第一方面所述的方法。
第四方面，本申请实施例提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行时，实现上述第一方面所述的方法。
本申请实施例中公开的容器应用的配置修改方法，加快了容器应用的配置修改的速度，同时也无需对用户的专业程度提出要求，提高了用户体验，降低了人工成本和时间成本。
附图说明
为了更清楚地说明本申请实施例技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本申请实施例提供的容器应用的配置修改方法的流程示意图；
图2是本申请实施例提供的容器应用的配置修改方法的子流程示意图；
图3是本申请实施例提供的容器应用的配置修改方法的子流程示意图；
图4是本申请实施例提供的容器应用的配置修改装置的示意性框图；
图5是本申请实施例提供的销毁单元的示意性框图；
图6是本申请实施例提供的创建单元的示意性框图；
图7是本申请实施例提供的计算机设备的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
图1是本申请实施例提供的容器应用的配置修改方法的流程示意图。如图1所示，该方法包括S101-S107。
S101，若接收到容器应用的配置修改指令，根据所述配置修改指令调用预设修改接口，以接收通过所述预设修改接口设置的所述容器应用的待修改的配置信息。
容器应用的配置修改指令可以由多种方式触发，如通过用户点击或者触发按钮或者图像等触发，如在容器应用的列表中，点击某一个容器应用所对应的配置修改按钮，触发该容器应用的配置修改指令；如通过接收用户的语音配置修改消息来触发对应的配置修改指令。该配置修改指令中包括容器应用的信息，如容器应用的标识信息。容器应用的标识信息可以为容器应用的名称或者容器应用的编号等等可以确定具体是哪一个容器应用的信息。根据配置修改指令调用预设修改接口，该预设修改接口是由开发人员开发的，可以以一个设置界面的形式存在。通过预设修改接口可以设置该容器应用待修改的配置信息。可以理解地，通过预设修改接口可以设置该容器应用待修改的配置信息，如此待修改的配置信息非常透明，可以直观的看到待修改的配置信息，提高了用户的体验。而且只需要简单的选择/输入操作即可进行设置，无需用户具有较高的专业知识，降低了人工成本和时间成本。
容器应用待修改的配置信息包括容器应用待修改的资源信息、容器应用待修改的镜像信息等。
其中，容器应用待修改的资源信息包括容器应用的每个容器实例所占用的 CPU资源(如CPU的核数)、内存资源(如内存容量)等。其中，容器应用的资源信息可以按照以下两种方式来进行确定：(一)获取该容器应用以往的流量；根据该容器应用以往的流量、当前的流量，预估该容器应用所需要的资源信息；将该预估的资源信息确定为容器应用的资源信息。或者根据该容器应用以前的流程高峰，来确定容器应用的资源信息。比如，可根据该容器应用以往的流量高峰，预估该容器应用大概需要的资源，如以往的流程高峰需要2核4G内存等，那么该容器应用的资源信息包括2核4G内存。(二)获取平台中保存的该容器应用的常用配置，将该常用配置确定为容器应用的资源信息。比如weblogic应用，一般需要2核4G内存，那么2核4G内存为weblogic应用的常用配置。即一般情况下，weblogic应用就会设置为2核4G内存。需要注意的是，该容器应用的常用配置是由用户根据公司业务场景进行设置的，即该常用配置是满足公司的业务场景的。确定了容器应用的资源信息后，将容器应用的资源信息显示在预设设置接口上，以供用户根据所显示的容器应用的资源信息设置该容器应用待修改的资源信息。如在一实施例中，用户可直接将所显示的容器应用的资源信息设置为该容器应用待修改的资源信息。在一实施例中，将所显示的容器应用的资源信息设置为默认的容器应用的资源信息；若接收到用户对默认的容器应用的资源信息的修改，获取用户修改的资源信息；将所获取的用户修改的资源信息作为待修改的资源信息。在一些实施例中，容器应用的资源信息还包括DNS服务器信息，DNS服务器信息一般是由企业的架构决定，一般情况下不做修改。
容器应用的镜像信息包括容器应用的镜像类型和镜像名称。容器应用的镜像信息可按照如下方式确定：确定一个镜像类型，如从数据库中获取多个候选镜像类型，接收用户从多个候选镜像类型中选择的一个镜像类型；根据该镜像类型确定一个具体镜像，如根据该镜像类型从数据库中获取该镜像类型下的所有的候选镜像(可以理解为，该镜像类型下存在有多个不同的镜像版本)；接收用户从候选镜像中选择的一个镜像作为具体镜像，并获取该具体镜像的镜像名。将用户选择的镜像类型和具体镜像作为待修改的镜像信息。需要注意的是，若容器应用待修改的镜像信息为空，那么可认为不修改容器应用的镜像信息。
可以理解地，所设置的容器应用待修改的配置信息可以只包括配置信息中 的某一个，如只包括待修改的镜像信息，或者只包括待修改的资源信息，或者只包括待修改的资源信息中的CPU，或者只包括待修改的资源信息中的内存等。
S102，若接收到设置完成指令，获取所述容器应用的待修改的配置信息。
设置完成指令可由多种方式触发，如通过用户点击或者触发按钮或者图像等触发，如用户点击对应的按钮或者图像触发，如“提交”按钮，“确定”图像等；如通过接收用户的语音确定消息来触发对应的设置完成指令。接收到设置完成指令后，获取所述容器应用的待修改的配置信息。
S103，检测所述待修改的配置信息中的待修改的镜像信息与所述容器应用的镜像信息是否一致。
其中，在数据库中保存有所有容器应用的所有信息。根据配置修改指令中的容器应用的标识信息确定是哪一个容器应用，并根据容器应用的标识信息从数据库获取该容器应用的各种信息。如获取数据库中保存的该容器应用的镜像信息。将获取的容器应用的镜像信息和待修改的配置信息中的带修改的镜像信息进行匹配，以确定待修改的镜像信息与数据库中保存的该容器应用的镜像信息是否一致。其中，若待修改的镜像信息为空，则确定待修改的镜像信息与该容器应用的镜像信息一致；若待修改的镜像信息不为空，但待修改的镜像信息与该容器应用的镜像信息相同，则确定待修改的镜像信息与该容器应用的镜像信息一致；否则，若待修改的镜像信息与该容器应用的镜像信息不相同，则确定待修改的镜像信息与该容器应用的镜像信息不一致。其中，待修改的镜像信息与该容器应用的镜像信息相同，可理解为镜像类型和镜像名都相同。若镜像类型和镜像版本中有一个信息不相同，则认为是不相同的，也即待修改的镜像信息与该容器应用的镜像信息不一致。
若待修改的镜像信息与该容器应用的镜像信息不一致，执行步骤S104；若待修改的镜像信息与该容器应用的镜像信息一致，执行步骤S106。
S104，解除所述容器应用的所有容器实例与相应的容器实例IP的绑定关系，并销毁所有容器实例。
先将容器应用的容器实例与容器实例IP的绑定关系解除，再销毁容器应用的容器实例。
在一实施例中，如图2所示，步骤S104包括以下步骤S1041-S1043。
S1041，确定所述容器应用的所有容器实例所在的宿主机。
在数据库中保存有该容器应用的所有容器实例所在的宿主机的信息，从数据库中获取该容器应用的所有容器实例所在的宿主机。如根据容器应用的标识信息从数据库中获取容器应用的信息，根据容器应用的信息从数据库中获取该容器应用的所有容器实例所在的宿主机。一般情况下，一个容器实例对应一个宿主机。若有多个容器实例，那么获取多个容器实例所对应的宿主机。需要注意的是，该宿主机上还可以包括多个其他应用的容器实例。
S1042，解除所述宿主机上的所述容器应用的容器实例与相应的容器实例IP的绑定关系。
数据库中保存有该容器应用的容器实例IP等信息。容器实例只有设置了容器实例IP后，才可以通过IP来访问该容器应用。从数据库中获取该容器应用的容器实例IP信息，根据该容器应用的容器实例IP信息确定宿主机上该容器应用的容器实例。解除宿主机上的该容器应用的容器实例与相应的容器实例IP的绑定关系，可通过如下方式实现：通过自动化运维工具连接该容器应用的容器实例，并解除该容器应用的容器实例与该容器实例IP的绑定关系。具体地，通过自动化运维工具连接该容器应用的容器实例，并下发删除网卡的指令将容器应用的容器实例的网卡删除。其中，自动化运维工具可以为ansible工具，还可以为其他的可以实现相同功能的工具。解除该容器应用的容器实例与该容器实例IP的绑定关系之后，该容器实例的IP状态也会发生改变，如从使用状态修改为停用状态等。在其他实施例中，还可以通过其他方式来解决宿主机上的该容器应用的容器实例与相应的容器实例IP的绑定关系。
需要注意的是，在解除所述宿主机上的所述容器应用的容器实例与相应的容器实例IP的绑定关系之前，所述方法还包括：停止所述宿主机上的所述容器应用的容器实例的运行。如可以通过执行指令的方式停止容器实例的运行，如docker stop指令。
S1043，销毁所述宿主机上的所述容器应用的容器实例并回收所述容器实例的资源。
如通过容器编排工具下发销毁指令到该容器应用的容器实例所在的宿主机，以在宿主机上将该容器应用的容器实例销毁并回收容器实例的资源。其中， 销毁容器实例将会释放并回收该容器实例所占用的所有资源，如包括CPU资源、内存资源、容器实例所对应的环境信息、文件输入输出流(关闭)、与数据库的连接(关闭)等。其中，编排工具如marathon等。具体地，销毁容器实例的资源，可以理解为，将容器实例在对应宿主机上的进程进行停止操作(kill操作)。一旦kill了该进程，则表示该容器实例在宿主机上已经不存在，也不会占用宿主机上的任何资源。可以理解地，一个容器实例对应一个进程。
该实施例实现了自动化实现将容器应用的所有容器实例与相应容器实例IP的绑定关系解除并销毁所有容器实例，提供了解除对应绑定关系以及销毁容器实例的速度。
S105，根据所述待修改的配置信息中的待修改的资源信息和待修改的镜像信息，创建新的容器实例，并将所创建的新的容器实例与相应的容器实例IP进行绑定，以完成所述容器应用的镜像信息的修改和更换。
其中，相应的容器实例IP即为销毁的容器实例所绑定的IP。创建新的容器实例的数量与所销毁的容器实例的数量相等。创建新的容器实例，并将创建的新的容器实例与相应的容器实例IP进行绑定。如此，无需为新的容器实例分配容器实例IP，直接使用销毁的容器实例所绑定的IP，提高了容器应用的镜像信息修改和更换的速度。
在一实施例中，如图3所示，步骤S105包括以下步骤S1051-S1054。
S1051，确定所述容器应用所在区域下的镜像仓库，并根据所述待修改的镜像信息从所确定的镜像仓库中获取具体镜像。
如在数据库中保存有该容器应用的应用环境、容器应用的区域。根据容器应用的应用环境、容器应用的区域确定该容器应用所在区域下的镜像仓库。具体地，根据容器应用的应用环境、容器应用的区域从数据库中查找该容器应用所在区域下的镜像仓库。可以理解为，每个应用环境、每个区域确定一个镜像仓库。每个应用环境下每个区域中都对应有保存镜像资源的镜像仓库，在该镜像仓库中保存有该应用环境下该区域所需要使用的所有的镜像资源。其中，应用环境包括生产环境、测试环境、开发环境等。确定了镜像仓库后，根据待修改的镜像信息中的镜像类型和镜像名称从镜像仓库中提取出具体镜像。
在一实施例中，可直接根据容器应用的标识信息从数据库中获取该容器应 用所在区域下的镜像仓库。
S1052，根据所述待修改的镜像信息和所述待修改的资源信息确定创建所述容器应用的新的容器实例的宿主机。
如可在数据库中获取该容器应用的应用环境和容器应用的区域，根据容器应用的应用环境和容器应用的区域确定宿主机集群，如根据容器应用的应用环境和容器应用的区域从数据库中获取所述容器应用所在区域下的宿主机集群。在一实施例中，可直接根据容器应用的标识信息从数据库中获取该容器应用所在区域下的宿主机集群。获取宿主机集群后，根据待修改的镜像信息和待修改的资源信息确定创建容器应用的新的容器实例的宿主机。创建容器实例是需要占用宿主机的资源的，根据待修改的资源信息、待修改的镜像信息确定创建新的容器实例需占用的资源；根据创建新的容器实例需占用的资源从该容器应用所在区域下的宿主机集群中确定创建新的容器实例的宿主机。
需要注意的是，所确定的创建新的容器实例的宿主机是随机分配的，并不一定是销毁的容器实例所在的宿主机。可以理解为，创建容器应用的镜像信息已经改变，如此，创建容器实例需占用的资源可能也已经改变，如果还在销毁的容器实例所在的宿主机上创建新的容器实例的话，很有可能存在销毁的容器实例所在的宿主机资源不足的情况，造成新的容器实例创建失败。因此，创建新的容器实例的宿主机是根据创建新的容器实例需占用的资源随机分配的，如此，随机分配的宿主机的资源不存在不足的情况。
需要说明的是，该步骤中的待修改的资源信息若全为空，则直接获取容器应用的资源信息，将容器应用的资源信息作为待修改的资源信息，意味着只修改容器应用的镜像信息，而所创建的新的容器实例的资源信息与销毁的容器实例的资源信息相同；若待修改的资源信息中的一部分为空，则该为空的一部分直接使用容器应用的对应的资源，不为空的部分则使用待修改的资源信息中的信息；若待修改的资源信息全部不为空，则直接使用待修改的资源信息。
S1053，根据所述具体镜像和所述待修改的资源信息在所确定的宿主机上创建新的容器实例。
如将待修改的资源信息进行封装，将封装后的待修改的资源信息和具体镜像，通过容器编排工具发送到所确定的宿主机上，以通过容器编排工具在所确 定的宿主机上进行容器实例的创建。具体的，调用容器编排工具中的API函数接口如创建接口，以实现容器实例的创建。其中，容器编排工具可以为Marathon工具，还可以为其他的容器编排工具。需要注意的是，该容器应用销毁多少个容器实例，那么该处就新建多少个容器实例。
S1054，将所创建的新的容器实例与相应的容器实例IP进行绑定。
如通过自动化运维工具来连接所创建的新的容器实例，并将所创建的新的容器实例与相应的容器实例IP进行绑定，以将销毁的容器实例IP设置为所创建的新的容器实例IP。其中，自动化运维工具可以为ansible工具等。IP与容器实例进行绑定后，IP的状态也会进行修改，如将IP的状态从停用状态改为使用状态。
需要注意的是，若容器应用有多个容器实例，那么获取多个宿主机上的容器实例，每个容器实例都进行应用镜像的更换。如此可一次性更换该容器应用的所有容器实例的应用镜像，无需一个一个容器实例进行更换。
该实施例直接在容器应用的基础上，通过修改容器应用的镜像信息的方式来快速的更换容器应用的服务，提供了一种全新的技术思路和技术方案来快速的更换容器应用的服务，可秒级实现，达到了意想不到的技术效果。另外，该实施例根据待修改的镜像信息和待修改的资源信息来创建新的容器实例，并将新的容器实例与销毁的容器实例IP进行绑定，该过程自动化完成，提高了容器应用镜像更换的速度和效率。可实现通过修改配置的方式来更换容器应用的服务，达到了快速更换服务的效果，提高了搭建服务的速度。
步骤S104-S105可以实现修改容器应用的应用镜像，即将容器应用的镜像信息更换为待修改的镜像信息，能达到快速的切换或者搭建服务，同时保持容器实例的IP不变。或者也可以理解为只替换容器应用的应用镜像或者应用服务，其他不变，快速地实现服务更换，可秒级实现。
S106，检测所述待修改的配置信息中的待修改的资源信息与所述容器应用的资源信息是否一致。
即若待修改的镜像信息与容器应用的镜像信息一致，那么确定容器应用的镜像信息没有发生变更，那么检测待修改的资源信息与容器应用的资源信息是否一致。如根据容器应用的标识信息从数据库中获取容器应用的资源信息，将 所获取的容器应用的资源信息与待修改的资源信息进行匹配，以确定待修改的资源信息与容器应用的资源信息是否一致。其中，若待修改的资源信息为空，则确定待修改的资源信息与该容器应用的资源信息一致；若待修改的资源信息不为空，但待修改的资源信息与该容器应用的资源信息相同，则确定待修改的资源信息与该容器应用的资源信息一致；否则，若待修改的资源信息与该容器应用的资源信息不相同，则确定待修改的资源信息与该容器应用的资源信息不一致。其中，待修改的资源信息与该容器应用的资源信息相同，可理解为待修改的资源信息中的所有信息都相同，若其中有一个信息不相同，则认为是不相同的，也即待修改的资源信息与该容器应用的资源信息不一致。
若待修改的资源信息与该容器应用的资源信息不一致，执行步骤S107；若待修改的资源信息与该容器应用的资源信息一致，即待修改的镜像信息与该容器应用的镜像信息一致，且待修改的资源信息与该容器应用的资源信息也一致，如此意味着该容器应用的配置信息没有做任何修改，流程结束。
S107，根据所述待修改的资源信息修改所述容器应用的资源，以完成所述容器应用的资源信息的修改。
从数据库中获取容器应用的资源信息，根据所获取的容器应用的资源信息、所设置的待修改的资源信息在所对应的宿主机上修改容器应用的资源。如根据待修改的资源信息与所获取的容器应用的资源信息中的差值来确定还需为该容器应用新增/删除的资源信息。如原始资源信息中的内存为2G，而待修改的资源信息中所设置的内存为4G，那么确定还需为该容器应用新增内存资源2G，即在对应宿主机上为该容器应用新增内存资源2G。若原始资源信息中的内存为4G，而待修改的资源信息中所设置的内存为2G，那么确定为该容器应用删除内存资源2G，即释放对应宿主机上的该容器应用所对应的内存资源2G。如此，更新容器应用的资源信息，以保证容器应用的资源足够容器应用的使用。
需要注意的是，若容器应用有多个容器实例，那么获取多个宿主机上的容器实例，每个容器实例都进行修改。
步骤S107实现了修改容器应用的资源信息，可一次性修改所有容器实例的资源，不必一个一个的进行修改，且修改容器时的资源信息自动完成，提高了容器应用资源信息修改的速度和效率，另外，无需登陆到对应的容器实例上进 行修改，也无需对用户的专业程度提出要求，提高了用户的体验。
在一实施例中，如图1所示，所述方法还包括：
S108，将所述容器应用所修改的配置信息更新到数据库中。
如将所修改的资源信息和/或所修改的应用镜像信息更新到数据库中，以确保数据库中的数据是实时同步的。
在一实施例中，如图1所示，所述方法还包括：
S109，重启所述容器应用，以使得所述容器应用的配置修改生效。
上述方法实施例可对容器应用的所有容器实例一次性修改相应的配置，且修改配置的过程自动完成，加快了容器应用的配置修改的速度，同时也无需对用户的专业程度提出要求，提高了用户体验，降低了人工成本和时间成本。具体地，如可实现更换容器应用的应用镜像，如此来更换容器应用的服务，提高了搭建服务的速度；如可快速的修改容器应用的资源信息等。此外，通过相应的预设设置接口，直观的设置待修改的配置信息，使得待修改的配置信息的设置非常透明，同时无需对用户的专业程度提出要求，提高了用户体验。
图4是本申请实施例提供的容器应用的配置修改装置的示意性框图。该装置包括用于执行上述容器应用的配置修改方法所对应的单元。如图4所示，该容器应用的配置修改装置100包括设置单元101、信息获取单元102、镜像检测单元103、销毁单元104、创建单元105、资源检测单元106、资源修改单元107。
设置单元101，用于若接收到容器应用的配置修改指令，根据所述配置修改指令调用预设修改接口，以接收通过所述预设修改接口设置的所述容器应用的待修改的配置信息。信息获取单元102，用于若接收到设置完成指令，获取所述容器应用的待修改的配置信息。镜像检测单元103，用于检测所述待修改的配置信息中的待修改的镜像信息与所述容器应用的镜像信息是否一致。销毁单元104，用于若所述待修改的镜像信息与所述容器应用的镜像信息不一致，解除所述容器应用的所有容器实例与相应的容器实例IP的绑定关系，并销毁所有容器实例。
在一实施例中，如图5所示，销毁单元104包括原宿主机确定单元1041、解除单元1042、容器销毁单元1043。其中，原宿主机确定单元1041，用于确定所述容器应用的所有容器实例所在的宿主机。解除单元1042，用于解除所述 宿主机上的所述容器应用的容器实例与相应的容器实例IP的绑定关系。容器销毁单元1043，用于销毁所述宿主机上的所述容器应用的容器实例并回收所述容器实例的资源。
创建单元105，用于根据所述待修改的配置信息中的待修改的资源信息和待修改的镜像信息，创建新的容器实例，并将所创建的新的容器实例与相应的容器实例IP进行绑定，以完成所述容器应用的镜像信息的修改和更换。
在一实施例中，如图6所示，创建单元105包括镜像确定单元1051、新宿主机确定单元1052、容器创建单元1053、绑定单元1054。其中，镜像确定单元1051，用于确定所述容器应用所在区域下的镜像仓库，并根据所述待修改的镜像信息从所确定的镜像仓库中获取具体镜像。新宿主机确定单元1052，用于根据所述待修改的镜像信息和所述待修改的资源信息确定创建所述容器应用的新的容器实例的宿主机。容器创建单元1053，用于根据所述具体镜像和所述待修改的资源信息在所确定的宿主机上创建新的容器实例。绑定单元1054，用于将所创建的新的容器实例与相应的容器实例IP进行绑定。
在一实施例中，新宿主机确定单元1052包括区域获取单元、宿主机集群确定单元、容器宿主机确定单元。其中，区域获取单元，用于获取所述容器应用的应用环境和容器应用的区域。宿主机集群确定单元，用于根据容器应用的应用环境和容器应用的区域确定宿主机集群。容器宿主机确定单元，用于根据所述待修改的镜像信息和所述待修改的资源信息，从所述宿主机集群中确定创建新的容器实例的宿主机。
资源检测单元106，用于若所述待修改的镜像信息与所述容器应用的镜像信息一致，检测所述待修改的配置信息中的待修改的资源信息与所述容器应用的资源信息是否一致。
资源修改单元107，用于若所述待修改的资源信息与所述容器应用的资源信息不一致，根据所述待修改的资源信息修改所述容器应用的资源，以完成所述容器应用的资源信息的修改。
在一实施例中，如图4所示，所述容器应用的配置修改装置100还包括：
数据库更新单元108，用于将所述容器应用所修改的配置信息更新到数据库中。
在一实施例中，如图4所示，所述容器应用的配置修改装置100还包括：
重启单元109，用于重启所述容器应用，以使得所述容器应用的配置修改生效。
需要说明的是，所属领域的技术人员可以清楚地了解到，上述装置和各单元的具体实现过程，可以参考前述方法实施例中的相应描述，为了描述的方便和简洁，在此不再赘述。
上述装置可以实现为一种计算机程序的形式，计算机程序可以在如图7所示的计算机设备上运行。
图7为本申请实施例提供的一种计算机设备的示意性框图。该设备为终端等设备，如PaaS平台中的服务器等。该设备100包括通过系统总线101连接的处理器102、存储器和网络接口103，其中，存储器可以包括非易失性存储介质104和内存储器105。
该非易失性存储介质104可存储操作系统1041和计算机程序1042。该非易失性存储介质中所存储的计算机程序1042被处理器102执行时，可实现上述服务器中所述的容器应用的配置修改方法。该处理器102用于提供计算和控制能力，支撑整个设备100的运行。该内存储器105为非易失性存储介质中的计算机程序的运行提供环境，该计算机程序被处理器102执行时，可使得处理器102执行上述服务器中所述的容器应用的配置修改方法。该网络接口103用于进行网络通信。本领域技术人员可以理解，图中示出的结构，仅仅是与本申请方案相关的部分结构的框图，并不构成对本申请方案所应用于其上的设备的限定，具体的设备可以包括比图中所示更多或更少的部件，或者组合某些部件，或者具有不同的部件布置。
其中，所述处理器102用于运行存储在存储器中的计算机程序，以实现上述容器应用的配置修改方法的任一实施例。
应当理解，在本申请实施例中，所称处理器102可以是中央处理单元(Central Processing Unit，CPU)，该处理器还可以是其他通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(应用程序lication Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field-Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立 硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
本领域普通技术人员可以理解的是实现上述实施例的方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成。该计算机程序可存储于一存储介质中，该存储介质可以为计算机可读存储介质。该计算机程序被该计算机系统中的至少一个处理器执行，以实现上述方法的实施例的流程步骤。
因此，本申请还提供了一种存储介质。该存储介质可以为计算机可读存储介质。该存储介质存储有计算机程序，该计算机程序当被处理器执行时实现上述容器应用的配置修改方法的任一实施例。
所述存储介质为实体的、非瞬时性的存储介质，例如可以是U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、磁碟或者光盘等各种可以存储程序代码的实体存储介质。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置、设备和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的装置、设备和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到各种等效的修改或替换，这些修改或替换都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。

Claims (20)

  1. 一种容器应用的配置修改方法，包括：
    若接收到容器应用的配置修改指令，根据所述配置修改指令调用预设修改接口，以接收通过所述预设修改接口设置的所述容器应用的待修改的配置信息；
    若接收到设置完成指令，获取所述容器应用的待修改的配置信息；
    检测所述待修改的配置信息中的待修改的镜像信息与所述容器应用的镜像信息是否一致；
    若所述待修改的镜像信息与所述容器应用的镜像信息不一致，解除所述容器应用的所有容器实例与相应的容器实例IP的绑定关系，并销毁所有容器实例；
    根据所述待修改的配置信息中的待修改的资源信息和待修改的镜像信息，创建新的容器实例，并将所创建的新的容器实例与相应的容器实例IP进行绑定，以完成所述容器应用的镜像信息的修改和更换。
  2. 根据权利要求1所述的方法，其中，所述方法还包括：
    若所述待修改的镜像信息与所述容器应用的镜像信息一致，检测所述待修改的配置信息中的待修改的资源信息与所述容器应用的资源信息是否一致；
    若所述待修改的资源信息与所述容器应用的资源信息不一致，根据所述待修改的资源信息修改所述容器应用的资源，以完成所述容器应用的资源信息的修改。
  3. 根据权利要求1所述的方法，其中，所述解除所述容器应用的所有容器实例与相应的容器实例IP的绑定关系，并销毁所有容器实例，包括：
    确定所述容器应用的所有容器实例所在的宿主机；
    解除所述宿主机上的所述容器应用的容器实例与相应的容器实例IP的绑定关系；
    销毁所述宿主机上的所述容器应用的容器实例并回收所述容器实例的资源。
  4. 根据权利要求3所述的方法，其中，所述销毁所述宿主机上的所述容器应用的容器实例并回收所述容器实例的资源，包括：
    通过容器编排工具下发销毁指令到所述容器应用的容器实例所在的宿主机，以在所述宿主机上将所述容器应用的容器实例销毁并回收所述容器实例的资源。
  5. 根据权利要求1所述的方法，其中，所述根据所述待修改的配置信息中的待修改的资源信息和待修改的镜像信息，创建新的容器实例，并将所创建的新的容器实例与相应的容器实例IP进行绑定，包括：
    确定所述容器应用所在区域下的镜像仓库，并根据所述待修改的镜像信息从所确定的镜像仓库中获取具体镜像；
    根据所述待修改的镜像信息和所述待修改的资源信息确定创建所述容器应用的新的容器实例的宿主机；
    根据所述具体镜像和所述待修改的资源信息在所确定的宿主机上创建新的容器实例；
    将所创建的新的容器实例与相应的容器实例IP进行绑定。
  6. 根据权利要求5所述的方法，其中，所述根据所述待修改的镜像信息和所述待修改的资源信息确定创建所述容器应用的新的容器实例的宿主机，包括：
    获取所述容器应用的应用环境和容器应用的区域；
    根据容器应用的应用环境和容器应用的区域确定宿主机集群；
    根据所述待修改的镜像信息和所述待修改的资源信息，从所述宿主机集群中确定创建新的容器实例的宿主机。
  7. 根据权利要求1所述的方法，其中，所述方法还包括：
    将所述容器应用所修改的配置信息更新到数据库中；
    重启所述容器应用，以使得所述容器应用的配置修改生效。
  8. 根据权利要求3所述的方法，其中，所述解除所述宿主机上的所述容器应用的容器实例与相应的容器实例IP的绑定关系之前，还包括：
    停止所述宿主机上的所述容器应用的容器实例的运行。
  9. 根据权利要求5所述的方法，其中，所述根据所述具体镜像和所述待修改的资源信息在所确定的宿主机上创建新的容器实例，包括：
    通过容器编排工具将封装后的所述待修改的资源信息和所述具体镜像发送至所确定的所述宿主机上；
    通过所述容器编排工具在所确定的所述宿主机上创建新的容器实例。
  10. 一种容器应用的配置修改装置，包括：
    设置单元，用于若接收到容器应用的配置修改指令，根据所述配置修改指令 调用预设修改接口，以接收通过所述预设修改接口设置的所述容器应用的待修改的配置信息；
    信息获取单元，用于若接收到设置完成指令，获取所述容器应用的待修改的配置信息；
    镜像检测单元，用于检测所述待修改的配置信息中的待修改的镜像信息与所述容器应用的镜像信息是否一致；
    销毁单元，用于若所述待修改的镜像信息与所述容器应用的镜像信息不一致，解除所述容器应用的所有容器实例与相应的容器实例IP的绑定关系，并销毁所有容器实例；
    创建单元，用于根据所述待修改的配置信息中的待修改的资源信息和待修改的镜像信息，创建新的容器实例，并将所创建的新的容器实例与相应的容器实例IP进行绑定，以完成所述容器应用的镜像信息的修改和更换。
  11. 一种计算机设备，包括存储器，以及与所述存储器相连的处理器；其中，所述存储器用于存储计算机程序；所述处理器用于运行所述存储器中存储的计算机程序，以执行以下步骤：
    若接收到容器应用的配置修改指令，根据所述配置修改指令调用预设修改接口，以接收通过所述预设修改接口设置的所述容器应用的待修改的配置信息；
    若接收到设置完成指令，获取所述容器应用的待修改的配置信息；
    检测所述待修改的配置信息中的待修改的镜像信息与所述容器应用的镜像信息是否一致；
    若所述待修改的镜像信息与所述容器应用的镜像信息不一致，解除所述容器应用的所有容器实例与相应的容器实例IP的绑定关系，并销毁所有容器实例；
    根据所述待修改的配置信息中的待修改的资源信息和待修改的镜像信息，创建新的容器实例，并将所创建的新的容器实例与相应的容器实例IP进行绑定，以完成所述容器应用的镜像信息的修改和更换。
  12. 根据权利要求11所述的计算机设备，其中，还包括：
    若所述待修改的镜像信息与所述容器应用的镜像信息一致，检测所述待修改的配置信息中的待修改的资源信息与所述容器应用的资源信息是否一致；
    若所述待修改的资源信息与所述容器应用的资源信息不一致，根据所述待修 改的资源信息修改所述容器应用的资源，以完成所述容器应用的资源信息的修改。
  13. 根据权利要求11所述的计算机设备，其中，所述解除所述容器应用的所有容器实例与相应的容器实例IP的绑定关系，并销毁所有容器实例，包括：
    确定所述容器应用的所有容器实例所在的宿主机；
    解除所述宿主机上的所述容器应用的容器实例与相应的容器实例IP的绑定关系；
    销毁所述宿主机上的所述容器应用的容器实例并回收所述容器实例的资源。
  14. 根据权利要求13所述的计算机设备，其中，所述销毁所述宿主机上的所述容器应用的容器实例并回收所述容器实例的资源，包括：
    通过容器编排工具下发销毁指令到所述容器应用的容器实例所在的宿主机，以在所述宿主机上将所述容器应用的容器实例销毁并回收所述容器实例的资源。
  15. 根据权利要求11所述的计算机设备，其中，所述根据所述待修改的配置信息中的待修改的资源信息和待修改的镜像信息，创建新的容器实例，并将所创建的新的容器实例与相应的容器实例IP进行绑定，包括：
    确定所述容器应用所在区域下的镜像仓库，并根据所述待修改的镜像信息从所确定的镜像仓库中获取具体镜像；
    根据所述待修改的镜像信息和所述待修改的资源信息确定创建所述容器应用的新的容器实例的宿主机；
    根据所述具体镜像和所述待修改的资源信息在所确定的宿主机上创建新的容器实例；
    将所创建的新的容器实例与相应的容器实例IP进行绑定。
  16. 根据权利要求15所述的计算机设备，其中，所述根据所述待修改的镜像信息和所述待修改的资源信息确定创建所述容器应用的新的容器实例的宿主机，包括：
    获取所述容器应用的应用环境和容器应用的区域；
    根据容器应用的应用环境和容器应用的区域确定宿主机集群；
    根据所述待修改的镜像信息和所述待修改的资源信息，从所述宿主机集群中确定创建新的容器实例的宿主机。
  17. 根据权利要求11所述的计算机设备，其中，还包括：
    将所述容器应用所修改的配置信息更新到数据库中；
    重启所述容器应用，以使得所述容器应用的配置修改生效。
  18. 根据权利要求13所述的计算机设备，其中，所述解除所述宿主机上的所述容器应用的容器实例与相应的容器实例IP的绑定关系之前，还包括：
    停止所述宿主机上的所述容器应用的容器实例的运行。
  19. 根据权利要求15所述的计算机设备，其中，所述根据所述具体镜像和所述待修改的资源信息在所确定的宿主机上创建新的容器实例，包括：
    通过容器编排工具将封装后的所述待修改的资源信息和所述具体镜像发送至所确定的所述宿主机上；
    通过所述容器编排工具在所确定的所述宿主机上创建新的容器实例。
  20. 一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行时使所述处理器执行以下操作：
    若接收到容器应用的配置修改指令，根据所述配置修改指令调用预设修改接口，以接收通过所述预设修改接口设置的所述容器应用的待修改的配置信息；
    若接收到设置完成指令，获取所述容器应用的待修改的配置信息；
    检测所述待修改的配置信息中的待修改的镜像信息与所述容器应用的镜像信息是否一致；
    若所述待修改的镜像信息与所述容器应用的镜像信息不一致，解除所述容器应用的所有容器实例与相应的容器实例IP的绑定关系，并销毁所有容器实例；
    根据所述待修改的配置信息中的待修改的资源信息和待修改的镜像信息，创建新的容器实例，并将所创建的新的容器实例与相应的容器实例IP进行绑定，以完成所述容器应用的镜像信息的修改和更换。
PCT/CN2019/103175 2019-05-17 2019-08-29 容器应用的配置修改方法、装置、计算机设备及存储介质 Ceased WO2020232887A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910413908.8 2019-05-17
CN201910413908.8A CN110262873B (zh) 2019-05-17 2019-05-17 容器应用的配置修改方法、装置、计算机设备及存储介质

Publications (1)

Publication Number Publication Date
WO2020232887A1 true WO2020232887A1 (zh) 2020-11-26

Family

ID=67913406

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/103175 Ceased WO2020232887A1 (zh) 2019-05-17 2019-08-29 容器应用的配置修改方法、装置、计算机设备及存储介质

Country Status (2)

Country Link
CN (1) CN110262873B (zh)
WO (1) WO2020232887A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114064279A (zh) * 2021-11-18 2022-02-18 广州文远知行科技有限公司 容器资源调度方法、装置、存储介质及计算机设备
CN115309457A (zh) * 2022-08-10 2022-11-08 中电金信软件有限公司 应用实例的重启方法、装置、电子设备及可读存储介质
CN120848908A (zh) * 2025-09-18 2025-10-28 摩尔线程智能科技(北京)股份有限公司 镜像生成方法、装置、设备、介质及程序产品

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110674043B (zh) * 2019-09-24 2023-09-12 聚好看科技股份有限公司 应用调试的处理方法及服务器
CN113190343B (zh) * 2020-01-14 2025-02-07 阿里巴巴集团控股有限公司 应用实例的控制方法、装置、设备及系统
CN112181597B (zh) * 2020-10-12 2024-01-19 成都精灵云科技有限公司 容器资源使用限制动态更新方法
CN113157339B (zh) * 2021-04-23 2023-07-18 东云睿连(武汉)计算技术有限公司 一种基于osb的应用服务扩展方法、系统、存储介质及装置
CN114265669B (zh) * 2021-12-30 2025-03-14 胜斗士(上海)科技技术发展有限公司 一种已销毁容器实例识别方法及装置
CN114706684B (zh) * 2022-04-15 2026-02-17 京东科技信息技术有限公司 请求处理方法、请求处理装置、计算机可读介质及设备

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107015995A (zh) * 2016-01-28 2017-08-04 华为技术有限公司 一种镜像文件的修改方法和装置
US20170249141A1 (en) * 2016-02-26 2017-08-31 Red Hat, Inc. Hot deployment in a distributed cluster system
CN107580083A (zh) * 2017-09-20 2018-01-12 北京京东尚科信息技术有限公司 一种容器ip地址分配的方法和系统
CN108683516A (zh) * 2018-03-14 2018-10-19 聚好看科技股份有限公司 一种应用实例的升级方法、装置和系统
CN108984268A (zh) * 2018-07-13 2018-12-11 郑州云海信息技术有限公司 Docker系统中容器管理的方法和装置
CN109343963A (zh) * 2018-10-30 2019-02-15 杭州数梦工场科技有限公司 一种容器集群的应用访问方法、装置及相关设备

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10346143B2 (en) * 2017-06-21 2019-07-09 Ca, Inc. Systems and methods for transforming service definitions in a multi-service containerized application
CN108958927B (zh) * 2018-05-31 2023-04-18 康键信息技术（深圳）有限公司 容器应用的部署方法、装置、计算机设备和存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107015995A (zh) * 2016-01-28 2017-08-04 华为技术有限公司 一种镜像文件的修改方法和装置
US20170249141A1 (en) * 2016-02-26 2017-08-31 Red Hat, Inc. Hot deployment in a distributed cluster system
CN107580083A (zh) * 2017-09-20 2018-01-12 北京京东尚科信息技术有限公司 一种容器ip地址分配的方法和系统
CN108683516A (zh) * 2018-03-14 2018-10-19 聚好看科技股份有限公司 一种应用实例的升级方法、装置和系统
CN108984268A (zh) * 2018-07-13 2018-12-11 郑州云海信息技术有限公司 Docker系统中容器管理的方法和装置
CN109343963A (zh) * 2018-10-30 2019-02-15 杭州数梦工场科技有限公司 一种容器集群的应用访问方法、装置及相关设备

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114064279A (zh) * 2021-11-18 2022-02-18 广州文远知行科技有限公司 容器资源调度方法、装置、存储介质及计算机设备
CN115309457A (zh) * 2022-08-10 2022-11-08 中电金信软件有限公司 应用实例的重启方法、装置、电子设备及可读存储介质
CN115309457B (zh) * 2022-08-10 2023-10-27 中电金信软件有限公司 应用实例的重启方法、装置、电子设备及可读存储介质
CN120848908A (zh) * 2025-09-18 2025-10-28 摩尔线程智能科技(北京)股份有限公司 镜像生成方法、装置、设备、介质及程序产品

Also Published As

Publication number Publication date
CN110262873A (zh) 2019-09-20
CN110262873B (zh) 2023-07-28

Similar Documents

Publication Publication Date Title
WO2020232887A1 (zh) 容器应用的配置修改方法、装置、计算机设备及存储介质
US10700947B2 (en) Life cycle management method and device for network service
US12149399B2 (en) Techniques and interfaces for troubleshooting datacenter networks
CN104410672B (zh) 网络功能虚拟化应用升级的方法、转发业务的方法及装置
CN110289982B (zh) 容器应用的扩容方法、装置、计算机设备及存储介质
WO2019237584A1 (zh) 容器的管理方法、装置、计算机设备及存储介质
WO2021051878A1 (zh) 基于用户权限的云资源获取方法、装置及计算机设备
CN114024853B (zh) 一种裸金属节点的硬件信息收集方法、系统及相关组件
WO2016078417A1 (zh) 一种虚拟化网络功能管理升级方法、装置及服务器
CN110225094B (zh) 负载均衡应用虚拟ip切换方法、装置、计算机设备及存储介质
EP3839726A1 (en) Software modification initiation method and apparatus
CN107005435B (zh) 一种网络服务描述符上架方法及装置
CN114003334B (zh) 虚拟机热迁移网络中断的优化方法、装置、设备、存储介质和系统
EP3522449A1 (en) Service state transition method and device
CN108319492B (zh) 复位物理机的方法、装置与系统
JP6104447B1 (ja) プログラム動作監視制御装置、分散オブジェクト生成管理装置、プログラム、及びプログラム動作監視システム
WO2024199358A1 (zh) 虚拟网络控制方法、装置、电子设备和存储介质
US20180089039A1 (en) Recovery of an infected and quarantined file in a primary storage controller from a secondary storage controller
CN107621963B (zh) 一种软件部署方法、软件部署系统及电子设备
CN110286996B (zh) 容器实例ip切换方法、装置、计算机设备及存储介质
CN110290172B (zh) 容器应用克隆方法、装置、计算机设备及存储介质
US10666721B2 (en) Resource management device and method
CN110275717B (zh) 私有镜像克隆方法、装置、计算机设备及存储介质
CN110278243B (zh) 负载均衡应用管理方法、装置、计算机设备及存储介质
CN109783196B (zh) 一种虚拟机的迁移方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19929627

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19929627

Country of ref document: EP

Kind code of ref document: A1