-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
host groups #2791
Comments
yes, we have a long list of servers (many, many virtual) that I have in I guess you could go further and have 'group summary' stats on the dashboard but just having them in categories would help with handling 20+ hosts. On 21/09/15 14:51, Stef Walter wrote:
|
@michaelwemoto Is this something you're interested in working on? I've placed it on our ideas page: |
@stefwalter Unfortunately I'm not so much a dev as an admin, I wouldn't know where to begin. sorry I couldn't be of more help. |
Makes sense. Hopefully someone will pick this up at some point. It may fit better once we have a more complete dashboard. It's at the top of the ideas page. |
Hello guys, is there an update on this topic? I'm new cockpit user and have the same idea and if there is somebody who working on it I would like to help or if there isn't I will start to working on it. |
I am afraid there is no update. |
@marusak How can I get more details about the changes? |
@garrett is currently designing it. |
While at the face-to-face meeting during DevConf at the end of Jan, I wanted to have automatic grouping of some sort, but rethought the idea as the auto-grouping didn't make sense. Since we're going to drop the graphs (as focused dashboard tooling would be better than anything we could provide), Cockpit would be able to scale to support additional hosts. Having some sort of grouping, as suggested in this issue, would help to make sense of a larger number of hosts. (The alternative is to rename the hosts to be descriptive, such as TL;DR: After seeing this issue* and reading the request, I think grouping makes sense and would like to work it into the dashboard mockup. * (thanks, @roskogabor, for asking about an update and then @marusak for mentioning me) I think we'd have an ungrouped list of hosts by default (and don't show the group title). When the first group is made, it should then show the custom groups first, then the "ungrouped" group of hosts. Adding hosts to a group could be done in the edit host dialog, with a dropdown of groups with a "new group" option that would then show an input field for the new group name. Additionally, when editing the hosts list with a toggle (as it's not a common occurance and the remove and edit buttons could otherwise be clicked too easily), we could have an edit group option exposed as well. Clicking it could then edit the group from a top-down instead of bottom-up approach: It would show a list of hosts and allow you to check them to move the hosts into that group. In other words: Dynamic groups and groups are set in the host config settings (where colors are currently set). We could also possibly have group editing (once groups are active). A mockup would probably be a bit easier to understand than my explanation above, so I'll try to work it in. No promises on if it'd make it in or when, however. It would have to be done on a second pass. A first pass would include existing functionality (minus the graphs). We would ideally follow back up with another iteration or two to add status and/or group support. But I do think this is would be a useful feature to have. Let's see what we can do. 😉 |
Additional nice feature would be to trigger updates for host groups? |
Groups would also be a great way to have a quick list of hosts available for live migration in cockpit-machines. That way you could choose from the hosts in the group or enter a URI if you need to do something specific/special (I realize this is a year later, but I can think of no better place to put this) |
We are actually moving away from managing multiple hosts. The dashboard is no more, there is a technical limit how many hosts you can connect to at the same time, and we even considered to entirely disable this functionality as it is insecure (we aren't actually going to, though). Moreover, this kind of grouping would be cockpit specific and only live in a single browser's localstorage. I don't see an appropriate system API to do this. As such, this is hard to implement, a fringe case, and low benefit, and hasn't made any progress in 7 years. We have plenty of other issues to work on. |
I would love to see some organisation of hosts, could there be a feature to add groups?
for example, a web group that could contain all web servers? a mail group for mail servers and mailing list servers? workstations for local machines?
The text was updated successfully, but these errors were encountered: