Skip to content

docs: update storage reqs/add archival da#1908

Merged
jcstein merged 1 commit intomainfrom
jcs/storage-increase
Mar 4, 2025
Merged

docs: update storage reqs/add archival da#1908
jcstein merged 1 commit intomainfrom
jcs/storage-increase

Conversation

@jcstein
Copy link
Copy Markdown
Member

@jcstein jcstein commented Feb 27, 2025 •
edited by coderabbitai bot
Loading

Overview

Summary by CodeRabbit

  • Documentation
    • Added two new sections that outline specifications for non-archival and archival data availability nodes.
    • Introduced detailed tables comparing node types, including updated disk capacity for archival nodes.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Feb 27, 2025 •
edited
Loading

Caution

Review failed

The pull request is closed.

Walkthrough

The document now includes two additional sections under "Data availability nodes": one for non-archival nodes and one for archival nodes. Both sections feature tables outlining the specifications for three node types—Light node, Bridge node, and Full storage node—with details on memory, CPU, disk, and bandwidth. In the archival section, the disk capacity for the Bridge and Full storage nodes is increased from 5 TiB NVME to 6 TiB NVME.

Changes

File Change Summary
how-to-guides/nodes-overview.md Added two new sections: "Non-archival data availability nodes" and "Archival data availability nodes". Included tables with node specifications. Disk capacity for the archival Bridge and Full storage nodes increased from 5 TiB NVME to 6 TiB NVME.

Possibly related PRs

Suggested labels

documentation

Suggested reviewers

  • mindstyle85

Poem

I hopped through docs with bounce and glee,
Adding tables for nodes as clear as can be,
Archival tweaks with disks grown wide,
Non-archival details now bona fide,
A rabbit’s cheer in every line, coding magic in every sign!
🐇✨

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 481f854 and 537e735.

📒 Files selected for processing (1)
  • how-to-guides/nodes-overview.md (1 hunks)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Feb 27, 2025

PR Preview Action v1.6.0

🚀 View preview at
https://celestiaorg.github.io/docs-preview/pr-1908/

Built to branch main at 2025-02-27 04:48 UTC.
Preview will be ready when the GitHub Pages deployment is complete.

jcstein
jcstein commented Feb 27, 2025
View reviewed changes
Comment thread how-to-guides/nodes-overview.md

| Node type | Memory | CPU | Disk | Bandwidth |
|-------------------|-------------|-------------|------------|-----------|
| Light node | 500 MB RAM | Single core | 100 GB SSD | 56 Kbps |
Copy link
Copy Markdown
Member Author

@jcstein jcstein Feb 27, 2025

Choose a reason for hiding this comment

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

should this be more for fully synced LN @Wondertan ?

@jcstein jcstein self-assigned this Feb 27, 2025
MSevey
MSevey approved these changes Feb 28, 2025
View reviewed changes
Copy link
Copy Markdown
Contributor

@MSevey MSevey left a comment

Choose a reason for hiding this comment

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

lgtm

@jcstein jcstein marked this pull request as ready for review March 4, 2025 22:28
@jcstein jcstein merged commit c667977 into main Mar 4, 2025
@jcstein jcstein deleted the jcs/storage-increase branch March 4, 2025 22:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@aWN4Y25pa2EK aWN4Y25pa2EK Awaiting requested review from aWN4Y25pa2EK

@Wondertan Wondertan Awaiting requested review from Wondertan

1 more reviewer

@MSevey MSevey MSevey approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@jcstein jcstein

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@jcstein @MSevey