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

3.      Patch from https://gerrit.onap.org/r/#/c/7719/ (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: [email protected] 
[mailto:[email protected]]
Sent: Wednesday, August 16, 2017 7:52 PM
To: 'DRAGOSH, PAMELA L (PAM)' <[email protected]>; Atul Shegokar 
<[email protected]>; Guo, Ruijing <[email protected]>
Cc: [email protected]
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 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 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: 
[email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of DRAGOSH, PAMELA L 
(PAM)
Sent: Wednesday, August 16, 2017 5:13 PM
To: Atul Shegokar 
<[email protected]<mailto:[email protected]>>; 
[email protected]<mailto:[email protected]>
Cc: [email protected]<mailto:[email protected]>
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: 
<[email protected]<mailto:[email protected]>>
 on behalf of Atul Shegokar 
<[email protected]<mailto:[email protected]>>
Date: Wednesday, August 16, 2017 at 4:31 AM
To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
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
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to