codehaus


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[queens]neutron][metadata] configuration


Hello Slawek, I do not want to use metadata in dhcp namespace. It forces
option 121 and I receive all subnet routes on my instances.
If I use more than 10 subnets on same vlan , it does not work because I do
not receive the 169.254.169.254 routing tables due to the following error:
dnsmasq-dhcp[52165]: cannot send DHCP/BOOTP option 121: no space left in
packet


Ignazio

Il giorno gio 13 feb 2020 alle ore 11:39 Slawek Kaplonski <
skaplons at redhat.com> ha scritto:

> Hi,
>
> In case of such isolated networks, You can configure neutron to serve
> metadata in dhcp namespace and that it will set route to 169.254.169.254
> via dhcp portâ??s IP address.
> Please check config options: [1] and [2]
>
> [1]
> https://docs.openstack.org/neutron/latest/configuration/dhcp-agent.html#DEFAULT.enable_isolated_metadata
> [2]
> https://docs.openstack.org/neutron/latest/configuration/dhcp-agent.html#DEFAULT.force_metadata
>
> > On 13 Feb 2020, at 11:19, Ignazio Cassano <ignaziocassano at gmail.com>
> wrote:
> >
> > Hello everyone, in my installation of Queees I am using many provider
> networks. I don't use openstack router but only dhcp.
> > I would like my instances to reach the metadata agent without the
> 169.154.169.254 route, so I would like the provider networks to directly
> reach the metadata agent on the internal api vip.
> > How can I get this configuration?
> > Thank you
> > Ignazio
>
> â??
> Slawek Kaplonski
> Senior software engineer
> Red Hat
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200213/13e04e28/attachment.html>