The way I see "openstack_project" manifests it's how Openstack infra servers are organized, i.e. a 'review' server would have a Gerrit, a Gerritbot, so on and so forth.
IMHO, site specific data should be either provided on site.pp or use facter wherever suitable. Host names and paths should change at some point, I think it is better if we provide those values outside of the "openstack_project" and avoid hardcoding-values for a better reuse of manifests.
This enhances the experience of developers willing to use layouts as "openstack_project" for testing or work on bugs about openstack-infra itself (I opened this bug while I was working on other openstack-infra launchpad-gerrit issue, had too many things to tweak to have a sane 'review' server in a local VM).
Hi Liz
The way I see "openstack_project" manifests it's how Openstack infra servers are organized, i.e. a 'review' server would have a Gerrit, a Gerritbot, so on and so forth.
IMHO, site specific data should be either provided on site.pp or use facter wherever suitable. Host names and paths should change at some point, I think it is better if we provide those values outside of the "openstack_project" and avoid hardcoding-values for a better reuse of manifests.
This enhances the experience of developers willing to use layouts as "openstack_project" for testing or work on bugs about openstack-infra itself (I opened this bug while I was working on other openstack-infra launchpad-gerrit issue, had too many things to tweak to have a sane 'review' server in a local VM).