amery/jpictl
2
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

rings: Prefix and Address factories #48

Merged
karasz merged 6 commits from pr-amery-rings into main 2024-05-29 17:44:11 +02:00
Conversation 2 Commits 6 Files Changed 3
+265
amery commented 2024-05-28 00:17:31 +02:00
Owner
Copy Link
Copy Source
  • ring 0 (backbone connecting all zones), 16 bits prefix.
  • ring 1 (per-zone lan), 20 bits prefix.
  • ring 2 (global services), 20 bits prefix.
  • ring 3 (pods of a region cluster), 12 bits prefix.
* ring 0 (backbone connecting all zones), 16 bits prefix. * ring 1 (per-zone lan), 20 bits prefix. * ring 2 (global services), 20 bits prefix. * ring 3 (pods of a region cluster), 12 bits prefix.
amery added 6 commits 2024-05-28 00:17:31 +02:00
rings: introduce RegionID, ZoneID and NodeID 378bab2f96 
and a Valid() method to check if their value is within the
valid range.

Signed-off-by: Alejandro Mery <amery@jpi.io>
rings: introduce generic ErrOutOfRange() factory 52e1195139 
Signed-off-by: Alejandro Mery <amery@jpi.io>
rings: RingOnePrefix()/RingOneAddress() 859e307ac4 
Ring one designates the (virtual) local network of a zone
within a region.

Signed-off-by: Alejandro Mery <amery@jpi.io>
rings: RingZeroPrefix()/RingZeroAddress() 127a5830cc 
Ring zero corresponds to the backbone that connects all zones.

Signed-off-by: Alejandro Mery <amery@jpi.io>
rings: RingThreePrefix() 1d7b37c3e7 
Ring 3 corresponds to the pods of the kubernetes cluster of a region

Signed-off-by: Alejandro Mery <amery@jpi.io>
rings: RingTwoPrefix() 16f6f1141c 
Ring 2 is the service network shared by all kubernetes clusters.

Signed-off-by: Alejandro Mery <amery@jpi.io>
amery requested review from karasz 2024-05-28 00:17:37 +02:00
amery added 1 commit 2024-05-28 02:52:19 +02:00
rings: DecodeRingZeroAddress() and DecodeRingOneAddress() 349b5a7df1 
Signed-off-by: Alejandro Mery <amery@jpi.io>
amery force-pushed pr-amery-rings from 349b5a7df1 to 16f6f1141c 2024-05-28 03:21:34 +02:00 Compare
amery added 4 commits 2024-05-28 16:36:51 +02:00
rings: RingOnePrefix()/RingOneAddress() 394a84c3ab 
Ring one designates the (virtual) local network of a zone
within a region.

Signed-off-by: Alejandro Mery <amery@jpi.io>
rings: RingZeroPrefix()/RingZeroAddress() 0f177acf57 
Ring zero corresponds to the backbone that connects all zones.

Signed-off-by: Alejandro Mery <amery@jpi.io>
rings: RingThreePrefix() 6142d0f7f0 
Ring 3 corresponds to the pods of the kubernetes cluster of a region

Signed-off-by: Alejandro Mery <amery@jpi.io>
rings: RingTwoPrefix() 72a2468a10 
Ring 2 is the service network shared by all kubernetes clusters.

Signed-off-by: Alejandro Mery <amery@jpi.io>
amery commented 2024-05-28 16:52:12 +02:00
Author
Owner
Copy Link
Copy Source

moved RingFooPrefix() and RingFooAddress() to encode.go in preparation for decode.go @karasz

moved `RingFooPrefix()` and `RingFooAddress()` to `encode.go` in preparation for `decode.go` @karasz
karasz approved these changes 2024-05-29 17:41:05 +02:00
karasz left a comment
Owner
Copy Link
Copy Source

LGTM

LGTM
karasz merged commit e1186975a6 into main 2024-05-29 17:44:11 +02:00
karasz deleted branch pr-amery-rings 2024-05-29 17:44:11 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
karasz
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
karasz (Nagy Károly Gábriel) amery (Alejandro Mery)
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: amery/jpictl#48
Delete Branch "pr-amery-rings"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?