arch constraint default changed?

[Gustavo Niemeyer]

Why isn't the default tweaked by --upload-tools itself then?  We
should be optimizing these options for users, rather than for
developers, and it sounds sensible to assume that the vast majority of
users do want to deploy on amd64 rather than i386 or arm.

On Mon, May 12, 2014 at 2:53 PM, Nate Finch <nate.finch at canonical.com> wrote:
> However, the fix is slightly different than just "always choose amd64".
> Instead, we always choose the same architecture as the client machine, that
> way if the user uses --upload-tools, the tools will actually work on the
> cloud machine.
>
> This means that if you're running i386, you would still need --arch amd64 to
> get amd64 machines in the cloud.
>
>
> On Mon, May 12, 2014 at 1:50 PM, John Meinel <john at arbash-meinel.com> wrote:
>>
>> https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1304407
>>
>> It should be fixed in 1.18.3.
>> John
>> =:->
>>
>>
>>
>> On Mon, May 12, 2014 at 9:36 PM, Henning Eggers <henning at keeeb.com> wrote:
>>>
>>> Hi!
>>>
>>> I just noticed that I now have specify the arch constraint if I want
>>> amd64
>>> instances. Without it, I get i386 instances. "juju help constraints"
>>> still
>>> tells me that amd64 is supposed to be the default.
>>>
>>> I am using juju 1.18.2 on EC2, precise on the instances, trusty on my
>>> workstation.
>>> Has this since been fixed? Or is it an intentional change and the help
>>> page is
>>> outdated?
>>>
>>> Cheers,
>>> Henning
>>>
>>>
>>> --
>>> 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
>



-- 

gustavo @ http://niemeyer.net