Howdy, You bet there's a way for NOS vendors to self-verify prior to certification.
Take a look at: * https://github.com/opencomputeproject/onie/tree/master/contrib/autobuild#testing-a-nos * https://github.com/opencomputeproject/onie/wiki/NOS-Validation Keep in mind, a NOS vendor needs to use a box running ONIE 2015.05 as it contains a core facility needed (FTS Subsystem) by our tools. The main tool doing the heaving lifting is mtree. The 'Testing a NOS' link provides additional information on how to enable mtree to be built, along with how to run the 'test-nos.sh' script, and some platform differences between x86 and others when performing the tests. That's the plan, start with ONL and then move towards getting the commercial NOSes (Cumulus Linux, PicOS, Switch Light, etc...) validated/compliant. If anyone has some of these boxes available for testing, please contact me so we can arrange testing. +--+ Carlos On Sun, May 17, 2015 at 7:20 PM, Curt Brune <c...@cumulusnetworks.com> wrote: > Hello Carlos, > > On Thu May 14 11:26, Carlos Cardenas wrote: > > Howdy, > > > > As many of y'all might have seen yesterday one the ONIE mailing list, > ONIE > > 2015.05 was released ( > > > http://lists.opencompute.org/pipermail/opencompute-onie/2015-May/000631.html > ). > > This brings the number of publicly supported platforms to 32 and we > picked > > up another vendor: Centec. > > This is great to see the open networking community thriving and growing. > > > > > While this is a fine milestone in it's own right, I would like to focus > on > > one key nugget in this release: ONIE NOS Validation ( > > https://github.com/opencomputeproject/onie/wiki/NOS-Validation). > > > > Starting with release 2015.05, ONIE is now able to perform NOS Validation > > to ensure a given NOS complies with the ONIE Software Contract: > > * No modification to ONIE (files, partition layout, etc...) > > * The ability for a user to uninstall a NOS and install another NOS > > * The ability for a user to update ONIE after a NOS has been installed > > * The ability for a user to enter ONIE's rescue mode after a NOS has been > > installed > > * The ability for a user to install and uninstall a NOS and update ONIE > > when a Diagnostic Image is present on the device > > > > ONIE Compliance Testing has been focused on ensuring that hardware > vendors > > adhere to the ONIE spec, starting with this release, we have expanded it > to > > include NOS vendors as well ( > > > https://github.com/opencomputeproject/onie/wiki/Testing-and-Certification > ). > > Does this include a way for NOS vendors to perform a self test? That > would be great for NOS vendors to self-verify their implementations. > > We should also put ONL through the process, just to see what happens. > The more operating systems tested the better we can make the tests and > specifications. > > Cheers, > Curt >
_______________________________________________ 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
