The lastest quantumclient 2.2 (or 2.1.2) support known options after positional parameters, so the bug reported has been addressed. The lastest quantumclient can be used combined with Folsom Quantum.
I confirmed it works.
$ quantum subnet-create net2 10.2.2.0/24 --ip-version 4 --gateway 10.2.2.200 Created a new subnet: +------------------+----------------------------------------------+ | Field | Value | +------------------+----------------------------------------------+ | allocation_pools | {"start": "10.2.2.1", "end": "10.2.2.199"} | | | {"start": "10.2.2.201", "end": "10.2.2.254"} | | cidr | 10.2.2.0/24 | | dns_nameservers | | | enable_dhcp | True | | gateway_ip | 10.2.2.200 | | host_routes | | | id | c68dda9b-75cb-4f5f-a8de-b63d9027bf7e | | ip_version | 4 | | name | | | network_id | 6e71cffa-d120-4f00-bbb7-cbd26bd1ccff | | tenant_id | 5d3f1dd8a3cd4ed9a06dda8d759ef2e0 | +------------------+----------------------------------------------+
The lastest quantumclient 2.2 (or 2.1.2) support known options after positional parameters, so the bug reported has been addressed. The lastest quantumclient can be used combined with Folsom Quantum.
I confirmed it works.
$ quantum subnet-create net2 10.2.2.0/24 --ip-version 4 --gateway 10.2.2.200 ------- -----+- ------- ------- ------- ------- ------- ------- ---+ ------- -----+- ------- ------- ------- ------- ------- ------- ---+ 75cb-4f5f- a8de-b63d9027bf 7e | d120-4f00- bbb7-cbd26bd1cc ff | 9a06dda8d759ef2 e0 | ------- -----+- ------- ------- ------- ------- ------- ------- ---+
Created a new subnet:
+------
| Field | Value |
+------
| allocation_pools | {"start": "10.2.2.1", "end": "10.2.2.199"} |
| | {"start": "10.2.2.201", "end": "10.2.2.254"} |
| cidr | 10.2.2.0/24 |
| dns_nameservers | |
| enable_dhcp | True |
| gateway_ip | 10.2.2.200 |
| host_routes | |
| id | c68dda9b-
| ip_version | 4 |
| name | |
| network_id | 6e71cffa-
| tenant_id | 5d3f1dd8a3cd4ed
+------