nova is switching to use oslo.i18n, oslo.utils, oslo.serialization with
change
d0e0ade702
nova.openstack.common removed some modules that has been replaced by the
ones from oslo.i18n, oslo.utils, oslo.serialization.
Closes-Bug: #1384039
Change-Id: I9fae9b61599a50b54fc40552b2c90fceb75d8522
In order to comply with local Openstack, change this value to more
general value "Lock"
Change-Id: I823392629ade0d98ead14bc814682f64da4a9745
Closes-Bug: #1380908
User call the following hosting cli to add a vNIC with IP and port
specified:
nova interface-attach --net-id {net_uuid} --fixed-ip {ipAddress}
<server_name>
PowerVC driver handle the request in the following driver method:
def attach_interface(self, instance, image_meta, network_info):
then call the PowerVC restAPI to attach the interface to server.
User call the following hosting cli to remove a vNIC with port
specified:
nova interface-detach <server-id> <port-id>
PowerVC driver handle the request in the following driver method:
def detach_interface(self, instance, network_info):
then call the PowerVC restAPI to attach the interface to server.
Change-Id: If0ae14a86005da06dc35620c2af47f37112228d5
Closes-Bug: #1375132
According to new PowerVC neutron locked port logic, adding magic device
id to PowerVC neutron agent synchronization logic.
Change-Id: I4366cd91c31388a77e08848021afd202661bbed3
To adapt to new configuration files.
Check blueprint new-configuration-strategy-needed-to-adapt-to-oslo-messaging
Closes-Bug: 1370337
Change-Id: Ic8e624206490680de07827613d4474bac62686a9
(cherry picked from commit ba29f897db)
This is based on Oslo messaging API that supports RPC and notifications over a
number of different messsaging transports.
* remove old powervc.common.messaging and create a new one to adapt to Oslo
messaging
* adapt all sync service managers to new messaging model
Change-Id: I0c9b4a9fa5bb5d0eaac1433e768a110871d8dab8
Closes-Bug: 1363618
* Extract and remove --config-file amqp_openstack.conf(or
amqp-openstack-neutron and --config-file amqp-powervc.conf from sys.argv to
create 2 AMQP cfg.ConfigOpts objects without conflicting with other options
parsing as before, particularly those OpenStack AMQP configurations in
[DEFAULT] section of nova.conf, cinder.conf.
* adapt all affected code to the new config strategy
Implements: blueprint
https://blueprints.launchpad.net/powervc-driver/+spec/new-configuration-strategy-needed-to-adapt-to-oslo-messaging
Closes-Bug: 1356225
Change-Id: I61a4fd0c28148e31a8cb85acea3793f40028dfb4
neutron removed the capability to auto generating the table schema and
use the alembic as the only way to create the db tables. powervc neutron
agent needs to follow the same way to create the tables schema and it
also added the db schema migration capability for powervc neutron agent.
As db2 alembic has problem at this time, I still retain the auto create
the table schema during startup, once db2 alembic is enabled, then we
can totally switch to use alembic to create the db schema
Change-Id: I4b5982b2f67b33aae3b8acc65b91fc6247b9b8a4
There are some flake8 issues in each component that are not based
on coding style rules .
And There are some unittest issues in some component that need to
be fixed
Change-Id: Ic9a3f2c3b779ced225a42f69a495a606cb62517e
Closes-Bug: #1350160
Implement boot VM with created neutron port include below changes:
1. Add get_port_uuid() rpc method in neutron to map the powervc uuid for
the local neutron port
2. Specify the 'port-id' in nova-powervc's driver spawn method for the
corresponding PowerVC port UUID from the requesting port-id from the
request.
Closes-Bug: 1350161
Change-Id: I4bc574c20ac06b625cd7111c4184b48cddbd7f64
Previous neutron.openstack.common.rpc is removed in Juno. Replace it
with neutron.common.rpc
Closes-bug: 1336131
Change-Id: Ibb7f7b5109476237df783e4cdd62ba9f5e264640
terryyao