=== EntropyWorks_ is now known as EntropyWorks
=== lborda is now known as lborda_afk
=== rvba` is now known as rvba
roaksoaxrvba: around?14:12
roaksoaxrvba: i'm seeing this: http://pastebin.ubuntu.com/5676753/ any thoughts?14:13
rvbaroaksoax: yep…14:13
rvbaroaksoax: btw, you still need to merge https://code.launchpad.net/~andreserl/maas/ipmi_usercreation_ilo_versions_trunk/+merge/148579 in trunk right?14:13
roaksoaxrvba: yeah so the reason why that did land in 1.2 and not trunk is because julian thought it would be better to have the testing of that in trunk,s ince it didn't make sense for 1.214:14
roaksoaxrvba: and the above might be due to the nodegroup change?14:15
rvbaroaksoax: right.  Julian and I agreed that we don't really have time to add the testing so let's land this as is and file a bug about the lack of test for this.14:15
roaksoaxrvba: ok sounds good to me14:15
rvbaroaksoax: the error you pasted is due to the fact that 2 nodegroups match when we're trying to determine to which nodegroup a node should be attached.14:18
roaksoaxrvba: so same network?14:18
rvbaYeah, the IP of the connecting node belongs to a network to which for nodegroups are connected to.14:19
rvbaThus we cannot determine to which is should be attached.14:19
rvbaYou can probably fix this by removing the network in question on one side.14:19
roaksoaxyeah makes sense, I was jus testing whether your changes do fix the issue, but I just realized I was managing interfaces in both nodes14:20
roaksoaxso makes sense14:20
roaksoaxrvba: so this is a result of the revert you provided me with yesterday, righ? Since the current escenario I'm testing was working before that change14:27
roaksoaxrvba: and this means that we cannot have 2 clusters in the same network14:27
allenaproaksoax: I've just had a chat with rvba, and we have a plan...14:27
rvbaroaksoax: exactly14:27
rvbaroaksoax: you can have two clusters in the same network, but you have to manually remove an interface (in MAAS) on one of the nodegroups.14:28
roaksoaxrvba: ok I know how to setup an environment with 2 different clusters in different networks that's quite easy to do with kvm :)14:28
roaksoaxrvba: I see14:28
roaksoaxallenap: cool! what's the plan :)?14:28
rvbaroaksoax: to tell to MAAS: this network, although physically attached to 2 nodegroups, is actually managed by *this* nodegroup.14:29
roaksoaxright! makes sense14:29
roaksoaxrvba: since the above error shows up even when both networks are *unmanaged*14:29
allenaproaksoax: I'll change the find_nodegroup() function to prioritise managed interfaces, but fall back to non-managed interfaces. Additionally, if more than one non-managed interface matches, we blow up, suggesting that either one interface is marked as managed, or to remove the other interface.14:29
roaksoaxerr both cluster interface are unmanaged14:29
rvbaroaksoax: indeed, you need to *remove* one interface on one of the nodegroups/14:30
rvbaIn your case, you don't have any managed interface.14:30
roaksoaxrvba: right, say the master running in the region controller should not have any interface in the same network as the other cluster (bnoth managed/unmanaged)14:30
rvbaroaksoax: exactly.14:31
roaksoaxallenap: makes sense to me. But wouldn't it make better sense that if there's 2 cluster in the same network, to simply use 1 of those 2?14:31
roaksoaxrvba: ok makes sense. Ok will setup an environment and test14:31
allenaproaksoax: That might be okay. I can't think of an issue with that offhand. rvba?14:32
rvbaallenap: seems reasonable, as long as this only happens when no managed interfaces on this network are found I think that's ok.14:33
allenaprvba: If there's a managed interface, we will choose that one anyway. What if we find two managed interfaces for the same network?14:34
roaksoaxif we found 2 managed interfaces in the same network that most likely would be the case that i'm using different ranges for DHCP. (which is what I was doing right now).14:35
roaksoaxi guess it would make sense to try to detect from which one the node pxebooted from14:35
roaksoaxif not fallback to the first one14:35
allenaproaksoax: When an interface is managed, the DHCP ranges are defined by the netmask, iirc, so you can't have two cluster controllers managing the same network.14:36
rvbaIndeed, I don't think that's possible in MAAS right now.14:37
roaksoaxallenap: right, but I can have 2 DHCP servers saying "Server IP between - 200" and another one that will server " - 99"14:37
allenaproaksoax: You /can/ do that, but it's not a supported configuration: the interface should be marked as unmanaged.14:40
roaksoaxalright :)14:40
allenapFinding a node's nodegroup (aka cluster controller) in a nutshell: 1 managed interface on the network = choose this one; >1 managed interfaces on the network = misconfiguration; >1 unmanaged interfaces on a network = choose any14:42
allenapVersion 2 of Finding a node's nodegroup (aka cluster controller) in a nutshell: 1 managed interface on the network = choose this one; >1 managed interfaces on the network = misconfiguration; 1 unmanaged interface on a network = choose this one; >1 unmanaged interfaces on a network = choose any14:43
roaksoaxallenap: sounds good to me14:49
roaksoaxallenap: oh btw... i just made this change to python-tx-tftp in raring. Spads was getting his connection dropped and him and Daviey investigated and came up with the solution: http://pastebin.ubuntu.com/5676874/14:51
allenaproaksoax: That's cool :) I'll submit that upstream (and also press for landing of the other patches).14:53
roaksoaxallenap: that would be great!14:54
AskUbuntuMaas Web Interface not reachable after new installation! | http://askubuntu.com/q/27787415:29
=== kentb is now known as kentb-out
=== ubot5` is now known as ubot5

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!