Standalone Gateways

Open
#1,472 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
networking

Research direction

Start by reviewing the linked issues in tf_operations and zos, especially #1889 and #1174, to understand the existing gateway and provider requirements. The issue does not name implementation files, tests, or a concrete completion condition; clarify the chosen architecture and scope before identifying the work needed.

Written by the indexing model from the issue text.

Description

type_story

Gateways is a built in feature of ZOS which allows users to create public gateways from the public internet to the private workloads of the user over wireguard or yggdrasil.

Benefits of using zos gateway primitive:

  • Integrated with the same ZOS api workload/deployment so no need to develop different APIs for it
  • Integrated with the billing system, consumption are reported as part of user consumption report
  • Most importantly, integration with the zos networking and user layout network, which allows the gateway to reach to the user private workloads.

If we have to build a standalone gateways that acts like this, it will need to re-implement huge parts of zos specially for the networking part. This is why i think the best course of action is to run entire zos node and limit it's support to only network+gateway workloads.

Gateways always also work as access points as well.

So from here we can tell we have only 2 paths:

  • Use ZOS for standalone gateways, you get everything for free.
  • Strip down the gateway with all supporting components, this is actually more work than it sounds to get everything right specially running the network workloads, and billing
  • Make zos installable on any system with say apt ?!

The other path is to make zos usable on other service providers, this still require some work to be able to deal with provided hardware (specially the networking) but in total that's still less work than separating the gateway part.

Dominant language
No language data
Stars
13
Forks
4
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from threefoldtech/grid_wiki

All issues in threefoldtech/grid_wiki

Similar issues

More Networking issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.