Re: [onap-discuss] [integration] [bootstrap] vagrant-onap project available into Integration repo
Thanks for this great explanation Erick, I double-checked to my computer and I
don’t have that plugin installed and it’s using Guest Additions Version:
4.3.36. So apparently this is an issue in the way that Vagrant masks mounted
directories, isn’t it? I only think about two possible alternatives for solving
this error
1. Ensuring that vagrant-vbguest is installed but disable its auto update
feature and report that to vagrant to solve that issue. The code into the
Vagrantfile should be something like:
if not Vagrant.has_plugin?('vagrant-vbguest')
system 'vagrant plugin install vagrant-vbguest'
raise 'vagrant-vbguest was installed but it requires to execute again'
end
config.vbguest.auto_update = false
2. Raise an error when the plugin is installed and force its uninstall
if Vagrant.has_plugin?('vagrant-vbguest')
system 'vagrant plugin uninstall vagrant-vbguest'
raise 'vagrant-vbguest was uninstalled but it requires to execute again'
end
I would be nice to have a way to restrict the Guest Additions Version,
Thanks
Victor Morales
From: "Multanen, Eric W" <eric.w.multa...@intel.com>
Date: Thursday, August 10, 2017 at 12:25 PM
To: Victor Morales <victor.mora...@intel.com>, "onap-discuss@lists.onap.org"
<onap-discuss@lists.onap.org>
Subject: RE: [onap-discuss] [integration] [bootstrap] vagrant-onap project
available into Integration repo
Here’s a summary of the issue and how I resolved / worked around it:
1. On the ‘vagrant up’, Guest Additions Version of the guest box is listed
as 4.3.36
2. My host virtual box version is 5.1.26
3. The vagrant-vbguest plugin was installed on the host, so it would mount
a newer version of the guest additions iso in the guest and install it (I
presume because it detected the older guest version).
a. The guest additions are installed in the guest /opt directory and then
links to /opt subdirectories are made for files and binaries in /sbin, etc. to
install.
4. Then, the host ./opt directory is mounted onto the guest /opt
directory. This succeeds - /opt on the guest is now shared with ./opt on the
host.
5. But, now the guest additions installed in /opt are masked by the
mounted ./opt directory from the host. Subsequent syncing (/lib, .m2, …) fails.
a. And the vagrant up fails at this point – the vm is up, but process of
bringing up mthe onap project fails
By uninstalling the vagrant-vbguest plugin on the host, a newer version of the
guest additions is not installed, so the masking of /opt in the guest does not
occur, all directories needing to sync are synced, and the bring up process is
able to continue.
From: Morales, Victor
Sent: Thursday, August 10, 2017 9:47 AM
To: Multanen, Eric W <eric.w.multa...@intel.com>; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [all] [integration] [bootstrap] vagrant-onap
project available into Integration repo
Hi Eric,
Adding more documentation is always welcome so if you find something that helps
to clarify the usage of this tool I encourage to submit the patch (I submitted
a patch to generate html documentation and it also includes an installation
guide[1]). For submitting a bug, I’d need more information about it, like
Do you the log of the error messages?
Did you only have issues syncing /opt folder? What about /lib and /.m2?
What version of Guest Additions did you have?
Once that you uninstall the guest additions, are the environments provisioned
without any error?
Thanks
Victor Morales
[1] https://gerrit.onap.org/r/#/c/7213/
From: "Multanen, Eric W"
<eric.w.multa...@intel.com<mailto:eric.w.multa...@intel.com>>
Date: Thursday, August 10, 2017 at 10:43 AM
To: Victor Morales <victor.mora...@intel.com<mailto:victor.mora...@intel.com>>,
"onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>"
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: RE: [onap-discuss] [all] [integration] [bootstrap] vagrant-onap
project available into Integration repo
Hello,
I’ve been trying this out (Windows 10 host, virtualbox, individual projects)
for the past couple weeks.
I ultimately found out that the source of the problems I encountered getting
synced folders/directories to work was a conflict between
the virtual box guest additions using the /opt directory of the guest and this
project syncing the /opt directory with the host. I got things to work
by uninstalling the vagrant guest additions plugin.
I’d be happy to either write up a bug report, or alternatively, add some
documentation for best known methods or tips on usage.
Any preference?
Eric
From:
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Morales, Victor
Sent: Wednesday, July 26, 2017 3:58 P
Re: [onap-discuss] [integration] [bootstrap] vagrant-onap project available into Integration repo
Here’s a summary of the issue and how I resolved / worked around it: 1. On the ‘vagrant up’, Guest Additions Version of the guest box is listed as 4.3.36 2. My host virtual box version is 5.1.26 3. The vagrant-vbguest plugin was installed on the host, so it would mount a newer version of the guest additions iso in the guest and install it (I presume because it detected the older guest version). a. The guest additions are installed in the guest /opt directory and then links to /opt subdirectories are made for files and binaries in /sbin, etc. to install. 4. Then, the host ./opt directory is mounted onto the guest /opt directory. This succeeds - /opt on the guest is now shared with ./opt on the host. 5. But, now the guest additions installed in /opt are masked by the mounted ./opt directory from the host. Subsequent syncing (/lib, .m2, …) fails. a. And the vagrant up fails at this point – the vm is up, but process of bringing up mthe onap project fails By uninstalling the vagrant-vbguest plugin on the host, a newer version of the guest additions is not installed, so the masking of /opt in the guest does not occur, all directories needing to sync are synced, and the bring up process is able to continue. From: Morales, Victor Sent: Thursday, August 10, 2017 9:47 AM To: Multanen, Eric W <eric.w.multa...@intel.com>; onap-discuss@lists.onap.org Subject: Re: [onap-discuss] [all] [integration] [bootstrap] vagrant-onap project available into Integration repo Hi Eric, Adding more documentation is always welcome so if you find something that helps to clarify the usage of this tool I encourage to submit the patch (I submitted a patch to generate html documentation and it also includes an installation guide[1]). For submitting a bug, I’d need more information about it, like Do you the log of the error messages? Did you only have issues syncing /opt folder? What about /lib and /.m2? What version of Guest Additions did you have? Once that you uninstall the guest additions, are the environments provisioned without any error? Thanks Victor Morales [1] https://gerrit.onap.org/r/#/c/7213/ From: "Multanen, Eric W" <eric.w.multa...@intel.com<mailto:eric.w.multa...@intel.com>> Date: Thursday, August 10, 2017 at 10:43 AM To: Victor Morales <victor.mora...@intel.com<mailto:victor.mora...@intel.com>>, "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>> Subject: RE: [onap-discuss] [all] [integration] [bootstrap] vagrant-onap project available into Integration repo Hello, I’ve been trying this out (Windows 10 host, virtualbox, individual projects) for the past couple weeks. I ultimately found out that the source of the problems I encountered getting synced folders/directories to work was a conflict between the virtual box guest additions using the /opt directory of the guest and this project syncing the /opt directory with the host. I got things to work by uninstalling the vagrant guest additions plugin. I’d be happy to either write up a bug report, or alternatively, add some documentation for best known methods or tips on usage. Any preference? Eric From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Morales, Victor Sent: Wednesday, July 26, 2017 3:58 PM To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: [onap-discuss] [all] [integration] [bootstrap] vagrant-onap project available into Integration repo ONAPers, The vagrant-onap project started as an alternative to deploy ONAP services in Virtual Machines hosted locally without the need of an OpenStack deployment. After several changes and additions to this project, its goal has changed to provision a Development Environment. Its current implementation support different providers (like VirtualBox, Libvirt and OpenStack) and has been tested in some OS(like Ubuntu, Mac OS). This is an ongoing effort to collect instructions and standardize the methods to build and compile ONAP artifacts, as you can expect there are many things that are still missed so I encourage to everyone to take a look of the scripts placed into lib folder[1] and improve the documentation[2][3]. We have plans to add more Unit Tests to this project[4] to validate any change. Thanks Victor Morales irc: electrocucaracha [1] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/lib [2] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/README.md [3] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/doc/source [4] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/tests ___ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
