Bug 1206701
| Summary: | [HE] configuring a new cluster in engine, and Ivy Bridge CPU type is missing | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-hosted-engine-setup | Reporter: | jas |
| Component: | UX | Assignee: | Simone Tiraboschi <stirabos> |
| Status: | CLOSED DUPLICATE | QA Contact: | meital avital <mavital> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | --- | CC: | bugs, chorn, dfediuck, jas, lsurette, mgoldboi, michal.skrivanek, rbalakri, sbonazzo, stirabos, yeylon, ykaul |
| Target Milestone: | ovirt-3.6.6 | Flags: | dfediuck:
ovirt-3.6.z?
mgoldboi: planning_ack+ ylavi: devel_ack? ylavi: testing_ack? |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-04-13 12:57:29 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
jas
2015-03-27 19:33:19 UTC
isn't it under the same family with Sandy bridge? Sandy Bridge is the same family. What exact thread are tou referring to? Hi Michael.
If, by exact thread you are referring to ovirt-users message thread... here is a message from Doron Fediuck:
Subject: [Users] CPU: Westmere vs. Ivy Bridge
From: Doron Fediuck dfediuck at redhat.com
Date: Wed Mar 19 12:11:40 EDT 2014
----- Original Message -----
> From: "Joshua Dotson" <josh at wrale.com>
> To: users at ovirt.org
> Sent: Tuesday, March 18, 2014 7:19:26 PM
> Subject: [Users] CPU: Westmere vs. Ivy Bridge
>
> Hello,
>
> The nodes on the cluster I'm installing have Ivy Bridge CPUs . The latest
> choice I see in the hosted-engine installer is Westmere. Am I missing out on
> anything significant by choosing Westmere in this case? Is there any plan to
> add Ivy Bridge as an option?
>
> Even if there is no difference behind the scenes from choosing Westmere,
> having an Ivy Bridge option would have saved me the time it took to reverse
> engineer the need to look at the source code to the need for the CPU family:
> instruction sets (performance?).
>
> Thanks,
> Joshua
Hi Joshua,
this is probably due to a missing patch.
Can you please open a bug for it?
----
Ivy bridge is based on Sandy bridge Architecture..a drop in replacement.. ovirt displays "CPU Type". However, type in my mind refers to the type of processor that I have which is Ivy Bridge.
Why does one need to specify CPU type in the creation of a cluster anyway? Do all users magically know the "type" of their CPU without looking it up??? Ovirt should fill in the type when the first node is added, but that's just my opinion.
that email refers to hosted engine setup, that is a separate thing. "Normal" UI has Sandy Bridge and Haswell it's meant to be a family name so just pick the closes compatible one from the list. You can use the lowest one which would work in all cases, but then you won't use some of the newer instructions and the VM would run slower. That's the only goal of this field, to enable as much CPU instructions as on physical hardware but keep all hosts in cluster unified so one can migrate between hosts. You may be right that with HE flow you already have the host so the installation can set it for you Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release. this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015. Please review this bug and if not a blocker, please postpone to a later release. All bugs not postponed on GA release will be automatically re-targeted to - 3.6.1 if severity >= high - 4.0 if severity < high This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset. Please set the correct milestone or add the z-stream flag. Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release. this is about HE setup, see comment #3, hence moving to integration note, in regular UI there are Conroe, Penryn, Nehalem, Westmere, Sandy Brdge, Haswell-noTSX, Haswell, Broadwell-noTSX, Broadwell. Simone, this should be already in 3.6.5, can you check and move to QA if already in? *** This bug has been marked as a duplicate of bug 1319881 *** |