Fri, Mar 08, 2013 at 12:24:34PM CET, rpazdera(a)redhat.com wrote:
Hello everyone!
I'm sending a proposal we might have already discussed at some point. At
the moment, it is required to write some specific IP addresses to the
recipes' configuration section to each interface.
This is usually not a problem, but theoretically, there can be collisions
with addresses you use somewhere else (for instance in the controller
network or to connect your slaves to the internet or whatever).
This could be problem particularly when we start building a large
library of these recipes. We could make the recipes even more portable
by leting the LNST controller chose which address to assign to different
interfaces.
We could do this by adding a special value to the address value field,
which should be very easy to implement:
<addresses>
<address value="auto"/>
</addresses>
In this case, the parser would resolve it to a valid ip address within
some pool that was allocated to the network segment the interface is
plugged into.
We could then maybe add an address type and more:
<addresses>
<address value="auto" type="ipv6"/>
</addresses>
Any feedback is appreciated :).
This seems reasonable. But we not have to clearly state that network
attribute is the one which will be used for this automatic assignment.
Also we have to use some different approach to address ports in
manageable switches in the future.
Cheers,
-Radek
_______________________________________________
LNST-developers mailing list
LNST-developers(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/lnst-developers