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.
H
On Tue, May 13, 2014 at 12:41 PM, John Meinel wrote:
> You might be running into this:
>
> http://askubuntu.com/questions/458535/how-to-change-juju-bootstrap-time-from-the-10min-it-gives-you
> John
> =:->
>
>
> On Mon, May 12, 2014 at 4:47 PM, boyd yang wrote:
>
>> Hello,
>>
>> I got juju bootstr
On Tue, May 13, 2014 at 4:04 PM, Andrew Wilkins <
andrew.wilk...@canonical.com> wrote:
> On Tue, May 13, 2014 at 12:41 PM, John Meinel wrote:
>
>> You might be running into this:
>>
>> http://askubuntu.com/questions/458535/how-to-change-juju-bootstrap-time-from-the-10min-it-gives-you
>> John
>> =:
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
whatsoeve
(for pedantry's sake: constraints are not really the issue here. They're
just a mechanism for filtering the acceptable set of results for a
provisioning decision; and they handy from a dev perspective in that they
allow us also to filter the inputs and cut down on the range of
possibilities we have
FWIW, I've gotten bug requests from a user that did a regular bootstrap and
then was trying to "juju upgrade-juju --upload-tools" and was confused that
his local machine wasn't able to upgrade tools for his environment. (he was
running i386 locally, and bootstrap created an amd64 machine).
And whil
FWIW, I think the byArch did a plain sort.Strings() which happens to pick
amd64 because it is before all other in a typographical fashion. IIRC, it
may have mutated a lot over time because the sorting was blocking bootstrap
from working on ppc64 which was why it was removed. Also, on MaaS, MaaS
doe
On Tue, May 13, 2014 at 8:18 AM, John Meinel wrote:
> FWIW, I've gotten bug requests from a user that did a regular bootstrap and
> then was trying to "juju upgrade-juju --upload-tools" and was confused that
> his local machine wasn't able to upgrade tools for his environment. (he was
> running i3
This sounds a lot like the static build problem: once a piece of shared
code is fixed/updated, how to make sure everything using it gets rebuilt?
charm-helpers is such a case. It's shared code used by a growing number of
charms.
Case in point: https://bugs.launchpad.net/charm-helpers/+bug/1317980
For the record, we can easily send branches against charms that matter
to us for this particular case (as we will for few other
landscape-owned branches waiting for review [1] [2] [3], hint hint :)
).
But this seems like a problem in need of a more general (and scalable) solution.
- Chris (tribaa
For what it's worth, I agree with everyone. John and I discussed it, and I
thought we had decided that we needed to use the local arch because of
upload tools, evidently John though we'd decided in the other direction.
And Gustavo is right that we should have pushed the discussion to the
mailing
Howdy,
On Tue, May 13, 2014 at 08:04:14AM +0400, John Meinel wrote:
I actually think this isn't about someone doing "juju set-env" but someone
just ssh'ing into the machine and changing things with a text editor.
Yes, this is my top concern.
Ian: Thanks for your comments and explanation. Thos
Hi everyone,
Now that the Vagrant boxes are sorted we're going to have a charm
school this Friday outlining a Vagrant workflow.
1900 UTC / 1500 EDT / 1200 (Noon PDT)
http://ubuntuonair.com
#juju on Freenode
Setting this up prior to the course will help you:
https://juju.ubuntu.com/docs/config-va
I wanted to announce this early as there is a bunch of expertise out
there blossoming on how to Troubleshoot Juju, so we're going to do two
charm schools over 2 weeks to gather all of this information. I wanted
to get this announcement out early.
June 6: Troubleshooting I
June 13: Troubleshooting
great! will be there :)
Abs,
Sebas.
2014-05-13 14:30 GMT-03:00 Jorge O. Castro :
> I wanted to announce this early as there is a bunch of expertise out
> there blossoming on how to Troubleshoot Juju, so we're going to do two
> charm schools over 2 weeks to gather all of this information. I wan
We shouldn't ever have to worry about whether or not --upload-tools was
used, because it's *already* been used at the point where we pick
instances, and the single possible arch is thus already chosen, entirely
independent of constraints or anything else. The only question should be:
given *multipl
On Tue, May 13, 2014 at 10:45 AM, Joey STANFORD wrote:
> Howdy,
>
>
> On Tue, May 13, 2014 at 08:04:14AM +0400, John Meinel wrote:
>
>> I actually think this isn't about someone doing "juju set-env" but someone
>> just ssh'ing into the machine and changing things with a text editor.
>>
>
> Yes, t
17 matches
Mail list logo
