Currently in lower-constraints job, pip install is issued with both
upper-constraints.txt by `install_command` in [testenv] and
lower-constraints.txt by `deps` in [testenv:lower-constraints] so
lower-constraints job actually tests aginst upper-constraints. We need
to remove upper-constraints.txt from lower-constraints job.
Along with the above, update version of mock, olso_messaging and
keystoneatuh1 package in lower-constraints.txt, requirements.txt and
test-requirements.txt.
Change-Id: I9f93075402dd5273a4ab045db5cd15bd4dea8582
Added new unit tests to cover create_wait, update_wait, delete_wait,
scale and scale_wait methods. Added heat-client fixture for writing
test cases. Also removed unreachable code in openstack module.
Change-Id: I9c1b5fe2e4efb41368d53cdac8dbbd49eea4b60a
In case of create VIM API, is_default_parameter accepts any string
values like "abc" or "1234" and set the value as True. It should
strictly check for valid boolean values.
Fixed this issue by using convert_to_boolean validator. so now, if
you pass any non-boolean value, it will return 400 error to the user.
NOTE:
The below test case fails if we inherit the test class
'..tests.unit.base.TestCase' from '..tests.base.BaseTestCase' with
KeyError:
tacker.tests.unit.nfvo.test_nfvo_plugin.TestNfvoPlugin.
test_create_ns_workflow_no_task_exception
The reason behind the failure is, the raised exception
'..extensions.nfvo.NoTasksException' expects that the 'action' and
'resource' should be passed as arguments to the exception while raising
it to form the exception message. If you don't pass these two arguments
then it fails to form the exception message and raises KeyError.
This happens because the '..tests.base.BaseTestCase' test class uses
exception fixture and sets 'use_fatal_exceptions' to True always which
results into not raising the raised exception again and it tries to
form the exception message and pass it to the base class __init__ for
further processing. It fails and raises KeyError while forming that
exception message because in 'test_create_ns_workflow_no_task_exception'
test case these arguments are not passed to the exception while
raising.
To fix this test case, passed the required 'action' and 'resource'
arguments to the exception while raising it.
DocImpact
Closes-Bug: #1746538
Change-Id: Ib533b38a48d31cb26eecdc546b20b0f99beeaa34
1. Add new option 'use_barbican' in config file [vim_keys] section,
default value is False for Pike.
2. Use fernet to encrypt vim password, and save the fernet key into
barbican as a secret.
3. Add new fields 'key_type', 'secret_uuid' into VimAuth.auth_cred
json string. secret_uuid is masked in vim-show or vim-list response.
4. Set the vim's default 'shared' value to False,
vim can only be used by who created it.
5. Add a devref to show how to test.
6. Add a release note.
Implements: blueprint encryption-with-barbican
Partial-bug: #1667652
Change-Id: I5c779041df5a08a361b9aaefac7d241369732551
In this patch, a tool is provided for team to do the sync to avoid
any gaps with global requirements.
Change-Id: Ie960eae7a2756aa0f267c8ad37ea60f5effe6742
Partial-bug: 1668848
This patch is the first step to bring the NFV Orchestration
API Reference to the repository.
It is a part of the effort described here [1]:
[1] https://wiki.openstack.org/wiki/Documentation/Migrate#API_Reference_Plan
Once this skeleton patch is merged, an api-ref job can be added to
the gate. The gate job makes it much easier to review API Reference
contents, which will be brought by follow-on patches.
Change-Id: I7cc587f2c7b3c546be9cd11bad7e3b4eeacad171
Co-Authored-By: Naoya Harada <n-harada@vx.jp.nec.com>
python-tackerclient is now available in global
requirements [1]. Moving to use pip dependency
to pull in tackerclient instead of directly
referring to the release tarball.
[1] https://review.openstack.org/334641
Change-Id: I2bc758a56f2371671db60eb626ae87194506c0a4
The translation proposal job complains about double requirements, remove
the extra one of six from test-requirements, since it's enough to have
it in requirements.txt.
Message was:
"Double requirement given: six>=1.9.0 (from -r
/home/jenkins/workspace/tacker-propose-translation-update/test-requirements.txt
(line 11)) (already in six>=1.9.0 (from -r
/home/jenkins/workspace/tacker-propose-translation-update/requirements.txt
(line 20)), name='six')"
to reproduce, run:
tox -e venv -- sphinx-build -b gettext -d releasenotes/build/doctrees releasenotes/source releasenotes/work
This fails without the change and works now.
Change-Id: Ia7b3bc86a348b3254a580cf3eaa3f6a13fe52861