Feature request - VM folders
-
Something like folders might be a good way to organize something like VApps
-
@JeffBerntsen Ooooo I like this idea.
-
@olivierlambert
I know this thread has kinda gone stagnant, but is an upcoming XO/UI change planning to incorporate ACLs with tags? This feature would be greatly appreciated, as carving out ACLs for individual VMs becomes very tedious.I can currently assign VMs to self-service resources, but the default permission when doing so is "admin" and I have users where I'd like to assign a lower level roll in bulk. I know I can go back and modify that ACL, but again...tedious, especially at scale. For the self-service resources maybe adding an "Admins", "Operators", & "Viewers" component in place of the current "Users" would be easier?
Maybe there is something else I'm missing?
-
ACLs v2 will be included later in XO 6, it's not a top priority right now with the already huge amount of work to make XO 6 itself. This might change if we grow fast enough to continue to hire people to scale horizontally.
-
My 2 cents as current vSphere user (searching for replacement after new VMware prices knocked my socks off):
Tags in XO are currently only "view filtering feature", nothing more.
There is no method in XO to (without selecting each vm separately):- attach ACL to group of vms
- select group of vms for backup job
Tags are also error-prone, as I have to manually enter tag name each time (for each vm) and possibly make a typo (there are not even "hints" from current tag names).
I would like to add vm to "group" and this should cause deriving ACLs from "group" and adding to backup job assigned to "group", etc; whatever this "group" would be - folder/tag.
As I have ~500 vms, grouping is "must have" for me.
I'll live if "groups" are tags not folders.
But not having this at all in XO is BIG disadvantage for me.
(without this I quite like what I found in xcp-ng/xo).For me - something like folder seems more natural for such things than tags, but I am biased (as vSphere has folders...).
And generally - in current situation (new prices for vSphere) I suspect there may be more users like me, searching for vSphere replacement, and making XO more friendly for them would be advantage for them...
-
@lukasz-engel What do you mean by "select group of vms for backup job"? That is entirely possible unless I'm missing something, I have backup jobs that base which VMs they back up on tags.
-
We do not doubt about that: we have a component already designed to assign any properties en masse to any kind of objects. It will be usable in XO Lite & XO 6.
For the folder view, that's also something we'll do in XO 6 at least (XO Lite it's less likely, maybe). I think @clemencebx is aware about this (but repinged her
) -
@lukasz-engel said in Feature request - VM folders:
My 2 cents as current vSphere user (searching for replacement after new VMware prices knocked my socks off):
Tags in XO are currently only "view filtering feature", nothing more.
There is no method in XO to (without selecting each vm separately):- attach ACL to group of vms
- select group of vms for backup job
Tags are also error-prone, as I have to manually enter tag name each time (for each vm) and possibly make a typo (there are not even "hints" from current tag names).
I would like to add vm to "group" and this should cause deriving ACLs from "group" and adding to backup job assigned to "group", etc; whatever this "group" would be - folder/tag.
As I have ~500 vms, grouping is "must have" for me.
I'll live if "groups" are tags not folders.
But not having this at all in XO is BIG disadvantage for me.
(without this I quite like what I found in xcp-ng/xo).For me - something like folder seems more natural for such things than tags, but I am biased (as vSphere has folders...).
And generally - in current situation (new prices for vSphere) I suspect there may be more users like me, searching for vSphere replacement, and making XO more friendly for them would be advantage for them...
I do think a lot of this 'group' idea could be made possible using the self service resourceSets, especially if we were able to maybe set "Operator" ACLs on said resourceSet. Maybe even allow tags to be applied to a resourceSet so things like backups would be applied to entire resourceSets vs. an individual VM?
-
+1 on the need, but I'd suggest framing it as a lighter first step rather than full folders.
Since tags are already first-class objects in XO , most of the "at a glance" need would be covered by an alternative tree grouping mode: instead of the current Pool > Host > VM hierarchy, let the navigation tree group VMs by tag.
A VM with multiple tags would simply appear under each matching tag node — which is arguably more flexible than folders (where a VM lives in exactly one place), and it sidesteps the hard part @olivierlambert flagged earlier (scope / ACL inheritance), because this is purely a presentation layer on top of data that already exists.
-
Feel free to vote if it exists or create a request on https://feedback.vates.tech
-
I didn't find a similar request, I added:
https://feedback.vates.tech/posts/87/group-vms-by-tag-in-the-navigation-tree
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login