NTP servers on regions and racks do not run in orphan mode
Bug #1625707 reported by
Gavin Panella
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Gavin Panella | ||
Bug Description
From http://
Orphan Mode allows a group of ntpd processes to automonously select a
leader in the event that all real time sources become unreachable
(i.e. are inaccessible).
This is important for:
- Continuity of service should routes out to the public Internet (or
wherever a user's NTP servers reside) go down for more than a few
minutes.
- Operating a MAAS installation that is deliberately not connected to
the public Internet and has no other time sources available. In this
instance we want MAAS's components and deployed nodes to be internally
consistent with one another.
Related branches
lp://staging/~allenap/maas/ntp-service-iburst-orphan-et-al
- Andres Rodriguez (community): Approve
- Blake Rouse (community): Approve
-
Diff: 357 lines (+115/-34)6 files modifiedsrc/maasserver/regiondservices/ntp.py (+2/-2)
src/maasserver/regiondservices/tests/test_ntp.py (+4/-4)
src/provisioningserver/ntp/config.py (+32/-8)
src/provisioningserver/ntp/tests/test_config.py (+70/-13)
src/provisioningserver/rackdservices/ntp.py (+2/-2)
src/provisioningserver/rackdservices/tests/test_ntp.py (+5/-5)
| Changed in maas: | |
| assignee: | nobody → Gavin Panella (allenap) |
| status: | Triaged → In Progress |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
