| Age | Commit message (Collapse) | Author |
|---|
|
Although the use of PRINC is deprecated in later versions of Yocto it
may still be used and if you are using this layer with older Yocto it
is recommended for use in bbappends. It is therefore expected to
work. PRINC expects a non-numeric prefix followed by a numeric value,
as can be seen in base.bbclass
pr_prefix = re.search("\D+",pr)
prval = re.search("\d+",pr)
if pr_prefix is None or prval is None:
bb.error("Unable to analyse format of PR variable: %s" % pr)
Failing to stick to this convention yields a parsing error when you
attempt to use PRINC:
ERROR: Unable to analyse format of PR variable
Adding the non-numeric prefix allows PRINC use in bbappends to
function correctly.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
|
|
Several packages utilize the keystone package service/user addition
services recently added. The data passed to this service depends on
the value assigned to CONTROLLER_IP (used as KEYSTONE_HOST), however,
bitbake is not able to automatically determine this dependency so
several tasks which should be rerun to create updated package postinst
scripts are not run when CONTROLLER_IP is modified. Adding the
necessary vardeps ensure these tasks are rerun and now adjustments
made to CONTROLLER_IP are reflected in the generated packages.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The patch CVE-2014-0006-swift-1265665.patch is already in the
latest Swift havana/stable release, so dropping it.
Signed-off-by: Vu Tran <vu.tran@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
convert FILESEXTRAPATHS to FILESEXTRAPATHS_append to avoid warnings from
the latest oe-core.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
This patch removes the openrc file from the keystone package and
references to openrc in the python-kystone_git.bb file.
Signed-off-by: Liam R. Howlett <Liam.Howlett@WindRiver.com>
|
|
Signed-off-by: Amy Fong <amy.fong@windriver.com>
|
|
Instead of creating tenant/user/role and service/endpoint for all
openstack services in keystone postinstall, now each of the services
creates keystone identities by itself in its own postinstall.
The existing identity.sh has been re-written to be a utility that takes
parameters, and the service postinstall calls identity.sh to create its
own keystone identities. The identity.sh can also be used as a tool to
manually create keystone identities at run time.
Signed-off-by: Andy Ning <andy.ning@windriver.com>
|
|
Instead of creating tenant/user/role and service/endpoint for all
openstack services in keystone postinstall, now each of the services
creates its own keystone identities by queueing them up in its postinstall
to a file /etc/keystone/service-user-setup. service-user-setup
script, when run as the last postinstall, calls identity.sh with keystone
identity parameters to create necessary identities for the services.
Signed-off-by: Andy Ning <andy.ning@windriver.com>
|
|
Adding /etc/keystone/hybrid-backend-setup and
convert_keystone_backend.py to set the backend
for keystone to hybrid and starts openldap and
restarts keystone.
Signed-off-by: Amy Fong <amy.fong@windriver.com>
|
|
Modify python-keystone to use openldap. keystone's identity and
assignment backends are configured to utilitze the hybrid backend for
keystone. This backend uses the SQL backend by default and goes to the ldap
database if the user doesn't exist.
Signed-off-by: Amy Fong <amy.fong@windriver.com>
|
|
This project provides two alternative backends for Keystone:
hybrid SQL and LDAP backends for OpenStack Keystone
Signed-off-by: Amy Fong <amy.fong@windriver.com>
|
|
Some of the openstack data is associated with external resources
(ie glance may have external files), we explicitly invoke the delete commands on those
in additional to dropping and recreating the databases.
Signed-off-by: Amy Fong <amy.fong@windriver.com>
|
|
Command "rally verify start" gives the following error:
TRACE rally File "/usr/lib64/python2.7/site-packages/rally/verification/verifiers/tempest/subunit2json.py", line 113, in stopTestRun
TRACE rally with open(self.results_file, 'wb') as results_file:
TRACE rally TypeError: coercing to Unicode: need string or buffer, int found
For Python 2.x, open() requires a string but not file descriptor number.
However for Python 3.x, open() can either accept a string file name of a
file descriptor number.
So modify code to pass in open() string file name. This should work
for both Python 2.x and 3.x
Signed-off-by: Vu Tran <vu.tran@windriver.com>
|
|
Command "rally-manage db recreate" gives the following error:
TRACE rally File "/usr/lib64/python2.7/site-packages/sqlalchemy/dialects/postgresql/base.py", line 898, in format_type
TRACE rally raise exc.CompileError("Postgresql ENUM type requires a name.")
TRACE rally CompileError: Postgresql ENUM type requires a name.
Signed-off-by: Vu Tran <vu.tran@windriver.com>
|
|
By default, Rally verification requires to do
following things:
* git clone tempest source from upstream
* setup virtualenv for this tempest
* setup testr environment with virtualenv above
* create tempest.conf for this tempest
If tempest is already installed/configured in rootfs
then force Rally to use this existing tempest.
A new introduced option "existing_tempest_config" in /etc/rally/rally.conf
can be used to configure Rally to either use the existing
tempest or to download from upstream.
If the option "existing_tempest_config" is not set then follows
the default path. If existing_tempest_config is set to absolute
path of tempest config folder (which contains tempest "tools"
and .testr.conf) then Rally uses this existing tempest.
Signed-off-by: Vu Tran <vu.tran@windriver.com>
|
|
OpenStack ironic is not currently supported, so remove
any code in rally that invokes ironicclient.
Signed-off-by: Vu Tran <vu.tran@windriver.com>
|
|
* Add Rally bb file
* Add Rally deployment json config for existing deployment
* Add task example
* To use custom Rally config file
Signed-off-by: Vu Tran <vu.tran@windriver.com>
|
|
OpenStack Rally requires oslotest.
Signed-off-by: Vu Tran <vu.tran@windriver.com>
|
|
The uuid candidate may be none, need to check for this.
Signed-off-by: Amy Fong <amy.fong@windriver.com>
|
|
Some of the neutron built-in testcases failed
because they can not find nec plugin extensions
based on the given relative path.
So forcing these failure testcases to look for
these extensions using absolute path.
Signed-off-by: Vu Tran <vu.tran@windriver.com>
|
|
The tests included with neutronclient are calling neutron commands
agents-list and net-list with the "-f" flag set to "json". This isn't
supported and throws an exception during the test. The exception is
unexpected and fails to free the resources allocated by the mox
testing library causing the following tests to fail. This fix applies
a patch that prevents the exception from being thrown by calling the
commands with the "-f" flag set to "csv", which is supported.
Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The keystoneclient-test package (created in the keystoneclient recipe)
is currently being generated with no files. This is causing a build
error. The path to the files to include in this package specify the
"${D}" variable at the beginning of the path, which isn't needed.
Removing this variable from the line fixes the problem.
Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
If the uuid specified has trailing whitespace, update
the error message to suggest that this is the case. (ie
give a more useful error message)
Signed-off-by: Amy Fong <amy.fong@windriver.com>
|
|
Ceilometer ceilometer/hardware/inspector/snmp.py and some
some ceilometer builtin tests require python pysnmp package.
Signed-off-by: Vu Tran <vu.tran@windriver.com>
|
|
One of the ceilometer builtin test
ceilometer.tests.api.v2.test_list_events_scenarios.TestListEvents.test_all_trailing_slash
failed as it tries to test with trailing slash.
The root cause is in pecan package, and the following two upstream
commits fix the issue:
Upstream 0e18b1f7d490695f4988d92c83bf239cf2937bf6 from
https://github.com/stackforge/pecan.git branch master
Upstream 573846e01209327030db146909de03e97cd8a858 from
https://github.com/stackforge/pecan.git branch master
Instead of back porting these commits, it's better to uprev
python-pecan to 0.5.0 version which also contains these commits.
Also remove meta-openstack/recipes-devtools/python/python-pecan_0.4.2.bb
Signed-off-by: Vu Tran <vu.tran@windriver.com>
|
|
New version of python-pecan (e.g pecan 0.5.0) requires
python logutils.
Signed-off-by: Vu Tran <vu.tran@windriver.com>
|
|
ceilometer tests against various databases: mongodb, db2,
sqlalchemy, hbase. For mongodb and db2, tests use environment
variables: CEILOMETER_TEST_MONGODB_URL and CEILOMETER_TEST_DB2_URL
for supplying URL database connection into tests. As we do not
support mangodb or db2, by not setting or setting bogus URLs to
these two environment variables will cause tests to fail.
These tests should be skipped as prerequisite is not satisfied.
Therefore we modify ceilometer testcases for mongodb and db2
to be skipped instead of failed if CEILOMETER_TEST_MONGODB_URL and
CEILOMETER_TEST_DB2_URL are not set.
Signed-off-by: Vu Tran <vu.tran@windriver.com>
|
|
Commit e5b7606eaa94033256eb1aca5f6a6eed4f9e54a0 from
https://github.com/openstack/ceilometer.git master
With the recent introduction of the identity_uri in keystoneclient,
there is a small backward incompatible change which means that weird
protocols like the ones we use during tests aren't support properly
anymore. The patch replaces "foottp" and "barttp" by "file" hopefully
keeping testing coverage the same.
Signed-off-by: Vu Tran <vu.tran@windriver.com>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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 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 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 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>
|
|
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>
|
|
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 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>
|
|
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 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 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>
|
|
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 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>
|
|
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>
|
Mark Asselstine
Vu Tran
Bruce Ashfield
Liam R. Howlett
Amy Fong
Andy Ning
Keith Holman