Decision note 0046: Keel Cloud, version 1 scope (proposed) #39
No reviewers
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Keel-Linux/handbook!39
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/decision-0046-keel-cloud-v1"
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?
Decision note 0046, proposed: the version 1 scope of Keel Cloud, which 0020 said "starts with its own decision note". Design only: no service code, no new repository, not for merging until the maintainer decides it.
Stacked on #38 (it builds on 0044 and 0045); the base moves to
mainwhen #38 merges.What it defines:
cloudsection of the spec..deb(0039), HA across three sites, IPv6 first and TLS only.The three-part justification of brief section 10 is in "Why a note, and why now", since 0024 to 0026 had moved membership and discovery to the nodes.
The IPv4 front door idea of the maintainer is recorded as a proposed addendum to 0044, in #38.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.