Metering/Bucket in this context is related to byte counting for billing purposes and not related to traffic policer or shaping. Metering is essential for billing the customers and below are the high-level requirements. *** 10 stages per ENI, prefix list can be optimized by tagging or other similar approach and reuse it for multiple ACLs/stages within the card thereby optimizing memory usageĭetailed scaling requirements can be found here 1.5 Metering requirements ** Support 10K peering in-region/cross-region This shall be limited to number of VNI hardware can support
#Sonic dash 3 software
* Number of VNET is a software limit as VNET by itself does not take hardware resources. TBD 1.4 Scaling requirementsįollowing are the minimal scaling requirements Item Warm-restart support is not considered in Phase 1.
User shall be able to show the DASH configured objects.Initial support is only for show and clear commands Eni, Vnic, VPort are used interchangeablyġ Requirements Overview 1.1 Functional requirementsĪt a high level the following should be supported:īringup SONiC image for DEVICE_METADATA subtype - Applianceīringup Swss/Syncd containers for switch_type - dpuĪble to program DASH objects configured via gRPC client to appliance card via SAI DASH API Definitions/Abbreviation Table 1: Abbreviations
General DASH HLD can be found at dash_hld. This document provides more detailed design of DASH APIs, DASH orchestration agent, Config and APP DB Schemas and other SONiC buildimage changes required to bring up SONiC image on an appliance card. Underlay Routing and ST/PL clarifications
SONiC-DASH HLD High Level Design Document Rev 1.1 Table of Contents
0 kommentar(er)
