Difference between revisions of "CSIT/Meeting"
From fd.io
< CSIT
Mackonstan (Talk | contribs) |
(→Agenda) |
||
Line 49: | Line 49: | ||
#* Netgate/ATOM; | #* Netgate/ATOM; | ||
#** CPE test cases; | #** CPE test cases; | ||
− | #** [https://lists.fd.io/ | + | #** [https://lists.fd.io/g/csit-dev/message/1895 functional tests proposal]; |
# Housekeeping; | # Housekeeping; | ||
#* wiki updates, jira tracking; | #* wiki updates, jira tracking; |
Revision as of 14:58, 2 May 2018
Meeting Details
Weekly on Wednesday 14:00 UTC => 07:00 PST, 10:00 EST, 15:00 BST, 16:00 CEST, 19:30 IST, 22:00 CST.
Click here to register for 02-May-2018. Note: registration now required, to mitigate Toll Fraud.
Issues connecting to meeting? Contact: Tibor Frank <tifrank@cisco.com>.
- IRC
- #fdio-csit room on freenode
- Web-based IRC client: https://webchat.freenode.net/
Agenda
The next CSIT meeting is scheduled for Wednesday 02-May 14:00-15:00 UTC. Proposed topics:
- Agenda bashing;
- Inputs from LF and FD.io projects;
- VPP, HoneyComb, TSC, other;
- Operational status;
- Jenkins jobs:
- per VPP patch: (auto+vote) vpp-csit-verify-virl-*, (triggered) vpp-csit-verify-hw-perf-*;
- per CSIT patch: (auto+vote) csit-vpp-functional-*, (triggered) csit-vpp-perf-*;
- perf trending: perf-mrr-daily-master;
- Other LF infra stability status, performance and/or availability issues;
- VPP project gerrit rechecks;
- Jenkins jobs:
- rls1801 follow-up;
- rls1804;
- CSIT framework developments;
- PAL: new telemetry data inputs - vpp show run;
- VPP performance trending and analysis;
- announced to csit-dev and vpp-dev;
- implemented methodology;
- performance dashboard;
- trendline graphs;
- job duration optimizations
- TRex topics;
- Test case additions;
- DMM CSIT status;
- FD.io CSIT lab infra;
- XEON Skylake servers;
- proposed low level design;
- initial build;
- multiple distros support(?)
- ARM additions to CSIT labs;
- VIRL platform;
- Netgate/ATOM;
- CPE test cases;
- functional tests proposal;
- XEON Skylake servers;
- Housekeeping;
- wiki updates, jira tracking;