-
Notifications
You must be signed in to change notification settings - Fork 491
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
NAS-130523 / 25.04 / Container support using Incus #14592
Conversation
e03876c
to
bf66dfa
Compare
@anodos325 @yocalebo I know this is not 100% yet but maybe this is acceptable for landing without major changes and the rest can be done through subsequent PRs. UI team is in need of work and perhaps this is enough for them to get started. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should also add some changes so that relevant datasets being used are reported as such by pool.dataset.details
src/middlewared/middlewared/plugins/service_/services/pseudo/misc.py
Outdated
Show resolved
Hide resolved
src/middlewared/middlewared/plugins/service_/services/pseudo/misc.py
Outdated
Show resolved
Hide resolved
src/middlewared/middlewared/plugins/service_/services/pseudo/misc.py
Outdated
Show resolved
Hide resolved
@Qubad786 thanks for the thorough review. I think I have handled most of the points raised with a reply so far, please let me know if I have forgotten anything. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some more nits
@@ -336,6 +339,22 @@ def build_details(self, mntinfo): | |||
'mount_info': self.get_mount_info(path_config['source'], mntinfo), | |||
}) | |||
|
|||
# virt instance | |||
for instance in self.middleware.call_sync('virt.instance.query'): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this expensive btw?
We usually want this endpoint to be very fast and in that case we might want to be as selective as we can be in terms of what we are retrieving if getting everything is expensive comparatively
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the alternative?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, this looks good from my viewpoint. I'm going to approve but I'd like @Qubad786's final approval before it's merged. (Also make sure the database migration ID's are still correct since we've had some migrations since this PR was opened up).
e594f8c
to
dce7f20
Compare
retest this please |
This PR has been merged and conversations have been locked. |
This PR should cover the basics for having LXC containers.
The device handling is incomplete (especially GPU) but I believe that can be completed in another set of PRs.
It should be enough for development of UI for the majority of functionality.