openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #18256
Re: VM connectivity
-
To:
"ext Salvatore Orlando" <sorlando@xxxxxxxxxx>
-
From:
"Heinonen, Johanna (NSN - FI/Espoo)" <johanna.heinonen@xxxxxxx>
-
Date:
Mon, 5 Nov 2012 10:54:34 +0200
-
Cc:
openstack@xxxxxxxxxxxxxxxxxxx
-
In-reply-to:
<CAGR=i3ib7H8kzGYamq35uQg_hNKyM2aoNAW3NnE4X5yJvU9VZw@mail.gmail.com>
-
Thread-index:
Ac2412pbxL3K7ll+TRq747Bo3Wcg5ACWFUFg
-
Thread-topic:
[Openstack] VM connectivity
Hi Salvatore,
I am using Quantum with OVS-plugin. My quantum files are attached.
I have done my configuration by following the instructions by E. Macchi
(includes a tenant internal network and a provider network) and Quantum
admin quide (folsom). I have a single node installation with one
interface eth0 and ubuntu 12.04. The OVS is configured like this:
ovs-vsctl add-br br-int
ovs-vsctl add-br br-ex
ovs-vsctl br-set-external-id br-ex bridge-id br-ex
ovs-vsctl add-port br-ex eth0
I am able to start VMs in both the tenant network and provider network,
they are getting IPs and they become active. The only problem is that I
am not able to connect to them anyhow (no ssh, no ping...)
ovs-vsctl looks like this:
root@localadmin:~# ovs-vsctl show
86f47d37-93b0-4037-a988-1667f85d7c10
Bridge br-tun
Port br-tun
Interface br-tun
type: internal
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Bridge br-ex
Port br-ex
Interface br-ex
type: internal
Port "eth0"
Interface "eth0"
Port "qg-89636625-f4"
Interface "qg-89636625-f4"
type: internal
Bridge br-int
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port "vnet1"
tag: 6
Interface "vnet1"
Port "vnet2"
tag: 1
Interface "vnet2"
Port "tap2fd9694b-51"
tag: 1
Interface "tap2fd9694b-51"
type: internal
Port "vnet0"
tag: 1
Interface "vnet0"
Port br-int
Interface br-int
type: internal
ovs_version: "1.4.0+build0"
Maybe there is something wrong in my configuration? What are the best
troubleshooting tools in this case?
Best regards,
Johanna
From: ext Salvatore Orlando [mailto:sorlando@xxxxxxxxxx]
Sent: Friday, November 02, 2012 10:53 AM
To: Heinonen, Johanna (NSN - FI/Espoo)
Cc: ext Daniel Oliveira; openstack@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Openstack] VM connectivity
Hi Johanna,
are you running Openstack with Quantum or nova-network? In the former
case, which plugin are you using?
If you are using nova-network, which network manager are you using?
Salvatore
On 2 November 2012 06:32, Heinonen, Johanna (NSN - FI/Espoo) <
johanna.heinonen@xxxxxxx> wrote:
Hi Daniel,
Did you solve your problem? If yes, what was the solution? I am
interested because I have similar issues in my setup.
BR
Johanna
From: openstack-bounces+johanna.heinonen=nsn.com@xxxxxxxxxxxxxxxxxxx
[mailto:openstack-bounces+johanna.heinonen
<mailto:openstack-bounces%2Bjohanna.heinonen> =
nsn.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of ext Daniel Oliveira
Sent: Thursday, October 18, 2012 3:17 PM
To: openstack@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Openstack] VM connectivity
So, can anyone help me?
2012/10/16 Daniel Oliveira <dvalbrand@xxxxxxxxx>
When viewing the console-log of a VM, I noticed the following:
"
Starting network...
udhcpc (v1.18.5) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing
WARN: /etc/rc3.d/S40-network failed
"
2012/10/16 Daniel Oliveira <dvalbrand@xxxxxxxxx>
Hello. I installed OpenStack via devStack, and I've noticed I am unable
to SSH, or even ping, to any VM I launch. I've already added both rules
to the default security group (port 22 for SSH, and ICMP rule). I hope
someone can help me, thanks in advance.
P.S.:
-I am not very experienced with all of this, so if you ask me for the
output of some command or log, please specify the file path/command;
-I had a thread with a similar question on this list, but I deleted it
from my email unintentionally.
--
My best regards,
Daniel Oliveira.
--
My best regards,
Daniel Oliveira.
--
My best regards,
Daniel Oliveira.
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
/etc/quantum/quantum.conf:
==========================
core_plugin = quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2
auth_strategy = keystone
fake_rabbit = False
rabbit_password = test123
/etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini:
========================================================
sql_connection = mysql://quantum:test123@localhost:3306/quantum
reconnect_interval = 2
tenant_network_type = gre
tunnel_id_ranges = 1:1000
integration_bridge = br-int
tunnel_bridge = br-tun
local_ip = 192.168.10.6
enable_tunneling = True
root_helper = sudo /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf
/etc/quantum/l3_agent.ini
=========================
[DEFAULT]
# Show debugging output in log (sets DEBUG log level output)
debug = True
# L3 requires that an interface driver be set. Choose the one that best
# matches your plugin.
# OVS
interface_driver = quantum.agent.linux.interface.OVSInterfaceDriver
# LinuxBridge
# interface_driver = quantum.agent.linux.interface.BridgeInterfaceDriver
# The Quantum user information for accessing the Quantum API.
auth_url = http://192.168.10.6:35357/v2.0
auth_region = RegionOne
admin_tenant_name = service
admin_user = quantum
admin_password = test123
# Use "sudo quantum-rootwrap /etc/quantum/rootwrap.conf" to use the real
# root filter facility.
# Change to "sudo" to skip the filtering and just run the comand directly
root_helper = sudo /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf
# Allow overlapping IP (Must have kernel build with CONFIG_NET_NS=y and
# iproute2 package that supports namespaces).
use_namespaces = False
# If use_namespaces is set as False then the agent can only configure one router.
# This is done by setting the specific router_id.
router_id = 2d257f25-d56d-497b-a6f2-69d1153249a5
# Each L3 agent can be associated with at most one external network. This
# value should be set to the UUID of that external network. If empty,
# the agent will enforce that only a single external networks exists and
# use that external network id
gateway_external_net_id = a2774019-a953-46a0-abb0-3c5936515aef
# Indicates that this L3 agent should also handle routers that do not have
# an external network gateway configured. This option should be True only
# for a single agent in a Quantum deployment, and may be False for all agents
# if all routers must have an external network gateway
# handle_internal_only_routers = True
# Name of bridge used for external network traffic. This should be set to
# empty value for the linux bridge
external_network_bridge = br-ex
# IP address used by Nova metadata server
metadata_ip = 192.168.10.6
# TCP Port used by Nova metadata server
metadata_port = 8775
# The time in seconds between state poll requests
polling_interval = 3
/etc/quantum/dhcp_agent.ini:
============================
use_namespaces = False
/etc/quanrum/api-paste.ini:
===========================
admin_tenant_name = service
admin_user = quantum
admin_password = test123
Follow ups
References