docs(adr): record server boot-mode policy (ADR-0009) - #6
Merged
Conversation
Documents the non-obvious default shift introduced by PR #3 and PR #4: `orca server create` and `orca server clone` now boot from image on the compute's local disk by default, falling back to boot-from-volume only when the flavor has `disk == 0`. Records the alternatives considered (unconditional ephemeral, the `--ephemeral / --boot-from-volume` pairing that was tried first) so a future contributor reading the diff does not silently undo the choice.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
PR #3 (server create) and PR #4 (server clone) flipped the default boot mode from boot-from-volume to boot-from-image. That's a policy decision worth recording as an ADR — the kind of change a future contributor could silently undo when refactoring if they don't know the why.
Changes
Docs-only; no code change, no CI impact beyond the markdown hooks (yaml/toml/whitespace).