Thanks Vish & Chris,
You helped me to understand what is wrong.
I add fixed_range=*10.0.0.0/16* and now all is right.
Solved !
Thank's again.
Regards
On Thu, May 31, 2012 at 1:15 AM, Chris Wright wrote:
> * Emilien Macchi (emilien.mac...@stackops.com) wrote:
> > But I haven't created an
* Emilien Macchi (emilien.mac...@stackops.com) wrote:
> But I haven't created any network yet, and my nova.conf on nova-network
> node is the default file.
>
> Do you think the problem comes from nova.conf ?
Indirectly, yes. The default fixed_range is 10.0.0.0/8 (which will cause a
NAT rule to b
But I haven't created any network yet, and my nova.conf on nova-network
node is the default file.
Do you think the problem comes from nova.conf ?
On Wed, May 30, 2012 at 11:12 PM, Vishvananda Ishaya wrote:
> It is probably because your fixed range for instances conflicts with the
> range used
Hi,
I've just discovered where exactly it's broken : the default NAT rules.
When I flush NAT rules with "*iptables -t nat -F*", I have Internet access.
What do you think about that ?
The fact is I use Ubuntu packages, with default configuration, so need I to
change something, or is it normal ?
Hi,
Which tests did you perform in order to recover your internet connectivity?
It might seem stupid but did you check your /etc/resolv.conf, try to
desinstall/reinstall nova-network, flush the iptables?
Tell us more about the recovery tests you've already done, after this we
will be able go furt
Hi Stackers,
I'm working on a multi-node architecture with Ubuntu 12.04 / Openstack
Essex from Ubuntu packages :
1 controller (with Rabbit-MQ, MySQL, Nova-API, Nova-Schedule), 1 network
(nova-network), 1 compute (nova-compute with KVM).
When I setup a fresh nova-network node, I do (and nothing
6 matches
Mail list logo
