Re: [spp] [PATCH 0/3] Introduce recipes as config

[Ferruh Yigit <ferruh.yigit@intel.com>]

On 6/13/2018 3:44 AM, ogawa.yasufumi@lab.ntt.co.jp wrote:
> From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
> 
> Hi,
> 
> SPP's network configuration is able to be restored with 'playback'
> command. This command is useful especially if the network has a lot
> of ports and paths.
> 
> Config files are included in 'docs/samples/command' and named as
> '*.config'. However, it is not a good habit because path is not
> appropriate in meaning and the extension '*config' is ambiguous.
> 
> I would like to introduce 'recipe' which is used for describing network
> configuration instead of 'config' file. As '*.config', the contents of
> recipe file is a set of SPP commands. So, you do not need to change
> existing config files, but simply rename it for usign as recipe.
> 
> Recipe files will be included in 'recipes' directory under the project
> root. Recipe will be named as '*.rcps' it stands for recipe scripts
> for SPP. Although you can use any of extension such as '*.txt' or
> '*.conf' as long as it is included in 'recipes' directory because it is
> just a text file actually, but it is better to use 'rcps' to be
> explicit.
> 
> Recipe is loaded with 'playback' command to restore the network
> configuration. This is an example.
> 
>     spp > playback recipes/spp/usecase/dual_bidir.rcps
> 
> 
> Yasufumi Ogawa (3):
>   recipes: add recipes directory
>   recipes: update SPP usecases
>   recipes: update SPP_VF usecases

Series applied, thanks.