| mup | Bug #1720167 opened: Clicking 'back to machine details' goes to the main summary page <ui> <MAAS:Triaged> <https://launchpad.net/bugs/1720167> | 15:21 |
|---|---|---|
| mup | Bug #1719639 changed: proxy description documentation fix <MAAS:Incomplete> <https://launchpad.net/bugs/1719639> | 16:15 |
| jamesbenson | hey | 17:16 |
| jamesbenson | Is there a terminal password set for machines? someway to log into machines physically? | 17:17 |
| roaksoax | jamesbenson: nop, you can set that yourself via cloud-init userdata | 17:51 |
| jamesbenson | okay. bummer. thanks roaksoax | 17:53 |
| bdx | hello, is it supported to have ipmi/pxe traffic on a separate network then the maas-mgmt net, or is it recommended to have maas-mgmt also be the ipmi/pxe net? | 17:58 |
| roaksoax | bdx: supported | 18:00 |
| roaksoax | bdx: you only need a rack controller in that separate network | 18:00 |
| bdx | roaksoax: to reduce cabling, I wan't to use my eth0 for my ipmi interface (on ipmi vlan), and maas-mgmt on eth0 (flat) | 18:02 |
| bdx | for each node | 18:02 |
| bdx | maas will let me specify the managed impi/pxe network separate from the mgmt-net? | 18:03 |
| bdx | roaksoax: I assume thats what you mean | 18:03 |
| roaksoax | bdx: maas has logic that tries to figure out which rack controllers can reach to the power management network | 18:04 |
| roaksoax | bdx: and if you were to have a rack controller directly connected to the BMC's, which is not a rack controller you would pxe boot machines from | 18:04 |
| roaksoax | bdx: maas will be able to power manage | 18:05 |
| bdx | roaksoax: so in my environment, I'm experimenting with a combined region + rack on the same machine | 18:05 |
| bdx | I've just never seen anywhere to configure the pxe/ipmi separate from the mgmt net ... but from what you are saying, it sounds like it doesn't matter | 18:06 |
| bdx | maas will just detect the bmc interface and manage it no matter what network its on | 18:07 |
| bdx | ^ yeah? | 18:07 |
| roaksoax | bdx: it is not a configurable option in maas. MAAS will automatically try to reach to the BMC | 18:22 |
| roaksoax | bdx: so for example, if you have 2 nics on he rack, on two different subnets | 18:22 |
| roaksoax | bdx: and one connects to the management network, one to the bmc network | 18:23 |
| roaksoax | bdx: maas will figure out on its own | 18:23 |
| scook | Howdy, anyone online? | 19:23 |
| bdx | roaksoax: wizardry! that's absolutely amazing | 21:11 |
| bdx | roaksoax: thx | 21:11 |
| roaksoax | no prob! | 21:20 |
| mup | Bug #1720242 opened: MAAS post-inst script can create duplicate lines in named.conf.local <MAAS:Triaged> <https://launchpad.net/bugs/1720242> | 21:54 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!