ec2: add support for C5 instance types

[Andrew Wilkins]

https://aws.amazon.com/blogs/aws/now-available-compute-intensive-c5-instances-for-amazon-ec2/

[Andrew Wilkins (axwalk)]

Bumping to 2.4, since there will be changes required to support storage. With C5, EBS volumes are exposed as NVMe block devices. See: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html

[John A Meinel (jameinel)]

Do we know if the Ubuntu images already support this?

On Wed, Nov 8, 2017 at 6:42 AM, Andrew Wilkins <<email address hidden>
> wrote:

> Bumping to 2.4, since there will be changes required to support storage.
> With C5, EBS volumes are exposed as NVMe block devices. See:
> http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html
>
> ** Changed in: juju
> Milestone: 2.3-rc1 => 2.4-beta1
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1730809
>
> Title:
> ec2: add support for C5 instance types
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1730809/+subscriptions
>

[Andrew Wilkins (axwalk)]

From the linked blog post: "The latest Amazon Linux, Microsoft Windows, Ubuntu, RHEL, CentOS, SLES, Debian, and FreeBSD AMIs all support C5 instances."

[Andrew Wilkins (axwalk)]

This is partially addressed by https://github.com/juju/juju/pull/8253. I'm reluctant to mark this Fix Committed, because the instance type data provided by AWS is incomplete; it doesn't include C5 or M5 for all regions, even where those instance types are supported.

[Heather Lanigan (hmlanigan)]

Between then and now, aws instance type selection within juju has changed and is received on the fly (with some limited caching). There are no issues deploying with c5 instance types on aws