[01:47] <AskUbuntu> Juju on AWS t1.micro (or other) reserved instances | http://askubuntu.com/q/307954
[02:15] <virusuy> hi guys !
[10:46] <BaribalWrk> Hi. I've gotten access to a few racks with rather impressive machines that run KVM/libvirtd. Is there a way to integrate juju in this environment?
[10:48] <Baribal> Also, so far they're only deploying CentOS VMs here, but AFAIK that shouldn't be an issue as juju downloads images itself anyways.
[11:29] <stub> Is the charm cache on the bootstrap node, or in the control bucket?
[13:10] <marcoceppi> stub: I think it's in the control bucket
[13:12] <jhf> hey all - question on best practices. my charm installs a service whose filesystem layout is different depending on version. so for example, if I install to /opt/liferay, then in one version, its "home dir" is /opt/liferay/v1 but in the next version it'll be /opt/liferay/v2.  So I am saving the value of /opt/liferay/v1 into a dot file so that in a future upgrade I can discover the filesystem layout of the "old" version during the upgrade. I considered making i
[13:12] <jhf> part of the charm config but that didn't feel right because this is not a user "tunable" and if one were to change it, it would break badly. so is it cool to save variables in this way during the install so that they can be available during an upgrade?
[13:14] <marcoceppi> jhf: absolutely. A lot of charms that need to keep track of low level data like that typically put them in a dot file in either the services home (not really a good idea in this case) or the $CHARM_DIR
[13:14] <jhf> hmm.. good idea re: charm dir, but when I upgrade the charm, will those files remain during the upgrade of the actual charm unit files?
[13:15] <marcoceppi> jhf: yes, upgrade-charm only overwrites files that are extracted from the new charm. So any files created by the charm are not touched
[13:16] <stub> marcoceppi: Thought so. I discovered the weirdness I was seeing was update-charm deploying revisions I was working on yesterday, despite a fresh bootstrapped environment.
[13:16] <jhf> nice.. I like that better than putting it in the service dir. I'll go with that, thanks!
[13:19] <jhf> btw - I tried to use the "juju debug-hooks" command, but it tries to do fancy things via the terminal, and gets really messed up on a mac: I am running ubuntu in a virtual box vm, so I ssh to the virtual ubuntu instance, and then run juju debug-hooks and my terminal gets all wonky, making juju debug-hooks unusable :(
[13:19] <jhf> I don't think this is juju's fault but just thought I'd mention it. haven't played with terminal settings yet to try and fix it.
[14:42] <jhf> hey all - I am using a local repository for charm testing - I am editing the files and then running juju upgrade-charm but it keeps using old, cached copies of the files so the resulting charm that is copied to the container doesn't have the updates.. is there a way for it not to use the old, cached charm files?
[14:55] <_mup_> Bug #1191030 was filed: Provisioning agent stops working <juju:New> <https://launchpad.net/bugs/1191030>
[15:41] <marcoceppi> jhf: You need to either increment the revision number or use the -f flag to force an uprade
[16:21] <jhf> woo! it works! now time to re-learn bzr to push the fixes :)
[16:38] <marcoceppi> Charm school in 20 mins!
[17:00] <marcoceppi> Charm School is now! http://ubuntuonair.com/
[17:07]  * FunnyLookinHat is watching :D
[17:07] <FunnyLookinHat> and taking notes
[17:20] <jhf> Is there a way to stop a service (not destroy-service)?  That is, something that triggers the stop hook, but otherwise leaves things as they were?
[17:21] <FunnyLookinHat> marcoceppi, select the gray box and double click the color next to "Fill" in the bottom left :)
[17:22] <FunnyLookinHat> But use the arrow tool to select it.
[17:37] <FunnyLookinHat> off-topic question for the charm school today, but I can't find documentation on how to fire a custom hook on a charm that's already deployed
[17:38] <jhf> https://juju.ubuntu.com/docs/policy.html#license refers to the list of OSI-approved licenses at http://opensource.org/licenses/
[17:44] <jhf> question!! Is there a way to stop a service (not destroy-service)?  That is, something that triggers the stop hook, but otherwise leaves things as they were?
[17:44] <FunnyLookinHat> jhf, That's what I'm aiming for...  :)
[17:44] <FunnyLookinHat> with a custom hook
[17:51] <FunnyLookinHat> Ah ok - so you'd write it into config-changed
[17:51] <jhf> Is there a reason there's no charms for any release other than precise?  I assume I'd start with the latest Ubuntu release, but didn't see any raring charms
[17:54] <sarnold> jhf: I'd expect saucy charms to pick up, as people prepare for 14.04 and assume it'll be the next LTS release
[17:54] <jhf> ah ok, thanks
[17:55] <sarnold> jhf: for my part, I did my (very few) charms on precise, because it seemed the most well-tested, and intended to port them to quantal; but I never got around to it, and next thing I know, raring is out...
[17:55] <FunnyLookinHat> Ok - so to do it in juju-core, you would have to fire a config change and handle the flag within config-changed
[17:55] <sarnold> .. and it's easier to ignore two broken things than one broken thing :)
[17:55] <jhf> :)
[17:56] <sarnold> jhf: but I'm in a different position, I don't have hundreds of machines to support, perhaps those people that do are just targetting the newest release that they actually have deployed in their environments
[18:01] <fred> hi
[18:02] <Guest89610> #nick fred
[18:02] <Guest89610> i forgot how to use irc :(
[18:02] <sarnold> Guest89610: /nick
[18:03] <sarnold> Guest89610: but, pick a different nickname, fred must be protected, it'll just change you away again :)
[18:03] <Guest89610> thamks man
[18:03] <Guest89610> *tnx
[18:03] <Guest89610> ah i see. okay
[18:03] <fred1234> fred1234 will do :P
[18:04] <fred1234> how ya all :P
[18:04] <fred1234> how's ubuntu?
[18:09] <fred1234> hi
[18:09] <fred1234> where can i get started?
[18:10] <fred1234> i mean, the flirst v
[18:10] <fred1234> i mean, the first vid of juju?
[18:10] <fred1234> i had not updated or been active with ubuntu lately. i want to catch-up.
[18:11] <FunnyLookinHat> So - if I were to deploy on AWS - is there a way to deploy to two separate regions at once?
[18:11] <fred1234> :-(
[18:12] <FunnyLookinHat> fred1234, I'd probably just read through this stuff: https://juju.ubuntu.com/docs/
[18:12] <FunnyLookinHat> Just go through the table of contents - it paints a picture pretty well and gets you into stuff quickly
[18:13] <fred1234> ah okay, fun :) this coyld help. been using ubuntu since 6.xx, but im not a c or c++ expert :(
[18:14] <fred1234> but had manage through terminal somehow lols :P
[18:14] <fred1234> *could
[18:14] <fred1234> tnx again. i'll carry-on
[18:18] <fred1234> #juju: i'm just finish with the home page. also ventured reading en.wiki -> http://en.wikipedia.org/wiki/Juju_%28software%29
[18:20] <fred1234> nice, like service ilnterfacing and concurrency, and cloukd... still wondering what services and how does it provide those....
[18:20] <fred1234> ... i'll read further lols
[19:08] <marcoceppi> FunnyLookinHat: no, not currently. Cloud (and region) federation is on the roadmap
[19:08] <marcoceppi> fred1234: check out jujucharms.com for a list of charms (services) we have currently!
[19:09] <FunnyLookinHat> marcoceppi, Ok - my worry is that AWS has had outages in the past, and without rackspace support I feel as though we're having to make a bad decision  :-/
[19:10] <marcoceppi> FunnyLookinHat: yeah, it's been on the roadmap for a while. I think with containerization and local provider being worked on that cloud federation will be ready by 14.04. It's kind of a requirment to make the tool truely "production" ready
[19:10] <FunnyLookinHat> yeah - I'm keeping a close eye on the containerization stuff  :)
[20:14] <jake> tes tes
[20:35] <Mage_Dude> How can you delete a node/service if juju status doesn't work?
[20:35] <rnathuji> Hi folks, I have a quick question on bootstrapping juju
[20:36] <rnathuji> I've deployed MaaS and enlisted 3 ARM nodes (shown as ready state).  juju bootstrap fails with "No matching node is available". I did try doing a set-constraint arch=armhf, but then it complains that it's not bootstrapped. Does the boostrap node have to be x86?
[20:40] <rnathuji> nm, figured it out
[20:40] <Mage_Dude> You wouldn't happen to know how to delete a node from maas would you?
[20:42] <rnathuji> I haven't tried it, but it looks like the UI has a "Delete node" button on if you click on the node name from the list of all nodes. Or is that itself not working for you?
[20:43] <Mage_Dude> No, you can't do it that way because the node has been allocated. However, juju status doesn't work so you can't unallocate the node! The *only* way I've found to do it is to wipe the MAAS db and recommission all the nodes again.
[20:44] <rnathuji> Can you use maas-cli to release the node and then delete it?
[20:45] <rnathuji> (I'm not even sure what exactly release does, just saw it on the maas-cli options list)
[20:45] <Mage_Dude> I'll have to look at it
[20:50] <Mage_Dude> That's bizzare. The cli only lists one node as allocated, but the gui shows two.
[20:59] <Mage_Dude> sudo maas-cli nodes release <some-id-value> ... why is that incorrect syntax?
[21:02] <Mage_Dude> Grrr
[22:13] <paraglade> marcoceppi: Just got done watching the vid for the charm school today and wanted to know if I heard you correctly say that we could submit are charms to GitHub.
[23:03] <Mage_Dude> Is maas+juju actually functional or is it a late April Fools joke?
[23:09] <Mage_Dude> So, maas doesn't do anything other than provision machines. Then you have to ssh into one of the provisioned machines and actually bootstrap juju there?
[23:10] <sarnold> Mage_Dude: that doesn't sound right..
[23:10] <sarnold> I don't have enough free hardware laying around to try out maas, but the maas provider for juju should just let you juju bootstrap ; juju deploy ...
[23:11] <Mage_Dude> sarnold: I wish. juju bootstrap (Yay kittens!) juju status (I will throw ambiguous errors!)
[23:12] <sarnold> heh :(
[23:12] <Mage_Dude> I can ssh directly into a 'provisioned' node with the ssh key generated. However, I try juju status and get an ssh key error. That makes no sense.
[23:12] <sarnold> Mage_Dude: it's true that juju status often passes up an opportunity to show something more meaningful from a log file. status is hard to capture in the few states available. :(
[23:14] <Mage_Dude> And it's so great when maas is trying to provision two nodes to do the same thing because it can't actually bootstrap/setup the node. Any thoughts on why my perfectly valid ssh key is being rejected?
[23:20] <m_3> paraglade: yeah, we can handle PRs, they're just a little more manual of a process until we get some things changed around
[23:20] <m_3> paraglade: I'd recommend pinging me or marcoceppi directly when you've submitted one... at least for the next few weeks
[23:38] <bkerensa> jcastro: will local environment work by OSCON? :)
[23:56] <m_3> bkerensa: shit, don't remember... jorge'd probably know
[23:56] <m_3> he's out today
[23:57] <bkerensa> m_3: ok just wondering were planning Juju demo at the booth and its either local enviroment or rackspace cloud neither of which worked last time I checked :P
[23:57] <bkerensa> m_3: unless jorge is expensing AWS :)
[23:57] <m_3> :)
[23:57] <m_3> which conference?
[23:59] <bkerensa> m_3: the one you will be at in July
[23:59] <m_3> bkerensa: awesome
[23:59] <bkerensa> :)