Aaah whaow. I have a default VPC myself, so that may explain the problem Tim is having. Early adopters problem!!
-- Samuel Cozannet Cloud, Big Data and IoT Strategy Team Business Development - Cloud and ISV Ecosystem Changing the Future of Cloud Ubuntu <http://ubuntu.com> / Canonical UK LTD <http://canonical.com> / Juju <https://jujucharms.com> [email protected] mob: +33 616 702 389 skype: samnco Twitter: @SaMnCo_23 [image: View Samuel Cozannet's profile on LinkedIn] <https://es.linkedin.com/in/scozannet> On Thu, Mar 16, 2017 at 9:17 AM, Andrew Wilkins < [email protected]> wrote: > On Thu, Mar 16, 2017 at 3:57 PM Samuel Cozannet < > [email protected]> wrote: > >> I am using the default settings, no change as far as I know to what Juju >> would do by default. >> > > What Juju will do depends on what is available in your EC2 account. Not > all EC2 accounts were born alike. > > If your account has a default VPC, that will be used by Juju. In that > case, you'll have p2 instance types available. I expect this to be the case > for most people - all accounts created since 2013-12-04 will have a default > VPC. > > If you've got an older account, then you may or may not have a default > VPC. If you do not, then Juju will fall back to EC2 Classic. In that case, > no p2 instance types. > > Cheers, > Andrew > > >> -- >> Samuel Cozannet >> Cloud, Big Data and IoT Strategy Team >> Business Development - Cloud and ISV Ecosystem >> Changing the Future of Cloud >> Ubuntu <http://ubuntu.com> / Canonical UK LTD <http://canonical.com> / >> Juju <https://jujucharms.com> >> [email protected] >> mob: +33 616 702 389 >> skype: samnco >> Twitter: @SaMnCo_23 >> [image: View Samuel Cozannet's profile on LinkedIn] >> <https://es.linkedin.com/in/scozannet> >> >> On Thu, Mar 16, 2017 at 8:52 AM, Andrew Wilkins < >> [email protected]> wrote: >> >> On Tue, Mar 14, 2017 at 8:48 PM Tim Van Steenburgh < >> [email protected]> wrote: >> >> 2.1.1 juju client and controller, controller bootstrapped in >> aws/us-east-1: >> >> juju deploy ./kubernetes-worker --constraints "instance-type=p2.xlarge" >> kubernetes-worker-gpu >> Deploying charm "local:xenial/kubernetes-worker-1". >> ERROR cannot add application "kubernetes-worker-gpu": invalid constraint >> value: instance-type=p2.xlarge >> valid values are: [m1.small cc2.8xlarge cr1.8xlarge g2.2xlarge r3.8xlarge >> i2.xlarge t1.micro c1.xlarge g2.8xlarge m3.xlarge m3.medium c3.4xlarge >> hs1.8xlarge r3.2xlarge m1.xlarge c3.xlarge c3.large c3.8xlarge r3.xlarge >> m2.xlarge m1.large i2.2xlarge i2.8xlarge cg1.4xlarge d2.2xlarge m2.2xlarge >> m3.2xlarge hi1.4xlarge m2.4xlarge r3.4xlarge r3.large d2.xlarge c1.medium >> d2.8xlarge m3.large m1.medium c3.2xlarge i2.4xlarge d2.4xlarge] >> >> Are you using VPC? p2 instance types only support VPC. >> >> I /am/ able to deploy a p2.xlarge in aws/us-east-1 using the AWS console. >> Looking at the code it seems this instance-type should be available: >> https://github.com/juju/juju/blob/juju-2.1.1/provider/ec2/internal/ec2instancetypes/generated.go#L6165 >> >> Not sure if this is a bug or PEBKAC. Grateful for any ideas while I continue >> to poke at it. >> >> >> Tim >> >> -- >> Juju mailing list >> [email protected] >> Modify settings or unsubscribe at: https://lists.ubuntu.com/ >> mailman/listinfo/juju >> >> >> -- >> Juju mailing list >> [email protected] >> Modify settings or unsubscribe at: https://lists.ubuntu.com/ >> mailman/listinfo/juju >> >> >>
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
