----- Original Message ----- > From: "Stéphane Klein" <[email protected]> > To: "users" <[email protected]>, [email protected], > [email protected], [email protected] > Sent: Tuesday, 15 November, 2016 9:44:22 AM > Subject: Why Metrics and Logging use Deployer container? > > Why Metrics and Logging use Deployer container? > > * https://github.com/openshift/origin-metrics/tree/master/deployer > * > https://github.com/openshift/origin-aggregated-logging/tree/master/deployer > > I think it's too difficult to hack, why don't use only Ansible for that?
The deployer containers are going to be deprecated as we move over to Ansible for this. Expect an update for this soon. > > I think there are too many layers to install this components (Metrics and > Logging): Ansible + Dockerfile + deployer template… > > If I want hack Metrics template I need: > > * fork origin-metrics > * update OpenShift config file objects > * rebuild Docker image > * upload to registry > * change metrics prefix image > * execute playbook > * fix my errors and restart to step 2 > > Why this complexity? Normally I would just say to deploy metrics and then modify the templates afterwards. Its not ideal, but it might be a bit easier than what you are currently doing. We also don't necessarily want people to be modifying the templates directly either and that can cause problems when you need to upgrade to a new version that is going to have new and different templates. This is why we want users to specify options for the deployment instead of modifying templates directly. Is there any features we are missing that you are needing to make changes for? > > Best regards, > Stéphane > -- > Stéphane Klein <[email protected]> > blog: http://stephane-klein.info > cv : http://cv.stephane-klein.info > Twitter: http://twitter.com/klein_stephane > _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
