summaryrefslogtreecommitdiffstats
path: root/docs
AgeCommit message (Collapse)AuthorFilesLines
2018-06-29Update git submodulesAlexandru Avadanii1-0/+0
* Update docs/submodules/fuel from branch 'stable/fraser' - sysinfo_print: Dump all iptables rules Change-Id: I0ce6d21e14efe6e5236759c8d8b3439f09e89675 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com> (cherry picked from commit fa26dabea271cee86c71b95f7d4650ef53eb2419)
2018-06-29Update git submodulesYang (Gabriel) Yu1-0/+0
* Update docs/submodules/bottlenecks from branch 'stable/fraser' - Modify ping test threshold Change the threshold to 5 VM pairs for basic common OPNFV verification requirements from Dovetail. Currently, offline test over apex pass: 1. ping subtest1: https://gist.github.com/gabrielyuyang/764b7ee636ac5502d5e561a348ae909b 2. ping subtest2: https://gist.github.com/gabrielyuyang/af17905a7e2379e870f492ea393c54c0 Working on testig over compass, trying to deploy a compass first. We could also see the result from compass on CI after this patch be merged. Results in Dovetial CI will also be updated then. Change-Id: If2cfe9988c046d733b30a23de3cd569ed06496e6 Signed-off-by: Yang (Gabriel) Yu <Gabriel.yuyang@huawei.com> (cherry picked from commit 62feef57918f110d423961a3989f77cf815058c6)
2018-06-29Update git submodulesXavier Simonart1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Fix NSB NfVi support for 25 and 40Gbps When setting interface_speed option in the test case, NSB/PROX was still considering 100% as 10 Gbps. With this fix, when interface_speed is set to for instance 25 Gbps then NSB/PROX will start generate at 25 Gbps. Yardstick logging info printed on the screen will show performance result as percentage of interface_speed (e.g. 100% will be 25 Gbps). This is done by sending the command "speed 250" to PROX (PROX cannot know the underlying interface speed in all cases e.g. in virtio, and hence considers 100% as 10Gbps). JIRA: YARDSTICK-1217 Change-Id: I4989161b04a7afa5e347935ee7ccef7dfe5a504d Signed-off-by: Xavier Simonart <xavier.simonart@intel.com> Signed-off-by: Emma Foley <emma.l.foley@intel.com> (cherry picked from commit 1d61af34eb7b35b912d124768ad26eb5f0cd03a8)
2018-06-29Update git submodulesEmma Foley1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "NSB Topology fix for Prox 4 port test case" into stable/fraser - NSB Topology fix for Prox 4 port test case The uplink and downlink interfaces for the 4 port test cases were inconsistent and fixed in this commit. This affects all the 4 port PROX test cases. Tested on: Heat L2fwd-4 and L3fwd-4 test case. JIRA: YARDSTICK-1185 Change-Id: Ia2ce7ed0dc395b812f84ede94e259b42dc833579 Signed-off-by:Abhijit Sinha <abhijit.sinha@intel.com> (cherry picked from commit 8ebd2d3fde473ffcd139090bd688882d4e5e0f44)
2018-06-29Update git submodulesEmma Foley1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "NSB NFVi BNG test fails to run - stops after one step" into stable/fraser - NSB NFVi BNG test fails to run - stops after one step JIRA: YARDSTICK-1244 When sending the start or stop command to PROX. We sould not send the same core. We should not send "start 1,1" instead we should send "start 1" Change-Id: Ie600dc3ed808fd00341e92f13bd52199e68dc51f Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com> (cherry picked from commit e219f22429ad2e6e6060c5c3440df72e014be273)
2018-06-29Update git submodulesEmma Foley1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge changes from topic 'prox-stable/fraser' into stable/fraser * changes: NSB NFVi PROX BNG losing many packets NSB NFVi PROX VPE losing many packets Decrease Sampling interval Addition of Configurable Sampling and Configurable Confirmation Retry - NSB NFVi PROX BNG losing many packets JIRA: YARDSTICK-1101 Problem was incorrect generator and changed the traffic profile to allow a tolerated loss of 5%. ARP packets are not managed (just passed thru the system) therefor the tolerated loss must be higehr than normal. Change-Id: I03bd62b397a66b50961e810d033c6894d0b3e9a6 Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com> (cherry picked from commit 48c9e48dcff498c8f51ec507d4107bc658b82d82) - NSB NFVi PROX VPE losing many packets JIRA: YARDSTICK-1105 Running a vPE test ends up with up to 25% drooped packets. This is due to tolerated loss being incorrectly configured, test duration was too short and test interval was too short. Note This is due to the fact that vPE use case have by default a tolerated loss of 100%, Now changed to 0.001, same as L2FWD Also: Grafan dashboard has been updated to show all SUT CPUS Utilization in 1 panel. And LINE rate MIN, MAX & TEST Rate have been added Change-Id: I7adae2199b3f656fe460705b6aeb3aa69c767d50 Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com> (cherry picked from commit 39b3d9ae8ff19a0d64bff0e874f05b6dbcc30b01) - Decrease Sampling interval JIRA: YARDSTICK-1219 Currently NSB for NFVI using PROX returns sampling information every 13 seconds. This is too slow. It is required to return sampling information form Generator AND VNF at least every 1 second. This change is depandant on JIRA: YARDSTICK-1212 and YARDSTICK-1220 Change-Id: Ica7ab795a2919d191d8cd846d028e15739e33fb7 Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com> (cherry picked from commit f8b45aca386ed5852d9568c531ba4595c68cc0e2) - Addition of Configurable Sampling and Configurable Confirmation Retry JIRA: YARDSTICK-1221 In order to increase accuracy of result the following are done :- - Improve Measurement Accuracy (YARDSTICK-1212) - Improve Sampling Interval (YARDSTICK-1219) - Allow 4 PROX ports to be read simultaneously (YARDSTICK-1220) This change does the following :- - Stores LINE Rate statistics of Sample - Requires a confirmation retry before deciding to increase or decrease this is configurable. - Allows the user to disable Sampling or specify a sample interval - Added Code Coverage of ProxDurationRunner based on YARDSTICK-1199 Change-Id: I27242ac1849c9a2712866385b5fbc05977c71516 Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com> (cherry picked from commit 2e447af9a5a54355aa20028813660d07d1bd2e18)
2018-06-29Update git submodulesEmma Foley1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "Convert SLA asserts to raises" into stable/fraser - Convert SLA asserts to raises This commit converts Python assertions to a custom exception in all places where SLA validation is checked with an assertion. This commit also fixes all emerged pylint errors. JIRA: YARDSTICK-966 Change-Id: If771ed03b2cbc0a43a57fcfb9293f18740b3ff80 Signed-off-by: Miikka Koistinen <miikka.koistinen@nokia.com> (cherry picked from 39f80e9b06395ae1515cfcf08508504ad4dd978a)
2018-06-29Update git submodulesdimitris.tsiolakis1-0/+0
* Update docs/submodules/sdnvpn from branch 'stable/fraser' - Clean up stale routers and gateway routers. During snaps_smoke test all floating IPs are allocated by routers as external IP's, as a result there are no more floating IPs left. This patch clean up stale routers and free the assigned IPs. JIRA: SNAPS-318 Change-Id: Ifbf01ce38db63315e692dca9ffa5d993dbfa4337 Signed-off-by: dimitris.tsiolakis <dmts@intracom-telecom.com> (cherry picked from commit 71737f23f718791a554edf374ee0c28bb77c9773)
2018-06-29Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'stable/fraser' - Updating release notes for OPNFV Fraser 6.2 Change-Id: I9a9da79cb4ccb245ddb38b50b561da51a40a359d Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2018-06-29Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'stable/fraser' - Adding support for Ubuntu 17.10... Change-Id: I9a9da79cb4ccb245ccb38b50b561da51a40a359d Signed-off-by: Deepak S <deepak.s@linux.intel.com> - Adding centos.json to be used with packer to generate a VM with PROX Based on a CentOS cloud image downloadable from the web, you can now use packer to create an image that has DPDK and PROX installed in the proper directories. The VM is also tuned for guest VNFs. A service is also created to deal with the proper isolated_cpu settings for tuned. The service will also make sure uio and igb_uio are loaded. The prox_user_data.sh is not needed any more and hence deleted. ctrl-c of runrapid.py will now also stop prox in all the VMs so a new test can be started. Change-Id: I16cc59878e2d4912757f42e05f98d51dff5feb89 Signed-off-by: Luc Provoost <luc.provoost@intel.com> - TempFix: vCGNAPT/vACL ipv4 perf issue Change-Id: I924fcac7a65c0d221d5d422f419deb9c0f864172 Signed-off-by: Deepak S <deepak.s@linux.intel.com> - Temp Fix for vFW perf issue Change-Id: I324fcac7a65c0d221d5d422f419deb9c0f864172 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2018-06-29Update git submodulesManuel Buil1-0/+0
* Update docs/submodules/sfc from branch 'stable/fraser' - Update release notes for Fraser 6.2 Depends-On: https://gerrit.opnfv.org/gerrit/#/c/59177/ Change-Id: I0d56aa4d5f494a25db92e61415a24b4257c71a04 Signed-off-by: Manuel Buil <mbuil@suse.com> (cherry picked from commit a52c05a07b2a01b8c911537d29c995fb42f66972)
2018-06-28Update git submodulesTrevor Bramwell1-0/+0
* Update docs/submodules/releng from branch 'master' - Merge "Fix unset RC_FILE_PATH in Scripts" - Fix unset RC_FILE_PATH in Scripts Even though RC_FILE_PATH is defined in Jenkins as passed in as a parameter, bash still sees it as unset. Removing the 'nounset' option from these scripts should allow the check to success (RC_FILE_PATH set to blank). Change-Id: Ibcfdcf0d2a12c8119d2fe3ec3b354be782338bd5 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-06-28Update git submodulesTrevor Bramwell1-0/+0
* Update docs/submodules/releng from branch 'master' - Fix the output of repo list to be 'repo, tag, ref' This was changed in a previous commit and causes calls to 'git branch' during the verification job to fail. Change-Id: I71c248abecf030658371b810d403e1f460933946 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-06-28Update git submodulesGerard Damm1-0/+0
* Update docs/submodules/auto from branch 'stable/fraser' - cosmetic change to R6.2 Release Notes JIRA: AUTO-41 forgot blank line before list of notable activities (line 277); opnfvdocs rendition did not look good; Change-Id: Ic5073e5021164c27fdcccab4b11fd8f375bfeeaf Signed-off-by: Gerard Damm <gerard.damm@wipro.com> (cherry picked from commit f2b7433b3f20299d935c42e978d56703b11eb17b)
2018-06-28Update git submodulesAlexandru Avadanii1-0/+0
* Update docs/submodules/armband from branch 'stable/fraser' - u/fuel: Bump & rebase for MaaS region fabric Change-Id: Iddd9591507b3985625cce31c3740deabd3eeded2 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-06-28Update git submodulesTrevor Bramwell1-0/+0
* Update docs/submodules/releng from branch 'master' - Fix Git URL Parameter for Release Merge Job This was incorrectly set to GIT_BASE, which includes the Project name, and should be set to GIT_URL, which does not. GIT_URL is used instead as each release file can contain multiple repos. Change-Id: I82b5e80f20f8999745cb5008c8057c81c4993574 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-06-28Update git submodulesGerard Damm1-0/+0
* Update docs/submodules/auto from branch 'stable/fraser' - Merge "R6.2 updates for Auto Release Notes and Configuration Guide" into stable/fraser - R6.2 updates for Auto Release Notes and Configuration Guide JIRA: AUTO-41 Several updates in Release Notes and Configuration Guide, to capture changes and progress since R6.1. Included tickets 35,37,40, since they can still be done for 6.2. Patch 2: made updates based on comments (note: need to close by 6/28) Patch 3: minor edits, will merge today Patch 4: removed Jira tickets 35, 37, 40 from Auto release 6.2 Change-Id: I7547a9ea9b807c28513ce4e995d53a9f32223eb1 Signed-off-by: Gerard Damm <gerard.damm@wipro.com> (cherry picked from commit d2a98b6fba905cd3de79c0b1c35021423b9dda9f)
2018-06-28Update git submodulesGerard Damm1-0/+0
* Update docs/submodules/auto from branch 'stable/fraser' - Merge "ci: Support for pylint and yamllint" into stable/fraser - ci: Support for pylint and yamllint A support for pylint and yamllint checks was introduced. Checks can be executed manually by invocation of ./check script (see script usage for more details). Automatic lint checks were integrated info VERIFY and MERGE job bodies. TODO: Improve pylint ratings of python code. Some issues can be fixed in python files or by relaxing pylint settings. However dependencies on ONAP includes can't be easily fixed. Thus pylint checks should be set as non-blocking at the beginning. Change-Id: I82a6a266b8003ae5d70f4f2a88ecc96817b97ac0 Signed-off-by: Martin Klozik <martin.klozik@tieto.com> (cherry picked from commit 6c1bcb7f02e4159bef21154341a9268f38bce438)
2018-06-28Update git submodulesAric Gardner1-0/+0
* Update docs/submodules/auto from branch 'stable/fraser' - Fix formatting in INFO.yaml file Soon we will have a valiadator that will not allow errors like this to be merged. Change-Id: I6d65f30376afe0e2b6da768f488888aed15bdb22 Signed-off-by: Aric Gardner <agardner@linuxfoundation.org> (cherry picked from commit b2b0c6cf161af535a185cdc8779ab9ddbeaeb335)
2018-06-28Update git submodulesGerard Damm1-0/+0
* Update docs/submodules/auto from branch 'stable/fraser' - Merge "docs: Fix long lines" into stable/fraser - docs: Fix long lines OPNFVDOCS scripts set max line length to 240 chars. This patch shortens long lines to avoid rst validation warnings during Auto docs generation. Change-Id: I124e3ea3aa04bc7fc8c2f5cf25ce9c75fdcef330 Signed-off-by: Martin Klozik <martin.klozik@tieto.com> (cherry picked from commit bf21f3086791419abd713757ec85d0b9a77312d5)
2018-06-28Update git submodulesGerard Damm1-0/+0
* Update docs/submodules/auto from branch 'stable/fraser' - Merge "update of config script using new release of OpenStack SDK" into stable/fraser - update of config script using new release of OpenStack SDK JIRA: AUTO-38 - Issues in OpenStack SDK 0.13 were fixed in new release 0.14 - revisited the script, made some changes (delete interfaces before deleting router) - Script now fully works: creates all objects, and can be used also for deleting (in a clean-up job for example) - resilient to re-runs: can attempt to re-create, won't crash if objects already exist (existence tests work, thanks to SDK 0.14 fix). Likewise, can attempt to re-delete (no crash). - next steps will be: * update created objects based on ONAP-B requirements (current: still from Amsterdam; should be quite similar) * script to ensure Python3 and SDK are installed, and to ensure files are there (clouds.yaml, .img) * chain in CI pipeline: Fuel/MCP install, and this script Patch 2: made changes to address the comments - fixed the summary (works in any execution case), tested on hpe12 - researched the URL support (use image proxy), but did not try yet (need to merge this for 6.2) Change-Id: Ibf647e33428c98a6fec17eda0a41e9ee11cc8085 Signed-off-by: Gerard Damm <gerard.damm@wipro.com> (cherry picked from commit c8f22d584e6bb23634d12e40d66400a718d5cbc7)
2018-06-28Update git submodulesGerard Damm1-0/+0
* Update docs/submodules/auto from branch 'stable/fraser' - Merge "checked code logic for UC2-vim001 recovery time measurement" into stable/fraser - checked code logic for UC2-vim001 recovery time measurement JIRA: AUTO-38 Leveraging new OpenStack SDK release 0.14, tested existing code for UC2/vif-001 (simulated VM failure), to verify that generic code for recovery time measurement works. Entered test code in placeholders for this test case: challenge start (suspend a VM), challenge stop (resume, although this was done outside (from Horizon), to simulate an ONAP-controlled recovery), test code (periodic status check, stop when VM is active again). Time was measured correctly, output files (.csv) were created successfully. This will allow to close Jira ticket 38. Next steps will be to interface with ONAP, to obtain VNF info (especially the ID of the corresponding OpenStack VMs), and perform the same measurement, which this time will be an actual recovery time, provided DCAE data collection, Policy and CLAMP have the proper configuration. Change-Id: I7320f7570c119d2b59d1ed6ca787ba975ad04a44 Signed-off-by: Gerard Damm <gerard.damm@wipro.com> (cherry picked from commit dffc2bee5650b10831f3792b162b6ea73a4624ae)
2018-06-28Update git submodulesGerard Damm1-0/+0
* Update docs/submodules/auto from branch 'stable/fraser' - Merge "ci: CI helper script" into stable/fraser - ci: CI helper script Skeleton of CI helper script. This script implements the body of AUTO CI jobs. It is executed from AUTO job definitions used by the OPNFV Jenkins. Change-Id: I17984293b795a0fe90bff8f9e06a8a82176c1612 Signed-off-by: Martin Klozik <martin.klozik@tieto.com> (cherry picked from commit bea663873a193b0b0d8deedd8ea579339598a5be)
2018-06-28Update git submodulesTrevor Bramwell1-0/+0
* Update docs/submodules/releng from branch 'master' - Fix Typo in repos release script As the scripts are ran under Python 3, parenthesis are required around print statements. Adding these doesn't seem to cause in error in Python 2. Change-Id: Ic0ce623ded5f3e3f27c8117e2067566afc8d8c0b Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-06-28Update git submodulesGerard Damm1-0/+0
* Update docs/submodules/auto from branch 'stable/fraser' - Merge "adding Mohan, removing Madhukesh" into stable/fraser - adding Mohan, removing Madhukesh In a phase of refreshing list of Auto committers. First batch: add Mohan, remove Madhukesh. Mohan: which email to use (mvista or gmail); and need your LF ID. Next batch: add Martin, Richard, Cristina, Paul, Joe (voting in progress), and review all list Does the "INFO" file need to be deleted (since "INFO.yaml" is the reference) ? patch 2: - updated Mohan's LFID - added entries for Joe, Cristina, Paul, Martin, Richard - still need LFIDs from Paul, Richard - seems INFO can be deleted indeed; will do during final patch (delta: about 6 names in INFO not in INFO.yaml) patch 3 (June 14th): - updated LFIDs for Paul, Richard - updated INFO, but not deleted yet; grouped names not in INFO.yaml; - INFO.yaml ready to be merged, pending TSC approval process Change-Id: Ie34283faebbab99afbed731d7ac92309518e3b03 Signed-off-by: Gerard Damm <gerard.damm@wipro.com> (cherry picked from commit 07a61a49978c842ba6b3e6a31a6a0f127084c639)
2018-06-28Update git submodulesMartin Klozik1-0/+0
* Update docs/submodules/auto from branch 'stable/fraser' - gitignore: Ignore docs generation dirs Update .gitignore file to ignore OPNFVDOCS scripts and directories used for docs generation. Change-Id: I8a8476677b4f3d488d8b09b4eb17d98cad8e77bd Signed-off-by: Martin Klozik <martin.klozik@tieto.com> (cherry picked from commit cc722289a74012c2f76a683f7fb6ca1904c85e93)
2018-06-28Update git submodulesTrevor Bramwell1-0/+0
* Update docs/submodules/releng from branch 'master' - Merge "Doctor Fraser opnfv-6.2.0" - Doctor Fraser opnfv-6.2.0 Change-Id: I9f61914d3c07ca52e9b062110a2d0036090b3626 Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
2018-06-28Update git submodulesDimitrios Markou1-0/+0
* Update docs/submodules/releng from branch 'master' - Disable SFC verify job in fraser branch We would like to disable the SFC verify job for fraser branch because jenkins give us -1 on new patches on stable fraser branch because of the lack of tox on that branch. We are not going to submit any new patches on the SFC fraser branch from now on except from one [0]. So we can disable the fraser job as an easy fix to the -1 jenkins-ci problem in gerrit. [0]: https://gerrit.opnfv.org/gerrit/#/c/59175/ Change-Id: Iab2cb1eea6ac14f262ca25bc3cc61e15556f21e9 Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com>
2018-06-28Update git submodulesMark Beierl1-0/+0
* Update docs/submodules/storperf from branch 'stable/fraser' - Merge "Fixes daily run" into stable/fraser - Fixes daily run Change-Id: I8f17efe0d0866a3dc6ecbbabe07985b93ac445e6 Signed-off-by: mbeierl <mark.beierl@dell.com> (cherry picked from commit 3c14f6cf6344c4a83aa7c4f586db39bb69a5d93e)
2018-06-28Update git submodulesmbeierl1-0/+0
* Update docs/submodules/storperf from branch 'stable/fraser' - Use MultiThreaded SNAPS Take advantage of multiple threads in SNAPS to get info on the stack more quickly. Change-Id: Ifbfaec4fb6f1a4a322c327176c82200b5f69d874 JIRA: STORPERF-245 Signed-off-by: mbeierl <mark.beierl@dell.com> (cherry picked from commit fa0e1935f3f0b6da79666963e5937c8402100287)
2018-06-28Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "Extended Context class with get_physical_nodes functionality" into stable/fraser - Extended Context class with get_physical_nodes functionality JIRA: YARDSTICK-1255 Change-Id: I446d715dc6cf716a4fcbc1b809c1b1d6303071e0 Signed-off-by: Chornyi, TarasX <tarasx.chornyi@intel.com> (cherry picked from commit 595212edf5ccd71af1bf7ef57a8d260fb1ec0c9e)
2018-06-28Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "Add "os_cloud_config" as a new context flag parameter" into stable/fraser - Add "os_cloud_config" as a new context flag parameter This new parameter will contain the OpenStack cloud specific configuration used by Shade client. This new flag is used only in Heat context. By default, this new parameter (dict) will contain this content: 'os_cloud_config': {'verify': False} This field will be used by HeatStack [1] to create a Shade cloud. Shade retrieves, if not defined, the OpenStack configuration from "os_client_config". This configuration is used to generate the cloud configuration, which is the description of the OpenStackCloud returned. The default parameter defined, "verify", refers to the related bug. By default, in case of using SSL certificate it will not be verified. [1] https://github.com/opnfv/yardstick/blob/b338d3091bb0beb89d4ad9f7c144f43a31a19a74/yardstick/orchestrator/heat.py#L47 JIRA: YARDSTICK-1139 Change-Id: I875a7018401b84e51dab775b8194174645d27e06 Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com> (cherry picked from commit 9ae331e1aa1081c3e821512d1940846dfb4063ec)
2018-06-28Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "Stop running tests from tests/unit" into stable/fraser - Stop running tests from tests/unit Since all tests have been moved into yardstick/tests, temperary code to run tests in both tests and yardstick/tests should be removed. JIRA: YARDSTICK-837 Change-Id: I3bf3c9ece9bc8457d992e53ee8cc5cadb1dec8f0 Signed-off-by: Emma Foley <emma.l.foley@intel.com> (cherry-picked from commit 64add9a435e9455b3bff6971d2717857cdce8193)
2018-06-28Update git submodulesPeriyasamy Palanisamy1-0/+0
* Update docs/submodules/sdnvpn from branch 'stable/fraser' - update sdnvpn release notes for fraser 6.2 Change-Id: I752fba0ba0d434ae1bc37b975479361f9d53e3b3 Signed-off-by: Periyasamy Palanisamy <periyasamy.palanisamy@ericsson.com> (cherry picked from commit b5e7619baeecec2494994caba86df275fa197c99)
2018-06-28Update git submodulesOnong Tayeng1-0/+0
* Update docs/submodules/fds from branch 'stable/fraser' - Update release notes for Fraser 6.2 Change-Id: I5905ac0e35dc025f665ce33263b92242097ee5f1 Signed-off-by: Onong Tayeng <otayeng@cisco.com> (cherry picked from commit 406d71e14b99b92db10bf6dc7137970baf6324cf)
2018-06-28Update git submodulesCédric Ollivier1-0/+0
* Update docs/submodules/functest from branch 'stable/fraser' - Modify config_patch.yaml according to the new snaps config It allows verifying ovs scenarios via snaps. JIRA: FUNCTEST-984 Change-Id: I0fedadc0b9e265c424ae3221469b8d28b9a68afa Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com> (cherry picked from commit 06caf7c89f3a49185e9b9c1cfe40720b25ee2bc2) - Config flavor metadata via functest - docs update Related to the merged patch : "SNAPS via functest with flavor metadata configurable" Functest documents are updated accordingly. Change-Id: I874f041935f64b7240a5ec5de6e9c89b0f4a09fd Signed-off-by: Panagiotis Karalis <pkaralis@intracom-telecom.com> (cherry picked from commit a62dc183e6a916095b31f22a294d8f81306bf23b) - SNAPS via functest with flavor metadata configurable The required data for the SNAPS flavors are sent through the config_functest yaml file in order for the SNAPS scenarios to be configured accordingly. If the config_functest yaml file includes empty flavor_extra_specs or there is not included this parameter, the SNAPS scenarios will be executed using the hardcoded value. Change-Id: I4ef46d1fe93497d658414170a72c4520d8f37808 Signed-off-by: Panagiotis Karalis <pkaralis@intracom-telecom.com> (cherry picked from commit 5a94beb62293151ef6f4e94ed500579de1f3673e)
2018-06-28Update git submodulesEmma Foley1-0/+0
* Update docs/submodules/samplevnf from branch 'stable/fraser' - Get multiple port stats simultaneously JIRA: YARDSTICK-1220 Implemented new "multi port stats <port list>" command, which returns a semi-colon-separated list of comma-separated values: - port id - total (at last_tsc) for rx_pkts, tx_pkts, no_mbufs, ierrors + imissed - last_tsc Change-Id: I8a8da79cb4ccb245ccb38b50b561da51a40a359d Signed-off-by: Patrice Buriez <patrice.buriez@intel.com> (cherry picked from commit a9d9979b1f5b7435552ae884da69220a42b81f81) Signed-off-by: Emma Foley <emma.l.foley@intel.com>
2018-06-28Update git submodulesJing Lu1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "Bugfix: HA kill process recovery has a conflict" into stable/fraser - Bugfix: HA kill process recovery has a conflict It happens in Nokia SUT when running in the Plugfest. The problem happens when the start_process start to recover the killed process (like nova-api), but the self-cured mechanism already recovered. And somehow it lead to a conflict and has problems. So the recover of the HA attack-recover should be improved to only recover it when it needs to. JIRA: YARDSTICK-1222 Change-Id: I1acb5a7d59d6fe4e0de0b0c5942fa89e051dd1ff Signed-off-by: rexlee8776 <limingjiang@huawei.com> (cherry picked from commit 736f3fa5d52345d6fe5174b83de043f779fa0600)
2018-06-28Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "Replace glance delete image with shade client." into stable/fraser - Replace glance delete image with shade client. Remove get_image_id function. Function delete_image now uses shade client. JIRA: YARDSTICK-892 Change-Id: I6e8510dfa49aa14786ed7ac3382b85c4e699fb9e Signed-off-by: Shobhi Jain <shobhi.jain@intel.com> (cherry picked from commit d6c1b8b7bfd257efd5fe2df30dd450bdb2c57c7d)
2018-06-28Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "Replace glance create image with shade client." into stable/fraser - Replace glance create image with shade client. Function create_image now uses shade client. JIRA: YARDSTICK-892 Change-Id: Ia41d9ce702a1f24031080f8a365c1b2bd9ac9faa Signed-off-by: Shobhi Jain <shobhi.jain@intel.com> (cherry picked from commit c31edc5ab9013d93ffd32ed72adb14740e43b24a)
2018-06-28Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "Replace cinder detach volume with shade client." into stable/fraser - Replace cinder detach volume with shade client. Function detach volume now uses shade client. JIRA: YARDSTICK-891 Change-Id: Ie437ccf1172cb82dc869963f0d62e31a5ab23ebb Signed-off-by: Shobhi Jain <shobhi.jain@intel.com> (cherry picked from commit f6cca46f6b1aa6134a0e634a3a9e524cdbbfa729)
2018-06-28Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "Replace cinder delete volume with shade client." into stable/fraser - Replace cinder delete volume with shade client. Function delete volume now uses shade client. JIRA: YARDSTICK-891 Change-Id: I016e1d3bf5972879cad176b56c7282e35413945e Signed-off-by: Shobhi Jain <shobhi.jain@intel.com> (cherry picked from commit 4c672aa7012a530806a2f8ff2d45a8badb7f7b21)
2018-06-28Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "Replace cinder create volume with shade client." into stable/fraser - Replace cinder create volume with shade client. Adds get_volume function. Function create volume now uses shade client. JIRA: YARDSTICK-891 Change-Id: I0b2fae5f2cf52eaf2e4a0062c858d49bc4ce9ccd Signed-off-by: Shobhi Jain <shobhi.jain@intel.com> (cherry picked from commit 2d33d0f289f3dd3864fe57289e953b876f362c06)
2018-06-28Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "Replace cinder get_volume_id with shade client." into stable/fraser - Replace cinder get_volume_id with shade client. Function get_volume_id now uses shade client. JIRA: YARDSTICK-891 Change-Id: I45ae40982a64f677dbbdeb6c9510a0ec9ac973f1 Signed-off-by: Shobhi Jain <shobhi.jain@intel.com> (cherry picked from commit be197a6197e803b6334f2ccf72f561245ef7aac7)
2018-06-28Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "Replace nova get flavor with shade client." into stable/fraser - Replace nova get flavor with shade client. Rename get_flavor_by_name with get_flavor. Function get_flavor now uses shade client. JIRA: YARDSTICK-1088 Change-Id: Ic82127e475baf39643be0a254b177f3058b85748 Signed-off-by: Shobhi Jain <shobhi.jain@intel.com> (cherry picked from commit 35bbd618b1e69a5b5edbd64a333720bfa5a92400)
2018-06-28Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "Replace nova get server with shade client." into stable/fraser - Replace nova get server with shade client. Rename get_server_by_name with get_server. Function get_server now uses shade client. JIRA: YARDSTICK-1088 Change-Id: I69c59145cefdb565f3ece27baaaf932905e1b757 Signed-off-by: Shobhi Jain <shobhi.jain@intel.com> (cherry picked from commit d75a91ebf2937e5cfe5cf2aa5a90db9121f73967)
2018-06-28Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "Replace nova attach volume to server with shade client." into stable/fraser - Replace nova attach volume to server with shade client. Function attach_volume_to_server now uses shade client instead of nova client. JIRA: YARDSTICK-1088 Change-Id: Id00df672c2c195b5c338cbbc30ddf2742a4e4d29 Signed-off-by: Shobhi Jain <shobhi.jain@intel.com> (cherry picked from commit 8fd82cd8d0146d8cebbc32ed7cbb6fb9d1861297)
2018-06-28Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "Replace nova delete keypair with shade client." into stable/fraser - Replace nova delete keypair with shade client. Function delete_keypair now uses shade client. JIRA: YARDSTICK-1088 Change-Id: I46b895748c5c44b0bf7d5b035395676ebff48d7f Signed-off-by: Shobhi Jain <shobhi.jain@intel.com> (cherry pick from commit aded0fdb30caf035e0eb94c1216f436ba597c2c7)
2018-06-28Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "Replace nova client create keypair with shade." into stable/fraser - Replace nova client create keypair with shade. Function create_keypair now uses shade client instead of nova client. JIRA: YARDSTICK-1088 Change-Id: I060580504d6969c5ba859ed4494082feb998d37d Signed-off-by: Shobhi Jain <shobhi.jain@intel.com> (cherry pick from commit c1ab98526209a761a0565afa7ccd552ba9ac7ade)
2018-06-28Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "Remove unused nova client functions." into stable/fraser - Remove unused nova client functions. Following funtions are not required by shade client also not been used in any of the scenario files: *create_aggregate *create_aggregate_with_host *create_instance *add_host_to_aggregate *create_aggregate_with_host *get_availability_zones *get_availability_zone_names *remove_hosts_from_aggregate *remove_host_from_aggregate *delete_aggregate *get_image_by_name *check_status JIRA: YARDSTICK-1088 Change-Id: I7ba0fbce6aa3e636aa55581a993c1ec1b48fbead Signed-off-by: Shobhi Jain <shobhi.jain@intel.com> (cherry picked from commit 2ca15a8c87e171cbd82b1e748dfc60903662b73b)