=== paulczar is now known as zz_paulczar === zz_paulczar is now known as paulczar === paulczar is now known as zz_paulczar === zz_paulczar is now known as paulczar === paulczar is now known as zz_paulczar === bjf[afk] is now known as bjf === CyberJacob is now known as CyberJacob|Away [01:15] marcoceppi: I know this is like a little kid asking "are we there yet?". Do you think you'll get to review my merge proposal (for etherpad-lite) today? [01:17] Azendale: if you're curious of progress, you can check the review queue out, we typically go in order top to bottom (a bunch of old stuff just showed up). http://manage.jujucharms.com/tools/review-queue [01:18] So if not tonight, then tomorrow [01:22] marcoceppi: ok, thanks. Psychologically, it's kind of like waiting for a package to to get here. :) [01:23] Azendale: :) === zz_paulczar is now known as paulczar [02:46] Just playing around with Juju. I added a mysql server. If I expose this, should I be able to connect to it from the internet? It appears that it only allows connections via relationships. [02:47] yikes, you're brave to consider exposing mysql to the world :) [02:47] sbbrtn: what environment are you running on? [02:47] aws [02:48] sbbrtn: ok, in that case I believe it would (but I haven't used AWS before, so I could be wrong) [02:48] sarnold: I wouldn't typically expose it to the outside world but just playing around [02:53] sbbrtn: I didn't see any calls to the 'open-port' juju hook in the mysql charm; I don't think you can directly expose its port by just running "juju expose mysql" [02:54] sbbrtn: (there is a defined python functio nthat run it, but I don't see it used anywhere: https://bazaar.launchpad.net/~charmers/charms/precise/mysql/trunk/view/head:/hooks/lib/utils.py#L119 ) [02:54] sarnold: ok, thanks. It wasn't opening up the port on my amazon firewall so I figured it wasn't opening.. [02:55] sarnold: how do I execute that function from the juju command prompt? juju mysql expose ? [02:58] sbbrtn: if you're just goofing around, you can juju ssh mysql/0 -- once you're logged in, you can run open-port and then connect your machine's mysql to the remote server ... [02:58] sbbrtn: I'm trying to find if there's anything you have to do once you're logged in to make the 'open-port' command "available" for you to run .. I'm having trouble finding that. :) [02:59] Ok. Thanks. I figured there might be a different option short of going in via SSH [03:00] sbbrtn: this might be the way to get there... https://juju.ubuntu.com/docs/authors-hook-debug.html [03:00] (it'll fire up ssh too. hehe. :) [03:00] sbbrtn: it -could- be; if you really wanted this, you could fork the charm and modify one of the hooks to expose the port for you [03:01] not a big deal. I'm really just playing around to see how Juju works. [03:01] thanks for the help [03:02] connecting the local mysql client to a remote hosted server would be a fun thing to see. I'd just be afraid to leave it up for very long, who knows how long it'd take before it's discovered and potentially abused. :) === paulczar is now known as zz_paulczar [03:06] yeah. I see why you wouldn't want to expose it. On my current web server I have multiple MySql instances running. One is open to the public and is a development database so not too concerned with the contents. The other two servers are only available via localhost and my VPN if I connect to it via OpenVPN. I need access to the DB since the updates are made directly to the database and that is the best way I have [03:06] found. I wonder if this is possible with Juju... [03:15] any way to kill a service after getting a hook failed? I can't bring it down with destroy-service [03:27] sbbrtn: run `juju resolved ` a few times [03:28] sbbrtn: sarnold it's odd that MySQL doesn't expose 3306. I should have that port "opened" and waiting for juju expose to be run. I'll look in to that [03:29] marcoceppi: Thanks (this is Jason955 from earlier BTW) [03:29] o/ [03:30] sbbrtn: if you could open a bug against the MySQL charm that it doesn't expose the default port, I'll have it patched https://bugs.launchpad.net/charms/+source/mysql/+bugs [03:30] marcoceppi: I dunno, I kind of like the idea that it isn't just easily exposed. it feels like every CPU from oracle includes at least one remote unauthenticated mysql attack. :( [03:30] marcoceppi: maybe a config option yes-really-expose-my-database or something? :) [03:31] sarnold: it won't be exposed unless the user really wants it to. What would be a better idea is to have the port configurable and have it use a non-standard port by default (if that was a concern) [03:31] marcoceppi: will do [03:31] marcoceppi: that'd be a help, but I wouldn't be surprised if mysql advertises itself on its port somehow.. [03:32] sbbrtn: feel free to open bugs for any other things you find odd. If you search for the charm in https://manage.jujucharms.com/ you'll find a link for "Bugs" that you can use [03:36] Azendale: Wasn't able to get to your merge tonight, but it's next on the list for tomorrow! [03:36] marcoceppi: will do. I just got my launchpad account. [03:38] marcoceppi: Awesome! [03:38] * marcoceppi heads to bed [03:38] g'night marcoceppi :) [03:42] Can I create multiple Mysql instances on different ports with Juju? === thumper is now known as thumper-afk === freeflying is now known as freeflying_away === freeflying_away is now known as freeflying === wedgwood is now known as Guest32887 [06:04] sbbrtn: possibly [06:04] but not using the same machine [06:12] There isn't a way to change the port? [06:20] sbbrtn: there might be [06:20] didn't you say you wanted to have multiple mysqls ? [06:23] Yes. I wanted one exposed to the web on a non-default port. [06:27] sbbrtn: the mysql charm doesn't currently support this, please raise a feature request, https://launchpad.net/charms/+source/mysql [06:28] will do [06:57] anyone awake that has any insight into the progress of https://bugs.launchpad.net/juju-core/+bug/1233457 [06:57] <_mup_> Bug #1233457: service with no units stuck in lifecycle dying

=== CyberJacob|Away is now known as CyberJacob === jamespage_ is now known as jamespage_ods === CyberJacob is now known as CyberJacob|Away === thumper-afk is now known as thumper === freeflying is now known as freeflying_away === freeflying_away is now known as freeflying === stokachu_ is now known as stokachu === _mup__ is now known as _mup_ === BradCrittenden is now known as bac === zz_paulczar is now known as paulczar === paulczar is now known as zz_paulczar === Guest32887 is now known as wedgwood === zz_paulczar is now known as paulczar [14:23] hey marcoceppi === paulczar is now known as zz_paulczar === zz_paulczar is now known as paulczar === paulczar is now known as zz_paulczar [16:18] hey evilnickveitch [16:18] can you index the local troubleshooting page? [16:18] I am unsure if you're making a new troubleshooting section or putting it somewhere else [16:22] jcastro, i am making a new section, but i will do it today [16:23] makes a nice change from trying to reverse engineer interfaces [16:32] heh === CyberJacob|Away is now known as CyberJacob === thumper is now known as thumper-hacking === gary_poster is now known as gary_poster|away === freeflying is now known as freeflying_away === freeflying_away is now known as freeflying === thumper-hacking is now known as thumper-gym === freeflying is now known as freeflying_away === CyberJacob is now known as CyberJacob|Away === freeflying_away is now known as freeflying