You can use the basic Quantum API client CLI to validate your setup. While still running the Quantum service, run the following command from the same host to confirm that the client can communicate with Quantum service API running your plugin:
quantum create_net quantum-fake-tenant net1
This command creates a Quantum network named 'net1' for a non-existent tenant named 'quantum-fake-tenant'. The resulting output should resemble:
Created a new Virtual Network with ID: 0a649eca-3764-417c-91a7-eb51291d4bb9 for Tenant: quantum-fake-tenant
This validation confirms that the Quantum service is able to communicate with the Quantum plugin and that the Quantum plugin is able to perform basic API operations. It does not test whether the Quantum plugin is correctly communicating with your switch infrastructure. See your plugin documentation for additional validation steps.
To experiment more with basic Quantum API commands, invoke the CLI utility with no arguments to see all available commands:
list_nets <tenant-id> [filterspec ...] create_net <tenant-id> <net-name> unplug_iface <tenant-id> <net-id> <port-id> plug_iface <tenant-id> <net-id> <port-id> <iface-id> update_port <tenant-id> <net-id> <port-id> <params> show_port_detail <tenant-id> <net-id> <port-id> show_net <tenant-id> <net-id> delete_port <tenant-id> <net-id> <port-id> delete_net <tenant-id> <net-id> list_nets_detail <tenant-id> [filterspec ...] show_net_detail <tenant-id> <net-id> show_iface <tenant-id> <net-id> <port-id> update_net <tenant-id> <net-id> <new-name> show_port <tenant-id> <net-id> <port-id> list_ports_detail <tenant-id> <net-id> [filterspec ...] create_port <tenant-id> <net-id> list_ports <tenant-id> <net-id> [filterspec ...]
Invoking the CLI utility with no arguments displays additional command-line options to, for example, specify an alternate Quantum server IP address or port.
