It still affects 1.16 and trunk/dev. The merge ended up just adding the
additional m3 instance types, without the removal of the m1 there's no
clear way for a user to specify.
On Wed, Apr 2, 2014 at 8:38 AM, Curtis Hovey <email address hidden> wrote:
It still affects 1.16 and trunk/dev. The merge ended up just adding the
additional m3 instance types, without the removal of the m1 there's no
clear way for a user to specify.
On Wed, Apr 2, 2014 at 8:38 AM, Curtis Hovey <email address hidden> wrote:
> ** No longer affects: juju-core/1.16 /bugs.launchpad .net/bugs/ 1280852 /bugs.launchpad .net/juju- core/+bug/ 1280852/ +subscriptions
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> juju specifies obsolete, more expensive, and worse performing instance
> types on aws
>
> To manage notifications about this bug go to:
> https:/
>