summaryrefslogtreecommitdiffstats
path: root/meta-openstack/recipes-devtools/python
Commit message (Collapse)AuthorAgeFilesLines
...
* ceilometer builtin tests config locationVu Tran2014-06-232-0/+131
| | | | | | | | | | Many ceilometer built-in testcases failed because they can not find ceilometer configuration file, as these tests use relative paths to find these configuration files. So forcing these failure testcases to look for these configuration file using absolute path. Signed-off-by: Vu Tran <vu.tran@windriver.com>
* cinder builtin tests config locationVu Tran2014-06-232-0/+29
| | | | | | | | | | | Many cinder built-in testcases failed because they can not find cinder configuration file, as these testcases assume that they are run at python site-packages dir. So forcing these failure testcases to look for these configuration file using absolute path. Signed-off-by: Vu Tran <vu.tran@windriver.com>
* glance builtin tests config location and missing packagesVu Tran2014-06-232-0/+96
| | | | | | | | | | | | | | | | Many glance built-in testcases failed because they can not find glance configuration files, as these testcases assume that they are run at python site-packages dir. So forcing these failure testcases to look for these confiugration file using absolute path. Also some tests fail because of missing two packages: python-psutil and qpid-python. So add these packages into glance-tests RDEPENDS Signed-off-by: Vu Tran <vu.tran@windriver.com>
* httpretty: create recipe for packageKeith Holman2014-06-232-1/+31
| | | | | | | | | Keystoneclient tests require the package httpretty be available on the system in order to run. This fix includes a recipe file for obtaining and building httpretty. The fix also adds httpretty as a dependency of keystoneclient. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* keystoneclient: add example test certificatesKeith Holman2014-06-232-1/+40
| | | | | | | | | The tests included with keystoneclient require the use of example certificates. This fix copies the example certificates that are found in the source to the target system. It also patches the test files to find the certificates in the correct location. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* nova: package plugin directory and fix its pathKeith Holman2014-06-232-0/+34
| | | | | | | | | | The tests included with nova require some files that are within the "plugin" directory. This fix includes the "plugin" directory on the target system as part of the recipe. This fix also includes a patch that updates the tests to find the "plugin" directory where it is installed on the target system. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* nova: package doc directory and fix its pathKeith Holman2014-06-232-0/+49
| | | | | | | | | | The tests included with nova require some setup and configuration files that are within the "doc" directory. This fix includes the doc directory on the target system as part of the recipe. This fix also includes a patch that updates the tests to find the "doc" directory where it is installed on the target system. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* nova: use absolute path to api-paste.ini fileKeith Holman2014-06-232-0/+34
| | | | | | | | | | The api-paste.ini file shipped with nova is installed into the /etc/nova directory on a target system. The tests included with nova expect the file to be relative to the location of the tests within the source tree. This fix sets the absolute path to the api-paste.ini file as it exists on the system. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* coverage: add recipe for coverage tool and dependencyKeith Holman2014-06-232-0/+30
| | | | | | | | | Nova requires the python-coverage to be available in order for the unit tests supplied to pass. This fix adds a recipe in order to build the coverage tool. It also adds the dependency to the new package to the recipe to build nova. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* Add metadata service support to controller nodeAndy Ning2014-06-185-2/+60
| | | | | | | | | | | | | | | | | | The metadata service is working as the following: - metadata is being served by nova-api on controller at port 8775. - VM instance requests metadata by 169.254.169.254 (eg, curl http://169.254.169.254/latest/meta-data) - metadata request comes to neutron-ns-metadata-proxy on controller in dhcp network name space. - neutron-ns-metadata-proxy forwards the request to neutron-metadata-agent through a unix domain socket (/var/lib/neutron/metadata_proxy). - neutron-metadata-agent sends the request to nova-api on port 8775 to be serviced. To support metadata service, neutron-ns-metadata-proxy is baked into the controller image. Also neutron-metadata-agent startup script (/etc/init.d/neutron-metadata-agent) and config file (/etc/neutron/metadata_agent.ini) are added to start up metadata agent at system initialization. dhcp_agent.ini and nova.conf are updated as well. A README.metadata is added in the Documentation/ directory. Signed-off-by: Andy Ning <andy.ning@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* barbican: handle white space in date stringsKeith Holman2014-06-162-0/+32
| | | | | | | | | | Barbican tests fail because white space is not being properly parsed by the iso8601 python package. This fix updates the barbican code using a patch file to strip white space from the date before passing it to the is8601 package for parsing. Signed-off-by: Keith Holman <Keith.Holman@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* barbican: add full path to test configuration filesKeith Holman2014-06-162-0/+37
| | | | | | | | | | | Barbican expects configuration files for its tests to be in the same location as they appear in the source tree. However, during deployment configuration files are put into the /etc/barbican directory. This fix patches the tests to find the configuration files in the directory they are placed by the barbican recipe. Signed-off-by: Keith Holman <Keith.Holman@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* novaclient: fix path to test certificateKeith Holman2014-06-162-0/+39
| | | | | | | | | | | | Novaclient contains a test that fails because it can't find the path to the test certficate. This is because the test is based off of running the test from the base of the source tree. This fix changes the path to look for the certificate from a relative path to the absolute path allowing the test to be ran from any directory. Signed-off-by: Keith Holman <Keith.Holman@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* keystone: remove git commands from testsKeith Holman2014-06-092-0/+43
| | | | | | | | | | | | | When running the keystone tests, the tests ensures that keystone is being tested against the latest version of keystone-client available by downloading keystone-client from source using git. However, on the target system keystone-client is installed as a separate package and it is undesirable to download a newer version to test against. This fix comments out the portion of the testing code that attempts to retrieve keystone-client from source code using git. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* keystone: create test temporary directoryKeith Holman2014-06-091-0/+2
| | | | | | | | | | | Some Keystone tests create temporary files, usually databases for testing. These files are stored in the "tmp" directory under the "tests" directory in Keystone. The fix creates this directory so these tests don't fail on failing to create temporary files because the path doesn't exist. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* keystone: fix location of files for testsKeith Holman2014-06-092-0/+37
| | | | | | | | | | | Keystone tests define the location of certificate files as the location of the files in the source tree. However, when installed on the system files are put in different locations. This change patches the configuration file for some tests to contain the full path to the tests directories. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* keystone: install example test certificatesKeith Holman2014-06-091-0/+3
| | | | | | | | | | | | Some tests provided by Keystone tests signing with an example certificate and signing key. If these certificates are not found these particular tests will hang. Thus, in order for these tests to pass we must install the example certificates to the system. This fix updates the install script for Keystone to include installing the example certificates. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* keystone: fix paths for testingKeith Holman2014-06-093-25/+46
| | | | | | | | | | | | | | Keystone tests are designed to run on the source tree. However, Keystone is installed on a system with files in various directories. This fix patches the testing source files to be able to find the files on the distribution. This fix incorporates the changes of a previous patch file into a new patch file that is generated, since the previous patch are related and close to eachother in the source and it is easier to maintain less patch files. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* openstack-nose: plugin for openstack style outputKeith Holman2014-06-092-0/+33
| | | | | | | | | | Openstack components provide a run_tests.sh script for running unit tests. Some of these tests expect the openstack-nose plugin to be installed. This fix provides a recipe for the building that plugin in order to allow the various run_tests.sh scripts to run. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* keystone: fix tabs in recipe according to style guideKeith Holman2014-06-091-15/+15
| | | | | | | | | | | | | | The bitbake recipe file for building Keystone is inconsistent with the use of tabs versus spaces. According to guidelines for the Yocto project (style guide), the tabs should be replaced with spaces in the case of indenting for lists. The style guide can be found at: https://wiki.yoctoproject.org/wiki/Recipe_&_Patch_Style_Guide This fix changes the Keystone recipe file to use spaces instead of tabs in list of files and package dependencies. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* colorama: python package for terminal coloursKeith Holman2014-06-091-0/+26
| | | | | | | | | Colorama is a python interface for sending ASCII terminal codes to facilitate setting cursor locations and outputting color to terminal windows. This change provides a recipe for obtaining the colorama package. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* termcolor: added recipe and dependencyKeith Holman2014-06-091-0/+26
| | | | | | | | Some packages require the termcolor package, which is used to generate colour output on terminal screens. This change provides a recipe for installing the termcolor package. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* horizon: add full path to test directoriesKeith Holman2014-06-043-66/+41
| | | | | | | | | | | | | | The tests included Horizon expect all files to be in a single location in order to be run directly from the source tree. The recipe for installing Horizon on the system installs Horizon as a python site-package and puts files in different locations depending on the file type. In order to have the tests support this type of install we need to explicitly indicate the full path of the test files to exclude in order to have the tests run successfully. This fix adds the absolute path to the test locations allows the Horizon tests to pass as expected. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* nose-exclude: add plugin for nose to exclude directoriesKeith Holman2014-06-042-0/+32
| | | | | | | | | | | Nose is a package to support unit testing of python source code. Node-exclude is a plugin extending Nose to specify directories to exclude from testing via the command line. Some packages require this plugin to be installed in order to run all the tests successfully. This fix creates recipe to install the node-exclude plugin on the target system. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* django-nose: add recipe and dependencies for testingKeith Holman2014-06-042-0/+33
| | | | | | | | | | Horizon provides unit tests for testing its deployment in target environment. These tests make use of django-nose testing framework. This provides a recipe for building django-nose and adds a dependency from Horizon on this recipe. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* horizon: patch test script to run without coverageKeith Holman2014-06-042-0/+66
| | | | | | | | | | | Currently, the run_tests.sh script provided by the horizon package requires the command "coverage" to be available even if the "-c" option (test with code coverage) is not specified on the command line. This fix patches the test script to remove the calls to the "coverage" tool and calls the test script directly if the "-c" option is not provided. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* cephclient: add main library/client ReST APIsBruce Ashfield2014-06-041-0/+30
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* cephclient: add supporting library python-lxmlBruce Ashfield2014-06-041-0/+29
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* cephclient: add supporting library python-html5libBruce Ashfield2014-06-041-0/+27
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* cephclient: add supporting library python-cssselectBruce Ashfield2014-06-041-0/+27
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* barbicanclient: update github repositoryBruce Ashfield2014-06-021-1/+1
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* barbican: update repository to githubBruce Ashfield2014-06-021-1/+1
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* ceilometer: need to start ceilometer agent notificationVu Tran2014-05-301-2/+12
| | | | | | | | | There are some missing ceilometer meters (e.g. vcpu) which have origin from notification. This is due to ceilometer-agent-notification service is not started on controller node. Signed-off-by: Vu Tran <vu.tran@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* keystone add user for tempestVu Tran2014-05-261-0/+16
| | | | | | | | | | | | To support tempest, modify keystone identity.sh script to: * add user with username=alt_demo, tenant=alt_demo, and password=password into keystone. * add user "admin" into tenant "demo". Signed-off-by: Vu Tran <vu.tran@windriver.com>
* python-six: No generic license file exists for: UNKNOWN in any providerAmy Fong2014-05-241-2/+2
| | | | | | Change license to MIT Signed-off-by: Amy Fong <amy.fong@windriver.com>
* python-amqplib: No generic license file exists for: LGPL-3 in any providerAmy Fong2014-05-241-2/+2
| | | | | | Modifying license to LGPL-3.0 Signed-off-by: Amy Fong <amy.fong@windriver.com>
* barbican: increase uwsgi buffer-size to work with keystoneKeith Holman2014-05-233-1/+45
| | | | | | | | | | | | uWSGI defaults to a maximum packet size of 4096 bytes. This is too small to support working with PKI tokens that are now default in Keystone. The size of the packets within Barbican are dependent on both the size of the Keystone token and the size of the secret to be stored & retrieved. Increasing the buffer size to the maximum allowed by uWSGI allows Barbican to support the largest possible secrets. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* barbican: output a log file for debugging purposesKeith Holman2014-05-231-3/+4
| | | | | | | | Currently, the /var/log/barbican directory is created but remains empty. This change outputs a Barbican log file for debugging communication problems that occur via uWSGI. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* heat: change template version to 2013-05-23Bruce Ashfield2014-05-223-3/+3
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* heatclient: add heatclient-tests bbVu Tran2014-05-211-1/+7
| | | | | | | | Heatclient tests requires python-mox3 and python-testscenarios. Create additional heatclient-tests package when included into final image will also include these 2 packages into final image. Signed-off-by: Vu Tran <vu.tran@windriver.com>
* Add new python-mox3 bbVu Tran2014-05-211-0/+22
| | | | | | | mox3 package is required by heatclient tests, so pulling this package in. Signed-off-by: Vu Tran <vu.tran@windriver.com>
* Add new python-testscenarios bbVu Tran2014-05-211-0/+19
| | | | | | | testscenarios package is required by heatclient tests, so pulling this package in. Signed-off-by: Vu Tran <vu.tran@windriver.com>
* heat tests change project_dir pathVu Tran2014-05-212-0/+24
| | | | | | | | | | | By default, heat-tests sets project dir to /usr/<lib/lib64>/python2.7/site-packages/ which is the starting place for heat-tests to search for default environment setting file. However all the required file are in /etc/heat. So set project_dir to "/" Signed-off-by: Vu Tran <vu.tran@windriver.com>
* heat: add example hot templatesVu Tran2014-05-214-2/+211
| | | | | | | | Add 2 hot templates which can be used to create heat stack for demonstrating heat stack lifecycle management and autoscaling Signed-off-by: Vu Tran <vu.tran@windriver.com>
* heat change config file for autoscalingVu Tran2014-05-211-2/+2
| | | | | | | | Set heat_metadata_server_url, heat_waitcondition_server_url config options in heat.conf to allow Ceilometer to be able to invoke heat when resource alarm triggered. Signed-off-by: Vu Tran <vu.tran@windriver.com>
* ceilometer: need to filter meter-id when doing sql queryingVu Tran2014-05-211-8/+9
| | | | | | | | | | | | | | | Currently statistic values for all the meters are the same, for example, 2 commands: $ ceilometer statistics -m cpu_util $ ceilometer statistics -m cpu return the same statistic values, and this is incorrect. It needs to query Ceilometer database for samples for the correct meter-id to calculate statistic. Signed-off-by: Vu Tran <vu.tran@windriver.com>
* cinder: ensure log-dir is set correctlyVu Tran2014-05-212-2/+3
| | | | | | | | | Make sure all Cinder services have the right setting for log_dir in the init script as well as in the config setting in .conf file as we shouldn't only count on our init script launch to get logging right. Signed-off-by: Vu Tran <vu.tran@windriver.com>
* cinder log postinsts missing var-log-cinderVu Tran2014-05-211-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | By turning on "log_dir=/var/log/cinder" in /etc/cinder/cinder.conf all cinder services require folder /var/log/cinder exist to be able to start. This folder is created through startup scripts "/etc/init.d/cinder-xxxx" However, at very first boot, cinder postinst script invokes "cinder-manage db sync" without first creating folder /var/log/cinder which causes "cinder-manage db sync" to fail with the following errors: Tue May 20 18:26:59 2014: Running postinst /etc/rpm-postinsts/114... Tue May 20 18:26:59 2014: Starting postgres server...already running. Tue May 20 18:27:01 2014: Traceback (most recent call last): Tue May 20 18:27:01 2014: File "/usr/bin/cinder-manage", line 543, in <module> Tue May 20 18:27:01 2014: main() Tue May 20 18:27:01 2014: File "/usr/bin/cinder-manage", line 523, in main Tue May 20 18:27:01 2014: logging.setup("cinder") Tue May 20 18:27:01 2014: File "/usr/lib64/python2.7/site-packages/cinder/openstack/common/log.py", line 359, in setup Tue May 20 18:27:01 2014: _setup_logging_from_conf() Tue May 20 18:27:01 2014: File "/usr/lib64/python2.7/site-packages/cinder/openstack/common/log.py", line 406, in _setup_logging_from_conf Tue May 20 18:27:01 2014: filelog = logging.handlers.WatchedFileHandler(logpath) Tue May 20 18:27:01 2014: File "/usr/lib64/python2.7/logging/handlers.py", line 386, in __init__ Tue May 20 18:27:01 2014: logging.FileHandler.__init__(self, filename, mode, encoding, delay) Tue May 20 18:27:01 2014: File "/usr/lib64/python2.7/logging/__init__.py", line 893, in __init__ Tue May 20 18:27:01 2014: StreamHandler.__init__(self, self._open()) Tue May 20 18:27:01 2014: File "/usr/lib64/python2.7/logging/__init__.py", line 912, in _open Tue May 20 18:27:01 2014: stream = open(self.baseFilename, self.mode) Tue May 20 18:27:01 2014: IOError: [Errno 2] No such file or directory: '/var/log/cinder/cinder-manage.log' So make sure "/var/log/cinder" is created before "cinder-manage db sync" is invoked. Signed-off-by: Vu Tran <vu.tran@windriver.com>
* pycrypto: void src/build separationMark Asselstine2014-05-131-1/+1
| | | | | | | | distutils.bbclass does not work when there is a build/src separation so inherit autotools-brokensep so continue building in the src dir. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* keystone: allow ability to store tokens in UUID or PKI formatKeith Holman2014-05-122-1/+4
| | | | | | | | | | Since Grizzly release Keystone defaults to storing tokens in PKI format. Some software works better with keystone if tokens are in the older UUID format. This change allows a simple way to set the storage format within the bitbake receipes. The default is to use the newer PKI format. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-08-04 07:53:00 +0000