Hi Carlos/Matt, Another thing to think about is the documentation of how/why the script/tool was run, sometimes the notes are more valuable than the results.
For example in the case where a vendor fails a pluggable inter-op due to a bug, that could easily be documented in the notes on the testing, if there is a workaround, that could also be mentioned. In the same example, as an end users I would like to know what cables to order and if the <insert vendor here> cables don't work with switch x, knowing that allows me to order cables that do work. > Carlos Cardenas <mailto:car...@cumulusnetworks.com> > July 14, 2015 at 11:05 AM > Hey Matt, > > Those are good points. > > For the first point, I think we can achieve that in the test plan. > Maybe another section or two? Are you thinking we should use "golden > NICs/servers" like OCP NICs and servers? > > Good logistical point on #2. Maybe a public github repo with all > scripts and configs? > > For #3, having some sort of "stock photos/videos" that not only the > lab could use, but each consortium member would be nice. thoughts? > > > > +--+ > Carlos > > > _______________________________________________ > opencompute-networking mailing list > Unsubscribe: > http://lists.opencompute.org/mailman/options/opencompute-networking > > opencompute-networking@lists.opencompute.org > http://lists.opencompute.org/mailman/listinfo/opencompute-networking > Matt Peterson <mailto:m...@peterson.org> > July 14, 2015 at 10:16 AM > Carlos, > > I would like to see3 specific items addressed in the proposal. > > * The first is presenting a clear "end-to-end" test scenario. While > the past two plugfests have been great for pluggables and NOS > vendors, I believe our ultimate end goal is certifying from NIC to > pluggable to chassis to NOS to L3 routing protocols and vice versa. > > * Second is full holding strong transparency & privacy - such as all > testing scripts, procedures, and configuration files will be made > publicly available. However in the case of a failed scenario, the > involved vendors would receive remediation time (say 2 months) to > re-test before results went public. For example, we've seen a few > NOS vendors not correctly program pluggable transceivers - usually > this is due to a NOS error of some sort, doesn't seem fair for a > pluggable vendor to be advertised as failing due to a NOS vendors > problem. > > * A clause or some wording around the use of press - generally > UNH-IOL events and activities have strict rules against any > participant from doing media capture (video, photos, etc). This > makes sense for a traditional consortium that may have pre-release > or pre-production equipment, however in the case of Open > Networking - many of the products are GA and existing mass market. > It seems incredibly important for us (under the OCP charter) to > continue education in the industry, presenting media is crucial to > this effort. Obviously members could opt out if requested, but > generally I'd like to see something a bit more flexible then > "request UNH-IOL staff to operate the camera, only group shots, no > close-ups" norm. This could be worded under the Public Relations > section. > > --Matt > > > _______________________________________________ > opencompute-networking mailing list > Unsubscribe: > http://lists.opencompute.org/mailman/options/opencompute-networking > > opencompute-networking@lists.opencompute.org > http://lists.opencompute.org/mailman/listinfo/opencompute-networking > Carlos Cardenas <mailto:car...@cumulusnetworks.com> > July 13, 2015 at 11:44 AM > Howdy, > > As a follow up to today's call on the Open Network Consortium Testing > section, the meeting minutes have been updated to reflect the link to > the Membership Proposal document (link here as well: > http://files.opencompute.org/oc/public.php?service=files&t=10b85b2c499f52fe77c3d75e89115759 > <http://files.opencompute.org/oc/public.php?service=files&t=10b85b2c499f52fe77c3d75e89115759>). > > For those that are interested, please review and provide feedback no > later than 31 July. > > Thanks. > > +--+ > Carlos > _______________________________________________ > opencompute-networking mailing list > Unsubscribe: > http://lists.opencompute.org/mailman/options/opencompute-networking > > opencompute-networking@lists.opencompute.org > http://lists.opencompute.org/mailman/listinfo/opencompute-networking
_______________________________________________ opencompute-networking mailing list Unsubscribe: http://lists.opencompute.org/mailman/options/opencompute-networking opencompute-networking@lists.opencompute.org http://lists.opencompute.org/mailman/listinfo/opencompute-networking
