Browse Source

Use login-defs role from tripleo-ansible in sc004

Add login-defs role to be in scenario004 and use it
from tripleo-ansible.
Depends-On: https://review.opendev.org/670768
Change-Id: I825ca49fb1fbf778fa5e5e62385ee4753424612c
changes/69/670769/7
Sagi Shnaidman 2 years ago
parent
commit
2ae95677fe
3 changed files with 11 additions and 9 deletions
  1. +1
    -0
      ci/environments/scenario004-standalone.yaml
  2. +9
    -8
      deployment/login-defs/login-defs-baremetal.yaml
  3. +1
    -1
      environments/login-defs.yaml

+ 1
- 0
ci/environments/scenario004-standalone.yaml View File

@ -25,6 +25,7 @@ resource_registry:
OS::TripleO::Services::PacemakerRemote: ../../deployment/pacemaker/pacemaker-remote-baremetal-puppet.yaml
OS::TripleO::Services::Clustercheck: ../../deployment/pacemaker/clustercheck-container-puppet.yaml
OS::TripleO::Services::MySQL: ../../deployment/database/mysql-pacemaker-puppet.yaml
OS::TripleO::Services::LoginDefs: ../../deployment/login-defs/login-defs-baremetal.yaml
OS::TripleO::Services::Keepalived: OS::Heat::None
# NOTE(mmagr): We need to disable Sensu client deployment for now as the container health check is based
# on successful RabbitMQ connection, which does not happen in this case. We can enable it again when we


deployment/login-defs/login-defs-baremetal-puppet.yaml → deployment/login-defs/login-defs-baremetal.yaml View File


+ 1
- 1
environments/login-defs.yaml View File

@ -1,5 +1,5 @@
resource_registry:
OS::TripleO::Services::LoginDefs: ../deployment/login-defs/login-defs-baremetal-puppet.yaml
OS::TripleO::Services::LoginDefs: ../deployment/login-defs/login-defs-baremetal.yaml
parameter_defaults:
PasswordMaxDays: 60


Loading…
Cancel
Save