[00:16] <thumper> wallyworld, babbageclunk: I have a question around upgrade-juju
[00:17] <thumper> I thought 'juju upgrade-juju --dry-run' would tell you what it would do
[00:17] <thumper> is that not right?
[00:17] <babbageclunk> thumper: otp (standup) - it should do, I think?
[00:17] <thumper> except in the situation where I'm using a build pre-release?
[00:18] <thumper> it says it would upgrade to 2.3.2
[00:18] <thumper> but I think it'll do 2.3.3.1
[00:18] <babbageclunk> thumper: have you specified --build-agent?
[00:18] <thumper> no
[00:18] <thumper> huh, this is different than it used to be
[00:46] <thumper> wallyworld, babbageclunk: I have a stop the line bug for the release...
[00:46] <thumper> the upgrade failed from 2.2.9
[00:46] <thumper> interestingly it failed upgrading to 2.3.2
[00:46] <babbageclunk> :(
[00:46] <thumper> I'd like some rubberducks
[00:47] <thumper> if you can jump in the release call, that'd be swell
[00:47] <babbageclunk> yup yup
[03:47] <babbageclunk> wallyworld: approved
[04:04] <anastasiamac> wallyworld: model cred in show-model and models output, PTAL https://github.com/juju/juju/pull/8372
[04:34] <anastasiamac> wallyworld: also, i *think* that htis is resolved now?... https://bugs.launchpad.net/juju/+bug/1680523
[04:34] <mup> Bug #1680523: add-credential azure fails <juju:Triaged> <https://launchpad.net/bugs/1680523>
[08:30] <kerem> Hi All,
[08:37] <thumper> o/ kerem
[08:43] <kerem> Hi Tim,
[08:43] <kerem> can you help me ?
[08:45] <kerem> I have a problem with juju
[08:47] <jam> whats up kerem?
[08:48] <kerem> Hey !
[08:49] <kerem> Is there anybody there?
[08:49] <jam> We're here, but you don't seem to be asking any questions yet
[08:50] <kerem> Hi Jam
[08:50] <kerem> We are trying to install Openstack using Juju (2.3.2) and MAAS (2.3). When we try to load the application via Juju, we get a random rope. for example when I want to work with 10.0.0.0/24 it uses the overlay (tenant) which is 192.168.1.0/24.  Q: How do I provide interface or ip assignments when distributing over the Juju? The same is true for LXD.
[08:51] <kerem> https://bugs.launchpad.net/juju/+bug/1616098
[08:51] <mup> Bug #1616098: Juju 2.0 uses random IP for 'PUBLIC-ADDRESS' with MAAS 2.0 <4010> <cpec> <juju:Fix Released by dimitern> <https://launchpad.net/bugs/1616098>
[08:52] <kerem> same problem
[08:52] <jam> kerem: so likely Juju knows about both addresses. And you can see those if you do "juju show-machine X". Its a bit arbitrary which address we pick to show in status, since we only have 1 value.
[08:52] <jam> kerem: is there an actual problem that you have for the application running, or is it just that 'status' is showing you an address you don't like?
[08:53] <kerem> I created 5 space and subnet
[08:55] <kerem> I want to use management-space in node setup, fkaat is using provider-space or ceph-cluster-space
[08:56] <kerem> My goal is that the physical server and the Lxd servers are in the same space.
[08:57] <kerem> When I try to deploy, the physical server gives me an ip address I do not want.
[08:57] <jam> kerem: so are you specifying those as bindings in the bundle?
[08:57] <jam> bindings:
[08:58] <jam> kerem: if you deploy the charm directly, you can do "juju deploy fkaat --bind provider-space" for example
[08:58] <kerem> yes
[08:58] <jam> or in the bundle definition it would be
[08:58] <jam> bindings:
[08:58] <jam>  "": provider-space
[08:58] <jam> (you can bind endpoints separately, but for now, I'm assuming you want them all to use the same binding for a given application)
[09:00] <kerem> I could not tell
[09:00] <kerem> sorry
[09:01] <jam> kerem: I'm assuming you're deploying from a bundle, can you share that bundle? say via pastebin.ubuntu.com ?
[09:03] <kerem> No, I have not yet.
[09:03] <kerem> Because I can not get it like I want.
[09:04] <kerem> https://bugs.launchpad.net/juju/+bug/1616098
[09:04] <mup> Bug #1616098: Juju 2.0 uses random IP for 'PUBLIC-ADDRESS' with MAAS 2.0 <4010> <cpec> <juju:Fix Released by dimitern> <https://launchpad.net/bugs/1616098>
[09:04] <kerem> This same problem
[09:05] <kerem> my management ip 10.50.10.81
[09:05] <kerem> my storage ip 10.1.3.81
[09:06] <kerem> on a node1
[09:07] <kerem> deployment start "juju deploy nova-comupte --bind management-space" is it true?
[09:26] <jam> kerem: something like that, but it depends what the actual spaces are and how you want the applications to be configured.
[20:47] <thumper> babbageclunk: ping
[20:47] <babbageclunk> thumper: pong
[20:48] <thumper> babbageclunk: can you be a rubber duck again?
[20:48] <babbageclunk> yup - give me 2 mins? Just making a OR
[20:48] <babbageclunk> PR
[20:48] <thumper> sure, just join the release HO when you are ready
[21:02] <hml> PR review please?  https://github.com/juju/juju/pull/8379
[21:59] <babbageclunk> hml: looking
[22:00] <hml> babbageclunk: ty
[22:04] <babbageclunk> hml: approved
[22:05] <hml> babbageclunk: :-)