Canonical Juju

Refresh support for new aws instance types

  1. Series 2.4
  2. Bug #1790647
Bug #1790647 reported by james beedy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Unassigned
Canonical Juju 2.6-beta1
2.3
Fix Released
High
Simon Richardson
Canonical Juju 2.3.9
2.4
Fix Released
High
Simon Richardson
Canonical Juju 2.4.4
2.5
Fix Released
High
Simon Richardson
Canonical Juju 2.5-beta1

Bug Description

Juju is unaware of latest aws instance-types. Can we get a refresh/update? Thx

Richard Harding (rharding)
Changed in juju:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.4.4
Revision history for this message
Simon Richardson (simonrichardson) wrote :

PR: https://github.com/juju/juju/pull/9172
Discourse Post: https://discourse.jujucharms.com/t/ec2-instance-types/223

Revision history for this message
Simon Richardson (simonrichardson) wrote :

We should consider re-looking at this for 2.5, as the instances that we currently use for default controllers (et al) are being phased out and we should really consider using the new aws instance types.

Canonical Juju QA Bot (juju-qa-bot)
Changed in juju:
milestone: 2.4.4 → none
Revision history for this message
Anastasia (anastasia-macmood) wrote :

I am pretty sure that this has been forward ported to develop and 2.6

Changed in juju:
status: Triaged → Fix Committed
milestone: none → 2.6-beta1
Anastasia (anastasia-macmood)
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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