SDN NETWORK ELEMENT AFFINITY BASED DATA PARTITION AND FLEXIBLE MIGRATION SCHEMES

• US 20160316011A1
• Filed: 04/27/2015
• Published: 10/27/2016
• Est. Priority Date: 04/27/2015
• Status: Abandoned Application

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Venkataraman, Chandramouli, Kothandaraman, Muthukumaran
• Application Number:
  US14/697,513
• Publication Number:
  US 20160316011A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 41/0668 by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
• CPC Class Codes: H04L 41/0695 the faulty arrangement being the maintenance, administration or management system
• CPC Class Codes: H04L 41/342 between virtual entities, e.g. orchestrators, SDN or NFV entities
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

A method is performed by a controller node to support network element (NE) data migration. The controller node is part of a cluster of controller nodes in a software defined networking (SDN) network. The method includes detecting that a peer controller node in a same replication zone as the controller node has failed, where the peer controller node is a master for data associated with an NE and the controller node is a backup for the data associated with the NE, transitioning a state of the NE to a migration state, transferring the data associated with the NE from backup storage (Zb) of the controller node to dead storage (Zd) of the controller node, receiving a request for the data associated with the NE from a requesting controller node, and transferring at least a fragment of the data associated with the NE to the requesting controller node.

Claims

1. A method performed by a controller node to support network element (NE) data migration, the controller node is part of a cluster of controller nodes in a software defined networking (SDN) network, the method comprising:

detecting that a peer controller node in a same replication zone as the controller node has failed, wherein the peer controller node is a master for data associated with an NE and the controller node is a backup for the data associated with the NE;

transitioning a state of the NE to a migration state;

transferring the data associated with the NE from backup storage (Zb) of the controller node to dead storage (Zd) of the controller node;

receiving a request for the data associated with the NE from a requesting controller node; and

transferring at least a fragment of the data associated with the NE to the requesting controller node.

2. The method of claim 1, further comprising:

transmitting a done message to the requesting controller node that indicates that transfer of the data associated with the NE has completed.

3. The method of claim 2, further comprising:

receiving an acknowledgment message from the requesting controller node that indicates that the done message has been received; and

deleting the data associated with the NE from the Zd of the controller node upon receiving the acknowledgment message.

4. The method of claim 1, further comprising:

receiving a connection request from a connecting NE;

transitioning a state of the connecting NE to a migration state if the connecting NE is not already in the migration state;

selecting a replication zone;

determining if a Zd of a controller node in the selected replication zone includes data associated with the connecting NE;

upon determining that the Zd of the controller node in the selected replication zone includes data associated with the connecting NE,

requesting the data associated with the connecting NE from the controller node in the selected replication zone,

receiving at least a fragment of the data associated with the connecting NE from the controller node in the selected replication zone, and

storing the received fragment of the data associated with the connecting NE in the Zd of the controller node;

determining whether all replication zones in the cluster of controller nodes have been selected; and

upon determining that all replication zones in the cluster of controller nodes have been selected,

transferring the data associated with the connecting NE from the Zd of the controller node to master storage (Zm) of the controller node, and

transitioning the state of the connecting NE to a stable state.

5. The method of claim 4, further comprising:

upon determining that not all replication zones in the cluster of controller nodes have been selected, selecting another replication zone not previously selected for determining if a Zd of a controller node in the selected another replication zone includes data associated with the connecting NE.

6. The method of claim 4, further comprising:

receiving a done message from the controller node in the selected replication zone that indicates that transfer of the data associated with the connecting NE has completed; and

upon receiving the done message from the controller node in the selected replication zone, transmitting an acknowledgment message to the controller node in the selected replication zone that indicates that the done message has been received.

7. The method of claim 4, further comprising:

causing the data associated with the connecting NE that is stored in the Zd of the controller node to be replicated at one or more peer controller nodes of the controller node.

8. The method of claim 4, further comprising:

modifying the data associated with the connecting NE while the connecting NE is in the migration state.

9. A network device configured to support network element (NE) data migration, the network device implements a controller node in a cluster of controller nodes in a software defined networking (SDN) network, the network device comprising:

a non-transitory machine readable storage medium to store a NE data migration component; and

a processor communicatively coupled to the non-transitory machine readable storage medium, the processor configured to execute the NE data migration component, wherein the NE data migration component is configured to detect that a peer controller node in a same replication zone as the controller node has failed, wherein the peer controller node is a master for data associated with an NE and the controller node is a backup for the data associated with the NE, transition a state of the NE to a migration state, cause the data associated with the NE to be transferred from backup storage (Zb) of the controller node to dead storage (Zd) of the controller node, and in response to a request for the data associated with the NE from a requesting controller node, cause at least a fragment of the data associated with the NE to be transferred to the requesting controller node.

10. The network device of claim 9, wherein the NE data migration component is further configured to, in response to a connection request from a connecting NE, transition a state of the connecting NE to a migration state if the connecting NE is not already in the migration state, select a replication zone, determine if a Zd of a controller node in the selected replication zone includes data associated with the connecting NE, and upon a determination that the Zd of the controller node in the selected replication zone includes data associated with the connecting NE,

cause to be transmitted a request for the data associated with the connecting NE from the controller node in the selected replication zone, store at least a fragment of the data associated with the connecting NE received from the controller node in the selected replication zone in the Zd of the controller node, and cause the received fragment of the data associated with the connecting NE to be replicated to one or more peer controller nodes in a same replication zone as the controller node,

wherein the NE data migration component is further configured to determine whether all replication zones in the cluster of controller nodes have been selected, and upon a determination that all replication zones in the cluster of controller nodes have been selected,

cause the data associated with the connecting NE to be transferred from the Zd of the controller node to master storage (Zm) of the controller node and transition the state of the connecting NE to a stable state.

11. A non-transitory computer readable medium having instructions stored therein to be executed by a network device for supporting network element (NE) data migration, the network device acts as a controller node in a cluster of controller nodes in a software defined networking (SDN) network, the instructions when executed by the network device cause the network device to perform a set of operations comprising:

detecting that a peer controller node in a same replication zone as the controller node has failed, wherein the peer controller node is a master for data associated with an NE and the controller node is a backup for the data associated with the NE;

transitioning a state of the NE to a migration state;

transferring the data associated with the NE from backup storage (Zb) of the controller node to dead storage (Zd) of the controller node;

receiving a request for the data associated with the NE from a requesting controller node; and

transferring at least a fragment of the data associated with the NE to the requesting controller node.

12. The non-transitory computer readable medium of claim 11, wherein the instructions when executed by the network device cause the network device to perform a further set of operations comprising:

transmitting a done message to the requesting controller node that indicates that transfer of the data associated with the NE has completed.

13. The non-transitory computer readable medium of claim 11, wherein the instructions when executed by the network device cause the network device to perform a further set of operations comprising:

receiving an acknowledgment message from the requesting controller node that indicates that the done message has been received; and

deleting the data associated with the NE from the Zd of the controller node upon receiving the acknowledgment message.

14. The non-transitory computer readable medium of claim 11, wherein the instructions when executed by the network device cause the network device to perform a further set of operations comprising:

receiving a connection request from a connecting NE;

transitioning a state of the connecting NE to a migration state if the connecting NE is not already in the migration state;

selecting a replication zone;

determining if a Zd of a controller node in the selected replication zone includes data associated with the connecting NE;

upon determining that the Zd of the controller node in the selected replication zone includes data associated with the connecting NE,

requesting the data associated with the connecting NE from the controller node in the selected replication zone,

receiving at least a fragment of the data associated with the connecting NE from the controller node in the selected replication zone, and

storing the at least the fragment of the data associated with the connecting NE in the Zd of the controller node;

determining whether all replication zones in the cluster of controller nodes have been selected; and

upon determining that all replication zones in the cluster of controller nodes have been selected,

transferring the data associated with the connecting NE from the Zd of the controller node to master storage (Zm) of the controller node, and

transitioning the state of the connecting NE to a stable state.

15. The non-transitory computer readable medium of claim 14, wherein the instructions when executed by the network device cause the network device to perform a further set of operations comprising:

upon determining that not all replication zones in the cluster of controller nodes have been selected, selecting another replication zone not previously selected for determining if a Zd of a controller node in the selected another replication zone includes data associated with the connecting NE.

16. The non-transitory computer readable medium of claim 14, wherein the instructions when executed by the network device cause the network device to perform a further set of operations comprising:

receiving a done message from the controller node in the selected replication zone that indicates that transfer of the data associated with the connecting NE has completed; and

upon receiving the done message from the controller node in the selected replication zone, transmitting an acknowledgment message to the controller node in the selected replication zone that indicates that the done message has been received.

17. The non-transitory computer readable medium of claim 14, wherein the instructions when executed by the network device cause the network device to perform a further set of operations comprising:

causing the data associated with the connecting NE that is stored in the Zd of the controller node to be replicated at one or more peer controller nodes in a same replication zone as the controller node.

18. The non-transitory computer readable medium of claim 14, wherein the instructions when executed by the network device cause the network device to perform a further set of operations comprising:

modifying the data associated with the connecting NE while the connecting NE is in the migration state.

19. A computing device implementing a plurality of virtual machines for implementing network function virtualization (NFV), wherein a virtual machine from the plurality of virtual machines is configured to implement a controller node that supports network element (NE) data migration, the controller node is part of a cluster of controller nodes in a software defined networking (SDN) network, the computing device comprising:

a storage medium to store a NE data migration component; and

a processor communicatively coupled to the storage medium, the processor configured to execute the virtual machine, where the virtual machine is configured to implement the NE data migration component, the NE data migration component configured to detect that a peer controller node in a same replication zone as the controller node has failed, wherein the peer controller node is a master for data associated with an NE and the controller node is a backup for the data associated with the NE, transition a state of the NE to a migration state, cause the data associated with the NE to be transferred from backup storage (Zb) of the controller node to dead storage (Zd) of the controller node, and in response to a request for the data associated with the NE from a requesting controller node, cause at least a fragment of the data associated with the NE to be transferred to the requesting controller node.

20. The computing device of claim 19, wherein the NE data migration component is further configured to, in response to a connection request from a connecting NE, transition a state of the connecting NE to a migration state if the connecting NE is not already in the migration state, select a replication zone, determine if a Zd of a controller node in the selected replication zone includes data associated with the connecting NE, and upon a determination that the Zd of the controller node in the selected replication zone includes data associated with the connecting NE,

cause to be transmitted a request for the data associated with the connecting NE from the controller node in the selected replication zone, store at least a fragment of the data associated with the connecting NE received from the controller node in the selected replication zone in the Zd of the controller node, and cause the received fragment of the data associated with the connecting NE to be replicated to one or more peer controller nodes in a same replication zone as the controller node,

wherein the NE data migration component is further configured to determine whether all replication zones in the cluster of controller nodes have been selected, and upon a determination that all replication zones in the cluster of controller nodes have been selected,

cause the data associated with the connecting NE to be transferred from the Zd of the controller node to master storage (Zm) of the controller node and transition the state of the connecting NE to a stable state.