[00:37] <jac_cplane> I'm seeing this error on Centos7  15:48:11 ERROR juju.worker.proxyupdater error writing apt proxy config file: open /etc/apt/apt.conf.d/95-juju-proxy-settings: no such file or directory
[00:39] <jac_cplane> apt does not run on Centos7:  any thoughts
[00:39] <jac_cplane> unit-rac-master-0: 15:48:12 ERROR juju.worker.proxyupdater error writing apt proxy config file: open /etc/apt/apt.conf.d/95-juju-proxy-settings: no such file or directory
[00:41] <jac_cplane> can I ignore this
[00:47] <tvansteenburgh> jac_cplane: i'm on the way out the door, but i'd ask that one on the mailing list.
[00:49] <tvansteenburgh> jac_cplane: you can probably ignore it but i'd recommend you ask there anyway
[02:22] <jac_cplane> ok - tahnks
[07:16] <kjackal> Good morning Juju world!
[14:28] <vlad_> Hey everyone just wanted to say this is a great IRC channel and you have all been really helpful. I also want to say thanks for putting up with me I know I ask a lot of questions, but I'm deeply interesting in learning juju and maas and learning it right.
[14:30] <vlad____> Anyway I was wondering if anyone in here is decently experience with maas?
[15:21] <lazyPower> vlad____: i have a bit of experience with MAAS. i'm not certain i can answer any advanced questions but i have a fundamental understanding of the application
[15:26] <zeestrat> vlad____: Anything in particular you're wondering about? If it's maas specific make sure to ask the guys in #maas too
[15:38] <vlad____> zeestrat: I'm having issues with the underlying networking of my openstack bundle. It complains that there are no public or private IPs available. I'm assuming this means juju needs to rely on something running dhcp and I wanted to know what the best practice is/was. Is it to run dhcp from maas for everything or have something like infoblox doing that? Or can juju operate without dhcp and I'm a complete idiot?
[16:16] <lazyPower> vlad____: maas really likes to have that DHCP control.
[16:16] <lazyPower> however, it can outsource to a third party DHCP server if configured to do so. it just stops its dhcp server and will let the networks existing DHCP do its thing.
[16:18] <lazyPower> vlad____: in any case, juju doesn't care. Whatever the machine enlists with network wise will be passed to juju. However, it will favor any interfaces that are set to "auto-assign" unless all interfaces are declared as DHCP, then it should hand over all the interfaces in one go, that's one gotchya i discovered last week
[17:15] <vlad____> Thanks for the help guys! Sorry had to afk for a bit
[17:15] <vlad____> lazyPower: Can you give me more details on that gotcha? I think this is what's kind of messing me up
[17:16] <lazyPower> vlad____: so, in your unit detail under the 'network' tab, you'll notice your interfaces list their fabric, and configuration
[17:16] <vlad____> Right now the cloud runs perfectly fine if all network configs in my bundle point to my PXE zone (that has its dhcp handled by maas) so I've assumed I was having a dhcp issue. However, I also have issues assigning all interfaces to dhcp in maas for some reason
[17:16] <vlad____> lazyPower: Yeah
[17:17] <lazyPower> if any of those interfaces are set to 'auto-assign', juju will favor that interface instead of any DHCP configured interfaces. in my experience, it yielded units with only a single configured interface. once i changed the 2 interfaces to DHCP i got the 2 interfaces as i expected.
[17:17] <vlad____> lazyPower: Were you using network zones and bindings in that example?
[17:17] <lazyPower> yeah i had tha tissue too, i would set it to DHCP and it would revert, what i found helps (in maas 2.2) is to set it, navigate to a different tab and then reload the interfaces tab to ensure it stuck.
[17:18] <vlad____> lazypower: Ahhh ok cool that's going to be super helpful!
[17:18] <lazyPower> I was not, i have a very vanilla flat network scheme. 1) management network that is host only, 2) proper top level lan network for the public-address.
[17:18] <lazyPower> i should note, i run VMAAS (maas in a vm) and its only managing VM's that are statically enlisted, not a pod or anything cool that maas currently supports :)
[17:19] <lazyPower> so some of this may not be useful to you, but anecdotally i hope it helps.
[17:23] <vlad____> lazyPower: It helps a lot. I'm on a team by myself deploying to less than ideal infrastructure being managed by a maas that's hosted on a VM. So I've got lots of moving targets to hit right and each deploy takes quite a while to finish (not too long to fail though).
[17:23] <vlad____> The VM is in vcenter as well which means it doesn't see the network the same way the physical boxes do... I've gotten the cloud deployed 90% complete but am having issues on the last leg with networking
[18:05] <lazyPower> vlad____: yeah, i understand your plight, i'm using direct KVM myself, so there's a bit of a gap there
[18:05] <lazyPower> but if maas is seeing the network config, and they are set to DHCP (either managed or unmanaged) juju should be getting the interfaces.
[18:06] <lazyPower> now i'm not 100% positive about the spaces, thats on my list to dive into but i haven't quite gotten there yet.
[18:36] <roaksoax> mpontillo: /win 3
[18:36] <roaksoax> err