mirror of
https://github.com/OpenNebula/one.git
synced 2026-10-25 04:37:42 +09:00
Jan Orel
82196ef2be
The remote scripts directory (former SCRIPTS_REMOTE_DIR) is now fixed
to /var/lib/one-remotes and the configuration attribute is gone. The
old default /var/tmp/one was broken in several ways: /var/tmp content
is aged away by systemd-tmpfiles, the world-writable parent allows
squatting on the directory, and the configurable location was silently
not honored by many drivers, probes and static files (sudoers,
AppArmor, tmpfiles, cron).
- The remotes are synced to /var/lib/one-remotes on the hosts; the
directory is created by the node packages, as it cannot be created
by the unprivileged oneadmin
- The node monitoring DB moves along to /var/lib/one-remotes-db;
it cannot live inside the remotes directory as the sync
(rsync --delete) would remove it. The monitord client migrates
the DB from the legacy location on its first start
- Helpers executed through sudo are installed at a fixed path
(/usr/lib/one/sbin) by the node packages, so they are no longer
executed from an oneadmin-writable location
- Remote hooks (REMOTE = yes) run from /var/lib/one-remotes/hooks.
Hook commands given as an absolute path are executed as-is and
must be updated manually
- Fix remotes sync to run the mkdir on the host: the local shell
interpreted the unquoted ';' and ran it on the frontend instead
- onecfg migrator drops SCRIPTS_REMOTE_DIR from oned.conf and the
stock :remote_hook_base_path from onehem-server.conf