-
Notifications
You must be signed in to change notification settings - Fork 294
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
Update documents for node-specific domain configuration file #8437
base: devel
Are you sure you want to change the base?
Conversation
adds background info / FAQs for upgrading prior to v14.0
Needs backport. |
having to use %h as part of the machine account name. | ||
|
||
Here is an example of PacketFence cluster of 3 nodes, the hostnames of each node are: `pfv14-1`, `pfv14-2` and `pfv14-3`, they all joined "a.com" + | ||
You will see 3 individual machine accounts on Windows Domain Controller, named `pfv14-1`, `pfv14-2` and `pfv14-3` (assuming we are using %h as machine account name). |
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.
node1, node2, node3 instead, based on the configuration file ?
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.
No, based on the assumption.
we assumes the hostnames of the 3 nodes are pfv14-1
pfv14-2
pfv14-3
use node1 node2 node3 instead ?
|
||
We've changed the structure of `domain.conf` configuration file. Since v14.0, each node in a cluster will have their own section. | ||
They will find and store their domain configurations under sections starts with their hostnames. + | ||
This change allows each node in a cluster have their indivudual domain configuration. For example, a node doesn't have to use %h as part of the machine |
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.
Rephrase it.
Description
Update documentation for node-specific domain.conf.
document new domain.conf structure and how to manually join / sync domain.conf in a cluster.
Impacts
update documents on joining a Active Directory Domain.
update migration script to rebuild domain.conf (WIP)
Issue
fixes #8401
Delete branch after merge
YES
Checklist
(REQUIRED) - [yes, no or n/a]
Enhancements
Bug Fixes
issue #8401