Right. If you don’t use vagrant, there is small env diff like software version, IP address so that you need to modify the script.
If you use socks5 proxy instead of http-proxy, you can use script from following to avoid editing dockerfile: 1. git clone http://gerrit.onap.org/gerrit/r/demo 2. demo/vagrant/setup_proxy.sh (can setup proxy for all applications) I just go through policy tutorial: https://wiki.onap.org/display/DW/Deploying+and+Debugging+the+Policy+Platform I can update policy by followings (not in tutorial): 1. sudo docker exec -ti pdp bash 2. cd /tmp/policy-install/config 3. bash ./push-policies.sh From: viswanath.kumarskandpr...@verizon.com [mailto:viswanath.kumarskandpr...@verizon.com] Sent: Wednesday, August 16, 2017 9:54 PM To: Guo, Ruijing <ruijing....@intel.com>; 'DRAGOSH, PAMELA L (PAM)' <pdrag...@research.att.com>; Atul Shegokar <as00500...@techmahindra.com> Cc: onap-discuss@lists.onap.org Subject: Re: [onap-discuss] Facing issues with policy setup with Vagrant Thanks Ruijing. I had to do minor changes in your script to have it run in my environment.. * For some reason docker-compose via pip install didn't work. So used docker-compose binary directly ( sudo * curl -o /usr/local/bin/docker-compose -L "https://github.com/docker/compose/releases/download/1.15.0/docker-compose-$(uname * -s)-$(uname -m)") * Patched settings.xml to work through corporate proxy * Added switches in between script to pause & wait for my action to proceed. * I had to manually edit each Dockerfile to add proxy configurations in /etc/apt/apt.conf as well. Simply exporting HTTP_PROXY didn't help in my case. With above modifications, I was able to be see them running now. I had to manually do the stuffs in for loop to make it work in my env ( mainly due to corporate proxy :( ). BTW after having all these dockers up, how am I supposed to use Policy GUI to create / edit / apply any policy? Could you help me with this info? BR, Viswa ________________________________ From: Guo, Ruijing <ruijing....@intel.com<mailto:ruijing....@intel.com>> Sent: Wednesday, August 16, 2017 6:14 PM To: Kumar Skand Priya, Viswanath V; 'DRAGOSH, PAMELA L (PAM)'; Atul Shegokar Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: [E] RE: [onap-discuss] Facing issues with policy setup with Vagrant Hi, Vagrant/virtualbox need virtualization support. you can setup policy from Ubuntu 16.04 VM/Bare Metal without vagrant/virtualbox: 1. Setup sudo without password in Ubuntu 16.04 VM/Bare Metal 2. Git clone http://gerrit.onap.org/r/policy/docker<https://urldefense.proofpoint.com/v2/url?u=http-3A__gerrit.onap.org_r_policy_docker&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=9F3pNUkzjE-2v1eTClkRVe_0_NKUnq80ofq4I8oRnFqsXZpLuCtlULKYzwU3QsHo&m=BiwgktBu2WkubfpvjJxIuU1GCvi2_M1MwN6TFyoa3XA&s=TetPhmjR4niPWqebxddSDtclVbO-TOPy54Li-WLgEM4&e=> 3. Patch from https://gerrit.onap.org/r/#/c/7719/<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_7719_&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=9F3pNUkzjE-2v1eTClkRVe_0_NKUnq80ofq4I8oRnFqsXZpLuCtlULKYzwU3QsHo&m=BiwgktBu2WkubfpvjJxIuU1GCvi2_M1MwN6TFyoa3XA&s=lgXD2jk_YK8u0rVjnid9236EzHyzHEXQGpU9tM7uH2c&e=> (still in review) 4. Change 192.168.0.10 in docker/vagrant/setup_policy.sh to interface IP address in your Ubuntu 16.04 VM/Bare Metal 5. Run setup_policy.sh I will remove hardcoded IP address. So you can just run setup_policy.sh Thanks, -Ruijing From: viswanath.kumarskandpr...@verizon.com<mailto:viswanath.kumarskandpr...@verizon.com> [mailto:viswanath.kumarskandpr...@verizon.com] Sent: Wednesday, August 16, 2017 7:52 PM To: 'DRAGOSH, PAMELA L (PAM)' <pdrag...@research.att.com<mailto:pdrag...@research.att.com>>; Atul Shegokar <as00500...@techmahindra.com<mailto:as00500...@techmahindra.com>>; Guo, Ruijing <ruijing....@intel.com<mailto:ruijing....@intel.com>> Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: RE: [onap-discuss] Facing issues with policy setup with Vagrant I’m also facing similar issue. Although, going through Google, I learnt that nested virtualization is not supported. Apparently, I’m running a Ubuntu VM in openstack and I’m trying to use vagrant to power-up V-Box inside that Ubuntu. Is there any much simpler approach to bring up entire policy component in single VM? The READ.ME from http://gerrit.onap.org/r/policy/docker<https://urldefense.proofpoint.com/v2/url?u=http-3A__gerrit.onap.org_r_policy_docker&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=9F3pNUkzjE-2v1eTClkRVe_0_NKUnq80ofq4I8oRnFqsXZpLuCtlULKYzwU3QsHo&m=BiwgktBu2WkubfpvjJxIuU1GCvi2_M1MwN6TFyoa3XA&s=TetPhmjR4niPWqebxddSDtclVbO-TOPy54Li-WLgEM4&e=> suggest to build individual mvn projects starting from “policy-common-modules”, but I couldn’t see that dir in my cloned repo. Also, https://wiki.onap.org/pages/viewpage.action?pageId=11929334<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D11929334&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=9F3pNUkzjE-2v1eTClkRVe_0_NKUnq80ofq4I8oRnFqsXZpLuCtlULKYzwU3QsHo&m=BiwgktBu2WkubfpvjJxIuU1GCvi2_M1MwN6TFyoa3XA&s=5QAuS_rIKSRqad7jQYGRLIkYxQf7g7EiLKL0Wp1vgtQ&e=> page explains about building PDP but not entire policy component. Could you somebody from policy team shed some light on development env setup? BR, Viswa From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of DRAGOSH, PAMELA L (PAM) Sent: Wednesday, August 16, 2017 5:13 PM To: Atul Shegokar <as00500...@techmahindra.com<mailto:as00500...@techmahindra.com>>; ruijing....@intel.com<mailto:ruijing....@intel.com> Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: [E] Re: [onap-discuss] Facing issues with policy setup with Vagrant Atul, Sorry that you are having issues. I don’t know what those errors are or where they come from. Perhaps Ruijing could help you, he setup the vagrant for Policy. Not sure if you saw this wiki or if it would help: https://wiki.onap.org/pages/viewpage.action?pageId=11930786<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D11930786&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=9F3pNUkzjE-2v1eTClkRVe_0_NKUnq80ofq4I8oRnFqsXZpLuCtlULKYzwU3QsHo&m=AOFrZt9XLFVYKw8kegDMurnoKluXMlwzETmPN4Ujmnw&s=zKoYP3cS-nwxQ6wKy0SzYG3OpBVBfFlduSzCMTfdeNY&e=> Regards, Pam From: <onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>> on behalf of Atul Shegokar <as00500...@techmahindra.com<mailto:as00500...@techmahindra.com>> Date: Wednesday, August 16, 2017 at 4:31 AM To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>> Subject: [onap-discuss] Facing issues with policy setup with Vagrant HI team, I am trying to make setup for policy using vagrant. When I try to use vagrant up command, it gives an error saying VT-x is not available (VERR_VMX_NO_VMX). I have already made below checks – 1) VT-x AMD-V rea active in VM. 2) VT-x is enabled in BIOS. 3) Hyper-V is disabled and system rebooted (it was checked earlier). Please guide help, if there are any other possible reasons which are affecting vagrant up command working. Thanks & Regards, Atul Shegokar ============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.techmahindra.com_Disclaimer.html&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4&m=ET5R9r4L8F5Imk4CVr4NbR9OTOvYMRD4t4Mi7HQEgz4&s=CLCDNXdk40202-s5qN8_DTq69katb1MRglD2cPK24t8&e=> externally http://tim.techmahindra.com/tim/disclaimer.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__tim.techmahindra.com_tim_disclaimer.html&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4&m=ET5R9r4L8F5Imk4CVr4NbR9OTOvYMRD4t4Mi7HQEgz4&s=YaRmfmY6xAp4FOAMFzTMYUTDCh2Ca7Kaa_a13uzjNHA&e=> internally within TechMahindra. ============================================================================================================================
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
