diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/proposal/integration_with_yardstick.rst | 32 | ||||
| -rw-r--r-- | docs/release/release-notes/brahmaputra.rst | 3 | ||||
| -rw-r--r-- | docs/release/release-notes/danube.rst | 159 | ||||
| -rw-r--r-- | docs/testing/developer/devguide/index.rst | 6 | ||||
| -rw-r--r-- | docs/testing/user/configguide/configuration.rst | 6 | ||||
| -rw-r--r-- | docs/testing/user/userguide/api.rst | 3 |
6 files changed, 98 insertions, 111 deletions
diff --git a/docs/proposal/integration_with_yardstick.rst b/docs/proposal/integration_with_yardstick.rst index a8298d6f..ce94b8fe 100644 --- a/docs/proposal/integration_with_yardstick.rst +++ b/docs/proposal/integration_with_yardstick.rst @@ -11,13 +11,13 @@ Problem description =================== For each specified QPI [1]_, QTIP needs to select a suite of test cases and collect -required test results. Based on these results, Qtip calculates the score. +required test results. Based on these results, QTIP calculates the score. Proposed change =============== -Qtip has a flexible architecture [2]_ to support different mode: standalone and agent. +QTIP has a flexible architecture [2]_ to support different mode: standalone and agent. It is recommended to use **agent mode** to work with existing test runners. Yardstick will -act as a runner to generate test result and trigger Qtip agent on the completion of test. +act as a runner to generate test result and trigger QTIP agent on the completion of test. Work Items in Yardstick @@ -25,41 +25,41 @@ Work Items in Yardstick 1. Create a customized suite in Yardstick -Yardstick not only has many existing suites but also support customized suites. Qtip could -create a suite named **Qtip-PoC** in Yardstick repo to verify workflow of Qtip agent mode. +Yardstick not only has many existing suites but also support customized suites. QTIP could +create a suite named **QTIP-PoC** in Yardstick repo to verify workflow of QTIP agent mode. -2. Launch Qtip in Yardstick +2. Launch QTIP in Yardstick -Whether to launch Qtip will be determined by checking the existence of OS environment -variable *QTIP*. If it exists, Qtip will be launched by using Yardstick CLI +Whether to launch QTIP will be determined by checking the existence of OS environment +variable *QTIP*. If it exists, QTIP will be launched by using Yardstick CLI `yardstick plugin install` [3]_. -3. Yardstick interacts with Qtip +3. Yardstick interacts with QTIP See -`Yardstick-Qtip+integration <https://wiki.opnfv.org/display/yardstick/Yardstick-Qtip+integration>`_ +`Yardstick-QTIP+integration <https://wiki.opnfv.org/display/yardstick/Yardstick-QTIP+integration>`_ for details. -Work Items in Qtip +Work Items in QTIP ------------------ 1. Provide an API for Yardstick to post test result and environment info After completing test execution, Yardstick will post test result and enviroment info with JSON format via QTIP API. See -`Yardstick-Qtip+integration <https://wiki.opnfv.org/display/yardstick/Yardstick-Qtip+integration>`_ +`Yardstick-QTIP+integration <https://wiki.opnfv.org/display/yardstick/Yardstick-QTIP+integration>`_ for details. 2. Parse yardstick test result -When Qtip agent receive Yarstick test result and enviroment info, Qtip agent will extract -metrics which is definded in metric spec configuration file. Based on these metrics, Qtip +When QTIP agent receive Yarstick test result and enviroment info, QTIP agent will extract +metrics which is definded in metric spec configuration file. Based on these metrics, QTIP agent will caculate QPI. 3. Provide an API for querying QPI -Qtip will provide an API for querying QPI. See -`Yardstick-Qtip+integration <https://wiki.opnfv.org/display/yardstick/Yardstick-Qtip+integration>`_ +QTIP will provide an API for querying QPI. See +`Yardstick-QTIP+integration <https://wiki.opnfv.org/display/yardstick/Yardstick-QTIP+integration>`_ for details. Implementation diff --git a/docs/release/release-notes/brahmaputra.rst b/docs/release/release-notes/brahmaputra.rst index 92fafd80..2db7e109 100644 --- a/docs/release/release-notes/brahmaputra.rst +++ b/docs/release/release-notes/brahmaputra.rst @@ -1,3 +1,6 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 + *********** Brahmaputra *********** diff --git a/docs/release/release-notes/danube.rst b/docs/release/release-notes/danube.rst index b50fb909..59c6f6f7 100644 --- a/docs/release/release-notes/danube.rst +++ b/docs/release/release-notes/danube.rst @@ -1,22 +1,24 @@ .. This work is licensed under a Creative Commons Attribution 4.0 International License. .. http://creativecommons.org/licenses/by/4.0 +****** +Danube +****** -This document provides the release notes for <RELEASE> of <COMPONENT>. +This document provides the release notes for Danube of QTIP. .. contents:: :depth: 3 :local: - Version history ---------------- +=============== +--------------------+--------------------+--------------------+--------------------+ | **Date** | **Ver.** | **Author** | **Comment** | | | | | | +--------------------+--------------------+--------------------+--------------------+ -| 2017-03-14 | TODO(yujunz): tag | Yujun Zhang | First draft | +| 2017-03-30 | Danube 1.0 | Yujun Zhang | | | | | | | +--------------------+--------------------+--------------------+--------------------+ @@ -32,9 +34,9 @@ Summary QTIP Danube release introduces **QPI**, a.k.a. QTIP Performance Index, which is calculated from metrics collected in performance tests. -A PoC of compute qpi benchmark plan is provided as a sample use case. +A PoC of compute performance benchmark plan is provided as a sample use case. -Available benchmark plans can be listed, shown and executed from `qtip-cli`, the command line interpreter of QTIP. +Available benchmark plans can be listed, shown and executed from command line or over API. Release Data ============ @@ -43,13 +45,13 @@ Release Data | **Project** | QTIP | | | | +--------------------------------------+--------------------------------------+ -| **Repo/commit-ID** | qtip/TBD | +| **Repo/commit-ID** | qtip/danube.1.0 | | | | +--------------------------------------+--------------------------------------+ -| **Release designation** | Danube 1.0 | +| **Release designation** | Danube base release | | | | +--------------------------------------+--------------------------------------+ -| **Release date** | TODO(yujunz): fill date | +| **Release date** | 2017-03-31 | | | | +--------------------------------------+--------------------------------------+ | **Purpose of the delivery** | OPNFV quality assurance | @@ -57,115 +59,98 @@ Release Data +--------------------------------------+--------------------------------------+ Version change -^^^^^^^^^^^^^^ +-------------- Module version changes -~~~~~~~~~~~~~~~~~~~~~~ +^^^^^^^^^^^^^^^^^^^^^^ -N/A +The following Python packages are used in this release:: -Document version changes -~~~~~~~~~~~~~~~~~~~~~~~~ + ansible==2.1.2.0 + click==6.7 + connexion==1.1.5 + Jinja2==2.9.5 + numpy==1.12.1 + paramiko==2.1.2 + pbr==2.0.0 + prettytable==0.7.2 + six==1.10.0 + PyYAML==3.12 -N/A -Reason for version -^^^^^^^^^^^^^^^^^^ -Feature additions -~~~~~~~~~~~~~~~~~ +It is considered as a baseline for future releases. -**JIRA BACK-LOG:** +Reason for version +------------------ -** TODO(yujunz) pull data from JIRA ** +Features additions +^^^^^^^^^^^^^^^^^^ -+--------------------------------------+--------------------------------------+ -| **JIRA REFERENCE** | **SLOGAN** | -| | | -+--------------------------------------+--------------------------------------+ -| | | -+--------------------------------------+--------------------------------------+ -| | | -+--------------------------------------+--------------------------------------+ +* Compute QPI (QTIP Performance Index) specification and benchmarking plan +* Command line interface +* API server -Bug corrections -~~~~~~~~~~~~~~~ +Framework evolution +^^^^^^^^^^^^^^^^^^^ -**JIRA TICKETS:** +The following components are implemented and integrated -** TODO(yujunz) pull data from JIRA ** +* Native runner +* File loader +* Ansible driver +* Logfile collector +* Grep parser +* Console reporter -+--------------------------------------+--------------------------------------+ -| **JIRA REFERENCE** | **SLOGAN** | -| | | -+--------------------------------------+--------------------------------------+ -| | | -+--------------------------------------+--------------------------------------+ -| | | -+--------------------------------------+--------------------------------------+ +See JIRA for full `change log <https://jira.opnfv.org/jira/secure/ReleaseNote.jspa?projectId=10308&version=10555>`_ Deliverables ------------ -Software deliverables -^^^^^^^^^^^^^^^^^^^^^ +Software +^^^^^^^^ -** TODO(yujunz) docker image, pip package ** +- `QTIP Docker image <https://hub.docker.com/r/opnfv/qtip>`_ (tag: danube.1.0) -Documentation deliverables -^^^^^^^^^^^^^^^^^^^^^^^^^^ +Documentation +^^^^^^^^^^^^^ -** TODO(yujunz) links to qtip document publish ** +- `Installation & Configuration <http://docs.opnfv.org/en/stable-danube/qtip/docs/testing/user/configguide>`_ +- `User Guide <http://docs.opnfv.org/en/stable-danube/submodules/qtip/docs/testing/user/userguide>`_ +- `Developer Guide <http://docs.opnfv.org/en/stable-danube/submodules/qtip/docs/testing/developer/devguide>`_ Known Limitations, Issues and Workarounds ========================================= -System Limitations -^^^^^^^^^^^^^^^^^^ +Limitations +----------- -None +- The compute benchmark plan is hard coded in native runner +- Baseline for Compute QPI is not created yet, therefore scores are not available Known issues -^^^^^^^^^^^^ - -** TODO(yujunz) pull data from JIRA ** - -**JIRA TICKETS:** - -+--------------------------------------+--------------------------------------+ -| **JIRA REFERENCE** | **SLOGAN** | -| | | -+--------------------------------------+--------------------------------------+ -| | | -+--------------------------------------+--------------------------------------+ -| | | -+--------------------------------------+--------------------------------------+ - -Workarounds -^^^^^^^^^^^ +------------ -N/A +* QTIP-230 - logger warns about socket /dev/log when running in container Test Result =========== QTIP has undergone QA test runs with the following results: -+--------------------------------------+--------------------------------------+ -| **TEST-SUITES** | **Results:** | -| | | -+--------------------------------------+--------------------------------------+ -| qtip-verify-danube | 72/72 passed | -| | | -| | 73% lines of code covered | -+--------------------------------------+--------------------------------------+ -| qtip-daily-fuel-zte-pod3-danube | Last 7 build fails | -| | | -| | blocked by the failure of zte-pod3 | -+--------------------------------------+--------------------------------------+ - -References -========== - -For more information on the OPNFV Danube release, please see: - -http://opnfv.org/danube ++---------------------------------------------------+--------------------------------------+ +| **TEST-SUITES** | **Results:** | +| | | ++---------------------------------------------------+--------------------------------------+ +| qtip-verify-danube | 94/94 passed | +| | | ++---------------------------------------------------+--------------------------------------+ +| qtip-os-nosdn-kvm-ha-zte-pod3-daily-danube | Successful | +| | | ++---------------------------------------------------+--------------------------------------+ +| qtip-os-nosdn-nofeature-ha-zte-pod3-daily-danube | Successful | +| | | ++---------------------------------------------------+--------------------------------------+ +| qtip-os-odl_l2-nofeature-ha-zte-pod1-daily-danube | Successful | +| | | ++---------------------------------------------------+--------------------------------------+ diff --git a/docs/testing/developer/devguide/index.rst b/docs/testing/developer/devguide/index.rst index 1c993dc9..a4dd072c 100644 --- a/docs/testing/developer/devguide/index.rst +++ b/docs/testing/developer/devguide/index.rst @@ -3,9 +3,9 @@ .. (c) 2016 ZTE Corp. -*************** -Developer Guide -*************** +******************** +QTIP Developer Guide +******************** .. toctree:: :maxdepth: 2 diff --git a/docs/testing/user/configguide/configuration.rst b/docs/testing/user/configguide/configuration.rst index 8cc891f0..f048558e 100644 --- a/docs/testing/user/configguide/configuration.rst +++ b/docs/testing/user/configguide/configuration.rst @@ -41,7 +41,7 @@ Run and enter the docker instance :: envs="INSTALLER_TYPE={INSTALLER_TYPE} -e INSTALLER_IP={INSTALLER_IP}" - docker run --name qtip -id -e $envs opnfv/qtip + docker run -p [HOST_IP:]<HOST_PORT>:5000 --name qtip -id -e $envs opnfv/qtip docker exec -i -t qtip /bin/bash ``INSTALLER_TYPE`` should be one of OPNFV installer, e.g. apex, compass, daisy, fuel @@ -68,14 +68,14 @@ Environment configuration Hardware configuration ---------------------- -Qtip does not have specific hardware requriements, and it can runs over any +QTIP does not have specific hardware requriements, and it can runs over any OPNFV installer. Jumphost configuration ---------------------- -Installer Docker on Jumphost, which is used for running Qtip image. +Installer Docker on Jumphost, which is used for running QTIP image. You can refer to these links: diff --git a/docs/testing/user/userguide/api.rst b/docs/testing/user/userguide/api.rst index 7e1d7b1c..05b0e8f2 100644 --- a/docs/testing/user/userguide/api.rst +++ b/docs/testing/user/userguide/api.rst @@ -19,8 +19,7 @@ Running After installing QTIP. API server can be run using command ``qtip-api`` on the local machine. -All the resources and their corresponding operation details can be seen at ``/v1.0/ui``, -on hosting server(``0.0.0.0:5000`` for the local machine). +All the resources and their corresponding operation details can be seen at ``/v1.0/ui``. The whole API specification in json format can be seen at ``/v1.0/swagger.json``. |