Replace it with program-output from
sphinxcontrib-programoutput
Depends-On: https://review.openstack.org/595480
Change-Id: I9b14af568996cc1aaefaeb4d94fe36163c6cbbf2
os-testr has moved over to use stestr instead of testr. While this
is usually compatible with existing settings, there is a warning
that is emitted when .stestr.conf is not present. It is usually
able to fall back to parsing the .testr.conf file, but to be more
correct and to prevent future problems we should update the config.
Change-Id: I10446c539aaf9edd8b52b17776e08c12757def31
Depends-On: I98a296d009e64d6afab02a53bd1af878f78c4321
The files '.project', '.pydevproject' and derectory '.ropeproject' are
autogenerated by different IDE tools and they have nothing to do with
released code, so they should be ignored when commiting the modified
code.
According my experience, these three files are generated in following
ways:
1. '.project' is autogenerated when importing the package as a general
project to Eclipse.
2. Use Eclipse with plugin PyDev, the '.pydevproject' is autogenerated
when setting the package as PyDev project.
3. Use VIM with plugin Python-mode as an Python IDE(enable rope support),
'.ropeproject' will be autogenerated under project's root directory.
Change-Id: If92bd5c00429ec1410a6a388e34ee9afc24ede1b
In this change [1] os_testr changed under the covers from using
testr to stestr, so that we now get the following warning:
ostestr.py:120:
UserWarning: No .stestr.conf file found in the CWD.
Please create one to to replace the .testr.conf. You can find a
script to do this in the stestr git repository.
So add .stestr.conf which was generated using a utility script
as documented here [2]. Leave .testr.conf since it is still
used by our functional tests.
[1] Id7cb2a39a8308f1413608dcf19273a1d7f33592e
[2] https://media.readthedocs.org/pdf/stestr/stable/stestr.pdf
TrivialFix
Change-Id: Iff31bd08aa03c5a2ba4e6800e4d57a4585ec51ab
Create the releasenotes directory and add the requisite
conf.py file to generate python-manilaclient's release notes.
project-config change: I522ba76263a6597026f6dd7b03ec51bb05bfb15a
Change-Id: I6b0fa6016781a252a71649a7cac85f02b0a019e8
Add generic functionality for functional tests using tempest-lib and
create related tox jobs.
Run of functional tests requires:
1) Access to deployed OpenStack with running, at least, Keystone and Manila
services.
2) Defined config options to be able to execute requests to Manila,
Manilaclient should know auth related information like username, password,
tenant_name, etc...
3) Run of functional tests searches for following optional env vars to be set:
'OS_MANILACLIENT_CONFIG_FILE' - name of conf file, default 'manilaclient.conf'
'OS_MANILACLIENT_CONFIG_DIR' - path to conf dir,
default '%project_dir%/etc/manilaclient'
'OS_MANILA_EXEC_DIR' - path to dir with manilaclient executable,
default '%project_dir%/.tox/functional/bin'
4) Config sample can be generated by following new tox job:
$ tox -egenconfig
it will create sample in
"%project_dir%/etc/manilaclient/manilaclient.conf.sample"
then just rename it removing ".sample" part and set option values.
To run functional tests use following new tox job:
$ tox -efunctional
To run only some specific tests use following:
$ tox -efunctional manilaclient.tests.functional.foo.bar
Partially implements blueprint functional-tests
Change-Id: I95a4e441d2143e51c54ec4fb47a069a91ed77dd7
Without this change git considers temp files of vim and cover tox job as new
files, so add them to .gitignore.
Change-Id: Id1f7b2785b928dedd00f0848aad7ad81718699eb
If we run unittests there are appear dir .venv and file subunit.log
So, add these files to gitignore.
Change-Id: I64c400d1333e12b87da7fcd2c64772964e3f1b3c
Goutham Pacha Ravi