| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Use the "keystone-manage bootstrap" command to instead of admin_token.
Because the admin_token is treated as a "shared secret" that can be used
to bootstrap Keystone through the API. This "token" does not represent a
user (it has no identity), and carries no explicit authorization (it
effectively bypasses most authorization checks).
Use the API v3 to instead of API v2.0. Identity API v3 was established to
introduce namespacing for users and projects by using "domains" as a
higher-level container for more flexible identity management and fixed a
security issue in the v2.0 API (bearer tokens appearing in URLs).
JIRA: COMPASS-491
Change-Id: I56182c14b761728c3492b9dd2b05c3b57aa5f35f
Signed-off-by: liyuenan <liyuenan@huawei.com>
|
|
JIRA: COMPASS-491
Change-Id: Ibca46dca0ca614b9a6e7eb3fe5b9d5c8ca26c006
Signed-off-by: liyuenan <liyuenan@huawei.com>
|
|
- add recovery shell scripts
- add boot-recovery role to stop services during system boot which
could cause boot pending
- configure nfs mount in /etc/fstab cause system boot pending,
so mount nfs during ansible-playbook run.
- kill mysqld before mysql recovery, running mysqld may cause mysql
recover failure
JIRA: COMPASS-474
Change-Id: I0f6f0ee935fbe3fbbe28a451a02decfb01a6165b
Signed-off-by: QiLiang <liangqi1@huawei.com>
|
|
JIRA: COMPASS-491
Change-Id: Id3ae5b254d06766a74140ec0b13608eb67339e29
Signed-off-by: liyuenan <liyuenan@huawei.com>
|
liyuenan
QiLiang