CN110990113A - Storage management method, system and related device in storage cluster - Google Patents

Storage management method, system and related device in storage cluster Download PDF

Info

Publication number
CN110990113A
CN110990113A CN201911053644.6A CN201911053644A CN110990113A CN 110990113 A CN110990113 A CN 110990113A CN 201911053644 A CN201911053644 A CN 201911053644A CN 110990113 A CN110990113 A CN 110990113A
Authority
CN
China
Prior art keywords
storage
cluster
open source
message queue
source message
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.)
Withdrawn
Application number
CN201911053644.6A
Other languages
Chinese (zh)
Inventor
王玉东
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Inspur Data Technology Co Ltd
Original Assignee
Beijing Inspur Data Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Inspur Data Technology Co Ltd filed Critical Beijing Inspur Data Technology Co Ltd
Priority to CN201911053644.6A priority Critical patent/CN110990113A/en
Publication of CN110990113A publication Critical patent/CN110990113A/en
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • G06F3/0628Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0662Virtualisation aspects
    • G06F3/0665Virtualisation aspects at area level, e.g. provisioning of virtual or logical volumes
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/54Interprogram communication
    • G06F9/546Message passing systems or structures, e.g. queues
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • G06F2009/45583Memory management, e.g. access or allocation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00Indexing scheme relating to G06F9/00
    • G06F2209/54Indexing scheme relating to G06F9/54
    • G06F2209/548Queue

Landscapes

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

Abstract

The application provides a storage management method in a storage cluster, which comprises the following steps: establishing storage by utilizing a preset type API and different storage plug-ins, wherein each storage corresponds to one storage type at the bottom layer of the storage cluster; deploying an open source message queue in the storage cluster in a DaemonSet mode; and keeping the long connection between the open source message queue and the storage cluster so that the open source message queue manages the storage volume in the storage cluster. The method and the device can realize unified management of storage, and realize automatic and efficient synchronization of the storage volume states of the cluster upper-layer platform and the cluster bottom layer. The application also provides a storage management system, a computer readable storage medium and a storage management device in the storage cluster, which have the beneficial effects.

Description

Storage management method, system and related device in storage cluster
Technical Field
The present application relates to the field of storage clusters, and in particular, to a method, a system, and a related device for storage management in a storage cluster.
Background
With the advent of the kubernets container cluster management system, the K8S provides a series of functions such as container arrangement, resource scheduling, elastic expansion, deployment management, service discovery and the like, and brings great convenience to container management. Once the container is restarted or destroyed during the life cycle of the container, the data disappears, which results in a significant reduction in the availability of the system. In order to prevent such an event, the corresponding storage is typically mounted in the corresponding application container. However, different storage vendors provide different storage, different interfaces, and interfacing storage is cumbersome and difficult to maintain.
Disclosure of Invention
The application aims to provide a storage management method, a storage management system, a computer readable storage medium and a storage management device in a storage cluster, which can effectively manage and maintain storage.
In order to solve the above technical problem, the present application provides a storage management method in a storage cluster, and the specific technical solution is as follows:
establishing storage by utilizing a preset type API and different storage plug-ins, wherein each storage corresponds to one storage type at the bottom layer of the storage cluster;
deploying an open source message queue in the storage cluster in a DaemonSet mode;
and keeping the long connection between the open source message queue and the storage cluster so that the open source message queue manages the storage volume in the storage cluster.
Wherein the managing the storage volumes in the cluster by the open source message queue comprises:
when the storage state of the storage volume changes, the open source message queue generates a corresponding state change message, and sends the state change message to a management platform of the cluster, so that the management platform updates the state information of the storage volume according to the state change message.
Wherein, still include:
modifying the storage size of the unmounted storage volume or deleting the unmounted storage volume.
Wherein deploying an open-source message queue in a DaemonSet manner in the storage cluster comprises:
and deploying an open source message queue on any node of the storage cluster in a DaemonSet mode.
Wherein the open source message queue is a RabbitMQ.
The present application further provides a storage management system in a storage cluster, including:
the storage creating module is used for creating storage by utilizing a preset type API and different storage plug-ins, and each storage corresponds to one storage type at the bottom layer of the storage cluster;
the application deployment module is used for deploying the open source message queue in the storage cluster in a DaemonSet mode;
and the storage management module is used for keeping the open source message queue in long connection with the storage cluster so that the open source message queue manages the storage volume in the storage cluster.
Wherein the storage management module comprises:
and the state management unit is used for generating a corresponding state change message by the open source message queue when the storage state of the storage volume changes, and sending the state change message to a management platform of the cluster, so that the management platform updates the state information of the storage volume according to the state change message.
Wherein, still include:
and the storage volume management unit is used for modifying the storage size of the unmounted storage volume or deleting the unmounted storage volume.
The present application also provides a computer-readable storage medium having stored thereon a computer program which, when being executed by a processor, carries out the steps of the storage management method as set forth above.
The present application further provides a storage management device, which includes a memory and a processor, where the memory stores a computer program, and the processor implements the steps of the storage management method when calling the computer program in the memory.
The application provides a storage management method in a storage cluster, which comprises the following steps: establishing storage by utilizing a preset type API and different storage plug-ins, wherein each storage corresponds to one storage type at the bottom layer of the storage cluster; deploying an open source message queue in the storage cluster in a DaemonSet mode; and keeping the long connection between the open source message queue and the storage cluster so that the open source message queue manages the storage volume in the storage cluster.
According to the method and the device, the storage type is created, and different storage manufacturers at the bottom layer are connected, so that unified management of storage is realized. And the state of a storage volume in the cluster can be monitored in real time by deploying the open source message queue in the cluster, and when the state of the storage volume changes, an upper layer is informed to modify the state of the storage volume, so that the automatic and efficient synchronization of the states of the storage volume of an upper platform of the cluster and a bottom layer of the cluster is realized. The present application further provides a storage management system, a computer-readable storage medium, and a storage management device in a storage cluster, which have the above beneficial effects and are not described herein again.
Drawings
In order to more clearly illustrate the embodiments of the present application 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 embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a storage management method in a storage cluster according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a storage management system in a storage cluster according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, fig. 1 is a flowchart of a storage management method in a storage cluster according to an embodiment of the present application, where the storage management method includes:
s101: establishing storage by utilizing a preset type API and different storage plug-ins, wherein each storage corresponds to one storage type at the bottom layer of the storage cluster;
the key point of the step is to provide storage unified management for different storage manufacturers, namely, the storage types of unified interfaces are realized by butting different storages. Because different storage manufacturers provide different storages, in kubernates, different storage plugins are selected when the storage types are created, namely different types of storage are selected, and relevant parameters required by different storage are filled in, so that different storage types can be created. In particular, it is also possible to delete a created storage type by a delete operation.
In brief, in this step, a uniform API needs to be provided, and then corresponding interface parameters are filled in for the API with respect to different storage types, so that each API can be interfaced with different types of storage, and different storage interface requirements are met.
Further, it should be noted that creating storage refers to creating a storage type, rather than creating a storage volume directly. In fact, after storage is created, it is often necessary to create a storage volume as well. And the created storage volume needs to be created according to a different storage type, namely, based on the created storage. The number of storage volumes that each storage type needs to create and the storage size of each storage volume are not limited herein.
S102: deploying an open source message queue in the storage cluster in a DaemonSet mode;
in this step, an open source message queue needs to be deployed in the storage cluster, where the deployment of which node in the cluster is not specifically limited, and the open source message queue may be deployed in a DaemonSet manner on any node of the storage cluster. Preferably, the open source message queue may be deployed on a master node of the storage cluster, and since the cluster master node does not deploy an application, the open source message queue is used for controlling other nodes in the cluster, thereby facilitating monitoring of the cluster by the open source message queue.
However, the open source message queue needs to be deployed in a DaemonSet manner, because once the open source message queue cannot be used for some reason, the monitoring on the cluster is stopped, and kubernats restarts the open source message queue, so that the open source message queue can be in a usable state at any time. In other words, deployment in the DaemonSet manner may ensure that the open source message queue is in a highly available state. Deployment in the DaemonSet mode refers to deployment by using a DaemonSet controller, and scheduling is selected by a kubernets scheduler in subsequent scheduling. Deployment in a DaemonSet mode can run a cluster storage daemon process, a log set, a monitoring background thread and the like on each host, so that the open source message queue can monitor the cluster.
The open source message queue is not particularly limited herein, and preferably, the open source message queue may be a RabbitMQ.
S103: and keeping the long connection between the open source message queue and the storage cluster so that the open source message queue manages the storage volume in the storage cluster.
In the prior art, the problem that interfaces of different storage types at the bottom layer are different is difficult to solve, so that the upper layer of a cluster is difficult to manage the storage at the bottom layer. On the other hand, in step S101 of the embodiment of the present application, a unified API is used to enable management of the storage volume.
After a storage volume is established, the state of the storage volume may change. The storage volume state mainly refers to whether the storage volume is mounted, whether the occupied storage size is changed, and information such as a user name of an occupied object can be contained. In this step, the open source message queue and the storage cluster are kept in long connection, so that the open source message queue monitors the state of the storage volume. When the storage state of the storage volume changes, the open source message queue generates a corresponding state change message, and sends the state change message to a management platform of the cluster, so that the management platform updates the state information of the storage volume according to the state change message.
Taking a rabbitMQ as an open source message queue as an example, the rabbitMQ message queue can be in long connection with kuberernates api server, the rabbitMQ can monitor the state of the kubernates storage volume, when the state of the kubernates storage volume changes, the cloud platform is informed to modify the state of the storage volume, and the state of the cloud platform storage volume is kept consistent with that of the kubernates.
Preferably, on the basis of the step, the method further comprises the following steps: modifying the storage size of the unmounted storage volume or deleting the unmounted storage volume.
The storage size of the storage volume can be modified or the storage volume can be deleted through the open source message queue. Of course, whether the storage size is modified or the storage volume is deleted, the storage volume is required to be unmounted, i.e., unused, or the normal operation of the storage cluster is affected.
According to the embodiment of the application, the storage type is created, and the unified management of storage is realized by connecting different storage manufacturers at the bottom layer. And the state of a storage volume in the cluster can be monitored in real time by deploying the open source message queue in the cluster, and when the state of the storage volume changes, an upper layer is informed to modify the state of the storage volume, so that the automatic and efficient synchronization of the states of the storage volume of an upper platform of the cluster and a bottom layer of the cluster is realized.
By the above description of the storage management method in the storage cluster provided by the present application, the storage management method is applied to a kubernates cluster. Upon restart or destruction of a container of a kubernates cluster, data stored in the container is randomly lost.
At the moment, the kubernates cluster provides a uniform API, and different storage plug-ins are combined to generate storage types corresponding to different storage manufacturers, namely, the uniform storage types of different storages are docked, so that different storage manufacturers and different docking modes at the bottom layer are shielded. And then directly creating the storage volume through the unified storage type.
And then deploying a RabbitMQ at the master node of the kubernates cluster in a DaemonSet mode, and making a RabbitMQ message queue in long connection with the kubernates api server, wherein the RabbitMQ monitors the state of a storage volume in the kubernates cluster to realize the storage management of the cluster.
Specifically, when the state of a storage volume in the kubernates cluster changes, an upper cloud platform is notified to modify the state of the storage volume, and the state of the storage volume of the cloud platform is kept consistent with that of the kubernates. The storage volumes that are rolled out at the new storage and are not mounted may be mounted by different components (e.g., deployed, stateful load mounted). Meanwhile, the storage volume which is not mounted can modify the size and carry out operations such as deletion and the like.
In the following, a storage management system in a storage cluster provided in an embodiment of the present application is introduced, and the storage management system described below and the storage management method described above may be referred to correspondingly.
Referring to fig. 2, fig. 2 is a schematic structural diagram of a storage management system in a storage cluster according to an embodiment of the present application, and the present application further provides a storage management system in a storage cluster, including:
a storage creating module 100, configured to create storages using a preset type API and different storage plug-ins, where each storage corresponds to a storage type of the bottom layer of the storage cluster;
an application deployment module 200, configured to deploy an open-source message queue in a DaemonSet manner in the storage cluster;
the storage management module 300 is configured to keep the open source message queue in long connection with the storage cluster, so that the open source message queue manages a storage volume in the storage cluster.
Based on the above embodiment, as a preferred embodiment, the storage management module 300 includes:
and the state management unit is used for generating a corresponding state change message by the open source message queue when the storage state of the storage volume changes, and sending the state change message to a management platform of the cluster, so that the management platform updates the state information of the storage volume according to the state change message.
Based on the above embodiment, as a preferred embodiment, the storage management system may further include:
and the storage volume management unit is used for modifying the storage size of the unmounted storage volume or deleting the unmounted storage volume.
Based on the foregoing embodiment, as a preferred embodiment, the application deployment module 200 is specifically a module for deploying an open-source message queue in a DaemonSet manner on any node of the storage cluster.
The present application also provides a computer readable storage medium having stored thereon a computer program which, when executed, may implement the steps provided by the above-described embodiments. The storage medium may include: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The present application further provides a storage management device, which may include a memory and a processor, where the memory stores a computer program, and the processor may implement the steps provided in the foregoing embodiments when calling the computer program in the memory. Of course, the storage management device may also include various network interfaces, power supplies, and other components.
The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. For the system provided by the embodiment, the description is relatively simple because the system corresponds to the method provided by the embodiment, and the relevant points can be referred to the method part for description.
The principles and embodiments of the present application are explained herein using specific examples, which are provided only to help understand the method and the core idea of the present application. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.
It is further noted that, in the present specification, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, 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 identical elements in a process, method, article, or apparatus that comprises the element.

Claims (10)

1. A method for storage management in a storage cluster, comprising:
establishing storage by utilizing a preset type API and different storage plug-ins, wherein each storage corresponds to one storage type at the bottom layer of the storage cluster;
deploying an open source message queue in the storage cluster in a DaemonSet mode;
and keeping the long connection between the open source message queue and the storage cluster so that the open source message queue manages the storage volume in the storage cluster.
2. The storage management method according to claim 1, wherein the managing storage volumes in the cluster by the open source message queue comprises:
when the storage state of the storage volume changes, the open source message queue generates a corresponding state change message, and sends the state change message to a management platform of the cluster, so that the management platform updates the state information of the storage volume according to the state change message.
3. The storage management method according to claim 1, further comprising:
modifying the storage size of the unmounted storage volume or deleting the unmounted storage volume.
4. The storage management method according to claim 1, wherein deploying an open source message queue in a DaemonSet manner in the storage cluster comprises:
and deploying an open source message queue on any node of the storage cluster in a DaemonSet mode.
5. The storage management method according to claim 1, wherein the open source message queue is a RabbitMQ.
6. A storage management system in a storage cluster, comprising:
the storage creating module is used for creating storage by utilizing a preset type API and different storage plug-ins, and each storage corresponds to one storage type at the bottom layer of the storage cluster;
the application deployment module is used for deploying the open source message queue in the storage cluster in a DaemonSet mode;
and the storage management module is used for keeping the open source message queue in long connection with the storage cluster so that the open source message queue manages the storage volume in the storage cluster.
7. The storage management system of claim 6, wherein the storage management module comprises:
and the state management unit is used for generating a corresponding state change message by the open source message queue when the storage state of the storage volume changes, and sending the state change message to a management platform of the cluster, so that the management platform updates the state information of the storage volume according to the state change message.
8. The storage management system according to claim 6, further comprising:
and the storage volume management unit is used for modifying the storage size of the unmounted storage volume or deleting the unmounted storage volume.
9. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the storage management method according to any one of claims 1 to 5.
10. A storage management device comprising a memory in which a computer program is stored and a processor which, when calling the computer program in the memory, implements the steps of the storage management method according to any one of claims 1 to 5.
CN201911053644.6A 2019-10-31 2019-10-31 Storage management method, system and related device in storage cluster Withdrawn CN110990113A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911053644.6A CN110990113A (en) 2019-10-31 2019-10-31 Storage management method, system and related device in storage cluster

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911053644.6A CN110990113A (en) 2019-10-31 2019-10-31 Storage management method, system and related device in storage cluster

Publications (1)

Publication Number Publication Date
CN110990113A true CN110990113A (en) 2020-04-10

Family

ID=70082809

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911053644.6A Withdrawn CN110990113A (en) 2019-10-31 2019-10-31 Storage management method, system and related device in storage cluster

Country Status (1)

Country Link
CN (1) CN110990113A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112783669A (en) * 2021-01-06 2021-05-11 北京同有飞骥科技股份有限公司 Distributed storage management method and system

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104156216A (en) * 2014-08-14 2014-11-19 浪潮(北京)电子信息产业有限公司 Heterogeneous storage management system and method oriented to cloud computing
US9479585B1 (en) * 2010-07-13 2016-10-25 Netapp, Inc. Policy based service management in a clustered network storage system
CN109491859A (en) * 2018-10-16 2019-03-19 华南理工大学 For the collection method of container log in Kubernetes cluster

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9479585B1 (en) * 2010-07-13 2016-10-25 Netapp, Inc. Policy based service management in a clustered network storage system
CN104156216A (en) * 2014-08-14 2014-11-19 浪潮(北京)电子信息产业有限公司 Heterogeneous storage management system and method oriented to cloud computing
CN109491859A (en) * 2018-10-16 2019-03-19 华南理工大学 For the collection method of container log in Kubernetes cluster

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112783669A (en) * 2021-01-06 2021-05-11 北京同有飞骥科技股份有限公司 Distributed storage management method and system

Similar Documents

Publication Publication Date Title
CN111290834B (en) Method, device and equipment for realizing high service availability based on cloud management platform
CN111800282B (en) Network system, instance management and control method, device and storage medium
US8239536B2 (en) System for generic service management in a distributed and dynamic resource environment, providing constant service access to users
CN113037794B (en) Method, device and system for computing resource allocation scheduling
WO2020248507A1 (en) Container cloud-based system resource monitoring method and related device
JP4315057B2 (en) Information processing apparatus, information processing method, and program
EP2176778A2 (en) Progressively implementing declarative models in distributed systems
WO2009005992A2 (en) Tuning and optimizing distributed systems with declarative models
CN109558260B (en) Kubernetes fault elimination system, method, equipment and medium
CN112328170B (en) Cloud hard disk capacity expansion method and device, computer equipment and storage medium
CN114090176A (en) Kubernetes-based container scheduling method
CN113626286A (en) Multi-cluster instance processing method and device, electronic equipment and storage medium
WO2018196462A1 (en) Resource scheduling apparatus, resource scheduling system and resource scheduling method
CN113382077B (en) Micro-service scheduling method, micro-service scheduling device, computer equipment and storage medium
CN112363820A (en) Uniform resource pooling container scheduling engine based on heterogeneous hardware and scheduling method thereof
CN114706690B (en) Method and system for sharing GPU (graphics processing Unit) by Kubernetes container
CN111786829A (en) Automatic management method for cloud firewall full life cycle
CN110990113A (en) Storage management method, system and related device in storage cluster
KR20100108578A (en) System resource influenced staged shutdown
CN114816272B (en) Magnetic disk management system under Kubernetes environment
CN112559127A (en) Virtual machine creation method, device, host and storage medium
CN116881012A (en) Container application vertical capacity expansion method, device, equipment and readable storage medium
CN116166413A (en) Lifecycle management for workloads on heterogeneous infrastructure
CN111767113A (en) Method and device for realizing container eviction
CN112187753B (en) Data updating method, device, equipment and readable storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
WW01 Invention patent application withdrawn after publication

Application publication date: 20200410

WW01 Invention patent application withdrawn after publication