Seems the gate wasn't running with 'warning-is-error' switched on.
Change-Id: Ib4498ff16ba82321fb568e3a97c8bb4d5060bec6
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
In order to avoid conflict with the in-tree nova.virt.powervm driver,
the namespace of out-of-tree ('ext'ernal) driver is being change to
nova.virt.powervm_ext.
Change-Id: I9c8ad22be448a724b4a62d560a0cf3021da1b9eb
Recently the PowerVM live migration object merged into Nova proper via
review: https://review.openstack.org/#/c/391284/
This removes the need for the PowerVM driver to have its own live
migration object, allowing us to remove a bunch of code and hacks around
this.
Change-Id: Ic61eefc0086c5b3954a8986d0fb9699d039f25f9
PvmVnicSriovVifDriver, a VIF driver for vNICs backed by SR-IOV VFs. The
main plug method intercepts incoming vif requests and branches off to
this new vif driver if the vif type is 'pvm_sriov'. The driver "plugs"
a new vNIC into the instance by:
- Building a new pypowervm.wrappers.iocard.VNIC object.
- Assigning backing devices from the pool of physical ports labeled
according to the physical network name.
- Creating the VNIC on the PowerVM REST server as a child of the LPAR
corresponding to the instance.
The unplug method locates the appropriate VNIC according to its MAC
address and deletes it from the PowerVM REST server.
Implements: bp/powervm-sriov-nova
Change-Id: I9b707e8c12c2124001089ac1a0f2ef28e5cc7478
Nova now sends the LiveMigrateData objects exclusively to
pass data between compute managers and conductor during live
migration. Since dicts are no longer supported the conversion
to objects must be done to continue to support live migration.
A previous change set added the object support to the nova-powervm
project. This change set adds the hack (as the nova core team described
to the PowerVM team on Feb 24th in IRC) that enables operators to use a
custom conductor that supports the PowerVM live migrate object.
Change-Id: I2517d543cc66696a43b2cdb160e2452653f402f1
Closes-Bug: #1551954
Update to the readme doc. Most changes are from future tense to
current. Some updates about new functions.
Also includes a brief paragraph on how to get started with the driver.
Change-Id: I1f80023ae37ea2f62932b6b2baae108579eb5e26
NPIV based deploys attempted to put the client vFC adapters on to the
fabric by creating the WWPNs ahead of time and mapping them to the
management partition. This created several issues and led to poor
performance.
There were issues around migration:
- Querying for a host could leave a stale adapter on the mgmt partition
There were issues with speed:
- Deploys could take over 120 seconds
- Migrations had additional delays
There were issues with some standard operations:
- Attaching a volume on a powered off VM required logging in the WWPNs
Subsequent analysis in Cinder showed that only some Cinder drivers had
this requirement. Many could work without this. Given the challenges
the code is removing the need to log in the WWPNs on the mgmt partition.
This resolves all of the above issues.
While it does limit some of the Cinder drivers when paired with NPIV,
ongoing work will be done to meet with the Cinder driver owners to see
if the requirements in their drivers can be relaxed.
For those that can not, the vSCSI Cinder Volume attach is also an option
and should provide the use cases that they need.
Change-Id: Id77650545ca4e0def9977f1c2572b9f13f451e0d
This change set provides a significant update to the nova-powervm
drivers dev-ref.
Rebases the documentation to reflect the development that has been done
over the last several months. Updates the readme to reflect the
execution that has completed.
Removes the fake_driver that is not useful.
Change-Id: I1910db886df89f884f3c399d6aab1eebdf10b5e0
Following the compute driver standards, the driver options should
be placed in their own configuration group. This change set
introduces the 'powervm' group.
Also, removed the reference to configuration credentials in the
README.rst file.
Change-Id: I8e28f118d4c6f9fe4922e6fd5ba095c5f9e62b4a
In preparation for stackforge proposal, updating the README.rst file to
include an updated set of information. Mostly tied to the new pypowervm
python library.
Also updates the API properties to remove references to the current
location of the API server. Makes the wording more generic.
Change-Id: I1167fa28b9120fa8833bbe7939d070cb0a157c37
1) Proper indent of continuation lines in bullet list item
2) Need to escape underscore at the end of "powervm_" so it's not
interpreted as a backlink.
3) Continuation lines for hyperlinks aren't possible in RST. In cases
where the link makes the line "too long", it's okay to break the
line-length rule. See the Dependencies section of the following
(approved) blueprint for precedent:
https://raw.githubusercontent.com/stackforge/fuel-specs/master/specs/5.1/openstack-from-master.rst
Change-Id: Ide52b4930ab4695e4b97bc11f6e7002af9beaf13
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
Takashi Kajinami