...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Dublin |
| Project Lifecycle State | Incubation |
| Participating Company | AT&T, Ericsson, Huawei, TechMahindra ? |
Scope
What is this release trying to address?
...
| Scope | Priority | Committer Lead | Resources Committed | Epic | Dependencies | |||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Technical Debt | Highest | Pamela Dragosh | Liam Fallon Ram Krishna Verma Jorge Hernandez James Hahn Michael Mokry - Libo Zheng - HPA OOF Model |
| ||||||||||||||||||||||||||||||||||||||||||||
| Policy Architecture Build | Highest | Platform Dedicated Resources
|
| Iteratively working with new models/templates being built for Model Drive Control Loop:
| ||||||||||||||||||||||||||||||||||||||||||||
| Logging Requirements - all components except policy/engine | High |
| ||||||||||||||||||||||||||||||||||||||||||||||
| Security Requirements | High |
|
| |||||||||||||||||||||||||||||||||||||||||||||
Control Loop Sub Committee Functional Requirements | High | Liam Fallon - shared models across PDP engines Josh Reich - Control Loop Coordination Pamela Dragosh - Guard/DCAE Configuration Pramod Jamkhedkar - Drools Control Loop Template, A&AI |
| Iteratively working with re-design of the Platform
| ||||||||||||||||||||||||||||||||||||||||||||
| AT&T Features/Fixes on the Casablanca codebase | Medium | Jorge Hernandez | Praveen Augustus |
|
Use Cases
DRAFT - not committed until resources are identified
| Use Case | Scope | Priority | Committer Lead | Resources committed | JIRA | Dependencies | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| vDNS (via Scale Out) | Control Loop Hardening | Highest | Pramod Jamkhedkar - A&AI work Tech Mahindra will provide - per Milind Jalwadi (Unlicensed) TSC call |
|
| |||||||||||||||||||||||||
| vFW | TBD - use APP-C LCM API vs old API for ModifyConfig
| High |
|
| ||||||||||||||||||||||||||
| 5G - FM Meta Data | DEFERRED TO NEXT RELEASE VES Event Registration - auto-generate control loop policies |
| ||||||||||||||||||||||||||||
| 5G - OOF & PCI | Adding 2nd control loop Add Control Loop Coordination Policies to support both control loops | Med | Wipro Corp. will provide |
|
| |||||||||||||||||||||||||
| vCPE | Test ONLY
| Med | ||||||||||||||||||||||||||||
| CCVPN | CCVPN Use Case (Dublin) - TBD Changes needed for policy | Med | Pamela Dragosh |
| TBD if this work is dependent upon the re-build.
| |||||||||||||||||||||||||
| BBS | NO REQUIREMENTS | |||||||||||||||||||||||||||||
| Change Management Dublin Extensions | Test ONLY Schedule optimization with Automated Conflict Avoidance Traffic Migration Workflow | Low | n/a |
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| Not enough resources to meet all the functional requirements. | All Epics are assessed a priority. | |
| Need the SO API defined by a reasonable timeframe for implementation to happen | We will use the current SO RESTful API until the new API is in place. |
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...