Age | Commit message (Collapse) | Author | Files | Lines |
|
* Update docs/submodules/fuel from branch 'master'
- [patch] Drop obsolete OVS port with route support
Since we switched all scenarios to using only global gateway settings
instead of per-interface routes, drop the obsolete patch for OVS
ports with explicit routes.
Change-Id: Ibd28849437b598add9847c991e0276b4d0fc505e
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Update Functest testcase list per tier"
- Update Functest testcase list per tier
Change-Id: I905527d509597218927908be7752ca16b6ea2cc5
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
* Update docs/submodules/storperf from branch 'master'
- Merge "Support Custom Workloads"
- Support Custom Workloads
Refactors interaction with test_executor to clean up the
tight coupling.
Adds ability to specify custom workloads.
Change-Id: Idbadcec1f42714e96c5f96d1e45c05982a531503
JIRA: STORPERF-246
Co-Authored-By: Ameed.Ashour.Ext@Nokia.com
Signed-off-by: mbeierl <mark.beierl@dell.com>
|
|
* Update docs/submodules/storperf from branch 'master'
- Merge "Set self.stack_id = None after delete stack"
- Set self.stack_id = None after delete stack
Change-Id: I09ad953776804f17f5eedf296955ced51c5ed3a4
JIRA: STORPERF-251
Signed-off-by: Ameed Ashour <Ameed.Ashour.ext@nokia.com>
|
|
* Update docs/submodules/functest from branch 'master'
- Merge "Define one logger per key module"
- Define one logger per key module
Snaps is printing lots of error messages which makes user confused.
It will decrease the size of functest.log.
Change-Id: I2c7d8ec968350563fbfbd62dcc2fc39b13b39a78
Signed-off-by: Cédric Ollivier <ollivier.cedric@gmail.com>
|
|
* Update docs/submodules/functest from branch 'master'
- Force region to RegionOne if OS_REGION_NAME is unset
tempest still selects the first one if unset [1].
JIRA: FUNCTEST-990
[1] https://docs.openstack.org/tempest/latest/sampleconf.html
Change-Id: I238d47173c2c4aa1db694028e4d44b80b0e280f1
Signed-off-by: Cédric Ollivier <ollivier.cedric@gmail.com>
|
|
* Update docs/submodules/barometer from branch 'master'
- Merge "docs: update userguide with new option for intel_pmu plugin"
- docs: update userguide with new option for intel_pmu plugin
Update the userguide for intel_pmu with new "Cores"
option available in plugin configuration.
Added sample config with default configuration.
Change-Id: Ibe4d451131dc2c9ae0282f018c7e23596f4bf2c1
Signed-off-by: Kamil Wiatrowski <kamilx.wiatrowski@intel.com>
|
|
* Update docs/submodules/barometer from branch 'master'
- Merge "Fix docs"
- Fix docs
Remove --net=host as it should not be used when
port mapping with the -p option
Change-Id: I7d6d73fe176362fc74df99200a6d68d2a3ec0994
Signed-off-by: John O Loughlin <john.oloughlin@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Add "tolerations" parameter in Kubernetes context
This new parameter, "torelations", is applied to pods and allow (but not
require) the pods to schedule onto node with matching tains [1].
Example of "tolerations" definition in a Kubernetes pod:
spec:
containers: [...]
tolerations:
- key: <key defined in the taint>
value: <key value to match with the taint>
effect: <effect in case of match>
operator: <matching operator>
- key: ...
Example of "tolerations" definition in a Yardstick test case:
context:
type: Kubernetes
servers:
host:
containers: [...]
tolerations:
- key: ...
value: ...
effect: ...
operator: ...
NOTE: if any toleration is defined, a default one will be applied in
order to allow any replication controller to create the pods in any
Kubernetes node. This default toleration is defined as:
spec:
tolerations:
- operator: "Exists"
[1] https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
JIRA: YARDSTICK-1254
Change-Id: I32fb9c7086b4218c323218738057f634eb6ffff4
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Add "ports" parameters in Kubernetes context
This new parameter, "ports", will allow the user to
automatically to add port variables in a pod definition:
context:
type: Kubernetes
servers:
host:
image: ...
commands: ...
ports:
- containerPort: <port value> # Mandatory
hostIP: <host IP> # Optional
hostPort: <host port> # Optional
name: <port name> # Optional
protocol: <protocol name> # Optional
The port type and the definition must be one of the supported ones
in Kubernetes [1].
Container port definition, V1 API, Kubernetes Python library v6.0.0 [2]
[1] https://kubernetes.io/docs/concepts/services-networking/connect-applications-service/
[2] https://github.com/kubernetes-client/python/blob/6.0.0/kubernetes/client/models/v1_container_port.py
JIRA: YARDSTICK-1183
Change-Id: I3673dbeec8d380cb2f8b1dacf6c25c7cdbc37e28
Signed-off-by: John O Loughlin <john.oloughlin@intel.com>
|
|
* Update docs/submodules/functest from branch 'master'
- Merge "1) Cleanup floating IPs that are assigned through Juju Deployment. 2) Add SCTP rule explicitly to the retrieved Security Group."
- 1) Cleanup floating IPs that are assigned through Juju Deployment.
2) Add SCTP rule explicitly to the retrieved Security Group.
Change-Id: I38e5b1267dbcdcf8e5aadb3c06dd784044e774d4
Signed-off-by: soumaya <soumaya.nayek@rebaca.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Add "restartPolicy" parameter in Kubernetes policy
This new parameter, "restartPolicy", will allow define the restart policy per pod.
Example of yaml definition in Kubernetes:
apiVersion: v1
kind: Pod
metadata:
name: frontend
spec:
containers:
- name: db
...
restartPolicy: Always # Possible values: "Always", "OnFailure" and "Never"
Example of definition in a Yardstick context:
context:
type: Kubernetes
servers:
host:
containers:
- name: ...
restartPolicy: Always # Default value: "Always"
Restart policy [1].
[1] https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy
JIRA: YARDSTICK-1175
Change-Id: Id4317b909f98422e89d6d4553e8cfb0e1f593355
Signed-off-by: John O Loughlin <john.oloughlin@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Add "resources" parameter in Kubernetes context"
- Add "resources" parameter in Kubernetes context
This new parameter, "resources", will allow the user to automatically
add resources in a pod definition per container.
Example of yaml definition in Kubernetes:
apiVersion: v1
kind: Pod
metadata:
name: frontend
spec:
containers:
- name: db
image: mysql
resources:
requests:
memory: "64Mi"
cpu: "250m"
limits:
memory: "128Mi"
cpu: "500m"
Example of definition in a Yardstick context:
context:
type: Kubernetes
servers:
host:
resources: # There are two possible keys in this dict:
# "requests" and "limits".
limits: <dictionary>
requests: <dictionary>
Resources in containers [1].
[1] https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
JIRA:YARDSTICK-1171
Change-Id: I163d72d9d3e88b538fca73eb4dbf38613aa23ff4
Signed-off-by: John O Loughlin <john.oloughlin@intel.com>
|
|
* Update docs/submodules/dovetail from branch 'master'
- New test specs for ha database/controller_restart
New test specifications have been created for dovetail project.
Test descriptions are related to test cases:
- dovetail.ha.database
- dovetail.ha.controller_restart
JIRA: DOVETAIL-680
JIRA: DOVETAIL-681
Change-Id: I632cb69f9166a46e76f38a467f078fe5f31b63b3
Signed-off-by: Panagiotis Karalis <pkaralis@intracom-telecom.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Add send socket commands function"
- Add send socket commands function
Pktgen provides a TCP socket connection to allow the user to control
it from a remote console or program [1].
This new method will provide Yardstick the ability to send string
commands to a port in a remote host.
[1] http://pktgen-dpdk.readthedocs.io/en/latest/socket.html
JIRA: YARDSTICK-1186
Change-Id: I9d64ccad662fa3599de65654c5dab02833fcc91d
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
* Update docs/submodules/functest from branch 'master'
- Publish cloudify scenario
It eases deploying any vnf via Cloudify.
It also stops duplicating code between vims and vrouter.
Co-Authored-By: Valentin Boucher <valentin.boucher@kontron.com>
Change-Id: I5fe06d91804f4781f6b1301da12862bac793ffbb
Signed-off-by: Cédric Ollivier <ollivier.cedric@gmail.com>
|
|
* Update docs/submodules/storperf from branch 'master'
- Switch to upstream nginx
Uses the official upstream nginx container image instead
of building a custom one to support ARM (aarch64).
Uses the official upstream node image instead of building
a customer one for ARM.
Change-Id: Ib465333204d3f1718da8cfb314cad32d955a3d2b
JITA: STORPERF-250
Signed-off-by: mbeierl <mark.beierl@dell.com>
|
|
* Update docs/submodules/functest from branch 'master'
- Force public identity endpoint in Shaker
It conforms with our VNFs by calling public endpoints (from VM).
It fixes by design the issues when testing Compass [1] due to
export OS_INTERFACE=publicURL
[1] https://build.opnfv.org/ci/view/functest/job/functest-compass-baremetal-daily-master/180/consoleFull
Change-Id: Iea15506ba5910879d05e61cfd20da2c0878e569b
Signed-off-by: Cédric Ollivier <ollivier.cedric@gmail.com>
|
|
* Update docs/submodules/sdnvpn from branch 'master'
- Detach quagga vm in the cleanup block
Change-Id: I45145dacaeec0f7b518ab61a33d3a824458e9af5
Signed-off-by: Periyasamy Palanisamy <periyasamy.palanisamy@ericsson.com>
|
|
* Update docs/submodules/armband from branch 'master'
- u/fuel: Bump & rebase for MaaS formula rework
Change-Id: Ica95d00123b99afc916c4fb58a45bf3f068ea7a6
|
|
* Update docs/submodules/nfvbench from branch 'master'
- [NFVBENCH-99] NFVbench should use NOVA scheduler by default
Change-Id: I5fc2b0a26ba0b903d84655d3cc6ad7741314c14e
Signed-off-by: Yichen Wang <yicwang@cisco.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Fix IXIA IxNetwork IMIX configuration
IxNet library is not setting correctly the IMIX definition per traffic
item. The correct input for "weightedRangePairs" parameter is:
[[64, 64, 10], [128, 128, 15], [512, 512, 5]]
JIRA: YARDSTICK-1296
Change-Id: Idb4034ce817250da5b9a434230b1be6dae0d3ba3
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
* Update docs/submodules/fuel from branch 'master'
- [patch] MaaS: Switch to upstream fabric/vlan mgmt
Obsolete our out of tree patch in favor of upstream mechanisms for
creating fabrics/VLANs/subnets.
Change-Id: I57d6d59764a825b428f423d48c5d90af7f2e676f
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
* Update docs/submodules/functest from branch 'master'
- Merge "Refactor tempest common"
- Refactor tempest common
It also renames two testcases and updates all docs because tests
run in parallel in case of tempest smoke.
To force one thread as before:
run:
module: 'functest.opnfv_tests.openstack.tempest.tempest'
class: 'TempestCommon'
args:
mode: '^tempest\.(api|scenario).*\[.*\bsmoke\b.*\]$'
option:
- '--concurrency=1'
JIRA: FUNCTEST-989
Change-Id: I1348f5908400a5046be8edf983db4afa12e546c3
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
* Update docs/submodules/functest from branch 'master'
- Add Vmtp as a new testcase
VMTP is a small python application that will automatically perform
ping connectivity, round trip time measurement (latency) and TCP/UDP
throughput.
JIRA: FUNCTEST-980
Change-Id: I8e94fc52a429f505ac14e14bbb9d0a3b20996ba4
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
* Update docs/submodules/releng from branch 'master'
- [compass4nfv] remove vping suite from verify
functest healthcheck include the vping, so we can remove this suite.
Change-Id: Ifc5f9e2195a9d31713f6e2c2ce47642dc7855855
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge changes from topics 'YARDSTICK-1286', 'YARDSTICK-1127'
* changes:
Make "IterationIPC" MQ producer for VNF control messages
Enable traffic generator PID in "NSPerf" scenario setup
Enable the MQ producer in "SampleVNFTrafficGen" class
Add "TrafficGeneratorProducer" for "GenericTrafficGen" instances
Add "IterationIPC" runner
- Make "IterationIPC" MQ producer for VNF control messages
"IterationIPC" runner class is a consumer for MQ aware VNFs. A MQ aware
traffic generator can send "started", "finished" and "iteration"
messages.
This feature implements a MQ producer in the runner in order to send
messages to the VNFs. The messages implemented are:
- "start_iteration"
- "stop_iteration"
JIRA: YARDSTICK-1286
Change-Id: I706f9a9dda5e5beed52231be7d71452945a7dbed
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
- Enable traffic generator PID in "NSPerf" scenario setup
Now "NSPerf" scenario will inform about the traffic generator PIDs after
setup process. With this information, IterationIPC runner will be able
to receive the messages sent by those traffic generators and control
the main iteration loop.
The following example, using vFW as VNF and OpenStack as context, makes
use of this new runner implementation:
/samples/vnf_samples/nsut/vfw/
tc_heat_rfc2544_ipv4_1rule_1flow_64B_trex_iterationipc.yaml
JIRA: YARDSTICK-1127
Change-Id: I46b1368bc209680b88ff9fb5c3b9beadf6271ac9
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
- Enable the MQ producer in "SampleVNFTrafficGen" class
Now all traffic generators using the default implementation of
"ClientResourceHelper.run_traffic" will update the status of
the traffic injection using the MQ.
The available methods are listed in common.messsaging (VNF_METHOD_*):
- tg_method_started: VNF app started
- tg_method_finished: VNF app finished
- tg_method_iteration: VNF app execution loop started
JIRA: YARDSTICK-1127
Change-Id: I12829e1762fc20cc95da3b50767a66f031e25ee8
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
- Add "TrafficGeneratorProducer" for "GenericTrafficGen" instances
Added "TrafficGeneratorProducer" class, a message producer specific for
"GenericTrafficGen" derived classes.
JIRA: YARDSTICK-1127
Change-Id: Icc87a6920155612e759a1d4d2f29028940c2e040
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
- Add "IterationIPC" runner
"IterationIPC" is a runner that runs a configurable number of times before
it returns. Each iteration has a configurable timeout. The loop control
depends on the feedback received from the running VNFs. The context PIDs
from the VNFs to listen the messages from are given in the scenario
"setup" method.
The MQ consumer, "RunnerIterationIPCConsumer", is subscribed to messages
sent to topic "messaging.TOPIC_TG". The endpoints are defined in the
class "RunnerIterationIPCEndpoint". Three are implemented:
"messaging.TG_METHOD_STARTED", "messaging.TG_METHOD_FINISHED" and
"messaging.TG_METHOD_ITERATION".
JIRA: YARDSTICK-1127
Change-Id: I4b2f11a15ef41e6f3c70bd64188d5c7fbcdb7eed
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
* Update docs/submodules/compass4nfv from branch 'master'
- stop running os-odl_l3-nofeature-ha scenario temporarily
Change-Id: Idffc91aa4a6d259cd9ffb85b653500a78d87095e
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
* Update docs/submodules/domino from branch 'master'
- Auto Generated INFO.yaml file
INFO.yaml meant to be machine readable.
This file was auto generated from an ldap lookup
and your projects INFO file.
Meeting times are not currently filled out.
please ammend this patchset to complete
Going forward comitter promotions should be done
against this file.
PTLs:
Must be merged for you to gain delete access on
testresults.opnfv.org
If project_lead: is missing (my script could not parse)
please amend with same from commiters section eg:
project_lead: &opnfv_dovetail_ptl
name: 'Lead Name'
email: 'lead email'
id: 'lead lfid'
company: 'lead company'
Change-Id: Iedf43c9ea55032ce43e72dc9fa55b8b5d8f8a058
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
* Update docs/submodules/functest from branch 'master'
- Merge "Cover vping_ssh"
- Cover vping_ssh
Change-Id: I37c52057a45d76e081a1a0145baee96041ca25a5
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
* Update docs/submodules/functest from branch 'master'
- Temporarily disable Snaps CreateRouterSuccessTests
The test could be falsy regarding the possible external network
configs [1]. This patch will be reverted as soon as the bug is closed
[2].
[1] https://build.opnfv.org/ci/view/functest/job/functest-apex-baremetal-daily-fraser/246/console
[2] https://jira.opnfv.org/browse/SNAPS-320
Change-Id: I680656b300f0d669e8d96bec6c94a4a804ebbecb
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
* Update docs/submodules/bottlenecks from branch 'master'
- Merge "Auto Generated INFO.yaml file"
- Auto Generated INFO.yaml file
INFO.yaml meant to be machine readable.
This file was auto generated from an ldap lookup
and your projects INFO file.
Meeting times are not currently filled out.
please ammend this patchset to complete
Going forward comitter promotions should be done
against this file.
PTLs:
Must be merged for you to gain delete access on
testresults.opnfv.org
Change-Id: I61cf3bacbc109286b258748834d59eccd489fdb7
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
* Update docs/submodules/clover from branch 'master'
- Merge "Initial commit for Clover Collector"
- Initial commit for Clover Collector
- Added a container named clover-collector using clover
container as a base with build script
- GRPC server to manage collector process
- Cassandra DB client interface to initialize visibility keyspace
- Init messaging adds table schemas for tracing - traces & spans
- Adds table for monitoring - metrics
- Does not implement Cassandra server but developed using
public Cassandra docker container
- Collector process in simple loop that periodically fetches
traces and monitoring data and inserts to Cassandra - not optimized
for batch retrieval yet for monitoring
- CLI interface added to collector process and used
by GRPC server for configuration
- Simple GRPC client script to test GRPC server and start/stop
of collector process
- Collector process can be configured with access for tracing,
monitoring and Cassandra
- Added a return value in monitoring query method
- Added ability to truncate tracing, metrics and spans tables
in cql
- Added cql prepared statements and batch insert for metrics
and spans
- Align cql connection to cql deployment within k8s
- Fix issue with cql host list using ast and collect process
args with background argument
- Added redis interface to accept service/metric list
externally for monitoring (will work in conjunction
with clover-controller)
- Use k8s DNS names and default ports for monitoring, tracing
and cassandra
- Added yaml manifest renderer/template for collector
Change-Id: I3e4353e28844c4ce9c185ff4638012b66c7fff67
Signed-off-by: Eddie Arrage <eddie.arrage@huawei.com>
|
|
* Update docs/submodules/clover from branch 'master'
- Merge "Sleep 1 sec after set test."
- Sleep 1 sec after set test.
if we set testid and start test immediately,
the first test's result can't be got from jaeger
Change-Id: Ia2ab8a91d8c5f9956ea4d3d7c2436fb05490acee
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
* Update docs/submodules/clover from branch 'master'
- Merge "[clover] Add script to setup k8s"
- [clover] Add script to setup k8s
what the script do
1. git clone the XCI repo
2. set variable to deploy k8s
how to use
run the below command in you teminal
./xci-k8s-setup.sh
requirement
1. don't under the root user
2. run sudo without password
Change-Id: I5015e12d8d3b0db31285d5e817b3c40d6739ba22
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
* Update docs/submodules/apex from branch 'master'
- Physical interface type note
add ovs_bridge as needed compared to earlier version
Change-Id: I1d0c6df9d1f47b0c98a3c1a8bf3a04eb5f53aff2
Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
|
|
* Update docs/submodules/dovetail from branch 'master'
- Add dovetail-webportal repo to INFO file Listing
Change-Id: I429e5bb1dffb1c63301ad5e9aba34d08d788ca27
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
* Update docs/submodules/copper from branch 'master'
- Auto Generated INFO.yaml file
INFO.yaml meant to be machine readable.
This file was auto generated from an ldap lookup
and your projects INFO file
Meeting times are not currently filled out.
please ammend this patchset to complete
Going forward comitter promotions should be done
against this file.
PTLs:
Must be merged for you to gain delete access on
testresults.opnfv.org
If project_lead: is missing (my script could not parse)
please amend with same from commiters sectioneg:
project_lead: &opnfv_dovetail_ptl
name: 'Lead Name'
email: 'lead email'
id: 'lead lfid'
company: 'lead company'
Change-Id: Id8640d35adf5f2eb378381300a7e11aaa4cd97f4
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
* Update docs/submodules/apex from branch 'master'
- Fix neutron-opendaylight-sriov.yaml path
In latest THT upstream, environment file neutron-opendaylight-sriov.yaml was
moved to services folder. Updating references in Apex to avoid deploy failure.
Change-Id: I7065e0d8e13c9add9ead282db2244a27c177e5a4
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
* Update docs/submodules/functest from branch 'master'
- Fix delete_keypair arg
It uses keypair name instead of id as expected by Shade.
It also increases timers as it boots an ubuntu VM.
Change-Id: I8cd131e7c7a94c8f6b0fcc54a4d75ef8af31b807
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
* Update docs/submodules/availability from branch 'master'
- Merge "Auto Generated INFO.yaml file"
- Auto Generated INFO.yaml file
INFO.yaml meant to be machine readable.
This file was auto generated from an ldap lookup
and your projects INFO file.
Meeting times are not currently filled out.
please ammend this patchset to complete
Going forward comitter promotions should be done
against this file.
PTLs:
Must be merged for you to gain delete access on
testresults.opnfv.org
Change-Id: I3b6c5ff8158ec3f0a9426e2b7b8566d04952d278
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "jjb/releng: fix partial image name matching"
- jjb/releng: fix partial image name matching
Docker image building script opnfv-docker.sh tries to remove existing
images before and after building. It simply uses grep to matching image
names, which may cause partial name matching problems.
Ex. opnfv/compass-tasks will match both opnfv/compass-tasks and
opnfv/compass-tasks-base, and may lead to accidentally removing of
images still in use when several building tasks run concurrently.
Error log:
https://build.opnfv.org/ci/job/compass-tasks-build-arm64-master/6/console
Change-Id: I1a83f801c5e0cc889cd9e17b8d1b4d895f1f68a9
Signed-off-by: Yibo Cai <yibo.cai@arm.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Add "env" parameter in Kubernetes context
This new parameter, "env", will allow the user to
automatically to add environment variables in a pod definition
Example of definition in a context:
context:
type: Kubernetes
servers:
host:
image: ...
commands: ...
env:
- <variable name>: <variable value>
- <variable name>: <variable value>
The volume type and the definition must be one of the supported
ones in Kubernetes [1].
[1] https://kubernetes.io/docs/concepts/storage/volumes/#types-of-volumes
JIRA: YARDSTICK-1161
Change-Id: Icf372a98c090063f10c9217755519ab92ba9b0ba
Signed-off-by: John O Loughlin <john.oloughlin@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Create user defined "NodePort" services per pod"
- Create user defined "NodePort" services per pod
This feature will give the user the ability to create user defined "NodePort"
services per pod, a part from the default SSH port created, by default, for
each pod created.
Example of Kubernetes yaml definition:
apiVersion: v1
kind: Servicemeta
data:
name: pod-1-service-nodeport
spec:
type: NodePort
ports:
- name: web
port: 80
targetPort: 8888
nodePort: 33333
clusterIP: 10.254.0.8
selector:
app: pod-1
Example of Yardstick test case definition:
context:
type: Kubernetes
servers:
host:
containers:
- image: ...
securityContext:
allowPrivilegeEscalation: false
- image: ...
node_ports:
- port: <port number> # Mandatory
name: <port name> # Optional
targetPort: <port name> # Optional, default: targetPort=port
nodePort: <port number> # Optional, assigned by Kubernetes
Kubernetes service, type "NodePort" [1]
[1] https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport
JIRA: YARDSTICK-1181
Change-Id: Ia7730e4569d5526d573402a98c27d55c5c82cdef
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Change "KubernetesObject" class name to "ReplicationController""
- Change "KubernetesObject" class name to "ReplicationController"
The class name "KubernetesObject" is not accurate. This class holds
the definition of a Kubernetes replication controller. The suggested name
is therefore "ReplicationControllerObject".
JIRA: YARDSTICK-1180
Change-Id: I9ee9228f9528cb779e54a9bc178760b6e24c85c2
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Specify the networks to be used per pod"
- Specify the networks to be used per pod
If CRD "Network" is defined and network items are created, each pod (server)
can have access to one or several networks. This is defined in the metadata
section, as "annotations.networks" [1].
Example of Kubernetes pod definition with networks:
apiVersion: v1
kind: Pod
metadata:
name: test-pod
annotations:
networks: '[{"name": "flannel"}]'
Example of Yardstick server definition with networks:
context:
type: Kubernetes
servers:
host:
containers:
- name: ...
networks:
- flannel # These names must be defined in
# context.networks
...
networks:
- name: flannel
plugin: flannel
Kubernetes annotations [2].
[1]https://github.com/intel/multus-cni/tree/b9446232cdf4f1b6f2bea583291973cc97e963f4#configuring-multus-to-use-kubeconfig-and-a-default-network
[2]https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/
JIRA: YARDSTICK-1178
Change-Id: I6e7b4bacf10810833ec733c14d44e5db613675e3
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Add new Kubernetes resource kind: "Network""
- Add new Kubernetes resource kind: "Network"
Add a new Kubernetes resource kind: "Network" [1] [2]
Kubernetes network plugins (alpha definition): [3]
Network definition example in Kubernetes:
apiVersion: "kubernetes.com/v1"
kind: Network
metadata:
name: flannel
plugin: flannel
args: '[
{delegate": {"isDefaultGateway": true}}
]'
Proposed Kubernetes context network definition:
context:
networks:
- name: flannel
plugin: flannel
args: (string)
- name: sriov_upload
plugin: sriov
args: (string)
[1]https://builders.intel.com/docs/networkbuilders/multiple-network-interfaces-in-kubernetes-application-note.pdf
[2]http://cdn.opensourcecloud.cn/zt/k8s/01.pdf
[3]https://kubernetes.io/docs/concepts/cluster-administration/network-plugins/
JIRA: YARDSTICK-1160
Change-Id: I71a49ac14e3d28ded91d2ed3cd9cc527e40303f7
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Add new Kubernetes resource kind: "CustomResourceDefinition""
- Add new Kubernetes resource kind: "CustomResourceDefinition"
Custom resource definition example in Kubernetes:
apiVersion: "apiextensions.k8s.io/v1beta"
kind: CustomResourceDefinition
metadata:
name: networks.kubernetes.com
spec:
group: kubernetes.com
version: v1
scope: Namespaced
names:
plural: networks
singular: network
kind: Network
Proposed Kubernetes context network definition:
context:
custom_resources:
- name: network # name of the resource (singular)
version: v1 # optional, "v1" by default
scope: Namespaced # optional, "Namespaced" by default
From this definition, we will extract the Kubernetes parameters:
- metadata.name: custom_resources.name + "s" + context_name + ".com"
- spec.group: context_name + ".com"
- spec.scope: custom_resources.scope
- spec.version: custom_resources.version
- spec.names.plural: custom_resources.name + "s"
- spec.names.singular: custom_resources.name
- spec.names.kind: custom_resources.name with first capital letter
[1] https://kubernetes.io/docs/concepts/api-extension/custom-resources/
JIRA: YARDSTICK-1163
Change-Id: If8980dc3f6ddf9c6949bf15be8011aa98482ddc9
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Add "securityContext" parameter in Kubernetes context"
- Add "securityContext" parameter in Kubernetes context
This new parameter, "securityContext", will allow the user to define the
privilege and access control settings for a pod or a container [1].
Example of "securityContext" definition in the pod (if only one container
is defined):
context:
type: Kubernetes
servers:
host:
image: ...
securityContext:
runAsUser: 1000
fsGroup: 2000
Example of "securityContext" definition in the pod and the container (if
several containers are defined):
context:
type: Kubernetes
servers:
host:
securityContext:
runAsUser: 1000
fsGroup: 2000
containers:
- image: ...
securityContext:
allowPrivilegeEscalation: false
- image: ...
[1] https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
JIRA: YARDSTICK-1156
Change-Id: I597a300c68cd834522a284b1cca0faa918493342
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "[Bug fix] Execute teardown if SLA is set to "assert""
- [Bug fix] Execute teardown if SLA is set to "assert"
In Duration runner if SLA is set to "assert" and a SLAValidationError
happens then a teardown is needed to avoid garbages in the environment.
JIRA: YARDSTICK-1291
Change-Id: I9056b0da3e7e496171ed42430ffc340b5c68f108
Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com>
|