Comment 24 for bug 1331214

Just to add my perspective and needs for this bug to be resolved. This issue currently gates certification on any system that uses AMT v9 . Bear in mind that without the MAAS requirements these systems would likely all pass hardware certification, so we're gating perfectly workable hardware because our provisioning system doesn't yet support ATM v9.

Newell's MP to MAAS that we worked on provides the necessary enablement to make AMT v9 work with maas for everything but in-band settings (creating a maas user and setting a maas password) which I'm not sure is possible at all in AMT anyway.

From a cert perspective, getting this merge reviewed and completed and packages built that include this enablement is pretty critical. FWIW, I don't need packages pushed into Trusty via Backports, just packages in either the Testing or Stable MAAS PPA will be sufficient for certification work.

One customer who ships servers based around AMT v9 has a test plan that has a deadline of March 16 to get two or three new AMT based servers certified for customer requirements.

I mentioned this this morning at the MAAS cross-team meeting, so I'm just adding notes here to preserve them in this bug.