Merge lp:~opnfv-team/maas-deployer/power8 into lp:~maas-deployers/maas-deployer/next
Proposed by
Narinder Gupta
Status: | Merged | ||||
---|---|---|---|---|---|
Merged at revision: | 65 | ||||
Proposed branch: | lp:~opnfv-team/maas-deployer/power8 | ||||
Merge into: | lp:~maas-deployers/maas-deployer/next | ||||
Diff against target: |
76 lines (+17/-5) 3 files modified
maas_deployer/vmaas/engine.py (+1/-1) maas_deployer/vmaas/templates/cloud-init.cfg (+3/-0) maas_deployer/vmaas/vm.py (+13/-4) |
||||
To merge this branch: | bzr merge lp:~opnfv-team/maas-deployer/power8 | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Narinder Gupta (community) | fixed | Approve | |
Billy Olsen | Needs Fixing | ||
Edward Hope-Morley | Pending | ||
Review via email:
|
Commit message
modified it to accommodate the review comments.
Description of the change
This patch is submitted from IBM power 8 and wants to merge this patch to enable MAAS deployer for IBM power 8 systems and VMs.
IBM is enabling opnfv JOID (Juju opnfv infratstruture deployer) with POWER 8 and this is first patch to enable the same. I think we are commenting one package in the patch but that is needed as that package does not exist for power8 system.
To post a comment you must log in.
Rather than simply commenting this out, I think we need to refactor this to pass the architecture through to the template that renders the cloud-init.cfg and handle it properly, rather than commenting it out which may risk breaking other arches, e.g.:
{% if not arch == 'power' -%} extra-virtual
- linux-image-
{% endif -%}