summaryrefslogtreecommitdiff
path: root/openstackclient/tests/unit/network
Commit message (Collapse)AuthorAgeFilesLines
* Resolve PEP8Pete Zaitcev2020-06-011-1/+1
| | | | | | | | | | No idea how this happened, but reviews started failing the pep8 gate job. The failures are legitimate, see the commit. I guess the pep8 tests became smarter and found these issues. Change-Id: Id9a0dad644134dafd68eed37fe8f41c583d7a619 (cherry picked from commit 52ff421e3d339f81c2625bff429e6829a2d9af67) (cherry picked from commit 37e2c536e4e0b59ec8cb3edd165a0c76d7d8800c)
* Fix router create/show if extraroute not supportedÉdouard Thuleau2020-03-181-0/+18
| | | | | | | | If neutron does not support extraroute l3 extension, the route column formatter fails. Change-Id: I7b89c4f818865073947e0850e86c18d0d2415a51 (cherry picked from commit 509ca3ed36b4ef512a47ff8d39c9df751084015a)
* Merge "Add floating IP Port Forwarding commands"Zuul2019-09-092-0/+579
|\
| * Add floating IP Port Forwarding commandsLIU Yulong2019-08-292-0/+579
| | | | | | | | | | | | | | | | | | | | | | | | Add following commands: floating ip port forwarding create floating ip port forwarding delete floating ip port forwarding list floating ip port forwarding set floating ip port forwarding show Closes-Bug: #1811352 Change-Id: I6a5642e8acce28fc830410d4fa3180597b862761
* | Merge "Bump hacking version"Zuul2019-08-281-1/+1
|\ \ | |/ |/|
| * Bump hacking versionStephen Finucane2019-08-271-1/+1
| | | | | | | | | | | | | | | | Pick up newer versions of this library. Thankfully no serious changes are needed. Change-Id: I69e523844529fc1c8aa0c1ce764182dbe29cfeb6 Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
* | Merge "openstack port create support --extra-dhcp-option"Zuul2019-08-011-0/+42
|\ \
| * | openstack port create support --extra-dhcp-optionzhouhenglc2019-07-251-0/+42
| |/ | | | | | | | | | | | | neutron create-port API has extra_dhcp_opts parameter, this parameter can set port with special extra dhcp options. Change-Id: I199f17e95c509a33f809ac85c65f685a37acd198
* | Support IPv6 addresses betterBrian Haley2019-07-152-3/+14
|/ | | | | | | | | | | | | | | | | | | When adding a security group rule, if no IP address is given we will use '0.0.0.0/0', but if the ethertype is IPv6 we will leave it as None. Change this to be '::/0' to match what we do for IPv4 - use the "any" address. The neutron server treats them both the same when checking for duplicates. Because there are most likely entries in the DB using None for the IP, print them as '0.0.0.0/0' or '::/0' so it is more obvious what address they are actually referring to. Also change to display the Ethertype column by default instead of with --long, since easily knowing IPv4 or IPv6 is useful. Change-Id: Ic396fc23caa66b6b0034c5d30b27c6ed499de5a6 Closes-bug: #1735575
* Merge "Change default security group protocol to 'any'"Zuul2019-06-222-1/+5
|\
| * Change default security group protocol to 'any'Brian Haley2019-05-062-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The default protocol used to create a security rule was changed to ``tcp``, which was a regression from the neutron client. Change it back to ``any``, which skips sending the protocol to the API server entirely when using the Neutron v2 API. Users that had been creating rules without specifying a protocol and expecting ``tcp`` need to change to use ``--protocol tcp`` explicitly. Change-Id: Iedaa027240e00dced551513d8fa828564386b79f Closes-bug: #1716789
* | Merge "Use cliff formattable columns in network commands"Zuul2019-06-229-240/+242
|\ \
| * | Use cliff formattable columns in network commandsAkihiro Motoki2019-05-099-240/+242
| |/ | | | | | | | | | | | | | | | | | | | | Use cliff formattable columns not to convert complex fields into a string when a machine readable format like JSON or YAML is requested. Partial-Bug: #1687955 Partially implement blueprint osc-formattable-columns Change-Id: I9878f327e39f56852cc0fb6e4eee9105b7141da9
* | Remove deprecated network optionsSean McGinnis2019-05-193-148/+13
|/ | | | | | | | | | | | | | | | The following were deprecated for several releases and can now be removed: * Remove ``port create|set`` options ``--device-id`` and ``--port-id`` * Remove ``router set`` option ``--clear-routes`` * Remove ``security group rule create`` options ``--src-group`` and ``--src-ip`` These are backwards incompatible changes and will require a major version bump after they are merged. Change-Id: Ieae74c14f6b3e263721a3146cf76f94a9ab792f6 Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com> Signed-off-by: Dean Troyer <dtroyer@gmail.com>
* Ignore case in security group rule --ethertypeJim Rollenhagen2019-04-011-0/+24
| | | | | | | | | Currently, this only allows 'IPv4' or 'IPv6', but one can imagine a user frequently typing e.g. 'ipv6' and getting frustrated. Allow any case, while still keeping correct case for the choices and the value sent to Neutron. Change-Id: I70ce1f43d32aad01b174437d03c984a5b608b161
* Fix: incorrect check when no shared/private inputKailun Qin2019-03-141-0/+49
| | | | | | | | | | | When neither of "--shared" and "--private" is input, we should not allow to specify "--project". Defaulting the created network segment range to shared is expected. Therefore, "project_id" attr should only be populated on a private range creation. Change-Id: Iab345e1651dd8b7904ff64a20633f194d719bb84 Story: 2005206 Task: 29980
* Fix: set invalid None project_id on range creationKailun Qin2019-03-131-6/+36
| | | | | | | | | | "project_id" attribute should not be set to None on shared network segment range creation since it is not a valid string type which is required for the API. Change-Id: Ia2bab12e39b4bb7e05ff2acfffb851252c100651 Story: 2005205 Task: 29975
* Merge "Add 'security_group' type support to network rbac commands"Zuul2019-03-112-0/+73
|\
| * Add 'security_group' type support to network rbac commandsDoug Wiegley2019-03-052-0/+73
| | | | | | | | | | | | Partial-Bug: #1817119 Depends-On: https://review.openstack.org/635311 Change-Id: I5f132fa54714514d8dae62df8bc494f3f6476768
* | Merge "Add network segment range command object"3.18.0Zuul2019-03-082-0/+612
|\ \
| * | Add network segment range command objectKailun Qin2019-03-072-0/+612
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add network segment range command object in support of network segment range management. This patch set includes documentation, unit tests and functional tests (currently skipped unit network segment range enabled in Neutron by default) for the following new commands: - "os network segment range create" - "os network segment range delete" - "os network segment range list" - "os network segment range set" - "os network segment range show" Co-authored-by: Allain Legacy <Allain.legacy@windriver.com> [depends on removed by dtroyer as those are all +W and trying to pass the gate, OSC has it's freeze dealine looming] Depends: https://review.openstack.org/624708 Depends: https://review.openstack.org/624709 Depends: https://review.openstack.org/638386 Partially-implements: blueprint network-segment-range-management Change-Id: I335692f2db5be07c1c164f09b13f1abb80b7ba33
* | | Merge "Add support for get details of Quota"Zuul2019-03-071-0/+23
|\ \ \ | |_|/ |/| |
| * | Add support for get details of QuotaSławek Kapłoński2019-02-241-0/+23
| |/ | | | | | | | | | | | | | | | | | | With passing "--detail" argument to "openstack quota list", details about current usage should be returned. It is currently supported by Nova and Neutron so details of resources from those projects can be returned. Change-Id: I48fda15b34283bb7c66ea18ed28262f48b9229fe Related-Bug: #1716043
* | Merge "Partially Revert "Add command to unset information from Subnet-pools""Zuul2019-02-271-34/+1
|\ \ | |/ |/|
| * Partially Revert "Add command to unset information from Subnet-pools"Bernard Cafarelli2018-09-051-34/+1
| | | | | | | | | | | | | | | | | | | | | | We do not support removing a prefix from a subnet pool, only updating with a larger prefix (which is handled by the set command) This reverts commit 063c722a110031883e9615064092644de6df8da2. Change-Id: I11224fbdb94dc1caef42a8a64cbcebaf1dc542fe Story: #1670230 Task: #13697
* | Add floating IP filter to floating IP list commandJohannes Kulik2019-01-141-0/+17
| | | | | | | | | | | | | | | | | | | | Add a parameter ``--floating-ip-address`` to ``floating ip list`` because it's supported by the API and also more efficient than the current ``floating ip show``. This also works as a work-around for pagination issues ``floating ip show`` might run into with an IP parameter. Change-Id: I113e3fa2495e1e86bb553c55c44f71a3f9f49d23
* | Merge "Support enable/disable uplink status propagation"Zuul2018-12-242-0/+42
|\ \
| * | Support enable/disable uplink status propagationHongbin Lu2018-12-052-0/+42
| |/ | | | | | | | | | | | | | | | | | | | | | | | | Add options to enable/disable uplink status propagation on creating a neutron port. Related patches: * neutron: https://review.openstack.org/#/c/571899/ * openstacksdk: https://review.openstack.org/#/c/586687/ Depends-On: https://review.openstack.org/#/c/586687/ Change-Id: I095a98fc5f5aee62d979a16b3cd79d91ec3b9ddb Related-Bug: #1722720
* | Merge "Supports router gateway IP QoS"Zuul2018-12-121-1/+155
|\ \
| * | Supports router gateway IP QoSLIU Yulong2018-12-101-1/+155
| |/ | | | | | | | | | | | | | | | | | | | | | | | | Adds --qos-policy and --no-qos-policy to `openstack router set`: --qos-policy <qos-policy> Attach QoS policy to router gateway IPs --no-qos-policy Remove QoS policy from router gateway IPs Adds --qos-policy to `openstack router unset`: --qos-policy Remove QoS policy from router gateway IPs Partially-Implements blueprint: router-gateway-ip-qos Closes-Bug: #1757044 Change-Id: Ifec3b2cf9bdb59513c8bcd7bd60305506a071192
* | Merge "Don't display router's is_ha and is_distributed attributes always"Zuul2018-12-101-2/+41
|\ \ | |/ |/|
| * Don't display router's is_ha and is_distributed attributes alwaysSławek Kapłoński2018-05-251-2/+41
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In case when is_ha or is_distributed attribute of Neutron's router is set to None, it means that it wasn't returned from server and should not be displayed. Otherwise it might be confusing for user is making openstack router show <router_name> call as an admin will return e.g. is_ha=True but same call done as regular user will return False or None. It might happen like that because returning of those attributes is forbidden for regular users in Neutron's policy.json Depends-On: https://review.openstack.org/567606/ Change-Id: I626b5193d9ecb308baad7b27939f9673c32b4182 Closes-Bug: #1689510 Task: 19789 Story: 2002110
* | Merge "Add DNS support to floating IP commands"Zuul2018-08-081-0/+12
|\ \
| * | Add DNS support to floating IP commandsJens Harbott2018-08-061-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add the DNS domain and name options to the ``floating ip create`` command. Also add these two columns to the output of the ``floating ip list --long`` command. Change-Id: Id4cb18b51b252f19b87b24ec5d77183771189d17 Story: 1547736 Task: 13114
* | | Merge "Add dns-domain support to Network object"Zuul2018-08-072-0/+13
|\ \ \ | |/ /
| * | Add dns-domain support to Network objectPierre Hanselmann2018-04-232-0/+13
| |/ | | | | | | | | | | | | | | | | | | | | Add "dns-domain" parameter to Network class. Also check backend extensions and send an error message in case of an argument (like dns-domain) is sent and the extension is missing (dns-integration in this case). Change-Id: I7303658c27d9b9f2d8381ccea0b29e96909cab54 Closes-Bug: 1633214 Partial-Bug: 1547736
* | Merge "Support filtering port with IP address substring"Zuul2018-07-251-0/+18
|\ \
| * | Support filtering port with IP address substringHongbin Lu2018-06-291-0/+18
| | | | | | | | | | | | | | | Change-Id: I9559f1c0a6db943705bd32aefb60d7ea7054dd1b Related-Bug: #1718605
* | | Merge "Do not require port argument when updating floating IP"Zuul2018-07-241-6/+51
|\ \ \ | |/ / |/| |
| * | Do not require port argument when updating floating IPyanpuqing2018-06-131-6/+51
| |/ | | | | | | | | | | | | | | | | | | | | When setting floating ip other properties, port argument is force to use. The patch modifies the command, when setting floating ip other properties, like tags, no need port argument. Change-Id: I908712c8913f32d3dd5fdfefe7347277d72f66de Story: 1751431 Task: 13865
* | Merge "Network: Add tag support for security group"Zuul2018-06-252-4/+171
|\ \
| * | Network: Add tag support for security groupDongcan Ye2018-06-142-4/+171
| | | | | | | | | | | | | | | Change-Id: Icccb23429913724c6a8bd15d4737672b47a5f13a Closes-Bug: #1750983
* | | Fix subnet host_routes errorHuang Cheng2018-06-141-0/+30
| | | | | | | | | | | | | | | | | | | | | When updating subnet with "no-host-route" option, set host_routes to an empty list as neutron_lib.api.validators expected. Change-Id: I6fe039793d813758429c7a104fd40172b4f8122b Closes-Bug: #1747101
* | | Allow setting network-segment on subnet updateHarald Jensas2018-06-061-0/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | To enable the possibility to migrate a non-routed network to a routed network allow updating the segment_id of a subnet. Change-Id: I3ebae2ff28d5d4e5373ebd1f52194f8c52071b88 Partial-Bug: bug/1692490 Depends-On: I1aee29dfb59e9769ec0f1cb1f5d2933bc5dc0dc5
* | | Make max_burst_kbps option as optional for bw limit QoS ruleSławek Kapłoński2018-05-251-6/+49
| |/ |/| | | | | | | | | | | | | | | | | Attribute max_burst_kbps of QoS bandwidth limit rule in Neutron's is optional in API so it should be also optional on client's side. Change-Id: Ie085b73fa885ff12f9ac080666cf3ca6a09b632a Related-Bug:#1770622 Task: 19658 Story: 2002017
* | Merge "Network: Add tag support for floating ip"Zuul2018-04-232-3/+134
|\ \
| * | Network: Add tag support for floating ipDongcan Ye2018-04-172-3/+134
| |/ | | | | | | | | Change-Id: I7a500a4ff6cec2442b4050df26c0b017d9f71903 Closes-Bug: #1750985
* | Merge "neutron: add --mtu for create/set network"Zuul2018-03-232-0/+10
|\ \
| * | neutron: add --mtu for create/set networkEmilien Macchi2018-03-152-0/+10
| | | | | | | | | | | | | | | | | | | | | Support Neutron network mtu configuration with a new argument, --mtu that allows CLI users to set MTU for Neutron networks. Change-Id: I93d23581c7e8c84eaf9bb3b293360036f60f456b
* | | Merge "Remove duplicated network attributes"Zuul2018-03-231-1/+0
|\ \ \ | |/ / |/| |
View Lorry Controller Status