So far so good. I renamed it, but it was still listed first in the list when creating an image for a VM. After closing out my browser and reconnecting, it’s now behaving as I’d expect - in alphabetical order.
On Jun 22, 2017, at 7:57 AM, Martin Sivak <msivak@redhat.com> wrote:
I do not see any reference to the name in the engine source code. Hosted engine agent uses UUID to identify it. So I think it should be fine.
Martin
On Thu, Jun 22, 2017 at 4:49 PM, aduckers <alex.duckers@gmail.com> wrote:
Can it be safely renamed? It looks like the GUI will let me but I don’t feel confident that it won’t create other issues.
On Jun 22, 2017, at 1:56 AM, Fred Rolland <frolland@redhat.com> wrote:
As a workaround, I think that the list of storage domains in the new disk window is sorted alphabetically. You can try to edit the name of the storage domain to be on the bottom of the list and not first.
On Thu, Jun 22, 2017 at 11:42 AM, Chris Boot <bootc@bootc.net> wrote:
On 19/06/17 15:30, Mike Farnam wrote:
Hi All - Is that a way to mark hosted_storage somehow so that it’s not available to add new VMs to? Right now it’s the default storage domain when adding a VM. At the least, I’d like to make another storage domain the default. Is there a way to do this?
This would be a nice thing to have.
AIUI, however, the oVirt folks are working towards not needing a dedicated storage domain for the hosted engine, which may alleviate this particular gripe. That being said, it would otherwise be nice to mark a storage domain as not usable for new volumes (a bit like the allocatable option for LVM physical volumes).
Cheers, Chris
-- Chris Boot bootc@bootc.net _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users