ornias
Wizard
- Joined
- Mar 6, 2020
- Messages
- 1,458
Thank you for pointing that up. I'll make sure to include a link to that discussion.@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
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.
It's a bug in the bugtracker and is being looked into.Btw all of them are private (and any new ticket in Jira right now). I don't know exactly why this is happening tho
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.@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.
I had created this one for FN/TNC, but it was closed by engineering - anyone to create a new one?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 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.I had created this one for FN/TNC, but it was closed by engineering - anyone to create a new one?
Beagle, it was not.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.
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. ;-)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.
Do you know if that has that been fixed? My tickets are still showing as "iX Private".It's a bug in the bugtracker and is being looked into.
Uhmm, new tickets should be fine I think...Do you know if that has that been fixed? My tickets are still showing as "iX Private".
I opened a ticket reporting the issue anyway: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 :)
Why make a invalid ticket (NAS tickets are not for issues with jira) instead of just asking (tagging!) the account assigned to your ticket?!I opened a ticket reporting the issue anyway:
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.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.