Define per-service mixerclient runtime configuration (#218)
Define per-service mixerclient runtime configuration (#218)

A single mixerclient may serve multiple destination services. Aspects
of runtime configuration must therefore be defined per-service,
e.g. Quota, APISpec. Express this per-service configuration as a map
of config elements indexed by the fully qualified destination service,
e.g. destination.service.

As an implementation note, the mixerclient could derive
destination.service using the `host` header. Alternatively, Pilot can
populate inbound route's opaque_config with the canonical destination
service name. The mixerclient can use this the destination service
name as key into the runtime configuration to determine the
approptiate quota, apispec, etc. This has the nice property of
automatically handling all domain name variations that may appear in
the host header, e.g. my-service, my-service.my-namespace,
my-service.my-namespace.svc.local.


istio/api,istio/api,istio/api,cloudfoundry-attic/api,geeknoid/api,istio/api,cloudfoundry-attic/api,geeknoid/api,rshriram/api,geeknoid/api,rshriram/api,cloudfoundry-attic/api,geeknoid/api,cloudfoundry-attic/api,rshriram/api,cloudfoundry-attic/api