5c1dacbd81
puppet-lint expands symbolic links and use the realpath when checking for the location of manifests. This means the autoloader_layout check still fail although we tried to force the correct folder name by using a symbolic link named after the puppet module. This change brings two changes. It now copies all files to a new folder named after the puppet module. Rsync is used for the copy process. The destination folder is excluded and so are hidden folders such as .git. It also uses an alternative method to determine the module name by reading the 'name' field from the Modulefile. This allows a puppet module repository or project to be renamed without breaking puppet-lint. An example of such use case would be a rename of puppet-quantum to puppet-neutron. If the Modulefile is not found or the name cannot be determined, the puppet-lint builder falls back to its default behavior which consists of running puppet-lint in the root of the workspace. Change-Id: I6158ab3b32499820b7d09db7b31d4226650af8ae
These are a set of puppet manifests and modules that are currently being used to manage the OpenStack Project infrastructure.
The main entry point is in manifests/site.pp.
In general, most of the modules here are designed to be able to be run either in agent or apply mode.
These puppet modules require puppet 2.7 or greater. Additionally, the site.pp manifest assumes the existence of hiera.
See http://ci.openstack.org for more information.