Re: [Xen-API] about XCP upgrade process

[George Shuklin <george.shuklin@xxxxxxxxx>]

Actually, the current 'blob'-way seems be more relable.

For example, if we upgrade centos in XCP 0.5 (enable repos and do yum
update) it will break some of lvmoiscsi SR functionality (sr-create fill
fail with some internal conflict). Same problem can occur in any
component and debug it will be really heavy. So 'freeze-package' systems
seems be more reliable.

I think, the model of one-by-one host upgrade (with downtime of single
host) is the best possible. pool-eject, clean upgrade, pool-join is
fine.

But it must keep somehow interoperability between versions of xapi.


В Ср., 22/12/2010 в 10:58 -0500, Todd Deshane пишет:
> On Wed, Dec 22, 2010 at 10:26 AM, George Shuklin
> <george.shuklin@xxxxxxxxx> wrote:
> > As far as I know XCP 0.5 and 1.0 (not sure about 0.11 and 0.5) can not
> > exists together in single pool.
> >
> 
> > Single way to upgrade I know involve full down for all hosts in pool -
> > configuration exported, host install from scratches with brand-new XCP
> > 1.0 and old configuration importing. But this cause some bugs with
> > duplicated templates and may be some other problems.
> >
> > Actually I really like to know way to upgrade XCP 0.5 pool to 1.0
> > without full down.
> >
> 
> Upgrading pools is supported by XenServer [1], so we should also be
> able to support it with XCP too.
> 
> XCP 1.0 is still in beta and upgrading is not yet possible, but it is planned.
> 
> yum install xcp (or similar) is also being discussed for future
> releases, stay tuned :)
> 
> Hope that helps.
> 
> Thanks,
> Todd
> 
> [1] 
> http://docs.vmd.citrix.com/XenServer/5.0.0/1.0/en_gb/installation.html#maintenance-updating_xs_40-vs_41



_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api