Can't juju deploy p2.xlarge in aws/us-east-1

Tue Mar 21 10:07:17 UTC 2017

Preferring a VPC if there is a single one that exists, even if it isn't
flagged as "default" for a region would probably be reasonable, and
probably not a lot of effort. If there are multiple, I wonder if we could
refuse to bootstrap/add-model unless one is specified.

John
=:->

On Tue, Mar 21, 2017 at 3:04 AM, Andrew Wilkins <
andrew.wilkins at canonical.com> wrote:

> On Mon, Mar 20, 2017 at 10:17 PM Junien Fridrick <
> junien.fridrick at canonical.com> wrote:
>
>> And once/if you have no Classic instance running in a region, you should
>> file a ticket to AWS Support asking for a default VPC creation. Once
>> it's done, you don't need to supply the VPC ID anymore.
>>
>> Could juju maybe be instructed to use a VPC if and only if a single VPC
>> exist in a region, without specifying its ID ? For example, --config
>> "force-vpc=true" or something.
>>
>
> Yes we could do that. I'd like to go a bit further; what I would like to
> have happen is:
>
> 1. juju will use the VPC specified in config, if any
> 2. else, Juju will look for a VPC called (say) "juju-default-vpc"
> 3. else, Juju will create a VPC with the same name, if it can*, and use
> that
> 4. else, Juju will use the default VPC, if available
> 5. else, bootstrap/add-model will fail
>
> The outcome being that Juju will then *always* use VPC, and the user
> shouldn't need to do a thing. This would also allow the provider to be
> cleaned up (assuming there's a migration path for existing deployments),
> and new features to be implemented more easily (e.g. support for EFS).
>
> Everyone on the team is currently fully booked, so I can't give you an
> estimate of when that'll come to fruition yet. We could do everything
> except have Juju fail pretty easily I would think.
>
> * "if it can", because there are pretty severe limits on the number of
> VPCs you can create: 5 per region.
>
> Cheers,
> Andrew
>
>
>> On Thu, Mar 16, 2017 at 08:04:22AM -0400, Tim Van Steenburgh wrote:
>> > Ahhhh. That was it. After passing --config "vpc-id=vpc-924fc7f6" to
>> `juju
>> > bootstrap`, I can now deploy p2 instance types. Thanks Andrew!
>> >
>> > On Thu, Mar 16, 2017 at 4:21 AM, Samuel Cozannet <
>> > samuel.cozannet at canonical.com> wrote:
>> >
>> > > 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>
>> > > samuel.cozannet at canonical.com
>> > > 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 <
>> > > andrew.wilkins at canonical.com> wrote:
>> > >
>> > >> On Thu, Mar 16, 2017 at 3:57 PM Samuel Cozannet <
>> > >> samuel.cozannet at canonical.com> 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>
>> > >>> samuel.cozannet at canonical.com
>> > >>> 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 <
>> > >>> andrew.wilkins at canonical.com> wrote:
>> > >>>
>> > >>> On Tue, Mar 14, 2017 at 8:48 PM Tim Van Steenburgh <
>> > >>> tim.van.steenburgh at canonical.com> 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
>> > >>> Juju at lists.ubuntu.com
>> > >>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>> > >>> an/listinfo/juju
>> > >>>
>> > >>>
>> > >>> --
>> > >>> Juju mailing list
>> > >>> Juju at lists.ubuntu.com
>> > >>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>> > >>> an/listinfo/juju
>> > >>>
>> > >>>
>> > >>>
>> > >
>>
>> > --
>> > Juju mailing list
>> > Juju at lists.ubuntu.com
>> > Modify settings or unsubscribe at: https://lists.ubuntu.com/
>> mailman/listinfo/juju
>>
>>
>> --
>> Juju mailing list
>> Juju at lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/
>> mailman/listinfo/juju
>>
>
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20170321/426df8b0/attachment.html>