Jason Zhang 20c5e4e193 Moved the configuration variables.
Moved the configuration variables from dhcp agent
to linux interface so l3-agent works with
Metadriver.

Also removed the unnecessary configuration variables
from quantum debug agent because of the above
modification.

Fixes: bug #1138757

Change-Id: Ib23fee18a08ef1c531feb05d98c9a76f5385a4ff
2013-03-05 18:50:52 -08:00
..
2013-01-22 11:42:15 +08:00
2013-02-17 17:33:05 +00:00

Debug Helper Script for Quantum

- Configure
export QUANTUM_TEST_CONFIG_FILE=/etc/quantum/debug.ini
or
export QUANTUM_TEST_CONFIG_FILE=/etc/quantum/l3_agent.ini

you can also specify config file by --config-file option

- Usage
quantum-debug commands

probe-create <net-id>
  Create probe port - create port and interface, then plug it in.
  This commands returns a port id of a probe port. A probe port is a port which is used to test.
  The port id is probe id.
  We can have multiple probe probes in a network, in order to check connectivity between ports.

  quantum-debug probe-exec probe_id_1 'nc -l 192.168.100.3 22'
  quantum-debug probe-exec probe_id_2 'nc -vz 192.168.100.4 22'

  Note: You should use a user and a tenant who has permission to
   modify network and subnet if you want to probe. For example, you need to be admin user if you
   want to probe external network.

probe-delete <port-id>  Delete probe - delete port then uplug
probe-exec <port-id> 'command'    Exec commands on the namespace of the probe
`probe-exec <port-id>` 'interactive command' Exec interactive command (eg, ssh)

probe-list     List probes
probe-clear    Clear All probes

ping-all --id <network_id> --timeout 1 (optional)
         ping-all is all-in-one command to ping all fixed ip's in all network or a specified network.
         In the command probe is automatically created if needed.

quantum-debug extends the shell of quantumclient,  so you can use all the commands of quantum