More info:
This is the command vagrant gets stuck on:
INFO ssh: Execute: cat /tmp/vagrant-network-entry_eth2 >>
/etc/sysconfig/network-scripts/ifcfg-eth2
if command -v nmcli &>/dev/null; then
if command -v systemctl &>/dev/null && systemctl -q is-enabled NetworkManager
&>/dev/null; then
nmcli c reload eth2
elif command -v service &>/dev/null && service NetworkManager status
&>/dev/null; then
nmcli c reload eth2
fi
fi
/sbin/ifdown eth2
/sbin/ifup eth2
rm -f /tmp/vagrant-network-entry_eth2
(sudo=true)
Thanks
Moshe Hoadley
M 972-9-77-62712
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Moshe Hoadley
Sent: Monday, November 20, 2017 3:19 PM
To: Binshtok, Edan <[email protected]>; Sandeep Shah2
<[email protected]>; [email protected]
Cc: SUNDELOF, ERIK <[email protected]>; MCGOLDRICK, PAUL <[email protected]>
Subject: Re: [onap-discuss] [vvp] - deployment
Hi
My dev env is Ubuntu 16. The virtualization framework is virtualbox.
The current status is that when running 'vagrant up', it is able to boot the
vm ' pxe_ops_01...'.
At this point vagrant gets stuck on network configuration:
devel@devel:~/dev/onap/vvp/devkit$ vagrant up Bringing machine 'ops-01' up with
'virtualbox' provider...
Bringing machine 'ceph-01' up with 'virtualbox' provider...
Bringing machine 'coreos-01' up with 'virtualbox' provider...
==> ops-01: Importing base box 'centos/7'...
==> ops-01: Matching MAC address for NAT networking...
==> ops-01: Setting the name of the VM: pxe_ops-01_1511190177841_48331 ==>
ops-01: Clearing any previously set network interfaces...
==> ops-01: Preparing network interfaces based on configuration...
ops-01: Adapter 1: nat
ops-01: Adapter 2: hostonly
ops-01: Adapter 3: hostonly
==> ops-01: Forwarding ports...
ops-01: 22 (guest) => 2502 (host) (adapter 1) ==> ops-01: Running
'pre-boot' VM customizations...
==> ops-01: Booting VM...
==> ops-01: Waiting for machine to boot. This may take a few minutes...
ops-01: SSH address: 127.0.0.1:2502
ops-01: SSH username: vagrant
ops-01: SSH auth method: private key
ops-01: Warning: Remote connection disconnect. Retrying...
ops-01: Warning: Remote connection disconnect. Retrying...
ops-01: Warning: Remote connection disconnect. Retrying...
==> ops-01: Machine booted and ready!
==> ops-01: Configuring and enabling network interfaces...
From my investigation I see that the command for restarting the networks 'eth1'
and 'eth2' is not returning.
Can't get passed this issue. Did anyone encounter this?
Thanks
Moshe Hoadley
M 972-9-77-62712
-----Original Message-----
From: Binshtok, Edan [mailto:[email protected]]
Sent: Thursday, November 16, 2017 10:12 PM
To: Sandeep Shah2 <[email protected]>; Moshe Hoadley
<[email protected]>; [email protected]
Cc: SUNDELOF, ERIK <[email protected]>; MCGOLDRICK, PAUL <[email protected]>
Subject: Re: [onap-discuss] [vvp] - documentation
On what setup are you guys running the project?
Which version of Linux for example.
Edan
From: Sandeep Shah2 <[email protected]>
Date: Thursday, 16 November 2017 at 18:18
To: Moshe Hoadley <[email protected]>, "Binshtok, Edan"
<[email protected]>, "[email protected]"
<[email protected]>
Cc: "SUNDELOF, ERIK" <[email protected]>, "Binshtok, Edan" <[email protected]>,
"MCGOLDRICK, PAUL" <[email protected]>
Subject: RE: [onap-discuss] [vvp] - documentation
Hi Moshe – this is what I have tried so far and at this time, I am running into
SSH authentication issues…
1. Update Vagrantfile in devkit/vagrant/pxe/Vagrantfile – add
* Require ‘yaml’
2. Change IDE to IDE Controller in pxe/Vagrantfile
I am running into the below issue at this time:
An error occurred in the underlying SSH library that Vagrant uses. The error
message is shown below. In many cases, errors from this library are caused by
ssh-agent issues. Try disabling your SSH agent or removing some keys and try
again.
If the problem persists, please report a bug to the net-ssh project.
timeout during server version negotiating Sandeep
847 708 1068
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Moshe Hoadley
Sent: Wednesday, November 15, 2017 9:32 AM
To: Binshtok, Edan; [email protected]
Subject: Re: [onap-discuss] [vvp] - documentation
Thanks for your reply.
As you suggested, I started working according to the 'devkit' summary:
- I setup a linux development environment with vagrant and ansible.
- from ../vvp/devkit I ran:
. setenv
vagrant up
watch -n5 "kubectl get po -n kube-system"
However, kubectl fails with: " The connection to the server localhost:8080 was
refused".
Am I missing a configuration step for kubectl?
Also, should I run a maven build before 'vagrant up'?
Thanks
Moshe Hoadley
M 972-9-77-62712
-----Original Message-----
From:
[email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Binshtok, Edan
Sent: Wednesday, November 15, 2017 10:48 AM
To: Moshe Hoadley <[email protected]<mailto:[email protected]>>;
[email protected]<mailto:[email protected]>
Subject: Re: [onap-discuss] [vvp] - documentation
Hello Moshe,
VVP is built from multiple containers which rely on each other except from
validation scripts.
You need to set up the all system in order to use it as platform not just a
single docker.
VVP is based on kubernetes and use rockets.
For example, the rocket you sent a picture of is just a FE.
The best way to handle booting up a system is of corse starting from the devkit
repo which is in charge of all the process mentioned above Here is the repo
https://gerrit.onap.org/r/gitweb?p=vvp%2Fdevkit.git;a=summary<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Dvvp-252Fdevkit.git-3Ba-3Dsummary&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=-Wgjy_QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec&m=XrY_MhvTFutbPkutCJgH2-Ub8sLvoajB0EkBhrK4mOc&s=fOGqKiBpW15TgJPxSHMYRdU0uxp0HMte29Bn_GLEnVA&e=>
Thank you,
Edan Binshtok.
From:
<[email protected]<mailto:[email protected]>>
on behalf of Moshe Hoadley
<[email protected]<mailto:[email protected]>>
Date: Thursday, 2 November 2017 at 10:33
To: "[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>
Subject: Re: [onap-discuss] [vvp] - documentation
Hi
I’m trying to learn more about the vvp project but couldn’t find any meaningful
information.
Where can I find documentation for this project?
I also tried building the code – I was able to create and run the vvp-portal
docker but couldn’t get it to actually work.
Thanks
Moshe Hoadley
• 972-9-77-62712
[id:[email protected]]
This message and the information contained herein is proprietary and
confidential and subject to the Amdocs policy statement, you may review at
https://www.amdocs.com/about/email-disclaimer<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=-Wgjy_QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec&m=tZAuQZ5XCthdERcZzjqfHSjn3qLiMiLHUV3wS95etKU&s=yfHWagPlxtDgYtqyQYH1S0tan-j2bRWQijRU0-JxgIg&e<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer-253chttps-3A_urldefense.proofpoint.com_v2_url-3Fu-3Dhttps-2D3A-5F-5Fwww.amdocs.com-5Fabout-5Femail-2D2Ddisclaimer-26d-3DDwMFAg-26c-3DLFYZ-2Do9-5FHUMeMTSQicvjIg-26r-3D-2DWgjy-5FQbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec-26m-3DtZAuQZ5XCthdERcZzjqfHSjn3qLiMiLHUV3wS95etKU-26s-3DyfHWagPlxtDgYtqyQYH1S0tan-2Dj2bRWQijRU0-2DJxgIg-26e&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=-Wgjy_QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec&m=XrY_MhvTFutbPkutCJgH2-Ub8sLvoajB0EkBhrK4mOc&s=SsgaPMbTPCemqlsOHCSxY_O47N8F4YJWbh6mYB2BbDY&e=>=>
This message and the information contained herein is proprietary and
confidential and subject to the Amdocs policy statement,
you may review at
https://www.amdocs.com/about/email-disclaimer<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=-Wgjy_QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec&m=XrY_MhvTFutbPkutCJgH2-Ub8sLvoajB0EkBhrK4mOc&s=KUAZGydLZAqT_s1QjVfDVlPBlPImkbj_EBRynkZtjwI&e=>
<https://www.amdocs.com/about/email-disclaimer<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=-Wgjy_QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec&m=XrY_MhvTFutbPkutCJgH2-Ub8sLvoajB0EkBhrK4mOc&s=KUAZGydLZAqT_s1QjVfDVlPBlPImkbj_EBRynkZtjwI&e=>>
_______________________________________________
onap-discuss mailing list
[email protected]<mailto:[email protected]>
https://lists.onap.org/mailman/listinfo/onap-discuss<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=-Wgjy_QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec&m=XrY_MhvTFutbPkutCJgH2-Ub8sLvoajB0EkBhrK4mOc&s=5xukJqI0PUjYZLWcvRtGUOIYFz65zT-6Ij_dHC2RDF8&e=>
============================================================================================================================
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=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=-Wgjy_QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec&m=XrY_MhvTFutbPkutCJgH2-Ub8sLvoajB0EkBhrK4mOc&s=D9J0K_esoww9Fh5FNXResi48yu_Db33HlFmNd9Wq200&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=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=-Wgjy_QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec&m=XrY_MhvTFutbPkutCJgH2-Ub8sLvoajB0EkBhrK4mOc&s=ZwUXqtPjEWGYYKiLvXBsFKk3XYkOhQ2RZI7R5jZT8_E&e=>
internally within TechMahindra.
============================================================================================================================
This message and the information contained herein is proprietary and
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
<https://www.amdocs.com/about/email-disclaimer>
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
This message and the information contained herein is proprietary and
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
<https://www.amdocs.com/about/email-disclaimer>
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
