Skip to content

Config-based named resources #1085

@clumsy

Description

@clumsy

Description

Add support for config-based named resources.

Motivation/Background

Changing any parameter of a resource currently requires making a code change. E.g. when using custom resource or not yet upstreamed to torchx ones - they have to be added to some installed package.

Detailed Proposal

Add support to describe resource spec in .torchxconfig file itself. I believe it needs to be structured, so it could be a JSON string.

Alternatives

Create forks and require new code releases if tweaking the number of CPUs, available memory is required for a new non-upstreamed resource.

Additional context/links

N/A

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions