UEFI support for MAAS

Bug #1227749 reported by Kent Baxley
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Blake Rouse

Bug Description

We are starting see cases where servers are (or will be) shipping components that require UEFI boot (advanced format drives w/ native 4k drives, as an example. ).

Currently MAAS supports systems booting in non-UEFI (i.e. legacy bios) modes.

As the trend starts to shift to servers booting only in UEFI mode, we need to make sure that MAAS is ready and knows how to handle these sorts of scenarios.

I'm opening this as a tracking bug since work also needs to be done in Ubuntu Server itself to support basic EFI netbooting.

Tags: provisioning

Related branches

Changed in maas:
status: New → Triaged
importance: Undecided → High
tags: added: provisioning
Revision history for this message
Steve Langasek (vorlon) wrote :

> I'm opening this as a tracking bug since work also needs
> to be done in Ubuntu Server itself to support basic EFI
> netbooting.

We need to get the binary from shim 0.4-0ubuntu4 signed by Microsoft (there's an RT open for this right now), but otherwise this is entirely done for 13.10 already.

Changed in maas:
assignee: nobody → Blake Rouse (blake-rouse)
Changed in maas:
status: Triaged → In Progress
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
milestone: none → 14.04
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Kent, have you been able to test this please?

Revision history for this message
Kent Baxley (kentb) wrote : Re: [Bug 1227749] Re: UEFI support for MAAS

On Wednesday, April 9, 2014, Julian Edwards <email address hidden>
wrote:

> Kent, have you been able to test this please?

Not yet but I can try and have a system tested by tomorrow.

>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1227749
>
> Title:
> UEFI support for MAAS
>
> Status in MAAS:
> Fix Committed
>
> Bug description:
> We are starting see cases where servers are (or will be) shipping
> components that require UEFI boot (advanced format drives w/ native 4k
> drives, as an example. ).
>
> Currently MAAS supports systems booting in non-UEFI (i.e. legacy bios)
> modes.
>
> As the trend starts to shift to servers booting only in UEFI mode, we
> need to make sure that MAAS is ready and knows how to handle these
> sorts of scenarios.
>
> I'm opening this as a tracking bug since work also needs to be done in
> Ubuntu Server itself to support basic EFI netbooting.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1227749/+subscriptions
>

--
Kent Baxley
Field Engineer, Canonical
<email address hidden>

Revision history for this message
Kent Baxley (kentb) wrote :

Tested today on a PowerEdge R720 at Dell in EFI mode. The 720 is one of Dell's best-sellers so I figured it'd be a good candidate.

In the first attempt, I had to re-commission the machine a couple of times, but, upon closer examination I think I had some networking hiccups that prevented me from reaching archive.ubuntu.com. Not sure what was up with that, but, the archive was pretty slow overall today.

Once I finally got the machine to commission all the way, the installation of the OS via fastpath went very smooth.

I had to use fastpath since the d-i installer won't work right now due to the images and archives being out of sync.

Just to make sure I couldn't repeat the commissioning problems, I deleted the node from maas and started the process all over again. This time, enlisting and comissioning went without any problems. The fastpath install once again seemed to without a hitch and it looks as if the image does the right thing with regard to setting the disk up properly for EFI mode.

Nice work, guys, and thanks for getting this done!

Revision history for this message
Julian Edwards (julian-edwards) wrote :

Excellent, thanks for confirming Kent.

Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.