as in nova side we tried to update image property and this is
always allowed by default, we thought it's an error, but actually
it's acceptable since next time we will do that again.
Change-Id: I82f538aaad8882a5b96c3cec1f4781bd91c5944b
Reraising an error would interrupt the process of removing
resources from the failed instance, and then make some resources
keep being occupied even after the instance has been deleted.
Change-Id: Id79eb4d58618987d9ae5e98a66f8339c423b4c4d
we need do some changes according to zvm_default_admin_userid
zvm_default_admin_userid will be the primary conf options from
then on.
part of blueprint:add_zvm_default_admin_userid
Change-Id: I666262895acdf3b8972f6ac0a5a3a6f228836d6f
zvm_user_default_password is not secure and we will use LBYONLY to
replace it and deprecate zvm_user_default_password.
part of blueprint:add_zvm_default_admin_userid
Change-Id: Ife905eb4499ccb7bbbdd8bbba75fc425e560606e
Currently, nova zvm virt driver is in nova namespace. This result
in some troubles when generating config file, generating docs and
packaging.
All changes in this commit are trying to move nova zvm virt driver
code into new namespace - nova_zvm .
Change-Id: I5251069dfd24ff4e337e9308439415482eb2234c
after this document, people is able to view what's supported and
what's not support.
part of blueprint: zvm_doc_update
Change-Id: Id1d57dd501e44c6e7c2a253378f269eebc1b507b
When boot-from-volume fails, its instance_fcp_map should be updated
correctly. Unfortunately, current code is wrong and will lead to an
error raised.
Change-Id: I7aa65d551b435e0600a40e652478a1fb775d5ca1
after this ,user is able to explore the configurations of
nova zvm driver supported.
part of blueprint:zvm_doc_update
Change-Id: Id58b5a5d9ebb7a9304e150e4c0471046ff6b1620
Right now, if delete userid failed due to image lock or device
lock, zvm driver has a looping call to check lock status with 10
minutes timeout.
Normaly, the image or device was locked by disk related actions
which could not be unlocked in short time. So turn to call
image_unlock_dm try to unlock it. Then try to delete the vm again.
Change-Id: I848d042231757d8673700e3db2b46f8fc9757596
Now the root_disk_units just has disk size in it. It doesn't have
units. So if customer specify a dismatch disk type, the driver
will not detect it until the create disk prompt the space is not
enough. This patch add units to root_disk_units, so it can give
customer clearly advise if error happens.
Change-Id: I1a31aa4bf77b774092fd04cc7174599252757538
zvm_default_admin_userid will be added and user is able to
log on cloud created user through this ID.
the old zvm_user_default_password will be removed in the near future.
part of blueprint:add_zvm_default_admin_userid
Change-Id: I8938669af3103df2e6f51cee1de458a6be339154
REST API layer might return 503 error, this means server is
temply not available, instead just fail, we can retry the work
as our REST calls are sync call, so no harm to retry it
as we can't retry forever, add a retry max count so that at
last we will still fail out.
Change-Id: I1e484265d241c87d2f0060f0aaef19cb6314ed4f