<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Certification on Deevnet IoTaaS</title><link>https://deevnet.github.io/deevnet-docs/docs/policies/lifecycle-management/certification/</link><description>Recent content in Certification on Deevnet IoTaaS</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://deevnet.github.io/deevnet-docs/docs/policies/lifecycle-management/certification/index.xml" rel="self" type="application/rss+xml"/><item><title>Hardware Certification</title><link>https://deevnet.github.io/deevnet-docs/docs/policies/lifecycle-management/certification/hardware-certification/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deevnet.github.io/deevnet-docs/docs/policies/lifecycle-management/certification/hardware-certification/</guid><description>&lt;h1 id="hardware-certification">
 Hardware Certification
 &lt;a class="anchor" href="#hardware-certification">#&lt;/a>
&lt;/h1>
&lt;p>How a model of hardware is certified for a role. The records are under

 &lt;a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/platforms/certification/hardware/">Certification → Hardware&lt;/a>.&lt;/p>
&lt;hr>
&lt;h2 id="what-is-certified">
 What is certified
 &lt;a class="anchor" href="#what-is-certified">#&lt;/a>
&lt;/h2>
&lt;p>A &lt;strong>model at a hardware revision, for a role&lt;/strong>. The same model in a different role, or at a different
hardware revision, is a separate certification. Hardware revisions do change what a board carries,
such as the NIC chipset.&lt;/p>
&lt;p>It is evaluated &lt;strong>with the software it will run&lt;/strong>: the OS and driver are part of what is tested,
because a NIC&amp;rsquo;s maturity depends on the driver. The record names the software it was tested with.
That software&amp;rsquo;s own certification is separate (
 &lt;a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/policies/lifecycle-management/certification/software-certification/">Software Certification&lt;/a>).&lt;/p></description></item><item><title>Software Certification</title><link>https://deevnet.github.io/deevnet-docs/docs/policies/lifecycle-management/certification/software-certification/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deevnet.github.io/deevnet-docs/docs/policies/lifecycle-management/certification/software-certification/</guid><description>&lt;h1 id="software-certification">
 Software Certification
 &lt;a class="anchor" href="#software-certification">#&lt;/a>
&lt;/h1>
&lt;p>How a release line of a product is certified for a role. The records are under

 &lt;a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/platforms/certification/software/">Certification → Software&lt;/a>.&lt;/p>
&lt;hr>
&lt;h2 id="what-is-certified">
 What is certified
 &lt;a class="anchor" href="#what-is-certified">#&lt;/a>
&lt;/h2>
&lt;p>A &lt;strong>release line of a product, for a role&lt;/strong>: OPNsense 26.7 as the core router, Proxmox VE 9 as a
hypervisor, Grafana 13 as the tenant dashboards. Device firmware is software, and is certified the
same way.&lt;/p>
&lt;p>&lt;strong>A line, not a version.&lt;/strong> Patch releases inherit the line&amp;rsquo;s certification. Before a patch is
applied, its release notes are read. If they change something a criterion depends on, the patch is
re-checked against that criterion, and the result is a dated addendum on the line&amp;rsquo;s record.
A new line is a new revision.&lt;/p></description></item><item><title>Certification Record Template</title><link>https://deevnet.github.io/deevnet-docs/docs/policies/lifecycle-management/certification/certification-record-template/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deevnet.github.io/deevnet-docs/docs/policies/lifecycle-management/certification/certification-record-template/</guid><description>&lt;h1 id="certification-record-template">
 Certification Record Template
 &lt;a class="anchor" href="#certification-record-template">#&lt;/a>
&lt;/h1>
&lt;p>The shape of a certification: one &lt;strong>item page&lt;/strong> per model or product, and one &lt;strong>revision page&lt;/strong>
per evaluation beneath it. Copy the skeletons below.&lt;/p>
&lt;hr>
&lt;h2 id="where-it-goes">
 Where it goes
 &lt;a class="anchor" href="#where-it-goes">#&lt;/a>
&lt;/h2>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>&lt;/th>
 &lt;th>Hardware&lt;/th>
 &lt;th>Software&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>&lt;strong>Item&lt;/strong>&lt;/td>
 &lt;td>&lt;code>content/docs/platforms/certification/hardware/&amp;lt;layer&amp;gt;/&amp;lt;model&amp;gt;/_index.md&lt;/code>&lt;/td>
 &lt;td>&lt;code>content/docs/platforms/certification/software/&amp;lt;layer&amp;gt;/&amp;lt;product&amp;gt;/_index.md&lt;/code>&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Revision&lt;/strong>&lt;/td>
 &lt;td>&lt;code>…/&amp;lt;model&amp;gt;/&amp;lt;YYYY-MM&amp;gt;-hw-&amp;lt;revision&amp;gt;.md&lt;/code>, e.g. &lt;code>2026-10-hw-1-20.md&lt;/code>&lt;/td>
 &lt;td>&lt;code>…/&amp;lt;product&amp;gt;/&amp;lt;line&amp;gt;.md&lt;/code>, e.g. &lt;code>26-7.md&lt;/code>&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Layer&lt;/strong>&lt;/td>
 &lt;td>&lt;code>network&lt;/code>, &lt;code>management-plane&lt;/code> or &lt;code>tenant-compute&lt;/code>, as on 
 &lt;a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/platforms/">Implementation &amp;amp; Tooling&lt;/a>&lt;/td>
 &lt;td>the same, or &lt;code>tooling&lt;/code> for build and automation tools&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Item title&lt;/strong>&lt;/td>
 &lt;td>The model, e.g. &amp;ldquo;TP-Link SG2218&amp;rdquo;&lt;/td>
 &lt;td>The product, e.g. &amp;ldquo;OPNsense&amp;rdquo;&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Revision title&lt;/strong>&lt;/td>
 &lt;td>&amp;ldquo;2026-10 · hardware 1.20&amp;rdquo;&lt;/td>
 &lt;td>&amp;ldquo;26.7&amp;rdquo;&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Weight&lt;/strong>&lt;/td>
 &lt;td>The first revision is &lt;code>1000&lt;/code>, and each new one is one lower, so the newest sorts first&lt;/td>
 &lt;td>the same&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Index&lt;/strong>&lt;/td>
 &lt;td>Add the item to its layer page, and to 
 &lt;a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/platforms/certification/">Certification&lt;/a>&lt;/td>
 &lt;td>the same&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;p>Add &lt;code>bookCollapseSection: true&lt;/code> to every item page, so its revisions stay folded in the sidebar.&lt;/p></description></item></channel></rss>