tempest

network client implementation is not standard

Bug #1288326 reported by Evgeny Fedoruk
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tempest
Fix Released
Wishlist
Ken'ichi Ohmichi

Bug Description

Network REST client implementation (NetworkClientBase) does not fit common approach where each resource has it's own client inheriting from common.rest_client.RestClient.

The issue causing code duplication in change https://review.openstack.org/#/c/74121/
(see wait_for_resource_deletion and is_resource_deleted functions)
Separate clients should be implemented for network resources and should inherit from common RestClient like in other projects.

When done, duplicated wait_for_resource_deletion and is_resource_deleted functions should be gone.

See original description
Tags: neutron
Evgeny Fedoruk (evgenyf)
tags: added: network
removed: neutron
tags: added: neutron
removed: network
description: updated
Mauro S M Rodrigues (maurorodrigues)
Changed in tempest:
status: New → Confirmed
importance: Undecided → Wishlist
Revision history for this message
Ken'ichi Ohmichi (oomichi) wrote :

The neutron service clients are already implemented as standard/stable interfaces.
And these interfaces are changed to common way like the other service clients.
So this bug has been solved now.

Changed in tempest:
status: Confirmed → Fix Released
assignee: nobody → Ken'ichi Ohmichi (oomichi)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.