Are these Virtualization features on the roadmap?

[ornias]

@beagle That being said:
(6) Import/Export VMs in OVA format

The guys/galls trying to install HassOS on SCALE would be very happy if that gets in :)
It might be worth while adding a link to their topic/discussion about how hard it is to get running in your issue, as a showcase

 

[beagle]

@beagle That being said:
(6) Import/Export VMs in OVA format

The guys/galls trying to install HassOS on SCALE would be very happy if that gets in :)
It might be worth while adding a link to their topic/discussion about how hard it is to get running in your issue, as a showcase

Thank you for pointing that up. I'll make sure to include a link to that discussion.

 

[beagle]

I've created tickets on Jira for the suggestions in the OP.

If you are interested in any of my suggestions please vote on its ticket on Jira.

(1) UI / UX

- Create tabbed view aggregating all the features/details of each VM

https://jira.ixsystems.com/browse/NAS-110419

(2) Network

- Show the IP address(es) assigned to a VM

https://jira.ixsystems.com/browse/NAS-110420

(3) Storage

- Add option to increase VM disk size directly from VM disk details

https://jira.ixsystems.com/browse/NAS-110435

- Import/Export VM disks

https://jira.ixsystems.com/browse/NAS-110436

(4) Snapshots

- Integrate snapshot in VM menu

https://jira.ixsystems.com/browse/NAS-110439

- Create VMs based on a snapshot of an existing VM

https://jira.ixsystems.com/browse/NAS-110440

(5) Templates

- Create/use VM templates and cloud-init

https://jira.ixsystems.com/browse/NAS-110441

(6) Import/Export VMs in OVA format

https://jira.ixsystems.com/browse/NAS-110442

(7) VM migration between nodes

https://jira.ixsystems.com/browse/NAS-110443

 

[stavros-k]

I've created tickets on Jira for the suggestions in the OP.

If you are interested in any of my suggestions please vote on its ticket on Jira.

Btw all of them are private (and any new ticket in Jira right now). I don't know exactly why this is happening tho

 

[ornias]

Btw all of them are private (and any new ticket in Jira right now). I don't know exactly why this is happening tho

It's a bug in the bugtracker and is being looked into.

 

[cyrus104]

@beagle
Great job, I also use XCP-ng / XO and fine a lot of the features you point to be very useful and convenient, I would love to see similar implementations get added to SCALE.

 

[beagle]

@beagle
Great job, I also use XCP-ng / XO and fine a lot of the features you point to be very useful and convenient, I would love to see similar implementations get added to SCALE.

SCALE has the foundation to be a solid storage appliance like Core already is. It just needs to develop and polish a bit more the Containerization and Virtualization features to become a complete hyperconverged solution.

iXsystem is on the right path. Slow and steady wins the race ;-)

 

[ornias]

@beagle You can add:
"Correct Intel GVT-D support" to the list....

 

[e7balt]

Unless I'm missing something, there does not seem to be a way to control the VM start order and set an auto start delay for VMs in TrueNAS scale. That seems like a really important feature to have, especially when running multiple virtual machines.

On a somewhat related note, I've noticed that when updating, rebooting, or shutting down TrueNAS Scale, it seems to just power off the VMs rather than giving them time to shutdown gracefully. Is there a way to give time for the VMs to gracefully shutdown before TrueNAS Scale reboots? I do see there is a "Shutdown Timeout" setting in each VM that defaults to 90 seconds, but at least as far as I can tell my VMs are just getting powered off immediately (rather than telling the guest OS to shutdown gracefully and giving them time to do so). Within a Windows VM, I can specifically see that the OS reports that the system was shutdown unexpectedly upon my next logon. Maybe I'm missing something with my configuration?

Thanks!

 

[Patrick M. Hausen]

Unless I'm missing something, there does not seem to be a way to control the VM start order and set an auto start delay for VMs in TrueNAS scale. That seems like a really important feature to have, especially when running multiple virtual machines.

I had created this one for FN/TNC, but it was closed by engineering - anyone to create a new one?

https://jira.ixsystems.com/browse/NAS-100166

 

[ornias]

@Patrick M. Hausen Moving things to suggestions just to excuse yourself for ignoring them seems like quite a dick move tbh.
The only reason there isn't more tracktion is because they didn't care to implement it.

 

[beagle]

I had created this one for FN/TNC, but it was closed by engineering - anyone to create a new one?

https://jira.ixsystems.com/browse/NAS-100166

I think it was closed because it may have been created on the wrong category. It probably should be in "Suggestion" instead of "New Feature". When I tried to create my tickets as "New Feature" I received an error message saying only engineers could open tickets in that category.

 

[ornias]

I think it was closed because it may have been created on the wrong category. It probably should be in "Suggestion" instead of "New Feature". When I tried to create my tickets as "New Feature" I received an error message saying only engineers could open tickets in that category.

Beagle, it was not.
The suggestion catagory didn't exist back in that day (look at how old that ticket is).
They closed is because they want to push it to the suggestion catagory, which they can ignore untill it gets 10 upvotes.

 

[beagle]

The suggestion catagory didn't exist back in that day (look at how old that ticket is).
They closed is because they want to push it to the suggestion catagory, which they can ignore untill it gets 10 upvotes.

I didn't notice the date. They should have been clear about the reason for closing the ticket. And if that's the policy, it's better to open a new ticket and let's ramp up those votes. ;-)

 

[beagle]

It's a bug in the bugtracker and is being looked into.

Do you know if that has that been fixed? My tickets are still showing as "iX Private".

 

[ornias]

Do you know if that has that been fixed? My tickets are still showing as "iX Private".

Uhmm, new tickets should be fine I think...
I don't think it's magically fixed for older tickets... @Kris Moore should be able to tell more about the fix that is or isn't applied by now :)

 

[beagle]

Uhmm, new tickets should be fine I think...
I don't think it's magically fixed for older tickets... @Kris Moore should be able to tell more about the fix that is or isn't applied by now :)

I opened a ticket reporting the issue anyway:

https://jira.ixsystems.com/browse/NAS-110629

 

[ornias]

I opened a ticket reporting the issue anyway:

https://jira.ixsystems.com/browse/NAS-110629

Why make a invalid ticket (NAS tickets are not for issues with jira) instead of just asking (tagging!) the account assigned to your ticket?!

These kinds of tickets are the reason a lot of companies have a private bigtracker tbh.

 

[beagle]

Why make a invalid ticket (NAS tickets are not for issues with jira) instead of just asking (tagging!) the account assigned to your ticket?!

These kinds of tickets are the reason a lot of companies have a private bigtracker tbh.

All the tickets were open as "Suggestion" and assigned to the "Triage Team" so unless I can tag them here I see no other option but raising a ticket to get the issue addressed. If there is anyone I should be tagging when the tickets are assigned to the "Triage Team" I would be happy to tag this person and close the ticket.

 

[ornias]

Maybe you should look at what I wrote and tagg the person I forwarded you towards? ;-)