Re: Configuring migration

2023-11-14 Thread Daniel P . Berrangé
On Tue, Nov 14, 2023 at 11:42:27AM +0100, Juan Quintela wrote: > Daniel P. Berrangé wrote: > > On Tue, Nov 14, 2023 at 11:28:28AM +0100, Juan Quintela wrote: > >> Daniel P. Berrangé wrote: > >> > On Thu, Nov 02, 2023 at 03:25:25PM +0100, Markus Armbruster wrote: > >> >> Now let's try to apply thi

Re: Configuring migration

2023-11-14 Thread Juan Quintela
Daniel P. Berrangé wrote: > On Tue, Nov 14, 2023 at 11:28:28AM +0100, Juan Quintela wrote: >> Daniel P. Berrangé wrote: >> > On Thu, Nov 02, 2023 at 03:25:25PM +0100, Markus Armbruster wrote: >> >> Now let's try to apply this to migration. >> >> >> >> As long as we can have just one migration, we

Re: Configuring migration

2023-11-14 Thread Daniel P . Berrangé
On Tue, Nov 14, 2023 at 11:28:28AM +0100, Juan Quintela wrote: > Daniel P. Berrangé wrote: > > On Thu, Nov 02, 2023 at 03:25:25PM +0100, Markus Armbruster wrote: > >> Now let's try to apply this to migration. > >> > >> As long as we can have just one migration, we need just one QAPI object > >> to

Re: Configuring migration

2023-11-14 Thread Juan Quintela
Daniel P. Berrangé wrote: > On Thu, Nov 02, 2023 at 03:25:25PM +0100, Markus Armbruster wrote: >> Now let's try to apply this to migration. >> >> As long as we can have just one migration, we need just one QAPI object >> to configure it. >> >> We could create the object with -object / object_add.

Re: Configuring migration

2023-11-14 Thread Juan Quintela
Markus Armbruster wrote: D> Cc: Paolo for QOM expertise. > > Peter Xu writes: > >> On Thu, Nov 02, 2023 at 03:25:25PM +0100, Markus Armbruster wrote: > > [...] > >>> Migration has its own idiosyncratic configuration interface, even though >>> its configuration needs are not special at all. This

Re: Configuring migration

2023-11-14 Thread Daniel P . Berrangé
On Tue, Nov 14, 2023 at 10:53:20AM +0100, Markus Armbruster wrote: > Daniel P. Berrangé writes: > > > On Thu, Nov 02, 2023 at 03:25:25PM +0100, Markus Armbruster wrote: > >> Now let's try to apply this to migration. > >> > >> As long as we can have just one migration, we need just one QAPI object

Re: Configuring migration

2023-11-14 Thread Markus Armbruster
Daniel P. Berrangé writes: > On Thu, Nov 02, 2023 at 03:25:25PM +0100, Markus Armbruster wrote: >> Now let's try to apply this to migration. >> >> As long as we can have just one migration, we need just one QAPI object >> to configure it. >> >> We could create the object with -object / object_ad

Re: Configuring migration (was: [PATCH v3 3/4] migration/qapi: Replace @MigrateSetParameters with @MigrationParameters)

2023-11-14 Thread Daniel P . Berrangé
On Thu, Nov 02, 2023 at 03:25:25PM +0100, Markus Armbruster wrote: > Now let's try to apply this to migration. > > As long as we can have just one migration, we need just one QAPI object > to configure it. > > We could create the object with -object / object_add. For convenience, > we'd probably

Re: Configuring migration

2023-11-13 Thread Markus Armbruster
Cc: Paolo for QOM expertise. Peter Xu writes: > On Thu, Nov 02, 2023 at 03:25:25PM +0100, Markus Armbruster wrote: [...] >> Migration has its own idiosyncratic configuration interface, even though >> its configuration needs are not special at all. This is due to a long >> history of decisions

Re: Configuring migration (was: [PATCH v3 3/4] migration/qapi: Replace @MigrateSetParameters with @MigrationParameters)

2023-11-02 Thread Peter Xu
On Thu, Nov 02, 2023 at 03:25:25PM +0100, Markus Armbruster wrote: > Juan Quintela writes: > > > Markus Armbruster wrote: > >> Peter Xu writes: > >> > >>> On Wed, Oct 11, 2023 at 04:21:02PM +0200, Markus Armbruster wrote: > > > >>> IIRC both of them used to be the goals: either allow compat pro