Merge remote-tracking branch 'upstream/main' into main

vijasrin · Apr 20, 2022 · 47f5e92 · 47f5e92
2 parents 83379b3 + 04185fc
commit 47f5e92
Show file tree

Hide file tree

Showing 3 changed files with 739 additions and 1 deletion.
diff --git a/documentation/general/design/sdn-features-packet-transforms.md b/documentation/general/design/sdn-features-packet-transforms.md
@@ -65,7 +65,7 @@ Why do we need this scenario?  There is a huge cost associated with establishing
 | Routes | 100k per v-port (max)  |
 | ACLs | 100k IP-Prefixes, 10k Src/Dst ports per v-port (max)  |
 | NAT | tbd  |
-| V-Port (aka ENI or Source VM) | 10k (max)  |
+| V-Port (aka ENI or Source VM) | 32 Primary, 32 Secondary assuming 2x OverSub, 32GB RAM, No ISSU, 10k (theorhetical max)  |
 | Mappings (VMS deployed) | 10 million total mapping per DPU; mappings are the objects that help us bridge the customer's virtual space (private ip address assigned to each VM) with Azure's physical space (physical/routable addresses where the VMs are hosted)  |
 |  | For each VPC, we have a list of mappings of the form: PrivateAddress -> (Physical Address v4, Physical Address V6, Mac Address, etc...) | VPC can have up to 1M mappings
 

diff --git a/documentation/gnmi/design/README.md b/documentation/gnmi/design/README.md
@@ -10,3 +10,4 @@ This folder contains DASH gNMI northbound API design and architecture documents.
 
 | Document                                               | Description                                |
 | ------------------------------------------------------ | ------------------------------------------ |
+| [Reference configuration example (JSON)](dash-reference-config-example.md) |Configuration schema example  |