You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 14
Next »
Monday, January 13
Track | Key Points | Challenges | Next Steps / AIs |
---|
Testing | Have 3 participants providing VNFs for testing Working on two infrastructures, with 3rd being setup - 2 OpenStack / ONAP ElAlto
- 1 OpenStack / ONAP Dublin (virtual, being setup)
VNF Images have uploaded to infrastructure | - Getting infrastructure up and ready for testing
- Some issues with ONAP reaching Open Stack API (should be solved by end of today)
| - Running conformance test cases
- Run validation test cases
|
CNTT | Community alignment | - Need to align release with main open source communities.
- OPFN, ONAP, OVP.
| - cross-community sessions to go through the details.
|
Containers verification | - Containers technology is evolving technology, how CNTT will adopt such a dynamic environment.
| - Launching/supporting OVP Phase 2.0 taking MVP approach.
|
OPNFV | CIRV is approved project in OPNFV - this is the delivery of RI and RC for CNTT.
|
|
|
CI/CD Evolution to solve today's problems | - Writing/fixing Jenkins is hard, need more modern solutions,...
- but which one(s)?
- Projects will have greater responsibilities/More on their own
| - propose a transition plan, once we agree / accept the migration pain and real $$ costs
|
OPNFV PDF to Airship Manifest transformation | - ← They aren't the same (but certainly possible to evolve to new/better description).
| |
VMware Integrated OpenStack Reference Implementation | Mark Beierl - add your notes! | This is a Project proposal! VCF Installer |
ONAP
| ONAP Usability
| - Unawareness of key documentation
- Unawareness of what has been done i.e. Modularity
| - Promote what we have done- bi-weekly news
- Provide guidelines to PTL
- Focus on Core Use Cases/Core components to reduce the complexity - including prioritization
|
Platform Maturity for Guilin | Are we making progress on platform maturity? - Performance, Stability - only Integration checks
- Resiliency, Scalability = OOM?
- Operability - upgrade build
| - During the project lifecycle & Reviews, let's review these potential assumptions with the PTL
- Platform enrichments vs full E2E use cases
- CI/CD investments
- Introduce S3P reqs through the new Requirements subcommittee (formerly Use Case reqs)
|
SO Enhancement | Next steps support: | - SO proposed architecture key additions:
- Puccini
- Artifacts
- k8s APIs
- Custom resources
- Custom controllers
|
SECCOM | Main requirements for Frankfurt - Python migration to version3
- Java migration to version 11
- CII badging with better code coverage
- OSJI backlogs
- Remove hardocded passwords
- Get HTTPS for all external ports
| How to get all OSJI solved by PTL ? => Need help from TSC to progress Proposals to remove all Root privileges to containers and to automatically check in Gating User management is also a key topic to be addressed. Some experience from ODL could be used. |
OOM: What's new | Main objectives for Frankfurt - Migrate to Kubernetes 1.16
- Migrate to Helm3
- Ingress controller introduction
- Database consolidation ongoing
- Storage class
- Password management
Creation of template for Helm charts
| Discussions on database: do we still need so many DB types ? Impacts on operations (backup/restore) Discussions on password managementto contuniue with dedicated sessions tomorrow |
Closed Loop | TOSCA based closed Loop Extend closed loop from DACE/Policy to other appalications CLAMP extension - pre-deployment verification
- app deployment
- CL monitoring
- CL update/delete
|
|
A
Tuesday, January 14
Track | Key Points | Challenges | Next Steps / AIs |
---|
Testing |
|
|
|
CNTT |
|
|
|
OPNFV |
|
|
|
ONAP |
|
|
|
Wednesday, January 15
Track | Key Points | Challenges | Next Steps / AIs |
---|
Testing |
|
|
|
CNTT |
|
|
|
OPNFV |
|
|
|
ONAP |
|
|
|
Thursday, January 16
Track | Key Points | Challenges | Next Steps / AIs |
---|
Testing |
|
|
|
CNTT |
|
|
|
OPNFV |
|
|
|
ONAP |
|
|
|