This is due to the changes made to handle the
community change where V1 glance API got removed
with Queens release of openstack. And, with V2
the response format has changed returning fewer
properties.This bug is to fix the issue related
to missing custom properties and add them back
to be displayed to the user.
Change-Id: I116ad05b00de6e94cf6c507dbcffa607b916fc42
Closes-Bug: #1814739
With the Queens release of Openstack, the community removed the
support for v1 glance API. Thus, we need to fix the corresponding
implementation in the PowerVC Driver using glance v1 calls to v2 calls.
As part of these changes, we've removed all the v1 glance client calls
to v2, and also observed that the response format has changed as well
and these changes should address all of that.
Change-Id: Ic76bad59ba3da7178acaeeb093113358e50c6169
Closes-Bug: #1783096
Do not sync bdm from pvc image to local image properties,
neither do sync from local to pvc, or it will break on both
pvc side and local os side.
Change-Id: I0bdd124c8e3897917050c6927e20ab358f30b65e
Closes-Bug: #1438547
oslo.messaging is exposing a new API allow creating listener by
supplying a pool name, then the listeners with that pool name will use
the queue name as the pool name, multiple listeners can be listening
with the same topic.
Change-Id: I220d50fad8cda6f6f50f31215a7a6b98523c35dc
Closes-Bug: #1388663
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 select an SCG / Storage Template , we add an extra
propertity to image properties , UI could use this data to format
the data for user to select the specific SCG / Storage Template ,
and also, other components which consumes PowerVC images in
Openstack can also leverage this.
Change-Id: I4b9dba719dada3823dc159748d15a3266ca9efa3
Closes-Bug: #1362904
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
Currently, powervc driver image sync service will sync the powervc image
meta properties to hosting openstack side, it's using
HTMLParser.unescape() to unescape the escape chars. It's over used, only
"<", and ">" that corresponding escpae char is "<" & ">" is needed
to be unescaped. Fix this only to unescape this two chars.
Closes-Bug: #1362886
Change-Id: I11db0cab46c8707a6c306f9967d7afc08fbad3ec
In Juno Release , there are four files in the Glance Component deleted
in the directory "glance/openstack/common" , based on
c3ff558fc0,
but glance-powervc driver need the ServiceLauncher to launch the driver service ,so
it starts failed.
The solution is to change to user nova ServiceLauncher to launch the
service by modifing import path in the file bin/glance-powervc and
manager/manager.py
Change-Id: I2f6ec46fbb098043ad9721155b0c640fbde25df0
Closes-Bug: #1337186