Technologies for managing disaggregated resources in a data center

Patent metadata

Field	Value
Publication number	US-2020257566-A1
Application number	US-201816642523-A
Country	US
Kind code	A1
Filing date	Aug 30, 2018
Priority date	Aug 30, 2017
Publication date	Aug 13, 2020
Grant date	—

Abstract

Technologies for managing disaggregated resources in a data center includes a compute device configured to determine that a service related task has been generated and create one or more microservices to perform the created service related task using at least one of a plurality of services managed by the microservice resource controller circuitry. The compute device is further configuration to generate one or more microtasks to compose at least one service based on the one or more microservices. Other embodiments are described herein.

First claim

1 - 25 . (canceled)

26 . A compute device for managing disaggregated resources in a data center, the compute device comprising:
microservice resource controller circuitry to (i) determine that a service related task has been generated and (ii) create one or more microservices to perform the determined service related task using at least one of a plurality of services managed by the microservice resource controller circuitry; and microtask resource controller circuitry to generate one or more microtasks to compose at least one service based on the one or more microservices.

27 . The compute device of claim 26 , wherein to generate the one or more microtasks comprises to create one or more threads for each of the one or more microservices, and wherein each of the one or more threads is to execute a respective one of the one or more microtasks.

28 . The compute device of claim 26 , wherein to create the one or more threads comprises to allocate a first thread to call a pod manager of the data center to discover resources of a hardware cluster of the data center.

29 . The compute device of claim 28 , wherein to create the one or more threads further comprises to allocate a second thread to compose a portion of the discovered resources into a composed node that is configured to function as a server.

30 . The compute device of claim 29 , wherein to create the one or more threads further comprises to allocate a third thread to deploy a storage volume to be associated with the composed node.

31 . The compute device of claim 30 , wherein the microservice resource controller circuitry is further to transmit a notification of completion to an entity that requested composition of the composed node, and wherein the notification of completion includes an identifier of the composed node.

32 . The compute device of claim 28 , wherein to create the one or more threads further comprises to allocate a plurality of threads to compose a portion of the discovered resources into a group of composed nodes, wherein each composed node of the group of composed nodes is configured to function as a server.

33 . The compute device of claim 32 , wherein the microservice resource controller circuitry is further to transmit a notification of completion to an entity that requested composition of the composed node, and wherein the notification of completion includes an identifier of each composed node of the group of composed nodes and a group identifier that identifies the group of composed nodes.

34 . The compute device of claim 28 , wherein to determine that the service related task has been generated comprises to determine that an underlay network of the data center is to be orchestrated, wherein to create the one or more threads comprises to start a master thread to compose network resources, and wherein the master thread is to (i) allocate a child thread to configure one or more switch ports of a switch of the data center and (ii) allocate one or more threads to configured one or more host ports of a node of the data center.

35 . The compute device of claim 34 , wherein the microservice resource controller circuitry is further to transmit a notification of completion to an entity that requested the underlay network to be orchestrated, and wherein the notification of completion includes a completion code and an identifier of the underlay network.

36 . The compute device of claim 26 , wherein to determine that the service related task has been generated comprises to determine that the generated service related task indicates that at least one node is to be orchestrated.

37 . The compute device of claim 26 , wherein the resources include compute resources, storage resources, and network resources.

38 . A compute device for managing disaggregated resources in a data center, the compute device comprising:
a compute engine to:
determine that a service related task has been generated and (ii) create one or more microservices to perform the determined service related task using at least one of a plurality of services managed by the compute engine; and
microtask resource controller circuitry to generate one or more microtasks to compose at least one service based on the one or more microservices.

39 . The compute device of claim 38 , wherein to generate the microtask comprises to create one or more threads for each of the one or more microservices, and wherein each of the one or more threads is to execute a respective one of the one or more microtasks.

40 . The compute device of claim 38 , wherein to determine that the service related task has been generated comprises to determine that the generated service related task indicates that at least one node is to be orchestrated, and wherein to create the one or more threads comprises to allocate a first thread to call a pod manager of the data center to discover resources of a hardware cluster of the data center, wherein the resources include compute resources, storage resources, and network resources.

41 . The compute device of claim 40 , wherein to create the one or more threads further comprises to allocate a second thread to compose a portion of the discovered resources into a composed node that is configured to function as a server.

42 . The compute device of claim 41 , wherein to create the one or more threads further comprises to allocate a third thread to deploy a storage volume to be associated with the composed node.

43 . The compute device of claim 42 , wherein the compute engine is further to transmit a notification of completion to an entity that requested composition of the composed node, and wherein the notification of completion includes an identifier of the composed node.

44 . The compute device of claim 40 , wherein to create the one or more threads further comprises to allocate a plurality of threads to compose a portion of the discovered resources into a group of composed nodes, wherein each composed node of the group of composed nodes is configured to function as a server.

45 . The compute device of claim 44 , wherein the compute engine is further to transmit a notification of completion to an entity that requested composition of the composed node, and wherein the notification of completion includes an identifier of each composed node of the group of composed nodes and a group identifier that identifies the group of composed nodes.

46 . The compute device of claim 40 , wherein to determine that the service related task has been generated comprises to determine that an underlay network of the data center is to be orchestrated, wherein to create the one or more threads comprises to start a master thread to compose network resources of the data center, and wherein the master thread is to (i) allocate a child thread to configure one or more switch ports of a switch of the data center and (ii) allocate one or more threads to configured one or more host ports of a node of the data center.

47 . The compute device of claim 46 , wherein the compute engine is further to transmit a notification of completion to an entity that requested the underlay network to be orchestrated, and wherein the notification of completion includes a completion code and an identifier of the underlay network.

48 . One or more machine-readable storage media comprising a plurality of instructions stored thereon that, when executed, causes a compute device to:
determine that a service related task has been generated; create

Assignees

• Intel Corp

Inventors

• Ganguli Mrittika
• Narayan Ananth S
• Bhandaru Malini K
• Kumar Mohan J
• Yang Wei
• Yang Lin
• Potter Nathaniel
• Kumari Madhuri

Classifications

• H04L47/83

  based on usage prediction · CPC title

• H04L41/0896

  Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities (flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76) · CPC title

• H04L49/40

  Constructional details, e.g. power supply, mechanical construction or backplane · CPC title

• H04L47/762

  triggered by the network · CPC title

• G06F15/161

  Computing infrastructure, e.g. computer clusters, blade chassis or hardware partitioning (casings, cabinets, racks or drawers for data centers H05K5/00) · CPC title