Development Update 24.07

[ffoulkes]

First draft of the public-facing P4CP "release" notes.

I've covered the Stratum updates and added a section on the P4Runtime Fork. (Old business, but we should probably mention it in every development update. Future editions can be shorter.)

Does anyone have anything to add? We should include any information about P4CP that's in the MEV release notes, since the general public does not have access to them.

[ffoulkes]

Nuts. It appears that rstcheck doesn't work correctly on files that use Sphinx macros.

Off the top of my head, this might be because:

• rstcheck isn't configured correctly
• It requires that additional packages be installed
• It doesn't work with Sphinx macros

I've removed rstcheck from the list of required checkers, to avoid blocking PRs until we have an answer.

Update: rstcheck has been fixed, and the checker is once again Required.

[5abeel]

Some candidates that we can add details on, based on the IPDK 24.01 release: https://github.com/ipdk-io/ipdk/blob/main/RELEASENOTES.md

• Update of Linux Networking program to the "v2" version
• Exception packet handlig
• Support for Link Aggregate Group (LAG)
• Packet IO
• Meters (think you have already mentioned these in this doc)
• Security enhancements
  • Upgrade from OpenSSL 1.1.1x to 3.x
  • Library updates to address security issues
    - Upgraded gRPC to 1.59.2 to address CVE-2023-33953, CVE-2023-4785
    - Upgraded protobuf to version 25.0
    - Upgraded abseil-cpp to version 20230802.0
    - Upgraded zlib to version 1.3

Upcoming attractions can include:

• Networking + IPsec combined recipe
• LAG in LACP mode
• Support for Geneve tunnel
• Default action support
• The "bf_" name changes?

[ffoulkes]

The bf_ name changes are specific to the E2100 SDE, and the SDE is not part of P4CP. We should only document aspects that are exposed through P4CP for the ES2K platform (whatever those may be).

[ffoulkes]

Some candidates that we can add details on, based on the IPDK 24.01 release: https://github.com/ipdk-io/ipdk/blob/main/RELEASENOTES.md

I'm inclined to backfill with a 24.03 development update, rather than lump the 24.01 release into this one.
I'm also tempted to add a line stating that the development update corresponds to <IPDK or ES2100 release 24.01>.

[5abeel]

Some candidates that we can add details on, based on the IPDK 24.01 release: https://github.com/ipdk-io/ipdk/blob/main/RELEASENOTES.md

I'm inclined to backfill with a 24.03 development update, rather than lump the 24.01 release into this one. I'm also tempted to add a line stating that the development update corresponds to <IPDK or ES2100 release 24.01>.

yes, we could do that. the dev update should contain everything since our last dev update which was 23.21 -- so, we could backfill with 24.03 instead of latest as of today.