This is actually what multi_host should be doing when enabled.  What
node is that original gateway address from?  Is that a different
compute node?

Nate

On Mon, Jul 2, 2012 at 8:41 AM, Marnus van Niekerk <m...@mjvn.net> wrote:
> I have managed to get this working by changing the default gateway on the
> guest to the compute node it is running on.
>
> ubuntu@monitor:~$ sudo route del default gw 10.10.11.129
> ubuntu@monitor:~$ sudo route add default gw 10.10.11.112
>
> But the default gateway is assigned by DHCP - so how can I change the
> default gateway that nova-network assigns on each compute node?
>
> Tx
> M
>
>
> On 02/07/2012 13:50, Marnus van Niekerk wrote:
>
> Hi.  I am trying to use multi_host to eliminate the "controller" hosts as a
> single point of failure.
>
> I followed the steps at
> http://docs.openstack.org/essex/openstack-compute/admin/content/existing-ha-networking-options.html
> and added thse options to the end of nova.conf. Now the guests have no
> connectivity to the outside world at all. (Running on ubuntu 12.04 using
> packages.)
>
> Controller:
> --multi_host=True
> --enabled_apis=ec2,osapi_compute,osapi_volume,metadata
>
> Compute nodes:
> --multi_host=True
> --enabled_apis=metadata
>
> I also tried changing the routing_source_ip option on each compute node to
> it's own ip address but it makes no difference.
> --routing_source_ip=10.10.20.11X
>
> What am I missing?
>
> Tx
> Marnus van Niekerk
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Reply via email to