[06:14] <manadart_> Anyone around for a simple review? https://github.com/juju/juju/pull/11851
[07:21] <manadart_> Merge 2.8 into develop: https://github.com/juju/juju/pull/11852
[10:47] <mirek186> Does anyone know how to deploy ntp on bare machine level? I know you can have relation with other charms, but what if all charms are deployed in LXD containers but you want just a single ntp server on the machine hosting LXD?
[10:48] <blahdeblah_> mirek186: Just use a basic charm like ubuntu, deploy it to the bare metal, and associate ntp with that.
[10:56] <mirek186> but what if it's part of a bigger deployment e.g openstack-bundle , where machine provisioning is done by maas for you, it's easy for ceph-osd and nova-compute as those components go on bare ubuntu, but I have few infrastructure machines where every charm is deployed into lxd container.
[11:10] <blahdeblah_> You can still push a basic charm onto the machine by adding it manually, or you can just configure MAAS to deploy an appropriate NTP config for you.
[11:10] <blahdeblah_> 9 times out of 10, the only thing you really need to change about the default ntpd or chronyd config is ensure that a list of at least 4 nearby NTP servers are used rather than random defaults which are half an Internet away from your network.
[11:12] <mirek186> blahdeblah_ with MAAS is there an out of the box option or you have to add an extra curtin script for it?
[11:12] <blahdeblah_> It has been a while since I touched it, but you could at least specify your own list of NTP servers, I think.
[11:14] <mirek186> In MAAS settings there is an option for NTP but is this a one which goes then to each deploy machine? If yes, is there a point of an extra ntp charm then?
[11:15] <blahdeblah_> Like I said, it's been a while since I touched it.  But when I still worked for Canonical, the MAAS team were trying to make it so that MAAS deployed out of the box with a decent NTP config so that you didn't need the charm.
[11:17] <mirek186> Ok, thanks for letting me know.
[19:27] <mirek186> Could someone help me trace down probably my misconfiguration on ovn-chassis, I have external network 10.10.60.0/24 and config: physnet1:br-ex, br-ex:br60 . When trying to create instance I've got an error nova.exception.PortBindingFailed: Binding failed for port, my ovn knowledge is zero, so I would appreciate if someone could point me in the right direction to verify first my ovn charm config is correct and then why it's it's failing to create. The nova
[19:27] <mirek186> host has access to br60 so it's not that I think.