executor: Add timeouts for the first BOOTP request, and network boot activity
Once !258 (merged) lands, I would like to be able to use the information to add timeouts:
- First BOOTP request
- Any other BOOTP/DHCP/TFTP/HTTP activity
This somewhat mirrors what we get with the serial console :) The network timeouts would be de-asserted as soon as the network console kicks in.
Now, making use of this feature in every single job.yml
would be tedious, so I suggest we use the training bootloop to learn sensible values for all these timeouts and store them in mars_db.yml
. The learnt values would be used if the job does not specify the timeouts (first network activity, boot network activity, and first console activity) values.