Hi Ido,
please note, that this is only a draft and not a final product.
But PyRecipes implementation will unfortunately break old XML recipes.
This should be discussed on LNST-dev meeting, my idea is, that when
implementation is ready, we push it to new branch and rework all tests
in recipes/ dir to this implementation, as well as regression-tests.
Then, when everything will be up and running and tested thoroughly,
we can merge the branch with upstream.
Have a nice day,
Jiri
2016-04-23 18:25 GMT+02:00 Ido Schimmel <idosch(a)mellanox.com>:
> Hi Jiri,
>
> Fri, Apr 22, 2016 at 11:51:58AM IDT, jprochaz(a)redhat.com wrote:
>>Hello everyone,
>>
>>first working draft implementation is completed. Please, read this cover
>>letter, check the patches and let me know what you like, what you don't like,
>>etc. Please, note, that this is not final implementation.
>>
>>NOTE - patches are not rebased to current HEAD, if you want to try it,
>>please, reset your branch to commit 2398f93.
>>
>>What doesn't work
>>=================
>>multi_match - didn't have time and resources to check physical machines,
>>on virt setup it works, but ends with exception due to no res value returned
>>loopbacks - can't be created
>>netem support - not implemented yet
>
> Good to see that it's coming along :) I'm unclear about something
> though. When applied, will this patchset break functionality of existing
> recipes in recipes/ or will this just add another way to construct
> recipes?
>
> Thanks!