Merge lp:~harlowja/cloud-init/local-before-net into lp:~cloud-init-dev/cloud-init/trunk

[Joshua Harlow]

Since cloud-init-local will typically write a networking
file (if used with config-drive) then it makes sense that
cloud-init-local should start before networking (not after).

[Server Team CI bot (server-team-bot)]

FAILED: Continuous integration, rev:967
https://server-team-jenkins.canonical.com/job/cloud-init-ci/52/
Executed test runs:
    None: https://server-team-jenkins.canonical.com/job/lp-vote-on-merge/26/console

Click here to trigger a rebuild:
https://server-team-jenkins.canonical.com/job/cloud-init-ci/52/rebuild

review: Needs Fixing (continuous-integration)

[Scott Moser (smoser)]

Hello,
Thank you for taking the time to contribute to cloud-init. Cloud-init has moved its revision control system to git. As a result, we are marking all bzr merge proposals as 'rejected'. If you would like to re-submit this proposal for review, please do so by following the current HACKING documentation at http://cloudinit.readthedocs.io/en/latest/topics/hacking.html .

Note, I think the general intent of this patch is now in trunk.

Unmerged revisions

967. By Joshua Harlow on 2014-03-11

Start before networking starts

Since cloud-init-local will typically write a networking
file (if used with config-drive) then it makes sense that
cloud-init-local should start before networking (not after).

=== modified file 'sysvinit/redhat/cloud-init-local'
--- sysvinit/redhat/cloud-init-local	2013-07-19 07:23:53 +0000
+++ sysvinit/redhat/cloud-init-local	2014-03-19 17:13:44 +0000
@@ -27,7 +27,7 @@
 # Provides:          cloud-init-local
 # Required-Start:    $local_fs $remote_fs
 # Should-Start:      $time
-# Required-Stop:
+# Required-Stop:     $network
 # Should-Stop:
 # Default-Start:     2 3 4 5
 # Default-Stop:      0 1 6