[00:08] bac: you around? [00:11] tvansteenburgh: what's up? Anything I can help with? [00:13] nah, not really. i just discovered that he broke something in charm-tools :P [00:13] doh [00:13] :) [00:13] but i'm just gonna fix it since he's not around [00:13] no worries [00:13] cool thanks === revagomes is now known as mGraf === mGraf is now known as revagomes === revagomes is now known as mGraf === mGraf is now known as revagomes === revagomes is now known as mGraf === sebas5384 is now known as _sEBAs_ === mGraf is now known as revagomes === revagomes is now known as xauz === xauz is now known as revagomes === _sEBAs_ is now known as sebas5384 === sebas5384 is now known as _sEBAs_ === _sEBAs_ is now known as sebas5384 === CyberJacob|Away is now known as CyberJacob === vladk|offline is now known as vladk === vladk is now known as vladk|offline === CyberJacob is now known as CyberJacob|Away [08:21] <_mup_> Bug #1320135 was filed: No way to configure the archive mirror === ev_ is now known as ev === vladk|offline is now known as vladk [09:16] Anyone around who can help me a little with a local devel version of a charm which isn’t picked up by juju (??) [09:36] zchander: i can (try to ) help [09:55] davecheney: The problem I got, is that any changes I make to my (devel) local config.yaml isn’t picked up when I deploy the charm (using the command juju deploy --repository=/home/madmin/charms/devel local:owncloud --to=6) [10:02] I just got a reply through the list. Seems the problem was/is with the versions I got in my repo (both named owncloud in the metadata.yaml). I am testing this now [10:02] It seems that was the problem…. [10:02] But the test/deploy is still running [11:29] zchander: that is probably the problem. Juju should throw an ambiguous error when more than one version of the charm is loaded via metadata.yaml [11:30] Got it working….. The reason I mentioned before (two different versions of the same charm, though different named (folder)) [11:30] Also got the Ceph relation working again, including MySQL ;) [11:30] * zchander is going to get some teachers happy [11:36] \o/ [12:06] marcoceppi: Is any information available to format e.g. metadata.yaml and config.yaml? I am trying to tidy the docs… [12:06] zchander: what do you mean to format? [12:27] marcoceppi: I want to add some newlines, but it won’t render properly…. [12:34] zchander: can you paste what you've got? [12:36] http://paste.ubuntu.com/7472808/ [12:37] Also for the config.yaml, I would like to make proper formatted descriptions [12:41] hmm... seems a bit over the top being placed in the description like that. [12:46] lazyPower: I know…. ;) But it is for my own testing (and this way I get to know the proper way to create the documentation) [12:46] zchander: something like that is better served in the README. The description is more for the front facing display in the charm store. [12:54] I’ll put it in the README. [12:54] What is a charm with a proper metadata I can refer to? [13:03] zchander: Postgres [13:04] its got a really well formed charm structure, metadata, etc. [13:07] I’ll have a look at it, tonight [13:17] lazyPower, aws-specific things are ok in charms, we prefer they be labelled clearly [13:18] so like "aws-loadbalancer" for example would be ok [13:18] jcastro: thing is, its a voilation of the tenants of the charm store. so its not "ok" in the charm store's current guidelines. [13:18] what we don't want is something that claims to be generic to have cloud specific bits, so like "haproxy" === ted is now known as tedg [13:18] and this is very much cloud specific to aws, openstack - as it won't work on azure / maas [13:18] it's a should [13:18] not a must [13:19] hmmm [13:19] charms "should make use of apparmor" too, but we don't reject if they don't [13:19] marcoceppi: i followed your lead here, i need backup. am I being too picky? [13:19] we should certainly clear it up [13:20] jcastro: i'm not opposed to the idea that i'm making a mistake, but i'd like clarification on if i'm nacking a charm that would otherwise be included but lower ratings because of it. [13:21] yeah [13:21] lazyPower: tldr? [13:21] marcoceppi: charm uses aws/openstack metadata ip hard coded in teh charm [13:21] marcoceppi, cloud specific charm features [13:21] i nacked it [13:21] is it ok to ack with lowr rating, or nack it and say "fix it"? [13:22] https://bugs.launchpad.net/charms/+bug/1259630 [13:22] <_mup_> Bug #1259630: add storage subordinate charm [13:22] I only noticed because I saw Kapil's comment scroll by [13:23] jcastro: the problem I have with acking provider specific charms is its not really apparent that this charm would only work on those 2 substrates. so some guy deploys this on his private maas cloud, and assumes this setup will work [13:23] lazyPower: well, that fails charm proof [13:23] marcoceppi: beg pardon? all i get is I fails stop/start hook [13:24] lazyPower, right, so in this case I think it's a naming issue [13:24] which si safe to ignore, but it's also got this hoks.d thing [13:24] er storageprovider.d [13:24] so like, this is really "s3-storage", not "storage" [13:24] * marcoceppi remembers why he punted on this review now [13:25] jcastro: not even, more like aws|openstack-block-storage [13:25] jcastro: ^ [13:25] sure [13:25] i was just typing that out. [13:25] either way, it's not generic "storage" at this time [13:25] jcastro: right, the only way to do that is in core [13:25] and that's, as Kapil mentioned, months away [13:25] lazyPower: well, charm testing will reveal that this doesn't work on X Y and Z cloud [13:25] right [13:25] if that was hooked up to the charm store [13:26] I think if we describe it properly, people will realize that [13:26] if the readme doesn't CLEARLY call out that it only works on X clouds, that's the only issue [13:26] right [13:26] Generic storage charm subordinate. Intended to aid in making charms [13:26] easier to interface with external storage solutions without having [13:26] to speak and understand each type. Presents a single mount point on [13:26] the unit, and communicates that back to your service through the data [13:26] relation. [13:26] I think "cloud-storage" might be a more apt name [13:26] as maas and local aren't a real cloud, though that does cut azure out [13:26] right, with clear limitations described in the description and readme [13:27] storage, I agree, is too all encompasing, unless then plan on adding azure, joyent, etc in future releases of the charm [13:27] yep [13:27] actually, maybe storage is okay [13:27] * marcoceppi reviews the charm [13:27] if you read that description I just pasted it makes it sound all encompassing [13:28] jcastro: right, so it has this storagebroker.d directory in hooks, that allows you to select different broker methods [13:28] should be something like "This subordinate charm uses the AWS metadata server, which currently is supported by X, Y, and Z. Local and A,B,C are currently not support" [13:28] there's a block-storage-broker, which is the aws/openstaack stuff. then local and nfs [13:29] which would work in a cloud agnostic environment [13:29] what does it default to? [13:29] I'm inclined to recind some of what I said earlier, this is an interesting attempt at making a plugin based charm [13:29] local [13:30] * marcoceppi goes to find what the heck that means [13:30] well thing is [13:30] hey so out of the box it'll work on every substrate? [13:30] the storage broker is whats supposed to be doing the communication with the aws storage services [13:30] asciishrug.tiff [13:30] teh rest of that data comes in over the wire [13:30] i'm wondering if the storage sub didn't get the update [13:30] lazyPower jcastro I'd nack this soley on the fact they don't seem to document each of the providers [13:31] a charm this monumental in undertaking needs more than 53 lines of readme [13:31] I'm 5 mins in to poking and I still can't figure out what's going on [13:31] marcoceppi, I'm not forming an opinion on the charm itself, doing a normal review of that is fine [13:31] I think we should just clarify what we mean by cloud-specific features in policy [13:31] I thought this was a nack or ack [13:31] jcastro: ah [13:31] well, we currently don't have any cloud-specific charms in the store [13:32] all of Kapil's AWS specific stuff is still personal namespaced [13:32] sure [13:32] so there's not precedence for this yet [13:32] so like, I think they should be fine, as long as it's obvious [13:32] and we'd be potentially making one with this charm [13:32] so if I do "aws-blueshift-workload-thing", that should be fine [13:32] I'm inclined to agree, esp. with testing being the true revealer of "does this work on X substrate" [13:32] right [13:33] -name works great when it's for one cloud [13:33] this is potentially n clouds where n is < substrates [13:33] ok, I'll propose to list. [13:33] jcastro: yeah, lets move the discussion there [13:33] the policy bullet is somewhat ambiguous [13:34] i put it in the review [13:34] lazyPower, I'll also post the new trusty vagrant juju boxes [13:34] teh verbatim bullet [13:34] but let's stick to precise for today [13:34] jcastro: did those get pushed? [13:34] awesome! [13:35] yeah yesterday [13:35] i have the precise box up right now [13:35] i'm going to release a github repo with the workflow items in it for people to clone and quickstart [13:35] lazyPower, link to my mailing list post for your review [13:35] ack [13:38] oh nice you mailed the list about it yesterday. hi5 jcastro [13:43] good morning :) [13:43] hmm [13:43] Morning sebas5384 [13:43] marcoceppi, any idea why https://code.launchpad.net/~jose/charms/precise/owncloud/port-change+repo+ssl-support/+merge/215527 is not in the review queue? [13:44] ben is working in the vagrant box for juju with trusty [13:44] jcastro: its listed as needs fixing by mbruzek [13:44] jcastro: it's not assigned to charmers [13:44] if it needs to be in the rev q, it needs the "request a review" button clicked [13:44] someone knows if there is a repository of the vagrantfile? [13:44] marcoceppi, oh I see, charmers is merely subscribed [13:44] that kind of sucks doesn't it? [13:44] jcastro: mbruzek gave the wrong canned message for the re-review [13:44] because I have one, and i would like to help :) [13:44] jcastro: yes [13:45] sebas5384, you want to talk to lazyPower [13:45] nice! [13:45] sebas5384, I was just about to post the address to the trusty boxes [13:45] sebas5384: the vagrantfile is very barebones. the vagrant image itself has a cloudinit package that sets up the environment. [13:45] marcoceppi, Did I? we talking about the owncloud charm? [13:45] yeah owncloud ssl [13:46] marcoceppi, I see now, sorry about that [13:47] marcoceppi, So if a MP has tests and they don't pass it is OK to ack it? [13:47] we should shove them in juju/vagrant on github or something [13:47] lazyPower: today the box use an externals python scripts [13:47] having to install bzr and cloning some scripts [13:48] mbruzek: only if the tests failed before the mp [13:48] mbruzek, he updated the branches after from what I can see [13:48] ack [13:48] no idea if it passes tests now though [13:48] because marco hasn't fixed the world yet. [13:48] come on marco, I want test results on the internet! [13:49] lazyPower: so that means there is code from other places being used into the box, and that difficult the collaboration :) [13:49] sebas5384: you're hitting me at literally the first corner i've turned with this process. up until now, the vagrant building process has lived witho ur cpc team [13:49] lazyPower: but hey, it's just an ideia [13:49] sebas5384: so i dont have an answer for you yet [13:49] i'm gonna need you to calm down :P [13:49] CURB YOUR ENTHUSIASM SEBAS!! [13:50] and i'll follow up with you when i have a better picture of whats where and how i can expose this to community contributors [13:50] sebas5384: DON'T LISTEN TO LAZYPOWER, UNCURB THE ENTHUSIASM [13:50] :D [13:50] marcoceppi: i'll push you :| [13:50] lazyPower: i don't understand what you mean, i'm not hiting you at all hehe [13:50] just push it somewhere dude [13:50] actually [13:50] let's do this [13:50] i think you guys are missing what i'm saying [13:50] let's do that after the charm school [13:51] and a) i'm already working on a github repo to go WITH the charm school today [13:51] lazyPower: calm down :) take a big breath :) [13:51] b) the vagrant file doesn't control much at present, just which box to use [13:52] sebas5384, http://cloud-images.ubuntu.com/vagrant/trusty/current/ [13:52] jcastro: nice! [13:53] mbruzek, tedg is being a squeaky wheel wrt to ssl support, so if you've got time to review that that would be <3 [13:53] * tedg squeaks [13:53] on it. [13:54] mbruzek, Thank you! [13:54] mbruzek: i rereleased tests, its close but still doesnt pass when being run through the test harness. [13:54] and they have not been merged yet afaik [13:55] lazyPower, They were your tests? [13:56] mbruzek: according to the bzr history yes - and they passed at one point. [13:58] which is why i started refactoring, because they do not pass now [13:58] either the test infrastructure has changed, or we encountered a 'this shouldnt work but does' situation. [14:27] Incoming! https://github.com/juju/docs/pull/102 [14:29] jcastro: 1 comment, otherwise LGTM [14:29] fixed and pushed [14:30] jose are you out there [14:30] lazyPower: sorry man, sniped that merge === vladk is now known as vladk|offline [14:39] you sniper, you [14:44] lazyPower: hey, updated the storage readme. thanks for the review, let me know what you think. [14:45] dpb1: pulling it up now, thanks for the quick turn around [14:48] lazyPower: np! write back on the review, if you have more feedback. I'll be AFK for today. [14:48] dpb1: ack. Should be good though. The hooks looked good when i looked through it, the big thing was the conversation that started with the metadata url [14:59] dpb1: perfect. === vladk|offline is now known as vladk === vladk is now known as vladk|offline === tedg is now known as ted === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === roadmr is now known as roadmr_afk [17:18] someone haves a guide of how to use ansible into a juju charm? [17:19] i sow that I need to download some tools for the charm to work [17:19] https://github.com/absoludity/charm-bootstrap-ansible [17:20] sebas5384, I used this charm as an example w/ ansible [17:20] whit: didn't know! what charm? [17:21] woops -> http://bazaar.launchpad.net/~michael.nelson/charms/precise/elasticsearch/trunk/view/head:/hooks/hooks.py [17:21] sebas5384, charmhelpers grabs ansible and installs it on the remote machine [17:22] ala charmhelpers.contrib.ansible.install_ansible_support [17:22] whit: exactly! [17:22] so i have to install charm-tools before [17:23] sebas5384: charm-helpers needs to be embeded in the charm [17:23] whit: elasticsearch, sweet! [17:23] helpers and tools are two distinctly different things [17:24] gotcha marcoceppi, because helpers is things that helps the charm, and tools are for the charmer [17:25] or something like that hehe [17:25] sebas5384: exactly that [17:25] :D [17:25] :D [17:25] i'm starting to develop the drupal charm in ansible :) [17:25] ah nice [17:26] yeah! I loved ansible [17:26] and that would be to help me to prove a concept [17:26] then start develop the charm factory :) [17:27] sebas5384, ansible great for this sort of stuff because it's fairly conscise and makes idempotency easy [17:27] whit: exactly!! [17:28] and reusable role are great to extend a charm [17:28] but something I was thinking about [17:47] ops, im back :P [17:47] let say i have a drupal charm, and for now attends what the project needs [17:47] but [17:47] now we have a new library dependency, and other things like that [17:48] so now, i have to "clone" the charm and called "nameOfTheProject" [17:49] but thats not nice, because now i have duplicated code, etc... [17:49] and now i have to maintain 2 codes [17:50] so, thats why i'm going forward to the ansible, so then, i can just update the ansible role [17:52] marcoceppi: what do you say, whats your advice to that case? [17:52] when i need to "extend" a charm, to attend the project needs [17:52] :) [17:53] sebas5384: you can use a subordinate charm [17:55] marcoceppi: so i would have a subordinate charm called with the name of the project, something like that? [17:55] sebas5384: well you can have a "drupal-project" subordinate, that would just install the themes, plugins, files, etc in the right place, create it's own apache configuration, etc [17:56] hummm [17:56] marcoceppi: interesting [17:57] but I have to deploy it --to the same machine, or subordinated charms executes all into the related charm? [17:58] https://juju.ubuntu.com/docs/authors-subordinate-services.html reading... [17:59] sebas5384: subordinates don't use --to, they only exist to co-exist on a service [18:00] oohhh [18:00] marcoceppi: gotcha [18:01] marcoceppi: thanks! I will look at it :) === CyberJacob|Away is now known as CyberJacob === roadmr_afk is now known as roadmr === vladk|offline is now known as vladk [18:49] "Juju Charm School Vagrant Workflow" starting in 10 minutes https://www.youtube.com/watch?v=qLNPn2rQynM === cff is now known as CodePulsar [18:51] jose, ping === revagomes is now known as mGraf === mGraf is now known as revagomes [18:56] yeahh!! \o/ [18:57] 3 minute warning! [18:57] https://www.youtube.com/watch?v=qLNPn2rQynM [19:03] CHARM SCHOOL! TUBULAR! [19:04] jcastro what's up [19:05] nm I figured it out! [19:05] np [19:05] Did the video stop for anyone else? [19:05] no [19:05] cory_fu: not i [19:05] nm, back [19:05] seems fine for me [19:05] i called youtube and asked them to stop it for cory_fu only [19:05] Also, is there any way in ubuntu to keep a video full screen on one monitor while typing in the second monitor? [19:06] :-) [19:06] tvansteenburgh: Jerk. :) [19:06] cory_fu: yes, there should be a way [19:06] sorry I couldnt help, I'm still trapped at university [19:07] lazyPower: it'd be cool if vagrant init just did that for you, re box_url [19:09] is it working like docker? [19:10] sysdrum: similar, vagrant uses different backends (VirtualBox, kvm, vmware) so it's not limited to just linux since docker seems to be only LXC [19:11] https://github.com/chuckbutler/juju-vagrant-charmschool [19:11] yeah i'm waiting, default: Warning: Connection timeout. Retrying... [19:12] jcastro: question: does it take this long to boot the vm everytime I do 'vagrant up' or just the first time it's provisioned? [19:13] tvansteenburgh: no, thats only the first time [19:14] tvansteenburgh: after that you can use just 'vagrant suspend' for example [19:14] but, here, gives me a timeout exceeded to boot [19:14] so im going to try again [19:16] mine took a bit Retrying with the remote connection [19:16] but eventually continued [19:17] lazyPower: mediawiki is spelled wrong [19:20] QUESTION: Would I be able to manage it from a remote windows clients if I spin it up on another windows host? [19:29] http://www.vagrantup.com/blog/feature-preview-vagrant-1-5-share.html [19:30] Do I have the ability to bridge the network? under VBox? [19:33] \o/ thanks jcastro and lazyPower! === roadmr is now known as roadmr_afk [19:36] was about to ask that. [19:38] sweet!! jcastro and lazyPower :) [19:41] jcastro: i remember that before these new vbox they where failing to connect after halting the vbox [19:41] so i assume this was fixed? === sebas538_ is now known as sebas5384 [19:42] thanks!! \o/ [19:43] Thanks for answering my questions. [19:43] sebas5384: yeah that's fixed last i checked. [19:43] sebas5384: if you have any further issues with it make sure you open a bug against it or ping me and i'll do the due dilligence [19:43] lazyPower: ohh great! nice work men :) [19:43] *man [19:44] o/ [19:44] thanks! [19:46] lazyPower, jacstro: good stuff, thanks guys! [19:46] jcastro even [19:46] omg [19:46] hey guys [19:46] http://itty-bitty-cat-4232.vagrantshare.com/ [19:47] `vagrant share` is totally awesome [19:47] I did that, logged into vagrantcloud via the CLI [19:47] and then it generated that URL [19:48] yeah! was introduced in the new version [19:49] its awesome! [20:15] sebas5384: So wrt your questions this morning about the Vagrantfile and what not [20:15] did that github repository give you what you were looking for? or was there more to that statement that we haven't covered? [20:24] mbruzek: lazypower is working on the tests [20:25] jose yeah I talked with him on that. [20:25] cool :) [20:25] also, I meant to set 443, 443 is https [20:25] jose: what i've pushed is where the tests are. [20:25] i dont have any additional cycles to devote to those atm [20:26] lazyPower: so tests are done for now? [20:26] jose: whats there is what i got mang. :| they work when being run direct but fail when run via charm test [20:26] jose, lazyPower: Since the tests did not run before the MP I can't nack it for that. [20:26] mbruzek: so we need my branch merged and subsequently Charles' branch [20:26] The owncloud needs a small fix that I found, I did not rejet on the tests. [20:27] it's stacked on mine afaik [20:27] jose, did you fix the 80 problem? [20:27] I am branching to fix it now [20:27] literally *just* turned on my PC :) [20:28] mbruzek: jose - https://code.launchpad.net/~lazypower/charms/precise/owncloud/refactor_amulet_tests [20:28] jose: i can propose this for merging into your branch and you can pick up teh torch from there [20:28] sound good? [20:28] lazyPower: sounds good to me, thank you [20:29] np - sorry i dont have a 100% golden package for you, my week kind of blew up, and next week is looking just as hectic [20:29] it's good :) [20:30] https://code.launchpad.net/~lazypower/charms/precise/owncloud/refactor_amulet_tests/+merge/219903 [20:32] ack, thanks! === roadmr_afk is now known as roadmr === vladk is now known as vladk|offline === CyberJacob is now known as CyberJacob|Away