On 14 May 2017 at 05:53, guru moorthi guru.elinux@gmail.com wrote:
Hello Team,
This is just the request as a lava user.
OK, but DHCP is an admin task, not a test writer.
Please clarify what you mean by lava user - admins of local instances are users just as much as test writers are for remote instances. It is not usually reasonable for test writers to dictate admin tasks unless it blocks some particular test use case.
Are you using an instance of LAVA setup by someone else, so the config is out of your control? Are you administering a local LAVA instance with your own devices?
It would be better if lava supports static ip configuration to deploy and etc stuff with target board.
This is already configurable by admins using the jinja2 device-type templates, if all the relevant devices support it. Most vendor and mainline builds of UBoot and the bootloaders would need customisation to use a static IP on the DUT.
For boards which do not need interaction at the bootloader, primary connections using ssh already require a fixed IPv4 address for the DUT.
Fixed addresses does not preclude DHCP, most DHCP servers can be configured to put certain MAC addresses on to the same IP address each time a new DHCP request is received on that interface.
The user who dont have dhcp setup means this will be very useful to work with target locally.
I think it would be unusual to have LAVA in a situation where there is no DHCP server anywhere on the local network. DHCP is not actually particularly hard to setup in most situations.
I hope you will consider this request and will support static ip also for lava users.
I'm not sure what you are actually asking to be done.
Are you asking for static IP for all DUTs at the bootloader level? Where devices have this support, the relevant jinja2 templates can be locally modified to handle static IP addresses instead of making calls to DHCP. Are you asking for static IP for the installation of lava-server (which is already supported)? Are you asking for static IP for the installation of a worker (this is also already supported)?
We also have device environment support which can help with corporate proxies etc.
Please give a lot more detail about your exact situation because your request, so far, is unclear.