Skip to content

docs(readme): update ecosystem overview for planner integration#795

Draft
cbartz wants to merge 2 commits into
mainfrom
docs/update-ecosystem-diagram-ISD-5817
Draft

docs(readme): update ecosystem overview for planner integration#795
cbartz wants to merge 2 commits into
mainfrom
docs/update-ecosystem-diagram-ISD-5817

Conversation

@cbartz
Copy link
Copy Markdown
Collaborator

@cbartz cbartz commented May 20, 2026

What this PR does

Why we need it

Checklist

  • I followed the contributing guide
  • I added or updated the documentation (if applicable)
  • I updated docs/changelog.md with user-relevant changes
  • I used AI to assist with preparing this PR
  • I added or updated tests as needed (unit and integration)
  • If this is a Grafana dashboard: I added a screenshot of the dashboard
  • If this is Terraform: terraform fmt passes and tflint reports no errors
  • If the github-runner-manager application has been changed: The application version number is updated in github-runner-manager/pyproject.toml.

Copy link
Copy Markdown
Contributor

@erinecon erinecon left a comment

Choose a reason for hiding this comment

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

Thanks! Nits only

Comment thread README.md
* [GitHub Runner](https://charmhub.io/github-runner): The central component that manages self-hosted GitHub runners. It interacts with OpenStack to spawn runner VMs and communicates with GitHub to register and manage runners.
* [Image Builder](https://charmhub.io/github-runner-image-builder): Responsible for generating images. It builds images on the builder OpenStack project and uploads them to the GitHub Runner OpenStack project.
* [MongoDB](https://charmhub.io/mongodb): Acts as a message queue to handle reactive runner requests. The [github-runner-webhook-router](https://charmhub.io/github-runner-webhook-router) charm will put events in MongoDB that will be consumed by the `github-runner` charm. Only for reactive runners.
* [Planner](https://charmhub.io/github-runner-planner): Consumes webhook events from an AMQP broker, tracks job state in PostgreSQL, and streams runner demand ("pressure") to the `github-runner` charm. Optional — without it the charm pre-spawns a fixed pool of runners configured via `base-virtual-machines`. The Planner integration requires:
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 think we should be more clear about what we mean by without it the charm pre-spawns... if I'm understanding correctly, you mean "without the planner charm, the GitHub runner charm pre-spawns". Please correct me if I'm mistaken!

Comment thread README.md
Comment on lines +104 to +105
MQ(["RabbitMQ"])
PG[(PostgreSQL)]
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.

Nit: AFAIK RabbitMQ and PostgreSQL are both deployed as charms, so why are they represented differently in the diagram?

Comment thread README.md
githubrunner <-->|"manage runners"| GH
tmate -->|"debug-ssh credentials"| githubrunner
GH -->|"workflow job webhooks"| webhookgateway
webhookgateway -->|"validated webhooks"| MQ
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.

Suggested change
webhookgateway -->|"validated webhooks"| MQ
webhookgateway -->|"validates webhooks"| MQ

Nit, to be consistent in the verb tense throughout the diagram

Comment thread README.md
imagebuilder -->|"builds images"| OS_BUILD
imagebuilder -->|"uploads images"| OS_RUNNERS
imagebuilder -->|"image ids"| githubrunner
githubrunner -->|"OpenStack credentials"| imagebuilder
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.

Nit: Thinking about adding a verb to this relation. Would it be correct to say:

Suggested change
githubrunner -->|"OpenStack credentials"| imagebuilder
githubrunner -->|"provides OpenStack credentials"| imagebuilder

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants