Configuration management method and device of cloud support component instance, electronic equipment and storage medium

Abstract

The invention discloses a configuration management method and device for cloud support component instances, electronic equipment and a storage medium, and the method and device are applied to the electronic equipment and specifically comprise the steps that component static configuration information of all cloud support component instances is collected; and performing identification processing based on the component static configuration information and the component dynamic configuration information of all the cloud support component instances to obtain a configuration change state. According to the method, the problem that configuration is difficult to manage in a manual mode due to the fact that instance component types and deployment form types are various and rapid to change in instance configuration management work is solved from the actual demand of cloud support instance configuration management in a cloud support platform scene, and the accuracy of configuration management is improved through fine management of a cloud support component configuration acquisition standard. The accuracy of the configuration data is ensured while the configuration acquisition efficiency of the cloud support component in the multi-cloud scene is improved, the problems of serious time consumption and poor accuracy in a manual mode are avoided, and more manpower and material resources can be saved.

Description

Technical Field

[0001] The present application relates to the field of cloud computing technology, and more specifically, to a method, device, electronic device, and storage medium for configuring and managing cloud support component instances. Background Art

[0002] A cloud computing platform is a distributed computing system that provides various services to users in a pay-per-use form, used to provide users with computing services, data storage services, and platform services that meet service quality requirements, and has characteristics such as high reliability, availability, scalability, and manageability. The realization of the functions of a cloud computing platform depends on a series of key underlying support components, namely cloud support components. Cloud support components include components that provide multiple key service capabilities such as public domain name resolution, public data storage, public software management, clock source synchronization, and control services. Through the service capabilities provided by cloud support component instances, while ensuring the provision of flexible and variable, scalable platform services at the application layer, a unified and stable basic capability is provided for all production nodes under the cloud support.

[0003] Currently, the configurations of each cloud support component instance are usually scattered in multiple instance objects or cloud services, and the management methods for them mostly adopt manual collection and manual maintenance methods. In the face of a large number of cloud support component instances in the cloud support scenario, there are problems of serious time consumption and poor accuracy in configuring and managing cloud support component instances through manual methods, and a large amount of manpower and material resources need to be consumed. Summary of the Invention

[0004] In view of this, the present application provides a method, device, electronic device, and storage medium for configuring and managing cloud support component instances, which are used to configure and manage cloud support components in an automated manner to avoid the problems of serious time consumption and poor accuracy in the manual method, and can save a lot of manpower and material resources.

[0005] To achieve the above object, the following solutions are proposed:

[0006] A method for configuring and managing cloud support component instances, which is applied to an electronic device, and the configuration management method includes steps:

[0007] Collect the component static configuration information of all cloud support component instances;

[0008] Based on the component static configuration information and the component dynamic configuration information of all cloud support component instances, perform identification processing to obtain the configuration change status.

[0009] Optionally, the component static configuration information includes global configuration information, physical configuration information, and software configuration information.

[0010] Optionally, the identification process based on the component static configuration information and the component dynamic configuration information of all cloud support component instances to obtain the configuration change status includes the steps of:

[0011] Collect the component dynamic configuration information according to the static configuration information;

[0012] Integrate the component dynamic configuration information collected regularly;

[0013] Compare the integrated component dynamic configuration information collected in previous times to obtain the configuration change status.

[0014] Optionally, the component dynamic configuration information includes non-fixed role configuration information, dynamic configuration information, and support component information.

[0015] Optionally, the configuration change status includes instance object differences and instance configuration differences.

[0016] A configuration management device for cloud support component instances, which is applied to an electronic device. The configuration management device includes:

[0017] An information collection module, configured to collect the component static configuration information of all cloud support component instances;

[0018] A management execution module, configured to perform an identification process based on the component static configuration information and the component dynamic configuration information of all cloud support component instances to obtain the configuration change status.

[0019] Optionally, the management execution module includes:

[0020] An information collection unit, configured to collect the component dynamic configuration information according to the static configuration information;

[0021] An information integration unit, configured to integrate the component dynamic configuration information collected regularly;

[0022] A comparison processing unit, configured to compare the integrated component dynamic configuration information collected in previous times to obtain the configuration change status.

[0023] Optionally, the component static configuration information includes global configuration information, physical configuration information, and software configuration information;

[0024] The component dynamic configuration information includes non-fixed role configuration information, dynamic configuration information, and support component information;

[0025] The configuration change status includes instance object differences and instance configuration differences.

[0026] An electronic device, the electronic device includes at least one processor and a memory connected to the processor, wherein:

[0027] The memory is used to store computer programs or instructions;

[0028] The processor is used to execute the computer programs or instructions, so that the electronic device implements the configuration management method as described above.

[0029] A computer-readable storage medium, applied to an electronic device, the storage medium carries one or more computer programs, and the one or more computer programs can be executed by the electronic device, so that the electronic device can implement the configuration management method as described above.

[0030] As can be seen from the above technical solutions, the present application discloses a configuration management method, device, electronic device and storage medium for cloud support component instances. The method and device are applied to an electronic device, specifically collecting the component static configuration information of all cloud support component instances; performing identification processing based on the component static configuration information and the component dynamic configuration information of all cloud support component instances to obtain the configuration change status. Starting from the actual needs of cloud support instance configuration management in the cloud support platform scenario, the present application solves the problem that it is difficult to manage the configuration manually due to the large number and fast changes of instance component types and deployment forms in the instance configuration management work. Through the refined management of the cloud support component configuration collection standard, while improving the efficiency of obtaining cloud support component configurations in a multi-cloud scenario, it ensures the accuracy of configuration data, avoids the problems of serious time consumption and poor accuracy in the manual method, and can save a lot of manpower and material resources. Description of the Drawings

[0031] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the following drawings are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0032] Figure 1 It is a flowchart of a configuration management method for cloud support component instances according to an embodiment of the present application;

[0033] Figure 2 It is a flowchart of the identification process of the configuration change status according to an embodiment of the present application;

[0034] Figure 3 It is a block diagram of a configuration management device for cloud support component instances according to an embodiment of the present application;

[0035] Figure 4A block diagram of a configuration management device for another cloud support component instance according to an embodiment of the present application;

[0036] Figure 5 This is a block diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0037] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0038] Figure 1 This is a flowchart of a configuration management method for a cloud support component instance according to an embodiment of the present application.

[0039] like Figure 1 As shown, the configuration management method provided in this embodiment is applied to electronic devices for configuration management of cloud support component instances of a cloud computing system. The electronic devices can be understood as computers, servers, and cloud platforms with computing capabilities. The configuration management method specifically includes the following steps:

[0040] S1. Collect component static configuration information of all cloud support component instances.

[0041] Through user input or automated collection methods, static information records of each cloud support component instance in the cloud computing system are collected, or component static configuration information. The component static configuration information in this application includes but is not limited to global configuration information, physical configuration information, and software configuration information. Among them, global configuration information includes region, deployment instance, availability zone, etc.; physical configuration information includes IP address, instance form, etc.; software configuration information includes component category, component cluster, etc. The details are shown in the following table:

[0042]

[0043]

[0044] By collecting this information, we can, on the one hand, record the static information of cloud-supported component instances and manage all component instances from different dimensions based on information such as deployment instance, component category, and cluster. On the other hand, we can also use the collected IP and component category configuration information as input for subsequent configuration to obtain dynamic component configuration information.

[0045] S2. Identify the configuration change status based on the collected component static configuration information.

[0046] That is, identify and process based on the collected component static configuration information and the component dynamic configuration information of all cloud support component instances, so as to obtain the configuration change status of all cloud support component instances. The specific process is as follows, as Figure 2 shown.

[0047] S201. Regularly collect component dynamic configuration information according to component static configuration information.

[0048] That is, use the collected component static configuration information as the input parameter for collecting the component static configuration information of all cloud support component instances, design the corresponding configuration acquisition interface based on this input parameter, and then regularly collect component dynamic configuration information based on this interface. The component dynamic configuration information specifically includes the following content:

[0049] 1. The non-fixed role configuration information of cloud support component instances, such as the roles of each zookeeper component node, etc.;

[0050] 2. The dynamic configuration information of cloud support component instances, such as the label information of container cluster Node nodes, etc.;

[0051] 3. The support component information for dynamic deployment, such as the container name, deployment node, IP node, running version, etc. in the container configuration items of the container cluster.

[0052] S202. Integrate and process the component static configuration information and the component dynamic configuration information.

[0053] Integrate and process the above-obtained component static configuration information and the regularly collected component dynamic configuration information according to the component type, and store them in each component data table respectively. The data table information can be displayed on the page, and a search function for filtering data according to attributes such as cloud instances and IPs is designed.

[0054] S203. Compare and process the component dynamic configuration information collected in previous times.

[0055] By comparing the component dynamic configuration information collected in previous times, the differences between the component dynamic configuration information of multiple cloud support component instances in previous times can be obtained, that is, the configuration change status. Among them, the configuration change status includes instance object differences and instance configuration differences.

[0056] The instance object difference refers to the difference in the number of instance objects when comparing the data obtained from two collections, and displays the instance objects marked as increased or decreased; the instance configuration difference refers to the configuration differences of the common instance objects in the data obtained from two collections, and displays the front and back data of the different configurations marked; among them, the instance objects with fixed deployment use the IP information as the unique identifier, and the instance objects with dynamic deployment use the name information as the unique identifier.

[0057] As can be seen from the above technical solution, this embodiment provides a method for configuring and managing cloud support component instances. This method is applied to an electronic device. Specifically, it collects the component static configuration information of all cloud support component instances, and performs identification processing based on the component static configuration information and the component dynamic configuration information of all cloud support component instances to obtain the configuration change status. Starting from the actual requirements of cloud support instance configuration management in the cloud support platform scenario, this application solves the problem that it is difficult to manage the configuration manually due to the large number and rapid changes of instance component types and deployment forms. Through the refined management of the cloud support component configuration collection standard, it realizes the improvement of the efficiency of obtaining cloud support component configurations in a multi-cloud scenario while ensuring the accuracy of configuration data, avoiding the problems of serious time consumption and poor accuracy in the manual method, and being able to save a lot of manpower and material resources.

[0058] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagram may represent a module, a program segment, or a part of code that contains one or more executable instructions for implementing the specified logical function. It should also be noted that, in some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, as well as the combination of blocks in the block diagram and / or flowchart, can be implemented by a dedicated hardware-based system for performing the specified functions or operations, or by a combination of dedicated hardware and computer instructions.

[0059] Although the operations are depicted in a particular order, this should not be construed as requiring that the operations be performed in the particular order shown or in sequential order. In certain circumstances, multitasking and parallel processing may be advantageous.

[0060] It should be understood that the various steps recited in the method embodiments of the present disclosure may be executed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this regard.

[0061] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages or combinations thereof. The above-mentioned programming languages include, but are not limited to, object-oriented programming languages such as Java, Smalltalk, C++, and also include conventional procedural programming languages such as the C language or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, executed as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer.

[0062] Figure 3 It is a block diagram of a configuration management device for an instance of a cloud support component according to an embodiment of the present application.

[0063] As Figure 3 shown, the configuration management device provided in this embodiment is applied to an electronic device and is used to perform configuration management on instances of cloud support components in a cloud computing system. The electronic device can be understood as a computer, a server, and the cloud platform itself with computing capabilities. The configuration management device specifically includes an information collection module 10 and a management execution module 20.

[0064] The information collection module is used to collect the component static configuration information of all cloud support component instances.

[0065] Through the user's input or an automated collection method, static information records of each cloud support component instance in the cloud computing system are collected, or in other words, component static configuration information. The component static configuration information in this application includes, but is not limited to, global configuration information, physical configuration information, and software configuration information. Among them, the global configuration information includes region, deployment instance, availability zone, etc.; the physical configuration information includes IP address, instance form, etc.; the software configuration information includes component category, the cluster to which the component belongs, etc. Specifically, it is shown in the following table:

[0066]

[0067]

[0068] By collecting the above information, on the one hand, static information records of cloud support component instances are made, and all component instances are managed from different dimensions according to information such as deployment instance, component category, and cluster. On the other hand, the IP and component category configuration information collected can also be used as input parameters for obtaining component dynamic configuration information in subsequent configurations.

[0069] The management execution module is used to identify the configuration change status based on the collected static configuration information of components.

[0070] That is, based on the already collected static configuration information of components and the dynamic configuration information of all cloud support component instances, identification processing is performed to obtain the configuration change status of all cloud support component instances. This management execution module includes an information collection unit 21, an information integration unit 22, and a comparison processing unit 23, as Figure 4 shown.

[0071] The information collection unit is used to regularly collect the dynamic configuration information of components according to the static configuration information of components.

[0072] That is, the collected static configuration information of components is used as the input parameter for collecting the static configuration information of all cloud support component instances. Based on this input parameter, a corresponding configuration acquisition interface is designed, and then the dynamic configuration information of components is regularly collected based on this interface. The dynamic configuration information of components specifically includes the following contents:

[0073] 1. The non-fixed role configuration information of cloud support component instances, such as the roles of each zookeeper component node, etc.;

[0074] 2. The dynamic configuration information of cloud support component instances, such as the label information of container cluster Node nodes, etc.;

[0075] 3. The support component information for dynamic deployment, such as the container name, deployment node, IP node, running version, etc. in the container configuration items of the container cluster.

[0076] The information integration unit is used to perform integration processing on the static configuration information of components and the dynamic configuration information of components.

[0077] For the above-obtained static configuration information of components and the regularly collected dynamic configuration information of components, data integration processing is performed according to the component type and stored in each component data table respectively. The data table information can be displayed through a page, and a search function for filtering data according to attributes such as cloud instances and IPs is designed.

[0078] The comparison processing unit is used to perform comparison processing on the dynamically configured information of components collected each time.

[0079] By comparing the dynamically configured information of components collected each time, the differences between the dynamically configured information of components for multiple cloud support component instances in each previous time can be obtained, that is, the configuration change status. Among them, the configuration change status includes instance object differences and instance configuration differences.

[0080] The instance object difference refers to the difference in the number of instance objects obtained by comparing the data collected twice, and displays the instance objects marked as increased or decreased; the strength configuration difference refers to the configuration differences of the common instance objects in the data obtained by comparing the data collected twice, and displays the data before and after the different configurations marked. Among them, the instance objects with fixed deployment use the IP information as the unique identifier, and the instance objects with dynamic deployment use the name information as the unique identifier.

[0081] As can be seen from the above technical solution, this embodiment provides a configuration management device for cloud support component instances, which is applied to an electronic device, specifically for collecting the component static configuration information of all cloud support component instances; performing identification processing based on the component static configuration information and the component dynamic configuration information of all cloud support component instances to obtain the configuration change status. Starting from the actual requirements of cloud support instance configuration management in the cloud support platform scenario, this application solves the problem that it is difficult to manage the configuration manually due to the large number and fast changes of instance component types and deployment forms in the instance configuration management work. Through the refined management of the cloud support component configuration collection standard, it realizes improving the efficiency of obtaining cloud support component configurations in a multi-cloud scenario while ensuring the accuracy of configuration data, avoiding the problems of serious time consumption and poor accuracy in the manual method, and being able to save a lot of manpower and material resources.

[0082] The units involved in the embodiments described in the present disclosure can be implemented in software or in hardware. Among them, the name of the unit does not constitute a limitation to the unit itself in some cases. For example, the first acquisition unit can also be described as "the unit for acquiring at least two Internet protocol addresses".

[0083] The functions described above in this article can be at least partially performed by one or more hardware logic components. For example, without limitation, the exemplary types of hardware logic components that can be used include: Field Programmable Gate Array (FPGA), Application Specific Integrated Circuit (ASIC), Application Specific Standard Product (ASSP), System on Chip (SOC), Complex Programmable Logic Device (CPLD), and so on.

[0084] Figure 5 It is a block diagram of an electronic device according to an embodiment of the present application.

[0085] Such as Figure 5As shown, it shows a schematic structural diagram of an electronic device suitable for implementing the electronic device in the embodiments of the present disclosure. The terminal device in the embodiments of the present disclosure may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Tablet Computers), PMPs (Portable Multimedia Players), in-vehicle terminals (such as in-vehicle navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. This electronic device is merely an example and should not impose any limitations on the functions and usage scope of the embodiments of the present disclosure.

[0086] The electronic device may include a processing device (such as a central processing unit, a graphics processing unit, etc.) 501, which may perform various appropriate actions and processes according to a program stored in the read-only memory ROM 502 or a program loaded from the input device 506 into the random access memory RAM 503. In the RAM, various programs and data required for the operation of the electronic device are also stored. The processing device, the ROM, and the RAM are connected to each other through a bus 504. The input / output (I / O) interface 505 is also connected to the bus 504.

[0087] Generally, the following devices may be connected to the I / O interface: input devices including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 507 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 508 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 509. The communication device 509 may allow the electronic device to communicate with other devices wirelessly or wirelessly to exchange data. Although the figure shows an electronic device having various devices, it should be understood that it is not required to implement or have all the shown devices. Instead, more or fewer devices may be implemented or had.

[0088] This application also provides an embodiment of a computer-readable storage medium.

[0089] The above computer-readable storage medium is applied to an electronic device and carries one or more computer programs. When the one or more computer programs are executed by the electronic device, the electronic device collects the component static configuration information of all cloud support component instances; performs identification processing based on the component static configuration information and the component dynamic configuration information of all cloud support component instances to obtain the configuration change status. Starting from the actual requirements of cloud support instance configuration management in the cloud support platform scenario, this application solves the problem that it is difficult to manage the configuration manually due to the large number and fast changes of instance component types and deployment forms in the instance configuration management work. Through the refined management of the cloud support component configuration collection standard, while improving the efficiency of obtaining the cloud support component configuration in a multi-cloud scenario, it ensures the accuracy of the configuration data, avoids the problems of serious time consumption and poor accuracy in the manual method, and can save a lot of manpower and material resources.

[0090] It should be noted that the computer-readable medium in the present disclosure can be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of the computer-readable storage medium can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0091] In the present disclosure, the computer-readable storage medium can be any tangible medium that contains or stores a program, and the program can be used by or in conjunction with an instruction execution system, apparatus, or device. In the present disclosure, the computer-readable signal medium can include a data signal propagated in a baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer-readable signal medium can also be any computer-readable medium other than the computer-readable storage medium, and the computer-readable signal medium can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted by any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0092] The embodiments in this specification are all described in a progressive manner. Each embodiment focuses on the differences from other embodiments. For the same or similar parts among the embodiments, reference can be made to each other.

[0093] Although the preferred embodiments of the embodiments of the present invention have been described, those skilled in the art can make additional changes and modifications to these embodiments once they know the basic creative concept. Therefore, the appended claims are intended to be construed as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present invention.

[0094] Finally, it should also be noted that in this text, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or terminal device comprising a series of elements not only includes those elements, but also includes other elements not expressly listed, or also includes elements inherent to such process, method, article or terminal device. Without further limitation, an element defined by the statement "comprising an..." does not exclude the presence of additional identical elements in the process, method, article or terminal device comprising the element.

[0095] The technical solutions provided by the present invention have been introduced in detail above. Specific examples are used in this article to elaborate on the principles and implementation manners of the present invention. The description of the above embodiments is only used to help understand the method and its core idea of the present invention; at the same time, for those of ordinary skill in the art, according to the idea of the present invention, there will be changes in the specific implementation manners and application scopes. In summary, the content of this specification should not be construed as a limitation to the present invention.

Claims

1. A configuration management method for cloud support component instances, which is applied to an electronic device, and is characterized in that, The described configuration management method includes the steps of: Collecting the component static configuration information of all cloud support component instances; Performing identification processing based on the component static configuration information and the component dynamic configuration information of all cloud support component instances to obtain the configuration change status.

2. The configuration management method according to claim 1, wherein: The component static configuration information includes global configuration information, physical configuration information, and software configuration information.

3. The configuration management method according to claim 1, characterized in that The performing identification processing based on the component static configuration information and the component dynamic configuration information of all cloud support component instances to obtain the configuration change status includes the steps of: Collecting the component dynamic configuration information according to the static configuration information; Performing integration processing on the component dynamic configuration information collected regularly; Performing comparison processing on the component dynamic configuration information collected in previous times after integration processing to obtain the configuration change status.

4. The configuration management method according to claim 3, wherein, The component dynamic configuration information includes non-fixed role configuration information, dynamic configuration information, and support component information.

5. The configuration management method according to claim 3, wherein: The configuration change status includes instance object differences and instance configuration differences.

6. A configuration management device for a cloud-supported component instance, applied to an electronic device, characterized in that: The described configuration management device includes: An information collection module configured to collect the component static configuration information of all cloud support component instances; A management execution module configured to perform identification processing based on the component static configuration information and the component dynamic configuration information of all cloud support component instances to obtain the configuration change status.

7. The configuration management device according to claim 6, wherein: The management execution module includes: An information collection unit configured to collect the component dynamic configuration information according to the static configuration information; An information integration unit configured to perform integration processing on the component dynamic configuration information collected regularly; A comparison processing unit configured to perform comparison processing on the component dynamic configuration information collected in previous times after integration processing to obtain the configuration change status.

8. The configuration management device according to claim 6 or 7, characterized in that, The component static configuration information includes global configuration information, physical configuration information, and software configuration information; The component dynamic configuration information includes non-fixed role configuration information, dynamic configuration information, and support component information; The configuration change status includes instance object differences and instance configuration differences.

9. An electronic device, characterized in that: The described electronic device includes at least one processor and a memory connected to the processor, wherein: The memory is used to store computer programs or instructions; The processor is used to execute the computer programs or instructions so that the electronic device implements the configuration management method according to any one of claims 1 to 5.

10. A computer-readable storage medium, applied to an electronic device, characterized in that, The storage medium carries one or more computer programs, and the one or more computer programs can be executed by the electronic device, so that the electronic device can implement the configuration management method according to any one of claims 1 to 5.

Images