[vpp-dev] ACL and Policier

2019-02-27 Thread mahdy . varasteh
Hi

I wondered if we can use ACLs instead of classifier tables in Policies. How is 
it possible? ( if it is possible)
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12382): https://lists.fd.io/g/vpp-dev/message/12382
Mute This Topic: https://lists.fd.io/mt/30161156/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


[vpp-dev] VPP crashed on servers with unusual numa config

2019-02-27 Thread Lijian Zhang
Hi Maintainers,
I have two supermicro x86 servers with unusual numa configs. The first server 
has two physical CPUs, but only one numa node. The other server has two 
physical CPUs, two numa nodes, but only numa node 0 has attached memories. The 
detailed CPU info are dumped as below.

VPP crashed on both server with below call-stack. VPP gets numa nodes ‘0-1’ 
from ‘/sys/devices/system/node/possible’, and initialize buffers for all of 
numa nodes, while numa node 1 has no memories, so below function failed with 
numa node.

If ‘/sys/devices/system/node/has_memories’ is used to detect the numa nodes, on 
which VPP initialize buffers, there will be no such crash issue.

Could you please evaluate this issue, and evaluate if this is a reasonable 
change requirement, or should we just skip the issue because of the abnormal 
numa configs in my servers?

#0  vlib_physmem_shared_map_create (vm=0x76853240 , 
name=0x7fffb786621c "buffers-numa-0", size=1073741824, log2_page_sz=30, 
numa_node=0, map_index=0x7fffb51ffd84) at 
/home/lijian/tasks/origin/src/vlib/physmem.c:45
#1  0x7657b279 in vlib_buffer_main_init_numa_node (vm=0x76853240 
, numa_node=0) at 
/home/lijian/tasks/origin/src/vlib/buffer.c:672
#2  0x7657b8f9 in vlib_buffer_main_init (vm=0x76853240 
) at /home/lijian/tasks/origin/src/vlib/buffer.c:801
#3  0x765c7bb2 in vlib_main (vm=0x76853240 , 
input=0x7fffb51fffb0) at /home/lijian/tasks/origin/src/vlib/main.c:1988
#4  0x7662570a in thread0 (arg=140737329312320) at 
/home/lijian/tasks/origin/src/vlib/unix/main.c:606
#5  0x76079544 in clib_calljmp () from 
/home/lijian/tasks/origin/build-root/build-vpp_debug-native/vpp/lib/libvppinfra.so.19.04
#6  0x7fffd2b0 in ?? ()
#7  0x76625bd7 in vlib_unix_main (argc=36, argv=0x5586f3b0) at 
/home/lijian/tasks/origin/src/vlib/unix/main.c:675
#8  0xbedc in main (argc=36, argv=0x5586f3b0) at 
/home/lijian/tasks/origin/src/vpp/vnet/main.c:274


lijian@net-x86-supermicro-01:~/tasks/origin$ sudo numactl -H
available: 1 nodes (0)
node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
node 0 size: 64383 MB
node 0 free: 33048 MB
node distances:
node   0
  0:  10
lijian@net-x86-supermicro-01:~/tasks/origin$ lscpu
Architecture:  x86_64
CPU op-mode(s):32-bit, 64-bit
Byte Order:Little Endian
CPU(s):20
On-line CPU(s) list:   0-19
Thread(s) per core:1
Core(s) per socket:10
Socket(s): 2
NUMA node(s):  1
Vendor ID: GenuineIntel
CPU family:6
Model: 63
Model name:Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz
Stepping:  2
CPU MHz:   2300.179
CPU max MHz:   3000.
CPU min MHz:   1200.
BogoMIPS:  4601.05
Virtualization:VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache:  256K
L3 cache:  25600K
NUMA node0 CPU(s): 0-19
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 
ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm epb invpcid_single 
kaiser tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep 
bmi2 erms invpcid cqm xsaveopt cqm_llc cqm_occup_llc dtherm arat pln pts


lijian@net-x86-supermicro-02:~/tasks/origin$ sudo numactl -H
available: 2 nodes (0-1)
node 0 cpus: 0 1 2 3 4 5 6 7 8 9
node 0 size: 64311 MB
node 0 free: 30865 MB
node 1 cpus: 10 11 12 13 14 15 16 17 18 19
node 1 size: 0 MB
node 1 free: 0 MB
node distances:
node   0   1
  0:  10  20
  1:  20  10
lijian@net-x86-supermicro-02:~/tasks/origin$ lscpu
Architecture:x86_64
CPU op-mode(s):  32-bit, 64-bit
Byte Order:  Little Endian
CPU(s):  20
On-line CPU(s) list: 0-19
Thread(s) per core:  1
Core(s) per socket:  10
Socket(s):   2
NUMA node(s):2
Vendor ID:   GenuineIntel
CPU family:  6
Model:   63
Model name:  Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz
Stepping:2
CPU MHz: 1200.176
CPU max MHz: 2300.
CPU min MHz: 1200.
BogoMIPS:4599.71
Virtualization:  VT-x
L1d cache:   32K
L1i cache:   32K
L2 cache:256K
L3 cache:25600K
NUMA node0 CPU(s):   0-9
NUMA node1 CPU(s):   10-19
Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx 

[vpp-dev] VPP - ixia tests failing

2019-02-27 Thread carlito nueno
Hi all,

I got a chance to get my hands on an ixia testing box. Unfortunately I
was not able to test because upstream (from ethernet to client) was
not working:

Not working: ixia on ethernet is not receiving packets
client (ixia) --> WiFi AP --> GigabitEthernet4/0/0.3 --> vpp -->
GigabitEthernet5/0/0 (ixia)

The other way is working: ixia client is receiving packets
(ixia)GigabitEthernet5/0/0 --> vpp --> GigabitEthernet4/0/0.3 --> wifi
AP  --> client (ixia)

Both TCP and UDP tests failed. Packets are being dropped by VPP
(error-drop, null-node: blackholed packets).

running: vpp v18.10-rc0~229-g869031c5

ixia mac addresses:
client: 00:21:dd:xx:xx:xx
server: 00:11:dd:xx:xx:xx

wifi access point mac address:
AP: a4:c5:ef:xx:xx:xx

I don't have ACLs setup.

Here is my vpp.conf and packet capture:
https://gist.github.com/ironpillow/9b1c5dd0905135ff09eba6067db179ae

Any advice?

Thanks
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12380): https://lists.fd.io/g/vpp-dev/message/12380
Mute This Topic: https://lists.fd.io/mt/30159793/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Re: [vpp-dev] VPP 19.04 Program Plan Deliverables

2019-02-27 Thread Dave Wallace

Honnappa,

It is best to propose deliverables as far in advance of F0 as 
practicable.  There is no penalty for deferring deliverables to a later 
release.


Common courtesy is to announce deliverables to the community early in 
the development process to avoid duplication of effort.  This may also 
save development time/effort if the feature is one that is deemed out of 
scope of the community's charter by the VPP committers.


Thanks,
-daw-

On 2/27/2019 9:58 AM, Honnappa Nagarahalli wrote:


Hi Dave,

Is there any deadline for proposing the deliverables? (F0?)

Thank you,

Honnappa

*From:*vpp-dev@lists.fd.io  *On Behalf Of *Dave 
Wallace

*Sent:* Monday, February 25, 2019 6:47 AM
*To:* vpp-dev@lists.fd.io
*Subject:* [vpp-dev] VPP 19.04 Program Plan Deliverables

Folks,

Please add the deliverables that you are planning to develop for the 
VPP 19.04 release to the "Deliverables" section of the VPP 19.04 
Program Plan.


https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_19.04#Release_Deliverables

Thanks,
-daw-
"Your Friendly VPP 19.04 Program Manager"



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12379): https://lists.fd.io/g/vpp-dev/message/12379
Mute This Topic: https://lists.fd.io/mt/30037464/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Re: [vpp-dev] New vpp project committer nomination: Paul Vinciguerra

2019-02-27 Thread Andrew Yourtchenko
+1

--a

> On 27 Feb 2019, at 09:21, Damjan Marion via Lists.Fd.Io 
>  wrote:
> 
> +1
> 
>> On 27 Feb 2019, at 14:20, Dave Barach via Lists.Fd.Io 
>>  wrote:
>> 
>> +1... Dave
>>  
>> From: vpp-dev@lists.fd.io  On Behalf Of Dave Barach via 
>> Lists.Fd.Io
>> Sent: Wednesday, February 27, 2019 7:38 AM
>> To: vpp-dev@lists.fd.io
>> Cc: vpp-dev@lists.fd.io
>> Subject: [vpp-dev] New vpp project committer nomination: Paul Vinciguerra
>>  
>> In view of significant code contributions to the vpp project - see below - 
>> I'm pleased to nominate Paul Vinciguerra as a vpp project committer. I have 
>> high confidence that he'll be a major asset to the project in a committer 
>> role.  
>>  
>> Paul has contributed 100 merged patches, concentrating on the “make test” 
>> .py framework. 
>> Seehttps://gerrit.fd.io/r/#/q/status:merged+owner:%22Paul+Vinciguerra+%253Cpvinci%2540vinciconsulting.com%253E%22
>>  
>> Committers, please vote (+1, 0, -1) on vpp-dev@lists.fd.io. We'll need a 
>> recorded vote so that the TSC will approve Paul’s nomination.
>>  
>> If at all possible please vote today, February 27, 2019 so we can add Paul’s 
>> nomination to tomorrow’s TSC agenda for final approval.
>>  
>> Thanks... Dave
>>  
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> 
>> View/Reply Online (#12356): https://lists.fd.io/g/vpp-dev/message/12356
>> Mute This Topic: https://lists.fd.io/mt/30151621/675642
>> Group Owner: vpp-dev+ow...@lists.fd.io
>> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [dmar...@me.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
> 
> -- 
> Damjan
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#12357): https://lists.fd.io/g/vpp-dev/message/12357
> Mute This Topic: https://lists.fd.io/mt/30151621/675608
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [ayour...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12378): https://lists.fd.io/g/vpp-dev/message/12378
Mute This Topic: https://lists.fd.io/mt/30151621/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Re: [vpp-dev] OpenSuse builds failing for stable/1901

2019-02-27 Thread Paul Vinciguerra
Great!

I'm not convinced that it's fully fixed.  See your log:
https://jenkins.fd.io/job/vpp-verify-1901-osleap15/81/consoleFull
I interpret these logs as we do not have feature parity across the various
distros at the moment.

Paul

*15:21:06* -- Found Threads: TRUE  *15:21:06* CMake Warning at
/usr/share/cmake/Modules/FindBoost.cmake:801 (message):*15:21:06*
New Boost version may have incorrect or missing dependencies and
imported*15:21:06*   targets*15:21:06* Call Stack (most recent call
first):*15:21:06*   /usr/share/cmake/Modules/FindBoost.cmake:906
(_Boost_COMPONENT_DEPENDENCIES)*15:21:06*
/usr/share/cmake/Modules/FindBoost.cmake:1544
(_Boost_MISSING_DEPENDENCIES)*15:21:06*   CMakeLists.txt:27
(find_package)*15:21:06* *15:21:06* *15:21:06* CMake Warning at
/usr/share/cmake/Modules/FindBoost.cmake:801 (message):*15:21:06*
New Boost version may have incorrect or missing dependencies and
imported*15:21:06*   targets*15:21:06* Call Stack (most recent call
first):*15:21:06*   /usr/share/cmake/Modules/FindBoost.cmake:906
(_Boost_COMPONENT_DEPENDENCIES)*15:21:06*
/usr/share/cmake/Modules/FindBoost.cmake:1544
(_Boost_MISSING_DEPENDENCIES)*15:21:06*   CMakeLists.txt:27
(find_package)*15:21:06* *15:21:06* *15:21:06* -- Could NOT find
Boost*15:21:06* -- Configuring done*15:21:06* -- Generating done


On Wed, Feb 27, 2019 at 3:38 PM Ed Warnicke  wrote:

> Paul,
>
> Looks like it was a ships in the night effect on a fix going into
> stable/1901... rebase *appears* to have fixed it:
>
> https://gerrit.fd.io/r/#/c/17884/
>
> Ed
>
> On Wed, Feb 27, 2019 at 2:14 PM Paul Vinciguerra <
> pvi...@vinciconsulting.com> wrote:
>
>> Ok.
>>
>> Let me know if I can do anything to help!
>>
>> On Wed, Feb 27, 2019 at 3:09 PM Ed Kern (ejk)  wrote:
>>
>>> thats a perfectly good and reasonable change and I support it..
>>>
>>> But that’s not the problem that the other ed is having right now.
>>>
>>> Ed
>>>
>>>
>>>
>>> On Feb 27, 2019, at 12:47 PM, Paul Vinciguerra <
>>> pvi...@vinciconsulting.com> wrote:
>>>
>>> Ed,
>>>
>>> There is an issue.  I am testing a fix.
>>> See: https://gerrit.fd.io/r/#/c/17917/
>>>
>>> Paul
>>>
>>> On Wed, Feb 27, 2019 at 2:23 PM Ed Warnicke  wrote:
>>>
 Paul,

 Good first thing to check... I've pushed
 https://gerrit.fd.io/r/#/c/17916/

 to cause the opensuse jobs to cat the /etc/os-release as you suggested,
 and rechecked: https://gerrit.fd.io/r/#/c/17884/
 to see what happens :)

 Ed

 On Wed, Feb 27, 2019 at 12:48 PM Paul Vinciguerra <
 pvi...@vinciconsulting.com> wrote:

> Can we confirm that they are truly osleap15?
>
> An osleap box reports correctly for me:
> docker run --shm-size=1024m -it opensuse/leap:leap-15 /bin/bash
> *ee4938c281e4:/ #* cat /etc/os-release
> NAME="openSUSE Leap"
> VERSION="15.0 Beta"
> ID="opensuse"
> ID_LIKE="suse"
> VERSION_ID="15.0"
> PRETTY_NAME="openSUSE Leap 15.0 Beta"
> ANSI_COLOR="0;32"
> CPE_NAME="cpe:/o:opensuse:leap:15.0"
> BUG_REPORT_URL="https://bugs.opensuse.org;
> HOME_URL="https://www.opensuse.org/;
>
> On Wed, Feb 27, 2019 at 1:12 PM Edward Warnicke 
> wrote:
>
>> In cherry picking some fixes back to stable/1901, I've found that the
>> builds for 1901 for OpenSuse Leap seem to be failing during install-deps:
>>
>> https://jenkins.fd.io/job/vpp-verify-1901-osleap15/77/console
>>
>> *10:50:21* No provider of 'libboost_thread1_68_0-devel-1.68.0' found.
>>
>>
>> Which looks like there is some upstream issue with a dependency no
>> longer being available for libboost.
>>
>> Digging deeper, it would appear that we are tripping on
>> SUSE_NAME=Tumbleweed:
>>
>> https://github.com/FDio/vpp/blob/stable/1901/Makefile#L131
>>
>> ifeq ($(OS_ID),opensuse)
>> ifeq ($(SUSE_NAME),Tumbleweed)
>> RPM_SUSE_DEVEL_DEPS = libboost_headers1_68_0-devel-1.68.0
>> libboost_thread1_68_0-devel-1.68.0 gcc
>> RPM_SUSE_PYTHON_DEPS += python2-ply python2-virtualenv
>> endif
>> ifeq ($(SUSE_ID),15.0)
>> RPM_SUSE_DEVEL_DEPS = libboost_headers-devel libboost_thread-devel
>> gcc6
>> else
>> RPM_SUSE_DEVEL_DEPS += libboost_headers1_68_0-devel-1.68.0 gcc6
>> RPM_SUSE_PYTHON_DEPS += python-virtualenv
>> endif
>> endif
>>
>> So for some reason, the servers are reporting SUSE_NAME=Tumbelweed,
>> and being asked to install the wrong packages even though they are OSLEAP
>> 15 boxes.  Note: this same Makefile fragment is identical on master where
>> the corresponding jobs are succeeding.
>>
>> Do any of the OpenSuse folks have ideas as to what could be happening
>> here?
>>
>> Ed
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>>
>> View/Reply Online (#12366):
>> https://lists.fd.io/g/vpp-dev/message/12366
>> Mute This Topic: 

Re: [vpp-dev] OpenSuse builds failing for stable/1901

2019-02-27 Thread Edward Warnicke
Paul,

Looks like it was a ships in the night effect on a fix going into
stable/1901... rebase *appears* to have fixed it:

https://gerrit.fd.io/r/#/c/17884/

Ed

On Wed, Feb 27, 2019 at 2:14 PM Paul Vinciguerra 
wrote:

> Ok.
>
> Let me know if I can do anything to help!
>
> On Wed, Feb 27, 2019 at 3:09 PM Ed Kern (ejk)  wrote:
>
>> thats a perfectly good and reasonable change and I support it..
>>
>> But that’s not the problem that the other ed is having right now.
>>
>> Ed
>>
>>
>>
>> On Feb 27, 2019, at 12:47 PM, Paul Vinciguerra <
>> pvi...@vinciconsulting.com> wrote:
>>
>> Ed,
>>
>> There is an issue.  I am testing a fix.
>> See: https://gerrit.fd.io/r/#/c/17917/
>>
>> Paul
>>
>> On Wed, Feb 27, 2019 at 2:23 PM Ed Warnicke  wrote:
>>
>>> Paul,
>>>
>>> Good first thing to check... I've pushed
>>> https://gerrit.fd.io/r/#/c/17916/
>>>
>>> to cause the opensuse jobs to cat the /etc/os-release as you suggested,
>>> and rechecked: https://gerrit.fd.io/r/#/c/17884/
>>> to see what happens :)
>>>
>>> Ed
>>>
>>> On Wed, Feb 27, 2019 at 12:48 PM Paul Vinciguerra <
>>> pvi...@vinciconsulting.com> wrote:
>>>
 Can we confirm that they are truly osleap15?

 An osleap box reports correctly for me:
 docker run --shm-size=1024m -it opensuse/leap:leap-15 /bin/bash
 *ee4938c281e4:/ #* cat /etc/os-release
 NAME="openSUSE Leap"
 VERSION="15.0 Beta"
 ID="opensuse"
 ID_LIKE="suse"
 VERSION_ID="15.0"
 PRETTY_NAME="openSUSE Leap 15.0 Beta"
 ANSI_COLOR="0;32"
 CPE_NAME="cpe:/o:opensuse:leap:15.0"
 BUG_REPORT_URL="https://bugs.opensuse.org;
 HOME_URL="https://www.opensuse.org/;

 On Wed, Feb 27, 2019 at 1:12 PM Edward Warnicke 
 wrote:

> In cherry picking some fixes back to stable/1901, I've found that the
> builds for 1901 for OpenSuse Leap seem to be failing during install-deps:
>
> https://jenkins.fd.io/job/vpp-verify-1901-osleap15/77/console
>
> *10:50:21* No provider of 'libboost_thread1_68_0-devel-1.68.0' found.
>
>
> Which looks like there is some upstream issue with a dependency no
> longer being available for libboost.
>
> Digging deeper, it would appear that we are tripping on
> SUSE_NAME=Tumbleweed:
>
> https://github.com/FDio/vpp/blob/stable/1901/Makefile#L131
>
> ifeq ($(OS_ID),opensuse)
> ifeq ($(SUSE_NAME),Tumbleweed)
> RPM_SUSE_DEVEL_DEPS = libboost_headers1_68_0-devel-1.68.0
> libboost_thread1_68_0-devel-1.68.0 gcc
> RPM_SUSE_PYTHON_DEPS += python2-ply python2-virtualenv
> endif
> ifeq ($(SUSE_ID),15.0)
> RPM_SUSE_DEVEL_DEPS = libboost_headers-devel libboost_thread-devel gcc6
> else
> RPM_SUSE_DEVEL_DEPS += libboost_headers1_68_0-devel-1.68.0 gcc6
> RPM_SUSE_PYTHON_DEPS += python-virtualenv
> endif
> endif
>
> So for some reason, the servers are reporting SUSE_NAME=Tumbelweed,
> and being asked to install the wrong packages even though they are OSLEAP
> 15 boxes.  Note: this same Makefile fragment is identical on master where
> the corresponding jobs are succeeding.
>
> Do any of the OpenSuse folks have ideas as to what could be happening
> here?
>
> Ed
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#12366):
> https://lists.fd.io/g/vpp-dev/message/12366
> Mute This Topic: https://lists.fd.io/mt/30154873/1594641
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [
> pvi...@vinciconsulting.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
 -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>>
>> View/Reply Online (#12371): https://lists.fd.io/g/vpp-dev/message/12371
>> Mute This Topic: https://lists.fd.io/mt/30154873/675649
>> Group Owner: vpp-dev+ow...@lists.fd.io
>> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [e...@cisco.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>
>>
>>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12374): https://lists.fd.io/g/vpp-dev/message/12374
Mute This Topic: https://lists.fd.io/mt/30154873/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Re: [vpp-dev] OpenSuse builds failing for stable/1901

2019-02-27 Thread Paul Vinciguerra
Ok.

Let me know if I can do anything to help!

On Wed, Feb 27, 2019 at 3:09 PM Ed Kern (ejk)  wrote:

> thats a perfectly good and reasonable change and I support it..
>
> But that’s not the problem that the other ed is having right now.
>
> Ed
>
>
>
> On Feb 27, 2019, at 12:47 PM, Paul Vinciguerra 
> wrote:
>
> Ed,
>
> There is an issue.  I am testing a fix.
> See: https://gerrit.fd.io/r/#/c/17917/
>
> Paul
>
> On Wed, Feb 27, 2019 at 2:23 PM Ed Warnicke  wrote:
>
>> Paul,
>>
>> Good first thing to check... I've pushed
>> https://gerrit.fd.io/r/#/c/17916/
>>
>> to cause the opensuse jobs to cat the /etc/os-release as you suggested,
>> and rechecked: https://gerrit.fd.io/r/#/c/17884/
>> to see what happens :)
>>
>> Ed
>>
>> On Wed, Feb 27, 2019 at 12:48 PM Paul Vinciguerra <
>> pvi...@vinciconsulting.com> wrote:
>>
>>> Can we confirm that they are truly osleap15?
>>>
>>> An osleap box reports correctly for me:
>>> docker run --shm-size=1024m -it opensuse/leap:leap-15 /bin/bash
>>> *ee4938c281e4:/ #* cat /etc/os-release
>>> NAME="openSUSE Leap"
>>> VERSION="15.0 Beta"
>>> ID="opensuse"
>>> ID_LIKE="suse"
>>> VERSION_ID="15.0"
>>> PRETTY_NAME="openSUSE Leap 15.0 Beta"
>>> ANSI_COLOR="0;32"
>>> CPE_NAME="cpe:/o:opensuse:leap:15.0"
>>> BUG_REPORT_URL="https://bugs.opensuse.org;
>>> HOME_URL="https://www.opensuse.org/;
>>>
>>> On Wed, Feb 27, 2019 at 1:12 PM Edward Warnicke 
>>> wrote:
>>>
 In cherry picking some fixes back to stable/1901, I've found that the
 builds for 1901 for OpenSuse Leap seem to be failing during install-deps:

 https://jenkins.fd.io/job/vpp-verify-1901-osleap15/77/console

 *10:50:21* No provider of 'libboost_thread1_68_0-devel-1.68.0' found.


 Which looks like there is some upstream issue with a dependency no
 longer being available for libboost.

 Digging deeper, it would appear that we are tripping on
 SUSE_NAME=Tumbleweed:

 https://github.com/FDio/vpp/blob/stable/1901/Makefile#L131

 ifeq ($(OS_ID),opensuse)
 ifeq ($(SUSE_NAME),Tumbleweed)
 RPM_SUSE_DEVEL_DEPS = libboost_headers1_68_0-devel-1.68.0
 libboost_thread1_68_0-devel-1.68.0 gcc
 RPM_SUSE_PYTHON_DEPS += python2-ply python2-virtualenv
 endif
 ifeq ($(SUSE_ID),15.0)
 RPM_SUSE_DEVEL_DEPS = libboost_headers-devel libboost_thread-devel gcc6
 else
 RPM_SUSE_DEVEL_DEPS += libboost_headers1_68_0-devel-1.68.0 gcc6
 RPM_SUSE_PYTHON_DEPS += python-virtualenv
 endif
 endif

 So for some reason, the servers are reporting SUSE_NAME=Tumbelweed, and
 being asked to install the wrong packages even though they are OSLEAP 15
 boxes.  Note: this same Makefile fragment is identical on master where the
 corresponding jobs are succeeding.

 Do any of the OpenSuse folks have ideas as to what could be happening
 here?

 Ed

 -=-=-=-=-=-=-=-=-=-=-=-
 Links: You receive all messages sent to this group.

 View/Reply Online (#12366): https://lists.fd.io/g/vpp-dev/message/12366
 Mute This Topic: https://lists.fd.io/mt/30154873/1594641
 Group Owner: vpp-dev+ow...@lists.fd.io
 Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [
 pvi...@vinciconsulting.com]
 -=-=-=-=-=-=-=-=-=-=-=-

>>> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#12371): https://lists.fd.io/g/vpp-dev/message/12371
> Mute This Topic: https://lists.fd.io/mt/30154873/675649
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [e...@cisco.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12373): https://lists.fd.io/g/vpp-dev/message/12373
Mute This Topic: https://lists.fd.io/mt/30154873/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Re: [vpp-dev] OpenSuse builds failing for stable/1901

2019-02-27 Thread Ed Kern via Lists.Fd.Io
thats a perfectly good and reasonable change and I support it..

But that’s not the problem that the other ed is having right now.

Ed



On Feb 27, 2019, at 12:47 PM, Paul Vinciguerra 
mailto:pvi...@vinciconsulting.com>> wrote:

Ed,

There is an issue.  I am testing a fix.
See: https://gerrit.fd.io/r/#/c/17917/

Paul

On Wed, Feb 27, 2019 at 2:23 PM Ed Warnicke 
mailto:hagb...@gmail.com>> wrote:
Paul,

Good first thing to check... I've pushed
https://gerrit.fd.io/r/#/c/17916/

to cause the opensuse jobs to cat the /etc/os-release as you suggested, and 
rechecked: https://gerrit.fd.io/r/#/c/17884/
to see what happens :)

Ed

On Wed, Feb 27, 2019 at 12:48 PM Paul Vinciguerra 
mailto:pvi...@vinciconsulting.com>> wrote:
Can we confirm that they are truly osleap15?

An osleap box reports correctly for me:
docker run --shm-size=1024m -it opensuse/leap:leap-15 /bin/bash
ee4938c281e4:/ # cat /etc/os-release
NAME="openSUSE Leap"
VERSION="15.0 Beta"
ID="opensuse"
ID_LIKE="suse"
VERSION_ID="15.0"
PRETTY_NAME="openSUSE Leap 15.0 Beta"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:15.0"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/;

On Wed, Feb 27, 2019 at 1:12 PM Edward Warnicke 
mailto:hagb...@gmail.com>> wrote:
In cherry picking some fixes back to stable/1901, I've found that the builds 
for 1901 for OpenSuse Leap seem to be failing during install-deps:

https://jenkins.fd.io/job/vpp-verify-1901-osleap15/77/console


10:50:21 No provider of 'libboost_thread1_68_0-devel-1.68.0' found.


Which looks like there is some upstream issue with a dependency no longer being 
available for libboost.

Digging deeper, it would appear that we are tripping on SUSE_NAME=Tumbleweed:

https://github.com/FDio/vpp/blob/stable/1901/Makefile#L131

ifeq ($(OS_ID),opensuse)
ifeq ($(SUSE_NAME),Tumbleweed)
RPM_SUSE_DEVEL_DEPS = libboost_headers1_68_0-devel-1.68.0  
libboost_thread1_68_0-devel-1.68.0 gcc
RPM_SUSE_PYTHON_DEPS += python2-ply python2-virtualenv
endif
ifeq ($(SUSE_ID),15.0)
RPM_SUSE_DEVEL_DEPS = libboost_headers-devel libboost_thread-devel gcc6
else
RPM_SUSE_DEVEL_DEPS += libboost_headers1_68_0-devel-1.68.0 gcc6
RPM_SUSE_PYTHON_DEPS += python-virtualenv
endif
endif

So for some reason, the servers are reporting SUSE_NAME=Tumbelweed, and being 
asked to install the wrong packages even though they are OSLEAP 15 boxes.  
Note: this same Makefile fragment is identical on master where the 
corresponding jobs are succeeding.

Do any of the OpenSuse folks have ideas as to what could be happening here?

Ed

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12366): https://lists.fd.io/g/vpp-dev/message/12366
Mute This Topic: https://lists.fd.io/mt/30154873/1594641
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  
[pvi...@vinciconsulting.com]
-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12371): https://lists.fd.io/g/vpp-dev/message/12371
Mute This Topic: https://lists.fd.io/mt/30154873/675649
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  
[e...@cisco.com]
-=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12372): https://lists.fd.io/g/vpp-dev/message/12372
Mute This Topic: https://lists.fd.io/mt/30154873/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Re: [vpp-dev] OpenSuse builds failing for stable/1901

2019-02-27 Thread Paul Vinciguerra
Ed,

There is an issue.  I am testing a fix.
See: https://gerrit.fd.io/r/#/c/17917/

Paul

On Wed, Feb 27, 2019 at 2:23 PM Ed Warnicke  wrote:

> Paul,
>
> Good first thing to check... I've pushed
> https://gerrit.fd.io/r/#/c/17916/
>
> to cause the opensuse jobs to cat the /etc/os-release as you suggested,
> and rechecked: https://gerrit.fd.io/r/#/c/17884/
> to see what happens :)
>
> Ed
>
> On Wed, Feb 27, 2019 at 12:48 PM Paul Vinciguerra <
> pvi...@vinciconsulting.com> wrote:
>
>> Can we confirm that they are truly osleap15?
>>
>> An osleap box reports correctly for me:
>>
>> docker run --shm-size=1024m -it opensuse/leap:leap-15 /bin/bash
>>
>> *ee4938c281e4:/ #* cat /etc/os-release
>>
>> NAME="openSUSE Leap"
>>
>> VERSION="15.0 Beta"
>>
>> ID="opensuse"
>>
>> ID_LIKE="suse"
>>
>> VERSION_ID="15.0"
>>
>> PRETTY_NAME="openSUSE Leap 15.0 Beta"
>>
>> ANSI_COLOR="0;32"
>>
>> CPE_NAME="cpe:/o:opensuse:leap:15.0"
>>
>> BUG_REPORT_URL="https://bugs.opensuse.org;
>> HOME_URL="https://www.opensuse.org/;
>>
>> On Wed, Feb 27, 2019 at 1:12 PM Edward Warnicke 
>> wrote:
>>
>>> In cherry picking some fixes back to stable/1901, I've found that the
>>> builds for 1901 for OpenSuse Leap seem to be failing during install-deps:
>>>
>>> https://jenkins.fd.io/job/vpp-verify-1901-osleap15/77/console
>>>
>>> *10:50:21* No provider of 'libboost_thread1_68_0-devel-1.68.0' found.
>>>
>>>
>>> Which looks like there is some upstream issue with a dependency no
>>> longer being available for libboost.
>>>
>>> Digging deeper, it would appear that we are tripping on
>>> SUSE_NAME=Tumbleweed:
>>>
>>> https://github.com/FDio/vpp/blob/stable/1901/Makefile#L131
>>>
>>> ifeq ($(OS_ID),opensuse)
>>> ifeq ($(SUSE_NAME),Tumbleweed)
>>> RPM_SUSE_DEVEL_DEPS = libboost_headers1_68_0-devel-1.68.0
>>> libboost_thread1_68_0-devel-1.68.0 gcc
>>> RPM_SUSE_PYTHON_DEPS += python2-ply python2-virtualenv
>>> endif
>>> ifeq ($(SUSE_ID),15.0)
>>> RPM_SUSE_DEVEL_DEPS = libboost_headers-devel libboost_thread-devel gcc6
>>> else
>>> RPM_SUSE_DEVEL_DEPS += libboost_headers1_68_0-devel-1.68.0 gcc6
>>> RPM_SUSE_PYTHON_DEPS += python-virtualenv
>>> endif
>>> endif
>>>
>>> So for some reason, the servers are reporting SUSE_NAME=Tumbelweed, and
>>> being asked to install the wrong packages even though they are OSLEAP 15
>>> boxes.  Note: this same Makefile fragment is identical on master where the
>>> corresponding jobs are succeeding.
>>>
>>> Do any of the OpenSuse folks have ideas as to what could be happening
>>> here?
>>>
>>> Ed
>>>
>>> -=-=-=-=-=-=-=-=-=-=-=-
>>> Links: You receive all messages sent to this group.
>>>
>>> View/Reply Online (#12366): https://lists.fd.io/g/vpp-dev/message/12366
>>> Mute This Topic: https://lists.fd.io/mt/30154873/1594641
>>> Group Owner: vpp-dev+ow...@lists.fd.io
>>> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [
>>> pvi...@vinciconsulting.com]
>>> -=-=-=-=-=-=-=-=-=-=-=-
>>>
>>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12371): https://lists.fd.io/g/vpp-dev/message/12371
Mute This Topic: https://lists.fd.io/mt/30154873/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Re: [vpp-dev] OpenSuse builds failing for stable/1901

2019-02-27 Thread Ed Kern via Lists.Fd.Io
just so you know…it does already echo the version id and os id in the console 
log


16:47:00 + OS_VERSION_ID=15.0
16:47:00 + echo OS_ID: opensuse
16:47:00 OS_ID: opensuse
16:47:00 + echo OS_VERSION_ID: 15.0
16:47:00 OS_VERSION_ID: 15.0
16:47:00 + hostname
16:47:00 1f2fe1a3f253
16:47:00 + export CCACHE_DIR=/tm


Ed



On Feb 27, 2019, at 11:48 AM, Paul Vinciguerra 
mailto:pvi...@vinciconsulting.com>> wrote:

Can we confirm that they are truly osleap15?

An osleap box reports correctly for me:
docker run --shm-size=1024m -it opensuse/leap:leap-15 /bin/bash
ee4938c281e4:/ # cat /etc/os-release
NAME="openSUSE Leap"
VERSION="15.0 Beta"
ID="opensuse"
ID_LIKE="suse"
VERSION_ID="15.0"
PRETTY_NAME="openSUSE Leap 15.0 Beta"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:15.0"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/;

On Wed, Feb 27, 2019 at 1:12 PM Edward Warnicke 
mailto:hagb...@gmail.com>> wrote:
In cherry picking some fixes back to stable/1901, I've found that the builds 
for 1901 for OpenSuse Leap seem to be failing during install-deps:

https://jenkins.fd.io/job/vpp-verify-1901-osleap15/77/console


10:50:21 No provider of 'libboost_thread1_68_0-devel-1.68.0' found.


Which looks like there is some upstream issue with a dependency no longer being 
available for libboost.

Digging deeper, it would appear that we are tripping on SUSE_NAME=Tumbleweed:

https://github.com/FDio/vpp/blob/stable/1901/Makefile#L131

ifeq ($(OS_ID),opensuse)
ifeq ($(SUSE_NAME),Tumbleweed)
RPM_SUSE_DEVEL_DEPS = libboost_headers1_68_0-devel-1.68.0  
libboost_thread1_68_0-devel-1.68.0 gcc
RPM_SUSE_PYTHON_DEPS += python2-ply python2-virtualenv
endif
ifeq ($(SUSE_ID),15.0)
RPM_SUSE_DEVEL_DEPS = libboost_headers-devel libboost_thread-devel gcc6
else
RPM_SUSE_DEVEL_DEPS += libboost_headers1_68_0-devel-1.68.0 gcc6
RPM_SUSE_PYTHON_DEPS += python-virtualenv
endif
endif

So for some reason, the servers are reporting SUSE_NAME=Tumbelweed, and being 
asked to install the wrong packages even though they are OSLEAP 15 boxes.  
Note: this same Makefile fragment is identical on master where the 
corresponding jobs are succeeding.

Do any of the OpenSuse folks have ideas as to what could be happening here?

Ed

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12366): https://lists.fd.io/g/vpp-dev/message/12366
Mute This Topic: https://lists.fd.io/mt/30154873/1594641
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  
[pvi...@vinciconsulting.com]
-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12367): https://lists.fd.io/g/vpp-dev/message/12367
Mute This Topic: https://lists.fd.io/mt/30154873/675649
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  
[e...@cisco.com]
-=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12370): https://lists.fd.io/g/vpp-dev/message/12370
Mute This Topic: https://lists.fd.io/mt/30154873/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Re: [vpp-dev] OpenSuse builds failing for stable/1901

2019-02-27 Thread Ed Kern via Lists.Fd.Io
when i pull your change
i see a different makefile then what you pasted below….

ifeq ($(SUSE_ID),15.0)
RPM_SUSE_DEVEL_DEPS = libboost_headers1_68_0-devel-1.68.0  
libboost_thread1_68_0-devel-1.68.0 gcc6
RPM_SUSE_PYTHON_DEPS += python2-ply python2-virtualenv
else
RPM_SUSE_DEVEL_DEPS +


so that will fail…

Ed




On Feb 27, 2019, at 12:23 PM, Edward Warnicke 
mailto:hagb...@gmail.com>> wrote:

Paul,

Good first thing to check... I've pushed
https://gerrit.fd.io/r/#/c/17916/

to cause the opensuse jobs to cat the /etc/os-release as you suggested, and 
rechecked: https://gerrit.fd.io/r/#/c/17884/
to see what happens :)

Ed

On Wed, Feb 27, 2019 at 12:48 PM Paul Vinciguerra 
mailto:pvi...@vinciconsulting.com>> wrote:
Can we confirm that they are truly osleap15?

An osleap box reports correctly for me:
docker run --shm-size=1024m -it opensuse/leap:leap-15 /bin/bash
ee4938c281e4:/ # cat /etc/os-release
NAME="openSUSE Leap"
VERSION="15.0 Beta"
ID="opensuse"
ID_LIKE="suse"
VERSION_ID="15.0"
PRETTY_NAME="openSUSE Leap 15.0 Beta"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:15.0"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/;

On Wed, Feb 27, 2019 at 1:12 PM Edward Warnicke 
mailto:hagb...@gmail.com>> wrote:
In cherry picking some fixes back to stable/1901, I've found that the builds 
for 1901 for OpenSuse Leap seem to be failing during install-deps:

https://jenkins.fd.io/job/vpp-verify-1901-osleap15/77/console


10:50:21 No provider of 'libboost_thread1_68_0-devel-1.68.0' found.


Which looks like there is some upstream issue with a dependency no longer being 
available for libboost.

Digging deeper, it would appear that we are tripping on SUSE_NAME=Tumbleweed:

https://github.com/FDio/vpp/blob/stable/1901/Makefile#L131

ifeq ($(OS_ID),opensuse)
ifeq ($(SUSE_NAME),Tumbleweed)
RPM_SUSE_DEVEL_DEPS = libboost_headers1_68_0-devel-1.68.0  
libboost_thread1_68_0-devel-1.68.0 gcc
RPM_SUSE_PYTHON_DEPS += python2-ply python2-virtualenv
endif
ifeq ($(SUSE_ID),15.0)
RPM_SUSE_DEVEL_DEPS = libboost_headers-devel libboost_thread-devel gcc6
else
RPM_SUSE_DEVEL_DEPS += libboost_headers1_68_0-devel-1.68.0 gcc6
RPM_SUSE_PYTHON_DEPS += python-virtualenv
endif
endif

So for some reason, the servers are reporting SUSE_NAME=Tumbelweed, and being 
asked to install the wrong packages even though they are OSLEAP 15 boxes.  
Note: this same Makefile fragment is identical on master where the 
corresponding jobs are succeeding.

Do any of the OpenSuse folks have ideas as to what could be happening here?

Ed

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12366): https://lists.fd.io/g/vpp-dev/message/12366
Mute This Topic: https://lists.fd.io/mt/30154873/1594641
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  
[pvi...@vinciconsulting.com]
-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12368): https://lists.fd.io/g/vpp-dev/message/12368
Mute This Topic: https://lists.fd.io/mt/30154873/675649
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  
[e...@cisco.com]
-=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12369): https://lists.fd.io/g/vpp-dev/message/12369
Mute This Topic: https://lists.fd.io/mt/30154873/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Re: [vpp-dev] OpenSuse builds failing for stable/1901

2019-02-27 Thread Edward Warnicke
Paul,

Good first thing to check... I've pushed
https://gerrit.fd.io/r/#/c/17916/

to cause the opensuse jobs to cat the /etc/os-release as you suggested, and
rechecked: https://gerrit.fd.io/r/#/c/17884/
to see what happens :)

Ed

On Wed, Feb 27, 2019 at 12:48 PM Paul Vinciguerra <
pvi...@vinciconsulting.com> wrote:

> Can we confirm that they are truly osleap15?
>
> An osleap box reports correctly for me:
>
> docker run --shm-size=1024m -it opensuse/leap:leap-15 /bin/bash
>
> *ee4938c281e4:/ #* cat /etc/os-release
>
> NAME="openSUSE Leap"
>
> VERSION="15.0 Beta"
>
> ID="opensuse"
>
> ID_LIKE="suse"
>
> VERSION_ID="15.0"
>
> PRETTY_NAME="openSUSE Leap 15.0 Beta"
>
> ANSI_COLOR="0;32"
>
> CPE_NAME="cpe:/o:opensuse:leap:15.0"
>
> BUG_REPORT_URL="https://bugs.opensuse.org;
> HOME_URL="https://www.opensuse.org/;
>
> On Wed, Feb 27, 2019 at 1:12 PM Edward Warnicke  wrote:
>
>> In cherry picking some fixes back to stable/1901, I've found that the
>> builds for 1901 for OpenSuse Leap seem to be failing during install-deps:
>>
>> https://jenkins.fd.io/job/vpp-verify-1901-osleap15/77/console
>>
>> *10:50:21* No provider of 'libboost_thread1_68_0-devel-1.68.0' found.
>>
>>
>> Which looks like there is some upstream issue with a dependency no longer
>> being available for libboost.
>>
>> Digging deeper, it would appear that we are tripping on
>> SUSE_NAME=Tumbleweed:
>>
>> https://github.com/FDio/vpp/blob/stable/1901/Makefile#L131
>>
>> ifeq ($(OS_ID),opensuse)
>> ifeq ($(SUSE_NAME),Tumbleweed)
>> RPM_SUSE_DEVEL_DEPS = libboost_headers1_68_0-devel-1.68.0
>> libboost_thread1_68_0-devel-1.68.0 gcc
>> RPM_SUSE_PYTHON_DEPS += python2-ply python2-virtualenv
>> endif
>> ifeq ($(SUSE_ID),15.0)
>> RPM_SUSE_DEVEL_DEPS = libboost_headers-devel libboost_thread-devel gcc6
>> else
>> RPM_SUSE_DEVEL_DEPS += libboost_headers1_68_0-devel-1.68.0 gcc6
>> RPM_SUSE_PYTHON_DEPS += python-virtualenv
>> endif
>> endif
>>
>> So for some reason, the servers are reporting SUSE_NAME=Tumbelweed, and
>> being asked to install the wrong packages even though they are OSLEAP 15
>> boxes.  Note: this same Makefile fragment is identical on master where the
>> corresponding jobs are succeeding.
>>
>> Do any of the OpenSuse folks have ideas as to what could be happening
>> here?
>>
>> Ed
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>>
>> View/Reply Online (#12366): https://lists.fd.io/g/vpp-dev/message/12366
>> Mute This Topic: https://lists.fd.io/mt/30154873/1594641
>> Group Owner: vpp-dev+ow...@lists.fd.io
>> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [
>> pvi...@vinciconsulting.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12368): https://lists.fd.io/g/vpp-dev/message/12368
Mute This Topic: https://lists.fd.io/mt/30154873/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Re: [vpp-dev] OpenSuse builds failing for stable/1901

2019-02-27 Thread Paul Vinciguerra
Can we confirm that they are truly osleap15?

An osleap box reports correctly for me:

docker run --shm-size=1024m -it opensuse/leap:leap-15 /bin/bash

*ee4938c281e4:/ #* cat /etc/os-release

NAME="openSUSE Leap"

VERSION="15.0 Beta"

ID="opensuse"

ID_LIKE="suse"

VERSION_ID="15.0"

PRETTY_NAME="openSUSE Leap 15.0 Beta"

ANSI_COLOR="0;32"

CPE_NAME="cpe:/o:opensuse:leap:15.0"

BUG_REPORT_URL="https://bugs.opensuse.org;
HOME_URL="https://www.opensuse.org/;

On Wed, Feb 27, 2019 at 1:12 PM Edward Warnicke  wrote:

> In cherry picking some fixes back to stable/1901, I've found that the
> builds for 1901 for OpenSuse Leap seem to be failing during install-deps:
>
> https://jenkins.fd.io/job/vpp-verify-1901-osleap15/77/console
>
> *10:50:21* No provider of 'libboost_thread1_68_0-devel-1.68.0' found.
>
>
> Which looks like there is some upstream issue with a dependency no longer
> being available for libboost.
>
> Digging deeper, it would appear that we are tripping on
> SUSE_NAME=Tumbleweed:
>
> https://github.com/FDio/vpp/blob/stable/1901/Makefile#L131
>
> ifeq ($(OS_ID),opensuse)
> ifeq ($(SUSE_NAME),Tumbleweed)
> RPM_SUSE_DEVEL_DEPS = libboost_headers1_68_0-devel-1.68.0
> libboost_thread1_68_0-devel-1.68.0 gcc
> RPM_SUSE_PYTHON_DEPS += python2-ply python2-virtualenv
> endif
> ifeq ($(SUSE_ID),15.0)
> RPM_SUSE_DEVEL_DEPS = libboost_headers-devel libboost_thread-devel gcc6
> else
> RPM_SUSE_DEVEL_DEPS += libboost_headers1_68_0-devel-1.68.0 gcc6
> RPM_SUSE_PYTHON_DEPS += python-virtualenv
> endif
> endif
>
> So for some reason, the servers are reporting SUSE_NAME=Tumbelweed, and
> being asked to install the wrong packages even though they are OSLEAP 15
> boxes.  Note: this same Makefile fragment is identical on master where the
> corresponding jobs are succeeding.
>
> Do any of the OpenSuse folks have ideas as to what could be happening here?
>
> Ed
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#12366): https://lists.fd.io/g/vpp-dev/message/12366
> Mute This Topic: https://lists.fd.io/mt/30154873/1594641
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [
> pvi...@vinciconsulting.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12367): https://lists.fd.io/g/vpp-dev/message/12367
Mute This Topic: https://lists.fd.io/mt/30154873/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


[vpp-dev] OpenSuse builds failing for stable/1901

2019-02-27 Thread Edward Warnicke
In cherry picking some fixes back to stable/1901, I've found that the
builds for 1901 for OpenSuse Leap seem to be failing during install-deps:

https://jenkins.fd.io/job/vpp-verify-1901-osleap15/77/console

*10:50:21* No provider of 'libboost_thread1_68_0-devel-1.68.0' found.


Which looks like there is some upstream issue with a dependency no longer
being available for libboost.

Digging deeper, it would appear that we are tripping on
SUSE_NAME=Tumbleweed:

https://github.com/FDio/vpp/blob/stable/1901/Makefile#L131

ifeq ($(OS_ID),opensuse)
ifeq ($(SUSE_NAME),Tumbleweed)
RPM_SUSE_DEVEL_DEPS = libboost_headers1_68_0-devel-1.68.0
libboost_thread1_68_0-devel-1.68.0 gcc
RPM_SUSE_PYTHON_DEPS += python2-ply python2-virtualenv
endif
ifeq ($(SUSE_ID),15.0)
RPM_SUSE_DEVEL_DEPS = libboost_headers-devel libboost_thread-devel gcc6
else
RPM_SUSE_DEVEL_DEPS += libboost_headers1_68_0-devel-1.68.0 gcc6
RPM_SUSE_PYTHON_DEPS += python-virtualenv
endif
endif

So for some reason, the servers are reporting SUSE_NAME=Tumbelweed, and
being asked to install the wrong packages even though they are OSLEAP 15
boxes.  Note: this same Makefile fragment is identical on master where the
corresponding jobs are succeeding.

Do any of the OpenSuse folks have ideas as to what could be happening here?

Ed
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12366): https://lists.fd.io/g/vpp-dev/message/12366
Mute This Topic: https://lists.fd.io/mt/30154873/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Re: [vpp-dev] New vpp project committer nomination: Paul Vinciguerra

2019-02-27 Thread Florin Coras
+1

Florin

> On Feb 27, 2019, at 5:20 AM, Dave Barach via Lists.Fd.Io 
>  wrote:
> 
> +1... Dave
>  
> From: vpp-dev@lists.fd.io   > On Behalf Of Dave Barach via Lists.Fd.Io
> Sent: Wednesday, February 27, 2019 7:38 AM
> To: vpp-dev@lists.fd.io 
> Cc: vpp-dev@lists.fd.io 
> Subject: [vpp-dev] New vpp project committer nomination: Paul Vinciguerra
>  
> In view of significant code contributions to the vpp project - see below - 
> I'm pleased to nominate Paul Vinciguerra as a vpp project committer. I have 
> high confidence that he'll be a major asset to the project in a committer 
> role.  
>  
> Paul has contributed 100 merged patches, concentrating on the “make test” .py 
> framework. 
> Seehttps://gerrit.fd.io/r/#/q/status:merged+owner:%22Paul+Vinciguerra+%253Cpvinci%2540vinciconsulting.com%253E%22
>  
> 
>  
> Committers, please vote (+1, 0, -1) on vpp-dev@lists.fd.io 
> . We'll need a recorded vote so that the TSC will 
> approve Paul’s nomination.
>  
> If at all possible please vote today, February 27, 2019 so we can add Paul’s 
> nomination to tomorrow’s TSC agenda for final approval.
>  
> Thanks... Dave
>  
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#12356): https://lists.fd.io/g/vpp-dev/message/12356 
> 
> Mute This Topic: https://lists.fd.io/mt/30151621/675152 
> 
> Group Owner: vpp-dev+ow...@lists.fd.io 
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub 
>   [fcoras.li...@gmail.com 
> ]
> -=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12365): https://lists.fd.io/g/vpp-dev/message/12365
Mute This Topic: https://lists.fd.io/mt/30151621/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Re: [vpp-dev] [csit-dev] Jenkins infra outage - 100% jobs queued, VPN access very slow

2019-02-27 Thread Ed Kern via Lists.Fd.Io
update:

mnaser  (vex host )  did a ‘live migration’  of the 
jenkins.fd.io  ’server’  taking RTT from >6 seconds back 
down
to the @100ms range.   As a result jobs are starting up again and the queue is 
grinding through the backlog and new
jobs.

Im not currently seeing the same delay on/towards other hosted services  
gerrit/nexus etc.

Ill be watching it closely the next few hours but please let me know if you see 
any unusual errors.

thanks,

Ed



On Feb 27, 2019, at 8:34 AM, Ed Kern via Lists.Fd.Io 
mailto:ejk=cisco@lists.fd.io>> wrote:

fyi to vpp-dev as well..


debugging with vexxhost

Begin forwarded message:

From: "Peter Mikus via Lists.Fd.Io" 
mailto:pmikus=cisco@lists.fd.io>>
Subject: [csit-dev] Jenkins infra outage - 100% jobs queued, VPN access very 
slow
Date: February 27, 2019 at 8:32:50 AM MST
To: "helpd...@fd.io" 
mailto:helpd...@fd.io>>
Cc: csit-...@lists.fd.io
Reply-To: pmi...@cisco.com

Hello team,

We are observing jobs queueing in Jenkins.fd.io and also 
the VPN access to infra is very slow.

Can you please investigate?

ping 10.30.51.50
PING 10.30.51.50 (10.30.51.50) 56(84) bytes of data.
64 bytes from 10.30.51.50: icmp_seq=1 ttl=62 time=9961 ms
64 bytes from 10.30.51.50: icmp_seq=2 ttl=62 time=8928 ms
64 bytes from 10.30.51.50: icmp_seq=3 ttl=62 time=7907 ms
64 bytes from 10.30.51.50: icmp_seq=4 ttl=62 time=6887 ms
64 bytes from 10.30.51.50: icmp_seq=5 ttl=62 time=5863 ms
64 bytes from 10.30.51.50: icmp_seq=6 ttl=62 time=4834 ms
64 bytes from 10.30.51.50: icmp_seq=7 ttl=62 time=3809 ms
64 bytes from 10.30.51.50: icmp_seq=8 ttl=62 time=2790 ms
64 bytes from 10.30.51.50: icmp_seq=9 ttl=62 time=1762 ms

Thank you.

Peter Mikus
Engineer – Software
Cisco Systems Limited


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#3348): https://lists.fd.io/g/csit-dev/message/3348
Mute This Topic: https://lists.fd.io/mt/30153144/675649
Group Owner: csit-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/csit-dev/unsub  
[e...@cisco.com]
-=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12363): https://lists.fd.io/g/vpp-dev/message/12363
Mute This Topic: https://lists.fd.io/mt/30153159/675649
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  
[e...@cisco.com]
-=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12364): https://lists.fd.io/g/vpp-dev/message/12364
Mute This Topic: https://lists.fd.io/mt/30153159/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


[vpp-dev] [csit-dev] Jenkins infra outage - 100% jobs queued, VPN access very slow

2019-02-27 Thread Ed Kern via Lists.Fd.Io
fyi to vpp-dev as well..


debugging with vexxhost

Begin forwarded message:

From: "Peter Mikus via Lists.Fd.Io" 
mailto:pmikus=cisco@lists.fd.io>>
Subject: [csit-dev] Jenkins infra outage - 100% jobs queued, VPN access very 
slow
Date: February 27, 2019 at 8:32:50 AM MST
To: "helpd...@fd.io" 
mailto:helpd...@fd.io>>
Cc: csit-...@lists.fd.io
Reply-To: pmi...@cisco.com

Hello team,

We are observing jobs queueing in Jenkins.fd.io and also 
the VPN access to infra is very slow.

Can you please investigate?

ping 10.30.51.50
PING 10.30.51.50 (10.30.51.50) 56(84) bytes of data.
64 bytes from 10.30.51.50: icmp_seq=1 ttl=62 time=9961 ms
64 bytes from 10.30.51.50: icmp_seq=2 ttl=62 time=8928 ms
64 bytes from 10.30.51.50: icmp_seq=3 ttl=62 time=7907 ms
64 bytes from 10.30.51.50: icmp_seq=4 ttl=62 time=6887 ms
64 bytes from 10.30.51.50: icmp_seq=5 ttl=62 time=5863 ms
64 bytes from 10.30.51.50: icmp_seq=6 ttl=62 time=4834 ms
64 bytes from 10.30.51.50: icmp_seq=7 ttl=62 time=3809 ms
64 bytes from 10.30.51.50: icmp_seq=8 ttl=62 time=2790 ms
64 bytes from 10.30.51.50: icmp_seq=9 ttl=62 time=1762 ms

Thank you.

Peter Mikus
Engineer – Software
Cisco Systems Limited


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#3348): https://lists.fd.io/g/csit-dev/message/3348
Mute This Topic: https://lists.fd.io/mt/30153144/675649
Group Owner: csit-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/csit-dev/unsub  
[e...@cisco.com]
-=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12363): https://lists.fd.io/g/vpp-dev/message/12363
Mute This Topic: https://lists.fd.io/mt/30153159/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Re: [vpp-dev] VPP 19.04 Program Plan Deliverables

2019-02-27 Thread Honnappa Nagarahalli
Hi Dave,
   Is there any deadline for proposing the deliverables? (F0?)

Thank you,
Honnappa


From: vpp-dev@lists.fd.io  On Behalf Of Dave Wallace
Sent: Monday, February 25, 2019 6:47 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] VPP 19.04 Program Plan Deliverables

Folks,

Please add the deliverables that you are planning to develop for the VPP 19.04 
release to the "Deliverables" section of the VPP 19.04 Program Plan.

https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_19.04#Release_Deliverables

Thanks,
-daw-
"Your Friendly VPP 19.04 Program Manager"
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12362): https://lists.fd.io/g/vpp-dev/message/12362
Mute This Topic: https://lists.fd.io/mt/30037464/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Re: [vpp-dev] New vpp project committer nomination: Paul Vinciguerra

2019-02-27 Thread Dave Wallace

+1

On 2/27/19 8:20 AM, Dave Barach via Lists.Fd.Io wrote:


+1... Dave

*From:* vpp-dev@lists.fd.io  *On Behalf Of *Dave 
Barach via Lists.Fd.Io

*Sent:* Wednesday, February 27, 2019 7:38 AM
*To:* vpp-dev@lists.fd.io
*Cc:* vpp-dev@lists.fd.io
*Subject:* [vpp-dev] New vpp project committer nomination: Paul 
Vinciguerra


In view of significant code contributions to the vpp project - see 
below - I'm pleased to nominate Paul Vinciguerra as a vpp project 
committer. I have high confidence that he'll be a major asset to the 
project in a committer role.


Paul has contributed 100 merged patches, concentrating on the “make 
test” .py framework. See 
https://gerrit.fd.io/r/#/q/status:merged+owner:%22Paul+Vinciguerra+%253Cpvinci%2540vinciconsulting.com%253E%22


Committers, please vote (+1, 0, -1) on vpp-dev@lists.fd.io 
. We'll need a recorded vote so that the 
TSC will approve Paul’s nomination.


If at all possible please vote _today_, February 27, 2019 so we can 
add Paul’s nomination to tomorrow’s TSC agenda for final approval.


Thanks... Dave


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12356): https://lists.fd.io/g/vpp-dev/message/12356
Mute This Topic: https://lists.fd.io/mt/30151621/675079
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [dwallac...@gmail.com]
-=-=-=-=-=-=-=-=-=-=-=-


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12361): https://lists.fd.io/g/vpp-dev/message/12361
Mute This Topic: https://lists.fd.io/mt/30151621/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Re: [vpp-dev] New vpp project committer nomination: Paul Vinciguerra

2019-02-27 Thread John Lo (loj) via Lists.Fd.Io
+1 from me.  -John

From: vpp-dev@lists.fd.io  On Behalf Of Dave Barach via 
Lists.Fd.Io
Sent: Wednesday, February 27, 2019 7:38 AM
To: vpp-dev@lists.fd.io
Cc: vpp-dev@lists.fd.io
Subject: [vpp-dev] New vpp project committer nomination: Paul Vinciguerra

In view of significant code contributions to the vpp project - see below - I'm 
pleased to nominate Paul Vinciguerra as a vpp project committer. I have high 
confidence that he'll be a major asset to the project in a committer role.

Paul has contributed 100 merged patches, concentrating on the "make test" .py 
framework. See 
https://gerrit.fd.io/r/#/q/status:merged+owner:%22Paul+Vinciguerra+%253Cpvinci%2540vinciconsulting.com%253E%22

Committers, please vote (+1, 0, -1) on 
vpp-dev@lists.fd.io. We'll need a recorded vote so 
that the TSC will approve Paul's nomination.

If at all possible please vote today, February 27, 2019 so we can add Paul's 
nomination to tomorrow's TSC agenda for final approval.

Thanks... Dave

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12360): https://lists.fd.io/g/vpp-dev/message/12360
Mute This Topic: https://lists.fd.io/mt/30151621/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Re: [vpp-dev] New vpp project committer nomination: Paul Vinciguerra

2019-02-27 Thread Sergio G.M.
+1

Cheers,
Sergio

On Wed, Feb 27, 2019 at 2:21 PM Damjan Marion via Lists.Fd.Io  wrote:

> +1
>
> On 27 Feb 2019, at 14:20, Dave Barach via Lists.Fd.Io <
> dbarach=cisco@lists.fd.io> wrote:
>
> +1... Dave
>
> *From:* vpp-dev@lists.fd.io  *On Behalf Of *Dave
> Barach via Lists.Fd.Io
> *Sent:* Wednesday, February 27, 2019 7:38 AM
> *To:* vpp-dev@lists.fd.io
> *Cc:* vpp-dev@lists.fd.io
> *Subject:* [vpp-dev] New vpp project committer nomination: Paul
> Vinciguerra
>
> In view of significant code contributions to the vpp project - see below -
> I'm pleased to nominate Paul Vinciguerra as a vpp project committer. I have
> high confidence that he'll be a major asset to the project in a committer
> role.
>
> Paul has contributed 100 merged patches, concentrating on the “make test”
> .py framework. See
> https://gerrit.fd.io/r/#/q/status:merged+owner:%22Paul+Vinciguerra+%253Cpvinci%2540vinciconsulting.com%253E%22
>
> Committers, please vote (+1, 0, -1) on vpp-dev@lists.fd.io. We'll need a
> recorded vote so that the TSC will approve Paul’s nomination.
>
> If at all possible please vote *today*, February 27, 2019 so we can add
> Paul’s nomination to tomorrow’s TSC agenda for final approval.
>
> Thanks... Dave
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#12356): https://lists.fd.io/g/vpp-dev/message/12356
> Mute This Topic: https://lists.fd.io/mt/30151621/675642
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [dmar...@me.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
> --
> Damjan
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#12357): https://lists.fd.io/g/vpp-dev/message/12357
> Mute This Topic: https://lists.fd.io/mt/30151621/682142
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [
> sergio.gonzalez.mon...@outlook.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12359): https://lists.fd.io/g/vpp-dev/message/12359
Mute This Topic: https://lists.fd.io/mt/30151621/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Re: [vpp-dev] New vpp project committer nomination: Paul Vinciguerra

2019-02-27 Thread Edward Warnicke
+1

On Wed, Feb 27, 2019 at 7:21 AM Damjan Marion via Lists.Fd.Io  wrote:

> +1
>
> On 27 Feb 2019, at 14:20, Dave Barach via Lists.Fd.Io <
> dbarach=cisco@lists.fd.io> wrote:
>
> +1... Dave
>
> *From:* vpp-dev@lists.fd.io  *On Behalf Of *Dave
> Barach via Lists.Fd.Io
> *Sent:* Wednesday, February 27, 2019 7:38 AM
> *To:* vpp-dev@lists.fd.io
> *Cc:* vpp-dev@lists.fd.io
> *Subject:* [vpp-dev] New vpp project committer nomination: Paul
> Vinciguerra
>
> In view of significant code contributions to the vpp project - see below -
> I'm pleased to nominate Paul Vinciguerra as a vpp project committer. I have
> high confidence that he'll be a major asset to the project in a committer
> role.
>
> Paul has contributed 100 merged patches, concentrating on the “make test”
> .py framework. See
> https://gerrit.fd.io/r/#/q/status:merged+owner:%22Paul+Vinciguerra+%253Cpvinci%2540vinciconsulting.com%253E%22
>
> Committers, please vote (+1, 0, -1) on vpp-dev@lists.fd.io. We'll need a
> recorded vote so that the TSC will approve Paul’s nomination.
>
> If at all possible please vote *today*, February 27, 2019 so we can add
> Paul’s nomination to tomorrow’s TSC agenda for final approval.
>
> Thanks... Dave
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#12356): https://lists.fd.io/g/vpp-dev/message/12356
> Mute This Topic: https://lists.fd.io/mt/30151621/675642
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [dmar...@me.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
> --
> Damjan
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#12357): https://lists.fd.io/g/vpp-dev/message/12357
> Mute This Topic: https://lists.fd.io/mt/30151621/464962
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [hagb...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12358): https://lists.fd.io/g/vpp-dev/message/12358
Mute This Topic: https://lists.fd.io/mt/30151621/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Re: [vpp-dev] New vpp project committer nomination: Paul Vinciguerra

2019-02-27 Thread Damjan Marion via Lists.Fd.Io
+1

> On 27 Feb 2019, at 14:20, Dave Barach via Lists.Fd.Io 
>  wrote:
> 
> +1... Dave
>  
> From: vpp-dev@lists.fd.io   > On Behalf Of Dave Barach via Lists.Fd.Io
> Sent: Wednesday, February 27, 2019 7:38 AM
> To: vpp-dev@lists.fd.io 
> Cc: vpp-dev@lists.fd.io 
> Subject: [vpp-dev] New vpp project committer nomination: Paul Vinciguerra
>  
> In view of significant code contributions to the vpp project - see below - 
> I'm pleased to nominate Paul Vinciguerra as a vpp project committer. I have 
> high confidence that he'll be a major asset to the project in a committer 
> role.  
>  
> Paul has contributed 100 merged patches, concentrating on the “make test” .py 
> framework. 
> Seehttps://gerrit.fd.io/r/#/q/status:merged+owner:%22Paul+Vinciguerra+%253Cpvinci%2540vinciconsulting.com%253E%22
>  
> 
>  
> Committers, please vote (+1, 0, -1) on vpp-dev@lists.fd.io 
> . We'll need a recorded vote so that the TSC will 
> approve Paul’s nomination.
>  
> If at all possible please vote today, February 27, 2019 so we can add Paul’s 
> nomination to tomorrow’s TSC agenda for final approval.
>  
> Thanks... Dave
>  
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#12356): https://lists.fd.io/g/vpp-dev/message/12356 
> 
> Mute This Topic: https://lists.fd.io/mt/30151621/675642 
> 
> Group Owner: vpp-dev+ow...@lists.fd.io 
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub 
>   [dmar...@me.com 
> ]
> -=-=-=-=-=-=-=-=-=-=-=-

-- 
Damjan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12357): https://lists.fd.io/g/vpp-dev/message/12357
Mute This Topic: https://lists.fd.io/mt/30151621/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Re: [vpp-dev] New vpp project committer nomination: Paul Vinciguerra

2019-02-27 Thread Dave Barach via Lists.Fd.Io
+1... Dave

From: vpp-dev@lists.fd.io  On Behalf Of Dave Barach via 
Lists.Fd.Io
Sent: Wednesday, February 27, 2019 7:38 AM
To: vpp-dev@lists.fd.io
Cc: vpp-dev@lists.fd.io
Subject: [vpp-dev] New vpp project committer nomination: Paul Vinciguerra

In view of significant code contributions to the vpp project - see below - I'm 
pleased to nominate Paul Vinciguerra as a vpp project committer. I have high 
confidence that he'll be a major asset to the project in a committer role.

Paul has contributed 100 merged patches, concentrating on the "make test" .py 
framework. See 
https://gerrit.fd.io/r/#/q/status:merged+owner:%22Paul+Vinciguerra+%253Cpvinci%2540vinciconsulting.com%253E%22

Committers, please vote (+1, 0, -1) on 
vpp-dev@lists.fd.io. We'll need a recorded vote so 
that the TSC will approve Paul's nomination.

If at all possible please vote today, February 27, 2019 so we can add Paul's 
nomination to tomorrow's TSC agenda for final approval.

Thanks... Dave

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12356): https://lists.fd.io/g/vpp-dev/message/12356
Mute This Topic: https://lists.fd.io/mt/30151621/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Re: [vpp-dev] New vpp project committer nomination: Paul Vinciguerra

2019-02-27 Thread Ole Troan


> On 27 Feb 2019, at 13:37, Dave Barach via Lists.Fd.Io 
>  wrote:
> 
> In view of significant code contributions to the vpp project - see below - 
> I'm pleased to nominate Paul Vinciguerra as a vpp project committer. I have 
> high confidence that he'll be a major asset to the project in a committer 
> role.  
>  
> Paul has contributed 100 merged patches, concentrating on the “make test” .py 
> framework. See 
> https://gerrit.fd.io/r/#/q/status:merged+owner:%22Paul+Vinciguerra+%253Cpvinci%2540vinciconsulting.com%253E%22
>  
> Committers, please vote (+1, 0, -1) on vpp-dev@lists.fd.io. We'll need a 
> recorded vote so that the TSC will approve Paul’s nomination.

+1

Cheers,
Ole

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12355): https://lists.fd.io/g/vpp-dev/message/12355
Mute This Topic: https://lists.fd.io/mt/30151621/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


[vpp-dev] New vpp project committer nomination: Paul Vinciguerra

2019-02-27 Thread Dave Barach via Lists.Fd.Io
In view of significant code contributions to the vpp project - see below - I'm 
pleased to nominate Paul Vinciguerra as a vpp project committer. I have high 
confidence that he'll be a major asset to the project in a committer role.

Paul has contributed 100 merged patches, concentrating on the "make test" .py 
framework. See 
https://gerrit.fd.io/r/#/q/status:merged+owner:%22Paul+Vinciguerra+%253Cpvinci%2540vinciconsulting.com%253E%22

Committers, please vote (+1, 0, -1) on vpp-dev@lists.fd.io. We'll need a 
recorded vote so that the TSC will approve Paul's nomination.

If at all possible please vote today, February 27, 2019 so we can add Paul's 
nomination to tomorrow's TSC agenda for final approval.

Thanks... Dave

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12354): https://lists.fd.io/g/vpp-dev/message/12354
Mute This Topic: https://lists.fd.io/mt/30151621/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


[vpp-dev] Inserting a node into ICMP path

2019-02-27 Thread Raj
Hello all,

To get a better understanding of DPO and feature arc, I am attempting
to insert a node "ip4-my-node" before  ip4-load-balance. So the ICMP
flow would be like

ip4-icmp-input->ip4-icmp-echo-request->my_node->ip4-load-balance->ip4-rewrite->..

For achieving this, I have created a DPO instance similar to
load-balance and in the ip4-icmp-echo-request node added the
following:

   .next_nodes = {
-[0] = "ip4-load-balance",
+[0] = "ip4-my-node",

But after changing this, the flow is still happening from
ip4-icmp-echo-request->ip4-load-balance, and packets are not hitting
ip4-my-node.

Do I have to make any other change apart from what I have already done
insert the ip4-my-node into the path?

Thanks and Regards,

Raj
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12353): https://lists.fd.io/g/vpp-dev/message/12353
Mute This Topic: https://lists.fd.io/mt/30151551/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Re: [vpp-dev] FD.io Maintenance: 2019-02-26 @ 2000 UTC (12:00pm PST) - 0000 UTC (4:00pm PST)

2019-02-27 Thread Anton Baranov
Maintenance is now completed

On Tue, Feb 26, 2019, 14:00 Vanessa Valderrama <
vvalderr...@linuxfoundation.org> wrote:

> Jenkins has been placed in shut down mode. We'll terminate any jobs not
> complete in one hour.
>
> Thank you,
> Vanessa
>
> On Feb 26, 2019, at 11:05 AM, Vanessa Valderrama <
> vvalderr...@linuxfoundation.org> wrote:
>>
>> Reminder today is FD.io system maintenance. We'll be putting Jenkins into
>> shutdown mode in one hour.
>> Thank you,
>> Vanessa
>>
>> On 02/25/2019 11:15 AM, Vanessa Valderrama wrote:
>>
>> Remind FD.io system maintenance is scheduled for tomorrow @ 2000 UTC
>>
>> *What:*
>>
>> FD.io system maintenance
>>
>>- Jenkins resizing, security patch upgrade, and OS updates
>>- Nexus upgrade and OS updates
>>- Gerrit upgrade and OS updates
>>- JIRA upgrade and OS updates
>>- Sonar upgrade and OS updates
>>- OpenGrok OS updates
>>
>> *When:*
>>
>> 2019-02-26 @ 2000 UTC (12:00pm PST) -  UTC (4:00pm PST)
>>
>> *Impact:*
>>
>> The maintenance will require a reboot of each FD.io system.  The
>> following systems will be impacted:
>>
>>- Jenkins production
>>- Jenkins sandbox
>>- Nexus
>>- Gerrit
>>- JIRA
>>- Sonar
>>- OpenGrok
>>
>> *Why:*
>> The Jenkins resizing is to resolve gateway timeout errors causing build
>> failures. The rest of the system maintenance is standard LF maintenance
>>
>>
>>
>>
>> --
Anton Baranov
Systems and Network Administrator
The Linux Foundation
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12352): https://lists.fd.io/g/vpp-dev/message/12352
Mute This Topic: https://lists.fd.io/mt/29900552/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


[vpp-dev] Problem with VPPSB compilation

2019-02-27 Thread Mostafa Salari
Hi,
I have some problems with compiling VPP with router plugin.
*1. I get the following error:*
/root/iliar/vpp/build-data/../router/router/tap_inject_netlink.c:18:10:
fatal error: librtnl/netns.h: No such file or directory
 #include 
  ^
compilation terminated.
Makefile:476: recipe for target 'router/tap_inject_netlink.lo' failed
make[1]: *** [router/tap_inject_netlink.lo] Error 1
make[1]: *** Waiting for unfinished jobs
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:--
 0/root/iliar/vpp/build-data/../router/router/tap_inject_node.c: In
function ‘tap_inject_tap_send_buffer’:
/root/iliar/vpp/build-data/../router/router/tap_inject_node.c:45:13: error:
implicit declaration of function ‘writev’; did you mean ‘write’?
[-Werror=implicit-function-declaration]
   n_bytes = writev (fd, , 1);
 ^~
 write
/root/iliar/vpp/build-data/../router/router/tap_inject_node.c: In function
‘tap_rx’:
/root/iliar/vpp/build-data/../router/router/tap_inject_node.c:231:13:
error: implicit declaration of function ‘readv’; did you mean ‘read’?
[-Werror=implicit-function-declaration]
   n_bytes = readv (fd, iov, MTU_BUFFERS);
 ^
 read
cc1: all warnings being treated as errors

2. How can I to wipe previous failed makes, completely! It seems that make
wipe-release option is removed!

3. What version of VPP is consistent with the last version of VPPSB?

4. Is there any alternative for VPPSB that can be used to integrate VPP
with Linux based control planes, i.e. Quagga / FRR ?

Thanks a lot
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12351): https://lists.fd.io/g/vpp-dev/message/12351
Mute This Topic: https://lists.fd.io/mt/30151521/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-