|Kapua jobs usage [message #1814794]
||Wed, 18 September 2019 12:35
| Pedro de Arquer
Registered: December 2018
I'm interested in configure a series of tasks to manage and maintain the Kura devices from Kapua. The kind of tasks I'm interested in would be:
- Install: install a set of packages and apply a configuration to the devices. Keeping in mind that the configurations vary from one device to another (the set of packages may also be different but they will be mostly standard).
- Update: upgrade the packages of all the devices to new versions.
- Restart: a given functionality across multiple devices. Could be done with the restart of given bundles.
- Reboot: of the whole device
In order to make this kind of tasks available for a user without programming skills, I'm considering the batch jobs feature but I'm unable to design a proper way for two of them because of:
- Install: different configurations for a single job depending on the device is completely unavailable
- Restart: can only be done via bundle ID, and such ID varies from one device to another for the same bundle.
Besides, the batch job is only executed once an then the task must be recreated or the devices removed and readded to reset its status.
Regarding this approach, I have three questions:
- Is there a better approach for such tasks? Maybe not with batch jobs, or an approach that requires a management specific service on Kura.
- The issues detected for install and restart tasks are by design or are they considered for further development?
- Which is the canonical usage of the batch jobs? As I have the sensation that I'm misunderstanding the purpose of the whole feature.
Thanks in advance,
Powered by FUDForum
. Page generated in 0.06133 seconds