IP Library Granted Patent US 9,935,830
Granted Patent B1
US 9,935,830 · App. 14/719,577 · Granted Apr 3, 2018

Cloud management system and method for disparate computing nodes in a cloud computing environment

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,935,830
App. No.
14/719,577
Granted
Apr 3, 2018
Kind
B1
Abstract

A cloud management system includes a computer executed application that generates an interface for management of the resources of a computing node by a cloud portal. The application receives an interface definition associated with the resource in which the interface definition includes information associated with one or more configuration operations to be performed on the resource. Using the interface definition, the application generates a cloud portal interface component that communicates with a cloud portal to translate the one or more configuration operations to a specified protocol, and generates a resource endpoint component that receives the configuration operations from the cloud portal interface component, translates the configuration operations to a format suitable for use by the resource, and transmits the configuration operations to the resource for configuring the resource.

Claims (36)

1. A cloud management system comprising:

a computing device comprising at least one memory for storing instructions that are executed by at least one processor and in communication with a computing node having a plurality of resources, the instructions are executed to, for at least one of the resources:

receive an interface definition associated with the at least one resource, the interface definition including information associated with a first configuration operation and a second configuration operation to be performed on the at least one resource, the first configuration operation being different than the second configuration operation;

generate, using the interface definition, a cloud portal interface component that communicates with a cloud portal to generate the first and the second configuration operations according to a specified protocol; and

generate, using the interface definition, a first resource endpoint component that receives a first message associated with the first configuration operation from the cloud portal interface component and a second resource endpoint component that receives a second message associated with the second configuration operation from the cloud portal interface component,

wherein the first resource endpoint component translates the first message to a format suitable for use by the at least one resource, and transmits the translated first message to the at least one resource for configuring the at least one resource according to the first configuration operation, and

wherein the second resource endpoint component translates the second message to a format suitable for use by the at least one resource, and transmits the translated second message to the at least one resource for configuring the at least one resource according to the second configuration operation.

2. The cloud management system of claim 1 , wherein the first and the second resource endpoint components translate the first and the second configuration operations into a format suitable for use by an element manager that controls the at least one resource.

3. The cloud management system of claim 1 , wherein the cloud portal does not natively support the computing node.

4. The cloud management system of claim 1 , wherein the instructions are executed to create the interface definition for the at least one resource using a discovery process that obtains type information about the at least one resource, and obtains characteristic information associated with the type information that is stored in the at least one memory, wherein the characteristic information is used to generate the interface definition.

5. The cloud management system of claim 1 , wherein the computing node comprises a converged infrastructure having multiple sub-systems that each functions in a virtualized environment.

6. The cloud management system of claim 1 , wherein the specified protocol comprises at least one of a Representational State Transfer (REST) protocol and a Javascript Object Notation (JSON) protocol.

7. The cloud management system of claim 1 , wherein the cloud portal interface component comprises a modular software component including at least one of a plug-in, an add-on, and an extension.

8. The cloud management system of claim 1 , wherein the instructions are executed to install the first and the second resource endpoint components on the at least one resource, the first and the second messages comprising a first and a second application program interface (API) message.

9. A method comprising:

receiving, using instructions stored in at least one memory and executed by at least one processor, an interface definition associated with at least one resource, the interface definition including information associated with a first configuration operation and a second configuration operation to be performed on the at least one resource, the first configuration operation being different than the second configuration operation;

generating, using the instructions executed by the processor, a cloud portal interface component that communicates with a cloud portal to generate the first and the second configuration operations according to a specified protocol using the interface definition; and

generating, using the instructions executed by the processor, a first resource endpoint component that receives a first message associated with the first configuration operation from the cloud portal interface component and a second resource endpoint component that receives a second message associated with the second configuration operation from the cloud portal interface component using the interface definition,

wherein the first resource endpoint component translates the first message to a format suitable for use by the at least one resource, and transmits the translated first message to the at least one resource for configuring the at least one resource according to the first configuration operation, and

wherein the second resource endpoint component translates the second message to a format suitable for use by the at least one resource, and transmits the translated second message to the at least one resource for configuring the at least one resource according to the second configuration operation.

10. The method of claim 9 , further comprising translating, by the first and the second resource endpoint components, the first and the second configuration operations into a format suitable for use by an element manager that controls the resource.

11. The method of claim 9 , further comprising creating the interface definition for the resource using a discovery process by obtaining type information about the resource, and obtaining characteristic information associated with the type information that is stored in the at least one memory, wherein the characteristic information is used to generate the interface definition.

12. The method of claim 9 , wherein the specified protocol comprises at least one of a Representational State Transfer (REST) protocol and a Javascript Object Notation (JSON) protocol.

13. The method of claim 9 , wherein the cloud portal interface component comprises a modular software component including at least one of a plug-in, an add-on, and an extension.

14. The method of claim 9 , further comprising installing the first and the second resource endpoint components on the resource, the resource endpoint component translating the first and the second messages comprising a first and a second application program interface (API) message.

15. Code implemented in a non-transitory, computer readable medium that when executed by at least one processor, is operable to perform at least the following:

receiving an interface definition associated with at least one resource, the interface definition including information associated with a first configuration operation and a second configuration operation to be performed on the at least one resource, the first configuration operation being different than the second configuration operation;

generating a cloud portal interface component that communicates with a cloud portal to generate the first and the second configuration operations according to a specified protocol using the interface definition; and

generating a first resource endpoint component that receives a first message associated with the first configuration operation from the cloud portal interface component and a second resource endpoint component that receives a second message associated with the second configuration operation from the cloud portal interface component using the interface definition,

wherein the first resource endpoint component translates the first message to a format suitable for use by the at least one resource, and transmits the translated first message to the at least one resource for configuring the at least one resource according to the first configuration operation, and

wherein the second resource endpoint component translates the second message to a format suitable for use by the at least one resource, and transmits the translated second message to the at least one resource for configuring the at least one resource according to the second configuration operation.

16. The code of claim 15 , further operable to perform translating the first and the second configuration operations into a format suitable for use by an element manager that controls the resource.

17. The code of claim 15 , further operable to perform creating the interface definition for the resource using a discovery process by obtaining type information about the resource, and obtaining characteristic information associated with the type information that is stored in the code, wherein the characteristic information is used to generate the interface definition.

18. The code of claim 15 , wherein the specified protocol comprises at least one of a Representational State Transfer (REST) protocol and a Javascript Object Notation (JSON) protocol.

19. The code of claim 15 , wherein the cloud portal interface component comprises a modular software component including at least one of a plug-in, an add-on, and an extension.

20. The code of claim 15 , further comprising installing the resource endpoint component on a dedicated resource of the at least one resource.

Assignments (5)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053546/0001) Recorded Jun 23, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC IP HOLDING COMPANY LLC
Reel/Frame 071642/0001 →
SECURITY AGREEMENT Recorded Apr 22, 2020
From: CREDANT TECHNOLOGIES INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 053546/0001 →
MERGER Recorded Apr 14, 2020
From: VCE IP HOLDING COMPANY LLC
To: EMC IP HOLDING COMPANY LLC
Reel/Frame 052398/0413 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 8, 2016
From: VCE COMPANY, LLC
To: VCE IP HOLDING COMPANY LLC
Reel/Frame 040576/0161 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 22, 2015
From: MAHAPATRA, AKSHAYA; TAN, MICHAEL; LIU, PENG; LAU, GILBERT
To: VCE COMPANY, LLC
Reel/Frame 035697/0647 →