Help with juju+maas setup

[Frantz, Chris]

Ok, I think I've figured things out.

My MAAS configuration was installing precise on my nodes, whereas raring is needed in order to get the correct version of MongoDB installed.

I edited /etc/maas/import_pxe_files to say:

# raring was not originally on the list
RELEASES="precise quantal raring"
# And raring apparently doesn't have an ARM version available yet.
ARCHES="amd64/generic i386/generic"

Re-ran /usr/sbin/maas-import-pxe-files.
Reconfigured MAAS to use raring as the default.
Deleted bootstrap-verify and provider-state from my previous bootstrap attempt:

$ maas-cli file delete boostrap-verify
$ maas-cli file delete provider-state

Bootstrap again using juju-core from launchpad (compiled from trunk a few days ago)

$ juju bootstrap

Then after maas provisioned and deployed the machine, I can

$ juju status
machines:
  "0":
    agent-state: started
    agent-version: 1.11.1.1
    dns-name: vsr19e1b3.master
    instance-id: /MAAS/api/1.0/nodes/node-97d895c4-dd7d-11e2-80f4-001a4b33aea8/
    series: raring
services: {}

Now off to try deploying some sample charms.
--Chris


-----Original Message-----
From: John Arbash Meinel [mailto:john at arbash-meinel.com] 
Sent: Wednesday, July 10, 2013 11:33 PM
To: Frantz, Chris
Cc: juju at lists.ubuntu.com
Subject: Re: Help with juju+maas setup

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2013-07-08 18:57, Frantz, Chris wrote:
> Hello,
> 
> 
> 
> I?m trying to setup a really simple Juju+MaaS setup to learn more 
> about both products.
> 
> 
> 
> I?ve got maas 1.3+bzr1461+dfsg-0ubuntu2 running on Ubuntu 13.04.
> I have 3 other systems successfully PXE booting and installing the 
> basic 12.04.2 LTS image.
> 
> 
> 
> On the system running the MaaS region controller, I?m running juju 
> from the launchpad trunk (e.g. go get launchpad.net/juju-core/?).
> It appears that I have successfully bootstrapped:  one of my nodes is 
> allocated to root and is running MongoDB.  During the bootstrap 
> process, the target installed an older version of mongo, so, I just 
> punted and overwrote the binaries with the newer version of MongoDB 
> and restarted the node. Everything seemed to come up fine after that.
> 
> 
> 
> As of now,  I?m unable to ?juju status?.  Juju appears to hang for
> 60 seconds and then emits ?error: cannot log in to admin databse? 
> as in https://bugs.launchpad.net/juju-core/+bug/1178328.
> 

What constitutes a "newer version of MongoDB"? The main concern is
that Juju enables SSL connections to Mongo, which requires fairly
specific versions of the binary. I think the version in Saucy (and
maybe Raring) is valid, but prior versions did not have SSL enabled,
so Juju has to install MongoDB from a PPA instead.

Can you give a bit more context as to what is running where?

Thanks,
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlHeNWwACgkQJdeBCYSNAAM/9QCdFze6DO8HQK+TjR6XdPfdn7Es
xjEAoLeHH5JTvEb2TXnrcmZx+JxtzBCw
=z7h6
-----END PGP SIGNATURE-----