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