Method, device and storage medium for publishing and interactive scheduling based on CMP heterogeneous cloud platform differentiated services

Abstract

The application discloses a method, device and storage medium for publishing and interactive scheduling based on CMP heterogeneous cloud platform differentiated services, relates to the technical field of cloud service management, service publishing and resource delivery, and discloses a method for publishing and interactive scheduling based on CMP heterogeneous cloud platform differentiated services, which comprises the following steps: publishing services through a cloud management platform CMP, publishing each service to a user in a self-service center in a service factory of the cloud management platform CMP, and composing each service by one or more basic service attributes.

Description

Technical Field

[0001] This invention relates to the field of cloud service management, service publishing, and resource delivery technology, specifically a method for publishing and interactive scheduling of differentiated services based on a CMP heterogeneous cloud platform. Background Technology

[0002] With the widespread adoption of cloud computing, more and more customers are using products and services from multiple cloud vendors simultaneously. However, these products and services vary considerably, creating a need for unified management of multiple cloud environments and the ability to publish the same service compatible with different cloud vendors. There are generally two approaches to addressing these differences in cloud vendor services. One approach involves integrating all logic together and differentiating by cloud vendor; this becomes increasingly complex the more cloud vendors are involved. The other approach is to separate each cloud vendor's services, allowing users to access the corresponding services from the chosen vendor.

[0003] However, customers typically don't want to expose their cloud vendors; at the same time, they face the problem that the more cloud vendors they integrate with, the more complicated the adjustments become. Therefore, to achieve service publishing across multiple cloud vendors, it's necessary to abstract service publishing in a consistent manner, forming a unified publishing standard. Then, services from different cloud vendors need to be coded and adapted to create multi-cloud interoperability components. Specific services will reference these components in their project code to adapt to multiple clouds, achieving the final interactive presentation of the service publishing and the billing capabilities of the service usage.

[0004] Common components are typically developed in-house using Vue or on low-code component platforms, generally employing a code-level implementation approach. Given this code-level implementation, the prominent drawbacks currently include:

[0005] 1. It depends on a specific programming language, and components need to be developed, assembled, and deployed as a whole, resulting in poor scalability;

[0006] 2. The service suffers from uncertainty, complexity, poor code readability, and difficulty in modification;

[0007] 3. The more services there are, the more specific components there are, increasing the difficulty of subsequent operation and maintenance;

[0008] 4. Inconsistent component writing styles among different personnel increase the difficulty of operation and maintenance with each new cloud vendor.

[0009] 5. Service-related configurations are not uniformly managed, such as billing configurations. Summary of the Invention

[0010] This invention aims to solve at least one of the technical problems existing in the prior art. To this end, this invention proposes a method for publishing and interactive scheduling of differentiated services based on CMP heterogeneous cloud platforms. This method enables users to publish services that simultaneously meet the product attributes and billing requirements of different cloud platforms, guides users to quickly perform differentiated and flexible configuration of services on different cloud platforms, and facilitates subsequent management and reduces operation and maintenance costs.

[0011] To achieve the above objectives, a first aspect of the present invention provides a method for publishing and interactive scheduling of differentiated services based on a CMP heterogeneous cloud platform, comprising:

[0012] S1: Publish services through the cloud management platform CMP. Publish each service in the service factory of the cloud management platform CMP for users to use in the self-service center. Each service consists of one or more basic service attributes.

[0013] S2: Differentiated configuration of service attributes, collecting the basic elements of the service attributes, expanding the basic elements into billing attributes and detail display attributes, and expanding them as a UI component, defining the attributes in the UI component on the front-end page, and configuring input, editable, and hideable attributes into the service attributes;

[0014] S3: Load service attributes and unify the parsing engine. The published service includes four modules: application, change, renewal, and unsubscription. Each module corresponds to multiple service attributes. When a user uses the four modules in the self-service center, the service attributes of the corresponding module are obtained according to the unified parsing engine.

[0015] S4: Automatic rendering of the front-end page. When the service module is accessed, the unified parsing engine loads the corresponding service attribute according to the service module, traverses the service attribute, obtains the UI component of the service attribute, parses it into JSON data that the front-end page can render, and finally encapsulates it into a complete JSON data, updates the front-end page, and completes automatic rendering on the front-end page.

[0016] S5: Interactive scheduling, using the product attributes of different cloud management platform CMPs to complete the corresponding service modules, the UI components can be configured differently on different cloud management platform CMPs, and service resources are delivered through service operations, realizing interactive scheduling of some differentiated operations.

[0017] Preferably, the differential conversion configuration in step S2 specifically includes:

[0018] A service attribute can be shared and used by all the cloud management platforms (CMPs).

[0019] A service attribute can be exclusive and can be loaded, hidden, or displayed based on the type of the cloud management platform CMP.

[0020] One service attribute corresponds to one UI component. The UI component can receive service attribute-related definition configurations or external input parameters to determine the output or display, and is the smallest unit to meet the differences of different cloud platforms;

[0021] A service attribute also has a version concept. As requirements change, historical work orders are affected. After configuring the version of a service attribute, the unified parsing engine can parse the service attribute corresponding to the version of the service module.

[0022] A service attribute can also be controlled by a process, allowing you to configure which step of the process is loaded and displayed.

[0023] Preferably, the unified parsing engine in step S3 specifically includes: parsing the service attributes corresponding to the service module, traversing these service attributes, loading each of its small UI components, and encapsulating them into a large UI component page. This can meet the differences between different cloud platforms and can determine the hiding and display of small UI components based on the cloud platform type.

[0024] Preferably, the automatic rendering of the front-end page in step S4 specifically includes: the large UI component page encapsulated by the unified parsing engine, with parameters interconnected between each of the small UI components, the output parameters of a UI component being the input parameters of another UI component, and when a user switches between different cloud platforms, only the UI components of the corresponding platform are displayed, while the others are hidden.

[0025] Preferably, updating the front-end page in step S4 specifically includes:

[0026] When a user accesses the service module, the cloud management platform CMP presentation layer requests data access, returns cached data, and triggers a data update strategy.

[0027] Synchronously request the latest data from the cloud management platform CMP to write JSON data, update the data management data version using Redux, and after the update is completed, send incremental data to the cloud management platform CMP presentation layer through the response link;

[0028] Listeners in the Cloud Management Platform (CMP) presentation layer are bound to the lifecycle of the front-end page. When the CMP presentation layer is visible and operable, reactive programming creates a data flow path through user data subscription, asynchronously and incrementally refreshes the CMP presentation layer view, and completes the front-end page update.

[0029] Preferably, the service has one or more of the following: unique ID, name, number, abbreviation, category, and product;

[0030] The service attributes include one or more of the following: ID, Service ID, Service KEY, Service Display Name, Type, Default Value, Parameter Association, UI Components, Whether Application is Editable, Whether Editable and Modifiable, Whether Comparison is Possible, Whether Billing is Possible, Whether to Hide, Whether to Display Details, and Purpose Tags.

[0031] The present invention also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor loads and executes the computer program to implement the steps of the method for publishing and interactive scheduling of differentiated services based on a CMP heterogeneous cloud platform as described above.

[0032] The present invention also provides a storage medium storing a computer program, which, when loaded and executed by a processor, implements the steps of the method for publishing and interactive scheduling of differentiated services based on a CMP heterogeneous cloud platform as described in any of the preceding claims.

[0033] Compared with the prior art, the beneficial effects of the present invention are:

[0034] This invention enables users to publish services that simultaneously meet the product attributes and billing requirements of different cloud platforms, guides users to perform differentiated and flexible configuration of services on different cloud platforms, and facilitates subsequent management and further reduces operation and maintenance costs. Attached Figure Description

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

[0036] Figure 1 This is a flowchart illustrating the method for publishing and interactive scheduling of differentiated services based on a CMP heterogeneous cloud platform according to the present invention.

[0037] Figure 2 This is a data model diagram of the method for publishing and interactive scheduling of differentiated services based on the CMP heterogeneous cloud platform according to the present invention.

[0038] Figure 3 This is a logical concept diagram of the method for publishing and interactive scheduling of differentiated services based on the CMP heterogeneous cloud platform according to the present invention.

[0039] Figure 4 This is the smallest unit of the operation diagram for the method of publishing and interactive scheduling of differentiated services based on CMP heterogeneous cloud platform of the present invention. Detailed Implementation

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

[0041] Please see Figure 1 The first aspect of this application provides a method for publishing and interactive scheduling of differentiated services based on a CMP heterogeneous cloud platform, including:

[0042] S1: Publish services through the cloud management platform CMP. Publish each service in the service factory of the cloud management platform CMP for users to use in the self-service center. Each service consists of one or more basic service attributes.

[0043] like Figure 2 As shown, the data model of this method includes services, service attributes, static data sources for service attributes, service process attributes, service attribute step configurations, and service attribute versions, demonstrating the relationships between services, service attributes, static data sources for service attributes, service process attributes, service attributes, and service attribute version steps. During the implementation of this method, the data model follows... Figure 2 The structure shown is used for data organization and storage.

[0044] Each service has a unique ID, name, number, abbreviation, category, and product ID.

[0045] Figure 3 This is a logical concept diagram of the method for publishing and interactive scheduling of differentiated services based on the CMP heterogeneous cloud platform according to the present invention.

[0046] S2: Differentiate configuration service attributes, collect the basic elements of the service attributes, expand the basic elements into billing attributes and detail display attributes, and expand them as UI components, and define the attributes in the UI components on the front-end page.

[0047] Optionally, input-friendly, editable, and hideable attributes can also be configured into the service attributes.

[0048] Service attributes include ID, service ID, service KEY, service display name, type, default value, parameter association, UI components, whether it is editable upon application, whether it is editable and modifiable, whether it is compared, whether it is billed, whether it is hidden, whether it is displayed in details, and usage tags.

[0049] The static data source for service attributes includes ID, service attribute ID, service attribute KEY value, extended information, etc.

[0050] The specific methods for filtering out service attribute keys include:

[0051] Create an iterable object to convert service properties into an iterable collection of key-value pairs;

[0052] Define filtering condition functions, create judgment functions, identify keys related to the approval process, and use judgment functions to identify whether the key contains specific keywords;

[0053] Construct a lazy operation chain by using generator functions or libraries that support lazy evaluation, and add filtering operations to the operation chain;

[0054] Implement lazy iteration, process service attributes, and obtain the service attribute key of the filtered approval process.

[0055] The service process attributes include ID, service attribute ID, process KEY, process step KEY, whether it is editable, and whether it is hidden.

[0056] The service attribute configuration steps include information such as ID, service ID, extended service ID, resource type, page title, and resource name.

[0057] Furthermore, the differential configuration includes:

[0058] A service attribute can be shared and used by all the cloud management platforms (CMPs).

[0059] A service attribute can be exclusive and can be loaded, hidden, or displayed based on the type of the cloud management platform CMP.

[0060] One service attribute corresponds to one UI component. The UI component can receive service attribute-related definition configurations or external input parameters to determine the output or display, and is the smallest unit to meet the differences of different cloud platforms;

[0061] A service attribute also has a version concept. As requirements change, historical work orders are affected. After configuring the version of a service attribute, the unified parsing engine can parse the service attribute corresponding to the version of the service module.

[0062] A service attribute can also be controlled by a process, allowing you to configure which step in the process loads and displays it.

[0063] S3: Load service attributes and unify the parsing engine. The published service contains multiple modules, and each module corresponds to multiple service attributes.

[0064] When the four modules are invoked by the user in the self-service center, the service attributes of the corresponding modules are obtained according to the unified parsing engine.

[0065] The module includes application, modification, renewal, and cancellation.

[0066] The service attribute version includes ID, service ID, type, version number, version time, and version record.

[0067] Furthermore, the steps of the unified parsing engine include:

[0068] S31: Parse the service attributes corresponding to the service module;

[0069] S32: Iterate through these service properties and load the UI components one by one;

[0070] This method matches one or more attributes of cloud products from different clouds into one or more smallest unit components of a service, that is, the external configuration effect of the smallest unit component is realized.

[0071] Specifically, based on the unified parsing engine, the service attributes of the corresponding modules of the corresponding services are obtained. Different service attributes, including billing attributes, detail attributes, comparison attributes, work order attributes, view attributes, edit attributes, application attributes, and API attributes, are matched to the services. Then, input parameters, output parameters, editing, display, default values, validation, and other services are matched to the smallest unit component. The unified parsing engine loads the corresponding service attributes according to the service modules, traverses the service attributes, obtains the smallest unit component of the service attributes, and converts it into JSON data that can be rendered by the front-end page through the unified parsing engine.

[0072] S33: Encapsulate it into a complete UI component page to meet the differences between different cloud platforms.

[0073] In step S32, the display / hide attributes of the small UI component can be determined based on the cloud platform type.

[0074] The method for publishing and interactive scheduling of differentiated services based on CMP heterogeneous cloud platforms of the present invention further includes:

[0075] S4: When the service module is accessed, the unified parsing engine loads the corresponding service attribute according to the service module, traverses the service attribute, obtains the UI component of the service attribute, parses it into JSON data that the front-end page can render, and finally encapsulates it into a complete JSON data, updates the front-end page, and completes automatic rendering on the front-end page.

[0076] Furthermore, the automatic rendering of the front-end page includes:

[0077] S41: The unified parsing engine encapsulates the overall UI component page, and each UI component has parameters that interact with each other; wherein, the output parameters of one UI component are the input parameters of another UI component, and when the user switches to different cloud platforms, only the UI components of the corresponding platform are displayed, and other components are hidden.

[0078] like Figure 4 As shown, this method demonstrates how the system operates internally within the smallest unit component corresponding to the cloud product attributes of different clouds, that is, how the differentiated configuration effect is implemented within the component. Specifically:

[0079] S42: Render the JSON frontend of the low-code platform component, initialize the component corresponding to the service attribute, and check if there is a corresponding component for the service attribute. If not, skip and end; if yes, initialize the component corresponding to the service attribute.

[0080] S43: Determine if the component is editable. If not, display "not editable"; if yes, display "editable".

[0081] S44: Determine if the component is assigned a value. If not, do not assign the first value. If yes, assign the first value.

[0082] S44: Determine if there is a default value. If not, do nothing. If so, assign a default value.

[0083] S45: Determine if there is a static data source. If not, do not load the static data source parser. If so, load the static data source parser.

[0084] S46: Obtain the UI component of the service attributes, parse it into JSON data that the front-end page can render, and then end.

[0085] The method for publishing and interactive scheduling of differentiated services based on CMP heterogeneous cloud platforms of the present invention further includes:

[0086] S5: Using the product attributes of different cloud management platform CMPs, complete the corresponding service modules, and configure the UI components differently on different cloud management platform CMPs. Service resources are delivered through service operations, realizing interactive scheduling of some differentiated operations.

[0087] According to another embodiment of the present invention, such as Figure 1-4As shown, suppose a user is preparing to publish a non-domestic-innovation ECS service on a cloud management platform, while simultaneously meeting the resource application and delivery logic of both China Telecom public cloud ECS and Huawei private cloud ECS. After defining an ECS service, the service is described below. The service described in this invention has several product attributes in the cloud product attributes of different clouds: region, availability zone, system disk type, system disk size, specification type, specification size, CPU, memory, image, purchase duration, etc. These product attributes can correspond to service attributes within the service (product attributes that deliver EIPs simultaneously with a public cloud but not with a private cloud), as follows:

[0088] The product attribute area corresponds to the UI component of the query area (dynamically loading data source), and also loads the extended attributes of manual delivery from public cloud or automated delivery from private cloud. The UI component loads the corresponding extended attributes according to different clouds.

[0089] The availability zone of the product attributes corresponds to the UI component for querying availability zones (dynamically loaded data source), which displays the availability zone of the corresponding cloud based on different clouds and architectures.

[0090] The system disk type of the product attributes corresponds to the UI component (static data source) for querying the system disk type. Some data sources are shared, while others are independent of different clouds. The corresponding data source is loaded and displayed according to the product of different clouds.

[0091] The Product Attribute Delivery Instruction (EIP) displays this UI component on a public cloud but not on a private cloud.

[0092] Other ECS product attributes are similar to the configurations of the four mentioned above.

[0093] The unified parsing engine parses the service attributes of a service into JSON data that the front-end page can recognize. During rendering, it finds the corresponding UI component to render.

[0094] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Furthermore, any references to memory, storage, databases, or other media used in the embodiments provided by this invention can include at least one of non-volatile and volatile memory.

[0095] It should be understood that, as used herein, the singular form "a" is intended to include the plural form as well, unless the context clearly supports an exception. It should also be understood that, as used herein, "and / or" refers to any and all possible combinations of one or more of the associatedly listed items. The embodiment numbers disclosed above are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0096] Those skilled in the art should understand that the discussion of any of the above embodiments is merely exemplary and is not intended to imply that the scope of the invention (including the claims) is limited to these examples. Within the framework of the invention, technical features of the above embodiments or different embodiments can be combined, and many other variations of different aspects of the invention exist, which are not provided in the details for the sake of brevity. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the invention should be included within the protection scope of the invention.

Claims

1. A method for publishing and scheduling differentiated services based on a CMP heterogeneous cloud platform, characterized in that, include: S1: Publish services through the cloud management platform CMP. Publish each service in the service factory of the cloud management platform CMP for users to use in the self-service center. Each service consists of one or more basic service attributes. S2: Differentiate the configuration of service attributes, collect the basic elements of the service attributes, expand the basic elements into billing attributes and detail display attributes, expand them as a UI component, and present the attributes in the UI component on the front-end page; S3: Load service attributes from the service center and start the unified parsing engine. The service published by the service factory in step S1 contains multiple modules, and each module corresponds to multiple service attributes. S4: When the module contained in the service published in step S3 is accessed, the unified parsing engine loads the corresponding service attribute according to the module of the service, traverses the service attribute, obtains the UI component of the service attribute, parses it into JSON data that the front-end page can render, and finally encapsulates it into a complete JSON data, updates the front-end page, and completes automatic rendering on the front-end page. S5: Using the product attributes of different cloud management platform CMPs, complete the corresponding service modules, configure the UI components differently on different cloud management platform CMPs, deliver service resources through service operations, and realize interactive scheduling of some differentiated operations.

2. The method for publishing and interactive scheduling of differentiated services based on a CMP heterogeneous cloud platform according to claim 1, characterized in that, The differentiated configuration in step S2 specifically includes: One service attribute is shared and used by all cloud management platforms (CMPs). A service attribute is exclusive and is loaded / hidden / displayed based on the type of the cloud management platform CMP. One service attribute corresponds to one UI component. The UI component receives the service attribute's related definition configuration or external input parameters to determine the output or display, and is the smallest unit to meet the differences between different cloud platforms; A service attribute has a version concept. As requirements change, historical work orders are affected. After configuring the version of a service attribute, the unified parsing engine parses the service attribute corresponding to the version of the service module.

3. The method for publishing and interactive scheduling of differentiated services based on a CMP heterogeneous cloud platform according to claim 2, characterized in that, In step S2, the input, editable, and hideable attributes are configured into the service attributes.

4. The method for publishing and interactive scheduling of differentiated services based on a CMP heterogeneous cloud platform according to claim 1, characterized in that, The unified parsing engine in step S3 specifically includes: parsing the service attributes corresponding to the service module, traversing these service attributes, loading each of its small UI components, encapsulating them into a large UI component page to meet the differences between different cloud platforms, and determining the hiding and display of small UI components based on the cloud platform type.

5. The method for publishing and interactive scheduling of differentiated services based on a CMP heterogeneous cloud platform according to claim 4, characterized in that, In step S3, the module includes four modules: application, change, renewal, and cancellation. When the user calls the four modules in the self-service center, the service attributes of the corresponding module are obtained according to the unified parsing engine.

6. The method for publishing and interactive scheduling of differentiated services based on a CMP heterogeneous cloud platform according to claim 5, characterized in that, The step S4 of updating the front-end page specifically includes: When a user accesses the service module, the cloud management platform CMP presentation layer requests data access, returns cached data, and triggers a data update strategy. Synchronously request the latest data from the cloud management platform CMP to write JSON data, update the data management data version using Redux, and after the update is completed, send incremental data to the cloud management platform CMP presentation layer through the response link; Listeners in the Cloud Management Platform (CMP) presentation layer are bound to the lifecycle of the front-end page. When the CMP presentation layer is in a visible and operable state, reactive programming creates a data flow link through user data subscription, asynchronously and incrementally refreshes the CMP presentation layer view, and completes the front-end page update.

7. The method for publishing and interactive scheduling of differentiated services based on a CMP heterogeneous cloud platform according to claim 1, characterized in that, The service has one or more of the following: unique ID, name, number, abbreviation, category, and product; The service attributes include one or more of the following: ID, Service ID, Service KEY, Service Display Name, Type, Default Value, Parameter Association, UI Components, Whether Application is Editable, Whether Editable and Modifiable, Whether Comparison is Possible, Whether Billing is Possible, Whether to Hide, Whether to Display Details, and Purpose Tags.

8. A computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor loads and executes the computer program to implement the steps of the method for publishing and interactive scheduling of differentiated services based on a CMP heterogeneous cloud platform as described in any one of claims 1-7.

9. A storage medium storing a computer program, which, when loaded and executed by a processor, implements the steps of the method for publishing and interactive scheduling of differentiated services based on a CMP heterogeneous cloud platform as described in any one of claims 1-7.

Images