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 is fixed at In Progress.

    • 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 a new 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 or Add Note from Template to create a note. Most systems will have at least two notes:

      • A note titled “Requester” with the name of the person who requested the certificate is required. This note should be created automatically, but you may optionally modify it.

      • A note titled “Test Notes” is usually present. It describes test-specific quirks, such as why a failure should be ignored (say, if a network test failed because of local network problems but succeeded on re-testing). If the miscellanea/get-maas-version test fails, be sure to specify the version of MAAS used to deploy the SUT.

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