yahoo-eng-team team mailing list archive

[Chad Smith <1895979@xxxxxxxxxxxxxxxxxx>]

This bug is believed to be fixed in cloud-init in version 20.4. If this
is still a problem for you, please make a comment and set the state back
to New

Thank you.

** Changed in: cloud-init
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1895979

Title:
  New cloud-init config modules for PowerVM Hypervisor based VMs

Status in cloud-init:
  Fix Released

Bug description:
  Linux Virtual Machines deployed (with ppcle architecture), using IBM
  PowerVM[1] Hypervisor on IBM Power System hosts, need an additional
  component (referred to as RMC - Remote Management Console) to be
  installed and successfully running on the VM. This RMC module/service
  must be installed and functioning on a ppcle VM, for the PowerVM
  Hypervisor to be able to communicate / manage these Virtual Machines.
  When a VM boots, there are some basic set of steps(generation of
  unique RMC node id; subsequent restart of the RMC service etc), that
  must be performed on a ppcle VM, to ensure that the communication of
  the VM and PowerVM Hypervisor is intact. RMC has to be active on the
  VM for the hypervisor to be able to perform many operations
  successfully. Thus a healthy RMC is a prerequisite for a PowerVM
  hypervisor based VM.

  To enable the healthy functioning of RMC services on ppcle Linux based
  VMs, there are couple of cloud-init config modules that we have been
  maintaining downstream. As part of this LP bug, we would like to
  upstream it, so that it benefits the larger community who is using
  PowerVM based VMs.

  References:
  [1] https://developer.ibm.com/depmodels/cloud/articles/cl-hypervisorcompare-powervm/

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1895979/+subscriptions