On 08/22/2012 10:19 AM, Daniel Pocock wrote: > I've started a branch for sending UUID instead of hostname > > This necessitates change to the XDR packet format, but it is backwards > compatible > > Nonetheless, it is not desirable to change the XDR format regularly, so > it would be good to know if there are other XDR changes people would > like to integrate for eventual release in 3.5.x? Then all such changes > can be combined in one go. > > The UUID branch is described here: > > https://github.com/ganglia/monitor-core/wiki/UUIDSources >
I'm a little confused how this is backwards compatible change. My reading of the wiki page is that HOST/@NAME will be set the the UUID, and the hostname itself will not be present. How will this not break the UI and anything else consuming the gmetad looking for hostnames? Regardless of compatibility, how are applications to maintain a hostname<-->UUID mapping? Why not have a new HOST/@UUID field? ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-developers
