[01:52] <lazyPower> Catalys: So, the agents report the ip address of the unit during its init phase. If the IP address changes, the unit should be reporting the new ip address if you cycle that unit/machine agent.
[02:06] <Catalys> @lazypower: Alright and by cycle you mean doing a simple reboot of that specific unit then?
[02:06] <lazyPower> Catalys: thats one way, but you should be able to just cycle the systemd unit. `systemctl restart jujud-unit-mysql-0` for example
[02:07] <lazyPower> that was from memory, pardon me if the systemd naming schema is a little off, like instead of unit, its 'agent'
[02:07] <Catalys> Thanks it was just some bothering me for a bit and not clearly described in the documentation, or I might be blind lol.
[02:08] <Catalys> At least the question has now been answered haha.
[02:09] <Catalys> lazypower: However to be clear, say I move to a new subnet then Juju will fully take care of itself and pick a new IP on it own though?
[02:10] <Catalys> Or do you still have to go into the SSH and edit the interfaces file there.
[02:12] <lazyPower> so long as that new subnet can reach the controller there shouldn't be any additional action on your part
[02:13] <lazyPower> there might be some holdover issues with certain charms that dont handle the ip update correctly
[02:13] <lazyPower> like if you move mysql to a new subnet and say keystone doesn't have any logic to handle the updated ip once the config is written, that may cause you some heartburn
[02:13] <lazyPower> but its reasonably safe to do so in most cases.
[17:29] <Budgie^Smore> o/ juju world are we having fun yet?