Commit Graph

12 Commits

Author SHA1 Message Date
Andreas Scheuring 0d444e7546 Execute docs job on python3
Travis executes docs build in python3 env. Let's do the same locally.
Docs job under python 3 is more picky than under python 2. Let's use it.

Change-Id: Ia835297eee127bd2f218c080ea0411ce7256e140
2018-04-10 14:46:32 +02:00
Prabhat Ranjan c8d33369cd change unit test case for vm.py
Need to change unit test case for vm.py.
We need to use zhmcclient_mock framework to write unit testcase.

closes-Bug: 1670667

Change-Id: Id8e743bd0602816af98559da6b67a52926e56262
Signed-off-by: Prabhat Ranjan <pranjank@in.ibm.com>
2017-04-13 12:07:17 +05:30
Prabhat Ranjan 8b2f9188fb Fix functional test case failing
After enabling functional test case in nova-dpm all
patch set are failing.

https://review.openstack.org/#/c/450700/

So in this patch we are enabling functional test in tox.ini

Change-Id: I76d265fe95a2e48ee65ee3ce1d2ef4db81ab46d0
Signed-off-by: Prabhat Ranjan <pranjank@in.ibm.com>
2017-04-04 18:14:32 +05:30
loooosy 2d1dd433f7 Drop py34 target in tox.ini and setup.cfg
We support py35 now.We do not have python 3.4 in setup.cfg which declares the explicit
supported versions.so it is no need to keep the supoort for py34.

Change-Id: I225c9d5d6d1f24d763dbdcb42eabcc3949797f62
see:https://review.openstack.org/#/c/349069/
2017-03-28 11:38:36 +08:00
Markus Zoeller 462956ba1f Docs: Add Release Notes
To give customers a glimpse of what to expect from each release,
this change adds a way to add release notes.

The "normal" OpenStack projects have two different sphinx directories:
* doc/source/
* releasenotes/source
That's reasonable for them, as they publish to two different locations.

As an out-of-tree driver, we cannot use the usual release notes
location at http://docs.openstack.org/releasenotes/ All our docs go
to http://nova-dpm.rtfd.io/

This made it necessary to *not* use the default release notes
directory "releasenotes/source/" like the other projects.
Otherwise we would have two different RTD projects, one for the
"normal" docs and another one for the release notes.

As we only have one place for documentation (including release notes)
it didn't make sense to have a separate tox target to create those
release notes. They are included when the docs are built with:

    $ tox -e docs

This slight deviation from the upstream defaults made it necessary
to explain the dealing with reno release notes in a developer reference
(devref).

The one added release note is only to double-check if everything
behaves as expected. It has to be updated before the next release.

Closes bug: 1657842
Change-Id: I0d2d10ea2d91bb5193aa1092997db310b277878b
2017-02-01 18:05:56 +01:00
Andreas Scheuring 8f82f0a442 Enable configfile autogeneration
This patch enables configfile autogeneration. It is triggered

* implicitly on every sphinx build
  output dir: doc/source/html/_static/nova_dpm.conf.sample
  for doc inclusion
* explicilty by tox -egenconfig
  output dir: etc/nova/nova_dpm.conf.sample
* explicitly by tox -edocs
  output dir: etc/nova/nova_dpm.conf.sample

In addition the return type of nova_dpm.conf.dpm.list_opts needed
to be changed to the default format (list of tuples).

Change-Id: Ib298b274f877d651dd846cac6525789c458da407
Closes-Bug: #1657701
2017-01-26 14:28:28 +01:00
Jenkins 7b695a5441 Merge "Fix an issue where no test coverage report is created" 2017-01-19 12:56:57 +00:00
Tin Lam ce0676d3d8 Fix an issue where no test coverage report is created
Running `tox -ecover` does not generate the coverage report.
Instead the following is displayed to the user:

    No coverage report, but warnings instead:
    Coverage.py warning: Module nova-dpm was never imported.

This patch set fixes the problem.

Change-Id: Iec85cf3a6453da3630d49df29c69b55ca5075d17
Closes-Bug: #1655920
2017-01-13 16:36:42 -06:00
Andreas Scheuring 28a7038550 Install stable zhmcclient via requirements.txt
Till now, zhmcclient is installed from github master branch using
pip. As zhmcclient is now an official OpenStack requirement [1]
We can switch to install the latest stable version via
requirements.txt.

To allow newer versions in the future, an update to the
upper-constraints.txt in the OpenStack requirements repo is
required.

To bump the minimum just increase the version in requirements.txt
of nova-dpm and make sure, that newer versions are allowed
by OpenStack requirements (see above).

[1] https://review.openstack.org/413689

Change-Id: I0da5f9271ee3391a4648064207eab5b4fb7e26fb
Closes-Bug: #1655905
2017-01-13 11:34:17 +01:00
preethipy d3947259fc Update code to python 34,35 compatible
Change-Id: Ia86c647a4ae102edcb5a5765d54e5a8b840d02a3
2016-12-28 17:41:55 +05:30
preethipy 00c646ab77 Devstack setup for nova-dpm
+ Updated tox.ini to install nova
+ Modified tox_install script to install zhmcclient requirements and removed
conditional nova installation check because new folder nova introduced for
devstack setup always returns true for the check that verifies if nova is
already installed

blueprint: devstack-setup-nova

Change-Id: I0c16e4bdda38eb331fa76010e39b5d8457475af4
2016-12-15 13:25:28 +00:00
preethipy 83c2926d1c Initial Cookiecutter Commit
* It's the initial commit based on coockiecutter template
* Upstream nova is installed using tox_install.sh as install_command
* zhmcclient is installed via tox dependencies as zhmcclient is not
listed in global openstack requirements and therefore cannot be
listed in requirements.txt

Partial-Bug: #1644216

Change-Id: Ic53e59ebdcb574f4e9fb9d09471c9ddff9bb1759
2016-12-01 12:48:30 +05:30