Skip to content

chore: document next steps #172

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.

Sign up for GitHub

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

Open
johnabass wants to merge 1 commit into
base: main
Choose a base branch
from
+30 −0
Open

chore: document next steps #172

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions WHATSNEXT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
# What's next?

## Code cleanup

`hashy` is in a prototype state at the moment. It needs some refactoring to clean things up.

## Currently implemented

- Loading groups from one or more .zone files
- Building one hash ring for each group
- Responding to DNS queries with entries selected from hash rings

## Currently not implemented

- Loading groups from another data source, such as:
- Another DNS server, e.g. Route53. This could involve zone transfers.
- A database
- A bulk interface for doing reverse hashes (e.g. which devices should hash to a given talaria)
- Integration with existing services:
- Petasos (existing DNS interface)
- Scytale (existing DNS interface)
- Talaria (unimplemented bulk interface)
- DNSSEC and security

## Open issues

- How to do zone transfers
- Should hashy be deployed via anycast, multicast, etc?
- How the bulk interface should be secured
- Rendezvous vs consistent hashing
Loading