Difference between revisions of "P4vpp/Meetings"
(→Sept 25th, 2017) |
CianFerriter (Talk | contribs) |
||
| Line 25: | Line 25: | ||
Skip Booth - Create P4VPP Wiki structure and Setup Webex meeting (Done) | Skip Booth - Create P4VPP Wiki structure and Setup Webex meeting (Done) | ||
| − | + | Cian - Kick the tires on the initial implementation and start to map the P4 V1Switch and PSA externs into VPP Libraries | |
Goal is to get the initial code migration from the private Github repository into the Gerrit repo by Oct 2nd. | Goal is to get the initial code migration from the private Github repository into the Gerrit repo by Oct 2nd. | ||
| Line 36: | Line 36: | ||
Cian - Will investigate manual modification of code to test initial implementation and work on implementing a library for the checksum extern. | Cian - Will investigate manual modification of code to test initial implementation and work on implementing a library for the checksum extern. | ||
| − | Next meeting on October | + | == Oct 9th, 2017 == |
| + | |||
| + | Andy worked on IR builder and infra for externs (packet in + verify). IR builder is used for most things. Has worked on merging. | ||
| + | |||
| + | Skip spent time making sure what we are generating can be connected up to VPP as a plugin. Uses the latest master of VPP to test the generated code. | ||
| + | |||
| + | Johann Tonsig and David George from Netronome to apply for access to team members not on the call interested in the project. | ||
| + | |||
| + | Plan is to use standard VPP repo. Old repo built plugin in tree. Plugin should be compilable out of tree with VPP installed. Add to makefile to check what version of VPP would be installed. Make based off this. Have a trusted tag. Have a test script that validates behaviour with static and run time integrity testing. There are some nice to haves here, which won't be available at first. | ||
| + | |||
| + | '''Opens''' | ||
| + | |||
| + | Having P4 files from Netronome to target specific use cases and prioritise certain features would be useful. | ||
| + | |||
| + | Netronome has found having IR in files to be useful for visualisation tools. | ||
| + | |||
| + | Next meeting on October 23th, 8:00 am PT | ||
Revision as of 14:53, 23 October 2017
Contents
P4VPP Project Meetings
Weekly Project Meetings are currently every Monday at 8:00 am PT, 11:00 am ET, 4:00 pm IT. As the community grows, this project meeting time may shift to accommodate more geographies. Audio/Web Conferencing details:
Meeting number: 204 722 006
Meeting Password: p4-vpp (740877 from phones)
To join from a browser: https://cisco.webex.com/ciscosales/j.php?MTID=m917fa25f6ee9f022acc3d42d2d4cd07c
To join directly via phone: +1-408-525-6800 Call-in toll number (US/Canada) +1-866-432-9903 Call-in toll-free number (US/Canada)
Agenda
Meeting Minutes, Action Items
Sept 18th, 2017
Andy Keep - Present current status of Project and High level design details: P4VPP Status 9-18-2017
Skip Booth - Create P4VPP Wiki structure and Setup Webex meeting (Done)
Cian - Kick the tires on the initial implementation and start to map the P4 V1Switch and PSA externs into VPP Libraries
Goal is to get the initial code migration from the private Github repository into the Gerrit repo by Oct 2nd.
Next meeting on Sept 25th, 8:00 am PT
Sept 25th, 2017
Andy - Presented status update on his work. Mentioned that checksum would be a good extern to implement.
Cian - Will investigate manual modification of code to test initial implementation and work on implementing a library for the checksum extern.
Oct 9th, 2017
Andy worked on IR builder and infra for externs (packet in + verify). IR builder is used for most things. Has worked on merging.
Skip spent time making sure what we are generating can be connected up to VPP as a plugin. Uses the latest master of VPP to test the generated code.
Johann Tonsig and David George from Netronome to apply for access to team members not on the call interested in the project.
Plan is to use standard VPP repo. Old repo built plugin in tree. Plugin should be compilable out of tree with VPP installed. Add to makefile to check what version of VPP would be installed. Make based off this. Have a trusted tag. Have a test script that validates behaviour with static and run time integrity testing. There are some nice to haves here, which won't be available at first.
Opens
Having P4 files from Netronome to target specific use cases and prioritise certain features would be useful.
Netronome has found having IR in files to be useful for visualisation tools.
Next meeting on October 23th, 8:00 am PT
