|
Re: FD.io Maintenance: 2019-05-28 @ 1700 UTC (10:00am PDT) - 2100 UTC (2:00pm PDT)
Vanessa Valderrama
Maintenance is starting now.
On 05/28/2019 09:20 AM, Vanessa
Valderrama wrote:
|
|
|
|
Re: FD.io Maintenance: 2019-05-28 @ 1700 UTC (10:00am PDT) - 2100 UTC (2:00pm PDT)
Vanessa Valderrama
Reminder of maintenance today. We will not be upgrading Gerrit due to some known issues with 2.16. Thank you,Vanessa
On 05/16/2019 02:58 PM, Vanessa
Valderrama wrote:
|
|
|
|
REMINDER: ONS Europe CFP Closes June 16th
Brandon Wick <bwick@...>
LFN Community, Open Networking Summit is the industry’s premier open networking event, enabling collaborative development and innovation across enterprises, service providers and cloud providers and discussing the future of Open Source Networking, including SDN, NFV, VNF, CNF/Cloud Native Networking, Orchestration, Automation of Cloud, Core Network, Edge, Access & IoT services. This year, ONS Europe is being held in Antwerp, Belgium, September 23 - 25th. Proposals to speak are now being accepted in the following tracks:
Please let me know if you have any questions. Thanks! Best, Brandon Wick
|
|
|
|
Re: Request Representative from FD.io to serve on LFN Strategic Planning Committee
Ray Kinsella
Pushed to next week, when Ed returns from Kubecon.
Ray K
From: tsc@... [mailto:tsc@...]
On Behalf Of Ray Kinsella
Sent: Thursday 23 May 2019 13:53 To: Phil Robb <probb@...>; tsc@... Subject: Re: [tsc] Request Representative from FD.io to serve on LFN Strategic Planning Committee
We should discuss this at today’s TSC meeting.
Ray K
From:
tsc@... [mailto:tsc@...]
On Behalf Of Phil Robb
Hello FD.io TSC:
This past Wednesday, the LFN Governing Board (GB) approved the creation of the Strategic Planning Committee (SPC) as described in Exhibit C (attached) with the additional amendment that the MAC Chair also be invited to participate in the committee. In the SPC slide deck, it states that "the TAC Representative of each TAC project will be a member of the SPC". That is not quite correct. The workgroup that built the SPC proposal wanted to allow the TSC of each TAC project to choose their SPC representative however they wanted. You can choose your TAC representative to also serve on the SPC but you do not have to. It can be two different people. The SPC workload will be larger than that of the TAC rep. In particular, the SPC representative should expect the following.
There is much work to do between now and the budget planning needed for 2020, and as such, additional meetings will be likely. I suggest whomever participates in the SPC should plan on spending a minimum of 2 hours per week on SPC meetings and activities between now and the face to face GB meeting on September 26th. The workload should go down a bit after this initial spin-up phase.
Please provide your SPC representative by June 3rd. All participants should plan on the first meeting of the SPC to occur some time the week of June 17th. The specific date/time will be selected through a doodle poll of the participants.
If you have any questions please do not hesitate to contact me.
Best,
Phi -- Phil Robb VP Operations - Networking & Orchestration, The Linux Foundation (O) 970-229-5949 (M) 970-420-4292 Skype: Phil.Robb
|
|
|
|
Re: Request Representative from FD.io to serve on LFN Strategic Planning Committee
Ray Kinsella
We should discuss this at today’s TSC meeting.
Ray K
From: tsc@... [mailto:tsc@...]
On Behalf Of Phil Robb
Sent: Friday 17 May 2019 20:28 To: tsc@... Subject: [tsc] Request Representative from FD.io to serve on LFN Strategic Planning Committee
Hello FD.io TSC:
This past Wednesday, the LFN Governing Board (GB) approved the creation of the Strategic Planning Committee (SPC) as described in Exhibit C (attached) with the additional amendment that the MAC Chair also be invited to participate in the committee. In the SPC slide deck, it states that "the TAC Representative of each TAC project will be a member of the SPC". That is not quite correct. The workgroup that built the SPC proposal wanted to allow the TSC of each TAC project to choose their SPC representative however they wanted. You can choose your TAC representative to also serve on the SPC but you do not have to. It can be two different people. The SPC workload will be larger than that of the TAC rep. In particular, the SPC representative should expect the following.
There is much work to do between now and the budget planning needed for 2020, and as such, additional meetings will be likely. I suggest whomever participates in the SPC should plan on spending a minimum of 2 hours per week on SPC meetings and activities between now and the face to face GB meeting on September 26th. The workload should go down a bit after this initial spin-up phase.
Please provide your SPC representative by June 3rd. All participants should plan on the first meeting of the SPC to occur some time the week of June 17th. The specific date/time will be selected through a doodle poll of the participants.
If you have any questions please do not hesitate to contact me.
Best,
Phi -- Phil Robb VP Operations - Networking & Orchestration, The Linux Foundation (O) 970-229-5949 (M) 970-420-4292 Skype: Phil.Robb
|
|
|
|
Request Representative from FD.io to serve on LFN Strategic Planning Committee
Phil Robb <probb@...>
Hello FD.io TSC: This past Wednesday, the LFN Governing Board (GB) approved the creation of the Strategic Planning Committee (SPC) as described in Exhibit C (attached) with the additional amendment that the MAC Chair also be invited to participate in the committee. In the SPC slide deck, it states that "the TAC Representative of each TAC project will be a member of the SPC". That is not quite correct. The workgroup that built the SPC proposal wanted to allow the TSC of each TAC project to choose their SPC representative however they wanted. You can choose your TAC representative to also serve on the SPC but you do not have to. It can be two different people. The SPC workload will be larger than that of the TAC rep. In particular, the SPC representative should expect the following. There is much work to do between now and the budget planning needed for 2020, and as such, additional meetings will be likely. I suggest whomever participates in the SPC should plan on spending a minimum of 2 hours per week on SPC meetings and activities between now and the face to face GB meeting on September 26th. The workload should go down a bit after this initial spin-up phase. Please provide your SPC representative by June 3rd. All participants should plan on the first meeting of the SPC to occur some time the week of June 17th. The specific date/time will be selected through a doodle poll of the participants. If you have any questions please do not hesitate to contact me. Best, Phi Phil Robb VP Operations - Networking & Orchestration, The Linux Foundation (O) 970-229-5949 (M) 970-420-4292 Skype: Phil.Robb
|
|
|
|
Sweetcomb 19.08 Release Plan
Ni, Hongjun
Hi Folks,
Below are the 19.08 Release Plan we discussed in weekly meetings. Please correct me if something missed. If you have more requirements, Please let us know.
# Integrate gNMI with Sysrepo
# Restconf support
# ACL • - Add OC Yang Models. • - Add OC Translation Layer. • - Add OC test cases.
# DNSMASQ • - Add Yang Models. • - Add Translation Layer. • - Add test cases.
# High Availability • - Replace scvpp plugin using VPP VOM. • - VPP Restart • - Sweetcomb Restart
# Configuration telemetry
# Strongswan Integration
# Framework of plugin registration and un-registration
Thanks, Hongjun
|
|
|
|
FD.io Maintenance: 2019-05-28 @ 1700 UTC (10:00am PDT) - 2100 UTC (2:00pm PDT)
Vanessa Valderrama
What: FD.io system maintenance
When: 2019-05-28 @ 1700 UTC (10:00am PDT) - 2100 UTC (2:00pm PDT)Impact: The maintenance will require a reboot of each FD.io system. Jenkins will be placed in shutdown mode at 1700 UTC. Please let us know if there are any jobs that cannot be aborted. The following systems will be impacted:
Jenkins sandbox will be upgraded Monday to allow time for testing
prior to upgrading production
|
|
|
|
2019-05-14 FD.io Jenkins security incident
Vanessa Valderrama
Event Summary Date of incident - 2019-05-14 Time event began - 2:13am PDT Project services restored - 6:15AM PDT Final resolution - Clean up the incursion and upgrade “Script Security” Plugin for Jenkins to avoid repeat infection. Causes Root cause - shell escape exploit in the “Script Security” plugin for Jenkins, remotely injected via a specially crafted URL. The exploit caused the Jenkins server to crash, but succeeded in running the payload. A bitcoin miner was installed under the Jenkins user for FD.io Jenkins. Other contributing causes:
Effects Downtime for projects: FD.IO Jenkins Minor downtime/interruptions for other project Jenkins systems as they were updated. Follow-up actions
Timeline (PDT) 2:13am PDT: exploit is successfully performed on FD.io Jenkins via a specially crafted URL containing the payload: 107.174.x.x - - [14/May/2019:09:13:26 +0000] "GET /descriptorByName/org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SecureGroovyScript/checkScript?sandbox=True&value=public+class+x%7Bpublic+x%28%29%7Bnew+String%28%22[payload_omitted]%22.decodeHex%28%29%29.execute%28%29%7D%7D HTTP/1.1" 200 6 "-" "python-requests/2.21.0" The exploit caused Jenkins to crash, but the payload execution was successful due to critical vulnerabilities in the “Script Security” Jenkins plugin. The payload downloaded and executed the following shell script: https://paste.fedoraproject.org/paste/LjwXwoLyXnAI78kS0vhBBg The script is not Jenkins-specific, so it does not attempt to modify any content owned by Jenkins. Since the script runs as a non-privileged user, most actions fail without any effect. The script does install a cryptocoin miner (“cryptonight”) and puts itself into crontab for the jenkins user in order to persist across reboots. 2:19am PDT: Monitoring recognizes that Jenkins is down and issues an alert, which is received and acknowledged by C.Hoy Poy (sysops on call). 2:48am PDT: C.Hoy Poy identifies that there has been a security incursion and shuts down the system per security first responder procedure. 2:56am PDT: The issue is escalated to K.Ryabitsev (Director of IT Security), J.Conway (SysOps Team Lead). 4:00am PDT: The incursion is traced down to the Jenkins “Script Security” plugin and payload is identified and analyzed. The team takes a decision to clean up the affected system instead of reinstalling it, since there is no indication that the payload succeeded to do anything beyond installing the cryptocoin miner. 6:15am PDT: The system is cleaned up and all plugins are updated to their latest security errata versions. Jenkins is brought back online and all services restored. ~2:00pm PDT: All other Jenkins systems are analyzed for traces of the same incursion and upgraded to the latest security errata. 2019-05-14 fd.io Jenkins security incident
|
|
|
|
FD.io Gerrit Maintenance: 2019-05-28 @ 1900 UTC (12:00pm PDT) - 2100 UTC (2:00pm PDT)
Vanessa Valderrama
What:
FD.io Gerrit maintenance When: 2019-05-28 @ 1900 UTC (12:00pm PDT) - 2100 UTC (2:00pm
PDT) Impact: Jenkins will be placed in shutdown mode one hour prior to maintenance to allow builds to complete and will remain in shutdown mode for the duration of the Gerrit upgrade. The following systems will be unavailable during the
maintenance window
Why: FD.io Gerrit maintenance to upgrade from 2.14.6 to 2.16
|
|
|
|
Ray Kinsella to chair May 23rd FD.io TAC
Ray has agreed to act as chair Wed May 23rd in my absence as I travel to Kubecon EU. Ed
|
|
|
|
Published: FD.io CSIT-1904 Benchmarking Report
Maciek Konstantynowicz (mkonstan)
Hi All,
FD.io CSIT-1904 report has been published on FD.io docs site: html: https://docs.fd.io/csit/rls1904/report/ pdf: https://docs.fd.io/csit/rls1904/report/_static/archive/csit_rls1904.pdf Many thanks to All in CSIT, VPP and FD.io community who contributed and worked hard to make CSIT-1904 happen! FD.io VPP points of note in the report: 1. VPP release notes a. Changes in CSIT-1904: http://bit.ly/309V2oJ b. Known issues: http://bit.ly/2Q2K5AM 2. VPP performance graphs a. Throughput 64B frames: http://bit.ly/2VrdASG b. Speedup Multi-Core: http://bit.ly/2LAhjbS c. Latency: http://bit.ly/307AQUl 3. VPP performance comparisons a. VPP-19.04 vs. VPP-19.01: http://bit.ly/30ci12w b. Xeon Skylake vs. Xeon Haswell: http://bit.ly/2PWhLzT 4. VPP performance test details a. Detailed results 64B IMIX 1518B 9kB: http://bit.ly/2JuTjV3 b. Configuration: http://bit.ly/2E4tvvA DPDK Testpmd and L3fwd performance sections follow similar structure. 1. DPDK release notes: a. Changes in CSIT-1904: http://bit.ly/2VrOSBK b. Known issues: http://bit.ly/2VuO3ry 2. DPDK performance graphs for Testpmd and L3fwd demonstrator apps a. Throughput 64B frames: http://bit.ly/2Lxwa72 b. Latency: http://bit.ly/2DZoKmO Functional tests, including VPP_Device (functional device tests), VPP_VIRL and HoneyComb are all included in the report. Welcome all Comments, best by email to csit-dev@lists.fd.io. Cheers, -Maciek On behalf of FD.io CSIT Project
|
|
|
|
You're Invited to the FD.io Mini Summit at KubeCon + CloudNativeCon
Jill Lovato <jlovato@...>
FD.io Community, For those attending KubeCon + CloudNativeCon EU, May 20-23, we invite you to attend the FD.io Mini Summit at KubeCon + CloudNativeCon, Monday, May 20th, 08:00 - 17:00.
08:00: Registration & Networking 09:00: IPSEC HW/Inline 09:30: High-Performance IPSec using fd.io VPP 10:00: Break 10:15: Apply VPP TLS stack to Nginx 10:45: VPP Host Stack 11:15: DMM 2.0 update: New Event Notification Mechanism and New Perf Testing Result 11:45: Lunch 13:00: Ligato - A Management and Control Plane for VPP-based CNFs 13:30: State of VPP in Network Service Mesh 14:00: High Performance Cloud Native Networking: K8s unleashing FD.io. 14:30: Break 14:45: TRex - Realistic Traffic Generator 15:15: Electric Cars Are The Future. But Most Aren't Using Them Yet. 15:45: Sweetcomb: Unified Management Agent/uCPE 16:15: VPP-enabled Clusters on Packet in No Time 16:45: An Introduction to the Hybrid Information-Centric Networking Project REGISTER TODAY Note: Pre-registration for the FD.io Mini-Summit is required and space is limited. There is a $50 registration fee. Click here to register now! To edit your registration or add a co-located event, visit the registration form here, log in as 'Already Registered' and edit the registration. FD.io BOOTH/DEMOS FD.io will also have a booth booth during the sponsor showcase with three demos and we encourage to to stop by. If you have an interest in volunteering in the booth, please email tdelanerolle@.... Please send any questions to jlovato@... and we hope to see many of you in Barcelona! Best,
|
|
|
|
Re: [MAC] LFN DDF + Plugfest Website & Registration Now Live
Ed Warnicke (eaw) <eaw@...>
Was this brought up to the communities? Did anyone ask them if this met their needs? Did this get discussed in any of the TSCs?
toggle quoted messageShow quoted text
Ed
|
|
|
|
LFN DDF + Plugfest Website & Registration Now Live
Brandon Wick <bwick@...>
LFN Communities, The LFN Developer Design Forum (DDF) + Plugfest website and registration are now live. See the links below. Space is limited so we encourage you to register today.
The LF Networking (LFN) Developer Design Forum (DDF) + Plugfest is the principal technical event for LFN projects. The next event will be held June 11-14, at the Kista Convention Center (Kistamässan), in Stockholm, Sweden. This event fosters collaboration both within and across the various technical communities under the LFN umbrella, including ONAP, OPNFV, OpenDaylight, and Tungsten Fabric. This is the second co-located DDF and Plugfest, following the first such event, held in January, in Saclay, France. Senior Integrated Marketing ManagerThe LFN DDF + Plugfest is focused on developer and engineer collaboration opportunities. The ONAP community will be working toward the El Alto and Frankfurt release while the OPNFV community will be focused on testing the Hunter release. There will also be ample opportunities for cross-project collaboration around automated testing, CI/CD, Lab-as-a-Service, infrastructure, the OPNFV Verification Program (OVP), documentation, and other ways to increase collaboration and operational excellence across projects. Attendees may attend project meetings, demos, hackfest activities, plugfest activities, as well as sessions specifically designed to encourage cross-community collaboration on subjects of mutual interest (e.g., test, infra). In addition, participants are encouraged to do “hands on” work, resolving bugs, and conducting interoperability testing, using remote connections to their hardware resources, as part of the Plugfest portion of the event. Participants will be provided with a dedicated space, where they may work, uninterrupted, separate from the main meeting area. Who Attends? The most common job types are Architects and Developers and other represented groups include Network Operations, Project/Program Manager, Sales & Marketing, Executives, and Students. We hope you'll join us in Stockholm! Best, Brandon Wick
|
|
|
|
CFP for LFN DDF+ Plugfest Open
Trishan de Lanerolle
Hi, The LF Networking (LFN) Developer Design Forum (DDF) + Plugfest is the principal technical event for LFN projects. The next event will be held June 11-14, at the Kista Convention Center (Kistamässan), in Stockholm, Sweden. This event fosters collaboration both within and across the various technical communities under the LFN umbrella, including ONAP, OPNFV, OpenDaylight, FD.io and Tungsten Fabric. This is the second co-located DDF and Plugfest, following the first such event, held in January, in Saclay, France. The LFN DDF + Plugfest is focused on developer and engineer collaboration opportunities. The ONAP community will be working toward the El Alto and Frankfurt release while the OPNFV community will be focused on testing the Hunter release. There will also be ample opportunities for cross-project collaboration around automated testing, CI/CD, Lab-as-a-Service, infrastructure, the OPNFV Verification Program (OVP), documentation, and other ways to increase collaboration and operational excellence across projects. Attendees may attend project meetings, demos, hackfest activities, plugfest activities, as well as sessions specifically designed to encourage cross-community collaboration on subjects of mutual interest (e.g., test, infra). In addition, participants are encouraged to do "hands on" work, resolving bugs, and conducting interoperability testing, using remote connections to their hardware resources, as part of the Plugfest portion of the event. Participants will be provided with a dedicated space, where they may work, uninterrupted, separate from the main meeting area. https://wiki.lfnetworking.org/pages/viewpage.action?pageId=15630372 Regards, Trishan Trishan R. de Lanerolle Program Manager, Networking Linux Foundation voice: +1.203.699.6401 skype: tdelanerolle email: tdelanerolle@...
|
|
|
|
Sweetcomb 19.04 Released
Ni, Hongjun
Hey all,
The Sweetcomb 19.04 Release is out !
Packages can be downloaded from Package Cloud: https://packagecloud.io/fdio/1904
Many thanks to all contributors and members for your great contribution and help!
Below are Sweetcomb 19.04 release notes:
# Features ## Northbound Interface - Init gNMI Server
## NAT - Add IETF NAT Yang Models. - Add IETF NAT Translation Layer. - Add IETF NAT test cases.
## High Availability - Add vpp health check.
## Code Refactor - Code global cleanup. - Refactor build system. - Rework scvpp to be only interface with VAPI. - Rework interface and local routing to leverage new scvpp.
## Test Framework - Add unit test framework. - Add unit test suite for interface and local routing. - Build docker environment to test integration of sweetcomb and VPP.
Thanks you all, Hongjun On behalf of the FD.io/Sweetcomb team
|
|
|
|
Call for Demos at Kubecon Barcelona May 21-23rd
Trishan de Lanerolle
FD.io will have a booth at Kubecon Barcelona May 21-23rd. This is a call out to the community for demo proposals to show in the booth. Please respond with a brief description of a demo you would like to run in the FD.io booth. You will be required to staff the demo during expo hours. If accepted, we will provide you with a conference pass. Submit your proposal by completing the following form no later than COB PT (5pm PT) Thursday April 25th.
|
|
|
|
Sweetcomb 19.04 RC1 milestone is complete
Ni, Hongjun
Hi all,
The Sweetcomb 19.04 RC1 milestone is complete.
The Sweetcomb 19.04 release branch (stable/1904) has been created. Sweetcomb master branch is now re-open for all patches slated for Sweetcomb 19.08 (and beyond). Sweetcomb stable/1904 is now also open - but for bug fix patches only.
Per the standard process, all bug fixes to the stable branch should follow the best practices: All bug fixes must be double-committed to the release throttle as well as to the master branch Commit first to the release throttle, then "git cherry-pick" into master Manual merges may be required, depending on the degree of divergence between throttle and master
All bug fixes need to have a Jira ticket. Please raise it in https://jira.fd.io/projects/SWEET/issues/?filter=allopenissues Please put Jira IDs into the commit messages. Please use the same Jira ID for both the stable branch and master.
Please let us know if there are any issues.
Thank you all for the great help during this RC1 milestone process!
Thanks a lot, Hongjun
|
|
|
|
Re: Unstable Builds
Vanessa Valderrama
The issue has been identified and resolved. We've restarted the
toggle quoted messageShow quoted text
unstable builds. Thank you, Vanessa
On 04/10/2019 09:27 AM, Vanessa Valderrama wrote:
We are aware of the unstable builds issue and are working on resolving
|
|
|
