I think I didn’t make it clear. Those 10 hosts are all Gen8 blades, that’s why
I want them to form a pool of their own. New Gen9 blades will go into a
different pool.
On 3/9/16, 10:14 AM, "Tim Mackey" wrote:
>In that case, Yiping, I would *definitely* recommend putting
In that case, Yiping, I would *definitely* recommend putting those servers
into at least two pools. The processors used in Gen8 and Gen9 servers can
not currently be joined into the same pool, and you actually need to be
very sensitive to the processor steppings. Dundee should fix that, but no
Hi, Tim:
Thanks for very detailed reply.
These are Gen8 HP blades and all my new servers will be Gen9. That’s why I’d
like to combine them into one maxed out cluster. I have only two guest VLAN’s
and roughly 400 VM instances for this 10 hosts cluster. So I think performance
wise I should
Yiping,
Here's the detailed answer
>From the XenServer perspective, there are a number of factors which go into
how various configuration limits are arrived at. Most of the time, they
aren't hard limits (for example I know of users with more than 16 hosts in
a pool). What the XenServer team
IIRC, its just a recommendation. I think it stemmed from performance
impact, due to numerous VLAN's present, in environments with lots of
tenants.
On Tue, Mar 8, 2016 at 2:10 PM, Yiping Zhang wrote:
> Hi, all:
>
> The CloudStack doc recommends that for XenServer, do not put