CN113885892A - Low code configuration access method based on multi-cloud platform - Google Patents
Low code configuration access method based on multi-cloud platform Download PDFInfo
- Publication number
- CN113885892A CN113885892A CN202111487807.9A CN202111487807A CN113885892A CN 113885892 A CN113885892 A CN 113885892A CN 202111487807 A CN202111487807 A CN 202111487807A CN 113885892 A CN113885892 A CN 113885892A
- Authority
- CN
- China
- Prior art keywords
- cloud platform
- cloud
- service
- platform
- type
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a multi-cloud platform-based low code configuration access method, which comprises the following steps: registering the type of the newly accessed cloud platform and the type of the cloud service; constructing a new cloud platform and a butted cloud platform package, and completing standard model configuration of the cloud platform; releasing and deploying the configured cloud platform version and the configured cloud service; completing standard service API configuration of the cloud platform; configuring a model related to a service type which is planned to be supported on an accessible cloud platform type; completing the adaptation of the cloud platform authority of the same service type and the standard authority; and configuring a cloud platform service API provided on the cloud platform with the same service type. The multi-cloud platform access method is flexible and simple, the difference of cloud platform resources and management function APIs in the lower heterogeneous cloud platform and the difference of page element expression are shielded, and designers can configure a page definition standard cloud service API on one screen according to abstract cloud services.
Description
Technical Field
The invention relates to the technical field of cloud platform service support, in particular to a low-code configuration access method based on a multi-cloud platform.
Background
With the comprehensive development of cloud computing services, a cloudy era comes, and a mixed cloudy will become a new normal state and will exist for a long time in the future, and will be enriched and improved continuously. In order to better help enterprises to implement a multi-cloud strategy, when a multi-cloud management platform is constructed, the multi-cloud management platform has to have good expansion capability, and can quickly cover the introduction of various heterogeneous infrastructures and cloud merchants by the enterprises; the method has the advantages that the client-centered service can be insistently performed, and the cloud-one-stop service experience of the user can be swiftly responded; open API capability must be provided, and only open API capability is provided, users can form a solution which accords with the API capability, and value is continuously created.
The multi-cloud management platform needs to uniformly manage and control cloud platforms of various different manufacturers and technical architectures, and the managed contents of the multi-cloud management platform are all from the bottom-layer cloud platform, so that different cloud platforms need to be connected. However, because the underlying cloud platforms all have respective resource and capability architectures, taking a public cloud of a certain manufacturer as an example, the number of the provided cloud services reaches more than 100, and each cloud service has dozens of APIs according to the open capability, if the docking is performed according to the traditional code writing mode, a large amount of manpower is consumed, so that a set of architecture capable of rapidly and flexibly docking various cloud service capability APIs on different cloud platforms is required.
Meanwhile, the cores of the multiple cloud management platforms are unified, that is, a set of unified operation, operation and maintenance and resource management capabilities for the multiple cloud platforms can be provided as much as possible, so that the whole multiple cloud management platform cannot be functionally modified due to new access to one cloud platform or a certain cloud service on one cloud platform, and the multiple cloud management platforms can be accessed to multiple cloud platforms, and also need to shield the difference of resources and capabilities on the underlying cloud platform, so that the multiple cloud platforms are controlled through a unified interface.
At present, for the management of multiple clouds, most methods are to perform customized encapsulation according to an interface of each cloud platform, and the method has the following disadvantages:
1. the method comprises the following steps that butt joint is complex, business logic managed by a cloud platform needs to be known, customization development is carried out aiming at a specific cloud platform interface calling mode, the requirement of the business logic managed by a cloud platform manufacturer on developers is high, and after the cloud platform is upgraded, if the interface is adjusted, customization continuous modification is needed;
2. the new requirements meet low efficiency, and the requirements on the timeliness of service access are gradually increased under the requirements of quick adaptation of the requirements or on-demand on the development of the current and future cloud computing services, particularly cloud computing services; the existing interface can not adjust access at any time according to the service requirement;
3. the expandability is weak, the cloud platform is managed in a customized mode, the expandability is weak, the customized mode is usually carried out according to different cloud manufacturers of each data center, if a new cloud manufacturer needs to be brought in, the development period is longer, a new cloud is accessed according to the past project experiment experience, one week is needed for completely docking a certain cloud product, meanwhile, the existing multi-cloud management framework cannot be compatible, and the framework and the model adjustment of the original system can be related.
An effective solution to the problems in the related art has not been proposed yet.
Disclosure of Invention
Aiming at the problems in the related art, the invention provides a multi-cloud platform-based low-code configuration access method to overcome the technical problems in the prior related art.
Therefore, the invention adopts the following specific technical scheme:
a multi-cloud platform-based low code configuration access method comprises the following steps:
s1, registering the type of the new access cloud platform and the type of the cloud service;
s2, constructing a new cloud platform and a docked cloud platform package, and completing standard model configuration of the cloud platform;
s3, releasing and deploying the configured cloud platform version and cloud service;
s4, completing standard service API configuration of the cloud platform;
s5, configuring a model related to a service type which is planned to be supported on the accessible cloud platform type;
s6, completing the adaptation of the cloud platform authority and the standard authority of the same service type;
and S7, configuring the cloud platform service API provided on the cloud platform with the same service type.
Further, the cloud platform type registration in S1 is to manage the cloud platform types that the product can access, including defining a service address type, a version number, and a basic package for each cloud platform type.
Further, in S1, the cloud service type registration is to define a cloud service type supported and managed by the product, and includes parameters of elastic cloud hosts, object storage, and load balancing, which define the cloud service type.
Further, the standard model configuration of the cloud platform in S2 includes a model definition, an attribute definition, and a relationship definition; the model defines a model icon, a model name and a template code of a standard model for managing the cloud platform; defining ID, name, type, default value and various constraint conditions of the attribute required by the configuration of the model by the attribute; the relationship definition is used for presentation and association analysis between topologies.
Further, when API configuration is performed on the standard service in S4, dividing configuration parameters into basic parameters and extended parameters according to the type of the cloud platform; the basic parameters are cloud platform type general parameters, and the extended parameters are cloud platform type personalized parameters.
Further, the model involved in the service type in S5 is consistent with the standard model configuration parameters of the cloud platform in S2.
Further, the cloud platform service API in S7 is consistent with the standard service API configuration parameters of the cloud platform in S4.
Further, when a public cloud platform or a private cloud platform is docked, the platform bag is divided into a platform foundation bag and a platform rule bag.
Further, the use flow of the platform basic package is as follows:
adding a required configuration file to indicate the type of a butted cloud platform, compiling logic according to interface specifications and constructing a platform foundation package;
after the basic package is packaged, the basic package is uploaded and verified and analyzed through management of a basic package management module;
and after the analysis is finished, when the service calling needs to access the cloud platform, calling the basic package by adopting the platform access control module.
Further, the usage flow of the platform rule package is as follows:
adding a required configuration file into the rule package, indicating an applicable cloud platform type and an applicable cloud service type, compiling related logic according to interface specifications and constructing a platform rule package;
after the rule package is packaged, the rule package is managed by a rule package management module to be uploaded and verified and analyzed;
after the analysis is completed, the atomic service registration module is used for adaptively selecting whether to load the corresponding rule check package, and if the loading is selected, the service calling control module is used for calling.
The invention has the beneficial effects that:
(1) the multi-cloud platform access method is flexible and simple, the difference of cloud platform resources and management function APIs in the lower heterogeneous cloud platform and the difference of page element expression are shielded, and a designer can configure a page definition standard cloud service API on one screen according to abstract cloud services; each upper application capability center can call the cloud service capabilities of different bottom cloud platforms through a standard cloud service API, so that the upper application capability center and the bottom cloud platform are decoupled; after the standard cloud service API is defined, designers can arrange and combine the native API of the bottom cloud platform in a dragging mode according to the capability of the standard cloud service API without code development to quickly complete the capability calling of the bottom cloud platform, so that the problems of complicated butt joint operation and the like of bottom heterogeneous cloud platform interfaces in the prior art are solved.
(2) The cloud platform data processing method and the cloud platform data processing system have the advantages that the visual design is flexible and convenient, differentiated data on each cloud platform can be collected and can be mapped and stored in a warehouse according to the standard model, the flexible and convenient whole-process visual one-screen configuration capacity is provided, a user can design and input normalization rules through dragging on an interface, various data processing components can be conveniently established, corresponding processing logics are input into the data processing components, meanwhile, basic logic judgment components and data processing components are provided for products, and the user can be helped to quickly finish adaptive mapping from cloud platform raw data to the standard model through the matching of the various capacities.
(3) The method decouples the upper cloud capacity center from the bottom heterogeneous cloud platforms, namely adapts management models, such as tenant, authority, area correlation, business correlation and other models, resource models and services on the cloud platforms, and abstracts the models, the resource models and the services into a unified set of specifications.
(4) The configuration method has strong expandability, and because the SDK packet and the adaptation layer interface with unified standards are adopted, if a new cloud platform needs to be accessed in an extended manner in the later period, only the configuration is needed, and the SDK packet of the cloud platform interface is added to be brought in an adapted manner; the method of the invention maintains the characteristics of each heterogeneous platform and supports unified management and interface scheduling, so that a user can select the required cloud platform deployment according to the application requirement.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
Fig. 1 is a schematic flowchart of a low code configuration access method based on a multi-cloud platform according to an embodiment of the present invention;
fig. 2 is a schematic diagram of a multi-cloud access flow in a multi-cloud platform-based low-code configuration access method according to an embodiment of the present invention;
fig. 3 is a schematic diagram of a cloud service call flow in a multi-cloud-platform-based low-code configuration access method according to an embodiment of the present invention.
Detailed Description
For further explanation of the various embodiments, the drawings which form a part of the disclosure and which are incorporated in and constitute a part of this specification, illustrate embodiments and, together with the description, serve to explain the principles of operation of the embodiments, and to enable others of ordinary skill in the art to understand the various embodiments and advantages of the invention, and, by reference to these figures, reference is made to the accompanying drawings, which are not to scale and wherein like reference numerals generally refer to like elements.
According to the embodiment of the invention, a multi-cloud platform-based low-code configuration access method is provided.
The present invention will be further described with reference to the accompanying drawings and specific embodiments, as shown in fig. 1, a low code configuration access method based on a multi-cloud platform according to an embodiment of the present invention includes the following steps:
s1, registering the type of the new access cloud platform and the type of the cloud service;
in one embodiment, the cloud platform type registration in S1 is to manage the cloud platform types that the product can access, including defining a service address type, a version number, and a basic package for each cloud platform type.
In one embodiment, the cloud service type registration in S1 is to define a cloud service type supported and managed by the product, and includes parameters of elastic cloud hosts, object storage, and load balancing, which define the cloud service type.
S2, constructing a new cloud platform and a docked cloud platform package, and completing standard model configuration of the cloud platform;
in one embodiment, the standard model configuration of the cloud platform in S2 includes a model definition, an attribute definition, and a relationship definition; the model defines a model icon, a model name and a template code of a standard model for managing the cloud platform; defining ID, name, type, default value and various constraint conditions of the attribute required by the configuration of the model by the attribute; the relationship definition is used for presentation and association analysis between topologies.
S3, releasing and deploying the configured cloud platform version and cloud service;
s4, completing configuration of a standard service API (Application Programming Interface) of the cloud platform;
in one embodiment, when API configuration is performed on the standard service in S4, the configuration parameters are divided into basic parameters and extended parameters according to the cloud platform type; the basic parameters are cloud platform type general parameters, and the extended parameters are cloud platform type personalized parameters.
Specifically, when configuring the standard service API parameter, the parameter is considered to be divided into a basic parameter and an extended parameter according to the cloud platform type, the basic parameter is a parameter that is common to abstract different cloud platform types, the extended parameter is suitable for a personalized parameter of the cloud platform type, and the standard service API is called by other modules, so that in order to consider compatibility problems, a version management function of the standard service API needs to be supported, and in addition, a calling path of the standard service API needs to be clearly divided, so that key information of the standard service API can be embodied through the calling path (such as/gateway/API/closed ecs/manage/createddtcestereconsisinstance).
S5, configuring a model related to a service type which is planned to be supported on the accessible cloud platform type;
in one embodiment, the model involved in the service type in S5 is consistent with the standard model configuration parameters of the cloud platform in S2, so as to ensure that the information obtained from the cloud platform is not lost. After model configuration under a certain service type is completed, after the service is specifically accessed to the cloud platform, the configuration information of the corresponding model can be instantiated and put in storage.
S6, completing the adaptation of the cloud platform authority and the standard authority of the same service type;
specifically, the corresponding relation between the two authorities is configured, so that the two authorities can be mutually converted, and unified control over the authorities is realized. The adaptation rule of the authority needs to meet 1 to 1 adaptation, and 1 to 1 is adapted to the standard authority according to the function realized by the authority control in the angle of the cloud platform authority.
And S7, configuring the cloud platform service API provided on the cloud platform with the same service type.
In one embodiment, the cloud platform service API in S7 is consistent with the standard service API configuration parameters of the cloud platform in S4. When a service on a certain cloud platform is called subsequently, the service is combined according to the configuration information of the API and then the call is initiated. The cloud platform service API comprises the following contents when configured: the service API defines: and managing basic information of the cloud platform service API, wherein the basic information comprises service calling modes, service calling types, service address types, API paths, adaptive versions, corresponding authority codes, service classifications, service actions and the like.
When a new cloud platform is docked, the related architecture of the cloud platform needs to be mastered clearly, and how to map the management model, the resource model and the service on the cloud platform to the unified specification can be known. With the development of business, the cloud platform type and the cloud platform version are continuously updated in an iterative manner, and most of the development work of docking codes can be reduced by adopting a low-code configuration mode to realize cloud service adaptation and cloud model adaptation. And guiding a user to configure the service rules of the cloud environment to be managed in a one-stop manner to a guide type extremely-simple configuration interface, and simply configuring the user according to the API specification and the actual service requirement of the corresponding cloud management platform to quickly bring the cloud service of the cloud management platform into line.
The low code configuration accesses a cloud management platform capable of realizing the main stream docking: the system comprises OpenStack, VMware, a container cloud platform and the like, and can be connected with a mainstream public cloud or a proprietary cloud platform: the cloud platform comprises public cloud platforms which are ranked at the top in the industry, such as Aliyun, Huazhiyun, Tianyi cloud, mobile cloud, Union cloud, Jinshan cloud and the like.
In one embodiment, when a public cloud platform or a private cloud platform is docked, the platform package is divided into a platform basic package and a platform rule package, the basic package is packaged with cloud platform login verification related business logic, a needed cloud platform sdk package during calling and calling business logic needing hard coding realization, and the rule package is packaged with business verification rules or exception handling rules of different services of the cloud platform, and can be constructed according to product or service dimensions.
In one embodiment, the usage flow of the platform foundation package is as follows:
adding a required configuration file to indicate the type of a butted cloud platform, compiling logic according to interface specifications and constructing a platform foundation package;
after the basic package is packaged, the basic package is uploaded and verified and analyzed through management of a basic package management module;
and after the analysis is finished, when the service calling needs to access the cloud platform, calling the basic package by adopting the platform access control module.
In one embodiment, the usage flow of the platform rule package is as follows:
adding a required configuration file into the rule package, indicating an applicable cloud platform type and a applicable cloud service type, compiling related logic according to an interface specification and constructing a platform rule package (the rule package does not relate to changes of resource states and attributes, and only needs to figure out which micro services need to pass to obtain required data and compile corresponding verification logic);
after the rule package is packaged, the rule package is managed by a rule package management module to be uploaded and verified and analyzed;
after the analysis is completed, the atomic service registration module is used for adaptively selecting whether to load the corresponding rule check package, and if the loading is selected, the service calling control module is used for calling.
When the model is adapted, after finding the corresponding adapted model relationship, the attributes on the model need to be adapted according to the rules, and the current model attributes support the following adaptation modes:
the cloud platform model attribute 1 is matched with the standard model attribute in a ratio of 1: an attribute of the cloud platform model can be adapted to an attribute of the standard model through a rule;
the cloud platform model attribute N is matched with the standard model attribute in a ratio of 1: multiple attributes of the cloud platform model can be adapted to one attribute of the standard model through a rule;
the cloud platform model attribute 1 is matched with the standard model attribute than N: 1 attribute of the cloud platform model can be adapted to a plurality of attributes of the standard model through rules;
self-adaptation of cloud platform model attributes: the attributes of the cloud platform model are adapted inside the model.
As shown in fig. 2, after receiving a northbound cloud platform access request, the cloud platform registration management under the multi-cloud access scheduling module controls the whole access process, verifies login credential information provided in the access request, pulls and stores tenant information, permissions after the verification is passed, maintains the relationship between the user, the tenant and the tenant permissions, adds an acquisition policy of the tenant, starts to acquire relevant resource data in real time, and converts the acquired resource data into standard resource data and reports the standard resource data after the acquisition is completed.
The login credential verification is used for logging in the corresponding cloud platform according to the login credential information in the access request; pulling the tenant information and the permission to obtain the corresponding tenant information and the corresponding tenant permission information, and converting the obtained tenant platform permission into a standard permission format; the tenant related information storage is used for storing a tenant login certificate, tenant authority information and a relationship between a tenant and a user; adding an acquisition strategy for adding acquisition rule information of the tenant in the acquisition strategy of the corresponding cloud platform; initiating real-time data acquisition for initiating real-time resource data acquisition, acquiring resource data of the tenant through the service configured in the acquisition template, and monitoring the acquisition process; and the data reporting is used for storing the collected metadata and converting the metadata into standard resource data for reporting.
After receiving a northbound standard cloud service request, controlling the whole service calling process through service calling control under a multi-cloud driving module, finding a corresponding cloud platform atomic service through service routing and adaptation, ensuring legal compliance of the service calling request through permission verification, then initiating calling, analyzing a result, converting a standard cloud service request format and returning.
The cloud service invoking process is as shown in fig. 3, wherein the service request routing is used for routing the cloud service request and the public parameter to the cloud platform atomic service according to the invoking standard; the cloud service adaptation is used for converting the standard cloud service request parameters into atomic service request parameters according to service adaptation configuration; the authority verification is used for verifying whether the user has the authority of calling the atomic service according to the authorization tenant certificate information and the authorization authority of the requesting user; the rule verification is used for acquiring a service calling business rule on the cloud platform according to the called atomic service and verifying whether the service calling business rule meets the atomic service calling rule according to the corresponding metadata state and attribute; initiating call for controlling the call flow of the cloud platform, acquiring a cloud platform login verification method, initiating call, and monitoring the platform access call process; and the result feedback is used for acquiring feedback data according to the cloud service analysis rule, changing metadata information according to the request, converting the atomic service feedback parameters into standard cloud service feedback parameters and feeding back the standard cloud service feedback parameters.
In summary, by means of the technical scheme, the multi-cloud platform access method is flexible and simple, the difference of cloud platform resources and management function APIs in the lower heterogeneous cloud platform and the difference of page element expression are shielded, and a designer can configure a page definition standard cloud service API on one screen according to an abstract cloud service; each upper application capability center can call the cloud service capabilities of different bottom cloud platforms through a standard cloud service API, so that the upper application capability center and the bottom cloud platform are decoupled; after the standard cloud service API is defined, designers can arrange and combine the native API of the bottom cloud platform in a dragging mode according to the capability of the standard cloud service API without code development to quickly complete the capability calling of the bottom cloud platform, so that the problems of complicated butt joint operation and the like of bottom heterogeneous cloud platform interfaces in the prior art are solved.
In addition, the invention has flexible and convenient visual design, can collect differentiated data on each cloud platform and can map and store the data according to the standard model, and provides flexible and convenient whole-course visual one-screen configuration capability, a user can drag and design and input normalization rules on an interface, and can conveniently establish various data processing components and input corresponding processing logics, and meanwhile, the product provides a basic logic judgment component and a data processing component, and the invention can help the user to quickly complete the adaptive mapping from the cloud platform raw data to the standard model through the matching of the capabilities.
In addition, the upper cloud capacity center and the bottom heterogeneous cloud platforms are decoupled, namely management models, such as tenant models, authority models, area correlation models, business correlation models and the like, resource models and services on the cloud platforms are adapted to be abstracted into a unified set of specifications.
In addition, the configuration method has strong expandability, and because the SDK packet and the adaptation layer interface with unified standards are adopted, if a new cloud platform needs to be accessed in an extended mode in the later period, only the configuration is needed, and the SDK packet of the cloud platform interface is added to be brought in an adaptive mode; the method of the invention maintains the characteristics of each heterogeneous platform and supports unified management and interface scheduling, so that a user can select the required cloud platform deployment according to the application requirement.
Claims (10)
1. A multi-cloud platform-based low-code configuration access method is characterized by comprising the following steps:
s1, registering the type of the new access cloud platform and the type of the cloud service;
s2, constructing a new cloud platform and a docked cloud platform package, and completing standard model configuration of the cloud platform;
s3, releasing and deploying the configured cloud platform version and cloud service;
s4, completing standard service API configuration of the cloud platform;
s5, configuring a model related to a service type which is planned to be supported on the accessible cloud platform type;
s6, completing the adaptation of the cloud platform authority and the standard authority of the same service type;
and S7, configuring the cloud platform service API provided on the cloud platform with the same service type.
2. The multi-cloud-platform-based low-code-configuration access method according to claim 1, wherein the cloud platform type registration in S1 is to manage the cloud platform types that the product can access, and includes defining a service address type, a version number, and a basic package for each cloud platform type.
3. The multi-cloud platform-based low-code configuration access method according to claim 1 or 2, wherein the cloud service type registration in S1 is to define a cloud service type supported and managed by a product, and includes parameters of elastic cloud hosts, object storage and load balancing for defining the cloud service type.
4. The multi-cloud platform-based low-code configuration access method according to claim 1, wherein the standard model configuration of the cloud platform in S2 includes a model definition, an attribute definition and a relationship definition;
the model defines a model icon, a model name and a template code of a standard model for managing the cloud platform;
defining ID, name, type, default value and various constraint conditions of the attribute required by the configuration of the model by the attribute;
the relationship definition is used for presentation and association analysis between topologies.
5. The multi-cloud-platform-based low-code configuration access method according to claim 1, wherein when API configuration is performed on the standard service in S4, configuration parameters are divided into basic parameters and extended parameters according to cloud platform types;
the basic parameters are cloud platform type general parameters, and the extended parameters are cloud platform type personalized parameters.
6. The multi-cloud platform-based low-code configuration access method according to claim 1, wherein a model involved in the service type in S5 is consistent with standard model configuration parameters of the cloud platform in S2.
7. The multi-cloud platform based low-code configuration access method according to claim 1, wherein the cloud platform service API in S7 is consistent with standard service API configuration parameters of the cloud platform in S4.
8. The multi-cloud platform-based low-code configuration access method according to claim 1 or 7, wherein when a public cloud platform or a private cloud platform is docked, the platform package is divided into a platform base package and a platform rule package.
9. The multi-cloud platform-based low-code configuration access method according to claim 8, wherein the usage flow of the platform basic package is as follows:
adding a required configuration file to indicate the type of a butted cloud platform, compiling logic according to interface specifications and constructing a platform foundation package;
after the basic package is packaged, the basic package is uploaded and verified and analyzed through management of a basic package management module;
and after the analysis is finished, when the service calling needs to access the cloud platform, calling the basic package by adopting the platform access control module.
10. The multi-cloud platform based low-code configuration access method according to claim 8, wherein the usage flow of the platform rule package is as follows:
adding a required configuration file into the rule package, indicating an applicable cloud platform type and an applicable cloud service type, compiling related logic according to interface specifications and constructing a platform rule package;
after the rule package is packaged, the rule package is managed by a rule package management module to be uploaded and verified and analyzed;
after the analysis is completed, the atomic service registration module is used for adaptively selecting whether to load the corresponding rule check package, and if the loading is selected, the service calling control module is used for calling.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111487807.9A CN113885892B (en) | 2021-12-08 | 2021-12-08 | Low code configuration access method based on multi-cloud platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111487807.9A CN113885892B (en) | 2021-12-08 | 2021-12-08 | Low code configuration access method based on multi-cloud platform |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113885892A true CN113885892A (en) | 2022-01-04 |
| CN113885892B CN113885892B (en) | 2022-03-22 |
Family
ID=79016493
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111487807.9A Active CN113885892B (en) | 2021-12-08 | 2021-12-08 | Low code configuration access method based on multi-cloud platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113885892B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114741060A (en) * | 2022-06-13 | 2022-07-12 | 浪潮通信技术有限公司 | Business system development method and device based on middle platform |
| CN116661756A (en) * | 2023-07-24 | 2023-08-29 | 浩鲸云计算科技股份有限公司 | Object analysis method and device based on low-code DSL |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2013097079A1 (en) * | 2011-12-26 | 2013-07-04 | 华为技术有限公司 | Method for providing services by cloud platform and cloud platform |
| CN107659624A (en) * | 2017-09-06 | 2018-02-02 | 国云科技股份有限公司 | A kind of isomery cloud management system and method suitable for cloud computing |
| CN107888673A (en) * | 2017-11-03 | 2018-04-06 | 国云科技股份有限公司 | A kind of unified management implementation method suitable for isomery cloud platform |
| US20180205604A1 (en) * | 2016-05-20 | 2018-07-19 | Vmware, Inc. | Deploying and monitoring multiplatform cloud-based infrastructures |
| CN109451028A (en) * | 2018-11-16 | 2019-03-08 | 深圳供电局有限公司 | A kind of cloud management system based on adapter technique |
| CN109729150A (en) * | 2018-12-05 | 2019-05-07 | 国云科技股份有限公司 | A kind of front end processing method based on cloudy more service accesses |
-
2021
- 2021-12-08 CN CN202111487807.9A patent/CN113885892B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2013097079A1 (en) * | 2011-12-26 | 2013-07-04 | 华为技术有限公司 | Method for providing services by cloud platform and cloud platform |
| US20180205604A1 (en) * | 2016-05-20 | 2018-07-19 | Vmware, Inc. | Deploying and monitoring multiplatform cloud-based infrastructures |
| CN107659624A (en) * | 2017-09-06 | 2018-02-02 | 国云科技股份有限公司 | A kind of isomery cloud management system and method suitable for cloud computing |
| CN107888673A (en) * | 2017-11-03 | 2018-04-06 | 国云科技股份有限公司 | A kind of unified management implementation method suitable for isomery cloud platform |
| CN109451028A (en) * | 2018-11-16 | 2019-03-08 | 深圳供电局有限公司 | A kind of cloud management system based on adapter technique |
| CN109729150A (en) * | 2018-12-05 | 2019-05-07 | 国云科技股份有限公司 | A kind of front end processing method based on cloudy more service accesses |
Non-Patent Citations (1)
| Title |
|---|
| 王一盟: "异构私有云管平台通用适配器的研究与实现", 《智能计算机与应用》 * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114741060A (en) * | 2022-06-13 | 2022-07-12 | 浪潮通信技术有限公司 | Business system development method and device based on middle platform |
| CN116661756A (en) * | 2023-07-24 | 2023-08-29 | 浩鲸云计算科技股份有限公司 | Object analysis method and device based on low-code DSL |
| CN116661756B (en) * | 2023-07-24 | 2023-10-27 | 浩鲸云计算科技股份有限公司 | Object analysis method and device based on low-code DSL |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113885892B (en) | 2022-03-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113885892B (en) | Low code configuration access method based on multi-cloud platform | |
| US8775588B2 (en) | Method and apparatus for transforming web service policies from logical model to physical model | |
| US8707261B2 (en) | Service integration modeling and execution framework | |
| US10628132B2 (en) | Inversion of control framework for multiple behaviors of a process | |
| US8448216B2 (en) | Method and apparatus for orchestrating policies in service model of service-oriented architecture system | |
| CN109684054A (en) | Information processing method and device, electronic equipment and memory | |
| CN105531688B (en) | The service of resource as other services is provided | |
| US9201702B2 (en) | Integrated cloud data center management | |
| US11487584B2 (en) | Rule generation and tasking resources and attributes to objects system and method | |
| CN107885547A (en) | A kind of collocation method of application program, device, configuration equipment and storage medium | |
| CN111917587B (en) | Method for network service management by using service system and service system | |
| US11640307B2 (en) | Process initiation | |
| US20120030612A1 (en) | Dynamic property attributes | |
| CN110007924A (en) | The automated construction method and system of YANG model configuration interface | |
| US20170249170A1 (en) | Home system establishing method | |
| CN114254606A (en) | Microservice framework model | |
| WO2023015988A1 (en) | Cloud platform management architecture, method and device, and storage medium | |
| Borges et al. | Cloud restriction solver: A refactoring-based approach to migrate applications to the cloud | |
| CN106484452A (en) | A kind of unified configuring management method of software platform and device | |
| CN105302586A (en) | Software upgrade processing method and device, terminal and server | |
| US20220413843A1 (en) | Combining model-driven applications and canvas-type applications with application lifecycle management | |
| CN114253546A (en) | Code generation method and device, storage medium and electronic device | |
| US20200210153A1 (en) | Inversion of control framework for multiple behaviors on top of a process | |
| Srinivasmurthy et al. | Web2exchange: A model-based service transformation and integration environment | |
| CN106548331A (en) | A kind of method and device for determining distribution order |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |