Neutron drivers for PowerVM network management.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Elod Illes a00fc731b1 Adjust version constraint of hacking 2 months ago
devstack Use opendev repository 11 months ago
doc Sync sphinx constraints with global-requirements 7 months ago
networking_powervm Merge "More py3.x support" 1 year ago
specs Omit the twice occured words in powervm-sriov-neutron.rst 1 year ago
.gitignore Clean up .gitignore 1 year ago
.gitreview OpenDev Migration Patch 11 months ago
.stestr.conf Cleanup tox.ini 1 year ago
.zuul.yaml Add Python 3 Train unit tests 7 months ago
CONTRIBUTING.rst Rename neutron-powervm to networking-powervm 4 years ago
HACKING.rst fix hacking docs link 2 years ago
LICENSE Initial Library Setup 5 years ago
README.rst Change pypowervm repo location 4 years ago
babel.cfg Add babel config 4 years ago
bindep.txt Add bindep.txt 7 months ago
lower-constraints.txt Add Python 3 Train unit tests 7 months ago
openstack-common.conf Rename neutron-powervm to networking-powervm 4 years ago
requirements.txt opt in for neutron-lib consumption patches 1 year ago
setup.cfg Enable support for both python3.6 and python3.7 6 months ago Manual sync with upstream requirements 3 years ago Rename neutron-powervm to networking-powervm 4 years ago
test-requirements.txt Adjust version constraint of hacking 2 months ago
tox.ini Enable support for both python3.6 and python3.7 6 months ago


PowerVM Neutron ML2 Agent

The IBM PowerVM hypervisor provides virtualization on POWER hardware. PowerVM operators can see benefits in their environments by making use of OpenStack. This project implements a ML2 compatible agent that provides capability for PowerVM admins to natively use OpenStack Neutron. This agent is tied to the Shared Ethernet Adapter technology which is currently the typical scenario for PowerVM network virtualization.

Problem description

This project provides a ML2 compatible agent for the PowerVM hypervisor. It is paired to the nova-powervm driver.

This PowerVM agent provides support for VLAN networks across Shared Ethernet Adapters. It provisions the VLANs on the Virtual I/O Servers (VIOS) to support the client workload, via the PowerVM REST API. The Nova component will set up the peer adapter as part of VIF plugging.

Only networks of physical type VLAN are supported.

Use Cases

  • Deploy a VLAN to the specified Virtual I/O Server (or pair of servers) as deploys occur.
  • Periodic heal of the systems (similar to Open vSwitch agent design).
  • Periodic optimization (removal of unused VLANs from the Shared Ethernet Adapters) of the system.
  • Heartbeat of the agent.

Project Priority


Data model impact


REST API impact


Security impact


Notifications impact


Other end user impact

None to end user.

Performance Impact

No performance impact. Deploy operations should not be impacted by using this agent.

Other deployer impact

The operator needs to obtain the agent from the code repository. The cloud administrator needs to install the agent on both the Neutron controller as well as on the compute node.

The operator will then need to configure the bridge_mappings, to define in the CONF file how to map the physical networks to the adapters. No further configuration is required for the operator. If only one physical network exists (the default), and a single Shared Ethernet Adapter, no bridge_mapping configuration is required. The agent will assume the default network maps to that single Shared Ethernet Adapter (or single pair SEAs set up for redundancy).

Redundant Shared Ethernet Adapters (as defined by the PowerVM Redbook) are fully supported by this agent.

Developer impact




Primary assignee:


Other contributors:

wpward svenkat efried


  • The Neutron ML2 Plugin.
  • Utilizes the PowerVM REST API specification for management. Will utilize future versions of this specification as it becomes available:
  • Builds on top of the pypowervm library. An open-source, python based library that interacts with the PowerVM REST API.


Tempest Tests

Since the tempest tests should be implementation agnostic, the existing tempest tests should be able to run against the PowerVM agent without issue.

Thorough unit tests exist within the agent that validate specific functions for this implementation.

Functional Tests

A third party functional test environment has been created. It monitors incoming Neutron change sets. Once it detects a new change set, it should execute the existing lifecycle API tests. A non-gating vote (+1 or -1) will be provided with information provided (logs) based on the result.

Work continues in this area.

API Tests

No changes (no new APIs)