diff options
| -rw-r--r-- | doc/ons2019/chainedci.png | bin | 0 -> 95192 bytes | |||
| -rw-r--r-- | doc/ons2019/ftth.png | bin | 0 -> 162001 bytes | |||
| -rw-r--r-- | doc/ons2019/index.html | 52 | ||||
| -rw-r--r-- | doc/ons2019/ons2019.md | 100 |
4 files changed, 152 insertions, 0 deletions
diff --git a/doc/ons2019/chainedci.png b/doc/ons2019/chainedci.png Binary files differnew file mode 100644 index 00000000..df594cd3 --- /dev/null +++ b/doc/ons2019/chainedci.png diff --git a/doc/ons2019/ftth.png b/doc/ons2019/ftth.png Binary files differnew file mode 100644 index 00000000..5b441d1d --- /dev/null +++ b/doc/ons2019/ftth.png diff --git a/doc/ons2019/index.html b/doc/ons2019/index.html new file mode 100644 index 00000000..3931b7f4 --- /dev/null +++ b/doc/ons2019/index.html @@ -0,0 +1,52 @@ +<html> +<head> +<title>From Infra to E2E testing</title> +<meta name="author" content="Cédric Ollivier"> +<meta name="viewport" + content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no"> +<link rel="stylesheet" href="../reveal.js/css/reveal.css"> +<link rel="stylesheet" href="../reveal.js/css/theme/white.css"> +<link rel="stylesheet" href="../reveal.js/lib/css/zenburn.css"> +<script> +var link = document.createElement( 'link' ); +link.rel = 'stylesheet'; +link.type = 'text/css'; +link.href = window.location.search.match( /print-pdf/gi ) ? '../reveal.js/css/print/pdf.css' : '../reveal.js/css/print/paper.css'; +document.getElementsByTagName( 'head' )[0].appendChild( link ); +</script> +</head> +<body> + <div class="reveal"> + <div class="slides"> + <section data-markdown="ons2019.md" data-separator="^\n\n\n" + data-separator-vertical="^\n\n" data-separator-notes="^Note:"></section> + </div> + </div> + <script src="../reveal.js/lib/js/head.min.js"></script> + <script src="../reveal.js/js/reveal.js"></script> + <script> + Reveal.initialize({ + dependencies : [ { + src : '../reveal.js/plugin/markdown/marked.js', + condition : function() { + return !!document.querySelector('[data-markdown]'); + } + }, { + src : '../reveal.js/plugin/markdown/markdown.js', + condition : function() { + return !!document.querySelector('[data-markdown]'); + } + }, { + src: '../reveal.js/plugin/highlight/highlight.js', + async: true, + callback: function() { + hljs.initHighlightingOnLoad(); + } + }, { + src: '../reveal.js/plugin/notes/notes.js', + async: true + } ] + }); + </script> +</body> +</html> diff --git a/doc/ons2019/ons2019.md b/doc/ons2019/ons2019.md new file mode 100644 index 00000000..6a7347c0 --- /dev/null +++ b/doc/ons2019/ons2019.md @@ -0,0 +1,100 @@ +# From Infra to E2E testing + +[Cédric Ollivier](mailto:cedric.ollivier@orange.com) + +2019/04/04 + + + +## Infrastructure verification + + +### Functest in a nutshell + +- verify any kind of OpenStack and Kubernetes deployments (OPNFV model) + including production environments +- conform with upstream rules (OpenStack gate jobs and Kubernetes conformance + tests) +- ensure that the platforms meet Network Functions Virtualization requirements + + +### Functest suites + +- all functional tests as defined by the upstream communities (e.g. Tempest, + neutron-tempest-api, Barbican, Patrole...) +- upstream API and dataplane benchmarking tools (Rally, Vmtp and Shaker) +- Virtual Network Function deployments and testing (vIMS, vRouter and vEPC) + + +### Xtesting in a nutshell + +- allow the developer to work only on the test suites without diving into + CI/CD integration +- simplify test integration in a complete LFN-based CI/CD toolchain (e.g. + Jenkins, Testing Containers, Test API and dashboard) +- allow a proper design and verify multiple components in the same CI/CD + toolchain (OpenStack, Kubernetes, ONAP, etc.) + +**Easy to use and very useful for any CI/CD toochain** + + +### Chained CI + + +<!-- .element: style="border: 0" --> + + + +## End2end network services testing + + +### Network automation journey + +- test network equipment and software including the Data-Center infrastructure +- improve method and validation process to shorten the TTM +- need tools and methodology to quickly disseminate CI/CD culture and assemble + sparsed testcases verifying network services + +**Why not leveraging on existing opensource tools such as Xtesting?** + + +### Deploy your own testing toolchain + +- deploy anywhere the full OPNFV CI/CD toolchain in a few commands +- could be instantiated for testing services out of the infrastructure domain +- offer all Xtesting-based fonctional jobs (e.g. Functest) to the endusers + + +### Testing [FTTH](https://en.wikipedia.org/wiki/Fiber_to_the_x) equipment + + +<!-- .element: style="border: 0; width: 90%" --> + + +### Demo + +- describe the testcase execution +- build and publish your container +- list your test in the toolchain description +- deploy your own toolchain in a few commands + +https://wiki.opnfv.org/pages/viewpage.action?pageId=32015004 + + + +## Conclusion + + +### Conclusion + +- Xtesting is a key helper from first tests to full end2end service testing +- And we are still pushing the limits: + - allow verifying production Infrastructure and then break the classical + preproduction/production model + - support Raspberry Pi + +**Upstream first! Try it, and you will love it! ** + + + +## Thank you |
