[Fuego] Regarding ttc configuration

[Tim.Bird at sony.com]

> -----Original Message-----
> From: Pooja Sanjay More <pooja.sm at pathpartnertech.com>
> 
> Hi,
> 
> We have installed "ttc" outside the container and configured it for basic commands like console and login. Using ttc commands we are
> able to login into rpi board.
> Also, for rpi hard reboot  "rpireboot.py"  script is assign to "reboot_cmd".
> 
> ttc.conf:
> 
> 
> ipaddr=192.168.3.162
> console_cmd=minicom -D /dev/ttyUSB0 -b 115200
> login_cmd=ssh pi at 192.168.3.162 <mailto:pi at 192.168.3.162>
> reboot_cmd=~/fuego/fuego-core/scripts/rpireboot.py

Sounds good.  I'm glad to hear it's working outside the container.

I have been thinking about the problem of where to place ttc helper scripts.
I have some problems in my own lab, with some ttc operations working
outside the Fuego container (that is, working when ttc is executed
directly on the host), but not working inside the container.

I have thought about putting ttc helper scripts into /usr/local/bin
(or maybe even a new directory /usr/test/bin), and bind-mounting
that into the Fuego container, so that 'ttc' in the container can use
the same helper scripts as 'ttc' outside the container.   Let me know
if you have any thoughts about this.  The 'labcontrol' project is intended
to provide a web-based rest API for board control, which will make
this situation go away.  However, that project is not quite ready yet,
and raises some issues of its own.

Note that the provisioning test uses the Fuego function 'target_reboot',
which currently only does a software reboot of the system.

However, there is an overlay function for hardware reboot:
ov_board_control_reboot(), which currently calls 'ftc power-cycle'
(which ends up using the BOARD_CONTROL variable in the system
to call either pdudaemon or ttc to perform a hard reboot of the board).

If you have 'ttc reboot' support inside the container, then you should be
able to add:
BOARD_CONTROL="ttc"
to your rpi board file (along with the TTC_TARGET setting),
and then Fuego should have hardware power control of the board.

Once your board settings are correct, and you can do 'ttc reboot' inside
the container, then you should also be able to do 'ftc power-cycle' both
inside and outside the container, to control power to your boards.

I'll try to get the Functional.reboot test working to test the different
reboot options and configurations in Fuego, so you can test your configuration
there.  The board control support was in flux that last time anyone worked on it, so I'm
not sure the state of it.  But I'd like to get it working in your lab.  And once the
design is settled, it all needs to get documented.
  -- Tim