DASH / High Availability WG

F5 joining call, Q&A

Exposing table to SONiC is not an issue; concerned w/speed
Inline sync is not easily decoupled from the dataplane - would never get the performance if we went w/SONiC
Perfect sync/Bulk sync there is no tight timeline
Think of as snapshot/restoring feature
See:
https://github.com/sonic-net/DASH/blob/main/documentation/high-avail/AMD-Pensando_HA_Proposal.md
https://github.com/sonic-net/DASH/pull/271/files
https://github.com/sonic-net/DASH/blob/main/documentation/high-avail/xsight-labs-ha-proposal-new-ideas.md

Continued bulk sync what to do with config changes during bulk sync.
Guohan needs SAI spec to be complete, for SONiC to have logic to handle cases.
Bulk sync s/be accurate (vs. performant), w/certainty re: how to test it.
Create a lightweight bmv2 HA for experimental version to verify algorithms?

BFD & ECMP - Prince
Overview, from a DASH perspective we would need to add-on

Community to Review please
https://github.com/Azure/DASH/pull/271 - amendments to PR 244 (Sanjay & Mukesh)

Prince: BFD & ECMP - move to Nov 8, 2022 - Still WIP

-Suggestions & Comments added to https://github.com/Azure/DASH/pull/244/files
-Heartbeat process and format: Message format is in the header file (flow sync message notification data)
-SAI_DASH_HA_REGISTER_CP_CHANNEL_ATTR_NAMED_PIPE
-Get from named pipe, or standard SAI notification?
-Callback function, is this defined? So SyncD can register (b/c ReDis is not used)
-Should we use 2 different channels? Named pipe for data, another for all control messages?
-HB messages are over UDP for this paper. Should we use BFD? Need to think more on this…
-Multi-path vs Single-path - need to think through this problem. We should have options to choose
-Come to next session w/ideas :)

MetaData standardization
AMD update to proposal
Syncs near real-time, not necessarily real-time

Discussion on MetaData policies/expectations
Proposals to define InterOp in the future
Future work suggested by Guohan: Community to work on CP and DP InterOp, and packet format
Need to get control channel defined

Unplanned Switchover discussion
Requested updates to HA Proposal document
Thank you Sanjay for presenting!
Next week discussion on MetaData policies/expectations

Reshma hosting :)

Pick up w/SAI definitions on page 10
Q: will this be represented as a P4 model?
A: Sanjay - this could be challenging. Will look for a way to formalize and represent it.
Q: Guohan - would be great if we can sample code to call the api.
A: SAI API common config examples (Marian)

Change CP messages opaque vs common

Continuance of AMD proposal - will need another session next week.
Next session: Pre-emption case to be discussed, SAI Spec, Overlay HA

AMD provided an overview of their HA proposal

Small agenda this week, push to next week

Review of XSightLabs proposal
SONiC Team attendance & discussion
SAI APIs to query flow state?
Performance concerns

AMD HA presentation

1. Participants should read: https://github.com/Azure/DASH/blob/main/documentation/high-avail/design/xsight-labs-ha-proposal-new-ideas.md
2. Bring concerns to the table please
3. Proposal is an attempt to cross Reliable/Perf while remaining InterOperable

Continue API details

Definition of switch_id
Active/Active convo
Protocol definition convo

June 28, 2022
@Marian sharing OpenCompute PR for SAI APIs in the experimental section
https://github.com/opencomputeproject/SAI saiexperimentaldashha.h

We did not get through the entire set of APIs

Administrative State up/down (add enum w/more states such as starting syncing, syncing progress, sync completed, etc…)
Peer ID (used to communicate state)
IP for the session
Role (optional)

@Michal presented an HA Deep Dive slide

Please review/leave Comments for SAI HA API proposal by Marian - thank you!
https://github.com/opencomputeproject/SAI/pull/1500

June 14, 2022
Discussion of API requirements

June 7, 2022

Reliable or stateless
Synchronization and state updates discussion

No description provided.

May 5, 2022 HA WG Call

April 19, 2022 HA WG Call