Comment 4 for bug 1087625

Mine is a templating system that takes the network/interfaces and rewrites
it in the late-commands. Daneyon's is a set of interface-patching and
service restart blocks. His is closely integrated with the openstack
block and simplifies some config at the expense of limiting possible
options; mine's entirely openstack-independent and you can write what
interface definitions you like (but no clues: it's just a raw interface
file).

--
Ian.

On 11/12/2012 18:56, "Mark T. Voelker" <email address hidden> wrote:

>Yes, the description mentions a solution from Ian as well, but doesn't
>say what it is. I think what's lacking here is a description of either
>solution. Hard to make a decision on their relative merits until we
>know what they are. =)
>
>--
>You received this bug notification because you are subscribed to the bug
>report.
>https://bugs.launchpad.net/bugs/1087625
>
>Title:
> Network config must be easy to adapt to different networking
> arrangements
>
>Status in Openstack @ Cisco:
> Confirmed
>Status in Cisco Openstack folsom series:
> Incomplete
>
>Bug description:
> It should be easy to change /etc/network/interfaces to deal with
> different network setups.
>
> End users are likely to want additional networking features. I've
>already seen:
> - multiple interfaces
> - interface bonding
>
> I'm sure there will be others. We should add a more configurable
> mechanism to allow the user to tailor the interfaces file.
>
> (Ian has a proposal in detail and will sort out a pull request.)
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/openstack-cisco/+bug/1087625/+subscriptions