Initial Load of Nova PowerVM Project

Initial work to enable the Nova PowerVM project in git.

The work done here provides:
 - .gitignore - Indicate which files not to track within Git.
 - .gitreview - Input to the git-review command on how to send to
                Gerrit.
 - .testr.conf - Conf file input for the testr command (UT)
 - CONTRIBUTING.rst - Information on how to contribute.
 - HACKING.rst - Information on what needs to be done for updates.
 - LICENSE - The license for the project
 - README.rst - Information on what this project is.  Currently this is
                the blueprint.
 - openstack-common.conf - Required openstack configuration for all
                           projects
 - setup.cfg - Input to the setup.py on how to execute certain actions.
 - setup.py - Used for build of the project.
 - requirements.txt - Required packages (and levels) to run the code.
 - test-requirements.txt - Required packages (and levels) in addition
                           to the requirements, that indicates what is
                           needed to run the UT.
 - tox.ini - The input for the tox commands.

In addition, a base set of packages for the agent and unit tests were
loaded in.

Change-Id: Iaa186e449e7e0f75dc06a033d024a23d7faa0267
This commit is contained in:
Drew Thorstensen 2014-10-20 10:44:01 -05:00
parent 2af6e5a926
commit 095e1c183b
19 changed files with 776 additions and 0 deletions

5
.gitignore vendored Normal file
View File

@ -0,0 +1,5 @@
build/*
.testrepository
.tox/
nova_powervm.egg-info/
*.pyc

4
.gitreview Normal file
View File

@ -0,0 +1,4 @@
[gerrit]
host=***REMOVED***
port=29418
project=nova-powervm.git

7
.testr.conf Normal file
View File

@ -0,0 +1,7 @@
[DEFAULT]
test_command=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-60} \
${PYTHON:-python} -m subunit.run discover -t ./ . $LISTOPT $IDOPTION
test_id_option=--load-list $IDFILE
test_list_option=--list

17
CONTRIBUTING.rst Normal file
View File

@ -0,0 +1,17 @@
If you would like to contribute to the development of OpenStack,
you must follow the steps in the "If you're a developer, start here"
section of this page:
http://wiki.openstack.org/HowToContribute
Once those steps have been completed, changes to OpenStack
should be submitted for review via the Gerrit tool, following
the workflow documented at:
http://wiki.openstack.org/GerritWorkflow
Pull requests submitted through GitHub will be ignored.
Bugs should be filed on Launchpad, not GitHub:
https://bugs.launchpad.net/nova-powervm

21
HACKING.rst Normal file
View File

@ -0,0 +1,21 @@
Nova-PowerVM Style Commandments
===============================
- Step 1: Read the OpenStack Style Commandments
http://docs.openstack.org/developer/hacking/
- Step 2: Read on
Nova-PowerVM Specific Commandments
----------------------------------
- Follow the Nova HACKING.rst
Creating Unit Tests
-------------------
For every new feature, unit tests should be created that both test and
(implicitly) document the usage of said feature. If submitting a patch for a
bug that had no unit test, a new passing unit test should be added. If a
submitted bug fix does have a unit test, be sure to add a new one that fails
without the patch and passes with the patch.
For more information on creating unit tests and utilizing the testing
infrastructure in OpenStack Nova, please read ``nova/tests/README.rst``.

176
LICENSE Normal file
View File

@ -0,0 +1,176 @@
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.

337
README.rst Normal file
View File

@ -0,0 +1,337 @@
===================
PowerVM Nova Driver
===================
Include the URL of your launchpad blueprint:
https://blueprints.launchpad.net/neutron/+spec/example
The IBM PowerVM hypervisor provides virtualization on POWER hardware. PowerVM
admins can see benefits in their environments by making use of OpenStack.
This driver (along with a Neutron ML2 compatible agent and Ceilometer agent)
will provide capability for admins of PowerVM (which encapsulates PHYP and
Virtual I/O Servers) to use OpenStack natively.
Problem Description
===================
As a new ecosystem evolves around the POWER platform, there is not an
OpenStack driver that meets all of the needs for that ecosystem. The work
done here is to build a PowerVM driver in within the broader community. This
will sit alongside the existing libvirt driver utilized by PowerKVM
environments.
This new driver must meet the following:
* Built within the community
* Fits the OpenStack model
* Utilizes automated functional and unit tests
* Enables use of PowerVM systems through the OpenStack APIs
* Allows attachment of volumes from Cinder over supported protocols
The use cases should be the following:
* As a deployer, all of the standard lifecycle operations (start, stop,
reboot, migrate, destroy, etc...) should be supported on a PowerVM based
instance.
* As a deployer, I should be able to capture an instance to an image.
Proposed Change
===============
The changes proposed are the following:
* Create a PowerVM based driver in a StackForge project. This will implement
the nova/virt/driver Compute Driver.
* Provide deployments that work with the OpenStack model.
* Driver will be implemented using a new version of the PowerVM REST API.
* Ephemeral disks will be supported either with Virtual I/O Server (VIOS)
hosted local disks or via Shared Storage Pools (a PowerVM cluster file
system).
* Volume support will be via Cinder through supported protocols for the
Hypervisor.
* Network integration will be supported via a ML2 compatible Neutron Agent.
* Automated Functional Testing will be provided to validate changes from the
broader OpenStack community against the PowerVM driver.
* Thorough unit testing will be provided for the driver.
The changes proposed will bring support for the PowerVM hypervisor into the
OpenStack ecosystem, following the OpenStack development model.
This development is planned to be done in StackForge in a project named
powervm. The intent is that the completion of this work will provide the
foundation to bring the PowerVM Nova driver (with supporting components) into
Nova Core via a separate BluePrint in the L release of OpenStack.
Until the subsequent BluePrint is proposed for the L release, this driver is
to be considered experimental.
Data Model Impact
-----------------
No data model impacts are anticipated as part of this work.
REST API Impact
---------------
The intent of this work item is to enable PowerVM to fit within the broader
OpenStack ecosystem, without requiring changes to the REST API.
As such, no REST API impacts are anticipated.
Security Impact
---------------
The user may need to configure the credentials to communicate with the PowerVM
REST API via a CONF file. These should be encoded.
New root wrap policies may need to be updated to support various commands for
the PowerVM REST API.
No other security impacts are foreseen.
Notifications Impact
--------------------
No new notifications are anticipated.
Other End User Impact
---------------------
The administrator will notice new logging messages in the nova compute logs.
Performance Impact
------------------
It is a goal of the driver to deploy systems with the same speed and agility
as the libvirt driver within OpenStack.
Since this process should match the OpenStack model, it is not planned to add
any new periodic tasks, database queries or other items.
Performance impacts should be limited to the Compute Driver, as the changes
should be consolidated within the driver on the endpoint. The API processes
for instance should not be impacted.
Other Deployer Impact
---------------------
The cloud administrator will need to refer to documentation on how to
configure OpenStack for use with a PowerVM hypervisor.
The existing configuration file attributes will be reused as much as possible.
This reduces the number of PowerVM specific items that will be needed.
However, the driver is likely to need some PowerVM specific options.
In this case, we plan to keep the PowerVM specifics contained within the
configuration file (and driver code). Any new configuration options will have
the prefix "powervm_".
There should be no impact to customers upgrading their cloud stack as this is
a genesis driver and should not have database impacts.
Developer Impact
----------------
The code for this driver will be contained within a powervm StackForge
project. The driver will be contained within /nova/virt/powervm/. The driver
will extend nova.virt.driver.ComputeDriver.
The code will interact with PowerVM through an Open Sourced python binding
that is being defined. This python binding is a wrapper to the PowerVM REST
API. All operations to the hypervisor will go through the PowerVM REST API
via this binding. The driver will be maintained to support future revisions
of the PowerVM REST API as needed.
For ephemeral disk support, either a Virtual I/O Server hosted local disk or a
Shared Storage Pool (a PowerVM clustered file system) will be supported. For
volume attachments, the driver will support Cinder based attachments via
protocols supported by the hypervisor.
For networking, a blueprint is being proposed for the Neutron project that
will provide a Neutron ML2 Agent. This too will be developed in StackForge,
and a subsequent blueprint will be created to move to Neutron Core in the L
release of OpenStack. The Agent will provide the necessary configuration on
the Virtual I/O Server. The Nova driver code will have a
/nova/virt/powervm/vif.py file that will configure the network adapter on the
client VM.
Automated functional testing will be provided through a third party continuous
integration system. It will monitor for incoming Nova change sets, run a set
of functional tests (lifecycle operations) against the incoming change, and
provide a non-gating vote (+1 or -1).
Developers should not be impacted by these changes unless they wish to try the
driver.
Until the driver is accepted into Nova core it will be considered experimental.
Community Impact
----------------
The intent of this blueprint is to bring another driver to OpenStack that
aligns with the ideals and vision of the community.
It will be discussed in the Nova IRC and mailing lists. Representatives
working on this driver will be at the design summit, though no sessions are
planned on this topic.
Alternatives
------------
No alternatives appear viable to bring PowerVM support into the OpenStack
community.
Implementation
==============
Assignee(s)
-----------
Primary assignee:
kyleh
Other contributors:
thorst
dwarcher
efried
Work Items
----------
* Create a base PowerVM driver that is non-functional, but defines the methods
that need to be implemented.
* Implement the host statistics methods (get_host_stats, get_host_ip_addr,
get_host_cpu_stats, get_host_uptime, etc.).
* Implement the spawn method.
* Implement the destroy method.
* Implement the instance information methods (list_instances, instance_exists,
poll_rebooting_instances, etc.).
* Implement the live migration methods. Note that, for ephemeral disks, this
will be specific to Shared Storage Pool environments where the Virtual I/O
Servers on the source and target systems share the same (clustered) file
system.
* Implement support for Cinder volume operations.
* Implement an option to configure an internal management NIC - used for
Resource Monitoring and Control (RMC) as part of deploy. This is a
prerequisite for migration and resize. This will be controlled as part of
the CONF file.
* Implement the network interface methods (attach_interface and
detach_interface). Delegate the Virtual I/O Server work to the
corresponding Neutron ML2 agent.
* Implement an automated functional test server that listens for incoming
commits from the community and provides a non-gating vote (+1 or -1) on the
change.
Dependencies
============
* Will utilize the PowerVM REST API specification for management. Will
utilize future versions of this specification as it becomes available:
http://ibm.co/1lThV9R
* Will build on top of a new open source python binding to previously noted
PowerVM REST API. This will be a prerequisite to utilizing the driver.
Testing
=======
Tempest Tests
-------------
Since the tempest tests should be implementation agnostic, the existing
tempest tests should be able to run against the PowerVM driver without issue.
This blueprint does not foresee any changes based off this driver.
Thorough unit tests will be created within the Nova project to validate
specific functions within this driver implementation.
Functional Tests
----------------
A third party functional test environment will be created. It will monitor
for incoming nova change sets. Once it detects a new change set, it will
execute the existing lifecycle API tests. A non-gating vote (+1 or -1) will
be provided with information provided (logs) based on the result.
API Tests
---------
The REST APIs are not planned to change as part of this. Existing APIs should
be valid. All testing is planned within the functional testing system and via
unit tests.
Documentation Impact
====================
User Documentation
------------------
Documentation will be contributed which identifies how to configure the
driver. This will include configuring the dependencies specified above.
Documentation will be done on wiki, specifically at a minimum to the following
page: http://docs.openstack.org/trunk/config-reference/content/
section_compute-hypervisors.html
Interlock will be done with the OpenStack documentation team.
Developer Documentation
-----------------------
No developer documentation additions are anticipated. If the existing
developer documentation is updated to reflect more hypervisor specific items,
this driver will follow suit.
References
==========
* PowerVM REST API Specification (may require newer versions as they
become available): http://ibm.co/1lThV9R
* PowerVM Virtualization Introduction and Configuration:
http://www.redbooks.ibm.com/abstracts/sg247940.html
* PowerVM Best Practices: http://www.redbooks.ibm.com/abstracts/sg248062.html

15
nova-powervm/__init__.py Normal file
View File

@ -0,0 +1,15 @@
# Copyright 2014 IBM Corp.
#
# All Rights Reserved.
#
# Licensed under the Apache License, Version 2.0 (the "License"); you may
# not use this file except in compliance with the License. You may obtain
# a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
# License for the specific language governing permissions and limitations
# under the License.

View File

@ -0,0 +1,15 @@
# Copyright 2014 IBM Corp.
#
# All Rights Reserved.
#
# Licensed under the Apache License, Version 2.0 (the "License"); you may
# not use this file except in compliance with the License. You may obtain
# a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
# License for the specific language governing permissions and limitations
# under the License.

View File

@ -0,0 +1,15 @@
# Copyright 2014 IBM Corp.
#
# All Rights Reserved.
#
# Licensed under the Apache License, Version 2.0 (the "License"); you may
# not use this file except in compliance with the License. You may obtain
# a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
# License for the specific language governing permissions and limitations
# under the License.

View File

@ -0,0 +1,15 @@
# Copyright 2014 IBM Corp.
#
# All Rights Reserved.
#
# Licensed under the Apache License, Version 2.0 (the "License"); you may
# not use this file except in compliance with the License. You may obtain
# a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
# License for the specific language governing permissions and limitations
# under the License.

View File

@ -0,0 +1,15 @@
# Copyright 2014 IBM Corp.
#
# All Rights Reserved.
#
# Licensed under the Apache License, Version 2.0 (the "License"); you may
# not use this file except in compliance with the License. You may obtain
# a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
# License for the specific language governing permissions and limitations
# under the License.

View File

@ -0,0 +1,15 @@
# Copyright 2014 IBM Corp.
#
# All Rights Reserved.
#
# Licensed under the Apache License, Version 2.0 (the "License"); you may
# not use this file except in compliance with the License. You may obtain
# a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
# License for the specific language governing permissions and limitations
# under the License.

4
openstack-common.conf Normal file
View File

@ -0,0 +1,4 @@
[DEFAULT]
# The base module to hold the copy of openstack.common
base=nova-powervm

6
requirements.txt Normal file
View File

@ -0,0 +1,6 @@
pbr>=0.5.21,<1.0
Babel>=1.3
six>=1.7.0
oslo.serialization>=1.0.0 # Apache-2.0
oslo.utils>=1.0.0 # Apache-2.0
oslo.config>=1.4.0 # Apache-2.0

45
setup.cfg Normal file
View File

@ -0,0 +1,45 @@
[metadata]
name = nova-powervm
summary = PowerVM driver for OpenStack Nova.
description-file = README.rst
author = IBM
author-email = kyleh@us.ibm.com
home-page = ???
classifier =
Environment :: OpenStack
Intended Audience :: Information Technology
Intended Audience :: System Administrators
License :: OSI Approved :: Apache Software License
Operating System :: POSIX :: Linux
Programming Language :: Python
Programming Language :: Python :: 2
Programming Language :: Python :: 2.7
Programming Language :: Python :: 2.6
Programming Language :: Python :: 3
Programming Language :: Python :: 3.3
[files]
packages =
nova-powervm
[build_sphinx]
source-dir = doc/source
build-dir = doc/build
all_files = 1
[upload_sphinx]
upload-dir = doc/build/html
[compile_catalog]
directory = nova-powervm/locale
domain = nova-powervm
[update_catalog]
domain = nova-powervm
output_dir = nova-powervm/locale
input_file = nova-powervm/locale/nova-powervm.pot
[extract_messages]
keywords = _ gettext ngettext l_ lazy_gettext
mapping_file = babel.cfg
output_file = nova-powervm/locale/nova-powervm.pot

22
setup.py Normal file
View File

@ -0,0 +1,22 @@
#!/usr/bin/env python
# Copyright 2014 IBM Corp.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
# implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# THIS FILE IS MANAGED BY THE GLOBAL REQUIREMENTS REPO - DO NOT EDIT
import setuptools
setuptools.setup(
setup_requires=['pbr'],
pbr=True)

12
test-requirements.txt Normal file
View File

@ -0,0 +1,12 @@
hacking>=0.9.2,<0.10
coverage>=3.6
discover
fixtures>=0.3.14
python-subunit
sphinx>=1.1.2
oslosphinx
testrepository>=0.0.17
testscenarios>=0.4,<0.5
testtools>=0.9.32
mock>=1.0

30
tox.ini Normal file
View File

@ -0,0 +1,30 @@
[tox]
minversion = 1.6
envlist = py26,py27,py33,pypy,pep8
skipsdist = True
[testenv]
usedevelop = True
install_command = pip install -U {opts} {packages}
setenv =
VIRTUAL_ENV={envdir}
deps = -r{toxinidir}/requirements.txt
-r{toxinidir}/test-requirements.txt
-egit+https://github.com/openstack/nova#egg=nova
commands = python -m nova.openstack.common.lockutils python setup.py testr --slowest --testr-args='{posargs}'
[testenv:pep8]
commands = flake8
[testenv:venv]
commands = {posargs}
[testenv:cover]
commands = python setup.py testr --coverage --testr-args='{posargs}'
[flake8]
ignore = E125,E712,H104
exclude = .venv,.git,.tox,dist,doc,*openstack/common*,*lib/python*,*egg,build,tools
[hacking]
import_exceptions = nova.i18n