summaryrefslogtreecommitdiffstats
path: root/fuel-plugin/vagrant/Vagrantfile
AgeCommit message (Collapse)AuthorFilesLines
2017-06-22cleanup: remove fuel plugin since fuel@opnfv uses mcpGuo Ruijing1-24/+0
Change-Id: I5e0687008c53ee03973da5a3b58880b9b7c7de1c Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
2017-03-05Add disk to vagrant for fuel plugin buildGuo Ruijing1-0/+3
1. add 500G disk to vagrant 2. change build home to /mnt in guest 3. do some basic test Change-Id: If58db0322dc9f1c23a8e6ed065f876e34bea872f Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
2016-06-20Rebase fuel-plugin for kvmfornfv to fuel 9.0davidjchou1-1/+1
1. Uplifit fuel-plugin for kvmfornfv to fuel 9.0 due to that fuel 9.0 will be the deployment tool of OPNFV Colorado release. 2. Fixed quirk for kernel. 3. Added all tools and libs for building OVS module. 4. Allow KVM developer to build fuel-plugin-kvm after they modify the kerenl code without commiting their change into the repo first. So, they can test their code change by fuel-plugin-kvm till they satisfy with their change, then commit to the repo. 5. The final code built into OPNFV fuel iso will depend on the commit ID for kvmfornfv speicifed in fuel for OPNFV source tree. Change-Id: Iaf9ff49c69df374d0757884cfdac4cccee3eebe4 Signed-off-by: davidjchou <david.j.chou@intel.com>
2016-05-03Create fuel kvm pluginGuo Ruijing1-0/+21
Upstream status: NA In Brahmaputra release, KVM plugin functionality was bundled inside the fuel-plugin-qemu. In order for easy maintenance, the KVM plugin functionality would be separated from fuel-plugin-qemu and moved into an independent fuel-plugin-kvm and keep the source code here starting from Colorado release. Change-Id: Id89069234a4529cca40f1887e2d947378f928dd2 Signed-off-by: davidjchou <david.j.chou@intel.com> Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>