That does sound interesting. However,
it also reminds me of RFC 1925:
http://tools.ietf.org/html/rfc1925
in particular "6a - It is always possible to add another level of
indirection.
" and perhaps #11 as well... Lots of wisdom in the old IETF...
I really liked your talk about what you'd done with Epiphyte - in
particular making hard things easy. Very impressive work. Is there
some way to organize this by starting from the "hard" use cases
NDS labs is trying to address, and drill down to the technology
components really needed to make that happen? Discovery does seem
likely to be a good part of it, but if it's based on key-value
pairs (for example) how does the user know what keys to query, who
sets the standards for those keys and meanings of corresponding
values? Aside from knowing where exactly the etcd server or
whatever is doing that work is. There's got to be some base
starting point, a system that knows enough to help the user do
things, can we work from there?
ÂÂ Arthur
On 10/30/14, 11:42 AM, Matthew Turk wrote:
Hi all,
In the other thread, Arthur brought up that we don't want
"just another cloud infrastructure," which I think was really
apt, and something that deserves thought for any NDS Labs
project. So I wanted to start a couple topics about what can be
provided on top of a standard cloud infrastructure that might be
of use.
I'm wondering about discovering data services within a
region, where that region is either some subnet on a cloud
provider, or even more globally across locations. If we are
thinking about interoperability of services, then there are
probably a few verbs that could be identified as being
necessary. If we can have services identify themselves as
providing verb endpoints, that could provide an environment for
testing interop.
Kacper and I have been experimenting with this ourselves,
mostly looking at the various service discovery mechanisms that
operate on docker containers being orchestrated across
machines. Some of these do this via introspection, and some
will even set up automatic (nginx) reverse proxies for docker
containers running inside a system. Right now it looks like
etcd is a pretty good solution for this:
as it can allow for key/value pairs to be stored, and it's
discoverable. For instance:
I think having a discussion about what we want services to be
able to do is perhaps a much bigger topic, but I wonder if this
type of thing -- particularly etcd -- would be useful to any
projects, and would be a good avenue for service discovery and
intertop. Is there something else that would be better?
-Matt