|
NOTIFICATION: FD.io Maintenance
Vanessa Valderrama
Please notify us immediately if this schedule causing a conflict for your project What: FD.io system migration to AWS When: JIRA & OpenGrok2018-05-01 from 2100 UTC to 0100 UTC Gerrit 2018-05-02 from 2100 UTC to 0100 UTC Sonar 2018-05-08 from 2100 UTC to 0100 UTC Impact:
Why: Linux Foundation is working to bring the FD.io infrastructure
inline with our 2018 hosting strategy. This move should result in
a reduction of costs, improved performance and increased
redundancy.
|
|
|
|
Federating Jira to LF Jira
Greetings TSC, I would like to propose that we allow the LF Jira instance (https://jira.linuxfoundation. Is this a topic that can be brought up at the next TSC meeting agenda? Thanks, Thanh
|
|
|
|
FD.io Intern Projects
LFN is funding internships for LFN Projects (of which FD.io is one): We already had one student reach out interested in working as a FD.io intern. To get there, we need Intern Project Proposals: (guidelines here: https://wiki.fd.io/view/Interns ) I encourage community members interested in mentoring an intern to propose projects. Additionally, the 'guidelines' and 'proposal template' should be considered 'a first draft'. So if you find something there that could be improved, please do so :) Ed
|
|
|
|
[FD.io] CFP: FD.io minisummit @Kubecon EU May 2-4 in Copenhagen.
Folks, let's get your talk proposals in :) Ed ---------- Forwarded message --------- From: Trishan de Lanerolle <tdelanerolle@...> Date: Wed, Apr 4, 2018 at 11:08 AM Subject: [FD.io] CFP: FD.io minisummit @Kubecon EU May 2-4 in Copenhagen. To: <main@...> Call for Proposals Open until EoD tomorrow. Join the FD.io community in Copenhagen, Denmark, for a co-located FD.io Mini summit at KubeCon+CloudNativeCon. Hear and learn from FD.io and industry experts who will be sharing information about the projects, use cases, capabilities, integration between FD.io and Kubernetes/ODL/OPNFV/other communities, tools and many more exciting topics. This is a great opportunity for KubeCon+CloudNativeCon attendees to share their thought leadership and innovations at one of the industry’s premier events. TO SUBMIT A SPEAKING PROPOSAL: Submissions must be received by 11:59pm PST on Thursday, April 5th, 2018. Dates to Remember
|
|
|
|
Committer Nomination for ci-management: Ed Kern
Vanessa Valderrama
Can we add an agenda item for TSC tomorrow to vote on Ed Kern becoming a
committer for the ci-management project. I've discussed this with Ed and he is interested in becoming a committer. The ci-managment committers have voted as well. https://lists.fd.io/g/ci-management-dev/topic/committer_nomination_ed_kern/16738959?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,16738959 Thank you, Vanessa
|
|
|
|
Proxy for the 5th of April
Ray Kinsella
Folks,
Keith Wiles will be acting as proxy for Venky Venkatesan for the 5th April TSC meeting.
Thanks,
Ray K
|
|
|
|
FD.io minisummit @ Kubecon EU May 2-4 Copenhagen CFP opens
FD.io will be holding a minisummit @Kubecon EU May 2-4 in Copenhagen. Please submit your talks at the CFP here: Ed
|
|
|
|
Re: FD.io TAC Proxy Policy
Ray Kinsella
+1 also – simple is best.
Ray K
From: tsc@... [mailto:tsc@...]
On Behalf Of George Zhao
Sent: Tuesday 13 March 2018 23:26 To: tsc@... Subject: Re: [tsc] FD.io TAC Proxy Policy
+1, same here, TAC can pick a proxy among FD.io TSCs
From:
tsc@... [mailto:tsc@...]
On Behalf Of Dave Barach
+1. Let’s try the simplest scheme [option 1] and see how it goes.
I am inclined to allow the rep to pick a proxy from the other TSC members. If the TSC observes a pattern it has a problem with, then we can change the rules (and we probably have a bigger problem.)
Yours, Joel
From:
tsc@... [mailto:tsc@...]
On Behalf Of Edward Warnicke
The LFN TAC has decided that the individual projects should set their policy on how proxies to the TAC are determined if their TAC representative is unable to attend.
As I see it, there are minimally a couple of options:
1) The FD.io representative to the TAC may pick a proxy themselves from the other FD.io TSC members (what was done two weeks ago for the TAC meeting) 2) The FD.io TSC votes on a proxy for the FD.io TAC rep in the event they notify the FD.io TSC they need one for a meeting on a case by case basis.
There may be other good ideas on how to handle it. Do folks have opinions?
Ed
|
|
|
|
TSC proxy for 3/14
Hello, Qing Chang will be my proxy on 3/14.
Thanks, George
|
|
|
|
Re: FD.io TAC Proxy Policy
+1, same here, TAC can pick a proxy among FD.io TSCs
From: tsc@... [mailto:tsc@...] On Behalf Of
Dave Barach
Sent: Tuesday, March 13, 2018 1:36 PM To: tsc@... Subject: Re: [tsc] FD.io TAC Proxy Policy
+1. Let’s try the simplest scheme [option 1] and see how it goes.
I am inclined to allow the rep to pick a proxy from the other TSC members. If the TSC observes a pattern it has a problem with, then we can change the rules (and we probably have a bigger problem.)
Yours, Joel
From: tsc@... [mailto:tsc@...]
On Behalf Of Edward Warnicke
The LFN TAC has decided that the individual projects should set their policy on how proxies to the TAC are determined if their TAC representative is unable to attend.
As I see it, there are minimally a couple of options:
1) The FD.io representative to the TAC may pick a proxy themselves from the other FD.io TSC members (what was done two weeks ago for the TAC meeting) 2) The FD.io TSC votes on a proxy for the FD.io TAC rep in the event they notify the FD.io TSC they need one for a meeting on a case by case basis.
There may be other good ideas on how to handle it. Do folks have opinions?
Ed
|
|
|
|
Re: FD.io TAC Proxy Policy
Dave Barach
+1. Let’s try the simplest scheme [option 1] and see how it goes.
From: tsc@... <tsc@...> On Behalf Of
Joel Halpern
Sent: Tuesday, March 13, 2018 2:23 PM To: tsc@... Subject: Re: [tsc] FD.io TAC Proxy Policy
I am inclined to allow the rep to pick a proxy from the other TSC members. If the TSC observes a pattern it has a problem with, then we can change the rules (and we probably have a bigger problem.)
Yours, Joel
From: tsc@... [mailto:tsc@...]
On Behalf Of Edward Warnicke
The LFN TAC has decided that the individual projects should set their policy on how proxies to the TAC are determined if their TAC representative is unable to attend.
As I see it, there are minimally a couple of options:
1) The FD.io representative to the TAC may pick a proxy themselves from the other FD.io TSC members (what was done two weeks ago for the TAC meeting) 2) The FD.io TSC votes on a proxy for the FD.io TAC rep in the event they notify the FD.io TSC they need one for a meeting on a case by case basis.
There may be other good ideas on how to handle it. Do folks have opinions?
Ed
|
|
|
|
Developer Activities at the beginning of the 2018 Open Source Networking Summit
Phil Robb <probb@...>
Hello LFN Community Members: Given that ONS this year is the first opportunity to get many developers from our key open source networking projects together, I’d like to map out what we have planned and invite you to participate in what will surely be a very productive event with many opportunities for collaborating on a myriad of technical topics. On Saturday and Sunday (3/24, and 3/25) there is an Infrastructure and CI/CD workshop held by members of OPNFV, OpenDaylight, OpenStack, ONAP, FD.io and other communities. This is a small gathering of key stakeholders responsible for CI/CD efforts across those projects. This event is at full registration and is not accepting any additional attendees at this time. On Sunday (3/25), Monday (3/26) afternoon, and Tuesday (3/27) morning, the OpenDaylight project is holding their Florine Release Developer Design Forum (DDF). Topics for the ODL DDF have been collected on this wiki page. The agenda for the DDF is being created by members of the ODL TSC and the sessions will be posted to the ONS Schedule. The format of the ODL DDF is generally:
800 Wilshire Blvd Los Angeles, CA 90017
Monday morning, the LFN communities will come together for a series of joint sessions with topics affecting several if not all of the projects in LFN. Topic areas for this portion of the Developer Forum include:
The Call for Topics for this portion of the event is over, but if you’d like to see what was submitted for consideration, please take a look here. The accepted sessions have been published on the ONS website and can be found here.
If you have a topic that you strongly feel belongs in this section but it’s not represented, please contact me at PRobb@... Monday afternoon and Tuesday morning there are technical breakout sessions focused on ONAP, OPNFV, and OpenDaylight (as I mentioned above). Sessions in these breakouts will be focused on the current technical discussions occurring within each of those communities. Within these sessions, we are also encouraging topics that may be of interest to one or more of the other LFN projects. An example of this would be ONAP’s use of OpenDaylight and any potential requests those communities may have of each other regarding future development and/or testing. In addition, FD.io is having a Mini Summit during the same time frame. The Call-For-Topics for these project-focused events are located at the links below. Please review these proposals at your earliest opportunity to see the topics for discussion during this unprecedented event. Finally, Tuesday morning from 8:00am to 9:00am PDT will be the first Linux Foundation Networking (LFN) project Technical Advisory Council (TAC) face to face meeting. The TAC is a new governance body formed at the creation of the LFN umbrella project and they are tasked with aiding in the coordination and cross-collaboration of the open source networking projects within LFN. In this meeting the TAC will provide an overview of topics and decisions since LFN was launched as well as lead a session meant to uncover and highlight the most important cross-project initiatives that should be started/continued, funded and tracked as part of our collective 2018 Goals and Objectives. Please don’t hesitate to reach out to me if you have questions or comments on this event. I look forward to seeing everyone in Los Angeles in two weeks! Phil. Phil Robb VP Operations - Networking & Orchestration, The Linux Foundation (O) 970-229-5949 (M) 970-420-4292 Skype: Phil.Robb
|
|
|
|
Re: FD.io TAC Proxy Policy
Joel Halpern
I am inclined to allow the rep to pick a proxy from the other TSC members. If the TSC observes a pattern it has a problem with, then we can change the rules (and we probably have a bigger problem.)
Yours, Joel
From: tsc@... [mailto:tsc@...] On Behalf Of
Edward Warnicke
Sent: Tuesday, March 13, 2018 2:03 PM To: tsc@... Subject: [tsc] FD.io TAC Proxy Policy
The LFN TAC has decided that the individual projects should set their policy on how proxies to the TAC are determined if their TAC representative is unable to attend.
As I see it, there are minimally a couple of options:
1) The FD.io representative to the TAC may pick a proxy themselves from the other FD.io TSC members (what was done two weeks ago for the TAC meeting) 2) The FD.io TSC votes on a proxy for the FD.io TAC rep in the event they notify the FD.io TSC they need one for a meeting on a case by case basis.
There may be other good ideas on how to handle it. Do folks have opinions?
Ed
|
|
|
|
FD.io TAC Proxy Policy
The LFN TAC has decided that the individual projects should set their policy on how proxies to the TAC are determined if their TAC representative is unable to attend. As I see it, there are minimally a couple of options: 1) The FD.io representative to the TAC may pick a proxy themselves from the other FD.io TSC members (what was done two weeks ago for the TAC meeting) 2) The FD.io TSC votes on a proxy for the FD.io TAC rep in the event they notify the FD.io TSC they need one for a meeting on a case by case basis. There may be other good ideas on how to handle it. Do folks have opinions? Ed
|
|
|
|
Florin will be my proxy for 3/8 TSC meeting
Hi Ed, Florin Coras will be my TSC proxy tomorrow. Thanks, George
|
|
|
|
Re: ARM hardware
Hi Vanessa,
I think Brian and Khem will set up CSIT test cases on top of these ARM hardware. thanks George 发件人：Vanessa Valderrama
收件人：tsc@...,
时间：2018-03-05 14:28:44
主 题：[tsc] ARM hardware
We'd like to know if any projects are using the VIRL network that was
requested awhile back? - 10.30.52.0/24 - 10.30.53.0/24 - 10.30.54.0/24 Thank you, Vanessa
|
|
|
|
ARM hardware
Vanessa Valderrama
We'd like to know if any projects are using the VIRL network that was
requested awhile back? - 10.30.52.0/24 - 10.30.53.0/24 - 10.30.54.0/24 Thank you, Vanessa
|
|
|
|
Re: [csit-dev] fd.io Community Goals and Objectives for reporting to the LFN board
Ray Kinsella
Hi folks,
So the LFN TAC is looking to close on the “Community goals and priorities” rollup by 9th March. This exercise is part of the process of obtaining a fair share of resources for FD.io in 2018. So if you haven’t already, please canvass your committers and contributors for their 2018 project plans. What new features do they anticipate developing? Are there plans for validation, new platform or hardware support etc ? You can either reply to this email directly, or send a note to myself or Ed W. Much appreciated, thanks, Ray K From: csit-dev-bounces@lists.fd.io [mailto:csit-dev-bounces@lists.fd.io] On Behalf Of Ed Warnicke Sent: Thursday 1 February 2018 16:43 To: tsc@lists.fd.io; discuss@lists.fd.io; vpp-dev <vpp-dev@lists.fd.io>; csit-dev@lists.fd.io; cicn-dev@lists.fd.io; tldk-dev@lists.fd.io; dmm-dev@lists.fd.io; odp4vpp-dev@lists.fd.io; pma_tools-dev@lists.fd.io Subject: [csit-dev] fd.io Community Goals and Objectives for reporting to the LFN board FD.io has recently transitioned from being its own independent foundation, to being one of several projects (ONAP, OpNFV, ODL, etc) under the Linux Foundation Networking (LFN) umbrella. As part of this transition, the LFN board has asked to be educated about what Goals and Objectives the community intends to undertake in the next year. Since an Open Source community intrinsically is a harmonious collection of folks working on different things, the only way to ascertain what its is really planning to do is to *ask* what folks are planning to do. What are the plans of various folks participating in the community for 2018? What are the themes of the problems you are planning to address, the kinds of features you are looking to implement etc? Ed
|
|
|
|
Reminder: CFP for FD.io@ONS mini-summit closes March 1st
Trishan de Lanerolle
Call for Proposals due March 1st Join us at the FD.io mini summit at ONS, to hear and learn from FD.io community experts who will be sharing information about the projects, use cases, capabilities, integration between FD.io and Kubernetes/ODL/OPNFV/Other communities, tools and many more exciting topics. This is a great opportunity for the ONS attendees to share their thought leadership and innovations at one of the industry’s premier events. Call for Proposals: https://goo.gl/HK2fo1 Submissions must be received by 11:59pm PST on Thursday, March 1st, 2018. Dates to Remember Trishan R. de Lanerolle Program Manager, Networking Linux Foundation voice: +1.203.699.6401 skype: tdelanerolle email: tdelanerolle@...
|
|
|
|
Re: NOTIFICATION: FD.io VPP - 2018-02-26 @ 1500 UTC (7:00am PST)
Vanessa Valderrama
Change https://gerrit.fd.io/r/#/c/10609/ has been merged. VPP jobs are now building on CPOC containers. Please contact snergster/valderrv on fdio-infra via IRC if you experience any issues. Thank you,Vanessa
On 02/26/2018 10:19 AM, Vanessa
Valderrama wrote:
|
|
|
