Merge lp:~jtv/maas/hardcode-dhcpv6-path into lp:~maas-committers/maas/trunk
Status: | Merged |
---|---|
Approved by: | Jeroen T. Vermeulen |
Approved revision: | no longer in the source branch. |
Merged at revision: | 2824 |
Proposed branch: | lp:~jtv/maas/hardcode-dhcpv6-path |
Merge into: | lp:~maas-committers/maas/trunk |
Diff against target: |
87 lines (+8/-11) 4 files modified
etc/celeryconfig_common.py (+0/-2) etc/democeleryconfig_common.py (+0/-2) src/provisioningserver/rpc/dhcp.py (+6/-4) src/provisioningserver/rpc/tests/test_dhcp.py (+2/-3) |
To merge this branch: | bzr merge lp:~jtv/maas/hardcode-dhcpv6-path |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Gavin Panella (community) | Approve | ||
Review via email: mp+232208@code.launchpad.net |
Commit message
Hard-code paths to DHCPv6 files, instead of taking them from Celery config.
At the point where these paths are needed, the celery config does not seem to contain them! I only see a very minimal celery config, not all the settings we define in celeryconfig_
Description of the change
It's hard to keep track of changes in execution environment with everybody working on different things. Julian used a similar approach for a similar problem the other day.
The one advantage of the configuring this in the Celery file is that we can have a different setting for development branches, but it does not make much sense to serve DHCP from a branch.
Jeroen