python-tempest 2014.1.dev4108.gf22b6cc-0ubuntu2 / usr / lib / python2.7 / dist-packages / tempest-2014.1.dev4108.gf22b6cc.egg-info / PKG-INFO

This file is indexed.

/usr/lib/python2.7/dist-packages/tempest-2014.1.dev4108.gf22b6cc.egg-info/PKG-INFO is in python-tempest 2014.1.dev4108.gf22b6cc-0ubuntu2.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below. 

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
Metadata-Version: 1.1
Name: tempest
Version: 2014.1.dev4108.gf22b6cc
Summary: OpenStack Integration Testing
Home-page: http://www.openstack.org/
Author: OpenStack
Author-email: openstack-dev@lists.openstack.org
License: UNKNOWN
Description: Tempest - The OpenStack Integration Test Suite
        ==============================================
        
        This is a set of integration tests to be run against a live OpenStack
        cluster. Tempest has batteries of tests for OpenStack API validation,
        Scenarios, and other specific tests useful in validating an OpenStack
        deployment.
        
        Design Principles
        ----------
        Tempest Design Principles that we strive to live by.
        
        - Tempest should be able to run against any OpenStack cloud, be it a
          one node devstack install, a 20 node lxc cloud, or a 1000 node kvm
          cloud.
        - Tempest should be explicit in testing features. It is easy to auto
          discover features of a cloud incorrectly, and give people an
          incorrect assessment of their cloud. Explicit is always better.
        - Tempest uses OpenStack public interfaces. Tests in Tempest should
          only touch public interfaces, API calls (native or 3rd party),
          public CLI or libraries.
        - Tempest should not touch private or implementation specific
          interfaces. This means not directly going to the database, not
          directly hitting the hypervisors, not testing extensions not
          included in the OpenStack base. If there is some feature of
          OpenStack that is not verifiable through standard interfaces, this
          should be considered a possible enhancement.
        - Tempest strives for complete coverage of the OpenStack API and
          common scenarios that demonstrate a working cloud.
        - Tempest drives load in an OpenStack cloud. By including a broad
          array of API and scenario tests Tempest can be reused in whole or in
          parts as load generation for an OpenStack cloud.
        - Tempest should attempt to clean up after itself, whenever possible
          we should tear down resources when done.
        - Tempest should be self testing.
        
        Quickstart
        ----------
        
        To run Tempest, you first need to create a configuration file that
        will tell Tempest where to find the various OpenStack services and
        other testing behavior switches.
        
        The easiest way to create a configuration file is to copy the sample
        one in the ``etc/`` directory ::
        
            $> cd $TEMPEST_ROOT_DIR
            $> cp etc/tempest.conf.sample etc/tempest.conf
        
        After that, open up the ``etc/tempest.conf`` file and edit the
        configuration variables to match valid data in your environment.
        This includes your Keystone endpoint, a valid user and credentials,
        and reference data to be used in testing.
        
        .. note::
        
            If you have a running devstack environment, tempest will be
            automatically configured and placed in ``/opt/stack/tempest``. It
            will have a configuration file already set up to work with your
            devstack installation.
        
        Tempest is not tied to any single test runner, but testr is the most commonly
        used tool. After setting up your configuration file, you can execute
        the set of Tempest tests by using ``testr`` ::
        
            $> testr run --parallel
        
        To run one single test  ::
        
            $> testr run --parallel tempest.api.compute.servers.test_servers_negative.ServersNegativeTestJSON.test_reboot_non_existent_server
        
        Alternatively, you can use the run_tempest.sh script which will create a venv
        and run the tests or use tox to do the same.
        
        Configuration
        -------------
        
        Detailed configuration of tempest is beyond the scope of this
        document. The etc/tempest.conf.sample attempts to be a self
        documenting version of the configuration.
        
        The sample config file is auto generated using the script:
        tools/generate_sample.sh
        
        The most important pieces that are needed are the user ids, openstack
        endpoints, and basic flavors and images needed to run tests.
        
        Common Issues
        -------------
        
        Tempest was originally designed to primarily run against a full OpenStack
        deployment. Due to that focus, some issues may occur when running Tempest
        against devstack.
        
        Running Tempest, especially in parallel, against a devstack instance may
        cause requests to be rate limited, which will cause unexpected failures.
        Given the number of requests Tempest can make against a cluster, rate limiting
        should be disabled for all test accounts.
        
        Additionally, devstack only provides a single image which Nova can use.
        For the moment, the best solution is to provide the same image uuid for
        both image_ref and image_ref_alt. Tempest will skip tests as needed if it
        detects that both images are the same.
        
        Unit Tests
        ----------
        
        Tempest also has a set of unit tests which test the tempest code itself. These
        tests can be run by specifing the test discovery path::
        
            $> OS_TEST_PATH=./tempest/tests testr run --parallel
        
        By setting OS_TEST_PATH to ./tempest/tests it specifies that test discover
        should only be run on the unit test directory. The default value of OS_TEST_PATH
        is OS_TEST_PATH=./tempest/test_discover which will only run test discover on the
        tempest suite.
        
        Alternatively, you can use the run_tests.sh script which will create a venv and
        run the unit tests. There are also the py26, py27, or py33 tox jobs which will
        run the unit tests with the corresponding version of python.
        
        Python 2.6
        ----------
        
        Tempest can be run with Python 2.6 however the unit tests and the gate
        currently only run with Python 2.7, so there are no guarantees about the state
        of tempest when running with Python 2.6. Additionally, to enable testr to work
        with tempest using python 2.6 the discover module from the unittest-ext
        project has to be patched to switch the unittest.TestSuite to use
        unittest2.TestSuite instead. See::
        
        https://code.google.com/p/unittest-ext/issues/detail?id=79
        
        
Platform: UNKNOWN
Classifier: Intended Audience :: Information Technology
Classifier: Intended Audience :: System Administrators
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: Apache Software License
Classifier: Operating System :: POSIX :: Linux
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 2
Classifier: Programming Language :: Python :: 2.7

APT Browse - Built by Thomas Orozco.