[uyuni-devel] Uyuni 4.0.1 Configuration files - schedule a check
Hello Community, I have setup a system with a centrally managed configuration file (/etc/motd) and when applying high state - it gets deployed. I checked the taskomatic and there is a job for checking (compare-configs-default) which properly detects a difference from centrally managed file and local one . Can someone hint me , how can I schedule a task so the files that diff to be replaced with the centrally managed one (from uyuni) - so if I edit /etc/motd locally -> the file to be restored on a schedule ? If there is no such option , is it currently under development ? Thanks in advance. Best Regards, Strahil Nikolov -- To unsubscribe, e-mail: uyuni-devel+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-devel+owner@opensuse.org
On 6/2/19 2:46 PM, Strahil Nikolov wrote:
Can someone hint me , how can I schedule a task so the files that diff to be replaced with the centrally managed one (from uyuni) - so if I edit /etc/motd locally -> the file to be restored on a schedule ?
If there is no such option , is it currently under development ?
One possibility is to schedule a highstate on your minions via cron. There is currently no integrated way to do this in Uyuni and, while proposals have come and gone several times in the past now, this is currently not in any short-term goal (for the development team at SUSE at least). Regards, -- Silvio Moioli SUSE Manager Development Team -- To unsubscribe, e-mail: uyuni-devel+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-devel+owner@opensuse.org
Hi Strahil, I have a small addition to Silvio's answer: if you don't want to call the whole highstate in the cron job, you can just apply the state that corresponds to the configuration channel which contains your configuration file. Each configuration channel creates a salt state that you can use, although its name is not visible in the UI (yet). The naming scheme of the generated states is as follows: manager_org_<your-org-id>.<config-channel-label> So if your motd file is in configuration channel with label 'motd-config' and your organization id is 1, then you can apply the state locally on the minion using this command: salt-call state.apply manager_org_1.motd-config HTH, Franky. Strahil Nikolov writes:
Hello Community,
I have setup a system with a centrally managed configuration file (/etc/motd) and when applying high state - it gets deployed.
I checked the taskomatic and there is a job for checking (compare-configs-default) which properly detects a difference from centrally managed file and local one .
Can someone hint me , how can I schedule a task so the files that diff to be replaced with the centrally managed one (from uyuni) - so if I edit /etc/motd locally -> the file to be restored on a schedule ?
If there is no such option , is it currently under development ?
Thanks in advance.
Best Regards, Strahil Nikolov
-- To unsubscribe, e-mail: uyuni-devel+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-devel+owner@opensuse.org
Hi Franky,
Hi Strahil,
I have a small addition to Silvio's answer: if you don't want to call the whole highstate in the cron job, you can just apply the state that corresponds to the configuration channel which contains your configuration file. Each configuration channel creates a salt state that you can use, although its name is not visible in the UI (yet). The naming scheme of the generated states is as follows:
manager_org_<your-org-id>.<config-channel-label>
So if your motd file is in configuration channel with label 'motd-config' and your organization id is 1, then you can apply the state locally on the minion using this command:
salt-call state.apply manager_org_1.motd-config
This is nice to know - will reduce the stress. ---So far i manage to "verify" the file: uyuni:~ # spacecmd configchannel_verifyfile TEST '/etc/motd' opensuse15-stripe INFO: Connected to https://uyuni.localdomain.com/rpc/api as admin INFO: Action ID: 69 --Check if it completed: uyuni:~ # spacecmd schedule_details 69 INFO: Connected to https://uyuni.localdomain.com/rpc/api as admin ID: 69 Action: Show differences between profiled config files and deployed config files scheduled by admin User: admin Date: 20190604T15:09:34 Completed: 1 Failed: 0 Pending: 0 Completed Systems ----------------- opensuse15-stripe ---Check the status of the task: uyuni:~ # spacecmd schedule_getoutput 69 INFO: Connected to https://uyuni.localdomain.com/rpc/api as admin System: opensuse15-stripe Completed: 20190604T15:09:40 Output ------ Files successfully compared But I can't get the output indicating if the file is the same or not. Any hint how can I find via spacecmd which systems have a difference between the file in the channel and locally on the minion? Silvio, Is there any plan such feature (automatic replacement of files that differs from the configuration channel) to be added into uyuni and thus into SuSE Manager ? Best Regards, Strahil Nikolov -- To unsubscribe, e-mail: uyuni-devel+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-devel+owner@opensuse.org
On 6/4/19 3:19 PM, Strahil Nikolov wrote:
Silvio,
Is there any plan such feature (automatic replacement of files that differs from the configuration channel) to be added into uyuni and thus into SuSE Manager ?
As Frantisek and I wrote, this is possible via Salt states and calling salt in a cron job (I am not sure if this is possible via spacecmd). I would recommend you looking into salt. Regards, -- Silvio Moioli SUSE Manager Development Team -- To unsubscribe, e-mail: uyuni-devel+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-devel+owner@opensuse.org
participants (3)
-
Frantisek Kobzik -
Silvio Moioli -
Strahil Nikolov