summaryrefslogtreecommitdiffstats
path: root/build/f_isoroot/f_kvm-pluginbuild
AgeCommit message (Collapse)AuthorFilesLines
2016-08-18Update kvm pluginMichal Skalski1-1/+1
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>
2016-07-20Update the commit ID of kvmfornfv upstream for fuel-plugin-kvmdavidjchou1-1/+1
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>
2016-06-29Move fuel plugin builder to DockerfileGuo Ruijing1-2/+0
Change-Id: I5c2bc9f4331bedd7a1d3e78ba2f9b82027e566ef Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
2016-06-28Add fuel-plugin-kvm to install kvmfornfvdavidjchou2-0/+107
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>