Cross-domain orchestration through boundary conditions
Presented herein are techniques to automatically provision cross-domain end-to-end services. A method includes receiving, at a cross-domain orchestrator, a request for a service, decomposing the request for the service into a first provisioning command and into a second provisioning command, sending the first and second provisioning commands to the first and second domains, respectively, receiving, from the first domain, in response to the first provisioning command, a first constraint associated with the first resource of the first domain, receiving, from the second domain, in response to the second provisioning command, a second constraint associated with the second resource of the second domain, distributing the first constraint to the second domain, and the second constraint to the first domain; and initiating, based on the first and second constraints, the service using the first resource of the first domain and the second resource of the second domain.
1. A method comprising:
receiving, at a cross-domain orchestrator, a request for a service;
determining that the service requires a first resource of a first domain and a second resource of a second domain;
decomposing the request for the service into a first provisioning command and into a second provisioning command;
sending the first provisioning command to the first domain;
sending the second provisioning command to the second domain;
receiving, from the first domain, in response to the first provisioning command, a first constraint associated with the first resource of the first domain;
receiving, from the second domain, in response to the second provisioning command, a second constraint associated with the second resource of the second domain;
distributing the first constraint to the second domain, and the second constraint to the first domain; and
initiating, based on the first constraint and the second constraint, the service using the first resource of the first domain consistent with the first constraint and the second resource of the second domain consistent with the second constraint.
2. The method of claim 1 , further comprising resolving the first constraint in view of the second constraint.
3. The method of claim 1 , further comprising receiving the request for the service as a service intent.
4. The method of claim 1 , further comprising, sending a third provisioning request to the first domain in response to the second constraint.
5. The method of claim 1 , further comprising ontology mapping a third constraint received from the first domain to a re-formatted third constraint that is understood by the second domain, and sending the re-formatted third constraint to the second domain.
6. The method of claim 1 , wherein the first constraint and the second constraint define boundary conditions of at least one of the first domain and the second domain.
7. The method of claim 6 , wherein at least one of the first constraint and the second constraint comprises at least one of an autonomous system number, an Internet Protocol address, a subnet address, a radio parameter, or a virtual local area network identifier.
8. The method of claim 1 , further comprising instantiating a YANG model to keep track of the first constraint associated with the first resource of the first domain and the second constraint associated with the second resource of the second domain.
9. The method of claim 8 , wherein at least one of the first constraint or the second constraint comprises a resource identifier, a logical condition, and a value of a resource corresponding to the resource identifier.
10. The method of claim 9 , wherein the logical condition comprises at least one of equality, greater than, less than, or query.
11. A device comprising:
an interface configured to enable network communications;
a memory; and
one or more processors coupled to the interface and the memory, and configured to:
receive, at a cross-domain orchestrator, a request for a service;
determine that the service requires a first resource of a first domain and a second resource of a second domain;
decompose the request for the service into a first provisioning command and into a second provisioning command;
send the first provisioning command to the first domain;
send the second provisioning command to the second domain;
receive, from the first domain, in response to the first provisioning command, a first constraint associated with the first resource of the first domain;
receive, from the second domain, in response to the second provisioning command, a second constraint associated with the second resource of the second domain;
distribute the first constraint to the second domain, and the second constraint to the first domain; and
initiate, based on the first constraint and the second constraint, the service using the first resource of the first domain consistent with the first constraint and the second resource of the second domain consistent with the second constraint.
12. The device of claim 11 , wherein the one or more processors are further configured to resolve the first constraint in view of the second constraint.
13. The device of claim 11 , wherein the one or more processors are further configured to receive the request for the service as a service intent.
14. The device of claim 11 , wherein the one or more processors are further configured to send a third provisioning request to the first domain in response to the second constraint.
15. The device of claim 11 , wherein the one or more processors are further configured to ontology map a third constraint received from the first domain to a re-formatted third constraint that is understood by the second domain, and send the re-formatted third constraint to the second domain.
16. The device of claim 11 , wherein the first constraint and the second constraint define boundary conditions of at least one of the first domain and the second domain.
17. The device of claim 16 , wherein at least one of the first constraint and the second constraint comprises at least one of an a autonomous system number, an Internet Protocol address, a subnet address, a radio parameter, or a virtual local area network identifier.
18. A non-transitory tangible computer readable storage media encoded with instructions that, when executed by at least one processor, is configured to cause the at least one processor to:
receive, at a cross-domain orchestrator, a request for a service;
determine that the service requires a first resource of a first domain and a second resource of a second domain;
decompose the request for the service into a first provisioning command and into a second provisioning command;
send the first provisioning command to the first domain;
send the second provisioning command to the second domain;
receive, from the first domain, in response to the first provisioning command, a first constraint associated with the first resource of the first domain;
receive, from the second domain, in response to the second provisioning command, a second constraint associated with the second resource of the second domain;
distribute the first constraint to the second domain, and the second constraint to the first domain; and
initiate, based on the first constraint and the second constraint, the service using the first resource of the first domain consistent with the first constraint and the second resource of the second domain consistent with the second constraint.
19. The non-transitory tangible computer readable storage media of claim 18 , further comprising instructions to cause the at least one processor to: resolve the first constraint in view of the second constraint.
20. The non-transitory tangible computer readable storage media of claim 18 , further comprising instructions to cause the at least one processor to: receive the request for the service as a service intent.