First pass, autosetting within canaryopt 'create' classmethod

[DanielHHowell]

No description provided.

[linear]

ENG-622 Auto-set the range of CPU and Memory

Auto-set the range of CPU and memory. Remove the requirement to configure the CPU and memory ranges (min and max), e.g., by using the formula that OKO uses (min = 0.5 * baseline, max = 1.5 * baseline) to derive default values based on the current value of baseline, while still allowing explicit values to be set

[DanielHHowell]

@linkous8 can you let me know if this is the right idea, mainly as far as where this logic should take place? And for the actual multipliers (just hardcoded temporarily for testing), do you think they should be constants somewhere or perhaps part of the config?

[DanielHHowell]

@linkous8 I moved the logic to startup. Any advice on how/where we should store the autosetting multipliers (constants? config? just leave as-is?)
I also added a small touch to just load default ranges when create_tuning_pod is False, doesn't really matter since the values aren't used anyways, just to hold the important pinned settings

[blakewatters]

why have these famous random values versus just raising?

[blakewatters]

startup seems correct here. I'd prolly argue for putting the multipliers into the config with defaults expecting that you never have to change them but you can if you have to. If you hardcode them with constants you need to cut new bits to experiment