|
Re: FD.io Maintenance: 2019-10-23 1700 UTC to 2100 UTC
The migration went much quicker towards the end. Maintenance is complete. All systems are available. Please open a ticket at support.linuxfoundation.org if you experience any issues.
The migration went much quicker towards the end. Maintenance is complete. All systems are available. Please open a ticket at support.linuxfoundation.org if you experience any issues.
|
By
Vanessa Valderrama
·
#1147
·
|
|
Re: FD.io Maintenance: 2019-10-23 1700 UTC to 2100 UTC
We need to extend the maintenance window until 2300 to allow the volume migration to complete.
We need to extend the maintenance window until 2300 to allow the volume migration to complete.
|
By
Vanessa Valderrama
·
#1146
·
|
|
Re: FD.io Maintenance: 2019-10-23 1700 UTC to 2100 UTC
Jenkins has been placed in shtudown mode in preparation for maintenance.
Jenkins has been placed in shtudown mode in preparation for maintenance.
|
By
Vanessa Valderrama
·
#1145
·
|
|
Re: FD.io Maintenance: 2019-10-23 1700 UTC to 2100 UTC
Maintenance reminder
By
Vanessa Valderrama
·
#1144
·
|
|
Catch the OVP Webinar on Tuesday, Oct 22, 10:00 AM PT
LFN Community:
For those not yet familiar, the OPNFV Verification Program (OVP) is an open source, community-led compliance and verification program to demonstrate the readiness and availability of
LFN Community:
For those not yet familiar, the OPNFV Verification Program (OVP) is an open source, community-led compliance and verification program to demonstrate the readiness and availability of
|
By
Brandon Wick <bwick@...>
·
#1143
·
|
|
FD.io Nexus Maintenance: 2019-10-23 1700 UTC to 2100 UTC
What:
LF will be performing standard system maintenance and a Jenkins migration
Jenkins
Migrate to two new SSD volumes
OS updates
What:
LF will be performing standard system maintenance and a Jenkins migration
Jenkins
Migrate to two new SSD volumes
OS updates
|
By
Vanessa Valderrama
·
#1142
·
|
|
Re: Scapy licensing issue in FD.io projects [Was: TRex distribution and licensing of external libraries]
>only discovering this now.
Not sure if it is relevant, but scapy linking has been introduced
to TRex [20], CSIT [21] and VPP [22] in 2016
(although for CSIT it was the first real commit in the
>only discovering this now.
Not sure if it is relevant, but scapy linking has been introduced
to TRex [20], CSIT [21] and VPP [22] in 2016
(although for CSIT it was the first real commit in the
|
By
Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco)
·
#1141
·
|
|
Scapy licensing issue in FD.io projects [Was: TRex distribution and licensing of external libraries]
Correcting the email subject to make it clear it’s related to Scapy licensing agenda topic for today’s FD.io TSC meeting.
Cheers,
-Maciek
Correcting the email subject to make it clear it’s related to Scapy licensing agenda topic for today’s FD.io TSC meeting.
Cheers,
-Maciek
|
By
Maciek Konstantynowicz <mackonstan@...>
·
#1140
·
|
|
TRex distribution and licensing of external libraries
Hi, Here is the background to Scapy licensing agenda topic for today’s FD.io TSC meeting.
Cheers,
-Maciek
Begin forwarded message:
From: "Miroslav Los -X (mirlos - PANTHEON TECHNOLOGIES at Cisco)"
Hi, Here is the background to Scapy licensing agenda topic for today’s FD.io TSC meeting.
Cheers,
-Maciek
Begin forwarded message:
From: "Miroslav Los -X (mirlos - PANTHEON TECHNOLOGIES at Cisco)"
|
By
Maciek Konstantynowicz <mackonstan@...>
·
#1139
·
|
|
Re: Scapy licensing issue in FD.io projects [Was: TRex distribution and licensing of external libraries]
I have a real problem with important parts of fd.io (and CSIT is an important part both for the project and for consumers of the project) being tied to GPL.
I am really unhappy that we are only
I have a real problem with important parts of fd.io (and CSIT is an important part both for the project and for consumers of the project) being tied to GPL.
I am really unhappy that we are only
|
By
Joel Halpern
·
#1138
·
|
|
Re: Scapy licensing issue in FD.io projects [Was: TRex distribution and licensing of external libraries]
>[rk] Ok my understand is that TRex had moved to github – that TRex repo is dead.
>I am not 100% certain it is still a FD.io project?
TRex is still FD.io project as far as I know.
Git+Gerrit
>[rk] Ok my understand is that TRex had moved to github – that TRex repo is dead.
>I am not 100% certain it is still a FD.io project?
TRex is still FD.io project as far as I know.
Git+Gerrit
|
By
Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco)
·
#1137
·
|
|
Re: Scapy licensing issue in FD.io projects [Was: TRex distribution and licensing of external libraries]
By
Ray Kinsella
·
#1136
·
|
|
Re: Scapy licensing issue in FD.io projects [Was: TRex distribution and licensing of external libraries]
>Why is TRex’s licensing being questioned?
It just happened to be the first FD.io project
examined (by Miroslav) for dependencies.
VPP and CSIT were examined (by Vratko) few days later.
>Why is TRex’s licensing being questioned?
It just happened to be the first FD.io project
examined (by Miroslav) for dependencies.
VPP and CSIT were examined (by Vratko) few days later.
|
By
Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco)
·
#1135
·
|
|
Re: Scapy licensing issue in FD.io projects [Was: TRex distribution and licensing of external libraries]
Ok … we need to contain the problem domain here, as it is way too complicated at the moment.
Why is TRex’s licensing being questioned?
Aren’t we just consumers or TRex, we don’t
Ok … we need to contain the problem domain here, as it is way too complicated at the moment.
Why is TRex’s licensing being questioned?
Aren’t we just consumers or TRex, we don’t
|
By
Ray Kinsella
·
#1134
·
|
|
Re: Scapy licensing issue in FD.io projects [Was: TRex distribution and licensing of external libraries]
>>I am not entirely sure how vpp "make test" sends packets to VPP.
>[rk] I thought it was veth network interface or similar, can you check?
It seems this document [11] still applies.
The python
>>I am not entirely sure how vpp "make test" sends packets to VPP.
>[rk] I thought it was veth network interface or similar, can you check?
It seems this document [11] still applies.
The python
|
By
Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco)
·
#1133
·
|
|
Re: Scapy licensing issue in FD.io projects [Was: TRex distribution and licensing of external libraries]
Hi Vratko,
Inline.
By
Ray Kinsella
·
#1132
·
|
|
Re: Scapy licensing issue in FD.io projects [Was: TRex distribution and licensing of external libraries]
>How is scapy invoked, is it a separate process or is it directly like with VPP/TRex?
The setup details differ. The C projects (VPP and the main part of TRex server)
are usually separate
>How is scapy invoked, is it a separate process or is it directly like with VPP/TRex?
The setup details differ. The C projects (VPP and the main part of TRex server)
are usually separate
|
By
Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco)
·
#1131
·
|
|
Re: Scapy licensing issue in FD.io projects [Was: TRex distribution and licensing of external libraries]
Hi Vratko,
So there is a lot of information thanks for putting this together.
What is of primary importance to understand is how TRex & VPP “talk” to scapy.
Scapy is GPL, any
Hi Vratko,
So there is a lot of information thanks for putting this together.
What is of primary importance to understand is how TRex & VPP “talk” to scapy.
Scapy is GPL, any
|
By
Ray Kinsella
·
#1130
·
|
|
Re: Scapy licensing issue in FD.io projects [Was: TRex distribution and licensing of external libraries]
Adding some technical details with quick links.
Scapy license [0] is GLP, not LGPL.
In python, using "import" statement amounts to linking,
which creates [1] a combined program, instead of
a
Adding some technical details with quick links.
Scapy license [0] is GLP, not LGPL.
In python, using "import" statement amounts to linking,
which creates [1] a combined program, instead of
a
|
By
Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco)
·
#1129
·
|
|
Re: Scapy licensing issue in FD.io projects [Was: TRex distribution and licensing of external libraries]
Resending from Cisco email account as it’s back and cleared for sending emails to tsc mailer.
Adding Miroslav, Hanoh and Vratko who has been also involved here (Miroslav brought up the issue).
Ed,
Resending from Cisco email account as it’s back and cleared for sending emails to tsc mailer.
Adding Miroslav, Hanoh and Vratko who has been also involved here (Miroslav brought up the issue).
Ed,
|
By
Maciek Konstantynowicz (mkonstan)
·
#1128
·
|