WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-api

Re: [Xen-API] about XCP upgrade process

To: Todd Deshane <todd.deshane@xxxxxxx>
Subject: Re: [Xen-API] about XCP upgrade process
From: George Shuklin <george.shuklin@xxxxxxxxx>
Date: Wed, 22 Dec 2010 19:15:41 +0300
Cc: xen-api@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 22 Dec 2010 08:17:13 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=dU67BTdSWUZ2NXdUpICB+5CchbLztF/Ud7j+RrRoCh4=; b=dZKe+meLmWNrfZOT+nznYU3bhg2m7rhyIneFIL4pUIzg7lHmDP5Ac6Jgtgmpib4VFx PvGSSGST7oEO5zW8ZLhRpsSTYBBXtjlMhpCl7G28tZCGxjlsCvouBFuD0JIF0TgY3O4q 0Qi4JbD2NekkBkr2d20j9dy6uJknMq440x7Ao=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=VY8O5dSosQt5ZD2CXc/AD02N8o4jX30mSt8wO5gg3o3mRx+eOXgdMTDo2N582QFIla A3ulldqT0GPX4Ad288FAI7sMqlLEZ4iJKZERnwkXhvli3BzO9g862LYO0u+nXHpwOlAS cWep/Fi0ZTEKbsA9rP5ghMF4asTzwQWN0jyJY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTi=LmGgeo0atWY3YjFRQgn87NgGouD5Bnheh730V@xxxxxxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTi=peUhBPruEGaKbx3eZKQ1Ja8b=dJe3XMJbPR6i@xxxxxxxxxxxxxx> <1293031565.2829.17.camel@mabase> <AANLkTi=LmGgeo0atWY3YjFRQgn87NgGouD5Bnheh730V@xxxxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
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

<Prev in Thread] Current Thread [Next in Thread>