slogan@openstack4:~/devstack/devstack$ ps -eaf | grep quantum
stack 4194 4133 0 12:57 pts/3 00:00:02 python /opt/stack/quantum/bin/quantum-server --config-file /etc/quantum/quantum.conf --config-file /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini
root 4264 4196 0 12:57 pts/6 00:00:00 sudo python /opt/stack/quantum/quantum/plugins/openvswitch/agent/ovs_quantum_agent.py --config-file /etc/quantum/quantum.conf --config-file /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini
root 4267 4264 0 12:57 pts/6 00:00:09 python /opt/stack/quantum/quantum/plugins/openvswitch/agent/ovs_quantum_agent.py --config-file /etc/quantum/quantum.conf --config-file /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini
Short answer, no. Maybe a devstack issue? It is what is supposed to launch it. I see evidence that it is being launched in the stack logs:
...
+ screen -S stack -p q-agt -X stuff 'sudo python /opt/stack/quantum/quantum/plugins/openvswitch/agent/ovs_quantum_agent.py --config-file /etc/quantum/quantum.conf --config-file /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini^M'
+ screen_it q-dhcp 'sudo python /opt/stack/quantum/bin/quantum-dhcp-agent --config-file /etc/quantum/quantum.conf --config-file=/etc/quantum/dhcp_agent.ini'
++ echo -ne '\015'
+ NL=$'\r'
+ is_service_enabled q-dhcp
+ services=q-dhcp
+ for service in '${services}'
+ [[ ,g-api,g-reg,key,n-api,n-cpu,n-sch,n-vnc,mysql,rabbit,openstackx,q-svc,quantum,q-agt,n-cpu,q-dhcp, =~ ,q-dhcp, ]]
+ return 0
+ screen_rc q-dhcp 'sudo python /opt/stack/quantum/bin/quantum-dhcp-agent --config-file /etc/quantum/quantum.conf --config-file=/etc/quantum/dhcp_agent.ini'
+ SCREENRC=/opt/stack/devstack/stack-screenrc
+ [[ ! -e /opt/stack/devstack/stack-screenrc ]]
+ grep q-dhcp /opt/stack/devstack/stack-screenrc
++ echo -ne '\015'
+ NL=$'\r'
+ echo 'screen -t q-dhcp bash'
+ echo 'stuff "sudo python /opt/stack/quantum/bin/quantum-dhcp-agent --config-file /etc/quantum/quantum.conf --config-file=/etc/quantum/dhcp_agent.ini^M"'
+ screen -S stack -X screen -t q-dhcp
+ sleep 1.5
+ [[ -n '' ]]
+ screen -S stack -p q-dhcp -X stuff 'sudo python /opt/stack/quantum/bin/quantum-dhcp-agent --config-file /etc/quantum/quantum.conf --config-file=/etc/quantum/dhcp_agent.ini^M'
+ NOVA_CONF_DIR=/etc/nova
+ [[ ! -d /etc/nova ]]
+ sudo mkdir -p /etc/nova
++ whoami
...
I tried running the command manually and same results in ps, perhaps it runs but for a short time. The fact it is being passed two arguments with same flag (--config-file) looks worrisome depending on how argc, argv is being parsed by the process (is that a good idea?). Nonetheless, both files exist:
/etc/quantum/dhcp_agent.ini:
[DEFAULT]
admin_password = password
admin_user = quantum
admin_tenant_name = service
auth_url = http://192.168.4.1:35357/v2.0
db_connection = mysql://root:password@localhost/ovs_quantum?charset=utf8
use_namespaces = True
debug = True
verbose = True
# Show debugging output in log (sets DEBUG log level output)
# debug = true
# Where to store dnsmasq state files. This directory must be writable by the
# user executing the agent. The value below is compatible with a default
# devstack installation.
state_path = /opt/stack/data
# The DHCP requires that an inteface driver be set. Choose the one that best
# matches you plugin.
# OVS
interface_driver = quantum.agent.linux.interface.OVSInterfaceDriver
# LinuxBridge
#interface_driver = quantum.agent.linux.interface.BridgeInterfaceDriver
# Ryu
#interface_driver = quantum.agent.linux.interface.RyuInterfaceDriver
# The agent can use other DHCP drivers. Dnsmasq is the simplest and requires
# no additional setup of the DHCP server.
dhcp_driver = quantum.agent.linux.dhcp.Dnsmasq
# Allow overlapping IP (Must have kernel build with CONFIG_NET_NS=y and
# iproute2 package that supports namespaces).
# use_namespaces = True
/etc/quantum/quantum.conf:
[DEFAULT]
rabbit_password = password
rabbit_host = localhost
auth_strategy = keystone
# Show more verbose log output (sets INFO log level output)
verbose = True
# Show debugging output in logs (sets DEBUG log level output)
debug = True
# Address to bind the API server
bind_host = 0.0.0.0
# Port the bind the API server to
bind_port = 9696
# Path to the extensions. Note that this can be a colon-separated list of
# paths. For example:
# api_extensions_path = extensions:/path/to/more/extensions:/even/more/extensions
# The __path__ of quantum.extensions is appended to this, so if your
# extensions are in there you don't need to specify them here
# api_extensions_path =
# Quantum plugin provider module
core_plugin = quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2
# Paste configuration file
api_paste_config = api-paste.ini
# The strategy to be used for auth.
# Supported values are 'keystone'(default), 'noauth'.
# auth_strategy = keystone
# Base MAC address. The first 3 octets will remain unchanged. If the
# 4h octet is not 00, it will also used. The others will be
# randomly generated.
# 3 octet
# base_mac = fa:16:3e:00:00:00
# 4 octet
# base_mac = fa:16:3e:4f:00:00
# Maximum amount of retries to generate a unique MAC address
# mac_generation_retries = 16
# DHCP Lease duration (in seconds)
# dhcp_lease_duration = 120
# Enable or disable bulk create/update/delete operations
# allow_bulk = True
# RPC configuration options. Defined in rpc __init__
# The messaging module to use, defaults to kombu.
# rpc_backend = quantum.openstack.common.rpc.impl_kombu
# Size of RPC thread pool
# rpc_thread_pool_size = 64,
# Size of RPC connection pool
# rpc_conn_pool_size = 30
# Seconds to wait for a response from call or multicall
# rpc_response_timeout = 60
# Seconds to wait before a cast expires (TTL). Only supported by impl_zmq.
# rpc_cast_timeout = 30
# Modules of exceptions that are permitted to be recreated
# upon receiving exception data from an rpc call.
# allowed_rpc_exception_modules = quantum.openstack.common.exception, nova.exception
# AMQP exchange to connect to if using RabbitMQ or QPID
control_exchange = quantum
# If passed, use a fake RabbitMQ provider
# fake_rabbit = False
# Configuration options if sending notifications via kombu rpc (these are
# the defaults)
# SSL version to use (valid only if SSL enabled)
# kombu_ssl_version =
# SSL key file (valid only if SSL enabled)
# kombu_ssl_keyfile =
# SSL cert file (valid only if SSL enabled)
# kombu_ssl_certfile =
# SSL certification authority file (valid only if SSL enabled)'
# kombu_ssl_ca_certs =
-----Original Message-----
From: bounces@canonical.com [mailto:bounces@canonical.com] On Behalf Of Aaron Rosen
Sent: Wednesday, August 29, 2012 1:31 PM
To: Syd (Sydney) Logan
Subject: Re: [Question #206604]: Quantum with Openvswitch and stack.sh no gateway interface
Question #206604 on quantum changed:
https://answers.launchpad.net/quantum/+question/206604
Aaron Rosen posted a new comment:
Is the dhcp agent running?
--
You received this question notification because you are a direct
subscriber of the question.
↧