On Tue, Apr 5, 2011 at 3:15 PM, Scott Henson <shenson(a)redhat.com> wrote:
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.
Rome wasn't built in a day. ;-)
I see this as an incremental process of obtaining feedback of what
ksmeta is used for, and making a decision of whether ksmeta is the
right place, or if a better home for it can be found/built.
> 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?
My ksmeta for one profile looks like this:
ks_meta : somevar=foo othervar=0 autofs_master=foo.auto.master
zabbix_server=10.0.0.1,::ffff:10.0.0.1,10.0.0.2,::ffff:10.0.0.2
ntp_servers=10.0.0.3 xen=false
tree=http://@@http_server@@/cblr/links/CentOS-5.3-x86_64
zabbix_proxy_server=10.1.0.1
puppet_server=puppetmaster.prod.loc.domain.com anothervar=0
ldap_servers=ldap://ldap01.prod.loc.domain.com:1234,ldap://ldap02.prod.loc.domain.com:1234
morevars=['foo', 'bar', 'baz']
So... the problem is, where ever there are quotes, or multiple
variables in an array, or a comma-separated list... the WebUI displays
this in a form that, if it's submitted without editing, is parsed
*completely* differently. The commas end up causing half of the value
from one variable to be stored as a totally new and distinct variable.
In short, it makes the WebUI only useful in a read-only context.