[Fuego] UOF - more thoughts after the call

[Bird, Timothy]

> -----Original Message-----
> From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp]
> Sent: Sunday, July 30, 2017 10:57 PM
> To: Bird, Timothy <Tim.Bird at sony.com>; fuego at lists.linuxfoundation.org
> Subject: RE: UOF - more thoughts after the call
> 
> > -----Original Message-----
> > From: Bird, Timothy [mailto:Tim.Bird at sony.com]
> > Sent: Tuesday, July 25, 2017 7:53 AM
> > To: Daniel Sangorrin; fuego at lists.linuxfoundation.org
> > Subject: RE: UOF - more thoughts after the call
> ....
> > > Agree. We need a schema for the criteria.json files. But it should be just a
> > > subschema
> > > of fuego-schema.json since I already put the criteria schema in it.
> > >
> > > > What do you think of /fuego-rw/test-conf ?  I'm open to other names
> for
> > > this. I think
> > > > it does need to be in the rw directory, because users (testers) are
> > > expected to customize it.
> > >
> > > Why not in /fuego-ro?
> > > Testers can customize it from the host, and Jenkins cannot
> overwrite/delete
> > > them by chance.
> > >
> > > > Anything that needs to be written to from inside the docker container
> > > needs to
> > > > be in the rw directory.
> > >
> > > But I was assuming that the user-provided data would be just read not
> > > written by
> > > jenkins. Could you elaborate a bit on that?
> >
> > My expectation is that in the long run (updated) pass criteria will mostly be
> > generated by Fuego tools, from existing log data - then changed with some
> > manual tweaks.   If the tools are normally run inside the container, having
> > the data in fuego-ro will add some extra complexity generating them
> > or replacing them.
> 
> OK. We can then point to a folder in fuego-rw and also support absolute
> paths.
>   - Relative path: ftc add-job --criteria mycriteria.json (would use /fuego-
> rw/test-conf/mycriteria.json)
>   - Absolute path: ftc add-job --criteria /fuego-ro/criteria/bonnie_criteria.json

That sounds good.  Another idea (not to implement now) is to add
the criteria reference in the spec file.  That would work for alternate
criteria stored with the test itself.  But this is getting too complicated.
Let's add support for what you've outlined first, and shake the issues
out of that implementation first.
 -- Tim