Configuration management publishing method and system

Abstract

The invention discloses a configuration management publishing method and system. The method comprises the following steps: a client sends a configuration file pulling request to a server; the server side predicts the processing duration of each client side according to the received configuration file pulling request and a to-be-released configuration file set, then divides all the client sides into a plurality of groups according to the processing duration of the client sides, distributes a corresponding configuration file pulling period for each client side group, and sends the configuration file pulling period to the server side; and finally, the configuration file pulling period is returned to the client. And the client side obtains the configuration file from the server side regularly according to the configuration file pulling period sent by the server side. The invention relates to the field of information communication, and can realize dynamic self-adaptive adjustment of configuration file pulling periods of all clients during configuration management release, thereby effectively meeting user requirements and reducing bandwidth consumption.

Description

Technical Field

[0001] The invention relates to a configuration management publishing method and system, and relates to the field of information communication. Background Art

[0002] In the configuration management and release solution of product software, the mechanism in which the client periodically and actively pulls configurations in batches from the server is widely used because of its simplicity, flexibility and lightweight.

[0003] However, with the increase in scenarios, richer requirements and more restrictions, the setting of the pull cycle is particularly important when there are many pull clients and limited network bandwidth, especially when the release of many configurations is dependent on each other. The next configuration can only be released after the previous configuration is released successfully, and there are certain requirements for the total time of configuration release. If the pull cycle is set too long, it will time out when the configuration is released and will not meet user needs; if the pull cycle is set too short, it will occupy too much bandwidth and even cause the pull request to accumulate and time out when there are many clients and limited bandwidth.

[0004] Therefore, how to achieve dynamic and adaptive adjustment of the configuration file pulling cycle of all clients when configuration management is released, so as to effectively meet user needs and reduce bandwidth consumption, has become a technical issue that technical personnel focus on. Summary of the invention

[0005] In view of this, the purpose of the present invention is to provide a configuration management publishing method and system, which can realize dynamic adaptive adjustment of the configuration file pulling cycle of all clients during configuration management publishing, thereby effectively meeting user needs and reducing bandwidth consumption.

[0006] In order to achieve the above object, the present invention provides a configuration management publishing method, comprising:

[0007] Step 1: The client sends a configuration file pull request to the server;

[0008] Step 2: The server predicts the processing time of each client based on the received configuration file pull request and the set of configuration files to be released, and then divides all clients into several groups based on the processing time of the clients, and assigns a corresponding configuration file pull cycle to each client group, and finally returns the configuration file pull cycle to the client;

[0009] Step 3: The client obtains the configuration file from the server at a fixed time according to the configuration file pulling cycle sent by the server.

[0010] In order to achieve the above object, the present invention also provides a configuration management publishing system, including a server device and multiple client devices, wherein:

[0011] The client device sends a configuration file pull request to the server device, and then obtains the configuration file from the server device at a fixed time according to the configuration file pull cycle sent by the server device;

[0012] The server device predicts the processing time of each client device based on the received configuration file pull request and the set of configuration files to be published, then divides all client devices into several groups based on the processing time of the client devices, and assigns a corresponding configuration file pull cycle to each client group, and finally returns the configuration file pull cycle to the client device.

[0013] In order to achieve the above object, the present invention further provides a computing device, comprising:

[0014] Memory and processor;

[0015] The memory is used to store computer executable instructions, and the processor is used to execute the computer executable instructions. When the computer executable instructions are executed by the processor, the steps of the configuration management publishing method are implemented.

[0016] In order to achieve the above-mentioned object, the present invention further provides a computer-readable storage medium storing computer-executable instructions, which can implement the steps of the configuration management publishing method when executed by a processor.

[0017] Compared with the prior art, the beneficial effects of the present invention are as follows: the present invention divides all clients into several groups, and sets different configuration file pulling cycles for different client groups, so that bandwidth can be used more efficiently and user needs can be met; while the server allocates a configuration file pulling cycle to each client, it can also set a first pulling delay time for each client, thereby effectively avoiding system performance degradation due to a large number of concurrencies; the client can also regularly adjust the configuration file pulling cycle according to its actual uplink bandwidth and downlink bandwidth, so as to better meet actual business needs. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 The figure is a flow chart of a configuration management publishing method shown in an exemplary embodiment of the present invention.

[0019] Figure 2 An exemplary embodiment of the present invention is shown Figure 1 In step 2, the server divides all clients into several groups according to the processing time of the clients, and allocates a specific process flow chart of the corresponding configuration file pulling cycle to each client group.

[0020] Figure 3It is a structural diagram of a configuration management and publishing system shown in an exemplary embodiment of the present invention.

[0021] Figure 4 It is a schematic diagram of the structure of a computer device according to an exemplary embodiment of the present invention. DETAILED DESCRIPTION

[0022] In order to make the objectives, technical solutions and advantages of the present invention more clear, the present invention is further described in detail below with reference to the accompanying drawings.

[0023] like Figure 1 As shown, the present invention provides a configuration management publishing method, comprising:

[0024] Step 1: The client sends a configuration file pull request to the server, wherein the configuration file pull request includes the number of client accounts;

[0025] Step 2: The server predicts the processing time of each client based on the received configuration file pull request and the set of configuration files to be released, and then divides all clients into several groups based on the processing time of the clients, and assigns a corresponding configuration file pull cycle to each client group, and finally returns the configuration file pull cycle to the client;

[0026] Step 3: The client obtains the configuration file from the server at a fixed time according to the configuration file pulling cycle sent by the server.

[0027] In step 2, the server predicts the processing time of each client, which may further include:

[0028] Step A1, according to the word length of the http request message of the configuration file pull request sent by all clients, calculate the total upstream bandwidth Tota l_UBW, the average upstream bandwidth AVE_UBW, the minimum upstream bandwidth MIN_UBW, and the maximum upstream bandwidth MAX_UBW: Tota l_UBW = SUM_DV_HTTP / unit time, AVE_UBW = Tota l_UBW / N, MIN_UBW = MIN_DV_HTTP / unit time, MAX_UBW = MAX_DV_HTTP / unit time, where SUM_DV_HTTP is the sum of the word lengths of the http request message of the configuration file pull request sent by all clients, MIN_DV_HTTP and MAX_DV_HTTP are the minimum and maximum word lengths of the http request message of the configuration file pull request sent by all clients, respectively, N is the total number of clients sending the configuration file pull request, and the unit time can be seconds;

[0029] Step A2, according to the configuration file set to be released by the server, calculate the total downstream bandwidth Tota l_DBW, the average downstream bandwidth AVE_DBW, the minimum downstream bandwidth MIN_DBW, and the maximum downstream bandwidth MAX_DBW: Tota l_DBW = SUM_DV_CONFIG / unit time, AVE_DBW = Tota l_DBW / N_config, MIN_DBW = MIN_DV_CONFIG / unit time, MAX_DBW = MAX_DV_CONFIG / unit time, where SUM_DV_CONFIG is the sum of the word lengths of all files in the configuration file set to be released by the server, MIN_DV_CONFIG and MAX_DV_CONFIG are respectively the minimum and maximum word lengths of all configuration files in the configuration file set, and N_config is the number of all configuration files in the configuration file set;

[0030] Step A3: Calculate the total bandwidth of each client: BW i =(AVE_UBW*2+AVE_DBW)*un i , where BW i 、un i are the total bandwidth and number of accounts of the i-th client respectively;

[0031] Step A4: Calculate the processing time of each client: Among them, PROC_TIME i is the processing time of the ith client, BW MAX It is the maximum bandwidth pre-set based on actual business needs.

[0032] like Figure 2 As shown, in step 2, the server divides all clients into several groups according to the processing time of the clients, and allocates a corresponding configuration file pulling cycle to each client group, which may further include:

[0033] Step B1, calculate the parallel maximum number pmn: determine whether N-1 has divisors other than 1 and itself, if so, calculate pmn: If not, calculate the largest divisor of N and N+1 except 1 and itself respectively, and then select the minimum value from the two values, which is pmn;

[0034] Step B2: sort all clients in ascending order of processing time to form a client sequence;

[0035] Step B3: extract the last client in the client sequence (i.e., the client with the longest processing time), set the configuration file pulling period of the extracted client to its processing time, and then delete the client from the client sequence;

[0036] Step B4, calculate the remaining client parallel number J: J = pmn-1, and create J empty group lists;

[0037] Step B5: write each client in the client sequence into a different group list one by one, so that the sum of the processing time of all clients in each group list is balanced, that is, all clients in the client sequence are divided into J groups, each group list corresponds to a client group, and the writing order of the clients in the group list is the arrangement order of the clients in the client group;

[0038] Step B6: Count the sum of the processing time of all clients in each group list one by one. The sum of the processing time is the configuration file pulling cycle of all clients in the group.

[0039] In step B5, writing each client in the client sequence into different grouping lists one by one may further include:

[0040] Step B51, set the pre-processing parameter before to True, the start number of the initial loop to 0, and the end number to N-2;

[0041] Step B52: determine whether before is True and start+1 is less than end. If so, extract J clients from the client sequence in order from the front to the back, and write each client extracted in order into each group list one by one, then delete the extracted client from the client sequence, set before to Fall, set start to J-1, and finally go to step B54; if not, proceed to the next step;

[0042] In step B52, in order from front to back, the client ranked at the first position extracted from the client sequence is written into the first group list, the client ranked at the second position is written into the second group list, ..., the client ranked at the Jth position is written into the Jth group list;

[0043] Step B53: determine whether before is True and start+1 is less than end. If so, extract J clients from the client sequence in order from the back to the front, and write each client extracted in order into each group list one by one, then delete the extracted clients from the client sequence, set before to True, set end to N-2-J, and finally go to step B54; if not, proceed to the next step;

[0044] In step B53, in order from the back to the front, the client ranked last in the client sequence is written into the first group list, the client ranked second to last is written into the second group list, ..., the client ranked Jth to last is written into the Jth group list;

[0045] Step B54, determine whether start+1 is greater than or equal to end. If so, the process ends; if not, go to step B52.

[0046] In step 2, the server allocates a configuration file pulling cycle to each client and can also set a first pulling delay for each client, so that different clients can obtain configuration files from the server at different times, thereby avoiding system performance degradation due to a large number of concurrency. Step 2 can also include:

[0047] According to the order of all clients in each client group, the first pull delay of the client ranked first in the client group is set to 0, and then the first pull delay of other clients in the client group is calculated one by one: Among them, Y jq PROC_TIME is the first pull delay of the client at position q in the jth client group. jf is the processing time of the client at position f in the jth client group,

[0048] Step three further includes:

[0049] When the client obtains the configuration file from the server for the first time, it waits for the first pull delay time and then obtains the configuration file from the server.

[0050] In step 3, each time the client successfully obtains the configuration file from the server, it will update the latest pull time saved locally to the current time. The client can also regularly adjust the configuration file pull cycle based on its actual uplink and downlink bandwidth, including:

[0051] Step C1: The client calculates the actual processing time according to the actual uplink bandwidth and the downlink bandwidth, and determines whether the actual processing time is within the preset interval of the configuration file pulling cycle. If yes, this process ends; if no, proceed to the next step;

[0052] For example, the 80 / 20 rule may be adopted, that is, when the actual processing time is within 20% of the current configuration file pulling cycle, the configuration file pulling cycle is not adjusted; otherwise, the configuration file pulling cycle is adjusted;

[0053] Step C2, calculate the minimum pull period st and the maximum pull period et: st = MIN_UBW*2 + MIN_DBW, et = MAX_UBW*2 + MAX_DBW;

[0054] Step C3: determine whether the latest pull time is saved locally. If not, reduce or enlarge the configuration file pull cycle, and this process ends; if yes, proceed to the next step;

[0055] Minification and enlargement profile pull cycles can be alternated;

[0056] Step C4: determine whether the time interval between the latest pull time and the current time is within the preset pull expiration time. If yes, shorten the configuration file pull cycle; if no, lengthen the configuration file pull cycle.

[0057] In steps C3 and C4, shortening the configuration file pulling cycle may further include:

[0058] Calculate the average processing time ave_t of the configuration files of all client accounts, then calculate the average value et_new of et and ave_t, and then randomly select a value from the interval [st,et_new] as the shortened configuration file pulling cycle.

[0059] In step C4, the configuration file pulling cycle is enlarged, which may further include:

[0060] Calculate the average processing time ave_t of the configuration files of all client accounts, then calculate the average value st_new of st and ave_t, and then randomly select a value from the interval [st_new,et] as the enlarged configuration file pulling cycle.

[0061] like Figure 3 As shown, the present invention provides a configuration management and publishing system, including a server device and multiple client devices, wherein:

[0062] The client device sends a configuration file pull request to the server device, wherein the configuration file pull request includes the number of accounts of the client device, and then obtains the configuration file from the server device at a regular interval according to the configuration file pull cycle sent by the server device;

[0063] The server device predicts the processing time of each client device based on the received configuration file pull request and the set of configuration files to be published, then divides all client devices into several groups based on the processing time of the client devices, and assigns a corresponding configuration file pull cycle to each client group, and finally returns the configuration file pull cycle to the client device.

[0064] See also Figure 4 , Figure 4 4 is a block diagram of a computing device 400 shown in an exemplary embodiment of this specification. The components of the computing device 400 include but are not limited to a memory 410 and a processor 420. The processor 420 is connected to the memory 410 via a bus 430, and the database 450 is used to store data.

[0065] The computing device 400 also includes an access device 440 that enables the computing device 400 to communicate via one or more networks 460. Examples of these networks include a public switched telephone network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or a combination of communication networks such as the Internet. The access device 440 may include one or more of any type of network interface (e.g., a network interface card (NIC)) of wired or wireless, such as an IEEE 802.11 wireless local area network (WLAN) wireless interface, a Worldwide Interoperability for Microwave Access (Wi-MAX) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, a Near Field Communication (NFC) interface, and the like.

[0066] In one embodiment of the present specification, the above components of the computing device 400 and Figure 4 Other components not shown in the figure may also be connected to each other, for example, via a bus. It should be understood that Figure 4 The computing device structure block diagram shown is only for the purpose of illustration, and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.

[0067] The computing device 400 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc.), a mobile phone (e.g., a smart phone), a wearable computing device (e.g., a smart watch, smart glasses, etc.), or other types of mobile devices, or a stationary computing device such as a desktop computer or a PC. The computing device 400 may also be a mobile or stationary server or a cloud server, etc.

[0068] The processor 420 is used to execute the following computer executable instructions, which, when executed by the processor, implement the steps of the above-mentioned configuration management publishing method.

[0069] The above is a schematic scheme of a computing device of this embodiment. It should be noted that the technical scheme of the computing device and the technical scheme of the configuration management publishing method are of the same concept, and the details not described in detail in the technical scheme of the computing device can be referred to the description of the technical scheme of the configuration management publishing method.

[0070] An embodiment of the present specification further provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the steps of the above-mentioned configuration management publishing method.

[0071] The above is a schematic scheme of a computer-readable storage medium of this embodiment. It should be noted that the technical scheme of the storage medium and the above configuration management publishing method belong to the same concept, and the details not described in detail in the technical scheme of the storage medium can be referred to the description of the technical scheme of the above configuration management publishing method or system.

[0072] An embodiment of the present specification also provides a computer program, wherein when the computer program is executed in a computer, the computer is caused to execute the steps of the above-mentioned configuration management publishing method.

[0073] The above is a schematic scheme of a computer program of this embodiment. It should be noted that the technical scheme of the computer program and the technical scheme of the configuration management publishing method are of the same concept, and the details not described in detail in the technical scheme of the computer program can be found in the description of the technical scheme of the configuration management publishing method or system.

[0074] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0075] The computer instructions include computer program codes, which may be in source code form, object code form, executable file or some intermediate form, etc. The computer readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc.

[0076] It should be noted that, for the above-mentioned method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the embodiments of this specification are not limited by the order of the actions described, because according to the embodiments of this specification, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the embodiments of this specification.

[0077] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A configuration management publishing method, characterized in that: Included are: Step 1: The client sends a configuration file pull request to the server; Step 2: The server predicts the processing time of each client based on the received configuration file pull request and the set of configuration files to be released, and then divides all clients into several groups based on the processing time of the clients, and assigns a corresponding configuration file pull cycle to each client group, and finally returns the configuration file pull cycle to the client; Step 3: The client obtains the configuration file from the server at a fixed time according to the configuration file pulling cycle sent by the server.

2. The method according to claim 1, characterized in that In step 2, the server predicts the processing time of each client, further including: Step A1, according to the word length of the http request message of the configuration file pull request sent by all clients, calculate the total upstream bandwidth Total_UBW, the average upstream bandwidth AVE_UBW, the minimum upstream bandwidth MIN_UBW, and the maximum upstream bandwidth MAX_UBW: Total_UBW = SUM_DV_HTTP / unit time, AVE_UBW = Total_UBW / N, MIN_UBW = MIN_DV_HTTP / unit time, MAX_UBW = MAX_DV_HTTP / unit time, where SUM_DV_HTTP is the sum of the word lengths of the http request message of the configuration file pull request sent by all clients, MIN_DV_HTTP and MAX_DV_HTTP are the minimum and maximum word lengths of the http request message of the configuration file pull request sent by all clients, respectively, N is the total number of clients sending the configuration file pull request, and the unit time is seconds; Step A2: Calculate the total downstream bandwidth Total_DBW, the average downstream bandwidth AVE_DBW, the minimum downstream bandwidth MIN_DBW, and the maximum downstream bandwidth MAX_DBW according to the configuration file set to be released by the server: Total_DBW=SUM_DV_CONFIG / unit time, AVE_DBW=Total_DBW / N_config, MIN_DBW=MIN_DV_CONFIG / unit time, MAX_DBW=MAX_DV_CONFIG / unit time, where SUM_DV_CONFIG is the sum of the word lengths of all files in the configuration file set to be released by the server, MIN_DV_CONFIG and MAX_DV_CONFIG are respectively the minimum and maximum word lengths of all configuration files in the configuration file set, and N_config is the number of all configuration files in the configuration file set; Step A3: Calculate the total bandwidth of each client: BW i =(AVE_UBW*2+AVE_DBW)*un i , where BW i 、un i are the total bandwidth and number of accounts of the i-th client respectively; Step A4: Predict the processing time of each client: Among them, PROC_TIME i is the processing time of the ith client, BW MAX It is the preset maximum bandwidth.

3. The method according to claim 1, characterized in that In step 2, the server divides all clients into several groups according to the processing time of the clients, and allocates a corresponding configuration file pulling cycle to each client group, further including: Step B1, calculate the parallel maximum number pmn: determine whether N-1 has divisors other than 1 and itself, if so, calculate pmn: If not, calculate the largest divisor of N and N+1 excluding 1 and itself respectively, and then select the minimum value from the two values, the minimum value is pmn, and N is the total number of clients that send configuration file pull requests; Step B2: sort all clients in ascending order of processing time to form a client sequence; Step B3: extract the last client in the client sequence, set the configuration file pulling period of the extracted client to its processing duration, and then delete the client from the client sequence; Step B4, calculate the remaining client parallel number J: J = pmn-1, and create J empty group lists; Step B5: write each client in the client sequence into a different group list one by one, so that the sum of the processing time of all clients in each group list is balanced, that is, all clients in the client sequence are divided into J groups, each group list corresponds to a client group, and the writing order of the clients in the group list is the arrangement order of the clients in the client group; Step B6: Count the sum of the processing time of all clients in each group list one by one. The sum of the processing time is the configuration file pulling cycle of all clients in the group.

4. The method according to claim 3, characterized in that: In step B5, each client in the client sequence is written into a different grouping list one by one, further comprising: Step B51, set the pre-processing parameter before to True, the start number of the initial cycle to 0, and the end number to N-2; Step B52: determine whether before is True and start+1 is less than end. If so, extract J clients from the client sequence in order from the front to the back, and write each client extracted in order into each group list one by one, then delete the extracted client from the client sequence, set before to False, set start to J-1, and finally go to step B54; if not, proceed to the next step; Step B53: determine whether before is False and start+1 is less than end. If so, extract J clients from the client sequence in order from the back to the front, and write each client extracted in order into each group list one by one, then delete the extracted client from the client sequence, set before to True, set end to N-2-J, and finally go to step B54; if not, proceed to the next step; Step B54, determine whether start+1 is greater than or equal to end. If so, the process ends; if not, go to step B52.

5. The method according to claim 1, characterized in that Step 2 also includes: According to the order of all clients in each client group, the first pull delay of the client ranked first in the client group is set to 0, and then the first pull delay of other clients in the client group is calculated one by one: Among them, Y jq PROC_TIME is the first pull delay of the client at position q in the jth client group. jf is the processing time of the client at position f in the jth client group, Step three further includes: When the client obtains the configuration file from the server for the first time, it waits for the first pull delay time and then obtains the configuration file from the server.

6. The method according to claim 1, characterized in that In step 3, each time the client successfully obtains the configuration file from the server, it updates the latest pull time saved locally to the current time, including: Step C1: The client calculates the actual processing time according to the actual uplink bandwidth and the downlink bandwidth, and determines whether the actual processing time is within the preset interval of the configuration file pulling cycle. If yes, this process ends; if no, proceed to the next step; Step C2, calculate the minimum pull period st and the maximum pull period et: st = MIN_UBW*2 + MIN_DBW, et = MAX_UBW*2 + MAX_DBW, where MIN_UBW and MAX_UBW are the minimum and maximum uplink bandwidths, respectively, and MIN_DBW and MAX_DBW are the minimum and maximum downlink bandwidths, respectively; Step C3: determine whether the latest pull time is saved locally. If not, reduce or enlarge the configuration file pull cycle, and this process ends; if yes, proceed to the next step; Step C4: determine whether the time interval between the latest pull time and the current time is within the preset pull expiration time. If yes, shorten the configuration file pull cycle; if no, lengthen the configuration file pull cycle.

7. The method according to claim 6, characterized in that In steps C3 and C4, shortening the configuration file pulling cycle further includes: Calculate the average processing time ave_t of the configuration files of all client accounts, then calculate the average value et_new of et and ave_t, and then randomly select a value from the interval [st,et_new] as the shortened configuration file pulling cycle. In step C4, the configuration file pulling cycle is enlarged, further comprising: Calculate the average processing time ave_t of the configuration files of all client accounts, then calculate the average value st_new of st and ave_t, and then randomly select a value from the interval [st_new,et] as the enlarged configuration file pulling cycle.

8. A configuration management and publishing system, characterized in that: It includes a server device and multiple client devices, wherein: The client device sends a configuration file pull request to the server device, and then obtains the configuration file from the server device at a fixed time according to the configuration file pull cycle sent by the server device; The server device predicts the processing time of each client device based on the received configuration file pull request and the set of configuration files to be published, then divides all client devices into several groups based on the processing time of the client devices, and assigns a corresponding configuration file pull cycle to each client group, and finally returns the configuration file pull cycle to the client device.

9. A computing device, characterized in that include: Memory and processor; The memory is used to store computer executable instructions, and the processor is used to execute the computer executable instructions. When the computer executable instructions are executed by the processor, the steps of the configuration management publishing method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium, characterized in that: It stores computer executable instructions, which, when executed by a processor, can implement the steps of the configuration management publishing method described in any one of claims 1 to 7.

Images