summaryrefslogtreecommitdiffstats
path: root/build/f_isoroot/f_kvm-pluginbuild
AgeCommit message (Collapse)AuthorFilesLines
2017-03-20[kvm-plugin] Rename node_reboot taskMichael Polenchuk1-1/+1
Change-Id: I5251f209c74613d8b4683f1923166513762cd526 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com> (cherry picked from commit 5ef4fd12ed427658ea41efea280f03bc9e07a234)
2017-02-17[kvm-plugin] Employ dedicated reboot taskMichael Polenchuk1-1/+1
* Use native reboot task after kernel setup. * Make dkms modules to get source files of the kernel. JIRA: FUEL-256 Change-Id: I1dd75fa0425e5080fafa2de0ef13cccf0090c4c9 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2016-12-08Turn kvm-plugin back onMichael Polenchuk1-2/+2
Change-Id: I7c46f263ec584b09b6022d9e961ae3c44c642954 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2016-09-20[KVM] Install plugin in post-deploymentMichal Skalski1-2/+2
JIRA: FUEL-171 Change-Id: Iead815ba2da76493f108ad71bc32cff265302b55 Signed-off-by: Michal Skalski <mskalski@mirantis.com>
2016-08-24build: cache: Consider UBUNTU_ARCH in .cacheidAlexandru Avadanii1-0/+1
Usually UBUNTU_ARCH is not changed inside the same repository, but we should consider this case anyway for future merging Armband and Fuel@OPNFV repositories/build systems. This applies to all Fuel plugins and the local repo. Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-08-19Merge "Claenup"Michal Skalski1-4/+2
2016-08-19[KVM]Add support for Broadcom NetXtremeII 10GbMichal Skalski1-1/+1
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>
2016-08-18Claenupdavidjchou1-4/+2
Remove the workaround marked by "# fix me" mentioned in commit id: e8928f93b50df3ecb11942ab754bae848c082c6a, since the issue (some files generated during kvmfornfv building are owned by "root") already resolved in fuel-plugin-kvm build process. Change-Id: I5efb60173b9974f6fba25f04da1f4b1f53207b1a Signed-off-by: davidjchou <david.j.chou@intel.com>
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>