[02:55] <nwingfield> How can I specify in the `requires` section of metadata.yaml that a database is required, but could be one of several choices (e.g., mongodb OR postgresql OR mysql)?
[03:00] <blr> nwingfield: you would add an interface for both mysql and postgresql and mongodb but set them as `optional: true`
[03:01] <blr> nwingfield: there may be a way to require that at least one is provided, but I'm not certain
[03:01] <nwingfield> yeah, i can’t find any examples of mutually exclusive interfaces
[03:02] <nwingfield> i’ll give that a shot though
[03:06] <thumper> nwingfield: hey there, yes have all three as optional
[03:06] <blr> thanks thumper
[03:06] <thumper> but with new status work, the charm could be put into a status that says "awaiting database"
[03:06] <thumper> so anyone that goes "juju status" would see that it isn't yet running
[03:07] <thumper> this is the new 'workload status' work
[03:10] <nwingfield> that will be nice
[03:11] <nwingfield> thanks for the help blr, thumper
[08:21] <chrome0> I've got a spinning jujud here - it's dumping tons of lines with "machine X has new addresses" over and over, cf. http://paste.ubuntu.com/11644054/
[08:21] <chrome0> Anyone seen something like this?
[10:32] <schkovich> there are two manual environments running in rackspace. i have a task to move n machines from environment A to environment B. is something like that possible at all?
[13:04] <gnuoy> jamespage, if you have a moment: https://code.launchpad.net/~gnuoy/charms/trusty/percona-cluster/use-dc-stable/+merge/261372
[15:09] <Odd_Bloke> Is there a difference between 'juju-run ...' and 'sudo juju-run ...' on an instance?
[15:11] <aisrael> Odd_Bloke: I wouldn't think so, as `juju-run` runs as root already
[15:13] <Odd_Bloke> aisrael: I'm running it from a shell as not-root; does it escalate itself?
[15:13] <lazyPower> Odd_Bloke: there is one context in which juju run will run as the ubuntu user
[15:13] <lazyPower> and i beleive thats when you target --machine, vs using --service or --unit
[15:14] <lazyPower> Odd_Bloke: otherwise the context of a juju run session is executed as root, no elevation required.
[15:44] <Bialogs> Is there a way to tell Juju not to overwrite configs? I'm editing Glance config and when I reboot Glance the configs switch back to the Juju settings.
[15:45] <rick_h_> Bialogs: it's in the charm and what it does. The charm has to support non-charm related edits to the configs.
[15:46] <Bialogs> rick_h_: Thanks
[16:32] <lazyPower> hey marcoceppi, have you ever seen the juju unit commands just flat out hang?
[16:32] <lazyPower> eg: unit-get, juju-log, etc.
[16:33] <lazyPower> doesn't seem to matter which command i run, its just hanging around like its attempting to connect to the event socket and never timing out.
[16:48] <Zetas> does it initiate an ssh connection?
[17:26] <lazyPower> I'm not sure about that Zetas, but i want to say no.
[17:27] <rick_h_> lazyPower: is there a gui running? canit connect to the wss?
[17:28] <lazyPower> rick_h_: i terminated the env and stood it back up. its worth noting that this also happened after dhx'ing into the unit, and that may have made an environmental change
[17:28] <rick_h_> oh hmm, ok
[17:28] <lazyPower> so i dont necessarily think this is core related, and more something wonky happened
[17:30] <rick_h_> lazyPower: have the url for charm testing handy? It's not linked in the bug and I can't find it in the docs under charm testing or anything.
[17:31] <rick_h_> lazyPower: is that not "live" atm?
[17:31] <lazyPower> rick_h_: thats a deceptively large topic, are you looking for the amulet docs? as in "how do i test my charm"?
[17:31] <rick_h_> lazyPower: the "charm tests failed on my charm, I think I fixed them, where's that test rnuner that would prove this to be true on a reporting page" testing
[17:32] <lazyPower> ah
[17:32] <lazyPower> http://reports.vapour.ws/latest-bundle-and-charm-results
[17:32] <lazyPower> that's not linked in the docs - the individual test runs should be embedded in the bug filed for the MP/Review request
[17:33] <rick_h_> lazyPower: right, just following up on https://bugs.launchpad.net/charms/+bug/1459345 and curious if the update ran/passed tests
[17:33] <mup> Bug #1459345: Review/promulgation request for the Redis charm <Juju Charms Collection:New> <https://launchpad.net/bugs/1459345>
[17:33] <lazyPower> rick_h_: that was probably run out of band by hand by a charmer.
[17:34] <lazyPower> i do know, that the current impl of the revq is linked to an older testing project in jenkins, and we have a newer setup that's using container isolation to kick off the tests that seems more reliable.
[17:34] <rick_h_> lazyPower: ah ok. Well not much we can do then. ty
[17:34] <lazyPower> we still have an open ticket to integrate the new method, and make it a tad more self-serving to end users, eg: open MP, get automated results like osci
[17:35] <lazyPower> thats upcoming this cycle by devx aiui, but no promises. I dont manage the workload on that team :D
[17:35] <marcoceppi> lazyPower: we have more than an open ticket, there's a spec being drafted that makes CI way more robust
[17:35] <lazyPower> even. better.
[17:35] <rick_h_> hmm, juju-gui results going back to aug of last year?
[17:41] <lazyPower> rick_h_: i may have spoken too soon i was able to reproduce. Deploying the gui now
[17:41] <lazyPower> rick_h_: is there something specific to look for other than wss connectivity?
[17:41] <rick_h_> lazyPower: well if it can talk to the API but you can't from the cli it might be network issues or something
[17:42] <rick_h_> lazyPower: basically can you load up the gui, service details, unit details
[17:42] <lazyPower> ack, makes sense
[17:43] <lazyPower> yeah gui is working as expected
[17:44] <lazyPower> this is weird, if i detach and re-run the hook it works as expected.
[17:44] <lazyPower> yet when attached via debug-hooks, dhx, etc. it hangs on every unit-agent command
[17:44] <lazyPower> config-get, juju-log, unit-get
[17:44]  * lazyPower takes an env dump
[19:29] <bilal> Hi, I was looking to deploy Openstack HA with juju and MAAS. I could not find any good step by step guide and architecture guide for it. Can someone help me point to it? I will be very thankful :)
[19:52] <lazyPower> beisner: ping :) ^
[19:52] <lazyPower> o/ bilal
[19:58] <beisner> hi bilal -  the openstack charms do generally support HA use cases, however only non-HA openstack bundles (solutions) have been published thus far in the juju charm store.
[20:05] <bilal> Thanks beisner. So in order to make a charm e.g. keystone charm to work in HA usecase, what different steps do I need to do? Also do you know if maybe outside juju charm store, someone has posted HA reference architecture?
[20:13] <thumper> lazyPower: so I got the django 1.7 support tests all passing with bundletester over the weekend
[20:13] <lazyPower> GREAT SUCCESS \O/
[20:13] <thumper> lazyPower: which included one with django 1.8, which also found a bug, which is also fixed in the branch
[20:13] <lazyPower> thats awesome news thumper
[20:13] <thumper> the autocommit attribute in the postgres config was removed in 1.8
[20:14] <thumper> lazyPower: was using juju 1.24 to run the tests though, not 1.23
[20:14] <thumper> lazyPower: I have celery worker support working locally too
[20:15] <lazyPower> thumper: ok, lets land the updates to 1.7 first
[20:15] <thumper> there is a wip merge proposal up so I can track changes
[20:15] <lazyPower> then we'll get celery in a feature branch
[20:15] <thumper> lazyPower: yes, definitely
[20:15] <lazyPower> sounds awesome though, thanks for the dedication there
[20:15] <thumper> lazyPower: it needs some tests though
[20:15] <lazyPower> so does whats in teh charm store :)
[20:15] <thumper> also coming once this has landed will be moving all the feature tests to amulet
[20:15] <lazyPower> oh thank the developer, that will be great
[20:16] <lazyPower> instead of continuing the carry the pre-amulet tests forward
[20:16]  * thumper nods
[20:16] <thumper> as I mentioned before, I'd like this charm to become an example of a well written charm
[20:16] <thumper> an exemplar if you will
[20:19] <thumper> as we get workload status too, I'd like to hook this up
[20:19] <thumper> seeing the great work landing in juju master right now has me eager to use it
[20:20] <thumper> kinda hard to work out if django is fully "up" though since it is a framework charm
[20:21]  * thumper thinks...
[20:21] <thumper> lazyPower: how about this as a crazy arse idea...
[20:21] <thumper> lazyPower: we encourate a "special" url in the app
[20:21] <thumper> lazyPower: something configurable, but defaulting to something like '/.juju-status'
[20:22] <thumper> lazyPower: and use that for workload status
[20:22] <thumper> if it is configured
[20:22] <lazyPower> That doesn't seem very practical and very scoped to juju.
[20:22] <thumper> socialize juju into django apps :)
[20:22] <lazyPower> I think something along the lines of checking for the CSRF token you get out of a django site would be good
[20:22] <thumper> that doesn't tell me it is working
[20:22] <thumper> for example
[20:22] <lazyPower> it tells you the framework is responding, othewrise you'd get a 503 bad gateway error and no CSRF token in the <head> tag
[20:22] <thumper> as far as I'm concerned, django isn't working if my app isn't there
[20:23] <thumper> my app provides https endpoints
[20:23] <thumper> lazyPower: this assumes that you are using the csrf middleware (which, you should be, but don't have to)
[20:24] <thumper> lazyPower: how about this...
[20:24] <thumper> lazyPower: as config
[20:24] <thumper> lazyPower: you specify which relations are needed
[20:25] <thumper> lazyPower: if all relations are made, service is up
[20:25] <thumper> lazyPower: that way, as the charm user, I could say "up means pqsql, amqp, django-settings"
[20:26] <thumper> although ideally we'd want to be able to specify the remote side name
[20:26] <lazyPower> that sounds strikingly similar to what the services framework is using as a basis for charming
[20:26] <thumper> I'd like to be able to say "you need a django-setting relation with foo"
[20:26] <thumper> lazyPower: I know nothing about the services framework
[20:26] <lazyPower> but what you're telling me you want to do sounds mor elike a health check of the service to a) ensure its online and b) has the associated components online and in a healthy state
[20:26] <thumper> exactly, this is what workload status is
[20:26] <thumper> and it shows up in juju status
[20:27] <thumper> (or it will soon...)
[20:27] <thumper> 1.25 I think
[20:27] <lazyPower> i think this needs more brainstorming than I have capacity for at the moment, because i see your point of "my service is an amalgamation of these components, just checking 200ok is not enough"
[20:27] <lazyPower> but theres a fair amount of overlap here that may or may not be present in other apps, and other healthchecks.
[20:27]  * thumper nods
[20:28] <lazyPower> s/apps/services/
[20:28] <thumper> lazyPower: how about we schedule a chat some time this week
[20:28] <thumper> with perhaps another eco member or two
[20:28] <thumper> and just spit-ball some ideas
[20:28] <lazyPower> im booked this week in prep for DockerCon, can we do this after the conference if you need me there?
[20:28] <thumper> look, this isn't urgent, and unlikely to happen in the next two weeks
[20:28] <thumper> so we can do it after
[20:29] <thumper> I'm really just thinking out loud
[20:29] <thumper> so to speak
[20:29] <lazyPower> perfect, i dont want you to lose the enthusiasm/momentum you've got going though
[20:29] <lazyPower> so i'm willing to be flexible when its not stacking :)
[20:29] <thumper> lazyPower: unlikely, I'm using this charm in a production environment
[20:29] <thumper> and I want it to be good
[20:31] <lazyPower> sounds good, we have open office hours
[20:31] <lazyPower> and this would be brilliant to bring up during the office hours - it might be a bit early for you though
[20:32] <thumper> lazyPower: when is it?
[20:32] <lazyPower> 6  AM in Canberra ACT
[20:33] <thumper> lazyPower: good think I'm in NZ and it is 8am then
[20:33] <lazyPower> oh perfect
[20:33] <lazyPower> i had no idea so i guessed at your locale
[20:33] <lazyPower> well i knew you were a kiwi, but thats as far as that goes
[20:33] <thumper> with my wife leaving for work early, it isn't hard for me to start at 8am
[20:33] <lazyPower> ok cool, on the 18'th of this month at 8am
[20:34] <thumper> I'll pencil it in
[20:35] <thumper> lazyPower: I have to say, with all this charm dev work, it makes me want to add more to the charmhelpers and making juju better...
[20:36] <thumper> also, I have a patch for bundletester
[20:36] <lazyPower> orly?
[20:36] <thumper> but I haven't worked out how to add a test...
[20:36] <thumper> lazyPower: just upper cases the debug flag
[20:36] <lazyPower> thumper: does it change -l DEBUG to -l d ebug?
[20:36] <thumper> so it can handle 'debug'
[20:36] <lazyPower> haha
[20:36] <lazyPower> i love it
[20:36] <lazyPower> called it
[20:36] <thumper> :)
[20:38] <thumper> lazyPower: https://github.com/juju-solutions/bundletester/pull/19
[20:40] <lazyPower> thumper: commented, one of the devx peeps will give that a thorough review / merge
[20:40] <thumper> sure, np
[20:40] <beisner> hi bilal, generally, the HA needs and topologies vary quite a bit from one environment to another.   also as you note, the approach is different per service (percona-cluster vs. keystone vs. glance and such).
[20:41] <lazyPower> aisrael: 'preciate you
[20:41] <aisrael> lazyPower: Right back atcha, dude.