System architecture for cloud-platform infrastructure layouts

• US 9,979,603 B2
• Filed: 08/04/2015
• Issued: 05/22/2018
• 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
• Primary Examiner(s): Ibrahim, Mohamed
• Application Number:
  US14/817,582
• Publication Number:
  US 20160072899A1
• Time in Patent Office: 1,022 Days
• Field of Search: None
• 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 northbound technical service;

determine a location of the northbound technical service at a first endpoint on a core layout;

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

traverse a second path from the first endpoint to a first node to determine a dependency for the northbound technical service;

access a manifest, the manifest configured to store a template comprising a path of nodes supporting the dependency;

perform a comparison between the template and the core layout;

responsive to the comparison;

determine to apply an extension to the core layout;

traverse a third path from the first node to a third endpoint to determine a second received technical service that fulfills the dependency, the third path traversing the extension to the core layout;

responsive to traversal of the third path, generate a workflow including a deployment script to implement the second received technical service; and

execute the deployment script by deploying a web resource to implement the second received technical service to fulfill the northbound technical service within a deployed instance of the core layout.

2. The product of claim 1, where:

the first and second received technical services comprise southbound technical services.

3. The product of claim 2, where:

the northbound technical service comprises wireless connectivity for an automobile.

4. The product of claim 3, where:

the first received technical service comprises a wireless carrier connection; and

the second received technical service comprises a wireless security protocol.

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

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

7. The product of claim 6, 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.

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

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

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

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

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

11. The product of claim 10, where the instructions are configured to implement a virtualization layer between the northbound technical service and the first received technical service by translating the first request into the second request.

12. The product of claim 1, where the comparison comprises traversing a fourth path from the northbound technical service to the second technical received service.

13. A method comprising:

accessing a catalog listing to determine a northbound technical service;

determining, within a core layout, a location of the northbound technical service at a first endpoint on the core layout;

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

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

accessing a manifest, the manifest configured to store a template comprising a path of nodes supporting the dependency;

performing a comparison between the template and the core layout;

responsive to the comparison;

determine to apply an extension to the core layout;

traversing a third path from the first node to a third endpoint to determine a second received technical service that fulfills the dependency, the third path traversing the extension to the core layout; and

responsive to traversal of the third path, generating a workflow including a deployment script to implement the second received technical service; and

executing the deployment script by deploying a web resource to implement the second received technical service to fulfill the northbound technical service within a deployed instance of the core layout.

14. The method of claim 13, where the extension defines a subclass of the first node.

15. The method of claim 14, further comprising passing a relationship of the first node to the subclass.

16. The method of claim 13, further comprising:

receiving a first request from an application programming interface (API) for the northbound technical service; and

translating the first request into a second request for the first received technical service.

17. The method of claim 16, further comprising implementing a virtualization layer between the northbound technical service and the first received technical service by translating the first request into the second request.

18. The method of claim 13, where performing the comparison 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 technical service;

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

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

first circuitry coupled to the first interface configured to provide the first southbound technical 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 technical service to the first southbound technical service;

perform a comparison between the template and 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; and

responsive to the first request, generate a workflow including a deployment script to implement the first southbound technical service on the first circuitry; and

execute the deployment script by causing the first circuitry to deploy a web resource to implement the first southbound technical service to fulfill the second request for the northbound technical service within a deployed instance of the core layout.

20. The system of claim 19, where

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

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