I have a couple of questions regarding XCP:
First, there were rumblings that there are issues upgrading XCP (1.5 ->
1.6)? Any further detail on these potential issues, or what needs to be
done to get around them?
Second, it previous versions of XCP there were tricks that had to be
played (documented on the Wiki) to make XenCenter believe that XCP was
actually a modern version of XenServer, since it would show up as
XenServer 1.1 or 1.4.90. I noticed after installing a fresh copy of 1.6
that the "XenServer Version" field on the General tab is gone - it
simply lists the build number and the build date. Does this mean there
is no longer any reason to trick XenCenter - that XenCenter is now
keying exclusively on the build number and not on the version? Or am I
still going to have to sed the xapi binary to get XenCenter to see all
of the features?
Finally, tying the previous two questions together, I currently have a
pool running XCP 1.5, with the xapi modification to make it look like
XenServer 6.0, and I''m wanting to upgrade that pool to 1.6. I
understand that I need to do the pool master, first, but I''m wondering
if there are going to be any problems once I upgrade the pool master if
it is suddenly seen as version 1.6.05 and the rest of the systems look
like 6.0.99, or, again, if the build number is what will be exclusively
used and there won''t be any issues?
Thanks - Nick
--------
This e-mail may contain confidential and privileged material for the sole use of
the intended recipient. If this email is not intended for you, or you are not
responsible for the delivery of this message to the intended recipient, please
note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information. In such a case, you are strictly prohibited
from downloading, photocopying, distributing or otherwise using this message,
its contents or attachments in any way. If you have received this message in
error, please notify us immediately by replying to this e-mail and delete the
message from your mailbox. Information contained in this message that does not
relate to the business of SEAKR is neither endorsed by nor attributable to
SEAKR.
