Putting a UUID in a field called 'HOST' seems backwards-incompatible to me. You're changing the meaning of the HOST field, even if the data type remains the same.
I'd favor reserving 'HOST' for a hostname, and adding a 'UUID' field to the XML for UUIDs. On Aug 22, 2012, at 10:02 AM, Daniel Pocock wrote: > Actually, there will be an option for that in gmond.conf, so it can be > deployed in either of two ways, depending upon what is needed by the admin: > > a) put UUID in HOST/@NAME (so that XML schema does not change) > > b) put UUID in some new attribute Making this configurable seems like unnecessary complexity. Wouldn't the web UI then have to know which mode gmond is running in (and support either), or would gmetad normalize this somehow? alex ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
