=== Daviey_ is now known as Daviey === bodie_ is now known as Guest78484 [13:08] anyone know what happened to the api for logs === bodie_ is now known as Guest7331 [13:24] hazmat: it got back burnered and didn't end up landing yet [13:25] hazmat: I'm trying to recall what it got pulled to but can't recall off the top of my head [13:28] rick_h_, yeah.. not seeing in the review queue or tree.. but i remember the discussions and thought it was imminent [13:28] hazmat: yea, we were tracking it to support debug-log in the gui, but it got handed off and then that person ended up getting pulled to a higher priority [13:28] hazmat: so it was still yellow close to red on the planning spreadsheet [13:29] yeah.. looks like the latest was this mp https://code.launchpad.net/~rogpeppe/juju-core/themue-058-debug-log-api/+merge/202909 [13:30] but that implementation is broken with ha [13:30] yea, there was a lot of implementation discussions and a couple of stabs and it needed some more work is my understanding. [13:54] is there a way to copy a non core juju plugin to the deployed system? [13:54] to be made available to a charm === bodie_ is now known as Guest84660 [15:13] stokachu, not sure if you got an answer.. but no re non-core plugin [19:26] hazmat: ok thanks [19:27] stokachu, the closet thing you can get is api access ala the gui, via config or login with credentials [19:28] hazmat: ok i was trying to write a parser for charm development but couldnt think of a clean way to access the library [19:28] stokachu, if its just a binary you can totally include it in a charm or pass it via juju scp [19:29] stokachu, but that's a little different then modifying the env [19:29] hazmat: so if i wrote it in go i could pass it through with scp [19:29] stokachu, its a fairly trivial go program to validate charms.. [19:29] was trying to do a parser for a 1 file charm deployment [19:29] stokachu, you mean like a bundle archive? or [19:29] yea [19:31] stokachu, but why do you want the validation in the service/unit? [19:31] its more of a parser like install => [ names => ['nginx'] ] [19:31] translate to apt-get install .. [19:31] stokachu, deployer has a good amount of the logic for validation and checking.. i'd be game for seeing bundle archive support there... but i'm not sure we're talking about the same thing [19:32] stokachu, if you want a dsl for charms, use charm-helpers.. [19:32] stokachu, we already have ansible, salt helpers there.. [19:32] but you still have to symlink all hooks to a hooks.py file [19:33] stokachu, still not clear on the use case but bug 1009687 would cover that [19:33] <_mup_> Bug #1009687: charms should be able to provide a 'missing-hook' script [19:34] hazmat: ah ok that helps [19:34] just linked it to core as well [19:34] just didnt like the fact i had to symlink files everywhere [19:35] stokachu, so charm-helpers + missing-hook + 1 file should be close to what your saying.. [19:35] would be easy if i could alter the cloud-init as well [19:35] hazmat: yea exactly [19:35] thinking more in line of like a Dockerfile or Vagrantfile [19:36] stokachu, you need to use the api for provisioning if you want to mod cloud-init [19:36] stokachu, i do it in some of my manual provider based plugins/tools [19:36] hazmat: yea i was looking at your judo stuff [19:36] hazmat: do you have it in there? [19:36] * hazmat tries to remember judo [19:36] so long ago.. before gui and before azure.. before core.. there was ju-jitsu .. [19:37] haha i remember that [19:37] stokachu, no.. that stuff is way old and pyjuju based.. [19:37] stokachu, i'm on a plane atm.. (bandwidth bites).. but checkout add.py on github in my juju-lxc project [19:38] re using the provisioning api [19:38] you can get a script, shove it into cloudinit and tweak the rest as needed [19:38] stokachu, what's the use case? [19:39] for modifying cloudinit? [19:39] hazmat: so basically i was attempting to create a Dockerfile syntax like for one file [19:39] but required installing a few packages [19:39] and i didnt want to install the packages in an install-hook and then re-eval after the fact [19:39] stokachu, dockerfiles have no orchestration.. there basically a simple makefile.. [19:39] with snapshots for each command [19:39] yea this was for charms [19:39] rather than writing pure shellscript [19:40] stokachu, iotw.. how is this dsl going to do relations? [19:40] stokachu, use ansible [19:40] well i was attempting to do it in perl :) [19:40] just to hack at it [19:40] * hazmat holds back the lol [19:40] stokachu, what you want is already possible today using charm-helpers ansible support [19:41] single file dsl, with relation support [19:41] yea [19:41] but you still have the symlinks until that bug gets fixed right? [19:41] stokachu, yes [19:41] ok thats not so bad then [19:41] stokachu, have fun