Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Issues

Select view

Select search mode

 
3 of 3

[UI] Customize proxy replicas and resources during DB creation in the wizard

Unresolved

Description

Similarly to the way that users are able to customize the number of DB engine replicas and resources they should also be allowed to customize the number of proxy replicas and their resources (CPU and RAM).

https://www.figma.com/design/yqprW09jvELb9a5edQofVM/Create%2FEdit-Database?node-id=297-42314&t=MMzOHTvfyyStA9qJ-0

During that setup, the number of proxy replicas should follow the number of nodes, unless the user manually changes that number.

Changing a selected preset in the nodes mustn’t change the preset in the proxies.

Presets

MySQL

  • Nodes:

    • Small - 1 CPU / 2 GB

    • Medium - 4 CPU / 8 GB

    • Large - 8 CPU / 32 GB

  • Proxies:

    • Small - 0.2 CPU / 0.2 GB

    • Medium - 0.5 CPU / 0.8 GB

    • Large - 0.8 CPU / 3 GB

MongoDB

  • Nodes:

    • Small - 1 CPU / 4 GB

    • Medium - 4 CPU / 8 GB

    • Large - 8 CPU / 32 GB

  • Proxies:

    • Small - 1 CPU / 2 GB

    • Medium - 2 CPU / 4 GB

    • Large - 4 CPU / 16 GB

PG

  • Nodes:

    • Small - 1 CPU / 2 GB

    • Medium - 4 CPU / 8 GB

    • Large - 8 CPU / 32 GB

  • Proxies:

    • Small - 1 CPU / 0.03 GB

    • Medium - 4 CPU/ 0.06 GB

    • Large - 8 CPU / 0.1 GB

Details

Assignee

Reporter

Labels

Sprint

Fix versions

Due date

Priority

Parent

Smart Checklist

Created January 23, 2024 at 7:05 AM
Updated January 27, 2025 at 3:05 PM

Activity

Iaroslavna SolovevaSeptember 2, 2024 at 10:30 AM

returned ticket to review, because now it’s not merged to main and needs some conflicts solving before

Yusaf AwanAugust 30, 2024 at 6:59 AM

As discussed, I have changed the fix version from 1.2.0 to 1.3.0.

Iaroslavna SolovevaAugust 27, 2024 at 1:47 PM

777 ticket reverts 777 and 1211, 1230 was merged before, so we shouldn’t revert it)

Yusaf AwanAugust 27, 2024 at 9:31 AM

We need to get the data from the DB experts on all possible combinations for the changes done in this ticket for all 3 DBs to test it properly. will confirm whether we need to include this ticket in release 1.2.0 or 1.3.0.
Also, highlighted if revert this ticket, we would need to revert and