Skip to content

731 document high level roles and functions of the nodes making up the cn - #1173

Closed
simonletort-da wants to merge 21 commits into
canton-network:mainfrom
simonletort-da:731-Document-high-level-roles-and-functions-of-the-nodes-making-up-the-CN
Closed

simonletort-da wants to merge 21 commits into
canton-network:mainfrom
simonletort-da:731-Document-high-level-roles-and-functions-of-the-nodes-making-up-the-CN

Conversation

@simonletort-da

Copy link
Copy Markdown
Contributor

Update from @ethancohen-da based on gDoc suggested in https://github.com/global-synchronizer-foundation/docs/discussions/20#discussioncomment-12568745

Fixes #731

Pull Request Checklist

Cluster Testing

  • [N/A] If a cluster test is required, comment /cluster_test on this PR to request it, and ping someone with access to the DA-internal system to approve it.
  • [N/A] If a hard-migration test is required (from the latest release), comment /hdm_test on this PR to request it, and ping someone with access to the DA-internal system to approve it.

PR Guidelines

  • [N/A] Include any change that might be observable by our partners or affect their deployment in the release notes.
  • Specify fixed issues with Fixes #n, and mention issues worked on using #n
  • [N/A] Include a screenshot for frontend-related PRs - see README or use your favorite screenshot tool

Merge Guidelines

  • Make the git commit message look sensible when squash-merging on GitHub (most likely: just copy your PR description).

@simonletort-da

Copy link
Copy Markdown
Contributor Author

@waynecollier-da,
@ethancohen-da converted the gDoc into .rst
And we've taken the suggestion to simplify and refer to Validator (instead of CC Validator, Participant) into account.
Can you review PR #1173?

Comment thread docs/src/deployment.rst
Overview
========

############

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.

why is this under deployment? This seems more like a background section

@ethancohen-da

Copy link
Copy Markdown

Moved delpoyment.rst file to its own section named overview in the index.rst file and changed the name from delpoyment.rst to overview.rst

@martinflorian-da

Copy link
Copy Markdown
Contributor

Moved delpoyment.rst file to its own section named overview in the index.rst file and changed the name from delpoyment.rst to overview.rst

@ethancohen-da did you push your changes? The PR looks unchanged to me since @moritzkiefer-da's feedback.

…ow-how-they-can-suggest-changes-to-the-docs' into 731-Document-high-level-roles-and-functions-of-the-nodes-making-up-the-CN
Comment thread docs/README.md

When making a change, rebuild the documentation using `sbt docs/bundle`.

## Simplified build

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.

I'm not fully convinced yet that we want and additional way to build docs; it increases complexity, adds maintenance overhead and with no one of the (core) devs using this route it can easily stop working without anyone noticing. So I'm not sure if in the long run we're simplifying the experience for non-developers with this at all.

In any case I suggest to make a separate PR for this and keep this PR small and focused only on the docs change described in the PR description. If nothing else, small PRs are easier to get reviews for.

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.

separate PR

Or maybe even just an issue at first for discussion...

Comment thread docs/src/conf.py
download_url = "/cn-release-bundles"
helm_repo_prefix = os.getenv("OCI_DEV_HELM_REGISTRY")
docker_repo_prefix = os.getenv("DEV_DOCKER_REGISTRY")
# with open(os.path.join(os.getenv("CANTON"), "SUBDIR")) as f:

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.

This doesn't look very "ready for review" to me. Consider keeping PRs in draft until you consider them ready to merge.

@martinflorian-da

martinflorian-da commented Jul 2, 2025 •

Copy link
Copy Markdown
Contributor

About the failed scala_test_wall_clock_time run: this is a known bug (https://github.com/DACH-NY/cn-test-failures/issues/4733) unrelated to the PR. Feel free to ignore / rerun and in general for docs-only changes [static] CI runs suffice (https://github.com/hyperledger-labs/splice/blob/main/TESTING.md#running-static-tests-only-in-ci)

Edit: added the static label to the PR now so you should get only static runs automatically (thanks @moritzkiefer-da for pointing that out)

@martinflorian-da martinflorian-da added the static Used to label PRs for which static tests suffice label Jul 2, 2025
@martinflorian-da

Copy link
Copy Markdown
Contributor

This PR looks stale to me, closing but feel to reopen!

@waynecollier-da

Copy link
Copy Markdown
Contributor

@martinflorian-da Please re-open; we need this doc to be added to the Splice docs. It just needs to be reorganized slightly.

@martinflorian-da

Copy link
Copy Markdown
Contributor

@martinflorian-da Please re-open; we need this doc to be added to the Splice docs. It just needs to be reorganized slightly.

As per Slack discussion: I'm assuming the authors here will not be finishing this PR, but it may very well be used as inspiration for whoever ends up completing #731

This branch was previously deployed

1 inactive deployment
ci-forks — 36c26404 Deployed Jun 30, 2025 by simonletort-da
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

static Used to label PRs for which static tests suffice

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document high-level roles and functions of the nodes making up the CN

7 participants