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

Refactoring of devices management #4542

Open
3 tasks
ShadowCurse opened this issue Apr 5, 2024 · 0 comments
Open
3 tasks

Refactoring of devices management #4542

ShadowCurse opened this issue Apr 5, 2024 · 0 comments
Labels
Status: Parked Indicates that an issues or pull request will be revisited later Type: Enhancement Indicates new feature requests Type: Fix Indicates a fix to existing code

Comments

@ShadowCurse
Copy link
Contributor

ShadowCurse commented Apr 5, 2024

There have been several discussions about the way devices, device resources and device managers need to coexist in Firecracker.
Here are some links:

Because device management is one of the key components in Firecracker we should think about the way to improve our code quality in this area as it will help us with future addition of new devices.

For now this issue can be just a hub for all thought about this topic.

Checks

  • Have you searched the Firecracker Issues database for similar requests?
  • Have you read all the existing relevant Firecracker documentation?
  • Have you read and understood Firecracker's core tenets?
@ShadowCurse ShadowCurse added Type: Enhancement Indicates new feature requests Type: Fix Indicates a fix to existing code labels Apr 5, 2024
@roypat roypat added the Status: Parked Indicates that an issues or pull request will be revisited later label Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Parked Indicates that an issues or pull request will be revisited later Type: Enhancement Indicates new feature requests Type: Fix Indicates a fix to existing code
Projects
None yet
Development

No branches or pull requests

2 participants