8. Requesting a Certificate

Once you’ve uploaded the data to the certification site, you should review it in the web interface. If you’re satisfied that there are no problems, you can request a certificate:

Important

Certificate requests must be based on the full test run submission, not ISO test submissions. In the case of additional device tests, a private certificate can be requested for the device based on the re-run submission results.

1. To view detailed results for a specific test run, click the date link under the Created column in the Submissions section. This will display a dedicated page with comprehensive information about that test run. Ensure that you have selected submissions for a full test run.

   In the submissions list page, you can use search keywords to filter the test run results. For example, to find all the test runs using the server-full test plan, specify testplan_id:"com.canonical.certification::server-full".

2. Click the Request Certificate link. The result should be a page with dropdown lists in which you can enter information:

   • Status can be set to:

     • Draft: The certificate request is in a draft state and will not be acted upon by Canonical. In this state, you can continue to make changes to the certificate request, such as linking additional submissions for re-tests.

     • Ready for Review: The certificate request is ready to be reviewed by Canonical. Notes may still be added, but additional submissions (for re-tests) may not be directly added to the certificate request. They may be linked as notes, but this practice is discouraged.

   • Certified Release indicates the Ubuntu release used for testing, and for which the certificate will be issued.

   • Level indicates the type of certification:

     • Certified is for for hardware that’s ready to be deployed with Ubuntu. This is the option to choose for server hardware as that typically does not ship with a pre-installed operating system.

     • Certified Pre-install is for hardware that ships with a (possibly customized) version of Ubuntu. This option is used almost exclusively for Client hardware such as desktops and laptops that typically ship with a pre-installed operating system.

   • Is Private should be checked if the certification should be kept private. Note that this check box affects the certificate only, not the entry for the computer as a whole on https://certification.canonical.com. Other public pre-existing certificates, or those issued in the future, will remain public.

3. Click Submit. You’ll see the certificate request screen in which you can enter more information. In particular, you can click:

   • Link Bug to link to a bug on https://bugs.launchpad.net. This option is available only to Canonical engineers.

   • Create Note and Add Note from Template enable you to create notes. You should create notes to document certain details and special circumstances, such as:

     • You should always create a note to link to the ISO test results.

     • If you made extra submissions to re-run any failed tests, create a note linking to those submissions.

     • If the node has special network devices that exist solely to link to the machine’s BMC, create a note to document this fact. Such devices will inevitably fail the network tests, and that failure, although acceptable, must be explained.

     In most cases, the “Private” check box should be checked for your notes.