1. Implementation Discussion Bin Hu (bh526r@att.com)
A DevOps Solution for Integrated NFV Platform and Beyond
Implementation Discussion
Bin Hu

2. Agenda Work Plan of 2019 Structure of Work Items and Leads
Infrastructure Evolution (Trevor Bramwell)
Code and Release Quality (Cristina Pauna and Cedric Ollivier)
Proposed Deliverables / Artifacts

3. Work Plan of 2019
Define deliverables / finished goods / what we can offer as OPNFV
Streamline workflow within and across
Installers, Infra WG (including security), Test WG, Cloud Native WG, Release WG
Evolve overall processes and role of feature projects to accommodate the new balanced strategy
Use case / test case / internal customer of DevOps platform
E.g. Edge Deployment as typical use case, test through DevOps platform, identify & fill gaps (incl. upstream)
Analyze opportunities for Cloud-Services based offering
Multiple factors should be considered: e.g. geographic distribution and heterogeneity of hardware for edge case and IOT case, and overall cost constrained by annual budget, etc.
Roadmap should include: e.g. what we must do on premise, and what we can put on cloud if it saves cost, and what is evolution path
Develop marketing message jointly with MWG

4. Structure of Work Items and Leads (12/06/2018)
Define deliverables / artifacts / what we can offer as OPNFV
TBD
CI/CD and XCI Evolution
Release Process Evolution
David McBride (Release WG)
Testing Evolution
Test WG
Compliance Evolution in OPNFV
NFVI test coverage and Broader LFN initiative
Trevor Cooper
Infrastructure Evolution
Trevor Bramwell (Infra WG)
Code and Release Quality
Security is part of it
Cristina Pauna and Cedric Ollivier
Use Case – Prioritization and Resource recommendation
General DevOps, Cloud Native, Edge, 5G
New Use Cases in the future
Qiao Fu

5. Infrastructure Evolution (Trevor Bramwell) (12/13/2018)
Labs
Hosting v.s. Packet.net
More information needed regarding costs of hosting v.s. support and break-even point, and other information such as capacity, networking options etc.
Perhaps we need to design a trial of packet.net
David M, Trevor B and Trevor C take the action to work on it.
PDF-based Information Model
LaaS for Multiple Labs
CI, Artifacts and Storage Evolution
Dynamic CI
PDF, SDF,

6. Code and Release Quality (Cristina Pauna and Cedric Ollivier) (12/20/2018)
A Process of Implementation is introduced
A template and examples are shared
Slides deck and Etherpad will be shared after New Year for further comments from community
To make the process, template and examples polished and more mature
This topic will be discussed again on Jan 24, 2019

7. Code and Release Quality (Cristina Pauna and Cedric Ollivier) (01/24/2019)
Proposal:
IRC:
Cristina will share the proposal in mailing list to get more feedback
The target is to get TSC approval of some of those proposals on 02/05/2019

8. Miscellaneous Discussions (01/31/2019)
Update of Code and Release Quality Improvement (Cristina Pauna)
Christina will ask for TSC approval of the suggested actions of the first 3 problems on 02/05/2019. This will be on TSC agenda on 02/05/2019
Infrastructure Evolution (Trevor B. and Trevor C.)
Live discussion captured in the slides deck
Trevor B. will develop a list of responsibilities for LF v.s. community
Continue to discuss this topic on 02/07/2019
IRC:

9. Miscellaneous Discussions (02/07/2019 – 1 of 2)
Infrastructure Evolution (Trevor B. and Trevor C.)
1st step: Trevor C continues to drive Intel's effort on replicating LaaS to Intel community lab
Document the best practice of LaaS replication
2nd step: Expand to other community labs.
Champion can be found at that time
The usage of community lab can be expanded as 3rd-party lab for compliance testing
Compliance Program Update (Trevor C and Georg K)
Now it is focusing on VNF testing in ONAP
Next OVP and Dovetail release is targeted in May, but quite stretch as resources are helping ONAP now

10. Miscellaneous Discussions (02/07/2019 – 2 of 2)
Update of Code and Release Quality Improvement (Cristina Pauna)
Proposal is to let each project decide whether they want to enforce this no-self-merge rule in this project or not. Single active committer project is always excepted.
Cristina takes the action to ask opinion of each PTL, and get a better overall picture.
IRC:

11. Proposed Deliverables / Artifacts
A “DevOps Solution”, e.g.:
Tooling to automatically compose the entire DevOps workflow
Some may be migrated to cloud service
Enhanced NFVI Compliance Program
E.g. broader test coverage and performance tests
E.g. compliance tools and methods for feeding into LFN compliance program
LaaS for LFN projects and stakeholders
Streamlined Integrated NFV Platform (NFVI)
E.g. consolidated and fewer scenarios, cloud native and edge focused, etc.
Packaged toolchains for more general purpose in a DevOps platform
Individual tools packaged into a series of tool suites

12. Questions?
Please direct any questions or comments to for discussion