GNOME Bugzilla – Bug 699315
Make it possible to manage brokers
Last modified: 2018-01-11 10:05:22 UTC
Libvirt connections are created using e.g. qemu:///system. Only way how to remove these connections is delete config files which are stored in .config/gnome-boxes/sources directory like qemu____system, localhost... It could be nice to have a possibility to remove these connections in gnome-boxes UI. Steps: Boxes is running. 1. Click on New button and then on Continue. 2. Click on Enter URL. 3. Enter collection URI qemu:///system and click on Continue. 4. Click on Create button. 5. Fill password and click on Authenticate. 6. Remove a connection - delete qemu____system. Are there other options?
It will probably need some kind of settings dialog to remove brokers.
(In reply to comment #1) > It will probably need some kind of settings dialog to remove brokers. While we are at that, we might as well think about allowing to edit options/URL etc. Would like UI designers input on this for sure.
The missing design is for the following cases: - Remove a broker connection that is no longer needed. - My access rights to the broker have been revoked
just wondering if we shouldn't allow detaching of just a single system broker box as there is an option to import it under New. Delete is probably something we always don't want to do with imported system broker machines.
(In reply to comment #3) > The missing design is for the following cases: > > - Remove a broker connection that is no longer needed. > - My access rights to the broker have been revoked Still is. :)
I'm wondering. Maybe all this should be handled by gnome-online-accounts?
When I've played with wires today[1] I must say maintaining broker connections in Boxes itself seems unnecessary perhaps. I ended up pretty much duplicating the online accounts panel. We might still provide a path to get to GOA from the setup assistant, but it seems like something we could indeed have in GOA. What do you think, Jon? [1] https://raw.githubusercontent.com/gnome-design-team/gnome-mockups/master/boxes/wires/newbox-assistant-broker.png
We really should decide whether or not we want this in Boxes. Maybe Allan can do the hard part of deciding for us. :)
Apart from deletion and editing of properties, we probably should also display if broker is connected or not, an error message in case connection attempt had failed etc. This will satisfy https://bugzilla.gnome.org/show_bug.cgi?id=744002#c1 .
to summarize what should be possible in GUI: 1. show stored sources 2. turn off source autoconnect 3. connect disconnected sources 4. delete source 5. see box origin in overview if other from session (system, ovirt, vnc, spice, etc). To distinguish between several sources of the same type we need address, too. 99.filtering based on sources (but that's a different story)
(In reply to vladimir benes from comment #10) > to summarize what should be possible in GUI: Thanks for the summary. > 2. turn off source autoconnect > 3. connect disconnected sources I think #2 will be easily covered by #3. i-e turning off the broker implies turning off autoconnect on startup. > 5. see box origin in overview if other from session (system, ovirt, vnc, > spice, etc). To distinguish between several sources of the same type we need > address, too. > 99.filtering based on sources (but that's a different story) These are not management related so shouldn't be part of management UI. I believe we have separate bugs for these already.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-boxes/issues/14.