Juju needs to enforce configuration sanity

Bug #804202 reported by Marc Cluet
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
pyjuju
Confirmed
Wishlist
Unassigned

Bug Description

If Juju is deploying an application it should be able to ensure that the configuration files for such application are not modified locally on individual machines, at least it should have the option to do so.

This is crucial for proper sysadmin and control of your running applications.

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Confirming. Actually, I'd really like to see etckeeper configured and used by default on these systems, set to track configuration changes in a version control system like bzr.

Changed in ensemble:
status: New → Confirmed
Revision history for this message
Gustavo Niemeyer (niemeyer) wrote :

This is a nice all-encompassing goal which we have to pursue over time, while keeping in mind the model adopted by Ensemble to deploy and manage software over time.

One aspect, for instance, is that the authoritative data for a service is not in the filesystem, but within the environment metadata which today lives within ZooKeeper. The Formula is supposed to apply that information into the deployed service in a preferred way within the config-changed hook. Over time, we'll develop best practices and enhance the way that such configuration takes place and is monitored.

Marc Cluet (lynxman)
summary: - Ensemble needs to enforce configuration sanity
+ Juju needs to enforce configuration sanity
description: updated
Changed in juju:
importance: Undecided → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.