Comment 3 for bug 1595228

Being able to tell what version of TripleO deployed an overcloud given only information on one of the overcloud nodes is likely impossible at the moment. Though it could definitely be useful to know if TripleO was used at all, and if so, what version of the heat templates was used for deploy.

Checking package versions won't help, because packages are installed at image build time and not deploy time. It is pretty unlikely that someone successfully deployed mismatched tripleo-heat-templates and overcloud puppet modules, but this feature would be most useful in the unsuccessful case.

I think puppet-tripleo would have a similar issue, in that it is installed in the overcloud image at image build time rather than deploy time.

That leaves tripleo-heat-templates. Adding something there that writes /etc/tripleo-release to the overcloud nodes seems like it would not be too hard to implement, and would solve this use case. It could even go a step further and write the templates/environments that were used to deploy the cloud somewhere on the overcloud, but maybe that is overkill.

I would also like to solve the corollary use case of determining what version of OpenStack is actually installed (vs. what version of OpenStack ran on the installer), but that would be better solved by packaging.