Skip to content

Conversation

douglas-reid
Copy link
Contributor

@douglas-reid douglas-reid commented Sep 19, 2017

This PR moves the "default" configs for mixer from the samples/app/bookinfo/rules dir to the main install/kubernetes/** tree.

This PR is needed because, without it, the install of mixer will be missing many important configs for basic operation, including:

  • attribute manifests
  • default metrics
  • configuration of prometheus and stdio adapters

To make use of the new location for the Mixer configs, the e2e framework code was updated to replace the istio-config-default namespace with the namespace of the test. The various, now unnecessary YAML files in the samples directory were deleted.

cc: @debianmaster, @karmab

Related issue: istio/old_issues_repo#59

Release note:

Provide default Mixer configuration for prometheus metrics and stdio logs.

Copy link
Member

@rshriram rshriram left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question/nit (non blocking): Can we bundle logs, metrics, prometheus as one YAML ? Does it make sense to deploy them individually, such that one can be used without the other? If not, I suggest using a single mixer-metrics-addon.yaml (Not even sure if this should be an addon or just be enabled by default).
Even if prometheus is unavailable, mixer keeps collecting metrics right? So, we can have it on by default.

@douglas-reid
Copy link
Contributor Author

@rshriram I don't want to bundle logs with any of the metrics stuff. It arguably could be two files itself (one for the adapter config, one for the logentry). But it is distinct, in the Mixer sense, from the metrics stuff.

The metrics stuff can be used separately from prometheus adapter (if you wanted to use stdio metrics handler or stackdriver, for instance). But maybe that is a detail we worry about later.

@mandarjog thoughts on the addons config organization? should we bundle metrics.yaml and prometheus.yaml ? which is easier for users (to understand AND to use)?

@mandarjog
Copy link
Contributor

We should bundle prometheus with related metrics.
Prometheus adapter is built-in so it is safe to do so.

Regarding using fully qualified instance and handler names inside actions, namespace can be elided from those names. We do this is configs checked into Mixer repo.

Let us get some feedback from users if short names are desirable over fully qualified names while operating within a namespace.
istio/old_mixer_repo#1323

@douglas-reid
Copy link
Contributor Author

PTAL. I moved the "default" Mixer YAMLs for metrics and logs into the template for mixer itself. This simplifies the number of files, etc. I also stripped some of the explicit namespacing.

@mandarjog
Copy link
Contributor

I don't fully like the idea of installing config resources in a namespace of our choice - istio-config-default. It does create a good out of the box experience, but I don't see a way for a user to specify a different namespace, unless I have missed something.

That said, this does get us back to parity with 0.1.

Copy link
Contributor

@mandarjog mandarjog left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@mandarjog
Copy link
Contributor

/lgtm

@istio-merge-robot
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mandarjog
We suggest the following additional approver: andraxylia

Assign the PR to them by writing /assign @andraxylia in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these OWNERS Files:

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

@douglas-reid
Copy link
Contributor Author

@mandarjog Filed #878

@douglas-reid
Copy link
Contributor Author

Merging, in advance of internal testing to allow for proper out-of-the-box Mixer experience.

@douglas-reid douglas-reid merged commit 70a8218 into istio:master Sep 20, 2017
istio-merge-robot pushed a commit to istio/test-infra that referenced this pull request Oct 5, 2017
Automatic merge from submit-queue.

Add release-note collector

**Release note**:

```release-note
none
```

It's a binary to collect release-note from repos.

Example command: 
``` Bash
$ bazel-bin/toolbox/release_note_collector/release_note_collector --repos istio --previous_release 0.2.2 --current_release 0.2.4 --pr_link
```
And the release-note would be put into a local file, default is in current directory, named "<repo>.releasenote"

The example output is: 
```Bash
$ cat istio.releasenote
istio: istio -- 0.2.4 release note
Previous release version: 0.2.2
* Provide default Mixer configuration for prometheus metrics and stdio logs.  istio/istio#866
* test setup doc update  istio/istio#831
* New config model (breaking change). Migration instructions are [here](https://github.com/istio/istio/blob/release-0.2/samples/CONFIG-MIGRATION.md)  istio/istio#829
```
mandarjog pushed a commit to mandarjog/istio that referenced this pull request Oct 30, 2017
Add the Handler configuration logic.

Handler configurer identifies and configures all the handlers that needs to be configure and infer the types to pass them.

Former-commit-id: d5caf7b7fd750f103390ca71ea999dd6e30bc50a
rshriram pushed a commit that referenced this pull request Oct 30, 2017
* Create default Mixer config YAMLs

* Update bookinfo BUILD

* Refactor configs to mixer yaml template

* delete metrics.yaml


Former-commit-id: 70a8218
mandarjog pushed a commit that referenced this pull request Oct 31, 2017
Add the Handler configuration logic.

Handler configurer identifies and configures all the handlers that needs to be configure and infer the types to pass them.

Former-commit-id: 52092f162abd315ce406139749097ebfe72b1643
vbatts pushed a commit to vbatts/istio that referenced this pull request Oct 31, 2017
* Create default Mixer config YAMLs

* Update bookinfo BUILD

* Refactor configs to mixer yaml template

* delete metrics.yaml


Former-commit-id: 70a8218
mandarjog pushed a commit that referenced this pull request Nov 2, 2017
* Create default Mixer config YAMLs

* Update bookinfo BUILD

* Refactor configs to mixer yaml template

* delete metrics.yaml


Former-commit-id: 70a8218
ChristinaLyu0710-zz pushed a commit to ChristinaLyu0710-zz/istio-flakey-test that referenced this pull request Jun 11, 2019
Automatic merge from submit-queue.

Add release-note collector

**Release note**:

```release-note
none
```

It's a binary to collect release-note from repos.

Example command: 
``` Bash
$ bazel-bin/toolbox/release_note_collector/release_note_collector --repos istio --previous_release 0.2.2 --current_release 0.2.4 --pr_link
```
And the release-note would be put into a local file, default is in current directory, named "<repo>.releasenote"

The example output is: 
```Bash
$ cat istio.releasenote
istio: istio -- 0.2.4 release note
Previous release version: 0.2.2
* Provide default Mixer configuration for prometheus metrics and stdio logs.  istio/istio#866
* test setup doc update  istio/istio#831
* New config model (breaking change). Migration instructions are [here](https://github.com/istio/istio/blob/release-0.2/samples/CONFIG-MIGRATION.md)  istio/istio#829
```
0x01001011 pushed a commit to thedemodrive/istio that referenced this pull request Jul 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants