Hi Isaac
From my point of view, we should choose between one way or another, I
find it can be confusing to support both options. I'd prefer templating
the file, but not only adding the memory parameter here, but make it
fully customizable so we remove the need to pass an external file.
Any other thoughts there?
El 11/01/16 a las 13:13, Isaac Beckman escribió:
Hi,
openstack-infra/puppet-jenkins holds a default file with the
configuration of jenkins master (/etc/default/jenkins).
Many times, this file needs to be customized in order to fit
downstream projects.
For example, one of the attributes in this file is the heap size
assigned to JAVA. By default it is 12G which only _large busy sites_
will need.
Customization of this file by downstream can be done by either using a
different default file or alternatively we can turn this file into a
puppet template that can be used dynamically.
Each option has its own cons & pros.
For example: It is simpler to use different file, but this option is
not good for a project with multiple jenkins masters each with
different system resources.
According to Yolanda, discussion about passing an external file Vs
customizing the default file in a template, took place in the past.
I would like to get a feedback and information from people who were
involved in this discussion in order to figure out what is the
preferred solution in this case.
Thanks,
Isaac Beckman
IBM XIV, Cloud Storage Solutions (previously HSG)
www.ibm.com/storage/disk/xiv
_______________________________________________
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
--
Yolanda Robla Mota
Cloud Automation and Distribution Engineer
+34 605641639
yolanda.robla-m...@hpe.com
_______________________________________________
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
