=== vladk|offline is now known as vladk === vladk is now known as vladk|offline === vladk|offline is now known as vladk === vladk is now known as vladk|offline === CyberJacob|Away is now known as CyberJacob === CyberJacob is now known as CyberJacob|Away === alexlist` is now known as alexlist === isviridov|away is now known as isviridov [08:47] hi all, appreciate it if you have a look at this issue and help me to fix it: http://ubuntuforums.org/showthread.php?t=2228930&p=13046316#post13046316 [08:56] mhshams: that sounds like https://bugs.launchpad.net/juju-core/+bug/1308767 [08:56] <_mup_> Bug #1308767: juju client is not using the floating ip to connect to the state server

[08:56] mhshams: if you're feeling brave you can try using Juju 1.19.3 which contains the fix === vladk|offline is now known as vladk [09:38] @sparkiegeek: thanks for the information. i'll try 1.19.3 for sure. === rogpeppe1 is now known as rogpeppe === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === rbasak_ is now known as rbasak === jelmer_ is now known as jelmer === vladk is now known as vladk|offline === BradCrittenden is now known as bac === med_ is now known as Guest22673 === vladk|offline is now known as vladk [13:29] noodles775: I've push my latest code for juju-ansible-role if you want to check: https://github.com/avoine/charm-ansible-roles === tvansteenburgh1 is now known as tvansteenburgh [13:30] I still need to migrate it to use your wsgi-app [13:31] avoine: Excellent, thanks. I'll probably not get a chance to look through the diff today, but will do after the session (hopefully tomorrow). [13:31] great [13:32] avoine: slides for the session here if you want to browse through - http://goo.gl/iewo1m [13:32] noodles775: ok, I'll check that out. I've got tons of questions and comments for the session :-) [13:33] avoine: great, as someone who's been using ansible for charms, it'd be great if you can join the hangout too. [13:33] noodles775: sure [13:42] gnuoy, a +1 on https://code.launchpad.net/~james-page/charms/trusty/openstack-dashboard/login-url-stable/+merge/221700 would be good if you have 5 mins [13:43] looking [13:44] jamespage, +1'd [13:44] jcastro, jose or marcoceppi: do one of you guys setup the hangout for me, or is it something I do myself? http://summit.ubuntu.com/uos-1406/meeting/22244/simpler-charms-with-ansible/ [13:45] if you set it up all I need is the hangout URL [13:45] and the youtube link it generates for you [13:45] or I can do it for you, up to you [13:48] jcastro: if it doesn't need to be linked to any special account, I can do it. If it requires me knowing a special url from which to start so it's linked to canonical, then I don't know that url. [13:49] nope, just as normal hangout on air [13:49] note, on air, not a normal hangout [13:52] want me to just do it? :) [13:53] jcastro: https://plus.google.com/events/cof2tovla6vsv84cq9d34u47b6c [13:54] noodles775, ok, I just the need the URL to the hangout, right from your browser location and I'll take care of the rest === avoine1 is now known as avoine2 [13:57] noodles775: should I use this link too? [13:59] avoine: Join #ubuntu-uds-dev [13:59] avoine: hangout url is https://plus.google.com/hangouts/_/hoaevent/AP36tYeQwxrxdZGveiZVKpetKkySfiZswgNHf5t0qJUtsowh4qjIIg?authuser=0&hl=en-GB === wwitzel3_ is now known as wwitzel3 === mbarnett` is now known as mbarnett === vladk is now known as vladk|offline === avoine is now known as patrick === patrick is now known as patrick-uds [16:09] How can I tell what juju is doing? Say I am working using the local environment and I have a slow connection to the internet, if I do a juju deploy whatever it needs to fetch an image for the instance (I can see the wget in htop), but all status tells me is the machine id is pending. [16:22] tech2: right, that fetch is only done once [16:22] then it creates a template [16:23] and subsequent deploys will clone taht templates [16:23] marcoceppi: okay, so that's a one-off time cost, that's cool, but is there a way of telling what it's up to in general? [16:23] tech2: not really, you can tail logs, and agent-state/status should show you what has just happened, but theres no real way to expose the event queue for a machine [16:24] marcoceppi: thanks again. [16:49] rick_h_: just caught up with the roadmap uds session - machine view looks really nice! [16:49] bloodearnest: :) woot [17:19] jamespage: so this juju-core SRU. If not going through every bug for SRU information, what other approach do you suggest? [17:19] An MRE applicatioN? [17:19] lazyPower, jcastro MAGIC! I just got juju-gui deployed locally with quickstart! finally :) [17:19] thanks a lot for the help [17:19] one thing worth mentioning is.. I see a bunch of WARNING messages when running juju status [17:20] like WARNING unknown config field "container" [17:20] not sure what that is, but at least I got the local provider running [17:20] * pindonga is happ(ier) :) [17:25] pindonga: awesome! [17:38] pindonga: what issue were you having? /me missed what was up. [17:39] marcoceppi: any chance you could review https://code.launchpad.net/~ubuntu-ci-engineering/charms/precise/apache2/apache-apt-update/+merge/222846 for me please [17:39] rick_h_, hi.. the issue was that I couldn't get the local provider to bootstrap and deploy things properly [17:39] pindonga: ah ok, so the GUI is behaving itself then? [17:39] yep, that was never an issue, it was juju breaking and not cleaning up itself properly [17:40] marcoceppi, omg juju kill [17:40] but with the cleanup plugin and some persistence I got around it :) [17:40] pindonga: awesome, glad you got through it [17:40] * pindonga too [17:40] * rick_h_ ducks back into the shadows until the next time someone mentions quickstart/gui [17:40] rick_h_, you're all set for the rest of the week [17:41] jcastro: now to get those releases out [17:41] jcastro: thanks for leashing me through the process there. :) [17:41] cory_fu, lazyPower: nice work churning through the queue fellas [17:42] jcastro: what are you talking about? we're not working the rev queue [17:42] we're playing broforce on steam right now [17:42] heh [17:42] oh i mean, yes, we're working feverishly on the rev q [17:46] lazyPower: any change you could pause broforce and look at https://code.launchpad.net/~davidpbritton/charms/precise/apache2/vhost-config-relation :) [17:47] dpb1: you must have ESP because i'm already looking at that one now [17:47] i'm kind of spooked about this really [17:47] lazyPower: look behind you [17:47] ahhh! [17:47] i see my cat [17:47] haha [17:53] https://plus.google.com/hangouts/_/hoaevent/AP36tYdCySsBAuEzAEONYU_JQO2lE6GNgDJyfQ2__c1KzGUX4Jc6jA?authuser=2&hl=en [17:54] marcoceppi, charm school will be there ^^^ [17:54] and anyone else who wants to be in the actual hangout [17:54] marcoceppi, 5 min warning [17:55] why did juju move to github? [17:56] mark06: increased exposure to the go-lang community? I imagine there's a number of reasons [18:00] dpb1: so we are still base64 encoding the templates with this vhost-relation extension? [18:00] yes, right. I think that is a requirement, unless there is something else preferred? [18:00] dpb1: is there a reason we are base64 encoding them vs just passing a string-blob on the wire for apache2 to parse/load/populate/deploy? [18:01] i am trying to configure the maas server so that two interfaces are configured on the server. I setup two interfaces on the cluster but the server comes up with only one. any ideas? [18:01] lazyPower: ^ [18:01] i dont think its necessarily required to be base64 encoded... i may be wrong. let me follow up with the ~charmers on this [18:01] hm [18:01] i think its added complexity that may not need to be there. becaus ehow cool would it be to just pass a heredoc or a file handle and let juju do its thing? [18:01] ok sure. I guess it would need to be encoded somehow or else the shell command (relation-set) would barf on it [18:02] thats probably why the base64 encoding came up as a requirement now that i think about it [18:02] but I haven't tried explicitly with a real template [18:02] yeah, it'll need to be escaped and all kinds of voodoo [18:03] do you ahve an example charm to use for this or do i need to codify one real quick to validate? [18:06] dpb1: ^ [18:08] lazyPower: the only one I have is in a landscape branch that is a bit hard to setup (since the code is proprietary -- as you know). It wouldn't be a good test, but you are free to look at how it implements. [18:08] lazyPower: we are waiting to submit until this one is up, since it will break without it. [18:09] lazyPower: the landscape-charm branch: lp:~davidpbritton/landscape-charm/vhost-config-relation/ [18:09] stands to reason... i'm not clear on what i'm giving the relationshiop. you call a method that makes me think its using jinja2 - template = get_template() [18:09] a great thing to have in here would be teh actual contents of an example template. even if its just plane ol yaml, it'll make it clearer and consicer than calling a ficticious method. [18:11] ah yeah, even in this example you're pulling it from unit data [18:11] ah, got it. This is basically a way to to specify 'vhost_http_template' and 'vhost_https_template' (current apache2 config settings) in a relation. But I agree, those are not doced well to begin with I guess (because they are very application specific). [18:13] so, it being in YAML format, whats the spec? vhost: {name} \n port: {port} \n access_log: {logpath} \n directory_root: {dir} ? [18:14] I think I explicitly documented that, let me check [18:15] relation-set vhosts="- {port: '443', template: dGVtcGxhdGU=}\n- {port: '80', template: dGVtcGxhdGU=}\n" [18:15] ah, i get that i was under the impression teh template itself was yaml spec [18:16] oh, no, the template is a jinja2 apache config file [18:16] so you can do {{ blah }} in the middle of it [18:16] yeah, it supports all the niceties of liquid syntax [18:16] dpb1: when you get some time, lets sync on this and clean up the apache readme a bit for new users so its more approachable. [18:17] you seem to have a lot of answers when it comes to the charm :) [18:17] lazyPower: ok. sure [18:17] lazyPower: I'm going to eat lunch, want to set up a time and we can chat? [18:17] I'm pretty booked today. Lets earmark this for post UOS? [18:19] lazyPower: ok, sounds reasonable [18:21] thanks for teh preemptive agreement. I'll try to get it on teh calendar for next week [18:24] thx === Ursinha is now known as Ursinha-afk [18:43] thanks marcoceppi === patrick-uds is now known as avoine === Ursinha-afk is now known as Ursinha [18:54] cory_fu: hi, I've addressed your comments on my reviewboard charm, ready for another round of review! [18:54] cory_fu: https://bugs.launchpad.net/charms/+bug/942032 [18:54] <_mup_> Bug #942032: Charm Needed: Review Board === roadmr is now known as roadmr_afk [18:54] Ok, I'll take a look. :) [18:55] cory_fu: cheers! [18:58] sparkiegeek: That was quick. :) I still need to test it, but it looks good. You do need to update the config option descriptions, though. [18:58] cory_fu: ah yes, the dreaded documentation ;) [18:58] I've got a meeting right now, but I'll test it shortly and add my +1 [18:58] ha === CyberJacob|Away is now known as CyberJacob [19:04] cory_fu: ok. Doc changes are made and pushed [19:04] Thanks [19:04] cory_fu: as for speed, I didn't want to end up on the wrong side of that big long review queue. Got to make the most of your attention ;) [19:12] sparkiegeek: I'm getting "no revisions to pull" [19:13] cory_fu: latest is r17... [19:13] lazyPower: hey there -- so what do I do to get that same thing merged into trusty? separate MP? how are you guys handling that? [19:14] cory_fu: my bad, r18 just pushed [19:16] Ok. Do you think it's worth documenting the semi-magic "localhost" -> public-address behavior? [19:16] dpb1: target trusty, make sure its got integration tests re: amulet or integration test method of your choosing. [19:16] cory_fu: it's in the README [19:17] So ti is [19:17] *So it is [19:18] Great. It looks perfect. I'll add my +1 and ping an official charmer (*ahem* lazyPower *ahem*) to get it promulgated shortly [19:19] promulgate: a word I only ever here from Juju people ;) [19:19] *hear [19:19] * lazyPower blinks [19:19] cory_fu: is it *good* [19:19] like *real good* ? [19:19] lazyPower: did you miss the "It looks perfect"? ;) [19:20] sparkiegeek: well... yes. i did. [19:20] I want stars, banners.... maybe even a pony? Can we juju deploy pony yet? [19:21] :) [19:21] lazyPower: ok, unit tests don't suffice? there are 0 integration tests (juju test) for apache2 right now. [19:21] afaict [19:21] unless I'm missing something (which is likely) [19:23] dpb1: wait is apaceh2 in trusty? *looks* [19:23] dpb1: ah it is! [19:23] yep, same process. Let me run a quick deploy test, if its g2g i'll ack it and merge [19:23] no need to fill out another MP. i may change my mind on the rquired MP in teh future, but today - nahhhh thats just extra busy work. [19:24] lazyPower: ok, let me know. I'll facilitate however need be [19:26] dpb1: always a pleasure working with you my man. +1 on a personal level [19:27] lazyPower: thanks! you have been great to work with as well. :) [19:36] dpb1: ack'd and pushed [19:37] thx lazyPower, much appreciated [19:37] lazyPower: does reviewboard get official blessing? Want to get in whilst the going is good :) [19:37] sparkiegeek: its up on the list, i need a few to do a review as well [19:38] lazyPower: ok. third time's the charm... or so they say :) [19:39] sparkiegeek: unless you include a pizza with attempt #2, then attempt #2 + bribery is the charm [19:39] lazyPower: fair! :) [19:40] sparkiegeek: just to be sure, i am reviewing lp:~adam-collard/charms/precise/reviewboard/trunk correct? [19:40] lazyPower: correct [19:40] ack, starting review now [19:45] sparkiegeek: nice charm! [19:46] lazyPower: why thank you :) I'd like to thank my family... [19:53] sparkiegeek: ackd, promulgated. it will be in the store shortly [19:54] Welcome to the charm store :) [19:55] lazyPower: great! thanks a lot. Between you and cory_fb (not forgetting jose) the quality of the charm greatly increased through the review process. [19:55] woohoo, congratulations sparkiegeek! [19:55] Thats our goal, with enough eyes we can squash papercuts [19:55] was a little scary to see the review queue so long, but thanks to your efforts we turned it around in only 2 days [19:56] i look forward to seeing your unit tests :) With those you'll be one step closer to a high quality mark on your charm. I've got a follow up todo after its ingested to fill out teh quality data. [19:56] lazyPower: right. Amulet tests are unfortunately, a non-starter. But unit tests are plausible (and desirable) [19:56] sparkiegeek: the review queue is kind of a fibber. it doesn't calculate based on last interaction, it reads from beginning of item - so, its quick to scatter the result. [19:57] lazyPower: top of my todo list :) [19:59] lazyPower: is there a way of subscribing to a particular charm's bugs in LP? [19:59] ah n/m found i [19:59] *it === vladk|offline is now known as vladk === roadmr_afk is now known as roadmr [20:27] sparkiegeek: ty for updating the bug to fix released, i just noticed i missed that [20:27] lazyPower: np === vladk is now known as vladk|offline === jcsackett_ is now known as jcsackett === ming is now known as Guest58318 === Beret- is now known as Beret === CyberJacob is now known as CyberJacob|Away [23:41] How to Access HBase after JUJU | http://askubuntu.com/q/482036