[00:05] <bradm> are there any decent docs about how to write preseed files and modify them for maas?
[00:06] <bigjools> bradm: it's not a maas-specific thing really
[00:06] <bigjools> https://help.ubuntu.com/12.04/installation-guide/i386/preseed-intro.html
[00:06] <bradm> bigjools: I'm talking about what you can do inside the {{ }} tags
[00:07] <bigjools> that's a templating language called Tempita:  http://pythonpaste.org/tempita/
[00:07] <bigjools> http://pythonpaste.org/tempita/#the-language specifically
[00:08] <bradm> bigjools: and how do we know what variables we have access to in there? apparently I want to access node.tags.all(), but how would I find that out?
[00:08] <bigjools> reading the code, it's not documented :(
[00:08] <bradm> I think what I want is {{ if 'nova-compute' in node.tags.all() }}
[00:09] <bradm> but its a guess based on the examples
[00:09] <bigjools> should work
[00:11] <bradm> cool, thanks
[02:20] <bradm> is there any way to either see the preseed that's used by maas for a node, or maybe to capture the output from syslog of the install?
[02:20] <bigjools> bradm: yeah there's a preview on the node page
[02:21] <bradm> bigjools: aha, sweet.
[02:22] <bradm> oh, haha, thats what happens when you make assumptions about tag names
[02:28]  * bigjools gets annoyed with whatever is stealing the ctrl-space shortcut on the desktop
[02:28] <bigjools> no, I don't ever want to change my keyboard layout once I set it, Unity
[03:50] <roaksoax> bigjools: howdy!! so maas was broken in latest trunk and nobody noticed
[03:50] <roaksoax> :)
[03:51] <roaksoax> bigjools: fixes were really packaging branch but if I hadn't tested, nobody would have noticed :)
[03:53] <bradm> ugh, debugging preseeds is time consuming
[03:54] <roaksoax> bigjools: so something changed on how maas binds ports? or how pserv does? cause now I had to use authbind for pserv too when before wasn't needed
[03:57] <roaksoax> bigjools: uploaded!
[04:03] <bradm> bigjools: any hints on what else it could be to match a tag?  if "compute" in node.tags.all() doesn't seem to do it
[04:33] <bradm> ah, node.tags.all() is empty in the preseed
[04:33] <bradm> and the node definately has a tag
[04:56] <bradm> do I need to be using the curtin installer or something?
[05:43] <bigjools> roaksoax: it's a *really* good idea to wait for a successful qa lab run before uploading anything
[05:44] <bigjools> bradm: it will be returning tag records, not tags, so it will need something like:
[05:44] <bigjools> tag.name for tag in node.tags.all()
[05:45] <bigjools> you might need :py mode, but see if it works
[05:47] <bradm> bigjools: can I assign that to a variable or something?
[05:47] <bigjools> yeah use a define block
[05:53] <bradm> bigjools: so a python define block to create a function?  like {{py: def tagsname(n): return tag.name for tag in node.tags.all() }} or something?
[05:54] <bigjools> no
[05:54] <bigjools> hang on
[05:54] <bradm> bigjools: or the {{def tagsname}} stuff?
[05:55] <bigjools> bradm: http://pythonpaste.org/tempita/#inherit-def
[05:56] <bigjools> you can set python vars as well
[05:58] <bradm> bigjools: hmm, I'll play about with it and see what I can do
[05:58] <bradm> bigjools: I think this is a really important idiom for tweaking preseeds based on tags
[06:05] <bigjools> bradm: yes, sounds reasonable
[06:12] <bradm> bigjools: clearly I suck at this :)
[06:13] <bradm> https://pastebin.canonical.com/104959/ prints out the tags on from the node
[06:24] <bigjools> use public pastebin if you can
[06:25] <bigjools> but glad it worked for you
[06:25] <bradm> yeah, just need to figure out how to turn that into an if statement now
[06:33] <bigjools> {{py: if "mytag" in [tag.name for tag in node.tags.all()] }}
[06:33] <bradm> bigjools: https://pastebin.canonical.com/104960/
[06:33] <bigjools> use public pastebin if you can
[06:33] <bigjools> please
[06:33] <bradm> oh, bah
[06:34] <bradm> http://pastebin.ubuntu.com/6947342/ - gives me a function I can use later like - if 'mytag' in tagnames(node)
[06:35] <bradm> bigjools: hrm, yours doesn't work for me
[06:35] <bigjools> it was untested :)
[06:36] <bigjools> if yours works then fine
[06:36] <bradm> yours is nicer in terms of using less space
[06:37] <bradm> http://pastebin.ubuntu.com/6947349/ <- what I'm trying to do - I can have different late_commands based on tags
[06:37] <bradm> I suspect its the endif etc thats there
[06:41] <bradm> bigjools: thanks for the help, this should work out nicely
[06:53] <bigjools> bradm: np
[06:54] <bradm> I don't like maintaining multiple sets of data with most of it duplicated, this will fix that
[07:24]  * jtv just wasted a few hours trying to get his escaping test for a data display working, only to realise the data got neatly un-escaped as part of the extraction from HTML in the test itself.
[08:43] <rvba> I'm still getting 'AttributeError: class Factory has no attribute 'forProtocol'' when running 'make run+webapp' on trunk. (http://paste.ubuntu.com/6947733/)
[08:43] <rvba> Anyone else seeing this?
[09:30] <rvba> bigjools: btw, about lp:~julian-edwards/maas/default-commissioning-series : we're now using Trusty for commissioning but we're still importing *all* the images.  This is such a waste of bandwidth!
[09:31] <jtv> Should be an easy fix!
[09:48] <rvba> bigjools: fixing this will reduce the time it takes to import the images.
[09:49] <bigjools> rvba: +1!
[09:49] <bigjools> silly omission
[09:49] <bigjools> although we may need some more for deployment to other releases
[09:51] <rvba> bigjools: we need to keep all the deployment images indeed.  But the ephemerals take much longer to import.
[09:51] <bigjools> yes
[12:34] <jtv> rvba: I've pushed a change that tests for, and fixes, the QuerySet nastiness.
[12:35] <rvba> jtv: cool, branch approved.
[12:39] <jtv> Thanks!
[12:43] <rvba> jtv: forgot to say, you might want to rename NetworkConnectNodesForm to re-use it verbatim in the method used to remove nodes.
[12:44] <jtv> Might, yes...  small tweak to the help string I guess.
[12:45] <rvba> Right.
[13:40] <jtv> rvba, want to try this one?  https://code.launchpad.net/~jtv/maas/sample-commissioning-data/+merge/206711
[13:46] <rvba> jtv: sure
[13:55] <tomixxx3> hi, does it make sense to set "ip address" equal to "router ip" in maas dashboard?
[13:56] <jtv> Hi tomixxx3.  I think it does, if your maas server is also your gateway.  But we don't really do anything with router_ip; it's just there so you can allocate nodes that are connected to a particular router.
[13:57] <tomixxx3> k i will try - and change it also in "interfaces"
[13:58] <tomixxx3> do i have to re-commission nodes after a change like this?
[13:59] <jtv> Which are you changing?  IP address of a cluster interface?
[13:59] <tomixxx3> no, gateway address of the network interface
[14:00] <jtv> Gateway address is different from router_ip...  The gateway is configuration for MAAS's DHCP server.
[14:00] <jtv> Basically, that's "when I serve DHCP to a node, where should I tell the node its gateway is?"
[14:00] <jtv> If you're not managing DHCP on any interfaces, it's not going to matter.
[14:01] <tomixxx3> puhh... ok, whre can i set the gateway-address then?
[14:01] <jtv> On the DHCP server.  Are you running your own DHCP server for the nodes, or are you letting MAAS serve DHCP?
[14:02] <tomixxx3> MAAS runs DHCP + DNS for the nodes
[14:02] <jtv> Ah OK
[14:03] <jtv> In that case you do need the gateway setting on the cluster interface.
[14:03] <jtv> I don't think you need re-commissioning after a change like that, per se, but the nodes may still have old information.
[14:04] <tomixxx3> k, i should maybe reboot nodes then
[14:04] <jtv> That would make them pick up the settings, yes.
[14:04] <tomixxx3> now is the question what is the gateway address
[14:05] <jtv> Whatever gateway the nodes should use when communicating to the internet.
[14:05] <tomixxx3> my maas server has 2 interfaces. is it the ip of the interface which connects the maas-server to internet?
[14:05] <tomixxx3> would make sense, not? ^^
[14:05] <jtv> Slightly different:
[14:06] <jtv> the gateway setting tells DHCP clients: "if you have a packet that you want to send to a host that's not on the same network, send it to the gateway and it will forward your packet."
[14:07] <jtv> So if your maas server is also the gateway between the nodes and the internet, it should be the IP address of the interface that the nodes can see.
[14:07] <jtv> (I hope.  Rusty!)
[14:08] <tomixxx3> hmm, i have set the gateway equal to ip address, but now my maas-server lost its i-net connection
[14:09] <jtv> The _server_?
[14:09] <jtv> The gateway setting will only affect the nodes.
[14:09] <tomixxx3> yes...
[14:09] <tomixxx3> i swear
[14:09] <tomixxx3> its the server
[14:09] <jtv> Are you sure you edited the cluster interface where you serve DHCP?
[14:09] <jtv> Or it could simply be unrelated...
[14:10] <tomixxx3> i have changed "interfaces" file and i have changed cluster interface settings in maas dashboard
[14:10] <jtv> Ah, then your interfaces file may be broken.
[14:10] <jtv> You could try running "sudo ifup <interface>" in a shell (where <interface> is e.g. eth0 or eth1)
[14:11] <jtv> Just to see if there's an error...
[14:11] <tomixxx3> ifup, ifdown works
[14:11] <jtv> Hmmm
[14:12] <tomixxx3> i dont understand this
[14:13] <jtv> Neither do I!
[14:15] <tomixxx3> i could try the ip of the other interface card as gateway
[14:16] <jtv> Well... gateway setting shouldn't affect the server itself.  Something else is wrong.
[14:17] <jtv> And it sounds as if it's in the system network settings, really, not the MAAS settings.
[14:18] <tomixxx3> server is reachable through 10.0.0.9/MAAS only i-net does not work
[14:19] <jtv> So... the nodes can reach the server and vice versa, but the server cannot reach the internet?
[14:19] <tomixxx3> yes
[14:20] <jtv> And that interface gets its IP address from the uni's DHCP server, right?
[14:20] <tomixxx3> yes
[14:20] <jtv> Does it have one now?  Is the interface up?
[14:20] <tomixxx3> yes
[14:20] <jtv> Can the server reach other hosts on the university network?
[14:21] <tomixxx3> just a moment, iam rebooting the server right now - and i have forgotten to run the NAT-script...
[14:21] <tomixxx3> its a NAT script provided by gmb
[14:21] <jtv> Yes, I remember.
[14:22] <jtv> I hope you don't have one of those weird setups where on some boots, eth0 and eth1 are switched around...
[14:22] <jtv> But probably not.
[14:22] <tomixxx3> hehe, i have tried already inverted ethernet ports in the script :D
[14:23] <jtv> Hope that didn't affect anything...
[14:23] <tomixxx3> schould not
[14:24] <tomixxx3> the server behaves like the nodes now: it can resolve the DNS name of any http-url but it cannot connect...
[14:24] <jtv> That does sound as if some wires got crossed somewhere...
[14:26] <tomixxx3> assume my gateway address is 143.205.140.30, the ip of the other network interface
[14:26] <tomixxx3> what could my ethernet settings look like xP - they should also allow 10.0.0.9 as a IP
[14:31] <tomixxx3> sorry wrong question. why iam not able to set the "network" parameter in cluster interface settings
[14:31] <tomixxx3> ?
[14:32] <jtv> Network parameter?  I don't understand what parameter that is... do you mean netmaks?
[14:32] <jtv> *netmask?
[14:34] <tomixxx3> no, i mean "network", the part of the net
[14:35] <jtv> Ohhh
[14:35] <jtv> That's not a parameter.
[14:35] <jtv> That's just a network address computed from your cluster interface's IP address and netmask.
[14:36] <tomixxx3> ok
[14:46] <tomixxx3> if i remove the gateway line from the "interfaces" file i have access to i-net on server again
[14:49] <jtv> Oh, did you set your own server's address as its own interface in its own interfaces file!?
[14:49] <jtv> That would create a fun situation.  :)
[14:50] <tomixxx3> yes i guess
[14:50] <tomixxx3> bad?
[14:51] <jtv> Yes — if you set a gateway in your interfaces file, that tells _that same machine_ where it should send its internet packets.
[14:52] <tomixxx3> so it asks only itself?
[14:52] <jtv> As you noticed we have 2 "gateway" settings.
[14:52] <jtv> One is in /etc/network/interfaces.
[14:52] <jtv> The other is in MAAS.
[14:52] <tomixxx3> yep
[14:53] <jtv> The one in /etc/network/interfaces is for configuring your server's own networking.
[14:53] <jtv> But the network interface that goes to the "outside" should just get its gateway from DHCP.
[14:53] <jtv> On the other hand, the gateway setting in MAAS is configuration for the DHCP server.
[14:53] <jtv> It doesn't do anything for your machine, but the nodes are its DHCP clients.
[14:53] <jtv> And it tells the _clients_ where their gateway is.
[14:54] <tomixxx3> ohoh
[14:54] <jtv> For the clients (your nodes), your server is the gateway.  That's fine.
[14:54] <jtv> But you configured your server to use itself (on the other interface) as the gateway.
[14:54] <jtv> And so it was probably just running around in circles.
[14:54] <tomixxx3> i understand
[14:55] <tomixxx3> good point
[14:57] <tomixxx3> so maas takes control over the one ethernet port?
[14:58] <tomixxx3> wow, this could solve a lot of troubles
[15:03] <tomixxx3> jtv: but i have to configure the ehternet port in the "interfaces" file too?
[15:03] <tomixxx3> jtv: just remove the "gateway" to be the same as the ip
[15:03]  * jtv reads backscroll
[15:04] <jtv> MAAS doesn't actually take control of any ethernet interfaces.  But it serves DHCP on the interface that faces your nodes, which is pretty bossy.
[15:04] <tomixxx3> OK, so only the "gateway" line should be replaced in the "interfaces" file?
[15:04] <jtv> I mean good, but it's more "taking control of the network" than "taking control of the ethernet port."
[15:05] <jtv> It's hard for me to imagine what the current state is, and it's getting a bit late to really dive into it... but generally, you set up your system's networking in /etc/networks/interfaces, and then you let MAAS run on top of that as basically just another server application.
[15:07] <jtv> MAAS tries to _detect_ your system setup when you install it, but it doesn't keep track after that and it doesn't change them.
[15:07] <jtv> It only does that sort of "bossy" stuff on the nodes.
[15:07] <tomixxx3> kk
[15:17] <tomixxx3> shit
[15:17] <tomixxx3> sorry, it seems it is working now!
[15:18] <tomixxx3> i have removed the "gateway" line from "interfaces" and set "ip router" in dashbaoard to "10.0.0.9" - same address like the IP address of the maaas-server
[15:19] <jtv> The "IP router" field in MAAS doesn't matter much — that's just for large setups where you sometimes want to allocate nodes that are connected to specific routers.
[15:19] <tomixxx3> hmmm, or was it the reboot of the nodes?
[15:19] <tomixxx3> i dont know...
[15:20] <jtv> Well the incorrect gateway setting in /etc/networks/interfaces you had earlier definitely sounded like a problem.
[15:20] <tomixxx3> yeah, but before today i had no gateway line configured...
[15:21] <tomixxx3> executed "wget www.orf.at" from ubuntu@cloud1 now and everything seemts to work "index.html" saved...
[15:23] <tomixxx3> i cant believe right now, maybe just a fata morgana
[15:23] <jtv> heh
[15:24] <jtv> Networking can be tough going, but it's useful knowledge in general life.
[15:25] <jtv> And when I say "general," obviously I mean "deeply technical computer-related."  :)
[15:27] <tomixxx3> yeah, quite a good feeling right now, i want to expand my cloud :D *hrhr*
[15:28] <tomixxx3> jtv: but it's definitely the "router ip" setting
[15:28] <tomixxx3> if have tried a different value now, and it is not working anymore
[15:29] <jtv> And if you set it back to the previous value, it works again..?
[15:29] <tomixxx3> jtv: worth a try
[15:29] <tomixxx3> what do u mean with previosu value? "ip address" == "router ip" or "ip address" == the address before today?
[15:30] <tomixxx3> i've tried it with "the address before today" and it does not work
[15:31] <jtv> I mean, if you reset it to the "good" value that worked just now, it works again?
[15:31] <tomixxx3> that's what im trying right now
[15:31] <tomixxx3> would be cool
[15:31] <tomixxx3> ^^
[15:32] <jtv> Let's hope it works!
[15:36] <tomixxx3> yep, working
[15:37] <jtv> Great!  I don't understand it, but maybe tomorrow I can look into it.
[15:37] <jtv> For now, I have to leave.
[15:38] <tomixxx3> kk, ty for help so far!
[15:39] <jtv> np!
[23:13] <chris38home__> just upgrade maas on trusty and got this in pserv.log :
[23:13] <chris38home__> twisted.internet.error.CannotListenError: Couldn't listen on 127.0.0.1:69: [Errno 2] No such file or directory.
[23:14] <chris38home__> any idea ?
[23:14] <bigjools> what version of the package?
[23:14] <chris38home__> 1.5+bzr1951+1951+243~ppa0~ubuntu14.04.1
[23:15] <bigjools> you are better off using the main archive for trusty
[23:15] <chris38home__> go it on 1.5+bzr1951-0ubuntu1 too
[23:15] <bigjools> the daily build packages may be broken at any time
[23:15] <bigjools> ok
[23:16] <bigjools> roaksoax: is that ^^ anything like the authbind error you saw?
[23:18] <roaksoax> bigjools yup. Still need to handle upgradea. Clean inatalls are not affected
[23:18] <bigjools> roaksoax: what's the procedure to handle the upgrade so chris38home__ can be unblocked?
[23:19] <bigjools> and the rest of us :)
[23:19] <chris38home__> ;-)
[23:19] <roaksoax> just edit /etc/authbind/byuid/xyz
[23:20] <roaksoax> and make ghe 68:68 become68:69
[23:20] <bigjools> right
[23:21] <chris38home__> cool, got it fixed
[23:21] <chris38home__> thanks ;-)