Network configuration service discovery

• US 10,148,506 B1
• Filed: 06/28/2016
• Issued: 12/04/2018
• Est. Priority Date: 06/28/2016
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Anburose, Nirmal, A, Chandrasekhar
• Primary Examiner(s): Gilles, Jude Jean
• Application Number:
  US15/195,960
• Time in Patent Office: 889 Days
• Field of Search: 709223, 709217, 709201, 709203, 709202, 709219, 709212, 709206, 709225, 709224
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: H04L 12/4641 Virtual LANs, VLANs, e.g. virtual private networks [VPN] LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/0853 by actively collecting configuration information or by backing up configuration information
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/5006 Creating or negotiating SLA contracts, guarantees or penalties
• CPC Class Codes: H04L 41/5058 Service discovery by the service manager
• CPC Class Codes: H04L 41/5077 wherein the managed service relates to simple transport services, i.e. providing only network infrastructure
• CPC Class Codes: H04L 45/64 using an overlay routing layer
• CPC Class Codes: H04L 67/53 using third party service providers

Abstract

A system and method for service discovery. A network management system fetches, from a first network device, configuration data associated with a service executing on the first network device. In response to determining that the service extends across multiple network devices, the network management system constructs, based on the configuration data, a first partial service instance associated with the service executing on the first network device. The network management system merges a plurality of partial service instances to form a merged partial service instance, the plurality of partial service instances including the first partial service instance and a second partial service instance associated with the service executing on a different network device. The network management system promotes the merged partial service instance as a service instance.

Claims

1. A method comprising:

fetching, by a network management system and from a first network device, configuration data associated with a service executing on the first network device;

in response to determining that the service extends across multiple network devices, constructing, by the network management system and based on the configuration data, a first partial service instance associated with the service executing on the first network device;

merging, by the network management system, a plurality of partial service instances to form a merged partial service instance, the plurality of partial service instances including the first partial service instance and a second partial service instance associated with the service executing on a different network device; and

promoting the merged partial service instance as a service instance.

2. The method of claim 1, wherein promoting the merged partial service instance as a service instance includes storing the service instance as a service object in the service database, wherein the service object includes service-level configuration information associated with the service instance.

3. The method of claim 1, wherein each service is characterized by a service model and by a mapper with a device schema having one or more attributes, the service model having a merge attribute mapped on one of the device schema attributes, wherein the merge attribute has a value, and

wherein merging includes selecting, as the second partial instance, a candidate partial service instance having a value of the merge attribute that matches the value of the merge attribute for the first partial service instance.

4. The method of claim 1, wherein each service is characterized by a service model having a merge attribute and by a mapper with a device schema having a first attribute and a second attribute, the merge attribute mapped on the first and second attributes, wherein the merge attribute has a value, and wherein each of the first and second device schema attributes include one or more values;

wherein merging includes selecting a candidate partial service instance as the second partial service instance, wherein one of the candidate partial service instance'"'"'s second attributes has a value that matches one of the first attribute values of the first partial service instance and wherein one of the candidate partial service instance'"'"'s first attributes has a value that matches one of the second attribute values of the first partial service instance.

5. The method of claim 1, wherein the service is characterized by a service model having a plurality of attributes, and

wherein merging includes selecting, as the second partial service instance, a candidate partial service instance having each of the plurality of attributes in the service model.

6. The method of claim 1, wherein each service is characterized by a service model and by a mapper with a device schema having one or more attributes, the service model having a merge attribute mapped on one of the device schema attributes, wherein the merge attribute has a value, and

wherein merging includes selecting, as the second partial service instance, a candidate partial service instance having each of the plurality of attributes in the service model and having a value of the merge attribute that matches the value of the merge attribute for the first partial service instance.

7. The method of claim 1, wherein the plurality of partial service instances further includes a third partial service instance, the third partial service instance associated with the service executing on a third network device.

8. The method of claim 7, wherein each service is characterized by a service model and by a mapper with a device schema having one or more attributes, the service model having a merge attribute mapped on one of the device schema attributes, wherein the merge attribute has a value, and

wherein merging includes identifying the second and the third partial service instances based on values of the merge attributes of the first, second and third partial service instances.

9. The method of claim 7, wherein each service is characterized by a service model and by a mapper with a device schema having one or more attributes, the service model having a merge attribute mapped on one of the device schema attributes, wherein the merge attribute has a value, and

wherein merging includes:

selecting, as the second partial service instance and from the plurality of partial service instances, a first candidate partial service instance having each of the plurality of attributes in the service model and having a value of the merge attribute that matches the value of the merge attribute for the first partial service instance; and

selecting, as the third partial service instance and from the plurality of partial service instances, a second candidate partial service instance having each of the plurality of attributes in the service model and having a value of the merge attribute that matches the value of the merge attribute for the first partial service instance.

10. The method of claim 1, wherein each service is characterized by a service model, and

wherein promoting the merged partial service instance as a service instance includes:

determining, from the service model, a minimum number of partial service instances required for the merged partial service instance to be promoted as a service instance;

if the merged partial service instance was formed from less than the minimum number of partial service instances required, storing the merged partial service instance in a partial service instance database; and

if the merged partial service instance was formed from at least the minimum number of partial service instances required, storing service-level configuration information associated with the service to a service database.

11. The method of claim 1, wherein each service is characterized by a service model and by a mapper with a device schema having one or more attributes, the service model having a merge attribute mapped on one of the device schema attributes, wherein the merge attribute has a value, and

wherein merging includes:

identifying, by the network management system, the second partial service instance based on the value of the merge attribute of the first and second partial service instances; and

merging the first and second partial service instances based on the merge strategy.

12. The method of claim 1, wherein each service is characterized by a service model and by a mapper with a device schema having one or more attributes, the service model having a merge attribute mapped on one of the device schema attributes, wherein the merge attribute has a value, and

wherein merging includes:

selecting, as the second partial service instance, a candidate partial service instance having each of the plurality of attributes in the service model and having a value of the merge attribute that matches the value of the merge attribute for the first partial service instance; and

merging the first and second partial service instances based on the merge strategy.

13. The method of claim 1, wherein the second partial service instance is a merged partial service instance retrieved from a partial service database.

14. The method of claim 1, further comprising:

suggesting, by a network management system, one or more merge strategies for a service model; and

receiving an input selecting one of the merge strategies; and

adding the selected merge strategy to the service model.

15. The method of claim 1, wherein each service is characterized by a service model and by a mapper with a device schema having one or more attributes, the service model having a merge attribute mapped on one of the device schema attributes,

wherein a second attribute of the plurality of attributes has an expected value, and

wherein constructing includes:

comparing a value of the second attribute received from the first network device to the expected value of the second attribute; and

if the value received from the first network device does not match the expected value, storing the value of the second attribute received from the first network device in memory to be used as the value of the second attribute when configuring the service on the first network device.

16. The method of claim 1, wherein each service is characterized by a service model and by a mapper with a device schema having one or more attributes, the service model having a merge attribute mapped on one of the device schema attributes, wherein the merge attribute has a value,

wherein merging includes:

retrieving a candidate partial service instance from a partial service database;

if the candidate partial service instance has a value of the merge attribute that matches the value of the merge attribute for the first partial service instance, selecting the candidate partial service instance as the second partial service instance, and

wherein promoting includes;

validating the merged partial service instance as a service;

if the merged partial service instance is validated as a service, storing the merged partial service instance to the service database; and

if the merged partial service instance is not validated as a service, storing the merged partial service instance to the partial service database.

17. The method of claim 1, wherein each service is characterized by a service model and by a mapper with a device schema having one or more attributes, the service model having a merge strategy and a merge attribute mapped on one of the device schema attributes, wherein the merge attribute has a value,

wherein merging includes:

retrieving a candidate partial service instance from a partial service database;

if the candidate partial service instance has a value of the merge attribute that matches the value of the merge attribute for the first partial service instance, selecting the candidate partial service instance as the second partial service instance; and

merging, based on the external mappings and the merge strategy, the first and second partial service instances, and

wherein promoting includes;

validating the merged partial service instance as a service;

if the merged partial service instance is validated as a service, storing the merged partial service instance to the service database; and

if the merged partial service instance is not validated as a service, storing the merged partial service instance to the partial service database.

18. The method of claim 1, wherein each service is characterized by a service model and by a mapper with a device schema having one or more attributes, the service model having a merge strategy, one or more external mappings and a merge attribute mapped on one of the device schema attributes, wherein the merge attribute has a value,

wherein merging includes:

retrieving a candidate partial service instance from a partial service database;

if the candidate partial service instance has a value of the merge attribute that matches the value of the merge attribute for the first partial service instance, selecting the candidate partial service instance as the second partial service instance; and

merging, based on the external mappings and the merge strategy, the first and second partial service instances, and

wherein promoting includes;

checking the merged partial service instance for validation errors;

if there are no validation errors, storing the merged partial service instance as a service object to the service database; and

if there are validation errors, storing the merged partial service instance to the partial service database.

19. A service management system, comprising:

a service database;

one or more service handlers connected to the service database;

a processor; and

at least one non-transitory computer-readable storage medium storing instructions that are executable by the processor to;

fetch, from a first network device, configuration data associated with a service executing on the first network device;

in response to determining that the service extends across multiple network devices, construct, based on the configuration data, a first partial service instance associated with the service executing on the first network device;

merge a plurality of partial service instances to form a merged partial service instance, the plurality of partial service instances including the first partial service instance and a second partial service instance associated with the service executing on a different network device; and

promote the merged partial service instance as a service instance.

20. The service management system of claim 19, wherein the instructions that are executable by the processor to promote the merged partial service instance as a service instance include instructions that are executable by the processor to store the merged partial service instance as a service object in the service database, wherein the service object includes service-level configuration information associated with the service instance.

21. The service management system of claim 19, wherein each service is characterized by a service model and by a mapper with a device schema having one or more attributes, the service model having a merge attribute mapped on one of the device schema attributes, wherein the merge attribute has a value, and

wherein the instructions that are executable by the processor to merge a plurality of partial service instances to form a merged partial service instance include instructions that are executable by the processor to select, as the second partial instance, a candidate partial service instance having a value of the merge attribute that matches the value of the merge attribute for the first partial service instance.

22. The service management system of claim 19, wherein each service is characterized by a service model and by a mapper with a device schema having a first attribute and a second attribute, the merge attribute mapped on the first and second attributes, wherein the merge attribute has a value, and wherein each of the first and second device schema attributes include one or more values, and

wherein the instructions that are executable by the processor to merge a plurality of partial service instances to form a merged partial service instance include instructions that are executable by the processor to select a candidate partial service instance as the second partial service instance, wherein one of the candidate partial service instance'"'"'s second attributes has a value that matches one of the first attribute values of the first partial service instance and wherein one of the candidate partial service instance'"'"'s first attributes has a value that matches one of the second attribute values of the first partial service instance.

23. The service management system of claim 19, wherein each service is characterized by a service model and by a mapper with a device schema having a first attribute and a second attribute, the merge attribute mapped on the first and second attributes, wherein the merge attribute has a value, and wherein each of the first and second device schema attributes include one or more values, and

wherein the instructions that are executable by the processor to merge a plurality of partial service instances to form a merged partial service instance include instructions that are executable by the processor to select, as the second partial service instance, a candidate partial service instance having each of the plurality of attributes in the service model.

24. The service management system of claim 19, wherein each service is characterized by a service model, and

wherein the instructions that are executable by the processor to promote the merged partial service instance as a service instance include instructions that are executable by the processor to:

determine, from the service model, a minimum number of partial service instances required for the merged partial service instance to be promoted as a service instance;

if the merged partial service instance was formed from less than the minimum number of partial service instances required, store the merged partial service instance in a partial service instance database; and

if the merged partial service instance was formed from at least the minimum number of partial service instances required, store service-level configuration information associated with the service to a service database.

25. The service management system of claim 19, wherein each service is characterized by a service model and by a mapper with a device schema having one or more attributes, the service model having a merge attribute mapped on one of the device schema attributes, wherein the merge attribute has a value, and

wherein the instructions that are executable by the processor to merge a plurality of partial service instances to form a merged partial service instance include instructions that are executable by the processor to:

identify the second partial service instance based on the value of the merge attribute of the first and second partial service instances; and

merge the first and second partial service instances based on the merge strategy.

26. The service management system of claim 19, wherein each service is characterized by a service model and by a mapper with a device schema having one or more attributes, the service model having a merge attribute mapped on one of the device schema attributes, wherein the merge attribute has a value, and

wherein the instructions that are executable by the processor to merge a plurality of partial service instances to form a merged partial service instance include instructions that are executable by the processor to:

select, as the second partial service instance, a candidate partial service instance having each of the plurality of attributes in the service model and having a value of the merge attribute that matches the value of the merge attribute for the first partial service instance; and

merge the first and second partial service instances based on the merge strategy.

27. The service management system of claim 19, wherein the instructions further comprise instructions that are executable by the processor to:

suggest one or more merge strategies for a service model; and

receive an input selecting one of the merge strategies; and

add the selected merge strategy to the service model.

28. The service management system of claim 19, wherein each service is characterized by a service model and by a mapper with a device schema having one or more attributes, the service model having a merge attribute mapped on one of the device schema attributes,

wherein a second attribute of the plurality of attributes has an expected value, and

wherein the instructions that are executable by the processor to construct a first partial service instance includes instructions that are executable by the processor to:

compare a value of the second attribute received from the first network device to the expected value of the second attribute; and

if the value received from the first network device does not match the expected value, store the value of the second attribute received from the first network device in memory to be used as the value of the second attribute when configuring the service on the first network device.

29. A non-transitory computer-readable storage medium encoded with instructions that, when executed, cause at least one processor of a computing device to:

fetch, from a first network device, configuration data associated with a service executing on the first network device;

in response to determining that the service extends across multiple network devices, construct, based on the configuration data, a first partial service instance associated with the service executing on the first network device;

merge a plurality of partial service instances to form a merged partial service instance, the plurality of partial service instances including the first partial service instance and a second partial service instance associated with the service executing on a different network device; and

promote the merged partial service instance as a service instance.