Juju on a Raspberry pi

[Matthew Williams]

HI Dave,

Thanks for replying, it's comforting to know I basically worked out what
was going on regarding the linking.  I've replied inline below

Cheers

Matt


On Mon, Jun 17, 2013 at 12:40 AM, David Cheney
<david.cheney at canonical.com>wrote:

>
>
>
> On Sat, Jun 15, 2013 at 2:04 AM, Matthew Williams <
> matthew.williams at canonical.com> wrote:
>
>> Hi Folks,
>>
>> I got bored the other night and wondered how far I could get installing
>> juju on a raspberry pi. I thought it might be useful to share my progress,
>> and also get some answers to questions I have:
>>
>> Using Juju 1.10.0
>>
>> I built this using the tgz on the juju-core downloads page (although it
>> appears the lpad dependency is missing). I had to do the build in stages:
>>
>> go build launchpad.net/juju-core/cmd/juju
>> go build launchpad.net/juju-core/cmd/jujud
>> go build launchpad.net/juju-core/cmd/builddb
>> go build launchpad.net/juju-core/cmd/charmd
>> go build launchpad.net/juju-core/cmd/charmtool
>>
>> Trying to do it in one lump (go build lp.net/juju-core/...) always seg
>> faulted, I set the memory split for 240M CPU and 16M GPU and had a tmpfs 1G
>> but still could only build by doing it in stages.
>>
>
> Yup, a 256mb version 1 model b won't really cut the mustard. linking juju
> takes hundreds of megabytes.
>

>
>>
>> Once it was built juju bootstrap resulted in
>> error: no matching tools available
>> Q: I'm guessing this is because it can't find a juju-10.0-unknown-arm
>> version of juju to install onto the bootstrap node?
>>
>
> ^ i'm assuming the error is cannot find juju-1.10.0-unknown-arm. This is
> the usual problem of the cli taking the tools version from the client
> rather than having a sane default. I thought that this was fixed for 1.10.
> I'm sure it is fixed at tip. The unknown comes from the pi missing
> /etc/lsb-release or not having sane lsb_release -a output
>
>
>> juju bootstrap --upload-tools
>> error: cannot start bootstrap instance: no "precise" images in us-east-1
>> with arches [arm]
>> Q: This is because it needs to find an arm image to start up - and it
>> doesn't look like aws have any?
>>
>
> Same issue as before, the cli is taking the arch of the client.
>
>
>>
>> Using tip I had more success:
>>
>> just doing go get launchpad.net/juju-core/... I was able to get juju
>> built without having to mess around with memory setting or increasing tmpfs.
>> Q: Could this be down to goyaml not depending on the c libraries anymore?
>>
>
> Yes, linking consumes less memory and takes fewer steps when we don't use
> cgo.
>
>
>> When I run juju bootstrap --upload-tools I get the same error us with
>> 1.10.0 - as I said before I guess this is because aws doesn't have arm
>> images of ubuntu?
>>
>>
> Please check the bug tracker, there must be a dozen bugs about that
> problem by now. Pick one and comment.
>
>
>> I was able to get as far as running a bootstrap node when just doing juju
>> bootstrap on tip. My bootstrap node was an instance of ami-e7582d8e
>> (precise amd64) However when I do juju deploy wordpress (you have to start
>> somewhere) the command returns and I see a new machine pending, but an
>> instance never starts.
>>
>
> If you read the log of the provisioner, juju debug-log is useful for this,
> it'll probably be trying to start an arm machine and not finding any
> suitable ami for it or, b can't find the tools, again looking for arm.
>

I looked at the time and didn't see anything meaningful, Looking again it
appears that I'm suffereing from
https://bugs.launchpad.net/juju-core/+bug/1191577. So I'll wait to see what
happens when this is fixed.


>
>
>> Q: Is this likely to be an issue with tip juju communicating with a
>> bootstrap agent running 1.11.0?
>>
>
> nope.
>
>
>> Here's a paste that shows the different versions using tip and a machine
>> that stays in pending
>>
>> http://pastebin.ubuntu.com/5765093/
>>
>> I understand that juju wasn't really designed with the raspberry pi in
>> mind, but I thought it would be a fun little exercise (and it was) - plus
>> it looks like we're almost there anyway??
>>
>
> This should just work. Replace arm with i386 and you'll have the same
> breakage.
>
>
>>
>> Thanks
>>
>> Matt
>>
>>
>> --
>> Juju mailing list
>> Juju at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20130617/0b56e6cb/attachment.html>