[00:02] marcoceppi: setting up that control env now [00:02] should be done for your morning [00:06] * m_3 making fun of one of your keys though... "Windows"... harumph [00:06] :) [00:06] m_3: heya, sooo check this out , been working on / tweaking a theme for a new site I've been tinkering with launching a week or so … themes only about 80% done or so, but thats not the cool part … check out this hack ( note the comment system ) http://www.cloudhero.net/hello-world ( most of the content is just dummy content while I work on the theme ) [00:09] its got the G+ commenting system thats only been released for blogger, and only a day or so there even … and that is a self hosted wordpress.org install on RAX using it :P [00:10] * imbrandon is happy with himself, so much so infact he is making it into a WP plugin for others. [00:12] imbrandon: oh, nice [00:12] imbrandon: yeah, that looks great [00:12] add the plugin to the wp charm too! :) [00:12] :) ty still rough edges but its almost there [00:12] m_3: for sure :) [00:13] like the theme in general too...not just the comments bit [00:13] nice and clean [00:13] thanks :) [00:13] its the first one i've done from scratch in a long time [00:13] m_3: sounds good, how will I know the address? [00:13] well its still bootstrap based, but barely [00:14] marcoceppi: still in progress :)... I'll send you the node once I have it bounced [00:14] marcoceppi: I'm adding the env config so you can pull that from the node once it's there [00:14] m_3: awesome, I'm curious to see if this works properly now so I'll check back after the gym [00:14] marcoceppi: that way you can control it too... and your keys get injected into everything (tpaas) in that env [00:15] marcoceppi: ack [00:15] m_3: \o/ [00:29] m_3: here is alot of the elements you dont see on the page as well, developing it as a full theme … http://www.cloudhero.net/misc/styleguide.html [00:31] about half of the form elements are still funky ( select, combo box, checkbox[alignment] ) and still adjusting the colors a bit … but yea i'm happy with it over all too, tis something fresh to work on that dosent seem like a cheap copy of something else :) [00:42] imbrandon: ack === wedgwood is now known as wedgwood_away === defunctzombie is now known as defunctzombie_zz === defunctzombie_zz is now known as defunctzombie [12:40] what causes "error: cannot log in to admin database: auth fails" ? [12:51] mattyw: ^did you get an answer to that error when you ran into it? [12:53] (looking at https://lists.ubuntu.com/archives/juju/2013-April/002301.html attachment) [12:54] evilnickveitch: possibly trying to deploy before stuff is ready, what were the steps you took to get that error? [12:56] hmmm. well, just recently - "juju bootstrap" followed by "juju status". so... [12:58] smgz, sorry - just in a call [12:58] presumably just the current breakage then, not sure which of them caused that [12:58] could be the upstart/cloudinit one or something else [12:58] smgz ok, was just curious :) [12:59] are you running from the devel ppa, and have you updated recently? the package from yesterday should be okay [12:59] ...then the issue is the tools in the bucket aren't updated yet... [13:00] smgz - ah, where should i be getting it from, just to make sure [13:01] https://launchpad.net/~juju/+archive/devel [13:02] smgz, I seem to remember that I was trying to do juju status too quickly [13:02] yeah, that's the one i have. I will make sure it is up to date [13:03] only built latest at the end of yesterday [13:05] evilnickveitch: you will get that error if the bootstrap instance has failed to bootstrap successfully [13:06] evilnickveitch: can you try ssh'ing to that instance (you can't use juju ssh for that though) and looking at the contents of /var/log/cloud-init-output.log [13:06] rogpeppe1, thanks. Some more investigating to do. [13:07] rogpeppe1: you should really make that error less lame [13:07] evilnickveitch: yeah. i think we should probably change that error message [13:07] where you=we [13:07] smgz: snap [13:07] smgz: it's bad because clients connect directly to mongo [13:07] smgz: in the near future, command line clients will connect to the API [13:08] smgz: so you won't get that error - you'll just get endless "connection refused" messages, which is arguably better, i suppose [13:09] evilnickveitch: the "auth refused" error means that the bootstrap instance got as far as starting mongo at least. [13:09] well, no, but I need to persuade you guys that bootstrap should be console-log aware still [13:09] smgz: yeah, i agree, but it's awkward to do [13:10] smgz: the command line tools can't know when the environment is bootstrapping vs when it's genuinely unavailable [13:10] they can, for several common classes of problems [13:11] if you don't get to cloud-init's happy message, you know something has gone wrong [13:11] smgz: i suppose juju bootstrap itself could know; perhaps juju bootstrap --debug --wait could wait until the instance comes up, ssh to it and tail -f cloud-init-output.log [13:12] right, and then make --no-wait --quiet the non-default passable flags :) [13:12] smgz: juju status on the other hand has no idea if it's waiting for the environment to bootstrap [13:12] you don't need to ssh to get the log [13:12] smgz: no? [13:12] you just call into the nova api (on openstack at least, ec2 has the 4 minute delay thing or whatever) [13:13] smgz: to get any log file on the system? [13:13] no, to get the log you care about (dmesg + cloudinit redirection) [13:13] smgz: the one that i find all the useful info in is cloud-init-output.log, which i don't think is the one you're talking about there. [13:15] there's this nice little line in our cloud config, that goes like this: [13:16] output: {all: '| tee -a /var/log/cloud-init-output.log'} [13:16] smgz: do you think we should change that? [13:17] or, in the go code, environs/cloudinit/cloudinit.go line 183: [13:17] c.SetOutput(cloudinit.OutAll, "| tee -a /var/log/cloud-init-output.log", "") [13:17] smgz: or does the output also end up in the other log. i'm afraid i am shamefully ignorant of the cloudinit detais [13:17] details [13:18] right, what you see in cloud-init-output.log also appears in the console log. [13:18] smgz: ah, ok [13:19] smgz: i wonder if it might be nicer to have a bootstrap-log command. that way even if i bootstrap silently, i can later inspect what went on in the bootstrap process [13:20] nicer than having bootstrap just working? no. in addition, perhaps. [13:21] smgz: i'm not sure what you mean by "just working" there. [13:21] erroring when there's an error, with a clear message, returning 0 when it succeeds. [13:22] smgz: i'm not sure i want the bootstrap command to wait for minutes by default [13:22] we'll have this argument in a few weeks :) [13:23] smgz: i think i'm on niemeyer's side on this on [13:23] this one [13:24] smgz: if the bootstrap process was more reliable, i'm not sure we'd be as concerned about this. there are definitely some places where a retry loop could help things (for instance the metadata service can fail transiently in ec2) [13:42] say I want to fork a charm (because I want to add an interface to it or something) after I've deployed it. can I switch the charm or is a redeploy necessary? [13:45] orospakr: not really. There's a bug about not being able to upgrade a charm from the store using a local repo [13:46] oh wow, yeah, that's the feature I'd want. well, so long as there's already a ticket filed. :) [13:46] So if you've always deployed it from your local repo you can use juju upgrade-charm to update the charm to the newer version, but if you deploy from store then try to upgrade from local - no go [13:46] alright, here's a fun question: what is Canonical's business model for this project? consulting? [13:46] orospakr: https://bugs.launchpad.net/juju/+bug/1040210 [13:46] <_mup_> Bug #1040210: can't upgrade a store-deployed service from a local repo

[13:49] hi, there seems to be a packaging problem in pyjuju in raring [13:49] zookeeper is "suggested", as is apt-cacher-ng [13:49] but lxc deployments won't work without it [13:50] is that expected? [13:50] hm, where is the reference documentation of all the fields permissible in charm metadata? [13:52] ahasenack: yes. you can use juju without the lxc provider, why should those people have to install zookeeper locally? === smgz_ is now known as smgz [13:53] smgz: ok, makes sense [14:01] ah, probably https://juju.ubuntu.com/docs/charm.html === wedgwood_away is now known as wedgwood === gianr_ is now known as gianr === defunctzombie is now known as defunctzombie_zz [14:47] what's the best way to automate charm upgrades? the goal here is some form of continuous deployment. :) [14:58] orospakr: bump 'revision', 'juju upgrade-charm service-name' , the upgrade charm hook will run on all units in parallel [15:11] SpamapS, okay. I figured that would be the approach. thank you. :) === rogpeppe3 is now known as rogpeppe [15:36] m_3: do you have that text file from your charm school section? the one where you had an agenda, etc. [15:36] or did you just generate that on the fly? [15:37] marcoceppi: 1 week warning on LISA13 submission deadline [15:38] jcastro: thanks, I've got a draft I'll send over to you if you don't mind giving it a once over [15:38] fo sho [15:38] m_3: Strata deadline is 5/16 [15:47] jcastro: one sec [15:48] hey marcoceppi [15:48] jcastro: yo [15:49] we need to do a virtual charm school for 2.0ish [15:49] cool [15:49] how does next Friday float for you? I'm thinking G+ [15:50] jcastro: that sounds fine to me [15:50] ok I'll schedule something [15:54] ok everyone [15:54] I've redone the messaging around 2.0 timeline [15:54] https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AoW1nhI7IMt3dGc1dmN6YUpxVXBidlYyX3VNOXNYclE#gid=0 [15:54] this gives us goals as to what to talk about based on when things land in 2.0 [15:54] and we have "general advocacy" on top of that [15:54] so if like, a milestone slips in core we can do other stuff === Guest92449 is now known as balloons [17:01] jcastro: that was one-off... I can reproduce it if you want [17:01] jcastro: usually just make notes for myself before each talk... based on the anticipated audience [17:03] m_3: yeah so what I'm going to do [17:03] is break up a charm school into "15 minute" chunks [17:03] and then write them all down [17:03] smart [17:03] so we can assemble them like legos [17:04] so like "this is not a toy example" is one [17:04] I can reproduce my general notes [17:04] maybe next week [17:04] yeah [17:04] convert them to video segments [17:04] :) [17:04] relation sequencing [17:04] managing service lifecycle [17:05] adding and removing relations [17:05] anatomy of a charm [17:05] service config [17:05] I like a "juju basics" right up front... "the point" [17:05] right [17:06] then charms, then advanced juju [17:07] right [17:55] sounds like what http://lullabot.com does with http://drupalize.me … its a huge hit [17:56] most vids are like 10 to 12 min but then they combine for an overall topic of about 1.5 to 2 hours total [17:57] jcastro / m_3 / marcoceppi ^^ [17:58] http://drupalize.me/videos/overview-drupal-theming <-- like that one on D7 theming is 7 min [18:01] imbrandon: yup... exactly [18:01] trick imo is to keep each vid to a single topic [18:01] one problem at a time [18:02] then it's easier to tag/search for what you want [18:02] and link from askubuntu and jujudocs [18:02] less seeking in the vid too trying to get to "the good part" whatever that is at the moment [18:05] the actual drupal "distribution" ( read: drush makefile ) that lullabot uses for drupalize.me storage and playback interface is opensource / well maintained too , should you all decide u wanted to use it … i'm sure something less complex to begin with tho [18:05] even just a wiki with youtube links is a start [18:07] * imbrandon heads back to lurking mode and off to do some more work/tweaking on cloudhero === defunctzombie_zz is now known as defunctzombie [20:36] jcastro: m_3: http://www.openstack.org/summit/portland-2013/session-videos/presentation/juju-with-openstack-workshop [20:36] :) [20:37] Thanks! I was wondering when that was going to come up [20:37] will share right after this call [20:53] robbiew: thanks [20:54] * m_3 watching now [21:07] http://www.youtube.com/watch?v=YenD4oxfEa4 [21:07] is anybody else getting a "your browser doesn't recognize the video format blah blah" on this page? [21:08] jcastro: nope, it works fine here [21:08] man, I do say "Ummmm" too often in charm schools === prefixed is now known as HAPPYFUNBALL [21:22] works good for me [21:22] ok posted to the world [21:22] 43 views so far [21:23] I'm ~45 mins in, great job so far [21:27] I am glad I switched to the gray ubuntu shirt [21:27] instead of those white snowball polos they had [21:30] lol [21:32] jcastro: ++ [21:33] jcastro: i get the format blah message in firefox [21:33] mwhudson: do you have flash installed? [21:33] yes, but i think i have the "html5 trial" or whatever enabled [21:34] there is a link to youtube.com/html5 where the video should be [21:35] jcastro: I haven't played w/ juju much on an openstack setup...how is it for deployment there on grizzly/havana stuff shaping up? [21:35] all my juju testing has been on ec2 [21:35] scuttlemonkey: you should be good to go [21:35] the openstack provider doesn't do constraints yet I don't think [21:35] cool [21:35] ah [21:35] but they'll be doing like biweekly releases of core now [21:36] nice [21:36] and the nice thing is juju is upgradable now [21:36] so you can wait for what you need, then upgrade [21:36] yeah, my plan is to move my entire test rig over to DreamCompute [21:36] without tearing it all down [21:37] since I'm on the hook for an in-ceph-tion-y talk about deploying ceph on ceph there [21:37] that's great news [21:37] yeah so the idea is [21:37] if you want a core feature faster [21:37] whine more [21:37] while it isn't hard to destroy environment on a test rig...the ability to have many other things running live will be happy-making [21:37] hahaha [21:37] we're almost to feature parity so sooon we'll be moving forward instead of trying to reach the line of scrimmage again [21:38] well in that case I will be the squeakiest wheel that ever squeakied :) [21:38] but first I need a platform...so I'll go squeaky at Dreamhost first [21:39] yeah I am waiting for Rackspace's cloud to be fixed so we can run on there [21:39] but they posted how they plan on getting closer to trunk or whatever, so the openstack provider should Just Work there soon [21:39] awesome [21:40] aight, time to go hunt down some dinner. Great vid [21:42] ta [21:42] I'll ping you later, I should get a list of things you want from you [21:43] and then we can bug mramm together [21:53] Is there a video tutorial I should watch to learn how to write charms? === wedgwood is now known as wedgwood_away