...
- Upgrade of ODL to Fluorine SR2 (CCSDK dependency)
- Platform Maturity (i.e., S3P items) https://wiki.onap.org/display/DW/Dublin+Release+Platform+Maturity
- Green color → Target level ( details see Platform Maturity below)
- Performance: Level 1
- Level 1: baseline performance criteria identified and measured (such as response time, transaction/message rate, latency, footprint, etc. to be defined on per component)
- Level 2: performance improvement plan created
- unzip feature.zip during building docker.
- Remove un-used bundles from CCSDK’s odlsli - depends on CCSDK
- Stability: Level 1 (may not reach 80% code coverageremain test coverage 50%)
- Level 1: 72 hour component-level soak test (random test transactions with 80% code coverage; steady load)
- Level 2: 72 hour platform-level soak test (random test transactions with 80% code coverage; steady load)
- Configuration Enhancement https://wiki.onap.org/display/DW/APPC+Configuration+Enhancement - Stretch goal
- Resiliency: Level 2
- Level 2: support automated failure detection & rerouting
- within a single geographic site
- stateless components: establish baseline measure of failed requests for a component failure within a site
- stateful components: establish baseline of data loss for a component failure within a site
- OOM: move to variable for database’s user/password
- CSIT OOM - Integration team
- Level 2: support automated failure detection & rerouting
- Security: Level 1, level 2 (PartialStretch)
- Level 1: CII Passing badge
- Including no critical and high known vulnerabilities > 60 days old
- Level 2: CII Silver badge, plus:
- All internal/external system communications shall be able to be encrypted: there is http internal connection between CDT and APPC, we need to find the resource to migrate from http to https.
- All internal/external service calls shall have common role-based access control and authorization using CADI framework.
- Level 1: CII Passing badge
- Scalability: Level 1
- Level 1: supports single site horizontal scale out and scale in, independent of other component
- APPC does not support dynamic cluster configuration in k8s only support static cluster configuration
- Clustering env with downstream: netconf, ansible
- Manageability: Level1, Level 2 (PartialStretch)
- Level 2:
- A component can be independently upgraded without impacting operation interacting components
- Component configuration to be externalized in a common fashion across ONAP projects
All application logging to adhere to ONAP Application Logging Specification v1.2Implement guidelines for a minimal container footprint - See this presentation and follow the Container Image Minimization Guidelines
- Level 2:
- Usability: Level 1
- Level 1:
- User guide created
- Deployment documentation
- API documentation
- Adherence to coding guidelines
- Level 1:
- Documentation updates (readthedocs) for Dublin, such as, but not limited to:
- LCM API Guide
- Release Notes
- CDT GUI Guide
- Code Coverage for CDT (Javascript) - TBD, no commitment at this stage
- Use Cases
- Closed Loop / E2E AutomationIntegrate automation test
- Change Management - APPC will continue supporting it.
- Closed Loop / E2E AutomationIntegrate automation test
...
APPC will contribute partially to the following use cases as part of the functional requirements.
- Closed Loop / E2E AutomationIntegrate automation test
- Change Management (will be done by Orange team)
...
Documentation, Training
- Highlight the team contributions to the specific document related to he the project (Config guide, installation guide...).
- Highlight the team contributions to the overall Release Documentation and training asset
- High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
- Documentation includes items such as:
- Installation instructions
- Configuration instructions
- Developer guide
- End User guide
- Admin guide
- ...
Note | ||
---|---|---|
| ||
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation assetAPPC will follow requirement by documentation team based on the APPC release capacities. |
Documentation updates planned for Dublin release are tracked under Documentation Epic:
Jira | ||||||
---|---|---|---|---|---|---|
|
...