...
High level overview of SNIRO
Use case Description:
Homing 1. Homing Use Case
The homing of resources is one of the fundamental requirements of provisioning a service over the cloud or non-cloud infrastructure. The Homing application allows designers of services/VNFs to specify their homing requirements (either in the Policy Service linked to the service model or directly in the TOSCA service model) and objective function (e.g., minimize latency). Then, at service deployment time, SNIRO collects information from A&AI, DCAE, and other sources to determine a homing solution that meets service constraints while considering both the service objective function and the service provider preferences (e.g., cost). SNIRO can home a request either to a cloud site where new virtual resources are to be created or to an existing service instance. When the services deployed become more complex (e.g., multiple VNFs with different constraints for individual VNFs and the combinations of VNFs) and the cloud infrastructure is large (e.g., dozens or more possible sites), such capability is essential for managing the services and the infrastructure.
2. Change Management Schedule Planning Use Case
Change Management (CM) application is responsible for managing and enforcing changes (e.g. device upgrade, configuration change, etc.) in the cloud and network infrastructure. The schedule planning application provides recommended schedules of changes for upgrading of VNFs under given constraints and current state of schedules and relationships of network elements. The primary challenge is when to schedule changes such that service disruption is minimized. SNIRO offers a schedule optimization service to the CM application, which can be invoked prior to schedule any change. A service designer designs a change request in SDC and configures the schedule requirements through policies. Prior to scheduling changes via Service Orchestrator (SO), the designer makes a call to the schedule optimization in SNIRO from SDC. SNIRO collects the existing scheduling information from a available ticketing system and vertical dependency information from A&AI and executes calculates a solution to the scheduling application in a scalable and resilient manner. Finally, the found schedules are recommended schedule is returned to SDC, which are is verified by the designer before pushing the schedules committing the schedules to Service Orchestrator.
Resources:
- Primary Contact Person
- Sastry Isukapalli - AT&T
- Names, gerrit IDs, and company affiliations of the committers
- Sastry Isukapalli - AT&T
- Ankit Patel - AT&T
- Matti Hiltunen - AT&T
- Shankar Naraynan - AT&T
- Joe D'Andrea - AT&T
- Names and affiliations of any other contributors
- Project Roles (include RACI chart, if applicable)
...