[04:50] <joebaker> Is there documentation to enable https for MAAS?
[04:52] <joebaker> to answer my own question:  I see that in /etc/apache2/conf.d/maas-http.conf  is probably the way to enable https.   It seems to be standard Apache stuff.
[05:01] <joebaker> answer:  This command line solved turning on SSL :   sudo a2enmod ssl  ;   service apache2 restart
[12:49] <AskUbuntu> Ubuntu server DNS/DHCP/MAAS woes | http://askubuntu.com/q/349061
[14:23] <roaksoax> smoser: howdy!! so I was wondering if you'
[14:23] <roaksoax> smoser: howdy!! so I was wondering if you've reviewed the new ephemerals_script that uses simplestreams
[14:25] <smoser> sort of.
[14:25] <smoser> but not in depth.
[14:25] <smoser> why?
[14:25] <smoser> i reviewed it with the eye of 'this looks fine if it is functionally equivalent'
[14:29] <roaksoax> smoser: yeah.. so are we meant to lose the fact that a user can specify what releases we want to import from /etc/maas/import_ephemerals?
[14:29] <roaksoax> smoser: or is now maas going to control the import process alone
[14:29] <roaksoax> and the user won't be able to
[14:29] <smoser> they'll need to be able to specify that somehow.
[14:29] <roaksoax> rvba: ^^
[14:29] <roaksoax> allenap: ^^
[14:30] <tych0> hi
[14:31] <smoser> tych0, roaksoax was asking about "are we meant to lose the fact that a user can specify what releases we want to import from /etc/maas/import_ephemerals?"
[14:31] <smoser> " or is now maas going to control the import process alone"
[14:31] <tych0> well, there is no config file stuff yet
[14:31] <tych0> you can do it with filters, though
[14:31] <tych0> e.g. maas_import_ephemerals.py release~(precise|quantal)
[14:32] <smoser> so we mean to make it configurable. but haven't yet.
[14:32] <roaksoax> tych0: right, but I didn't mean it particularly for releases  though (but for all the options)
[14:32] <smoser> and i think that bigjools suggested that you should read the old config file ?
[14:32] <tych0> yeah
[14:32] <smoser> roaksoax, what all options are there.
[14:32] <roaksoax> tych0: so my point being is that are we losing functionanility by being able to specify the options on the config file (since there's no config file)
[14:33] <tych0> yep
[14:33] <tych0> it's on the todo list to implement
[14:33] <tych0> just pre-empted by higher priority cloud installer stuff atm
[14:33] <roaksoax> tych0: and does this mean that *maas* only can run the script, or will the user will be able to do so?
[14:33] <tych0> no, users should be able to run it
[14:34] <roaksoax> tych0: right, since I see the script being installed in srcf/provisioningserver/import_images/ephemerals_script.py... i don't see how this will end up in /usr/bin
[14:34] <roaksoax> or /usr/sbin for that matter
[14:34] <tych0> there's still one in /scripts/maas_import_ephemerals.py
[14:34] <tych0> which basically just invokes that
[14:34] <tych0> (FWIW i didn't put it there)
[14:34] <tych0> the original was all in python
[14:34] <tych0> er, all in /scripts
[14:34] <roaksoax> tych0: i see now..
[14:35] <roaksoax> tych0: ok so when are we meant to deprecate the shell script in favor of the python one? (i'd like to drop the .py from the binary to not have to rename it in packaging)
[14:35] <tych0> roaksoax: i don't know, probably best ask gavin
[14:36] <tych0> i agree, though
[14:36] <tych0> r.e. dropping the ext
[14:36] <roaksoax> tych0: perfect! Thanks for taking care of this!
[14:36] <tych0> yep
[14:36] <roaksoax> allenap: when are we looking to deprecate the shell script for ephemeral import in favor of the python one?
[14:51] <allenap> roaksoax: Not sure yet, but in time for 13.10.
[14:51] <allenap> roaksoax: tych0 and jtv have been working on it.
[14:51] <allenap> roaksoax: Want me to get a more solid estimate?
[14:54] <roaksoax> allenap: if it is in time for 13.10 i'm good with that (so far) I just wanna start making the packaging changes needed to have the latest in soonish
[14:55] <tych0> afaik there shouldn't really be any packaging changes needed
[14:55] <tych0> bigjools' request was that the script migrate configs itself
[14:55] <tych0> so that we don't have to do any more postinst stuff
[14:55] <tych0> (that's assuming we drop the .py, i guess)
[15:03] <allenap> tych0, roaksoax: These scripts should no longer be available for users to run directly (well, not on PATH at least), so I think that simplifies things.
[15:06] <roaksoax> tych0: yeah but we do need other packaging changes (new dependencies and stuff)
[15:06] <roaksoax> allenap: so maas-import-ephemerals should no longer be run by the user?
[15:06] <roaksoax> smoser: ^^
[15:07] <smoser> allenap, "These scripts should no longer be available for users to run directly (well, not on PATH at least), so I think that simplifies things."
[15:07] <smoser> i dont know why that is required or desireable
[15:09] <tych0> roaksoax: ah, yeah, good point
[18:56] <kurt_> roaksoax: do you know if it's necessary to reconfigure maas-dhcp and maas-dns when adding/removing interfaces on the maas region controller?
[18:57] <kurt_> or does dpkg-reconfigure maas-region-controller take care of all that?
[19:01] <roaksoax> kurt_: if you add/remove interfaces you do not need to configure maas-dhcp/maas-dns
[19:02] <kurt_> roaksoax: ok, thnx
[19:02] <roaksoax> kurt_: but of course the interface need to be configured for the particular network (since maas only configures the interfaces in terms of dhcp/dns) and doesn't actually congfigure the network interface with the network parameters you want (as in it doesn't give the interface an IP address, netwmask, etc)
[19:03] <kurt_> right
[19:04] <kurt_> roaksoax: troubleshooting why pxe boot doesn't appear to be working
[19:04] <kurt_> there are many reasons this could happen - I get it.
[19:04] <kurt_> just working to narrow it down
[19:06] <roaksoax> kurt_: what's been displayed in /var/log/maas/pserv.log
[19:06] <roaksoax> kurt_: what about maas-serv is running?
[19:07] <roaksoax> what about DHCP?
[19:08] <kurt_> no maas-serv
[19:09] <kurt_> http://pastebin.ubuntu.com/6146865/
[19:25] <roaksoax> kurt_: sudo service maas-pserv start?
[19:28] <kurt_> Something is wrong with the maws-dhcp - I can't find where the configuration causing this is:
[19:28] <kurt_> http://pastebin.ubuntu.com/6146952/
[19:29] <roaksoax> kurt_: then something is not configured properly
[19:29] <roaksoax> kurt_: i'm assuming you are using maas for both dns/dhcp
[19:29] <kurt_> correct
[19:29] <kurt_> that configuration is not in maas/dhcpd.conf
[19:29] <kurt_> nor is it in /etc/dhcp/dhcpd.conf
[19:29] <kurt_> my maas-pserv is running
[19:30] <kurt_> maas-pserv start/running, process 838
[19:49] <roaksoax> kurt_: correct so tftp works locally?
[19:50] <kurt_> not sure about that. it doesn't appear to
[19:50] <kurt_> I see my VM trying to tftp boot - and nothing is happening
[19:50] <kurt_> I have another installation where this is working fine
[19:51] <roaksoax> kurt_: so in the same maas server: tftp <maas-server-ip?
[19:51] <roaksoax> get pxelinx.0
[19:51] <kurt_> let me ask this - can the interface take the router address too?
[19:51] <kurt_> ie. .1?
[19:51] <roaksoax> kurt_: if the maas server is the router, itwould
[19:51] <roaksoax> kurt_: but if it is kvm
[19:51] <roaksoax> the "router" is the host
[19:54] <kurt_> tftp> get pxelinx.0
[19:54] <kurt_> Error code 1: File not foun
[19:54] <roaksoax> pxelinux.0
[19:54] <roaksoax> sorry
[19:54] <kurt_> Received 26837 bytes in 0.1 seconds
[19:55] <kurt_> that's to localhost
[19:55] <kurt_> and same thing for my address which I've arbitrarily chosen as 172.16.200.1
[19:56] <kurt_> I fixed the dhcp issue.  I can see the host getting an IP in the log
[19:56] <kurt_> it gets .w
[19:56] <kurt_> .2
[20:57] <Tim_> Has anyone gotten maas-pserv to operate the tftp server off of a NIC other than eth0?
[20:57] <Tim_> e.g. eth3
[21:12] <sconklin_> Is it possible to run a dhcp server that is not on the maas server, and point the pxeboot at the maas server? I've been tryng this and it's not working
[21:12] <Tim_> Lol
[21:12] <Tim_> I just asked the same question
[21:13] <sconklin_> ha, I see
[21:13] <Tim_> sconklin_: Is the pxe-booted machine getting the right DHCP info?
[21:14] <sconklin_> it's getting the right IP address, so I know it's getting serviced by the machine I think it should (not maas), but it appears to be grabbing the images from the dhcp server and not the maas server.
[21:15] <Tim_> sconklin_: Do you have the 'next-server' attribute set to point to the maas server in the dhcp config?
[21:16] <sconklin_> this is what's in the dhcp config (I didn't set it up):
[21:16] <sconklin_> dhcp-option=tag:MaaS,3,10.98.5.1
[21:16] <sconklin_> dhcp-option=tag:MaaS,6,10.98.5.1
[21:16] <sconklin_> dhcp-boot=tag:MaaS,pxelinux.0,10.98.5.65
[21:16] <sconklin_> pxe-service=tag:MaaS,x86PC,pxelinux,10.98.5.65
[21:19] <Tim_> hmm
[21:19] <Tim_> what dhcp package is it using?
[21:19] <Tim_> The syntax appears different from "normal"
[21:19] <sconklin_> dnsmasq, ubuntu 12.04
[21:20] <sconklin_> it's a cobbler server
[21:20] <Tim_> Right
[21:21] <Tim_> I'm not familiar with that package. Hang on, I'll check...
[21:23] <Tim_> It seems like the last dhcp-boot argument is the tftp sever
[21:23] <Tim_> as per here: http://www.heath-bar.com/blog/?p=326
[21:25] <sconklin_> 10.98.5.65 is definitely the maas machine, I can hit the webui there
[21:34] <Tim_> Not sure I can help much with Dnsmasq, I don't know it
[21:35] <sconklin_> ack, thanks. But in theory, as long as the pxeboot is pointed at the maas server, it should be ok? Is there any other reason that the dhcp serevr has to be run on the maas machine?
[21:43] <Tim_> Well here's my problem: I'm running the dhcp server on something other maas, but the tftp server (which is running as a twisted python process) doesn't seem to connect to clients
[21:43] <Tim_> issue here: http://askubuntu.com/questions/346339/maas-with-external-dhcp-tftp-time-out
[21:43] <Tim_> bug here: https://bugs.launchpad.net/maas/+bug/1191735
[21:44] <sconklin_> oh, let me check the tftp server logs and see if there's any indication that might help me. Thanks for the pointer