From: cntt-gov@... [mailto:cntt-gov@...] On Behalf Of cedric.ollivier via Lists.Opnfv.Org
Sent: Thursday, November 28, 2019 08:40
To: cntt-gov@...; TSC OPNFV (opnfv-tsc@...) <opnfv-tsc@...>; Kosonen, Juha (Nokia - FI/Espoo) (juha.kosonen@...) <juha.kosonen@...>; GOYAL, PANKAJ <pg683k@...>; SEVILLA Karine TGI/OLN <karine.sevilla@...>
Cc: cntt-gov@...
Subject: [cntt-gov] New CNTT-API compliance containers in Functest

 

Hi,                         

 

We just released the first CNTT API compliance containers from OPNFV Functest and the associated tooling to quickly setup plug-and-play Continuous Integration toolchains everywhere (Xtesting CI).

The 8 GNU/Linux commands (a few minutes) to deploy the full CI/CD toolchain are available on the wiki https://wiki.opnfv.org/pages/viewpage.action?pageId=32015004

 

Our gating is already successful which means that our CNTT API Compliance test cases are good and that our Functest System Under Tests (SUTs) are compliant which RA1 Chapter 5 (API).

It also confirms that RA1 Chapter 5 is implemented and then correct.

https://build.opnfv.org/ci/view/functest/job/functest-hunter-daily/329/

 

Thanks to API descriptions recently added in CNTT, we can easily implement the compliance too via Functest.  

Compared to our classical containers verifying any OpenStack deployment, the new containers mostly override our classical test lists (e.g. forbidding skipping tests vs mandatory services/capabilities) and tune the test configurations.

The CNTT RI CI Jobs are ready too and will automatically execute this new testcases after the next successful deployment.

 

For the time being, I haven’t seen any metric regarding API benchmarking (Rally) or dataplane benchmarking (Shaker and Vmtp).

The default values are kept as they are but opnfv/functest-benchmarking-cntt is already in place for the next steps.

 

From my understanding, opnfv/functest-healthcheck and functest-vnf should be executed in the Compliance process as they are.

They leverage on the mainline API and it makes sense to get a quick feedback before testing deeply and to onboard and test the existing “real” VNFs here (IMS, EPC and vRouter).

 

Regarding the next CI/CD steps, it would more than helpful to leverage on Xtesting to wrap the RI deployment calls.

It will deeply simplify the cookbook by offering a new playbook in CNTT RI tree.

 

We can easily add any OPNFV testcase supporting the common testcase execution.

But I haven’t seen any key update in the related CNTT issues or new patchsets in OPNFV gerrit.

 

Be free to review API Chapter 5 and/or all testcases as proposed in opnfv/functest-smoke-cntt and opnfv/functest-benchmarking-cntt and to ask any additional details.

I can also propose a specific track in the next CNTT event in Prague.

 

Cédric

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.

Links:

You receive all messages sent to this group.

View/Reply Online (#197) | Reply To Sender | Reply To Group | Mute This Topic | New Topic

Your Subscription | Contact Group Owner | Unsubscribe [Mark.Shostak@...]