CN112866306B - Resource management method and cloud service platform - Google Patents
Resource management method and cloud service platform Download PDFInfo
- Publication number
- CN112866306B CN112866306B CN201911100611.2A CN201911100611A CN112866306B CN 112866306 B CN112866306 B CN 112866306B CN 201911100611 A CN201911100611 A CN 201911100611A CN 112866306 B CN112866306 B CN 112866306B
- Authority
- CN
- China
- Prior art keywords
- resource
- cloud
- cloud resource
- account
- request
- 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
- 238000007726 management method Methods 0.000 title claims abstract description 23
- 238000000034 method Methods 0.000 claims abstract description 36
- 238000012217 deletion Methods 0.000 claims description 57
- 230000037430 deletion Effects 0.000 claims description 57
- 238000004590 computer program Methods 0.000 claims description 10
- 238000010586 diagram Methods 0.000 description 20
- 230000006870 function Effects 0.000 description 8
- 230000005540 biological transmission Effects 0.000 description 4
- 238000003491 array Methods 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000001902 propagating effect Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- RYGMFSIKBFXOCR-UHFFFAOYSA-N Copper Chemical compound [Cu] RYGMFSIKBFXOCR-UHFFFAOYSA-N 0.000 description 1
- 229910052802 copper Inorganic materials 0.000 description 1
- 239000010949 copper Substances 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000011022 operating instruction Methods 0.000 description 1
- 230000008447 perception Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The disclosure relates to a resource management method and a cloud service platform. The method is applied to a cloud service platform, and comprises the following steps: receiving a resource creation request sent by a first account, wherein the resource creation request is used for requesting to create a first cloud resource based on a first cloud product, a data dependency relationship exists between the first cloud resource and a second cloud resource, and the second cloud resource is a cloud resource created by a second account based on a second cloud product; creating a resource relationship tag, wherein the resource relationship tag is used for indicating the data dependency relationship between the first cloud resource and the second cloud resource to the second cloud resource; and sending the resource relation label to the second account. According to the method and the device, the cloud resources in the cloud service platform can be effectively managed across account numbers and products, and therefore the use experience of a user on the cloud service platform is improved.
Description
Technical Field
The disclosure relates to the technical field of computers, in particular to a resource management method and a cloud service platform.
Background
In the cloud service platform, an association relationship may exist between cloud resources in different cloud products under different accounts. When cloud resources with data dependency relationships exist among different cloud products under different account numbers, the cloud products with the data dependency Fang Yun resources can sense the data dependency relationships among the cross-product, but the cloud products with the data dependent Fang Yun resources cannot sense the data dependency relationships among the cross-product, so that the cloud resources in the cloud service platform cannot be effectively managed.
Disclosure of Invention
In view of this, the disclosure provides a resource management method and a cloud service platform, so that cross-account and cross-product effective management can be implemented on cloud resources in the cloud service platform, and further user experience of a user on the cloud service platform is improved.
According to a first aspect of the present disclosure, there is provided a resource management method, the method being applied to a cloud service platform, the method comprising: receiving a resource creation request sent by a first account, wherein the resource creation request is used for requesting to create a first cloud resource based on a first cloud product, a data dependency relationship exists between the first cloud resource and a second cloud resource, and the second cloud resource is a cloud resource created by a second account based on a second cloud product; creating a resource relationship tag, wherein the resource relationship tag is used for indicating the data dependency relationship between the first cloud resource and the second cloud resource to the second cloud resource; and sending the resource relation label to the second account.
In one possible implementation manner, the resource relationship tag includes: the identification of the first cloud product, the identification of the first cloud resource, and the attribute name of the first cloud resource.
In one possible implementation, the method further includes: receiving a de-reliance request sent by the second account, wherein the de-reliance request is used for requesting to release the data dependency relationship between the first cloud resource and the second cloud resource; responding to the de-dependency request, and releasing the data dependency relationship between the first cloud resource and the second cloud resource; receiving a first deletion request sent by the second account, wherein the first deletion request is used for requesting to delete the second cloud resource; and responding to the first deleting request, and executing deleting operation on the second cloud resource.
In one possible implementation, the method further includes: and sending a second deletion request to the first account, so that the first account executes a deletion operation on the first cloud resource by responding to the second deletion request.
According to a second aspect of the present disclosure, there is provided a cloud service platform, comprising: the receiving module is used for receiving a resource creation request sent by a first account, wherein the resource creation request is used for requesting to create a first cloud resource based on a first cloud product, a data dependency relationship exists between the first cloud resource and a second cloud resource, and the second cloud resource is a cloud resource created by a second account based on a second cloud product; the label creation module is used for creating a resource relation label, wherein the resource relation label is used for indicating the data dependency relationship between the first cloud resource and the second cloud resource to the second cloud resource; and the sending module is used for sending the resource relation tag to the second account.
In one possible implementation manner, the resource relationship tag includes: the identification of the first cloud product, the identification of the first cloud resource, and the attribute name of the first cloud resource.
In one possible implementation manner, the cloud service platform further includes: a dependency release module and a deletion module; the receiving module is further configured to receive a de-dependency request sent by the second account, where the de-dependency request is used to request to release a data dependency relationship between the first cloud resource and the second cloud resource; the dependency relation releasing module is used for responding to the de-dependency request and releasing the data dependency relation between the first cloud resource and the second cloud resource; the receiving module is further configured to receive a first deletion request sent by the second account, where the first deletion request is used to request deletion of the second cloud resource; and the deleting module is used for responding to the first deleting request and executing deleting operation on the second cloud resource.
In a possible implementation manner, the sending module is further configured to send a second deletion request to the first account, so that the first account performs a deletion operation on the first cloud resource by responding to the second deletion request.
According to a third aspect of the present disclosure, there is provided a cloud service platform, comprising: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to perform the resource management method of the first aspect.
According to a fourth aspect of the present disclosure, there is provided a non-transitory computer readable storage medium having stored thereon computer program instructions, wherein the computer program instructions, when executed by a processor, implement the resource management method of the first aspect described above.
In the cloud service platform, a resource creation request sent by a first account number and used for requesting to create a first cloud resource based on a first cloud product is received, a data dependency relationship exists between the first cloud resource and a second cloud resource created by a second account number based on a second cloud product, a resource relationship tag used for indicating the data dependency relationship between the first cloud resource and the second cloud resource to the second cloud resource is created, and the resource relationship tag is sent to the second account number, so that the cloud resource in the cloud service platform can be effectively managed across accounts and products, and the use experience of a user on the cloud service platform is improved.
Other features and aspects of the present disclosure will become apparent from the following detailed description of exemplary embodiments, which proceeds with reference to the accompanying drawings.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments, features and aspects of the present disclosure and together with the description, serve to explain the principles of the disclosure.
FIG. 1 illustrates a schematic view of a scenario of resource management in a cloud service platform according to an embodiment of the present disclosure;
Fig. 2 is a schematic diagram illustrating a relationship among an elastic container instance, a cloud server, and an elastic network card in a cloud service platform according to an embodiment of the disclosure;
FIG. 3 shows a flow diagram of a resource management method of an embodiment of the present disclosure;
FIG. 4 shows a schematic diagram of resource management in a cloud services platform according to an embodiment of the present disclosure;
fig. 5 illustrates a schematic structural diagram of a cloud service platform according to an embodiment of the present disclosure;
Fig. 6 shows a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.
Detailed Description
Various exemplary embodiments, features and aspects of the disclosure will be described in detail below with reference to the drawings. In the drawings, like reference numbers indicate identical or functionally similar elements. Although various aspects of the embodiments are illustrated in the accompanying drawings, the drawings are not necessarily drawn to scale unless specifically indicated.
The word "exemplary" is used herein to mean "serving as an example, embodiment, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.
In addition, numerous specific details are set forth in the following detailed description in order to provide a better understanding of the present disclosure. It will be understood by those skilled in the art that the present disclosure may be practiced without some of these specific details. In some instances, methods, means, elements, and circuits well known to those skilled in the art have not been described in detail in order not to obscure the present disclosure.
The cloud service platform provides various cloud products for users, the users can log in the cloud service platform based on the account numbers of the users, and cloud resources needed by the users can be created in the cloud service platform based on the cloud products provided by the cloud service platform. Data dependency may exist between cloud resources created by different users (corresponding to different accounts) based on different cloud products. The data dependency relationship between two cloud resources refers to that when one cloud resource changes in data, the normal use of the other cloud resource is affected. For example, when cloud resource 2 is configuration information when cloud resource 1 is created, a data dependency relationship exists between cloud resource 1 and cloud resource 2, cloud resource 1 is a data relying party in the data dependency relationship, and cloud resource 2 is a data relied party in the data dependency relationship.
In practical application, whether data dependency relationship exists between different cloud resources is predetermined by hardware logic at the bottom of the cloud service platform, which is not specifically limited in the disclosure. For example, when a cloud server (Elastic Computer Service, ECS) is required to be used as configuration information in creating the elastic container instance (Elastic Container Instance, ECI), a data dependency exists between the ECI and the ECS.
Fig. 1 illustrates a schematic view of a scenario of resource management in a cloud service platform according to an embodiment of the present disclosure. As shown in fig. 1, a user a creates a cloud resource A1 based on a cloud product a in a cloud service platform, a data dependency relationship exists between the cloud resource A1 and a cloud resource B1 created by a user B based on a cloud product B in the cloud service platform (for example, the cloud resource B1 is included in configuration information when the cloud resource A1 is created), and a data dependency relationship exists between the cloud resource B1 and a cloud resource A2 created by the user a based on the cloud product a in the cloud service platform. Currently, such data dependencies are only perceptible to the data relying party, and not perceptible to the relying party. Because the user a creates the cloud resource A1 based on the cloud product a, the user a knows that the cloud resource B1 is included in the configuration information at the time of creation, that is, the user a can perceive the data dependency relationship between the cloud resource A1 and the cloud resource B1 as a data relying party. Because the user B does not know the creation of the cloud resource a by the user a, the user B, as a data depended party, cannot perceive the data dependency relationship between the cloud resource A1 and the cloud resource B1. Similarly, the user B as a data relying party can perceive the data dependency relationship between the cloud resource B1 and the cloud resource A2, and the user a as a data relying party cannot perceive the data dependency relationship between the cloud resource B1 and the cloud resource A2.
The perception manner of the data dependency relationship cannot effectively manage the cloud resources, for example, because the data dependency relationship exists between the cloud resources A1 and the cloud resources B1, when the data dependency relationship is not released, in order to ensure normal use of the cloud resources A1, the cloud resources B1 cannot be deleted, but because the user B as data by a relying party cannot perceive the data dependency relationship between the cloud resources A1 and the cloud resources B1, the user B cannot execute a deletion operation on the cloud resources B1 created by the user B in the cloud service platform, and the reason why the cloud resources B1 cannot be deleted cannot be determined.
Fig. 2 is a schematic diagram illustrating a relationship among an elastic container instance, a cloud server, and an elastic network card in a cloud service platform according to an embodiment of the disclosure. As shown in fig. 2, for cloud products in the cloud service platform, there is a data dependency relationship between the ECI and the cloud server under the ECI account. The user-defined private network (Virtual Private Cloud, VPC) is opened by mounting the user's elastic network card (Elastic Network Interface, ENI) to the ECS under the ECI account, so that the association between the user service and the ECS is opened, and the user can perform cloud product instance creation and cloud product instance management based on the VPC. As can be seen from fig. 2, the user's ENI network card is created by the ECI account for the user, so that in order to facilitate the user to manage his own network card, to avoid the occurrence of erroneous deletion, the user needs to be informed of the source of the ENI network card and the ECI instance specifically corresponding to the ENI network card, that is, the cloud resource in the cloud service platform needs to be effectively managed across accounts and products.
In the related art, because the cloud resources in the cloud service platform cannot be effectively managed across accounts and products, the ECS deletion fails, and a Virtual Machine (VM) appears, so that the resources in the cloud service platform are wasted.
The resource management method provided by the disclosure can be applied to the scenes of the cloud service platform shown in fig. 1 and/or fig. 2, so that the cloud resources in the cloud service platform can be effectively managed across accounts and products, and the use experience of a user on the cloud service platform is improved.
In one example of the present disclosure, a user logs into a cloud service platform through a user account (first account), sends a resource creation request for creating an ENI (first cloud resource) based on an ECS (first cloud product) to the cloud service platform, the cloud service platform receives the resource creation request, the cloud service platform determines that there is a data dependency relationship between the ENI and an ECI instance (second cloud resource) based on underlying hardware logic, the ECI instance is created based on the ECS (second cloud product) for the ECI account (second account), and the cloud service platform creates the ENI for the user in response to the resource creation request. In order to enable an ECI instance (second cloud resource) to perceive a data dependency relationship between the ECI instance (second cloud resource) and an ENI (first cloud resource), the cloud service platform creates a resource relationship tag for indicating the data dependency relationship between the ENI (first cloud resource) and the ECI instance (second cloud resource) to the ECI instance (second cloud resource), and sends the resource relationship tag to an ECI account (second account) such that the ECI account (second account) tags the ECI instance (second cloud resource) according to the resource relationship tag. Therefore, the user and the ECI account can determine the source of the ENI (first cloud resource) and the ECI instance (second cloud resource) corresponding to the source, and management of the ENI (first cloud resource) can be effectively achieved. For example, when an ECI instance (second cloud resource) needs to be deleted, the data dependency relationship between the ENI (first cloud resource) and the ECI instance (second cloud resource) needs to be released according to the resource relationship label, so that deletion of the ECI instance (second cloud resource) can be realized; the system comprises an ECI (first cloud resource) and an ECI (second cloud resource), wherein the ECI (first cloud resource) is used for storing data, and the ECI (second cloud resource) is used for storing data.
The resource management method provided by the present disclosure is described in detail below. It should be understood by those skilled in the art that the cloud products and cloud resources mentioned in the present disclosure may include other cloud products and cloud resources besides the ECS, ECI instance, and ENI described above, and the specific cloud products and cloud resources do not limit the present disclosure.
Fig. 3 shows a flow diagram of a resource management method of an embodiment of the present disclosure. The method shown in fig. 3 may be applied to a cloud service platform, and as shown in fig. 3, the method may include:
Step S31, a resource creation request sent by a first account is received, wherein the resource creation request is used for requesting to create a first cloud resource based on a first cloud product, a data dependency relationship exists between the first cloud resource and a second cloud resource, and the second cloud resource is a cloud resource created by a second account based on a second cloud product.
Step S32, creating a resource relation tag, wherein the resource relation tag is used for indicating the data dependency relationship between the first cloud resource and the second cloud resource to the second cloud resource.
And step S33, sending the resource relation label to the second account.
The first user logs in the cloud service platform through the first account number, and then a resource creation request for requesting to create a first cloud resource based on the first cloud product is sent to the cloud service platform. The cloud service platform receives the resource creation request sent by the first user based on the first account number, determines that the first cloud resource and the second cloud resource have a data dependency relationship (for example, the cloud service platform can determine that the first cloud resource and the second cloud resource have a data dependency relationship based on inherent underlying logic between cloud products), and the second cloud resource is a cloud resource created by the second account number (the second user) based on the second cloud product, and then the cloud service platform creates the first cloud resource for the first user in response to the resource creation request.
In order to enable the second cloud resource to sense the data dependency relationship between the second cloud resource and the first cloud resource, the cloud service platform creates a resource relationship tag for indicating the data dependency relationship between the first cloud resource and the second cloud resource to the second cloud resource, and sends the resource relationship tag to the second account, so that the second account tags the second cloud resource according to the resource relationship tag.
In one possible implementation, the resource relationship tag includes: the method comprises the steps of identifying a first cloud product, identifying a first cloud resource and an attribute name of the first cloud resource.
Fig. 4 shows a schematic diagram of resource management in a cloud service platform according to an embodiment of the present disclosure. As shown in fig. 4, the cloud service platform creates a cloud resource B1 for a user B (second account) based on a cloud product B, a data dependency relationship exists between the cloud resource B1 and a cloud resource A2 created by the cloud service platform for a user a (first account) based on a cloud product a, when the cloud service platform creates the cloud resource B1 or after creating the cloud resource B1, a resource relationship tag 1 for indicating the data dependency relationship between the cloud resource B1 and the cloud resource A2 to the cloud resource A2 is created, the resource relationship tag 1 is in a key-value pair (key-value) form, specifically in the form of "key= [ identification of the cloud product B ]: [ attribute name of the cloud resource B1 ]", and the cloud service platform sends the resource tag 1 to the user a (first account) so that the user a (first account) tags the cloud resource A2 as a data depended party according to the resource relationship tag 1;
The cloud service platform creates a cloud resource A1 for a user A (a first account) based on a cloud product A, a data dependency relationship exists between the cloud resource A1 and the cloud resource B1, when the cloud service platform creates the cloud resource A1 or after creating the cloud resource A1, a resource relation tag 2 for indicating the data dependency relationship between the cloud resource A1 and the cloud resource B1 to the cloud resource B1 is created, the resource relation tag 2 is in a key-value pair (key-value) form, specifically in the form of' key= [ identification of the cloud product A ]: [ attribute name of the cloud resource A1 ], value= [ identification of the cloud resource A1 ] ", and the cloud service platform sends the resource tag 2 to a user B (a second account) so that the user B (the second account) tags the cloud resource B1 which is a data depended party according to the resource relation tag 2.
By marking the resource relation label for the data depended party, the data depended party can perceive the data dependency relation between cloud resources according to the resource relation label, and then when the data depended party fails to delete the resources, the reason of the failure of deleting the resources can be quickly known according to the resource relation label.
Taking fig. 4 as an example, it is assumed that the user B (second account) does not tag the cloud resource B1 as the data depended party according to the resource relationship tag 2, when the user B (second account) sends a resource deletion request for requesting to delete the resource B1 to the cloud service platform, the cloud service platform refuses to execute the deletion operation on the cloud resource B1 due to the data dependency relationship between the cloud resource A1 and the cloud resource B1, that is, the cloud resource B1 fails to delete, and at this time, the user B (second account) cannot determine the reason why the cloud resource B1 fails to delete due to the fact that the user B (second account) cannot perceive the data dependency relationship between the cloud resource A1 and the cloud resource B1.
When the cloud service platform creates the cloud resource A1 or creates the resource relationship tag 2 after creating the cloud resource A1, and sends the resource relationship tag 2 to the user B (second account), and then after the user B (second account) tags the cloud resource B1 as a data depended party according to the resource relationship tag 2, when the user B (second account) sends a resource deletion request for requesting to delete the resource B1 to the cloud service platform, and when the cloud service platform refuses to execute a deletion operation on the cloud resource B1 due to a data dependency relationship between the cloud resource A1 and the cloud resource B1, the user B (second account) can quickly determine the reason that the cloud resource B1 fails to delete according to the resource relationship tag 2 because a data dependency relationship exists between the cloud resource A1 and the cloud resource B1.
After the data depended party quickly knows the reason of the resource deletion failure according to the resource relation label, if the resource deletion operation still needs to be executed, the data depended party needs to be relieved of the data dependence firstly.
In one possible implementation, the method further includes: receiving a de-reliance request sent by a second account, wherein the de-reliance request is used for requesting to release the data dependency relationship between the first cloud resource and the second cloud resource; responding to the de-dependency request, and releasing the data dependency relationship between the first cloud resource and the second cloud resource; receiving a first deletion request sent by a second account, wherein the first deletion request is used for requesting to delete the second cloud resource; and responding to the first deleting request, and executing deleting operation on the second cloud resource.
Taking the above fig. 4 as an example, the user B (the second account) may determine, according to the resource relationship tag 2, a data dependency relationship between the cloud resource A1 and the cloud resource B1, when the user B (the second account) wishes to delete the cloud resource B1, the user B (the second account) first sends, to the cloud service platform, a solution dependency request for requesting to release the data dependency relationship between the cloud resource A1 and the cloud resource B1, and the cloud service platform responds to the solution dependency request, to release the data dependency relationship between the first cloud resource and the second cloud resource (for example, the cloud service platform may make the cloud resource A1 as a data dependency party unable to work with the cloud resource B2 as a configuration information, and may instruct the user B (the second account) to delete the resource relationship tag 2), and after the solution of the data dependency relationship is released, the user B (the second account) determines, according to the first instruction information, that the data dependency relationship between the cloud resource A1 and the cloud resource B1 has been released, and then the user B (the second account) sends, to the cloud service platform to request to delete the cloud service platform to perform the cloud service request to delete the cloud service 1.
In an example, the cloud service platform responds to the de-dependency request sent by the second account to release the data dependency relationship between the first cloud resource and the second cloud resource, and specifically includes: the cloud service platform forwards the de-reliance request to the first account; receiving second indication information returned by the first account, wherein the second indication information is used for indicating that the first account agrees to release the data dependency relationship between the first cloud resource and the second cloud resource; the cloud service platform releases the data dependency relationship between the first cloud resource and the second cloud resource.
Taking fig. 4 as an example, the user B (the second account) sends a de-dependency request for requesting to release the data dependency relationship between the cloud resource A1 and the cloud resource B1 to the cloud service platform, and after receiving the de-dependency request, the cloud service platform forwards the de-dependency request to the user a (the first account). If the user A (the first account) agrees to release the data dependency relationship between the cloud resource A1 and the cloud resource B1, the user A (the first account) returns second indication information to the cloud service platform, and the cloud service platform determines that the user A (the first account) agrees to release the data dependency relationship between the cloud resource A1 and the cloud resource B1 according to the second indication information, so that the cloud service platform releases the data dependency relationship between the cloud resource A1 and the cloud resource B1.
In one possible implementation, the method further includes: and sending a second deletion request to the first account, so that the first account executes a deletion operation on the first cloud resource by responding to the second deletion request.
After the cloud service platform responds to the first deletion request and executes the deletion operation on the second cloud resource, as the data dependency relationship between the first cloud resource and the second cloud resource is relieved and the second cloud resource is deleted, the cloud service platform sends the second deletion request to the first account, so that the first account executes the deletion operation on the first cloud resource by responding to the second deletion request, and under the condition that the first cloud resource cannot be used due to the data dependency relationship resolution and the second cloud resource deletion, the first cloud resource is deleted, thereby avoiding resource waste in the cloud service platform.
In an example, further comprising: the cloud service platform forwards the de-reliance request to the first account; receiving third indication information returned by the first account, wherein the third indication information is used for indicating that the first account does not agree to release the data dependency relationship between the first cloud resource and the second cloud resource; the cloud service platform does not execute the operation of releasing the data dependency relationship between the first cloud resource and the second cloud resource, and returns fourth prompt information to the second account, wherein the fourth prompt information is used for prompting that the data dependency relationship between the first cloud resource and the second cloud resource of the second account cannot be released.
Taking fig. 4 as an example, the user B (the second account) sends a de-dependency request for requesting to release the data dependency relationship between the cloud resource A1 and the cloud resource B1 to the cloud service platform, and after receiving the de-dependency request, the cloud service platform forwards the de-dependency request to the user a (the first account). If the user a (first account) does not agree to release the data dependency relationship between the cloud resource A1 and the cloud resource B1, the user a (first account) returns third indication information to the cloud service platform, the cloud service platform determines that the user a (first account) does not agree to release the data dependency relationship between the cloud resource A1 and the cloud resource B1 according to the third indication information, and further the cloud service platform cannot release the data dependency relationship between the cloud resource A1 and the cloud resource B1, the cloud service platform sends fourth indication information to the user B (second account), and the user B (second account) determines that the data dependency relationship between the cloud resource A1 and the cloud resource B1 cannot be released according to the fourth prompt information, and further the user B (second account) determines that the cloud resource B1 cannot be deleted.
In the cloud service platform, a resource creation request sent by a first account number and used for requesting to create a first cloud resource based on a first cloud product is received, a data dependency relationship exists between the first cloud resource and a second cloud resource created by a second account number based on a second cloud product, a resource relationship tag used for indicating the data dependency relationship between the first cloud resource and the second cloud resource to the second cloud resource is created, and the resource relationship tag is sent to the second account number, so that the cloud resource in the cloud service platform can be effectively managed across accounts and products, and the use experience of a user on the cloud service platform is improved.
Fig. 5 shows a schematic structural diagram of a cloud service platform according to an embodiment of the disclosure. The cloud service platform 50 shown in fig. 5 may be used to implement the steps of the method embodiment shown in fig. 3, where the cloud service platform 50 includes:
The receiving module 51 is configured to receive a resource creation request sent by a first account, where the resource creation request is used to request creation of a first cloud resource based on a first cloud product, a data dependency relationship exists between the first cloud resource and a second cloud resource, and the second cloud resource is a cloud resource created by a second account based on a second cloud product;
The label creation module 52 is configured to create a resource relationship label, where the resource relationship label is configured to indicate, to the second cloud resource, a data dependency relationship between the first cloud resource and the second cloud resource;
And the sending module 53 is configured to send the resource relationship label to the second account.
In one possible implementation, the resource relationship tag includes: the method comprises the steps of identifying a first cloud product, identifying a first cloud resource and an attribute name of the first cloud resource.
In one possible implementation, the cloud service platform 50 further includes: a dependency release module and a deletion module;
The receiving module 51 is further configured to receive a de-dependency request sent by the second account, where the de-dependency request is used to request to release a data dependency relationship between the first cloud resource and the second cloud resource;
the dependency relation releasing module is used for responding to the de-dependency request and releasing the data dependency relation between the first cloud resource and the second cloud resource;
the receiving module 51 is further configured to receive a first deletion request sent by the second account, where the first deletion request is used to request deletion of the second cloud resource;
And the deleting module is used for responding to the first deleting request and executing deleting operation on the second cloud resource.
In a possible implementation manner, the sending module 53 is further configured to send a second deletion request to the first account, so that the first account performs a deletion operation on the first cloud resource by responding to the second deletion request.
The cloud service platform 50 provided in the present disclosure can implement each step in the method embodiment shown in fig. 3, and achieve the same technical effects, and for avoiding repetition, a detailed description is omitted herein.
Fig. 6 shows a schematic structural diagram of an electronic device according to an embodiment of the present disclosure. As shown in fig. 6, at the hardware level, the electronic device comprises a processor, optionally together with an internal bus, a network interface, a memory. The Memory may include a Memory, such as a Random-Access Memory (RAM), and may further include a non-volatile Memory (non-volatile Memory), such as at least 1 disk Memory. Of course, the electronic device may also include hardware required for other services.
The processor, network interface, and memory may be interconnected by an internal bus, which may be an industry standard architecture (Industry Standard Architecture, ISA) bus, a peripheral component interconnect standard (PERIPHERAL COMPONENT INTERCONNECT, PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, among others. The buses may be divided into address buses, data buses, control buses, etc. For ease of illustration, only one bi-directional arrow is shown in FIG. 6, but not only one bus or type of bus.
And a memory for storing the program. In particular, the program may include program code including computer-operating instructions. The memory may include memory and non-volatile storage and provide instructions and data to the processor.
The processor reads the corresponding computer program from the nonvolatile memory to the memory and then runs the computer program to form a cloud service platform on a logic level. A processor executing the program stored in the memory, and specifically executing: receiving a resource creation request sent by a first account, wherein the resource creation request is used for requesting to create a first cloud resource based on a first cloud product, a data dependency relationship exists between the first cloud resource and a second cloud resource, and the second cloud resource is a cloud resource created by a second account based on a second cloud product; creating a resource relationship tag, wherein the resource relationship tag is used for indicating a data dependency relationship between the first cloud resource and the second cloud resource to the second cloud resource; and sending the resource relation label to the second account.
In one possible implementation, the resource relationship tag includes: the method comprises the steps of identifying a first cloud product, identifying a first cloud resource and an attribute name of the first cloud resource.
In one possible implementation, the processor is further configured to perform: receiving a de-reliance request sent by a second account, wherein the de-reliance request is used for requesting to release the data dependency relationship between the first cloud resource and the second cloud resource; responding to the de-dependency request, and releasing the data dependency relationship between the first cloud resource and the second cloud resource; receiving a first deletion request sent by a first account, wherein the first deletion request is used for requesting to delete a second cloud resource; and responding to the first deleting request, and executing deleting operation on the first cloud resource.
In one possible implementation, the processor is further configured to perform: and sending a second deletion request to the first account, so that the first account executes a deletion operation on the first cloud resource by responding to the second deletion request.
The processor may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or by instructions in the form of software. The processor may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; but may also be a digital signal Processor (DIGITAL SIGNAL Processor, DSP), application SPECIFIC INTEGRATED Circuit (ASIC), field-Programmable gate array (Field-Programmable GATE ARRAY, FPGA) or other Programmable logic device, discrete gate or transistor logic device, discrete hardware components. The various methods, steps and logic blocks disclosed in the embodiments of this specification may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present specification may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.
The electronic device may execute the method executed by the method embodiment shown in fig. 3 and implement the functions of the method embodiment shown in fig. 3, which are not described herein.
The present description also proposes a computer-readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by an electronic device comprising a plurality of application programs, enable the electronic device to perform the resource management method in the embodiment shown in fig. 3, and in particular to perform the steps of the method embodiment shown in fig. 3.
The present disclosure may be a system, method, and/or computer program product. The computer program product may include a computer readable storage medium having computer readable program instructions embodied thereon for causing a processor to implement aspects of the present disclosure.
The computer readable storage medium may be a tangible device that can hold and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: portable computer disks, hard disks, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static Random Access Memory (SRAM), portable compact disk read-only memory (CD-ROM), digital Versatile Disks (DVD), memory sticks, floppy disks, mechanical coding devices, punch cards or in-groove structures such as punch cards or grooves having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media, as used herein, are not to be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., optical pulses through fiber optic cables), or electrical signals transmitted through wires.
The computer readable program instructions described herein may be downloaded from a computer readable storage medium to a respective computing/processing device or to an external computer or external storage device over a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmissions, wireless transmissions, routers, firewalls, switches, gateway computers and/or edge servers. The network interface card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium in the respective computing/processing device.
The computer program instructions for performing the operations of the present disclosure may be assembly instructions, instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages, including an object oriented programming language such as SMALLTALK, C ++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer readable program instructions may be executed 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 case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, aspects of the present disclosure are implemented by personalizing electronic circuitry, such as programmable logic circuitry, field Programmable Gate Arrays (FPGAs), or Programmable Logic Arrays (PLAs), with state information of computer readable program instructions, which can execute the computer readable program instructions.
Various aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.
These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable medium having the instructions stored therein includes an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowcharts 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 disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). 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 foregoing description of the embodiments of the present disclosure has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the various embodiments described. The terminology used herein was chosen in order to best explain the principles of the embodiments, the practical application, or the technical improvement of the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
Claims (10)
1. A method for resource management, wherein the method is applied to a cloud service platform, the method comprising:
receiving a resource creation request sent by a first account, wherein the resource creation request is used for requesting to create a first cloud resource based on a first cloud product, a data dependency relationship exists between the first cloud resource and a second cloud resource, and the second cloud resource is a cloud resource created by a second account based on a second cloud product; wherein the first cloud resource is a data relying party; the second cloud resource is a data depended party;
creating a resource relationship tag, wherein the resource relationship tag is used for indicating the data dependency relationship between the first cloud resource and the second cloud resource to the second cloud resource;
And sending the resource relation tag to the second account, so that the second account perceives the data dependency relationship between the first cloud resource and the second cloud resource based on the resource relation tag.
2. The method according to claim 1, wherein the resource relationship tag comprises: the identification of the first cloud product, the identification of the first cloud resource, and the attribute name of the first cloud resource.
3. The method according to claim 1, wherein the method further comprises:
receiving a de-reliance request sent by the second account, wherein the de-reliance request is used for requesting to release the data dependency relationship between the first cloud resource and the second cloud resource;
responding to the de-dependency request, and releasing the data dependency relationship between the first cloud resource and the second cloud resource;
Receiving a first deletion request sent by the second account, wherein the first deletion request is used for requesting to delete the second cloud resource;
and responding to the first deleting request, and executing deleting operation on the second cloud resource.
4. A method according to claim 3, characterized in that the method further comprises:
and sending a second deletion request to the first account, so that the first account executes a deletion operation on the first cloud resource by responding to the second deletion request.
5. A cloud service platform, comprising:
The receiving module is used for receiving a resource creation request sent by a first account, wherein the resource creation request is used for requesting to create a first cloud resource based on a first cloud product, a data dependency relationship exists between the first cloud resource and a second cloud resource, and the second cloud resource is a cloud resource created by a second account based on a second cloud product; wherein the first cloud resource is a data relying party; the second cloud resource is a data depended party;
The label creation module is used for creating a resource relation label, wherein the resource relation label is used for indicating the data dependency relationship between the first cloud resource and the second cloud resource to the second cloud resource;
And the sending module is used for sending the resource relation tag to the second account so that the second account perceives the data dependency relationship between the first cloud resource and the second cloud resource based on the resource relation tag.
6. The cloud service platform of claim 5, wherein the resource relationship tag comprises: the identification of the first cloud product, the identification of the first cloud resource, and the attribute name of the first cloud resource.
7. The cloud service platform of claim 5, further comprising: a dependency release module and a deletion module;
the receiving module is further configured to receive a de-dependency request sent by the second account, where the de-dependency request is used to request to release a data dependency relationship between the first cloud resource and the second cloud resource;
The dependency relation releasing module is used for responding to the de-dependency request and releasing the data dependency relation between the first cloud resource and the second cloud resource;
the receiving module is further configured to receive a first deletion request sent by the second account, where the first deletion request is used to request deletion of the second cloud resource;
and the deleting module is used for responding to the first deleting request and executing deleting operation on the second cloud resource.
8. The cloud service platform of claim 7,
The sending module is further configured to send a second deletion request to the first account, so that the first account executes a deletion operation on the first cloud resource by responding to the second deletion request.
9. A cloud service platform, comprising:
A processor;
A memory for storing processor-executable instructions;
Wherein the processor is configured to perform the resource management method of any of claims 1-4.
10. A non-transitory computer readable storage medium having stored thereon computer program instructions, which when executed by a processor, implement the resource management method of any of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911100611.2A CN112866306B (en) | 2019-11-12 | 2019-11-12 | Resource management method and cloud service platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911100611.2A CN112866306B (en) | 2019-11-12 | 2019-11-12 | Resource management method and cloud service platform |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112866306A CN112866306A (en) | 2021-05-28 |
| CN112866306B true CN112866306B (en) | 2024-05-28 |
Family
ID=75984335
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911100611.2A Active CN112866306B (en) | 2019-11-12 | 2019-11-12 | Resource management method and cloud service platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112866306B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101515234A (en) * | 2009-03-26 | 2009-08-26 | 华亚微电子（上海）有限公司 | Associated data processing method and associated data device |
| CN101640613A (en) * | 2009-09-11 | 2010-02-03 | 中兴通讯股份有限公司 | Method and device for network resource relating management |
| CN103425751A (en) * | 2013-07-24 | 2013-12-04 | 浙江大学 | Linkage increment updating method of vector space data based on dependency |
| CN104954330A (en) * | 2014-03-27 | 2015-09-30 | 华为软件技术有限公司 | Method of accessing data resources, device and system |
| CN105704188A (en) * | 2014-11-27 | 2016-06-22 | 华为软件技术有限公司 | Deployment method and apparatus of applications and services |
| US9882775B1 (en) * | 2014-10-22 | 2018-01-30 | Amazon Technologies, Inc. | Dependent network resources |
| CN108171265A (en) * | 2017-12-26 | 2018-06-15 | 北京奇艺世纪科技有限公司 | A kind of label preparation method, device and electronic equipment |
| CN109471729A (en) * | 2018-11-15 | 2019-03-15 | 平安科技（深圳）有限公司 | Based on recursive resource method for cleaning and device |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8676848B2 (en) * | 2010-06-09 | 2014-03-18 | International Business Machines Corporation | Configuring cloud resources |
| US20170344363A1 (en) * | 2016-05-26 | 2017-11-30 | Linkedin Corporation | Dependency management |
| US10230582B2 (en) * | 2016-08-29 | 2019-03-12 | International Business Machines Corporation | Identifying resources for purging in a cloud based on inter-dependency graph analysis |
-
2019
- 2019-11-12 CN CN201911100611.2A patent/CN112866306B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101515234A (en) * | 2009-03-26 | 2009-08-26 | 华亚微电子（上海）有限公司 | Associated data processing method and associated data device |
| CN101640613A (en) * | 2009-09-11 | 2010-02-03 | 中兴通讯股份有限公司 | Method and device for network resource relating management |
| CN103425751A (en) * | 2013-07-24 | 2013-12-04 | 浙江大学 | Linkage increment updating method of vector space data based on dependency |
| CN104954330A (en) * | 2014-03-27 | 2015-09-30 | 华为软件技术有限公司 | Method of accessing data resources, device and system |
| US9882775B1 (en) * | 2014-10-22 | 2018-01-30 | Amazon Technologies, Inc. | Dependent network resources |
| CN105704188A (en) * | 2014-11-27 | 2016-06-22 | 华为软件技术有限公司 | Deployment method and apparatus of applications and services |
| CN108171265A (en) * | 2017-12-26 | 2018-06-15 | 北京奇艺世纪科技有限公司 | A kind of label preparation method, device and electronic equipment |
| CN109471729A (en) * | 2018-11-15 | 2019-03-15 | 平安科技（深圳）有限公司 | Based on recursive resource method for cleaning and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112866306A (en) | 2021-05-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10740136B2 (en) | Automatic virtual machine termination in a cloud | |
| CN110505162B (en) | Message transmission method and device and electronic equipment | |
| CN109831494B (en) | User data management method and device | |
| CN108762956B (en) | Method for acquiring Native local data, server, mobile terminal and storage medium | |
| CN110289983B (en) | Load balancing application creation method and device, computer equipment and storage medium | |
| CN108234551B (en) | Data processing method and device | |
| CN110609656B (en) | Storage management method, electronic device, and computer program product | |
| CN113536174A (en) | Interface loading method, device and equipment | |
| US20160284013A1 (en) | Order processing system and order processing method | |
| US9948694B2 (en) | Addressing application program interface format modifications to ensure client compatibility | |
| CN107453937B (en) | Management method of network connection pool, network access method and related equipment | |
| CN112866306B (en) | Resource management method and cloud service platform | |
| CN108965108B (en) | Message pushing method and related equipment | |
| CN112783635A (en) | Resource limit adjusting method and device | |
| CN111131409A (en) | Request responding method, device and related equipment | |
| CN107547437B (en) | Application identification method and device | |
| CN112948138A (en) | Method and device for processing message | |
| CN116149749A (en) | Retry method, device, equipment and storage medium for business operation | |
| CN112286622A (en) | Virtual machine migration processing and strategy generating method, device, equipment and storage medium | |
| CN114625458A (en) | Page data processing method and device, electronic equipment and storage medium | |
| CN112241337B (en) | Method, apparatus and computer program product for managing backup data | |
| CN114296823A (en) | Information processing method and device for decoupling between service modules | |
| CN114071066A (en) | Information processing method and server applied to big data video conference | |
| CN107885982B (en) | Login control processing method and terminal | |
| CN108288135B (en) | System compatibility method and device, computer readable storage medium and electronic equipment |
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 |