CN112153156B - Data processing method and device for cloud service - Google Patents
Data processing method and device for cloud service Download PDFInfo
- Publication number
- CN112153156B CN112153156B CN202011045246.2A CN202011045246A CN112153156B CN 112153156 B CN112153156 B CN 112153156B CN 202011045246 A CN202011045246 A CN 202011045246A CN 112153156 B CN112153156 B CN 112153156B
- Authority
- CN
- China
- Prior art keywords
- cloud
- component
- custom
- script
- extension
- 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.)
- Active
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 22
- 238000013515 script Methods 0.000 claims abstract description 97
- 230000004044 response Effects 0.000 claims abstract description 22
- 238000000034 method Methods 0.000 claims description 34
- 238000012545 processing Methods 0.000 claims description 13
- 230000001960 triggered effect Effects 0.000 claims description 6
- 230000006870 function Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 8
- 238000004590 computer program Methods 0.000 description 7
- 230000008901 benefit Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000009434 installation Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the application discloses a data processing method for cloud service, which comprises the steps of firstly receiving a first adding request, wherein the first adding request is used for requesting to add custom attribute information of a cloud component; then, in response to receiving a first adding request, adding the custom attribute information of the cloud components into at least one type of cloud components to obtain a first extension component; adding the script of the cloud component into the first extension component to obtain a second extension component; finally, storing the second expansion component into a set of cloud components, wherein the set of cloud components is obtained by modeling cloud service resources and comprises at least one type of cloud components; by adding the custom attribute information and adding the cloud component script, the technical problem that the cloud component does not have expansibility is solved.
Description
Technical Field
The application relates to the technical field of cloud services, in particular to a data processing method and device for cloud services.
Background
The cloud service is to obtain required services in an on-demand and easily-extensible manner through a network, and to extend virtualized resources through the internet.
Aiming at the problems that in the related art, the components are updated based on the workflow tool, but due to the fact that service scenes are complex and changeable, and the workflow is difficult to maintain and multiplex due to the fact that cloud components are tightly coupled with the services, the components are updated by the workflow tool, and the expansibility of the components is poor.
Disclosure of Invention
The application mainly aims to provide a data processing method for cloud services, so as to solve the problem that components in the related art do not have expansibility.
In order to achieve the above object, in a first aspect, the present application provides a data processing method for a cloud service.
The data processing method for the cloud service comprises the following steps: receiving a first adding request, wherein the first adding request is used for requesting to add custom attribute information of the cloud component; in response to the first adding request, adding the custom attribute information of the cloud components into at least one type of cloud components to obtain a first extension component; adding the script of the cloud component into the first extension component to obtain a second extension component; and storing the second expansion component into a set of cloud components, wherein the set of cloud components is a set of cloud components obtained by modeling cloud service resources, and the set of cloud components comprises at least one type of cloud component.
In some embodiments, prior to storing the second extension component into the set of cloud components, the method further comprises: receiving a second adding request, wherein the first adding request is used for requesting to add a custom operation type of the cloud component; in response to receiving the second adding request, adding the custom operation type of the cloud component into at least one type of cloud component; binding the custom operation type of the cloud component with the script of the cloud component to obtain a second extension component; wherein storing the second extension component into the set of cloud components comprises: and storing the bound second extension component into the set of cloud components.
In some embodiments, after storing the second extension component into the set of cloud components, the method further comprises: in response to the at least one cloud component obtained from the cloud component set, modeling the at least one cloud component to obtain a cloud service framework; and releasing the cloud service framework to the cloud service directory.
In some embodiments, prior to storing the second extension component into the set of cloud components, the method further comprises: and modeling the cloud service resources in an object-oriented mode to obtain a set of cloud components.
In some embodiments, adding the script of the cloud component to the first extension component, resulting in a second extension component, comprises: and adding the preset script of the cloud component to the first extension component to obtain a second extension component.
In some embodiments, adding the script of the cloud component to the first extension component, resulting in a second extension component, comprises: and adding the self-defined script of the cloud component to the first extension component to obtain a second extension component.
In a second aspect, an embodiment of the present disclosure provides a data processing apparatus of a cloud service, including a first receiving unit configured to receive a first addition request, where the first addition request is used to request to add custom attribute information of a cloud component; the first adding unit is configured to add the custom attribute information of the cloud components to at least one type of cloud components in response to receiving a first adding request, and obtain a first extension component; the second adding unit is configured to add the script of the cloud component into the first extension component to obtain a second extension component; a storage unit configured to store the second extension component into a set of cloud components, wherein the set of cloud components is a set of cloud components obtained by modeling cloud service resources, and the set of cloud components includes at least one type of cloud component.
In some embodiments, the apparatus further comprises: a second receiving unit configured to receive a second adding request, wherein the first adding request is used for requesting to add a custom operation type of the cloud component; an adding unit configured to add the custom operation type of the cloud component to at least one type of cloud component in response to receiving the second addition request; the binding unit is configured to bind the custom operation type of the cloud component with the script of the cloud component to obtain a second extension component; wherein storing the second extension component into the set of cloud components comprises: and storing the bound second extension component into the collection of cloud components.
In some embodiments, the apparatus further comprises a modeling unit configured to model the at least one cloud component to obtain a cloud service framework in response to obtaining the at least one cloud component from the set of cloud components; the publishing unit is configured to publish the cloud service framework to the cloud service directory.
In some embodiments, the second adding unit is further configured to add a script of the customized cloud component to the first extension component, resulting in a second extension component.
In the embodiment of the application, a data processing method and a data processing device for cloud services are provided, and the method comprises the steps of firstly receiving a first adding request, wherein the first adding request is used for requesting to add custom attribute information of a cloud component; then, in response to receiving a first adding request, adding the custom attribute information of the cloud components into at least one type of cloud components to obtain a first extension component; adding the script of the cloud component into the first extension component to obtain a second extension component; finally, storing the second expansion component into a cloud component set, wherein the cloud component set is obtained by modeling cloud service resources and comprises at least one type of cloud component; by adding the custom attribute information and the cloud component script, the cloud component is expanded.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this application, serve to provide a further understanding of the application and to enable other features, objects, and advantages of the application to be more apparent. The drawings and the description of the exemplary embodiments of the present application are provided for explaining the present application and do not constitute an undue limitation on the present application. In the drawings:
fig. 1 is a flowchart of one embodiment of a data processing method for cloud services according to the present application;
FIG. 2 is a flow diagram of another embodiment of a data processing method for cloud services according to the present application;
fig. 3 is an application scenario diagram of an embodiment of a data processing method for cloud services according to the present application;
fig. 4 is a schematic structural diagram of an embodiment of a data processing apparatus for cloud services according to the present application.
Detailed Description
In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only partial embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the accompanying drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used may be interchanged under appropriate circumstances such that embodiments of the application described herein may be used. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
In this application, the terms "upper", "lower", "left", "right", "front", "rear", "top", "bottom", "inner", "outer", "middle", "vertical", "horizontal", "lateral", "longitudinal", and the like indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings. These terms are used primarily to better describe the present application and its embodiments, and are not used to limit the indicated devices, elements or components to a particular orientation or to be constructed and operated in a particular orientation.
Moreover, some of the above terms may be used to indicate other meanings besides the orientation or positional relationship, for example, the term "on" may also be used to indicate some kind of attachment or connection relationship in some cases. The specific meaning of these terms in this application will be understood by those of ordinary skill in the art as appropriate.
In addition, the term "plurality" shall mean two as well as more than two.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
Referring to fig. 1, fig. 1 shows a flow 100 of one embodiment of a data processing method for cloud services according to the present disclosure. The data processing method for the cloud service comprises the following steps:
In this embodiment, the execution subject may receive a first addition request sent by a client terminal device or other server device, where the first addition request may be triggered based on a class included in a selected cloud component, for example, a mouse device of the client clicks on the class included in the cloud component (for example, a parent class is selected), so as to trigger the addition request.
Specifically, the custom attribute information may be information that is not included in preset attribute information in the cloud component, and the attribute information input by the client may be used as the custom attribute information, and the custom attribute information is information for meeting cloud service resource deployment requirements and parameter control requirements, and may include a main key, a type, a default value, an option, and a description. For example, when creating a component Oracle, different application systems have specific requirements and custom requirements for the deployment requirements and parameter control of Oracle. The attribute can expose the configuration parameters to be filled in by the application components on the interface configuration by setting the custom attribute according to the deployment requirements of different systems, and transmits the custom parameters.
in this embodiment, when a client device selects a class of components, the components inherit all the property information and interface operations of the selected class, so that sub-classes have various properties and methods of parent classes without writing the same code again. When the sub-category inherits the parent category, the attribute information contained in the parent category can be redefined, and some methods are rewritten, namely the original attribute information and methods of the parent category are covered, so that the sub-category can obtain different functions from the parent category. And the execution main body adds the self-defined attribute information to the selected cloud component of a certain type to obtain a first extension component.
For example, when component type Software is selected, the Software is used as a parent class, an Oracle component can be created, the Oracle component can have various attributes of the parent class Software component, and the attribute information can be customized to enable the Oracle component to obtain different functions from the parent class. And when the key value of the attribute information added by the user definition is the same as the key value of the attribute information in the parent component, the attribute definition in the parent component is covered.
In this embodiment, each stage of the component lifecycle is controlled by a script, which benefits from a powerful underlying class library, and supports self-definition scripts including secure, terrafrorm, shell, powershell, json, yaml, python, text, and the like. In the "script List" view, you can add a script file by creating a new file. After adding the custom attribute information, the execution main body transmits the custom attribute item as a custom parameter to the script of the component, and based on the transmitted custom parameter, the execution main body can search the script associated with the custom parameter in a script list and add the script to the first extension component; the execution main body can also add a custom script based on the custom parameters, the added custom script and add the custom script to the first extension component.
As some optional implementation manners of this embodiment, adding a script of a cloud component to the first extension component to obtain a second extension component includes: and adding the preset script of the cloud component to the first extension component to obtain a second extension component.
In this embodiment, after adding the custom attribute information, the execution subject transmits the custom attribute item as a custom parameter to the script of the component, and based on the transmitted custom parameter, the execution subject may search for a preset script associated with the custom parameter in a preset script list, and add the preset script to the first extension component.
As some optional implementation manners of this embodiment, adding a script of a cloud component to the first extension component to obtain a second extension component includes: adding the self-defined script of the cloud component to the first extension component to obtain a second extension component
In this embodiment, a custom script may also be added based on the custom parameter, and the custom script is added to the first extension component.
As an optional implementation manner of this embodiment, before storing the second extension component in the set of cloud components, the method further includes: receiving a second adding request, wherein the first adding request is used for requesting to add a custom operation type of the cloud component; in response to receiving the second addition request, adding the custom operation type of the cloud component into at least one type of cloud component; binding the custom operation type of the cloud component with the script of the cloud component to obtain a second extension component; wherein storing a second extension component into the set of cloud components comprises: and storing the second bound extension component into a set of cloud components.
In this embodiment, the operations include various types (e.g., refresh operation, create operation, etc.) to perform a complete lifecycle management for the creation, configuration, start, stop, deletion, etc. of the application system. All software configuration work from installation deployment to due uninstallation is completed through corresponding to the script
Specifically, the second addition request may be triggered based on an input of the client device, and after the execution subject receives an input operation request of the client, the custom operation type requested to be input is added to the cloud component, so that the operation type is bound with a script in the cloud component.
More specifically, the execution main body may directly add the customized operation type to the unexpanded cloud component, or add the customized operation type to the first extension component obtained by adding the customized property, or add the customized operation type to the second extension component obtained by adding the script, to finally obtain the second extension component (new extension component), and bind the second extension component to the script in the cloud component, where the binding mode may be binding by using the existing technology or binding by using a binding release available in the future.
And 104, storing the second expansion component into a cloud component set, wherein the cloud component set is obtained by modeling cloud service resources, and the cloud component set comprises at least one type of cloud component.
In this embodiment, the executing entity stores the second extension component obtained in step 103 into a set of cloud components, where the set of cloud components is obtained based on modeling of cloud service resources, and the types of cloud components may include a custom type, such as a class type, a Pass type, and a Software type, or other custom types.
In some optional implementations of this embodiment, before storing the second extension component in the set of cloud components, the method further includes modeling the cloud service resources in an object-oriented manner to obtain the set of cloud components.
In this embodiment, the object-oriented approach is used to organize the related data and methods into a whole for modeling the system. The modeling mode can be used for modeling the cloud service resources by using a component mode, wherein the cloud service resources can be any resources such as software resources, infrastructure resources or container resources and the like; the modeling mode can also be a future modeling mode for modeling, so that the cloud service component is obtained.
The data processing method for the cloud service, provided by the embodiment of the application, comprises the steps of firstly receiving a first adding request, wherein the first adding request is used for requesting to add custom attribute information of a cloud component; then, in response to receiving a first adding request, adding the custom attribute information of the cloud components into at least one type of cloud components to obtain a first extension component; adding the script of the cloud component into the first extension component to obtain a second extension component; finally, storing the second expansion component into a cloud component set, wherein the cloud component set is obtained by modeling cloud service resources and comprises at least one type of cloud component; by adding the custom attribute information and the cloud component script, the cloud component is expanded.
With further reference to fig. 2, fig. 2 shows a flow of another embodiment of a data processing method for cloud services according to the present application, the data processing method for cloud services comprising the steps of:
step 201: receiving a first adding request, wherein the first adding request is used for requesting to add custom attribute information of the cloud component;
in this embodiment, the execution subject may receive a first addition request sent by the client, where the first addition request may be triggered based on the client device selecting a class included in the cloud component, for example, a mouse device of the client clicks on the class included in the cloud component (for example, a parent class is selected), so as to trigger the addition request.
Specifically, the custom attribute information may be information that is not included in preset attribute information in the cloud component, and the attribute information input by the client may be used as the custom attribute information, and the custom attribute information is information for meeting cloud service resource deployment requirements and parameter control requirements, and may include a main key, a type, a default value, an option, and a description. For example, when creating a component Oracle, different application systems have specific requirements and custom requirements for the deployment requirements and the parameter control of Oracle. The attribute can expose the configuration parameters to be filled in by the application components on the interface configuration by setting the custom attribute according to the deployment requirements of different systems, and transmits the custom parameters.
in this embodiment, when a client device selects a class of components, the components inherit all the property information and interface operations of the selected class, so that sub-classes have various properties and methods of parent classes without writing the same code again. When the sub-category inherits the parent category, some attribute information contained in the parent category can be redefined, and some methods are rewritten, namely original attribute information and methods of the parent category are covered, so that functions different from those of the parent category are obtained. And the execution main body adds the self-defined attribute information to the selected cloud component of a certain type to obtain a first extension component.
For example, when component type Software is selected, the Software is used as a parent class, an Oracle component can be created, the Oracle component can have various attributes of the parent class Software component, and the attribute information can be customized to enable the Oracle component to obtain different functions from the parent class. And when the key value of the attribute information added by self definition is the same as the key value of the attribute information in the parent component, the attribute definition in the parent component is covered.
In this embodiment, each stage of the component lifecycle is controlled by a script, which benefits from a powerful underlying class library and supports self-definition of scripts including anchor, terrafrorm, shell, powershell, json, yaml, python, text, and the like. In the "script List" view, you can add a script file by creating a new file. After adding the custom attribute information, the execution main body transmits the custom attribute item as a custom parameter to the script of the component, and based on the transmitted custom parameter, the execution main body can search the script associated with the custom parameter in a script list and add the script to the first extension component; the execution main body can also add a custom script based on the custom parameters, the added custom script and add the custom script to the first extension component.
As some optional implementation manners of this embodiment, adding a script of a cloud component to the first extension component to obtain a second extension component includes: and adding the preset script of the cloud component to the first extension component to obtain a second extension component.
In this embodiment, after adding the custom attribute information, the execution subject transmits the custom attribute item as a custom parameter to the script of the component, and based on the transmitted custom parameter, the execution subject may search for a preset script associated with the custom parameter in a preset script list, and add the preset script to the first extension component.
As some optional implementation manners of this embodiment, adding a script of a cloud component to the first extension component to obtain a second extension component includes: adding the self-defined script of the cloud component to the first extension component to obtain a second extension component
In this embodiment, a customized script may also be added based on the customized parameter, and the customized script is added to the first extension component.
As an optional implementation manner of this embodiment, before storing the second extension component in the set of cloud components, the method further includes: receiving a second adding request, wherein the first adding request is used for requesting to add a custom operation type of the cloud component; in response to receiving the second addition request, adding the custom operation type of the cloud component into at least one type of cloud component; binding the custom operation type of the cloud component with the script of the cloud component to obtain a second extension component; wherein storing a second extension component into the set of cloud components comprises: and storing the second bound extension component into a set of cloud components.
In this embodiment, the operations include various types (e.g., refresh operation, create operation, etc.) to perform a complete lifecycle management for the creation, configuration, start, stop, deletion, etc. of the application system. All software configuration work from installation deployment to due uninstallation is completed through corresponding to the script
Specifically, the second addition request may be triggered based on an input of the client device, and after the execution main body receives an input operation request of the client, the custom operation type requested to be input is added to the cloud component, so that the operation type is bound with a script in the cloud component.
More specifically, the execution main body may directly add the customized operation type to the unexpanded cloud component, or add the customized operation type to the first extension component obtained by adding the customized property, or add the customized operation type to the second extension component obtained by adding the script, to finally obtain the second extension component (new extension component), and bind the second extension component to the script in the cloud component, where the binding mode may be binding by using the existing technology or binding by using a binding release available in the future.
And 204, storing the second expansion component in a cloud component set, wherein the cloud component set is obtained by modeling cloud service resources, and the cloud component set comprises at least one type of cloud component.
In this embodiment, the executing entity stores the second extension component obtained in step 103 into a set of cloud components, where the set of cloud components is obtained based on modeling of cloud service resources, and the types of cloud components may include a custom type, such as a class type, a Pass type, and a Software type, or other custom types.
In some optional implementations of this embodiment, before storing the second extension component in the set of cloud components, the method further includes modeling the cloud service resources in an object-oriented manner to obtain the set of cloud components.
In the embodiment, an object-oriented mode is used for organizing related data and methods into a whole to be used for modeling the system. The modeling mode can be used for modeling the cloud service resources by using a component mode, wherein the cloud service resources can be any resources such as software resources, infrastructure resources or container resources and the like; the modeling mode can also be a future modeling mode for modeling, so that the cloud service component is obtained.
In this embodiment, after the execution subject acquires any one or more cloud components, the acquired cloud components are modeled to obtain a cloud service framework, and the cloud service framework is published to a cloud service directory. The cloud component can be obtained by sending the cloud component to the execution main body in a dragging mode based on the client device, after the cloud component is obtained, the execution main body can model the cloud component to obtain a cloud service framework, the obtained cloud service framework can be obtained by adopting the existing modeling mode or a future available mode, and the cloud service framework is released to the cloud service directory after the cloud service framework is obtained. After being published to the cloud service directory, cloud resources can also be deployed. Referring to fig. 3, fig. 3 shows an application scenario diagram of the embodiment, after the cloud component is obtained, the cloud component is modeled to obtain a cloud service framework, and after the cloud service framework is obtained, the cloud service framework is released to a cloud service directory. After being published to the cloud service directory, cloud resources can also be deployed.
As can be seen from fig. 2, unlike the embodiment shown in fig. 1, the present embodiment highlights that, in response to acquiring at least one cloud component from a set of cloud components, modeling the at least one cloud component to obtain a cloud service framework; and releasing the cloud service framework to the cloud service directory. The cloud service functions can be expanded by further blue-mapping any cloud component (including unexpanded and expanded cloud components) to obtain a cloud service framework and publishing the cloud service framework to a cloud service directory.
Referring to fig. 4, as an implementation of the methods shown in the above figures, the present application provides an embodiment of an apparatus for cloud service data processing, where the apparatus embodiment corresponds to the method embodiment shown in fig. 1, and the apparatus may be specifically applied to various electronic devices.
As shown in fig. 4, the data processing apparatus 300 for cloud service of the present embodiment includes: a first receiving unit 401, a first adding unit 402, a second adding unit 403, and a storing unit 404. The first receiving unit 401 is configured to receive a first addition request, where the first addition request is used for requesting to add custom attribute information of a cloud component; a first adding unit, configured to add the custom attribute information of the cloud component to the at least one type of cloud component in response to receiving a first adding request, resulting in a first extended component; the second adding unit is configured to add the script of the cloud component into the first extension component to obtain a second extension component; the storage unit is configured to store the second extension component into a set of cloud components, wherein the set of cloud components is a set of cloud components obtained by modeling cloud service resources, and the set of cloud components comprises at least one type of cloud component.
In this embodiment, for specific processing of the first receiving unit 401, the first adding unit 402, the second adding unit 403, and the storage unit 404 in the data processing apparatus 400 for cloud service and beneficial effects brought by the specific processing, reference may be made to the description of the implementation manners of steps 401 to 404 in the embodiment corresponding to fig. 1, and details are not repeated here.
In some optional implementations of this embodiment, the apparatus 400 further includes: a second receiving unit (not shown) configured to receive a second addition request, wherein the first addition request is used for requesting to add a custom operation type of the cloud component; an adding unit configured to add the custom operation type of the cloud component to at least one type of cloud component in response to receiving the second addition request; the binding unit is configured to bind the custom operation type of the cloud component with the script of the cloud component to obtain a second extension component; wherein storing the second extension component into the set of cloud components comprises: and storing the bound second extension component into the set of cloud components.
In some optional implementations of this embodiment, the apparatus further includes: the modeling unit is configured to respond to the acquisition of the at least one cloud component from the cloud component set, model the at least one cloud component and obtain a cloud service framework; a publishing unit configured to publish the cloud service framework into a cloud service directory.
In some optional implementations, the second adding unit is further configured to add a script of the customized cloud component to the first extension component, resulting in a second extension component.
According to an embodiment of the present disclosure, the processes described above with reference to the flow charts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication section, and/or installed from a removable medium. The computer program, when executed by a central processing unit, performs the above-described functions defined in the method of the present application. It should be noted that the computer readable medium described herein can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The above description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (10)
1. A data processing method for cloud services is characterized by comprising the following steps:
receiving a first adding request, wherein the first adding request is used for requesting to add custom attribute information of the cloud component; wherein the first add request is triggered based on a class included in the selected cloud component; the custom attribute information is information used for meeting the cloud service resource deployment requirement and the parameter control requirement;
in response to receiving the first adding request, adding the custom attribute information of the cloud component into the at least one type of cloud component to obtain a first extension component; after the client device selects the class of the component, the component inherits all attribute information and interface operation of the selected class, so that the sub-class has the attribute and method of the parent class; or when the sub-category inherits the parent category, the original attribute information and method of the parent category are covered, so that the sub-category has a function different from that of the parent category;
adding a script of a cloud component into the first extension component to obtain a second extension component;
storing a second expansion component into the set of cloud components, wherein the set of cloud components is a set of cloud components obtained by modeling cloud service resources, and the set of cloud components comprises at least one type of cloud component; wherein each stage of the component lifecycle is controlled by the script; after adding the custom attribute information, transmitting the custom attribute item as a custom parameter to the script of the component, based on the transmitted custom parameter, the execution main body can search the script associated with the custom parameter in the script list and add the script to the first extension component; the execution main body can also add a custom script based on the custom parameters, the added custom script and add the custom script to the first extension component.
2. The data processing method for cloud services of claim 1, wherein prior to storing a second extension component into the set of cloud components, the method further comprises:
receiving a second adding request, wherein the second adding request is used for requesting to add a custom operation type of the cloud component;
in response to receiving the second addition request, adding a custom operation type of a cloud component to the at least one type of cloud component;
binding the custom operation type of the cloud component with the script of the cloud component to obtain the second extension component;
wherein storing a second extension component into the set of cloud components comprises: and storing the second bound extension component into a set of cloud components.
3. The data processing method for the cloud service according to claim 1 or 2, wherein after storing a second extension component into the set of cloud components, the method further comprises:
in response to the at least one cloud component obtained from the cloud component set, modeling the at least one cloud component to obtain a cloud service framework;
and releasing the cloud service framework to a cloud service directory.
4. The data processing method for cloud services of claim 1, wherein prior to storing a second extension component into the set of cloud components, the method further comprises:
and modeling the cloud service resources in an object-oriented mode to obtain a set of cloud components.
5. The data processing method for the cloud service according to claim 1, wherein adding a script of a cloud component to the first extension component to obtain a second extension component comprises:
and adding a preset script of the cloud component to the first extension component to obtain a second extension component.
6. The data processing method for the cloud service according to claim 1, wherein adding a script of a cloud component to the first extension component to obtain a second extension component comprises:
and adding the self-defined script of the cloud component to the first extension component to obtain a second extension component.
7. A data processing apparatus for cloud services, comprising:
a first receiving unit configured to receive a first addition request, wherein the first addition request is used for requesting to add custom attribute information of a cloud component; wherein the first add request is triggered based on a class included in the selected cloud component; the custom attribute information is information used for meeting the cloud service resource deployment requirement and the parameter control requirement;
a first adding unit configured to add the custom attribute information of the cloud component to the at least one type of cloud component in response to receiving the first adding request, so as to obtain a first extended component; after the client device selects the class of the component, the component inherits all attribute information and interface operation of the selected class, so that the sub-class has the attribute and the method of the parent class; or when the sub-category inherits the parent category, the original attribute information and method of the parent category are covered, so that the sub-category has a function different from that of the parent category;
a second adding unit configured to add a script of a cloud component to the first extension component, resulting in a second extension component;
a storage unit configured to store a second extension component into the set of cloud components, wherein the set of cloud components is a set of cloud components obtained by modeling cloud service resources, and the set of cloud components includes at least one type of cloud component; wherein each stage of the component lifecycle is controlled by the script; after adding the custom attribute information, transmitting the custom attribute item as a custom parameter to the script of the component, based on the transmitted custom parameter, the execution main body can search the script associated with the custom parameter in the script list and add the script to the first extension component; the execution main body can also add a custom script based on the custom parameters, the added custom script and add the custom script to the first extension component.
8. The data processing apparatus for cloud services of claim 7, wherein the apparatus further comprises:
a second receiving unit configured to receive a second addition request, wherein the second addition request is used for requesting to add a custom operation type of a cloud component;
an adding unit configured to add a custom operation type of a cloud component to the at least one type of cloud component in response to receiving the second addition request;
the binding unit is configured to bind the custom operation type of the cloud component with the script of the cloud component to obtain the second extension component;
wherein storing a second extension component into the set of cloud components comprises: and storing the second bound extension component into a set of cloud components.
9. The data processing apparatus for cloud services of claim 7, wherein the apparatus further comprises:
the modeling unit is configured to respond to the acquisition of the at least one cloud component from the cloud component set, model the at least one cloud component and obtain a cloud service framework;
a publishing unit configured to publish the cloud service framework into a cloud service directory.
10. The data processing apparatus for cloud services of claim 7, wherein the second adding unit is further configured to add a script of a customized cloud component to the first extension component, resulting in a second extension component.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011045246.2A CN112153156B (en) | 2020-09-28 | 2020-09-28 | Data processing method and device for cloud service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011045246.2A CN112153156B (en) | 2020-09-28 | 2020-09-28 | Data processing method and device for cloud service |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112153156A CN112153156A (en) | 2020-12-29 |
| CN112153156B true CN112153156B (en) | 2023-01-10 |
Family
ID=73895895
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011045246.2A Active CN112153156B (en) | 2020-09-28 | 2020-09-28 | Data processing method and device for cloud service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112153156B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8261295B1 (en) * | 2011-03-16 | 2012-09-04 | Google Inc. | High-level language for specifying configurations of cloud-based deployments |
| CN108495192A (en) * | 2018-03-13 | 2018-09-04 | 武汉斗鱼网络科技有限公司 | Page editing processing method and processing device |
| CN110554874A (en) * | 2019-09-12 | 2019-12-10 | 北京百度网讯科技有限公司 | Method and device for reusing webpage components of SaaS platform |
-
2020
- 2020-09-28 CN CN202011045246.2A patent/CN112153156B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8261295B1 (en) * | 2011-03-16 | 2012-09-04 | Google Inc. | High-level language for specifying configurations of cloud-based deployments |
| CN108495192A (en) * | 2018-03-13 | 2018-09-04 | 武汉斗鱼网络科技有限公司 | Page editing processing method and processing device |
| CN110554874A (en) * | 2019-09-12 | 2019-12-10 | 北京百度网讯科技有限公司 | Method and device for reusing webpage components of SaaS platform |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112153156A (en) | 2020-12-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US12327093B2 (en) | Executing a process-based software application in a first computing environment and a second computing environment | |
| US8527985B2 (en) | Techniques for rapid deployment of service artifacts | |
| CN114115852A (en) | Visual service orchestration method, device, device and medium | |
| US11132114B2 (en) | Method and apparatus for generating customized visualization component | |
| CN104636139A (en) | Visualized cross-platform mobile application development and generation system | |
| CN112051993A (en) | State machine template generation and task processing method, device, medium and equipment | |
| CN108279882B (en) | Framework generation method, device, equipment and computer readable medium | |
| US10545736B1 (en) | Conversion of interpretive language functions into web applications or services | |
| CN112860247A (en) | Custom generation method, device, equipment and medium for model component | |
| CN117539459B (en) | API interface configuration method, system and equipment | |
| KR101086620B1 (en) | Server and operation method for smart office system and operation | |
| CN114217842A (en) | A general visual resource directory configuration method and system | |
| CN119089881A (en) | Method, device, electronic device and storage medium for processing workflow in table | |
| CN109814915B (en) | Parameter configuration method, device, medium and electronic equipment based on lua | |
| CN110263932B (en) | Multi-agent simulation system graphical combination construction method and device | |
| CN112153156B (en) | Data processing method and device for cloud service | |
| CN111782251A (en) | Software function module updating method and device and computer equipment | |
| CN114675921B (en) | A method, device, electronic device and storage medium for customizing interface | |
| CN117035664A (en) | Template-based trust approval standardized processing method, device, equipment and medium | |
| CN111367500A (en) | Data processing method and device | |
| CN116225394A (en) | Method, device, electronic equipment and storage medium for creating cloud development environment | |
| CN111124386B (en) | Animation event processing method, device, equipment and storage medium based on Unity | |
| US9372669B2 (en) | Multiple architecture viewpoints in single unified modeling language (UML) model | |
| CN117406980A (en) | Model drive development method, device, equipment and storage medium | |
| CN110704537A (en) | Intelligent contract generation method, device, equipment and storage medium |
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 |