On 12/17/2015 10:32 PM, Willard Dennis wrote:

Hi all,

Doing the hosted engine setup on Gluster; am at the point of configuring the storage domain / datacenter names, and not sure of what my best move is here… Here’s what I’m seeing:

—— --== STORAGE CONFIGURATION ==--

During customization use CTRL-D to abort. Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs3, nfs4)[nfs3]: glusterfs [ INFO ] Please note that Replica 3 support is required for the shared storage. Please specify the full shared storage connection path to use (example: host:/path): localhost:/engine [WARNING] Due to several bugs in mount.glusterfs the validation of GlusterFS share cannot be reliable. [ INFO ] GlusterFS replica 3 Volume detected [ INFO ] Installing on first host Please provide storage domain name. [hosted_storage]: Local storage datacenter name is an internal name and currently will not be shown in engine's admin UI. Please enter local datacenter name [hosted_datacenter]: ——

Concerned about the "Local storage datacenter name is an internal name and currently will not be shown in engine's admin UI” message… I want to use a second distributed Gluster volume (name = “vmdata”) for VM storage if I can, and don’t want to mess up the install… What should I consider when setting names for the storage domain name and local datacenter names?

You can safely go with the defaults here. To set up a second storage domain (using gluster volume) - once the engine VM is up and running, you can use the user interface to create the domain (vmdata). Note: replica 3 gluster volume is recommended to use as storage domain

Thanks, Will _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users