Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
Change-Id: Ie788bcac905ffb84b70751a91996e3177f5577bf
Signed-off-by: rohitsakala <rohitsakala@gmail.com>
|
|
Change-Id: I81424c3670b6a6e03a38da83dc93c998bf8c2f5e
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
Docker build failed due to the wrong path for downloading cirros images for
aarch64. The right path should be:
http://download.cirros-cloud.net/daily/20161201/cirros-d161201-aarch64-disk.img
http://download.cirros-cloud.net/daily/20161201/cirros-d161201-aarch64-initramfs
http://download.cirros-cloud.net/daily/20161201/cirros-d161201-aarch64-kernel
Change-Id: I3f1391995c10be54e178943919dabdcf5763edde
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
|
|
|
|
In order to run functest on an aarch64 POD, some custom configuration
is needed. Up until now that custom configuration was put on the arm
jenkins slave. With this commit it is integrated in functest project.
1. In order to identify if the POD is aarch64 or x86 function
get_arch() from https://gerrit.opnfv.org/gerrit/#/c/29099
is used
2. Changes to config_functest.yaml are made via a new patch file
config_aarch64_patch.yaml which is applied for all scenarios.
Function patch_config_file() is modified to be more generic. It
now receives a file as parameter and merges any type of patch file
3. The aarch64 cirros images are downloaded into the data directory.
Functest can be run from both an aarch64 or a x86 jenkins slave
in order to test an aarch64 POD. So the images are downloded in both
dockerfiles
4. Other custom config needs to be added to /etc/rally/rally.conf
in the docker. The custom config is set in rally_aarch64_patch.conf
and inserted in the needed file before the rally environment is
set up
JIRA: ARMBAND-60
Change-Id: I8e460cdf02d297c259cbbd9c05e7983367fd2bb9
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
|
|
|
|
|
|
|
|
|
|
Some users need to run a specific list of
tempest test cases. This patch allows them
to do that by running the command:
functest testcase run tempest_custom
Change-Id: If8e7726b98c3a71398c7abdf80aea79f10653ebf
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
|
|
|
|
Refstack is the OpenStack project that provides the tooling
to run the approved specific tempest test cases (Defcore guidelines)
by the Interop working group and by the OpenStack board
for OpenStack certification purposes.
For more info: https://refstack.openstack.org/
This adds the possibility for a Functest user to run this list
of tempest test cases by just issuing the command:
functest testcase run tempest_defcore
The test will be run on daily loops with the scenario nosdn-nofeature
on any installer.
Change-Id: I920b2a44cff418116008fdf514425e69dc959412
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
|
|
|
|
JIRA: FUNCTEST-530
1.setting "nosdn-nofeature" scinario in testcase.yaml.
1.adding process of setting result details for push DB
2.Delete of define "vrouter_data" in config_functest.yaml.
3.modify of vrouter git tag's name "stable".
4.modrify of testcase name "vyos_vrouter" In order to more specific.
Change-Id: I0602c01dbf9a5e71bf85943c2b5e40ef51269ffd
Signed-off-by: Hideyasu Hayashi <hideyasu.hayashi@okinawaopenlabs.org>
|
|
JIRA: FUNCTEST-726
Change-Id: Ie6a35a817aa327a7e9143d93b5ea2582e99e0066
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
|
|
CI for compass and joid failed as there is no key defined in
installer_params.yaml
Change-Id: I8d17d36d854974c0751d3fd3bab4994205f786bb
Signed-off-by: helenyao <yaohelan@huawei.com>
|
|
Change-Id: I177820638c7b050764c5354cd7ed22a7ccf3acbc
Signed-off-by: Ulas Kozat <ulas.kozat@gmail.com>
|
|
|
|
|
|
JIRA: FUNCTEST-706
Change-Id: I485337c2010f1250f34dcffdca91c52793e274c5
Signed-off-by: rohitsakala <rohitsakala@gmail.com>
|
|
JIRA: FUNCTEST-707
Change-Id: Ieaa888375136eddbbe003a24b32bf09fd0f92923
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
With the recent changes in Cirros image default password, we
need to support configuring these credentials.
JIRA: ARMBAND-218
Change-Id: I5962ec2aeee4ffecefdd8b7e70bdb7ed88457553
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
The healthcheck tier has grown thanks to the
adoption of SNAPs library. Now we have a SNAPs test
case that checks that creating a Network, a VM
and making sure it gets an IP from the DHCP agent
works. Basically, we are duplicating both test cases.
This patch removes the execution of the former test
without eliminating the code.
Change-Id: Iad6fec10fa1c247151c68313dc3760a55e511555
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
|
|
JIRA: FUNCTEST-727
Change-Id: I4d8e24c0cb6272d92dc777dc82d56490948598db
Signed-off-by: helenyao <yaohelan@huawei.com>
|
|
|
|
Change-Id: I12b17ee7ed03987473825e0705074f0430b820bb
Signed-off-by: ashishk1994 <ashishk.iiit@gmail.com>
|
|
Kingbird functest was excluded from Functest due to python client
dependency conflict. But in Functest container, the kingbird was
installed only for tempest plugin descovery and execution of tempest
test cases. It's safe to restore kingbird installation in the Dockerfile
now.
The kingbird installation works after the functest container image
was built.
Change-Id: I44593dcf47dd1deed2f6a94b7e801230bae9b251
Signed-off-by: joehuang <joehuang@huawei.com>
|
|
|
|
|
|
Also, add a executor method in VNFBase
to allow re-write it for some cases
where the feature is another python
script instead of shell script.
Change-Id: Id734553dffe32fdc9a0befc3f4c0e29e5d56fc61
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
Example virtual deployment apex:
http://paste.openstack.org/raw/599536/
Example CI POD:
http://paste.openstack.org/raw/599537/
Change-Id: I0711b45a525bc074a9c05f0ea3a194b2db05f2d9
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
Adding admin role to the new_user for the new tenant
It will fix this bug for other tests based on this class
JIRA: FUNCTEST-734
Change-Id: Ia3b8797fa391f528d24425a5b13c1b329cb992f4
Signed-off-by: boucherv <valentin.boucher@orange.com>
|
|
If the VNF does not properly boot after timeout, wait_for_vnf
should return "None" to flag the error.
Also, refresh the VNF on every iteration.
Change-Id: I9ed7c399e689dfbace7c5c8914552e77bf45fc8f
Signed-off-by: Juan Vidal <juan.vidal.allende@ericsson.com>
|
|
|
|
Change-Id: I1828242cec6449b36d09be21a62074b3c131af17
Signed-off-by: Juan Vidal <juan.vidal.allende@ericsson.com>
|
|
Change the way of using few variables like vnf from object
to dictionary for consistency.
Change-Id: I5cf92ff16ba1296f223a60f85de4b815aadc8875
Signed-off-by: ashishk1994 <ashishk.iiit@gmail.com>
|
|
|
|
|
|
|
|
create_vnf function could end up in and endless loop if it is not able to
retrieve the VNF id. Also, a timeout could help to detect problems when
instantiation is too slow.
Change-Id: I21744338a73f122d0c7a8fbe699738b11a7e2b76
Signed-off-by: Juan Vidal <juan.vidal.allende@ericsson.com>
|