fuel-dev team mailing list archive

[Andrey Danin <adanin@xxxxxxxxxxxx>]

There is a little chance that a node will boot up via another interface and
Cobbler will put it to the bootstrap stage instead of the target stage. We
have to provide all MAC addresses of a node to Cobbler but it can't use one
IP for all MACs. So we have to allocate a lot of IPs.

We can improve our mechanism by the following:
  * Assign IP to the node's admin interface only. Use it as a default
behavior but add an UI switch to enable a greedy behavior.
  * Run a predeployment DHCP check in order to find all interfaces which
really can communicate with PXE network and assign IPs to these interfaces
only.



On Thu, Jan 23, 2014 at 12:29 AM, Ryan Moe <rmoe@xxxxxxxxxxxx> wrote:

> What is the reasoning behind assigning an IP from the admin network to all
> interfaces [1]? It has caused problems in deployments where IPs are tightly
> managed and/or machines have a large number of interfaces.
>
> Thanks,
> Ryan
>
> [1]
> https://github.com/stackforge/fuel-web/blob/master/nailgun/nailgun/task/helpers.py#L435
>
> --
> Mailing list: https://launchpad.net/~fuel-dev
> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~fuel-dev
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Andrey Danin
adanin@xxxxxxxxxxxx
skype: gcon.monolake