feat: расчёт стоимости платного тестирования/аренды GPU-серверов
Новая вкладка «Аренда» в конфигураторе (доступна для проектов с флагом
rental_enabled): расчёт по методичке "Регламент расчёта стоимости
платного тестирования и аренды GPU-серверов" — Разовый + Еженедельный
платёж по каждому компоненту (New/БУ чекбоксом), с аплифтом к Estimate.
Заодно: поддержка (support_code) в Base-вкладке теперь добавляется как
обычный LOT в спеку (SVC_{срок}y{уровень}_{платформа}) через
autocomplete-пикер вместо выпадающего списка — партномер собирается
тем же lot_name-based механизмом, что и для GPU/CPU/памяти, справочная
цена по регламенту техподдержки хранится в qt_settings.support_pricing.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Sonnet 5
parent
b48436de93
commit
7edb80e498
@@ -148,6 +148,55 @@ badge on the tab label when required categories are missing.
|
||||
|
||||
---
|
||||
|
||||
### `support_pricing`
|
||||
|
||||
Price data from "Регламент расчёта стоимости технической поддержки серверов", used by the
|
||||
Base tab's support-level picker to display a computed price next to the chosen support code.
|
||||
This is reference/quoting data only — QF never adds it as a cart line or configuration cost;
|
||||
see [02-architecture.md](02-architecture.md#support-pricing-reference-not-a-cart-item).
|
||||
|
||||
x86 is a percent of sale price (QF approximates sale price as the configuration's Estimate
|
||||
total). HGX platforms (any GPU category component present, classified by chip generation via
|
||||
lot_name substring) use a fixed multi-year price instead. Both are keyed `level -> duration in
|
||||
years (as a JSON string key) -> value`; a combination absent from the table is not offered by
|
||||
the regulation and the picker won't show it.
|
||||
|
||||
**Value format:**
|
||||
|
||||
```json
|
||||
{
|
||||
"x86_percent": {
|
||||
"W": {"3": 0.06},
|
||||
"B": {"1": 0.05, "3": 0.10, "5": 0.14},
|
||||
"S": {"1": 0.07, "3": 0.13, "5": 0.18},
|
||||
"P": {"1": 0.12, "3": 0.20, "5": 0.45}
|
||||
},
|
||||
"hgx_price": {
|
||||
"HGX-H200": {
|
||||
"B": {"1": 20000, "3": 55000, "5": 80000},
|
||||
"S": {"1": 28000, "3": 70000, "5": 100000},
|
||||
"P": {"1": 63000, "3": 105000}
|
||||
},
|
||||
"HGX-B200": {
|
||||
"B": {"1": 40000, "3": 100000, "5": 145000},
|
||||
"S": {"1": 55000, "3": 130000, "5": 185000},
|
||||
"P": {"1": 101000, "3": 176000}
|
||||
},
|
||||
"HGX-B300": {
|
||||
"B": {"1": 40000, "3": 100000, "5": 145000},
|
||||
"S": {"1": 55000, "3": 130000, "5": 185000},
|
||||
"P": {"1": 112000, "3": 187000}
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
Editing this setting in MariaDB (no QF release needed) changes the price shown by the picker
|
||||
immediately on the next component sync — this is the intended way to keep support pricing
|
||||
current as the regulation evolves.
|
||||
|
||||
---
|
||||
|
||||
## Backward compatibility
|
||||
|
||||
- If `qt_settings` does not exist (old server): QF logs `Warn` during sync and
|
||||
|
||||
Reference in New Issue
Block a user