Regarding support for WFX backend for software updates in CIP Images

Adding Koshiro Onuki san from Toshiba to the mail chain

From: [email protected] <[email protected]> On Behalf Of Adithya Balakumar
Sent: Thursday, June 20, 2024 11:26 AM
To: [email protected]
Cc: dinesh kumar(ＴＳＩＰ TMIEC ODG Porting) <[email protected]>; kunijadar shivanand(ＴＳＩＰ TMIEC ODG Porting) <[email protected]>; ashrith sai(ＴＳＩＰ) <[email protected]>; hayashi kazuhiro(林 和宏 ＤＭＥ ○ＤＩＧ□ＭＰＳ○ＭＰ４) <[email protected]>
Subject: [cip-dev] Regarding support for WFX backend for software updates in CIP Images

Hi All,

This is regarding support for WFX backend for software updates in CIP Images. I am writing to understand the opinions of the community on how to go about with the integration of WFX support.

As I understand there are 2 parts to the WFX integration:
1. Hosting the WFX server.
2. Suricatta configuration in the CIP Images via the swupdate.cfg for communication with WFX server.

As from the device side, communication with the WFX server is already supported by SWUpdate through the server_wfx.lua module. See [1]. However the necessary suricatta configs in the swupdate.cfg file are required to be set which is currently missing from image recipes.

Based on CIP Core work group meetings, I understand that there is already a plan to host a WFX server for CIP related purposes. While that is still in the works, would it be alright to update recipes to include the necessary configs needed for WFX support or wait for the server side to be completed?

Until the planned WFX server setup is completed, how about including details of setting up a WFX server and other details for minimal verification in a README file?

Would like to understand the opinions of the maintainer and the rest of the community on such an approach and also other ideas on how to go about with this integration?

[1]: https://github.com/sbabic/swupdate/blob/master/suricatta/server_wfx.lua

Thanks and Regards,
Adithya Balakumar