[01:55] <bigjools> hey roaksoax, got a minute?
[01:58] <roaksoax> bigjools: hey!
[01:58] <roaksoax> sure! what's up?
[01:58] <bigjools> roaksoax: hey dude
[01:58] <bigjools> I am trying to make maas configure the forwarders option for bind
[01:58] <bigjools> it's tricky, because I can't duplicate the options{} block
[01:59] <bigjools> at least I think that's the case - just wanted to check with you on your opinions of what I can do here?
[02:00] <roaksoax> bigjools: uhmm, so i do not thinkig we would need to duplicate the options would we?
[02:01] <roaksoax> bigjools: we only need to add forwarders if the user wants to add them
[02:01] <bigjools> roaksoax: all I need to do is add forwarders - but options is in a file that we don't have templated
[02:01] <bigjools> named.conf.options
[02:02] <bigjools> I assumed I could add something only in named.conf.maas.... but bind9 complains there's two options blocks
[02:02] <roaksoax> bigjools: i see what you mean
[02:02] <bigjools> so I'm looking for suggestions :)
[02:02] <roaksoax> bigjools: let me look at it a bit deeper
[02:03] <roaksoax> bigjools: otherwise, we would need to ask lamont
[02:03] <bigjools> hang on, door
[02:06] <roaksoax> bigjools: yeah, I think we'd need to ask lamont
[02:09] <roaksoax> bigjools: ok I think we can do this:
[02:09] <roaksoax> zone "pixar.com" { type forward; forwarders { 138.72.10.20; 138.72.30.28; };
[02:09] <roaksoax> };
[02:09] <bigjools> sorry, back
[02:09] <roaksoax> bigjools: http://docstore.mik.ua/orelly/networking_2ndEd/dns/ch10_05.htm
[02:10] <bigjools> roaksoax: I looked at that, it's not what we want I think
[02:10] <bigjools> it only forwards for requests on the same zone doesn't it?
[02:10] <bigjools> unknown requests I mean
[02:10] <bigjools> the point of setting the global one is so that nodes can resolve non-node addresses
[02:11] <roaksoax> yeah
[02:11] <roaksoax> it seems so
[02:11] <bigjools> the other option is to template the options file
[02:12] <roaksoax> bigjools: yeah... i don't think that'd be ideal
[02:12] <bigjools> quite
[02:12] <roaksoax> bigjools: i think we should ask lamont
[02:12] <bigjools> or - try and rewrite it on the fly
[02:12] <bigjools> is lamont there?
[02:12] <roaksoax> bigjools: in ODS? no
[02:13] <bigjools> ok.  how'd it go BTW?
[02:13] <roaksoax> bigjools: the demo? didn't finish
[02:13] <roaksoax> not enough time
[02:14] <bigjools> damn
[02:15] <roaksoax> bigjools: so he just didn't show the running cloud
[02:15] <roaksoax> but things were working
[02:15] <bigjools> roaksoax: was that from the bundle deployment?
[02:18] <freeflying> when apply a tag to a node, can I use hostname of the node?
[02:18] <roaksoax> bigjools: yup
[02:19] <bigjools> freeflying: http://maas.ubuntu.com/docs/tags.html#manually-assigning-tags
[02:19] <bigjools> basically, no, you need to use system id
[02:20] <freeflying> bigjools, ok, thanks :)
[02:23] <bigjools> roaksoax: will you chase lamont or do you want me to do it?
[02:24] <roaksoax> bigjools: I think it would be better if you could since i'm still oin hongkong and i'm on and off
[02:24] <bigjools> roaksoax: no probs
[02:24] <bigjools> cheers
[02:25] <roaksoax> bigjools: thanks!
[02:49] <shimey> Does MaaS have the ability to discover/configure IPMI addresses automatically/dynamically?
[02:52] <bigjools> shimey: sort of.  It inspects for BMCs on enlisting machines and reprograms one of the user slots with a known password.
[02:52] <bigjools> that gets sent back to maas when it finishes enlisting so then maas can use ipmi
[02:53] <shimey> that's cool, but you still have to obtain the IPMI IP address...
[02:54] <shimey> If it can set the BMC password, should it be able to assign an IP?
[02:54] <bigjools> it obtains all its details, no more action required.
[02:55] <bigjools> BMCs get IPs over DHCP generally, and ipmitool can inquire about all that
[02:55] <shimey> Ahh, so people just DHCP the address
[02:55] <bigjools> yes, but we don't depend on that to get all the details
[02:56] <shimey> Wouldn't it make sense for MaaS to DHCP lease the IPMI address?
[03:01] <bigjools> shimey: it does.
[03:01] <bigjools> well, it doesn't *have* to, that's the point
[03:01] <bigjools> but it can
[03:01] <shimey> Oh, I guess it would...if my IPMI where on the same network as my MaaS
[03:01] <bigjools> it inspects the BMC details by running a script on the machine itself
[03:01] <bigjools> yes - many people have separate BMC networks
[03:05] <shimey> Right I've actually have three separate networks. Public, IPMI and a MaaS backend...  I guess If I had controller of the IPMI network I could start DHCP on the cluster controller for that interface.
[03:06] <shimey> my MaaS backend I setup a private vlan but the IPMI I don't have real control over.
[03:06] <shimey> (more of a personal issue)
[03:08] <shimey> Another question however, I have nodes get stuck for various reasons and have to use IPMI to reboot them, should MaaS have the ability to shutdown/reboot a node via IMPI via the GUI/ReST?
[03:10] <bigjools> yeah, that's a possibility
[03:10] <bigjools> for now it assumes (naively) that all the power commands work and the machine boots perfectly every time
[03:14] <shimey> Ya it seemed like there wasn't any hardware watchdog support for images booting.  And if just using WOL, I think it would be very easy to loose machines.
[03:16] <bigjools> WoL is going away
[03:16] <shimey> Ya, I don't think it would suffice.
[03:17] <bigjools> we plan on adding watchdogs, but it's a little tricky
[03:17] <shimey> Do you know if there is going to be any support for other linux distros?
[03:18] <bigjools> not in the immediate future, but you never know
[03:19] <shimey> PCH watchdog?
[03:24] <shimey> Maybe a software watchdog would suffice...
[03:28] <shimey> One last question, any suggestions on getting juju and MaaS working together.  Are there certain versions that work together?
[03:29] <bigjools> the latest versions in saucy should work
[03:29] <bigjools> 1.16.2 is the minimum juju-core
[03:30] <bigjools> also if you want to use precise, add the cloud-archive
[03:30] <bigjools> I have to factory reset my router now, back in a while
[03:30] <shimey> I was having trouble getting the ephemeral images to mount in saucy
[03:31] <shimey> thanks bigjools,  I'll see about 1.16.2 of juju-core and try the could-archive
[03:31] <shimey> good night
[03:31] <bigjools> bye
[06:22] <Azendale> So, I have a weird problem with MaaS. If too many (like 5) machines start within 20 seconds or so of each other, it seems like it will overload MaaS, and then past that, the dhcp server will not respond over the network, even well after any load has gone away. Rebooting the MaaS server will fix it
[06:23] <Azendale> Running ps aux shows the DHCP process, and a packet capture on the MaaS server with the DHCP on it will show all the requests making it in
[06:23] <Azendale> any suggestions on where/how to figure out what is going on?
[08:20] <freeflying> maas-cli maas tag update-nodes my_tag remove=system_id, seems doesn't remove a node from a tag, anything I missed?
[10:28] <jtv> gmb: were you saying you might extract run_command / run_remote_command / test_install_maas_package?
[11:00] <gmb> jtv: Yes.
[11:02] <jtv> gmb: great!  It ties in with my work.  Could I ask you to push your branch at EOD even if it isn't done, so I can build on it tomorrow?
[11:02] <jtv> Tag-team dev...
[11:02] <gmb> jtv: Certainly!
[11:03] <jtv> Thank you.
[11:03] <jtv> And with that, I bid you good day.
[19:00] <phenoche> is it possible to create software raids with maas and juju?
[19:04] <Azendale> phenoche: you mean as in the various services having a software raid configuration of their hard disks?
[19:06] <phenoche> yeah i have a box with 2 disks that is enlisted and i would like to run say the wp charm on that but have it make a software raid with the disks
[19:08] <phenoche> Azendale, so yes : )
[19:09] <Azendale> phenoche: this is going to be more of a juju thing to deal with. But a charm can be made to set up any configuration you can configure an ubuntu install in. The wordpress charm probably doesn't have the code to do that though (I could be wrong, look at the charm options). If you wanted to make your own version of the wordpress charm and get into what the code in the charm does, you could make a modified version of the charm, and then specify what machine it get
[19:10] <phenoche> Azendale, great thanks thats exact what i was wondering i'll check in on this on the juju side of things
[19:14] <Azendale> phenoche: No problem. I think you can get the wordpress code with something like bzr branch lp:charms/wordpress  And you can deploy with something like juju deploy --repository=<path_to_branch_on_your_disk> local:wordpress
[22:21] <phenoche> so I have been looking a little closer at creating a raid with maas and i think you might be able to do it by altering the preseed file. does that sound like I'm on the right path
[22:53] <bigjools> good morning