cdddf60c5f
The files and templates we carry are almost always in a state of
maintenance. The upstream services are maintaining these files and
there's really no reason we need to carry duplicate copies of them. This
change removes all of the files we expect to get from the upstream
service. while the focus of this change is to remove configuration file
maintenance burdens it also allows the role to execute faster.
* Source installs have the configuration files within the venv at
"<<VENV_PATH>>/etc/<<SERVICE_NAME>>". The role will now link the
default configuration path to this directory. When the service is
upgraded the link will move to the new venv path.
* Distro installs package all of the required configuration files.
To maintain our current capabilities to override configuration the
role will fetch files from the disk whenever an override is provided and
then push the fetched file back to the target using `config_template`.
Change-Id: I8fba4a1f70d7f5870ad81c8a84e3b1d15742c70f
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
|
||
|---|---|---|
| .. | ||
| providers | ||
| dependent_neutron_roles.yml | ||
| main.yml | ||
| mq_setup.yml | ||
| neutron_check.yml | ||
| neutron_db_setup.yml | ||
| neutron_install_source.yml | ||
| neutron_install.yml | ||
| neutron_l3_ha.yml | ||
| neutron_ml2_ovs_powervm.yml | ||
| neutron_post_install.yml | ||
| neutron_pre_install.yml | ||
| neutron_selinux.yml | ||
| neutron_service_setup.yml | ||