Skip to content

Move the time of a job, instead of/as well as the place #7

Description

@jacklockyerstevens

Moving the location of a job may not be practical because:

  • There are monetary/carbon costs in data transmission
  • Serverless VPC Connectors are required in every candidate region
  • Data governance requirements may not permit movement

In these cases, moving the time of the job may be the most appropriate way to save carbon.
To do this:

  • Forecast carbon intensity data would be required (e.g as provided by National Grid).
  • The user would provide a time range in which the job must run.
  • VertFlow would schedule the job to run at the greenest time in that region.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions