Report: Remove DNV testbeds

[csit.git] / docs / report / introduction / methodology_autogen.rst

diff --git a/docs/report/introduction/methodology_autogen.rst b/docs/report/introduction/methodology_autogen.rst
index 1bf5e9e..5453775 100644 (file)
--- a/docs/report/introduction/methodology_autogen.rst
+++ b/docs/report/introduction/methodology_autogen.rst
@@ -23,7 +23,7 @@ The generated suites (and their contents) are affected by multiple information
 sources, listed below.
 
 Git Suites
 sources, listed below.
 
 Git Suites

-----------
+``````````

 
 The suites present in git repository act as templates for generating suites.
 One of autogen design principles is that any template suite should also act
 
 The suites present in git repository act as templates for generating suites.
 One of autogen design principles is that any template suite should also act


@@ -33,7 +33,7 @@ In practice, autogen always re-creates the template suite with exactly
 the same content, it is one of checks that autogen works correctly.
 
 Regenerate Script
 the same content, it is one of checks that autogen works correctly.
 
 Regenerate Script

------------------
+`````````````````

 
 Not all suites present in CSIT git repository act as template for autogen.
 The distinction is on per-directory level. Directories with
 
 Not all suites present in CSIT git repository act as template for autogen.
 The distinction is on per-directory level. Directories with


@@ -44,13 +44,13 @@ The script also specifies minimal frame size, indirectly, by specifying protocol
 (protocol "ip4" is the default, leading to 64B frame size).
 
 Constants
 (protocol "ip4" is the default, leading to 64B frame size).
 
 Constants

----------
+`````````

 
 Values in Constants.py are taken into consideration when generating suites.
 The values are mostly related to different NIC models and NIC drivers.
 
 Python Code
 
 Values in Constants.py are taken into consideration when generating suites.
 The values are mostly related to different NIC models and NIC drivers.
 
 Python Code

------------
+```````````

 
 Python code in resources/libraries/python/autogen contains several other
 information sources.
 
 Python code in resources/libraries/python/autogen contains several other
 information sources.


@@ -89,7 +89,7 @@ Some information sources are available in CSIT repository,
 but do not affect the suites generated by autogen.
 
 Testbeds
 but do not affect the suites generated by autogen.
 
 Testbeds

---------
+````````

 
 Overall, no information visible in topology yaml files is taken into account
 by autogen.
 
 Overall, no information visible in topology yaml files is taken into account
 by autogen.


@@ -121,7 +121,7 @@ Autogen does not care, as suites are agnostic.
 Robot tag marks the difference, but the link presence is not explicitly checked.
 
 Job specs
 Robot tag marks the difference, but the link presence is not explicitly checked.
 
 Job specs

----------
+`````````

 
 Information in job spec files depend on generated suites (not the other way).
 Autogen should generate more suites, as job spec is limited by time budget.
 
 Information in job spec files depend on generated suites (not the other way).
 Autogen should generate more suites, as job spec is limited by time budget.


@@ -129,7 +129,7 @@ More suites should be available for manually triggered verify jobs,
 so autogen covers that.
 
 Bootstrap Scripts
 so autogen covers that.
 
 Bootstrap Scripts

------------------
+`````````````````

 
 Historically, bootstrap scripts perform some logic,
 perhaps adding exclusion options to Robot invocation
 
 Historically, bootstrap scripts perform some logic,
 perhaps adding exclusion options to Robot invocation