Currently the size in backup is src volume size rather than backup
file/object size, it's used to record original volume size that avoid
damaging target in restore operation if the volume has been resized.
But it may be more useful for end user to tell them backup files/objects
size(object count
Hi,
Currently, I find our RPC client always need create a new callback queue
for every call requests to track the reply belongs, at least in Newton.
That's pretty inefficient and lead to poor performance. I also find some
RPC implementations no need to create a new queue, they track the request
ease see mistral-actions
<https://github.com/int32bit/mistral-actions>.
It work well on our environment but not sure if there is any potential
risk. Thanks for any suggest and comment.
[1]
https://docs.openstack.org/developer/mistral/developer/creating_custom_a
Hi,
I am trying to deploy cinder-backup service and c-vol uses multi-backend,
the configuration as follows:
...
enabled_backends = ceph1, ceph2
backup_driver = cinder.backup.drivers.ceph
backup_ceph_conf=/etc/ceph/ceph.conf
backup_ceph_user = admin
backup_ceph_chunk_size = 134217728
Hi, All,
I'm a newcomer to Openstack Ironic. Recently, I'm work on deploy ironic
manually, and I found that the node status 100% *blocked in `callback wait`
status* until timeout. The ironic-api log shows that:
2017-01-12 10:21:00.626 158262 INFO keystonemiddleware.auth_token [-]
Rejecting
Hi, all. As we know, the "index()" method usually return object list and
the "show()" method return an object for detail in api's controller. But I
found in our InstanceUsageAuditLogController[1], the 'index' method return
an object, I'm really not sure that index() is buggy, and I wonder what it
