Interface Type | Virtual Test Head VTH | Underlying Protocol | Target Release | Completion Status | Note |
---|---|---|---|---|---|
O1 | O1 VTH | NETCONF | Bronze | completed | used in O1 healthcheck |
A1 | A1 VTH | RESTful/HTTPS | Bronze | completed | used in A1 policy healthcheck |
E1 | E1 VTH | SCTP | |||
F1 | F1 VTH | SCTP | |||
E2 | E2 VTH | SCTP | Dawn | ||
FH | FH VTH | M-Plane is NETCONF, and CUS is SCTP | |||
|
| ||||
|
The VTH development is closely aligned with the SIM project. The message generators developed under SIM project will be mostly reused in VTH.
5 Comments
Martin Skorupski
For O1 there could be a row added for VES messages (async notifications).
It might be useful for full end-to-end tests by OTF, adding a row for interfacing with the NBIs of SDN-R (RestConf).
Kevin Wan
Good point! I added a VES VTH for genric purpose and it can be used by various test cases involving VES notification.
Yan Yang
Kevin Wan ,I am interested OTF and have some quesitons about OTF, but I couldn't find your email address
Kevin Wan
sure, kevin.wan@att.com
Tünde Gáti
Hi Kevin,
Would you be so kind to help me about the actual status/plans about OTF and existing VTHs(O1:NetConf) and planned VTHs(O1:NetConf/YANG/CM, O1:VES/FM,CM,PM) compliance with the standards?
All the best,Tünde