On 05/21/2014 09:24 AM, Jiri Moskovcak wrote:
On 05/21/2014 02:49 PM, Bob Doolittle wrote:
On 05/21/2014 03:09 AM, Sven Kieske wrote:
I'd want to add that these rules are for NFSv3 asking Bob if he is maybe useing NFSv4 ?
At the moment I don't need either one. I need to solve my major issues first. Then when things are working I'll worry about setting up NFS to export new domains from my host.
Like - why didn't my default domains get configured properly?
Where is my Data Domain, and why is my ISO Domain unattached? Why didn't hosted-engine --deploy set this up properly? I took the defaults during deployment for domain setup.
When I first login to webadmin #vms, it shows HostedEngine as green/up. At #storage it shows my ISO Domain and ovirt-image-repository as unattached. No Data Domain. At #dataCenters it shows my Default datacenter as down/uninitialized If I go to #storage and select ISO_DOMAIN and select it's Data Center tab (#storage-data_center), it doesn't show any Data Centers to attach to.
-Bob
- can you login to the VM running the engine and try to mount the nfs share manually to some directory, just to see if it works? Neither engine nor setup is responsible for setting the nfs share (and configuring iptables for nfs server), so it's up to you to set it up properly and make sure it's mountable from engine.
I'm afraid NFS was a red herring. NFS shares from the host to the engine are not required for basic oVirt operation, correct? If I understand Sandro correctly, that should not be affecting my storage connections to engine. I'm sorry I brought it up - it was my misunderstanding. I believe the first thing to look at is why the ISO domain is unattached to my Default Datacenter, is that correct? Then my Datacenter should become operational, and I can add a Data Domain. I can manually mount the ISO_DOMAIN directory on both my host and my engine without issues (it resides on my engine). So why is my Datacenter not visible when I go to attach my ISO domain? -Bob