No, the Engine does not currently have communication directly to the storage network where GSA-Stor1 (aka GSA-Stor1e.engine.local) and GSA-Stor2 reside. The host it is running on does have access. Where am I supposed to go from here?
Thank you, -Robert Sent using OWA for iPhone ________________________________ From: Sahina Bose <sab...@redhat.com> Sent: Tuesday, May 2, 2017 11:44:08 AM To: Langley, Robert Cc: knarra; users Subject: Re: [ovirt-users] Trouble Adding Gluster Host in oVirt Manager On Tue, May 2, 2017 at 9:59 AM, Langley, Robert <robert.lang...@ventura.org<mailto:robert.lang...@ventura.org>> wrote: Okay, no, the Engine does not have that communication. So, this answers a question I have had. The requirements for the Engine are similar in nature as vSphere's VCenter server, where the VCenter server has to have a direct connection to the storage networks. Makes sense, they have to be managed by the Engine. I wasn't sure if the Engine somehow used the host's network connection without having its own. Then, what I need to know, is how to go about connecting the storage network to the Engine VM? I have not found this in documentation. Also, do I need to do the same thing for the Engine's storage network (192.168.3.x)? Or, is that supposed to have been done already, as part of setup? I have looked around in the Manager and attempted to add an interface for the VM storage network (192.168.2.x) for the Engine. I believe I was met with resistance. I feel as though I may have been going about it wrong. Is the gsa-stor1e.engine.local accessible to the the engine VM? If so, you should be adding the hosts to engine using this address. Once the host is added, create a Logical network in the cluster (non-VM network) and assigne this a role of "Gluster" network in the cluster. You can then assign this network to the gsa-stor1s.local using the host's "Setup Networks" option. This will ensure that gluster is aware of this network to be used while creating bricks from the UI. Thank you, Robert ________________________________ From: knarra <kna...@redhat.com<mailto:kna...@redhat.com>> Sent: Tuesday, May 2, 2017 3:44:53 AM To: Langley, Robert; users Subject: Re: [ovirt-users] Trouble Adding Gluster Host in oVirt Manager Hi, Can you please tell me which is the version of ovirt you are using ? I looked at the engine log and i see that engine failed to establish SSH session with the host . Can you check if your hosts are reachable from the engine ? 2017-04-25 16:46:23,944-07 ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-34) [0335c88e-96cc-46f4-ab22-cbf10d4645a2] Failed to establish session wi th host 'gsa-stor1s.stor.local': SSH connection timed out connecting to 'root@192.168.2.5<mailto:root@192.168.2.5>' 2017-04-25 16:46:23,944-07 WARN [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-34) [0335c88e-96cc-46f4-ab22-cbf10d4645a2] Validation of action 'AddVds' failed for user admin@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__HOST,$server 192.168.2.5,VDS_CANNOT_CONNECT_TO_SERVER 2017-04-25 16:47:53,357-07 ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-59) [3724100f-2593-41d6-b8fc-513c24cb2074] Failed to establish session wi th host 'gsa-stor1s.stor.local': SSH connection timed out connecting to 'root@192.168.2.5<mailto:root@192.168.2.5>' Thanks kasturi On 05/02/2017 01:47 AM, Langley, Robert wrote: Attempt #3 to send engine log file with the compressed file. -Robert These log files can be large for sending in email. So, I’m guessing it is best to send them as compressed. I’m learning here with the mailing list. _____________________________________________ From: Langley, Robert Sent: Monday, May 1, 2017 12:58 PM To: 'users' <users@ovirt.org><mailto:users@ovirt.org> Cc: 'Fred Rolland' <froll...@redhat.com><mailto:froll...@redhat.com> Subject: Re: Trouble Adding Gluster Host in oVirt Manager Engine.log attached from 20170427 (only including the one day, in order to decrease size) Please, bear with me, I’m not sure about the best practice for sending the log. I hope the attachment goes through okay. << File: engine.log-20170427.txt >> _______________________________________________ Users mailing list Users@ovirt.org<mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users@ovirt.org<mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
