Code Review / integration.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 645712f) | patch
Allow using separate storage pool for Vagrant-based minimal ONAP deployment 61/108961/2
authorPawel Wieczorek <p.wieczorek2@samsung.com>
Mon, 8 Jun 2020 14:39:56 +0000 (16:39 +0200)
committerPawel Wieczorek <p.wieczorek2@samsung.com>
Fri, 12 Jun 2020 05:24:29 +0000 (07:24 +0200)
commit0f46da66af49c177254ac75ba552ccdb7cb467fd
treeab748263b8f642c0e913e600255901f06b8d5ca8tree | snapshot
parent645712f578c93cb2596e629a9828e0379caad0b2commit | diff
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>
bootstrap/vagrant-minimal-onap/Vagrantfile diff | blob | history
Integration framework, automated tools, code and scripts, best practice guidance related to cross-project Continuous System Integration Testing (CSIT), and delivery of ONAP.