Skip to content
This repository has been archived by the owner on Apr 18, 2024. It is now read-only.

L1 Bootstrapping #10

Open
aarshkshah1992 opened this issue May 25, 2022 · 2 comments
Open

L1 Bootstrapping #10

aarshkshah1992 opened this issue May 25, 2022 · 2 comments
Assignees
Labels
L1 Requires work on the L1 node Orchestrator Requires work on the Orchestrator swarm-connectivity
Milestone

Comments

@aarshkshah1992
Copy link
Contributor

aarshkshah1992 commented May 25, 2022

When an L1 node comes up:

  • It connects to a pre-configured Bootstrapper and registers itself.
  • The Bootstrapper geo-locates the L1.
  • The Boostrapper shares information about geo-located L1s with L2s as per L2 Boostrapping #9 to form the L1s Swarm.
  • The L1 periodically pings the Boostrapper to register liveliness (so Bootstrappers keep these L1s in their list).
  • L1 pings an L2 when an L2 connects to it as per L2 Boostrapping #9 and only admits an L2 to it's Swarm if the measured RTT is below a certain threshold.

Note that an L1s can always ask the Bootstrapper for more L2s periodically if it's Swarm size drops below a certain threshold. But, we will implement this post MVP.

@aarshkshah1992 aarshkshah1992 added L1 Requires work on the L1 node Orchestrator Requires work on the Orchestrator swarm-connectivity labels May 25, 2022
@aarshkshah1992 aarshkshah1992 self-assigned this May 25, 2022
@DiegoRBaquero
Copy link

This is pretty much the orchestrator registration

@aarshkshah1992
Copy link
Contributor Author

We will reuse @DiegoRBaquero 's orchestrator for this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
L1 Requires work on the L1 node Orchestrator Requires work on the Orchestrator swarm-connectivity
Projects
None yet
Development

No branches or pull requests

2 participants