Skip to content

docs: add deployment assumptions, security model, and build troubleshooting steps - #54

Open
roshan-ku wants to merge 7 commits into
OpenVisualCloud:mainfrom
roshan-ku:docs/troubleshooting-pip-nasm
Open

docs: add deployment assumptions, security model, and build troubleshooting steps#54
roshan-ku wants to merge 7 commits into
OpenVisualCloud:mainfrom
roshan-ku:docs/troubleshooting-pip-nasm

Conversation

@roshan-ku

Copy link
Copy Markdown
Contributor

Description

Checklist

Code Quality

  • Code follows project style guidelines
  • No unnecessary debug logs or commented-out code
  • No hardcoded values / secrets

Testing

  • Unit test added/modified accordingly
  • Perform manual basic sanity testing at system level

Review Readiness

  • PR title and description are clear and meaningful
  • Story/Task IDs are linked

Documentation

  • README or relevant docs updated (if applicable)

Security

  • No sensitive data exposed (keys, passwords, tokens)
  • Input validation added where needed

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Documentation content changes
  • Testing
  • Other... Please describe:

Document the dedicated-switch trust boundary raised in the SDLE review:

- New docs/assumptions.md covering the TX host / dedicated L2 switch /
  receiver topology inside the locked cabinet, the deployment assumptions
  the security model depends on, the security properties the toolkit does
  not provide (security follows MTL and ST 2110, offloaded to physical and
  L2 isolation), and the residual risk with mitigations.
- Link the new document from the README overview and from Security.md,
  which now also states the in-scope and out-of-scope components.
@roshan-ku roshan-ku changed the title docs: add pip --break-system-packages and nasm troubleshooting steps docs: add deployment assumptions, security model, and build troubleshooting steps Aug 19, 2026
Comment thread README.md Outdated
Replace the ffmpeg-plugin-extra-pixel-format tag with commit
7bee24231c864d12da6db2c2ffbfd3986717af5a in the clone instructions and in
all MTL documentation links, so the build steps reference a fixed commit
rather than a movable tag.

Addresses PR review feedback.
- environment-check: rename the mtl-version input to mtl-commit and default
  it to 7bee24231c864d12da6db2c2ffbfd3986717af5a, matching the commit the
  README now documents. The env cache key picks up the new value
  automatically, so runners rebuild instead of restoring a stale MTL.
- daily_build: raise the libFuzzer run from 300s to 7200s per sanitizer
  mode and extend the job timeout to 300 minutes to cover both modes plus
  the builds.
…otes

- daily_build: libFuzzer runs 3600s per sanitizer mode (~2h total) with a
  138 minute job timeout.
- README: 12-bit pix_fmts require MTL and FFmpeg to both be built from the
  pinned commit, since the plugin sources are compiled into libavdevice.
- README: drop the stale instruction to hand-patch mtl_common.h for
  p2_port..p7_port; those AVOptions are present at the pinned commit, so
  8 NICs work with the default FFmpeg TX path unpatched.
Comment thread .github/workflows/daily_build.yml
uses: ./.github/actions/analysis/libfuzzer
with:
max-seconds: '300'
max-seconds: '3600'

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

check if this runs for 2 hrs or 1 hr in your fork

Comment thread .github/workflows/daily_build.yml
- afl-fuzz job: max-seconds 300 -> 7200 (single AFL run, so 2h total) and
  timeout-minutes 25 -> 138 to leave headroom for install and build.
- Corpus seeds were written against an older schema: fps/fmt were placed in
  the video object but the parser reads them from tx_video, so the tx_video
  branch was never exercised. Moved them and added scale_width/scale_height.
- Added nic_index to interfaces[] and tx_sessions[].
- New seeds for parameters with no coverage: ptp_config.json (ptp enable/pi/
  unicast booleans), screen_capture.json (input_mode/screen_input) and
  multi_nic.json (multiple interfaces, 12-bit fmt, session-to-NIC mapping).
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