Skip to content

Resource budget for each developer/team (cloud cost control) #2121

@bpmct

Description

@bpmct

To manage cloud costs, it would be helpful to give developers or teams a budget/quota around how many cloud resources they can provision.

  • Developer 1 uses one large 32-core workspaces
  • Developer 2 uses five small workspaces for reproducing bugs on different operating systems

Developer 1 and developer 2 leverage auto-shutdown and spot instances to stay within their resource cap/budget and develop with the infrastructure they need to do their job.

We've discussed this idea before internally, but it was also suggested by @chrisae9 and @jorlina at Sonatype. Folks - feel free to add more context in this issue :)

Ideas:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions