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/
Hello Divya and thanks for reaching out. We are very positive towards this kind of upstreaming effort, so your contributions to cloud-init will be very much welcome.
As you probably know already while we track bugs on Launchpad the actual development of cloud-init happens on GitHub [1]. The starting point for sending contributions upstream is the HACKING document [2], which also points to the contributor license agreement [3] that has to be signed by contributors for code inclusion.
I don't know what's the size of the code you plan submit for inclusion, but in general the more you are able to split it into functionally independent pull requests the better. Do not hesitate to file additional bugs if that helps tracking progress.
Thanks!
[1] https:/
[2] https:/
[3] https:/