Hello,
i have a general question regarding the proposed use of salt-stack in OMV5.
I use salt stack to manage all of my systems, including all of my OMV Installations, will this be possible with OMV5??
My OMV Systems (i have more than one) all are Salt-Minions to a seperate Salt-Master.
AFAIK a Minion can only connect to one Master
Thanks for clarification
OK, i just learned that you CAN connect a minion to multiple salt-masters IF the master keys are the same.
I guess i can hack this into my environment somehow.
A little Update on this, as i now use OMV5 for my Backup NAS:
Salt seems to run in local mode, so i just set up OMV with all Plugins i need and uncommented all lines in /etc/salt/minion.d/openmediavault.conf.
I have no idea how this will affect OMV in the future, but i need saltstack to manage my server. If i run into issues i will report back.
If anyone knows how the official solution would be if i want to use saltstack with my own master, please let me know.
Update: after some days of normal operation i can now say that this solution is absolutely not what you want!
Every time you apply a configuration change OMV5 checks against its salt states and will fail if they aren't there.
I then have to enable the custom OMV Salt Configuration, apply the change and then disable the config again.
I still haven't found any official information regarding the salt stack usage in OMV5 but this is sadly breakting my usecase for OMV
Error you will get when salt is not happy:
Error #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run cron 2>&1' with exit code '1': /usr/lib/python3/dist-packages/salt/transport/zeromq.py:42: VisibleDeprecationWarning: zmq.eventloop.minitornado is deprecated in pyzmq 14.0 and will be removed.
Install tornado itself to use zmq with the tornado IOLoop.
import zmq.eventloop.ioloop
/usr/lib/python3/dist-packages/salt/modules/file.py:32: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
from collections import Iterable, Mapping, namedtuple
pluto:
----------
ID: create_cron_powermanagement
Function: file.managed
Name: /etc/cron.d/openmediavault-powermngmt
Result: True
Comment: File /etc/cron.d/openmediavault-powermngmt updated
Started: 10:24:43.529936
Duration: 29.423 ms
Changes:
----------
diff:
New file
mode:
0644
----------
ID: remove_cron_userdefined_scripts
Function: module.run
Result: False
Comment: Module function remove_cron_userdefined_scripts is not available
Started: 10:24:43.560054
Duration: 0.407 ms
Changes:
----------
ID: create_cron_userdefined
Function: file.managed
Name: /etc/cron.d/openmediavault-userdefined
Result: True
Comment: File /etc/cron.d/openmediavault-userdefined updated
Started: 10:24:43.560543
Duration: 13.475 ms
Changes:
----------
diff:
New file
mode:
0644
Summary for pluto
------------
Succeeded: 2 (changed=2)
Failed: 1
------------
Total states run: 3
Total run time: 43.305 ms in /usr/share/php/openmediavault/system/process.inc:182
Stack trace:
#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(60): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(167): OMV\Engine\Module\ServiceAbstract->deploy()
#2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusIK...', '/tmp/bgoutputDo...')
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#7 /usr/share/openmediavault/engined/rpc/config.inc(189): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#12 {main}any news about it? I'm fan of Ansible, but I see OMV already use similar salt solution. But how to use it if, for example, I have multiple OMV computers? I'd like to manage them in one centralised point, the best would be sth like roles in Ansible, stored in GIT. So if sth bad happens, I can clone GIT repo on any computer, install Ansible on this computer, install OMV, then run playbook and my OMV is in desired state
Don’t have an account yet? Register yourself now and be a part of our community!