Skip to content

Conversation

@1597463007
Copy link

Introduces Sphinx-based documentation for the project, including configuration, requirements, and initial content for adapter and protocol documentation. Adds a GitHub Actions workflow to build and publish the documentation to GitHub Pages on release or manual trigger. Also includes .gitignore updates to exclude build artifacts and IDE files.

Introduces Sphinx-based documentation for the project, including configuration, requirements, and initial content for adapter and protocol documentation. Adds a GitHub Actions workflow to build and publish the documentation to GitHub Pages on release or manual trigger. Also includes .gitignore updates to exclude build artifacts and IDE files.
@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Aug 25, 2025

CLA Not Signed

401:
description: Unauthorized, e.g., invalid or missing auth_token
schema:
$ref: '#/definitions/Error'
Copy link

Choose a reason for hiding this comment

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

We probably need a 404 error for unknown worker_ids.

from scaler.utility.mixins import Reporter

class ScalingController(Reporter, abc.ABC):
async def on_state_client(self, state_client: StateClient):

Choose a reason for hiding this comment

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

should be decorated by @abc.abstractmethod

│ └────────┘
┌───────────┐ Webhook Requests ┌───────┴─┐ Start ┌────────┐
│ Scaling ├───────────────────► Adapter ├────────► Worker │

Choose a reason for hiding this comment

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

let's change the wording adapater to WorkerManagerAdapter

Choose a reason for hiding this comment

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

also this chart might be better went to the summary page

  1. summary:
    • user need implement allocate policy or using existing ones
    • user need implement worker manager adapters or using existing ones
    • then chart
    • briefly explain the roles of above
      Then you have 2 separate pages talks about
  2. how allocate policy is implemented in detail
  3. how worker manager adapter is implemented, also include detail about json formatting etc.

Choose a reason for hiding this comment

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

in the summary you can also draw graph about how client, scheduler, worker, worker manager adapters, allocate policy works, give them an overview.

Always better give them overview, and define the terminologies, then break down each name and for the detail

Replaces references to individual workers with worker groups in schema.yaml and documentation. Updates webhook request and response examples, handler method names, and scaling controller implementation notes to reflect the new worker group model.
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.

3 participants