summaryrefslogtreecommitdiff
path: root/openstackclient/tests/functional/network
Commit message (Collapse)AuthorAgeFilesLines
* Add support for CRUD operations for QoS minimum packet rate rulePrzemyslaw Szczerbik2022-07-011-0/+67
| | | | | | | Closes-Bug: #1922237 Depends-On: https://review.opendev.org/c/openstack/openstacksdk/+/810364 See-Also: https://review.opendev.org/785236 Change-Id: Ie7e1eb0575fd37121d5097ecbc318d0769ab3db0
* Support Neutron Local IP CRUDNurmatov Mamatisa2022-01-281-0/+161
| | | | | | | | | Add support for Neutron Local IP CRUD operations. Partial-Bug: #1930200 Depends-On: https://review.opendev.org/c/openstack/neutron/+/804523 Depends-On: https://review.opendev.org/c/openstack/openstacksdk/+/804988 Change-Id: I1095100efb27b8559412469f0a9d07fc0a3db9d5
* Merge "Make functional Neutron tests running fine on ML2/OVN environments"Zuul2021-06-294-13/+45
|\
| * Make functional Neutron tests running fine on ML2/OVN environmentsSlawek Kaplonski2021-05-274-13/+45
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Devstack recently switched default Neutron's backend from ML2/OVS to ML2/OVN. As OVN backend has some parity gaps and differences in some APIs, functional tests job was failing with ML2/OVN as some tests weren't properly skipped in case of missing some Neutron API extensions. This patch fixes that by doing some small changes in the functional tests: - skip DHCP/L3 agent tests when dhcp/l3 agent scheduler extensions aren't available, - skip updating neutron agent as OVN agents don't allows that, - skip service providers tests when there is no Neutron L3 agent available, - skip setting router as distributed as OVN backend don't supports that router's attribute at all. Depends-On: https://review.opendev.org/c/openstack/neutron/+/793141 Change-Id: I29a8db202086b0b49fed865409fa8ca244b98439
* | Add support for Neutron's L3 conntrack helper resourceSlawek Kaplonski2021-06-071-0/+145
|/ | | | | | | | | | | | | | Neutron has got CRUD API for L3 conntrack helper since some time. This patch adds support for it in the OSC. OpenStack SDK supports that since [1] This patch also bumps minimum OpenStack SDK version to the 0.56.0 as that version introduced support for the Neutron's L3 conntrack helper. [1] https://review.opendev.org/c/openstack/openstacksdk/+/782870 Change-Id: I55604182ae50b6ad70c8bc1f7efad8859f191269
* Support Neutron Address Group CRUDHang Yang2020-12-241-0/+177
| | | | | | | | | | Add support for Neutron address group CRUD operations. Subsequent patches will be added to use address groups in security group rules. Change-Id: I3c313fc9329837dde67815901528a34dca98ebcc Implements: blueprint address-groups-in-sg-rules Depends-On: https://review.opendev.org/738274 Depends-On: https://review.opendev.org/745594
* Merge "Support for stateless security groups"Zuul2020-04-081-1/+3
|\
| * Support for stateless security groupsTom Stappaerts2020-03-311-1/+3
| | | | | | | | | | | | | | | | | | | | | | Add support for stateful attribute of security groups, using --stateful and --no-stateful flag on security group. This allows a user to create security groups with stateful false. Change-Id: Ifd20b5fc47fd0ea0bb5aeda84820dcc0fb1e8847 Blueprint: stateless-security-groups Depends-On: https://review.opendev.org/711513/
* | Add command: router add/remove route --routeBence Romsics2020-03-301-0/+43
|/ | | | | | | | | | | | | | | | | | | Add commands to osc to call the two new API methods introduced by new Neutron extension: extraroute-atomic. Bump our openstacksdk requirement to >=0.38.0 which contains the corresponding sdk change. The lower-constraints of dogpile.cache and keystoneauth1 are bumped because of requirements bumps in openstacksdk. The lower-constraint of decorator is bumped because of problem already fixed by amotoki here: https://review.opendev.org/701706 Change-Id: Ia9b9c216f1d1161ebedac31594a2c464d77f4ae2 Depends-On: https://review.opendev.org/674324 Partial-Bug: #1826396 (rfe) Related-Change: https://review.opendev.org/655680 (spec)
* Remove races in floating ip functional testsDean Troyer2019-08-311-53/+67
| | | | | | | | Multiple subnets with the same name are occasionally created when running tests in parallel. Change-Id: Ifb85e39ee53b529e2b97abf782c7fba93d48e9e2 Signed-off-by: Dean Troyer <dtroyer@gmail.com>
* Merge "Use cliff formattable columns in network commands"Zuul2019-06-227-53/+38
|\
| * Use cliff formattable columns in network commandsAkihiro Motoki2019-05-097-53/+38
| | | | | | | | | | | | | | | | | | | | | | 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
* | Batch up minor cleanups for releaseDean Troyer2019-05-202-3/+3
|/ | | | | Change-Id: Id45788e17c5388cee54e79cab1c120cfcc8f9f62 Signed-off-by: Dean Troyer <dtroyer@gmail.com>
* Tweak network segment range fiunction testsDean Troyer2019-04-121-8/+8
| | | | | | | | | We seem to be having occasional overlaps in the ranges, as they were identical in all tests, change each test to not overlap the others so running in parallel is not racy. Change-Id: I7ea467a3aa2e4a4b4a334c10ea6ba21409c46af0 Signed-off-by: Dean Troyer <dtroyer@gmail.com>
* Fix service discovery in functional testsGlenn Van de Water2019-03-132-8/+8
| | | | | | | | | | | | | | | | | | | | | If a required service is not enabled then we skip the test. The discovery is done by tests/functional/base.py:is_service_enabled but this method is broken, credentials are not passed to the 'openstack service show' command so every call will fail and every test that relies on it will be skipped. This commit fixed that method and the issues that popped up when re-enabling tests. Network segment range: - issue where we assumed network-segment-range extension is always present - issue where we compare integers and string representations of numbers Subnet: - issue where we try to deepcopy an uncopyable object in UnsetSubnet Change-Id: Id3cc907c1ed2a25b49cf6f4a7233e0401a02383a Story: 2005169 Task: 29908
* Add network segment range command objectKailun Qin2019-03-071-0/+145
| | | | | | | | | | | | | | | | | | | | | | | | | 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
* Replace assertEqual(True/False, expr) with assertTrue/assertFalseliuyamin2018-11-146-131/+38
| | | | | | | In some cases, If the result of expr is a boolen value, we shoud use assertTrue/assertFalse to instead. Because it is clear and simple. Change-Id: I53b345fc3915a7b0e737e9dd4d58fe09c746d61c
* Make max_burst_kbps option as optional for bw limit QoS ruleSławek Kapłoński2018-05-251-1/+0
| | | | | | | | | | 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
* Fix functional job failedDongcan Ye2018-04-201-3/+14
| | | | | | | | | | After Neutron patch I3c93818002c2d7753454547231ba08544b6fa1c0 merged, the default value of segment description is an empty string. This patch will determine whether the Neuron shim extension standard-attr-segment supported. Change-Id: I68a3c018f03e5bb53bd637844ac9d7742a765db0
* Clean up W503 and E402 pep8 errorsSean McGinnis2018-04-155-195/+170
| | | | | | | | | | | | pycodestyle 2.40 and later enforce these rules that were not previously enforced. Rather than just skipping them, this cleans up the trivial instances of these violations. This does also include some other updates that were not triggering errors in an attempt to keep some of the style consistent. Change-Id: Id7c0a6b8f1f835e69d844b000e3ed751852ada63 Closes-bug: #1762803
* Allow port list to shown undefined attributesAkihiro Motoki2017-11-241-0/+10
| | | | | | | | | | | | | | | | | At now, OSC command implementation extracts resource attributes based on a predefined column list, so if a user specifies an unknown attribute not defined in the column lists, such attribute will be ignored. In case of 'port list', the neutron port defines many attributes and it is not a good idea to show all attributes even in the long mode from the perspective of user experience. This commit consumes osc_lib.utils.calculate_headers_and_attrs() function to show undefined port attributes if requested in -c option. Closes-Bug: #1707848 Depends-On: I6c6bc3c6e3c769c96869fd76b9d9c1661280850e Change-Id: I130a6aed41d80603698b6cab0c9a1d1dc59df743
* Display Network QoS rule type detailsSławek Kapłoński2017-11-051-0/+7
| | | | | | | | | | Neutron API now supports getting details of supported QoS rule type. This patch adds support for this feature to OpenStack client. Change-Id: I74d16563ce2236a7c899f5994f1dab43ace02138 Depends-On: I448b5d4f8e4ef42eafe50d9d6c63d0be666f98fc Related-Bug: #1686035
* Attempt to de-race qos policyDean Troyer2017-10-181-3/+7
| | | | | | | | | We're getting about 1-in-6 failures on qos policy delete now, with the message that the policy is in use by a network. It shouldn't be, this is possibly due to the small window where the policy is set as the default. Let's remove that and shore up the test using --share instead. Change-Id: I8d669bd3c5c88dadd2927aee89e5ef72cf4001c4
* Unroll the network qos policy functional testsDean Troyer2017-09-171-33/+42
| | | | | | | These seem to have gotten a bit racy in the last revision, just do it the long way now. Change-Id: I3748b8b4f264dbfa8c991b32653682e5c86eeb4c
* Attempt to work around chronically failing server issues with aggregates and qosDean Troyer2017-09-151-2/+5
| | | | | | | | So yeah, this is not kosher for functional tests, but we're testing the client interaction, not the raciness of Nova or Neutron. Failure to delete is not our problem. Change-Id: I21043f1de0fbacee1aec63110fb12a7cff42e0a0
* Convert remaining network functional tests to JSONAkihiro Motoki2017-08-232-55/+39
| | | | Change-Id: Ib7dff5506cc69549b5b1fbb8bf6e649468563dd6
* Convert network qos functional tests to JSONAkihiro Motoki2017-08-233-233/+193
| | | | Change-Id: Ie5cde2f927ec6abb6334ea01adfb06749384ed01
* Convert network security group functional tests to JSONAkihiro Motoki2017-08-232-106/+52
| | | | Change-Id: Icb63aa0dfbce9016fb824f97915a660cf130d120
* Convert network segment functional tests to JSONDean Troyer2017-08-131-45/+99
| | | | Change-Id: I8dc1e992d54c63c93bbe2bdd7acba61a7a6773d0
* network functest: Remove condition for segment testAkihiro Motoki2017-07-271-84/+48
| | | | | | | | | | | | | | | Previously fucntional tests for network segment feature are skipped as neutron 'segment' API extension was disabled in the gate. We now enable neutron 'segment' API extension, so we can safely drop the check for the segment extension from the test code. Also setup code in test_network_segment is moved from setUpClass to setUp. There is no good reason to do them in setUpClass and having them in setUp simplifies the test code. no user once this commit is applied. Change-Id: I183310b94d9b6d7f4311a3859b59dc22d36440db
* Network tag supportAkihiro Motoki2017-07-236-5/+115
| | | | | | | | | | | | | Neutron tag mechanism now supports network, subnet, port, subnetpool and router. Tag support for more resources is planned. This commit introduces a common mixin class to implement tag operation and individual resource consumes it. To support tag remove, network unset command is added. Implements blueprint neutron-client-tag Change-Id: Iad59d052f46896d27d73c22d6d4bb3df889f2352
* Clean up the changes of os.environ in functional testsRui Chen2017-07-2013-118/+157
| | | | | | | | | | | | Use fixtures to restore the API version changes of os.environ in each functional tests, aims to avoid the following test cases failing in unexpected context. And make sure setUpClass/tearDownClass call super class's corresponding methods first. Change-Id: Ie248fe9d3a9e25f1b076c9f2c363200f29a83817 Closes-Bug: #1696080
* Merge "Network L3 Router Commands for OSC"Jenkins2017-07-202-0/+70
|\
| * Network L3 Router Commands for OSCAnkur Gupta2017-07-112-0/+70
| | | | | | | | | | | | | | Implements: blueprint network-l3-commands Co-Authored-By: Akihiro Motoki <amotoki@gmail.com> Change-Id: Ia24d76227e164062e89a74c1621b8acb830b26cf
* | Fix dynamic names in network functional testsDean Troyer2017-07-1911-25/+36
|/ | | | | | | | Move all of the dynamic resource naming in Network functional tests into setUpClass() methods (if they exist) rather than assigning those names at load-time. Change-Id: Ic550ff7d40c2b3ca5128cacccbe331790d6ae340
* Add new parameter "is_default" to Network QoS policy.Rodolfo Alonso Hernandez2017-07-051-0/+13
| | | | | | | | | | | | Add a set of exclusive parameters to the Network QoS policy: --default: makes this policy the default policy for the project to which the qos policy belongs. --no-default: unset the property. Closes-Bug: #1639220 Depends-On: If5ff2b00fa828f93aa089e275ddbd1ff542b79d4 Depends-On: Ibe7b7881cb190bfd5582f35b6de51a8bc21135de Change-Id: I0269b837dc29bbd8ee2089d847cadb72d800fa30
* Add direction field to QoS bandwidth limit.Rodolfo Alonso Hernandez2017-06-221-7/+9
| | | | | | | | | | This patch enables the direction ('ingress'/'egress') field on the QoS bandwidth limit rule object and CRUD commands. Closes-Bug: #1614121 Depends-On: Ia13568879c2b6f80fb190ccafe7e19ca05b0c6a8 Depends-On: I90c412a5c8757b3ffe8abfc1165a70bdb8744702 Change-Id: Ic6981474f22efbf294ac11c2e0304b04494a1bbe
* Add default-quota to subnet pool commandsReedip2017-06-121-4/+35
| | | | | | | | | | | | | | Add --default-quota option to subnet pool create and set commands. Setting default-quota back to None may break the current Neutron behavior, therefore support for Unset command is not provided in this patch. Neutron API: https://github.com/openstack/neutron/blob/a0e0e8b6686b847a4963a6aa6a3224b5768544e6/neutron/api/v2/attributes.py#L239 Closes-Bug: #1667294 Change-Id: Ia4e7c23a49e91a090133c729353cdb8e62bc5674
* Trivial fix typosVu Cong Tuan2017-05-302-2/+2
| | | | Change-Id: I72a1da209df38e226ec02d9dbd0142ed4020c0d2
* Rework floating ip functional testsDean Troyer2017-05-101-140/+178
| | | | | | | Regualr expresstions were an interesting diversion, get rid of them from the functional tests. It did lead to better structure... Change-Id: I1ff32ad7715ebd88401925ce3f6c412a66e82566
* Nova net functional tests round 3Dean Troyer2017-04-2814-161/+320
| | | | | | | | | | | | | | | | | | | | * network segment * network service * port * router * security group * security group rule * subnet * subnet pool * extension The extension tests were duplicated to have both compute and network extensions tests so the nova-net case will still exercise the extension commands. Also clean up formatting from previous reviews to make the Network functional tests look and act consistently. Change-Id: I286c40572faa31ddcef595cec740da933b2defc1
* Merge "Fix Nova-net netowrk commands"Jenkins2017-04-281-94/+222
|\
| * Fix Nova-net netowrk commandsDean Troyer2017-04-271-94/+222
| | | | | | | | | | | | | | | | | | | | | | | | In cleaning up functional tests for nova-net, I discovered some problems in network create: * --subnet option is required in network create command * Switch API to use /os-networks rather than /os-tenant-networks as this is what we were actually using via novaclient * Fix functional tests for nova-net * Normalize some private function names in network/v2/network.py Change-Id: I426b864406756d58d140575a3a45ee9aee67ce84
* | Nova net functional tests round 2Dean Troyer2017-04-286-106/+180
| | | | | | | | | | | | | | | | | | | | | | * floating ip * ip availability * network qos policy * network qos rule * network qos rule type * network rbac Change-Id: Id3946bdff43bfef3a1d879c058bde4792bd299c6
* | Nova net functional tests round 1Dean Troyer2017-04-287-136/+286
|/ | | | | | | | | | | | | | | | * address scope * network agent * network flavor * network flavor profile * network meter * network meter rule Also create a new common network functional test class NetworkTests to house the setting of haz_network in a single place. The individual test skipping stays in the final classes to re-enforce the idea that some tests work with both Nova-net and Neutron. Change-Id: Ie3910231c6fc9e2031438c599afa904f43c874a7
* Functional test for subnet_pooljiahui.qiang2017-04-261-37/+268
| | | | | | Refactor functional tests for testing more command options. Change-Id: I0c9c3b04dd2b79766a8fe82cbc5315c030f4784d
* Fix network list functional testHuanxuan Ao2017-04-191-1/+1
| | | | | | | | An error in network func test broke our CI, looks like the "is_default" should be "False" by default for now. Change-Id: I021eb8abd9bdf55c7c06031152c107312f104b34
* "floating ip set/unset port" for OSCSindhu Devale2017-04-051-0/+76
| | | | | | | | | | | | | | | | | | | | | | | Implements Neutron feature of floating ip associate/disassociate into OpenStack Client. Previously, network.find_ip() function only supported to search floating ip by UUID. Hence, _find_floating_ip() function is used in floating_ip.py, to search fip both by UUID and ip_address. [1] adds the ability to find fip object using both UUID and ip_address. This functionality however, won't be available until the SDK is released. Hence, we continue to use _find_floating_ip() method, which was cleaned up by [2] to remove the use of ip_cache. Once, the SDK is released, we will remove all the usage of _find_floating_ip() method and instead only use network.find_ip(). [1] https://review.openstack.org/#/c/449879/2 [2] https://review.openstack.org/#/c/447938/ Change-Id: I6c5222287c46ca42365917d2deae70bdb626347 Co-Authored-By: Reedip<reedip.banerjee@nectechnologies.in> Co-Authored-By: RuiChen<chenrui.momo@gmail.com> Closes-Bug: #1560297
* Introduce neutron flavor associate, disassociate to OSCShashank Kumar Shankar2017-04-031-0/+51
| | | | | | | | | | This patch introduces network flavor associate and disassociate to OSC. The following neutron equivalent commands are implemented in OSC: - neutron flavor-associate - neutron flavor-disassociate Change-Id: Icba4dbf7300a36353142586359059cd6784049dc
* Merge "Simplify logic around option lists in port set"Jenkins2017-03-271-8/+75
|\