# US 2018/0027093 A1 · Methods and apparatus for sdi support for automatic and transparent migration

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2018/0027093 A1
- Document ID: US20180027093A1
- Status: Published application
- Kind: A1
- Application number: 15/655,874
- Filed: 2017-07-20
- Published: 2018-01-25
- Earliest claimed: 2016-07-22
- Assignees: Intel Corporation
- Applicants: Intel Corporation
- Inventors: FRANCESC GUIM BERNAT; SUSANNE M. BALLE; DANIEL RIVAS BARRAGAN; JOHN CHUN KWOK LEUNG; MARK S. MYERS; SURAJ PRABHAKARAN; MURUGASAMY K. NACHIMUTHU; SLAWOMIR PUTYRSKI
- Web page: https://patentgrep.com/patent/US20180027093A1

## CPC

- H04L 41/0895: Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
- G06F 16/2282: {Tablespace storage structures; Management thereof}
- G06F 16/2379: {Updates performed during online database operations; commit processing}
- H04L 41/0816: the condition being an adaptation, e.g. in response to network events
- H04L 41/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)
- H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities
- H04L 41/5025: by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade
- H04L 43/0876: Network utilisation, e.g. volume of load or congestion level
- H04L 43/16: Threshold monitoring
- H04L 47/803: {Application aware}
- H04L 47/83: based on usage prediction
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/1031: Controlling of the operation of servers by a load balancer, e.g. adding or removing servers that serve requests
- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- H04Q 9/00: Arrangements in telecontrol or telemetry systems for selectively calling a substation from a main station, in which substation desired apparatus is selected for applying a control signal thereto or for obtaining measured values therefrom
- H04L 41/16: using machine learning or artificial intelligence
- H04L 41/5009: Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
- H04L 41/5054: Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
- H04L 43/0858: {One way delays}
- H04L 43/0894: Packet rate
- H04L 47/722: at the destination endpoint, e.g. reservation of terminal resources or buffer space
- H04L 47/805: {QOS or priority aware}
- H04Q 2209/20: using a distributed architecture
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04Q: SELECTING (switches, relays, selectors H01H; wireless communication networks H04W)

## Abstract

Techniques for migration for composite nodes in software-defined infrastructures (SDI) are described. A SDI system may include a SDI manager component, including one or more processor circuits, configured to access one or more remote resources, the SDI manager component may include a partition manager configured to receive a request to create a composite node from an orchestrator component, the request including at least one preferred compute sled type and at least one alternative compute sled type. The SDI manager may create a composite node using a first compute sled matching the at least one alternative compute sled type. The SDI manager may determine, based upon a migration table stored on a non-transitory computer-readable storage medium that a second compute sled matching the at least one preferred compute sled type is available. The SDI manager may perform an migration from the first compute sled to the second compute sled. Other embodiments are described and claimed.

## Claims

### Claim 1

A software-defined infrastructure (SDI) system, comprising:
an SDI manager component, including one or more processor circuits to access one or more remote resources, the SDI manager component including migration logic to:
receive a request to create a composite node, the request including at least one preferred compute sled type and at least one alternative compute sled type;
create a composite node using a first compute sled matching the at least one alternative compute sled type;
receive an indication that a second compute sled has become available;
determine that the second compute sled matches the at least one preferred compute sled type; and
migrate an application from the first compute sled to the second compute sled.

### Claim 2 (depends on 1)

The system of claim 1, wherein the at least one alternative compute sled type is defined by a set of compute requirements different than a set of compute requirements defining the least one preferred compute sled type.

### Claim 3 (depends on 1)

The system of claim 1, wherein the migration includes hibernating at least one application executing on the first compute sled.

### Claim 4 (depends on 3)

The system of claim 3, wherein the hibernated at least one application is stored within a designated disaggregated portion of the at least one or more remote resources.

### Claim 5 (depends on 4)

The system of claim 4, wherein the second compute sled determines a memory location of the hibernated at least one application based upon a pre-defined memory location reserved for migration operations.

### Claim 6 (depends on 5)

The system of claim 5, wherein the second compute node determines a memory location of the hibernated at least one application based upon a message from the SDI manager component.

### Claim 7 (depends on 1)

The system of claim 1, wherein the SDI manager component is configured to receive an indication when the migration has finished.

### Claim 8 (depends on 7)

The system of claim 7, wherein the SDI manager component is configured to release the first compute sled upon receiving the indication when the migration has finished.

### Claim 9 (depends on 1)

The system of claim 1, wherein the determination is based upon a migration table stored on a non-transitory computer-readable storage medium.

### Claim 10 (depends on 1)

The system of claim 1, wherein the ability to perform a migration is dependent upon the use of memory disaggregated from the first or second compute sled.

### Claim 11

A computer-implemented method, comprising:
receiving, by an SDI manager component, a request to create a composite node from an orchestrator component, the request including at least one preferred compute sled type and at least one alternative compute sled type;
creating a composite node using a first compute sled matching the at least one alternative compute sled type;
receive an indication that a second compute sled has become available;
determine that the second compute sled matches the at least one preferred compute sled type; and
performing a migration from the first compute sled to the second compute sled.

### Claim 12 (depends on 11)

The method of claim 11, wherein the at least one alternative compute sled type is defined by a set of compute requirements different than a set of compute requirements defining the least one preferred compute sled type.

### Claim 13 (depends on 11)

The method of claim 11, wherein the migration includes hibernating at least one application executing on the first compute sled.

### Claim 14 (depends on 13)

The method of claim 13, wherein the hibernated at least one application is stored within a designated disaggregated portion of the at least one or more remote resources.

### Claim 15 (depends on 14)

The method of claim 14, wherein the second compute sled determines a memory location of the hibernated at least one application based upon a pre-defined memory location reserved for migration operations.

### Claim 16 (depends on 15)

The method of claim 15, wherein the second compute node determines a memory location of the hibernated at least one application based upon a message from the SDI manager component.

### Claim 17 (depends on 11)

The method of claim 11, wherein the SDI manager component is configured to receive an indication when the migration has finished.

### Claim 18 (depends on 17)

The method of claim 17, wherein the SDI manager component is configured to release the first compute sled upon receiving the indication when the migration has finished.

### Claim 19 (depends on 11)

The method of claim 11, wherein the determination is based upon a migration table stored on a non-transitory computer-readable storage medium.

### Claim 20 (depends on 11)

The method of claim 11, wherein the ability to perform an migration is dependent upon the use of memory disaggregated from the first or second compute sled.

### Claim 21

An article comprising a non-transitory computer-readable storage medium that stores instructions for execution by processing circuitry of a software-defined infrastructure (SDI) system, the instructions to cause a SDI manager component of the SDI system to:
receive a request to create a composite node from an orchestrator component, the request including at least one preferred compute sled type and at least one alternative compute sled type;
create a composite node using a first compute sled matching the at least one alternative compute sled type;
receive an indication that a second compute sled has become available;
determine that the second compute sled matches the at least one preferred compute sled type; and
perform a migration from the first compute sled to the second compute sled.

### Claim 22 (depends on 21)

The article of claim 21, wherein the at least one alternative compute sled type is defined by a set of compute requirements different than a set of compute requirements defining the least one preferred compute sled type.

### Claim 23 (depends on 21)

The article of claim 21, wherein the migration includes hibernating at least one application executing on the first compute sled.

### Claim 24

A software-defined infrastructure (SDI) system, comprising:
means for receiving a request to create a composite node, the request including at least one preferred compute sled type and at least one alternative compute sled type;
means for creating a composite node using a first compute sled matching the at least one alternative compute sled type;
means for receiving an indication that a second compute sled has become available;
means for determining that the second compute sled matches the at least one preferred compute sled type; and
means for migrating an application from the first compute sled to the second compute sled.

### Claim 25 (depends on 1)

The system of claim 1, wherein the at least one alternative compute sled type is defined by a set of compute requirements different than a set of compute requirements defining the least one preferred compute sled type.
