SYSTEM ARCHITECTURE FOR CLOUD-PLATFORM INFRASTRUCTURE LAYOUTS

• US 20160072899A1
• Filed: 08/04/2015
• Published: 03/10/2016
• Est. Priority Date: 09/04/2014
• Status: Active Grant

• Current Assignee: Accenture Global Services Limited (Accenture PLC)
• Original Assignee: Accenture Global Services Limited (Accenture PLC)
• Inventors: Tung, Teresa Sheausan, Gomadam, Karthik, Xie, Qing
• Granted Patent: US 9,979,603 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 41/0843 based on generic templates
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/145 involving simulating, designing, planning or modelling of a network
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 41/5045 Making service definitions prior to deployment
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring

Abstract

A system maintains, generates, and manages infrastructure layouts. The infrastructure layouts interconnect infrastructure components and capture relational aspects between the components within the interconnections. The infrastructure layouts map northbound services, which are service outputs, to southbound services, which are service capabilities, for fulfillment. The system may traverse a mapping from a northbound service to a fulfilling southbound service to generate a workflow to support deployment of the northbound service. In various implementations, the system may compare a path, which maps a northbound service to a southbound service, to a policy model to determine compliance with the policy.

Claims

1. A product comprising:

a machine readable medium other than a transitory signal; and

instructions stored on the machine readable medium, the instructions configured to, when executed by a processor;

access a catalog listing to determine a service offering;

determine a location of the service offering at an first endpoint on a core layout;

traverse a first path from the first endpoint to a second endpoint to determine a first received service to support deployment of the service offering;

traverse a second path from the first endpoint to a first node to determine an dependency for the service offering;

responsive to determining the dependency, determine to apply an extension to the core layout; and

traverse a third path from the first node to a third endpoint to determine a second received service to fulfill the dependency, the third path traversing the extension to the core layout.

2. The product of claim 1, where:

the service offering comprises a northbound service and the first and second received services comprise southbound services.

3. The product of claim 2, where:

the northbound service comprises wireless connectivity for an automobile.

4. The product of claim 3, where:

the first received service comprises a wireless carrier connection; and

the second received service comprises a wireless security protocol.

5. The product of claim 1, where the instructions are configured to determine to apply the extension to the core layout by accessing a manifest for the service offering, the manifest configured to identify the unfulfilled dependency for the service offering.

6. The product of claim 5, where the manifest comprises a fourth path from the service offering to the second received service.

7. The product of claim 6, where the instructions are configured to determine the extension by comparing the second path to the fourth path.

8. The product of claim 5, where the instructions are configured to apply the extension by determining a relationship between the first node and a second node within the extension.

9. The product of claim 8, where the instructions are configured to link the first and second nodes in accord with the relationship.

10. The product of claim 8, where the instructions are configured to access a template stored in the manifest.

11. The product of claim 10, where:

the template is configured to store the relationship as a triplet;

the triplet defines the first node as a subject of the triplet;

the triplet defines the second node as an object of the triplet.

12. The product of claim 1, where the extension defines a subclass of the first node.

13. The product of claim 12, where the instructions are configured to pass a relationship of the first node to the subclass.

14. The product of claim 1, where the instructions are further configured to:

receive a first request from an application programming interface (API) for the service offering; and

translate the first request into a second request for the first received service.

15. The product of claim 14, where the instructions are configured to implement a virtualization layer between the service offering and the first received service by translating the first request into the second request.

16. A method comprising:

accessing a catalog listing to determine a service offering;

determining, within a core layout, a location of the service offering at an first endpoint on the core layout;

traversing a first path from the first endpoint to a second endpoint to determine a first received service to support deployment of the service offering;

traversing a second path from the first endpoint to a first node to determine an unfulfilled dependency for the service offering;

responsive to determining the dependency;

determining to apply an extension to the core layout; and

traversing a third path from the first node to a third endpoint to determine a second received service to fulfill the dependency, the third path traversing the extension to the core layout.

17. The method of claim 16, where determining to apply the extension to the core layout comprises accessing a manifest for the service offering, the manifest configured to identify the unfulfilled dependency for the service offering.

18. The method of claim 17, where applying the extension comprises determining a relationship between the first node and a second node within the extension.

19. A system comprising:

a first interface configured to receive a first request for a first southbound service;

a second interface, coupled via a network to the first interface, the second interface configured to receive a second request for a northbound service; and

send, to the first interface, the request for the first southbound service;

first circuitry coupled to the first interface configured to provide the first southbound service, via the first interface responsive to the first request; and

second circuitry configured to;

access a manifest, the manifest configured to store a template comprising a path of nodes from the northbound service to the first southbound service;

perform a comparison between the template to a core layout stored at the first circuitry;

responsive to the comparison;

determine to apply an extension to the core layout; and

determine a relationship between a first node of the path and second node of the path, the first node of the path comprising a node within the core layout and the second node of the path comprising a node within the extension; and

apply the extension by joining the first and second nodes in accord with the relationship; and

generate the first request responsive to the second request by traversing the path.

20. The system of claim 19, where

the second circuitry is further configured to generate a third request for a second southbound service responsive to the second request;

the second southbound service is fulfilled by the core layout prior to application of the extension.