Skip to content

Add serverity and power control to leak detection HLD#2217

Open
fraserg-arista wants to merge 1 commit intosonic-net:masterfrom
fraserg-arista:leak-severity-hld
Open

Add serverity and power control to leak detection HLD#2217
fraserg-arista wants to merge 1 commit intosonic-net:masterfrom
fraserg-arista:leak-severity-hld

Conversation

@fraserg-arista
Copy link
Copy Markdown

Posting for design discussion.

Adds severity information and power control operations (for the liquid-cooled power domain) to the leak detection high-level design. The two domains are major and minor, representing leaks that require immediate and delayed shutdown, respectively.

The interface attempts to be generic enough to support different hardware implementation approaches, for both sensor technology and for whether power control is handled in hardware/firmware, software, or both.

@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown

No pipelines are associated with this pull request.

Signed-off-by: Fraser Gordon <fraserg@arista.com>
@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown

No pipelines are associated with this pull request.

@fraserg-arista
Copy link
Copy Markdown
Author

@judyjoseph I've opened this for design discussion for adding severity to leak detection.

![LCflow chart](https://github.com/sonic-net/SONiC/blob/73f11eb7ad058b214d745e9ef728b8319574edbe/images/bmc/leakage_detection_flow.png)

### 3.1 Leak severity
Depending on the placement of a leak sensor within the chassis, a given leak event will represent a "major" or "minor"
Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As per the design here, these should be changed to "critical" and "minor".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants