[vpp-dev] Build deb packages in debug mode

2016-12-13 Thread Dmitry Bufistov 
Hi list,

Could you please advice a simple way to get VPP deb packages with all debug
info?
I am trying this change:
diff --git a/build-data/platforms/vpp_lite.mk b/build-data/platforms/
vpp_lite.mk
index 81ba90d..f9ee550 100644
--- a/build-data/platforms/vpp_lite.mk
+++ b/build-data/platforms/vpp_lite.mk
@@ -39,9 +39,9 @@ vpp_lite_debug_TAG_CFLAGS = -g -O0 -DCLIB_DEBUG
-DFORTIFY_SOURCE=2 -march=$(MARC
 vpp_lite_debug_TAG_LDFLAGS = -g -O0 -DCLIB_DEBUG -DFORTIFY_SOURCE=2
-march=$(MARCH) \
-fstack-protector-all -fPIC -Werror

-vpp_lite_TAG_CFLAGS = -g -O2 -DFORTIFY_SOURCE=2 -march=$(MARCH)
-mtune=$(MTUNE) \
+vpp_lite_TAG_CFLAGS = -g -O0 -DCLIB_DEBUG  -DFORTIFY_SOURCE=2
-march=$(MARCH) \
-fstack-protector -fPIC -Werror
-vpp_lite_TAG_LDFLAGS = -g -O2 -DFORTIFY_SOURCE=2 -march=$(MARCH)
-mtune=$(MTUNE) \
+vpp_lite_TAG_LDFLAGS = -g -O0 -DCLIB_DEBUG -DFORTIFY_SOURCE=2
-march=$(MARCH) \
-fstack-protector -fPIC -Werror

 vpp_lite_gcov_TAG_CFLAGS = -g -O0 -DCLIB_DEBUG -march=$(MARCH) \

But still see that all linking tasks are done with -O2.
My target platform is vpp_lite, this is not a mistake.

Thanks a lot for any help.

Dmitry
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] vHost user test scenarios for CSIT - TWS meeting

2016-12-13 Thread Alec Hothan (ahothan) 

Thanks for confirming Billy and Thomas.
Could you also check regarding link bonding (whether deployments use link 
bonding).

A single tenant interface + bonding (which means 2 phys interfaces bonded) will 
exercise the bonding code in dpdk for the egress traffic..
This will also dictate the spec of the traffic generator frames (likely range 
of L3 addresses) in order to do proper load balancing.


Best Regards,

   Alec






From:  on behalf of Thomas F Herbert 

Date: Tuesday, December 13, 2016 at 9:39 AM
To: "vpp-dev@lists.fd.io" 
Subject: Re: [vpp-dev] vHost user test scenarios for CSIT - TWS meeting




On 12/13/2016 07:53 AM, Billy McFall wrote:
I consulted with some of my Red Hat colleagues (primarily ODL developers) and 
they agree that the typical deployment they have seen is with one interface, 
not two.
+1


Billy McFall

On Tue, Dec 13, 2016 at 2:27 AM, Pierre Pfister (ppfister) 
> wrote:
As per my action item from last meeting, I asked RedHat guy why they came up 
with testing with 2 physical interfaces instead of just one.

And the answer is really that they did that out of simplicity.
We should probably run some tests and see if using a single interface makes a 
difference (and take a decision based on that).

The person I talked to also mentioned that it is desirable to run tests with 
realistic flows and packet size rather than focusing on the very limited 64B 
Mpps test.

- Pierre



Le 7 déc. 2016 à 01:20, Maciek Konstantynowicz (mkonstan) 
> a écrit :

REMINDER:

Next call details:
https://wiki.fd.io/view/TWS
CSIT - vHost user test scenarios for CSIT
Wednesday, 7 December 2016
09:00  |  PST Time | 1 hr
17:00  |  GMT Time (London, GMT)  |  1 hr
Join WebEx meeting: 
https://cisco.webex.com/ciscosales/j.php?MTID=m2d165f5c9f3fdf722826e7c05a4499c9
Meeting number: 202 237 426
Meeting password: RZrXrBac (79797222 from phones)

-Maciek

On 2 Dec 2016, at 17:17, Maciek Konstantynowicz (mkonstan) 
> wrote:

Many thanks to all who attended the TWS call today. Notes were taken on 
#fdio-meeting IRC and CSIT wiki per links below.
We agreed to have a follow-up TWS call to finish the live discussion - on 
Wednesday 7-Dec 09:00-10:00 PST, call details below and on FD.io 
TWS page.

Minutes:
* Meeting ended Fri Dec  2 18:07:36 2016 UTC.  Information about MeetBot at 
http://wiki.debian.org/MeetBot . (v 0.1.4)
* Minutes:
http://ircbot.wl.linuxfoundation.org/meetings/fdio-meeting/2016/fdio-meeting.2016-12-02-16.58.html
* Minutes (text): 
http://ircbot.wl.linuxfoundation.org/meetings/fdio-meeting/2016/fdio-meeting.2016-12-02-16.58.txt
* Log:
http://ircbot.wl.linuxfoundation.org/meetings/fdio-meeting/2016/fdio-meeting.2016-12-02-16.58.log.html

Updates:
https://wiki.fd.io/view/CSIT/vhostuser_test_scenarios

Next call details:
https://wiki.fd.io/view/TWS
CSIT - vHost user test scenarios for CSIT
Wednesday, 7 December 2016
09:00  |  PST Time | 1 hr
17:00  |  GMT Time (London, GMT)  |  1 hr
Join WebEx meeting: 
https://cisco.webex.com/ciscosales/j.php?MTID=m2d165f5c9f3fdf722826e7c05a4499c9
Meeting number: 202 237 426
Meeting password: RZrXrBac (79797222 from phones)

-Maciek


On 1 Dec 2016, at 15:05, Maciek Konstantynowicz (mkonstan) 
> wrote:

Here call details:

vHost user test scenarios for CSIT - TWS meeting
Friday, 2 December 2016
17:00  |  GMT Time (London, GMT)  |  1 hr
09:00  |  PST Time | 1 hr

Join WebEx meeting: 
https://cisco.webex.com/ciscosales/j.php?MTID=m80cb727098e36de668591ffdcf11ad83
Meeting number: 203 819 086
Meeting password: A335rJNd (23357563 from phones)

Also updated here: https://wiki.fd.io/view/TWS

-Maciek

vHost user test scenarios for CSIT - TWS meeting
Friday, 2 December 2016
17:00  |  GMT Time (London, GMT)  |  1 hr

Join WebEx meeting: 
https://cisco.webex.com/ciscosales/j.php?MTID=m80cb727098e36de668591ffdcf11ad83
Meeting number: 203 819 086
Meeting password: A335rJNd (23357563 from phones)

Join by phone
+1-408-525-6800 Call-in toll number (US/Canada)
+1-866-432-9903 Call-in toll-free number (US/Canada)
Access code: 203 819 086
Global call-in numbers  |  Toll-free calling restrictions

On 1 Dec 2016, at 10:56, Maciek Konstantynowicz (mkonstan) 
> wrote:

OK, this sounds convincing at least to em. Set for 09:00 - 10:00am PST 
tomorrow, Friday, 2-Dec.
I will set up webex, and advertise it on csit-dev and vpp-dev and on TWS page.
Give me an hour or so.. working in PST TZ makes me slower than UK - is it CA 
air? ;)

-Maciek

On 1 Dec 2016, at 05:02, Thomas F Herbert 
> wrote:




On 11/30/2016 08:41 PM, Maciek Konstantynowicz (mkonstan) wrote:
All,

We

Re: [vpp-dev] QQs on VPP clone.sh

2016-12-13 Thread Ed Warnicke 
Ray,

The reason is because vagrant produces a bunch of 'issues' when trying to
build from a 'mounted' share.

When running vagrant, /vpp gets mounted with where ever the source is
*outside* the vagrant VM

Once inside, if you try to build from /vpp, a variety of things can and do
break sadly :(

So we clone vpp again into the local-to-the-VM storage.

Does that answer your question?

Ed

On Tue, Dec 13, 2016 at 10:47 AM, Kinsella, Ray 
wrote:

> Folks,
>
> Two QQ on clone.sh
> (https://git.fd.io/vpp/tree/build-root/vagrant/clone.sh)
>
> 1. Why are we re-cloning source already available in /vpp?
> 2. Why do we ssh to remote server on the third last line ?
> (this presumably hangs?).
>
> Ray K
>
>
> # Setup the vpp code
> cd ~vagrant/
> sudo -u vagrant mkdir git
> cd git/
> echo "SSH_AUTH_SOCK  $SSH_AUTH_SOCK x"
> chmod 777 $SSH_AUTH_SOCK
>
> CLONE_URL=`cd /vpp;git remote -v | grep origin |grep fetch |awk '{print
> $2}'`
> echo "CLONE_URL $CLONE_URL"
> echo $CLONE_URL | grep -q "^ssh:"
> if [ $? == 0 ]; then
> SSH_HOST=`echo $CLONE_URL| awk -F/ '{print $3}'`
> SSH_PORT=`echo $SSH_HOST| awk -F: '{print $2}'`
> if [ -n $SSH_PORT ]; then
> SSH_PORT="-p $SSH_PORT"
> fi
> SSH_HOST=`echo $SSH_HOST| awk -F: '{print $1}'`
> echo "SSH_HOST $SSH_HOST"
> echo "SSH_PORT $SSH_PORT"
> sudo -HE -u vagrant ssh -oStrictHostKeyChecking=no -v $SSH_PORT
> $SSH_HOST
> fi
> sudo -HE -u vagrant git clone $CLONE_URL
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] VIRL servers back in operation

2016-12-13 Thread Jan Gelety -X (jgelety - PANTHEON TECHNOLOGIES at Cisco) 
Hello,

Issue with VIRL servers is fixed (and small correction that should avoid such 
issue in the future applied) and vpp-csit-verify job can be run now.

Recheck was applied on following affected patches:

https://gerrit.fd.io/r/#/c/4267/1
https://gerrit.fd.io/r/#/c/4197/2
https://gerrit.fd.io/r/#/c/4269/1

Patch https://gerrit.fd.io/r/4217 seems to be a draft (no recheck possible 
there from our side).

Regards,
Jan
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] vHost user test scenarios for CSIT - TWS meeting

2016-12-13 Thread Thomas F Herbert 



On 12/13/2016 07:53 AM, Billy McFall wrote:
I consulted with some of my Red Hat colleagues (primarily ODL 
developers) and they agree that the typical deployment they have seen 
is with one interface, not two.

+1


Billy McFall

On Tue, Dec 13, 2016 at 2:27 AM, Pierre Pfister (ppfister) 
> wrote:


As per my action item from last meeting, I asked RedHat guy why
they came up with testing with 2 physical interfaces instead of
just one.

And the answer is really that they did that out of simplicity.
We should probably run some tests and see if using a single
interface makes a difference (and take a decision based on that).

The person I talked to also mentioned that it is desirable to run
tests with realistic flows and packet size rather than focusing on
the very limited 64B Mpps test.

- Pierre




Le 7 déc. 2016 à 01:20, Maciek Konstantynowicz (mkonstan)
> a écrit :

REMINDER:

Next call details:
https://wiki.fd.io/view/TWS
CSIT - vHost user test scenarios for CSIT
Wednesday, 7 December 2016
09:00  |  PST Time | 1 hr
17:00  |  GMT Time (London, GMT)  |  1 hr
Join WebEx meeting:

https://cisco.webex.com/ciscosales/j.php?MTID=m2d165f5c9f3fdf722826e7c05a4499c9


Meeting number:202 237 426
Meeting password:RZrXrBac (79797222 from phones)

-Maciek


On 2 Dec 2016, at 17:17, Maciek Konstantynowicz (mkonstan)
> wrote:

Many thanks to all who attended the TWS call today. Notes were
taken on #fdio-meeting IRC and CSIT wiki per links below.
We agreed to have a follow-up TWS call to finish the live
discussion - on Wednesday 7-Dec 09:00-10:00 PST, call details
below and on FD.io  TWS page.

Minutes:
* Meeting ended Fri Dec  2 18:07:36 2016 UTC.  Information about
MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
* Minutes:

http://ircbot.wl.linuxfoundation.org/meetings/fdio-meeting/2016/fdio-meeting.2016-12-02-16.58.html


* Minutes (text):

http://ircbot.wl.linuxfoundation.org/meetings/fdio-meeting/2016/fdio-meeting.2016-12-02-16.58.txt


* Log:

http://ircbot.wl.linuxfoundation.org/meetings/fdio-meeting/2016/fdio-meeting.2016-12-02-16.58.log.html



Updates:
https://wiki.fd.io/view/CSIT/vhostuser_test_scenarios


Next call details:
https://wiki.fd.io/view/TWS
CSIT - vHost user test scenarios for CSIT
Wednesday, 7 December 2016
09:00  |  PST Time | 1 hr
17:00  |  GMT Time (London, GMT)  |  1 hr
Join WebEx meeting:

https://cisco.webex.com/ciscosales/j.php?MTID=m2d165f5c9f3fdf722826e7c05a4499c9


Meeting number:202 237 426
Meeting password:RZrXrBac (79797222 from phones)

-Maciek



On 1 Dec 2016, at 15:05, Maciek Konstantynowicz (mkonstan)
> wrote:

Here call details:

vHost user test scenarios for CSIT - TWS meeting
Friday, 2 December 2016
17:00  |  GMT Time (London, GMT)  |  1 hr
09:00  |  PST Time | 1 hr

Join WebEx meeting:

https://cisco.webex.com/ciscosales/j.php?MTID=m80cb727098e36de668591ffdcf11ad83


Meeting number:203 819 086
Meeting password:A335rJNd (23357563 from phones)

Also updated here: https://wiki.fd.io/view/TWS


-Maciek

vHost user test scenarios for CSIT - TWS meeting
Friday, 2 December 2016
17:00  |  GMT Time (London, GMT)  |  1 hr

Join WebEx meeting:

https://cisco.webex.com/ciscosales/j.php?MTID=m80cb727098e36de668591ffdcf11ad83


Meeting number:203 819 086
Meeting password:A335rJNd (23357563 from phones)

Join by phone
+1-408-525-6800  Call-in toll number
(US/Canada)
+1-866-432-9903  Call-in toll-free
number (US/Canada)
Access code: 203 819 086
Global call-in numbers  |  Toll-free calling restrictions


On 1 Dec 2016, at 10:56, Maciek Konstantynowicz (mkonstan)
> wrote:

OK, this sounds convincing at least to em. Set for 09:00 -

[vpp-dev] Modify tag on tap/vhost interface

2016-12-13 Thread Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) 
Hi,

I noticed that tag field  is not present in the tap_modify/modify_vhost_user_if 
message, but is present in tap_connect/create_vhost_user_if.
Does it mean tag is meant to be unmodifiable, or value is missing because of 
oversight?

Regards,
Marek
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] vxlan setup guidance

2016-12-13 Thread Kinsella, Ray 


I had manually set flags=0x8 to get scapy + vpp to work correctly also.
Might be something to fix in Scapy and upstream?

Ray K

On 09/12/2016 19:34, Matej Klotton -X (mklotton - PANTHEON TECHNOLOGIES 
at Cisco) wrote:

My understanding is, if is VXLAN then UDP destination port is 4789 and
must have set I bit to 1. If is frame encapsulated into VXLAN GPE then
UDP destination port is 4790 and must have set I and P bits (probably
some others too). The RFCs also defines that if is received wrong bit
set it should be ignored.


___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev