Age | Commit message (Collapse) | Author | Files | Lines |
|
JIRA: FUEL-171
Change-Id: Iead815ba2da76493f108ad71bc32cff265302b55
Signed-off-by: Michal Skalski <mskalski@mirantis.com>
(cherry picked from commit 53e6d97c9157f1e908d99dcca1207de23ea73132)
|
|
This NIC is used on Ericsson CI POD2
JIRA: KVMFORNFV-45
JIRA: FUEL-171
Change-Id: I44576b399b6195ccc1e64dfc0b04e239ced8acc7
Signed-off-by: Michal Skalski <mskalski@mirantis.com>
|
|
Move kernel installation to main phase of deployment which may reduce
problems with mcollective agent after node reboot.
JIRA: KVMFORNFV-45
JIRA: FUEL-171
Change-Id: I48308471f9336b73cde238ff055433f030395e19
Signed-off-by: Michal Skalski <mskalski@mirantis.com>
|
|
This version of kvmfornfv upstream fixed the issue of failing to launch
instances in Horizon after OPNFV environment deployed.
Change-Id: I05fa9f977924ee679312c599ee0bccabaf7bf1a9
Signed-off-by: davidjchou <david.j.chou@intel.com>
|
|
1. The installer function for kvmfornfv was in fuel-plug-qemu in
Brahmaputra release, it will be in this new fuel-plugin-kvm for
Colorado release for clarity
2. Deleted f_qemupluginbuild sub-directory
3. Two "# fix me" for "@sudo rm -rf kvmfornfv" instead of "@rm -rf
kvmfornfv" in Makefiel are the temp workgrounds for some files
generated during kvmfornfv building are owned by "root", will
remove these workarounds after resolving this issue in
fuel-plugin-kvm build process
Change-Id: I8a1e2dfaff692dc9813afb5d3bf038170871cade
Signed-off-by: davidjchou <david.j.chou@intel.com>
|