From d27a391eba36d7066a3dba2c03c64649a752eb7a Mon Sep 17 00:00:00 2001 From: Cédric Ollivier Date: Mon, 30 Nov 2020 16:43:54 +0100 Subject: Publish CNTT/OPNFV CI assets MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit It will be introduced to ORAN. It's also available in [1] [1] http://testresults.opnfv.org/functest/oran Change-Id: I00c187a642ca0d03bffcdceed4592632f04d6a8f Signed-off-by: Cédric Ollivier --- docs/com/pres/oran/ftth.png | Bin 0 -> 162001 bytes docs/com/pres/oran/oran.md | 90 ++++++++++++++++++++++++++++++++++++++++++++ docs/com/pres/oran/rc1.png | Bin 0 -> 360960 bytes 3 files changed, 90 insertions(+) create mode 100644 docs/com/pres/oran/ftth.png create mode 100644 docs/com/pres/oran/oran.md create mode 100644 docs/com/pres/oran/rc1.png (limited to 'docs/com') diff --git a/docs/com/pres/oran/ftth.png b/docs/com/pres/oran/ftth.png new file mode 100644 index 000000000..5b441d1de Binary files /dev/null and b/docs/com/pres/oran/ftth.png differ diff --git a/docs/com/pres/oran/oran.md b/docs/com/pres/oran/oran.md new file mode 100644 index 000000000..87fba1306 --- /dev/null +++ b/docs/com/pres/oran/oran.md @@ -0,0 +1,90 @@ +--- +author: Cédric Ollivier +title: OPNFV/CNTT CI assets +date: 2020/12/01 +--- +## Continuous integration + + +### A few CNTT reqs + +- OPNFV has built a complete CI/CD toolchain for continuously deploying and + testing cloud infrastructure +- Reference conformance only requires for the local deployment of the + same components +- all test cases must be delivered as **Docker containers** including the + common test case execution and the unified way to manage all the interactions + +**Integrate smoothly and deploy fastly** + + +### How OPNFV/CNTT helps? + +- **Functest** offers a collection of state-of-the-art virtual infrastructure + test suites +- **Xtesting** helps assembling sparse test cases and accelerating the adoption + of CI/CD best practices +- **XtestingCI** eases deploying anywhere plug-and-play CI/CD toolchains in a + few commands +- **CNTT** defines conformance suites and its playbooks leveraging this 3 + testing frameworks + +**Leverage best opensource tools and practices** + + +### Testing [FTTH](https://en.wikipedia.org/wiki/Fiber_to_the_x) equipment + +![FTTH](ftth.png) + + +### Deploy your CI toolchain + +``` +virtualenv xtesting +. xtesting/bin/activate +pip install ansible +ansible-galaxy install collivier.xtesting +git clone https://gerrit.opnfv.org/gerrit/functest-xtesting functest-xtesting-src +ansible-playbook functest-xtesting-src/ansible/site.yml +deactivate +rm -rf functest-xtesting-src xtesting +``` + +**More scenarios in [[1]](https://wiki.opnfv.org/pages/viewpage.action?pageId=32015004)** + + + +## Testing + + +### Verif', Compliance and Interop' + +- verification allows skipping test if optional services or capabilities are + missing +- compliance forces the full API descriptions as currently proposed by + CNTT and then skips all optional capability testing +- the opensource certifications are driven by simple interoperability testing + (RefStack and OVP are about less than 10% of Functest. **trustability?**) + +**Fine tune the same test frameworks** + + +### [CNTT RC1](https://build.opnfv.org/ci/view/functest/job/functest-leguer-daily/12/) + +![RC1](rc1.png) + + + +## Conclusion + + +### Key takeaways + +- **test integration requirements** are crucial to smoothly assemble all + test cases +- leverage **existing** OPNFV testing knowledge (projects) and experience + (history) by utilising the OPNFV toolchain design already in-place +- **3000+** functional tests, **3 hours** upstream API and dataplane benchmarks + and VNFs automatically onboarded and tested **can be reused asis** + +**Keep it simple and do not reivent the wheel** diff --git a/docs/com/pres/oran/rc1.png b/docs/com/pres/oran/rc1.png new file mode 100644 index 000000000..9179f3bb6 Binary files /dev/null and b/docs/com/pres/oran/rc1.png differ -- cgit 1.2.3-korg