Various improvements
- Refer to fabric-v1model.p4 in quickstart and mention the future plan
- Remove reference to private docker registry from deployment guide
- Update port ID in both netcfg and chassis config
- Remove private links from ignore list
- Update link to QoS config generator script
- Add link to SD-Fabric helm chart in PFCP configuration section
- Fix GitHub link anchor issue
Change-Id: I5272cb7363176d741a03145242a40db502d2fb24
diff --git a/configuration/network.rst b/configuration/network.rst
index 1ab1766..6f6d0d0 100644
--- a/configuration/network.rst
+++ b/configuration/network.rst
@@ -115,19 +115,9 @@
Before describing the ONOS netcfg, it is worth nothing how we refer to ports for
Tofino-based devices. Netcfg uses the format ``device:<name>/<port-number>``.
-``<port-number>`` is a special value that is usually different than the number
-shown in the switch front panel. It is the same number used for P4 table
-programming and depends on the specific Tofino ASIC SKU (e.g., dual-pipe vs.
-quad-pipe) and switch vendor/platform. In Stratum this is often referred to as
-the *SDK port ID*, as this is the number used for all Tofino SDK calls. In Intel
-documentation this is referred to as the ``DP_ID``. We plan to remove this
-dependency on such a low level detail in future releases, but for now, to find
-out the mapping between front-panel ports and ``DP_ID`` you have the following
-options:
-
-- Ask your switch vendor
-- Use the command `pm.show` on the BF shell of a running Stratum instance
- (see :ref:`troubleshooting_guide`)
+``<port-number>`` is a unique, arbitrary value that should be consistent
+with the ``id`` field defined in Stratum chassis config.
+See :ref:`singleton_port` for more details.
Bridging and Unicast Routing
----------------------------