Interface Type     

Virtual Test Head VTH

Underlying ProtocolTarget ReleaseCompletion StatusNote
O1O1 VTHNETCONFBronzecompletedused in O1 healthcheck
A1A1 VTHRESTful/HTTPSBronzecompletedused in A1 policy healthcheck
E1E1 VTHSCTP


F1F1 VTHSCTP


E2E2 VTHSCTPDawn

FHFH VTH

M-Plane is NETCONF, and CUS is SCTP




Asyn Msg Subscription

(DMaaP MR)

DMaaP_SUB VTH

HTTPSBronze
run in polling-mode. So it can be implemented as a reusable Task module

Asyn Msg Subscription

(VES)

VES_Collector VTHHTTPSBronze
run in server-mode

The VTH development is closely aligned with the SIM project. The message generators developed under SIM project will be mostly reused in VTH.

  • No labels

5 Comments

  1. 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). 

    1. Good point!  I added a VES VTH for genric purpose and it can be used by various test cases involving VES notification.

  2. Kevin Wan ,I am interested OTF and  have some quesitons about OTF, but I couldn't find your email address

    1. sure, kevin.wan@att.com

  3. 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