Skip to content

Conversation

supriya-premkumar
Copy link
Contributor

Why are these changes needed?

  • Updates operator socket format to host:v1DispersalPort;v1RetrievalPort;v2DispersalPort;V2RetrievalPort
  • Refactors parseOperatorSocket to handle v2 retrieval socket with strict port validation
  • Adds ValidatePort() to core utils
  • Adds stricter validation for operator sockets. Valid formats:
    • host:v1DispersalPort;v1RetrievalPort
    • host:v1DispersalPort;v1RetrievalPort;v2DispersalPort;V2RetrievalPort
  • Adds host validation supporting both FQDN and IP addr
  • Registers node for the new V2 retrieval service

Checks

  • I've made sure the tests are passing. Note that there might be a few flaky tests, in that case, please comment that they are not relevant.
  • I've checked the new test coverage and the coverage percentage didn't drop.
  • Testing Strategy
    • Unit tests
    • Integration tests

@supriya-premkumar supriya-premkumar force-pushed the supriya-egda-819-v1v2-port-separation branch 3 times, most recently from 6da5a24 to f33b818 Compare January 29, 2025 10:28
@supriya-premkumar supriya-premkumar force-pushed the supriya-egda-819-v1v2-port-separation branch 2 times, most recently from a34665a to c446a82 Compare January 29, 2025 21:40
@supriya-premkumar supriya-premkumar force-pushed the supriya-egda-819-v1v2-port-separation branch from c446a82 to 47d0d86 Compare January 30, 2025 20:23
Copy link
Contributor

@ian-shim ian-shim left a comment

Choose a reason for hiding this comment

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

lgtm

Copy link
Contributor

@pschork pschork left a comment

Choose a reason for hiding this comment

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

LG

@supriya-premkumar supriya-premkumar force-pushed the supriya-egda-819-v1v2-port-separation branch 2 times, most recently from 6e7971e to 4fbba32 Compare January 30, 2025 22:31
- Updates operator socket format to host:v1DispersalPort;v1RetrievalPort;v2DispersalPort;V2RetrievalPort
- Refactors parseOperatorSocket to handle v2 retrieval socket with strict port validation
- Adds ValidatePort() to core utils
- Adds stricter validation for operator sockets. Valid formats:
    - host:v1DispersalPort;v1RetrievalPort
    - host:v1DispersalPort;v1RetrievalPort;v2DispersalPort;V2RetrievalPort
- Adds host validation supporting both FQDN and IP addr
- Registers node for the new V2 retrieval service
- Removes serverv2 under v1retrieval service
- Adds a check to enable v2Enable when the v2 disperser port or v2 retrieval port is enabled
- Adds a check to ensure specified v1/v2 dispersal/retrieval ports are different
@supriya-premkumar supriya-premkumar force-pushed the supriya-egda-819-v1v2-port-separation branch from 4fbba32 to 28ce67e Compare January 30, 2025 23:48
@supriya-premkumar supriya-premkumar merged commit 8424283 into Layr-Labs:master Jan 30, 2025
9 checks passed
@supriya-premkumar supriya-premkumar deleted the supriya-egda-819-v1v2-port-separation branch January 31, 2025 00:01
pschork added a commit that referenced this pull request Jan 31, 2025
pschork added a commit that referenced this pull request Feb 2, 2025
Update dataAPI swagger BlobFeed response to resolve correct v2.BlobHeader

Add Makefile docker-node-group for testing local node
Add Makefile run target for running local node (requires local .env)
Add Makefile run-update-socket target (requires local .env)
Add Makefile run-update-socket-v1 target (requires local .env)
Add Makefile run-list-quorums target (requires local .env)

Fix swagger gen for v2 BlobHeader

Rebase #1181

Add `--disableV1` flag to disable v1 when running in isolation mode

Change requirement that V2 ports are specified when V2 is disabled. It
was previously impossible to disableV2 without defining v2 ports.
```
2025/01/31 11:26:53 application failed: enable v2 flag needs to be set when v2 dispersal port (NODE_V2_DISPERSAL_PORT) is specified
```
but if V2 ports were unset then node would still fail to start regardless if `--enableV2` was set or not
```
2025/01/31 12:13:41 application failed: Required flags "node.v2-dispersal-port, node.v2-retrieval-port" not set
```
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.

3 participants