Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. What is the current (beta) version? Is there a release note for the current (beta) version?

    The current version is 0.78.0 for Dovetail, released on 910/2925. All dependent components (Docker containers) are listed here: 

    Yes, the release note documents all KNOWN ISSUES that should be reviewed before testing:

    Why does
  2. Why does the user guide outline ‘testsuite’ option argument in ‘dovetail run’ command that does not work?
    Convention ‘CVP‘OVP_1_0_0’ for ‘testsuite’ option, where versioning represents ‘<major>_<minor>_<patch>’ will be adopted in future releases. Please use ‘proposed_tests’  
    For current version opnfv/dovetail:cvp.0.8.0, please use ‘cvp.0.8.0’ as the argument for ‘testsuite’ during the beta.
    Suggest to not give testsuite when running tests, then dovetail will use the default one for each specify version.

  3. What image formats must the SUT compute nodes support?
    Images are submitted to the image service as qcow2, so compute services must support this format.

  4. Does direct result upload from test host to CVP OVP portal work?
    No, the user must first obtain the singular tar.gz file from test host and upload it through the CVP OVP portal.

  5. My tests were passing initially but are starting to fail without any configuration changes to the system under test. Why is this occurring?
    Dovetail creates many objects (images, networks, etc.) within the SUT public APIs during the course of testing. These objects are normally removed at the end of each test. However, there are scenarios where this fails to happen. For example, this can occur when a use kills the dovetail test while it is still running or when a dovetail console session drops during testing. Using Linux 'screen' to persist terminal sessions or avoiding killing (Ctrl-C) Dovetail during tests runs is encouraged to avoid this issue. Deletion of stale objects in the SUT admin services may also be necessary to remedy the failing tests.

...

ParticipantPlatformStatus
IntelLab environment with Pharos PODPlanned
ZTEOne OPNFV distrosPlanned
UNH-IOL3'rd Party LabProposed
NOKIAOne or more OPNFV distrosPlanned
BIIPharos POD1(fuel, danube3.0)

Planned

China Mobilelab environment with pharos podplanned
HuaweiOne or more OPNFV distros, if Possible, FusionSpherePlanned
CENGN3'rd Party LabProposed
Wind RiverTitanium Cloud R4 (Pharos POD 14)Planned
Ericssoninternal lab environment with OpenStack/OPNFV deploymentPlanned

Beta documentation

...

Beta release information