publiccloud: Boottime thresholds per flavor

[cfconrad]

We get very different timings for boottime validation. So we need to
specify thresholds per FLAVOR.

• Related ticket: https://progress.opensuse.org/issues/56462
• Verification run: TBD

[cfconrad]

Also fixed http://openqa-perf.qa.suse.de/d/A-z8Cz0Zz/systemd-analyze-blame view.

[jlausuch]

overall should be higher than userspace, right?
Why are you setting now overall to 180 if it was 160 in the default list?

[cfconrad]

ok

[jlausuch]

According to the discussion with PC team, the idea was to have it per provider, not per flavor. I know doing it per flavor is more flexible, but I wonder if it would be clearer to have only 3 values for each parameter (1 value per provider), something like a matrix, instead of patching some default values.

[asmorodskyi]

According to the discussion with PC team, the idea was to have it per provider, not per flavor. I know doing it per flavor is more flexible, but I wonder if it would be clearer to have only 3 values for each parameter (1 value per provider), something like a matrix, instead of patching some default values.

I second that , instead of programmatically nice looking thingy I would prefer to have clear matrix split by provider

[cfconrad]

I don't like the idea of having it per provider. At least we should separate between BYOS and On-Demand. Look at Azure http://s.qa.suse.de/KS1y there is a diff of 1min between them.

[cfconrad]

According to the discussion with PC team, the idea was to have it per provider, not per flavor.

They also had the idea to separate per instance-type. So I guess this isn't the last iteration and I would keep the config-matrix as small as possible, but flexible.

[asmorodskyi]

LGTM