From Eric.Wong at solvians.com Thu Mar 19 14:04:11 2015 Content-Type: multipart/mixed; boundary="===============0291711794741535674==" MIME-Version: 1.0 From: Eric Wong To: users at ovirt.org Subject: [ovirt-users] Hosted Engine config in our hardware environment Date: Thu, 19 Mar 2015 18:04:04 +0000 Message-ID: <87E152BF0D55124F8311754D69D209F67BE51E32@MSEX-01-FRA9.corp.solvians.com> --===============0291711794741535674== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable --_000_87E152BF0D55124F8311754D69D209F67BE51E32MSEX01FRA9corps_ Content-Type: text/plain; charset=3D"iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello oVirt guru out there: I want to seek some advice on upgrade path for our oVirt management vm conf= =3D iguration. We have been using oVirt for over 3 years. When we first setup= =3D oVirt environment, Hosted Engine componment did not exist. Our question i= =3D s should we migrate our current configuration to use Hosted Engine? First let me give an overview of our configuration. We have blade servers = =3D in 2 separate racks. D1 & X1. Each side has 10 blades. Storage is iSCSI = =3D SAN. Inside our oVirt 3.5.0.1-1.el6 installation, it is configured with 2 data c= =3D enters. D1 & X1. Each datacenter has the 10 blades for that side. The ma= =3D nagement function of oVirt (oVirt web console) is running off 2 VMs, ovirt-= =3D mgmt-1 on D1, and ovirt-mgmt-2 on X1. We have keepalived to maintain a flo= =3D wing IP for the oVirt management console. The keepalived script makes sure= =3D only one copy of ovirt-engine is running at any time. It can be on D1 or = =3D X1. The mgmt VMs have Postgresql setup in replication mode. In case one o= =3D f the mgmt vm failed, the other mgmt vm on the other rack can pick up the m= =3D gmt role. Both mgmt VMs can see all blades and SAN resources on D1 & X1. This configuration has been working well for us. The drawback is if both o= =3D virt mgmt vm crashed, we will not be able to start them or make any change = =3D to the ovirt environment. It is because the mgmt VMs are running within th= =3D e oVirt domain. We tried to upgrade our configuration to Hosted Engine configuration. From= =3D what I understand, the Hosted Engine will run in a separate storage domain= =3D . In both times we tried to upgrade to Hosted Engine, they both failed dur= =3D ing export and import of current configuration. I think my questions are: - will the Hosted Engine model works in our hardware configuration. With h= =3D ardware in 2 racks, D1 & X1. Can a single Hosted Engine manage hardware on= =3D both sides? - How can we achieve redundancy when running Hosted Engine? We need to hav= =3D e management capibility in case one side completely failed. Thanks in advance. Eric --_000_87E152BF0D55124F8311754D69D209F67BE51E32MSEX01FRA9corps_ Content-Type: text/html; charset=3D"iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello oVi= rt=3D guru out there:

I want to seek some advice on upgrade path for ou= r =3D oVirt management vm configuration.  We have been using oVirt for over = =3D 3 years.  When we first setup oVirt environment, Hosted Engine componment did not exist.  Our question is should we mi= =3D grate our current configuration to use Hosted Engine?   

First l= et=3D me give an overview of our configuration.  We have blade servers in 2= =3D separate racks.  D1 & X1.  Each side has 10 blades.  St= =3D orage is iSCSI SAN. 

Inside our oVirt 3.5.0.1-1.el6 installation, it is configured wit= =3D h 2 data centers.  D1 & X1.  Each datacenter has the 10 blade= =3D s for that side.  The management function of oVirt (oVirt web console)= =3D is running off 2 VMs, ovirt-mgmt-1 on D1, and ovirt-mgmt-2 on X1.  We have keepalived to maintain a flowing IP for the oVirt man= =3D agement console.  The keepalived script makes sure only one copy of ov= =3D irt-engine is running at any time.  It can be on D1 or X1.  The m= =3D gmt VMs have Postgresql setup in replication mode.  In case one of the mgmt vm failed, the other mgmt vm on the other rack can pi= =3D ck up the mgmt role.  Both mgmt VMs can see all blades and SAN&nb= =3D sp;resources on D1 & X1.

This configuration has been working well for us.  The drawback is= =3D if both ovirt mgmt vm crashed, we will not be able to start them or make a= =3D ny change to the ovirt environment.  It is because the mgmt VMs are ru= =3D nning within the oVirt domain.

We tried to upgrade our configuration to Hosted Engine configuration. = =3D  From what I understand, the Hosted Engine will run in a separate stor= =3D age domain.  In both times we tried to upgrade to Hosted Engine, = =3D they both failed during export and import of current configuration.

I think my questions are:
- will the Hosted Engine model works in our hardware configuration. &n= =3D bsp;With hardware in 2 racks, D1 & X1.  Can a single Hosted Engine= =3D manage hardware on both sides?
- How can we achieve redundancy when running Hosted Engine? = =3D  We need to have management capibility in case one side completely fai= =3D led.

Thanks in advance.
Eric 
--_000_87E152BF0D55124F8311754D69D209F67BE51E32MSEX01FRA9corps_-- --===============0291711794741535674== Content-Type: multipart/alternative MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="attachment.bin" LS1fMDAwXzg3RTE1MkJGMEQ1NTEyNEY4MzExNzU0RDY5RDIwOUY2N0JFNTFFMzJNU0VYMDFGUkE5 Y29ycHNfCkNvbnRlbnQtVHlwZTogdGV4dC9wbGFpbjsgY2hhcnNldD0iaXNvLTg4NTktMSIKQ29u dGVudC1UcmFuc2Zlci1FbmNvZGluZzogcXVvdGVkLXByaW50YWJsZQoKSGVsbG8gb1ZpcnQgZ3Vy dSBvdXQgdGhlcmU6CgpJIHdhbnQgdG8gc2VlayBzb21lIGFkdmljZSBvbiB1cGdyYWRlIHBhdGgg Zm9yIG91ciBvVmlydCBtYW5hZ2VtZW50IHZtIGNvbmY9CmlndXJhdGlvbi4gIFdlIGhhdmUgYmVl biB1c2luZyBvVmlydCBmb3Igb3ZlciAzIHllYXJzLiAgV2hlbiB3ZSBmaXJzdCBzZXR1cD0KIG9W aXJ0IGVudmlyb25tZW50LCBIb3N0ZWQgRW5naW5lIGNvbXBvbm1lbnQgZGlkIG5vdCBleGlzdC4g IE91ciBxdWVzdGlvbiBpPQpzIHNob3VsZCB3ZSBtaWdyYXRlIG91ciBjdXJyZW50IGNvbmZpZ3Vy YXRpb24gdG8gdXNlIEhvc3RlZCBFbmdpbmU/CgpGaXJzdCBsZXQgbWUgZ2l2ZSBhbiBvdmVydmll dyBvZiBvdXIgY29uZmlndXJhdGlvbi4gIFdlIGhhdmUgYmxhZGUgc2VydmVycyA9CmluIDIgc2Vw YXJhdGUgcmFja3MuICBEMSAmIFgxLiAgRWFjaCBzaWRlIGhhcyAxMCBibGFkZXMuICBTdG9yYWdl IGlzIGlTQ1NJID0KU0FOLgoKSW5zaWRlIG91ciBvVmlydCAzLjUuMC4xLTEuZWw2IGluc3RhbGxh dGlvbiwgaXQgaXMgY29uZmlndXJlZCB3aXRoIDIgZGF0YSBjPQplbnRlcnMuICBEMSAmIFgxLiAg RWFjaCBkYXRhY2VudGVyIGhhcyB0aGUgMTAgYmxhZGVzIGZvciB0aGF0IHNpZGUuICBUaGUgbWE9 Cm5hZ2VtZW50IGZ1bmN0aW9uIG9mIG9WaXJ0IChvVmlydCB3ZWIgY29uc29sZSkgaXMgcnVubmlu ZyBvZmYgMiBWTXMsIG92aXJ0LT0KbWdtdC0xIG9uIEQxLCBhbmQgb3ZpcnQtbWdtdC0yIG9uIFgx LiAgV2UgaGF2ZSBrZWVwYWxpdmVkIHRvIG1haW50YWluIGEgZmxvPQp3aW5nIElQIGZvciB0aGUg b1ZpcnQgbWFuYWdlbWVudCBjb25zb2xlLiAgVGhlIGtlZXBhbGl2ZWQgc2NyaXB0IG1ha2VzIHN1 cmU9CiBvbmx5IG9uZSBjb3B5IG9mIG92aXJ0LWVuZ2luZSBpcyBydW5uaW5nIGF0IGFueSB0aW1l LiAgSXQgY2FuIGJlIG9uIEQxIG9yID0KWDEuICBUaGUgbWdtdCBWTXMgaGF2ZSBQb3N0Z3Jlc3Fs IHNldHVwIGluIHJlcGxpY2F0aW9uIG1vZGUuICBJbiBjYXNlIG9uZSBvPQpmIHRoZSBtZ210IHZt IGZhaWxlZCwgdGhlIG90aGVyIG1nbXQgdm0gb24gdGhlIG90aGVyIHJhY2sgY2FuIHBpY2sgdXAg dGhlIG09CmdtdCByb2xlLiAgQm90aCBtZ210IFZNcyBjYW4gc2VlIGFsbCBibGFkZXMgYW5kIFNB TiByZXNvdXJjZXMgb24gRDEgJiBYMS4KClRoaXMgY29uZmlndXJhdGlvbiBoYXMgYmVlbiB3b3Jr aW5nIHdlbGwgZm9yIHVzLiAgVGhlIGRyYXdiYWNrIGlzIGlmIGJvdGggbz0KdmlydCBtZ210IHZt IGNyYXNoZWQsIHdlIHdpbGwgbm90IGJlIGFibGUgdG8gc3RhcnQgdGhlbSBvciBtYWtlIGFueSBj aGFuZ2UgPQp0byB0aGUgb3ZpcnQgZW52aXJvbm1lbnQuICBJdCBpcyBiZWNhdXNlIHRoZSBtZ210 IFZNcyBhcmUgcnVubmluZyB3aXRoaW4gdGg9CmUgb1ZpcnQgZG9tYWluLgoKV2UgdHJpZWQgdG8g dXBncmFkZSBvdXIgY29uZmlndXJhdGlvbiB0byBIb3N0ZWQgRW5naW5lIGNvbmZpZ3VyYXRpb24u ICBGcm9tPQogd2hhdCBJIHVuZGVyc3RhbmQsIHRoZSBIb3N0ZWQgRW5naW5lIHdpbGwgcnVuIGlu IGEgc2VwYXJhdGUgc3RvcmFnZSBkb21haW49Ci4gIEluIGJvdGggdGltZXMgd2UgdHJpZWQgdG8g dXBncmFkZSB0byBIb3N0ZWQgRW5naW5lLCB0aGV5IGJvdGggZmFpbGVkIGR1cj0KaW5nIGV4cG9y dCBhbmQgaW1wb3J0IG9mIGN1cnJlbnQgY29uZmlndXJhdGlvbi4KCkkgdGhpbmsgbXkgcXVlc3Rp b25zIGFyZToKLSB3aWxsIHRoZSBIb3N0ZWQgRW5naW5lIG1vZGVsIHdvcmtzIGluIG91ciBoYXJk d2FyZSBjb25maWd1cmF0aW9uLiAgV2l0aCBoPQphcmR3YXJlIGluIDIgcmFja3MsIEQxICYgWDEu ICBDYW4gYSBzaW5nbGUgSG9zdGVkIEVuZ2luZSBtYW5hZ2UgaGFyZHdhcmUgb249CiBib3RoIHNp ZGVzPwotIEhvdyBjYW4gd2UgYWNoaWV2ZSByZWR1bmRhbmN5IHdoZW4gcnVubmluZyBIb3N0ZWQg RW5naW5lPyAgV2UgbmVlZCB0byBoYXY9CmUgbWFuYWdlbWVudCBjYXBpYmlsaXR5IGluIGNhc2Ug b25lIHNpZGUgY29tcGxldGVseSBmYWlsZWQuCgpUaGFua3MgaW4gYWR2YW5jZS4KRXJpYwoKLS1f MDAwXzg3RTE1MkJGMEQ1NTEyNEY4MzExNzU0RDY5RDIwOUY2N0JFNTFFMzJNU0VYMDFGUkE5Y29y cHNfCkNvbnRlbnQtVHlwZTogdGV4dC9odG1sOyBjaGFyc2V0PSJpc28tODg1OS0xIgpDb250ZW50 LVRyYW5zZmVyLUVuY29kaW5nOiBxdW90ZWQtcHJpbnRhYmxlCgo8aHRtbCBkaXI9M0QibHRyIj4K PGhlYWQ+CjxtZXRhIGh0dHAtZXF1aXY9M0QiQ29udGVudC1UeXBlIiBjb250ZW50PTNEInRleHQv aHRtbDsgY2hhcnNldD0zRGlzby04ODU5LT0KMSI+CjxzdHlsZSB0eXBlPTNEInRleHQvY3NzIj48 L3N0eWxlPjxzdHlsZSB0eXBlPTNEInRleHQvY3NzIiBpZD0zRCJvd2FQYXJhU3R5bD0KZSI+PC9z dHlsZT48c3R5bGUgdHlwZT0zRCJ0ZXh0L2NzcyI+PC9zdHlsZT4KPC9oZWFkPgo8Ym9keSBmcHN0 eWxlPTNEIjEiIG9jc2k9M0QiMCI+CjxkaXYgc3R5bGU9M0QiZGlyZWN0aW9uOiBsdHI7Zm9udC1m YW1pbHk6IFRhaG9tYTtjb2xvcjogIzAwMDAwMDtmb250LXNpemU6ID0KMTBwdDsiPgo8ZGl2IHN0 eWxlPTNEImZvbnQtZmFtaWx5OiBIZWx2ZXRpY2E7IGZvbnQtc2l6ZTogMTFweDsiPjxzcGFuIHN0 eWxlPTNEImZvbnQ9Ci1zaXplOiAxNXB4OyI+PHNwYW4gc3R5bGU9M0QiZm9udC1mYW1pbHk6IENh bGlicmksIHNhbnMtc2VyaWY7Ij5IZWxsbyBvVmlydD0KIGd1cnUgb3V0IHRoZXJlOjwvc3Bhbj48 L3NwYW4+PC9kaXY+CjxkaXYgc3R5bGU9M0QiZm9udC1mYW1pbHk6IEhlbHZldGljYTsgZm9udC1z aXplOiAxMXB4OyI+PHNwYW4gc3R5bGU9M0QiZm9udD0KLXNpemU6IDE1cHg7Ij48c3BhbiBzdHls ZT0zRCJmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiPjxicj4KPC9zcGFuPjwvc3Bh bj48L2Rpdj4KPGRpdiBzdHlsZT0zRCJmb250LXNpemU6IDExcHg7IGZvbnQtZmFtaWx5OiBDYWxp YnJpLCBzYW5zLXNlcmlmOyI+PHNwYW4gc3R5PQpsZT0zRCJmb250LXNpemU6IDE1cHg7Ij5JIHdh bnQgdG8gc2VlayBzb21lIGFkdmljZSBvbiB1cGdyYWRlIHBhdGggZm9yIG91ciA9Cm9WaXJ0IG1h bmFnZW1lbnQgdm0gY29uZmlndXJhdGlvbi4mbmJzcDsgV2UgaGF2ZSBiZWVuIHVzaW5nIG9WaXJ0 IGZvciBvdmVyID0KMyB5ZWFycy4mbmJzcDsgV2hlbiB3ZSBmaXJzdCBzZXR1cCBvVmlydCBlbnZp cm9ubWVudCwKIEhvc3RlZCBFbmdpbmUgY29tcG9ubWVudCBkaWQgbm90IGV4aXN0LiZuYnNwOyBP dXIgcXVlc3Rpb24gaXMgc2hvdWxkIHdlIG1pPQpncmF0ZSBvdXIgY3VycmVudCBjb25maWd1cmF0 aW9uIHRvIHVzZSBIb3N0ZWQgRW5naW5lPyZuYnNwOyZuYnNwOyZuYnNwOzwvc3A9CmFuPjwvZGl2 Pgo8ZGl2IHN0eWxlPTNEImZvbnQtZmFtaWx5OiBIZWx2ZXRpY2E7IGZvbnQtc2l6ZTogMTFweDsi Pjxicj4KPC9kaXY+CjxkaXYgc3R5bGU9M0QiZm9udC1zaXplOiAxNXB4OyBmb250LWZhbWlseTog Q2FsaWJyaSwgc2Fucy1zZXJpZjsiPkZpcnN0IGxldD0KIG1lIGdpdmUgYW4gb3ZlcnZpZXcgb2Yg b3VyIGNvbmZpZ3VyYXRpb24uJm5ic3A7IFdlIGhhdmUgYmxhZGUgc2VydmVycyBpbiAyPQogc2Vw YXJhdGUgcmFja3MuJm5ic3A7IEQxICZhbXA7IFgxLiZuYnNwOyBFYWNoIHNpZGUgaGFzIDEwIGJs YWRlcy4mbmJzcDsgU3Q9Cm9yYWdlIGlzIGlTQ1NJIFNBTi4mbmJzcDs8L2Rpdj4KPGRpdiBzdHls ZT0zRCJmb250LWZhbWlseTogSGVsdmV0aWNhOyBmb250LXNpemU6IDExcHg7Ij48YnI+CjwvZGl2 Pgo8ZGl2IHN0eWxlPTNEImZvbnQtc2l6ZTogMTVweDsgZm9udC1mYW1pbHk6IENhbGlicmksIHNh bnMtc2VyaWY7Ij4KPGRpdj5JbnNpZGUgb3VyJm5ic3A7b1ZpcnQgMy41LjAuMS0xLmVsNiBpbnN0 YWxsYXRpb24sIGl0IGlzIGNvbmZpZ3VyZWQgd2l0PQpoIDIgZGF0YSBjZW50ZXJzLiZuYnNwOyBE MSAmYW1wOyBYMS4mbmJzcDsgRWFjaCBkYXRhY2VudGVyIGhhcyB0aGUgMTAgYmxhZGU9CnMgZm9y IHRoYXQgc2lkZS4mbmJzcDsgVGhlIG1hbmFnZW1lbnQgZnVuY3Rpb24gb2Ygb1ZpcnQgKG9WaXJ0 IHdlYiBjb25zb2xlKT0KIGlzIHJ1bm5pbmcgb2ZmIDIgVk1zLCBvdmlydC1tZ210LTEgb24gRDEs IGFuZCBvdmlydC1tZ210LTIKIG9uIFgxLiZuYnNwOyBXZSBoYXZlIGtlZXBhbGl2ZWQgdG8gbWFp bnRhaW4gYSBmbG93aW5nIElQIGZvciB0aGUgb1ZpcnQgbWFuPQphZ2VtZW50IGNvbnNvbGUuJm5i c3A7IFRoZSBrZWVwYWxpdmVkIHNjcmlwdCBtYWtlcyBzdXJlIG9ubHkgb25lIGNvcHkgb2Ygb3Y9 CmlydC1lbmdpbmUgaXMgcnVubmluZyBhdCBhbnkgdGltZS4gJm5ic3A7SXQgY2FuIGJlIG9uIEQx IG9yIFgxLiAmbmJzcDtUaGUgbT0KZ210IFZNcyBoYXZlIFBvc3RncmVzcWwgc2V0dXAgaW4gcmVw bGljYXRpb24gbW9kZS4gJm5ic3A7SW4KIGNhc2Ugb25lIG9mIHRoZSBtZ210IHZtIGZhaWxlZCwg dGhlIG90aGVyIG1nbXQgdm0gb24gdGhlIG90aGVyIHJhY2sgY2FuIHBpPQpjayB1cCB0aGUgbWdt dCByb2xlLiAmbmJzcDtCb3RoIG1nbXQgVk1zJm5ic3A7Y2FuIHNlZSBhbGwgYmxhZGVzIGFuZCBT QU4mbmI9CnNwO3Jlc291cmNlcyBvbiBEMSAmYW1wOyBYMS48L2Rpdj4KPGRpdj48YnI+CjwvZGl2 Pgo8ZGl2PlRoaXMgY29uZmlndXJhdGlvbiBoYXMgYmVlbiB3b3JraW5nIHdlbGwgZm9yIHVzLiAm bmJzcDtUaGUgZHJhd2JhY2sgaXM9CiBpZiBib3RoIG92aXJ0IG1nbXQgdm0gY3Jhc2hlZCwgd2Ug d2lsbCBub3QgYmUgYWJsZSB0byBzdGFydCB0aGVtIG9yIG1ha2UgYT0KbnkgY2hhbmdlIHRvIHRo ZSBvdmlydCBlbnZpcm9ubWVudC4gJm5ic3A7SXQgaXMgYmVjYXVzZSB0aGUgbWdtdCBWTXMgYXJl IHJ1PQpubmluZyB3aXRoaW4gdGhlIG9WaXJ0IGRvbWFpbi48L2Rpdj4KPGRpdj48YnI+CjwvZGl2 Pgo8ZGl2PldlIHRyaWVkIHRvIHVwZ3JhZGUgb3VyIGNvbmZpZ3VyYXRpb24gdG8gSG9zdGVkIEVu Z2luZSBjb25maWd1cmF0aW9uLiA9CiZuYnNwO0Zyb20gd2hhdCBJIHVuZGVyc3RhbmQsIHRoZSBI b3N0ZWQgRW5naW5lIHdpbGwgcnVuIGluIGEgc2VwYXJhdGUgc3Rvcj0KYWdlIGRvbWFpbi4gJm5i c3A7SW4gYm90aCB0aW1lcyB3ZSB0cmllZCB0byB1cGdyYWRlJm5ic3A7dG8gSG9zdGVkIEVuZ2lu ZSwgPQp0aGV5IGJvdGggZmFpbGVkJm5ic3A7ZHVyaW5nIGV4cG9ydCBhbmQgaW1wb3J0IG9mIGN1 cnJlbnQKIGNvbmZpZ3VyYXRpb24uPC9kaXY+CjxkaXY+PGJyPgo8L2Rpdj4KPGRpdj5JIHRoaW5r IG15IHF1ZXN0aW9ucyBhcmU6PC9kaXY+CjxkaXY+LSB3aWxsIHRoZSBIb3N0ZWQgRW5naW5lIG1v ZGVsIHdvcmtzIGluIG91ciBoYXJkd2FyZSBjb25maWd1cmF0aW9uLiAmbj0KYnNwO1dpdGggaGFy ZHdhcmUgaW4gMiByYWNrcywgRDEgJmFtcDsgWDEuICZuYnNwO0NhbiBhIHNpbmdsZSBIb3N0ZWQg RW5naW5lPQogbWFuYWdlIGhhcmR3YXJlIG9uIGJvdGggc2lkZXM/PC9kaXY+CjxkaXY+LSZuYnNw O0hvdyBjYW4gd2UgYWNoaWV2ZSZuYnNwO3JlZHVuZGFuY3kgd2hlbiBydW5uaW5nIEhvc3RlZCBF bmdpbmU/ID0KJm5ic3A7V2UgbmVlZCB0byBoYXZlIG1hbmFnZW1lbnQgY2FwaWJpbGl0eSBpbiBj YXNlIG9uZSBzaWRlIGNvbXBsZXRlbHkgZmFpPQpsZWQuPC9kaXY+CjxkaXY+PGJyPgo8L2Rpdj4K PGRpdj5UaGFua3MgaW4gYWR2YW5jZS48L2Rpdj4KPGRpdj5FcmljJm5ic3A7PC9kaXY+CjwvZGl2 Pgo8L2Rpdj4KPC9ib2R5Pgo8L2h0bWw+CgotLV8wMDBfODdFMTUyQkYwRDU1MTI0RjgzMTE3NTRE NjlEMjA5RjY3QkU1MUUzMk1TRVgwMUZSQTljb3Jwc18tLQo= --===============0291711794741535674==-- From stirabos at redhat.com Fri Mar 20 07:02:49 2015 Content-Type: multipart/mixed; boundary="===============2876633443745408750==" MIME-Version: 1.0 From: Simone Tiraboschi To: users at ovirt.org Subject: Re: [ovirt-users] Hosted Engine config in our hardware environment Date: Fri, 20 Mar 2015 07:02:47 -0400 Message-ID: <181156407.262296.1426849367081.JavaMail.zimbra@redhat.com> In-Reply-To: 87E152BF0D55124F8311754D69D209F67BE51E32@MSEX-01-FRA9.corp.solvians.com --===============2876633443745408750== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable ----- Original Message ----- > From: "Eric Wong" > To: users(a)ovirt.org > Sent: Thursday, March 19, 2015 7:04:04 PM > Subject: [ovirt-users] Hosted Engine config in our hardware environment > = > Hello oVirt guru out there: > = > I want to seek some advice on upgrade path for our oVirt management vm > configuration. We have been using oVirt for over 3 years. When we first > setup oVirt environment, Hosted Engine componment did not exist. Our > question is should we migrate our current configuration to use Hosted > Engine? > = > First let me give an overview of our configuration. We have blade servers= in > 2 separate racks. D1 & X1. Each side has 10 blades. Storage is iSCSI SAN. > = > Inside our oVirt 3.5.0.1-1.el6 installation, it is configured with 2 data > centers. D1 & X1. Each datacenter has the 10 blades for that side. The > management function of oVirt (oVirt web console) is running off 2 VMs, > ovirt-mgmt-1 on D1, and ovirt-mgmt-2 on X1. We have keepalived to maintai= n a > flowing IP for the oVirt management console. The keepalived script makes > sure only one copy of ovirt-engine is running at any time. It can be on D1 > or X1. The mgmt VMs have Postgresql setup in replication mode. In case one > of the mgmt vm failed, the other mgmt vm on the other rack can pick up the > mgmt role. Both mgmt VMs can see all blades and SAN resources on D1 & X1. > = > This configuration has been working well for us. The drawback is if both > ovirt mgmt vm crashed, we will not be able to start them or make any chan= ge > to the ovirt environment. It is because the mgmt VMs are running within t= he > oVirt domain. > = > We tried to upgrade our configuration to Hosted Engine configuration. From > what I understand, the Hosted Engine will run in a separate storage domai= n. > In both times we tried to upgrade to Hosted Engine, they both failed duri= ng > export and import of current configuration. > = > I think my questions are: > - will the Hosted Engine model works in our hardware configuration. With > hardware in 2 racks, D1 & X1. Can a single Hosted Engine manage hardware = on > both sides? Yes it can. > - How can we achieve redundancy when running Hosted Engine? We need to ha= ve > management capibility in case one side completely failed. With hosted engine you are going to have a single VM managing three data-ce= nter: D1, X1 and an hosted-engine specific one. The hosted-engine datacenter will use an additional shared storage domain (= with 3.5 iSCSI is fine) dedicated to hosted engine. On each host you are de= ploying hosted-engine on (2 o 3 hosts), an agent for HA will be installed: = it's up to that agent to monitor the status on the engine VM and restart it= (with the needed locking mechanism to have just one copy of it running) if= the host were it was previously running has crashed. So ovirt-hosted-engine-ha will ensure HA for the engine VM without the need= to have to copy of that with a replicated DB. > Thanks in advance. > Eric > = > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users >=20 --===============2876633443745408750==-- From stirabos at redhat.com Fri Mar 20 07:06:23 2015 Content-Type: multipart/mixed; boundary="===============8365754185159443236==" MIME-Version: 1.0 From: Simone Tiraboschi To: users at ovirt.org Subject: Re: [ovirt-users] Hosted Engine config in our hardware environment Date: Fri, 20 Mar 2015 07:06:22 -0400 Message-ID: <1432878009.263652.1426849582381.JavaMail.zimbra@redhat.com> In-Reply-To: 87E152BF0D55124F8311754D69D209F67BE51E32@MSEX-01-FRA9.corp.solvians.com --===============8365754185159443236== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable ----- Original Message ----- > From: "Eric Wong" > To: users(a)ovirt.org > Sent: Thursday, March 19, 2015 7:04:04 PM > Subject: [ovirt-users] Hosted Engine config in our hardware environment > = > Hello oVirt guru out there: > = > I want to seek some advice on upgrade path for our oVirt management vm > configuration. We have been using oVirt for over 3 years. When we first > setup oVirt environment, Hosted Engine componment did not exist. Our > question is should we migrate our current configuration to use Hosted > Engine? > = > First let me give an overview of our configuration. We have blade servers= in > 2 separate racks. D1 & X1. Each side has 10 blades. Storage is iSCSI SAN. > = > Inside our oVirt 3.5.0.1-1.el6 installation, it is configured with 2 data > centers. D1 & X1. Each datacenter has the 10 blades for that side. The > management function of oVirt (oVirt web console) is running off 2 VMs, > ovirt-mgmt-1 on D1, and ovirt-mgmt-2 on X1. We have keepalived to maintai= n a > flowing IP for the oVirt management console. The keepalived script makes > sure only one copy of ovirt-engine is running at any time. It can be on D1 > or X1. The mgmt VMs have Postgresql setup in replication mode. In case one > of the mgmt vm failed, the other mgmt vm on the other rack can pick up the > mgmt role. Both mgmt VMs can see all blades and SAN resources on D1 & X1. > = > This configuration has been working well for us. The drawback is if both > ovirt mgmt vm crashed, we will not be able to start them or make any chan= ge > to the ovirt environment. It is because the mgmt VMs are running within t= he > oVirt domain. > = > We tried to upgrade our configuration to Hosted Engine configuration. From > what I understand, the Hosted Engine will run in a separate storage domai= n. > In both times we tried to upgrade to Hosted Engine, they both failed duri= ng > export and import of current configuration. Here you can find some hint about how to migrate to hosted-engine: http://www.ovirt.org/Migrate_to_Hosted_Engine > I think my questions are: > - will the Hosted Engine model works in our hardware configuration. With > hardware in 2 racks, D1 & X1. Can a single Hosted Engine manage hardware = on > both sides? > - How can we achieve redundancy when running Hosted Engine? We need to ha= ve > management capibility in case one side completely failed. > = > Thanks in advance. > Eric > = > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users >=20 --===============8365754185159443236==-- From Eric.Wong at solvians.com Tue Mar 24 04:36:25 2015 Content-Type: multipart/mixed; boundary="===============5938057584607307360==" MIME-Version: 1.0 From: Eric Wong To: users at ovirt.org Subject: Re: [ovirt-users] Hosted Engine config in our hardware environment Date: Tue, 24 Mar 2015 08:36:11 +0000 Message-ID: <87E152BF0D55124F8311754D69D209F67BE69161@MSEX-01-FRA9.corp.solvians.com> In-Reply-To: 1432878009.263652.1426849582381.JavaMail.zimbra@redhat.com --===============5938057584607307360== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Simone: Thanks for your quick respond. It clarified some of the confusion I have w= ith the hosted-engine. However, I still have one question. Sorry. It is my bad that I did not ex= plain clearer on our hardware configuration, mainly on the SAN. We also ha= ve 2 SAN, one on D1 & another one on X1. The blades on D1 can only see the= storage in SAN D1. X1 blades can only see SAN X1. Does it mean that we will need to manage our oVirt environment separately w= hen we switch to use hosted-engine? Because from your explanation, the hos= ted-engine in selected nodes will use separate iSCSI hosted-engine storage = to store the DB. Since there is no cross D1 & X1 storage in our current co= nfig, that means we need separate hosted-engine setup on each side. Thanks, Eric -----Original Message----- From: Simone Tiraboschi [mailto:stirabos(a)redhat.com] = Sent: Friday, March 20, 2015 7:06 PM To: Eric Wong Cc: users(a)ovirt.org Subject: Re: [ovirt-users] Hosted Engine config in our hardware environment ----- Original Message ----- > From: "Eric Wong" > To: users(a)ovirt.org > Sent: Thursday, March 19, 2015 7:04:04 PM > Subject: [ovirt-users] Hosted Engine config in our hardware environment > = > Hello oVirt guru out there: > = > I want to seek some advice on upgrade path for our oVirt management vm > configuration. We have been using oVirt for over 3 years. When we first > setup oVirt environment, Hosted Engine componment did not exist. Our > question is should we migrate our current configuration to use Hosted > Engine? > = > First let me give an overview of our configuration. We have blade servers= in > 2 separate racks. D1 & X1. Each side has 10 blades. Storage is iSCSI SAN. > = > Inside our oVirt 3.5.0.1-1.el6 installation, it is configured with 2 data > centers. D1 & X1. Each datacenter has the 10 blades for that side. The > management function of oVirt (oVirt web console) is running off 2 VMs, > ovirt-mgmt-1 on D1, and ovirt-mgmt-2 on X1. We have keepalived to maintai= n a > flowing IP for the oVirt management console. The keepalived script makes > sure only one copy of ovirt-engine is running at any time. It can be on D1 > or X1. The mgmt VMs have Postgresql setup in replication mode. In case one > of the mgmt vm failed, the other mgmt vm on the other rack can pick up the > mgmt role. Both mgmt VMs can see all blades and SAN resources on D1 & X1. > = > This configuration has been working well for us. The drawback is if both > ovirt mgmt vm crashed, we will not be able to start them or make any chan= ge > to the ovirt environment. It is because the mgmt VMs are running within t= he > oVirt domain. > = > We tried to upgrade our configuration to Hosted Engine configuration. From > what I understand, the Hosted Engine will run in a separate storage domai= n. > In both times we tried to upgrade to Hosted Engine, they both failed duri= ng > export and import of current configuration. Here you can find some hint about how to migrate to hosted-engine: http://www.ovirt.org/Migrate_to_Hosted_Engine > I think my questions are: > - will the Hosted Engine model works in our hardware configuration. With > hardware in 2 racks, D1 & X1. Can a single Hosted Engine manage hardware = on > both sides? > - How can we achieve redundancy when running Hosted Engine? We need to ha= ve > management capibility in case one side completely failed. > = > Thanks in advance. > Eric > = > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users >=20 --===============5938057584607307360==-- From stirabos at redhat.com Tue Mar 24 05:10:57 2015 Content-Type: multipart/mixed; boundary="===============7557795240185104995==" MIME-Version: 1.0 From: Simone Tiraboschi To: users at ovirt.org Subject: Re: [ovirt-users] Hosted Engine config in our hardware environment Date: Tue, 24 Mar 2015 05:10:53 -0400 Message-ID: <1441096793.1840641.1427188253466.JavaMail.zimbra@redhat.com> In-Reply-To: 87E152BF0D55124F8311754D69D209F67BE69161@MSEX-01-FRA9.corp.solvians.com --===============7557795240185104995== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable ----- Original Message ----- > From: "Eric Wong" > To: "Simone Tiraboschi" > Cc: users(a)ovirt.org > Sent: Tuesday, March 24, 2015 9:36:11 AM > Subject: RE: [ovirt-users] Hosted Engine config in our hardware environme= nt > = > Simone: > = > Thanks for your quick respond. It clarified some of the confusion I have > with the hosted-engine. > = > However, I still have one question. Sorry. It is my bad that I did not > explain clearer on our hardware configuration, mainly on the SAN. We also > have 2 SAN, one on D1 & another one on X1. The blades on D1 can only see > the storage in SAN D1. X1 blades can only see SAN X1. > = > Does it mean that we will need to manage our oVirt environment separately > when we switch to use hosted-engine? Because from your explanation, the > hosted-engine in selected nodes will use separate iSCSI hosted-engine > storage to store the DB. = With hosted engine not only the DB but all the engine VM is going to be sto= red on a dedicated iSCSI LUN so each host involved (not managed by) in host= ed-engine should be able to access that device in order to be able to start= the engine VM after other host failures. So, if you want to have it restarting the engine VM on a X1 host after a co= mplete failure of D1 rack, you need to store the engine VM on a location th= at is accessible both by D1 and X1. NFS could be an option too. Otherwise you should check your storage path design in order to have a cros= s rack path; you could also evaluate iSCSI multipathing. > Since there is no cross D1 & X1 storage in our > current config, that means we need separate hosted-engine setup on each > side. > = > Thanks, > Eric > = > = > -----Original Message----- > From: Simone Tiraboschi [mailto:stirabos(a)redhat.com] > Sent: Friday, March 20, 2015 7:06 PM > To: Eric Wong > Cc: users(a)ovirt.org > Subject: Re: [ovirt-users] Hosted Engine config in our hardware environme= nt > = > = > = > ----- Original Message ----- > > From: "Eric Wong" > > To: users(a)ovirt.org > > Sent: Thursday, March 19, 2015 7:04:04 PM > > Subject: [ovirt-users] Hosted Engine config in our hardware environment > > = > > Hello oVirt guru out there: > > = > > I want to seek some advice on upgrade path for our oVirt management vm > > configuration. We have been using oVirt for over 3 years. When we first > > setup oVirt environment, Hosted Engine componment did not exist. Our > > question is should we migrate our current configuration to use Hosted > > Engine? > > = > > First let me give an overview of our configuration. We have blade serve= rs > > in > > 2 separate racks. D1 & X1. Each side has 10 blades. Storage is iSCSI SA= N. > > = > > Inside our oVirt 3.5.0.1-1.el6 installation, it is configured with 2 da= ta > > centers. D1 & X1. Each datacenter has the 10 blades for that side. The > > management function of oVirt (oVirt web console) is running off 2 VMs, > > ovirt-mgmt-1 on D1, and ovirt-mgmt-2 on X1. We have keepalived to maint= ain > > a > > flowing IP for the oVirt management console. The keepalived script makes > > sure only one copy of ovirt-engine is running at any time. It can be on= D1 > > or X1. The mgmt VMs have Postgresql setup in replication mode. In case = one > > of the mgmt vm failed, the other mgmt vm on the other rack can pick up = the > > mgmt role. Both mgmt VMs can see all blades and SAN resources on D1 & X= 1. > > = > > This configuration has been working well for us. The drawback is if both > > ovirt mgmt vm crashed, we will not be able to start them or make any ch= ange > > to the ovirt environment. It is because the mgmt VMs are running within= the > > oVirt domain. > > = > > We tried to upgrade our configuration to Hosted Engine configuration. F= rom > > what I understand, the Hosted Engine will run in a separate storage dom= ain. > > In both times we tried to upgrade to Hosted Engine, they both failed du= ring > > export and import of current configuration. > = > Here you can find some hint about how to migrate to hosted-engine: > http://www.ovirt.org/Migrate_to_Hosted_Engine > = > > I think my questions are: > > - will the Hosted Engine model works in our hardware configuration. With > > hardware in 2 racks, D1 & X1. Can a single Hosted Engine manage hardwar= e on > > both sides? > > - How can we achieve redundancy when running Hosted Engine? We need to = have > > management capibility in case one side completely failed. > > = > > Thanks in advance. > > Eric > > = > > _______________________________________________ > > Users mailing list > > Users(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > > = >=20 --===============7557795240185104995==-- From Eric.Wong at solvians.com Wed Mar 25 07:12:56 2015 Content-Type: multipart/mixed; boundary="===============3281635400765483695==" MIME-Version: 1.0 From: Eric Wong To: users at ovirt.org Subject: Re: [ovirt-users] Hosted Engine config in our hardware environment Date: Wed, 25 Mar 2015 11:12:47 +0000 Message-ID: <87E152BF0D55124F8311754D69D209F67BE6AB76@MSEX-01-FRA9.corp.solvians.com> In-Reply-To: 1441096793.1840641.1427188253466.JavaMail.zimbra@redhat.com --===============3281635400765483695== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Simone: I discussed with our SAN guy. We currently is not able to configure the SA= N in D1 & X1 to be seen by blades in both sides. So we are pretty much stu= ck with our current ovirt mgmt. vms configuration. I guess the main concern is how to control all the virtual machines with oV= irt infrastructure if both our ovirt-mgmt vms went down, how can we start t= hem up again. That also applies to any virtual machines. If the oVirt mgm= t infrastructure is not able, I think there is no way to start a VM, correc= t? Again, Many Thanks, Eric -----Original Message----- From: Simone Tiraboschi [mailto:stirabos(a)redhat.com] = Sent: Tuesday, March 24, 2015 5:11 PM To: Eric Wong Cc: users(a)ovirt.org Subject: Re: [ovirt-users] Hosted Engine config in our hardware environment ----- Original Message ----- > From: "Eric Wong" > To: "Simone Tiraboschi" > Cc: users(a)ovirt.org > Sent: Tuesday, March 24, 2015 9:36:11 AM > Subject: RE: [ovirt-users] Hosted Engine config in our hardware environme= nt > = > Simone: > = > Thanks for your quick respond. It clarified some of the confusion I have > with the hosted-engine. > = > However, I still have one question. Sorry. It is my bad that I did not > explain clearer on our hardware configuration, mainly on the SAN. We also > have 2 SAN, one on D1 & another one on X1. The blades on D1 can only see > the storage in SAN D1. X1 blades can only see SAN X1. > = > Does it mean that we will need to manage our oVirt environment separately > when we switch to use hosted-engine? Because from your explanation, the > hosted-engine in selected nodes will use separate iSCSI hosted-engine > storage to store the DB. = With hosted engine not only the DB but all the engine VM is going to be sto= red on a dedicated iSCSI LUN so each host involved (not managed by) in host= ed-engine should be able to access that device in order to be able to start= the engine VM after other host failures. So, if you want to have it restarting the engine VM on a X1 host after a co= mplete failure of D1 rack, you need to store the engine VM on a location th= at is accessible both by D1 and X1. NFS could be an option too. Otherwise you should check your storage path design in order to have a cros= s rack path; you could also evaluate iSCSI multipathing. > Since there is no cross D1 & X1 storage in our > current config, that means we need separate hosted-engine setup on each > side. > = > Thanks, > Eric > = > = > -----Original Message----- > From: Simone Tiraboschi [mailto:stirabos(a)redhat.com] > Sent: Friday, March 20, 2015 7:06 PM > To: Eric Wong > Cc: users(a)ovirt.org > Subject: Re: [ovirt-users] Hosted Engine config in our hardware environme= nt > = > = > = > ----- Original Message ----- > > From: "Eric Wong" > > To: users(a)ovirt.org > > Sent: Thursday, March 19, 2015 7:04:04 PM > > Subject: [ovirt-users] Hosted Engine config in our hardware environment > > = > > Hello oVirt guru out there: > > = > > I want to seek some advice on upgrade path for our oVirt management vm > > configuration. We have been using oVirt for over 3 years. When we first > > setup oVirt environment, Hosted Engine componment did not exist. Our > > question is should we migrate our current configuration to use Hosted > > Engine? > > = > > First let me give an overview of our configuration. We have blade serve= rs > > in > > 2 separate racks. D1 & X1. Each side has 10 blades. Storage is iSCSI SA= N. > > = > > Inside our oVirt 3.5.0.1-1.el6 installation, it is configured with 2 da= ta > > centers. D1 & X1. Each datacenter has the 10 blades for that side. The > > management function of oVirt (oVirt web console) is running off 2 VMs, > > ovirt-mgmt-1 on D1, and ovirt-mgmt-2 on X1. We have keepalived to maint= ain > > a > > flowing IP for the oVirt management console. The keepalived script makes > > sure only one copy of ovirt-engine is running at any time. It can be on= D1 > > or X1. The mgmt VMs have Postgresql setup in replication mode. In case = one > > of the mgmt vm failed, the other mgmt vm on the other rack can pick up = the > > mgmt role. Both mgmt VMs can see all blades and SAN resources on D1 & X= 1. > > = > > This configuration has been working well for us. The drawback is if both > > ovirt mgmt vm crashed, we will not be able to start them or make any ch= ange > > to the ovirt environment. It is because the mgmt VMs are running within= the > > oVirt domain. > > = > > We tried to upgrade our configuration to Hosted Engine configuration. F= rom > > what I understand, the Hosted Engine will run in a separate storage dom= ain. > > In both times we tried to upgrade to Hosted Engine, they both failed du= ring > > export and import of current configuration. > = > Here you can find some hint about how to migrate to hosted-engine: > http://www.ovirt.org/Migrate_to_Hosted_Engine > = > > I think my questions are: > > - will the Hosted Engine model works in our hardware configuration. With > > hardware in 2 racks, D1 & X1. Can a single Hosted Engine manage hardwar= e on > > both sides? > > - How can we achieve redundancy when running Hosted Engine? We need to = have > > management capibility in case one side completely failed. > > = > > Thanks in advance. > > Eric > > = > > _______________________________________________ > > Users mailing list > > Users(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > > = >=20 --===============3281635400765483695==-- From didi at redhat.com Wed Mar 25 07:22:00 2015 Content-Type: multipart/mixed; boundary="===============1806149495133442022==" MIME-Version: 1.0 From: Yedidyah Bar David To: users at ovirt.org Subject: Re: [ovirt-users] Hosted Engine config in our hardware environment Date: Wed, 25 Mar 2015 07:21:59 -0400 Message-ID: <980353246.5641019.1427282519618.JavaMail.zimbra@redhat.com> In-Reply-To: 87E152BF0D55124F8311754D69D209F67BE6AB76@MSEX-01-FRA9.corp.solvians.com --===============1806149495133442022== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable ----- Original Message ----- > From: "Eric Wong" > To: "Simone Tiraboschi" > Cc: users(a)ovirt.org > Sent: Wednesday, March 25, 2015 1:12:47 PM > Subject: Re: [ovirt-users] Hosted Engine config in our hardware environme= nt > = > Simone: > = > I discussed with our SAN guy. We currently is not able to configure the = SAN > in D1 & X1 to be seen by blades in both sides. So we are pretty much stu= ck > with our current ovirt mgmt. vms configuration. > = > I guess the main concern is how to control all the virtual machines with > oVirt infrastructure if both our ovirt-mgmt vms went down, how can we sta= rt > them up again. That also applies to any virtual machines. If the oVirt > mgmt infrastructure is not able, I think there is no way to start a VM, > correct? Not really - ovirt-hosted-engine-ha does that :-) In principle you can check how it does that and do so too. IIRC we have an RFE to make it support more VMs (in addition to the engine's one). IIUC this will not help you directly, because HA still relies on shared storage. Best, -- = Didi --===============1806149495133442022==-- From stirabos at redhat.com Wed Mar 25 07:35:29 2015 Content-Type: multipart/mixed; boundary="===============6728539373742227791==" MIME-Version: 1.0 From: Simone Tiraboschi To: users at ovirt.org Subject: Re: [ovirt-users] Hosted Engine config in our hardware environment Date: Wed, 25 Mar 2015 07:35:28 -0400 Message-ID: <1388349179.2580127.1427283328978.JavaMail.zimbra@redhat.com> In-Reply-To: 87E152BF0D55124F8311754D69D209F67BE6AB76@MSEX-01-FRA9.corp.solvians.com --===============6728539373742227791== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable ----- Original Message ----- > From: "Eric Wong" > To: "Simone Tiraboschi" > Cc: users(a)ovirt.org > Sent: Wednesday, March 25, 2015 12:12:47 PM > Subject: RE: [ovirt-users] Hosted Engine config in our hardware environme= nt > = > Simone: > = > I discussed with our SAN guy. We currently is not able to configure the = SAN > in D1 & X1 to be seen by blades in both sides. So we are pretty much stu= ck > with our current ovirt mgmt. vms configuration. That is not an hosted engine issue, it's a design issue. If you want to provide HA or disaster recovery capabilities between your tw= o racks both of them should be able to access your shared storage otherwise= you simply cannot directly migrate a VM from D1 to X1 or viceversa. If you have two racks with two different and insulated SAN and they cannot = access each other you have two distinct insulated systems and you could onl= y manage them as that; you could use a single oVirt engine for that but the= engine VM itself could not migrate to the other system by design. > I guess the main concern is how to control all the virtual machines with > oVirt infrastructure if both our ovirt-mgmt vms went down, how can we sta= rt > them up again. That also applies to any virtual machines. If the oVirt > mgmt infrastructure is not able, I think there is no way to start a VM, > correct? At low level you could directly use virsh directly on the host to start a V= M directly over libvirtd but it's really a extreme solution. = > Again, Many Thanks, > Eric > = > = > -----Original Message----- > From: Simone Tiraboschi [mailto:stirabos(a)redhat.com] > Sent: Tuesday, March 24, 2015 5:11 PM > To: Eric Wong > Cc: users(a)ovirt.org > Subject: Re: [ovirt-users] Hosted Engine config in our hardware environme= nt > = > = > = > ----- Original Message ----- > > From: "Eric Wong" > > To: "Simone Tiraboschi" > > Cc: users(a)ovirt.org > > Sent: Tuesday, March 24, 2015 9:36:11 AM > > Subject: RE: [ovirt-users] Hosted Engine config in our hardware environ= ment > > = > > Simone: > > = > > Thanks for your quick respond. It clarified some of the confusion I ha= ve > > with the hosted-engine. > > = > > However, I still have one question. Sorry. It is my bad that I did not > > explain clearer on our hardware configuration, mainly on the SAN. We a= lso > > have 2 SAN, one on D1 & another one on X1. The blades on D1 can only s= ee > > the storage in SAN D1. X1 blades can only see SAN X1. > > = > > Does it mean that we will need to manage our oVirt environment separate= ly > > when we switch to use hosted-engine? Because from your explanation, the > > hosted-engine in selected nodes will use separate iSCSI hosted-engine > > storage to store the DB. > = > With hosted engine not only the DB but all the engine VM is going to be > stored on a dedicated iSCSI LUN so each host involved (not managed by) in > hosted-engine should be able to access that device in order to be able to > start the engine VM after other host failures. > = > So, if you want to have it restarting the engine VM on a X1 host after a > complete failure of D1 rack, you need to store the engine VM on a location > that is accessible both by D1 and X1. > NFS could be an option too. > Otherwise you should check your storage path design in order to have a cr= oss > rack path; you could also evaluate iSCSI multipathing. > = > = > > Since there is no cross D1 & X1 storage in our > > current config, that means we need separate hosted-engine setup on each > > side. > > = > > Thanks, > > Eric > > = > > = > > -----Original Message----- > > From: Simone Tiraboschi [mailto:stirabos(a)redhat.com] > > Sent: Friday, March 20, 2015 7:06 PM > > To: Eric Wong > > Cc: users(a)ovirt.org > > Subject: Re: [ovirt-users] Hosted Engine config in our hardware environ= ment > > = > > = > > = > > ----- Original Message ----- > > > From: "Eric Wong" > > > To: users(a)ovirt.org > > > Sent: Thursday, March 19, 2015 7:04:04 PM > > > Subject: [ovirt-users] Hosted Engine config in our hardware environme= nt > > > = > > > Hello oVirt guru out there: > > > = > > > I want to seek some advice on upgrade path for our oVirt management vm > > > configuration. We have been using oVirt for over 3 years. When we fir= st > > > setup oVirt environment, Hosted Engine componment did not exist. Our > > > question is should we migrate our current configuration to use Hosted > > > Engine? > > > = > > > First let me give an overview of our configuration. We have blade ser= vers > > > in > > > 2 separate racks. D1 & X1. Each side has 10 blades. Storage is iSCSI = SAN. > > > = > > > Inside our oVirt 3.5.0.1-1.el6 installation, it is configured with 2 = data > > > centers. D1 & X1. Each datacenter has the 10 blades for that side. The > > > management function of oVirt (oVirt web console) is running off 2 VMs, > > > ovirt-mgmt-1 on D1, and ovirt-mgmt-2 on X1. We have keepalived to > > > maintain > > > a > > > flowing IP for the oVirt management console. The keepalived script ma= kes > > > sure only one copy of ovirt-engine is running at any time. It can be = on > > > D1 > > > or X1. The mgmt VMs have Postgresql setup in replication mode. In case > > > one > > > of the mgmt vm failed, the other mgmt vm on the other rack can pick up > > > the > > > mgmt role. Both mgmt VMs can see all blades and SAN resources on D1 &= X1. > > > = > > > This configuration has been working well for us. The drawback is if b= oth > > > ovirt mgmt vm crashed, we will not be able to start them or make any > > > change > > > to the ovirt environment. It is because the mgmt VMs are running with= in > > > the > > > oVirt domain. > > > = > > > We tried to upgrade our configuration to Hosted Engine configuration. > > > From > > > what I understand, the Hosted Engine will run in a separate storage > > > domain. > > > In both times we tried to upgrade to Hosted Engine, they both failed > > > during > > > export and import of current configuration. > > = > > Here you can find some hint about how to migrate to hosted-engine: > > http://www.ovirt.org/Migrate_to_Hosted_Engine > > = > > > I think my questions are: > > > - will the Hosted Engine model works in our hardware configuration. W= ith > > > hardware in 2 racks, D1 & X1. Can a single Hosted Engine manage hardw= are > > > on > > > both sides? > > > - How can we achieve redundancy when running Hosted Engine? We need to > > > have > > > management capibility in case one side completely failed. > > > = > > > Thanks in advance. > > > Eric > > > = > > > _______________________________________________ > > > Users mailing list > > > Users(a)ovirt.org > > > http://lists.ovirt.org/mailman/listinfo/users > > > = > > = >=20 --===============6728539373742227791==--