Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I151ab12fd3a8c47f1efe098d532a5fce7149940a
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
Change-Id: I8151fe50bc5f0d93aeec1583485e9604b3a0ad8a
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
Change-Id: Ic740396c3f8d1a6412a08a56a21ff9cfbeb925b1
Signed-off-by: Manuel Buil <mbuil@suse.com>
(cherry picked from commit fd707b3d268129d02e726523517dae837b2f0556)
|
|
Change-Id: I0d6f48eff3edd7e1117ec0c5f7f16c1de35300d5
Signed-off-by: Manuel Buil <mbuil@suse.com>
(cherry picked from commit 72121b19a9c12961afdfd6ee7d4fe3eff95d8b10)
|
|
As discussed with the releng-xci team, each project should have the scenario in
its repo
Change-Id: I2cb407892edeeccabf396c7b1c341c78fba2828e
Signed-off-by: Manuel Buil <mbuil@suse.com>
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
(cherry picked from commit 90b3ef7c16d604e53cce22169822878438ced78a)
|
|
Apex deployment shows a problem when creating the SFC config in ODL and
it is impossible to know what might be going on
Change-Id: If8d33d1c60daaf9cd9773a5cb9c7e47f64e1caa9
Signed-off-by: Manuel Buil <mbuil@suse.com>
(cherry picked from commit f19a910411260203ff33d290e7460a296f5786fc)
|
|
We moved to a new image for SFs but we have not moved the name of the image
in the vnfd
Change-Id: I8f658e1dfcf0de3117845f615eddb8fd5b1e11af
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
To create the four SFs we will use the sfc_nsh_euphrates image. This image is
like the sfc_nsh_danube but modifying the vxlan_tool which now has the
important fix:
https://git.opendaylight.org/gerrit/#/c/64116/
Change-Id: I396b5523b7243472b6d05b62d831837938067422
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
|
|
Change-Id: Ief3908496bd6809c412bd394e7fd744f2ee796ae
Signed-off-by: Manuel Buil <mbuil@suse.com>
(cherry picked from commit a69bbffa313618b15f100707db532781e6f6ed9b)
|
|
This is an update of the release notes for the Euphrates release
Change-Id: Ia74839aceb53f6a647b4695c0cc3f7cf8d8e8282
Signed-off-by: Manuel Buil <mbuil@suse.com>
(cherry picked from commit 53798427e7cf6f4c709ae2c03bd305b920cbb773)
|
|
Sometimes VM starts very quickly and then it takes longer for this service
to come up
Change-Id: Ibc4ea47eb0b4b6655e338d1b85e6ed14e61d0064
Signed-off-by: Manuel Buil <mbuil@suse.com>
(cherry picked from commit 95503c8d3aa79e64be4a68348436f3c64dc8464e)
|
|
As agreed with the releng-xci guys, we should not use capital letters to refer
to openstack-ansible (osa)
Change-Id: I634747b07e72513f751cde3eb33f3b4bad5c176d
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
JIRA: SFC-116
It is confusing that our test-1 is in the second position of config.yaml
and that it uses test2-vnfd instead of test-vnfd
Change-Id: Iffd22f295630bce0ce854d4876c1478c56690cfa
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
After testing, there are three topologies which work and three topologies which
do not work because of bugs in OVS and ODL. We remove those two from the
testing in 5.0.0
Change-Id: I576768978bfa763725027239081686c95408eef4
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
Change-Id: I64caba2eea3ff93d082c08915f82be7ef701a3f1
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
JIRA: SFC-114
Some cases show that it was not enough with the patch:
https://gerrit.opnfv.org/gerrit/#/c/42801/
We should explicitely disable security in the SF ports. That can be done
with a the antispoofing parameter in the vnfd
Change-Id: Ie20ab961633866f48a4abcc299a62e8c55280088
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
JIRA: SFC-117
Change-Id: I20e12e38a3cf2a9954893cf52187ac153b64bdfa
Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com>
|
|
Test 2 is continuously failing because of tacker missing functionality
Change-Id: I785e79d78df4bfb9f48e20288e261efff741bcd4
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
JIRA:SFC-113
We used to check that the ACL and RSP flows were implemented because it took a
lot of time. However, the new ODL Nitrogen reduced this time a lot and thus we
must check that the vxlan_tool is up and the HTTP port is up in the server
before doing any test
Change-Id: I70219071c7965781b17e80631bf3e2efbfcfe4cd
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
Having the SFs port in security groups delays packets artifically in the tests
Besides, the netvirt guys suggested not to do it because it might be confusing
for ODL in some situations and it is not a 'suitable construct'
Tests without security groups show indeed a better behaviour
Change-Id: I33281215cd2e80804c8f09ca201c046f590249ab
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
JIRA: SFC-110
Sometimes the test is quicker than ODL and when it checks the configured RSP,
that configuration has not yet been submitted in ODL, thus ODL replies with an
empty list. We add an iteration to try again for a couple of times
Change-Id: I21e4ac3fc3a919791daa7e41cb2953f7565c4ebb
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
JIRA: SFC-107
We are submitting the vnffgd with a variable for the neutron_port. Before
creating the vnffg, we must provide a file with the neutron_port value
Change-Id: I9994e2baa53f323df17434448d372598c0d94c72
Signed-off-by: Manuel Buil <mbuil@suse.com>
(cherry picked from commit 9c11d59035ff1741c5e6d935aa7c2ed23d15f485)
|
|
|
|
|
|
JIRA: SFC-106
In sfc_two_chain testcase we need to delete first the blue
and then the red vnffg because if we do it the other way around
the tacker produces a warning that the flow classifier of the vnffg red
is in use and cannot delete the chain.
The aforementioned warning is produced because during the execution
of the two_chain testcase we reassing the classifier from the red vnffg
to the blue vnffg. So if we try to delete first the red vnffg we get the
warning because the classifier is assigned and in use from the blue
vnffg.
Change-Id: I3cb7bef4b9b9e75eef4961fe7f63cbc1755130be
Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com>
|
|
It is currently impossible to obtain the vnfd_id based on the vnfd_name when
we want to create the vnffg
Change-Id: Ib7752156db43d76c24f8c6c2803eb7dbc5bbe1d8
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
JIRA: SFC-105
They have a typo which resulted in errors in Tacker when loading the template
Change-Id: I5723c756add7610377815180352140d58fd783a5
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
There are some checks in sfc_two... which do not exist in sfc_one. Those checks
should be done at the beginning of the test
Change-Id: I44c612c7dfe6bb4329bc49478f3342cda555229c
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
Two things must be done:
1 - Be compatible with the new way of doing SFC in ODL Nitrogen
2 - Be installer independent
Change-Id: Ibbb3057db30a7c00e92f788bb03e770749e2b255
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
Change-Id: I3a34daaca258cd2ce511aee51819cf438110e403
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
|
|
My VMs take around 80 seconds to be able to respond to pings. The current
timeout is in 50 seconds. I will increase it to 150 to have a buffer
Change-Id: Ie684e76799210e3d7239e35df2d4bdd7af507669
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
ODL requires that parameter to be present in order to classify
Change-Id: Idb8e0578a9c4c22cd35e4615755333b67d4fe658
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
|
|
|
|
In this patch [0] we adapt the Tacker library which is
located to the SFC repo to the new Tacker API
With the current patch we allign the testcases to the
aforementioned API
[0] https://gerrit.opnfv.org/gerrit/#/c/40839/
Change-Id: I07f8bcefbda7d058e9322465df38077ac0346d83
Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com>
|
|
Change-Id: I078e9f26d3040cf04120abd425f03cb4f2e8daef
Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com>
|
|
We are going to use ODL Nitrogen which does not require the NSH hack as
packets reaching the VNF will use ETH+NSH encapsulation
Change-Id: I5a55fde84e8f17860783ec9de8b99242fc38b9a9
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
Change-Id: I710e6f5da92ddfddd9111c6c53274b92d76d7449
Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com>
|
|
Change-Id: I16a5e4522dde96de8d06e6cfb1e3a429b4f171de
Signed-off-by: Taseer Ahmed <taseer94@gmail.com>
|
|
Right now the testcases are dependent to only one installer.
So when we are trying to run the testcases to multiple installers
the tests are failing.
This patch make the testcases independent to the installer that they
run.
The testcases are running until the point which they hit the tacker
client commands.They are failing in the tacker client commands
because we need the new library for the upstream tacker API.
The testaces have already tested to two installers (Fuel,Apex-ha).
Also this patch contains the changes which are required for the
adaptation to the new functest.
For more information see the Jira tickets [0],[1],[2].
[0]: https://jira.opnfv.org/browse/SFC-100
[1]: https://jira.opnfv.org/browse/SFC-101
[2]: https://jira.opnfv.org/browse/SFC-102
Change-Id: Id1e5d5c94a65ab8bdea9584fa833bfa0cdec6632
Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com>
|
|
Change-Id: I33f3fd0aa0bc71a1ee07ea4504619b090517a87b
Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com>
|
|
- Create VNFFG Descriptors for testcases
JIRA: SFC-102
Change-Id: Ib51364d98c58942fec1f54b1f149bb0e8ffedc43
Signed-off-by: Taseer Ahmed <taseer94@gmail.com>
|
|
In previous releases we used a custom tacker client
because we also used a custom tacker.
For the next release we migrate to the the upstream tacker
so we don't need anymore the aforementioned installation script
because now we support the upstream tacker client.
Change-Id: I0c502426161bbeaaf2418823fe91c2025f1494a8
Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com>
|
|
In OPNFV/SFC project we are going to substitute
the custom tacker that we used so far with the upstream one.
So as outcome of the aforementioned change we will need the
upstream tacker client.
Change-Id: I8425c7168c1be69d090481efbf3f966e8d04e609
Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com>
|
|
artifacts.opnfv is not used anymore. We are using now docs.opnfv
Apart from that, I removed the OVS-NSH workaround explanation as we don't use
it anymore
Change-Id: Iaf4f2d97a4252754f5b22709aef653fff0777eae
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
As part of MS6 we must have an updated directory structure. I added the two new
scenarios using fdio
Change-Id: If74dade8c75c59d452b034b98fff5dc0791b2191
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
- Update vnfd tosca templates
JIRA: SFC-102
Change-Id: I712b64e45c317582e0cb54e42364605f537aeee3
Signed-off-by: Taseer Ahmed <taseer94@gmail.com>
|
|
MS6 requires to have the docs directory structure ready and a preliminary
versio of the documents inside it.
- Moved requirements file to the requirements folder
- Removed the NSH workaround info as we don't need it anymore
- Added some new requirements
Change-Id: Icca89c738b1eb1865adff510ca2850c592c7a14a
Signed-off-by: Manuel Buil <mbuil@suse.com>
|