Open Stack

On Mon, Mar 4, 2013 at 12:52 PM, Nathanael Burton <
nathanael.i.burton at gmail.com> wrote:

> "If for whatever reason, available range is supposed to include:
> 10.1.0.0 -- 10.1.3.255
> then fixed range will have to be set to 10.1.0.0/22 - including the
> 10.1.4.0/24 range and setting up a natting rule for it. This might affect
> existing traffic."
>
> Proposal: The fix proposed in patches I've tested locally (need to clean
> up, write test cases, and add to devstack(?)), pulls the configured
> networks on a host via the network api and then calls the init_host() code
> for each network.  Aside from configuring things automatically, this has
> the side benefit of configuring only what networks are needed and currently
> in use on the host.
>
> References:
> [1]
> https://github.com/openstack/nova/blob/master/nova/network/linux_net.py#L635
> [2] https://bugs.launchpad.net/nova/+bug/741626
>
> Thanks,
>
> Nate
>

And I just noticed that the example in the ticket is actually bad.  Change
that to 10.1.0.0 - 10.1.2.255 and then the fixed_range would be
10.1.0.0/22which would include
10.1.3.0/24 which isn't being used.

Thanks,

Nate
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130304/3a5463db/attachment.html>