White Papers

Understanding OPNFV

Issue link: https://read.uberflip.com/i/1344850

Contents of this Issue

Navigation

Page 109 of 144

Understanding OPNFV 109 VNF vIMS (Clearwater) test Weekly ↑ Low Performance Full performance testing Weekly Components Full OpenStack testing, specific performance tests Daily Features Specific project tests, such as Doctor, Promise, security scan, HA, IPv6, SFC, and so on Daily Smoke Basic smoke, sanity, vPing tests Daily Verify (Health Check) Gating test Commit test A trust indicator has been defined for test cases and scenarios. Trust simply means that with each subsequent tier, the confidence in the scenario being tested increases. Test cases with higher levels of trust are also run at a lower frequency, because they are often long running tests, and hardware resources are always limited. In this manner, the trust indicator helps both users in evaluating scenarios and the infrastructure team in optimizing CI resources. Purpose A test case may have one of many purposes: ● To gate commits: The verify or health-check test is run in response to a commit to provide a +1 or -1 to gerrit. ● To gate a release: These are tests that must pass for a release to occur. As mentioned earlier, major OPNFV releases are on a 6-month cadence. Each major release also has minor releases, such as Danube 1.0, 2.0 and 3.0, each of which share the same stable branch and vary only in terms of bug fixes. ● Informational only: A number of performance tests do not gate a release. They are simply run to publish informational data. ● Benchmark: These metrics synthesize a benchmark based on performance metrics. ● OPNFV compliance: These tests test against a set of validation criteria to be able to use OPNFV trademarks. They are not to be confused with regulatory compliance testing.

Articles in this issue

view archives of White Papers - Understanding OPNFV