cpu-power constraint conflicts with with instance-type when trying to launch a t2.medium

[Jorge Castro]

We're trying to launch a t2.medium on AWS and running into some weirdness:

    $ juju deploy cassandra --constraints="instance-type=t2.medium" -n 3
     juju status --format yaml cassandra
    environment: aws-west-2
    machines:
      "9":
        agent-state-info: no instance types in us-west-2 matching constraints "cpu-power=100
        instance-type=t2.medium"
        instance-id: pending
        series: trusty
      "10":
        agent-state-info: no instance types in us-west-2 matching constraints "cpu-power=100
        instance-type=t2.medium"
        instance-id: pending
        series: trusty
      "11":
         agent-state-info: no instance types in us-west-2 matching constraints "cpu-power=100
         instance-type=t2.medium"
         instance-id: pending
        series: trusty

Ok so weird, it thinks we want something with cpu-power=100 and that doesn't match, so let's be explicit:

    $ juju deploy cassandra --constraints="cpu-power=0 instance-type=t2.medium" -n 3
    Added charm "cs:trusty/cassandra-3" to the environment.
    ERROR ambiguous constraints: "cpu-power" overlaps with "instance-type"

How do we launch a t2.medium?

[Katherine Cox-Buday (cox-katherine-e)]

Currently under review.

PR is here: https://github.com/juju/juju/pull/3259
Review is here: http://reviews.vapour.ws/r/2638/diff/#

[Katherine Cox-Buday (cox-katherine-e)]

Forward ports currently under review (reviews have links to PR):
1.25:
- http://reviews.vapour.ws/r/2715/

master:
- http://reviews.vapour.ws/r/2716/