cloudfoundry / cloudfoundry/stratos

V3 API: Support new 'Processes' concept

Open
#3,154 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

v3 api
Dominant language
TypeScript
Stars
267
Forks
137
Avg merge
5h 14m
Merged PRs (30d)
77

Description

  • in v2 the api exposed instances which can be scaled
  • we show these instances in the ui along with their state.
  • in v3 processes have been exposed, which were previously 1:1 with instances
  • instances are now M:1 with processes
    • Most will contain a process of type web
    • Other processes can be used to execute before/after scaling, etc
  • Changing the instance count will increase the web process count but not other processes
  • Application state needs to be updated to take into account the web process state... and possibly the state of any other process during transitions
  • memory/disk quota's are by process now, not per application

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the v3 API's processes data into the UI application state, including scaling and transition handling. Done means the UI reflects web and other process states and applies memory and disk quotas per process; the issue does not name files or tests to run.

Written by the indexing model from the issue text.

Assessment

Tech stack
angular, typescript
Domain
api, cloud, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.