-
validate layer_presence query for blank/invalid/multiple-sections
blank-layer-presence-query
```
apiVersion: "recommender.com/v1"
kind: "AutotuneConfig"
metadata:
name: "blank-layer-presence…
-
Require validation for layer-presence-label-name
**Actual behaviour:** Throws Null pointer exception for no-value/blank/null layer-presence-label-name
**Expected behaviour:** Relevant message…
-
Goal: Update autotune hotpsot config yaml with default tunables for containers.
As part of this goal, in this sprint will have a discussion with OpenJDK team regarding the updates required to the t…
-
Required validation for upper bound
blank-tunable-upper-bound yaml
```
apiVersion: "recommender.com/v1"
kind: "AutotuneConfig"
metadata:
name: "blank-tunable-upper-bound"
layer_name: contai…
-
I noticed at https://github.com/zfsonlinux/zfs/pull/9648#issuecomment-559634577
That this bug was only exposed when a tunable was flipped.
That got me thinking that perhaps there are bug lurking…
-
Tunable lower bound can not be blank, invalid and can not have multiple sections
blank-tunable-lower-bound yaml
```
apiVersion: "recommender.com/v1"
kind: "AutotuneConfig"
metadata:
name: "b…
-
layer presence query key can not have blank/invalid/multiple values
blank-layer-presence-query-key
```
apiVersion: "recommender.com/v1"
kind: "AutotuneConfig"
metadata:
name: "blank-layer-pr…
-
Required validation for blank, invalid, multiple-sections of tunable value type
blank-tunable-value-type yaml
```
apiVersion: "recommender.com/v1"
kind: "AutotuneConfig"
metadata:
name: "bla…
-
Given that MTK has changed behavior now and is promoting all tunables to a common type, the doc discussion of parameter typing needs to be checked and updated accordingly (or perhaps
just removed unt…
-
layer presence label value cannot be blank/invalid
blank-layer-presence-label-value
```
apiVersion: "recommender.com/v1"
kind: "AutotuneConfig"
metadata:
name: "blank-layer-presence-labelval…