Add project_id kwarg as part of the call to deduct quotas
during unregister volume. This will make sure the
deduction happens for the correct project to which
the volume actually belongs to in ICM.
Change-Id: Ib0596aef1b2fde4da0c8164141d39dae2ece4c94
Closes-Bug: #1712093
Fix for volume description is moved from property "display_description"
to "description" for master Edit
Change-Id: I566fb3c18823552becc267be5f0dd31d52694df5
Closes-Bug: #1545973
List all resources across different service by adding "all-tenant"
when call restAPI
Change-Id: Ie29e0bac6fa4c3fe4b771489a722b6712edc3a28
Closes-Bug: #1496781
Cinder duplicated volume deletion, which will cause multiple quota
deduction.
Change-Id: I5e970cdb682abac51599b4da93b325fc0707c8f5
Closes-Bug: #1494561
quotas are not updated when the volumes/instances are synced from
powervc side, this fix help to sync the quota during sync resources
from powervc side, increase quota when insert to local resource,
deduct quota when delete local resources.
Change-Id: Ic5a77e7d154b247d253db19d59ee66a7aa473995
Closes-Bug: 1493232
This bug tracks the implementation for volume sync and create/attach/detach
for multiattach function. Host status update also fixed along with this bug.
Change-Id: I45a776775473818c75388c3554664982849c4fae
Closes-Bug: #1491723
From PBC, the customer encounter below error:
1. Create a volume in ICM
2. Update PowerVC UUID in cinder volume metadata, in the mean time,
PowerVC volume created, end event comes.
3. Check if PowerVC UUID set in volume metadata, but there is
Time window issue here, sometimes db update not reflect
immediately, so no PVC UUID found , and create a duplicated
volume by mistake.
Change-Id: I4e5546034dbf3ff50c2db588e948818431a665c6
Closes-Bug: #1472126
This is due to get_local_volumes api changed from community, it always
cannot get local volume from db(empty list []), so driver attempts
to insert new volumes every time restarted or periodically sync.
Change-Id: I225394bfaff2229dbb93caa69e067154c608c15a
Closes-Bug: 1435121
This is due to glanceclient update. The glanceclient.common.http.HTTPClient
requires a string, but after the changes commited above,
the tuple is returned and causes the parameter mismatch.
Searched all related potential errors and found only this one. Will fix this on kilo release.
Change-Id: I3afef5ceee57b0c1aeb57696c7f73262f3bf16f1
Closes-Bug: 1407567
1. Move the wait volume state logic from nova to cinder
2. Wait volume state to be "in-use", then complete volume attachment
3. Change volume sync code to not sync "attaching" or "detaching" state
as if sync code change such state, then volume attach/detach will be
broken
Closes-Bug: #1402467
Change-Id: I3640afe9ad4aba8788a932d05e94f55a3b8d6333
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
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
Openstack in cinder-powervc
Currently cinder service uses threading instead of eventlet's event,
This causes if you don't monkey patch threading, it will hang there
all the time. For detail, check this fix in incubator project:
https://github.com/openstack/oslo-incubator/commit/\
1e7007824374842bc8108dff5e5e2694e12932b2
Will create a bug to cinder to fix this. Temporarily fix is to replace
cinder service instead of nova service in 1365373.
Change-Id: Ibe770e51563f43495228d84dd6d0284a62bba9e8
Closes-Bug: #1365373
PowerVC cinder driver __init__ does not call it's super's __init__,
and latest cinder driver change result in cinder-volume can not be
started due to this reason.
Closes-Bug: #1363846
Change-Id: I4743513b115fd02521fac546985981ea5197527c
To enhance the code to fetch volume display_name for latest PowerVC
If fetched "display_name" is empty then fetch "name" instead, if
still empty then just display local os as empty as previous.
Change-Id: I43161b50d153d9ed3750f8a2ea740c0dce633e35
Closes-Bug: #1363846
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
arunmani