My suggested plan forward would be:
 a.) promote the 14.04:ppc64el:hwe-v to released for ppc64el
     I will need someone to test that and suggest its reasonable
     That can be done by using the daily stream and doing an install to a
     system marked as 'generic/hwe-v'
 b.) remove 14.04:ppc64el:hwe-t product from both daily and released streams.
     This exploits maas bug http://pad.lv/1508975 , but should end up
     making even existing users to just start getting hwe-v kernels for
     enlistment, commissioning, and default install.
 c.) document this ppc64el specific behavior in some external facing place
     this should
  i. describe why hwe-t/3.13 is not available for ppc64el.
  ii. describe how to use linux-generic (3.13/hwe-t) in a maas
      installed VM if desired.  That looks something like:
      sudo apt-get install linux-generic # probably not necessary
      sudo apt-get --purge remove 
"linux-(image|headers)-(3.16.0|3.19.0|4.2.0)-.*"
      sudo apt-get autoremove
      sudo reboot
  iii. inform the user about hwe kernels and what their support path
      will be using their 'hwe-v', and subseqently hwe-w and then
      hwe-x kernels.
      probabably should point to [1]

I can do 'a' and 'b' above, but I suggest that 'c' should be done first.
I'm not sure what the appropriate place is for this documentation, and I'd be 
looking for Mike or Michael or Jeff to write it.

[1]
https://wiki.ubuntu.com/Kernel/LTSEnablementStack#Kernel.2BAC8-Support.A14.04.x_Ubuntu_Kernel_Support

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1508565

Title:
  maas uses 3.13 (hwe-t) kernel which does not work on non-virtual IBM
  power

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1508565/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Reply via email to