- Summary
- Add target database (aka "board dictionary") feature to fuego; Owner: Tim; Reporter: Tim; Status: closed; Priority: medium
|
; Summary: Add target database (aka "board dictionary") feature to fuego; Owner: Tim; Reporter: Tim; Status: closed; Priority: medium
|
|
|
= Description =The target database holds information about a board, for use by the fuegosystem. The "board dictionary" holds the information for a particular board.
|
|
The information that needs to be held for a particular board dependson the tests that are installed in the system. Thus the system needsto be ad-hoc.
|
The information that needs to be held for a particular board dependson the tests that are installed in the system. Thus the system needsto be ad-hoc.
|
|
ftc should be used to manage the board dictionary values (liketdb). A user should be able to manually clear values, update valuesand read values.
|
ftc should be used to manage the board dictionary values (liketdb). A user should be able to manually clear values, update valuesand read values.
|
|
The board file should be used to hold the board dictionary. The dictionaryvalues should be kept in ENVIRONMENT variables, that are set when theboard file is source'd.
|
The board file should be used to hold the board dictionary. The dictionaryvalues should be kept in ENVIRONMENT variables, that are set when theboard file is source'd.
|
|
Some values that should be considered "board dictionary" values are: * SATA_DEV * SATA_MP * LTP_OPEN_POSIX_SUBTEST_COUNT_POS * LTP_OPEN_POSIX_SUBTEST_COUNT_NEG * FUNCTIONAL_BC_PROGRAM
|
Some values that should be considered "board dictionary" values are: * SATA_DEV * SATA_MP * LTP_OPEN_POSIX_SUBTEST_COUNT_POS * LTP_OPEN_POSIX_SUBTEST_COUNT_NEG * FUNCTIONAL_BC_PROGRAM
|
|
This feature supports manual and programmatic modification of the informationfor a board. This supports several features: * ability to scan a target, and add info to the file * for detecting test binaries * for assistance in installing board files (autodetect SSH_PORT, IP, TRANSPORT, PLATFORM) * ability to add info for latest tests * performance baseline?
|
This feature supports manual and programmatic modification of the informationfor a board. This supports several features: * ability to scan a target, and add info to the file * for detecting test binaries * for assistance in installing board files (autodetect SSH_PORT, IP, TRANSPORT, PLATFORM) * ability to add info for latest tests * performance baseline?
|
|
|
= Notes =When updating the board file, updates to existing values shouldreplace lines in the same position in the file. (Lines should be replacedin-place, and not moved around on an edit).
|
|
Should there be an indication of whether a value should be persistent or not?Some values might change, if the software on the target changes.For example, FUNCTIONAL_BC_PROGRAM might change if the distro on the targetchanges, or if the program gets deleted. Should this be treated likea cache variable, instead of an immutable fact about the board?How would we indicate that?
|
Should there be an indication of whether a value should be persistent or not?Some values might change, if the software on the target changes.For example, FUNCTIONAL_BC_PROGRAM might change if the distro on the targetchanges, or if the program gets deleted. Should this be treated likea cache variable, instead of an immutable fact about the board?How would we indicate that?
|
|
Update in May 2017 - dynamic variables are now placed in the file:/fuego-rw/boards/<board>.vars. These can be erased at any time, and willbe rebuilt by tests that populate the file.
|
Update in May 2017 - dynamic variables are now placed in the file:/fuego-rw/boards/<board>.vars. These can be erased at any time, and willbe rebuilt by tests that populate the file.
|
|
For now, ignore this issue.
|
For now, ignore this issue.
|
- backlink
Fuego Issues List
|
; backlink: [[Fuego Issues List]]
|