hosted-engine with iscsi storage domain
We have a hosted-engine running on 4.1 with an iSCSI hosted_storage domain, and are able to import the domain. However, we cannot attache the domain to the data center. Just to make sure I'm not missing something basic, does the engine VM need to be able to connect to the iSCSI target itself? In other words, does the iSCSI traffic need to go over the ovirtmgmt bridged network? Currently we have the iSCSI SAN on a separate subnet from ovirtmgmt, so the hosted-engine VM can't directly see the iSCSI storage. Thanks, Devin
On Mon, Mar 20, 2017 at 4:30 PM, Devin A. Bougie <devin.bougie@cornell.edu> wrote:
We have a hosted-engine running on 4.1 with an iSCSI hosted_storage domain, and are able to import the domain. However, we cannot attache the domain to the data center.
The engine should import it by itself once you add your first storage domain for regular VMs. No manual import actions are required.
Just to make sure I'm not missing something basic, does the engine VM need to be able to connect to the iSCSI target itself? In other words, does the iSCSI traffic need to go over the ovirtmgmt bridged network? Currently we have the iSCSI SAN on a separate subnet from ovirtmgmt, so the hosted-engine VM can't directly see the iSCSI storage.
No, a separate network for the storage is even recommended.
Thanks, Devin _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Mar 20, 2017, at 12:54 PM, Simone Tiraboschi <stirabos@redhat.com> wrote:
The engine should import it by itself once you add your first storage domain for regular VMs. No manual import actions are required.
It didn't seem to for us. I don't see it in the Storage tab (maybe I shouldn't?). I can install a new host from the engine web ui, but I don't see any hosted-engine options. If I put the new host in maintenance and reinstall, I can select DEPLOY under "Choose hosted engine deployment action." However, the web UI than complains that: Cannot edit Host. You are using an unmanaged hosted engine VM. P{ease upgrade the cluster level to 3.6 and wait for the hosted engine storage domain to be properly imported. This is on a new 4.1 cluster with the hosted-engine created using hosted-engine --deploy on the first host.
No, a separate network for the storage is even recommended.
Glad to hear, thanks! Devin
On Tue, Mar 21, 2017 at 3:06 PM, Devin A. Bougie <devin.bougie@cornell.edu> wrote:
On Mar 20, 2017, at 12:54 PM, Simone Tiraboschi <stirabos@redhat.com> wrote:
The engine should import it by itself once you add your first storage domain for regular VMs. No manual import actions are required.
It didn't seem to for us. I don't see it in the Storage tab (maybe I shouldn't?). I can install a new host from the engine web ui, but I don't see any hosted-engine options. If I put the new host in maintenance and reinstall, I can select DEPLOY under "Choose hosted engine deployment action." However, the web UI than complains that: Cannot edit Host. You are using an unmanaged hosted engine VM. P{ease upgrade the cluster level to 3.6 and wait for the hosted engine storage domain to be properly imported.
Did you already add your first storage domain for regular VMs? If also that one is on iSCSI, it should be connected trough a different iSCSI portal. This is on a new 4.1 cluster with the hosted-engine created using
hosted-engine --deploy on the first host.
No, a separate network for the storage is even recommended.
Glad to hear, thanks!
Devin
Hi Simone, On Mar 21, 2017, at 4:06 PM, Simone Tiraboschi <stirabos@redhat.com> wrote:
Did you already add your first storage domain for regular VMs? If also that one is on iSCSI, it should be connected trough a different iSCSI portal.
Sure enough, once we added the data storage the hosted-storage imported and attached successfully. Both our hosted-storage and our VM data storage are from the same iSCSI target(s), but separate LUNs. Many thanks! Devin
participants (2)
-
Devin A. Bougie -
Simone Tiraboschi