Open Stack

Hi Roman,

Thanks for your detailed response.

1. Is there anyway to have Neutron schedule DHCP on all DHCP agents by
default? We are running a multi-tenant setup, and most of our users will be
using Horizon to deploy their instances/networking. It would be great to
have an option in the Neutron config to automatically push to all agents.

2. Do you have a blueprint to follow for this? Would be great to see!

3. So if we spin up another "network node" with the OVS agent running on
it, it should automatically create the L2 networking there as well?

Thanks!


On Fri, Jul 19, 2013 at 6:59 AM, Roman Podolyaka <rpodolyaka at mirantis.com>wrote:

> Hi all,
>
> Indeed, Neutron doesn't provide an HA solution out-of-box. I would say
> that, agents scheduling described in [1] is just the first step on a way to
> HA.
>
> Nevertheless, there are a few ways of providing HA for different parts of
> Neutron requiring some additional efforts:
>
> 1. DHCP-agent. Neutron networks can be scheduled to a few DHCP-agents
> running on different nodes, and thus providing HA for DHCP in Active/Active
> mode.
>
> 2. L3-agent. Neutron routers can be scheduled to a few L3-agents, but only
> one of them can be active at the time. Should an L3-agent hosting a router
> fail, it's up to you to reschedule the router. Though, an Active/Active HA
> solution was proposed recently [2].
>
> 3. L2-agent. An agent of this type is run on every node of a cluster. I'm
> not sure you can run a multiple instances of it on one node (as it performs
> configuration of network interfaces/etc, so this would eventually lead to
> race-conditions). So this is similar to a failure of nova-compute daemon or
> a physical node.
>
> Thanks,
> Roman
>
> [1]
> http://www.mirantis.com/blog/a-new-agent-management-approach-in-quantum-for-openstack-grizzly/
> [2]
> http://telekomcloud.github.io/2013/06/10/openstack-networking-high-availability.html
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20130719/7e9a7a49/attachment.html>