-
Notifications
You must be signed in to change notification settings - Fork 8
Add syncing sysvol with osync #24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
gochankot
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
have questions to "templates/osync.conf"
|
From the discussion in the office: to guarantee the same state of dc0 and other domain controllers, it takes 2 osync passes (which runs crond once in samba_sysvol_sync_timeout minutes, and if it = 5, then we get a wait of at least 10 minutes after starting). Из обсуждения в офисе: для гарантировано одинакового состояния dc0 и других контролеров домена, требуется ожидание 2 проходов osync (который запускается crond раз в samba_sysvol_sync_timeout минут, и если он = 5, то получаем ожидание минимум 10 минут после запуска). |
gochankot
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
По отношению к https://github.com/altlinuxteam/ansible-samba/pull/4/files изменения - это отсутствие Vagrantfile и параметров в provision.yml (нет запуска для в template по умолчанию) запуск systemd units crond
|
I suggest to finish the task "AS IS" if it is working because we may cause scope creep. We may plan |
|
@mastersin accept pull request? |
|
JFYI, As I can remember there were some issues with an initial data synchronization via osync among controllers. In some cases an actual data can be deleted on dc0 due an unexistance same data on rest of controllers. Such behaviour has prevented to merge previous PR and needs to be more investigated. I strongly recommends to start with rsync for purposes of SysVol replication and move to use the osync only in case of lack of functionality from rsync side. |
|
osync_v1.2.pdf |
Добавлена таска для установки и настройки синхронизации sysvol.
Запускается из main.yml, если параметр samba_sysvol_sync установлен в true