1、SONiC Community Hardware Testing LabBrian OConnor(Google)Guohan Lu(Microsoft)sonic-labsonicfoundation.dev OutlinePurpose of the LabInfrastructure OverviewSupported Testbed TopologiesTesting PlanAccess PolicyCall for ParticipationPurpose of the LabThe SONiC Community Hardware Testing Labis hosted and
2、 maintained by the University of New Hampshire Interoperability Lab(UNH-IOL)on behalf of and for the benefit of the SONiC Project.Purpose1.Serve as a community testbed for automated CI testingProvide visibility into quality of SONiC imagesValidate feature readiness on diverse array of platforms2.Pro
3、vide space for community troubleshooting and developmentEnable users from vendors,their partners,and their customers to collaborate on shared hardwareLab InfrastructureSpace for 10 testbeds2 racks,44RU&8kW availableCommon infrastructure includes:Management networkEnv serverVPNRemote PDUsCooling Phys
4、ical Testbed SetupDevice Under Test(DUT)Leaf Fanout/Control SwitchTest Server(optional)Testbeds are physically and logically isolated from each otherTwo identical SONiC switches are deployed in a common back-to-back topologySome flexibility exists for additional fanouts/servers,but they are isolated
5、 to a single testbedAll hardware(e.g.,switches and cables)is provided by the testbed vendorMgmtConsoleVMContainerService portNICUSBMgmt NetworkTestbed IsolationPhysical AccessUNH-IOL staff onlyNetwork SegregationLogical and Physical IsolationUnique VLAN for each testbeds management networkRouting Re
6、strictions No IP routing between VLANsRemotely connecting users(VPNs)are automatically allowed access only to their specific equipmentPDU AccessDUTs can be power cycled remotelyTestbed:Company ATestbed:Company BSupported Logical Testbed Topologiessonic-mgmt virtual topologies and testsE.g.,t0,t1,ptf