[02:40] <burnbrighter> cheez0r: thanks.  I started over.  We'll see how it goes this time.
[05:07] <burnbrighter> cheez0r: ut?
[06:28] <burnbrighter> bigjools: how exactly should the /etc/hosts file look for the primary maas node?  There seems to be some confusion around this.
[06:30] <bigjools> you don't need one, cobbler updates your dns
[06:38] <burnbrighter> I see two entries - 127.0.0.1 for localhost - the usual
[06:38] <burnbrighter> then I see 127.0.1.1 for my host's name
[06:38] <burnbrighter> (maas01)
[06:39] <burnbrighter> cheez0r experienced ssh problems in juju because of his dual-homed set up - which is what I have
[06:40] <burnbrighter> and I continue to see problems with commissioning
[06:40] <burnbrighter> sometimes it works, sometimes it doesn't
[06:52] <burnbrighter> and, cobbler updates internal dns, how about external dns?
[06:52] <burnbrighter> like when you need to update packages and such or maas-import-isos?
[06:53] <burnbrighter> my external dns doesn't seem to work
[06:53] <bigjools> it updates the dns server you configured on it, which is probably your local dnsmasq
[06:53] <burnbrighter> if I try to update resolvconf/resolv.conf/base or something else, that mucks with the required 127.0.0.1 entry
[06:54] <bigjools> yes, resolv.conf defers to dnsmasq locally
[06:54] <burnbrighter> anything in resolvconf overwrites resolv.conf
[06:55] <burnbrighter> and if you add something to base in resolvconf, it messes up the external dns
[06:55] <burnbrighter> so how can you get around that?
[06:56] <burnbrighter> am I missing some basic configuration?
[06:56] <burnbrighter> or are these known issues
[06:58] <bigjools> you don't need to change this stuff
[06:58] <bigjools> if the box is multi homed then make dnsmasq serve on all addresses
[07:03] <burnbrighter> do you have hints on how I would go about doing this?
[07:04] <bigjools> I don't know without looking but I'd start with "man dnsmasq" :)
[07:05] <burnbrighter> isn't a dual-homed system for the maas server one of the common configurations, out of curiosity?
[07:06] <burnbrighter> I mean, how are people deploying them mostly
[07:06] <bigjools> most people will use bind for real deployments - dnsmasq is not proven in larger environments
[07:07] <bigjools> and in fact we are removing support for dnsmasq in the next revision of maas
[07:16] <burnbrighter> interesting, ok
[11:52] <cheez0r> burnbrighter: the trick is to ensure that you have two hosts configured- one for your eth0 ip and one for your eth1 ip; to have whichever of those two networks is your MaaS network's hostname in /etc/hostname; and to ensure that you've installed maas, maas-dhcp and ensured that either during the install or with dpkg-reconfigure you've specified the IP data of the MaaS network.
[11:54] <cheez0r> I find that building the initial MaaS install by specifying the public or 'outside' IP network and DNS servers that are reachable, and then adding the MaaS network to the machine, setting the hostnames up, then dpkg-reconfigure maas, and apt-get install maas-dhcp to be the easiest procedure.
[14:00] <roaksoax> rvba: yui is shipping some non free files right?
[14:01] <rvba> roaksoax: off-hand, I've got no idea.
[14:03] <roaksoax> rvba: what about these two? rm maas-$(VER).orig/src/maasserver/static/jslibs/yui/3.4.1/build/uploader/assets/uploader.swf rm maas-$(VER).orig/src/maasserver/static/jslibs/yui/3.4.1/build/io-xdr/io.swf
[14:05] <rvba> roaksoax: note that in the version we currently use (3.5.1), uploader.swf is in ./src/maasserver/static/jslibs/yui/uploader-deprecated/assets
[14:06] <roaksoax> rvba: http://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2012-June/003761.html
[14:06] <roaksoax> Daviey: ^^
[14:07] <rvba> roaksoax: io.swf is a tiny flash component required (I think) to circumvent some of the limitations of the browsers.
[16:43] <burnbrighter> cheez0r: any chance I could see what your host file looks like?  And did you have to do any dnsmasq tweaking?  Did you have external dns resolution issues there?
[17:01] <cheez0r> burnbrighter: http://pastebin.ubuntu.com/1052955
[17:02] <cheez0r> THe /etc/dnsmasq.conf file is populated from a cobbler template at /etc/cobbler/dnsmasq.template so that's where those dhcp-host lines are located, and then when you maas-import-isos it moves that file into place at /etc/dnsmasq.conf and does service dnsmasq restart for you.
[17:02] <burnbrighter> thanks - what did you do with the 127.0.1.1 address maas created?  did you get right of that?
[17:02] <cheez0r> It never created such an address for me.
[17:03] <cheez0r> when you do the initial install you configure the public side network (outside)
[17:03] <cheez0r> then you add the internal network and reconfigure maas, then install the maas-dhcp package
[17:04] <cheez0r> 127.0.0.1 is a loopback address and should remain; I'm unclear where the 127.0.1.1 address is originating from.
[17:04] <burnbrighter> that was confusing for me because the hostname actually points to that address
[17:04] <cheez0r> shouldn't.
[17:05] <burnbrighter> for example, my host name is maas01, so that was pointed to 127.0.1.1
[17:05] <cheez0r> weird. 127.0.0.1 should point to localhost
[17:05] <cheez0r> your hostname should point to the maas network IP address
[17:05] <cheez0r> and a second host should be configured for the public IP side
[17:05] <burnbrighter> and everything just worked for you?
[17:06] <cheez0r> yeah
[17:06] <burnbrighter> how about external dns resolution problems?
[17:06] <burnbrighter> sorry, I haven't read everything you wrote above - too many meetings :)
[17:06] <cheez0r> none- if you do the initial install with the public IP configured, you can reference your real DNS servers
[17:06] <cheez0r> that should eliminate any issues once you install maas-dhcp and that installs dnsmasq
[17:09] <burnbrighter> hmmm.  I'm seeing dnsmasq or resolvconf overwriting dns
[17:09] <burnbrighter> I mean resolv.conf
[17:09] <burnbrighter> it always gets written to 127.0.0.1
[17:09] <cheez0r> yeah you have to configure dns-nameserver to /etc/network/interfaces
[17:09] <cheez0r> so on your public interface you configure dns-nameservers and then service network restart and it should populate /etc/resolv.conf appropriately.
[17:09] <burnbrighter> and you set each one separately there?
[17:10] <cheez0r> one line, multiple servers separated with spaces
[17:10] <cheez0r> gotta run- good luck, I'll respond in ~1hr when I get back
[17:10] <burnbrighter> ahhh...resolv.conf is populated based on the interfaces file???
[17:10] <burnbrighter> ok, thanks for the info
[18:43] <cheez0r> burnbrighter: with resolvconf they are, and resolvconf is on the MaaS node by default.
[18:46] <burnbrighter> I don't think I see any entries in resolvconf from maas
[18:47] <cheez0r> MaaS has nothing to do with resolvconf.
[18:47] <burnbrighter> exactly
[18:47] <cheez0r> when you configure the node during the install of MaaS, you supply DNS server IP addresses.
[18:47] <cheez0r> It inserts them into the /etc/network/interfaces file, from which the resolv.conf is generated.
[18:47] <burnbrighter> ? I don't it does
[18:47] <burnbrighter> s/don't/don't think/
[18:48] <cheez0r> During the install of the MaaS node it prompts you for DNS servers.
[18:48] <cheez0r> You must've typed in 127.0.1.1.
[18:48] <burnbrighter> k, I don't remember that part
[18:48] <burnbrighter> no, I definitely do not
[18:48] <burnbrighter> I never put in 127.0.0.1
[18:48] <burnbrighter> that's populated by maas
[18:48] <cheez0r> 127.0.0.1 is a loopback address. It is present on most unix/linux systems.
[18:49] <burnbrighter> which version are you using.  and yes I know that
[18:49] <cheez0r> I'm installing from the Ubuntu 12.04 CD.
[18:49] <burnbrighter> are you using the regular apt-get version?
[18:49] <burnbrighter> yeah - I don't recall it asking about DNS, and I know for certain I've never put in the loop back address
[18:49] <cheez0r> No, you install the MaaS head node by booting it from the Ubuntu ISO and choosing to install MaaS, and then having it install Ubuntu for you.
[18:50] <burnbrighter> correct
[18:50] <cheez0r> If you're doing it a different way I've got no experience with it and therefore can't help you.
[18:50] <burnbrighter> the only two ways I know how to do it are the one you mention, the other is installing base 12.04, then adding maas after the fact
[18:52] <burnbrighter> in any case, back to our conversation above - are you saying what's in /etc/network/interfaces gets written to /etc/resolv.conf by the OS?
[18:52] <cheez0r> No, by the resolvconf package.
[18:53] <burnbrighter> ok, and you can set it separately for each interface?
[18:53] <cheez0r> yes, but generally you dont.
[18:54] <cheez0r> You only set it for the interface that can see that DNS server, and then it resolves there for the entire box.
[18:54] <burnbrighter> my problem is I either get internally resolvable dns OR external dns, but never both together
[18:54] <cheez0r> what does that statement mean?
[18:54] <cheez0r> What is an 'internally resolvable dns'?
[18:55] <burnbrighter> the internally resolvable addresses for dns created by maas-dhcp
[18:55] <burnbrighter> or cobbler
[18:55] <burnbrighter> not sure which
[18:55] <cheez0r> You are creating a MaaS network. You are installing the MaaS node. It should have 'external' DNS servers that the MaaS node resolves against. The MaaS node should resolve hosts for the rest of the MaaS cluster.
[18:55] <burnbrighter> let me explain a little...
[18:56] <burnbrighter> if I do a ping against node-0050c06467.maas.local and my resolv.conf has nameserver 127.0.0.1, it works
[18:56] <burnbrighter> if I do a ping against www.cnn.com with nameserver set to same, it doesn't
[18:57] <cheez0r> I don't know enough about dnsmasq to help with that issue.
[18:57] <cheez0r> If you follow the steps I gave, it will work. Beyond that I don't know.
[18:57] <burnbrighter> if I change resolv.conf to external dns, or even my router which passes dns ie. 192.168.1.1, then pinging www.cnn.com works, but node-0050c06467.maas.local doesn't
[18:58] <burnbrighter> bigjools was suggesting tweaking the dnsmasq config, but also informed me they are dropping support in the next release anyways
[18:59] <cheez0r> My solution to that was to statically map my DNS entries in /etc/hosts and to statically assign DHCP entries in /etc/dnsmasq.conf
[18:59] <cheez0r> you saw that configuration.
[19:00] <burnbrighter> yeah, I'm going to try it.  I've been trying to get this right for two weeks and I'm becoming a bit frazzled
[19:00] <cheez0r> I hear ya, I've been banging on mine for about a month now
[19:01] <burnbrighter> I'm trying to do this in a VM too
[19:01] <burnbrighter> with fully virtualized network
[19:01] <burnbrighter> well, not fully
[19:01] <burnbrighter> bridging the set up adds its own set of complications
[19:02] <burnbrighter> eventually I will need to add a third network in for a third party piece of software the works with openstack
[19:02] <burnbrighter> that needs to communicate over a bridged dmz interface.  been having problems with bleed over in bridging