VOL-4836 - Cosmetic edits to force a jenkins job.
Makefile
bandwidth-profiles/bandwidth-profiles.rst
-----------------------------------------
o Update document text to force trivial deltas.
o For readability: reformat runon command output to fit 80cpl.
howto/edit_voltha_docs.rst
--------------------------
o Copy in gendocs howto text from repo:infra-docs.
overview/troubleshooting.rst
----------------------------
o Update document text to force trivial deltas.
o Change variable delimiter syntax $()-makefile into ${}-shell since context is the command line.
o cat | grep command can be replaced by a single grep command to avoid the extra process.
testing/index.rst
-----------------
o Minor reformatting for readability.
o Include URLs for both voltha-system-test repository access: gerrit & github.
o Added a "See Also" section to hilight cord-* resources.
Change-Id: Ibf0881a6172abcb866f54dce57ce67a4c29b1bb1
diff --git a/bandwidth-profiles/bandwidth-profiles.rst b/bandwidth-profiles/bandwidth-profiles.rst
index fe78939..6fe7661 100644
--- a/bandwidth-profiles/bandwidth-profiles.rst
+++ b/bandwidth-profiles/bandwidth-profiles.rst
@@ -10,7 +10,7 @@
===========================================
The ONOS Sadis application supports configuration of the bandwidth profiles in two formats, `IETF` and `MEF`.
The values contained are expressed in kilobits/second (kbps).
-THe expectation is that a `Default` meter is always present for workflows that have flow rules installed at port
+The expectation is a `Default` meter will always present for workflows that have flow rules installed at port
startup, such as for EAPOL and DHCP. Meters referred by subscribers must also be present.
The `MEF` Brandwidth Profile format is as follows:
@@ -39,14 +39,18 @@
"gir": 0
}
-Independently of the format the `olt` ONOS apps will generate a meter per bandwidth profile.
+Independent of format the `olt` ONOS apps will generate a meter-per-bandwidth profile.
An example of a meter in ONOS is:
.. code:: bash
onos> meters
- DefaultMeter{device=of:00000a0a0a0a0a0a, cellId=1, appId=DefaultApplicationId{id=411, name=org.opencord.olt}, unit=KB_PER_SEC, isBurst=true, state=ADDED, bands=[DefaultBand{rate=600, burst-size=30, type=DROP, drop-precedence=null}, DefaultBand{rate=101000, burst-size=60, type=DROP, drop-precedence=null}, DefaultBand{rate=100000, burst-size=0, type=DROP, drop-precedence=null}], annotations={}}
+ DefaultMeter{device=of:00000a0a0a0a0a0a, cellId=1, appId=DefaultApplicationId{id=411, name=org.opencord.olt},
+ unit=KB_PER_SEC, isBurst=true, state=ADDED,
+ bands=[DefaultBand{rate=600, burst-size=30, type=DROP, drop-precedence=null},
+ DefaultBand{rate=101000, burst-size=60, type=DROP, drop-precedence=null},
+ DefaultBand{rate=100000, burst-size=0, type=DROP, drop-precedence=null}], annotations={}}
note the different bands that map to the values of the `Default` bandwidth profile as well.
The number of bands in the meter are based on the BW profile. If BW profile has only PIR value, then there is only
@@ -107,7 +111,9 @@
.. code:: bash
- ADDED, bytes=0, packets=0, table=0, priority=10000, selector=[IN_PORT:256, ETH_TYPE:eapol], treatment=[immediate=[OUTPUT:CONTROLLER, VLAN_PUSH:vlan, VLAN_ID:4091], meter=METER:1, metadata=METADATA:ffb004000000001/0]
+ ADDED, bytes=0, packets=0, table=0, priority=10000, selector=[IN_PORT:256, ETH_TYPE:eapol],
+ treatment=[immediate=[OUTPUT:CONTROLLER, VLAN_PUSH:vlan, VLAN_ID:4091], meter=METER:1,
+ metadata=METADATA:ffb004000000001/0]
TCONT Mapping