Goal: 

• As it already happened with infrared, people may need to pass private configuration information (credentials or internal IPs for storage appliances, for example). when deploying the overcloud. Right now, the way to define a 17.1 scenario with ci-framework forces people to list all required configuration files and doesn't allow people to pass a private configuration file.

For example, something like:

--
parameter_defaults:
    ManilaNetappDriverHandlesShareServers: 'false'
    ManilaNetappEnableBackend: 'true'
    ManilaNetappLogin: 'foo'
    ManilaNetappPassword: 'bar'
    ManilaNetappServerHostname: '<some_ip>'
    ...
    CinderEnableIscsiBackend: false
    CinderEnableNetappBackend: true
    CinderNetappBackendName: 'somebackend'
    CinderNetappLogin: 'auser'
    CinderNetappPassword: 'apassword'
    CinderNetappServerHostname: '<some_other_ip>'
    ...

Acceptance Criteria:

Users should be able to pass a private THT configuration file when deploying OSP 17.1 through ci-framework.