Re: Constraints for Additional Units

2017-03-16 Thread James Beedy 
I think I see *my* issue here. I have placed the constraints on the
machines (to which the charms are mapped) in my bundle, and not on the
actual applications themselves. I guess I shouldn't expect the constraints
to be associated with the charms in that case. Does this sound correct?

On Thu, Mar 16, 2017 at 8:13 PM, James Beedy  wrote:

> With the following spaces and subnets http://paste.ubuntu.com/24192913/
>
> I deploy my haproxy units to the igw subnets, and keep the rest of the
> components of my applications behind the nat gateway on the nat subnets. I
> tag the appropriate spaces on the machines in my bundle, but following a
> bundle deploy, the units don't scale out with the correct constraints (e.g.
> end up in the wrong space) if I go to add any additional units. As can be
> seen here (http://paste.ubuntu.com/24192930/) the additional unit of
> 'feed-web' obviously does not end up on one of my nat gateway subnets hence
> it has a public ip.
>
> On Thu, Mar 16, 2017 at 8:01 PM, Tim Penhey 
> wrote:
>
>> On 17/03/17 14:23, James Beedy wrote:
>>
>>> Currently, if I scale the units of my application, the new units do not
>>> have the same constraints as the previously deployed units.
>>>
>>
>> Well, I certainly think they should be carrying over the constraints as
>> the constraints are set on the application, not the unit.
>>
>> If this isn't working, I believe it is a bug.
>>
>> Can you give an example of what is not working?
>>
>> Cheers,
>> Tim
>>
>>
>> Moreover, it
>>> doesn't seem there is anyway to specify constraints for additional
>>> units. I'm thinking the 'add-unit' command needs to be able to accept
>>> constraints, or constraints need to be carried forward for additional
>>> units of the same application.  This is a request for the 'add-unit'
>>> command to accept constraints, or for constraints to grow some sort of
>>> associativity/sensitivity to applications. Also, this is a huge blocker
>>> for me right now. Any insight as to how we might solve this issue would
>>> be greatly appreciated.
>>>
>>> Thanks
>>>
>>> https://bugs.launchpad.net/juju/+bug/1673639
>>>
>>>
>>>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Constraints for Additional Units

2017-03-16 Thread Tim Penhey 

On 17/03/17 14:23, James Beedy wrote:

Currently, if I scale the units of my application, the new units do not
have the same constraints as the previously deployed units.


Well, I certainly think they should be carrying over the constraints as 
the constraints are set on the application, not the unit.


If this isn't working, I believe it is a bug.

Can you give an example of what is not working?

Cheers,
Tim


Moreover, it
doesn't seem there is anyway to specify constraints for additional
units. I'm thinking the 'add-unit' command needs to be able to accept
constraints, or constraints need to be carried forward for additional
units of the same application.  This is a request for the 'add-unit'
command to accept constraints, or for constraints to grow some sort of
associativity/sensitivity to applications. Also, this is a huge blocker
for me right now. Any insight as to how we might solve this issue would
be greatly appreciated.

Thanks

https://bugs.launchpad.net/juju/+bug/1673639




--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: Constraints for Additional Units

2017-03-16 Thread Tim Penhey 

On 17/03/17 14:23, James Beedy wrote:

Currently, if I scale the units of my application, the new units do not
have the same constraints as the previously deployed units.


Well, I certainly think they should be carrying over the constraints as 
the constraints are set on the application, not the unit.


If this isn't working, I believe it is a bug.

Can you give an example of what is not working?

Cheers,
Tim


Moreover, it
doesn't seem there is anyway to specify constraints for additional
units. I'm thinking the 'add-unit' command needs to be able to accept
constraints, or constraints need to be carried forward for additional
units of the same application.  This is a request for the 'add-unit'
command to accept constraints, or for constraints to grow some sort of
associativity/sensitivity to applications. Also, this is a huge blocker
for me right now. Any insight as to how we might solve this issue would
be greatly appreciated.

Thanks

https://bugs.launchpad.net/juju/+bug/1673639




--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Constraints for Additional Units

2017-03-16 Thread James Beedy 
Currently, if I scale the units of my application, the new units do not
have the same constraints as the previously deployed units. Moreover, it
doesn't seem there is anyway to specify constraints for additional units.
I'm thinking the 'add-unit' command needs to be able to accept constraints,
or constraints need to be carried forward for additional units of the same
application.  This is a request for the 'add-unit' command to accept
constraints, or for constraints to grow some sort of
associativity/sensitivity to applications. Also, this is a huge blocker for
me right now. Any insight as to how we might solve this issue would be
greatly appreciated.

Thanks

https://bugs.launchpad.net/juju/+bug/1673639
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: Juju 2.2-alpha and conjure-up, are here!

2017-03-16 Thread Uros Jovanovic 
Please note, that the experience with "juju login jaas" in 2.2-Alpha1 is
still quite broken. The login command will add jaas controller to the
controllers.yaml, so the next time you'd like to use it, you'll have to do
"juju switch jaas" instead of "juju login jaas".  We'll improve the
experience by the next release.

PS: In case you've already registered JAAS controller, please unregister it
and run "juju login jaas" again.

On Thu, Mar 16, 2017 at 10:19 PM, Curtis Hovey-Canonical <
cur...@canonical.com> wrote:

> A new release of Juju, 2.2-alpha1, and conjure-up, are here!
>
>
> ## What's new in 2.2-alpha1
>
> - juju login
>
>
> ### juju login
>
> Juju login command now accepts the name of the public controller as a
> parameter.
>
> juju login jaas
>
> This would add the jaas public controller to the list of the controllers
> you can use, it will also get cached in the controllers.yaml. Public
> controllers use external identity providers. JAAS uses Ubuntu SSO as an
> external provider, so in order to use this controller, you have to
> register at Ubuntu SSO. In order to get access to the JAAS public
> controller, please register through jujucharms.com or using this URL
> https://jujucharms.com/login
>
> The previous version of the command accepted the user name as a
> parameter. In order to login as a local user, pass the -u option.
>
> juju login -u bob
>
> Note that this release includes only the initial implementation of the
> juju login command changes. Polishing and improved UX will come with
> following releases.
>
>
> ## Resolved Issues
>
> Check the milestones for a detailed breakdown of Juju and conjure-up
> bugs corrected.
>
> https://github.com/conjure-up/conjure-up/milestone/20?closed=1
> https://launchpad.net/juju/+milestone/2.2-alpha1
>
>
> ## How do I get it?
>
> If you are running Ubuntu, you can get Juju from the juju stable ppa:
>
>sudo add-apt-repository ppa:juju/devel; sudo apt-get update
>
>sudo apt-get install juju
>
> Or install Juju from the snap store:
>
>snap install juju --classic --beta
>
> Install conjure-up from the snap store:
>
>snap install conjure-up --classic --edge
>
> If you are on Trusty, you'll need to run a few extra commands:
>
>sudo apt-get install snapd
>sudo groupadd lxd && sudo usermod -a -G lxd $USER
>sudo reboot
>
> Now you can install snaps, including conjure-up, as normal:
>
>snap install conjure-up --classic --edge
>
> Windows, CentOS, and MacOS users can get a corresponding Juju
> installer at:
>
>https://launchpad.net/juju/+milestone/2.2-alpha1
>
>
> ## Feedback Appreciated!
>
> We encourage everyone to let us know how you're using Juju. Send us a
> message on Twitter using #jujucharms, join us at #juju on freenode, and
> subscribe to the mailing list at j...@lists.ubuntu.com.
>
>
> ## More information
>
> To learn more about these great technologies please visit
> https://jujucharms.com and http://conjure-up.io.
>
>
> --
> Curtis Hovey
> Canonical Cloud Development and Operations
> http://launchpad.net/~sinzui
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju-dev
>
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Juju 2.2-alpha and conjure-up, are here!

2017-03-16 Thread Curtis Hovey-Canonical 
A new release of Juju, 2.2-alpha1, and conjure-up, are here!


## What's new in 2.2-alpha1

- juju login


### juju login

Juju login command now accepts the name of the public controller as a
parameter.

juju login jaas

This would add the jaas public controller to the list of the controllers
you can use, it will also get cached in the controllers.yaml. Public
controllers use external identity providers. JAAS uses Ubuntu SSO as an
external provider, so in order to use this controller, you have to
register at Ubuntu SSO. In order to get access to the JAAS public
controller, please register through jujucharms.com or using this URL
https://jujucharms.com/login

The previous version of the command accepted the user name as a
parameter. In order to login as a local user, pass the -u option.

juju login -u bob

Note that this release includes only the initial implementation of the
juju login command changes. Polishing and improved UX will come with
following releases.


## Resolved Issues

Check the milestones for a detailed breakdown of Juju and conjure-up
bugs corrected.

https://github.com/conjure-up/conjure-up/milestone/20?closed=1
https://launchpad.net/juju/+milestone/2.2-alpha1


## How do I get it?

If you are running Ubuntu, you can get Juju from the juju stable ppa:

   sudo add-apt-repository ppa:juju/devel; sudo apt-get update

   sudo apt-get install juju

Or install Juju from the snap store:

   snap install juju --classic --beta

Install conjure-up from the snap store:

   snap install conjure-up --classic --edge

If you are on Trusty, you'll need to run a few extra commands:

   sudo apt-get install snapd
   sudo groupadd lxd && sudo usermod -a -G lxd $USER
   sudo reboot

Now you can install snaps, including conjure-up, as normal:

   snap install conjure-up --classic --edge

Windows, CentOS, and MacOS users can get a corresponding Juju
installer at:

   https://launchpad.net/juju/+milestone/2.2-alpha1


## Feedback Appreciated!

We encourage everyone to let us know how you're using Juju. Send us a
message on Twitter using #jujucharms, join us at #juju on freenode, and
subscribe to the mailing list at juju@lists.ubuntu.com.


## More information

To learn more about these great technologies please visit
https://jujucharms.com and http://conjure-up.io.


-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Juju 2.2-alpha and conjure-up, are here!

2017-03-16 Thread Curtis Hovey-Canonical 
A new release of Juju, 2.2-alpha1, and conjure-up, are here!


## What's new in 2.2-alpha1

- juju login


### juju login

Juju login command now accepts the name of the public controller as a
parameter.

juju login jaas

This would add the jaas public controller to the list of the controllers
you can use, it will also get cached in the controllers.yaml. Public
controllers use external identity providers. JAAS uses Ubuntu SSO as an
external provider, so in order to use this controller, you have to
register at Ubuntu SSO. In order to get access to the JAAS public
controller, please register through jujucharms.com or using this URL
https://jujucharms.com/login

The previous version of the command accepted the user name as a
parameter. In order to login as a local user, pass the -u option.

juju login -u bob

Note that this release includes only the initial implementation of the
juju login command changes. Polishing and improved UX will come with
following releases.


## Resolved Issues

Check the milestones for a detailed breakdown of Juju and conjure-up
bugs corrected.

https://github.com/conjure-up/conjure-up/milestone/20?closed=1
https://launchpad.net/juju/+milestone/2.2-alpha1


## How do I get it?

If you are running Ubuntu, you can get Juju from the juju stable ppa:

   sudo add-apt-repository ppa:juju/devel; sudo apt-get update

   sudo apt-get install juju

Or install Juju from the snap store:

   snap install juju --classic --beta

Install conjure-up from the snap store:

   snap install conjure-up --classic --edge

If you are on Trusty, you'll need to run a few extra commands:

   sudo apt-get install snapd
   sudo groupadd lxd && sudo usermod -a -G lxd $USER
   sudo reboot

Now you can install snaps, including conjure-up, as normal:

   snap install conjure-up --classic --edge

Windows, CentOS, and MacOS users can get a corresponding Juju
installer at:

   https://launchpad.net/juju/+milestone/2.2-alpha1


## Feedback Appreciated!

We encourage everyone to let us know how you're using Juju. Send us a
message on Twitter using #jujucharms, join us at #juju on freenode, and
subscribe to the mailing list at j...@lists.ubuntu.com.


## More information

To learn more about these great technologies please visit
https://jujucharms.com and http://conjure-up.io.


-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui

-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

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

2017-03-16 Thread Tim Van Steenburgh 
A. 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.cozan...@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   / Canonical UK LTD  /
> Juju 
> samuel.cozan...@canonical.com
> mob: +33 616 702 389
> skype: samnco
> Twitter: @SaMnCo_23
> [image: View Samuel Cozannet's profile on LinkedIn]
> 
>
> On Thu, Mar 16, 2017 at 9:17 AM, Andrew Wilkins <
> andrew.wilk...@canonical.com> wrote:
>
>> On Thu, Mar 16, 2017 at 3:57 PM Samuel Cozannet <
>> samuel.cozan...@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   / Canonical UK LTD  /
>>> Juju 
>>> samuel.cozan...@canonical.com
>>> mob: +33 616 702 389
>>> skype: samnco
>>> Twitter: @SaMnCo_23
>>> [image: View Samuel Cozannet's profile on LinkedIn]
>>> 
>>>
>>> On Thu, Mar 16, 2017 at 8:52 AM, Andrew Wilkins <
>>> andrew.wilk...@canonical.com> wrote:
>>>
>>> On Tue, Mar 14, 2017 at 8:48 PM Tim Van Steenburgh <
>>> tim.van.steenbu...@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@lists.ubuntu.com
>>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>>> an/listinfo/juju
>>>
>>>
>>> --
>>> Juju mailing list
>>> Juju@lists.ubuntu.com
>>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>>> an/listinfo/juju
>>>
>>>
>>>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

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

2017-03-16 Thread Samuel Cozannet 
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   / Canonical UK LTD  / Juju

samuel.cozan...@canonical.com
mob: +33 616 702 389
skype: samnco
Twitter: @SaMnCo_23
[image: View Samuel Cozannet's profile on LinkedIn]


On Thu, Mar 16, 2017 at 9:17 AM, Andrew Wilkins <
andrew.wilk...@canonical.com> wrote:

> On Thu, Mar 16, 2017 at 3:57 PM Samuel Cozannet <
> samuel.cozan...@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   / Canonical UK LTD  /
>> Juju 
>> samuel.cozan...@canonical.com
>> mob: +33 616 702 389
>> skype: samnco
>> Twitter: @SaMnCo_23
>> [image: View Samuel Cozannet's profile on LinkedIn]
>> 
>>
>> On Thu, Mar 16, 2017 at 8:52 AM, Andrew Wilkins <
>> andrew.wilk...@canonical.com> wrote:
>>
>> On Tue, Mar 14, 2017 at 8:48 PM Tim Van Steenburgh <
>> tim.van.steenbu...@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@lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/
>> mailman/listinfo/juju
>>
>>
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/
>> mailman/listinfo/juju
>>
>>
>>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

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

2017-03-16 Thread Andrew Wilkins 
On Thu, Mar 16, 2017 at 3:57 PM Samuel Cozannet <
samuel.cozan...@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   / Canonical UK LTD  /
> Juju 
> samuel.cozan...@canonical.com
> mob: +33 616 702 389
> skype: samnco
> Twitter: @SaMnCo_23
> [image: View Samuel Cozannet's profile on LinkedIn]
> 
>
> On Thu, Mar 16, 2017 at 8:52 AM, Andrew Wilkins <
> andrew.wilk...@canonical.com> wrote:
>
> On Tue, Mar 14, 2017 at 8:48 PM Tim Van Steenburgh <
> tim.van.steenbu...@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@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

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

2017-03-16 Thread Samuel Cozannet 
I am using the default settings, no change as far as I know to what Juju
would do by default.


--
Samuel Cozannet
Cloud, Big Data and IoT Strategy Team
Business Development - Cloud and ISV Ecosystem
Changing the Future of Cloud
Ubuntu   / Canonical UK LTD  / Juju

samuel.cozan...@canonical.com
mob: +33 616 702 389
skype: samnco
Twitter: @SaMnCo_23
[image: View Samuel Cozannet's profile on LinkedIn]


On Thu, Mar 16, 2017 at 8:52 AM, Andrew Wilkins <
andrew.wilk...@canonical.com> wrote:

> On Tue, Mar 14, 2017 at 8:48 PM Tim Van Steenburgh <
> tim.van.steenbu...@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@lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/
>> mailman/listinfo/juju
>>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

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

2017-03-16 Thread Andrew Wilkins 
On Tue, Mar 14, 2017 at 8:48 PM Tim Van Steenburgh <
tim.van.steenbu...@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@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju