Age | Commit message (Collapse) | Author | Files | Lines |
|
A test dealing with the verification of the ports exposed as nodeports
is already integrated. The goal of the patch is to compelte with a test
dealing with all the internal ports retrieved from k8s on the ONAP namespace.
Unlike nodeport_check_certs, this test must be executed from inside the
cluster.
As a consequence a dependency is added in testcases.yaml
- TEST_ENVIRONMENT: 'internal_job'
In order to avoir triggerring the test when executing all the infra
tests of this xtesting dockers.
A kubernetes job consuming the image shall be created in xtesting-onap
to execute the test.
Issue-ID: INT-1818
Signed-off-by: mrichomme <morgan.richomme@orange.com>
Change-Id: I16bb55fb784bd67f8a2b59f9f895fb754da8e3d0
|
|
Instead of parsing only helm status, this new test is also taking a look
at specific helm deploy plugin logs.
Also, main pages is now "html" based instead of raw based.
Issue-ID: INT-1718
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: Ia851db5c8cfd866394ed22e3cd3b7ce183ef0fb9
|
|
Note the success criteria part shall be refactored
For the moment I keep as it is but it is too complex
As we plan to refactor onap-helm to include more detail
I do not do it here
Issue-ID: INT-1718
Signed-off-by: mrichomme <morgan.richomme@orange.com>
Change-Id: Ib93e0afca6b31571607bc0bd548b71a194f44c44
|
|
Now everything is done in ONAP, no ref to gitlab.com needed
+ fix for certif test call
+ harmonization https+pip to use git.onap.org (not gerrit.onap.org)
Issue-ID: INT-1570
Signed-off-by: mrichomme <morgan.richomme@orange.com>
Change-Id: Idde25ae6e96b60f35a4383ff9dbc494422d8bf4c
|
|
this tests checks the validity of the certificates
by testing each SSL termination corresponding to node
ports retrieved from the k8s python client
It generates an html page with the list of the
SSL certficiates, it indicates
- the expiration date
- the certificate owner
A code color is provided too indicate if the cert is about
to expire
and/or is too wide (364 days max)
The integration to xtesting is the first step before
adding the test in Master daily CI
Issue-ID: INT-1570
Signed-off-by: mrichomme <morgan.richomme@orange.com>
Change-Id: Ia20fc999610d1967eb9eed9415a568b3dbdda3e7
Signed-off-by: mrichomme <morgan.richomme@orange.com>
|
|
The goal is to use xtesting once we shall be able to build
all the dockers properly
Issue-ID: INT-1366
Signed-off-by: mrichomme <morgan.richomme@orange.com>
Change-Id: I068eb6019f6eec04b46b545222cbb5cecb265234
Signed-off-by: mrichomme <morgan.richomme@orange.com>
|
|
Issue-ID: INT-1366
Signed-off-by: mrichomme <morgan.richomme@orange.com>
Change-Id: I3af9c4697f0e67d3ce5b6d2fceeb978aeb20a0ff
|
|
All the Dockerfiles and xtesting configurations were hosted in gitlab.com [1]
The goal of this patch is to host these assets in ONAP
A jenkins jjb shall be created to generated the docker and push them on the nexus
(today the built-in registry of ONAP was used)
These xtesting dockers are referencing integration categories [2] and integration
use cases [3]
These xtesting dockers shall also simplify the way to integrate new use cases in any
CI chain (jenkins or gitlab-ci based)
[1]: https://gitlab.com/Orange-OpenSource/lfn/onap/integration/xtesting
[2]: https://wiki.onap.org/pages/viewpage.action?pageId=71835330
[3]: http://testresults.opnfv.org/onap/api/v1/projects/integration/cases
Issue-ID: INT-1366
Signed-off-by: mrichomme <morgan.richomme@orange.com>
Change-Id: Iba0fc0b0415731a7a81ba0225a70ae16391dd129
Signed-off-by: mrichomme <morgan.richomme@orange.com>
|