tree: abc84352633e9f7d3ca59f36e1a0fdcbd87faf3f [path history] [tgz]
  1. M00_maple_olt_tests.md
  2. M01_maple_olt_tests_activate_olt.md
  3. M02_maple_olt_tests_onos.md
  4. M03_maple_olt_eapol_auth.md
  5. M03_maple_olt_tests_eapol_auth.md
  6. M04_maple_olt_tests_verify_dhcp.md
  7. M04_maple_verify_dhcp.md
  8. M05_maple_olt_tests_unicast.md
  9. M05_maple_tests_unicast.md
  10. M06_maple_olt_tests_multicast.md
  11. M06_maple_tests_multicast.md
  12. M09_maple_olt_tests_verify_authentication.md
  13. M10_maple_olt_tests_verify_dhcp.md
  14. M11_maple_olt_tests_verify_unicast.md
  15. M12_maple_olt_tests_verify_multicast.md
  16. M13_maple_olt_tests_verify_cvid_upstream.md
  17. M14_maple_olt_tests_verify_cvid_downstream.md
  18. M15_maple_olt_tests_verify_qinq_upstream.md
  19. M16_maple_olt_tests_verify_qinq_downstream.md
  20. M17_maple_olt_tests_verify_ipv4_downstream.md
  21. M18_maple_olt_tests_verify_ipv4_downstream_case2.md
  22. M19_maple_olt_tests_ranging.md
  23. M20_maple_olt_tests_mib.md
  24. M21_maple_olt_tests_2000_byte_frames.md
  25. M22_maple_olt_tests_data_and_video.md
  26. M23_maple_olt_tests_overnight.md
  27. M24_maple_olt_tests_ha_fiber_disconnect.md
  28. M25_maple_olt_tests_ha_onu_reset.md
  29. M26_maple_olt_tests_ha_olt_reset.md
  30. M27_maple_olt_tests_ha_tor_switch_reset.md
  31. N00_netconf.md
  32. N01_netconf_bringup_deploy.md
  33. N02_netconf_client_connect.md
  34. N03_netconf_client_retrieve_YANG_modules.md
  35. N04_netconf_client_get_volthainstance.md
  36. N05_netconf_client_get_adapters.md
  37. P00_previews.md
  38. P01_previews_kpi_collection.md
  39. P02_previews_yang_and_netconf.md
  40. P03_previews_scale_out.md
  41. README.md
  42. S00_ponsim_tests.md
  43. S00_ponsim_tests_original.md
  44. S01_ponsim_tests_launch_and_activate.md
  45. S02_ponsim_tests_eapol_install.md
  46. S02_ponsim_tests_onos.md
  47. S03_ponsim_eapol_auth.md
  48. S03_ponsim_tests_eapol_in_out.md
  49. S04_ponsim_tests_install_all_flows.md
  50. S04_ponsim_verify_dhcp.md
  51. S05_ponsim_tests_unicast.md
  52. S06_ponsim_tests_multicast.md
  53. S07_ponsim_tests_verify_multicast.md
  54. T00_tibit_olt_tests.md
  55. T01_tibit_olt_tests_activate_olt.md
  56. T02_tibit_olt_tests_onos.md
  57. T03_tibit_olt_eapol_auth.md
  58. T04_tibit_verify_dhcp.md
  59. T05_tibit_tests_unicast.md
  60. T06_tibit_tests_multicast.md
  61. T09_tibit_olt_tests_verify_authentication.md
  62. T10_tibit_olt_tests_verify_dhcp.md
  63. T11_tibit_olt_tests_verify_unicast.md
  64. T12_tibit_olt_tests_verify_multicast.md
  65. T13_tibit_olt_tests_verify_cvid_upstream.md
  66. T14_tibit_olt_tests_verify_cvid_downstream.md
  67. T15_tibit_olt_tests_verify_qinq_upstream.md
  68. T16_tibit_olt_tests_verify_qinq_downstream.md
  69. T17_tibit_olt_tests_verify_ipv4_downstream.md
  70. T18_tibit_olt_tests_verify_ipv4_downstream_case2.md
  71. T19_tibit_olt_tests_ranging.md
  72. T20_tibit_olt_tests_mib.md
  73. T21_tibit_olt_tests_2000_byte_frames.md
  74. T22_tibit_olt_tests_data_and_video.md
  75. T23_tibit_olt_tests_overnight.md
  76. T24_tibit_olt_tests_ha_fiber_disconnect.md
  77. T25_tibit_olt_tests_ha_onu_reset.md
  78. T26_tibit_olt_tests_ha_olt_reset.md
  79. T27_tibit_olt_tests_ha_tor_switch_reset.md
  80. V00_voltha.md
  81. V00_voltha_bringup.md
  82. V01_voltha_bringup_deploy.md
  83. V02_voltha_bringup_rest.md
  84. V03_voltha_bringup_cli.md
  85. V04_voltha_bringup_async.md
  86. consul_sample_service_list.png
  87. netconf_connected.png
  88. netconf_download_schema.png
  89. netconf_get_adapters.png
  90. netconf_get_volthainstance.png
  91. netconf_load_module.png
  92. netconf_login_prompt.png
  93. netconf_modules_downloaded.png
  94. netconf_modules_loaded.png
  95. old/
  96. preparations.md
  97. requirements.md
  98. swagger_1.png
  99. swagger_2.png
  100. swagger_3.png
docs/manuals/user/labtests/README.md

Overview

Purpose

The purpose of this section is to assist in potential lab testing of Voltha and Voltha-certified PON hardware solutions.

Approach and Outline

Test exercises are currently grouped based on scope. Although a few tests require nothing more that a single Linux server, most tests require a hardware installation, a "test POD," available.

Specifically, we structure the test process as follows:

Recommended Test Method

Most of the activation steps desribed in the test procedure can be directly copy-pasted from the test document to the respecive test terminal window.

For best outcome, we recommend bringing up this test documentation on-line. There are two ways of doing that:

  1. In a PDF document viewer

  2. (Recommended) In a Web browser in gitbook reading mode. To do this, you need access to the HTML-compiled version of this gitbook document. You can easily do it on a Voltha development host, following these steps:

    cd $VOLTHA_BASE
    cd docs
    make serve
    

    This will build the documentation into an HTML dir structure and will start serving it up on the http://localhost:4000 URL.

    If you need remote access from the browser to the server where the doc is generated, Ctrl-C the make serve line, and instead do as follows:

    cd _book
    python -m SimpleHTTPServer.py 4000
    

    You shall now be able to reach the docs using the http://localhost:4000 URL.