juju cannot create GPU instances on GCE

Bug #1688183 reported by Samuel Cozannet
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Low
Unassigned

Bug Description

GCE doesn't provide instance types for GPUs, it's just an option to add when creating an instance.

As a result, juju constraints do not apply, and it's impossible to have Juju to start GPU instances. The only way to operate them is to pre-create them then manually add-machine.

It would be great if constraints treated GPUs as first class citizens, which would eventually make sure that a requests such as --constraints "gpus=2" created machines with the right settings on each cloud.

Changed in juju:
importance: Undecided → Wishlist
status: New → Triaged
Revision history for this message
Nick Veitch (evilnick) wrote :

This has become quite limiting for Kubernetes. Even in the AWS case it would be useful to have e.g.

  gpu=k80
or
  gpus=1

For gce, you can create custom instance templates which make adding GPUs easier, but Juju does not support custom instance types.

Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

Changed in juju:
importance: Wishlist → Low
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.