WO2024130997A1 - 一种节点配置方法、装置、设备、非易失性可读存储介质及服务器 - Google Patents
一种节点配置方法、装置、设备、非易失性可读存储介质及服务器 Download PDFInfo
- Publication number
- WO2024130997A1 WO2024130997A1 PCT/CN2023/101927 CN2023101927W WO2024130997A1 WO 2024130997 A1 WO2024130997 A1 WO 2024130997A1 CN 2023101927 W CN2023101927 W CN 2023101927W WO 2024130997 A1 WO2024130997 A1 WO 2024130997A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- configuration
- node
- configuration file
- difference
- incremental
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 71
- 238000004590 computer program Methods 0.000 claims description 15
- 230000002159 abnormal effect Effects 0.000 claims description 4
- 230000004044 response Effects 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 4
- 238000011161 development Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 101001121408 Homo sapiens L-amino-acid oxidase Proteins 0.000 description 1
- 102100026388 L-amino-acid oxidase Human genes 0.000 description 1
- 101100012902 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) FIG2 gene Proteins 0.000 description 1
- 101100233916 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) KAR5 gene Proteins 0.000 description 1
- 230000005856 abnormality Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
Definitions
- the present application relates to the field of cloud computing platforms, and in particular to a node configuration method.
- the present application also relates to a node configuration device, equipment, non-volatile readable storage medium and server.
- Kubernetes (K8s) is a new container cluster management system based on container technology. Based on Docker technology, it provides deployment and operation, resource scheduling, service discovery, and dynamic scaling functions for containerized applications, providing the convenience of large-scale container cluster management.
- Cloud computing platforms are usually composed of many business modules with complex functions. Whether each business module in the cloud computing platform can operate normally and provide services depends on the correctness of the configuration files of each business module. Therefore, when deploying the cloud computing platform on K8s, a very important task is to generate correct configuration files for each business module and provide them to the business modules for use, so that they can operate normally and provide services.
- the existing technology lacks a mature configuration method, which makes it difficult to efficiently configure the configuration files of the business modules.
- the purpose of this application is to provide a node configuration method, which not only realizes the configuration of the business module efficiently, but also can perform different configurations according to the characteristics of the node.
- Deploying differentiated nodes in a cloud computing platform improves the flexibility of the cloud computing platform architecture;
- another object of the present application is to provide a node configuration device, equipment, non-volatile readable storage medium and server, which not only efficiently realizes the configuration of business modules, but also can perform different configurations according to the characteristics of the nodes.
- differentiated nodes can be deployed in the cloud computing platform, thereby improving the flexibility of the cloud computing platform architecture.
- the present application provides a node configuration method, including:
- the pre-stored differential incremental configuration files corresponding to the own node and the business module to be configured are obtained from K8s as follows:
- obtaining a differential incremental configuration file that matches the node identification information from the node differential incremental configuration file is specifically as follows:
- the business module to be configured is directly configured according to the default configuration file corresponding to the business module to be configured;
- the difference incremental configuration file matching the node identification information is obtained from the node difference incremental configuration total file.
- adding the difference between the difference incremental configuration file and the default configuration file to the default configuration file is specifically as follows:
- the configuration block to be checked does not exist in the default configuration file, then the configuration block to be checked is added to the default configuration file;
- the difference between the configuration block to be checked and the default configuration file is added to the default configuration file
- a step of determining a configuration block to be checked from the differential incremental configuration file is performed.
- adding the difference between the configuration block to be checked and the default configuration file to the default configuration file is specifically as follows:
- a step of determining a difference incremental configuration item to be checked from the configuration block to be checked is performed.
- the node configuration method further includes:
- the node configuration method further includes:
- obtaining the pre-stored node difference incremental configuration total file corresponding to the business module to be configured from K8s is specifically:
- the difference increment configuration items include CPU over-allocation ratio, memory over-allocation ratio, and number of occupied threads.
- the differential delta profile includes a delta profile configuration field
- the incremental configuration file configuration field includes a configuration file type field for describing the file type, a location field for describing the location of the differential incremental configuration file in the node, and a configuration block field for accommodating differential incremental configuration items.
- the differential delta configuration file further includes a reserved information field, so that the reserved information is obtained from the reserved information field or the reserved information is filled into the reserved information field.
- obtaining the pre-stored node difference incremental configuration total file corresponding to the business module to be configured from K8s is specifically:
- the pre-stored node difference incremental configuration total file corresponding to the business module to be configured is obtained from K8s.
- obtaining the node identification information of the own node is specifically as follows:
- the step of obtaining the difference incremental configuration file matching the node identification information from the node difference incremental configuration total file is executed;
- control prompter prompts that the node identification information acquisition is abnormal.
- the node configuration method further includes:
- the step of determining the subordinate business modules to be configured is performed;
- control prompter When all subordinate business modules are configured, the control prompter prompts that the business module configuration is completed.
- the node configuration method further includes:
- the control prompter will prompt that reconfiguration is required.
- the node configuration method further includes:
- the faulty device is a preset device related to the differential incremental configuration file, the original default configuration files of each subordinate business module are obtained;
- the present application also provides a node configuration device, including:
- a determination module is used to determine the subordinate business modules to be configured
- the first acquisition module is used to obtain the pre-stored differential incremental configuration files corresponding to its own node and the business module to be configured from K8s;
- the second acquisition module is used to acquire a pre-stored default configuration file corresponding to the service module to be configured
- the merge module is used to add the difference between the differential incremental configuration file and the default configuration file to the default configuration file
- the execution module is used to configure the business module to be configured according to the default configuration file after adding the difference content.
- the present application also provides a node configuration device, including:
- a processor is used to implement the steps of the above node configuration method when executing a computer program.
- the present application also provides a server, including a server body and a node configuration device as above connected to the server body.
- the present application also provides a non-volatile readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above node configuration method are implemented.
- This application provides a node configuration method. Considering that for the same business module located in different nodes, the difference in the nodes will also lead to different configuration files required by the business module, this application can obtain the pre-stored configuration files of the business module to be configured from K8s.
- the differential incremental configuration file corresponding to the business module can then add the difference content of the default configuration file corresponding to the business module to be configured in the differential incremental configuration file to the default configuration file, thereby obtaining the configuration file required for the business module to be configured under the node, so as to complete the configuration of the business module. It not only efficiently realizes the configuration of the business module, but also can perform different configurations according to the characteristics of the node. In this case, differentiated nodes can be deployed in the cloud computing platform, which improves the flexibility of the cloud computing platform architecture.
- the present application also provides a node configuration device, equipment, non-volatile readable storage medium and server, which have the same beneficial effects as the above node configuration method.
- FIG1 is a schematic diagram of a flow chart of a node configuration method provided by the present application.
- FIG2 is a schematic diagram of the structure of a node configuration device provided by the present application.
- FIG3 is a schematic diagram of the structure of a node configuration device provided in the present application.
- the core of the present application is to provide a node configuration method, which not only efficiently realizes the configuration of the business module, but also can perform different configurations according to the characteristics of the node.
- differentiated nodes can be deployed in the cloud computing platform, thereby improving the flexibility of the cloud computing platform architecture;
- another core of the present application is to provide a node configuration device, equipment, non-volatile readable storage medium and server, which not only efficiently realizes the configuration of the business module, but also can perform different configurations according to the characteristics of the node.
- differentiated nodes can be deployed in the cloud computing platform, thereby improving the flexibility of the cloud computing platform architecture.
- FIG. 1 is a schematic diagram of a flow chart of a node configuration method provided by the present application.
- the node configuration method includes:
- both node A and node B have business module A, and there are obvious differences in structure and performance between node A and node B.
- node A has 4 CPUs
- node B has 8 CPUs.
- the configuration content required for business module A in node A and business module A in node B is also different. Therefore, different configurations for business module A need to be implemented.
- the present application intends to configure its own subordinate business modules through the nodes in the cloud computing platform. Therefore, it is possible to first determine its own subordinate business modules to be configured so that the business modules to be configured can be configured in subsequent steps.
- the embodiments of the present application can be applied to a single node of a cloud computing platform, and the number of business modules that need to be configured contained in a single node can also be multiple, which is not limited in the embodiments of the present application.
- the cloud computing platform where the node in the embodiment of the present application is located can be of various types, for example, it can be an OpenStack cloud computing platform, etc., and the embodiment of the present application is not limited here.
- OpenStack is an open source cloud computing management platform. Its main purpose is to hide the details of the underlying physical hardware through virtualization technology, and provide users with resource isolation and resource usage restrictions at the computing, storage and network levels, so that users can see it as if they have a single machine.
- OpenStack has become increasingly mature and stable. While providing high availability, it also has flexible scalability. Therefore, OpenStack has been widely used in all walks of life. It has become a trend to deploy the OpenStack cloud computing platform on Kubernetes to improve the deployment flexibility, scalability, fault self-recovery and other capabilities of the OpenStack cloud computing platform.
- S102 Obtain pre-stored differential incremental configuration files corresponding to the node itself and the business module to be configured from K8s;
- the differential incremental configuration file corresponding to each node and each business module to be configured can be pre-stored in the K8s platform, and then each node can obtain it uniformly from the K8s platform, thereby improving data acquisition efficiency.
- the difference incremental configuration file can serve as the data basis for subsequent steps.
- the differential incremental configuration files in the embodiments of the present application not only correspond to the business module to be configured, but also need to correspond to the node. This can be achieved in the generation stage of the differential incremental configuration files.
- the corresponding differential incremental configuration files can be designed according to the characteristics of the node and the characteristics of the business module, so that for the same business module located at different nodes, different differential incremental configuration files can be designed according to the differences in the nodes where they are located, so that differentiated configuration of the business module can be achieved subsequently.
- the embodiment of the present application can obtain the pre-stored default configuration file corresponding to the business module to be configured, so as to serve as the data basis for subsequent steps. It can be seen that the difference incremental configuration file can actually be based on the various configuration items contained in the default configuration file, and specifies a small part of the configuration items that need special settings due to the different characteristics of the nodes where the business modules are located.
- the pre-storage location of the default configuration file can be freely set, for example, it can be pre-stored inside each node, etc., and the embodiment of the present application does not limit this.
- the difference between the differential incremental configuration file and the default configuration file can be added to the default configuration file, so as to obtain a default configuration file with added difference content, and use it as the data basis for subsequent steps.
- S105 configuring the service module to be configured according to the default configuration file after adding the difference content.
- the business module to be configured can be configured according to the current default configuration file.
- the configured business module also meets the relevant requirements of the node when running, which means that each business module can run smoothly and efficiently.
- the differential incremental configuration files in the embodiments of the present application can be designed for each node, that is, corresponding differentiated configuration files are designed for the scenarios of the same business module in different nodes, the structure and configuration of each node can also be flexibly designed in this case, thereby improving the flexibility of building the cloud computing platform and improving the user experience.
- the present application provides a node configuration method. Taking into account that for the same business module located at different nodes, the difference in the nodes will also lead to different configuration files required by the business module, the present application can obtain the pre-stored differential incremental configuration files corresponding to its own node and the business module to be configured from K8s for the business module to be configured, and then the difference content of the default configuration file corresponding to the business module to be configured in the differential incremental configuration file can be added to the default configuration file, thereby obtaining the configuration file required by the business module to be configured under the node, so as to complete the configuration of the business module. Not only the configuration of the business module is efficiently realized, but also different configurations can be performed according to the characteristics of the node. In this case, differentiated nodes can be deployed in the cloud computing platform, thereby improving the flexibility of the cloud computing platform architecture.
- the pre-stored differential incremental configuration files corresponding to the own node and the business module to be configured are obtained from K8s as follows:
- a node differential incremental configuration master file (referred to as the master file) is designed for each business module in the embodiment of the present application.
- the master file can accommodate the differential incremental configuration files of a specific business module in different nodes of the cloud computing platform, which not only reduces the space occupancy, but also can quickly find the unique master file corresponding to the business module to be configured during the search, thereby improving the configuration efficiency.
- the total file can be organized using the yml format, which is not limited in the embodiment of the present application.
- the difference incremental configuration file corresponding to the node itself can also be obtained from the node difference incremental configuration total file in other ways, and the embodiment of the present application is not limited here.
- obtaining a differential incremental configuration file that matches the node identification information from the node differential incremental configuration file is specifically as follows:
- the business module to be configured is directly configured according to the default configuration file corresponding to the business module to be configured;
- the difference incremental configuration file matching the node identification information is obtained from the node difference incremental configuration total file.
- the business module to be configured in the node itself may not need to be differentially configured, so in this case, the differential incremental configuration file corresponding to the node may not be designed. Therefore, in the embodiment of the present application, it is possible to determine whether there is a differential incremental configuration file matching the node identification information in the node differential incremental configuration total file. If not, the business module to be configured can be directly configured according to the default configuration file corresponding to the business module to be configured. If it exists, the differential incremental configuration file matching the node identification information can be obtained from the node differential incremental configuration total file.
- adding the difference between the difference incremental configuration file and the default configuration file to the default configuration file is specifically as follows:
- the difference between the configuration block to be checked and the default configuration file is added to the default configuration file
- a step of determining a configuration block to be checked from the differential incremental configuration file is performed.
- the differential incremental configuration items of different categories can be placed in different configuration blocks in the differential incremental configuration file for easy management and search. Then, when adding the difference content between the differential incremental configuration file and the default configuration file to the default configuration file, each configuration block can be traversed in turn in a traversal manner. The configuration blocks that do not exist in the default configuration file can be directly added to the default configuration file.
- the difference content between the configuration block to be checked and the default configuration file can be added to the default configuration file until all the configuration blocks in the differential incremental configuration file are traversed and checked, thereby avoiding omissions and ensuring the reliable implementation of the configuration work.
- adding the difference between the configuration block to be checked and the default configuration file to the default configuration file is specifically as follows:
- the difference incremental configuration item to be checked is added to the default configuration file
- the difference incremental configuration item to be checked exists in the default configuration file, the difference incremental configuration item to be checked is updated to the default configuration file;
- a step of determining a difference incremental configuration item to be checked from the configuration block to be checked is performed.
- a single configuration block may also have multiple differential incremental configuration items.
- the embodiment of the present application can also adopt a traversal method to check one by one. If it exists in the default configuration file, there may also be numerical differences. Since the differential incremental configuration item has a higher priority, the differential incremental configuration item to be checked can be updated (overwritten or replaced) to the default configuration file. If it does not exist in the default configuration file, the differential incremental configuration item to be checked can be added to the default configuration file, further avoiding omissions and ensuring the reliable progress of the configuration work.
- the node configuration method further includes:
- the embodiment of the present application can execute the step of obtaining pre-stored differential incremental configuration files corresponding to its own node and the business module to be configured from K8s at preset intervals, so as to timely discover the updated differential incremental configuration files and update the designed business modules in time, with a high degree of automation.
- the preset period can be set independently, and the embodiment of the present application does not limit it here.
- the node configuration method further includes:
- the staff may directly inform the node in the form of configuration instructions, so in the embodiment of the present application, it is possible to respond to the received configuration instructions, extract the differential incremental configuration items in the configuration instructions, and determine the business modules corresponding to the extracted differential incremental configuration items, and then update the extracted differential incremental configuration items to their corresponding business modules, thereby providing a way to update the business module configuration in a timely manner, improving work efficiency and user experience.
- obtaining the pre-stored node difference incremental configuration total file corresponding to the business module to be configured from K8s is specifically:
- a kubernetes configmap resource can be created using the master file; when the business module is deployed, the high-priority node difference incremental configuration file in the configmap is mounted to the relevant directory in the business module pod to execute the above method and obtain it from the K8s Config Map resource, which has the advantages of fast reading rate and strong reliability.
- the pre-stored node difference incremental configuration total file corresponding to the business module to be configured can also be obtained from other locations, and the embodiment of the present application is not limited here.
- the difference increment configuration items include CPU over-allocation ratio, memory over-allocation ratio, and number of occupied threads.
- the CPU over-allocation ratio is related to the number of CPU cores and CPU frequency of the node
- the memory over-allocation ratio is related to the memory capacity
- the number of occupied threads is related to the number of CPU cores, CPU frequency and memory capacity of the node, which are relatively important difference incremental configuration items.
- difference increment configuration item can also be other specific content, which is not limited in the embodiments of the present application.
- the differential delta profile includes a delta profile configuration field
- the incremental configuration file configuration field includes a configuration file type field for describing the file type, a location field for describing the location of the differential incremental configuration file in the node, and a configuration block field for accommodating differential incremental configuration items.
- some parameters of a rich differential incremental configuration file can be specified in the incremental configuration file configuration field.
- the configuration block field for accommodating differential incremental configuration items it can also include a configuration file type field for describing the file type and a location field for describing the location of the differential incremental configuration file in the node.
- the matching parsing method can be found through the file type, and the location of the differential incremental configuration file in the node can be found through the location, which improves the reliability of the configuration work.
- the differential incremental configuration file may also include other contents, which are not limited in the embodiments of the present application.
- the differential delta configuration file further includes a reserved information field, so that the reserved information is obtained from the reserved information field or the reserved information is filled into the reserved information field.
- the differential incremental configuration files in the embodiments of the present application may also include a reserved information field so as to obtain reserved information from the reserved information field or fill the reserved information into the reserved information field.
- obtaining the pre-stored node difference incremental configuration total file corresponding to the business module to be configured from K8s is specifically:
- the pre-stored node difference incremental configuration total file corresponding to the business module to be configured is obtained from K8s.
- the total file contains differential incremental configuration files of multiple nodes
- the total file generally exists.
- the node may not be able to obtain the total file.
- the configuration of the business module cannot be carried out. Therefore, an alarm can be issued in this case so that the staff can be informed and repaired in time, further improving the reliability of the configuration work.
- obtaining the node identification information of the own node is specifically as follows:
- the step of obtaining the difference incremental configuration file matching the node identification information from the node difference incremental configuration total file is performed;
- control prompter prompts that the node identification information acquisition is abnormal.
- the control prompter can prompt the node identification information acquisition abnormality, so that the staff can be informed and perform maintenance in time, thereby further improving the reliability of the configuration work.
- the prompter can be of various types, such as a display, etc., which is not limited in the embodiments of the present application.
- the node configuration method further includes:
- the step of determining the subordinate business module to be configured is performed
- control prompter When all subordinate business modules are configured, the control prompter prompts that the business module configuration is completed.
- the configuration work for multiple business modules existing in the node in order to automatically execute the configuration work for multiple business modules existing in the node, in the embodiment of the present application, after configuring a business module to be configured, it can be determined whether all the business modules under it have been configured. When all the business modules under it have not been fully configured, it can execute the steps of determining the business modules under it to be configured, thereby improving the degree of automation. When the execution is completed, the prompter can be controlled to prompt that the business module configuration is completed, so that the staff can understand the progress of the business module configuration work.
- the node configuration method further includes:
- the control prompter will prompt that reconfiguration is required.
- the embodiment of the present application proposes a monitoring mechanism, which can determine whether the current faulty device of the node itself belongs to the preset device related to the differential incremental configuration file. If it does, the prompter can be controlled to prompt that reconfiguration is required, so that the staff can discover the situation in time and control the node to repair the faulty device or reconfigure the business module, etc., thereby improving the working stability of the cloud computing platform.
- the node configuration method further includes:
- the faulty device is a preset device related to the differential incremental configuration file, the original default configuration files of each subordinate business module are obtained;
- the embodiment of the present application can obtain the original default configuration files of each subordinate business module, and then configure the corresponding business modules according to the default configuration files, that is, to meet the basic work of the business modules and ensure that the business modules continue to work.
- FIG. 2 is a schematic diagram of the structure of a node configuration device provided by the present application, wherein the node configuration device includes:
- a determination module 21 is used to determine the subordinate business modules to be configured
- the first acquisition module 22 is used to obtain a pre-stored differential incremental configuration file corresponding to its own node and the business module to be configured from K8s;
- the second acquisition module 23 is used to acquire a pre-stored default configuration file corresponding to the service module to be configured
- a merging module 24 is used to add the difference between the difference incremental configuration file and the default configuration file to the default configuration file
- the execution module 25 is used to configure the service module to be configured according to the default configuration file after adding the difference content.
- the present application provides a node configuration device. Taking into account that for the same business module located at different nodes, the difference in the nodes will also lead to different configuration files required by the business module, the present application can obtain the pre-stored differential incremental configuration files corresponding to its own node and the business module to be configured from K8s for the business module to be configured, and then the difference content of the default configuration file corresponding to the business module to be configured in the differential incremental configuration file can be added to the default configuration file, thereby obtaining the configuration file required by the business module to be configured under the node, so as to complete the configuration of the business module. Not only the configuration of the business module is efficiently realized, but also different configurations can be performed according to the characteristics of the node. In this case, differentiated nodes can be deployed in the cloud computing platform, thereby improving the flexibility of the cloud computing platform architecture.
- FIG. 3 is a schematic diagram of the structure of a node configuration device provided by the present application, wherein the node configuration device includes:
- the processor 32 is used to implement the steps of the node configuration method in the above-mentioned embodiment when executing the computer program.
- the memory includes a non-volatile storage medium and an internal memory.
- the non-volatile storage medium stores an operating system and computer-readable instructions
- the internal memory provides an environment for the operation of the operating system and computer-readable instructions in the non-volatile storage medium.
- the processor executes the computer program stored in the memory, the following steps can be implemented: determine the business module to be configured under itself; obtain the pre-stored differential incremental configuration file corresponding to its own node and the business module to be configured from K8s; obtain the pre-stored default configuration file corresponding to the business module to be configured; add the difference content between the differential incremental configuration file and the default configuration file to the default configuration file; configure the business module to be configured according to the default configuration file after adding the difference content.
- the present application provides a node configuration device. Considering that for the same business module located in different nodes, the difference in the nodes will also lead to the difference in the configuration files required by the business module.
- the present application can obtain the pre-stored difference incremental configuration files corresponding to its own node and the business module to be configured from K8s, and then can convert the difference incremental configuration files corresponding to the business module to be configured into the node configuration file.
- the difference content of the default configuration file corresponding to the business module is added to the default configuration file, so as to obtain the configuration file required by the business module to be configured under the node, so as to complete the configuration of the business module. It not only realizes the configuration of the business module efficiently, but also can make different configurations according to the characteristics of the node. In this case, differentiated nodes can be deployed in the cloud computing platform, which improves the flexibility of the cloud computing platform architecture.
- the present application also provides a server, including a server body and a node configuration device as in the aforementioned embodiment connected to the server body.
- the present application provides a server. Taking into account that for the same business module located at different nodes, the difference in the nodes will also lead to different configuration files required by the business module, the present application can obtain the pre-stored differential incremental configuration files corresponding to its own node and the business module to be configured from K8s for the business module to be configured, and then the difference content of the default configuration file corresponding to the business module to be configured in the differential incremental configuration file can be added to the default configuration file, thereby obtaining the configuration file required by the business module to be configured under the node, so as to complete the configuration of the business module. Not only the configuration of the business module is efficiently realized, but also different configurations can be performed according to the characteristics of the node. In this case, differentiated nodes can be deployed in the cloud computing platform, thereby improving the flexibility of the cloud computing platform architecture.
- the present application also provides a non-volatile readable storage medium, on which a computer program is stored.
- a computer program is stored on which a computer program is stored.
- the non-volatile readable storage medium may include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program code.
- the storage medium stores a computer program, and when the computer program is executed by the processor, the following steps are implemented: determine the business module to be configured under itself; obtain the difference incremental configuration file pre-stored in K8s corresponding to its own node and the business module to be configured; obtain the pre-stored default configuration file corresponding to the business module to be configured; The difference content between the differential incremental configuration file and the default configuration file is added to the default configuration file; and the business module to be configured is configured according to the default configuration file after the difference content is added.
- the present application provides a non-volatile readable storage medium. Considering that for the same business module located at different nodes, the difference in the nodes will also lead to different configuration files required by the business module, the present application can obtain the pre-stored differential incremental configuration files corresponding to its own node and the business module to be configured from K8s for the business module to be configured, and then the difference content of the default configuration file corresponding to the business module to be configured in the differential incremental configuration file can be added to the default configuration file, thereby obtaining the configuration file required by the business module to be configured under the node, so as to complete the configuration of the business module. Not only the configuration of the business module is efficiently realized, but also different configurations can be performed according to the characteristics of the node. In this case, differentiated nodes can be deployed in the cloud computing platform, thereby improving the flexibility of the cloud computing platform architecture.
- each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same and similar parts between the embodiments can be referred to each other.
- the description is relatively simple, and the relevant parts can be referred to the method part description.
- relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations.
- the term "includes”, “comprising” or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, article or equipment including a series of elements includes not only those elements, but also other elements that are not explicitly listed, or also includes elements inherent to such process, method, article or equipment. In the absence of more restrictions, the elements defined by the sentence "including one" do not exclude the existence of other identical elements in the process, method, article or equipment including the element.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
本申请公开了一种节点配置方法、装置、设备、非易失性可读存储介质及服务器，属于云计算平台领域，用于对部署于K8s平台的云计算平台中节点的业务模块进行配置。本申请对于待配置业务模块，可以从K8s中获取预存的与自身节点以及待配置业务模块对应的差异增量配置文件，接着可以将差异增量配置文件中与待配置业务模块对应的默认配置文件的差异内容，添加至默认配置文件，从而得到该节点下的待配置业务模块所需的配置文件，以便完成对于该业务模块的配置，不但高效地实现了业务模块的配置，而且可以针对所在节点的特点进行不同的配置，在这种情况下便可以在云计算平台中部署差异化的节点，提升了云计算平台架构的灵活性。
Description
相关申请的交叉引用
本申请要求于2022年12月21日提交中国专利局，申请号为2022116451462，申请名称为“一种节点配置方法、装置、设备、可读存储介质及服务器”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
本申请涉及云计算平台领域，特别是涉及一种节点配置方法，本申请还涉及一种节点配置装置、设备、非易失性可读存储介质及服务器。
Kubernetes(K8s)是一种全新的基于容器技术的容器集群管理系统，其在docker技术的基础上，为容器化的应用提供部署运行、资源调度、服务发现和动态伸缩等功能，提供了大规模容器集群管理的便捷性。
云计算平台通常由很多业务模块组成，且功能复杂，云计算平台中的每一个业务模块是否能够正常运行并提供服务，则依赖于每一个业务模块的配置文件的正确性，因此，在将云计算平台部署在K8s上时，很重要的一个工作就是为每一个业务模块生成正确的配置文件，并将其提供给业务模块使用，以使其正常运行并提供服务，然而现有技术中缺少一种成熟的配置方法，导致难以高效的对业务模块进行配置文件的配置。
因此，如何提供一种解决上述技术问题的方案是本领域技术人员目前需要解决的问题。
发明内容
本申请的目的是提供一种节点配置方法，不但高效的实现了业务模块的配置，而且可以针对所在节点的特点进行不同的配置，在这种情况下便可以
在云计算平台中部署差异化的节点，提升了云计算平台架构的灵活性；本申请的另一目的是提供一种节点配置装置、设备、非易失性可读存储介质及服务器，不但高效的实现了业务模块的配置，而且可以针对所在节点的特点进行不同的配置，在这种情况下便可以在云计算平台中部署差异化的节点，提升了云计算平台架构的灵活性。
为解决上述技术问题，本申请提供了一种节点配置方法，包括：
确定自身下属的待配置业务模块；
从K8s中获取预存的，与自身节点以及待配置业务模块对应的差异增量配置文件；
获取预存的与待配置业务模块对应的默认配置文件；
将差异增量配置文件中与默认配置文件的差异内容，添加至默认配置文件；
根据增加差异内容后的默认配置文件配置待配置业务模块。
在一些实施例中，从K8s中获取预存的，与自身节点以及待配置业务模块对应的差异增量配置文件具体为：
从K8s中获取预存的与待配置业务模块对应的节点差异增量配置总文件；
获取自身节点的节点标识信息；
从节点差异增量配置总文件中获取与节点标识信息匹配的差异增量配置文件。
在一些实施例中，从节点差异增量配置总文件中获取与节点标识信息匹配的差异增量配置文件具体为：
判断节点差异增量配置总文件中是否存在与节点标识信息匹配的差异增量配置文件；
若节点差异增量配置总文件中不存在与节点标识信息匹配的差异增量配置文件，则直接根据待配置业务模块对应的默认配置文件配置待配置业务模块；
若节点差异增量配置总文件中存在与节点标识信息匹配的差异增量配置文件，则从节点差异增量配置总文件中获取与节点标识信息匹配的差异增量配置文件。
在一些实施例中，将差异增量配置文件中与默认配置文件的差异内容，添加至默认配置文件具体为：
从差异增量配置文件中确定一个待核对的配置块；
判断待核对的配置块是否存在于默认配置文件；
若待核对的配置块不存在于默认配置文件，则将待核对的配置块添加至默认配置文件；
若待核对的配置块存在于默认配置文件，则将待核对的配置块中与默认配置文件的差异内容，添加至默认配置文件；
判断差异增量配置文件中的所有配置块是否均已核对；
若差异增量配置文件中的所有配置块至少有一个未核对，则执行从差异增量配置文件中确定一个待核对的配置块的步骤。
在一些实施例中，将待核对的配置块中与默认配置文件的差异内容，添加至默认配置文件具体为：
从待核对的配置块中确定一个待核对的差异增量配置项；
判断待核对的差异增量配置项是否存在于默认配置文件；
若待核对的差异增量配置项不存在于所述默认配置文件，则将待核对的差异增量配置项添加至默认配置文件；
若待核对的差异增量配置项存在于所述默认配置文件，则将待核对的差异增量配置项更新至默认配置文件；
判断待核对的配置块中的所有差异增量配置项是否均已核对；
若待核对的配置块中的所有差异增量配置项至少有一个未核对，则执行从待核对的配置块中确定一个待核对的差异增量配置项的步骤。
在一些实施例中，根据增加差异内容后的默认配置文件配置待配置业务模块之后，该节点配置方法还包括：
每隔预设周期，执行从K8s中获取预存的，与自身节点以及待配置业务模块对应的差异增量配置文件的步骤。
在一些实施例中，根据增加差异内容后的默认配置文件配置待配置业务模块之后，该节点配置方法还包括：
响应于接收到的配置指令，提取配置指令中的差异增量配置项；
确定出提取的差异增量配置项对应的业务模块；
将提取的差异增量配置项更新至其对应的业务模块中。
在一些实施例中，从K8s中获取预存的与待配置业务模块对应的节点差异增量配置总文件具体为：
从K8s的Config Map资源中，获取预存的与待配置业务模块对应的节点差异增量配置总文件。
在一些实施例中，差异增量配置项包括CPU超分比、内存超分比以及占用线程数。
在一些实施例中，差异增量配置文件包括增量配置文件配置字段；
其中，增量配置文件配置字段包括用于说明文件类型的配置文件类型字段、用于说明差异增量配置文件在节点中归属位置的位置字段以及用于容纳差异增量配置项的配置块字段。
在一些实施例中，差异增量配置文件还包括预留信息字段，以便从预留信息字段中获取预留信息或将预留信息填入预留信息字段。
在一些实施例中，从K8s中获取预存的与待配置业务模块对应的节点差异增量配置总文件具体为：
判断K8s中是否存在与待配置业务模块对应的节点差异增量配置总文件；
若K8s中不存在与待配置业务模块对应的节点差异增量配置总文件，则进行告警；
若K8s中存在与待配置业务模块对应的节点差异增量配置总文件，则从K8s中获取预存的与待配置业务模块对应的节点差异增量配置总文件。
在一些实施例中，获取自身节点的节点标识信息具体为：
判断是否能够获取到自身节点的节点标识信息；
若能够获取到自身节点的节点标识信息，则执行从节点差异增量配置总文件中获取与节点标识信息匹配的差异增量配置文件的步骤；
若不能够获取到自身节点的节点标识信息，则控制提示器提示节点标识信息获取异常。
在一些实施例中，根据增加差异内容后的默认配置文件配置待配置业务模块之后，该节点配置方法还包括：
判断自身下属的所有业务模块是否均配置完毕；
在自身下属的所有业务模块中的至少一个未配置完毕的情况下，则执行确定自身下属的待配置业务模块的步骤；
在自身下属的所有业务模块均配置完毕的情况下，则控制提示器提示业务模块配置完毕。
在一些实施例中，根据增加差异内容后的默认配置文件配置待配置业务模块之后，该节点配置方法还包括：
获取自身节点当前的故障设备；
判断故障设备是否属于预设的与差异增量配置文件相关的设备；
若故障设备属于预设的与差异增量配置文件相关的设备，则控制提示器提示需重新配置。
在一些实施例中，判断故障设备是否属于预设的与差异增量配置文件相关的设备之后，该节点配置方法还包括：
若故障设备属于预设的与差异增量配置文件相关的设备，则获取自身下属的各个业务模块原始的默认配置文件；
根据默认配置文件配置对应的各个业务模块。
为解决上述技术问题，本申请还提供了一种节点配置装置，包括：
确定模块，用于确定自身下属的待配置业务模块；
第一获取模块，用于从K8s中获取预存的，与自身节点以及待配置业务模块对应的差异增量配置文件；
第二获取模块，用于获取预存的与待配置业务模块对应的默认配置文件；
合并模块，用于将差异增量配置文件中与默认配置文件的差异内容，添加至默认配置文件；
执行模块，用于根据增加差异内容后的默认配置文件配置待配置业务模块。
为解决上述技术问题，本申请还提供了一种节点配置设备，包括：
存储器，用于存储计算机程序；
处理器，用于执行计算机程序时实现如上节点配置方法的步骤。
为解决上述技术问题，本申请还提供了一种服务器，包括服务器本体以及与服务器本体连接的如上的节点配置设备。
为解决上述技术问题，本申请还提供了一种非易失性可读存储介质，非易失性可读存储介质上存储有计算机程序，计算机程序被处理器执行时实现如上节点配置方法的步骤。
本申请提供了一种节点配置方法，考虑到对于位于不同节点的同一业务模块来说，所在节点的差异也会导致该业务模块需要的配置文件的不同，本申请对于待配置业务模块，可以从K8s中获取预存的与自身节点以及待配置
业务模块对应的差异增量配置文件，接着可以将差异增量配置文件中与待配置业务模块对应的默认配置文件差异内容，添加至默认配置文件，从而得到该节点下的待配置业务模块所需的配置文件，以便完成对于该业务模块的配置，不但高效的实现了业务模块的配置，而且可以针对所在节点的特点进行不同的配置，在这种情况下便可以在云计算平台中部署差异化的节点，提升了云计算平台架构的灵活性。
本申请还提供了一种节点配置装置、设备、非易失性可读存储介质及服务器，具有如上节点配置方法相同的有益效果。
为了更清楚地说明本申请实施例中的技术方案，下面将对现有技术和实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本申请提供的一种节点配置方法的流程示意图；
图2为本申请提供的一种节点配置装置的结构示意图；
图3为本申请提供的一种节点配置设备的结构示意图。
本申请的核心是提供一种节点配置方法，不但高效的实现了业务模块的配置，而且可以针对所在节点的特点进行不同的配置，在这种情况下便可以在云计算平台中部署差异化的节点，提升了云计算平台架构的灵活性；本申请的另一核心是提供一种节点配置装置、设备、非易失性可读存储介质及服务器，不但高效的实现了业务模块的配置，而且可以针对所在节点的特点进行不同的配置，在这种情况下便可以在云计算平台中部署差异化的节点，提升了云计算平台架构的灵活性。
为使本申请实施例的目的、技术方案和优点更加清楚，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获
得的所有其他实施例，都属于本申请保护的范围。
请参考图1，图1为本申请提供的一种节点配置方法的流程示意图，该节点配置方法包括：
S101：确定自身下属的待配置业务模块；
具体的，考虑到如上背景技术中的技术问题，又结合考虑到对于位于不同节点的同一业务模块来说，所在节点的差异也会导致该业务模块需要的配置文件的不同，例如对于业务模块A来说，节点A以及节点B内均具有该业务模块A，同时节点A以及节点B存在结构以及性能上的明显差异，例如节点A具有4个CPU，而节点B存在8个CPU，在这种情况下，节点A中的业务模块A以及节点B中的业务模块A需要的配置内容也存在差别，因此需要实现对于业务模块A不同的配置，而本申请欲通过云计算平台中的节点对自身下属的业务模块进行配置，因此可以首先确定自身下属的待配置业务模块，以便后续步骤对待配置业务模块进行配置。
其中，本申请实施例可以应用于云计算平台的单个节点中，而单个节点中所包含的需要进行配置的业务模块的数量也可以有多个，本申请实施例在此不做限定。
具体的，本申请实施例中的节点所在的云计算平台可以为多种类型，例如可以为OpenStack云计算平台等，本申请实施例在此不做限定。
其中，OpenStack是一种开源的云计算管理平台，其主要目的是通过虚拟化技术隐藏底层物理硬件的细节，为用户提供计算、存储和网络等层面的资源隔离及资源使用限制，使得在用户层面上来看仿佛是独占一台机器一样。目前在全球范围内有大量的开发者参与其中，为OpenStack的快速发展提供了强有力的保障。OpenStask经过多年的发展，其技术已日趋成熟和稳定，在提供高可用的同时，也具有灵活的可扩展性，因此，OpenStack在各行各业得到了广泛的应用。将OpenStack云计算平台部署在Kubernetes上已成为一种趋势，以提高OpenStack云计算平台的部署灵活性、可扩展性、故障自我恢复等能力。
S102：从K8s中获取预存的，与自身节点以及待配置业务模块对应的差异增量配置文件；
具体的，为了便于各节点对差异增量配置文件的获取，本申请实施例中可以在K8s平台中预存与各个节点以及各个待配置业务模块对应的差异增量配置文件，而后各节点便可以统一从K8s平台中获取，提高了数据获取效率。
其中，差异增量配置文件可以作为后续步骤的数据基础。
具体的，考虑到对于位于不同节点的同一业务模块来说，所在节点的差异也会导致该业务模块需要的配置文件的不同，因此本申请实施例中的差异增量配置文件除了与待配置业务模块对应外，还需要与节点相对应，这在差异增量配置文件的生成阶段便可以实现，可以根据节点特征以及业务模块的特征设计对应的差异增量配置文件，从而实现对位于不同节点的同一业务模块，根据其所在节点的差异设计不同的差异增量配置文件，以便后续通过其实现对于业务模块差异化的配置。
S103：获取预存的与待配置业务模块对应的默认配置文件；
具体的，考虑到对于业务模块来说，所在节点的差异带来的配置项的差异内容只占一小部分，在这种情况下为了减轻工作人员设计差异增量配置文件的工作量，本申请实施例可以获取预存的与待配置业务模块对应的默认配置文件，以便作为后续步骤的数据基础，至此可以看出，差异增量配置文件实际上可以是在默认配置文件所包含的各个配置项的基础上，规定了一小部分“由于业务模块所在节点的特征的不同”而导致需要特殊设置的配置项。
其中，默认配置文件的预存位置可以自由设置，例如可以预存于各节点内部等，本申请实施例在此不做限定。
S104：将差异增量配置文件中与默认配置文件的差异内容，添加至默认配置文件；
具体的，由于差异增量配置文件规定了一些特殊设置的配置项，而这些特殊的配置项很可能在默认配置文件中是不存在或者不同的，因此为了将该差异增量配置文件中的各配置项内容应用到业务模块中，本申请实施例中可以将差异增量配置文件中与默认配置文件的差异内容，添加至默认配置文件，以便得到增加了差异内容的默认配置文件，并将其作为后续步骤的数据基础。
S105：根据增加差异内容后的默认配置文件配置待配置业务模块。
其中，在得到增加了差异内容的默认配置文件后，便可以根据当前的默认配置文件对待配置业务模块进行配置，配置后的业务模块在运行时也符合所在节点的相关要求，也即使得各业务模块能够顺利高效运行。
具体的，由于本申请实施例中的差异增量配置文件可以针对各节点进行设计，也即对于同一业务模块在不同节点中的场景分别设计对应的差异化的配置文件，因此在这种情况下各节点的结构以及配置也可以进行灵活设计，提升了云计算平台搭建时的灵活性，提升了用户体验。
本申请提供了一种节点配置方法，考虑到对于位于不同节点的同一业务模块来说，所在节点的差异也会导致该业务模块需要的配置文件的不同，本申请对于待配置业务模块，可以从K8s中获取预存的与自身节点以及待配置业务模块对应的差异增量配置文件，接着可以将差异增量配置文件中与待配置业务模块对应的默认配置文件差异内容，添加至默认配置文件，从而得到该节点下的待配置业务模块所需的配置文件，以便完成对于该业务模块的配置，不但高效的实现了业务模块的配置，而且可以针对所在节点的特点进行不同的配置，在这种情况下便可以在云计算平台中部署差异化的节点，提升了云计算平台架构的灵活性。
在上述实施例的基础上：
在一些实施例中，从K8s中获取预存的，与自身节点以及待配置业务模块对应的差异增量配置文件具体为：
从K8s中获取预存的与待配置业务模块对应的节点差异增量配置总文件；
获取自身节点的节点标识信息；
从节点差异增量配置总文件中获取与节点标识信息匹配的差异增量配置文件。
具体的，考虑到节点数量较多，若设计多份与各个节点一一对应的差异增量配置文件，不但增加了空间占用，而且节点在查找自身对应的差异增量配置文件时也比较繁琐，因此为了缩减空间占用以及查找效率，本申请实施例中为每个业务模块设计了一个节点差值增量配置总文件(简称总文件)，在该总文件中便可以容纳特定的一个业务模块在云计算平台的不同节点中的差异增量配置文件，不但减小了空间占用，而且在查找时也能快速查找到与待配置业务模块对应的唯一的总文件，提升了配置效率。
其中，为了查找自身节点对应的总文件，可以通过自身的节点标识信息进行匹配，通过简单的查找方式可以进一步提升查找效率。
其中，总文件可以使用yml格式进行组织，本申请实施例在此不做限定。
当然，除了该种查找方式外，还可以通过其他方式从节点差异增量配置总文件中获取与自身节点对应的差异增量配置文件，本申请实施例在此不做限定。
在一些实施例中，从节点差异增量配置总文件中获取与节点标识信息匹配的差异增量配置文件具体为：
判断节点差异增量配置总文件中是否存在与节点标识信息匹配的差异增量配置文件；
若节点差异增量配置总文件中不存在与节点标识信息匹配的差异增量配置文件，则直接根据待配置业务模块对应的默认配置文件配置待配置业务模块；
若节点差异增量配置总文件中存在与节点标识信息匹配的差异增量配置文件，则从节点差异增量配置总文件中获取与节点标识信息匹配的差异增量配置文件。
具体的，考虑到由于所在节点特征的特点，可能该节点中的待配置业务模块本身就不需要进行差异配置，因此在这种情况下可以不设计该节点对应的差异增量配置文件，因此本申请实施例中可以判断节点差异增量配置总文件中是否存在与节点标识信息匹配的差异增量配置文件，如果不存在，则可以直接根据待配置业务模块对应的默认配置文件配置待配置业务模块，而在存在的时候则可以从节点差异增量配置总文件中获取与节点标识信息匹配的差异增量配置文件。
在一些实施例中，将差异增量配置文件中与默认配置文件的差异内容，添加至默认配置文件具体为：
从差异增量配置文件中确定一个待核对的配置块；
判断待核对的配置块是否存在于默认配置文件；
若待核对的配置块不存在于所述默认配置文件，则将待核对的配置块添加至默认配置文件；
若待核对的配置块存在于所述默认配置文件，则将待核对的配置块中与默认配置文件的差异内容，添加至默认配置文件；
判断差异增量配置文件中的所有配置块是否均已核对；
若差异增量配置文件中的所有配置块至少有一个未核对，则执行从差异增量配置文件中确定一个待核对的配置块的步骤。
具体的，考虑到差异增量配置项的内容可能较多，而众多的差异增量配置项具有明显的类别特征，因此可以将不同类别的差异增量配置项在差异增量配置文件中放在不同的配置块中，便于管理与查找，那么在将差异增量配置文件中与默认配置文件的差异内容，添加至默认配置文件时，便可以采用遍历的方式依次遍历各个配置块，将不存在于默认配置文件中的配置块可以直接添加至默认配置文件，而对于存在于默认配置文件中的配置块，考虑到其中的某些差异增量配置项可能与默认配置文件存在差别，因此可以将待核对的配置块中与默认配置文件的差异内容，添加至默认配置文件，直至遍历核对完差异增量配置文件中所有的配置块，可以避免遗漏，保证配置工作的可靠进行。
在一些实施例中，将待核对的配置块中与默认配置文件的差异内容，添加至默认配置文件具体为：
从待核对的配置块中确定一个待核对的差异增量配置项；
判断待核对的差异增量配置项是否存在于默认配置文件；
若待核对的差异增量配置项不存在于默认配置文件，则将待核对的差异增量配置项添加至默认配置文件；
若待核对的差异增量配置项存在于默认配置文件，则将待核对的差异增量配置项更新至默认配置文件；
判断待核对的配置块中的所有差异增量配置项是否均已核对；
若待核对的配置块中的所有差异增量配置项至少有一个未核对，则执行从待核对的配置块中确定一个待核对的差异增量配置项的步骤。
具体的，单个配置块中可能也具有多个差异增量配置项，而为了查找到其中与默认配置文件中差异的配置项内容，本申请实施例中同样可以采用遍历的方式进行逐一核对，如果存在于默认配置文件，可能也存在数值上的不同，由于差异增量配置项的优先级较高，因此可以将待核对的差异增量配置项更新(覆盖或替换)至默认配置文件，如果不存在与默认配置文件，那么便可以将待核对的差异增量配置项添加至默认配置文件，进一步避免了遗漏，保证配置工作的可靠进行。
在一些实施例中，根据增加差异内容后的默认配置文件配置待配置业务模块之后，该节点配置方法还包括：
每隔预设周期，执行从K8s中获取预存的，与自身节点以及待配置业务模块对应的差异增量配置文件的步骤。
具体的，考虑到在后续过程中工作人员可能还存在对于业务模块进行配置文件的需求，因此本申请实施例中可以每隔预设周期，执行从K8s中获取预存的，与自身节点以及待配置业务模块对应的差异增量配置文件的步骤，以便及时发现更新的差异增量配置文件并及时对设计到的业务模块进行更新配置，自动化程度较高。
其中，预设周期可以进行自主设定，本申请实施例在此不做限定。
在一些实施例中，根据增加差异内容后的默认配置文件配置待配置业务模块之后，该节点配置方法还包括：
响应于接收到的配置指令，提取配置指令中的差异增量配置项；
确定出提取的差异增量配置项对应的业务模块；
将提取的差异增量配置项更新至其对应的业务模块中。
具体的，考虑到为了及时的进行对业务模块的更新配置，工作人员可能直接通过配置指令的形式告知节点，因此本申请实施例中可以响应于接收到的配置指令，提取配置指令中的差异增量配置项，并确定出提取的差异增量配置项对应的业务模块，然后将提取的差异增量配置项更新至其对应的业务模块中即可，提供了一种及时更新业务模块配置的途径，提高了工作效率以及用户体验。
在一些实施例中，从K8s中获取预存的与待配置业务模块对应的节点差异增量配置总文件具体为：
从K8s的Config Map资源中，获取预存的与待配置业务模块对应的节点差异增量配置总文件。
具体的，业务模块部署前，可以使用总文件创建一个kubernetes的configmap资源；业务模块部署时将该configmap中的高优先级节点差异增量配置文件挂载到业务模块pod内的相关目录下，以便执行上述方法，从K8s的Config Map资源中进行获取，具有读取速率快以及可靠性强等优点。
当然，除了该具体方式外，还可以从其他位置获取预存的与待配置业务模块对应的节点差异增量配置总文件，本申请实施例在此不做限定。
在一些实施例中，差异增量配置项包括CPU超分比、内存超分比以及占用线程数。
具体的，CPU超分比与节点CPU核数以及CPU频率相关，内存超分比则与内存容量相关联，占用线程数则与节点CPU的核数、CPU频率以及内存容量相关联，属于比较重要的差异增量配置项。
当然，除了该具体实例外，差异增量配置项还可以为其他具体内容，本申请实施例在此不做限定。
在一些实施例中，差异增量配置文件包括增量配置文件配置字段；
其中，增量配置文件配置字段包括用于说明文件类型的配置文件类型字段、用于说明差异增量配置文件在节点中归属位置的位置字段以及用于容纳差异增量配置项的配置块字段。
具体的，在增量配置文件配置字段可以规定丰富的差异增量配置文件的一些参数，除了用于容纳差异增量配置项的配置块字段外，还可以包括用于说明文件类型的配置文件类型字段以及用于说明差异增量配置文件在节点中归属位置的位置字段，通过文件类型可以找到与之匹配的解析方法，而通过归属位置则可以找到差异增量配置文件在节点中归属位置，提升了配置工作的可靠性。
当然，除了上述字段内容外，差异增量配置文件还可以包括其他内容，本申请实施例在此不做限定。
在一些实施例中，差异增量配置文件还包括预留信息字段，以便从预留信息字段中获取预留信息或将预留信息填入预留信息字段。
具体的，考虑到工作人员存在通过差异增量配置文件与节点/业务模块进行信息交互的需求，因此本申请实施例中的差异增量配置文件中还可以包括预留信息字段，以便从预留信息字段中获取预留信息或将预留信息填入预留信息字段。
在一些实施例中，从K8s中获取预存的与待配置业务模块对应的节点差异增量配置总文件具体为：
判断K8s中是否存在与待配置业务模块对应的节点差异增量配置总文件；
若K8s中不存在与待配置业务模块对应的节点差异增量配置总文件，则进行告警；
若K8s中存在与待配置业务模块对应的节点差异增量配置总文件，则从K8s中获取预存的与待配置业务模块对应的节点差异增量配置总文件。
具体的，由于总文件中包含了多个节点的差异增量配置文件，因此一般情况下总文件是存在的，然而在某些情况下由于存在路径错误等原因，节点可能无法获取到总文件，在这种情况下就无法开展业务模块的配置工作，因此在这种情况下可以进行告警，以便工作人员及时获知并进行检修，进一步提升了配置工作的可靠性。
在一些实施例中，获取自身节点的节点标识信息具体为：
判断是否能够获取到自身节点的节点标识信息；
若能够获取到所述自身节点的节点标识信息，则执行从节点差异增量配置总文件中获取与节点标识信息匹配的差异增量配置文件的步骤；
若不能够获取到所述自身节点的节点标识信息，则控制提示器提示节点标识信息获取异常。
具体的，考虑到节点标识信息也是从总文件中获取差异增量配置文件的关键信息，且节点标识信息在某些异常情况下也可能无法正常获取，因此本申请实施例中可以在不能获取到自身节点的节点标识信息时，控制提示器提示节点标识信息获取异常，以便工作人员及时获知并进行检修，进一步提升了配置工作的可靠性。
其中，提示器可以为多种类型，例如显示器等，本申请实施例在此不做限定。
在一些实施例中，根据增加差异内容后的默认配置文件配置待配置业务模块之后，该节点配置方法还包括：
判断自身下属的所有业务模块是否均配置完毕；
在自身下属的所有业务模块中的至少一个未配置完毕的情况下，则执行确定自身下属的待配置业务模块的步骤；
在自身下属的所有业务模块均配置完毕的情况下，则控制提示器提示业务模块配置完毕。
具体的，为了自动化的执行对于节点中存在的多个业务模块的配置工作，本申请实施例中可以在配置完一个待配置业务模块之后，判断自身下属的所有业务模块是否均配置完毕，在自身下属的所有业务模块未全部配置时，便可以执行定自身下属的待配置业务模块的步骤，提升了自动化程度，且在执行完毕时可以控制提示器提示业务模块配置完毕，以便工作人员了解到业务模块配置工作的进度。
在一些实施例中，根据增加差异内容后的默认配置文件配置待配置业务模块之后，该节点配置方法还包括：
获取自身节点当前的故障设备；
判断故障设备是否属于预设的与差异增量配置文件相关的设备；
若故障设备属于预设的与差异增量配置文件相关的设备，则控制提示器提示需重新配置。
具体的，考虑到自身节点中的设备故障可能影响到业务模块的配置需求发生变化，因此本申请实施例提出了监测机制，可以判断自身节点当前的故障设备是否属于预设的与差异增量配置文件相关的设备，如果属于，则可以控制提示器提示需重新配置，以便工作人员及时发现该情况并控制节点对故障设备进行检修或者对业务模块进行重新配置等，提升了云计算平台的工作稳定性。
在一些实施例中，判断故障设备是否属于预设的与差异增量配置文件相关的设备之后，该节点配置方法还包括：
若故障设备属于预设的与差异增量配置文件相关的设备，则获取自身下属的各个业务模块原始的默认配置文件；
根据默认配置文件配置对应的各个业务模块。
具体的，考虑到工作人员可能无法及时获知“需重新配置”的提示内容，在这种情况下为了使得相关业务模块进行正常工作，本申请实施例中可以获取自身下属的各个业务模块原始的默认配置文件，然后根据默认配置文件配置对应的各个业务模块，也即满足业务模块基本的工作，保证业务模块持续工作。
请参考图2，图2为本申请提供的一种节点配置装置的结构示意图，该节点配置装置包括：
确定模块21，用于确定自身下属的待配置业务模块；
第一获取模块22，用于从K8s中获取预存的，与自身节点以及待配置业务模块对应的差异增量配置文件；
第二获取模块23，用于获取预存的与待配置业务模块对应的默认配置文件；
合并模块24，用于将差异增量配置文件中与默认配置文件的差异内容，添加至默认配置文件；
执行模块25，用于根据增加差异内容后的默认配置文件配置待配置业务模块。
本申请提供了一种节点配置装置，考虑到对于位于不同节点的同一业务模块来说，所在节点的差异也会导致该业务模块需要的配置文件的不同，本申请对于待配置业务模块，可以从K8s中获取预存的与自身节点以及待配置业务模块对应的差异增量配置文件，接着可以将差异增量配置文件中与待配置业务模块对应的默认配置文件差异内容，添加至默认配置文件，从而得到该节点下的待配置业务模块所需的配置文件，以便完成对于该业务模块的配置，不但高效的实现了业务模块的配置，而且可以针对所在节点的特点进行不同的配置，在这种情况下便可以在云计算平台中部署差异化的节点，提升了云计算平台架构的灵活性。
对于本申请实施例提供的节点配置装置的介绍请参照前述的节点配置方法的实施例，本申请实施例在此不再赘述。
请参考图3，图3为本申请提供的一种节点配置设备的结构示意图，该节点配置设备包括：
存储器31，用于存储计算机程序；
处理器32，用于执行计算机程序时实现如前述实施例中节点配置方法的步骤。
具体的，存储器包括非易失性存储介质、内存储器。该非易失性存储介质存储有操作系统和计算机可读指令，该内存储器为非易失性存储介质中的操作系统和计算机可读指令的运行提供环境。处理器执行存储器中保存的计算机程序时，可以实现以下步骤：确定自身下属的待配置业务模块；从K8s中获取预存的，与自身节点以及待配置业务模块对应的差异增量配置文件；获取预存的与待配置业务模块对应的默认配置文件；将差异增量配置文件中与默认配置文件的差异内容，添加至默认配置文件；根据增加差异内容后的默认配置文件配置待配置业务模块。
本申请提供了一种节点配置设备，考虑到对于位于不同节点的同一业务模块来说，所在节点的差异也会导致该业务模块需要的配置文件的不同，本申请对于待配置业务模块，可以从K8s中获取预存的与自身节点以及待配置业务模块对应的差异增量配置文件，接着可以将差异增量配置文件中与待配
置业务模块对应的默认配置文件差异内容，添加至默认配置文件，从而得到该节点下的待配置业务模块所需的配置文件，以便完成对于该业务模块的配置，不但高效的实现了业务模块的配置，而且可以针对所在节点的特点进行不同的配置，在这种情况下便可以在云计算平台中部署差异化的节点，提升了云计算平台架构的灵活性。
对于本申请实施例提供的节点配置设备的介绍请参照前述的节点配置方法的实施例，本申请实施例在此不再赘述。
本申请还提供了一种服务器，包括服务器本体以及与服务器本体连接的如前述实施例中的节点配置设备。
本申请提供了一种服务器，考虑到对于位于不同节点的同一业务模块来说，所在节点的差异也会导致该业务模块需要的配置文件的不同，本申请对于待配置业务模块，可以从K8s中获取预存的与自身节点以及待配置业务模块对应的差异增量配置文件，接着可以将差异增量配置文件中与待配置业务模块对应的默认配置文件差异内容，添加至默认配置文件，从而得到该节点下的待配置业务模块所需的配置文件，以便完成对于该业务模块的配置，不但高效的实现了业务模块的配置，而且可以针对所在节点的特点进行不同的配置，在这种情况下便可以在云计算平台中部署差异化的节点，提升了云计算平台架构的灵活性。
对于本申请实施例提供的服务器的介绍请参照前述的节点配置方法的实施例，本申请实施例在此不再赘述。
本申请还提供了一种非易失性可读存储介质，非易失性可读存储介质上存储有计算机程序，计算机程序被处理器执行时实现如前述实施例中节点配置方法的步骤。
具体的，该非易失性可读存储介质可以包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。该存储介质上存储有计算机程序，计算机程序被处理器执行时实现以下步骤：确定自身下属的待配置业务模块；从K8s中获取预存的，与自身节点以及待配置业务模块对应的差异增量配置文件；获取预存的与待配置业务模块对应的默认配置文件；
将差异增量配置文件中与默认配置文件的差异内容，添加至默认配置文件；根据增加差异内容后的默认配置文件配置待配置业务模块。
本申请提供了一种非易失性可读存储介质，考虑到对于位于不同节点的同一业务模块来说，所在节点的差异也会导致该业务模块需要的配置文件的不同，本申请对于待配置业务模块，可以从K8s中获取预存的与自身节点以及待配置业务模块对应的差异增量配置文件，接着可以将差异增量配置文件中与待配置业务模块对应的默认配置文件差异内容，添加至默认配置文件，从而得到该节点下的待配置业务模块所需的配置文件，以便完成对于该业务模块的配置，不但高效的实现了业务模块的配置，而且可以针对所在节点的特点进行不同的配置，在这种情况下便可以在云计算平台中部署差异化的节点，提升了云计算平台架构的灵活性。
对于本申请实施例提供的非易失性可读存储介质的介绍请参照前述的节点配置方法的实施例，本申请实施例在此不再赘述。
本说明书中各个实施例采用递进的方式描述，每个实施例重点说明的都是与其他实施例的不同之处，各个实施例之间相同相似部分互相参见即可。对于实施例公开的装置而言，由于其与实施例公开的方法相对应，所以描述的比较简单，相关之处参见方法部分说明即可。还需要说明的是，在本说明书中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个......”限定的要素，并不排除在包括该要素的过程、方法、物品或者设备中还存在另外的相同要素。
对所公开的实施例的上述说明，使本领域专业技术人员能够实现或使用本申请。对这些实施例的多种修改对本领域的专业技术人员来说将是显而易见的，本文中所定义的一般原理可以在不脱离本申请的精神或范围的情况下，在其他实施例中实现。因此，本申请将不会被限制于本文所示的这些实施例，而是要符合与本文所公开的原理和新颖特点相一致的最宽的范围。
Claims (20)
- 一种节点配置方法，其特征在于，包括：确定自身下属的待配置业务模块；从K8s中获取预存的，与自身节点以及所述待配置业务模块对应的差异增量配置文件；获取预存的与所述待配置业务模块对应的默认配置文件；将所述差异增量配置文件中与所述默认配置文件的差异内容，添加至所述默认配置文件；根据增加所述差异内容后的所述默认配置文件配置所述待配置业务模块。
- 根据权利要求1所述的节点配置方法，其特征在于，所述从K8s中获取预存的，与自身节点以及所述待配置业务模块对应的差异增量配置文件具体为：从K8s中获取预存的与所述待配置业务模块对应的节点差异增量配置总文件；获取自身节点的节点标识信息；从所述节点差异增量配置总文件中获取与所述节点标识信息匹配的差异增量配置文件。
- 根据权利要求2所述的节点配置方法，其特征在于，所述从所述节点差异增量配置总文件中获取与所述节点标识信息匹配的差异增量配置文件具体为：判断所述节点差异增量配置总文件中是否存在与所述节点标识信息匹配的差异增量配置文件；若所述节点差异增量配置总文件中不存在与所述节点标识信息匹配的差异增量配置文件，则直接根据所述待配置业务模块对应的默认配置文件配置所述待配置业务模块；若所述节点差异增量配置总文件中存在与所述节点标识信息匹配的差异增量配置文件，则从所述节点差异增量配置总文件中获取与所述节点标识信息匹配的差异增量配置文件。
- 根据权利要求1所述的节点配置方法，其特征在于，所述将所述差异增量配置文件中与所述默认配置文件的差异内容，添加至所述默认配置文件具体为：从所述差异增量配置文件中确定一个待核对的配置块；判断所述待核对的配置块是否存在于所述默认配置文件；若所述待核对的配置块不存在于所述默认配置文件，则将所述待核对的配置块添加至所述默认配置文件；若所述待核对的配置块存在于所述默认配置文件，则将所述待核对的配置块中与所述默认配置文件的差异内容，添加至所述默认配置文件；判断所述差异增量配置文件中的所有配置块是否均已核对；若所述差异增量配置文件中的所有配置块至少有一个未核对，则执行所述从所述差异增量配置文件中确定一个待核对的配置块的步骤。
- 根据权利要求4所述的节点配置方法，其特征在于，所述将所述待核对的配置块中与所述默认配置文件的差异内容，添加至所述默认配置文件具体为：从所述待核对的配置块中确定一个待核对的差异增量配置项；判断所述待核对的差异增量配置项是否存在于所述默认配置文件；若所述待核对的差异增量配置项不存在于所述默认配置文件，则将所述待核对的差异增量配置项添加至所述默认配置文件；若所述待核对的差异增量配置项存在于所述默认配置文件，则将所述待核对的差异增量配置项更新至所述默认配置文件；判断所述待核对的配置块中的所有差异增量配置项是否均已核对；若所述待核对的配置块中的所有差异增量配置项至少有一个未核对，则执行所述从所述待核对的配置块中确定一个待核对的差异增量配置项的步骤。
- 根据权利要求5所述的节点配置方法，其特征在于，所述根据增加所述差异内容后的所述默认配置文件配置所述待配置业务模块之后，该节点配置方法还包括：每隔预设周期，执行所述从K8s中获取预存的，与自身节点以及所述待配置业务模块对应的差异增量配置文件的步骤。
- 根据权利要求6所述的节点配置方法，其特征在于，所述根据增加所述差异内容后的所述默认配置文件配置所述待配置业务模块之后，该节点配置方法还包括：响应于接收到的配置指令，提取所述配置指令中的差异增量配置项；确定出提取的所述差异增量配置项对应的业务模块；将提取的所述差异增量配置项更新至其对应的所述业务模块中。
- 根据权利要求2所述的节点配置方法，其特征在于，所述从K8s中获取预存的与所述待配置业务模块对应的节点差异增量配置总文件具体为：从K8s的Config Map资源中，获取预存的与所述待配置业务模块对应的节点差异增量配置总文件。
- 根据权利要求5所述的节点配置方法，其特征在于，所述差异增量配置项包括CPU超分比、内存超分比以及占用线程数。
- 根据权利要求9所述的节点配置方法，其特征在于，所述差异增量配置文件包括增量配置文件配置字段；其中，所述增量配置文件配置字段包括用于说明文件类型的配置文件类型字段、用于说明所述差异增量配置文件在节点中归属位置的位置字段以及用于容纳所述差异增量配置项的配置块字段。
- 根据权利要求10所述的节点配置方法，其特征在于，所述差异增量配置文件还包括预留信息字段，以便从所述预留信息字段中获取预留信息或将预留信息填入所述预留信息字段。
- 根据权利要求2所述的节点配置方法，其特征在于，所述从K8s中获取预存的与所述待配置业务模块对应的节点差异增量配置总文件具体为：判断K8s中是否存在与所述待配置业务模块对应的节点差异增量配置总文件；若K8s中不存在与所述待配置业务模块对应的所述节点差异增量配置总文件，则进行告警；若K8s中存在与所述待配置业务模块对应的所述节点差异增量配置总文件，则从K8s中获取预存的与所述待配置业务模块对应的节点差异增量配置总文件。
- 根据权利要求12所述的节点配置方法，其特征在于，所述获取自身节点的节点标识信息具体为：判断是否能够获取到自身节点的节点标识信息；若能够获取到所述自身节点的节点标识信息，则执行所述从所述节点差异增量配置总文件中获取与所述节点标识信息匹配的差异增量配置文件的步骤；若不能够获取到所述自身节点的节点标识信息，则控制提示器提示节点标识信息获取异常。
- 根据权利要求1所述的节点配置方法，其特征在于，所述根据增加所述差异内容后的所述默认配置文件配置所述待配置业务模块之后，该节点配置方法还包括：判断自身下属的所有业务模块是否均配置完毕；在自身下属的所有所述业务模块中的至少一个未配置完毕的情况下，则执行所述确定自身下属的待配置业务模块的步骤；在自身下属的所有所述业务模块均配置完毕的情况下，则控制提示器提示业务模块配置完毕。
- 根据权利要求1至14任一项所述的节点配置方法，其特征在于，所述根据增加所述差异内容后的所述默认配置文件配置所述待配置业务模块之后，该节点配置方法还包括：获取自身节点当前的故障设备；判断所述故障设备是否属于预设的与所述差异增量配置文件相关的设备；若所述故障设备属于预设的与所述差异增量配置文件相关的设备，则控制提示器提示需重新配置。
- 根据权利要求15所述的节点配置方法，其特征在于，所述判断所述故障设备是否属于预设的与所述差异增量配置文件相关的设备之后，该节点配置方法还包括：若所述故障设备属于预设的与所述差异增量配置文件相关的设备，则获取自身下属的各个业务模块原始的所述默认配置文件；根据所述默认配置文件配置对应的各个所述业务模块。
- 一种节点配置装置，其特征在于，包括：确定模块，用于确定自身下属的待配置业务模块；第一获取模块，用于从K8s中获取预存的，与自身节点以及所述待配置业务模块对应的差异增量配置文件；第二获取模块，用于获取预存的与所述待配置业务模块对应的默认配置文件；合并模块，用于将所述差异增量配置文件中与所述默认配置文件的差异内容，添加至所述默认配置文件；执行模块，用于根据增加所述差异内容后的所述默认配置文件配置所述待配置业务模块。
- 一种节点配置设备，其特征在于，包括：存储器，用于存储计算机程序；处理器，用于执行所述计算机程序时实现如权利要求1至16任一项所述节点配置方法的步骤。
- 一种服务器，其特征在于，包括服务器本体以及与所述服务器本体连接的如权利要求18所述的节点配置设备。
- 一种非易失性可读存储介质，其特征在于，所述非易失性可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1至16任一项所述节点配置方法的步骤。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211645146.2 | 2022-12-21 | ||
| CN202211645146.2A CN115632944B (zh) | 2022-12-21 | 2022-12-21 | 一种节点配置方法、装置、设备、可读存储介质及服务器 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2024130997A1 true WO2024130997A1 (zh) | 2024-06-27 |
Family
ID=84909635
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2023/101927 WO2024130997A1 (zh) | 2022-12-21 | 2023-06-21 | 一种节点配置方法、装置、设备、非易失性可读存储介质及服务器 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN115632944B (zh) |
| WO (1) | WO2024130997A1 (zh) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115632944B (zh) * | 2022-12-21 | 2023-03-14 | 苏州浪潮智能科技有限公司 | 一种节点配置方法、装置、设备、可读存储介质及服务器 |
| CN116208498A (zh) * | 2023-05-04 | 2023-06-02 | 苏州浪潮智能科技有限公司 | 一种OpenStack云平台节点差异化配置的方法、装置、设备及介质 |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180088926A1 (en) * | 2016-09-27 | 2018-03-29 | Ca, Inc. | Container image management using layer deltas |
| CN107896162A (zh) * | 2017-11-08 | 2018-04-10 | 平安科技（深圳）有限公司 | 监控系统的部署方法、 装置、 计算机设备及存储介质 |
| CN113535262A (zh) * | 2021-07-07 | 2021-10-22 | 曙光信息产业(北京)有限公司 | 一种代理节点的启动控制方法、装置、设备及存储介质 |
| CN115167884A (zh) * | 2022-08-03 | 2022-10-11 | 杭州新迪数字工程系统有限公司 | 一种kubernetes部署方法及系统 |
| CN115632944A (zh) * | 2022-12-21 | 2023-01-20 | 苏州浪潮智能科技有限公司 | 一种节点配置方法、装置、设备、可读存储介质及服务器 |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106412955B (zh) * | 2016-09-29 | 2019-06-11 | 宇龙计算机通信科技(深圳)有限公司 | 一种执行ims业务的方法、装置及终端 |
| CN111090446A (zh) * | 2019-12-20 | 2020-05-01 | 北京海益同展信息科技有限公司 | 一种配置文件更新方法及系统 |
| CN111580884B (zh) * | 2020-04-30 | 2024-04-19 | 北京金山云网络技术有限公司 | 配置更新方法、装置、服务器和电子设备 |
-
2022
- 2022-12-21 CN CN202211645146.2A patent/CN115632944B/zh active Active
-
2023
- 2023-06-21 WO PCT/CN2023/101927 patent/WO2024130997A1/zh unknown
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180088926A1 (en) * | 2016-09-27 | 2018-03-29 | Ca, Inc. | Container image management using layer deltas |
| CN107896162A (zh) * | 2017-11-08 | 2018-04-10 | 平安科技（深圳）有限公司 | 监控系统的部署方法、 装置、 计算机设备及存储介质 |
| CN113535262A (zh) * | 2021-07-07 | 2021-10-22 | 曙光信息产业(北京)有限公司 | 一种代理节点的启动控制方法、装置、设备及存储介质 |
| CN115167884A (zh) * | 2022-08-03 | 2022-10-11 | 杭州新迪数字工程系统有限公司 | 一种kubernetes部署方法及系统 |
| CN115632944A (zh) * | 2022-12-21 | 2023-01-20 | 苏州浪潮智能科技有限公司 | 一种节点配置方法、装置、设备、可读存储介质及服务器 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115632944A (zh) | 2023-01-20 |
| CN115632944B (zh) | 2023-03-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2024130997A1 (zh) | 一种节点配置方法、装置、设备、非易失性可读存储介质及服务器 | |
| CN110716748B (zh) | 业务处理方法、装置、计算机可读介质及电子设备 | |
| CN110543328B (zh) | 基于Ambari的跨平台组件管理方法、系统、终端及存储介质 | |
| CN107896162B (zh) | 监控系统的部署方法、装置、计算机设备及存储介质 | |
| US20050262501A1 (en) | Software distribution method and system supporting configuration management | |
| CN107566165B (zh) | 一种发现及部署电力云数据中心可用资源的方法及系统 | |
| CN112486466B (zh) | 一种基于微服务架构的快速通用基础框架实现方法 | |
| CN106293820A (zh) | 开发测试运维一体化系统、部署、全量以及增量更新方法 | |
| CN108229799B (zh) | 一种多源异构电网运行实时数据接入系统及方法 | |
| CN113204353B (zh) | 一种大数据平台组件部署方法及装置 | |
| CN111245634A (zh) | 一种虚拟化管理方法及装置 | |
| US11113186B1 (en) | Testing and publishing of resource handlers in a cloud environment | |
| CN114840223A (zh) | 资源处理方法及装置 | |
| CN113708971A (zh) | 一种Openstack云平台的部署方法及相关装置 | |
| US12217098B2 (en) | Deployment of pod cohorts | |
| US20230393876A1 (en) | Landing zones for pattern-based cloud computing | |
| WO2023061257A1 (zh) | 数据库业务处理方法和装置 | |
| CN116414647A (zh) | 换电资源数据的监控管理方法、系统、设备和介质 | |
| Akue et al. | Integrating an online configuration checker with existing management systems: Application to CIM/WBEM environments | |
| US20240419920A1 (en) | Natural language-based management of computing resources executing radio access network workloads | |
| CN115604101B (zh) | 系统管理方法及相关设备 | |
| US11954469B2 (en) | Bases for pattern-based cloud computing | |
| US12026491B2 (en) | System architecture for pattern-based software applications | |
| CN118092982B (zh) | 一种云原生应用的多集群运维方法、设备及介质 | |
| US20240338209A1 (en) | Software life-cycle component management system |
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: 23905183 Country of ref document: EP Kind code of ref document: A1 |