Migrate the Scenario Tests to the Tempest Clients

Registered by Matthew Treinish

Move to the tempest clients in the scenario tests

Blueprint information

Status:
Complete
Approver:
Matthew Treinish
Priority:
High
Drafter:
Matthew Treinish
Direction:
Approved
Assignee:
Masayuki Igawa
Definition:
Approved
Series goal:
Accepted for juno
Implementation:
Implemented
Milestone target:
milestone icon juno-rc
Started by
Matthew Treinish
Completed by
Masayuki Igawa

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:scenario,n,z

Addressed by: https://review.openstack.org/106738
    move scenario tests to tempest client

Gerrit topic: https://review.openstack.org/#q,topic:bp/tempest-client-scenarios,n,z

Addressed by: https://review.openstack.org/107552
    Add os-networks JSON client for tempest

Addressed by: https://review.openstack.org/107369
    Base class for scenario test using Tempest clients

Addressed by: https://review.openstack.org/107722
    Migrate swift scenario test to tempest client

Addressed by: https://review.openstack.org/107562
    Migrate test_minimun_basic to tempest client

Addressed by: https://review.openstack.org/107659
    Migrate test_dashboard_basic_ops to tempest clients

Addressed by: https://review.openstack.org/107428
    Migrate test_aggregates_basic_ops to Tempest clients

Addressed by: https://review.openstack.org/108902
    Migrate test_server_basic_ops to tempest client

Addressed by: https://review.openstack.org/108906
    Migrate test_server_advanced_ops to tempest client

yfried:
I'm not sure if that's the best place to discuss this effort, so I'm coping a review I did. let me know if this should go somewhere else:
It seems like this client change is giving up some of the long-time developed (if not perfect) generic methods of scenarios. one example is the status_timeout. another, is the replacement of resource.get() and resource.delete().
Is this intentional/WIP/oversight?
Also - should we use nova-network api (nova network client) when neutron is available?
-> discussion in https://etherpad.openstack.org/p/tempest-client-scenarios

Addressed by: https://review.openstack.org/110426
    Migrate test_snapshot_pattern to tempest client

stevebaker: I wonder if it is not worth doing this for the orchestration scenario tests. I've started the work to make the orchestration scenario tests be the first in-tree heat functional tests, so these tests may be deleted from tempest "soon"

Addressed by: https://review.openstack.org/110626
    Move new manager code to a new module

Addressed by: https://review.openstack.org/111718
    Enhance Tempset network_client for scenario support

Addressed by: https://review.openstack.org/111719
    Migrate test_network_basic_ops to tempest clients

Addressed by: https://review.openstack.org/111905
    Migrate test_encrypted_cinder_volumes to tempest client

Addressed by: https://review.openstack.org/112115
    Add MatchesDictExceptForKeys custom matcher

Addressed by: https://review.openstack.org/112199
    Migrate security_groups_basic to tempest clients

Addressed by: https://review.openstack.org/112535
    Migrate test_volume_boot_pattern to tempest client

Gerrit topic: https://review.openstack.org/#q,topic:bp/tempest-client-scenarios-patch12,n,z

Addressed by: https://review.openstack.org/113124
    Migrate advanced server network to tempest clients

Addressed by: https://review.openstack.org/102700
    Adds status check for FloatingIP in scenarios

Addressed by: https://review.openstack.org/113807
    Migrate test_large_ops to tempest client

Addressed by: https://review.openstack.org/117673
    Migrate baremetal_basic_ops to tempest clients

Addressed by: https://review.openstack.org/117713
    Fix response body format of orchestration_client to dict

Addressed by: https://review.openstack.org/117714
    Migrate test_server_cfn_init to tempest clients

Addressed by: https://review.openstack.org/118232
    Migrate test_load_balancer_basic to tempest client

Addressed by: https://review.openstack.org/113707
    Fix load balancer scenario if no tenant network

Addressed by: https://review.openstack.org/112660
    Fix network/secgroup scenario tests for ironic

Addressed by: https://review.openstack.org/118513
    Add baremetal tests for get node by instance/port

Addressed by: https://review.openstack.org/119670
    large ops test should be derived from OfficialClientTest

Addressed by: https://review.openstack.org/122196
    Migrate TestStampPattern to tempest client

Addressed by: https://review.openstack.org/122197
    Unskip TestStampPattern for testing purposes

Addressed by: https://review.openstack.org/122320
    WIP: Migrate test_autoscaling to tempest clients

Addressed by: https://review.openstack.org/123260
    Drop autoscaling scenario test.

Addressed by: https://review.openstack.org/124013
    Drop OfficialClientTest and NetworkTest

Addressed by: https://review.openstack.org/124014
    Rename NeutronScenarioTest to NetworkScenarioTest

Addressed by: https://review.openstack.org/124015
    Migrate scenario utils to tempest client

Addressed by: https://review.openstack.org/124016
    Cleanup leftover dependencies to official clients

Addressed by: https://review.openstack.org/124017
    Drop OfficialClientManager from tenant isolation

Addressed by: https://review.openstack.org/124018
    Drop OfficialClientManager and references to it

Addressed by: https://review.openstack.org/124019
    Drop client_type for auth module

Addressed by: https://review.openstack.org/124253
    Drop python-*client from requirements

Addressed by: https://review.openstack.org/124618
    Removes deprecated net_common module

Addressed by: https://review.openstack.org/126214
    Remove OfficialClient dependency from HACKING.rst

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.