Age | Commit message (Collapse) | Author | Files | Lines |
|
The vagrant-onap tool needs to be moved to its own repo to have better
control of versions and autonomy. This change removes the project from
integration repository.
Change-Id: I90bd4505a9fc7376c31a780aa1b833ee2663af3e
Signed-off-by: Victor Morales <victor.morales@intel.com>
Depends-On: I79df8c35fccaa266a789217d441a6cf1183bd42a
Issue-ID: INT-441
|
|
Signed-off-by: Manjeet Singh Bhatia<manjeet.s.bhatia@intel.com>
Issue-ID: INT-416
Change-Id: Idd88e2c4fed40cd082d467e9e96570334c09f491
|
|
The instructions to provision a ONAP Operations Manager environment
was included into the vagrant-onap tool. This script requires a
specific docker version besides some tasks that wait for certain
services.
Change-Id: I39f0b7947e7c87d8aa44ffa93cdb414d700379bd
Signed-off-by: Victor Morales <victor.morales@intel.com>
Co-Authored-By: Shashank Kumar Shankar <shashank.kumar.shankar@intel.com>
Issue-ID: INT-370
|
|
This patch removes the network adapter info for libvirt vagrant
provider, which was causing conflicts provisioning environments
with this provider.
Change-Id: Ib84a66227a96e4adbcf5febbe81ec5c15b83636b
Signed-off-by: Victor Morales <victor.morales@intel.com>
Issue-ID: INT-357
|
|
Apparently there are some issues in the way that VirtualBox is
installed in a Windows Host machine. This commit provides a workaround
for that.
Change-Id: Ia1142d2980ec9189e2a4ff982fa51e336fa6061b
Signed-off-by: Victor Morales <victor.morales@intel.com>
Issue-Id: INT-98
|
|
This patch adds the VNFSDK installation scripts and other
minor fixed in the Vagrant ONAP project.
Issue-Id: INT-290
Change-Id: I6402a1ffad4e373eb701945beabd5e95f091ff5b
Signed-off-by: Shashank Kumar Shankar <shashank.kumar.shankar@intel.com>
|
|
This patch adds documentation on example usages of
Vagrant ONAP.
Change-Id: I434d3b9f43d83d845c11627c10b00362ec4b1ea7
Issue-Id: INT-238
Signed-off-by: Shashank Kumar Shankar <shashank.kumar.shankar@intel.com>
|
|
In order to make more flexible the execution workflow of this
project, a new mechanism has been implemented to override the
default configuration values.
Change-Id: Ie6c5aeeb35b7f0de47379ea764ccc8dc21e4bff7
Signed-off-by: Victor Morales <victor.morales@intel.com>
Issue-Id: INT-236
|
|
It's possible to use these provisioning scripts to setup a
development environment without installing vagrant on it.
This commit specifies the steps and variables required for that
process.
Change-Id: Ica3e377f76b65c149d7ea7b805853b2e315e114c
Signed-off-by: Victor Morales <victor.morales@intel.com>
Issue-Id: INT-25
|
|
The known issues section should be placed in its own file for
future additions. It was also included a validation that
prevents the auto update feature of vagrant-vbguest plugin.
Change-Id: Ibdbd89c15b657b11b346c2cbcc084176f82d8102
Signed-off-by: Victor Morales <victor.morales@intel.com>
Issue-Id: INT-98
|
|
It was moved the information about to setup the usage of proxy
and the configuration of Vagrant default provider into the
setup installation guide.
Change-Id: I0f5c006ebd97346f05da06efdc6ef19555eef6d2
Issue-Id: INT-96
Signed-off-by: Victor Morales <victor.morales@intel.com>
|
|
It was added the process to create documentation thru sphinx tool.
Now it's possible to generate all the documentation locally running:
$ tox -e docs
Lastly, the installation guide was included as a reference to
different methods to install requirements.
Change-Id: Id0b277d605cf83ddbde54ecd9f4648e1f89023c3
Signed-off-by: Victor Morales <victor.morales@intel.com>
|
|
Given some internal procedures was not possible to submit all the
changes. In the meantime, those changes were placed into an
non-official project. This change syncronizes the latest changes
into the official repository.
Issue-id: INT-17
Change-Id: Ia4125f4b70273401e4ed3cc1908d2e2ad7d1c2e9
Signed-off-by: Victor Morales <victor.morales@intel.com>
|