Skip to content
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.

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

Tidy docs for Device API #4361

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

sftim
Copy link
Contributor

@sftim sftim commented Jan 12, 2024

Changes

Tidying for https://github.com/firecracker-microvm/firecracker/blob/main/docs/device-api.md

Reason

Minor cleanups for readability and context.

License Acceptance

By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license. For more information on following
Developer Certificate of Origin and signing off your commits, please check
CONTRIBUTING.md.

PR Checklist

  • If a specific issue led to this PR, this PR closes the issue.
  • The description of changes is clear and encompassing.
  • Any required documentation changes (code and docs) are included in this PR.
  • API changes follow the Runbook for Firecracker API changes. not applicable
  • User-facing changes are mentioned in CHANGELOG.md. not applicable
  • All added/changed functionality is tested. not applicable
  • New TODOs link to an issue. not applicable
  • Commits meet contribution quality standards.

  • This functionality cannot be added in rust-vmm.

@sftim sftim force-pushed the 20240112_docs_tidy_device_api branch from 59077a3 to 5376f38 Compare January 12, 2024 11:50
Signed-off-by: Tim Bannister <tim@scalefactory.com>
@sftim sftim force-pushed the 20240112_docs_tidy_device_api branch from 5376f38 to 5d099cf Compare January 12, 2024 11:53
@sftim sftim marked this pull request as ready for review January 12, 2024 11:53
Copy link
Contributor

@ShadowCurse ShadowCurse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @sftim, thx for the PR. Unfortunately changes here seem not very accurate/correct.
Can you describe why did you think they were necessary?

Comment on lines +3 to +4
Firecracker provides the _Device_ API to let you manage the virtual hardware
available inside each microVM.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no Device API. The Device-API means Device <-> API matrix.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK. Good to know. The existing doc is confusing.

required for an API call to be usable.

**O** - Optional: The device (column) **is not required** for a Firecracker
microVM API call to succeed. If the device (column) is omitted from a uVM
microVM API call to succeed. If the device (column) is omitted from a μVM
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We prefer to use either microvm or uVM to describe VM. Adding third type of wording will only increase the confusion.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's use microVM. The docs don't use “uVM” outside this page.

(μ is an abbreviation for micro, which is why I suggested it).

@sftim sftim marked this pull request as draft January 15, 2024 15:24
@sftim
Copy link
Contributor Author

sftim commented Mar 4, 2024

I haven't found time yet to redo this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants