Private cloud profile management method and device, and storage medium

By classifying and managing private cloud configuration files, the problem that the Disconf open-source solution could not achieve deployment planning and automatic configuration generation is solved, thus realizing efficient management and automatic generation of private cloud configuration files.

CN114968293BActive Publication Date: 2026-05-19TENCENT TECHNOLOGY (SHENZHEN) CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
TENCENT TECHNOLOGY (SHENZHEN) CO LTD
Filing Date
2021-02-26
Publication Date
2026-05-19

AI Technical Summary

Technical Problem

In existing technologies, the Disconf open-source solution cannot split private cloud configuration files, which makes it impossible to implement upper-layer functions such as hosting deployment planning and automatic configuration generation.

Method used

By acquiring the configuration file package of the target private cloud, the data of each management item is screened out, and a configuration data management page is built to realize the classified management of the private cloud configuration file, including editing and updating management items such as improving basic content, service planning and attributes.

Benefits of technology

It enables the categorized management of private cloud configuration files, providing a foundation for deployment planning and automatic configuration generation, and improving the efficiency and flexibility of configuration file management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114968293B_ABST
    Figure CN114968293B_ABST
Patent Text Reader

Abstract

The application provides a management method and device of a configuration file of a private cloud and a storage medium. In the management method of the configuration file of the private cloud, after obtaining a configuration file package of a target private cloud, data belonging to each management item of a configuration data management page of the target private cloud is screened out according to the requirements of the management items, and the configuration data management page of the target private cloud is constructed by using the data of each management item. Since each management item is a management dimension of the configuration file of the target private cloud, screening out the data of each management item of the configuration data management page of the target private cloud classifies the configuration file package of the target private cloud, and the configuration file package of the target private cloud can be managed from each management dimension, thereby providing a basis for implementing upper functions such as load deployment planning and automatic configuration generation.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of cloud platform technology, and in particular to a method, apparatus, and storage medium for managing configuration files of a private cloud. Background Technology

[0002] In existing technologies, the Disconf open-source solution is typically used as a management solution for configuration files in private clouds.

[0003] However, the Disconf open-source solution is essentially a configuration file hosting platform. It can host configuration files of any type and provide web management functionality, allowing users to see which business applications are using each configuration file. However, because it doesn't split configuration files, it's impossible to implement higher-level functions such as deployment planning or automatic configuration generation. Summary of the Invention

[0004] In view of the shortcomings of the prior art, this application proposes a method, device and storage medium for managing configuration files of a private cloud, so as to realize the classified management of configuration files of a private cloud.

[0005] The first aspect of this application provides a method for managing configuration files in a private cloud, including:

[0006] Obtain the configuration file package of the target private cloud; wherein, the configuration file package of the target private cloud includes: the configuration file of each component included in the target private cloud;

[0007] From the configuration file package of the target private cloud, the data of each management item belonging to the configuration data management page of the target private cloud is screened out; wherein, each management item is a management dimension of the configuration file of the target private cloud;

[0008] Using the data from each management item of the target private cloud's configuration data management page that has been screened out, construct the target private cloud's configuration data management page.

[0009] Optionally, the configuration file for each component of the target private cloud includes: basic environment information and service table of the component; management items include: improving basic content, improving basic information, improving service planning and improving service attributes;

[0010] Specifically, data for each management item belonging to the configuration data management page of the target private cloud is extracted from the configuration file package of the target private cloud, including:

[0011] Using the architecture information of the target private cloud, the data for completing the basic content is generated; wherein, the data for completing the basic content is used to describe the composition of the target private cloud in terms of region, availability zone and cluster.

[0012] From the basic environment information of each component included in the configuration file, find the attribute information of each region of the target private cloud, the attribute information of each availability zone under each region of the target private cloud, and the attribute information of each cluster under each availability zone under each region of the target private cloud; combine the attribute information of clusters belonging to the same availability zone to obtain the data of each availability zone in the complete basic information; combine the attribute information of each availability zone belonging to the same region to obtain the data of each region in the complete basic information; combine the attribute information of each region belonging to the target private cloud to obtain the data of the entire region in the complete basic information.

[0013] From the service table of each component included in the configuration file, according to the correspondence between products and components under the cluster, the service information provided by the components belonging to the same product is found, and the services with parent-child relationships among the services provided by the components belonging to the same product are identified; a service list of components included in each product under each cluster of the target private cloud is constructed to obtain the data in the improved service plan; wherein, in the service list of components included in a product, the service information of the services provided by each component under that product is stored according to the category item, and the service information of services with parent-child relationships is stored in a manner that the parent service is stored at the first level and the child service is stored at the second level; the data of the service attribute category item in the service list of components included in each product under each cluster of the target private cloud is used as the data for improving service attributes.

[0014] Optionally, the configuration file for each component in the target private cloud also includes: the component's private configuration information, resource information, and component table; management items also include: confirming product information, improving address planning, improving product custom configuration, component custom configuration, and component capacity configuration; control methods also include:

[0015] Based on the correspondence between products and components in the cluster, determine the components of each product contained in the cluster of the target private cloud from the component table of each component in the target private cloud, and construct a list of products contained in each cluster of the target private cloud and a list of components contained in the same product as data in the product information confirmation.

[0016] Obtain the download address of each component contained in the target private cloud, and combine the download addresses of components belonging to the same cluster of the target private cloud as the download address plan of the cluster of the target private cloud; wherein, the download address plan of each cluster contained in the target private cloud is used as data to improve the address plan.

[0017] Construct a list of products included in each cluster of the target private cloud. Obtain the configuration information of each product in the list of products included in each cluster of the target private cloud from the private configuration information of the component configuration file, and store the obtained product configuration information in the list of products to which it belongs. The list of products included in each cluster of the target private cloud that stores the product configuration information is used as data to improve the product custom configuration.

[0018] Based on the correspondence between products and components in the cluster, construct a list of products included in each cluster of the target private cloud and a list of components included in each product; find the private configuration information of components belonging to the same product from the component configuration files, including private configuration information, and store the private configuration information of the found components belonging to the same product in the corresponding component list; wherein, the list of products included in each cluster of the target private cloud and the list of components included in each product containing the private configuration information of the components are used as data in the component custom configuration;

[0019] Based on the correspondence between products and components within the cluster, construct a list of products included in each cluster of the target private cloud and a list of components included in each product; find the capacity configuration information of components belonging to the same product from the resource information of each component in the configuration file, and store the capacity configuration information of the found components belonging to the same product in the corresponding component list of the product; wherein, the list of products included in each cluster of the target private cloud and the list of components included in each product containing the component capacity configuration information are used as data in the component capacity configuration.

[0020] Optionally, after constructing the configuration data management page of the target private cloud using the data from the various management items of the screeningd configuration data management page, the control method further includes:

[0021] The configuration data management page of the target private cloud displays the data for each management item; each management item's data occupies one page.

[0022] Responding to the editing command entered by the user on the data display page of the management item, the system executes the corresponding editing command on the data of the management item to obtain the updated data of the management item; wherein, the updated data of the management item replaces the data of the management item displayed on the configuration data management page of the target private cloud.

[0023] Optionally, the configuration data management page of the target private cloud displays comprehensive service planning data, responds to editing commands entered by the user on the data display page of the management item, executes the editing commands corresponding to the editing commands on the data of the management item, and obtains the updated data of the management item, including:

[0024] In response to the migration command entered by the user on the data display page for improving service planning, determine the service specified by the migration command; wherein, the service specified by the migration command is a child service with a parent-child relationship;

[0025] According to the migration instruction, determine the parent service of the service specified in the migration instruction after migration, establish the parent-child relationship between the determined parent service and the service specified in the migration instruction, and release the original parent service of the service specified in the migration instruction and the parent-child relationship between the service specified in the migration instruction and the service specified in the migration instruction.

[0026] Optionally, the control methods also include:

[0027] The service table in the configuration file of the target component is updated using the service specified by the migration instruction and the parent-child relationship of the parent service after the migration of the service specified by the migration instruction; wherein, the target component is the component that provides the service specified by the migration instruction to the target private cloud.

[0028] Optionally, the configuration data management page of the target private cloud displays complete service attribute data. The response to the user's edit command input on the data display page of the management item involves executing the edit command corresponding to the edit command on the data of the management item to obtain the updated data of the management item, including:

[0029] Respond to the editing instructions entered by the user on the data display page for improving service attributes, and determine the service specified in the editing instructions;

[0030] Receive the service attributes edited by the user according to the edit command, and update the original service attributes of the service specified by the edit command with the edited service attributes.

[0031] Optionally, the control methods also include:

[0032] From the service dependency information of each component of the target private cloud, identify the components that provide the services specified by the dependency editing instructions;

[0033] Using the updated service attributes specified by the edit command, update the configuration content in the component generation configuration table of the component specified by the edit command.

[0034] A second aspect of this application provides a configuration file management device for a private cloud, comprising:

[0035] The acquisition unit is used to acquire the configuration file package of the target private cloud; wherein, the configuration file package of the target private cloud includes: the configuration file of each component included in the target private cloud;

[0036] The screening unit is used to screen out data belonging to each management item of the configuration data management page of the target private cloud from the configuration file package of the target private cloud; wherein each management item is a management dimension of the configuration file of the target private cloud;

[0037] The building unit is used to construct the configuration data management page of the target private cloud using the data of each management item of the screening data belonging to the configuration data management page of the target private cloud.

[0038] Optionally, the configuration file for each component in the target private cloud includes: basic environment information and service tables for the component; management items include: improving basic content, improving basic information, improving service planning, and improving service attributes; among which, the screening unit includes:

[0039] The first screening unit is used to generate data with complete basic information using the architecture information of the target private cloud; wherein, the data with complete basic information is used to describe the composition of the target private cloud in terms of region, availability zone and cluster.

[0040] The second screening unit is used to find the attribute information of each region of the target private cloud, the attribute information of each availability zone under each region of the target private cloud, and the attribute information of each cluster under each availability zone under each region of the target private cloud from the basic environment information of each component included in the configuration file; combine the attribute information of clusters belonging to the same availability zone to obtain the data of each availability zone in the complete basic information; combine the attribute information of each availability zone belonging to the same region to obtain the data of each region in the complete basic information; and combine the attribute information of each region belonging to the target private cloud to obtain the data of the entire region in the complete basic information.

[0041] The third screening unit retrieves service information for services provided by components belonging to the same product from the service table of each component in the configuration file, based on the correspondence between products and components under the cluster. It then identifies services with parent-child relationships among the services provided by components belonging to the same product. A service list of components included in each product under each cluster of the target private cloud is constructed to obtain data for the comprehensive service planning. Specifically, the service list of components included in a product stores service information for each component under that product, categorized by type, and service information for services with parent-child relationships is stored in a first-level hierarchy, with child services in a second-level hierarchy. The service attribute category data in the service list of components included in each product under each cluster of the target private cloud serves as data for the comprehensive service attributes.

[0042] Optionally, the configuration file for each component in the target private cloud also includes: the component's private configuration information, resource information, and component table; management items also include: confirming product information, improving address planning, improving product custom configuration, component custom configuration, and component capacity configuration; the screening unit also includes:

[0043] The fourth screening unit is used to determine the components of each product contained in the cluster of the target private cloud from the component table of each component in the target private cloud according to the correspondence between products and components under the cluster, and to construct a list of products contained in each cluster of the target private cloud and a list of components contained in the same product as data in the product information confirmation.

[0044] The fifth screening unit is used to obtain the download address of each component contained in the target private cloud, and combine the download addresses of components belonging to the same target private cloud cluster as the download address plan of the target private cloud cluster; wherein, the download address plan of each cluster contained in the target private cloud serves as data for improving the address plan.

[0045] The sixth screening unit is used to construct a list of products included in each cluster of the target private cloud. It obtains the configuration information of each product in the list of products included in each cluster of the target private cloud from the private configuration information of the component configuration file, and stores the obtained product configuration information in the list of its own product. The list of products included in each cluster of the target private cloud that stores the product configuration information is used as data to improve the product custom configuration.

[0046] The seventh screening unit is used to construct a list of products included in each cluster of the target private cloud and a list of components included in each product, according to the correspondence between products and components under the cluster; it finds the private configuration information of components belonging to the same product from the component configuration files including private configuration information, and stores the private configuration information of the found components belonging to the same product in the corresponding component list; wherein, the list of products included in each cluster of the target private cloud and the list of components included in each product containing the private configuration information of the components are used as data in the component custom configuration;

[0047] The eighth screening unit is used to construct a list of products included in each cluster of the target private cloud and a list of components included in each product, according to the correspondence between products and components under the cluster; it finds the capacity configuration information of components belonging to the same product from the resource information of each component included in the configuration file, and stores the capacity configuration information of the found components belonging to the same product in the corresponding component list of the product; wherein, the list of products included in each cluster of the target private cloud and the list of components included in each product containing the component capacity configuration information are used as data in the component capacity configuration.

[0048] Optionally, the control device also includes:

[0049] The display unit is used to show the data of each management item on the configuration data management page of the target private cloud; the data of each management item occupies one page.

[0050] The editing unit is used to respond to the editing instructions entered by the user on the data display page of the management item, execute the editing instructions on the data of the management item, and obtain the updated data of the management item; wherein, the updated data of the management item replaces the data of the management item displayed on the configuration data management page of the target private cloud.

[0051] Optionally, the configuration data management page of the target private cloud displays data with complete basic information. The editing unit executes the editing instructions entered by the user on the data display page of the management item, and performs the editing corresponding to the editing instructions on the data of the management item to obtain the updated data of the management item, which is used for:

[0052] Responding to the user's instruction to add items on the data display page for completing basic information, outputting a template page for the added items; where the added items include: adding a region, availability zone, or cluster; receiving the attribute information of the added items entered by the user on the template page for the added items, converting the data on the template page after the attribute information of the added items is filled in, obtaining the configuration information of the added items, and saving the attribute information of the added items.

[0053] Optionally, the configuration data management page of the target private cloud displays the complete address planning data. The editing unit executes the editing instructions entered by the user on the data display page of the management item, and performs the editing corresponding to the editing instructions on the data of the management item to obtain the updated data of the management item, which is used for:

[0054] In response to the user's edit command input on the data display page for improving address planning, download the download addresses of all components in the currently selected cluster and edit them to obtain the edited download addresses of all components in the currently selected cluster; obtain the edited download addresses of all components in the currently selected cluster uploaded by the user, and replace the stored download addresses of all components in the currently selected cluster with the edited download addresses of all components in the currently selected cluster.

[0055] Optionally, the configuration data management page of the target private cloud displays comprehensive service planning data. The editing unit executes the editing commands entered by the user on the data display page of the management item, performs the editing commands corresponding to the editing commands on the data of the management item, and obtains the updated data of the management item, which is used for:

[0056] Responding to the migration instructions entered by the user on the data display page for improving service planning, the system identifies the service specified in the migration instructions. The service specified in the migration instructions is a child service with a parent-child relationship. According to the migration instructions, the system determines the parent service of the service specified in the migration instructions after migration, establishes the parent-child relationship between the determined parent service and the service specified in the migration instructions, and releases the parent-child relationship between the original parent service of the service specified in the migration instructions and the service specified in the migration instructions.

[0057] Optionally, the control device also includes:

[0058] The first update unit is used to update the service table in the configuration file of the target component by utilizing the service specified by the migration instruction and the parent-child relationship of the parent service after the migration of the service specified by the migration instruction; wherein, the target component is the component that provides the service specified by the migration instruction for the target private cloud.

[0059] Optionally, the configuration data management page of the target private cloud displays complete service attribute data. The editing unit executes the editing instructions entered by the user on the data display page of the management item, performs the editing corresponding to the editing instructions on the data of the management item, and obtains the updated data of the management item, which is used for:

[0060] Respond to the editing instructions entered by the user on the data display page for improving service attributes, determine the service specified in the editing instructions, receive the service attributes edited by the user for the service specified in the editing instructions, and update the original service attributes of the service specified in the editing instructions with the edited service attributes.

[0061] Optionally, the control device also includes:

[0062] The determination unit is used to determine the component that provides the service specified by the dependency editing instruction from the service dependency information of each component of the target private cloud.

[0063] The second update unit is used to update the configuration content in the component generation configuration table of the component of the service specified by the edit instruction by utilizing the updated service attributes of the service specified by the edit instruction.

[0064] The specific working principle of the control device provided in this application embodiment can be found in the relevant steps of the control method provided in this application embodiment, and will not be described in detail here.

[0065] A third aspect of this application provides a storage medium for storing a computer program, which, when executed, implements a management method for a private cloud configuration file as described in any of the first aspects.

[0066] As can be seen from the above technical solutions, in the private cloud configuration file management method provided in this application embodiment, after obtaining the configuration file package of the target private cloud, the data belonging to each management item is screened out according to the requirements of each management item of the configuration data management page of the target private cloud, and the configuration data management page of the target private cloud is constructed using the data of each management item. Since each management item is a management dimension of the configuration file of the target private cloud, screening out the data belonging to each management item of the configuration data management page of the target private cloud classifies the configuration file package of the target private cloud, which can realize the management of the configuration file package of the target private cloud from each management dimension, providing a foundation for realizing upper-layer functions such as deployment planning and automatic configuration generation. Attached Figure Description

[0067] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0068] Figure 1 This is a flowchart illustrating a method for managing configuration files in a private cloud, as proposed in an embodiment of this application.

[0069] Figure 2 This is a diagram illustrating the relationship between components and services proposed in the embodiments of this application;

[0070] Figure 3 This is a diagram illustrating the various management items of the configuration data management page proposed in the embodiments of this application;

[0071] Figures 4a to 4m This is a diagram illustrating a configuration data management page for various management items, as proposed in an embodiment of this application.

[0072] Figure 5This is a flowchart illustrating another method for managing configuration files in a private cloud, as proposed in an embodiment of this application.

[0073] Figure 6a This is an architecture diagram of a private cloud proposed in an embodiment of this application;

[0074] Figure 6b This is a diagram showing the relationship between components and services under the service discovery strategy proposed in the embodiments of this application.

[0075] Figure 7a This is a diagram illustrating the product components proposed in an embodiment of this application;

[0076] Figure 7b This is a diagram illustrating the dependency graph proposed in the embodiments of this application;

[0077] Figure 8 A flowchart illustrating the self-healing process provided in the embodiments of this application;

[0078] Figure 9 This is a schematic diagram of the structure of the configuration file management device for a private cloud proposed in an embodiment of this application. Detailed Implementation

[0079] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0080] This application discloses a method for managing configuration files in a private cloud, such as... Figure 1 As shown, the steps include:

[0081] S101. Obtain the configuration file package of the target private cloud.

[0082] The configuration file package for the target private cloud includes the configuration file for each component of the target private cloud.

[0083] It should be noted that the private cloud configuration file management method provided in this application embodiment is applied to a configuration center. Based on the customer's requirements, the number of regions, availability zones, clusters, and component selections included in the private cloud are determined. Further, a configuration file package and a component package for the private cloud are obtained. The component package includes all components included in the private cloud, and the configuration package is used to complete the configuration of the private cloud, primarily configuring each component of the private cloud.

[0084] When you need to manage a configuration file package of a private cloud, you need to first initialize the private cloud (i.e., the target private cloud) in the configuration center. After the initialization is completed, you can get the original data (i.e., the initialization data) displayed on the configuration data management page.

[0085] For any given private cloud, there are a large number of components. Analyzing the configuration files of these components reveals that the dynamic parts of the configuration files (referring to the content that varies across different environments) can be categorized as follows:

[0086] Basic environmental information, such as the main domain name and region list of a private cloud.

[0087] Private configurations are private, such as toggling certain features of a component that do not need to be known by other components.

[0088] Service dependency refers to a component accessing the services of other components.

[0089] Resource limitations, such as CPU and memory limitations.

[0090] Scheduling strategies, such as which machines each component will be deployed on, affinity, etc.

[0091] For the relationship between the private cloud components and the categorized configuration files of the aforementioned components, please refer to [link to relevant documentation]. Figure 2 .

[0092] The data types mentioned above are generally stored in list format during backend storage. It's understandable that initialization data is stored in list format. Specifically, basic environment information data can generally be stored in four tables: global basic information table, regional basic information table, availability zone basic information table, and physical cluster basic information table. The formats of these four tables are shown below.

[0093] 1. Global Basic Information Table

[0094] Fields type Remark global_id int Primary key placeholder global_attr string global properties

[0095] Attributes are self-explanatory standard formats, for example: [

[0097] {

[0098] "description": "Page Title",

[0099] "key": "title",

[0100] "value": "TCE"

[0101] } ]

[0103] 2. Regional Basic Information Table

[0104] Fields type Remark region_id int Region ID region_attr string Regional attributes

[0105] 3. Basic Information Table of Availability Zones

[0106] Fields type Remark region_id int Region ID zone_id int Availability Zone ID zone_attr string Availability zone attributes

[0107] 4. Physical Cluster Basic Information Table

[0108] Fields type Remark region_id int Region ID zone_id int Availability Zone ID cluster_id int Physical Cluster ID cluster_attr string Physical cluster attributes

[0109] Data in the category of private configurations is generally stored using component private configuration tables and product private configuration tables. The component private configuration table is shown in the table below.

[0110] Fields type Remark region_id int Region ID zone_id int Availability Zone ID cluster_id int Physical Cluster ID mod_id string Component ID private_attr string This component's private configuration attribute set has the same format as the global_attr in the global basic information table.

[0111] The product's proprietary configuration table is shown below.

[0112] Fields type Remark region_id int Region ID zone_id int Availability Zone ID cluster_id int Physical Cluster ID mod_id string Product ID private_attr string This product's private configuration attribute set has the same format as the global_attr in the global basic information table.

[0113] Data in the category of service dependencies is generally stored using a service dependency table, as shown in the table below.

[0114] Fields type Remark mod_id string Component ID svc_id string Dependent Service ID customize_name string Give the dependent services an alias that this component uses. scop string Service discovery strategy

[0115] The service discovery strategies listed in the table above support:

[0116] null allows access to the nearest location;

[0117] The `region` parameter specifies a region-level service within the current region.

[0118] The `zone` parameter specifies a service at the availability zone level within the current availability zone of the current region.

[0119] `cluster` specifies a cluster-level service for the current physical cluster in the current availability zone of the current region;

[0120] all_region provides services at the region level within all regions;

[0121] all_zone: Services at the availability zone level among all availability zones in the current region;

[0122] all_cluster: A cluster-level service among all physical clusters in the current availability zone of the current region;

[0123] all_region_all_zone provides a specific availability zone-level service across all regions and availability zones.

[0124] all_zone_all_cluster is a cluster-level service for all physical clusters in all availability zones of the current region;

[0125] all_region_all_zone_all_cluster refers to a cluster-level service for all regions, all availability zones, and all physical clusters;

[0126] Data related to resource constraints is typically stored using a component resource table, as shown in the table below.

[0127] Fields type Remark region_id int Region ID zone_id int Availability Zone ID cluster_id int Physical Cluster ID mod_id string Component ID ins_num int Number of copies cpu_request int How many cores should be allocated at least? cpu_limit int Maximum number of cores mem_request int How much memory to allocate at least mem_limit int Maximum memory limit init_delay_second int How many seconds after startup will the liveness detection begin?

[0128] Data in the category of scheduling strategies is generally stored in a component scheduling strategy table, as shown in the table below.

[0129] Fields type Remark region_id int Region ID zone_id int Availability Zone ID cluster_id int Physical Cluster ID mod_id string Component ID node_selector string Matching label scheduling, for example, {"cvm":"enable"} taint string Exclusive scheduling, such as exclusive use of a machine. topology string Topology-based unpacking scheduling, such as unpacking across availability zones.

[0130] S102. From the configuration file package of the target private cloud, filter out the data of each management item belonging to the configuration data management page of the target private cloud.

[0131] To manage the configuration files of various components in a private cloud and enable upper-layer functions such as deployment planning and automatic configuration generation, the component configuration files need to be categorized and stored. Therefore, the configuration data management page has multiple management items, each referring to a dimension of data in the component's configuration file.

[0132] Step S101 can obtain the raw data of each management item of the configuration data management page, that is, the data that forms the data of each management item of the configuration data management page. Therefore, before generating the data of each management item of the configuration data management page, it is necessary to classify the data in the target private cloud configuration file package according to the requirements of each management item of the configuration data management page.

[0133] S103. Using the data from each management item of the configuration data management page of the target private cloud that has been screened out, construct the configuration data management page of the target private cloud.

[0134] Each management item in the configuration management page has its corresponding data storage format. After the data belonging to each management item of the configuration data management page is screened in step S102, it needs to be processed according to the data storage format requirements of each management item to obtain the storage data of each management item. After the storage data of each management item of the configuration management page is obtained, the configuration data management page of the target private cloud is completed.

[0135] After obtaining the configuration data management page of the target private cloud from the configuration center, the user performs operations on the configuration management data page. The configuration center responds to the user's operations and displays the data of the management items on the configuration data management page specified by the user.

[0136] In the private cloud configuration file management method provided in this application embodiment, after obtaining the configuration file package of the target private cloud, the data belonging to each management item is screened out according to the requirements of each management item of the configuration data management page of the target private cloud, and the configuration data management page of the target private cloud is constructed using the data of each management item. Since each management item is a management dimension of the configuration file of the target private cloud, screening out the data belonging to each management item of the configuration data management page of the target private cloud classifies the configuration file package of the target private cloud. This enables the management of the configuration file package of the target private cloud from each management dimension, providing a foundation for realizing upper-layer functions such as deployment planning and automatic configuration generation.

[0137] Alternatively, in another embodiment of this application, such as Figure 3 As shown, the management items that can be set on the configuration data management page of the private cloud include: completing basic content, completing basic information, confirming product information, completing address planning, completing product custom configuration, component custom configuration, component capacity configuration, completing service planning, and completing service attributes.

[0138] Therefore, it is necessary to use the data of each of the above management items from the configuration file package of the target private cloud in step S102, format the data of each of the above management items, and construct the configuration data management page of the target private cloud.

[0139] Specifically, in this embodiment, in the implementation of step S102, the data for each of the above management items can be obtained by filtering through the following aspects:

[0140] 1. Utilize the architecture information of the target private cloud to generate data with complete basic content; the data with complete basic content is used to describe the composition of the target private cloud in terms of region, availability zone and cluster.

[0141] From a basic architecture perspective, a private cloud is divided into multiple regions, each region includes multiple availability zones, and each availability zone includes multiple clusters. Therefore, the "Complete Basic Content" management item on the configuration data management page is used to display the basic architecture of the target private cloud.

[0142] like Figure 4a On the left side of the screen, "global" indicates the global domain of a private cloud. Specifically, under this global domain, there is a region called "hongkong". The region "hongkong" contains availability zones "hongkong-pccw" and "cutko". Availability zone "hongkong-pccw" includes cluster "gaia-1".

[0143] 2. From the basic environment information of each component included in the configuration file, find the attribute information of each region of the target private cloud, the attribute information of each availability zone under each region of the target private cloud, and the attribute information of each cluster under each availability zone under each region of the target private cloud; combine the attribute information of clusters belonging to the same availability zone to obtain the data of each availability zone in the complete basic information; combine the attribute information of each availability zone belonging to the same region to obtain the data of each region in the complete basic information; combine the attribute information of each region belonging to the target private cloud to obtain the data of the entire region in the complete basic information.

[0144] The "Complete Basic Information" management item mainly describes the target private cloud's basic attribute information in terms of region, availability zone, and region. Specifically, the basic attribute information describes the attribute information of each region included in the target private cloud, the attribute information of the availability zones included in each region of the target private cloud, and the attribute information of each cluster included in each availability zone under each region of the target private cloud.

[0145] The four tables—global basic information table, regional basic information table, availability zone basic information table, and physical cluster basic information table—presented above for each component can determine the attribute information of each region of the target private cloud, the attribute information of each availability zone within each region of the target private cloud, and the attribute information of each cluster within each availability zone of each region of the target private cloud. Furthermore, the display page for the improved basic information management items can also be found here. Figure 4a and Figure 4b . Figure 4a The right side displays the attribute information of each region under the target private cloud's overall scope. Figure 4b The right side displays the attribute information of each availability zone under the target private cloud's Hong Kong region.

[0146] 3. Based on the correspondence between products and components under the cluster, determine the components of each product contained in the cluster of the target private cloud from the component table of each component in the target private cloud, and construct a list of products contained in each cluster of the target private cloud and a list of components contained in the same product, as data in the product information confirmation.

[0147] A component's component table can be in the form of the following table.

[0148] Fields type Remark region_id int Region ID zone_id int Availability Zone ID cluster_id int Physical Cluster ID mod_id string Component ID

[0149] By using the component ID in the component table of each component, the identifier of the product to which the component belongs can be calculated. Each cluster of the target private cloud contains multiple products. After calculating the identifier of the product to which each component of the target private cloud belongs, the components included in each product can be determined according to the correspondence between products and components under the cluster. Then, a list of products included in each cluster and a list of components included in the same product can be constructed respectively.

[0150] See Figure 4c The product list of cluster gaia-1 is displayed in the right column. Figure 4d This shows Figure 4c The product being displayed includes a list of its components.

[0151] 4. Obtain the download address of each component contained in the target private cloud, and combine the download addresses of components belonging to the same cluster of the target private cloud as the download address plan for the cluster of the target private cloud; among them, the download address plan of each cluster contained in the target private cloud is used as data to improve the address plan.

[0152] The download addresses of the components are stored in another external system. The download addresses of each component included in the target private cloud are obtained from this external system. The "Improved Address Planning" management item displays and manages the download addresses of components at the cluster level. Therefore, after obtaining the download address of each component, it is necessary to combine the download addresses of the components in each cluster according to the requirements of the components included in the target private cloud cluster.

[0153] See Figure 4e The download links for components not included in the gaia-1 cluster are displayed in the right-hand column of the page.

[0154] 5. Construct a list of products included in each cluster of the target private cloud. Obtain the configuration information of each product in the list of products included in each cluster of the target private cloud from the private configuration information of the component's configuration file, and store the obtained product configuration information in the list of its own product. The list of products included in each cluster of the target private cloud that stores the product configuration information is used as data to improve the product's custom configuration.

[0155] The product private configuration table under the category of "private configuration of a component" proposed above shows the private configuration of a component at the product level. Therefore, the configuration attributes of the component at the product level can be obtained from the product private configuration table under the category of "private configuration of a component" in the target private cloud.

[0156] Figure 4f This displays a list of products within a cluster. Figure 4g Showing Figure 4f The configuration information of a product in the product list.

[0157] 6. Based on the correspondence between products and components under the cluster, construct a list of products included in each cluster of the target private cloud and a list of components included in each product; find the private configuration information of components belonging to the same product from the private configuration information included in the configuration file, and store the private configuration information of the found components belonging to the same product in the corresponding component list; the list of products included in each cluster of the target private cloud and the list of components included in each product containing the private configuration information of the components are used as data in the component custom configuration.

[0158] Similar to point 5, the category of private configuration in the component's configuration file also includes a component private configuration table, which displays the component's private configuration information. Therefore, the component's private configuration information is extracted from the component private configuration table of each component in the target private cloud.

[0159] Figure 4h It displays a list of components included in a product within a cluster. Figure 4i Showing Figure 4h The configuration information of a component in the component list.

[0160] 7. Based on the correspondence between products and components under the cluster, construct a list of products included in each cluster of the target private cloud and a list of components included in each product; find the capacity configuration information of components belonging to the same product from the resource information of each component included in the configuration file, and store the capacity configuration information of the found components belonging to the same product in the corresponding component list; wherein, the list of products included in each cluster of the target private cloud and the list of components included in each product containing the component capacity configuration information are used as data in the component capacity configuration.

[0161] The component's resource information is displayed in a resource information table, as follows:

[0162] Fields type Remark region_id int Region ID zone_id int Availability Zone ID cluster_id int Physical Cluster ID mod_id string Component ID ins_num int Number of copies cpu_request int How many cores should be allocated at least? cpu_limit int Maximum number of cores mem_request int How much memory to allocate at least mem_limit int Maximum memory limit init_delay_second int How many seconds after startup will the liveness detection begin?

[0163] In the table above, the four rows from cpu_request to mem_limit show the capacity configuration information of a component.

[0164] Similarly, the component ID can be used to identify the product to which the component belongs. In this way, the capacity configuration information of components belonging to the same product can be found from the resource information table of each component.

[0165] Figure 4j It displays a list of components included in a product within a cluster. Figure 4k Showing Figure 4j The capacity configuration information of a component in the component list.

[0166] 8. From the service table of each component included in the configuration file, according to the correspondence between products and components under the cluster, find the service information provided by the components belonging to the same product, and identify the services with parent-child relationships among the services provided by the components belonging to the same product; construct the service list of each product included in each cluster of the target private cloud to obtain the data for perfecting the service plan; wherein, in the service list of components included in a product, the service information of each component under that product is stored according to the category item, and the service information of services with parent-child relationships is stored in the manner of parent services at the first level and child services at the second level; the data of the service attribute category items in the service list of each product included in each cluster of the target private cloud is used as the data for perfecting the service attributes.

[0167] The service table for one component is shown in the table below:

[0168] Fields type Remark region_id int Region ID zone_id int Availability Zone ID cluster_id int Physical Cluster ID svc_id string Service ID svc_level string Service levels: global, region, zone, cluster. parent_region_id int Parent service's region ID parent_zone_id int Parent service's availability zone ID parent_cluster_id int Parent service physical cluster ID parent_svc_id string Parent Service ID parent_svc_level string Parent service level svc_own_mod_id string Service Components svc_description string Service Notes svc_attr string Service attribute sets, with the same format as the global_attr in the global basic information table, mainly contain information such as domain name, IP address, port, and node_list. Different service attribute sets differ and are extensible.

[0169] In the component's service table, the rows from `parent_region_id` to `parent_svc_level` describe the basic information of the parent services of the services provided by the component itself. The service information for each service provided by the component is described by the `svc_attr` service attribute category.

[0170] have Figure 4l As can be seen, the service name circled in the large box, db.db_1, is the parent service of the other two services in the box. In other words, the services circled in the large box have a parent-child relationship. Furthermore, the child service is displayed below the parent service, and the operation execution items of the child service also display the migration operation button circled in the small box. Figure 4m It displays service information for a service.

[0171] Services with a parent-child relationship have the following functions:

[0172] Deployment relationships are expressed through parent-child services. For example, if a database service's parent service is a database instance service, it means that the database resides on a specific instance. If a database instance service's parent service is a database cluster service, it means that the instance resides within a specific cluster.

[0173] Sub-services automatically inherit all attributes from their parent services, achieving attribute layering and reducing configuration complexity. For example, the database service's attribute set includes the database name, username, and password. The database instance service's attribute set includes the address and port. The database cluster service's attribute set includes the list of storage hosts and the cluster administrator account, etc.

[0174] It should also be noted that the management items on the configuration data management page provided in the above embodiments are relatively comprehensive. In actual applications, the management items on the configuration data management page may not include all of the above-mentioned items. They may include only four management items: improving basic content, improving basic information, improving service planning, and improving service attributes. In other words, the data of the target private cloud's configuration file package is managed from the management dimensions corresponding to these four management items. In this case, when screening the data for the management items, the solutions shown in only aspects 1, 2, and 8 can be implemented.

[0175] Of course, the other display options can be optionally implemented when setting the corresponding management items on the configuration data management page.

[0176] Another embodiment of this application also provides a method for managing configuration files in a private cloud, such as... Figure 5 As shown, the steps include:

[0177] S501. Obtain the configuration file package of the target private cloud; wherein, the configuration file package of the target private cloud includes: the configuration file of each component included in the target private cloud.

[0178] S502. From the configuration file package of the target private cloud, filter out the data of each management item belonging to the configuration data management page of the target private cloud; where each management item is a management dimension of the configuration file of the target private cloud.

[0179] S503. Using the data from each management item of the configuration data management page of the target private cloud that has been screened out, construct the configuration data management page of the target private cloud.

[0180] S504. On the configuration data management page of the target private cloud, display the data for each management item; the data for each management item occupies one page.

[0181] For the target private cloud, after obtaining the various management items on its configuration data management page, the user can perform operations in the configuration center to call the configuration data management page and display the data of each management item on the target private cloud's configuration data management page.

[0182] The configuration data management page displays the configuration file data of the target private cloud components by management item, with each management item occupying a separate display page. This allows users to view the data according to the management dimensions corresponding to the management item.

[0183] S505: Respond to the editing command entered by the user on the data display page of the management item, execute the editing command corresponding to the editing command on the data of the management item, and obtain the updated data of the management item; wherein, the updated data of the management item replaces the data of the management item displayed on the configuration data management page of the target private cloud.

[0184] In this embodiment, the specific implementation of steps S501 to S503 is the same as that in the above embodiments, and will not be repeated here.

[0185] Based on the actions performed by users on the display pages of different management items, it is possible to edit the data of the management items operated by the users. The following are some examples to illustrate this.

[0186] In one implementation of step S505, if the user's input on the configuration data management page of the target private cloud is an operation to add a region, availability zone, or cluster, then step S505 is as follows:

[0187] Responding to the user's instruction to add items on the data display page for completing basic information, output a template page for the added items; among which, the added items include: adding a region, availability zone or cluster.

[0188] Receive the attribute information of the new item entered by the user on the template page for adding the new item, transform the data on the template page after the attribute information of the new item is filled in, obtain the configuration information of the new item, and save the attribute information of the new item.

[0189] like Figure 4a As shown, the data display page for completing basic information includes a "Add Region" button. The current page displays attribute information for each region within the entire domain. When a user needs to add a region, the "Add Region" button can be triggered. Upon receiving the user's instruction to add a region by triggering the "Add Region" button, the template page for that new item, i.e., the region's template page, will be invoked.

[0190] Users can enter the region's attribute information on the region's template page. The configuration center will then convert the data on the template page after the attribute information of the new item has been entered, obtain the configuration information of the new item, and save the attribute information of the new item.

[0191] Of course, you can also add availability zones or clusters, for example. Figure 4b As shown, on the current page displaying the attribute information of the Hong Kong region, touching the "Add Zone" button adds a new availability zone under the Hong Kong region. The system then calls up the availability zone template page and displays it to the user for completion. After the user completes the attribute information for the new availability zone, the configuration center converts the data on the template page containing the added attribute information to obtain and save the configuration information for the new item.

[0192] In another implementation of step S505, the complete address planning data is displayed on the configuration data management page of the target private cloud. The operation entered by the user on the configuration data management page of the target private cloud is an editing command. Correspondingly, step S505 is as follows:

[0193] In response to the user's edit command input on the data display page for improving address planning, download the download addresses of all components in the currently selected cluster and edit them to obtain the edited download addresses of all components in the currently selected cluster.

[0194] Retrieve the download addresses of all components in the currently selected cluster after editing by the user, and replace the stored download addresses of all components in the currently selected cluster with the edited download addresses of all components in the currently selected cluster.

[0195] like Figure 4eAs shown, the page displaying the data for perfecting the address planning also shows two buttons: "Download Address Planning Template" and "Upload Address Rules". When you need to modify the download address of a component of a cluster in the target private cloud, you can click the "Download Address Planning Template" button to download the download address of the component of that cluster to your local machine. After making the modifications locally, you can click the "Upload Address Rules" button to upload the modified download address of the cluster component to the configuration center.

[0196] In another implementation of step S505, the complete service planning data is displayed on the configuration data management page of the target private cloud. The operation entered by the user on the configuration data management page of the target private cloud is a migration command. Correspondingly, step S505 is:

[0197] In response to the migration command entered by the user on the data display page for improving service planning, determine the service specified by the migration command; wherein, the service specified by the migration command is a child service with a parent-child relationship;

[0198] According to the migration instruction, determine the parent service of the service specified in the migration instruction after migration, establish the parent-child relationship between the determined parent service and the service specified in the migration instruction, and release the original parent service of the service specified in the migration instruction and the parent-child relationship between the service specified in the migration instruction and the service specified in the migration instruction.

[0199] In this embodiment, the migration command is used to adjust the parent-child relationship of services with a parent-child relationship. For example, it can delete the child services included in a parent service and establish a parent-child relationship between a child service and a service.

[0200] like Figure 4j As shown in the diagram, once the migration button (circled in a small box) is triggered, the relationship between two services that originally had a parent-child relationship can be adjusted. Specifically, a migration command typically specifies the child service to be migrated and the new service to which the parent-child relationship needs to be established. Therefore, based on the migration command, the child service to be migrated and the service to which the new parent-child relationship needs to be established can be found, the child service to be migrated and its original parent service can be released, and the parent-child relationship between the child service to be migrated and the service to which the new parent-child relationship needs to be established can be re-established.

[0201] After the parent-child relationships between services are adjusted, the parent-child relationship information in the service tables of the components originally stored in the configuration center also needs to be adjusted accordingly. To achieve this, after determining the parent service of the service specified in the migration instruction after migration, establishing the parent-child relationship between the determined parent service and the service specified in the migration instruction, and releasing the original parent service of the service specified in the migration instruction and the parent-child relationship between the service specified in the migration instruction and the service specified in the migration instruction, the following can also be executed:

[0202] Update the service table in the configuration file of the target component using the service specified by the migration command and the parent-child relationship of the parent service after the migration of the service specified by the migration command; where the target component is the component that provides the service specified by the migration command to the target private cloud.

[0203] Specifically, the service table of the component to which the service specified by the migration command belongs is located in the configuration center. In the service table, the information in parent_region_id to parent_svc_id is updated to the information of the parent service after the service specified by the migration command is migrated.

[0204] In another implementation of step S505, the complete service attribute data is displayed on the configuration data management page of the target private cloud. The operation entered by the user on the configuration data management page of the target private cloud is an editing command. Correspondingly, step S505 is:

[0205] Respond to the editing instructions entered by the user on the data display page for improving service attributes, and determine the service specified in the editing instructions.

[0206] Receive the service attributes edited by the user according to the edit command, and update the original service attributes of the service specified by the edit command with the edited service attributes.

[0207] exist Figure 4k On the displayed page, each service has an edit button in the service attributes section. Users can adjust the service attributes of each service by triggering this button.

[0208] It should also be noted that when a service attribute is adjusted, the configuration content in the component generation configuration table of the service that the adjusted service depends on will be updated. Specifically, upon receiving the service attribute edited by the user according to the edit command, and updating the original service attribute of the service specified by the edit command with the edited service attribute, the following can be executed:

[0209] From the service dependency information of each component in the target private cloud, identify the component that provides the service specified by the dependency editing command.

[0210] Using the updated service attributes specified by the edit command, update the configuration content in the component generation configuration table of the component specified by the edit command.

[0211] Specifically, the service dependency information of a component is displayed in a service dependency table, which has already been shown above. In the service dependency table, svc_id indicates the ID of the service that the component depends on. The search is performed in the service dependency table of each component in the target private cloud until a service whose ID matches the service specified in the dependency editing command is found. Simultaneously, the component ID of the component whose service the dependency editing command specified is also found in the service dependency table.

[0212] One of the component's generation configuration tables is shown below:

[0213] Fields type Remark region_id int Region ID zone_id int Availability Zone ID cluster_id int Physical Cluster ID mod_id string Component ID mod_conf string Component configuration content error_msg string Error messages during configuration generation

[0214] After finding the component ID of the component that depends on the service specified by the edit command, the generator configuration table is located using the component ID, and the contents of mod_conf in the generator configuration table are updated.

[0215] It should also be noted that when searching the dependency service table of each component in the target private cloud until the ID of the component's dependency service matches the service specified by the dependency editing command, and the component ID of the component of the service specified by the dependency editing command is found, the contents of the scop in the service dependency table also need to be considered.

[0216] Assume there is Figure 6a The private cloud is assumed to have a component belonging to service S located in cluster-1.

[0217] Which components depend on service S, and what service discovery strategies are used when these components depend on this service? Based on the service level and service discovery strategy, it can be determined which components in the physical cluster will actually access the service. This can be elaborated as follows: Figure 6b .

[0218] Using the "region" branch in the diagram as an example, service S is at the region level. When a component declares that it needs to access this service:

[0219] If the access strategy is to access the nearest node, then only the local domain will be able to access the service, so the scope can be narrowed down to cluster1 to cluster4.

[0220] If the access strategy is list access, then the service will be accessible from any region, so the range is cluster1 to cluster8.

[0221] After calculating the affected logical scope using the above method, the configuration information of the components in the cluster that depend on this service can be automatically updated.

[0222] It should also be noted that the private cloud configuration file management method disclosed in this application can also construct a directed graph of components and services in the environment based on the relationships between components, thereby providing the following views:

[0223] Which services does a component depend on? Which components depend on a service? Which components does a component depend on? Which components does a component depend on? Graph showing the relationships between components.

[0224] Figure 7a The image displays multiple components belonging to the product CLB. The "Operations" section shows buttons for each component's dependent components, its dependent components, and a "View Dependency Graph" button. Triggering these buttons displays the component's dependent components, its dependent components, and the dependency graph. For example, triggering the "View Dependency Graph" button on the component with the ID "tcloud-clb-ccdb" shown in the image will display the dependency graph as follows: Figure 7b As shown.

[0225] In the configuration center, an additional copy of the full template information is stored. Figure 4d When you select the product component list, the configuration center will perform a self-healing process, filling in any missing configuration items with the default values ​​from the template. Maintaining configuration information on the page involves making minor adjustments based on the self-healing results. For details on the self-healing process, please refer to [link / reference needed]. Figure 8 The steps include:

[0226] S801, Complete the newly added items in the basic environment information.

[0227] Added items to the complete basic environment information, such as global configuration items for multilingual support.

[0228] S802, Get the version and tag of each component.

[0229] Specifically, according to Figure 4d Check the box above to get the product component list and obtain the version and latest tag of each component in this private cloud project version.

[0230] S803. Delete the configuration items associated with obsolete components.

[0231] Specifically, for obsolete components, the data in each of the component's data tables will be deleted.

[0232] S804, Complete the newly added custom configuration.

[0233] If any private configuration items are added to an existing component, the default values ​​should be synchronized.

[0234] S805, Complete the newly added resource and scheduling configurations.

[0235] If a component has new resource limits or scheduling features, the default values ​​should be synchronized.

[0236] S806, Override service dependency declaration.

[0237] The specific service dependencies will depend on the new version.

[0238] S807, Complete the newly added services.

[0239] For any new services added by each component, they must be synchronized, and the IP information and other details must be the same as the original services provided by that component.

[0240] S808, Update the URL path field for each service.

[0241] For example, if the URL suffix of an existing service changes, it needs to be updated to the new version.

[0242] It should be noted that the configuration file management method for private clouds provided in this application can also be applied to blockchain systems.

[0243] Blockchain is a novel application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and cryptographic algorithms. Essentially, a blockchain is a decentralized database, a chain of data blocks linked together using cryptographic methods. Each data block contains information about a batch of network transactions, used to verify the validity of the information (anti-counterfeiting) and generate the next block. A blockchain can include an underlying platform, a platform product and service layer, and an application service layer.

[0244] The underlying blockchain platform can include functional modules such as user management, basic services, smart contracts, and operational monitoring. The user management module is responsible for managing the identity information of all blockchain participants, including maintaining public and private key generation (account management), key management, and maintaining the correspondence between user real identities and blockchain addresses (access management). Furthermore, under authorization, it monitors and audits transactions of certain real identities and provides risk control rule configuration (risk control audit). The basic services module is deployed on all blockchain node devices to verify the validity of business requests. After consensus is reached on valid requests, they are recorded in storage. For a new business request, the basic services first perform interface adaptation parsing and authentication (interface adaptation), and then encrypt the business information using a consensus algorithm (consensus management). After encryption, the data is transmitted completely and consistently to the shared ledger (network communication) and recorded and stored. The smart contract module is responsible for contract registration, issuance, triggering, and execution. Developers can define contract logic using a programming language and publish it to the blockchain (contract registration). According to the contract terms, the key or other events are invoked to trigger execution and complete the contract logic. It also provides functions for contract upgrades and cancellations. The operation monitoring module is mainly responsible for deployment, configuration modification, contract settings, cloud adaptation, and real-time status visualization output during product release, such as alarms, network monitoring, and monitoring of node device health status.

[0245] The platform's product service layer provides the basic capabilities and implementation frameworks for typical applications. Developers can leverage these basic capabilities, along with the specific characteristics of their business needs, to implement blockchain-based business logic. The application service layer provides blockchain-based application services to business stakeholders.

[0246] Another embodiment of this application also provides a device for managing configuration files in a private cloud, such as... Figure 9 As shown, it includes:

[0247] The acquisition unit 901 is used to acquire the configuration file package of the target private cloud; wherein, the configuration file package of the target private cloud includes: the configuration file of each component included in the target private cloud;

[0248] The screening unit 902 is used to screen out data from the configuration file package of the target private cloud, which belongs to each management item of the configuration data management page of the target private cloud; wherein each management item is a management dimension of the configuration file of the target private cloud.

[0249] Construction unit 903 is used to construct the configuration data management page of the target private cloud using the data of each management item of the screening belonging to the configuration data management page of the target private cloud.

[0250] Optionally, the configuration file for each component of the target private cloud includes: basic environment information and service tables for the component; management items include: improving basic content, improving basic information, improving service planning, and improving service attributes; wherein, screening unit 902 includes:

[0251] The first screening unit is used to generate data with complete basic information using the architecture information of the target private cloud; the data with complete basic information is used to describe the composition of the target private cloud in terms of region, availability zone and cluster.

[0252] The second screening unit is used to find the attribute information of each region of the target private cloud, the attribute information of each availability zone under each region of the target private cloud, and the attribute information of each cluster under each availability zone under each region of the target private cloud from the basic environment information of each component included in the configuration file; combine the attribute information of clusters belonging to the same availability zone to obtain the data of each availability zone in the complete basic information; combine the attribute information of each availability zone belonging to the same region to obtain the data of each region in the complete basic information; and combine the attribute information of each region belonging to the target private cloud to obtain the data of the entire region in the complete basic information.

[0253] The third screening unit retrieves service information from the service tables of each component in the configuration file, based on the correspondence between products and components within the cluster. It then identifies services with parent-child relationships among these services. A service list of components included in each product within each cluster of the target private cloud is constructed to obtain data for the comprehensive service planning. Within the service list of components included in a product, service information for each component under that product is stored according to its category, with parent services at the first level and child services at the second level. The service attribute category data within the service list of components included in each product within each cluster of the target private cloud serves as the data for comprehensive service attributes.

[0254] Optionally, the configuration file for each component in the target private cloud also includes: the component's private configuration information, resource information, and component table; management items also include: confirming product information, improving address planning, improving product custom configuration, component custom configuration, and component capacity configuration; the screening unit 902 also includes:

[0255] The fourth screening unit is used to determine the components of each product contained in the cluster of the target private cloud from the component table of each component in the target private cloud according to the correspondence between products and components under the cluster, and to construct a list of products contained in each cluster of the target private cloud and a list of components contained in the same product as data in the product information confirmation.

[0256] The fifth screening unit is used to obtain the download address of each component contained in the target private cloud, and combine the download addresses of components belonging to the same target private cloud cluster as the download address plan of the target private cloud cluster; wherein, the download address plan of each cluster contained in the target private cloud serves as data for improving the address plan.

[0257] The sixth screening unit is used to construct a list of products included in each cluster of the target private cloud. It obtains the configuration information of each product in the list of products included in each cluster of the target private cloud from the private configuration information of the component configuration file, and stores the obtained product configuration information in the list of its own product. The list of products included in each cluster of the target private cloud that stores the product configuration information is used as data to improve the product custom configuration.

[0258] The seventh screening unit is used to construct a list of products included in each cluster of the target private cloud and a list of components included in each product, according to the correspondence between products and components under the cluster; it finds the private configuration information of components belonging to the same product from the component configuration files including private configuration information, and stores the private configuration information of the found components belonging to the same product in the corresponding component list; wherein, the list of products included in each cluster of the target private cloud and the list of components included in each product containing the private configuration information of the components are used as data in the component custom configuration;

[0259] The eighth screening unit is used to construct a list of products included in each cluster of the target private cloud and a list of components included in each product, according to the correspondence between products and components under the cluster; it finds the capacity configuration information of components belonging to the same product from the resource information of each component included in the configuration file, and stores the capacity configuration information of the found components belonging to the same product in the corresponding component list of the product; wherein, the list of products included in each cluster of the target private cloud and the list of components included in each product containing the component capacity configuration information are used as data in the component capacity configuration.

[0260] Optionally, the control device also includes:

[0261] The display unit is used to show the data of each management item on the configuration data management page of the target private cloud; the data of each management item occupies one page.

[0262] The editing unit is used to respond to the editing instructions entered by the user on the data display page of the management item, execute the editing instructions on the data of the management item, and obtain the updated data of the management item; wherein, the updated data of the management item replaces the data of the management item displayed on the configuration data management page of the target private cloud.

[0263] Optionally, the configuration data management page of the target private cloud displays data with complete basic information. The editing unit executes the editing instructions entered by the user on the data display page of the management item, and performs the editing corresponding to the editing instructions on the data of the management item to obtain the updated data of the management item, which is used for:

[0264] Responding to the user's instruction to add items on the data display page for completing basic information, outputting a template page for the added items; where the added items include: adding a region, availability zone, or cluster; receiving the attribute information of the added items entered by the user on the template page for the added items, converting the data on the template page after the attribute information of the added items is filled in, obtaining the configuration information of the added items, and saving the attribute information of the added items.

[0265] Optionally, the configuration data management page of the target private cloud displays the complete address planning data. The editing unit executes the editing instructions entered by the user on the data display page of the management item, and performs the editing corresponding to the editing instructions on the data of the management item to obtain the updated data of the management item, which is used for:

[0266] In response to the user's edit command input on the data display page for improving address planning, download the download addresses of all components in the currently selected cluster and edit them to obtain the edited download addresses of all components in the currently selected cluster; obtain the edited download addresses of all components in the currently selected cluster uploaded by the user, and replace the stored download addresses of all components in the currently selected cluster with the edited download addresses of all components in the currently selected cluster.

[0267] Optionally, the configuration data management page of the target private cloud displays comprehensive service planning data. The editing unit executes the editing commands entered by the user on the data display page of the management item, performs the editing commands corresponding to the editing commands on the data of the management item, and obtains the updated data of the management item, which is used for:

[0268] Responding to the migration instructions entered by the user on the data display page for improving service planning, the system identifies the service specified in the migration instructions. The service specified in the migration instructions is a child service with a parent-child relationship. According to the migration instructions, the system determines the parent service of the service specified in the migration instructions after migration, establishes the parent-child relationship between the determined parent service and the service specified in the migration instructions, and releases the parent-child relationship between the original parent service of the service specified in the migration instructions and the service specified in the migration instructions.

[0269] Optionally, the control device also includes:

[0270] The first update unit is used to update the service table in the configuration file of the target component by utilizing the service specified by the migration instruction and the parent-child relationship of the parent service after the migration of the service specified by the migration instruction; wherein, the target component is the component that provides the service specified by the migration instruction for the target private cloud.

[0271] Optionally, the configuration data management page of the target private cloud displays complete service attribute data. The editing unit executes the editing instructions entered by the user on the data display page of the management item, performs the editing corresponding to the editing instructions on the data of the management item, and obtains the updated data of the management item, which is used for:

[0272] Respond to the editing instructions entered by the user on the data display page for improving service attributes, determine the service specified in the editing instructions, receive the service attributes edited by the user for the service specified in the editing instructions, and update the original service attributes of the service specified in the editing instructions with the edited service attributes.

[0273] Optionally, the control device also includes:

[0274] The determination unit is used to determine the component that provides the service specified by the dependency editing instruction from the service dependency information of each component of the target private cloud.

[0275] The second update unit is used to update the configuration content in the component generation configuration table of the component of the service specified by the edit instruction by utilizing the updated service attributes of the service specified by the edit instruction.

[0276] The specific working principle of the control device provided in this application embodiment can be found in the relevant steps of the control method provided in this application embodiment, and will not be described in detail here.

[0277] Another embodiment of this application provides a storage medium for storing a computer program, which, when executed, implements a private cloud configuration file management method as disclosed in any of the above embodiments.

[0278] According to one aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the new word discovery method provided in various alternative implementations of any of the above aspects.

[0279] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0280] It should be noted that the concepts of "first" and "second" mentioned in this invention are only used to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0281] Those skilled in the art will be able to implement or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for managing configuration files in a private cloud, characterized in that, include: Obtain the configuration file package of the target private cloud; wherein, the configuration file package of the target private cloud includes: the configuration file of each component included in the target private cloud; the configuration file of each component included in the target private cloud includes: the basic environment information and service table of the component; From the configuration file package of the target private cloud, data belonging to each management item of the configuration data management page of the target private cloud is screened out; wherein, each management item is a management dimension of the configuration file of the target private cloud; the management item includes: improving basic content, improving basic information, improving service planning, and improving service attributes; Using the data from each management item of the configuration data management page of the target private cloud that has been screened out, the configuration data management page of the target private cloud is constructed; Specifically, data belonging to various management items of the configuration data management page of the target private cloud are screened from the configuration file package of the target private cloud, including: Using the architecture information of the target private cloud, the data for completing the basic content is generated; wherein, the data for completing the basic content is used to describe the composition of the target private cloud in terms of region, availability zone, and cluster; From the basic environment information of each component included in the configuration file, the attribute information of each region of the target private cloud, the attribute information of each availability zone under each region of the target private cloud, and the attribute information of each cluster under each availability zone under each region of the target private cloud are found; the attribute information of clusters belonging to the same availability zone is combined to obtain the data of each availability zone in the complete basic information; the attribute information of each availability zone belonging to the same region is combined to obtain the data of each region in the complete basic information; and the attribute information of each region belonging to the target private cloud is combined to obtain the data of the entire region in the complete basic information. From the service table of each component included in the configuration file, according to the correspondence between products and components under the cluster, the service information provided by the components belonging to the same product is found, and the services with parent-child relationships among the services provided by the components belonging to the same product are identified; a service list of the components included in each product under each cluster of the target private cloud is constructed to obtain the data in the improved service plan; wherein, in the service list of the components included in a product, the service information of the services provided by each component under that product is stored according to the category item, and the service information of services with parent-child relationships is stored in a manner that the parent service is at the first level and the child service is at the second level; the data of the service attribute category item in the service list of the components included in each product under each cluster of the target private cloud is used as the data of the improved service attributes.

2. The control method according to claim 1, characterized in that, The configuration file for each component in the target private cloud also includes: the component's private configuration information, resource information, and component table; the management items also include: confirming product information, improving address planning, improving product custom configuration, component custom configuration, and component capacity configuration; the control method also includes: Based on the correspondence between products and components under the cluster, the components of each product included in the cluster of the target private cloud are determined from the component table of each component in the target private cloud, and a list of products included in each cluster of the target private cloud and a list of components included in the same product are constructed as data in the confirmed product information. Obtain the download address of each component contained in the target private cloud, and combine the download addresses of components belonging to the same cluster of the target private cloud as the download address plan of the cluster of the target private cloud; wherein, the download address plan of each cluster contained in the target private cloud is used as the data of the improved address plan; Construct a list of products included in each cluster of the target private cloud, obtain the configuration information of each product in the list of products included in each cluster of the target private cloud from the private configuration information of the component's configuration file, and store the obtained product configuration information in the list of its own product; wherein, the list of products included in each cluster of the target private cloud that stores the product configuration information serves as data in the improved product custom configuration; Based on the correspondence between products and components within a cluster, a list of products included in each cluster of the target private cloud and a list of components included in each product are constructed. From the component's configuration file, including private configuration information, the private configuration information of components belonging to the same product is retrieved, and this private configuration information is stored in relation to the components in the product's list of included components. The list of products included in each cluster of the target private cloud and the list of components included in each product containing the component's private configuration information serve as data in the component's custom configuration. Based on the correspondence between products and components within a cluster, a list of products included in each cluster of the target private cloud and a list of components included in each product are constructed. From the resource information of each component included in the configuration file, the capacity configuration information of components belonging to the same product is found, and the capacity configuration information of the found components belonging to the same product is stored corresponding to the components in the list of components included in the product. The list of products included in each cluster of the target private cloud and the list of components included in each product containing the stored component capacity configuration information serve as the data in the component capacity configuration.

3. The control method according to claim 1, characterized in that, After constructing the configuration data management page of the target private cloud using the data of each management item identified through screening and belonging to the configuration data management page of the target private cloud, the control method further includes: On the configuration data management page of the target private cloud, the data for each management item is displayed; wherein the data for each management item occupies one page. In response to an editing command input by the user on the data display page of the management item, the data of the management item is edited according to the editing command to obtain the updated data of the management item; wherein, the updated data of the management item replaces the data of the management item displayed on the configuration data management page of the target private cloud.

4. The control method according to claim 3, characterized in that, The configuration data management page of the target private cloud displays comprehensive service planning data. Responding to editing commands input by the user on the data display page of the management item, the system executes the editing commands corresponding to the editing commands on the data of the management item to obtain the updated data of the management item, including: In response to a migration command input by a user on the data display page for improving service planning, the service specified by the migration command is determined; wherein, the service specified by the migration command is a child service with a parent-child relationship; According to the migration instruction, determine the parent service of the service specified by the migration instruction after migration, establish the parent-child relationship between the determined parent service and the service specified by the migration instruction, and release the original parent service of the service specified by the migration instruction and the parent-child relationship between the service specified by the migration instruction and the service specified by the migration instruction.

5. The control method according to claim 4, characterized in that, Also includes: The service table in the configuration file of the target component is updated using the service specified by the migration instruction and the parent-child relationship of the parent service after the migration of the service specified by the migration instruction; wherein, the target component is the component that provides the service specified by the migration instruction to the target private cloud.

6. The control method according to claim 3, characterized in that, The configuration data management page of the target private cloud displays complete service attribute data. Responding to editing commands input by the user on the data display page of the management item, the system executes the editing commands corresponding to the editing commands on the data of the management item to obtain the updated data of the management item, including: In response to an editing instruction entered by the user on the data display page for improving service attributes, determine the service specified by the editing instruction; Receive the service attributes edited by the user according to the edit command, and update the original service attributes of the service specified by the edit command with the edited service attributes.

7. The control method according to claim 6, characterized in that, Also includes: From the service dependency information of each component of the target private cloud, determine the components that depend on the service specified by the editing command; Using the updated service attributes of the service specified by the editing instruction, update the configuration content in the component generation configuration table of the component of the service specified by the editing instruction.

8. A management and control device for configuration files in a private cloud, characterized in that, include: An acquisition unit is used to acquire a configuration file package of a target private cloud; wherein, the configuration file package of the target private cloud includes: a configuration file of each component included in the target private cloud; the configuration file of each component included in the target private cloud includes: basic environment information and service table of the component; The screening unit is used to screen out data belonging to each management item of the configuration data management page of the target private cloud from the configuration file package of the target private cloud; wherein each management item is a management dimension of the configuration file of the target private cloud; the management item includes: improving basic content, improving basic information, improving service planning, and improving service attributes; A construction unit is used to construct the configuration data management page of the target private cloud using the data of each management item of the screening belonging to the configuration data management page of the target private cloud; The screening unit includes: The first screening unit is used to generate the data for completing the basic content using the architecture information of the target private cloud; wherein the data for completing the basic content is used to describe the composition of the target private cloud in terms of region, availability zone and cluster. The second screening unit is used to find the attribute information of each region of the target private cloud, the attribute information of each availability zone under each region of the target private cloud, and the attribute information of each cluster under each availability zone under each region of the target private cloud from the basic environment information of each component included in the configuration file; combine the attribute information of clusters belonging to the same availability zone to obtain the data of each availability zone in the complete basic information; combine the attribute information of each availability zone belonging to the same region to obtain the data of each region in the complete basic information; and combine the attribute information of each region belonging to the target private cloud to obtain the data of the entire region in the complete basic information. The third screening unit is used to find the service information of the services provided by the components belonging to the same product from the service table of each component included in the configuration file, according to the correspondence between products and components under the cluster, and to determine the services with parent-child relationships among the services provided by the components belonging to the same product; construct the service list of the components included in each product under each cluster of the target private cloud to obtain the data in the improved service plan; wherein, in the service list of the components included in a product, the service information of the services provided by each component under that product is stored according to the category item, and the service information of services with parent-child relationships is stored in a manner that the parent service is at the first level and the child service is at the second level; the data of the service attribute category item in the service list of the components included in each product under each cluster of the target private cloud is used as the data of the improved service attributes.

9. The control device according to claim 8, characterized in that, The configuration file for each component in the target private cloud also includes: the component's private configuration information, resource information, and component table; the management items also include: confirming product information, improving address planning, improving product custom configuration, component custom configuration, and component capacity configuration; the screening unit also includes: The fourth screening unit is used to determine the components of each product contained in the cluster of the target private cloud from the component table of each component in the target private cloud according to the correspondence between products and components under the cluster, and to construct a list of products contained in each cluster of the target private cloud and a list of components contained in the same product as data in the confirmed product information. The fifth screening unit is used to obtain the download address of each component contained in the target private cloud, and combine the download addresses of components belonging to the same cluster of the target private cloud as the download address plan of the cluster of the target private cloud; wherein, the download address plan of each cluster contained in the target private cloud is used as the data for the improved address plan. The sixth screening unit is used to construct a list of products included in each cluster of the target private cloud, obtain the configuration information of each product in the list of products included in each cluster of the target private cloud from the private configuration information of the component's configuration file, and store the obtained product configuration information in the list of its own product; wherein, the list of products included in each cluster of the target private cloud that stores the product configuration information is used as data in the improved product custom configuration. The seventh screening unit is used to construct a list of products included in each cluster of the target private cloud and a list of components included in each product, according to the correspondence between products and components under the cluster; to find the private configuration information of components belonging to the same product from the configuration files of the components, and to store the private configuration information of the found components belonging to the same product in the corresponding list of components included in the product; wherein, the list of products included in each cluster of the target private cloud and the list of components included in each product containing the configuration private information of the components are used as data in the custom configuration of the components; The eighth screening unit is used to construct a list of products included in each cluster of the target private cloud and a list of components included in each product, according to the correspondence between products and components under the cluster; to find the capacity configuration information of components belonging to the same product from the resource information of each component included in the configuration file, and to store the capacity configuration information of the found components belonging to the same product in the corresponding list of components included in the product; wherein, the list of products included in each cluster of the target private cloud and the list of components included in each product containing the capacity configuration information are used as data in the component capacity configuration.

10. The control device according to claim 8, characterized in that, The control device also includes: The display unit is used to display the data of each management item on the configuration data management page of the target private cloud; wherein the data of each management item occupies one page; An editing unit is used to respond to an editing command input by a user on the data display page of the management item, and to perform the editing corresponding to the editing command on the data of the management item to obtain the updated data of the management item; wherein the updated data of the management item replaces the data of the management item displayed on the configuration data management page of the target private cloud.

11. The control device according to claim 10, characterized in that, The configuration data management page of the target private cloud displays comprehensive service planning data. The editing unit executes editing commands input by the user on the data display page of the management item, and performs the editing corresponding to the editing commands on the data of the management item to obtain the updated data of the management item, which is used for: In response to a migration instruction input by a user on the data display page for improving service planning, the service specified by the migration instruction is identified; wherein the service specified by the migration instruction is a child service with a parent-child relationship; according to the migration instruction, the parent service after the migration of the service specified by the migration instruction is identified, and the parent-child relationship between the identified parent service and the service specified by the migration instruction is established, and the original parent service of the service specified by the migration instruction and the parent-child relationship between the service specified by the migration instruction and the service specified by the migration instruction are released.

12. The control device according to claim 11, characterized in that, Also includes: The first update unit is used to update the service table in the configuration file of the target component by using the service specified by the migration instruction and the parent-child relationship of the parent service after the migration of the service specified by the migration instruction; wherein, the target component is a component that provides the service specified by the migration instruction to the target private cloud.

13. The control device according to claim 10, characterized in that, The configuration data management page of the target private cloud displays complete service attribute data. The editing unit executes editing commands input by the user on the data display page of the management item, and performs the editing corresponding to the editing commands on the data of the management item to obtain the updated data of the management item, which is used for: In response to an editing instruction entered by the user on the data display page for improving service attributes, the system determines the service specified by the editing instruction; receives the service attributes edited by the user for the service specified by the editing instruction, and updates the original service attributes of the service specified by the editing instruction with the edited service attributes.

14. The control device according to claim 13, characterized in that, Also includes: The determining unit is used to determine, from the service dependency information of each component of the target private cloud, the components that depend on the service specified by the editing instruction; The second update unit is used to update the configuration content in the component generation configuration table of the component of the service specified by the edit instruction by utilizing the updated service attributes of the service specified by the edit instruction.

15. A storage medium, characterized in that, Used to store computer programs, which, when executed, implement the management method for the configuration file of a private cloud as described in any one of claims 1 to 7.

16. A computer program product, characterized in that, The method includes computer instructions stored in a computer-readable storage medium; a processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the management method for the configuration file of a private cloud as described in any one of claims 1 to 7.