Cannot insert ramdisk fragments before network configuration

[Clint Byrum]

If one wants to load a network module before the network configuration in the ramdisk element, one must override the element and write a whole new init script. This should be doable with snippet files like the rest of init.d.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/56836

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/56836
Committed: http://github.com/openstack/diskimage-builder/commit/c9f432d45b9282e1c773cbf1258c9438548c8b47
Submitter: Jenkins
Branch: master

commit c9f432d45b9282e1c773cbf1258c9438548c8b47
Author: Chris Jones <email address hidden>
Date: Sun Nov 17 20:37:26 2013 +0000

    Split network bringup out of base ramdisk init.

    We now run the network bringup portion of the ramdisk init from an
    init.d script, thus allowing image builders to inject code into the init
    script before that point (e.g. configure network hardware).
    The environment variables used by the network bringup code are retained
    in the base init script so they can be overridden by init.d fragments.

    Change-Id: I1ef0bb21e7f26c0ff3f02266f853ce5402bcb94d
    Closes-Bug: #1252023