Allow using separate storage pool for Vagrant-based minimal ONAP deployment

Vagrant-based minimal ONAP deployment requires at least 160GiB of
storage space. It is useful to be able to relocate Vagrant machines to
separate storage pools (e.g. on various storage devices).

Issue-ID: ONAPARC-551
Change-Id: I3f81c20f61264b958e121cf46f7b4354f04dc20c
Signed-off-by: Pawel Wieczorek <p.wieczorek2@samsung.com>

1 files changed, 10 insertions, 4 deletions

diff --git a/bootstrap/vagrant-minimal-onap/Vagrantfile b/bootstrap/vagrant-minimal-onap/Vagrantfile
index bd162431e..2bdee65e2 100644
--- a/bootstrap/vagrant-minimal-onap/Vagrantfile
+++ b/bootstrap/vagrant-minimal-onap/Vagrantfile
@@ -24,6 +24,7 @@ vm_cpus = 8
 vm_box = "generic/ubuntu1804"
 vm_disk = 32
 vm_disk_onap = 64
+vm_storage_pool = "default"
 
 operation = {
   name: 'operator',
@@ -31,7 +32,8 @@ operation = {
   ip: '172.17.4.254',
   cpus: vm_cpu,
   memory: vm_memory,
-  disk: vm_disk
+  disk: vm_disk,
+  pool: vm_storage_pool
 }
 devstack = {
   name: 'devstack',
@@ -39,7 +41,8 @@ devstack = {
   ip: '172.17.4.200',
   cpus: vm_cpu,
   memory: vm_memory_os,
-  disk: vm_disk
+  disk: vm_disk,
+  pool: vm_storage_pool
 }
 control = {
   name: 'control',
@@ -47,7 +50,8 @@ control = {
   ip: '172.17.4.100',
   cpus: vm_cpu,
   memory: vm_memory,
-  disk: vm_disk
+  disk: vm_disk,
+  pool: vm_storage_pool
 }
 worker = {
   name: 'worker',
@@ -55,7 +59,8 @@ worker = {
   ip: '172.17.4.101',
   cpus: vm_cpus,
   memory: vm_memory_onap,
-  disk: vm_disk_onap
+  disk: vm_disk_onap,
+  pool: vm_storage_pool
 }
 
 cluster = [] << control << worker
@@ -220,6 +225,7 @@ Vagrant.configure('2') do |config|
         v.memory = machine[:memory]
         v.cpus = machine[:cpus]
         v.machine_virtual_size = machine[:disk] # set at VM creation
+        v.storage_pool_name = machine[:pool]
       end
 
       config.vm.network :private_network, ip: machine[:ip]