[04:28] <mup> Bug #1284131 changed: Feature Request: maas-cli change ownership of machine <maas-shared-lab> <uosci> <MAAS:Expired> <https://launchpad.net/bugs/1284131>
[08:26] <mup> Bug #1681477 changed: Clicking in the disk selection dropdown (for storage hardware testing parameters) in the far right doesn't open the dropdown <ui> <MAAS:Invalid> <https://launchpad.net/bugs/1681477>
[08:29] <mup> Bug #1681477 opened: Clicking in the disk selection dropdown (for storage hardware testing parameters) in the far right doesn't open the dropdown <ui> <MAAS:Invalid> <https://launchpad.net/bugs/1681477>
[08:32] <mup> Bug #1681477 changed: Clicking in the disk selection dropdown (for storage hardware testing parameters) in the far right doesn't open the dropdown <ui> <MAAS:Invalid> <https://launchpad.net/bugs/1681477>
[08:35] <mup> Bug #1681477 opened: Clicking in the disk selection dropdown (for storage hardware testing parameters) in the far right doesn't open the dropdown <ui> <MAAS:Invalid> <https://launchpad.net/bugs/1681477>
[08:38] <mup> Bug #1681477 changed: Clicking in the disk selection dropdown (for storage hardware testing parameters) in the far right doesn't open the dropdown <ui> <MAAS:Invalid> <https://launchpad.net/bugs/1681477>
[08:38] <mup> Bug #1738436 changed: [2.3,  UI] No way to disable DHCP relaying <MAAS:Fix Released> <https://launchpad.net/bugs/1738436>
[08:41] <mup> Bug #1738436 opened: [2.3,  UI] No way to disable DHCP relaying <MAAS:Fix Released> <https://launchpad.net/bugs/1738436>
[08:44] <mup> Bug #1738436 changed: [2.3,  UI] No way to disable DHCP relaying <MAAS:Fix Released> <https://launchpad.net/bugs/1738436>
[09:53] <mup> Bug #1849166 changed: Support root on software raid in UEFI mode <MAAS:Invalid> <https://launchpad.net/bugs/1849166>
[10:05] <mup> Bug #1785314 changed: maas spaces are mis-translated <track> <juju:Triaged> <MAAS:Invalid> <https://launchpad.net/bugs/1785314>
[10:08] <mup> Bug #1785314 opened: maas spaces are mis-translated <track> <juju:Triaged> <MAAS:Invalid> <https://launchpad.net/bugs/1785314>
[10:11] <mup> Bug #1785314 changed: maas spaces are mis-translated <track> <juju:Triaged> <MAAS:Invalid> <https://launchpad.net/bugs/1785314>
[16:52] <inure> how are credentials passed from the MAAS db to the rack controller when authenticating to a OOB device?
[17:54] <mup> Bug #1864686 opened: Dropdown does not go away after selection <ui> <MAAS:New> <https://launchpad.net/bugs/1864686>
[17:57] <mup> Bug #1864686 changed: Dropdown does not go away after selection <ui> <MAAS:Incomplete> <https://launchpad.net/bugs/1864686>
[18:03] <mup> Bug #1864686 opened: Dropdown does not go away after selection <ui> <MAAS:Incomplete> <https://launchpad.net/bugs/1864686>
[18:21] <mup> Bug #1864691 opened: Traceback from cloud-init during enlistment ipmitool no such file or directory <MAAS:New> <https://launchpad.net/bugs/1864691>
[19:24] <inure> roaksoax: quick question?
[20:11] <roaksoax> inure: shoot... (although I no longer work on MAAS/Canonical/Ubuntu)
[20:14] <inure> roaksoax: well that is unfortunate but if you don't  know maybe you can direct me to someone who does.    I am trying to determine how OOB credentials are passed from the MAAS DB, to the OOB device, during actions to control the OOB.   What I am looking for specifically is, is this traffic encrypted or are credentials passed from Region to Rack ove
[20:14] <inure> r plain text?
[20:21] <roaksoax> inure: is largely unencrypted. THe assumption was that you'd never put MAAS public facing, hence, region <-> rack communication is largely unencrypted. A deploying (and deployed) get data from MAAS over HTTP (so not encrypted)
[20:23] <roaksoax> what *is* encrypted, is the protocol created for rack to rack internal communication to perform neighbor discovery, but otherwide, Region <-> to rack communication, which is RPC, and machine to MAAS communication (which was PXE/HTTP) is unencrypted
[20:43] <inure> roaksoax: we were hoping to manage a PCI/SOX network with rack controller on buy region controller out.  neither public
[20:44] <inure> roaksoax: would it be officially recommend to avoid this, or would it be acceptable to wrap the RPC across SSL tunnel?
[20:54] <roaksoax> inure: you mean a VPN ?
[21:03] <inure> no.  We have core networks which have normal security, and PCI/SOX networks which have heavily locked down networks
[21:03] <inure> roaksoax:
[21:03] <inure> all are internal to the data center
[21:03] <roaksoax> inure: i dunno if that would work, we've never really tried that. But a VPN... I do believe that would work
[21:04] <inure> like a site 2 site vpn configuration?
[21:05] <inure> or just a vpn tunnel?
[21:05] <roaksoax> inure: whatever makes it transparent for the machine, it should just work for MAAS
[21:06] <inure> ok
[21:06] <inure> ty for the advice