On Fri, Feb 7, 2014 at 11:40 AM, Dave Cheney <email address hidden> wrote:
> On Fri, Feb 7, 2014 at 7:37 PM, Antonio Rosales
> <email address hidden>wrote:
>
>> After discussion John and Dan the mapping for arm and ppc should look
>> like:
>>
>> aarch64 should map to arm64
>>
>
> This one should be the other way around
>
>
>> ppc64 should map to ppc64el
Apologies, there's a couple points of confusion here. To be explicit:
Yes, the le/el is transposed between the two ppc64 ones. Weird, I know.
Yes, we said ppc64 above but I'm saying ppc64le now. This is because
code inspection shows that juju is using 'uname -m' here in the script
it passes to the manual provisioned hosts, and this wasn't clear when
we asked a ppc64el/le porter about it. I explicitly asked our porter
friend to run 'uname -m', and he confirmed it returns "ppc64le".
On Fri, Feb 7, 2014 at 11:40 AM, Dave Cheney <email address hidden> wrote:
> On Fri, Feb 7, 2014 at 7:37 PM, Antonio Rosales
> <email address hidden>wrote:
>
>> After discussion John and Dan the mapping for arm and ppc should look
>> like:
>>
>> aarch64 should map to arm64
>>
>
> This one should be the other way around
>
>
>> ppc64 should map to ppc64el
Apologies, there's a couple points of confusion here. To be explicit:
uname -m returns: ppc64le, aarch64
dpkg uses: ppc64el, arm64
Yes, the le/el is transposed between the two ppc64 ones. Weird, I know.
Yes, we said ppc64 above but I'm saying ppc64le now. This is because
code inspection shows that juju is using 'uname -m' here in the script
it passes to the manual provisioned hosts, and this wasn't clear when
we asked a ppc64el/le porter about it. I explicitly asked our porter
friend to run 'uname -m', and he confirmed it returns "ppc64le".