Add a blog post about Mixer adapters. #700
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Jenkins job istio.github.io/presubmit passed |
1 similar comment
|
Jenkins job istio.github.io/presubmit passed |
douglas-reid
reviewed
Nov 3, 2017
_posts/2017-11-03-adapter-model.md
Outdated
|
|
||
| In addition to insulating application-level code from the details of infrastructure backends, Mixer provides an intermediation model that allows operators to inject and control policies between application code and backends. Operators can control which data is reported to which backend, which backend to consult for authorization, and much more. | ||
|
|
||
| Given that individual infrastructure backends each have different interfaces and operational models, Mixer needs custom code to deal with each and we call these custom bundles of code *[adapter*s](https://github.com/istio/istio/blob/master/mixer/doc/dev/adapters.md). |
There was a problem hiding this comment.
I feel like the '*'s surrounding adapter aren't doing what is intended. Here and elsewhere (templates, instances, rules), should this be: [*adapter*s] (instead of *[adapter*s]) ?
|
Ugh, those are markdown conversion errors. They're fixed now. Good catch. PTAL. |
douglas-reid
reviewed
Nov 3, 2017
_posts/2017-11-03-adapter-model.md
Outdated
| ## Instances: Attribute Mapping | ||
|
|
||
| You control which data is delivered to individual adapters by creating [*instances*](https://istio.io/docs/concepts/policy-and-control/mixer-config | ||
| .html#instances). Instances control how Mixer uses the [attributes](https://istio.io/docs/concepts/policy-and-control/attributes.html) delivered by the proxy into individual bundles of data that can be routed to different adapters. |
There was a problem hiding this comment.
i think the line break here (between mixer-config and .html) screws up the markdown for the link.
|
Fixed. Thanks.
…On Fri, Nov 3, 2017 at 10:12 AM, Douglas Reid ***@***.***> wrote:
***@***.**** commented on this pull request.
One small markdown issue (at least in github's view mode).
------------------------------
In _posts/2017-11-03-adapter-model.md
<#700 (comment)>:
> +You configure each adapter by creating [*handlers*](https://istio.io/docs/concepts/policy-and-control/mixer-config.html#handlers) for them. A handler is a
+configuration resource which represents a fully configured adapter ready for use. There can be any number of handlers for a single adapter, making it possible to reuse an adapter in different scenarios.
+
+## Templates: Adapter Input Schema
+
+Mixer is typically invoked twice for every incoming request to a mesh service, once for precondition checks and once for telemetry reporting. For every such call, Mixer invokes one or more adapters. Different adapters need different pieces of data as input in order to do their work. A logging adapter needs a log entry, a metric adapter needs a metric, an authorization adapter needs credentials, etc.
+Mixer [*templates*](https://istio.io/docs/reference/config/mixer/template/) are used to describe the exact data that an adapter consumes at request time.
+
+Each template is specified as a [protobuf](https://developers.google.com/protocol-buffers/) message. A single template describes a bundle of data that is delivered to one or more adapters at runtime. Any given adapter can be designed to support any number of templates, the specific templates the adapter supports is determined by the adapter developer.
+
+[metric](https://istio.io/docs/reference/config/mixer/template/metric.html) and [logentry](https://istio.io/docs/reference/config/mixer/template/logentry.html) are two of the most essential templates used within Istio. They represent respectively the payload to report a single metric and a single log entry to appropriate backends.
+
+## Instances: Attribute Mapping
+
+You control which data is delivered to individual adapters by creating [*instances*](https://istio.io/docs/concepts/policy-and-control/mixer-config
+.html#instances <https://istio.io/docs/concepts/policy-and-control/mixer-config+.html#instances>). Instances control how Mixer uses the [attributes](https://istio.io/docs/concepts/policy-and-control/attributes.html) delivered by the proxy into individual bundles of data that can be routed to different adapters.
i think the line break here (between mixer-config and .html) screws up
the markdown for the link.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#700 (review)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AVucHVwuMtkinwp6yu1y79nahZuFpwdVks5sy0lhgaJpZM4QRE3j>
.
|
|
Jenkins job istio.github.io/presubmit passed |
douglas-reid
approved these changes
Nov 3, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.