Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FeatureRequest]: consume wanna.yaml from stdin like kubectl apply #128

Open
racinmat opened this issue Mar 28, 2024 · 0 comments
Open

[FeatureRequest]: consume wanna.yaml from stdin like kubectl apply #128

racinmat opened this issue Mar 28, 2024 · 0 comments

Comments

@racinmat
Copy link
Contributor

Contact Details

No response

Is your feature request related to a problem? Please describe

I like to parameterize wanna.yaml for some grid search experiments.
The yaml natively supports env vars, but they are not thread-safe, so I can't run them in parallel (since e.g. job creation is blocking).

Describe the solution you'd like

Supporting something like

wanna job run -f - <<EOF
wanna_project:
  name: wanna-mlops
  version: 0.0.0
  authors: 
    - [email protected]

gcp_profiles:
  - profile_name: mlops-dev
  - ...

docker:
#  cloud_build: true
  cloud_build: false
  ...

jobs:
  - name: nvidia-driver
    worker:
      container:
        docker_image_ref: data
        command: []
      args: []
      machine_type: "n1-highmem-2"  # the cheapest machine with gpu
      gpu:
        accelerator_type: NVIDIA_TESLA_T4
        count: 1
    enable_web_access: true
    region: ${region}
    ...

Describe alternatives you've considered

I am creating some temporary files.
I also used env vars, but it did not work due to their thread non-safety on windows

jobs:
  - name: nvidia-driver
    worker:
      container:
        docker_image_ref: data
        command: []
      args: []
      machine_type: "n1-highmem-2"  # the cheapest machine with gpu
      gpu:
        accelerator_type: NVIDIA_TESLA_T4
        count: 1
    enable_web_access: true
    region: ${region}
    network: projects/.../global/networks/${region}-...
    subnet: projects/.../regions/${region}/subnetworks/${region}-...

Additional context

No response

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

No branches or pull requests

2 participants