As stated below, the following patch addresses the VM recovery in this and
few other scenarios: https://review.openstack.org/#/c/11086/
Also, there is another patch which can be used to simplify failure
detection: https://review.openstack.org/#/c/10903/
Unfortunately, neither of the two made it f
BTW, here is my configuration:
[ldap]
url = ldap://10.64.11.199
tree_dn = cn=accounts,dc=mydomain,dc=com
user_tree_dn = cn=users,cn=accounts,dc=mydomain,dc=com
user_objectclass = person
user_name_attribute = uid
user_id_attribute = uid
tenant_tree_dn = cn=groups,cn=accounts,dc=mydomain,dc=com
tena
Hi all,
I have a problem to consult, this problem occurs in _create_image when I boot a
new instance(someone else may boot one at the same time).
The instance UUID of mine is e8752971-d390-450f-a083-819b7716fd53, and it
booted failed, the other instance UUID is 79e7b88f-2302-4387-a27e-ffdbd483f6d
Thanks qiujian!
By using this configuration, can we log in through dashboard? If I want to
implement that, is there any other configuration I have to do?
2012/9/24 邱剑
> BTW, here is my configuration:
>
> [ldap]
> url = ldap://10.64.11.199
> tree_dn = cn=accounts,dc=mydomain,dc=com
> user_tree_dn
4 matches
Mail list logo