Strongly agree with gustavo/henning. In *all* cases, the possibilities are defined by the arches of the available tools, images, and instance types. When using --upload-tools, the arches of the available tools are further restricted, and may thus force i386, but that should have no impact whatsoever on our method for choosing amongst the available options.
I remember writing a byArch sort that prioritised amd64; it seems to have disappeared at some point in the last year, as the tools/instance-types/etc code evolved, but this was always intended behaviour; please reinstate it. On Tue, May 13, 2014 at 9:15 AM, Henning Eggers <henn...@keeeb.com> wrote: > Although I don't know about --upload-tools, I have to agree with Gustavo > here > that selecting the instance arch depending on the workstation arch is > unintuitive from a user's perspective. I would not expect that at all. > > Yes, amd64 is a very sensible default. I would wish that it stayed that > way. > > Henning > > Am 12.05.2014 19:58, schrieb 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.fi...@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. > >> > > > -- > 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