hmmm...
MySQL only supports two databases sharing master-master replication, however you could setup the database nodes of the other clusters to be slaves to the 'primary' (for lack of a better term) cluster's database of their local datacenter.
You would need to have discipline to only make changes to cluster that spans the datacenters (the others could be in a single datacenter). Though you might end up with collisions on the audits and metrics. You can off-box the audits (or disable them) to prevent those, but not sure if you can disable the metrics. Also you would want to keep an eye out for the tables with cluster data in them, but I think those should be ok.
It might be easier to just run a sql script to push the relevant tables' data across to the other clusters' databases, and if you export/import to sync them up first then all the index keys will match so you won't have to worry about any broken object references...
You could script the whole thing using CMT/WSMan (GMU) as Gopinath suggests but personally I think it may be easier to just deal with the database because if you can get master-slave replication or an event trigger working to your non-primary clusters then it becomes fully automatic... You may also need to keep an eye on the sql bin and reley logs...