----- Original Message -----
> On Tue, 2 Jul 2013 06:50:47 -0400 (EDT), Nathan Scott
> <nathans@xxxxxxxxxx> wrote:
> > ----- Original Message -----
> >> Also, most cloud provides (including AWS/EC2) do not permit
> >> multicast
> >> in it's entirety.
> >
> > Are there auto-discovery alternatives to Avahi that these cloud/other
> > systems provide that is comparable? (not multicast, but proprietary
> > protocols I guess?)
>
> Not really that I have seen. Most seem to invent their own way of
> discovery. For example, elasticsearch uses the AWS web APIs to query
> information about it's nodes if you are using the "ec2" discovery
> plugin.
I had the same thought, wondering "what would batman^Welasticsearch do?"
and I came across this...
http://www.elasticsearch.org/blog/here-comes-the-cloud/
which has an interesting aside in the very last sentence, suggesting that
"jcloud" is the way its achieving cloud-agnostic integration nowadays (the
link there bounces, http://jclouds.incubator.apache.org/ is it now).
For PCP, I think that suggests we should definitely keep the separation of
the Avahi-based discovery (so separate daemon, separate rpm) and consider
also at some point looking into a java-based auto-configuration mechanism
(could not find a C/python equivalent) for clouds.
So, perhaps separate pcp-avahi-server, pcp-jcloud-server, pcp-xxx-server
mechanisms - all bog-simple servers that just catch messages from the
network/cloud about new hosts, and write to /etc/pcp/pm*/control.d/ ...?
Then other already existing PCP pieces take over and make the real magic
happen.
cheers.
--
Nathan
|