[01:05] hi [01:06] does anyone know how to assign a floating ip to a lxc? [01:14] guys, let's say I have only one AWS account but set two environments with different names but the same credentials. will that work for having 2 diff environments? [01:16] jose: I haven't tested but that sure feels like something that should just work [01:16] sarnold: if you can tell me it won't break everything, then I can give it a try :P [01:16] jose: you're a charmbot 2000! what could go wrong? :) [01:17] haha, let's do this [01:17] jose: (just be sure to look at the storage used for the bucket uploads once you're done -- I got a surprise bill from aws when my free period ended because I hadn't cleaned up my juju bucket -- just clearing the instances wasn't sufficient, of course.) [01:18] <3 aws billing alerts [01:18] sarnold: thanks for the tip, will need to make sure! I depend on billing alerts too :P [01:25] sarnold: should I use a different bucket name for the second env? [01:25] jose: eek. no idea :) [01:25] will try with the same [01:28] sarnold: voilĂ ! it worked! just needs a different bucket name! [01:29] jose: cool :D [01:29] charmbot.. 3000? :) [01:29] I was 5000 originally, maybe I can go up to 4999? :P [01:29] oh! my apologies. [01:29] (see '/ns info joseeantonior' for more info) [01:31] jose: aww, I don't see any charmbot 5000 details there :/ [01:31] sarnold: yeah he needsa a different bucket name :) for reference. [01:31] heya lazypower-travel :) [01:31] sarnold: if you can't see it, /ns info charmbot5000 === lazypower-travel is now known as lazypower [01:32] jose: haha [01:32] lazypower: no more travel? [01:32] sarnold: not until Monday [01:34] lazypower: ahhh. all the more time to go get some more of that steak. was it as good as it looked? :) heh [01:35] oh man, not only did i have steak, i had cheesesteak [01:35] CHEESESTEAK? oh man. [01:35] it was amazing [01:35] philly cheesesteak in philly [01:36] * jose has never had philly steak [01:36] one of these days I'll make it to that side of the rocky mountains and get some from the source... [01:37] its worth it. true story. [01:42] https://joseeantonior.wordpress.com/2014/06/20/juju-multiple-environments-with-just-one-account/ [01:44] jose: charmbot 5001 :) [01:44] \o/ [01:49] wooo https://twitter.com/cammoraton/status/480124918173294592 [01:50] \o/ === CyberJacob|Away is now known as CyberJacob === CyberJacob is now known as CyberJacob|Away === 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 [13:04] jcastro_, jamespage: FYI, bug 1328958. Seems critical to me for the normal user trying out juju use case. === scuttle|afk is now known as scuttlemonkey === scuttle|afk is now known as scuttlemonkey === scuttle|afk is now known as scuttlemonkey === vladk|offline is now known as vladk [17:15] Hi ALL.. Can any body how can i deploy a service in kvm i.e neutron-gateway when all other services are in lxc mode [18:01] any idea how to get rid off a lingering dead charm ? I tried juju remove-service and restart the jujud on the target unit but the charm is still there. shows up as agent-state: stopped life: dead === vladk is now known as vladk|offline [18:37] the charm shows up life as dead and agent as stopped however doesnt get removed. Same result by destroying it from the juju gui. any idea how to remove these dying charms [18:41] galebba try juju resolved service-name [18:41] after destroying the service [18:42] galebba: if that didnt work then you have to destroy the machine where that service is in dying state [18:43] yeah it says the service is not in error state [18:43] so i guess destroying the machine is the last resort ? i have other services in the same machine [18:43] but when you destroy machine you might have to use --force command [18:44] if you have other services then try following 1. destroy-service 2. remove-service and then juju resolve service-name [18:44] this works for me few times [18:45] i guess first i have to destroy the relations before those ? [18:45] yes if you have relations then yes [18:46] then do the same 1. destry-relation 2. destroy-service 3. remove-service and then after 1 min juju resolve service-name [18:47] i will check the logs next time i face that issue but i think juju resolve try to clear all the pending / dying states === CyberJacob|Away is now known as CyberJacob [19:03] could anyone tell me do i need to set the ppa:juju/stable repos to install openstack on 14.04 ? From all the docs i see this is not mentioned and i cant seem to set it anyways === scuttlemonkey is now known as scuttle|afk [22:26] galebba: you shouldn't need to no. 14.04 has juju-stable in the repositories [23:55] thank you, lazypower