[00:00] <bigjools> if you alt-f8 (I think) you should see more output
[00:00] <bigjools> it takes a while
[00:00] <bigjools> it downloads some stuff from the repos
[00:01] <TheChistoso> it's been about 30 min.
[00:01] <bigjools> ok
[00:01] <bigjools> it should be around 5-10
[00:01] <TheChistoso> alt-f8 didn't give me anything -- but then again, i'm using it over the bmc and the keystroke may or may not be getting across
[00:01] <bigjools> ok
[00:01] <bigjools> one sec
[00:02] <TheChistoso> i don't suppose you know the default username/password?
[00:02] <bigjools> there isn't one
[00:02] <TheChistoso> (let me guess -- password is generated?)
[00:02] <bigjools> but there's a backdoor image that you can use to commission with that has a user/password set up
[00:02]  * bigjools looks for it
[00:02] <TheChistoso> well i can't ssh w/ the key i provided in my preferences
[00:02] <bigjools> no, you can't log in at all with commissioning
[00:03] <TheChistoso> it's past commissioning
[00:03] <bigjools> it's not - otherwise it would be ready
[00:03] <TheChistoso> it's commissioned -- it's deployed
[00:03] <bigjools> ...
[00:03] <TheChistoso> that is, the OS is installed, cloud-init reported as having completed
[00:03] <bigjools> ok let's get the terminology straight
[00:03] <TheChistoso> lol okay (c:
[00:03]  * mwhudson was going to say :)
[00:04] <bigjools> you were previously at the "ready" state?
[00:04] <TheChistoso> i was at whatever the name for the state is when you've brought up the machine, maas recognizes it, and then i hit "accept & commission" (or "start & commission")
[00:04] <bigjools> that is, it enlisted, powered off, you clicked "accept and commission" and it powered up, did stuff and powered off again
[00:05] <TheChistoso> that ran -- the OS installed, it restarted, there's a login prompt, w/ some output indicating that cloud init completed
[00:05] <bigjools> wait
[00:05] <mwhudson> how did you tell the os installed?
[00:05] <mwhudson> it probably didn't
[00:05] <TheChistoso> i watched the os install
[00:05] <bigjools> on the second boot, did it power down?
[00:06] <bigjools> it is not installing anything when it commissions
[00:06] <bigjools> nothing usable for you anyway
[00:06] <TheChistoso> honestly, there were a few reboots and i'm not sure when it powered down and when it didn't
[00:06] <TheChistoso> yes, i know
[00:06] <bigjools> what state does it say that node has in maas now?
[00:07] <TheChistoso> it starts up and you throw something on there (enough to communicate w/ maas and provide it w/ information so the admin can review and decide to actually proceed)
[00:07] <bigjools> what state does it say that node has in maas now?
[00:07] <TheChistoso> and then when you accept and commission, it reboots, and at that point the OS is actually installed
[00:08] <TheChistoso> status shows "allocated to sysadmin"
[00:08] <Marlinc> But wait if I get it right. If I want MAAS to have another node I just boot it up ones from PXE and MAAS then handles it from then on?
[00:08] <bigjools> ok so your story of events is incorrect somewhere
[00:08] <TheChistoso> i'm telling you exactly what i saw
[00:08] <TheChistoso> (as i recall it, granted :D )
[00:08] <bigjools> TheChistoso: if it says "allocated" you clicked something else
[00:09] <bigjools> can you "ssh ubuntu@<your node>"
[00:09] <bigjools> because you've commissioned it, it shut down, and now you clicked "start"
[00:09] <TheChistoso> yes -- i did forget that step
[00:10] <bigjools> right, so you have an installed node
[00:10] <mwhudson> so is it possible that the node is in fact ready for use?
[00:10] <bigjools> so ssh to the ubuntu user
[00:10] <Marlinc> My node can't be booted up from the network (at least it doesn't seem to work) or another way. What could I do about that? Could the node still work with MAAS
[00:10] <TheChistoso> i can't ssh into the machine
[00:10] <bigjools> Marlinc: without control of PXE/DHCP you cannot use maas
[00:11] <Marlinc> PXE and DHCP work
[00:11] <bigjools> TheChistoso: how are you trying to ssh in?
[00:11] <Marlinc> It cant start from poweroff state
[00:11] <Marlinc> Using WOL
[00:11] <Marlinc> Thats what I mean
[00:12] <bigjools> Marlinc: ok so just power up manually after maas requests a startup
[00:12] <Marlinc> Okay great
[00:12] <bigjools> (in that order, specifically)
[00:12] <bigjools> if you try to boot a node that maas doesn't think should be starting, it'll do weird stuff
[00:13] <TheChistoso> from the maas controller, logged in as "sysadmin" (w/ the same account name configured in maas as a super user and w/ the SSH key registered there that corresponds w/ my unix account), i type: ssh ubuntu@<ip of node>
[00:14] <TheChistoso> i've also tried it on port 2181...
[00:14] <bigjools> did you add your public ssh key to the sysadmin account in maas *before* starting up the node?
[00:14] <bigjools> fwiw, juju makes this stuff much easier
[00:14] <TheChistoso> of course i can't be sure that's the ip of the machine b/c i can't configure it to use a static ip
[00:15] <bigjools> no, you can't because MAAS manages the DNS
[00:15] <TheChistoso> i'd love to use juju w/ this -- but i can't get nodes working in order to use juju w/ it (c:
[00:15] <bigjools> you're looking at the problem incorrectly
[00:15] <bigjools> you have got nodes working, you just think you don't
[00:16] <bigjools> it's a cloud-like resource, not an installer
[00:16] <bigjools> once nodes are at "ready" you just set the API key in environments.yaml etc and then you can use juju
[00:17] <bigjools> are you using maas to manage DNS?
[00:17] <Marlinc> Should a MAAS node have PXE boot as primary boot location?
[00:17] <TheChistoso> yes maas is managing dns
[00:17] <bigjools> Marlinc: you mean in the BIOS?  yes
[00:18] <Marlinc> Okay
[00:18] <TheChistoso> i understand how it's supposed to work
[00:18] <bigjools> TheChistoso: ok so just resolve through there and ignore the IP - the DNS  entry will be the same as the node's name in the MAAS UI
[00:18] <bigjools> the zone file will be named after the cluster's name
[00:20] <TheChistoso> well nslookup doesn't find it - looking at resolv.conf shows that you're not setting up the local machine to use itself for DNS name resolution
[00:22] <bigjools> TheChistoso: no, you have to do that
[00:23] <bigjools> maas cannot set up resolv.conf for machines it doesn't boot, it's set via DHCP
[00:24] <TheChistoso> it can set the machine it's running on's network interfaces
[00:24] <TheChistoso> i'm doing these commands from the same machine that maas is running on
[00:24] <bigjools> that machine is not managed by maas
[00:25] <TheChistoso> at any rate -- i added 127.0.0.1 to /etc/network/interfaces, restarted networking, and now i can ssh into the machine
[00:25] <TheChistoso> you would think that maas itself would want to use its own DNS services (c:
[00:25] <bigjools> I just explained why it's how it is
[00:26] <TheChistoso> i understand what you said -- but i simply disagree that maas shouldn't use its own DNS service to resolve names locally
[00:27] <bigjools> I think you don't understand
[00:27] <bigjools> but it;s working so goofd
[00:27] <bigjools> good
[00:27] <TheChistoso> well please explain -- if i truly don't understand something, then a little education would be good (c:
[00:28] <bigjools> I explained above
[00:28] <bigjools> "maas cannot set up resolv.conf for machines it doesn't boot, it's set via DHCP"
[00:28] <TheChistoso> yes i understand all of that
[00:28] <mwhudson> i think i would have been pretty upset if maas had started mutilating the networking of the host i installed it on
[00:28] <bigjools> so you understand why you need to set resolv.conf yourself?
[00:29] <TheChistoso> but when you install maas, you could configure the local machine to resolve against itself
[00:29] <mwhudson> (even if i was using maas-dns, which i'm not)
[00:29] <TheChistoso> at the very least, it would make sense to document this
[00:29] <bigjools> maas should not mess with networking on non-managed machines
[00:29] <bigjools> I agree with the doc
[00:29] <bigjools> we should change it
[00:30] <bigjools> since you had trouble working this out
[00:30] <TheChistoso> it's certainly not immediately obvoius that the reason why something can't transition to ready is that nameservers aren't configured properly
[00:31] <TheChistoso> (assuming this is the ultimate culprit)
[00:31] <bigjools> you are using the state names incorrectly
[00:31] <bigjools> ready is when something is available in the pool
[00:31] <bigjools> not something that's deployed
[00:32] <bigjools> and nameservers configuration has nothing to do with state transitions
[00:32] <mwhudson> TheChistoso: there is no state transition in maas when the node is installed and ready for use
[00:32] <TheChistoso> the maas ui shows the node's deployed -- so what's the next state called that i want to get it to?
[00:32] <Marlinc> I think MAAS isn't a toy but really it feels like it. Especially because I've never worked with PXE and never with machines that boot automatically when needed. Really this is just awesome
[00:32] <mwhudson> it's just "allocated"
[00:32] <Marlinc> I just connected another machine tot the network. Set PXE as default boot mode and enabled WOL
[00:33] <Marlinc> And it works
[00:33] <bigjools> it transitions from "ready" to "allocated" when someone requests a node
[00:33] <TheChistoso> mwhudson: the first screen (i have just 1 node) says "1 node deployed"
[00:33] <bigjools> Marlinc: great!
[00:33] <bigjools> TheChistoso: look at the detail node list
[00:33] <TheChistoso> the entire pie chart is blue
[00:33] <TheChistoso> yes -- that says "allocated"
[00:33] <TheChistoso> so you need to get your verbage consistent
[00:33] <bigjools> the pie chart is geared to managing 1000s of nodes at once
[00:33] <mwhudson> eh, maybe the node list and the pie chart could use the same words...
[00:34] <bigjools> yeah, that's inconsistent
[00:34]  * bigjools files a bug
[00:34] <Marlinc> Wow WOL is just magic
[00:35] <bigjools> Marlinc: WoL is a hack, you can't power down using it
[00:35] <Marlinc> Well okay thats true
[00:35] <bigjools> it suffices for basic testing
[00:36] <TheChistoso> okay, so what would my next steps be?
[00:36] <TheChistoso> i've defined .juju/environments.yaml and i ran juju bootstrap and it tells me that no matching nodes are available
[00:36] <Marlinc> Mmm the second machine doesn't do much but I'm thinking it is a hardware problem because it is a old computer
[00:37] <bigjools> TheChistoso: I presume you only have one node commissioned and it's already in use?
[00:38] <TheChistoso> by "in use" do you mean allocated to a user? then yes (although i'm fuzzy on how a node is allocated to a user -- it is tied to the user that accepts, commissions, and starts the node?)
[00:38] <bigjools> TheChistoso: no, it's the user who "starts" it
[00:38] <TheChistoso> (*is it)
[00:38] <TheChistoso> okay -- that makes sense
[00:38] <bigjools> only admins can accept for commissioning
[00:39] <TheChistoso> (minor feature request, although perhaps it already exists -- auto-accept, commission, and start, assigning it to a default user)
[00:39] <bigjools> that won't be accepted as a feature
[00:39] <bigjools> it's not designed to work like that
[00:39] <bigjools> you need to think cloud-like
[00:40] <Marlinc> It looks like the DNS is not working the way its supposed to work: 2013-05-02 02:39:13,994 ERROR Invalid host for SSH forwarding: ssh: Could not resolve hostname fqehy.master: No such file or director
[00:40] <Marlinc> It is managed at least it should be
[00:40] <Marlinc> My laptop is using the MAAS server's DNS server
[00:41] <bigjools> where's that error from?
[00:41] <Marlinc> Juju
[00:41] <TheChistoso> since these are meant to serve physical machines, makes sense to me that if you've racked, cabled, and powered it up, then you want to commission it.
[00:41] <Marlinc> When I try to run juju status
[00:42] <bigjools> TheChistoso: the commissioning process is more complicated than that in a DC, often people will want to do burn-ins, update firmware etc.
[00:42] <bigjools> Marlinc: can you manually look up that host?
[00:42] <Marlinc> Nope
[00:42] <Marlinc> Or well
[00:42] <Marlinc> It doesn't work
[00:43] <TheChistoso> well my suggestion is for those people who don't want to babysit the process :D
[00:43] <bigjools> can you check to see if it's present in the zone file
[00:43] <Marlinc> Let me take a look
[00:43] <bigjools> TheChistoso: we'll add a mass-accept at some point
[00:43] <TheChistoso> that would be better :D
[00:43] <Marlinc> Where's it stored?
[00:43] <bigjools> Marlinc: under /var/ib/maas IIRC
[00:44] <TheChistoso> okay, so do you think that i'm at the point where i should be able to use juju?
[00:44] <bigjools> TheChistoso: yep
[00:44] <bigjools> you need to release that node
[00:44] <TheChistoso> how do i do that?
[00:44] <bigjools> sadly there's no way in the UI of doing it (don't ask...), you need to use maas-cli
[00:44] <TheChistoso> ah...
[00:45] <Marlinc> Mm there's nothing related to DNS
[00:45] <bigjools> maas-cli does API calls
[00:45] <TheChistoso> can you point this out in the documentation? b/c i did not see it. gotta have my eyes checked...
[00:45] <bigjools> TheChistoso: I think we have gaps in the docs
[00:45] <TheChistoso> this seems like a major one
[00:45] <bigjools> which bit?
[00:46] <TheChistoso> that to actually use a node w/ juju you have to run a command
[00:46] <bigjools> you don't
[00:46] <TheChistoso> ?
[00:46] <TheChistoso> well i'm confused (c:
[00:47] <bigjools> juju will use available nodes on maas
[00:47] <bigjools> but you don't have any available
[00:47] <bigjools> because you started one manually already
[00:47] <TheChistoso> you'll have to slow down there b/c i'm thoroughly confused
[00:47] <bigjools> basically - just don't use "Start" in the UI
[00:48] <TheChistoso> i was just going to ask that
[00:48] <bigjools> it's completely unnecessary
[00:48] <bigjools> juju manages everything
[00:48] <bigjools> even the SSH key
[00:48] <TheChistoso> is that in the docs as well?
[00:48] <bigjools> it's in juju docs I expect
[00:48] <TheChistoso> it's natural, i think, to hit a "start" button when you see it (c:
[00:48] <bigjools> but there's a section on juju in the maas docs IIRC
[00:48] <TheChistoso> i don't recall reading anything that says "don't press that button!"
[00:49] <bigjools> I think the problem here is that you've not really understood how it works from a higher level.  Maybe we need a doc section for that.
[00:49] <TheChistoso> minor feature request: add a label or help text (or something) next to the button in maas when it says 'start" to prevent this from happening
[00:50] <Marlinc> Mmm.. None of the zone files contain any reference to the node bigjools
[00:50] <TheChistoso> i understand how juju is supposed to work (at a high level), but these are small details. c'mon now -- "don't hit start if you want to use it w/ juju"? that seems pretty confusing to anybody starting out.
[00:51] <bigjools> Marlinc: ok that means that something went wrong with parsing the dhcp leases
[00:51] <bigjools> TheChistoso: I think it's only confusing if you don't understand resource allocation concepts in maas
[00:51] <bigjools> Marlinc: please check the celery.log
[00:52] <Marlinc> Sure
[00:52] <bigjools> TheChistoso: which boils down to a higher-level doc that we need to explain these concepts
[00:52] <TheChistoso> given the bad documentation and the fact that i don't work on the product, i don't think it's hard to see why not
[00:53] <bigjools> this support stuff is largely done on an "as best" basis for non-paying customers
[00:53] <TheChistoso> i assumed juju worked w/ already running systems, simply orchestrating services atop already-installed OSes
[00:53] <Marlinc> Okay the're one error in there but it isn't very clear http://pastebin.ubuntu.com/5624546/
[00:53] <bigjools> I think you need to read the juju docs
[00:53] <TheChistoso> your paying customers don't read docs then, eh? (c:
[00:53] <bigjools> TheChistoso: no, they pay for consultants
[00:53] <TheChistoso> have you read your docs recently?
[00:54] <bigjools> You're welcome for the help
[00:54] <bigjools> Marlinc: aha, that's the problem
[00:54] <TheChistoso> i do thank you for your help -- i'm not trying to be ungrateful :/
[00:54] <bigjools> Marlinc: well, an indication of the problem
[00:54] <TheChistoso> but it does seem likely that a newbie (such as myself) has read the docs more recently than somebody working on the product
[00:54] <Marlinc> True
[00:55] <bigjools> TheChistoso: that's very likely
[00:55] <bigjools> the product evolves and things get missed, but the vast majority of people don't have problems
[00:55] <TheChistoso> so that experienmced somebody is trying to warn you that it's confusing.
[00:56] <TheChistoso> how do you know that? my previous attempt had me throwing my hands in the air and moving on to other solutions
[00:56] <TheChistoso> iow, you don't know how many people get frustrated w/ the product and leave w/o saying a word
[00:57] <bigjools> I know from speaking to many people they are happy with it. There will always be people with problems though - this is a complicated product solving a complicated problem.
[00:57] <TheChistoso> i know bind, dnsmasq, dhcp, cobbler, pxe, tftp, etc. and i found things confusing
[00:57] <Marlinc> There is a bug report with the same error but it is pretty old and I don't know if its still relevant
[00:57] <bigjools> Marlinc: are there log entries talking about leases?
[00:57] <TheChistoso> perhaps those folks have consultants who know the product and have been using it for a while? (c:
[00:57] <Marlinc> Well in my syslog
[00:58] <bigjools> Marlinc: specifically in the celery.log
[00:58] <Marlinc> [2013-05-02 02:57:33,775: INFO/Beat] Scheduler: Sending due task provisioningserver.tasks.upload_dhcp_leases
[00:58] <bigjools> TheChistoso: like I said, it's best effort, like all OSS projects.
[00:58] <bigjools> Marlinc: ok cool, one sec
[00:58] <Marlinc> [2013-05-02 02:57:33,780: INFO/MainProcess] Got task from broker: provisioningserver.tasks.upload_dhcp_leases[****]
[00:58] <Marlinc> These things?
[00:58] <Marlinc> Okay nice
[00:58] <TheChistoso> is maas not backed by canonical?
[00:58] <bigjools> it is
[01:00] <TheChistoso> so you have real dollars being thrown at it w/ staff dedicating at least some partial amount of their time to it. that's a great thing! now as an open source user of your product, i'm just trying to warn you that your documentation is lacking and you could be turning away users without knowing it.
[01:00] <bigjools> Marlinc: can you see your node's MAC/IP in the leases file?
[01:01] <Marlinc> It is
[01:01] <bigjools> TheChistoso: I'm sorry it wasn't up to scratch for you - people will try to make it better
[01:01] <TheChistoso> okay, so what are my options at this point? can i "un-start" (or "un-use") it so i can use it from juju?
[01:01] <bigjools> Marlinc: can you look at the celery-region log for errors
[01:01] <bigjools> TheChistoso: look at maas-cli
[01:02] <bigjools> it has a release command
[01:03] <Marlinc> There are bigjools http://pastebin.ubuntu.com/5624558/
[01:03] <bigjools> Marlinc: did you install maas-dns?
[01:03] <bigjools> and maas-dhcp
[01:03] <Marlinc> Yes I did it is running because my laptop is using it right now
[01:03] <Marlinc> And it is using the dhcp too
[01:03] <bigjools> weird
[01:04] <Marlinc> I did need to edit the /etc/network/interfaces file in order to make the DHCP work
[01:04] <bigjools> is maas in /etc/sudoers?
[01:04] <bigjools> is "rndc" available?
[01:04] <Marlinc> rndc is available
[01:04] <Marlinc> But maas is not in the sudoers file
[01:04] <bigjools> mmmm
[01:05] <bigjools> which version of maas are you using?
[01:05] <Marlinc> I've used the Ubuntu 13.04 install
[01:05] <bigjools> ok
[01:06] <bigjools> maas should be in sudoers anyway, which expains the other "omshell" failure
[01:06] <bigjools> not sure why it's not there
[01:06] <Marlinc> Well I don't know either
[01:06] <Marlinc> Just add it or?
[01:07] <bigjools> packaging should have added it
[01:07] <bigjools> one sec
[01:08] <Marlinc> k
[01:10] <TheChistoso> okay awesome -- pie chart is now green showing "1 node queued" and the node list shows its status as "ready"
[01:10] <TheChistoso> so at this point i can "juju bootstrap"?
[01:10] <Marlinc> Yes
[01:10] <TheChistoso> awesome!
[01:10] <Marlinc> environments.yaml is setup?
[01:11] <Marlinc> Or you could get the same problem as me :P the hostname's of nodes are not resolving
[01:12] <TheChistoso> i ran juju bootstrap and the node is now rebooting
[01:14] <bigjools> Marlinc: do you have a /etc/sudoers.d/99-maas-sudoers ?
[01:14] <TheChistoso> Marlinc: can you provide more information wrt your environment? network (including network mask), are these machines on the same L2 network, etc.
[01:15] <bigjools> his dns is not resolving because the node is not in the zone file
[01:15] <Marlinc> Ah that is available
[01:15] <bigjools> there are a few causes for that
[01:15] <Marlinc> I don't think it is my network setup
[01:16] <bigjools> Marlinc: have you got zone files in /etc/bind/maas/
[01:16] <TheChistoso> well bigjools has been working on the issue longer than i've paid attention so probably best for me to follow his line of thinking
[01:16] <Marlinc> named.conf.maas  named.conf.rndc.maas  rndc.conf.maas  zone.1.168.192.in-addr.arpa  zone.2.168.192.in-addr.arpa  zone.master
[01:17] <bigjools> is your node in zone.master?
[01:17] <bigjools> there should be a CNAME if so
[01:17] <Marlinc> Nope
[01:17] <TheChistoso> hmmm -- well it prompted for the partitioning scheme again
[01:17] <bigjools> TheChistoso: I'd ask in #ubuntu-server about that, I've never had that
[01:20] <Marlinc> It is not bigjools :p
[01:20] <bigjools> Marlinc: one secx
[01:20] <Marlinc> okay :)
[01:21] <bigjools> Marlinc: http://pastebin.ubuntu.com/5624592/
[01:21] <bigjools> try that and see what output you get
[01:21] <Marlinc> Okay
[01:22] <Marlinc> The output is good
[01:22] <Marlinc> ip->mac mappings
[01:22] <bigjools> you see your node?
[01:22] <Marlinc> Yep
[01:22] <bigjools> ok so something went wrong where it writes out the zone file
[01:23] <bigjools> let's try: sudo service apache2 restart
[01:24] <Marlinc> Mmm okay
[01:24] <Marlinc> Restarted
[01:24] <bigjools> it will reload the wsgi for maas which causes a job to rewrite the zone file
[01:24] <bigjools> so check the zone file(s) again
[01:25] <bigjools> and check celery-region.log to see if anything went wrong since you restarted
[01:26] <Marlinc> No new output in that log
[01:26] <Marlinc> And it is still in none of the bind maas files
[01:27] <bigjools> hmmm
[01:27] <bigjools> can you try renaming the node
[01:27] <bigjools> ands watch the log
[01:28] <Marlinc> Sure
[01:29] <Marlinc> It did a 'upload_dhcp_release'
[01:29] <Marlinc> It did a 'upload_dhcp_leases'
[01:29] <Marlinc> *
[01:29] <bigjools> yeah that runs periodically
[01:29] <Marlinc> Other then that nothing
[01:32] <bigjools> arey you looking in celery-region ?
[01:32] <Marlinc> Well tailed both of them
[01:32] <Marlinc> [2013-05-02 02:05:34,807: INFO/MainProcess] Task provisioningserver.tasks.rndc_command[6499426a-eb2c-4b30-bfbc-0314632cef2f] retry: None
[01:32] <Marlinc> None
[01:32] <Marlinc> Is the last
[01:37] <bigjools> I'm not sure what's going on, there are no errors but the file is not getting written
[01:38] <Marlinc> I'll reboot the thing
[01:38] <Marlinc> Maybe something is not working
[01:42] <Marlinc> Now
[01:42] <Marlinc> [2013-05-02 03:40:27,551: INFO/MainProcess] Task provisioningserver.tasks.rndc_command[6499426a-eb2c-4b30-bfbc-0314632cef2f] retry: None
[01:42] <Marlinc> None
[01:42] <Marlinc> Runs without issues
[01:43] <Marlinc> But there's still no entry
[01:49] <Marlinc> bigjools, ^
[01:49] <bigjools> yeah#
[01:49] <bigjools> trying to think
[01:49] <bigjools> someone else will be around soon that may have more ideas
[01:49] <Marlinc> Okay
[01:49] <Marlinc> What is soon? Because it is well time to sleep
[01:50] <Marlinc> For some hours already though
[01:50] <Marlinc> Usage: time [-apvV] [-f format] [-o file] [--append] [--verbose]
[01:50] <Marlinc>        [--portability] [--format=format] [--output=file] [--version]
[01:50] <Marlinc>        [--quiet] [--help] command [arg...]
[01:50] <Marlinc> do mei  2 03:50:07 CEST 2013
[01:50] <bigjools> !
[01:51] <bigjools> there's a guy near your TZ and one about to start, so just ping later
[01:51] <Marlinc> Okay
[01:51] <Marlinc> I'll see tomorrow
[01:51] <Marlinc> Good night
[01:52] <bigjools> good night
[03:04] <roaksoax> bigjools: howdy! just wanted to let you know that it seems there's not gonna be an sru anytime soon
[03:04] <bigjools> yay
[03:05] <roaksoax> bigjools: MIR'ing the dependencies is not as easy as it seems, and will probably require TB intervention, meaning, request the TB to provide a exception for those dependencies
[03:05] <bigjools> joy
[03:05] <roaksoax> yep
[04:34] <Dr{Who}> Hmm. i changed the IP of my 13.04 maas box and it needs some reconfigureing but I cant figure out what to run or edit. dpkg-reconfigure maas does not seem do do anything on this release.
[04:51] <bigjools> Dr{Who}: it's all done in the UI
[04:51] <bigjools> edit the cluster
[05:48] <TheChistoso> okay, so i added a new machine to maas. i didn't hit "start node" yet. the machine is currently powered off. i should be able to just use it automatically from juju, correct?
[05:48] <TheChistoso> e.g. i want to just do "juju deploy mysql"
[05:48] <TheChistoso> it picks the right machine, but i don't see it turning on and installing the OS as expected
[06:17] <TheChistoso> any maas+juju users present?
[06:44] <shang> bigjools: ping
[06:44] <shang> bigjools: last time I check,the new maas still haven't been backported to 12.04 yet. Has this changed since?
[06:44] <shang> few weeks ago
[07:04] <TheChistoso> so, uh, anybody? :D
[08:06] <Marlinc> Hello
[11:51] <Marlinc> My Juju only finds one node. When I try to add a unit it says "ProviderError: No matching node is available." there is another node ready
[11:51] <Marlinc> What could I do about this?
[11:56] <rbasak> bug 1064291 perhaps?
[11:57] <rbasak> But that's only one possibility
[11:57] <rbasak> I don't remember how to tell juju to use no constraints at all, but if you find out please add it to the bug.
[11:57] <rbasak> It'd be nice to document the workaround.
[11:58] <Marlinc> Ah so.. I've specified i386 and now it works
[11:59] <Marlinc> But let me guess
[11:59] <Marlinc> Now only 32 bit nodes will work
[11:59] <melmoth> i m not sure how to remove a global constraint for arch, but for the node name, i use juju "set-constraints maas-name="
[11:59] <rbasak> You can change the default constraints
[11:59] <melmoth> then i double check it s set to NULL again with juju get-constraint
[12:01] <rbasak> Marlinc: please mark bug 1064291 as "affects me too"
[12:01] <Marlinc> Done
[12:01] <rbasak> Thanks!
[12:01] <Marlinc> So it looks like I'm not the only one
[12:03] <Marlinc> Is it possible to allow multiple architectures using a constraint?
[12:04] <rbasak> I'm not sure. #juju might have more people who can help.
[12:43] <Marlinc> MAAS should boot a machine when Juju requests it right?
[12:45] <rbasak> Correct. Not only boot, but install.
[12:45] <rbasak> (thus it takes a while)
[12:47] <Marlinc> Well the last works
[12:47] <Marlinc> But it is no longer starting the machine
[12:49] <Marlinc> Ah now it works
[12:55] <Marlinc> There's a little issue I think
[12:56] <Marlinc> One my machine's has needs a binary blob for the NIC. It can't boot connect without so it cannot install fully automatically
[13:00] <rbasak> I don't think maas will be able to support that case any time soon. You should be able to hack it though, by customizing the preseed.
[13:00] <rbasak> Although it wohn't be able to fetch the preseed. Hmm.
[13:01] <rbasak> It can still be done. Perhaps by hacking the installer initrd. Perhaps more trouble than it's worth. I can't think of a non-trivial way to do it off the top of my head.
[13:01] <Marlinc> Mmm I kept the USB in the machine
[13:01] <Marlinc> Now it works
[13:01] <Marlinc> I guess I need to keep in the machine lol
[13:47] <Teduardo> Hey is anyone around here that knows MAAS/JUJU?
[13:48] <Teduardo> I'm trying to figure something out; and that is.. if MAAS doesn't know the hardware specifications of the boxes it's managing how can I know whether certain juju charms are approriate to install?
[13:48] <Teduardo> err, sorry how can IT know
[13:49] <mgz> it does know, see http://maas.ubuntu.com/docs/
[13:50] <mgz> see particularly the tags section
[13:51] <Teduardo> ah, when I login to maas it tells me all of my 4 core VMware machines have 32 cores
[13:52] <mgz> presumably the underlyinf hardware has 32 cores?
[13:52] <Teduardo> nope, it has 8 cores and 16 threads
[13:53] <mgz> anyway, you can look at the lshw output and #1 file a bug with it attached, #2 create your own tag for the bits you care about
[16:38] <Dr{Wh0}> Q. I am trying to setup a multi-homed server for my maas box so I can manage it from my trusted network. I setup maas from 13.04 and then changed the trusted interface ip and now some pages still have links to the original dhcp'd ip it got at boot. How can i get it to reload or reconfigure itself?
[16:42] <roaksoax> Dr{Wh0}: sudo dpkg-reconfigure maas-region-controller
[16:42] <roaksoax> Dr/win 14
[16:44] <Dr{Wh0}> so I did try that and it didnt seem to fix some links on the pages. going to try again.
[16:44] <Dr{Wh0}> nope. same thing the main page has a link on it with a warning "Some cluster controllers are missing boot images. Either the import task has not been initiated (for each cluster, the task must be initiated by hand the first time), or the import task failed. "
[16:44] <Dr{Wh0}> this link goes to the wrong ip.
[16:46] <Dr{Wh0}> not gone through all the code still learning it but it seems to be here in api.py "absolute_reverse("settings")"
[17:07] <roaksoax> Dr{Wh0}: ah so you need to sudo dpkg-reconfigure maas-cluster-controller on all the nodes that are the cluster controllers
[17:26] <TheChistoso> i'm using maas+juju. i added a new machine and it's shown as "ready" in the node list. when i try and deploy mysql, it never picks up the new machine
[17:26] <TheChistoso> i started the deploy last night and 10 hours later juju status is still showing it as "pending"
[17:51] <roaksoax> TheChistoso: will first you need to verify that the bootstrap node is up and running
[18:50] <Dr{Who}> roaksoax: sorry got disconnected. I dont have any other systems just this one MAAS system to start with.
[20:57] <TheChistoso|2> roaksoax: i just got back to this. my bootstrap node is up and running fine.
[22:01] <TheChistoso|2> i resolved my issue -- issue was that my juju bootstrap node was running precise w/ a known bug where you need to include the port # in the maas-server entry in your environments.yaml for juju
[22:33] <Dr{Who}> Well I have even grep'ed the entire hard drive for that ip address and other than a few pg files I dont see it anyplace yet the MAAS ui still knows about it.
[22:40] <Marlinc> How can I change the port of the MAAS interface?
[22:40] <Marlinc> To 8080 for example
[22:41] <mwhudson> editing /etc/apache2/conf.d/mass.conf i assume?
[22:41] <mwhudson> note: i don't know if there is a better wya
[22:44] <Marlinc> Mm okay
[23:14] <mwhudson> roaksoax: ping
[23:55] <Dr{Who}> Q. the /settings/ page has "Some cluster controllers are missing boot images. Either the import task has not been initiated (for each cluster, the task must be initiated by hand the first time), or the import task failed." but the url link on this line is to the wrong IP. it was the IP the box was initially setup on dhcp. Its now static. I have yet to find how to get the system to change this url. Ideas? I already tried dpkg-reconfigure maas-cluster-
[23:55] <Dr{Who}> controller . Is this a bug?
[23:55] <bigjools> edit the cluster
[23:57] <Dr{Who}> ok how do I do that. I only have 1 box so far this one MAAS box a 13.04 installed with "MAAS" as the install option.
[23:59] <Dr{Who}> ok found the cluster edit page in the ui looking now. done see any ip's yet.