Hello Aaron, I can ping to 192.168.3.3
ping 192.168.3.3
PING 192.168.3.3 (192.168.3.3) 56(84) bytes of data.
64 bytes from 192.168.3.3: icmp_req=1 ttl=64 time=0.237 ms
64 bytes from 192.168.3.3: icmp_req=2 ttl=64 time=0.193 ms
What am I missing?
Regards.
Guilherme.
2013/2/23 Rahul Sharma
>
As long as there is ip connectivity between the networks it doesn't matter
if you are using tunnels.
On Sat, Feb 23, 2013 at 8:09 AM, Rahul Sharma wrote:
> In one config, you have specified local_ip as 10.10.10.1 and in other as
> 192.168.3.3 . Doesn't they should belong to same network? As per
In one config, you have specified local_ip as 10.10.10.1 and in other as
192.168.3.3 . Doesn't they should belong to same network? As per the doc,
it should be 10.10.10.3? Plus, these both belong to Data-Network, which is
not controller-network communication but compute-network communication.
-Reg
>From the network+controller node can you ping to 192.168.3.3 (just to
confirm there is ip connectivity between those).
Your configs look fine to me. The issue you are having is that your
network+controller node doesn't have a tunnel to your HV node. I'd suggest
restarting the quantum-plugin-open
Here is my controller + network node:
cat /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini
[DATABASE]
# This line MUST be changed to actually run the plugin.
# Example:
# sql_connection = mysql://root:nova@127.0.0.1:3306/ovs_quantum
# Replace 127.0.0.1 above with the IP address of the datab
Running with two nics for this should be fine for tunneling as ip routing
would handle which nic the packets should go out. From what you pasted I
see that one HV has a gre tunnel setup to 10.10.10.1 <-- Who is that host?
Can you attach your /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini
o
Hello Aaron,
Sorry about attaching the infos, about the quantum agent, is it the
quantum-plugin-openvswitch-agent? If i was, the job is already ruunning at
the controller and the compute nodes:
service quantum-plugin-openvswitch-agent start
start: Job is already running: quantum-plugin-openvswit
Hi Guilherme,
(next time please paste these in the email rather than attaching, thx).
>From the text in the attachment (show below). It seems like you are not
running the quantum-openvswitch-agent on your network node as there is no
GRE tunnel from that to your compute node. Once you have
quantu
So guys, any idea about what am i missing?
Thanks.
2013/2/22 Guilherme Russi
> Hello Aaron,
>
> Here are the outputs.
>
>
> Thanks.
>
> Guilherme.
>
>
> 2013/2/21 Aaron Rosen
>
>> The output to the following would be a good start:
>>
>> quantum net-list
>> quantum port-list
>> ovs-dpctl sho
Hello Aaron,
Here are the outputs.
Thanks.
Guilherme.
2013/2/21 Aaron Rosen
> The output to the following would be a good start:
>
> quantum net-list
> quantum port-list
> ovs-dpctl show (on all nodes)
>
> Also make sure the quantum-dhcp-agent is running on your network node.
>
> Aaron
>
>
The output to the following would be a good start:
quantum net-list
quantum port-list
ovs-dpctl show (on all nodes)
Also make sure the quantum-dhcp-agent is running on your network node.
Aaron
On Thu, Feb 21, 2013 at 11:23 AM, Guilherme Russi <
luisguilherme...@gmail.com> wrote:
> Sorry about
Sorry about that, I'm using Folsom release with quantum, I'm installing the
controller node and the network node in the same physical machine, I'm
following this tutorial:
http://docs.openstack.org/folsom/basic-install/content/basic-install_controller.html
Which config files do you need?
Thanks.
Hi,
You'll have to provide more information than this for anyone to help you:
i.e are you using quantum or nova-network, if your using quantum which
plugin, config files etc.
Aaron
On Thu, Feb 21, 2013 at 11:13 AM, Guilherme Russi <
luisguilherme...@gmail.com> wrote:
> Hello guys,
>
> I'm gett
13 matches
Mail list logo
