[04:24] <timClicks[m]> We have an inconsistency wrt how we describe LXD
[04:25] <timClicks[m]> Within the CLI, it's the "localhost" cloud
[04:25] <timClicks[m]> But that term isn't used in the public docs
[05:24] <jam> wallyworld, kelvinliu Is there an easy way for a Unit agent to determine the name of the K8s pod names? (or for 1 unit to find the names of all pods)
[05:24] <jam> without hitting the K8s API?
[05:25] <kelvinliu> u mean to find that unit's workload pod?
[05:26] <jam> kelvinliu, right. AIUI, there are config options where you need to configure Mongo with the pod DNS names for its replica set
[05:27] <jam> I'm mostly acting as a proxy for the question from MarkMaglana
[05:31] <kelvinliu> i assume it's a statefulset
[05:31] <kelvinliu> and the pod's names are fixed
[05:31] <jam> kelvinliu, for Mongo I'm sure it would be  (if you need to configure the name of pods before the pods exist, they have to be fixed)
[05:32] <jam> kelvinliu, I don't know the exact use case MarkMaglana is requesting. Just that he wanted to know the names of the pods, and I'd like to have general answers for them
[05:34] <kelvinliu> we do have the pod name in `cloudcontainers` for statefulset
[05:35] <kelvinliu> im thinking he can get it
[05:35] <kelvinliu> how the uniter can get it.
[05:36] <jam> kelvinliu, that is in the pod spec or ?
[05:36] <kelvinliu> nah
[05:36] <kelvinliu> we get the pod name after the pod has been created
[05:38] <kelvinliu> so we update it into that doc once k8s tells us the pod name
[05:39] <kelvinliu> we can easily get the pod name by k8s API because we have proper labels and annotations to look for
[05:41] <jam> kelvinliu, sure, but we don't currently expose that to the charm, do we?
[05:41] <kelvinliu> we have k8s python client built into our operator image already
[05:42] <kelvinliu> so charm can have a in-cluster k8s client to get access of it
[05:43] <jam> kelvinliu, ok. But that isn't talking to Juju or coordinating with Juju data. That said, it is still stuff that we can point charmers at.
[05:43] <kelvinliu> https://github.com/kubernetes-client/python
[05:44] <kelvinliu> I don't think currently charm can get the pod name from juju for now
[05:45] <kelvinliu> but if it's the action scripts want to know the pod name then it's easy
[05:45] <kelvinliu> because k8s expose the pod name in ENV inside the pod itself
[05:46] <kelvinliu> juju run --unit mariadb-k8s/0  'env | grep mariadb-k8s-0'
[05:46] <kelvinliu> HOSTNAME=mariadb-k8s-0
[05:55] <jam> kelvinliu, so I'm pretty sure this is more about during eg 'config-changed' than during an action.
[05:55] <jam> And wanting to know all pod names
[05:58] <kelvinliu> probablly we have to let the leader to filter the pod list using application name labels
[05:59] <kelvinliu> wait u mean he want this pod name list to generate the replica string?
[06:03] <kelvinliu> then the charm should be operator charm
[06:05] <kelvinliu> for an operator charm to provision a new instance of mongo, it might be reasonable to do it via an action?
[06:06] <kelvinliu> im not quite sure what's the current status of operator charm feature yet. might be good to discuss on mattermost further
[06:12] <jam> kelvinliu, so as mentioned I don't know the exact use case. If it was something like Mongo, I don't think it quite fits the idea of an operator charm, other than you can solve anything in some way eventually :)
[06:34] <kelvinliu> ok
[08:39] <stickupkid> achilleasa, approved the integration test changes
[08:45] <achilleasa> stickupkid: cool. thanks! no issues with the changes in the arg parser then?
[08:45] <stickupkid> achilleasa, nope, I tested the output of all flags
[09:21] <achilleasa> manadart_: what do you think about moving ProviderInterfaceInfo into core/network? this (https://github.com/juju/juju/blob/develop/environs/networking.go#L98) is the only thing in the Networking interface that forces you to import juju/network
[09:24] <manadart_> achilleasa: It's already duplicated. See core/network/nic.go
[09:24] <manadart_> achilleasa: So by all means, get rid of the juju/network one.
[09:24] <achilleasa> ah nice! will do
[09:25] <manadart_> achilleasa: And we should be using HardwareAddress over MACAddress, because Infiniband devs do not have a MAC.
[09:26] <achilleasa> manadart_: ok, I will try to rename it... hopefully it won't break too many tests :D
[09:26] <manadart_> achilleasa: NBD if it's a hassle.
[11:18] <manadart_> achilleasa: Can you look at this one? https://github.com/juju/juju/pull/11778
[11:18] <achilleasa> looking
[11:30] <achilleasa> manadart_: running QA now; in the meantime can you look at https://github.com/juju/juju/pull/11779?
[11:31] <manadart_> achilleasa: Yep.
[11:47] <achilleasa> manadart_: seems to fail during the merge: https://pastebin.canonical.com/p/Cr25N4KymT/
[11:51] <manadart_> achilleasa: Did you change the MAC address? Let me try it again...
[11:52] <achilleasa> yes, I changed name, mac (the :fe:fe at the end) and providerid
[12:13] <manadart_> achilleasa: I think omitting the _id has affected this. I ran it again with success. https://pastebin.canonical.com/p/g9sq3qFxf7/
[12:14] <achilleasa> manadart_: ah crap... forgot that IDs are generated by us... sorry
[12:15] <achilleasa> approved
[19:18] <yan0s> Is it possible to add a new LXC having an interface on a space that its host didn't originally had this space?
[19:19] <yan0s> but the host now has a manually provided interface on the subnet of this space
[19:22] <yan0s> I want to add the LXC on a new vlan interface wityhout having to redeploy the host
[19:57] <pmatulis> can i configure a lxd profile on a per-machine basis?
[19:57] <pmatulis> hml, ?
[19:57] <hml> pmatulis:  with juju?  or in general?
[19:58] <hml> pmatulis:  you can add a profile with more info to an existing machine, the machine may get rebooted.
[19:58] <hml> pmatulis: not sure if juju would pick that up or not
[19:59] <pmatulis> hml, ideally with juju
[19:59] <hml> pmatulis:  juju lxd profiles are via the charm and per application.
[20:00] <hml> pmatulis:  you can add what you want to the default profile and juju uses that for all machines
[20:00] <pmatulis> right ok
[20:00] <pmatulis> so i will have to do it manually then
[20:01] <pmatulis> that too bad. maybe i will open a wishlist bug