On 03/07/2012 09:53, Marnus van Niekerk wrote:
I can now see the bridge created and assigned an address on each
compute node, but all of the VMs get stuck after the bootloader - they
never boot any further.
Sorry, they do actually boot after a while but without any networking..
cloud-init-non
On 02/07/2012 16:33, Razique Mahroua wrote:
I've put a small section here
http://docs.openstack.org/diablo/openstack-compute/admin/content/multi-host.html
Using this I have made progress, except I had to use "nova-manage
network delete 10.10.11.128/26" to delete the network and then added it
They are identical except for these options:
--vncserver_proxyclient_address=10.10.20.11X
--vncserver_listen=10.10.20.11X
--routing_source_ip=10.10.20.11X
The ip that gets issues as gateway is the one in this option
--flat_network_dhcp_start=10.10.11.129
The network range for the flat network an
Are the nova.conf files identical across all the nodes?
On Jul 2, 2012 10:47 AM, "Marnus van Niekerk" wrote:
>
> On 02/07/2012 16:14, Nathanael Burton wrote:
>
>> This is actually what multi_host should be doing when enabled. What
>> node is that original gateway address from? Is that a differe
On 02/07/2012 16:14, Nathanael Burton wrote:
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?
Yes, its is the br100 ip of the controller node which is also a compute
node.
M
_
On 02/07/2012 16:33, Razique Mahroua wrote:
I've put a small section here
http://docs.openstack.org/diablo/openstack-compute/admin/content/multi-host.html
If I read this right then it is saying that nova-api should not run on
every compute node, only nova-network and nova-compute.
Is that ri
Hi Marnus, I've put a small section herehttp://docs.openstack.org/diablo/openstack-compute/admin/content/multi-host.htmlI'm thinking about the routing_source_ip configuration option into your nova.conf files
Nuage & Co - Razique Mahroua razique.mahr...@gmail.com
Le 2 juil. 2012 à 14:41, Marnus van
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 wrote:
> I have managed to get this working by changing the default gateway on the
> guest t
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 chan
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 n
10 matches
Mail list logo
