Het Gala writes:
> On 05/04/24 7:58 pm, Fabiano Rosas wrote:
>> !---|
>>CAUTION: External Email
>>
>> |---!
>>
>> Het Gala writes:
>>
>>> On 27/03/24 2:37 am, Fabia
On 05/04/24 7:58 pm, Fabiano Rosas wrote:
!---|
CAUTION: External Email
|---!
Het Gala writes:
On 27/03/24 2:37 am, Fabiano Rosas wrote:
Het Gala writes:
So
Het Gala writes:
> On 27/03/24 2:37 am, Fabiano Rosas wrote:
>> Het Gala writes:
>>
>> Some comments, mostly just thinking out loud...
>>
>>> For --> migrate
>>> //
>>> //O:/...
>>>
>>> For --> validate
>>> ///O:/O:/
>>> /O:/O:/...
>> Do we need an optional 'capability' element? I'm not su
ping !
On 27/03/24 4:18 pm, Het Gala wrote:
On 27/03/24 2:37 am, Fabiano Rosas wrote:
Het Gala writes:
Some comments, mostly just thinking out loud...
For --> migrate
//
//O:/...
For --> validate
///O:/O:/
/O:/O:/...
Do we need an optional 'capability' element? I'm not sure how pr
On 27/03/24 2:37 am, Fabiano Rosas wrote:
Het Gala writes:
Some comments, mostly just thinking out loud...
For --> migrate
//
//O:/...
For --> validate
///O:/O:/
/O:/O:/...
Do we need an optional 'capability' element? I'm not sure how practical
is to leave that as 'others', because t
Het Gala writes:
Some comments, mostly just thinking out loud...
> For --> migrate
> //
> //O:/...
>
> For --> validate
> ///O:/O:/
> /O:/O:/...
Do we need an optional 'capability' element? I'm not sure how practical
is to leave that as 'others', because that puts it at the end of the
str
Hi Maintainers, this is my first attempt trying to standardise the
grammar around migration qtests. I am not sure at multiple places on
whether a particular string is placed at the right place with the
right grammar. Please comment on the patch, if anything you feel can
be improvised in the existi
For --> migrate
//
//O:/...
For --> validate
///O:/O:/
/O:/O:/...
test-type:: migrate | validate
migration-mode
a. migrate --> :: precopy | postcopy | multifd
b. validate -->:: (what to validate)
methods :: preempt | recovery | reboot | suspend | simple