mupBug #1523091 changed: dhcp/dns inconsistency prevents enlistment <MAAS:Expired> <https://launchpad.net/bugs/1523091>04:23
mupBug #1523091 opened: dhcp/dns inconsistency prevents enlistment <MAAS:Expired> <https://launchpad.net/bugs/1523091>04:29
mupBug #1523091 changed: dhcp/dns inconsistency prevents enlistment <MAAS:Expired> <https://launchpad.net/bugs/1523091>04:32
=== cpaelzer_afk is now known as cpaelzer_
=== rbasak_ is now known as rbasak
=== cpaelzer is now known as cpaelzer_afk
=== cpaelzer_afk is now known as cpaelzer
mupBug #1532271 changed: maas fails to deploy ibm power nodes <MAAS:New> <https://launchpad.net/bugs/1532271>11:39
=== roaksoax-brb is now known as roaksoax
mupBug #1532271 opened: maas fails to deploy ibm power nodes <MAAS:New> <https://launchpad.net/bugs/1532271>11:42
mupBug #1532271 changed: maas fails to deploy ibm power nodes <MAAS:New> <https://launchpad.net/bugs/1532271>11:57
mupBug #1542287 opened: BMC fails after node is commissioned  <MAAS:New> <https://launchpad.net/bugs/1542287>11:57
=== rvba` is now known as rvba
=== cpaelzer is now known as cpaelzer_afk
mupBug #1542287 changed: BMC fails after node is commissioned  <MAAS:New> <https://launchpad.net/bugs/1542287>12:03
mupBug #1542287 opened: BMC fails after node is commissioned  <MAAS:New> <https://launchpad.net/bugs/1542287>12:09
=== cpaelzer_afk is now known as cpaelzer
mupBug #1542324 opened: Nodes enlist without any IPMI/BMC information <MAAS:Confirmed> <MAAS 1.10:Confirmed> <https://launchpad.net/bugs/1542324>13:48
mupBug #1542326 opened: Cannot deploy Ubuntu 14.04/15.10 on EFI system after 1.8 version to 1.9 upgrade <MAAS:New> <https://launchpad.net/bugs/1542326>13:48
=== cpaelzer is now known as cpaelzer_afk
=== cpaelzer_afk is now known as cpaelzer
mupBug #1542349 opened: Network aliases are created during commissioning <cdo-qa> <MAAS:New> <MAAS 1.9:New> <https://launchpad.net/bugs/1542349>14:58
mupBug #1542353 opened: 6 Core system is listed as having a single CPU <cdo-qa> <MAAS:New> <https://launchpad.net/bugs/1542353>14:58
haasnI'm playing around with a new MAAS setup (for testing) and there are a few things I'm stuck on:15:11
haasn1. Network topology. I don't understand the intended design. I have a public LAN that is connected to the internet and uses real IPs (134.X.X.X), and my maas region+cluster controller has one interface in this LAN and one interface currently not connected to anything15:13
haasnI understand from documentation that it's typical to have a second interface on the cluster controller plugged into an extra LAN on an extra switch for this cluster, which is where the nodes will be connected. The cluster controller's DHCP manages this LAN15:14
haasnBut then how are nodes expected to connect with the internet?15:14
haasnAnd am I supposed to use private IPs here or another public (global) IP block for this cluster?15:15
haasnIf the former, does that mean the cluster controller needs NAT? How do I make the nodes reachable, then?15:15
haasnOr is the intended design that *every* node has two NICs, one connected to the internet via the public LAN and one connected to the local network for DHCP/pxeboot/management purposes?15:15
haasnBut that would require having two NICs on every single machine I want to manage, which seems excessive15:16
haasnAlternatively, I could consider having a “flat” network setup where I reserve a real IP range on the (non-maas) DHCP server running on the “public”/internet-connected LAN and manually configure this with fixed addresses, then set it to use next-server <maas.ip> for pxe-boot purposes15:17
haasnBut then I wouldn't be using the maas DHCP at all, and I understand this comes with configuration annoyances beyond the overhead of setting up the DHCP once15:18
haasn2. Node commissioning. For now, I've just created a few VMs for testing on the “public” LAN and set the external DHCP server up to load pxelinux.0 and set next-server as the IP of the maas region/cluster controller as described in my previous message. When adding the nodes in the maas web GUI, it shuts them on, boots into its own image, and a minute later or so the status changes to “Failed15:20
haasncommissioning” with no further debug output15:20
haasnI watched the terminal output of the VMs while it was commissioning and all the messages go by really quickly, but I do see a lot of apt failures referring to being unable to connect to external domains. I assumed it was some DNS/DHCP error, and decided to boot a livecd for testing purposes (ubuntu), but this livecd has no problems reaching ubuntu.com15:21
haasnSo I'm not really sure why the commission image seems to be silently failing with no logs that give me any information15:21
haasnhttps://insights.ubuntu.com/2015/04/10/maas-network-layouts-for-the-landscape-autopilot/ seems to go into some detail about network topology but it leaves me with more questions than answers15:29
haasn1. in the “flat network” approach, why does one of the devices still require two NICs plugged into the *same* network? That just seems excessive!15:29
haasn2. In the “split network” approach, why are both networks plugged into the same switch? Huh?15:29
haasnIs the switch supposed to have VLANs configured for them? Why not just draw two switches then?15:30
haasnAnd it still doesn't explain how the nodes are supposed to be able to reach the internet15:30
haasnIf they're stuck on a private network15:30
haasnThis graphic would be much more helpful with real example IPs15:41
haasnhttps://www.mirantis.com/blog/understanding-options-deployment-topologies-high-availability-ha-openstack/ is not maas-specific but it suggests https://www.mirantis.com/wp-content/uploads/2012/09/netlayout.png15:43
haasnSo I guess that answers what I'm confused about: Yes, you really are supposed to get two NICs on every single node, one for public and one for private usage15:44
haasnNow I just need maas to actually work :p15:47
roaksoaxhaasn: if you are running on single machine with region/cluster on it, you can have maas on a flat network. You may need 2 nic's connected to the cluster if you want to power manage machine and these are in a different netwpork, if they are routed, then you dont15:59
roaksoaxhaasn: however, in reality, if you only had 1 NIC, power managed is routed, and you have a gateway (aka your router), then you only need to configure the Cluster Controller interfac efor which you want to manage DNS/DHCP and that's were MAAS will pxe boot from16:01
haasnI think I've decided to stick with a flat network approach and just disable the maas DHCP server, that way I only need one NIC per node and the only drawback is that I have to manually add all new nodes. I don't expect to have more than 10 nodes at most16:03
haasnSo this is fine16:03
haasnI also don't need an extra switch or upstream configuration16:03
haasnTo clarify about my commissioning troubles: The machines are recognized, I get a full YAML output of all details including CPU, memory, disks etc. which are all recognized successfully16:07
haasnSo clearly it's communicating right, the machines are recognized successfully.. and then it just sets the status to “Commissioning failed”16:08
haasnWith no further debug logs16:08
roaksoaxhaasn: did you see to commissioning scripts section at the bottom and see whether anything failed?16:09
roaksoaxhaasn: so if you go to the details page, at the bottom you'll have lshw output, and a drop down to chose between commissioning output and the scripts16:10
roaksoaxand maybe one of the scripts is failing, which is causing commissioning to fail16:10
roaksoaxthat's if you are using 1.8+ though16:10
haasnroaksoax: ah, I missed that dropdown menu16:16
haasnI get a lot of failed scripts, e.g. https://0x0.st/X2V.txt16:16
haasn134.60.209.143:8000 is the maas controller16:16
haasnBut nothing is running on port 800016:16
haasnmaas-proxy is installed on the machine, but I didn't touch its configs. The documentation doesn't seem to mention anything about maas-proxy or it being required16:17
=== dimitern_ is now known as dimitern
haasnHmm. Seems maas-proxy.conf is configured to use http_port 8000 and http_port transparent 3128, but the former is ignored by squid3?16:46
haasnI'm not sure if maas-proxy.conf is being used at all.. it isn't mentioned in the command line of the running squid3 instance16:53
haasnI found the error17:06
haasnsquid3 was already running with the wrong config (why?)17:06
haasnstopped it, started maas-proxy manually and now it works17:07
haasnp.s. does this mean I'm running an open proxy on that machine that the entire internet can access?17:07
haasnSeems like it, “allow localhost src all # TODO: change this” nice17:10
haasnAlso, wake on lan doesn't seem to work. It works if I run it manually (ether-wake -i enp1s1f0 MAC)17:10
haasnBut maas doesn't get that17:10
haasnapt install wakeonlan # fixed it17:13
=== marcoceppi_ is now known as marcoceppi
mupBug #1542410 opened: [1.10] IPMI power query fails <MAAS:New> <https://launchpad.net/bugs/1542410>17:25
mupBug #1542410 changed: [1.10] IPMI power query fails <MAAS:New> <https://launchpad.net/bugs/1542410>17:28
mupBug #1542410 opened: [1.10] IPMI power query fails <MAAS:New> <https://launchpad.net/bugs/1542410>17:31
=== frobware_ is now known as frobware
=== narindergupta is now known as narindergupta_aw
mupBug #1542410 changed: [1.10] IPMI power query fails <MAAS:New> <https://launchpad.net/bugs/1542410>19:40
haasnThe MAAS documentation and advertising suggests I can “Setup the RAID and Network configuration you want through the MAAS web UI or CLI” but I can't find any way to setup RAID on the web interface20:35
haasnOr does that require changes to the preseed?20:36

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