Merge lp:~jtv/maas/netifaces into lp:maas/trunk
| Status: | Merged | ||||
|---|---|---|---|---|---|
| Approved by: | Jeroen T. Vermeulen on 2012-10-02 | ||||
| Approved revision: | 1122 | ||||
| Merged at revision: | 1125 | ||||
| Proposed branch: | lp:~jtv/maas/netifaces | ||||
| Merge into: | lp:maas/trunk | ||||
| Diff against target: |
450 lines (+88/-304) 3 files modified
required-packages/base (+1/-0) src/provisioningserver/network.py (+25/-54) src/provisioningserver/tests/test_network.py (+62/-250) |
||||
| To merge this branch: | bzr merge lp:~jtv/maas/netifaces | ||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Julian Edwards (community) | 2012-10-02 | Approve on 2012-10-02 | |
|
Review via email:
|
|||
Commit Message
Replace ifconfig-parser with netifaces. We need this to avoid fork()ing off ifconfig, which confuses Upstart's fork tracking.
Description of the Change
Briefly discussed with Julian. This one's needed to get tests passing on the branch that will make celery run as the maas user: we were forking once to get our networks information *before* the crucial fork of the celery "daemon" which we wanted upstart to track.
Jeroen
| Gavin Panella (allenap) wrote : | # |
I like this too. An alternative approach, should we have problems with other forks, would be to fork, then exec celery in the *parent* and continue doing whatever it is we need to do in the child process. Then upstart wouldn't need to follow forks, and there would be no chance of it getting confused.


Nice.