Hey Viswa, I have to recognize that Vagrant is not easy to understand at the beginning (or at least that was my case). For that execution, apparently you have the proxy environment variables defined in your environment (http_proxy, https_proxy and no_proxy). We added a validation that installs an additional plugin for that scenario and stops the execution[1]. Once this plugin is installed you won’t have issues to run it again (basically, run `$ vagrant up sdnc`, we suggest to run only one service for now because we have been testing them in that way or run `$ DEPLOY_MODE=all-in-one vagrant up` that tries to install all the services in a single VM).
Regarding Vagrant, it uses snapshots (vagrant boxes) for its execution, more likely it will take some time to download the “ubuntu/trusty64” box[2] which is hosted in their cloud[3]. After that snapshot is downloaded and started a copy several customizations will be applied (like shared folders, amount memory, number of cpus, hostname, private ip, volume partitions, etc)[4][5] and a local script executed[6][7] passing arguments[8] and environment variables[9][10] [1] https://github.com/electrocucaracha/vagrant-onap/blob/master/Vagrantfile#L42-L50 [2] https://github.com/electrocucaracha/vagrant-onap/blob/master/Vagrantfile#L53 [3] https://atlas.hashicorp.com/ubuntu/boxes/trusty64 [4] https://github.com/electrocucaracha/vagrant-onap/blob/master/Vagrantfile#L55-L65 [5] https://github.com/electrocucaracha/vagrant-onap/blob/master/Vagrantfile#L184-L185 [6] https://github.com/electrocucaracha/vagrant-onap/blob/master/Vagrantfile#L187 [7] https://github.com/electrocucaracha/vagrant-onap/blob/master/postinstall.sh [8] https://github.com/electrocucaracha/vagrant-onap/blob/master/Vagrantfile#L188 [9] https://github.com/electrocucaracha/vagrant-onap/blob/master/Vagrantfile#L189 [10] https://github.com/electrocucaracha/vagrant-onap/blob/master/Vagrantfile#L4-L28 From: Viswa KSP <kspviswa.git...@gmail.com> Date: Thursday, June 15, 2017 at 4:37 PM To: Victor Morales <victor.mora...@intel.com> Cc: "Shankar, Shashank Kumar" <shashank.kumar.shan...@intel.com>, "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org> Subject: Re: [onap-discuss] Standardizing docker-maven-plugin, com.spotify or io.fabric8 Thanks for the heads-up Victor. I have been trying to use your project to bootstrap a dev environment, but haven't been succesfull. Could you please help me? I tried installing vagrant & git in brand new instance and here is what I get. PS : I'm completely new to vagrant and I might be asking something very obvious for hello-world. Pls bear with my stupidity :) kspviswa@kspviswa-onap-xlarge:~/ws/vagrant-onap$ vagrant up Installing the 'vagrant-proxyconf' plugin. This can take a few minutes... /usr/lib/ruby/2.3.0/rubygems/specification.rb:946:in `all=': undefined method `group_by' for nil:NilClass (NoMethodError) from /usr/lib/ruby/vendor_ruby/vagrant/bundler.rb:275:in `with_isolated_gem' from /usr/lib/ruby/vendor_ruby/vagrant/bundler.rb:231:in `internal_install' from /usr/lib/ruby/vendor_ruby/vagrant/bundler.rb:102:in `install' from /usr/lib/ruby/vendor_ruby/vagrant/plugin/manager.rb:62:in `block in install_plugin' from /usr/lib/ruby/vendor_ruby/vagrant/plugin/manager.rb:72:in `install_plugin' from /usr/share/vagrant/plugins/commands/plugin/action/install_gem.rb:37:in `call' from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call' from /usr/lib/ruby/vendor_ruby/vagrant/action/builder.rb:116:in `call' from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:66:in `block in run' from /usr/lib/ruby/vendor_ruby/vagrant/util/busy.rb:19:in `busy' from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:66:in `run' from /usr/share/vagrant/plugins/commands/plugin/command/base.rb:14:in `action' from /usr/share/vagrant/plugins/commands/plugin/command/install.rb:32:in `block in execute' from /usr/share/vagrant/plugins/commands/plugin/command/install.rb:31:in `each' from /usr/share/vagrant/plugins/commands/plugin/command/install.rb:31:in `execute' from /usr/share/vagrant/plugins/commands/plugin/command/root.rb:56:in `execute' from /usr/lib/ruby/vendor_ruby/vagrant/cli.rb:42:in `execute' from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:268:in `cli' from /usr/bin/vagrant:173:in `<main>' Installing the 'vagrant-proxyconf' plugin. This can take a few minutes... /usr/lib/ruby/2.3.0/rubygems/specification.rb:946:in `all=': undefined method `group_by' for nil:NilClass (NoMethodError) from /usr/lib/ruby/vendor_ruby/vagrant/bundler.rb:275:in `with_isolated_gem' from /usr/lib/ruby/vendor_ruby/vagrant/bundler.rb:231:in `internal_install' from /usr/lib/ruby/vendor_ruby/vagrant/bundler.rb:102:in `install' from /usr/lib/ruby/vendor_ruby/vagrant/plugin/manager.rb:62:in `block in install_plugin' from /usr/lib/ruby/vendor_ruby/vagrant/plugin/manager.rb:72:in `install_plugin' from /usr/share/vagrant/plugins/commands/plugin/action/install_gem.rb:37:in `call' from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call' from /usr/lib/ruby/vendor_ruby/vagrant/action/builder.rb:116:in `call' from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:66:in `block in run' from /usr/lib/ruby/vendor_ruby/vagrant/util/busy.rb:19:in `busy' from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:66:in `run' from /usr/share/vagrant/plugins/commands/plugin/command/base.rb:14:in `action' from /usr/share/vagrant/plugins/commands/plugin/command/install.rb:32:in `block in execute' from /usr/share/vagrant/plugins/commands/plugin/command/install.rb:31:in `each' from /usr/share/vagrant/plugins/commands/plugin/command/install.rb:31:in `execute' from /usr/share/vagrant/plugins/commands/plugin/command/root.rb:56:in `execute' from /usr/lib/ruby/vendor_ruby/vagrant/cli.rb:42:in `execute' from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:268:in `cli' from /usr/bin/vagrant:173:in `<main>' /home/kspviswa/ws/vagrant-onap/Vagrantfile:45:in `block in <top (required)>': vagrant-proxyconf was installed but it requires to execute again (RuntimeError) from /usr/lib/ruby/vendor_ruby/vagrant/config/v2/loader.rb:37:in `load' from /usr/lib/ruby/vendor_ruby/vagrant/config/loader.rb:113:in `block (2 levels) in load' from /usr/lib/ruby/vendor_ruby/vagrant/config/loader.rb:107:in `each' from /usr/lib/ruby/vendor_ruby/vagrant/config/loader.rb:107:in `block in load' from /usr/lib/ruby/vendor_ruby/vagrant/config/loader.rb:104:in `each' from /usr/lib/ruby/vendor_ruby/vagrant/config/loader.rb:104:in `load' from /usr/lib/ruby/vendor_ruby/vagrant/vagrantfile.rb:28:in `initialize' from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:706:in `new' from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:706:in `vagrantfile' from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:452:in `host' from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:179:in `block in action_runner' from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:33:in `run' from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:439:in `hook' from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:688:in `unload' from /usr/bin/vagrant:176:in `ensure in <main>' from /usr/bin/vagrant:176:in `<main>' kspviswa@kspviswa-onap-xlarge:~/ws/vagrant-onap$ ls BR, Viswa On Thu, Jun 15, 2017 at 11:07 PM, Morales, Victor <victor.mora...@intel.com<mailto:victor.mora...@intel.com>> wrote: Hi Viswa, Our main focus is to provide a method to provision a ONAP development environment. In other words, after running `vagrant up mso` or `vagrant up aai` the output should be a Virtual Machine with all the configuration and dependencies installed to be able to work in that particular module. Maybe something like a Devstack for ONAP. We believe that the capability to build docker images locally is crucial to any developer, no matter if they are behind a corporate proxy. Regarding running ONAP in a laptop, it should be nice to do it or a least only running their services. We have been testing this in our laptops which are MacBook Pro (2.7 GHz and 16 GB), hopefully that should be enough. Regards/Saludos Victor Morales irc: electrocucaracha From: <onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>> on behalf of Viswa KSP <kspviswa.git...@gmail.com<mailto:kspviswa.git...@gmail.com>> Date: Thursday, June 15, 2017 at 9:57 AM To: "Shankar, Shashank Kumar" <shashank.kumar.shan...@intel.com<mailto:shashank.kumar.shan...@intel.com>> Cc: "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] Standardizing docker-maven-plugin, com.spotify or io.fabric8 Hi Shashank / Victor, Great initiative. Does this vagrant aid only in docker builds or does it support deployment as well - something like ONAP in a laptop also possible ? Could you also comment on resource requirements ? BR, Viswa On Wed, Jun 14, 2017 at 12:06 AM, Shankar, Shashank Kumar <shashank.kumar.shan...@intel.com<mailto:shashank.kumar.shan...@intel.com>> wrote: Thank you very much for the details Manoop. Regards, Shashank From: "TALASILA, MANOOP (MANOOP)" <talas...@research.att.com<mailto:talas...@research.att.com>> Date: Tuesday, June 13, 2017 at 11:28 AM To: Shashank Kumar Shankar <shashank.kumar.shan...@intel.com<mailto:shashank.kumar.shan...@intel.com>> Cc: "ROSE, DANIEL V" <dr6...@att.com<mailto:dr6...@att.com>>, "Morales, Victor" <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] Standardizing docker-maven-plugin, com.spotify or io.fabric8 Hi Shashank, Portal’s Jenkin's jobs checkout the ecomp-sdk folder from “ecompsdkos<https://gerrit.onap.org/r/#/admin/projects/ecompsdkos>" repo. The same job executes the below shell script to build the portal container. I hope this helps. Here is the reference to one of the Portal’s Jenkins job: https://jenkins.onap.org/view/portal/job/portal-docker-master-merge-docker-script/configure Regards, Manoop Talasila AT&T Labs Research 1 AT&T Way, Bedminster, NJ 07921 ···························································· Office: +1 (908)901 2158 | e-mail: talas...@research.att.com<mailto:talas...@research.att.com> "This e-mail and any files transmitted with it are AT&T property, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other uses, retention, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited." On Jun 13, 2017, at 2:21 PM, Shankar, Shashank Kumar <shashank.kumar.shan...@intel.com<mailto:shashank.kumar.shan...@intel.com>> wrote: Hi Daniel, Thanks for the info. We also had another question regarding the local build of portal container. It looks like the os_build_febe.sh script in portal expects to have a directory named ecomp-sdk as seen in [1] in the root directory. But it seems like there is no directory named ecomp-sdk there [2]. Any idea from where the SDK folder gets created or is it left out? [1] - https://git.onap.org/portal/tree/deliveries/os_build_febe.sh#n33<https://urldefense.proofpoint.com/v2/url?u=https-3A__git.onap.org_portal_tree_deliveries_os-5Fbuild-5Ffebe.sh-23n33&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w&m=9kcWxXd3Er0kISsFneyOtJtqLNooDSp4TfmuEf61S7A&s=qVyH0UDP83xEA-JyL8BGB-XYx1nqqW9EnQtpqVJpOow&e=> [2] - https://git.onap.org/portal/tree/<https://urldefense.proofpoint.com/v2/url?u=https-3A__git.onap.org_portal_tree_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w&m=9kcWxXd3Er0kISsFneyOtJtqLNooDSp4TfmuEf61S7A&s=iLi3F8MdOB5Nz2G4ILfTJ1Hr6SXI9vV5xV-8hUJ9TNI&e=> Regards, Shashank From: <onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>> on behalf of "ROSE, DANIEL V" <dr6...@att.com<mailto:dr6...@att.com>> Date: Tuesday, June 13, 2017 at 7:26 AM To: "Morales, Victor" <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] Standardizing docker-maven-plugin, com.spotify or io.fabric8 We currently build docker images via scripts, via fabric8 plugin and via Spotify plugin. Spotify and fabric8 should be easier to merge, the script way may be harder. I leave it to others to decide if we should standardize ☺ Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308 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: Tuesday, June 13, 2017 10:23 AM To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: [onap-discuss] Standardizing docker-maven-plugin, com.spotify or io.fabric8 Howdy, Shashank and I started a vagrant project to collect the set of instructions to build ONAP Docker Images[1]. What we have found is that not all the projects are building their images in the same way. Even more, some of them uses different maven plugins, for example data-router that uses the Spotify plugin[2] and MSO uses Fabric8[3]. I’m not pretending to start a discussion about which is better but shouldn’t be better to keep one a standardize the method to build those images? Regards/Saludos Victor Morales irc: electrocucaracha [1] https://github.com/electrocucaracha/vagrant-onap/blob/master/lib/functions#L135-L154<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_electrocucaracha_vagrant-2Donap_blob_master_lib_functions-23L135-2DL154&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=RewA7K8yAmaw4CPli1rONNj1D50vCHLdbJloDLb2H6I&s=SpElGUuQgrGiChtxw93tMs9UlAu2PIllH6Ov9ouoh9k&e=> [2] https://git.onap.org/aai/data-router/tree/pom.xml#n161<https://urldefense.proofpoint.com/v2/url?u=https-3A__git.onap.org_aai_data-2Drouter_tree_pom.xml-23n161&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=RewA7K8yAmaw4CPli1rONNj1D50vCHLdbJloDLb2H6I&s=iBMmiHFxvUguNUqfwqqFIt9QLnY9vRvRwe2fN0KTOVE&e=> [3] https://git.onap.org/mso/tree/packages/docker/pom.xml#n101<https://urldefense.proofpoint.com/v2/url?u=https-3A__git.onap.org_mso_tree_packages_docker_pom.xml-23n101&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=RewA7K8yAmaw4CPli1rONNj1D50vCHLdbJloDLb2H6I&s=goOLaTLEbE3uwXebXnQqo1jBlnHoZu2jZmgdLdtHjWg&e=> _______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w&m=9kcWxXd3Er0kISsFneyOtJtqLNooDSp4TfmuEf61S7A&s=Bs8DM2osd1n6a8eNxViyupUMv8q9wv6ovYWq_cnhu_o&e= _______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> https://lists.onap.org/mailman/listinfo/onap-discuss
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
