[08:31] <nileshsawant> All all, we are facing issue in juju add-machine
[08:32] <nileshsawant> os deployment is marked as failed in maas
[08:32] <nileshsawant> is anyone facing this issue ?
[12:57] <tvansteenburgh> rick_h: you around?
[12:58] <rick_h> Packing what's up?
[13:00] <rick_h> tvansteenburgh: ^
[13:01] <tvansteenburgh> rick_h: juju upgrade-charm foo --config cfg.yaml ... i can't figure out what the format of cfg.yaml is supposed to be. everything i've tried so far fails
[13:01] <tvansteenburgh> rick_h: you happen to know anything about this? sorry to interrupt the packing
[13:02] <tvansteenburgh> if you don't have time, no worries-
[13:04] <rick_h> tvansteenburgh: hmm, I'd expect either a flat yaml list of config options or a root key "options" to match up with bundle format
[13:04] <rick_h> tvansteenburgh: what's not working atm?
[13:04] <tvansteenburgh> rick_h: okay, flat is what i tried first. then i tried giving it the output from `juju config foo -o cfg.yaml`
[13:05] <rick_h> tvansteenburgh: that'd make some sense :)
[13:05] <tvansteenburgh> but alas
[13:05] <tvansteenburgh> i'll just keep tinkering. looks like i know what i'm doing at the docs sprint today
[13:07] <rick_h> hah
[13:07] <rick_h> tvansteenburgh: hmm, actually. does it need the service name in it?
[13:07] <rick_h>  I'm looking atm let me see what I can find
[13:08] <tvansteenburgh> well the output of `juju config foo -o cfg.yaml` has an application key in it, but juju doesn't like that if you feed it back in
[13:08] <rick_h> k
[13:09] <rick_h> I thought I remembered seeing some config like that. I must be remembering the output there
[13:12] <rick_h> tvansteenburgh: so https://github.com/juju/juju/blob/8cb1f452f4d21e3d7d929ab0615c1a4d7b1cac42/cmd/juju/application/upgradecharm_test.go#L203 seems to imply it's just flat config
[13:13] <tvansteenburgh> hmm
[13:14] <tvansteenburgh> rick_h: mystery solved
[13:14] <rick_h> tvansteenburgh: but not finding a lot in here that gives me confidence tbh. That's the only reference to upgade-charm and config|options I can see atm.
[13:14] <tvansteenburgh> top level key has to be the app name
[13:14] <rick_h> tvansteenburgh: yay?
[13:15] <rick_h> tvansteenburgh: ugh, ok that's what I was remembering but damn that's not easy to figure out. :(
[13:15] <tvansteenburgh> yeah, i'll get something in the docs later today, thanks for the help
[13:15] <rick_h> tvansteenburgh: docs sprint is cool, but maybe update the help text for the upgrade-charm command as well?
[13:15] <tvansteenburgh> +1
[13:16] <rick_h> tvansteenburgh: I know evilnickveitch has updated them in the past and can walk through where that's edited at.
[13:22] <evilnickveitch> tvansteenburgh, https://jujucharms.com/docs/2.2/developer-upgrade-charm is probably the most relevant page, though it doesn't really mention anything about config. The implication from the juju help is that it would be in the same format as config applied during a deploy
[13:26] <tvansteenburgh> evilnickveitch: also this page https://jujucharms.com/docs/2.2/charms-config says at the bottom "you can do it with a file" but doesn't say what the format should be
[13:29] <evilnickveitch> tvansteenburgh, erm, it doea. There is an example and everything https://jujucharms.com/docs/2.2/charms-config#configuring-an-application-at-deployment
[13:29] <tvansteenburgh> wow
[13:30] <tvansteenburgh> i actually looked at this page while i was floundering around, and totally missed that :/
[13:31] <tvansteenburgh> so, never mind?
[13:32] <evilnickveitch> tvansteenburgh, well, I think there are a few takeaways. The 'upgrade-charm' stuff should link here to explain the config option, probably
[13:32] <evilnickveitch> Perhaps it could do with a longer/better example?
[13:32] <evilnickveitch> or a note that says "TIM! LOOK AT ME!"
[13:33] <tvansteenburgh> definitely the latter
[13:33] <tvansteenburgh> it was just my fault, didn't read carefully enough. i'm glad to see we have it. i think it would be useful to link the upgrade-charm docs to that example
[13:34] <evilnickveitch> +1
[13:35] <evilnickveitch> I will add some issues
[13:35] <tvansteenburgh> evilnickveitch: tyvm!
[16:25] <ryebot> where can I find the source for the relation-list tool?
[17:18] <aisrael> Hi folks, just a reminder that the next virtual docs sprint starts at the top of the hour. We'll be diving into the charms.reactive framework. https://www.youtube.com/watch?v=rS9hxsySfNA
[17:59] <aisrael> We're about to start our virtual sprint on the charms.reactive framework docs. Feel free to follow along, ask questions, open new issues, or write some docs!
[19:44] <Budgie^Smore> ok today's off the wall question... can I get a juju controller to manage multiple "clouds"? for instance is it possible to get controller to have one model on AWS and one model on bare metal using MAAS? (I know that JAAS can handle multiple public clouds based on the account credentials but not sure how that was accomplished)
[21:00] <rick_h> Budgie^Smore: no, can't do it currently
[21:01] <Budgie^Smore> rick_h: "on the roadmap"?