[04:20] <timrc> Wow one super annoying side effect of putting every hook into one file and then symlinking is if there is an error... you potentially have to "resolve" a lot of failed states if you're not careful where you put things
[05:02] <bradm> anyone about who knows about the swift-storage charms?
[09:14] <JoshStrobl> Hey guys, I have a question regarding Juju charm development. I am currently developing a charm that pulls down my open source database system, which is PHP-based and only requires an HTTP server like nginx / apache. Is it correct that I'd only need to define a single "requires" of website: interface: http (which is set to optional since it merely puts the database in the root of the http server, such as /var/www/). Would it be
[09:14] <JoshStrobl> correct that the relation hooks should be website-relation-*, even if they are optional.
[09:24] <stefano-palazzo> Hi guys! The wiki links on this page are down: http://www.ubuntu.com/download/cloud/install-ubuntu-cloud (under "real-world deployment")
[10:21] <jcastro> stefano-palazzo, heya, if you can file a bug on lp:ubuntu-website I'll make sure someone sees it
[10:23] <stefano-palazzo> will do
[10:28] <stefano-palazzo> https://bugs.launchpad.net/ubuntu-website/+bug/1276996
[10:28] <_mup_> Bug #1276996: Dead links to wiki pages on OpenStack into page <maas> <openstack> <Ubuntu Website:New> <https://launchpad.net/bugs/1276996>
[10:29] <stefano-palazzo> looks like a couple of them went bad when maas.ubuntu.com was set up. no big deal, the information's still there
[12:03] <stub> juju-test.conductor.01_lint.test DEBUG   : Running 01_lint.test (tests/01_lint.test)
[12:03] <stub> make: *** [lint] Error 1
[12:03] <stub> juju-test.conductor.01_lint.test DEBUG   : Got exit code: 2
[12:03] <stub> juju-test.conductor.01_lint.test RESULT  : ✘
[12:03] <stub> oh, foot gun. Its quiet cause I told it to me.
[12:11] <stefano-palazzo> thanks jorge
[12:20] <stub> When a local environment is destroyed, ~/.juju/environments/foo.jenv should be removed, yes?
[12:22] <stub> Hmm... I think juju test is swallowing my stdout if I have stderr
[12:28] <marcoceppi> stub: it is, there's a bug about jenv not being removed
[12:28] <marcoceppi> stub: try running juju test with -v flag
[12:28] <marcoceppi> JoshStrobl: you want to provide an http interface for the website realtion
[12:29] <stub> marcoceppi: ta, I thought that was the problem but hadn't been  able to engineer a repeatable failure yet.
[12:29] <marcoceppi> JoshStrobl: the charm should then insall nginx, apapche, whatever it needs to run the php codd
[12:29] <marcoceppi> timrc: yeah, a better pattern is to put all the methods in a file, then stub them in each hook file
[12:30] <JoshStrobl> marcoceppi: Yea, figured http interface for website relation. My install script already does proper dependency checking as well :) I'm just wondering if I need to provide the website-relation-* hooks, since the website is considered optional and nothing technically ties into the charm *yet*.
[12:31] <stub> marcoceppi: Do you know if tests in the tests directory are supposed to run as root, or an unprivileged user? I thought root, but saw one MP with 'sudo apt-get-install' lines, so am unsure.
[12:32] <JoshStrobl> marcoceppi: The Charm is primarily meant for easier deployment of the system, though I intend in the future of having services that tie into it.
[12:33] <marcoceppi> stub: the tests will be run by a user with at least sudo access
[12:33] <stub> ta
[12:33] <marcoceppi> JoshStrobl: all you reall need is a website-relation-joined hook with one line to make it tie in to other charms
[12:34] <JoshStrobl> marcoceppi: Thanks for your help. I do appreciate it =)
[12:34] <marcoceppi> JoshStrobl: here's an example: https://bazaar.launchpad.net/~charmers/charms/precise/wordpress/trunk/view/head:/hooks/website-relation-joined
[12:35] <JoshStrobl> Yea I've been looking at the website-relation-joined of Wordpress :) Just was doing it via the Juju Charms website.
[12:35] <marcoceppi> replace port with whichever port you have the webserver running on
[12:36] <JoshStrobl> marcoceppi: It'll still be port 8080 since the system directly ties into an nginx or apache install, so doesn't really look like I have to change much at all.
[15:07] <stefano-palazzo> I'm trying to set up a juju box with the null provider. bootstrapping works fine, but add-machine gives me this error:
[15:07] <stefano-palazzo> ERROR Get http://cloud:8040/provider-state: dial tcp 10.15.124.116:8040: connection refused
[15:08] <stefano-palazzo> anybody know what that's about?
[16:14] <cjohnston> When deploying with juju... should I be getting one security group per machine deployed?
[16:24] <marcoceppi> cjohnston: that sounds about right
[16:24] <marcoceppi> well, about "right"
[16:24] <cjohnston> marcoceppi: its killing me :-(
[16:24] <sarnold> (I'd guess one per service instead, but ti's a guess..)
[16:25] <cjohnston> either way.. it makes life miserable
[16:25] <marcoceppi> sarnold: you get one per unit, then one per service
[16:25] <marcoceppi> cjohnston: one per service group makes "more" sense
[16:25] <marcoceppi> they're going to be working on fixing that, are you on hp cloud cjohnston?
[16:26] <cjohnston> marcoceppi: yup
[16:26] <marcoceppi> cjohnston: just join live help, ask for 100 sec groups
[16:26] <marcoceppi> and then ask for like 100 machines
[16:26] <marcoceppi> and they'll just do it (tm)
[16:26] <marcoceppi> that's how I got around that problem
[16:26] <cjohnston> ta marcoceppi
[16:28] <sarnold> marcoceppi: ah, that makes sense
[16:28] <marcoceppi> sarnold: well, one per service should be sufficent, since you shouldn't have units doing different things
[16:29] <marcoceppi> it's a bit of overkill to have so many sec groups
[17:47] <vila_> marcoceppi: related to hp secgroups, https://bugs.launchpad.net/juju/+bug/1027641 , it's said there to use 'firewall-mode: global', will my current 'juju bootstrap' node take that into account or should I destroy/bootstrap again ?
[17:47] <_mup_> Bug #1027641: assigning a unique security group to each machine uses up security group quotas in HPCloud (openstack) <pyjuju:Triaged> <juju-core:Fix Released by niemeyer> <https://launchpad.net/bugs/1027641>
[17:56] <marcoceppi> vila_: firewall-mode global does work, but you have to re-bootstrap
[18:00] <vila_> marcoceppi: thanks !