Hello everyone, Can you help me on below two questions?
1. I did email notification settings for sending emails after job complete or incomplete. How can I get whole logs (where are logs?) about email sending process? I need to debug email sending.
2. I want to use script to control device state periodically. How can I set device to maintenance state using command, like lava-tool command?
Thanks in advance.
On 12 October 2016 at 09:34, kingboli lijinbohehe@163.com wrote:
Hello everyone, Can you help me on below two questions?
- I did email notification settings for sending emails after job complete
or incomplete. How can I get whole logs (where are logs?) about email sending process? I need to debug email sending.
LAVA uses django which just uses local settings for your mail transport agent, probably exim4 by default in Jessie. Configuring exim4 for your local email setup is outside the scope of this list or the LAVA documentation. What you can test is that sending mail from the command line on the master needs to work, then the django processes should be able to send email as well. So try the mail program directly on the command line of the master, as the lavaserver user.
- I want to use script to control device state periodically. How can I set device to maintenance state using command, like lava-tool
command?
lava-tool does not support this but XML-RPC calls are available. See the api/help/ pages on your localhost or https://staging.validation.linaro.org/api/help/
https://staging.validation.linaro.org/api/help/#scheduler.put_into_maintenan... https://staging.validation.linaro.org/api/help/#scheduler.put_into_online_mo...
Taking devices in and out of maintenance mode frequently is unnecessary churn. LAVA is not a booking system so think carefully about your lab design so that devices are available for automated submissions more often than not.
Hi Neil Williams,
Sometimes the devices are not in auto-testing, and we want to improve the devices usage by using the devices for some manual tests and do not want the manual jobs to be interrupted by a sudden auto-test task.
Have check the XML-RPC and it is very useful. However, the functions in xmlrpclib of my localhost is not as many as the website lists. And unfortunately, no scheduler.put_into_maintenance_mode() and scheduler.put_into_online_mode() after running server.system.listMethods(). can you share the latest complete xmllib python file? p.s. All functions I get about scheduler are: 'scheduler.all_device_types', 'scheduler.all_devices', 'scheduler.all_jobs', 'scheduler.cancel_job', 'scheduler.get_pipeline_device_config', 'scheduler.job_details', 'scheduler.job_output', 'scheduler.job_status', 'scheduler.notify_incomplete_job', 'scheduler.pending_jobs_by_device_type', 'scheduler.resubmit_job', 'scheduler.submit_job', 'scheduler.validate_yaml', 'scheduler.worker_heartbeat', 'system.getCapabilities',
Thanks.
At 2016-10-12 16:46:53, "Neil Williams" neil.williams@linaro.org wrote:
On 12 October 2016 at 09:34, kingboli lijinbohehe@163.com wrote:
Hello everyone, Can you help me on below two questions?
- I did email notification settings for sending emails after job complete
or incomplete. How can I get whole logs (where are logs?) about email sending process? I need to debug email sending.
LAVA uses django which just uses local settings for your mail transport agent, probably exim4 by default in Jessie. Configuring exim4 for your local email setup is outside the scope of this list or the LAVA documentation. What you can test is that sending mail from the command line on the master needs to work, then the django processes should be able to send email as well. So try the mail program directly on the command line of the master, as the lavaserver user.
- I want to use script to control device state periodically. How can I set device to maintenance state using command, like lava-tool
command?
lava-tool does not support this but XML-RPC calls are available. See the api/help/ pages on your localhost or https://staging.validation.linaro.org/api/help/
https://staging.validation.linaro.org/api/help/#scheduler.put_into_maintenan... https://staging.validation.linaro.org/api/help/#scheduler.put_into_online_mo...
Taking devices in and out of maintenance mode frequently is unnecessary churn. LAVA is not a booking system so think carefully about your lab design so that devices are available for automated submissions more often than not.
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
On 17 October 2016 at 06:03, kingboli lijinbohehe@163.com wrote:
Hi Neil Williams,
Sometimes the devices are not in auto-testing, and we want to improve the devices usage by using the devices for some manual tests and do not want the manual jobs to be interrupted by a sudden auto-test task.
This is a bad design for any LAVA lab. Do everything you can to avoid this kind of mixed deployment. A Continuous Integration system like LAVA needs to be able to run an automated test immediately. Manual tests can be done using hacking sessions. Otherwise, users of the automated tests have no idea of when results will be available which makes the automated tests largely worthless.
Maintenance mode is designed for use around planned maintenance windows or unscheduled downtime - for example a few times a year. It is a misuse of maintenance mode to hijack a LAVA device for personal testing instead of actual lab maintenance.
The solution is to obtain more hardware, then the automated tests can run without interruption.
https://validation.linaro.org/static/docs/v2/hacking-session.html
Have check the XML-RPC and it is very useful. However, the functions in xmlrpclib of my localhost is not as many as the website lists.
You need to upgrade lava-server using jessie-backports and the production repo. You are using an old version of LAVA.
https://validation.linaro.org/static/docs/v2/installing_on_debian.html#debia...
Thanks.
At 2016-10-12 16:46:53, "Neil Williams" neil.williams@linaro.org wrote:
On 12 October 2016 at 09:34, kingboli lijinbohehe@163.com wrote:
Hello everyone, Can you help me on below two questions?
- I did email notification settings for sending emails after job
complete or incomplete. How can I get whole logs (where are logs?) about email sending process? I need to debug email sending.
LAVA uses django which just uses local settings for your mail transport agent, probably exim4 by default in Jessie. Configuring exim4 for your local email setup is outside the scope of this list or the LAVA documentation. What you can test is that sending mail from the command line on the master needs to work, then the django processes should be able to send email as well. So try the mail program directly on the command line of the master, as the lavaserver user.
- I want to use script to control device state periodically. How can I set device to maintenance state using command, like
lava-tool command?
lava-tool does not support this but XML-RPC calls are available. See the api/help/ pages on your localhost or https://staging.validation.linaro.org/api/help/
https://staging.validation.linaro.org/api/help/#scheduler.put_into_maintenan... https://staging.validation.linaro.org/api/help/#scheduler.put_into_online_mo...
Taking devices in and out of maintenance mode frequently is unnecessary churn. LAVA is not a booking system so think carefully about your lab design so that devices are available for automated submissions more often than not.
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
-
kingboli -
Neil Williams