Changes to 'tags' etc..

[andrewwatson]

How open are you guys to thinking about alternate tagging for service nodes?

For my purposes, I'd really like to be able to tag a node as running both a macro version of a service (Authentication v2.0 for example) and also possibly versions of specific messages (whether it's REST HTTP JSON or protocol buffers or amqp envelope bodies...) and then be able to resolve something like this by having some things have default values...

client_grant.v1.authentication.v2.us-west-1a.consul 
client_grant.authentication.us-west-1a.consul
authentication.consul

and being able to publish serf tags as appropriate to create these records.

what do you think?

[andrewwatson]

Changing this up a bit after some IRC...

Would like to be able to submit multiple tags and have all nodes that match certain tags get round robin.

Example:

If node A uses ["client-grant-authorization", "client-grant-authorization-v2", "authorization"] and node B used ["authorization"] then a DNS query for authorization.consul would round robin between both