[00:50] <mwhudson> hi
[00:50] <mwhudson> i'm trying to follow https://maas.ubuntu.com/docs/quantal/juju-quick-start.html
[00:50] <mwhudson> and having a few problems
[02:41] <marcoceppi> mwhudson: what are the issues you're having?
[02:41] <mwhudson> marcoceppi: ah, hi
[02:41] <mwhudson> marcoceppi: i overcame my initial issues but now i get
[02:41] <mwhudson> root@calxeda02-11-00:~# juju  bootstrap
[02:41] <mwhudson> 2013-04-19 21:41:45,622 INFO Bootstrapping environment 'maas' (origin: distro type: maas)...
[02:41] <mwhudson> 2013-04-19 21:41:47,124 ERROR No matching node is available.
[02:42] <marcoceppi> mwhudson: Just so you know, I glanced over those docs and they're pretty outdated
[02:42] <mwhudson> marcoceppi: i sort of suspected as much
[02:43] <mwhudson> i'm wondering if this is some kind of series (precise vs quantal) thing
[02:43] <mwhudson> but it's all pretty opaque to me :)
[02:43] <marcoceppi> Did you install Juju from the ppa or from the distro?
[02:44] <mwhudson> ppa
[02:45] <marcoceppi> excellent, do you have nodes in maas that are 'ready' (or whatever the state is that maas displays)?
[02:45] <mwhudson> yeah
[02:46] <mwhudson> and clicking 'start node' on one of them worked
[02:46] <mwhudson> (eventually :-)
[02:47] <marcoceppi> mwhudson: cool, let me poor over my notes from when I tried this about a year ago
[02:47] <mwhudson> i've got as far as seeing "MAASAPINotFound: File not found" and "NodesNotAvailable: No matching node is available." in the maas.log file when i try to bootstrap
[02:47] <mwhudson> but i don't know what arguments are being passed...
[02:47] <mwhudson> was poking around the juju source
[02:48] <mwhudson> marcoceppi: fwiw, this is an armhf setup
[02:49] <marcoceppi> heh, so all bets are off ;)
[02:49] <mwhudson> i couldn't possibly comment!
[02:49] <marcoceppi> When I tested this, I used virtual box to simulate maas nodes, so what I got working probably isn't a standard setup
[02:50] <marcoceppi> mwhudson: A couple of things, are the nodes assigned to the same user whos oauth key you're using?
[02:50] <mwhudson> marcoceppi: the nodes are not assigned at all yet
[02:50] <mwhudson> there is only one user set up in maas yet
[02:51] <marcoceppi> mwhudson: I think that user needs to "own" them to use them, which might be why you're getting the no matching node available
[02:51] <mwhudson> oh ok
[02:51] <marcoceppi> I found this: http://askubuntu.com/questions/172011/no-matching-node-is-available-error-when-trying-to-bootstrap-juju
[02:51] <mwhudson> maas-cli default node acquire node-.* sort of thing?
[02:52] <mwhudson> well
[02:52] <mwhudson> commissioning is complete
[02:52] <marcoceppi> mwhudson: I wouldn't be able to say
[02:52] <mwhudson> hm
[02:52] <mwhudson> the api method that bootstrapping is calling (and failing on) is acquire
[02:53] <marcoceppi> ah, so it acquires them for the user
[02:53] <mwhudson> yeah
[02:53] <marcoceppi> All the questions on Ask Ubuntu about that error say that means there are no machines "ready" but as you've said that's not the case
[02:53] <mwhudson> right
[02:53] <mwhudson> i'm about >< this far from editing maas source to add some logging methods :)
[03:04] <mwhudson> ah hahahaha
[03:04] <mwhudson> POST:<QueryDict: {u'mem': [u'512'], u'cpu_count': [u'1'], u'arch': [u'amd64'], u'op': [u'acquire']}>,
[03:04] <mwhudson> i think i can see the problem here
[03:05] <marcoceppi> OH, right it defaults to amd64
[03:06] <marcoceppi> For all cloud providers
[03:06] <marcoceppi> You should be able to change that with --constraints "arch=armhf" in the bootstrap and subsequent commands
[03:07] <marcoceppi> mwhudson:  https://juju.ubuntu.com/docs/constraints.html
[03:07] <mwhudson> i can't put that into environments.yaml?
[03:09] <mwhudson> hm
[03:09] <mwhudson> progress
[03:10] <mwhudson> LookupError: SSH authorized/public key not found.
[03:10] <mwhudson> oh
[03:10] <mwhudson> right
[03:10] <mwhudson> the key isn't on this node...
[03:10] <marcoceppi> mwhudson: unfortuntately no, you'll have to specify it for each bootstrap, and then either keep specifying it for each deploy or use set-constraints to change the default
[03:15] <mwhudson> ok
[03:19] <mwhudson> well, i presume *something* is happening :)
[03:20] <marcoceppi> mwhudson: if bootstrap exited cleanly, then there's a good chance something _is_ happening after a few mins you'll find a node somewhere has turned on and is ready to roll
[03:22] <mwhudson> yeah
[03:23] <mwhudson> ah yes, life on the serial console of the allocated node
[03:23] <marcoceppi> huzzah
[03:23] <mwhudson> i guess i'll be wanting to set up a local archive mirror if i'm going to do this a lot...
[03:23] <marcoceppi> mwhudson: probably a good idea
[03:24] <marcoceppi> maas esp can be pretty package hungry
[03:30] <mwhudson> although configuring packages seems to be taking the vast bulk of the time
[03:30] <mwhudson> i wonder if anything came of that "dd an image onto the disk" idea...
[03:46] <mwhudson> frigging ssh host key checking
[03:49] <mwhudson> marcoceppi: seems that the arch constraint was automatically propagated into the environment
[03:50] <marcoceppi> mwhudson: they may have changed the default behavior of bootstrapping with constraints. It does make sense to make that the default
[03:51] <mwhudson> right, two more nodes pending
[03:51] <mwhudson> time to go home
[03:51] <mwhudson> marcoceppi: thanks for your help!
[03:51] <marcoceppi> mwhudson: o/ no problem!