Google Drive
Gist
Clipboard
or
or
By clicking below, you agree to our terms of service.
Sign in with Wallet
New to HackMD? Sign up
| Syntax | Example | Reference | |
|---|---|---|---|
| # Header | Header | 基本排版 | |
| - Unordered List |
|
||
| 1. Ordered List |
|
||
| - [ ] Todo List |
|
||
| > Blockquote | Blockquote |
||
| **Bold font** | Bold font | ||
| *Italics font* | Italics font | ||
| ~~Strikethrough~~ | |||
| 19^th^ | 19th | ||
| H~2~O | H2O | ||
| ++Inserted text++ | Inserted text | ||
| ==Marked text== | Marked text | ||
| [link text](https:// "title") | Link | ||
|  | Image | ||
| `Code` | Code |
在筆記中貼入程式碼 | |
| ```javascript var i = 0; ``` |
|
||
| :smile: |  |
Emoji list | |
| {%youtube youtube_id %} | Externals | ||
| $L^aT_eX$ | LaTeX | ||
| :::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Do you want to remove this version name and description?
Syncing
xxxxxxxxxx-
Any changes
Be notified of any changes
-
Mention me
Be notified of mention me
-
Unsubscribe
SubscribeETSI Plugtests
NFV API Conformance Results
During the Remote NFV&MEC API Plugtest 2021, Totally 136 API Conformance test sessions were executed for [NFV-SOL003] were executed as well as for [NFV-SOL005].
we had 2 contributions on the NFV Specifications and reported 22 issues on the Robot Test Suites as well as 5 bugs on Tacker.
By the end of September, all the issues reported to ETSI and Tacker in Feb. have been fixed. The latest results show that for VNF LifecycleManagement API, although the total number of test session increased,the pass rate increased from 71.62% to 85.06%. Also for the VNF Package Management API, the pass rate increased from 58.18% to 90.91%.
Results between Feb. and Oct.
VNF LifecycleManagement API
VNF Package Management API
Test Results in Detail (Feb.)
The following clauses provide tables and figures which summarize the results for the NFV API Conformance test for the different APIs
NFV-SOL003
NFV-SOL005
VNF LifecycleManagement API
The table and figures below summarize the results for VNFLifecycleManagement API per test session for [NFV-SOL003].
VNF Package Management API
The table and figures below summarize the results for VNF Package Management API API per test session for [NFV-SOL003] and [NFV-SOL005] .
NFV-SOL003
NFV-SOL005
Test Results in Detail (Oct.)
The following clauses provide tables and figures which summarize the latest results for the NFV API Conformance test for the different APIs
NFV-SOL003
NFV-SOL005
VNF LifecycleManagement API
The table and figures below summarize the results for VNFLifecycleManagement API per test session for [NFV-SOL003].
VNF Package Management API
The table and figures below summarize the results for VNF Package Management API API per test session for [NFV-SOL003] and [NFV-SOL005] .
Plugtest Outcome
The following clauses shows the detaild of feedback on NFV Specifications and the issues we reported both on Robot Test Suite and Tacker.
Feedback on NFV Specifications
Potential inconsistency on disk and container format
A retrieved inconsistency among the NFV-SOL specifications has been identified related to the definition of disk and
container format permitted values in the VnfPackageSoftwareImageInfo data type in [NFV-SOL003] and [NFVSOL005]. In particular, [NFV-SOL005] in Table 9.5.3.2-1 (and the same in [NFV-SOL003] Table 10.5.3.2-1) specifies.the permitted values disk and container format attributes as all uppercase
However, two notes in the [NFV-SOL005] Table 9.5.3.2-1 (and the same in [NFV-SOL003] Table 10.5.3.2-1) state that the list of permitted values was taken from “Container formats” and “Disk Formats” defined by Openstack in:https://docs.openstack.org/glance/pike/user/formats.html
In these Openstack reference definitions, the disk and container format permitted values are defined as all lowercase, so not aligned with [NFV-SOL005] Table 9.5.3.2-1 and [NFV-SOL003] Table 10.5.3.2-1 specifications.
Issue 8008 has been reported to NFV SOL Working Group to notify this potential inconsistency.
Usability issue on hardcoded authorization header name
From the specification perspective, the [NFV-SOL013] specifies the header name for authorization to be required, this being the name “Authorization”. However, as part of OpenStack, Tacker use the header "X-Auth-Token" which avoiding us to run the NFV API Conformance tests at all
in order to achieve conformance to the specifications, Tacker shall work to allow their products and implementation to utilize the standard authorization header name ( i.e. “Authorization”).
Feedback on the NFV Robot Test Suite
The issues we reported during the tests are as followed.
Feedback on Tacker
The bugs we reported during the tests are as followed.