On 2015/6/23 15:50, Markus Armbruster wrote:
zhanghailiang writes:
On 2015/6/19 16:11, Markus Armbruster wrote:
[...]
To avoid the ugliness, we could change the QAPI generator. Currently,
{ 'command': 'migrate-set-parameters',
'data': 'MigrationParameters' }
generates the sa
zhanghailiang writes:
> On 2015/6/19 16:11, Markus Armbruster wrote:
[...]
>> To avoid the ugliness, we could change the QAPI generator. Currently,
>>
>> { 'command': 'migrate-set-parameters',
>>'data': 'MigrationParameters' }
>>
>> generates the same interface as when you inline Mi
On 2015/6/19 16:11, Markus Armbruster wrote:
zhanghailiang writes:
Hi,
Is there any news about this discussion?
Is anyone working on it? ;)
Since the 'hard feature freeze' time is closer, we'd better to fix it in 2.4
before libvirt uses it.
I have sent a RFC patch "[RFC] migration: Re-imple
zhanghailiang writes:
> Hi,
>
> Is there any news about this discussion?
> Is anyone working on it? ;)
>
> Since the 'hard feature freeze' time is closer, we'd better to fix it in 2.4
> before libvirt uses it.
>
> I have sent a RFC patch "[RFC] migration: Re-implement
> 'migrate-set-parameters'
Hi,
Is there any news about this discussion?
Is anyone working on it? ;)
Since the 'hard feature freeze' time is closer, we'd better to fix it in 2.4
before libvirt uses it.
I have sent a RFC patch "[RFC] migration: Re-implement 'migrate-set-parameters' to
make it easily for extension"
http://
"Dr. David Alan Gilbert" writes:
> * Markus Armbruster (arm...@redhat.com) wrote:
>> "Dr. David Alan Gilbert" writes:
>>
>> > * Eric Blake (ebl...@redhat.com) wrote:
>> >> On 06/05/2015 03:50 AM, Dr. David Alan Gilbert wrote:
>> >> > Hi,
>> >> > Is there any way that we could make it easier t
* Markus Armbruster (arm...@redhat.com) wrote:
> "Dr. David Alan Gilbert" writes:
>
> > * Eric Blake (ebl...@redhat.com) wrote:
> >> On 06/05/2015 03:50 AM, Dr. David Alan Gilbert wrote:
> >> > Hi,
> >> > Is there any way that we could make it easier to add new migration
> >> > parameters? The
"Dr. David Alan Gilbert" writes:
> * Eric Blake (ebl...@redhat.com) wrote:
>> On 06/05/2015 03:50 AM, Dr. David Alan Gilbert wrote:
>> > Hi,
>> > Is there any way that we could make it easier to add new migration
>> > parameters? The current way is complicated and error prone;
>> > as far as I
* Eric Blake (ebl...@redhat.com) wrote:
> On 06/05/2015 03:50 AM, Dr. David Alan Gilbert wrote:
> > Hi,
> > Is there any way that we could make it easier to add new migration
> > parameters? The current way is complicated and error prone;
> > as far as I can tell, to add a new parameter we need t
On 06/05/2015 03:50 AM, Dr. David Alan Gilbert wrote:
> Hi,
> Is there any way that we could make it easier to add new migration
> parameters? The current way is complicated and error prone;
> as far as I can tell, to add a new parameter we need to:
>
> 1) qapi-schema.json
> a) Add to 'Mig
* Dr. David Alan Gilbert (dgilb...@redhat.com) wrote:
> Hi,
> Is there any way that we could make it easier to add new migration
> parameters? The current way is complicated and error prone;
> as far as I can tell, to add a new parameter we need to:
>
> 1) qapi-schema.json
> a) Add to 'Mig
Hi,
Is there any way that we could make it easier to add new migration
parameters? The current way is complicated and error prone;
as far as I can tell, to add a new parameter we need to:
1) qapi-schema.json
a) Add to 'MigrationParameter' enum, include comment
b) Add to migrate-set-par
12 matches
Mail list logo
