On Thu, Oct 13, 2016 at 3:01 PM, Brian Foley wrote:
> On Fri, Oct 07, 2016 at 08:38:05PM +0100, 'Viktor Bachraty' via
> ganeti-devel wrote:
> > In some failure modes, Ganeti state of record may desync from actual
> > state of world. This patch allows migrate --cleanup to
On Fri, Oct 07, 2016 at 08:37:55PM +0100, 'Viktor Bachraty' via ganeti-devel
wrote:
>
> This is my try to make Xen migrations more robust. I'm not entirely sure if
> the approach is acceptable, but couldn't come up with a nicer solution within
> the current design/limitations.
Considering that
Comment #2 on issue 1191 by sascha.l...@gisa.de: sample logrotate conf
breaks with >=logrotate-3.8 and split-user
https://code.google.com/p/ganeti/issues/detail?id=1191
create and su do not the same. create is for setting the owner/permission
on newly created logfile. su is for setting
On Fri, Oct 07, 2016 at 08:38:00PM +0100, 'Viktor Bachraty' via ganeti-devel
wrote:
> Migration is supported on KVM/Xen hypervisors only. Finalize methods are
> called in both success or suspected failure (the master node can't
> certainly know about failures - e.g. in case of timeouts). Thus
On Fri, Oct 07, 2016 at 08:37:57PM +0100, 'Viktor Bachraty' via ganeti-devel
wrote:
> Non-functional changes, smaller code cleanup.
>
> Signed-off-by: Viktor Bachraty
As you say, just cleanup and minor refactoring. LGTM. Thanks.
On Fri, Oct 07, 2016 at 08:37:59PM +0100, 'Viktor Bachraty' via ganeti-devel
wrote:
> GetInstanceInfo returns info that is already parsed with state being an
> enum value coverted from string using _XenToHypervisorInstanceState()
typo: s/coverted/converted/
>
> Signed-off-by: Viktor Bachraty
On Fri, Oct 07, 2016 at 08:38:03PM +0100, 'Viktor Bachraty' via ganeti-devel
wrote:
> In case of Xen migrations, the most common failure case is when the
> instance fails to freeze so the migration fails with domains running on
> both target and source node. This patchs allows migrate --cleanup
On Thu, Oct 13, 2016 at 01:16:39PM +0100, Viktor Bachraty wrote:
>On Thu, Oct 13, 2016 at 12:48 PM, 'Brian Foley' via ganeti-devel
><[1]ganeti-devel@googlegroups.com> wrote:
>
> On Fri, Oct 07, 2016 at 08:38:02PM +0100, 'Viktor Bachraty' via
> ganeti-devel wrote:
> This
On Thu, Oct 13, 2016 at 12:48 PM, 'Brian Foley' via ganeti-devel <
ganeti-devel@googlegroups.com> wrote:
> On Fri, Oct 07, 2016 at 08:38:02PM +0100, 'Viktor Bachraty' via
> ganeti-devel wrote:
>
> This should definitely help cleaning up after migrates. LGTM modulo nits
> below.
>
> >
On Fri, Oct 07, 2016 at 08:38:02PM +0100, 'Viktor Bachraty' via ganeti-devel
wrote:
This should definitely help cleaning up after migrates. LGTM modulo nits below.
> FinalizeMigrationSource and FinalizeMigrationDst should compose an
> 'atomic' operation consisting of 2 idempotent steps, that
On Fri, Oct 07, 2016 at 08:38:05PM +0100, 'Viktor Bachraty' via ganeti-devel
wrote:
> In some failure modes, Ganeti state of record may desync from actual
> state of world. This patch allows migrate --cleanup to adopt an instance
> if it is detected running on an unexpected node.
I'm trying to
On Fri, Oct 07, 2016 at 08:38:07PM +0100, 'Viktor Bachraty' via ganeti-devel
wrote:
> Add a side effect to StartInstance on Xen hypervisor that restores the
> Xen configuration in case it is missing. This is a common failure
> scenario during migrations. The generic backend checks if the instance
12 matches
Mail list logo