centurylinkcloud / estimatortco Goto Github PK

The tco tool on the dev server is using "Proxima Nova" instead of "Open Sans".

1. In TCO tool, check 'Match IOPS Performance' box
2. In 'IOPS Manual Entry' field, enter some digits

expected: 'IOPS Manual Entry' field should be disabled if 'Match IOPS Performance' is checked

actual: 'Match IOPS Performance' field remains enable and briefly shows any numbers entered before being cleared out

The hourly rates for the CenturyLink windows and redhat linux hourly rates differ from the excel file when the "Match CPU/RAM Performance" checkbox is checked. The CPU and Ram values match, but the hourly rates don't.

Many users won't know what 'Daily Snapshots', or Match CPU/RAM Performance, or even IOPS. It might be a good idea to add some kind of legend or tooltip to explain the various fields the user can manipulate.

Repro
Switching from 5 daily snapshots to 14

Expected
The CenturyLink cloud pricing should increase to reflect new additional snapshot costs

Actual
Only the AWS pricing changes

Screenshots show same price for 5 vs 14 daily snapshots

The amazon and azure hourly rates look good, but some of the CenturyLink hourly rates can be off by $.001, which results in a 1% savings difference compared to the excel file.

I remember we ran into this problem the first time around, but we were able to match the excel file exactly.

The production TCO has the padding value.

Checkboxes for 'MATCH CPU/RAM PERFORMANCE' and 'MATCH IOPS PERFORMANCE'
in IE quite large compared to other browsers. This ok?