-
Notifications
You must be signed in to change notification settings - Fork 118
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
[Glossary] Terminology definition for testing per issue #1495 #1649
Conversation
Updates to say results may be useful for comparison
doc/tech/glossary.md
Outdated
|
||
- **Performance Measurement:** The procedure or set of operations having the object of determining a Measured Value or Measurement Result. In this context, Performance Measurements reflect data generated and collected within the cloud infrastructure, that reflects a performance aspect of the cloud infrastructure. For example, a count of frames or packets traversing an interface, memory usage information, other resource usage and availability, etc. These data may be instantaneous or accumulated, and made available (i.e. exposed) based on permissions and contexts (e.g., workload vs. infra). | ||
|
||
- **Performance Testing**: The main objective of CNTT performance testing is to understand if a potential BOM is functioning correctly to get expected performance. It requires a set of performance testing tools (open source) that help with the dimensioning of a solution by an operator. Testing results may be useful to compare infrastructure capabilites between the System Under Test (SUT) and a CNTT reference implementation of RA-2. Performance testing for the purpose of comparing between different commercial implementations is not a goal of CNTT. Performance testing relies on well established benchmark specifications. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This section should become an introduction for the Test Related Terminology Section, so I suggest to delete the text here and move under the section title.
- **Performance Testing**: The main objective of CNTT performance testing is to understand if a potential BOM is functioning correctly to get expected performance. It requires a set of performance testing tools (open source) that help with the dimensioning of a solution by an operator. Testing results may be useful to compare infrastructure capabilites between the System Under Test (SUT) and a CNTT reference implementation of RA-2. Performance testing for the purpose of comparing between different commercial implementations is not a goal of CNTT. Performance testing relies on well established benchmark specifications. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated per CVC
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@acmacm can this be resolved?
@trevgc would you mind please addressing comments above? |
Issue #1495 |
@xmulligan shall this PR be closed? |
@trevgc would you like to address the comments or should we close this PR pending further discussion in CNTT? |
fixes #1495 |
The discussion will be moved to https://wiki.lfnetworking.org/display/LN/Performance+Testing+Minutes until a formal PR will be raised |
1) Fixed TOC titles to march headings and updated numbering 2) Updated test terminology per CVC agreed definitions ref https://wiki.lfnetworking.org/display/LN/Performance+Testing+Minutes
Related
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@trevgc please resolve or remove Milestone=M3. If conflicts are resolved, also remove label=Conflict. thank you.
@trevgc do you want to resolve the conflicts here or should we close it? |
@xmulligan +1 to close it. We could reopen it later if needed. |
@xmulligan I just saw this and looked back at the history. The pull request was approved by 3 people, I am not sure what the conflict was that needed to be resolved? Lets not lose this as the glossary needs some improvements. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Subject to conflict resolution
@trevgc It states that there are conflicts and that will prevent merge |
@trevgc if you click on the resolve conflicts button, it will show what needs to be resolved |
Closed this pull request as it cannot be merged due to files moving around. Have replaced it with #2201 |
Added section 1.7 for test related terminology and updated with existing text in general terminology section this is test related and with definition text from related issue.