Hi,
In case of live-migration reporting I'd rather go with real-time stats,
queried from compute, instead of reporting this data to db first. While
amount of of rpc requests/db updates is relatively small, total number of
such requests depends on amount of active migrations. While realtime data
On 02/04/2016 11:02 PM, Bhandaru, Malini K wrote:
Another thought, for such ephemeral/changing data, such as progress,
why not save the information in the cache (and flush to database at a
lower rate), and retrieve for display to active listeners/UI from the
cache. Once complete or aborted, of
I think we can add a config option for this and set a theoretical proper
default value,
we also add help messages to inform the the user about how inappropriate
value of
this config option will effect the performance.
On Wed, Feb 3, 2016 at 7:45 PM, Daniel P. Berrange
ilto:berra...@redhat.com]
Sent: Wednesday, February 03, 2016 11:46 AM
To: Paul Carlton <paul.carlt...@hpe.com>
Cc: Feng, Shaohe <shaohe.f...@intel.com>; OpenStack Development Mailing List
(not for usage questions) <openstack-dev@lists.openstack.org>
Subject: Re: [openstack-de
On 2016年02月05日 12:02, Bhandaru, Malini K wrote:
I agree with Daniel, keep the periods consistent 5 - 5 .
Another thought, for such ephemeral/changing data, such as progress, why not
save the information in the cache (and flush to database at a lower rate), and
retrieve for display to
On Wed, Feb 03, 2016 at 10:44:36AM +, Daniel P. Berrange wrote:
> On Wed, Feb 03, 2016 at 10:37:24AM +, Koniszewski, Pawel wrote:
> > Hello everyone,
> >
> > On the yesterday's live migration meeting we had concerns that interval of
> > writing migration progress to the database is too
On Wed, Feb 03, 2016 at 10:37:24AM +, Koniszewski, Pawel wrote:
> Hello everyone,
>
> On the yesterday's live migration meeting we had concerns that interval of
> writing migration progress to the database is too short.
>
> Information about migration progress will be stored in the database
Hello everyone,
On the yesterday's live migration meeting we had concerns that interval of
writing migration progress to the database is too short.
Information about migration progress will be stored in the database and
exposed through the API (/servers//migrations/). In current
proposition [1]
> -Original Message-
> From: Daniel P. Berrange [mailto:berra...@redhat.com]
> Sent: 03 February 2016 10:49
> To: OpenStack Development Mailing List (not for usage questions)
> Cc: Feng, Shaohe
> Subject: Re: [openstack-dev] [nova] Migration progress
>
> On We
On 03/02/16 10:49, Daniel P. Berrange wrote:
On Wed, Feb 03, 2016 at 10:44:36AM +, Daniel P. Berrange wrote:
On Wed, Feb 03, 2016 at 10:37:24AM +, Koniszewski, Pawel wrote:
Hello everyone,
On the yesterday's live migration meeting we had concerns that interval of
writing migration
On Wed, Feb 03, 2016 at 11:27:16AM +, Paul Carlton wrote:
> On 03/02/16 10:49, Daniel P. Berrange wrote:
> >On Wed, Feb 03, 2016 at 10:44:36AM +, Daniel P. Berrange wrote:
> >>On Wed, Feb 03, 2016 at 10:37:24AM +, Koniszewski, Pawel wrote:
> >>>Hello everyone,
> >>>
> >>>On the
Hi Paul,
Comments inline:
2015-11-23 16:36 GMT+08:00 Paul Carlton :
> John
>
> At the live migration sub team meeting I undertook to look at the issue
> of progress reporting.
>
> The use cases I'm envisaging are...
>
> As a user I want to know how much longer my instance
On 23 November 2015 at 08:36, Paul Carlton wrote:
> John
>
> At the live migration sub team meeting I undertook to look at the issue
> of progress reporting.
>
> The use cases I'm envisaging are...
>
> As a user I want to know how much longer my instance will be migrating
>
On 23/11/15 11:02, John Garbutt wrote:
On 23 November 2015 at 08:36, Paul Carlton wrote:
John
At the live migration sub team meeting I undertook to look at the issue
of progress reporting.
The use cases I'm envisaging are...
As a user I want to know how much longer
On Mon, Nov 23, 2015 at 08:36:32AM +, Paul Carlton wrote:
> John
>
> At the live migration sub team meeting I undertook to look at the issue
> of progress reporting.
>
> The use cases I'm envisaging are...
>
> As a user I want to know how much longer my instance will be migrating
> for.
>
John
At the live migration sub team meeting I undertook to look at the issue
of progress reporting.
The use cases I'm envisaging are...
As a user I want to know how much longer my instance will be migrating
for.
As an operator I want to identify any migration that are making slow
progress so
16 matches
Mail list logo