Hi, Recently I starting looking at how we implement password changes in an existing deployment, and found that there were issues. This made me wonder whether we needed a test job to confirm that password changes (and other config changes) are in fact executed properly.
As far as I understand it, the way to do password changes is to - 1) Create a yaml file containing the parameters to be changed and their new values 2) call openstack overcloud deploy and append -e new_params.yaml Note that the above steps can really describe the testing of setting any config changes (not just passwords). Of course, if we do change passwords, we'll want to validate that the config files have changed, the keystone/dbusers have been modified, the mistral plan has been updated, services are still running etc. After talking with many folks, it seems there is no clear consensus where code to do the above tasks should live. Should it be in tripleo- upgrades, or in tripleo-validations or in a separate repo? Is there anyone already doing something similar? If we end up creating a role to do this, ideally it should be deployment tool agnostic - usable by both infrared or quickstart or others. Whats the best way to do this? Thanks, Ade __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev