Skip to content

RDoc-3881 Document Azure Premium SSD v2 support in RavenDB Cloud#2466

Open
PFYasu wants to merge 3 commits into
ravendb:mainfrom
PFYasu:RDoc-3881
Open

RDoc-3881 Document Azure Premium SSD v2 support in RavenDB Cloud#2466
PFYasu wants to merge 3 commits into
ravendb:mainfrom
PFYasu:RDoc-3881

Conversation

@PFYasu
Copy link
Copy Markdown
Contributor

@PFYasu PFYasu commented May 26, 2026

Issue link

https://issues.hibernatingrhinos.com/issue/RDoc-3881

Additional description

Documents support for Azure Premium SSD v2 in RavenDB Cloud (deployed in RDBCL-2860 / Cloud PR #4216).

cloud/cloud-scaling.mdx

  • New subsection #### Azure Premium SSD v2 inside ### Azure Disks, covering:
    • Independently configurable IOPS and Throughput (Throughput range depends on IOPS)
    • Availability constraints: data-disk-only (requires Single Data Disk layout — Production Tier); not available for PN* (ephemeral) instances; not available for yearly plans; region must support Premium SSD v2 (auto-detected by the portal); no Azure Performance Tier customization
    • One-way migration: downgrade to Standard (under Single Data Disk layout) or to Premium (v1) is not possible
    • Two ways to obtain it: migrate to Data Disk in a supporting region, or use Upgrade to Premium V2 in the Storage section
    • Upgrade characteristics: node-by-node, brief unavailability per node, may take multiple hours, creates a support request handled by the Cloud team
    • Pricing note: IOPS and Throughput billed separately from capacity
  • Note in ### Data disks that on Azure, in regions supporting Premium SSD v2, the new data disk is automatically created as Premium SSD v2

cloud/portal/cloud-portal-products-tab.mdx

  • Short mention of the Upgrade to Premium V2 button in the Storage section, with a cross-link to cloud-scaling.mdx#azure-premium-ssd-v2 for full details (eligibility, constraints, behavior). Per project convention, the portal page only describes where the action lives; the technical details live in the dedicated cloud-scaling.mdx page.

Screenshots — added 4 new screenshots (storage edit form with editable IOPS/Throughput for Premium SSD v2, the Upgrade to Premium V2 modal, the Migrate to data disk modal showing the Premium SSD v2 note, and the Storage section with the Upgrade to Premium V2 button visible).

Type of change

  • Content - docs
  • Content - cloud
  • Content - guides
  • Content - start pages/other
  • New docs feature (consider updating /templates or readme)
  • Bug fix
  • Optimization
  • Other

Changes in docs URLs

  • No changes in docs URLs
  • Articles are restructured, URLs will change, mapping is required (update /scripts/redirects.json file, set Documents Moved PR label)

Changes in UX/UI

  • No changes in UX/UI
  • Changes in UX/UI (include screenshots and description)

@PFYasu PFYasu self-assigned this May 26, 2026
@PFYasu PFYasu added the Cloud label May 26, 2026
@PFYasu PFYasu requested review from hiddenshadow21 and matz985 May 26, 2026 11:55
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no support request path. Please update it once RDBCL-5302 is deployed.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Image

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed.

@PFYasu PFYasu requested a review from matz985 May 26, 2026 13:08
… flow

Replaces the upgrade modal screenshot and rewords the surrounding text to
reflect the direct user-initiated upgrade currently exposed in the portal,
instead of the support-request flow introduced by RDBCL-5302 (not yet
deployed).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants