aboutsummaryrefslogtreecommitdiffstats
path: root/INFO.yaml
blob: 730cd4a6b6cff735c64aa662fe1f4ab50e2219d8 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
---
project: 'Test framework for verifying infrastructure compliance (yardstick)'
project_creation_date: 'April 28th, 2015'
project_category: 'Integration & Testing'
lifecycle_state: 'Incubation'
project_lead: &opnfv_yardstick_ptl
    name: 'Ross Brattain'
    email: 'ross.b.brattain@intel.com'
    id: 'rbbratta'
    company: 'intel.com'
    timezone: 'PST'
primary_contact: *opnfv_yardstick_ptl
issue_tracking:
    type: 'jira'
    url: 'https://jira.opnfv.org/projects/Yardstick'
    key: 'Yardstick'
mailing_list:
    type: 'mailman2'
    url: 'opnfv-tech-discuss@lists.opnfv.org'
    tag: '[yardstick]'
realtime_discussion:
    type: irc
    server: 'freenode.net'
    channel: '#opnfv-yardstick'
meetings:
    - type: 'gotomeeting+irc'
      agenda:  'https://wiki.opnfv.org/display/yardstick/Yardstick+Meetings'
      url:  'https://global.gotomeeting.com/join/819733085'
      server: 'freenode.net'
      channel: '#opnfv-yardstick'
      repeats: 'weekly'
      time:  '08:30 UTC'
repositories:
    - 'yardstick'
committers:
    - <<: *opnfv_yardstick_ptl
    - name: 'Jörgen Karlsson'
      email: 'jorgen.w.karlsson@ericsson.com'
      company: 'ericsson.com'
      id: 'jnon'
    - name: 'Kubi'
      email: 'jean.gaoliang@huawei.com'
      company: 'huawei.com'
      id: 'kubi'
    - name: 'Rex Lee'
      email: 'limingjiang@huawei.com'
      company: 'huawei.com'
      id: 'rexlee8776'
    - name: 'Jing Lu'
      email: 'lvjing5@huawei.com'
      company: 'huawei.com'
      id: 'JingLu5'
    - name: 'zhihui wu'
      email: 'wu.zhihui1@zte.com.cn'
      company: 'zte.com.cn'
      id: 'wu.zhihui'
    - name: 'Trevor Cooper'
      email: 'trevor.cooper@intel.com'
      company: 'intel.com'
      id: 'trev'
    - name: 'Jack Chan'
      email: 'chenjiankun1@huawei.com'
      company: 'huawei.com'
      id: 'chenjiankun'
    - name: 'Emma Foley'
      email: 'emma.l.foley@intel.com'
      company: 'intel.com'
      id: 'elfoley'
    - name: 'Rodolfo Alonso Hernandez'
      email: 'rodolfo.alonso.hernandez@intel.com'
      company: 'intel.com'
      id: 'rodolfo.ah'
    - name: 'Kanglin Yin'
      email: '14_ykl@tongji.edu.cn'
      company: 'tongji.edu.cn'
      id: 'tjuyinkanglin'
    - name: 'Abhijit Sinha'
      email: 'abhijit.sinha@intel.com'
      company: 'intel.com'
      id: 'abhijitsinha'
tsc:
    # yamllint disable rule:line-length
    approval: 'http//meetbot.opnfv.org/meetings/'
    # yamllint enable rule:line-length
ypical VF | | | storage performance requirements, it can provide | | | pass/fail thresholds for test, staging, and production | | | NFVI environments. | +----------------+---------------------------------------------------------+ | VSperf | This project provides a framework for automation of NFV | | | data-plane performance testing and benchmarking. The | | | NFVI fast-path includes switch technology and network | | | with physical and virtual interfaces. VSperf can be | | | used to evaluate the suitability of different Switch | | | implementations and features, quantify data-path | | | performance and optimize platform configurations. | +----------------+---------------------------------------------------------+ | Yardstick | The goal of the Project is to verify the infrastructure | | | compliance when running VNF applications. NFV Use Cases | | | described in ETSI GS NFV 001 show a large variety of | | | applications, each defining specific requirements and | | | complex configuration on the underlying infrastructure | | | and test tools.The Yardstick concept decomposes typical | | | VNF work-load performance metrics into a number of | | | characteristics/performance vectors, which each of them | | | can be represented by distinct test-cases. | +----------------+---------------------------------------------------------+ =================================== The testing working group resources =================================== The assets ========== Overall Architecture -------------------- The Test result management can be summarized as follows:: +-------------+ +-------------+ +-------------+ | | | | | | | Test | | Test | | Test | | Project #1 | | Project #2 | | Project #N | | | | | | | +-------------+ +-------------+ +-------------+ | | | V V V +---------------------------------------------+ | | | Test Rest API front end | | http://testresults.opnfv.org/test | | | +---------------------------------------------+ ^ | ^ | V | | +-------------------------+ | | | | | | | Test Results DB | | | | Mongo DB | | | | | | | +-------------------------+ | | | | | +----------------------+ +----------------------+ | | | | | Testing Dashboards | | Landing page | | | | | +----------------------+ +----------------------+ The testing databases --------------------- A Mongo DB Database has been introduced for the Brahmaputra release. The following collections are declared in this database: * pods: the list of pods used for production CI * projects: the list of projects providing test cases * testcases: the test cases related to a given project * results: the results of the test cases * scenarios: the OPNFV scenarios tested in CI This database can be used by any project through the testapi. Please note that projects may also use additional databases. This database is mainly use to colelct CI results and scenario trust indicators. This database is also cloned for OPNFV Plugfest. The test API ------------ The Test API is used to declare pods, projects, test cases and test results. Pods correspond to the cluster of machines (3 controller and 2 compute nodes in HA mode) used to run the tests and defined in Pharos project. The results pushed in the database are related to pods, projects and cases. If you try to push results of test done on non referenced pod, the API will return an error message. An additional method dashboard has been added to post-process the raw results in the Brahmaputra release (deprecated in Colorado release). The data model is very basic, 5 objects are available: * Pods * Projects * Testcases * Results * Scenarios For detailed information, please go to http://artifacts.opnfv.org/releng/docs/testapi.html The reporting ------------- The reporting page for the test projects is http://testresults.opnfv.org/reporting/ .. figure:: ../../images/reporting_page.png :align: center :alt: Testing group reporting page This page provides a reporting per OPNFV release and per testing project. .. figure:: ../../images/reporting_danube_page.png :align: center :alt: Testing group Danube reporting page An evolution of this page is planned. It was decided to unify the reporting by creating a landing page that should give the scenario status in one glance (it was previously consolidated manually on a wiki page). The landing page (planned for Danube 2.0) will be displayed per scenario: * the status of the deployment * the score of the test projectS * a trust indicator Additional filters (version, installer, test collection time window,... ) are included. The test case catalog --------------------- Until the Colorado release, each testing project was managing the list of its test cases. It was very hard to have a global view of the available test cases among the different test projects. A common view was possible through the API but it was not very user friendly. In fact you may know all the cases per project calling: http://testresults.opnfv.org/test/api/v1/projects/<project_name>/cases with project_name: bottlenecks, functest, qtip, storperf, vsperf, yardstick It was decided to build a web site providing a consistent view of the test cases per project and allow any scenario owner to build his/her custom list of tests (Danube 2.0). Other resources =============== wiki: https://wiki.opnfv.org/testing mailing list: test-wg@lists.opnfv.org IRC chan: #opnfv-testperf weekly meeting (https://wiki.opnfv.org/display/meetings/TestPerf): * Usual time: Every Thursday 15:00-16:00 UTC / 7:00-8:00 PST * APAC time: 2nd Wednesday of the month 8:00-9:00 UTC ======================= Reference documentation ======================= +----------------+---------------------------------------------------------+ | Project | Documentation links | +================+=========================================================+ | Bottlenecks | https://wiki.opnfv.org/display/bottlenecks/Bottlenecks | +----------------+---------------------------------------------------------+ | CPerf | https://wiki.opnfv.org/display/cperf | +----------------+---------------------------------------------------------+ | Dovetail | https://wiki.opnfv.org/display/dovetail | +----------------+---------------------------------------------------------+ | Functest | https://wiki.opnfv.org/display/functest/ | +----------------+---------------------------------------------------------+ | Qtip | https://wiki.opnfv.org/display/qtip | +----------------+---------------------------------------------------------+ | Storperf | https://wiki.opnfv.org/display/storperf/Storperf | +----------------+---------------------------------------------------------+ | VSperf | https://wiki.opnfv.org/display/vsperf | +----------------+---------------------------------------------------------+ | Yardstick | https://wiki.opnfv.org/display/yardstick/Yardstick | +----------------+---------------------------------------------------------+