Hi guys,
1. I set the conifg deferred_auth_method with value trusts, so a trust
record will be created in keystone when creating a stack, and heat save the
trust result to db.
2. Delete the stack, if all resources has been deleted successfully, heat
will delete the trust record in
Hi guys,
I get some resources by creating a stack, e.g. ,the resources may be 2
volumes, volume A and volume B. If the volume A and volume B are useless, we
can delete them by deleting the stack , we also can delete them by cinder.If
they are deleted by cinder, though the volumes have
Hi guys,
I find a interesting problem in Juno version.
First, I create a new stack, it contains three resources, e.g. (In my
test, there are six resources)
heat_template_version: 2014-10-16
resources:
volume1:
type: OS::Cinder::Volume
properties: {name: test1, size:
Hi guys,
When creating volume type, extra_specs is optional in body, as can be seen
from API document, http://developer.openstack.org/api-ref-blockstorage-v2.html
but I notice that in cinder-client, the method of create in
VolumeTypeManager dose not take extra_specs in body,
Hi guys,
I created a stack with several resources, for example, resource A,B,C,and B
depends on A, C depends on B,.Now I delete the stack , then heat would delete
resource C, then resource B, at last, resource A, isn't it?
Suppose that the resource C has been deleted, but an error occurred
Hi guys,
I'm using cinder-clinet to backup a volume and query the status of the
backup-volume in a loop per 3 seconds. I got the token from keystone when I
begin to backup the volume,assuming that the token is expired in 2 minutes, but
the backup need 5 minutes to finish, so after 3 minutes
