Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RM Ch08] Compare / Align with OVP and CVC Compliance Definitions #363

Closed
michaelfix opened this issue Oct 2, 2019 · 5 comments
Closed
Assignees
Labels
Archive Archive Item
Projects

Comments

@michaelfix
Copy link
Collaborator

michaelfix commented Oct 2, 2019

Per 10/2 RM Ch 8 call, purpose of the issue is to close on definitions and terms of Compliance, Verification, and Validation, by comparing CNTT and CVC/OVP documentation.

Resource link: https://wiki.lfnetworking.org/pages/viewpage.action?pageId=10551934

@michaelfix
Copy link
Collaborator Author

Will assign to Trevor Cooper upon receipt of his GitHub ID.

@michaelfix
Copy link
Collaborator Author

@trevgc - please review/comment.

@trevgc
Copy link
Collaborator

trevgc commented Oct 8, 2019

  1. Compliance: A "device" is compliant if it meets the requirements defined within a specification, i.e. a power plug is required to have 3 prongs and would be consider compliant if it indeed has 3 prongs in the correct locations and orientations. Meaning of NFVi compliance, scope of testing as well as considerations for future can be found in the OVP Program Guidelines Addendum https://opnfv-dovetail.readthedocs.io/en/latest/testing/user/ovpaddendum/index.html
  • Indicates adherence of an NFV platform to behaviors defined through specific platform capabilities, allowing to prepare, instantiate, operate and remove VNFs running on the NFVI

  • Compliance test cases are designated as compulsory or optional based on the maturity of OPNFV capabilities as well as industry expectations

  • Test coverage and pass/fail criteria are designed to ensure an acceptable level of compliance but not be so restrictive as to disqualify variations in platform implementations, capabilities and features

  1. Validation: A "device" is validated when it operated according to its intended purpose or design, i.e. a power plug is able to connect to a socket that is also known to be compliant and passes electricity, both have been validated (it really works). CVP today includes platform specific validation (Functest functional tests):

  2. Performance - not currently implemented

Conformance vs compliance is not defined in CVP and previously was debated without conclusion. Recommend we avoid using "conformance" without first agreeing definition with LFN CVC.

Certification: CVP uses certification to describe the Tools and Process that allow test cases to run and results to be submitted to a repository for approval .

@michaelfix michaelfix self-assigned this Oct 10, 2019
@rabiabdel rabiabdel added this to the Snezka milestone Nov 5, 2019
@michaelfix
Copy link
Collaborator Author

@markshostak @rrajesh70 - can we close this issue?

@rabi-abdel rabi-abdel added this to To do in RM via automation Feb 6, 2020
@rabi-abdel rabi-abdel added RM and removed RM Com labels Feb 6, 2020
@rabi-abdel rabi-abdel removed this from the Snezka milestone Feb 11, 2020
@rabi-abdel rabi-abdel added this to the M3 (Freeze Contributions) milestone Feb 25, 2020
@kedmison
Copy link
Collaborator

kedmison commented Mar 5, 2020

As per issue #988 the cntt-gov decided to use conformance/conformant. RM changes made in PR #1208.

@kedmison kedmison closed this as completed Mar 5, 2020
RM automation moved this from To do to Done Mar 5, 2020
@rabi-abdel rabi-abdel added the Archive Archive Item label May 15, 2020
@project-bot project-bot bot moved this from Done to Achieve in RM May 15, 2020
@rabi-abdel rabi-abdel removed this from the M3 (Freeze Contributions) milestone May 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Archive Archive Item
Projects
RM
  
Achieve
Development

No branches or pull requests

5 participants