[00:53] <_mup_> Bug #906647 was filed: zookeeper fails to build when installing on OSX <juju:New> < https://launchpad.net/bugs/906647 >
[00:54] <_mup_> Bug #906647 was filed: zookeeper fails to build when installing on OSX <juju:New for mchenetz> < https://launchpad.net/bugs/906647 >
[07:06] <TheMue> moo
[07:54] <nijaba> meh
[09:05] <koolhead11> hi alll
[09:08] <nijaba> Hello, I have a FAILED to build on the charm-tools ppa that seems a bit odd to me: it fails on a test using wget with "wget not found" which would seem to be part of base Ubuntu install. See https://launchpadlibrarian.net/87956598/buildlog_ubuntu-natty-i386.charm-tools_0.2%2Bbzr95-4~natty1_FAILEDTOBUILD.txt.gz
[09:50] <poolie> jelmer, which part of the charm is supposed to be checked in to the branch?
[09:54] <poolie> jelmer, lp:~mbp/charm/oneiric/launchpad/trunk
[09:54] <poolie> it's not that impressive
[09:54] <poolie> i need to work out whether to just copy & paste from devscripts or somehow make it reused
[10:01] <jelmer> poolie: thanks
[10:04] <jelmer> poolie: yeah, that seems to be the sufficient bits
[10:10] <drt24> nijaba: I don't think that wget is always part of the base Ubuntu install though it does have priority standard which would imply that it would normally be installed.
[11:19] <niemeyer> Good morning!
[15:24] <SpamapS> nijaba: no, wget is not part of the base install, charm-tools needs to build-depend on wget
[15:24] <SpamapS> and I thought it did actually
[15:25] <SpamapS> nijaba: buildd's have *only* the absolute *minimal* install, + build-essential
[15:30] <SpamapS> nijaba: the reason that FTBFS was that it was using the old lp:~charmers/charm-tools/packaging bits. I re-pointed the charm-helpers-daily build to lp:ubuntu/charm-tools which has the most up to date packaging
[15:32] <SpamapS> nijaba: I'll take a look at the peer-scp stuff today
[15:33] <nijaba> SpamapS: gah... /me was going mad
[15:33] <nijaba> SpamapS: I thought it was due to the fix I merged yesterday...
[15:33]  * SpamapS considers deleting the old packaging branch to prevent further confusion
[15:34] <SpamapS> nijaba: no, its been FTBFS'ing since the first test merge. :-P
[15:36] <SpamapS> nijaba: as we add more build-deps, I'll need to merge them into the ubuntu packaging to keep the daily builds going (thats kind of the idea though.. keep packaging up to date with trunk. :)
[15:40]  * SpamapS nearly cries when he sees that he has 753 unread emails waiting for him
[15:53] <jcastro> nijaba: do we have any juju marketing flyers?
[15:53] <nijaba> jcastro: I do not think so
[15:53] <nijaba> jcastro: should ask sonia
[15:53] <jcastro> ok
[15:54] <jcastro> so like if I want to have a collection of flyers that we send to conferences we attend, I ping her for that?
[15:54] <nijaba> jcastro: no, that would be cezzaine
[15:54] <jcastro> ok
[15:54] <nijaba> jcastro: beware that she has a form for these request ;)
[15:59] <jcastro> maybe I can do them all at once
[15:59] <jcastro> and then we'll be set for the year
[16:11] <negronjl> jcastro: I usually attend a few conferences, meetings and such in the Bay Area so, if you can score some for me to distribute on my side that would be great :)
[16:16]  * jcastro nods
[16:25] <koolhead11> m_3: around
[16:34] <koolhead11>  i wanted to know if its good idea to use custom sql schema along with user created say "admin:admin"
[16:35] <jcastro> koolhead11: he should be back in a few hours
[16:35] <koolhead11> jcastro: cool.
[16:35] <jcastro> SpamapS: We should talk before the break about our scale talk (lunching now though, ping me later)
[16:35]  * koolhead11 leaves for home
[16:36] <SpamapS> jcastro: you ping me, I'll be answering email for the next few hours. :-/
[16:37] <_mup_> juju/ssh-known_hosts r449 committed by jim.baker@canonical.com
[16:37] <_mup_> Test key files
[16:52] <mchenetz> Question about the Wordpress charm… Does it have code to sync wordpress instances when you scale them? I haven't looked at the Charm yet...
[16:59] <SpamapS> mchenetz: wordpress just uses the database for all storage
[16:59] <SpamapS> mchenetz: one thing I haven't checked on is whether it uses the databse for sessioning
[16:59] <mchenetz> not exactly… The graphics and files are stored locally
[17:00] <mchenetz> That is the problem i am having right now with EC2 and multiple wordpress instances
[17:00] <mchenetz> I might have to run rsync or something
[17:01] <mchenetz> I tired to use w3 total-cache, which uploads content to S3… However it did not work reliably
[17:03] <mchenetz> Spamaps: any suggestions… You probably know a hell of a lot more than i do about this.,, Any help is much appreciated. :-)
[17:05] <SpamapS> mchenetz: I use an s3 plugin on my wordpress blog, which is why I didn't even think about that. ;)
[17:05] <mchenetz> Which one do you use?
[17:05] <SpamapS> mchenetz: for mediawiki, m_3 was working on just doing an NFS server and maybe gluster to store the uploaded images.
[17:05] <SpamapS> mchenetz: let me check
[17:05] <mchenetz> spamaps: thanks
[17:05] <SpamapS> mchenetz: http://tantannoodles.com/toolkit/wordpress-s3/
[17:06] <SpamapS> setup was pretty much a no-brainer
[17:06] <mchenetz> Spamaps: Perfect!!! Just what i needed.
[17:09] <mchenetz> The next question is advantages of using haproxy vs ELB… Currently I have them using ELB
[17:10] <SpamapS> mchenetz: there probably aren't any advantages. ELB should be cheaper
[17:10] <mchenetz> I will stick with that. ;-)
[17:10] <SpamapS> mchenetz: I believe there is an ELB charm
[17:10] <SpamapS> tho not in the official list
[17:10] <mchenetz> Really, i was just thinking about that
[17:10] <SpamapS> and not super useful since it will eat up an instance. :-/
[17:11] <mchenetz> hmmm, maybe there should be the idea of using a single instance for multiple charms… Like for administration like ELB… This way yyou could create a local provider and have it use many management charms...
[17:12] <SpamapS> I believe once subordinate services lands though, the thought was that you would just deploy an ELB "client" like charm that would use the API to add the node to the ELB. I disagree with this approach, as it exposes the AWS credentials on machines, but its at least workable.
[17:12] <mchenetz> Or maybe there should be juju, "plugins" that add management commands to the actually juju interface…
[17:14] <mchenetz> I am just thinking out loud
[17:14] <SpamapS> mchenetz: we've talked about CLI plugins yeah
[17:14] <mchenetz> Spamaps: cool
[17:14] <SpamapS> mchenetz: but in the case of ELB, it needs to be responsive to adds/removes of units.. so it feels more like a charm.
[17:15] <nijaba> mchenetz: another option would be to use ch_peer_rsync, once we can trigger relation events fron config-changed hooks
[17:15] <SpamapS> mchenetz: its just a charm that we don't want to take up space on an instance. I have suggested in the past this would be a "virtual" service that runs its hooks on the same node as ZK runs.
[17:15] <SpamapS> nijaba: in this case, you have to rsync on upload
[17:15] <mchenetz> Spamaps: That sounds like a good idea
[17:16] <nijaba> mchenetz: this would allow for any content modified on the leader to be replicated elsewhere
[17:16] <SpamapS> nijaba: there's no need for the triggering of relation events from config-changed to implement that though...
[17:16] <nijaba> SpamapS: the idea is: modifiy leader, change config param, and all goes from there
[17:16] <mchenetz> nijaba: That sounds like an interesting option. I will look into that
[17:16] <nijaba> SpamapS: yes, because ch_peer_rsync needs to be done within a relation
[17:16] <SpamapS> nijaba: you can simply cache the relation settings locally in the relation hook.
[17:17] <nijaba> SpamapS: sounds like a a lot of work for something that should be coming for free in juju in a little bit according to niemeyer
[17:18] <SpamapS> nijaba: when it lands, we can get rid of all that logic.. until it does, we can get cool things done now.
[17:18] <mchenetz> Sounds like there is some great future functionality in the pipline...
[17:18] <nijaba> SpamapS: let's get ch_peer_rsync reviewed first, I'll see on extending it then :P
[17:19] <nijaba> SpamapS: the biggest pb I have at the moment is with the test script
[17:19] <nijaba> SpamapS: you'll see that in one of 756 emals you have to read ;)
[17:19] <SpamapS> Yeah I'm digging through them
[17:20] <SpamapS> its been starred, and I've moved on to less complex emails :)
[17:20] <nijaba> hehe
[17:21] <mchenetz> Where would i find the charms that are unofficial… e.g. ELB)… I know they are not on http://charms.kapilt.com/charms
[17:21] <SpamapS> mchenetz: https://code.launchpad.net/charm
[17:21] <mchenetz> thanks
[17:25] <mchenetz> Just an FYI… The Wordpress Charm in examples that comes with Juju should be updated, because it does not include a website: association
[17:34] <nijaba> m_3: you need a review on juju-classroom?
[17:36] <jcastro> looks like owncloud hasn't had a review yet either
[17:36] <jcastro> nijaba: ok so are you a "charmer" now or do we need to get a vote from someone?
[17:37] <nijaba> jcastro: yep, I am a charmer now
[17:37] <jcastro> \o/
[17:37] <nijaba> jcastro: you want me to look at it?
[17:37] <jcastro> sure
[17:37] <jcastro> https://bugs.launchpad.net/charm/+bug/905410
[17:37] <_mup_> Bug #905410: Charm needed: Owncloud2 <new-charm> <juju Charms Collection:In Progress by koolhead17> < https://launchpad.net/bugs/905410 >
[17:38] <nijaba> jcastro: it's marked in progress, and last comment from koolhead17looks like he is working on a mysql backend
[17:39] <koolhead17> nijaba: hey there. yes. currently owncloud works with sqlite
[17:40] <nijaba> koolhead17: so, should I review it now or wait?
[17:40] <koolhead17> nijaba: it will be good if you could review it, i will consider it 1st iteration :D
[17:40] <nijaba> koolhead17: ok, doing so now
[17:40] <koolhead17> thanks
[17:41] <SpamapS> mchenetz: thats intentionaly actually... the example charms are not necessarily integratable with the lp:charm charms. they're just meant to be super simple examples.
[17:43] <jcastro> iirc I filed a bug about this
[17:43] <jcastro> imo we should just not include example charms in the packages
[17:44] <mchenetz> What about a charm repo. So it can download automagically from the cli?
[17:44] <jcastro> install charm-tools
[17:44] <mchenetz> oh, okay
[17:44] <mchenetz> I din't know it did that
[17:44] <jcastro> "charm get mysql" etc.
[17:44] <mchenetz> okay cool...
[17:45] <jcastro> yeah so hazmat is working on the charm store
[17:45] <jcastro> so you can just go
[17:45] <jcastro> juju deploy cs:mysql
[17:45] <mchenetz> awesome
[17:45] <jcastro> but charm get is our bandaid for now
[17:45] <mchenetz> works for me
[17:47] <jcastro> mchenetz: did you see Elliot's tips on the juju mailing list wrt. osx?
[17:48] <mchenetz> no, i just saw the bug report from last night
[17:49] <jcastro> https://lists.ubuntu.com/archives/juju/2011-December/001132.html
[17:49] <jcastro> see that thread
[17:49] <mchenetz> currently reading it...
[17:50] <jcastro> might be a good idea to subscribe to the list, it's not high traffic (yet)
[17:51] <mchenetz> I agree with a lot of the stuff he's saying… A single method would work good… I didn't create the test model yet… It was a first revision. ;-)
[17:52] <jcastro> mchenetz: I don't think it's a bad idea to try to see which one would work best
[17:52] <mchenetz> I would like to make it easier for people to install. Since Mac's come with easy_install, i was thinking it might be best… I do think the mac app store might be ideal though
[17:53] <mchenetz> I am still working out what the best option is...
[17:56] <mchenetz> I am looking at Elliots brew formula and i will se if i can get it to work with the current packages
[17:58] <_mup_> juju/ssh-known_hosts r450 committed by jim.baker@canonical.com
[17:58] <_mup_> Mock testing for key gen
[18:08] <nijaba> koolhead17: review of Bug #905410 done.
[18:08] <_mup_> Bug #905410: Charm needed: Owncloud2 <new-charm> <juju Charms Collection:Incomplete by koolhead17> < https://launchpad.net/bugs/905410 >
[18:09] <nijaba> koolhead17: please set the bug status back to fix comitted when you think the issues have been addressed
[18:10] <koolhead17> thanks nijaba :)
[18:21] <_mup_> Bug #907016 was filed: cannot set hardware constraints on services <juju:New> < https://launchpad.net/bugs/907016 >
[18:26] <_mup_> Bug #907019 was filed: service constraints are not used when deploying units <juju:New> < https://launchpad.net/bugs/907019 >
[18:26] <jcastro> hi ejat
[18:32] <_mup_> Bug #907024 was filed: provisioning agent ignores machine constraints <juju:New> < https://launchpad.net/bugs/907024 >
[18:44] <ejat> jcastro : hi
[18:53] <jcastro> ejat: any progress on the charms you signed up for?
[18:53] <jcastro> remember to holler if you need help with anything!
[18:55] <ejat> on progress … yes i will holler to everyone :) … since now a bit tight with daily task :(
[19:37] <mchenetz> Okay, looking at the Mac app store… It seems to be the best method. I just need to build Juju and then submit it to the app store… I will charge 1,000,000 dollars… oh hahah… Okay, i guess i will give it away free.. I will get started on it.
[19:40] <marcoceppi> mchenetz: What's the update process like for upgrading Juju?
[19:40] <marcoceppi> I might be wise to wait until the 12.04 release to put it in the mac store
[19:41] <mchenetz> i just have to submit it to the mac app store and it will allow the update
[19:44] <SpamapS> upgrading juju is an unknown :-/
[19:45] <SpamapS> I believe once we have the ability to reboot, upgrades will be more obvious, and work just like upgrading anything else.
[19:45] <mchenetz> hehe… We can wait… I will get the process started though
[19:50] <SpamapS> I think it would be great to have it in there. I'd say juju is still beta quality at best, so just mark it as such
[19:53] <mchenetz> okay, will do
[19:54] <robbiew> +1 on marking as beta
[19:54]  * robbiew swings by the channel and makes a passing comment
[19:55] <marcoceppi> I meant upgrading the app in the "store"
[19:55] <marcoceppi> When are we going to see Juju for Android :)
[20:04] <mchenetz> Android should be relatively easy as i think it supports android by default
[20:04] <mchenetz> python i meant
[20:06] <koolhead17> will it be good idea to have our own software store for the sw which is not on repository? In this way our charm will not get broken if source/sw gets moved/modified/upgraded
[20:06] <koolhead17> just a thought
[20:08] <mchenetz> I thought about that… may be a next phase
[20:09] <koolhead17> cool!! :)
[20:53] <m_3> nijaba: yes, please review juju-classroom when you get a chance.  There're additional things we can do to scale this, but it's useful as-is for demos
[20:56] <SpamapS> m_3: o/ ... just waving hi.. on my way to lunch.. ;)
[20:56] <m_3> hey man
[20:57] <m_3> yay... mup's back
[21:01]  * m_3 to the "manamanat" muppet song
[22:35] <_mup_> juju/ssh-known_hosts r451 committed by jim.baker@canonical.com
[22:35] <_mup_> Refactored mock keygen
[22:36] <_mup_> Bug #907094 was filed: AWS credentials should not be in Zookeeper <security> <juju:New> < https://launchpad.net/bugs/907094 >
[23:23] <EvilBill> mchenetz: I've still not been able to get Juju going on my Mac OS boxes
[23:24] <mchenetz> Evilbill, what issues are you having?
[23:24] <EvilBill> https://bugs.launchpad.net/juju/+bug/906647?comments=all
[23:24] <_mup_> Bug #906647: zookeeper fails to build when installing on OSX <osx> <juju:New for mchenetz> < https://launchpad.net/bugs/906647 >
[23:24] <EvilBill> That permissions issue thing
[23:25] <mchenetz> hmmm, did you try the easy_install method?
[23:25] <EvilBill> no, just pure brew.
[23:25] <mchenetz> i would try the easy install, it seems to work better
[23:25] <EvilBill> ok, will do.
[23:25] <EvilBill> thanks.
[23:25] <EvilBill> gotta run to a meeting, will try after I get out
[23:26] <mchenetz> no prob… If you have issues just hit me up here or at mchenetz (at) inventivedigital.com
[23:26] <EvilBill> Will do, thx!