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

zero touch device registration #36

Open
Vad1mo opened this issue Jul 26, 2024 · 7 comments · May be fixed by #54
Open

zero touch device registration #36

Vad1mo opened this issue Jul 26, 2024 · 7 comments · May be fixed by #54

Comments

@Vad1mo
Copy link
Contributor

Vad1mo commented Jul 26, 2024

Is there a way how a satellite can register to ground control, are there zero touch capable solutions?

@kunal-511
Copy link

Cloud-Based Registration Services: Cloud-based services provide a centralized registration platform for satellites, enabling zero-touch registration and management.
Some popular zero-touch capable solutions include:
1.Red Hat Satellite
2.AWS Ground Station
3.SaltStack

@Vad1mo
Copy link
Contributor Author

Vad1mo commented Jul 30, 2024

Thank you ChatGPT

@kunal-511
Copy link

Ya meta AI😅😂

@bupd
Copy link
Collaborator

bupd commented Aug 13, 2024

here's some idea I had regarding the zero touch registration.
excalidraw 1

@Vad1mo
Copy link
Contributor Author

Vad1mo commented Aug 13, 2024

A sequence diagram would be helpful @bupd

@bupd
Copy link
Collaborator

bupd commented Aug 16, 2024

Sequence Diagram

Sequence Diagram

Breakdown of the Process Flow

Participants:

GC (Ground Control): Manages satellites, registration, and grouping.
Satellite: Edge devices that connect to Ground Control and fetch artifacts.
Reg (Central Registry): Stores and provides access to OCI-compliant artifacts.
Operator: The person managing the Ground Control system.
  1. Token Generation and Deployment:

    • GC generates a general token.
    • Independently deploy the Satellite with this general token.
  2. Satellite Registration:

    • Satellite calls /ztr/reg on GC with the general token.
    • GC confirms the registration and issues a unique token to the Satellite.
  3. Updating and Grouping:

    • GC updates the list of registered and online satellites.
    • Operator (GC Operator) accepts the satellite registration.
    • Operator creates a group and assigns the Satellite to this group.
  4. Artifact Management:

    • Operator groups artifacts from the Central Registry.
    • GC pushes the grouped artifacts to the OCI repository associated with the satellite group.
  5. Communication with Satellite:

    • GC sends the Satellite the registry URL, authentication parameters, and group assignment.
    • Satellite subscribes to the appropriate OCI repository and fetches artifacts.
    • Satellite sends regular heartbeat/ping signals to GC.

cc // @Vad1mo

@bupd
Copy link
Collaborator

bupd commented Aug 21, 2024

Better Sequence Diagram

Sequence diagram

@Vad1mo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Ready
3 participants