SYNCHRONIZING CONFIGURATION OF PARTNER OBJECTS ACROSS DISTRIBUTED STORAGE SYSTEMS USING TRANSFORMATIONS

• US 20160092463A1
• Filed: 09/25/2014
• Published: 03/31/2016
• Est. Priority Date: 09/25/2014
• Status: Active Grant

• Current Assignee: NetApp, Inc.
• Original Assignee: NetApp, Inc.
• Inventors: Vijayan, Anoop Chakkalakkal
• Granted Patent: US 9,836,476 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/0712 in a virtual computing platform, e.g. logically partitioned systems
• CPC Class Codes: G06F 11/1484 involving virtual machines
• CPC Class Codes: G06F 11/1658 Data re-synchronization of a redundant component, or initial sync of replacement, additional or spare unit
• CPC Class Codes: G06F 11/20 using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
• CPC Class Codes: G06F 11/2089 Redundant storage control functionality
• CPC Class Codes: G06F 16/10 File systems; File servers
• CPC Class Codes: G06F 16/128 Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion use of snapshots for error detection or correction G06F11/14, G06F11/16
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• CPC Class Codes: G06F 16/1827 Management specifically adapted to NAS management of storage area networks [SAN] G06F3/067
• CPC Class Codes: G06F 16/256 in federated or virtual databases
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 3/0607 by facilitating the process of upgrading existing storage systems, e.g. for improving compatibility between host and storage device
• CPC Class Codes: G06F 3/0665 at area level, e.g. provisioning of virtual or logical volumes
• CPC Class Codes: G06F 3/0667 at data level, e.g. file, record or object virtualisation
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Abstract

A configuration for a component of a primary node is synchronized with a configuration for a component of a partner node in a different cluster by replicating the primary node configuration with the partner node. A baseline configuration replication comprises a snapshot of a component configuration on the primary. The baseline configuration can be generated by traversing through the configuration objects, capturing their attributes and encapsulating them in a package. The baseline package can then be transferred to the partner node. The configuration objects can be applied on the partner node in the order in which they were captured on the primary node. Attributes of the configuration objects are identified that are to be transformed. Values for the identified attributes are transformed from a name space in the primary node to a name space in the partner node.

Claims

1. A method for replicating a component configuration from a first node to a second node, the method comprising:

receiving a first configuration object, the first configuration object having a first identifier in a first identifier space of the first node;

transforming the first identifier for the first configuration object into a second identifier in a second identifier space for the second node;

determining, based at least in part on the second identifier, whether a second configuration object corresponding to the first configuration object exists in a second configuration for a second component of the second node;

in response to determining that the second configuration object does not exist in the second configuration, creating the second configuration object in the second configuration and assigning the second identifier to the second configuration object; and

in response to determining that the second configuration object exists in the second configuration, modifying one or more attributes of the second configuration object to match one or more object attributes of the first configuration object.

2. The method of claim 1, wherein the component configuration comprises a configuration for a storage virtual machine (SVM) and wherein receiving the first configuration object comprises receiving a baseline configuration object for the SVM.

3. The method of claim 1, further comprising:

comparing one or more keys of the first configuration object with one or more keys of the second configuration object; and

in response to determining that the one or more keys of the first configuration object are less than the one or more keys of the second configuration object, deleting the second configuration object.

4. The method of claim 3, wherein the first configuration object is included in a plurality of baseline configuration objects, wherein the second configuration object is included in a plurality of partner configuration objects, and wherein said method further comprises:

ordering the plurality of baseline configuration objects and the plurality of partner configuration objects.

5. The method of claim 4, wherein ordering the plurality of baseline configuration objects and the plurality of partner configuration objects includes ordering the plurality of baseline configuration objects and the plurality of partner configuration objects according to an order of object creation.

6. The method of claim 1, wherein transforming the first identifier for the first configuration object into the second identifier in the second identifier space for the second configuration object comprises:

determining, based at least in part on a tag for the first configuration object and the second configuration object, a field name of an attribute storing the first identifier; and

utilizing the field name to obtain the first identifier from the first configuration object and to store the second identifier in the second configuration object.

7. The method of claim 6, wherein the tag for the first configuration object is specified in a configuration schema for the first configuration object.

8. A non-transitory machine readable medium having stored thereon instructions comprising machine executable code that when executed by at least one machine, causes the at least one machine to:

receive a first configuration object, the first configuration object having a first identifier in a first identifier space of a first node;

transform the first identifier for the first configuration object into a second identifier in a second identifier space for a second node;

determine, based at least in part on the second identifier, whether a second configuration object corresponding to the first configuration object exists in a second configuration for a second component of the second node;

in response to a determination that the second configuration object does not exist in the second configuration, create the second configuration object in the second configuration and assigning the second identifier to the second configuration object; and

in response to a determination that the second configuration object does exist in the second configuration, modify one or more attributes of the second configuration object to match one or more object attributes from the first configuration object.

9. The non-transitory machine readable medium of claim 8, wherein the first configuration object is included in a configuration for a storage virtual machine (SVM).

10. The non-transitory machine readable medium of claim 8, wherein the machine executable code further comprises machine executable code to cause the at least one machine to:

compare one or more keys of the first configuration object with one or more keys of the second configuration object; and

in response to a determination that the one or more keys of the first configuration object are less than the one or more keys of the second configuration object, delete the second configuration object.

11. The non-transitory machine readable medium of claim 10, wherein the first configuration object is included in a plurality of baseline configuration objects, wherein the second configuration object is included in a plurality of partner configuration objects, and wherein the machine executable code further comprises machine executable code to cause the at least one machine to:

order the plurality of baseline configuration objects and the plurality of partner configuration objects.

12. The non-transitory machine readable medium of claim 11, wherein the machine executable code to cause the at least one machine to order the plurality of baseline configuration objects and the plurality of partner configuration objects includes machine executable code to cause the at least one machine to order the plurality of baseline configuration objects and the plurality of partner configuration objects according to an order of object creation.

13. The non-transitory machine readable medium of claim 8, wherein the machine executable code to cause the at least one machine to transform the first identifier for the first configuration object into the second identifier in the second identifier space for the second configuration object includes the machine executable code to cause the at least one machine to:

determine, based at least in part on a tag for the first configuration object and the second configuration object, a field name of an attribute storing the first identifier; and

utilize the field name to obtain the first identifier from the first configuration object and to store second identifier in the second configuration object.

14. The non-transitory machine readable medium of claim 13, wherein the tag for the first configuration object is specified in a configuration schema for the first configuration object.

15. An apparatus comprising:

a processor; and

a non-transitory machine readable medium having stored thereon instructions comprising processor executable code that when executed by at least one processor, causes the apparatus to,

receive a first configuration object, the first configuration object having a first identifier in a first identifier space of a first node,

transform the first identifier for the first configuration object into a second identifier in a second identifier space for a second node,

determine, based at least in part on the second identifier, whether a second configuration object corresponding to the first configuration object exists in a second configuration for a second component of the second node,

in response to a determination that the second configuration object does not exist in the second configuration, create the second configuration object in the second configuration and assigning the second identifier to the second configuration object, and

in response to a determination that the second configuration object does exist in the second configuration, modify one or more attributes of the second configuration object to match one or more object attributes from the first configuration object.

16. The apparatus of claim 15, wherein the first configuration object is included in a configuration for a storage virtual machine (SVM).

17. The apparatus of claim 15, wherein the processor executable code further comprises processor executable code to cause the apparatus to:

compare one or more keys of the first configuration object with one or more keys of the second configuration object; and

in response to a determination that the one or more keys of the first configuration object are less than the one or more keys of the second configuration object, delete the second configuration object.

18. The apparatus of claim 17, wherein the first configuration object is included in a plurality of baseline configuration objects, wherein the second configuration object is included in a plurality of partner configuration objects, and wherein the processor executable code further comprises processor executable code to cause the apparatus to:

order the plurality of baseline configuration objects and the plurality of partner configuration objects.

19. The apparatus of claim 18, wherein the processor executable code to cause the apparatus to order the plurality of baseline configuration objects and the plurality of partner configuration objects includes processor executable code to cause the apparatus to order the plurality of baseline configuration objects and the plurality of partner configuration objects according to an order of object creation.

20. The apparatus of claim 15, wherein the processor executable code to cause the apparatus to transform the first identifier for the first configuration object into the second identifier in the second identifier space for the second configuration object includes processor executable code to cause the apparatus to:

determine, based at least in part on a tag for the first configuration object and the second configuration object, a field name of an attribute storing the first identifier; and

utilize the field name to obtain the first identifier from the first configuration object and to store second identifier in the second configuration object.