Cloud network management system, cloud network change method, device, medium, and product

Abstract

Embodiments of the present application provide a cloud network management system, a cloud network change method, equipment, a medium and a product. For a device in the cloud network as a change object, the workflow engine in the system can verify the compliance of the change execution logic corresponding to the change type of the change object according to the change policy corresponding to the change type. For the compliant change execution logic, the management controller in the system can further verify whether the change execution logic meets the execution condition set according to the running state of the cloud network. Finally, the change of the change object is realized by executing the change execution logic that meets the execution condition. In the above process, the workflow engine verifies the compliance of the change execution logic, which can ensure the safety of the change process; the execution condition set in real time according to the running state of the cloud network can improve the flexibility of the object change time, such as avoiding the period not suitable for change, thereby improving the success rate of change.

Description

Technical Field

[0001] This application relates to the field of network technology, and in particular to a cloud network management system, a cloud network modification method, a medium, and a product. Background Technology

[0002] Cloud networks can be divided into three logical layers: the underlying physical network (underlay), the virtual network (overlay), and the user plane. The virtual network provides the network capabilities necessary for deploying cloud services within the cloud network. A large number of devices are typically deployed in different logical layers of the cloud network to ensure the normal operation of cloud services. The user plane serves as the interface exposed to users, allowing them to access cloud services.

[0003] In practice, devices at different logical layers of a cloud network often undergo numerous and frequent changes. These changes support the evolution of the cloud network and the iterative upgrades of cloud services. And, understandably, the success rate of device changes directly impacts the performance of cloud services, and even the performance of the entire cloud network.

[0004] Therefore, improving the success rate of device changes in cloud networks has become an urgent problem to be solved. Summary of the Invention

[0005] In view of this, embodiments of this application provide a cloud network management system, a cloud network change method, a device, a medium, and a product to improve the success rate of device changes in a cloud network.

[0006] This application provides a cloud network management system, including: a workflow engine and a management controller; The workflow engine is used to obtain a change policy corresponding to the change type of the object being changed; obtain change execution logic corresponding to the change type, wherein the object being changed includes devices in the cloud network; and verify the compliance of the change execution logic according to the change policy. The management controller is used to verify whether the change execution logic meets the execution conditions set according to the cloud network operation status if the change execution logic is compliant, so as to change the object by executing the change execution logic when the execution conditions are met. The compliant change execution logic is used to implement the change steps included in the change strategy.

[0007] This application provides a cloud network modification method, applied to a cloud network management system, the method comprising: Obtain the change policy corresponding to the change type of the object being changed, and the change execution logic corresponding to the change type, wherein the object being changed includes devices in the cloud network; The compliance of the change execution logic is verified according to the change strategy. The compliant change execution logic is used to implement the change steps included in the change strategy. If the change execution logic is compliant, then verify whether the change execution logic meets the execution conditions set according to the cloud network operating status; If the change execution logic meets the execution conditions, the change execution logic is executed to modify the object to be modified.

[0008] This application provides a cloud network management system, including: a workflow engine and a performance monitoring engine; The workflow engine is used to obtain a change policy corresponding to the change type of the object being changed; obtain change execution logic corresponding to the change type, wherein the object being changed includes devices in the cloud network; verify the compliance of the change execution logic according to the change policy, wherein the compliant change execution logic is used to implement the change steps included in the change policy; The performance monitoring engine is used to monitor the network performance metrics of the cloud network during the execution of the compliant change execution logic, wherein the network performance metrics are used to determine whether to retain or revoke the changes to the change object.

[0009] This application provides a cloud network modification method, applied to a cloud network management system, the method comprising: Obtain the change policy corresponding to the change type of the object being changed, and the change execution logic corresponding to the change type, wherein the object being changed includes devices in the cloud network; The compliance of the change execution logic is verified according to the change strategy. The compliant change execution logic is used to implement the change steps included in the change strategy. Execute the compliant change execution logic to modify the object to be changed; During the execution of the change execution logic, the network performance indicators of the cloud network are monitored to determine whether to retain or revoke the changes to the object based on the network performance indicators.

[0010] This application provides a cloud network management system, including: a management controller and a performance monitoring engine; The management controller is used to obtain change execution logic corresponding to the change type of the object being changed, the object being changed including devices in the cloud network; and to verify whether the change execution logic meets the execution conditions set according to the cloud network operating status, so as to change the object being changed by executing the change execution logic when the execution conditions are met. The performance monitoring engine is used to monitor the network performance metrics of the cloud network during the execution of the change execution logic that meets the execution conditions, wherein the network performance metrics are used to determine whether to retain or revoke the changes to the change object.

[0011] This application provides a cloud network modification method, applied to a cloud network management system, the method comprising: Obtain the change execution logic corresponding to the change type of the changed object, wherein the changed object includes devices in the cloud network; Verify whether the change execution logic meets the execution conditions set according to the cloud network operating status; Execute the change execution logic that meets the execution conditions, and modify the object to be modified; During the execution of the change execution logic, the network performance indicators of the cloud network are monitored to determine whether to retain or revoke the changes to the object of the change based on the network performance indicators.

[0012] This application provides an electronic device including a processor and a memory. The memory stores one or more computer instructions, which, when executed by the processor, implement the cloud network modification method described above. The electronic device may also include a communication interface for communicating with other devices or communication networks.

[0013] This application provides a non-transitory machine-readable storage medium storing executable code. When the executable code is executed by a processor of an electronic device, the processor can at least implement the cloud network change method described above.

[0014] This application provides a computer program product, which includes a computer program or instructions. When the computer program or instructions are executed by a processor, the processor is able to implement the cloud network change method described above.

[0015] The cloud network management system provided in this application embodiment may include a workflow engine and a management controller. The system's operation can be as follows: the workflow engine verifies the compliance of the change execution logic corresponding to the change type of the object being changed, based on the change policy. The object being changed may include devices in the cloud network, and compliant change execution logic is used to implement the change steps included in the change policy. For compliant change execution logic, the management controller can further verify whether the change execution logic meets the execution conditions set according to the cloud network's operating status. Finally, by executing the change execution logic that meets the execution conditions, the change to the object can be achieved.

[0016] In the above process, on the one hand, the workflow engine verifies the compliance of the change execution logic, ensuring the safety of the object change process in the cloud network, thereby improving the success rate of object changes. On the other hand, the execution conditions can be set in real time and flexibly according to the cloud network's operating status. This includes factors such as the cloud network's operational status, the presence of any sudden emergencies, or changes to different devices within the cloud network. Compared to following a fixed change schedule, this solution offers greater flexibility in object change timing, avoiding unsuitable periods for changes, thus further improving the success rate of object changes. Attached Figure Description

[0017] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings: Figure 1 This application provides a schematic diagram illustrating the relationship between different logical layers in a cloud network. Figure 2 This is a schematic diagram of the structure of a cloud network management system provided in an embodiment of this application; Figure 3 This is a schematic diagram of another cloud network management system provided in an embodiment of this application; Figure 4 This is a schematic diagram of the structure of another cloud network management system provided in an embodiment of this application; Figure 5 This is a schematic diagram of the structure of another cloud network management system provided in an embodiment of this application; Figure 6 A signaling diagram illustrating the working process of a cloud network management system provided in this application embodiment; Figure 7 A flowchart illustrating a cloud network modification method provided in this application embodiment; Figure 8 This is a schematic diagram of the structure of another cloud network management system provided in an embodiment of this application; Figure 9 This is a schematic diagram of the structure of another cloud network management system provided in an embodiment of this application; Figure 10 A flowchart illustrating another cloud network modification method provided in this application embodiment; Figure 11 This is a schematic diagram of the structure of another cloud network management system provided in an embodiment of this application; Figure 12 A flowchart illustrating yet another cloud network modification method provided in this application embodiment; Figure 13This is an application diagram of a cloud computing environment provided in an embodiment of this application; Figure 14 This application provides a schematic diagram of the structure of an electronic device. Detailed Implementation

[0018] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0019] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the application. The singular forms “a,” “said,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms, unless the context clearly indicates otherwise. “Multiple” generally includes at least two, but does not exclude the inclusion of at least one.

[0020] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0021] Depending on the context, the words “if” or “suppose” as used here can be interpreted as “when” or “in response to determination” or “in response to identification.” Similarly, depending on the context, the phrases “if determination” or “if identification (of the condition or event of the statement)” can be interpreted as “when determination” or “in response to determination” or “when identification (of the condition or event of the statement)” or “in response to identification (of the condition or event of the statement).”

[0022] It should be noted that, in the cases involving user interaction operations or triggering operations in the embodiments of this application, the user interaction operations or triggering operations involved in the embodiments of this application include, but are not limited to, various interaction operations such as touch operations, gesture operations, voice operations, head movement operations, and eye movement operations; among them, touch operations include, but are not limited to, click operations, double click operations, long press operations, swipe operations, pinch operations, or mouse hover operations. Swipe operations include, but are not limited to, straight line swipes and curved line swipes.

[0023] It should be noted that, in the case of user information involved in the embodiments of this application, the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in the embodiments of this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0024] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a product or system comprising a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a product or system. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the product or system that includes said element.

[0025] Before describing the various embodiments provided in this application in detail, the relevant concepts involved in the various embodiments of this application may also be introduced.

[0026] Cloud networking refers to a set of network capabilities and services provided by cloud service providers to users for connecting to and managing resources in the cloud. Cloud networks can be used to store, process, and distribute data, as well as provide cloud services such as computing services, storage services, and database services. As introduced in the background section, cloud networks can be divided into the following logical layers: the underlying physical network, the virtual network, and the user plane. The relationship between the underlying physical network, the virtual network, and the user plane can also be combined... Figure 1 understand.

[0027] Furthermore, various messages generated during cloud service usage, such as control messages, data messages, and log messages, can be transmitted at different logical layers within the cloud network. For example, data messages generated by a user terminal using cloud services can be transmitted sequentially through the user plane to the virtual network and then to the underlying physical network; conversely, data messages generated by a server providing cloud services can be transmitted sequentially through the underlying physical network to the virtual network and then to the user plane. Control messages can also be transmitted bidirectionally between the underlying physical network and the virtual network.

[0028] The underlying physical network: the actual network infrastructure in a cloud network, composed of physical network devices. Physical network devices can include, for example, switches, routers, fiber optic cables, etc.

[0029] Virtual network: A virtual logical network built on top of a physical network using tunneling technology. Virtual networks can be composed of virtual network devices. Examples of virtual network devices include virtual switches (vSwitch), virtual routers (vRouter), virtual gateways (vGW), and virtual network elements obtained through Network Functions Virtualization (NFV). These virtual network devices are used to provide cloud services within cloud networks.

[0030] User plane: This is equivalent to the interface exposed to users in the cloud network. User terminals can use this interface to access and use various cloud services provided by the cloud network.

[0031] Based on the above, some embodiments of this application can be described in detail below with reference to the accompanying drawings. Where there is no conflict between the embodiments, the following embodiments and features can be combined with each other. Furthermore, the timing of the steps in the following method embodiments is merely an example and not a strict limitation.

[0032] Figure 2 This is a schematic diagram of a cloud network management structure provided in an embodiment of this application. Figure 2 As shown, the system may include a workflow engine and a management controller with communication connections.

[0033] In the first phase, the workflow engine can obtain the change policy corresponding to the change type of the object being changed, as well as the change execution logic corresponding to the change type. Then, the workflow engine can verify the compliance of the change execution logic based on the change policy. Optionally, the compliance of the change execution logic can reflect whether executing the change execution logic will reduce the operational stability of the cloud network. Operational stability can be reflected by indicators such as the cloud network's packet loss rate, latency, and jitter frequency.

[0034] The object of change can be any physical or virtual device within the cloud network that is subject to modification. As described in the above concepts and background section, for a cloud network divided into an underlying physical network, a virtual network, and a user plane, physical or virtual devices at different logical layers can be modified. Therefore, the object of change mentioned in the embodiments of this application can be any device at any logical layer of the cloud network. Optionally, in practice, common objects of change can be various devices in the virtual network.

[0035] The types of changes to the object can include version upgrades, migrations, configuration updates, scaling up or down, etc., and these various types of changes can be applied to different scenarios such as version upgrades, migrations, and fault recovery of cloud services.

[0036] Optionally, the change strategy can be a declarative file, such as a YAML file, which records the change process and may include multiple change steps. However, this file does not record the specific implementation methods of the change steps, that is, it does not record the specific logic for implementing the change. For example, when the change type is a version upgrade, the change strategy can record the change steps required to implement the version upgrade, such as the pre-check step, the execute step, and the post-check step. The pre-check step is used to check the feasibility of the upgrade, and the post-check step is used to check whether the upgrade is successful and the stability of the new version. Corresponding to the change strategy, the change execution logic can describe the specific way to implement the change. Therefore, the change execution logic can be the specific implementation method of the change strategy, and the change execution logic can also be in file form. It can be seen that the introduction of the change strategy in this embodiment achieves the decoupling of change steps and change logic.

[0037] Furthermore, similar to how the change process recorded in the change strategy can be broken down into multiple change steps, the change execution logic can also be broken down into multiple execution logic fragments. Therefore, in the first stage described above, the workflow engine's verification process for the change strategy can be described as follows: if the execution logic fragments contained in the change execution logic correspond to the change steps contained in the change strategy, it indicates that the functions achievable by different execution logic fragments in the change execution logic are the same as the change steps in the change strategy. That is, the execution logic fragments in the change execution logic can be specific implementations of the change steps in the change strategy, and thus the change execution logic is compliant; otherwise, the change execution logic is non-compliant.

[0038] Optionally, for non-compliant change execution logic, the workflow engine can generate a notification message and send it to the management controller in the system. The management controller can receive and respond to the notification message to control the change execution logic to stop executing, that is, not to modify the object being changed.

[0039] For compliant change execution logic, the process can proceed to the second stage: the management controller can further verify whether the change execution logic meets the execution conditions. Meeting the execution conditions indicates that the change is currently within the permitted time window.

[0040] The execution conditions can be set based on the cloud network's operational status. Optionally, the cloud network's operational status can reflect the real-time operational status of the cloud network, or it can reflect whether a sudden external event has occurred in the cloud network. For example, the cloud network's operational status can include whether there is a sudden emergency event in the cloud network, such as a network shutdown event. In response to this event, the cloud network management system can also receive a global change pause signal. The cloud network's operational status can also include the change status of different devices in the cloud network, such as whether other objects are currently being changed, and the current object can only be changed after the changes of other objects are completed. For example, you need to change the Virtual Private Cloud (VPC) first, and then change the vSwitch in the VPC.

[0041] Finally, for change execution rules that meet the execution conditions, the process can proceed to the third stage: executing the change execution logic to implement the change to the object. Optionally, if the change execution logic succeeds, meaning the change to the object is completed, the change can be retained. Alternatively, if the change execution logic fails, the change to the object can be revoked, meaning the object is rolled back to its state before the change logic was executed.

[0042] In this embodiment, the workflow engine can implement a change policy corresponding to the change type of the object being changed, and verify the compliance of the change execution logic corresponding to the change type. For compliant change execution logic, the management controller can further verify whether the change execution logic meets the execution conditions. Finally, the change to the object is implemented by executing the change execution logic that meets the execution conditions.

[0043] In the above process, on the one hand, the workflow engine verifies the compliance of the change execution logic, ensuring the safety of the object change process in the cloud network, thereby improving the success rate of object changes. On the other hand, the execution conditions can be set in real time and flexibly according to the operating status of the cloud network. Compared with following a fixed change schedule, the timing of object changes in this solution is more flexible and can avoid unsuitable periods for changes, thus improving the success rate of object changes.

[0044] Furthermore, the technical effects achieved by the systems and methods provided in the various embodiments of this application can also be understood in conjunction with the following: First, the change steps included in the change strategies in the various embodiments of this application describe a compliant change process that will not reduce the stability of cloud network operation. Therefore, the workflow engine verifies the change execution logic according to the change strategy, which can improve the problem of reduced cloud network operation stability due to the lack of change steps.

[0045] Secondly, change policies can be manually written, and in practice, it is more common for change policies to record change execution logic. This means that for each change to each object, corresponding change execution logic needs to be written, which greatly increases the pressure of manual writing and also leads to a surge in the number of files that record change execution logic, thereby increasing the file storage pressure on the cloud network management system.

[0046] In the embodiments of this application, although the change strategy can also be written manually, since the change strategy contains change steps but does not record the specific execution logic of the change steps, only one change strategy needs to be written for the same change type of the same change object, thereby reducing the writing pressure and the number of files that record the change strategy, thus reducing the file storage pressure of the cloud network management system.

[0047] For example, if vSwitch is upgraded from version 1.0 to 2.0, and then from 2.0 to 3.0, it would require manually writing and storing the change policies for each of the three versions, thus increasing the workload of writing and storing the necessary files. However, with the system provided in the embodiments of this application, since the aforementioned multiple changes are essentially vSwitch version upgrades, only one change policy for implementing vSwitch version upgrades needs to be manually written, thereby reducing the workload of writing and storing the necessary files.

[0048] for Figure 2 The first stage mentioned in the illustrated embodiment will be described in detail below, detailing the process by which the workflow engine obtains change policies and change execution logic.

[0049] Figure 3 This is a schematic diagram of another cloud network management system provided in an embodiment of this application. Figure 2 Based on the system shown, such as Figure 3 As shown, the system may also include a policy database and a change execution component. The policy database can store change policies corresponding to different change types of different change objects; that is, the policy database stores multiple change policies, and one change policy in the policy database can correspond to a type of change for a particular change object. Simultaneously, the change execution component can also store change execution logic corresponding to different change types of different change objects; one change execution logic can correspond to a type of change for a particular change object.

[0050] Optionally, the workflow engine can retrieve the change strategy corresponding to the change type from the strategy database and the change execution logic corresponding to the change type from the change execution component, based on the change type of the change object.

[0051] Optionally, such as Figure 3 As shown, the change execution component can also be configured with an interface and a logic database. The specific change execution logic corresponding to different change types of different change objects can be stored in the logic database of the change execution component. More specifically, for obtaining the change execution logic, after the workflow engine obtains the change object and its change type, it can use this interface to call the change execution component. Responding to the workflow engine's call, the change execution component can query the logic database for the change execution logic corresponding to the change type of the change object and send this logic to the workflow engine for compliance verification.

[0052] As described above, the change strategy and change execution logic are based on the type of the change object. Therefore, to obtain the change object and change type, optionally, they can be parsed from the user-submitted change plan file. As for parsing the change plan file, alternatively, the change plan file can be directly submitted by the user to the management controller, which will then parse the file and send the parsed change object and change type to the workflow engine, as... Figure 3 The solid line flow in the illustrated embodiment is shown. Alternatively, the change plan document can also be directly submitted to the workflow engine, which can then directly parse out the change object and change type, as shown... Figure 3 The dashed flow diagram in the illustrated embodiment is shown.

[0053] Optionally, such as Figure 3 As shown, the cloud network management system may also include a configuration management database (CMDB), which stores the configuration and identity information of different devices in the cloud network. Therefore, for any of the above parsing methods, the object to be changed can be queried in the CMDB based on the change plan document.

[0054] In this embodiment, a CMDB (Configuration Management Database) is introduced into the cloud network management system, enabling the workflow engine to accurately identify which objects in the cloud network require modification. A logical database and a policy database are also introduced, allowing the workflow engine to accurately obtain the change policy and execution logic corresponding to the change type of the object. The execution change component introduced into the cloud network management system can be used to implement object changes. Therefore, the different components introduced in this embodiment can ensure the success rate of changes from different perspectives.

[0055] for Figure 2 The second stage mentioned in the illustrated embodiment will be described in detail below, which is the process by which the management controller verifies the execution conditions.

[0056] Optionally, the execution conditions may include static gating conditions and / or dynamic gating conditions that describe the operational status of the cloud network. Static gating conditions can reflect changes to different types of objects in the cloud network; for example, static gating conditions may include whether the prerequisite tasks for the changed object have been completed.

[0057] For example, if the object to be changed is a vSwitch within a VPC, then its prerequisite dependency task could be changing the VPC itself. If the object to be changed is a primary device, then its prerequisite dependency task could be changing the backup device. Furthermore, if the object to be changed is located in a test region for a cloud service, then its prerequisite dependency task could be changing devices in a non-test region.

[0058] Dynamic gating conditions can reflect the real-time operating status of the cloud network or whether sudden external events have occurred in the cloud network. For example, dynamic gating conditions may include whether there are any change suspension signals in the cloud network due to network blocking events, or whether the network performance indicators of the cloud network meet preset indicator values.

[0059] The management controller can then verify whether the change execution logic meets the aforementioned execution conditions. If the change execution logic meets the full-department control condition, indicating that the current time window for allowing changes is in effect, a first control instruction can be generated. Upon sensing the generation of this first control instruction, the change execution component can utilize the compliant change execution logic to modify the object. Optionally, the management controller can directly send the first control instruction to the change execution component, allowing the component to execute the change execution logic and thus modify the object.

[0060] In this embodiment, the management controller uses gating conditions to verify whether the time window for executing change execution logic has been reached. Since the gating conditions are set in real-time and flexibly based on the cloud network's operating status, the timing of object changes in this embodiment is more flexible compared to following a fixed change schedule. This avoids unsuitable periods for changes, thus improving the success rate of object changes. Furthermore, using gating conditions does not consume excessive computing power from the cloud network management system, and the verification time is short, allowing for faster entry into the process. Figure 2 The second stage in the illustrated embodiment can improve the efficiency of object modification. Furthermore, the above-described gating conditions are merely illustrative; the embodiments of this application do not limit the specific content of the gating conditions. The gating conditions can also be set according to the characteristics of the actual modified object, thus improving the applicability of the systems and methods provided in the embodiments of this application.

[0061] for Figure 2 The third stage mentioned in the illustrated embodiment can be further described in detail below, which involves using change execution logic to modify the object.

[0062] exist Figure 3 Based on the illustrated embodiment, Figure 4 This is a schematic diagram of the structure of another cloud network management system provided in the embodiments of this application.

[0063] After implementing changes to the object using change execution logic, it is easy to understand that the following two situations may occur: one is that if the change execution logic is executed successfully, the change is retained; the other is that if the change execution logic fails, the change to the object is revoked.

[0064] Optionally, such as Figure 4 As shown, the change execution component can include multiple sub-components. Change objects in the cloud network can include different types, such as vSwitch, vRouter, vGW, NFV, etc., so each sub-component in the change execution component can correspond to one type of change object.

[0065] For the change objects mentioned in the above embodiments, if the type of the change object corresponds to a target sub-component in the change execution component, then the target sub-component can respond to the call of the workflow engine, retrieve the change execution logic corresponding to the change type of the change object from the logical database, and send the change execution logic to the workflow engine. After passing the compliance and execution condition verification, the target sub-component can also use the change execution logic retrieved from the logical database to implement the change of the change object.

[0066] In this embodiment, the change execution component can be divided into multiple sub-components according to the different types of change objects in the cloud network. Each sub-component is used to implement the change of a certain type of change object. This ensures that the failure of one sub-component will not affect the normal operation of other sub-components, thereby improving the availability of the change execution component and the success rate of object changes.

[0067] Optionally, such as Figure 4 As shown, the change execution component in this system can also be configured with an authorization interface, and the system can also include an execution platform. The change execution component can serve as a channel connecting the workflow engine and the execution platform, thereby enabling changes to the change object.

[0068] Specifically, as Figure 3 As described in the illustrated embodiment, after the workflow engine verifies that the change execution logic is compliant, and the management controller also verifies that the change execution logic meets the execution conditions, the management controller can generate a first control instruction. Subsequently, the management controller can also send this first control instruction to the workflow engine to instruct the workflow engine to begin making changes to the object being changed.

[0069] Upon receiving the first control instruction, the workflow engine can further send an authorization instruction to the change execution component. The change execution component, after receiving the authorization instruction via the authorization interface, can then generate a second control instruction. Unlike the first control instruction, which serves as an indication, this second control instruction is the actual control instruction used to implement the change execution logic. This second control instruction can also be sent by the change execution component to the execution platform, which can execute it to modify the object being changed. In other words, the execution platform is the main entity in the cloud network management system that truly executes the change execution logic. The execution platform can output execution results reflecting the success or failure of the change execution logic. This execution result can be transmitted from the execution platform to the management controller via the change execution component and the workflow engine, allowing the management controller to also understand the change status of various devices in the cloud network in real time.

[0070] It is easy to understand that, for the multiple sub-components contained in the change execution component, the process of receiving the authorization instruction and generating and sending the second control instruction can be specifically executed by the target sub-component corresponding to the type of the change object.

[0071] Similar to changing the execution component, such as Figure 4 As shown, the execution platform can also include multiple sub-platforms, each corresponding to a type of change object. Therefore, the aforementioned second control instruction can also be specifically defined by the type to which the change object belongs (e.g., Figure 4The third type (in the text) corresponds to the target sub-platform execution, meaning that the change execution logic is actually executed by the target sub-platform. Optionally, when making changes to a type of change object, at least one sub-platform can be used, meaning that the number of target sub-platforms can be at least one.

[0072] It should be noted here that, Figure 4 Although four types of change objects are shown in the document, and the target sub-platform corresponds to the third type of change object, this is only an illustration. This application does not limit the number of change object types in the cloud network, nor does it limit the correspondence between the sub-platform and the change object types.

[0073] For sub-platforms, optionally, they can take different forms, such as servers, container orchestration tools, databases, etc. Therefore, server-based sub-platforms can be used when implementing changes to vSwitch, vRouter, vGW, and other similar change objects. Container orchestration tools, such as Kubernetes, can be used when implementing changes to NFV-type change objects. Database-based sub-platforms can also be used when implementing changes to vSwitch, vRouter, vGW, and NFV-type change objects.

[0074] In this embodiment, the settings for the acquisition interface in the change execution component enable the workflow engine to obtain the change execution logic in the first stage of object change; the settings for the authorization interface in the change execution component enable the change execution component to receive authorization instructions in the third stage of object change, and further authorize the execution platform to execute the change execution logic. In other words, the interface settings enable interaction and collaboration between the workflow engine, the change execution component, and the execution platform, allowing the workflow engine to successfully change objects even without knowing the details of the change execution logic. On the other hand, introducing the change execution component and execution platform on top of the workflow engine decouples the verification and execution processes of the change execution logic, effectively offloading the workflow engine's execution function for the change execution logic and reducing the management pressure on the cloud network.

[0075] Figure 5 This is a schematic diagram illustrating the structure of another cloud network management system provided in an embodiment of this application. In the above... Figures 2-4 Based on any of the illustrated embodiments, such as Figure 5 As shown, the system may also include a performance monitoring engine.

[0076] The execution of change logic can be performed as described in the above embodiments. During the execution of change logic on the changed object, the performance monitoring engine monitors the network performance indicators of the cloud network to obtain monitoring results. More specifically, the performance monitoring engine can monitor the network performance indicators of the changed object and other devices in the cloud network that have a network connection relationship with the changed object and a dependency relationship with the changed object. Furthermore, the aforementioned changed object and other devices can be used to provide the same type of cloud service in the cloud network. Optionally, the performance monitoring engine can determine whether the performance of the cloud network and / or the cloud service in the cloud network meets preset indicator values ​​during the execution of the change logic based on the monitored network performance indicators. If the preset indicator values ​​are not met, a monitoring result reflecting performance degradation is output; if the preset indicator values ​​are met, a monitoring result reflecting stable performance is output. Optionally, network performance indicators can include network bandwidth, network latency, packet loss rate, jitter, etc. Furthermore, the cloud service provided by the aforementioned changed object and other devices can be the same service as the cloud service for which network performance monitoring is performed, and the performance monitoring engine can also feed back the monitoring results to the management controller.

[0077] In one scenario, if the monitoring results indicate that the network performance metrics meet the preset values, the changes to the object can be retained. In another scenario, if the monitoring results received by the management controller indicate that the network performance metrics do not meet the preset values, suggesting a performance degradation in the cloud network and / or cloud services during the execution of the change logic, the change type of the object can be referenced to determine whether this performance degradation is normal and expected, ultimately deciding whether to retain or revert the changes to the object.

[0078] For example, if the change type is a migration, it is normal and expected that cloud service performance will decrease during the execution of the change logic. In this case, it is advisable to retain the changes to the object being changed. If the change type is a version upgrade, it is abnormal for cloud service performance to decrease during the execution of the change logic to complete the upgrade. In this case, it is advisable to revoke the retention of the changes to the object being changed, that is, to roll back the object to its state before the change.

[0079] In this embodiment, the introduction of a performance monitoring engine enables the monitoring of the effects of changes. Based on the monitoring results, it can be determined whether to retain the changes to the object. If the changes cannot be retained, the management controller can promptly roll back the changed object to ensure the performance of the cloud network and / or cloud services.

[0080] Furthermore, the working process of the cloud network management system provided in the above embodiments can also be combined with Figure 6 The signaling diagram shown is for comprehension.

[0081] In real-world cloud networks, there may be situations where a large number of identical objects undergo the same type of change. These numerous changes of the same type targeting the same object can constitute a change task, and optionally, this change task can be parsed by the management controller from a user-submitted change plan file. For the parsed change task, the management controller can further break it down into multiple subtasks, each of which can be considered a batch. The cloud network management system can then execute one subtask at a time, following the methods provided in the above embodiments.

[0082] For splitting change tasks, one option is for the management controller to use a preset algorithm to split the change tasks. The splitting result can be represented as a Directed Acyclic Graph (DAG), where each node in the DAG represents a subtask. Another option is for the management controller to use task execution time and task execution risk as constraints, and solve the problem using a mathematical model to split the change tasks. Task execution risk indicates the likelihood that the network performance of the cloud network and / or the performance of cloud services within the cloud network will degrade after executing the task.

[0083] After task decomposition, assume the management controller can split the change task into multiple subtasks, each containing a first subtask and a second subtask. The change object and its change type mentioned in the above embodiments can be included in the first subtask, and the second subtask needs to be executed after the first subtask. Based on this assumption, the management controller can send the first subtask to the workflow engine. Upon receiving the first subtask, the workflow engine can verify the compliance of the change execution logic according to the change policy corresponding to the change type of the change object. After successful compliance verification, the management controller can also verify whether the compliant change execution logic meets the execution conditions. If the change execution logic meets the non-execution conditions, the first subtask will not be executed, and the management controller will not send the second subtask from the change task to the workflow engine. If the change execution logic meets the execution conditions, it can be executed through the collaborative work between the workflow engine, the change execution component, and the execution platform.

[0084] Optionally, during the execution of the change execution logic, the performance monitoring engine can monitor the network performance of the cloud network and / or cloud services to obtain monitoring results that can reflect whether the performance of the cloud network and / or cloud services has degraded.

[0085] If network performance metrics fail to meet preset values ​​during the execution of the change execution logic, resulting in performance degradation, it indicates that modifying the object in the first subtask will affect the performance of the cloud network and / or cloud services. In other words, executing the first subtask can reduce the operational stability of the cloud network. Therefore, the management controller can pause the entire change task, i.e., stop sending the second subtask after the first subtask to the workflow engine. Simultaneously, the management controller can also determine whether to retain or revert the changes to the object in the first subtask.

[0086] If the network performance metrics meet the preset values ​​during the execution of the change execution logic, thus obtaining a monitoring result reflecting that the performance remains unchanged, it indicates that changing the object in the first subtask will not affect the performance of the cloud network and / or cloud services. That is, executing the first subtask will not reduce the operational stability of the cloud network. Then, the management controller can continue to send the second subtask to the workflow engine until all subtasks in the change task are completed.

[0087] Optionally, after executing the change execution logic, the workflow engine can also generate and send the execution result to the management controller. This execution result reflects whether the change execution logic was executed successfully, i.e., whether the change to the object was successfully modified after execution. If the change execution logic fails, it indicates that executing the logic cannot complete the modification of the object, and executing the first subtask may reduce the operational stability of the cloud network. In this case, the management controller can revert the modification to the object in the first subtask and stop sending the second subtask to the workflow engine. If the change execution logic succeeds, it indicates that the object has been successfully modified after execution, and executing the first subtask will not reduce the operational stability of the cloud network. In this case, the management controller can continue sending the second subtask to the workflow engine.

[0088] For example, a change task could include making changes to 1 million vSwitch instances in VPCs across different regions. The management controller could then split the vSwitch instances deployed in the test region into subtask 1, and the vSwitch instances deployed in non-test regions into subtask 2.

[0089] If the execution results generated by the workflow engine reflect that the change execution logic failed, and / or the monitoring results generated by the performance monitoring engine reflect a performance degradation, it indicates that executing subtask 1 can reduce the operational stability of the cloud network and / or cloud services. In this case, subtask 2 will not be executed. Therefore, operational stability can be guaranteed during the change to the cloud network and / or cloud services.

[0090] In this embodiment, splitting the change task enables batch changes to a large number of objects, thereby improving the change speed and reducing the workload of the cloud network management system. Furthermore, during the batch change process, the monitoring results generated by the performance monitoring engine and / or the execution results generated by the workflow engine can be used to monitor in real time whether the changes in the current batch will reduce the operational stability of the cloud network and / or cloud services. If operational stability decreases, subsequent batches of changes can be stopped, thus controlling the impact of object changes on the performance of the cloud network and / or cloud services to a minimum.

[0091] In addition, any content not described in detail in this embodiment can be found in the descriptions of the relevant embodiments above, and will not be repeated here.

[0092] Based on the above Figures 2-5 The above embodiments provide an introduction to the structure and working process of the cloud network management system. The working process of the cloud network management system provided in the above embodiments can also be described from a process perspective.

[0093] Figure 7 This is a flowchart illustrating a cloud network modification method provided in an embodiment of this application. This method can be derived from the methods described above in this application. Figures 2-5 The cloud network management system provided in the illustrated embodiment is referred to as the management system in this embodiment and subsequent method embodiments. Figure 7 As shown, the method may include the following steps: S101, obtain the change policy corresponding to the change type of the object being changed, and the change execution logic corresponding to the change type. The object being changed includes devices in the cloud network.

[0094] S102, Verify the compliance of the change execution logic according to the change policy. The compliant change execution logic is used to implement the change steps included in the change policy.

[0095] S103, If the change to the execution logic is compliant, then verify whether the change to the execution logic meets the execution conditions set according to the cloud network operating status.

[0096] S104. If the change execution logic meets the execution conditions, execute the change execution logic to modify the object.

[0097] The management system can obtain the change policy and change execution logic corresponding to the change type of the object being changed. Then, it verifies whether the change execution logic is compliant and meets the execution conditions. For compliant change execution logic that meets the execution conditions, the management system can execute the logic to change the object being changed.

[0098] For a detailed description of the object of change, the type of change, the change strategy, and the change execution logic, please refer to [link to relevant documentation]. Figure 2 For the relevant descriptions in the illustrated embodiments, and for the verification process regarding whether the changed execution logic is compliant and whether the execution conditions are met, please refer to [link / reference needed]. Figure 2 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0099] In addition, although the method provided in this embodiment can be executed by the management system, more specifically, steps S101 and S102 in this embodiment can be executed by the workflow engine in the management system, step S103 can be executed by the management controller in the management system, and step S104 can be executed collaboratively by the change execution component and the execution platform in the system.

[0100] In this embodiment, the management system can implement a change policy corresponding to the change type of the object being changed, and verify the compliance of the change execution logic corresponding to the change type. For compliant change execution logic, it can further verify whether the change execution logic meets the execution conditions set according to the cloud network operating status. Finally, by executing the change execution logic that meets the execution conditions, the change to the object can be achieved.

[0101] In the above process, on the one hand, verifying the compliance of the change execution logic ensures the security of the object change process in the cloud network, thereby improving the success rate of object changes. On the other hand, the execution conditions can be set in real time and flexibly according to the operating status of the cloud network. Compared with following a fixed change schedule, the timing of object changes in this solution is more flexible and can avoid unsuitable periods for changes, thus improving the success rate of object changes.

[0102] Optionally, in order to improve the speed of changes and reduce the workload of the cloud network management system, the management system can also split the change tasks submitted by users into multiple sub-tasks. In this case, the change object and the change type of the change object mentioned in step S101 can be included in the first sub-task, which can be obtained by the management system after dividing the change task.

[0103] Optionally, during the execution of the change execution logic, the management system can also monitor the network performance indicators of the cloud network and / or cloud services in real time, and obtain monitoring results by determining whether the monitored performance indicators meet preset indicator values. Optionally, after the execution of the change execution logic, the workflow engine can also monitor whether the change execution logic was executed successfully to obtain execution results. Based on the monitoring results and / or execution results obtained by itself, the management system can determine whether the execution of the first subtask will reduce the operational stability of the cloud network and / or cloud services, and thus determine whether to continue executing the second subtask in the change task. Optionally, the above-mentioned network performance indicator monitoring process can be specifically implemented by the performance monitoring engine in the management system. Therefore, task splitting can also control the impact of object changes on the performance of the cloud network and / or cloud services to a smaller range.

[0104] Optionally, even without splitting the change task, the performance monitoring engine can monitor the network performance of the cloud network and / or cloud services during the execution of the change execution logic corresponding to the change task. This allows the engine to determine whether the execution of the change execution logic will degrade the operational stability of the cloud network and / or cloud services, i.e., whether the changes to the object should be retained. If the changes cannot be retained, the management system can promptly roll back the changed object to ensure the performance of the cloud network and / or cloud services.

[0105] Furthermore, for details not described in this embodiment and the technical effects that can be achieved, please refer to the above. Figures 2-6 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0106] Figure 8 This is a schematic diagram of the structure of another cloud network management system provided in an embodiment of this application. For example... Figure 8 As shown, the system may include a workflow engine and a performance monitoring engine.

[0107] The workflow engine can obtain the change policy corresponding to the change type of the object being changed, and also the change execution logic corresponding to the change type. The object being changed can be a physical or virtual device used to provide cloud services within the cloud network. The workflow engine can then verify the compliance of the change execution logic based on the change policy. For compliant change execution logic, it can be used to implement the changes to the object being changed. Furthermore, during the execution of the change execution logic to change the object, the performance monitoring engine can monitor the network performance metrics of the cloud network and / or cloud services, and output monitoring results based on whether the monitored network performance metrics meet preset metric values. These monitoring results are used to determine whether to retain or revert the changes to the object being changed.

[0108] The methods by which the workflow engine obtains the changed object, the changed type, and the changed strategy can be found in the description of the relevant embodiments above, and will not be repeated here.

[0109] In this embodiment, the workflow engine verifies the compliance of the change execution logic, ensuring the safety of the change process and thus improving the success rate of the change. On the other hand, the introduction of the performance monitoring engine enables the monitoring of the change's effects, determining whether to retain the changes to the object based on the monitoring results. If the change cannot be retained, it can be rolled back promptly to ensure the performance of the cloud network and / or cloud services.

[0110] Figure 9 This is a schematic diagram illustrating the structure of yet another cloud network management system provided in an embodiment of this application. Figure 8 Based on the system shown, optionally, as Figure 9 As shown, the system may also include a change execution component, which may be equipped with an acquisition interface and a logical database. The change execution logic corresponding to different change types of different change objects may be stored in the logical database.

[0111] After obtaining the object to be changed and its change type, the workflow engine can use this interface to invoke the change execution component. Responding to the workflow engine's call, the change execution component can query the logic from the logical database corresponding to the change type of the object and send this logic to the workflow engine for compliance verification. For compliant change execution logic, the management system can use it to modify the object.

[0112] The methods by which the workflow engine obtains the changed object, the changed type, and the changed strategy can be found in the description of the relevant embodiments above, and will not be repeated here.

[0113] Optionally, such as Figure 9 As shown, the change execution component can also be configured with an authorization interface, and the system can also include an execution platform.

[0114] After verifying the compliance of the change execution logic, the workflow engine can generate and send an authorization instruction to the change execution component. The change execution component can respond to the received authorization instruction and use this change execution logic to modify the object. More specifically, optionally, in response to the received authorization instruction, the change execution component can generate and send a control instruction to the execution platform, so that the execution platform can specifically execute this control instruction, thereby realizing the modification of the object. The control instruction generated by the change execution component here is... Figure 4 The second control command in the illustrated embodiment.

[0115] In this embodiment, the settings for the acquisition interface in the change execution component enable the workflow engine to obtain the change execution logic; the settings for the authorization interface in the change execution component enable the change execution component to receive authorization instructions and further authorize the execution platform to execute the change execution logic. In other words, the interface settings enable interaction and collaborative work between the workflow engine, the change execution component, and the execution platform, allowing the workflow engine to successfully change objects even without knowing the details of the change execution logic. On the other hand, introducing the change execution component and execution platform on top of the workflow engine decouples the verification and execution processes of the change execution logic, effectively offloading the workflow engine's execution function for the change execution logic and reducing the management pressure on the cloud network.

[0116] Furthermore, the contents not described in detail in this embodiment and the technical effects that can be achieved can be found in the relevant descriptions in the above embodiments, and will not be repeated here.

[0117] Large-scale changes can also occur in cloud networks. These large-scale changes can form a change task, which can optionally be broken down into multiple sub-tasks. Figure 8 or Figure 9 The change object and change type mentioned in the illustrated embodiment can be included in the first subtask of multiple subtasks, and the multiple subtasks can also include a second subtask executed after the first subtask.

[0118] The workflow engine can then acquire these multiple subtasks and send the first subtask to the change execution component. After receiving the first subtask, the change execution component can modify the object in the first subtask according to the methods provided in the above embodiments. If the first subtask executes successfully—that is, the object in the first subtask is successfully modified and the modification does not cause a performance degradation of the cloud network and / or cloud services—the change execution component can also modify the object in the second subtask according to the methods provided in the above embodiments. If the first subtask fails—that is, the object in the first subtask fails to be modified or the modification would cause a performance degradation of the cloud network and / or cloud services—the workflow engine can stop sending the second subtask to the change execution component. At this point, the entire change task will stop executing.

[0119] In this embodiment, splitting the change task allows for batch changes to a large number of objects, thereby improving the change speed and reducing the workload of the cloud network management system. Furthermore, during the batch change process, it is possible to determine in real time whether the execution of the current sub-task will reduce the operational stability of the cloud network and / or cloud services. If operational stability decreases, the execution of subsequent sub-tasks can be stopped, thus controlling the impact of object changes on the performance of the cloud network and / or cloud services to a minimum.

[0120] in addition, Figure 8 or Figure 9 The working processes of different components in the management system shown can also be found in the relevant descriptions in the above embodiments, and will not be repeated here.

[0121] Figure 10 A flowchart illustrating another cloud network modification method provided in this application embodiment. This method can be derived from this application. Figure 8 or Figure 9 The management system provided in the illustrated embodiment is executed. For example... Figure 10 As shown, the method may include the following steps: S201, Obtain the change policy corresponding to the change type of the object being changed, and the change execution logic corresponding to the change type. The object being changed includes devices in the cloud network.

[0122] S202, Verify the compliance of the change execution logic according to the change policy. The compliant change execution logic is used to implement the change steps included in the change policy.

[0123] S203, execute compliant change execution logic to make changes to the object being changed.

[0124] S204. During the execution of the change execution logic, monitor the network performance indicators of the cloud network to determine whether to retain or revoke the changes to the object of the change based on the network performance indicators.

[0125] The management system can obtain change policies corresponding to the change types of the objects being changed, and also obtain change execution logic corresponding to the change types. The objects being changed can be physical or virtual devices used to provide cloud services within the cloud network. The management system can then verify the compliance of the change execution logic based on the change policies. For compliant change execution logic, it can be used to implement changes to the objects being changed. Furthermore, during the execution of the change execution logic to change the objects, the management system can also monitor network performance metrics of the cloud network and / or cloud services, and determine whether to retain or revoke the changes to the objects based on whether the monitored network performance metrics meet preset values.

[0126] In this embodiment, verifying the compliance of the change execution logic ensures the safety of the change process for the changed object, thereby improving the success rate of the change. On the other hand, the management system can monitor the effect of the change and determine whether to retain the changes to the changed object based on the monitoring results. If the change cannot be retained, the changed object can be rolled back in a timely manner to ensure the performance of the cloud network and / or cloud services.

[0127] Furthermore, for details not described in this embodiment and the technical effects that can be achieved, please refer to the above. Figures 1-4 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0128] Figure 11 This is a schematic diagram of the structure of another cloud network management system provided in an embodiment of this application. For example... Figure 11 As shown, the system may include a management controller and a performance monitoring engine.

[0129] The management controller can obtain the change execution logic corresponding to the change type of the object being changed, and verify whether the change execution logic meets the execution conditions set according to the cloud network's operating status. The object being changed can be a physical or virtual device used to provide cloud services within the cloud network. If the execution conditions are met, the change object can be modified by executing the change execution logic.

[0130] Furthermore, during the process of modifying the object, the performance monitoring engine can also monitor network performance metrics of the cloud network and / or cloud services, and output monitoring results based on the monitored network performance metrics. The management controller can determine whether to retain or revoke the changes to the object based on the monitoring results output by the performance monitoring engine.

[0131] In this embodiment, the management controller verifies the execution conditions. Since these conditions can be set flexibly and in real-time according to the cloud network's operational status, the timing of object changes is more flexible compared to following a fixed change schedule. This avoids unsuitable periods for changes, thus improving the success rate of object changes. Furthermore, the introduction of a performance monitoring engine allows for monitoring the effects of changes. Based on the monitoring results, it can be determined whether to retain the changes to the object. If the changes cannot be retained, the management controller can promptly roll back the changed object to ensure the performance of the cloud network and / or cloud services.

[0132] Optionally, large-scale changes may occur in the cloud network. These large-scale changes can form a change task, which the management controller can parse from the user-submitted change plan file. The management controller can then break down the change task into multiple subtasks, which may include a first subtask and a second subtask executed after the first subtask. Figure 11 The change objects and change types mentioned in the illustrated embodiments can be included in the first subtask.

[0133] If the change execution logic of the first subtask fails, it indicates that the object to be changed in the first subtask was not successfully changed. In this case, the management controller can either revert the changes to the object in the first subtask or stop verifying whether the change execution logic of the second subtask meets the execution conditions. In this situation, the entire change task will also stop executing.

[0134] If, during the execution of the change execution logic for the first subtask, the network performance metrics of the cloud network and / or cloud services fail to meet preset values, indicating that changing the object in the first subtask would reduce the operational stability of the cloud network and / or cloud services, the management controller can decide to retain or revoke the changes to the object in the first subtask, or stop verifying whether the change execution logic for the second subtask meets the execution conditions. In this case, the entire change task will also stop executing.

[0135] In this embodiment, splitting the change task allows for batch changes to a large number of objects, thereby improving the change speed and reducing the workload of the cloud network management system. Furthermore, during the batch change process, it is possible to determine in real time whether the execution of the current sub-task will reduce the operational stability of the cloud network and / or cloud services. If operational stability decreases, the execution of subsequent sub-tasks can be stopped, thus controlling the impact of object changes on the performance of the cloud network and / or cloud services to a minimum.

[0136] Optionally, the management platform may also include change execution components and execution platform.

[0137] The coordinated operation of the management controller, change execution component, and execution platform enables the modification of the object to be modified. Specifically, for change execution logic that meets the execution conditions, the change execution component can generate control instructions describing this change execution logic and send these control instructions to the execution platform. The execution platform can then execute the control instructions to modify the object to be modified. These control instructions are... Figure 4 The second control command in the illustrated embodiment.

[0138] In addition, the contents not described in detail in this embodiment and Figure 11 The working processes of different components in the management system shown can also be found in the relevant descriptions in the above embodiments, and will not be repeated here.

[0139] Figure 12 A flowchart illustrating another cloud network modification method provided in this application embodiment. This method can be derived from the methods described above in this application. Figure 11 The management system provided in the illustrated embodiment is executed. For example... Figure 12 As shown, the method may include the following steps: S301, obtain the change execution logic corresponding to the change type of the changed object, which includes devices in the cloud network.

[0140] S302, Verify whether the change execution logic meets the execution conditions set according to the cloud network operating status.

[0141] S303, execute the change execution logic if the execution conditions are met, and make changes to the object to be changed.

[0142] S304: During the execution of the change execution logic, monitor the network performance indicators of the cloud network to determine whether to retain or revoke the changes to the object of the change based on the network performance indicators.

[0143] The management system can obtain the change execution logic corresponding to the change type of the object being changed, and verify whether the change execution logic meets the execution conditions set according to the cloud network's operating status. The object being changed can be a physical or virtual device used to provide cloud services within the cloud network. If the execution conditions are met, the change execution logic can be executed to modify the object. Furthermore, during the modification process, the management system can monitor the network performance metrics of the cloud network and / or cloud services, and determine whether to retain or revert the changes to the object based on the monitoring results.

[0144] In this embodiment, since the execution conditions can be set flexibly and in real time according to the operating status of the cloud network, the timing of object changes is more flexible compared to following a fixed change schedule. This avoids unsuitable periods for changes and thus improves the success rate of object changes. On the other hand, the management system can monitor the effects of changes and determine whether to retain the changes to the object based on the monitoring results. If the changes cannot be retained, the management controller can promptly roll back the changed object to ensure the performance of the cloud network and / or cloud services.

[0145] Furthermore, any content not described in detail in this embodiment, as well as the technical effects that can be achieved, can be found in the relevant descriptions of the above embodiments, and will not be repeated here.

[0146] It should be noted that, although the executing entity of each step is specified in the description of the steps provided in the above embodiments, this application does not limit the steps in the above method embodiments to the same device. That is, each step in the method embodiment can be executed by the same device, or the method can be executed by different devices. For example, the execution subject of steps S101 to S103 can be device A; or the execution subject of steps S101 and S102 can be device A, and the execution subject of step S103 can be device B; and so on.

[0147] Furthermore, in some of the processes described in the above embodiments and accompanying drawings, multiple operations appear in a specific order. However, it should be clearly understood that these operations may not be executed in the order they appear in this document, or they may be executed in parallel. The operation numbers, such as S101, S102, etc., are merely used to distinguish different operations and do not represent any execution order. Additionally, these processes may include more or fewer operations, and these operations may be executed sequentially or in parallel. It should be noted that the descriptions such as "first" and "second" in this document are used to distinguish different messages, devices, modules, etc., and do not represent a sequential order, nor do they limit "first" and "second" to different types.

[0148] The cloud network management system provided in the above embodiments of this application can be deployed on server-side devices in a cloud computing environment. Users can trigger tasks to the server-side devices in the system via client devices. Optionally, the server-side devices can be cloud servers maintained by cloud service providers—referred to as nodes. Client devices can be laptops, tablets, PCs, robots, etc.

[0149] In such Figure 13 The cloud computing environment shown may include several distributed deployments. Figure 13 The diagram illustrates compute nodes (201-1, 201-2, ...), and cache nodes. Each node can possess processing resources such as computing and storage. In a cloud computing environment, multiple nodes can be organized to provide a certain service, such as the cloud services mentioned in the embodiments of this application, including computing services, storage services, and database services. Of course, a single node can also provide one or more services, such as... Figure 13 The diagram illustrates services A, B, C, and D. In a cloud computing environment, services can be provided through external service interfaces, which client devices can call to use the corresponding services. Service interfaces include Software Development Kits (SDKs) and Application Programming Interfaces (APIs), among others.

[0150] The services described above are deployed using various virtualization technologies supported by cloud computing environments, such as virtual machine-based and container-based virtualization technologies. Taking container-based virtualization technology as an example, several containers corresponding to a service can be assembled into a container group (pod). For example... Figure 13 The illustrated service B can be configured with one or more pods, and each pod can include a proxy and one or more containers. The one or more containers in the pod are used to handle requests related to one or more corresponding functions of the service, and the proxy in the pod is used to control network functions related to the service, such as routing and load balancing.

[0151] During operation, executing requests from client devices may require invoking one or more services in the cloud computing environment, and executing one or more functions of one service may require invoking one or more functions of another service. For example... Figure 13 As shown, after receiving a request from a client device, service A can call service B, and service B can request service D to perform one or more functions.

[0152] In one possible design, the cloud network management system provided in the above embodiments can also be applied to an electronic device. For example... Figure 14 As shown, the electronic device may include a processor 21 and a memory 22. The memory 22 stores programs that support the electronic device in performing various operations that the aforementioned cloud network management system can perform. Figure 7 or Figure 10 or Figure 12 The cloud network modification method provided in the illustrated embodiment includes a program in which the processor 21 is configured to execute a program stored in the memory 22. The program includes one or more computer instructions, wherein the one or more computer instructions, when executed by the processor 21, can achieve the following: Figure 7 or Figure 10 or Figure 12 The steps provided in the illustrated embodiment.

[0153] The structure of the electronic device may also include other components such as a communication component 23, a display 24, a power supply component 25, and an audio component 26.

[0154] Figure 14 The diagram only shows some components and does not mean that the electronic device includes only these components. Figure 14 The components shown.

[0155] in addition, Figure 14The components mentioned are optional, not mandatory, and depend on the specific product form of the electronic device. The electronic device in this application embodiment can be a conventional server, cloud server, or server array, etc.

[0156] The processor 21 can be any hardware processing device capable of executing the above-described method logic. Optionally, the processor can be a CPU, a graphics processing unit (GPU), or a microcontroller unit (MCU); it can also be a field-programmable gate array (FPGA), a programmable array logic (PAL), a general array logic (GAL), a complex programmable logic device (CPLD), or other programmable devices; or it can be an advanced RISC machine (ARM) or a system on chip (SoC), etc., but is not limited to these.

[0157] The aforementioned memory 22 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random-Access Memory (SRAM), Electrically Erasable Programmable Read Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0158] The aforementioned communication component 23 is configured to facilitate wired or wireless communication between the device containing the communication component and other devices. The device containing the communication component can access wireless networks based on communication standards, such as Wi-Fi, 2G (e.g., Global System for Mobile Communications (GSM)), 3G (e.g., Wideband Code Division Multiple Access (WCDMA), 4G (e.g., Long Term Evolution (LTE)), 4G+ (e.g., LTE-Advanced (LTE-A)), or 5G (5th Generation Mobile Communication Technology), or combinations thereof. In one exemplary embodiment, the communication component receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component also includes a Near Field Communication (NFC) module to facilitate short-range communication. For example, the NFC module may be based on Radio Frequency Identification (RFID), Infrared Data Association (IRDA) technology, Ultra Wide Band (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0159] The aforementioned display 24 includes a screen, which may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a Touch Panel, the screen can be implemented as a touchscreen to receive input signals from the user. The Touch Panel includes one or more touch sensors to sense touches, swipes, and gestures on the Touch Panel. The touch sensors can sense not only the boundaries of touch or swipe actions but also the duration and pressure associated with the touch or swipe operation.

[0160] The aforementioned power supply component 25 provides power to various components of the device in which it resides. The power supply component may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device in which it resides.

[0161] The audio component 26 described above can be configured to output and / or input audio signals. For example, the audio component includes a microphone (MIC) configured to receive external audio signals when the device containing the audio component is in an operating mode, such as call mode, recording mode, or voice recognition mode. The received audio signals can be further stored in memory or transmitted via a communication component. In some embodiments, the audio component also includes a speaker for outputting audio signals.

[0162] Accordingly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, enables the processor to implement the steps in the above-described method embodiments. The computer-readable storage medium includes volatile or non-volatile or a combination thereof, and can be removable or non-removable. Examples of computer-readable storage media include, but are not limited to, phase-change random access memory (PRAM), SRAM, dynamic random access memory (DRAM), other types of random-access memory (RAM), ROM, EEPROM, EPROM, PROM, flash memory or other memory technologies, CD-ROM, Digital Video Disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium.

[0163] Accordingly, this application also provides a computer program product, which includes a computer program or instructions. When the computer program or instructions are executed by a processor, the processor is able to implement the steps in the above method embodiments. These computer programs or instructions can be applied to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device, so that the processor of the general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing device can be implemented as a means to implement the corresponding functions in the above method embodiments.

[0164] Furthermore, the specific implementation form of the computer program product is not limited in the embodiments of this application. In some embodiments, the computer program product may be implemented as an application (APP), a mini-program, a PC client, a program module, a plug-in, an installation package, a software development kit (SDK), an image file of an optical disc (such as an ISO file), a plug-in, or software in the form of Software as a Service (SaaS), etc., but is not limited to these.

[0165] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A cloud network management system, characterized in that, include: Workflow engine and management controller; The workflow engine is used to obtain the change strategy corresponding to the change type of the object being changed; Obtain the change execution logic corresponding to the change type, wherein the change object includes devices in the cloud network; Verify the compliance of the change execution logic according to the change policy; The management controller is used to verify whether the change execution logic meets the execution conditions set according to the cloud network operation status if the change execution logic is compliant, so as to change the object by executing the change execution logic when the execution conditions are met. The compliant change execution logic is used to implement the change steps included in the change strategy.

2. The system according to claim 1, characterized in that, The workflow engine is used to generate a notification message if the change execution logic is non-compliant. The management controller is used to receive the notification message and, based on the notification message, control the change execution logic to stop executing.

3. The system according to claim 1, characterized in that, The system also includes a policy database; The workflow engine is used to obtain the change type of the change object parsed from the change plan file submitted by the user; Retrieve the change policy corresponding to the change type of the object from the policy database.

4. The system according to claim 1, characterized in that, The system also includes a change execution component, which is equipped with an acquisition interface and a logical database; The workflow engine is used to invoke the change execution component using the acquisition interface; The logical database is used to store the change execution logic corresponding to the different change types of the different change objects; The change execution component is used to respond to the call of the workflow engine and retrieve the change execution logic corresponding to the change type of the change object from the logical database; Send the change execution logic to the workflow engine; The change object is modified using the compliant change execution logic.

5. The system according to claim 4, characterized in that, The change execution component includes multiple sub-components, and the target sub-component among the multiple sub-components corresponds to the type of the change object; The target sub-component is used to respond to the call of the workflow engine and obtain the change execution logic corresponding to the type of the change object from the logical database.

6. The system according to claim 4, characterized in that, The management controller is configured to generate a first control instruction if it verifies that the change execution logic meets the execution conditions, wherein the execution conditions include static gating conditions and / or dynamic gating conditions describing the operating state of the cloud network. The change execution component is used to modify the change object in response to the generation of the first control instruction, using the compliant change execution logic.

7. The system according to claim 6, characterized in that, The change execution component is also equipped with an authorization interface; The management controller is used to send the first control command to the workflow engine; The workflow engine is configured to send an authorization instruction to the change execution component in response to receiving the first control instruction; The change execution component is used to receive the authorization instruction using the authorization interface; In response to the receipt of the authorization instruction, the object to be modified is modified using the compliant change execution logic.

8. The system according to claim 7, characterized in that, The system also includes an execution platform; The change execution component is used to generate a second control instruction describing the change execution logic in response to receiving the authorization instruction; Send the second control command to the execution platform; The execution platform is used to execute the second control instruction to modify the object to be modified.

9. The system according to claim 8, characterized in that, The execution platform includes multiple sub-platforms, and the target sub-platform among the multiple sub-platforms corresponds to the type of the object being changed. The target sub-platform is used to execute the second control command to modify the object to be modified.

10. The system according to any one of claims 1 to 9, characterized in that, The management controller is used to receive change plan files submitted by users; parse the change plan files to obtain change tasks; The change task is broken down into multiple sub-tasks; Send the first subtask of the plurality of subtasks to the workflow engine. The first subtask includes the changed object and the change type of the changed object. The workflow engine is used to respond to the receipt of the first subtask and verify the compliance of the change execution logic according to the change policy corresponding to the change type of the changed object.

11. The system according to claim 10, characterized in that, The system also includes a configuration management database; The management controller is used to query the change object in the first subtask in the configuration management database according to the change plan file.

12. The system according to claim 10, characterized in that, The workflow engine is used to determine whether the change execution logic has been executed successfully; The management controller is configured to, if the change execution logic fails, revert the changes to the object in the first subtask and stop sending the second subtask after the first subtask to the workflow engine; If the change execution logic is executed successfully, the second subtask is sent to the workflow engine.

13. The system according to claim 10, characterized in that, The system also includes a performance monitoring engine, used to monitor the network performance indicators of the cloud network during the execution of the change execution logic, so as to obtain monitoring results; The management controller is configured to retain or revoke the changes to the object in the first subtask and stop sending the second subtask after the first subtask to the workflow engine if the monitoring results indicate that the network performance indicators do not meet the preset indicator values ​​during the execution of the change execution logic. If the network performance metrics meet the preset metric values ​​during the execution of the change execution logic, then the second subtask is sent to the workflow engine.

14. A cloud network modification method, characterized in that, Applied to a cloud network management system, the method includes: Obtain the change policy corresponding to the change type of the object being changed, and the change execution logic corresponding to the change type, wherein the object being changed includes devices in the cloud network; The compliance of the change execution logic is verified according to the change strategy. The compliant change execution logic is used to implement the change steps included in the change strategy. If the change execution logic is compliant, then verify whether the change execution logic meets the execution conditions set according to the cloud network operating status; If the change execution logic meets the execution conditions, the change execution logic is executed to modify the object to be modified.

15. The method according to claim 14, characterized in that, The object to be changed and the type of change to the object to be changed are included in the first subtask, and the first subtask and the second subtask executed after the first subtask are included in the change task; Before obtaining the change strategy corresponding to the change type of the changed object, and the change execution logic corresponding to the change type, the method further includes: Receive the first subtask.

16. The method according to claim 15, characterized in that, The method further includes: Monitor the network performance metrics of the cloud network during the execution of the change execution logic; If, during the execution of the change execution logic, the network performance indicators do not meet the preset indicator values, then the changes to the object in the first subtask are retained or revoked, and the reception of the second subtask is stopped.

17. The method according to claim 15, characterized in that, The method further includes: If the change execution logic of the first subtask fails, the changes to the object in the first subtask are revoked, and the reception of the second subtask is stopped.

18. A cloud network management system, characterized in that, include: Workflow engine and performance monitoring engine; The workflow engine is used to obtain the change strategy corresponding to the change type of the object being changed; Obtain the change execution logic corresponding to the change type, wherein the change object includes devices in the cloud network; The compliance of the change execution logic is verified according to the change strategy. The compliant change execution logic is used to implement the change steps included in the change strategy. The performance monitoring engine is used to monitor the network performance metrics of the cloud network during the execution of the compliant change execution logic, wherein the network performance metrics are used to determine whether to retain or revoke the changes to the change object.

19. The system according to claim 18, characterized in that, The system also includes a change execution component, which is equipped with an acquisition interface and a logical database; The workflow engine is used to invoke the change execution component using the acquisition interface; The change execution component is used to respond to the call of the workflow engine and retrieve the change execution logic corresponding to the change type of the change object from the logical database; Send the change execution logic to the workflow engine; The change object is modified using the compliant change execution logic.

20. The system according to claim 19, characterized in that, The change execution component is also equipped with an authorization interface; The workflow engine is used to generate the authorization instruction after verifying that the change execution logic is compliant; Send the authorization instruction to the change execution component; The change execution component is used to change the object in response to the receipt of the authorization instruction, using the change execution logic.

21. The system according to claim 20, characterized in that, The system also includes an execution platform; The change execution component is used to generate a control instruction describing the change execution logic in response to receiving the authorization instruction; Send the control command to the execution platform; The execution platform is used to execute the control instructions to modify the object being modified.

22. The system according to claim 19, characterized in that, The workflow engine is used to obtain change tasks parsed from a change plan file submitted by a user, wherein the change task includes a first subtask and a second subtask executed after the first subtask, and the first subtask includes the change object and the change type of the change object; The change execution component is used to change the object in the second subtask after successfully changing the object in the first subtask using the change execution logic of the first subtask, and then to change the object in the second subtask using the change execution logic of the second subtask.

23. A cloud network management method, characterized in that, Applied to a cloud network management system, the method includes: Obtain the change policy corresponding to the change type of the object being changed, and the change execution logic corresponding to the change type, wherein the object being changed includes devices in the cloud network; The compliance of the change execution logic is verified according to the change strategy. The compliant change execution logic is used to implement the change steps included in the change strategy. Execute the compliant change execution logic to modify the object to be changed; During the execution of the change execution logic, the network performance indicators of the cloud network are monitored to determine whether to retain or revoke the changes to the object based on the network performance indicators.

24. A cloud network management system, characterized in that, The system includes: a management controller and a performance monitoring engine; The management controller is configured to acquire change execution logic corresponding to the change type of the object being changed, the object being changed including devices in the cloud network; verify whether the change execution logic meets the execution conditions set according to the cloud network operating status, so as to change the object being changed by executing the change execution logic when the execution conditions are met; and determine whether to retain or revoke the change to the object being changed based on the monitoring results output by the performance monitoring engine. The performance monitoring engine is used to monitor the network performance indicators of the cloud network during the execution of the change execution logic that meets the execution conditions, so as to output the monitoring results.

25. The system according to claim 24, characterized in that, The management controller is used to receive change plan documents submitted by users; Parse the change plan document to obtain the change tasks; The change task is divided into multiple subtasks, including a first subtask and a second subtask executed after the first subtask. The first subtask includes the object to be changed and the change type of the object to be changed. If the change execution logic fails, the changes to the object in the first subtask are revoked, and the verification of whether the change execution logic of the second subtask meets the execution conditions is stopped. If the network performance metrics do not meet the preset metric values ​​during the execution of the change execution logic, then it is determined to retain or revoke the changes to the object in the first subtask, and the verification of whether the change execution logic of the second subtask meets the execution conditions is stopped.

26. The system according to claim 24, characterized in that, The system also includes: a change execution component and an execution platform; The change execution component is used to generate control instructions describing the change execution logic and send the control instructions to the execution platform. The execution platform is used to execute the control instructions and modify the object to be modified.

27. A cloud network modification method, characterized in that, Applied to a cloud network management system, the method includes: Obtain the change execution logic corresponding to the change type of the changed object, wherein the changed object includes devices in the cloud network; Verify whether the change execution logic meets the execution conditions set according to the cloud network operating status; Execute the change execution logic that meets the execution conditions, and modify the object to be modified; During the execution of the change execution logic, the network performance indicators of the cloud network are monitored to determine whether to retain or revoke the changes to the object of the change based on the network performance indicators.

28. An electronic device comprising: A memory and a processor; wherein the memory stores executable code, and when the executable code is executed by the processor, the processor performs the cloud network change method as described in any one of claims 14 to 17, or the cloud network change method as described in claim 23, or the cloud network change method as described in claim 27.

29. A non-transitory machine-readable storage medium, characterized in that, The non-transitory machine-readable storage medium stores executable code that, when executed by a processor of an electronic device, causes the processor to perform the cloud network change method as described in any one of claims 14 to 17, or the cloud network change method as described in claim 23, or the cloud network change method as described in claim 27.

30. A computer program product, characterized in that, The computer program product includes a computer program or instructions that enable the computer program or instructions to implement the cloud network change method of any one of claims 14 to 17, or the cloud network change method of claim 23, or the cloud network change method of claim 27.

Images