Build metadata for a linker
See http://www.awsarchitectureblog.com/2015/03/backoff.html
Represents the total configuration of a Linkerd process.
Provides a protocol-agnostic interface for protocol-specific configuration & initialization.
A router configuration builder api.
A router configuration builder api.
Each router must have a protocol that assists in the parsing and intialization of a router and its services.
params
contains all params configured on this router, including
(in order of ascending preference):
Each router must have one or more Servers.
Concrete implementations are provided by a ProtocolInitializer.
A Server configuration, describing a request-receiving interface for a Router.
A Server configuration, describing a request-receiving interface for a Router.
Concrete implementations are provided by ProtocolInitializer.
Loadable TLS client configuration module.
Loadable TLS client configuration module.
Implementers may read params from the config file and must produce a TlsClientPrep module which will control how this router makes TLS requests.
Linkerd provides a modular & pluggable configuration layer to support programmatic and configuration-driven initialization of software routers.
The library provides a family of configuration types:
* A Linker represents the complete runtime configuration for a linkerd application (and not its virtual machine). A linker must have one or more Routers.
* A Router represents the complete runtime configuration for a router--the outbound client-side dispatching module--and its serving interfaces, Servers.
The ProtocolInitializer exposes a protocol-agnostic interface supporting protocol-aware configuration and initialization. ProtocolInitializer modules are discovered at runtime with finagle's
LoadService
facility.