| === CyberJacob is now known as CyberJacob|Away | |
| === Mike is now known as Guest21559 | |
| === cmagina-away is now known as cmagina | |
| === cmagina is now known as cmagina-away | |
| === vladk|offline is now known as vladk | |
| [06:33] <jose> marcoceppi: hey, just as a heads up, you may want to close this bug when/if the charm is on the store: https://bugs.launchpad.net/charms/+bug/1294232 | |
| [06:33] <_mup_> Bug #1294232: Charm Needed: Magento <Juju Charms Collection:New> <https://launchpad.net/bugs/1294232> | |
| === vladk is now known as vladk|offline | |
| === psivaa_ is now known as psivaa-afk | |
| [09:12] <themonk> marcoceppi: hi | |
| [09:17] <themonk> if provider charm has only relation joined and requirer charm only relation changed will it be wrong? here provider relation joined sets variable and requirer charm gets those variables | |
| === CyberJacob|Away is now known as CyberJacob | |
| === CyberJacob is now known as CyberJacob|Away | |
| === vladk|offline is now known as vladk | |
| === CyberJacob|Away is now known as CyberJacob | |
| [11:32] <Tug> hi, I tried manual providing yesterday and it was working like a charm | |
| [11:33] <Tug> now if I try to connect to the agent machine agent (just doing juju status in fact) | |
| [11:33] <Tug> ERROR state/api: websocket.Dial wss://my.domain.com:17070/: dial tcp XXX.XXX.XXX.XXX:17070: connection refused | |
| [11:34] <Tug> s/manual providing/manual provisioning/ | |
| === CyberJacob is now known as CyberJacob|Away | |
| === vladk is now known as vladk|offline | |
| [12:55] <marcoceppi> Tug: you're using 1.16? | |
| [12:55] <Tug> nop I switch to devel :s | |
| [12:56] <marcoceppi> devel should work with manual provider. what version Ubuntu is the machine? | |
| [12:58] <Tug> the machine with the client or the agent ? | |
| [12:58] <marcoceppi> agent | |
| [12:58] <Tug> ubuntu server 12.04 | |
| [12:58] <marcoceppi> :/ | |
| [12:59] <Tug> yeah it was an experiment... | |
| [12:59] <marcoceppi> ssh in to the machine, run sudo initctl list | grep juju | |
| [12:59] <marcoceppi> so far you are doing all the right things | |
| [13:00] <Tug> I have "juju-db stop/waiting" that's no good right ? | |
| [13:00] <marcoceppi> you should have two juju jobs | |
| [13:00] <marcoceppi> so the provisioning seems incomplete | |
| [13:01] <Tug> jujud-unit-redis-master-0 start/running, process 10004 | |
| [13:01] <Tug> jujud-unit-nirror-front-0 start/running, process 10006 | |
| [13:01] <Tug> jujud-unit-nirror-proxy-0 start/running, process 10005 | |
| [13:01] <Tug> juju-db stop/waiting | |
| [13:01] <Tug> jujud-machine-0 start/running, process 10003 | |
| [13:01] <marcoceppi> but yes, that should be running | |
| [13:01] <marcoceppi> oh, start the juju-db job then | |
| [13:01] <Tug> I may have reconfigured mongodb for my needs | |
| [13:01] <Tug> is it using mongodb ? | |
| [13:01] <marcoceppi> sudo start juju-db | |
| [13:01] <marcoceppi> yes | |
| [13:01] <Tug> :s | |
| [13:01] <marcoceppi> juju-db is mongodb | |
| [13:02] <Tug> yeah I wiped out the db to connec to a replicaset | |
| [13:02] <marcoceppi> which explains why now. if you want to run a charm on node 0 which uses mongodb, try --to lxc:0 instead | |
| [13:03] <Tug> ok but I would have to start over because the configuration is lost right ? | |
| [13:05] <marcoceppi> Tug: you might be able to save it but odds are it's best to start over | |
| [13:05] <Tug> ok, thanks for helping me again marcoceppi :) | |
| [13:06] <marcoceppi> Tug: np! | |
| [13:07] <Tug> next time I try the real thing in AWS ;) | |
| [13:23] <zchander> ping marcoceppi | |
| [13:25] <Tug> I wonder how I will update my application once deployed though. Is there an API or something to execute commands on all the units of a service ? | |
| [13:25] <Tug> I like the way deployment is done with capistrano | |
| [13:47] <Tug> I'm not a fan of polling a deployment repository | |
| === CyberJacob|Away is now known as CyberJacob | |
| === CyberJacob is now known as CyberJacob|Away | |
| === CyberJacob|Away is now known as CyberJacob | |
| [21:16] <marcoceppi> Tug: typically, you can make a version configuration option to decouple charm from application version | |
| [21:17] <marcoceppi> Tug: some charms even do something like repo, branch where repo can be a git, bzr, or hg repository and branch can be a git tag, git branch, bzr tag, etc | |
| [21:19] <Tug> ok, but if I change the config option of the service all units are updated ? | |
| [21:19] <Tug> what if I want to update half of it to keep the system online for instance ? | |
| [21:59] <lazyPower> Tug: I may be wrong, but i don't think juju supports that ootb. You woudl want ot deploy 2 clusters of the application, and update them independently behind a load balancer | |
| [21:59] <lazyPower> eg: wordpress1, wordpress2, behind haproxy | |
| [21:59] <lazyPower> set wordpress1 to perform the update, haproxy will route to wordpress2 while wordpress1 is "down" for the update. | |
| === Ursinha is now known as Ursinha-afk | |
| === Ursinha-afk is now known as Ursinha | |
| [22:48] <marcoceppi> Tug: lazyPower is correct. You're managing service groups not units. If you want to matinain diffferent service groups and do cascading upgrades, deploy your service twice with different alias (juju deploy wordpress wp1; as an example) | |
| [22:48] <Tug> ok makes sens :) | |
| [22:48] <Tug> *sense | |
| [22:49] <Tug> have to go, thx for tthe tips | |