[00:14] <Valduare> hi guys
[00:14] <lazyPower> Allo Valduare
[00:14] <Valduare> looking into this maas and juju stuff tonight :)
[00:14] <Valduare> wishing I had spare hardware to test on
[00:15] <lazyPower> I've you've got a single beefy machine you can try out MAAS in avirtual machine
[00:15] <Valduare> that I dont
[00:15] <Valduare> I run amde350 proc board
[00:16] <Valduare> does juju and these charms play nicely with arm too?
[00:16] <lazyPower> I dont have an answer for that...
[00:17] <lazyPower> But I can get back to you tomorrow
[00:18] <Valduare> looking forward to the day when I could use things like mk902 for small server farm heh
[00:19] <lazyPower> Ideally thats just compilation time magic and some PPA's
[00:19] <lazyPower> build an arm compiler farm, and start porting packages.
[00:19] <lazyPower> there's already some ARM support in the ubuntu archives
[00:20] <Valduare> beyond my skillset
[00:22] <davecheney> Valduare: yes, charms work on arm systems
[00:23] <Valduare> davecheney: I was just talking to one of the guys in #maas about arm devices for maas as well
[00:23] <Valduare> looks like things are getting pretty close to a guy like me being able to set something up heh
[00:23] <davecheney> Valduare: there aren't a lot in the realm that mortals ca nafford
[00:23] <davecheney> but there are server options like hp's moonshot
[00:24] <davecheney> and the calexeda machines [rip]
[00:24] <Valduare> davecheney: I use a gigabyte ga-e350n board with 16 gigs of ram hosting 14 vm’s right now
[00:24] <davecheney> maas requires that the machines can netboot and have an LOM
[00:24] <davecheney> a LOM
[00:24] <Valduare> LOM?
[00:24] <davecheney> but you can always use the manual provider to enroll machines that you've already setup
[00:25] <davecheney> LOM == iLO == IPMI == Lights out management
[00:25] <Valduare> ah
[00:25] <davecheney> IBM call them service processors
[00:25] <davecheney> dell call's them DRACs
[00:25] <Valduare> with these arm units using half watt idle can maas be configured to not try and shut them down?
[00:25] <davecheney> Valduare: skip maas
[00:25] <davecheney> use the manual privcer
[00:26] <davecheney> provider
[00:36] <lazyPower> davecheney: whats the benefit to skipping maas? Less to worry about being ported or....
[00:36] <lazyPower> my knowledge of arm in the realm of ubuntu is sadly limited. I'll add it ot my required reading list.
[00:39] <sarnold> I suspect its because maas is mostly useful if you want to turn machines off and on :)
[00:39] <sarnold> if they're just going to be on all the time, why bother?
[00:40] <Valduare> isnt it also for if you want a baremetal server for something ?
[00:40] <Valduare> and then roll it back “into the cloud"
[00:41] <davecheney> Valduare: /s/cloud/butt/
[00:41] <davecheney> maas lets you treat raw tin like virtual machines
[00:42] <davecheney> so you can 'checkout', or 'reserve' a raw hardware which is running *exactly* the same cloud image that you find on any of our CPC partners
[00:42] <davecheney> (certified public cloud)
[00:42] <lazyPower> I get the purpose of MAAS as a whole, i was just curious about skipping it as the provisioner.
[00:42] <lazyPower> I'm actually pining over a VMAAS setup for some reason
[00:42] <lazyPower> (mostly because I want to learn more about maas)
[00:43] <davecheney> lazyPower: we skip the privisioner because there is no maas provider for little arm boards
[00:43] <davecheney> rpi, bbb, pandaboard etc don't have a management nic
[00:43] <davecheney> so we can't remote power them or remote netboot them
[00:43] <davecheney> at the moment
[00:43] <davecheney> most of the parts exist if you're prepared to work at it
[00:43] <davecheney> for instance the arm builders that ubuntu uses are remotely powered
[00:44] <lazyPower> ahhh ok - i've been in talks with marco about it, and the dual nic was a blocker for my suggested rpi setup
[00:44] <davecheney> and you can use uboot (grub for arm device)
[00:44] <lazyPower> makes sense
[00:44] <davecheney> to netboot
[00:44] <davecheney> but as a function of time == money
[00:44] <davecheney> this would never be more than a side project
[00:44] <davecheney> honestly
[00:45] <davecheney> it's easier to just use the ssh provider
[00:45] <davecheney> and skip maas
[00:45] <lazyPower> I'm considering picking up a few BBB boards and building a micro cluster out of them for some in home apps, and power down my beefy quad core to save on power.
[00:45] <lazyPower> it doesn't take much to run python code
[00:45] <Valduare> lazyPower: look into mk902
[00:46] <davecheney> lazyPower: meh, just rent a digital ocean server for 5 bucks a month
[00:46] <Valduare> much more for your money than BBB
[00:46] <lazyPower> davecheney: these are apps that are specific to my house, and not suited for the cloud. I dont want to run my garage door opener on DO :P
[00:46] <davecheney> lazyPower: don't you trust the cloud ?
[00:46] <lazyPower> not with the keys to my house, nope nope
[00:46] <davecheney> Valduare: /s/cloud/butt/
[00:46] <lazyPower> With my RSS Reader and blog, you bet.
[00:48] <sarnold> davecheney: lol
[00:50] <davecheney> lazyPower: the BBB is a great first choice
[00:51] <davecheney> little bit faster than the Rpi
[00:51] <davecheney> and you get a little bit of built in flash
[00:51] <lazyPower> Yea, the 1g of on board memory is what akes me happy
[00:51] <davecheney> it's 512mb
[00:51] <lazyPower> theres a 1g bbb board i thought
[00:51] <davecheney> ORLY ?
[00:51]  * davecheney googles
[00:51] <lazyPower> https://www.tigal.com//product.asp?pid=3406
[00:52] <davecheney> yup, 512mb
[00:52] <lazyPower> gah, nope, says 512 in the read out
[00:52] <sarnold> these things look nice compared to the pandaboard es I've got: http://cubox-i.com/table/
[00:52] <davecheney> BBB will run at 1Ghz with enough current, or 550mhz with USB 500ma
[00:52] <sarnold> cheaper -and- faster...
[00:52] <davecheney> sarnold: oh no
[00:52] <davecheney> not the cubox i
[00:53] <davecheney> the biuld quality makes dollar store kids toys look solid
[00:53] <davecheney> i have one
[00:53] <sarnold> oh no!
[00:53] <sarnold> sigh
[00:53] <sarnold> it's almost like $55 isn't a good price for a computer :)
[00:53] <davecheney> http://www.hardkernel.com/main/products/prdt_info.php?g_code=G137510300620
[00:53] <davecheney> consider the udoo board
[00:54] <davecheney> they support ubuntu now
[00:54] <davecheney> identical hardware (iMX.6) to the cubox
[00:54] <Valduare> guys guys… have you seen the mk902 specs?
[00:54] <davecheney> A10/A20 I think
[00:55] <lazyPower> haha Valduare, you sound like a broken record. Are you a share holder with the mk902?
[00:55] <Valduare> no
[00:55] <davecheney> Valduare: looks nice
[00:55] <Valduare> just cant wait to get one ordered :P
[00:56] <Valduare> granted most of the community around the mk devices are home theatre box types
[00:56] <Valduare> but the hardware runs ubuntu quite nicely
[00:56] <davecheney> Valduare: i was thinking of the older mk800 series devices which were HDMI stick type things
[00:56] <Valduare> I have a bunch of mk808 sticks
[00:57] <Valduare> just returned an mk802 cozyswan clone to amazon, deciding wether to put the money towards an mk902 or ram upgrade for my laptop
[00:58] <lazyPower> hmm... $110 pc...
[01:07] <lazyPower> sarnold: sold, i want one of these cuboxi's
[01:07] <lazyPower> actually, ~ 5 of them to be exact.
[01:07] <sarnold> haha
[01:08] <sarnold> lazyPower: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741127
[01:09] <davecheney> their current kernel
[01:09] <davecheney> in fact all the iMX6 kernels are OOOOOOOOOOOOOOOOOOOLD
[01:09] <davecheney> 3.0.36
[01:09] <sarnold> ow
[01:09] <davecheney> yeah
[01:09] <davecheney> bourns!
[01:10] <lazyPower> bummer :|
[01:11] <lazyPower> you know, i dont think buliding that would be all that crazy, and cloud storage is cheap...
[01:11] <lazyPower> however, just about every update ever run would cause it to break stuff
[01:11] <lazyPower> nevermind, i'm wishful thinking again
[01:12]  * sarnold giggles, "butt storage"
[01:12] <lazyPower> Vatt is this s/cloud/butt/ thing that seems to have taken off. Did i miss a warthogs post or something?
[01:13] <davecheney> lazyPower: welcome to the internet
[01:13] <sarnold> lazyPower: https://addons.mozilla.org/en-US/firefox/addon/cloud-to-butt-plus/
[01:13] <davecheney> https://chrome.google.com/webstore/detail/cloud-to-butt-plus/apmlngnhgbnjpajelfkmabhkfapgnoai?hl=en
[01:13] <davecheney> JYNX!
[01:13] <sarnold> diversity! firefox -and- chrome are covered :)
[01:14] <lazyPower> http://i.imgur.com/XEJveUI.png
[02:24] <Valduare> so these charms
[02:24] <Valduare> how are they made
[02:30] <davecheney> Valduare: charms are a collecton of shell scripts
[02:30] <davecheney> in a tarball
[02:31] <davecheney> with names like
[02:31] <davecheney> hooks/install
[02:31] <davecheney> hooks/config-changed
[02:32] <Valduare> so all the normal commands i’d do to provision a servr just wraped up in a shell ?
[02:32] <davecheney> Valduare: exactly
[02:32] <Valduare> so not something you’d do for if your just provisioning 2 or 3 of a certain webapp etc? :P
[02:33] <davecheney> Valduare: sure
[02:33] <davecheney> but the thing is
[02:33] <davecheney> you can use other peoples charms
[02:33] <davecheney> in fact
[02:33] <davecheney> you shold
[02:33] <davecheney> charms encapsulate the best practice of configuring a particular service
[02:33] <davecheney> need mysql
[02:33] <davecheney> deploy the mysql charm
[02:33] <davecheney> need rabbit mq
[02:33] <davecheney> deploy the rabbit mq charm
[02:33] <davecheney> need an openstack install
[02:34] <davecheney> deploy the openstack charms, or all in one as a bundle
[02:34] <Valduare> are these charms checked over and scrutinized?
[02:34] <davecheney> Valduare: of course
[02:35] <davecheney> https://juju.ubuntu.com/docs/authors-charm-policy.html
[02:38] <Valduare> interesint
[02:38] <Valduare> is there place I can search what charms are available
[02:38] <Valduare> looking for a canvas server specifically - instructure learning management system
[02:38] <davecheney> Valduare: sure, https://jujucharms.com/
[02:39] <davecheney> i don't think we have had a canvas charm contributed
[02:39] <Valduare> darn
[02:39] <Valduare> its pretty fancy lms
[02:46] <lazyPower> Valduare: actually - to build on davecheney's answer, you're not just dropping shell scripts. We actually encourage users to use configuration management tools if you're already familiar with them
[02:47] <lazyPower> if you look at the rails charm, it uses chef. The puppet master server, puppet master.   I'm getting fairly handy with ansible in a few of my newer iterations on charms
[02:47] <lazyPower> s/, puppet master/puppet/
[02:47] <Valduare> i’ve never done anything more than follow a blog post guide for setting up what Im looking to do heh
[02:48] <lazyPower> welp, you're 80% of the way there. Encapsulate teh logics into idempotent bash scripts, and segregate the logic into the proper hooks and you've got a charm.
[04:33] <jose> hey! in the case I want to deploy rabbitmq-server, do I need to deploy ceph-client or hacluster?
[04:35] <davecheney> jose: not unless you need those services
[04:35] <jose> davecheney: cool, thanks~
[04:35] <jose> !*
[04:35] <jose> I'm in the middle of an attempt to write a Reddit charm - it's more hard than what I initially thought
[04:36] <davecheney> reddit ?
[04:37] <jose> yep, what powers reddit.com, it's open source :)
[04:37] <jose> https://github.com/reddit/reddit/
[04:37] <sarnold> cool :)
[04:37] <davecheney> jose: right, are you deploying reddit with juju ?
[04:37] <jose> (I didn't know about it until a while ago)
[04:37] <jose> davecheney: not yet, I'm in the process of writing the charm still
[04:38] <jose> but that would be the final purpose, yes
[04:38] <davecheney> cool
[04:38] <davecheney> you've come to the right channel then
[04:38] <jose> oh, oh, are you a charmer?
[04:40] <davecheney> some think i am, i think they are mistaken
[04:40] <jose> mind doing a review of a charm?
[04:41] <davecheney> jose: sure I can take a quick look
[04:41] <jose> awesome :)
[04:41] <davecheney> if you want a proper review, why not consider submitting it to the store
[04:41] <jose> https://bugs.launchpad.net/charms/+bug/1199052 and https://code.launchpad.net/~jose/charms/precise/mailman/trunk
[04:41] <_mup_> Bug #1199052: New charm: mailman <Juju Charms Collection:New> <https://launchpad.net/bugs/1199052>
[04:41] <jose> well, I already have, but it's still on the queue
[04:41] <jose> 11 days as of today
[05:01] <AskUbuntu> Error in creating juju bootstrap | http://askubuntu.com/q/438851
[05:05] <jose> davecheney: did you get to take a peek?
[05:10] <davecheney> jose: i had a little look
[05:10] <davecheney> it's late in my work day
[05:10] <jose> oh, I thought you were down under
[05:10]  * jose has to stop making assumptions
[05:10] <davecheney> jose: i am
[05:11] <jose> well, anyways :)
[06:51] <AskUbuntu> How to restart OpenStack services after restart/logout? | http://askubuntu.com/q/438871
[08:35] <themonk> marcoceppi: hi
[08:36] <themonk> marcoceppi: i am facing problem in charm relation
[08:38] <themonk> marcoceppi: i am setting private ip and server port in relation set in relation-joined of provider charm but cant get it in requere charm relation joined/changed using relation get
[08:38] <themonk> i am facing problem in charm relation
[08:38] <themonk> i am setting private ip and server port in relation set in relation-joined of provider charm but cant get it in require charm relation joined/changed using relation-get
[08:59] <jose> themonk: mind if I take a look at the code?
[08:59] <jose> is it in LP somewhere?
[10:13] <jamespage> if there are any charmers around with some time I need a review of:
[10:13] <jamespage> https://code.launchpad.net/~james-page/charm-helpers/neutron-packages/+merge/198518
[10:13] <jamespage> https://code.launchpad.net/~openstack-charmers/charm-helpers/active-active/+merge/211285
[10:13] <jamespage> and
[10:13] <jamespage> https://code.launchpad.net/~openstack-charmers/charm-helpers/icehouse/+merge/211934
[10:14] <jamespage> aside from active-active, the other two branchs have been in use in OpenStack CI for the last week
[10:16] <jamespage> nope - they are all in use in the CI environment
[10:45] <marcoceppi> jamespage: reviewing now
[10:45] <jamespage> marcoceppi, thanks
[10:52] <marcoceppi> jamespage: icehouse branch gives me conflicts, it apparently does something different than the first neutron-packages branch
[10:52] <jamespage> marcoceppi, most likely yes
[10:52] <marcoceppi> I can resolve the diference really quickly if you tell me which to go with
[10:52] <marcoceppi> jamespage: http://paste.ubuntu.com/7150639/
[10:52] <marcoceppi> I'm guessing MERGE-SOURCE is the way to go
[10:53] <jamespage> marcoceppi, that is odd - I thought that icehouse had that branch merged
[10:53] <jamespage> marcoceppi, but yes MERGE_SOURCE is good
[10:53] <marcoceppi> fwiw, it's the only conflict I got
[10:53] <marcoceppi> jamespage: ack, will resolve
[10:53] <jamespage> that has the change to accomodate the 3.13 kernel
[10:53] <jamespage> marcoceppi, apologues - these have stacked up a bit
[10:54] <marcoceppi> jamespage: np, seems like a lot of good work though
[10:54] <jamespage> marcoceppi, more to come
[10:54] <jamespage> ssl-everywhere man!
[10:54] <marcoceppi> jamespage: ping me if you need more charm-helpers merges this week
[10:54] <jamespage> marcoceppi, will do
[10:58] <jamespage> marcoceppi, if you fancy another quicky - https://code.launchpad.net/~james-page/charms/precise/rabbitmq-server/source-take-two/+merge/212576
[10:58] <jamespage> that should unblock mbruzek's test failures for his tests branch
[10:58] <jamespage> marcoceppi, just read that back
[10:58] <jamespage> lol
[10:59] <jamespage> marcoceppi, I have a full charm-helpers redux backed up so need to get that and mbruzek's stuff landed
[10:59] <marcoceppi> jamespage: so source is no longer immutable for rabbitmq-server charm?
[11:00] <jamespage> marcoceppi, you can change it on the fly!
[11:00] <marcoceppi> \o/ jamespage thanks for that, appreciate it will review after the icehouse branch
[11:00] <jamespage> marcoceppi, of course for the majority of time, this will not do much
[11:00] <jamespage> unless a new rabbitmq is avaliable.
[11:00] <marcoceppi> ack
[11:01] <marcoceppi> I'll just drop that little note in the readme when I review it
[11:02] <jamespage> marcoceppi, ah - good idea
[11:02] <jamespage> I can update that now
[11:08] <jamespage> marcoceppi, notes added to README
[11:08] <marcoceppi> jamespage: Oh, brilliant, thank you!
[11:10] <marcoceppi> lazyPower: hey, can you put a few charms in the top of your queue for reviewing today?
[11:21] <zchander> ping lazyPower
[11:32] <overm1nd> I'm a bit confused, what happen if I put phpmyadmin service on the same machine as wordpress?
[11:32] <overm1nd> some times it works some times it doesn't
[11:32] <overm1nd> checking for the open port is not a requirement for the charm?
[11:38] <marcoceppi> overm1nd: it's typically /never/ a good idea to use the --to flag without isolation
[11:38] <marcoceppi> charms are created with the idea that they have the entire machine at their control
[11:38] <overm1nd> ok
[11:39] <overm1nd> what you mean for isolation?
[11:39] <marcoceppi> case in point, by default WordPress uses nginx, php5-fpm and phpmyadmin uses apache2 and mod-php5
[11:39] <marcoceppi> overm1nd: using either --to lxc: or --to kvm:
[11:40] <marcoceppi> where it will create a new LXC or KVM instance on the machine, so --to lxc:1 will create a new LXC container on machine 1
[11:40] <overm1nd> so it will isolate the service
[11:41] <marcoceppi> overm1nd: yeah, in a container/vm instead of directly placing it on the machine
[11:41] <overm1nd> understand
[11:41] <marcoceppi> if you're going for density, that's the way to go
[11:41] <overm1nd> I have some early feedback from yesterday about juju
[11:42] <overm1nd> I was expecting more "stability" in the sense of coerence between states
[11:42] <marcoceppi> overm1nd: how so?
[11:43] <overm1nd> after one day of juju deploy I see that some time if you push a service with resolved
[11:43] <overm1nd> it works
[11:43] <overm1nd> even if the juju resolved before was not
[11:43] <marcoceppi> overm1nd: so you're having charms in an error state after a "long running deployment"?
[11:43] <overm1nd> mmm no
[11:44] <overm1nd> but is I change a little the order of commands
[11:44] <overm1nd> I see different results
[11:44] <marcoceppi> well, that /shouldn't/ happen. charms are designed to be idempotent
[11:45] <overm1nd> yes I was expecting it
[11:45] <marcoceppi> however, some charms are a bit old and outdated and may not work like we expect. Which charms are you having issues with?
[11:45] <overm1nd> I have the feeling that not all charms are destroying everithing on the machine
[11:46] <overm1nd> I experimented with haproxy worpress phpmyadmin
[11:46] <overm1nd> juju-gui and mysql
[11:46] <overm1nd> I opened a bug for wp
[11:47] <marcoceppi> overm1nd: ah, I see that bug, thanks
[11:47] <marcoceppi> overm1nd: destroy service doesn't actually clean up the machine
[11:47] <overm1nd> again I'm not a guru so take it with care
[11:47] <marcoceppi> but the install hoook isn't being robust enough
[11:48] <marcoceppi> overm1nd: typically, you would terminate-machine to remove the machine, then deploy on a clean machine
[11:48] <overm1nd> in italiy we say "pinze" :P
[11:48] <overm1nd> ok noted
[11:48] <marcoceppi> but that's a bug in wp as well as the hook isn't really being idempotent, so I'll address that
[11:48] <overm1nd> some charms does not have any info about the address to use them
[11:49] <marcoceppi> overm1nd: how so?
[11:49] <overm1nd> like phpmyadmin, munin
[11:49] <overm1nd> like the url to access to the interface
[11:49] <marcoceppi> All charms can query their address information with `unit-get private-address`, unit-get public-address`
[11:50] <overm1nd> seems obviuos but I had to dig in the config on the node machine to understant the url
[11:50] <overm1nd> I didn't know
[11:51] <overm1nd> another note: why the juju-gui does not say the number of the machine?
[11:51] <overm1nd> I think its a really useful info
[11:51] <marcoceppi> overm1nd: becuase you're looking at a service overview, not a machine view
[11:51] <marcoceppi> overm1nd: there's working being done to show a machine view of the deployment
[11:52] <overm1nd> right
[11:53] <overm1nd> my next step is to start writing a charm
[11:53] <overm1nd> I want to have revive-server (ex openx)
[11:53] <overm1nd> scalable
[11:54] <marcoceppi> awesome!
[11:55] <overm1nd> but I still to understand juju more
[11:55] <overm1nd> I was not able to use haproxy
[11:55] <overm1nd> as a frontend for more than 1 service
[11:55] <overm1nd> maybe I didn't getr the point
[11:56] <overm1nd> I'm used to have an I density service server by my own
[11:56] <overm1nd> juju seems to waste a lot of resources :P
[11:57] <overm1nd> high* density*
[11:57] <marcoceppi> overm1nd: you can, but you have to configure haproxy a little more to do multiple services
[11:58] <marcoceppi> overm1nd: well, juju was designed with high-scale cloud deployments in mind, so if you're looking to manage a smaller pool of resources you have to bend a few things in juju
[11:58] <overm1nd> is ok to deploy with juju and than configure the machine itself by hand?
[11:58] <marcoceppi> overm1nd: you typically wouldn't do that
[11:58] <marcoceppi> what do you need to configure outside of juju?
[11:59] <overm1nd> for example
[11:59] <overm1nd> how can I create a subdomani on apache server and deploy a simple php app?
[12:00] <overm1nd> I think juju is for doing way bigger deployment than what I need
[12:01] <overm1nd> but I woiuld like to use it at least as scalable backend of frontend for other services
[12:01] <marcoceppi> overm1nd: deploying a simple php app would be one of two ways
[12:01]  * overm1nd listening 
[12:02] <marcoceppi> either build a subordinate charm to the apache2 charm, or build a standalone charm that installs apache2 and php and your app
[12:02] <overm1nd> i don't know uet what is a subordinate charm
[12:02] <overm1nd> yet*
[12:02]  * overm1nd reading docs 
[12:02] <marcoceppi> overm1nd: subordinate charm is a charm that co-exists with another charm on a deployment, it's a way to extend fucntionality that complements a service
[12:03] <overm1nd> sounds what I need
[12:03]  * marcoceppi nods
[12:04] <overm1nd> last question I promise
[12:04] <marcoceppi> so, you can make a charm that deploys on top of the apache2 charm, which will put your app in, say, /var/www/<app> creates a new virtual host in /etc/apache2/sites-available, enables that  vhost, etc
[12:04] <marcoceppi> overm1nd: you can ask as many questions as you need!
[12:04] <overm1nd> this is a type of charm I will try first to write
[12:05] <overm1nd> the question is: if a service is stuck in pending
[12:05] <overm1nd> what can I do? resolve do nothing
[12:05] <overm1nd> because is not an error state
[12:05] <overm1nd> and I can not debug using putty :P
[12:05] <marcoceppi> overm1nd: pending likely means the machine is still starting, juju failed to install on the machine, or something else that's bad
[12:05] <marcoceppi> overm1nd: typically, if a machine is pending more than 10 mins something went wrong
[12:06] <marcoceppi> and juju isn't actually set up on that machine
[12:07] <overm1nd> I think I will try to debug from a wirtual machine
[12:07] <overm1nd> but is the juju env portable?
[12:08] <overm1nd> I mean the machine I use to give commands
[12:09] <overm1nd> if I want to manage the cluster from another pc can I move juju?
[12:14] <marcoceppi> overm1nd: yes
[12:14] <overm1nd> because from putty mtux does not work
[12:15] <overm1nd> or I am not lucky :P
[12:23] <overm1nd> thank you very much for your suggestions marcoceppi I will try them
[12:38] <lazyPower> marcoceppi: sure
[12:38] <lazyPower> zchander: pong
[12:39] <marcoceppi> lazyPower: sd-agent, importio if you would please <3
[12:39] <lazyPower> marcoceppi: dd-agent you mean?
[12:40] <marcoceppi> lazyPower: nope, sd-agent
[12:40] <lazyPower> ah ok, see it
[13:16] <tvansteenburgh> can someone remind me which apt-repo to add to get juju-devel?
[13:17] <tvansteenburgh> marcoceppi told me i get 3 months of dumb questions for free, so i'm starting right away
[13:17] <marcoceppi> tvansteenburgh: I was kidding about the three months ;)
[13:18] <marcoceppi> tvansteenburgh: and it's not a dumb question! ppa:juju/devel
[13:18] <tvansteenburgh> thanks :D
[13:19] <lazyPower> wesleymason: great work on the server density charm.
[13:19] <lazyPower> haha, he's callin you out marcoceppi
[13:19] <wesleymason> lazyPower: cheers, I noticed you open an account, assumed you were testing :)
[13:19] <lazyPower> i like this guy already
[13:19] <lazyPower> wesleymason: theres just one thing stopping it from going to the charmstore. I left notes on the bug
[13:19] <jcastro> can anyone find the rails scalable example bundle?
[13:19] <lazyPower> its literally a one liner 30 second fix.
[13:20] <wesleymason> lazyPower: awesome, cheers, I'll talk a look in a bit
[13:20] <jcastro> man, awesome, lazyPower, someone added ceph support to owncloud
[13:20] <lazyPower> jcastro: it appears to be missing. I'm only getting the rails-single.
[13:20] <lazyPower> jcastro: that was zchander :)
[13:20] <jcastro> zchander, nice!
[13:21] <lazyPower> our community is bringing the heat with these new MP's in the Q
[13:21] <jcastro> wesleymason, I think you have my email right? I can send you a juju shirt for your charm, just jet me along your address and size.
[13:21] <jcastro> zchander, you too! my address is jorge@ubuntu.com
[13:22] <jcastro> lazyPower, importio is still waiting too
[13:22] <lazyPower> jcastro: next in the Q
[13:22] <jcastro> man, a good week in submissions!
[13:22] <wesleymason> jcastro: w00t, thanks!
[13:23] <jcastro> lazyPower, ping me when you promulgate server density, I'd like to blog it
[13:23] <lazyPower> jcastro: pending a one liner from wesleymason, then give me a minute thirty and you'll have it.
[13:24] <lazyPower> so draft away senor
[13:24] <noodles775> sinzui: Hi, if you have a chance, let me know what I missed with https://bugs.launchpad.net/bugs/1297201 that it's incomplete.
[13:24] <_mup_> Bug #1297201: Can not bootstrap after upgrade to 1.17.6 <juju-core:Incomplete> <https://launchpad.net/bugs/1297201>
[13:24] <sinzui> noodles775,  apt-cache policy juju-local
[13:25] <wesleymason> lazyPower: quick question because I couldn't find a very solid answer in the the interface docs, if I change the requires def to "serverdensity" on line 15, it using the juju-info interface is still fine, correct?
[13:25] <lazyPower> correct
[13:25] <wesleymason> \o/
[13:25] <lazyPower> the relationship name should *never* be juju-info, as thats reserved
[13:26] <lazyPower> but the interface is fine being juju-info, that just means you haven't defined a specific interface for the relationship and to use the default.
[13:26] <sinzui> noodles775, do you get your packages from the devel ppa or ubuntu. Mayne ubuntu has a bad package. I cannot help with that, but I can let someone know
[13:26] <wesleymason> lazyPower: makes sense, thanks
[13:26] <marcoceppi> wesleymason: there's also a "local-monitors" interface, that charms like nagios and munin are using
[13:26] <lazyPower> wesleymason: suggestion on improvement for the docs? I know the relationship stuff can get a bit confusing - since I've been staring at them for 3 months, i feel like i've got a decent grasp on them  and your feedback is pure gold.
[13:26] <beuno> o/ wesleymason
[13:27] <jcastro> yeah you're supposed to be able to swap in serverdensity for any one of those tools right?
[13:27] <marcoceppi> where charms will tell the subordinate what services to actually monitor, not sure if that's relevant for the SD charm or not, but thought you might want to know
[13:27] <wesleymason> aha, I was looking for something like that, might be more appropriate
[13:27] <marcoceppi> wesleymason: it could definetly be a post-store revision
[13:27] <noodles775> sinzui: Ah - I see. I'd updated juju-core, but it didn't (and couldn't know to) update juju-local. I should have done it the other way around. Thanks.
[13:28] <marcoceppi> wesleymason: as is this works, I can dig up the local-monitors docs for you if you'd like
[13:28] <wesleymason> marcoceppi: yeah, I'll have a think on the best one later
[13:28] <sinzui> noodles775, well I don't think you should need to. upgrade should have noticed there was a newer juju-local
[13:28] <wesleymason> lazyPower: I'll put my thoughts together tonight and mail you something
[13:28] <marcoceppi> wesleymason: cool, I'll open a bug on lp when this is promulgated to track it's progress, etc
[13:28] <lazyPower> wesleymason: ta! I appreciate the feedback
[13:35] <wesleymason> lazyPower: pushed some changes
[13:36] <zchander> lazyPower: Today I made some additional changes for the ownCloud charm and the Merge Proposal did work :D
[13:36] <zchander> Thanks for your information
[13:36] <lazyPower> wesleymason: excellent. One thing for you to be aware of, if you go the route of  local-monitors you will want ot *Add* the relationship instead of changing this one.
[13:36] <lazyPower> that way you maintain compat with existing deployments.
[13:36] <lazyPower> zchander: awesome!
[13:36] <wesleymason> lazyPower: ah, noted
[13:36] <lazyPower> glad its sorted :)
[13:37] <lazyPower> wesleymason: thanks for the quick turn around. Promulgating now
[13:37] <zchander> Anyone familiar with File_sender? (https://www.assembla.com/spaces/file_sender/wiki)
[13:38] <wesleymason> btw - I gave an unconf talk at PHP NE Conference 2014 the other week on Juju, wrote it up about an hour before giving it, and gave a live demo of deploying a PHP app as a service on the local provider that all worked like a charm: http://1stvamp.github.io/phpne-2014-juju-talk/
[13:39] <lazyPower> nice!
[13:40] <lazyPower> jcastro: read wesleymason's comment here, this will get you excited ^
[13:45] <overm1nd> zchander I appreciate your work on owncloud but why not seafile?
[13:45] <overm1nd> seems less popular but more mature
[13:46] <overm1nd> I don't know file_sender
[13:46] <marcoceppi> overm1nd: you could add it :)
[13:47] <overm1nd> ehehe too much stuff to do on juju for know :P
[13:54] <zchander> overm1nd: It was something I found via Google and it was already a charm. ;) It made my life a bit easier :D
[13:55] <overm1nd> ok, I wanted only to suggest you better alternatives
[13:56] <overm1nd> I digged in to the sync world recently
[13:59] <jcastro> is owncloud still an old version in the charm? we should fix that
[14:00] <jcastro> lazyPower, hey before you promulgate serverdensity check the README, the usage section needs some markdown love for the commands
[14:00] <lazyPower> jcastro: already promulgated, and it renders correct in uberwriter
[14:01] <jcastro> https://jujucharms.com/sidebar/search/~wesmason/precise/serverdensity-24/?text=serverdensity#readme
[14:01] <jcastro> huh
[14:01] <jcastro> but not in the store?
[14:01] <lazyPower> weak sauce
[14:01] <lazyPower> i cant wait until our docs are in markdown
[14:01] <lazyPower> i'll just run the readme's through that and get a 1:1 comparison
[14:02] <lazyPower> apparently my tools support more flavors of markdown than you can shake a stick at
[14:02] <jcastro> we should specifically do github-markdown
[14:02] <jcastro> or whatever the defacto standard is
[14:03] <wesleymason> GHFM is fairly defacto, for better or worse
[14:04] <marcoceppi> jcastro: the md docs I'm working on are doing GFM, with a few extras
[14:06] <marcoceppi> jcastro: it looks like charmworld has a bit of a back log? check again in about 10 mins
[14:06] <jcastro> yeah that was my plan
[14:06] <jcastro> rails/example-complex is missing too
[14:06] <jcastro> I told rick about it
[14:12] <zchander> jcastro: I have included the 6.0.2 version in my ‘version’
[14:13] <jcastro> nice!
[14:16] <themonk> jose: ok i will
[14:43] <overm1nd> guys is there an up-to-date juju windows client? on the site is 1.16.6
[14:47] <marcoceppi> overm1nd: 1.16.6 is the lastest stable juju client
[14:48] <marcoceppi> we don't build devel windows clients
[14:48] <overm1nd> ah ok
[14:48] <marcoceppi> nor do we put devel releases of juju client in homebrew
[14:48] <overm1nd> so is the enviroment file grammare change a bit since last rel?
[14:49] <overm1nd> I get no registered provider for manual
[14:49] <overm1nd> error
[14:50] <overm1nd> when I try to import my juju conf from another machine
[14:54] <marcoceppi> overm1nd: yeah, the provider name changes from null to manual in 1.16 -> 1.17
[14:54] <overm1nd> ok thx
[14:59] <marcoceppi> wesleymason: jcastro: serverdensity is in charm store, fyi https://jujucharms.com/precise/serverdensity/
[15:08] <wesleymason> \o/
[15:12] <bloodearnest> wesleymason: nice work
[15:13] <wesleymason> bloodearnest: ta
[15:15] <jcastro> lazyPower, hey what was our TLDR for the sample rails app?
[15:16] <lazyPower> jcastro: I don't think we have one atm. I haven't had a chance to circle back on it
[15:47] <marcoceppi> hazmat: question about deployer using the -o flag. If a charm doesn't have that key that I'm overriding will it fail or will it just press on?
[15:47] <marcoceppi> I'm assuming the latter, but just want to confirm
[15:50] <frankban> rbasak: we just released a new version of juju-quickstart: https://pypi.python.org/pypi/juju-quickstart
[16:04] <rbasak> frankban: thanks! We're in feature freeze now though. We need an exception I guess?
[16:05] <frankban> rbasak: I think we already asked for an exception, rick_h_ ^^^
[16:05] <rick_h_> rbasak: yes, there's an existing exception, sec I'll get the link
[16:06] <rbasak> I see https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1282630
[16:06] <rick_h_> https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1282630
[16:06] <_mup_> Bug #1282630: [FFE] remove sudo support <juju-quickstart (Ubuntu):New> <juju-quickstart (Ubuntu Trusty):New> <https://launchpad.net/bugs/1282630>
[16:06] <_mup_> Bug #1282630: [FFE] remove sudo support <juju-quickstart (Ubuntu):New> <juju-quickstart (Ubuntu Trusty):New> <https://launchpad.net/bugs/1282630>
[16:06] <rick_h_> yep
[16:06] <rbasak> That's to drop sudo support though, not for a new upstream release.
[16:06] <rick_h_> it ended up juju released an interim release that has our support and we don't need to wait for 1.18
[16:06] <rbasak> I don't see a problem getting an FFe for a new upstream release, but we probably need to modify that existing one or something.
[16:07] <rick_h_> rbasak: sorry, this release drops the sudo support since 1.17.6 has the fixes we needed that were originally targeted at 1.18
[16:07] <rbasak> And explain what exactly changed, etc.
[16:07] <rbasak> rick_h_: please could you document that in the bug? Then we'll need a release team ack.
[16:07] <rick_h_> rbasak: ok will do
[16:07] <rick_h_> frankban: can you catagog the fix in there and mention the retarget from 1.18 to 1.17.6
[16:08] <frankban> rick_h_: sure
[16:08] <rbasak> frankban: a summary of everything that changed from the previous release, please.
[16:09] <frankban> rbasak: will do
[16:15] <jcastro> hey guys, so mbruzek and I are modifying a charm for a local deployment
[16:16] <mbruzek> but we are still seeing the old hook get run.
[16:16] <jcastro> how do we increment the charm version? juju always wants to deploy the charm without our local changes
[16:16] <jcastro> we've tried `juju deploy -u`
[16:16] <Fishy__> delete charm cache if you want to be sure ?
[16:16] <jcastro> do we just bump `revision` up manually?
[16:17] <jcastro> the -u is what clears the cache afaict
[16:19] <jose> jcastro: I always have to destroy my environment and bootstrap again when doing that, if you have a clue it'd be nice to know
[16:20] <marcoceppi> jcastro: what version juju?
[16:20] <marcoceppi> 1.17 or 1.16?
[16:20] <jcastro> yeah we've done that, I am suspecting our JUJU_REPOSITORY is pointing to the wrong place
[16:20] <jcastro> 1.17
[16:21] <jose> oh, bah, I'm using 1.16
[16:21] <marcoceppi> jcastro: then -u is being depricated and not needed
[16:21] <marcoceppi> jcastro: are you switching from charmstore to local?
[16:21] <jcastro> yeah
[16:21] <marcoceppi> jcastro: or has this always been local?
[16:21] <marcoceppi> jcastro: have you used --switch yet?
[16:21] <jcastro> no
[16:21] <jcastro> it's always been local
[16:22] <marcoceppi> jcastro: ah, okay
[16:22] <jcastro> so basically, we are editing the charm on disk
[16:22] <marcoceppi> jcastro: what does juju status show the charm revision at?
[16:22] <jcastro> 5
[16:22] <jcastro> it's supposed to be 6
[16:22] <marcoceppi> jcastro: is revision file set to 6?
[16:22] <jcastro> it is now
[16:22] <jcastro> it was not before
[16:22] <marcoceppi> jcastro: try doing upgrade-charm now
[16:22] <marcoceppi> if that doesn't work then your JUJU_REPOSITORY might not be set properly, but juju should have complained about that
[16:24] <jcastro> found the issue
[16:25] <jcastro> we were deploying from the pristine upstream charm, and not from our local repository where we made the changes
[16:25] <jcastro> jose, juju upgrade-charm normally is what you do
[16:25] <jose> jcastro: even if there's no upgrade-charm hook?
[16:27] <jcastro> I'll let you know next time, already started over
[16:27] <lazyPower> jose: who am I meeting with re: open week presentation in :30?
[16:28] <jose> lazyPower: that's in a month still
[16:28] <lazyPower> wat
[16:28] <jose> :P
[16:28] <jose> 22 April at 18 UTC
[16:28] <lazyPower> i thought it was today!
[16:28] <lazyPower> WOW
[16:28] <lazyPower> clearly I'm on-the-ball
[16:28] <jose> we like to plan things with time :)
[16:29] <lazyPower> and i see on the table on the wiki page, i was anticipating this being shoot from the hip
[16:29] <lazyPower> awesome
[16:29] <jose> I'll still get to all of you guys who will be presenting to let you know who your contact during the event will be
[16:30] <jose> I haven't got my university schedule yet, so I can't promise anything
[16:30] <lazyPower> jose: welp the fact its not today buys me tons of time. Roger dodger
[16:31] <jose> maybe some time to promulgate the mailman charm? :P
[16:31] <jose> jk
[16:31] <lazyPower> Your review will be before I EOD :)
[16:31] <lazyPower> you've waited patiently
[16:31] <lazyPower> that has merit in my book
[16:31] <jose> \o/
[16:32] <jose> well, I'll continue looking into this reddit charm, install hook fails :P
[16:48] <jamespage> marcoceppi, you rock - thanks for the reviews and merges today!
[16:48] <jcastro> marcoceppi, found the problem
[16:48] <jcastro> you won't believe it
[16:48] <jcastro> https://github.com/juju/docs/pull/34/files
[16:49] <jcastro> It's forgettable enough that I felt the need to write it down
[16:49] <marcoceppi> jcastro: wat
[16:49] <jcastro> yeah
[16:49] <jcastro> our hooks were all files
[16:49] <jcastro> because scp follows links, it doesn't copy them over
[16:49] <jcastro> so any charm you copy over with scp that has symlinks for hooks = ouch
[16:49] <marcoceppi> jcastro: interesting
[16:49] <jcastro> you need to either rsync or tar-then-scp
[16:50] <marcoceppi> rsync ftw
[16:58] <Fishy__> cobbler is ruining my life
[17:42] <jose> Pagekite charm submitted!
[17:51] <lazyPower> interesting solution
[17:51] <lazyPower> bookmarking pagekite for later reference
[18:36] <Fishy__> should I worry about this
[18:37] <Fishy__> juju bootstrap WARNING no tools available, attempting to retrieve from https://juju-dist.s3.amazonaws.com/ WARNING picked arbitrary tools &{"1.16.6-precise-amd64" "http://192.168.4.1/MAAS/api/1.0/files/?key=55dd93f8-b44c-11e3-ac66-7054d2ab7b42&op=get_by_key" "60a008598b13effa46ee50fa13bbe9601ad1018bbb5d9eda379f117e14f145ec" %!q(int64=4666968)}
[18:51] <marcoceppi> Fishy__: no, that's just a warning
[19:12]  * zchander won't be scripting/hacking/copying/coding tonight. Just relaxing on the couch with a PS3 controller in my hands ;)
[19:23] <Fishy> Do I need a certain # of nodes enlisted before I can use juju maas?
[19:23] <Fishy> I have 1 now and status fails
[19:30] <marcoceppi> Fishy: you need probably two nodes
[19:30] <marcoceppi> one for bootstrap
[19:30] <marcoceppi> one for a service
[19:33] <Fishy> bummer
[19:34] <Fishy> can I make local LXC nodes and have them enlist with maas?
[19:34] <Fishy> running out of space to put laptops on my desk
[19:34] <Fishy> + i dont want to waste hardware nodes for bootstrap
[19:34] <Fishy> want them LXCs i would think
[19:36] <marcoceppi> Fishy: not lxc, but qemu/kvm, yes
[19:42] <Fishy> virtual box?
[19:44] <marcoceppi> Fishy: no, not really
[19:44] <marcoceppi> virtual box and MAAS don't work together very well
[19:44] <Fishy> bah
[19:45] <sarnold> virtualbox's main selling point seemed to be that you got something slightly better than vnc for graphics...
[19:45] <Fishy> yah I can just point and click admin it in 30 seconds
[19:45] <sarnold> you don't really care about graphics in this case, right? might as well pick the more stable / easier / lighter-weight kvm..
[19:45] <tvansteenburgh> wwitzel3, you're doing maas with virtualbox aren't you?
[19:45] <Fishy> in the past week I have already learned openVZ and LXC
[19:45] <marcoceppi> Fishy: there's a GUI tool for KVM if you want to try that
[19:46] <Fishy> trying to avoid a 3rd VM provider ;)
[19:46] <marcoceppi> OpenVZ isn't very good because it relies on an older kernel
[19:46] <Fishy> ya we want to get rid of it
[19:46] <marcoceppi> Virtuozzo, their commercial product, is much better
[19:46] <Fishy> but some old stuff is on it
[19:46] <marcoceppi> there's virt-manager or somethign like that, which is a GUI to qemu/kvm
[19:46] <marcoceppi> it's like virtualbox, only better ;)
[19:47] <marcoceppi> qemu/kvm at least, and it's compatibile with MAAS
[19:47] <Fishy> ok, installing
[19:48] <Fishy> qemu and kvm are the same thing?
[19:48] <marcoceppi> well, for now yes
[19:48] <marcoceppi> qemu is a generic machine emulator, kvm is the underlying provisioner
[19:49] <marcoceppi> so, MAAS can talk to QEMU which can talk to KVM, and virt-manager is the GUI to create KVM machines
[19:49] <marcoceppi> KVM virtual machines are isolated like virtualbox machines, so you have that full level of virtualization
[19:49] <marcoceppi> it's just a chain of tools to do stuff
[19:51] <Fishy> so i need to make a bridge
[19:51] <Fishy> heavy
[19:52] <Fishy> nat wont do pxe
[19:52] <Fishy> boo
[19:52] <marcoceppi> Fishy: it's not that heavy
[19:52] <marcoceppi> QEMU/KVM think of it as one tool
[19:53] <marcoceppi> it's your virtualizer
[21:24] <Fishy> maas keeps shutting off my servers (that are enlisted but not yet in use)
[21:24] <Fishy> how rude
[21:29] <marcoceppi> Fishy: that's by design :)
[21:30] <Fishy> and the idea is to use WOL when they are needed?
[21:30] <marcoceppi> WOL or whatever power management tool, IMPI, AMT, QEMU, etc
[21:31] <Fishy> heres to hoping one of them works ;)
[21:31] <Fishy> went up from 1 node to 3 nodes, juju status still never returns
[21:34] <Fishy> ok after 10 mins says
[21:34] <Fishy> Error details: no reachable servers
[21:35] <Fishy> which seems to mean the WOL or whatever doesn't work
[21:37] <marcoceppi> Fishy: does the machine in MAAS work with WOL?
[21:38] <Fishy> 1 laptop and 2 kvm VMs
[21:38] <Fishy> see no reason why it wouldnt
[21:38] <Fishy> enabled in laptop bios
[21:44] <jose> marcoceppi: hey, it's good if I submit patches to the proof errors that are in the review queue?
[21:45] <marcoceppi> jose: totally!
[21:45] <jose> cool then, working on a couple atm :)
[21:45] <jose> will file bugs too
[21:46] <marcoceppi> jose: \o/
[21:53] <lazyPower> jose: YES!!!
[21:53] <lazyPower> that would be amazing
[21:54] <jose> lazyPower: well, I have some spare time before starting university and I'm a bit tired of checking and checking the reddit charm without results, so I'll do that instead :)
[21:54] <jose> about the store errors, I can't do much - I can give you a clue that the postfix and mailman ones are because I changed my username
[21:58] <snewpy> is there a way to get the remote unit's IP address during a relation-joined event without specifically passing it as a relation property?
[21:59] <jose> snewpy: I believe `relation-get private-address` gives you that info
[22:01] <snewpy> awesome, thx!
[22:06] <jose> lazyPower, marcoceppi: tells me that I don't have permissions to make an MP?
[22:07] <marcoceppi> jose: how are you trying to propose merge?
[22:07] <jose> marcoceppi: with an MP
[22:07] <jose> or should it be done via a bug? (also filed one)
[22:07] <marcoceppi> jose: that clears it up perfectly!
[22:08] <jose> huh?
[22:08] <marcoceppi> jose: so, what are the targets for the MP
[22:08] <marcoceppi> I'm trying to figure out why it's failing
[22:08] <jose> lp:charms/assaultcube
[22:08] <jose> and lp:~jose/charms/precise/assaultcube/1297529-fix is the proposed branch
[22:09] <marcoceppi> huh, jose can we jump on a hangout so I can see your screen?
[22:09] <jose> sure!
[22:09] <marcoceppi> jose: one sec
[22:40] <jose> marcoceppi: I see a problem on the charm, does config.yaml allow a name that's 2 characters long?
[22:40] <jose> or there needs to be a minimum?
[22:40] <marcoceppi> jose: no
[22:40] <jose> what's the minimum?
[22:40] <marcoceppi> needs to be more than two characters, that's a yaml limitation
[22:40] <marcoceppi> 3
[22:40] <jose> ok, thanks
[22:42] <lazyPower> hey jose, i see you have the mailman charm listed as depends on:  lp:~jose/charms/precise/postfix/trunk
[22:42] <lazyPower> but there's no relationship for this dependency - was it planned but not implemented?
[22:42] <jose> lazyPower: oh, that's not the case anymore
[22:43] <jose> correct
[22:43] <lazyPower> ack. I'll disregard
[22:43] <jose> thanks :)
[23:42] <jose> hey guys, what should I do with a charm which has no maintainer? set the maintainer to charmers?
[23:51] <lazyPower> jose: file a bug for needs maintainer against the charm
[23:52] <jose> ok, in the meanwhile I'll fix the other stuff