Merge lp://staging/~smoser/maas-images/trunk.lp1749019-re-add-cloud-intramfs-dyn-netconf into lp://staging/maas-images
| Status: | Merged | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Merged at revision: | not available | ||||||||
| Proposed branch: | lp://staging/~smoser/maas-images/trunk.lp1749019-re-add-cloud-intramfs-dyn-netconf | ||||||||
| Merge into: | lp://staging/maas-images | ||||||||
| Diff against target: | 0 lines | ||||||||
| To merge this branch: | bzr merge lp://staging/~smoser/maas-images/trunk.lp1749019-re-add-cloud-intramfs-dyn-netconf | ||||||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Andres Rodriguez (community) | Approve | ||
|
Review via email:
|
|||
Commit message
Re-add cloud-initramfs
The previous commit to trunk dropped cloud-initramfs
the maas image in releases newer than xenial.
That caused errors in MAAS. cloud-initramfs
a.) writes /run/network/
this is a ENI style file with data retrived from ipconfig
b.) convert 'BOOTIF' string in the value of IP
Example:
ip=
will be effectively rendered as:
ip=
'b' is still required by maas.
Note: in maas v3 images, the squashfs image is re-used pristine
from cloud-images. Because of this, the installation into the image
affects initramfs creation, but does not affect the image. That is
correct in that this package is not needed in the image but only
in the initramfs.
lgtm!