On Tue, 5 Apr 2011 14:24:32 -0700, brett lentz <brett.lentz(a)gmail.com> wrote:
My problem with ksmeta is that it ends up being a dumping ground for
a
myriad of meta-information. It would be preferable to have information
specific to a config management system clearly identified and
separated out, similar to the way network interfaces are expanded.
True, but breaking out this one field doesn't really help the situation
much.
It also doesn't help that the WebUI and CLI parse changes to
ksmeta
completely differently, and updating a system through the WebUI is
liable to break even a moderately complex use of ksmeta.
This, we should probably fix. Can you give me an example of what
happens?
--
Scott Henson
Red Hat CIS Operator
WVU Alum BSAE/BSME