[07:16] <wpk> rick_h_: hm, I was sure this was possible, dunno why. But now, looking at add-model help - yep, it states that you can't have multiple clouds on one controller
[11:53] <TheAbsentOne> Does the layer-index repo on github has (guaranteed) the most recent interface and charm layers?
[13:12] <stub> TheAbsentOne: That is what charm build uses to map interface:foo to a repo, so yes
[13:19] <TheAbsentOne> allright, thx stub!
[19:01] <kwmonroe> TheAbsentOne: you asked about mysql-root yesterday.  there's really not much different between mysql and mysql-root interfaces -- the latter simply does a more permissive grant.  as an example of a charm that connects to mysql, have a look here: https://github.com/juju-solutions/layer-ubuntu-devenv/blob/master/reactive/ubuntu-devenv.py#L81
[19:02] <kwmonroe> TheAbsentOne: ubuntu-devenv doesn't actually do anything with the db -- but it does print out the host, db, passwords, etc from the connection string (impl'd here btw: https://github.com/johnsca/juju-relation-mysql/blob/master/requires.py#L40)
[19:02] <ejat> anyone can assist me with this : https://paste.ubuntu.com/p/nQYZbxvj8G/
[19:06] <ejat> i think someone has file the bug here https://bugs.launchpad.net/juju/+bug/1761577
[19:06] <mup> Bug #1761577: Juju does not automatically use the correct default instance type for certain Azure data-centers <azure-provider> <cdk> <cpe-onsite> <k8s> <kubernetes> <juju:Triaged> <https://launchpad.net/bugs/1761577>
[19:09] <TheAbsentOne> hey kwmonroe thanks man! I was really confused as there is no request function for a database and I read somewhere (but I guess that was wrong) that the mysql-root interface didn't in fact create a database. Really confusing me
[19:10] <TheAbsentOne> I haven't find the time to further experiment with it but I would love to get it to work ofcourse. Hopefully tomorrow!
[19:10] <TheAbsentOne> So if I get it right, as soon as you do add-relation the charm requests a database over mysql-root, right? kwmonroe
[19:11] <TheAbsentOne> also your second link is the mysql interface right? Not the mysql-root interface?
[19:18] <kwmonroe> oh yeah TheAbsentOne!  the admin (mysql-root) interface doesn't create a db:  https://github.com/marcoceppi/charm-mysql/blob/master/hooks/db-relation-joined#L70
[19:19] <kwmonroe> that must be on purpose, but i don't remember why.  maybe it's because we want to do all mysqly things over the mysql interface, and the only time you would ever use mysql-root is for granting privs to the created user.
[19:21] <kwmonroe> TheAbsentOne: so as soon as the db-relation-joined hook fires (which happens when you add a db relation -- NOT db-admin), the db gets created on line 71 in the above link.
[19:25] <TheAbsentOne> kwmonroe: hmm it's really annoying tbh x) If I use the mysql or mysql-shared interface I can properly create a database but I end up with an user that cannot grant himself privileges so that he can access from other hosts as well. And if I use the mysql-root interface I can't properly create a database with a custom databasename. :/ I'm kinda stuck
[19:25] <TheAbsentOne> I tried running sql queries with pymysql to grant privileges to the received user (so that he could connect from other hosts) but that is not possible as he hasn't the grant option (if I understand it correctly)
[20:40] <le_g> Hi everyone !
[20:41] <le_g> I'm using juju and conjure-up for the first time and I'm trying to deploy a staging k8s cluster on aws, but it fails when I try to deploy with a "juju.errors.JujuAPIError: cannot select controller: no matching controllers found" although i've selected the saas controller on the previous step
[20:41] <le_g> Has anyone encountered such an error ?
[20:48] <TheAbsentOne> what docs did you follow le_g might be usefull information for the experts here
[21:18] <le_g> TheAbsentOne it was this : https://jujucharms.com/kubernetes-core/bundle/337
[21:26] <TheAbsentOne> le_g: and you installed with snap conjure up or juju? The problem is probably your controller that isn't bootstrapped correctly or an issue with credentials/provider
[21:30] <le_g> I tried to installed it with conjure-up
[21:30] <le_g> It seems to work when I create a controller but I should be using the saas one which would save me a useless aws machien
[21:30] <le_g> machine
[21:43] <TheAbsentOne> I'm sorry, I don't think I'm able to help you :/ I'm sure others might help you!
[21:46] <bdx> Ie_g: `juju login jaas`
[21:46] <bdx> on that machine
[21:47] <bdx> make sure you can see the jaas controller locally in `juju controllers`, then conjure-up should pick it up