Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking issue for RFC 696 #722

Open
12 of 51 tasks
xla opened this issue Jul 1, 2021 · 0 comments
Open
12 of 51 tasks

Tracking issue for RFC 696 #722

xla opened this issue Jul 1, 2021 · 0 comments
Assignees

Comments

@xla
Copy link
Contributor

xla commented Jul 1, 2021


  • systemd support
    • implement socket activation
    • test socket activation
    • add service definition templates
  • launchd support
    • implement socket activation
    • test socket activation
    • add service definition templates
  • run peer
    • drive network protocol
    • ensure rebinding
    • ensure graceful shutdown
    • get read&write access on behalf of current profile
    • provide tincans to subroutines
    • expose config knobs via cli params
  • protocols
    • announcements
      • implement protocol
      • implement subroutine
      • expose config via cli params
    • API
      • implement protocol
      • implement subroutine
      • expose config via cli params
      • implement auto-shutdown once last connection is closed
    • replication requests
      • implement protocol
      • implement subroutine
      • expose config via cli params
    • tracking
      • implemnt protocol
      • implement subroutine
      • expose config via cli params
  • API lib
    • implement request-response payloads
    • implement payload serialisation
    • implement RPC client
    • implement RPC server on UNIX domain socket
  • expose knobs for logging/tracing
  • metrics
    • implement prometheus metrics
    • expose internals (tasks, etc.)
  • documentation
    • generate man pages

Blocking issues/PRs:

@xla xla self-assigned this Jul 1, 2021
xla added a commit that referenced this issue Sep 14, 2021
First iterative implementation of RFC 0696 focusing on driving the core
peer protocol and establishing the harness for configuration of a running node.
Rite of passage for it will be replacement of the ephemeral peer in the e2e
networkss, as that requires a well behaved peer with a set of knobs exposed.

Structurally the majority of the implementation lives in a library crate
node-lib. The code is rather Mario-esque as it is primarily plumbing of code
that either existed in other crates backing binaries or newish code doing the
same thing for core pieces.

There are still large pieces missing, which a tracked in #722 and will be
piled on-top as patches to keep this already big delta focused. The declared
initial goal is to get linkd into a state where it can run as bootstrap/seed
node.

Signed-off-by: Alexander Simmerl <a.simmerl@gmail.com>
xla added a commit that referenced this issue Sep 14, 2021
First iterative implementation of RFC 0696 focusing on driving the core
peer protocol and establishing the harness for configuration of a running node.
Rite of passage for it will be replacement of the ephemeral peer in the e2e
networkss, as that requires a well behaved peer with a set of knobs exposed.

Structurally the majority of the implementation lives in a library crate
node-lib. The code is rather Mario-esque as it is primarily plumbing of code
that either existed in other crates backing binaries or newish code doing the
same thing for core pieces.

There are still large pieces missing, which a tracked in #722 and will be
piled on-top as patches to keep this already big delta focused. The declared
initial goal is to get linkd into a state where it can run as bootstrap/seed
node.

Signed-off-by: Alexander Simmerl <a.simmerl@gmail.com>
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

No branches or pull requests

1 participant