[00:06] <wallyworld> vino: the bzr command is "bzr revision-info"
[00:08] <kelvin> wallyworld, do u think we should define the device constrains at `juju/juju/device` or somewhere else?
[00:10] <wallyworld> hmmm. i think "devices" is ok for now
[00:11] <kelvin> in the root dir `/devices`?
[00:16] <vino> ok.
[00:19] <vino> wallyworld : and for mercurial hg equivalent is hd id --id
[00:19] <wallyworld> great
[00:19] <wallyworld> kelvin: yeah, i think so for now
[00:20] <kelvin> wallyworld, great, thx
[01:35] <thumper> wallyworld, kelvin: how about core/devices?
[01:35] <thumper> i had wanted to move the /network into core/network
[01:35] <thumper> as long has it has no state or api dependencies
[01:36] <kelvin> core/devices looks a good one,
[01:37] <kelvin> yes, then we can shorter the root dir ls
[02:13] <wallyworld> thumper: we should move storage as well then
[02:13] <thumper> wallyworld: yes
[03:05] <wallyworld> anastasiamac: if you have a moment? https://github.com/juju/names/pull/89
[03:11] <wallyworld> veebers: want to talk about resources? thumper has stodd me up for our 1:1 :-)
[03:11] <veebers> wallyworld: hah, sure thing
[03:11] <thumper> wallyworld: we did have a long catch up this morning :)
[03:12] <wallyworld> we did. but you could have told me :-)
[03:14] <thumper> wallyworld: sorry, was planning to but got stuck talking to xavpaice
[03:25] <kelvin> wallyworld, could I have ur a few minutes?
[03:36] <kelvin> thinking if it's reasonable to consolidate the struct (params struct) at api and apiserver in single place.
[03:39] <kelvin> to have the api schema shared for client, server side, or other dependencies.
[03:44] <wallyworld> kelvin: sure, just finished talking to chris, free now
[03:45] <kelvin> c u in hangout
[03:45] <kelvin> now?
[04:08] <babbageclunk> thumper: will the hub drop messages if the handler takes too long?
[04:09] <babbageclunk> (I mean, if a subscribed handler takes too long)
[04:46] <anastasiamac> wallyworld: reviewed..
[04:46] <wallyworld> ty
[04:52] <wallyworld> anastasiamac: i pushed a change to use a common method
[05:06] <kelvin> wallyworld, could u take a look the PR again when u have time? thx
[06:35] <vino> wallyworld: have a min ?
[06:35] <wallyworld> sure
[06:35] <vino> HO
[06:36] <wallyworld> am in standup
[07:54] <thumper> babbageclunk: no
[07:54] <babbageclunk> good
[07:54] <thumper> did you want to chat about it?
[07:55]  * thumper is back in the office for a bit
[07:55] <babbageclunk> no, it's fine
[07:55] <babbageclunk> thanks!
[07:55] <thumper> jam: are you back around?
[09:04] <jam> thumper: hey, just got back, quite the adventure.. are you still here?
[09:10] <thumper> um... was just about to leave, but can chat
[09:11] <thumper> jam: did you want to catch up?
[09:15] <jam> thumper: sure. Just chatting with manadart, will be available in 2min.
[09:16] <thumper> kk
[09:29] <manadart> Need a review for: https://github.com/juju/juju/pull/8838
[09:33] <stickupkid> manadart: i'll take a look
[09:34] <stickupkid> manadart: just out of curiosity, but jam will probably want to vet the whole thing (?)
[09:38] <manadart> stickupkid: Assume so.
[10:06] <stickupkid> manadart: done - just a few questions
[10:06] <manadart> stickupkid: Shoot.
[10:23] <stickupkid> manadart: questions in the PR
[10:28] <manadart> stickupkid: Ta.
[11:05] <naturalblue> hi. I am trying to deploy a juju maas controller and it starts to deploy but i notice later on it looks for an IP (that was MAAS's old IP address) and then fails to deploy. Is there a way to get the details of what it is looking for. I have changed all ips and restarted all services on MAAS. I am not sure why it is still looking for the old address.
[11:07] <BlackDex> naturalblue: Did you re-deploy juju?
[11:07] <BlackDex> the controller?
[11:08] <BlackDex> If not, i think you need to reconfigure your cloud providers in juju
[11:14] <naturalblue> ah that maybe it. i think although i removed the cloud provider after the controller, i possible changed its ip after i added it back in.
[11:14] <naturalblue> I will give it atry and let you know.
[11:14] <naturalblue> BlackDex: Thansk
[11:15] <naturalblue> no, i just checked with juju show-cloud openstack-maas and the endpoing shows the correct ip (i.e. the new IP)
[11:17] <naturalblue> but cloud-init is definitely looking for the old address and then aborting
[11:17] <BlackDex> during boot?
[11:17] <BlackDex> pxe boot?
[11:19] <BlackDex> Please check the if the IP's are correct during the following command: `sudo dpkg-reconfigure maas-region-controller maas-rack-controller`
[11:21] <naturalblue> during pxe boot, after i ask to bootstrap a new controller, maas rolls the OS, then juju starts the deploy of the controller. Watching the console its installing but suddenly i see a cloud-init script that references the old ip address of maas and the system shutsdown
[11:22] <naturalblue> the ip in `sudo dpkg-reconfigure maas-region-controller maas-rack-controller` was incorrect, it was the old one
[11:23] <naturalblue> i didnt realise i had to run that after chaning the ip from the maas web ui and rebooting
[11:25] <naturalblue> its asking for the api address now on the dpkg-reconfigure. Do i put in thr port of 5240 or is that just for the web gui
[11:56] <BlackDex> 5240
[11:56] <BlackDex> that is the API port
[11:56] <BlackDex> port 80 wil be deprecated in 2.4 or 2.5 if i'm correct
[11:57] <BlackDex> yea, you can change those in a file somewhere, but this is better, and it restart the services needed after :)
[12:02] <rick_h_> naturalblue: it might be in the cache for the cloud in .local/share/juju/clouds.yaml
[12:14] <naturalblue> BlackDex: rick_h_ : Thanks
[12:15] <manadart> stickupkid: Are you in any position to push your changes that further strangle out rawProvider?
[12:16] <manadart> stickupkid: I am having rewrite provider tests and it makes no sense to be stubbing/mocking out changes to something we are ditching.
[12:17] <magicaltrout> anyone know why if i try and deploy to a machine into an lxd container
[12:17] <magicaltrout> it sets my resolv.conf seemingly incorrectly and the charm fails to apt update?
[12:17] <rick_h_> magicaltrout: bionic?
[12:17] <rick_h_> magicaltrout: there was a bug around that for bionic I know that was worked on and a fix landed
[12:18] <magicaltrout> the controller is on bionic the machines are xenial
[12:18] <rick_h_> magicaltrout: https://bugs.launchpad.net/juju/+bug/1764317
[12:18] <mup> Bug #1764317: bionic LXD containers on bionic hosts get incorrect /etc/resolve.conf files <bionic> <cdo-qa> <cdo-qa-blocker> <foundations-engine> <kvm> <lxd> <network> <uosci> <juju:Fix Committed by ecjones> <juju 2.3:Fix Released by ecjones> <https://launchpad.net/bugs/1764317>
[12:29] <enrico_> Hello, I am trying to deploy a service with juju. I want to deploy it inside an lxd container. Till now ok. But I want to add 2 NIC, how can I do?
[12:43] <stickupkid> manadart: i can do, but it's broken a few things... let me just fix what i've got so you can at least see what i've done
[12:56] <stickupkid> manadart: this is a very much work in progress - https://github.com/juju/juju/compare/develop...SimonRichardson:lxd-schema?expand=1
[12:56] <stickupkid> manadart: i'm in the middle of refactoring the tests, before I get to the construction of the provider - although I may change my mind whilst I'm writing the tests
[13:06] <manadart> stickupkid: Ta.
[14:24] <naturalblue> when i try to install juju gui with juju upgrade-gui i get this "ERROR cannot upgrade to most recent release: cannot retrieve Juju GUI archive info: error fetching simplestreams metadata: invalid URL "https://streams.canonical.com/juju/gui/streams/v1/index.sjson" not found"
[14:25] <naturalblue> ^^but i have tried a wget and can retrieve the file from both the client and the controller
[14:30] <naturalblue> ^^ please ignore this. turns out i had a proxy variable in /etc/environment which get reapplied on a reboot. removed now and variables unset.
[15:34] <Guest53> Hi I just booted three ceph osd that were shutdown.  One came up fine but the other two say they are stuck in upgrading.  The log message I am getting is DEBUG config-changed Error ENOENT: error obtaining osd_hostname_luminous_start.
[15:34] <Guest53> Any idea where this luminous start file is located?
[16:07] <acss> Anyone know why I would see the following in a juju ceph-osd unit log? 2018-06-21 16:03:06 INFO juju-log Monitor config-key get failed with message: b''
[16:07] <rick_h_> acss: hmm, some sort of unexpected config value the charm couldn't parse?
[16:08] <acss> This would be based on my ceph.conf file?
[16:30] <acss> I am confused because I have another OSD functioning fine with the same charm configuration.
[16:43] <rick_h_> acss: sorry, ran for lunch stuff. So this is the juju config
[16:43] <rick_h_> acss: so you can see what you've got with juju config ceph-osd
[16:43] <acss> okay
[16:44] <acss> where is this located?
[16:47] <rick_h_> acss: so it's the config juju is told to send to the charms and changes to that config triggers the charm's config-changed event which then causes it to evaluate things and update any local files/apis/settings that need updating for the software in question
[16:47] <acss> okay thank you
[21:23] <sfeole> hello all... we have bootstrapped a controller out on AWS cloud and deployed rabbitmq, juju status displays the internal cloud IP address.   However, i want to query rabbitmq via the assigned floating ip address, will juju correctly translate/route  floatingip -> internal cloud ip?
[21:32] <rick_h_> sfeole: so you need to expose the rabbit unit for the floating IP to be the one to work since by default the firewall won't allow any traffic to it
[21:32] <sfeole> patriciadomin, ^^
[21:33] <sfeole> rick_h_, so just,  juju expose <unit>   ?
[21:33] <rick_h_> sfeole: juju expose rabbitmq or whatever the application name is
[21:33] <rick_h_> sfeole: that'll set the firewall rules as long as the charm is setup to expose the rabbit port
[21:33] <sfeole> rick_h_, ok thanks,
[21:33] <sfeole> patriciadomin, ^^
[21:36] <patriciadomin> rick_h_ sfeole thx