[00:30] <_mup_> ensemble/expose-ec2-provider r271 committed by jim.baker@canonical.com
[00:30] <_mup_> Merged trunk
[11:02] <SpamapS> hazmat: I have the ec2->common stuff ready, will push soon now
[12:28] <kirkland> hazmat: awesome, thanks for working with negronjl 
[12:28] <kirkland> hazmat: glad to see we're cranking ;-)
[12:34] <ixxvil> hey sladen , kim0 
[12:36] <etneg> sladen: ping
[12:36] <etneg> kim0: ping
[12:36] <kim0> hey
[12:37] <kim0> wonder what time is it for sladen 
[12:37] <sladen> 13:37
[12:37] <kim0> :)
[12:37] <kim0> cool then
[12:37] <kim0> etneg: how's it going 
[12:38] <sladen> etneg: are you the same as ixxvil?
[12:38] <sladen> etneg: (one disappeared, as the other appeared)
[12:39] <etneg> not too bad
[12:39] <etneg> oh ye
[12:39] <etneg> :D
[12:39] <etneg> did you guys see some rocky guy's logo?
[12:39] <etneg> that looked like an atom
[12:40] <etneg> nobody commented on it, just thought i'd give you a headsup
[12:40] <etneg> http://ubuntuone.com/p/13yI/
[12:42] <etneg> i haent done any new stuff, kinda got tied up but ill do a few today and upload
[12:48] <koolhead17> etneg, capital E would be much better :P
[12:49] <etneg> koolhead17: for which one?
[12:49] <etneg> the one i just posted?
[12:49] <etneg> that's not my design, it's a robbie williamson's concept
[12:50] <koolhead17> etneg, hmm. okey
[12:51] <etneg> robbie@ubuntu.com
[12:51] <etneg> but ye leave comments
[12:51] <etneg> :D
[12:51] <etneg> more options on the table
[12:52] <koolhead17> he comes here too i suppose
[12:53] <etneg> ah ok
[12:54] <etneg> well either way we have more people working on it,good sign
[12:54] <koolhead17> etneg, indeed
[12:54]  * koolhead17 looks at SpamapS 
[12:55] <etneg> i sitll need someone to start coloring mine:/
[13:23] <_mup_> Bug #809319 was filed: zookeeper finding should be the machine provider's responsibility <Ensemble:New> < https://launchpad.net/bugs/809319 >
[13:38] <hazmat> g'morning
[13:44] <niemeyer> hazmat: Yo!
[13:47] <niemeyer> hazmat: How did it go yesterday?
[13:50] <hazmat> niemeyer, pretty good, got some good momentum on the security policy stuff
[13:50] <hazmat> niemeyer, negronjl and i were able to work through some of the deploy issues, afaics it was just an update issue
[13:51] <niemeyer> hazmat: Hmm.. how did the issue go away?  It felt like it was reproduced after a clean bootstrap.. was that not the case?
[13:51] <hazmat> niemeyer, not after updating and doing a clean bootstrap
[13:51] <hazmat> the issue went away
[13:51] <niemeyer> hazmat: Ah, sweet
[13:52] <hazmat> niemeyer, re robbiew's email on weekly releases.. i'm a little wary atm, but i'm also unclear on how often packages get pushed to the distro repo for ubuntu-next (oneiric)
[13:53] <niemeyer> hazmat: Probably not too often
[13:53] <niemeyer> hazmat: Weekly integration releases sounds sensible
[13:53] <hazmat> to me the question would be if we're hitting backwards compatibility issues
[13:54] <niemeyer> hazmat: We have some time to allow for wild backwards incompatible changes in terms of deployments
[13:54] <hazmat> niemeyer, what's involved in making that happen, can the daily build recipe be adjusted to a weekly?
[13:54] <niemeyer> hazmat: We'll soon have to put that in control, though
[13:54] <niemeyer> hazmat: I suggest we address this on the Austin sprint
[13:54] <hazmat> niemeyer, sounds good
[13:54] <niemeyer> hazmat: From then on, it has to handle the situation cleanly
[13:55] <niemeyer> hazmat: Even if that means saying to admin "You can't use that version" in some tricky situations
[13:55] <niemeyer> hazmat: We'll need a hand from real Ubuntu Developers there :-)
[14:03] <koolhead17> hi robbiew 
[14:03] <robbiew> hi
[14:22] <niemeyer> fwereade: Can you please have a look at this branch when you have a sec: https://code.launchpad.net/~hazmat/ensemble/security-principal-def/+merge/67618
[14:22] <fwereade> niemeyer, ofc
[14:32] <robbiew> hazmat: so with this treadmill desk thing you got setup...will we need to move our sprint from the hotel conference room to the gym? :P
[14:36] <hazmat> robbiew, i'm game. while the view might be nicer, the logistics are a bit harder to get a good roundtable setup or whiteboard usage. we might as well just sprinting from the pool treading water ;-)
[14:37] <robbiew> hazmat: hmm...they make waterproof laptops?
[14:37] <SpamapS> they do
[14:38] <hazmat> robbiew, toughbooks probably have a model for that
[14:38] <robbiew> nice
[14:38] <robbiew> hazmat: on the serious side...about how many calories do you burn a day now...or miles walked
[14:40] <hazmat> robbiew, about 6 miles a day walked, i take desk breaks where i work/sit at a desk, i've been trying to start the day with a mile run to kick things off.
[14:42] <robbiew> hazmat: nice
[14:45] <niemeyer> hazmat: Would you mind to have a look at fwereade's branch which is a follow up on the previous conversation: https://code.launchpad.net/~fwereade/ensemble/zkaw-in-provider/+merge/67703
[14:55] <hazmat> niemeyer, sure
[15:12] <fwereade> btw, what's the protocol for merging to trunk?
[15:12] <fwereade> request reviews from hazmat and niemeyer, wait for both, go?
[15:12] <fwereade> well, wait for both to *approve*, I guess ;)
[15:18] <SpamapS> fwereade: btw, welcome. :)
[15:19] <fwereade> SpamapS, thanks :)
[15:19] <fwereade> SpamapS, very glad to be here (and especially *here*)
[15:25] <hazmat> fwereade, basically, the second reviewer is also supposed to set the merge proposal to approved, for work done at the sprint, we're going with one review, to try and keep things a bit more fluid. i typically do a bzr-pipeline when i've got multiple related things in review, so i can keep forward progress on development
[15:25] <hazmat> for related things
[15:26]  * SpamapS is going to have to look into pipelines
[15:27]  * fwereade is looking into the right now :)
[15:28] <fwereade> hazmat, anyway, I'm good to merge now then?
[15:30] <hazmat> fwereade, can you add a separate test for the new provider method
[15:30] <kim0> SpamapS: Howdy Clint. So did you check out Ryan's email from mediawiki. I see this as a good opportunity, and I imagine either you or m_3 should get involved. Any thoughts ?
[15:30] <hazmat> else it lgtm, +1
[15:30] <fwereade> hazmat, ofc
[15:31] <SpamapS> kim0: I nearly spit my turkish coffee out when I read that.. *very* excited about it.
[15:31] <kim0> SpamapS: wow very good :)
[15:31] <kim0> so the ball is in our playground 
[15:32] <kim0> I think we'll need someone to help convert that infrastructure
[15:38] <SpamapS> kim0: I know some ex-wikia people and have met Ryan personally. I'll reach out to them soon and maybe go up there and play with it a bit with them.
[15:38] <kim0> SpamapS: Awesome :) so we're in good hands
[15:38] <SpamapS> Ryan and I think very much alike.
[15:39] <kim0> good stuff indeed
[15:43] <fwereade> hazmat, niemeyer: re tests: a lot of the stuff I want to test is currently in the tests for EC2Connect, and (almost certainly) EC2LaunchMachine and EC2Bootstrap
[15:43] <jcastro> Hi everyone, here's the weekly report so far, anyone have anything to add? http://pad.ubuntu.com/ensemble-report
[15:43] <fwereade> what's the local consensus on where such things should be?
[15:44] <jcastro> kim0: I don't know how to describe william's ec2zookeeper aware thing.
[15:44] <fwereade> jcastro: it's just some preliminary refactoring we think we need before we can do a cobbler provider
[15:45] <fwereade> jcastro: there have been no actual changes in functionality
[15:45] <jcastro> ok
[15:46] <fwereade> hazmat, niemeyer: on one hand, duplication bad: if we end up changing the precise operations performed we need to change tests in several places
[15:46] <kim0> fwereade: Glad you explained it :) indeed I had not idea what it was doing
[15:46] <fwereade> kim0: heh, sorry :)
[15:47] <fwereade> on other hand, redundant verification good: if we didn't have this style of test it would have been much harder to refactor in this specific instance
[15:47] <fwereade> ...but I'm still reluctant to introduce *more* duplication until someone tells me it's a good idea :p
[15:48] <kim0> SpamapS: I can't wait for the storage formulas nfs/ceph/...etc This is gonna rock so hard ;)
[15:50] <hazmat> jcastro, i'm doing some of the initial security implementation work
[15:51] <hazmat> jcastro, else most of what i've been landing has been following stuff up from last week
[15:52] <kim0> hazmat: is the config-set work still in review?
[15:53] <hazmat> kim0, yes.. it hasn't landed yet.
[15:55] <jimbaker> kim0, SpamapS - any thoughts on what's the planned mapping of ceph to the cloud infrastructure? that sounds quite interesting
[16:07] <SpamapS> jimbaker: ceph is a ring.. it should work a lot like Cassandra actually.
[16:08] <SpamapS> jimbaker: the holy grail is to be able to just say 'requires: storage\ninterface: shared-mount' in any program that needs a shared mount point.
[16:08] <koolhead17> hey all
[16:08] <SpamapS> jimbaker: so ceph and nfs and gluster are interchanagable
[16:08] <SpamapS> changeable even
[16:08]  * SpamapS wishes irssi had spell check.. maybe time for a foray into X-chat again.
[16:09] <kim0> koolhead17: hey 
[16:09] <koolhead17> apt-cache showpkg moodle  shows mysql-client as deps but does not install it. Using dbconfig-common for installation throws error saying mysql-client needs to be installed before this process to finish. do i need to file a bug for this?
[16:09]  * kim0 wishes unity had bell support so he can hear irssi's bells
[16:09] <koolhead17> i asked the same on u-server
[16:09] <m_3> SpamapS: do we have an interface list yet?
[16:09] <kim0> r u falling in love with dbconfig-common
[16:10] <m_3> SpamapS: I chose "filestore" and "mount"... we should standardize
[16:10] <SpamapS> m_3: no we *definitely* should standardize though
[16:11] <m_3> storage and mount/shared-mount are great
[16:11] <m_3> does mount need 'master' or is that something for 'shared-mount'?
[16:11] <SpamapS> m_3: the relation name should always be a reference to what function inside the formula it performs..
[16:12] <m_3> SpamapS: right, but filestore and storage would both work
[16:13] <SpamapS> Yeah
[16:13] <SpamapS> m_3: I forget, did I hand off the NFS formula entirely to you or did we agree I should complete it?
[16:13] <m_3> SpamapS: I do like storage better
[16:13]  * SpamapS feels his head wanting to turn hard right, starting the spin...
[16:14] <koolhead17> kim0, well indeed i am
[16:14] <m_3> SpamapS: ha!  I've been working on it, but was expecting to merge... I can finish if you want
[16:15] <SpamapS> m_3: Just push up what you've got into a branch.. I wanna see. :)
[16:15] <m_3> yup, will do... I've been having problems with legal branch names in lp... just using +junk now
[16:16] <m_3> is 
[16:16] <m_3> 'master' there for a reason? or is that just thinking about a 'shared-mount' interface?
[16:17] <koolhead17> SpamapS, so i forget dbconfig-common while writing ensemble formulas :D
[16:17] <SpamapS> koolhead17: well you can use it!
[16:18] <SpamapS> koolhead17: since it knows how to configure the service for database access, its not totally useless. Its just *confusing* is all.
[16:18] <koolhead17> SpamapS, am stuck at phpmyadmin because a dbconfig-common bug which was reported in debian too
[16:19] <SpamapS> that reminds me
[16:19] <SpamapS> adam_g: did you hack the mysql formula to work w/ shared db's yet?
[16:26] <adam_g> SpamapS: yes!
[16:26] <koolhead17> hey obino 
[16:26] <adam_g> SpamapS: i was gonna clean it up just a bit and send a proposal.
[16:27] <adam_g> SpamapS: https://code.launchpad.net/~gandelman-a/ensemble/mysql   ive been using it a bunch. works well
[16:28] <SpamapS> adam_g: *sweet* .. I think it will be useful for phpmyadmin as well
[16:28] <adam_g> SpamapS: cool. ill send a merge proposal before lunch hopefully
[16:29] <SpamapS> adam_g: no rush.. just wanted to see how it was going
[16:29] <adam_g> one thing ive noticed, tho
[16:30] <adam_g> maybe this is the only formula that has multiple peers relating to it? but, the list of related peers for mysql unit in 'ensemble status' only lists the last related peer, not a list of all peers related.. if that makes sense
[16:30] <SpamapS> adam_g: I noticed it too
[16:30] <SpamapS> adam_g: I think the status output is just masking the actual list of relations
[16:30] <adam_g> obviously not a huge deal, but it would be convinient to have them listed there as well
[16:30] <SpamapS> adam_g: I think I saw a bug on that, did you file that?
[16:30] <adam_g> SpamapS: no, i haven't
[16:31] <SpamapS> adam_g: status' output is critical actually.. for a number of reasons.
[16:31] <m_3> adam_g: dude, the shared-db-relations look great
[16:31] <adam_g> cool thans
[16:32] <adam_g> ive also got a rabbitmq formula that needs a bug worked out and ready to submit, and a buncha nova stuff
[16:32] <adam_g> (nova-compute, nova-cloud-controller, glance)
[16:32] <SpamapS> adam_g: swift?
[16:32] <adam_g> no swift yet, was gonna try to tackle that this week
[16:32] <SpamapS> seems swift should be pretty straight forward as a formula.. the consumers just have to list and connect to the nodes right?
[16:33] <jimbaker> SpamapS, i take it that ceph would simply use the instance storage?
[16:33] <adam_g> SpamapS: well, yeah. but constructing the swift proxy and all of the storage nodes is a bit less trivial. its almost like building a raid array
[16:33] <SpamapS> jimbaker: yeah I think thats the simplest way
[16:34] <SpamapS> adam_g: sounds like I need to re-read the swift architecture page again
[16:34] <jimbaker> SpamapS, yeah, that does keep it simple. i wonder how that works out costwise in comparison to EBS
[16:35] <SpamapS> jimbaker: Actually I think I'd recommend we use EBS root instances.
[16:35] <SpamapS> jimbaker: at least until we have a better storage management story.
[16:36] <jimbaker> SpamapS, yeah, that's why i was curious :)
[16:37] <SpamapS> RoAkSoAx: re the orchestra-provider branch, I'm playing with it now.. can you try running './test ensemble.ftests.test_orchestracontrol' ? does that work with the environments.yaml I pastebinned earlier?
[16:40] <RoAkSoAx> SpamapS: let me check
[16:46] <RoAkSoAx> SpamapS: ZOOKEEPER_PATH what should I set in the environment variable
[16:46] <SpamapS> RoAkSoAx: hm shouldn't need that.. 
[16:47] <SpamapS> RoAkSoAx: do you have zookeeper installed?
[16:49] <RoAkSoAx> SpamapS: yeah working now
[16:49] <kim0> SpamapS: m_3 You are invited to add Ensemble sessions to https://wiki.ubuntu.com/UbuntuCloudDays/Timetable
[16:51] <jcastro> so are we keeping the principia name or not? I'd like to just rename the wiki page to /Formulas
[16:52] <koolhead17|afk> robbiew, saw the ensemble logo idea of yours. Capital E would be better :P
[16:54] <robbiew> koolhead17|afk: heh...that's pretty easy to switch...but I thought the lower case looked better
[16:55] <kim0> reminds of IE though :)
[16:56] <SpamapS> somebody should maybe grab this https://launchpad.net/formulas
[16:57] <SpamapS> robbiew: Oh! yeah, the logo is *sweet*. As much as I like the oxygen reference with the number of electrons.. I think it might be too busy ;)
[16:57] <jcastro> SpamapS: I'll snag that on launchpad
[16:58] <SpamapS> RoAkSoAx: http://pad.ubuntu.com/orchestra-setup-for-ensemble .. working on it now
[16:58] <jcastro> lp.net/ensemble-formulas perhaps?
[16:58] <robbiew> SpamapS: yeah...had that thought too
[16:58] <robbiew> that's easily reduced though
[16:58] <robbiew> maybe just three
[16:58] <robbiew> to hint at the heads in the ubuntu logo
[16:59] <RoAkSoAx> SpamapS: awesome, thank you!
[16:59] <robbiew> that's actually how I originally had it
[17:00] <kim0> m_3: thanks for the session \o/
[17:00] <smoser> RoAkSoAx, so is the pad doc there working for you?
[17:00] <RoAkSoAx> smoser: yes
[17:01] <smoser> cool. i will reproduce here too.
[17:06] <m_3> kim0: np... lemme know if you'd like another topic (i.e., if we need one for data instead)
[17:07] <m_3> kim0: I figured maybe the etherpad-lite node app would be cool to see
[17:12] <jcastro> what's the preferred license of a formula? Ideally whatever the upstream project's license is I would assume?
[17:19] <m_3> jcastro: maybe more open than that... formulas won't nec be written by the people maintaining the upstream project
[17:20] <jcastro> m_3: right, so in general we don't really care as long as it's open? Like we don't have an overarching guideline?
[17:22] <smoser> RoAkSoAx, i'm guessing its just user error
[17:22] <smoser> but /etc/apache2/conf.d/dav.conf doesnt work for me
[17:22] <smoser> Syntax error on line 5 of /etc/apache2/conf.d/dav.conf:
[17:22] <smoser> Invalid command 'Dav', perhaps misspelled or defined by a module not included in the server configuration
[17:26] <SpamapS> sudo a2enmod dav
[17:26] <SpamapS> adding
[17:28] <smoser> ok. so that was fixed.
[17:28] <smoser> now Unknown DAV provider: filesystem
[17:29] <SpamapS> hrm
[17:29] <m_3> a2enmod dav_fs?
[17:30] <SpamapS> maybe
[17:31] <m_3> jcastro: we want to promote formula re-use... don't know what else
[17:32] <SpamapS> jcastro: the formula has to be redistributable under a free license so that we are in the clear and users know they can use it w/o any problems.
[17:35] <SpamapS> smoser: thats printing when you restart apache?
[17:35] <smoser> works now.
[17:35] <smoser> needed dav_fs
[17:35] <smoser> updated etherpad
[17:37] <SpamapS> Note that I just updated the pre-seed template to point at the right 'repo' instead of 'pkgs'
[18:15] <_mup_> ensemble/security-node-policy-def r271 committed by kapil.thangavelu@canonical.com
[18:15] <_mup_> implement security policy, returns acls for new nodes by path.
[18:33] <niemeyer> I love robbiew's logo: http://ubuntuone.com/p/148H/
[18:35] <m_3> niemeyer: +1
[18:36] <m_3> goes right along with the physics theme... "canonical ensemble"
[18:36] <m_3> we really do need some options that allow for "grand canonical ensemble" or "micro canonical ensemble"
[18:40] <SpamapS> Ensemble: Now w/ less electrons. ;)
[18:40] <SpamapS> niemeyer: +1 from me too.. I think we should adopt it.
[18:41]  * SpamapS begins work on creating an "Ensemble Man" out of The Simpsons' Radioactive Man
[18:41] <m_3> like little ladder operators... from the vacuum state to an excited state in two shakes
[18:41] <m_3> SpamapS: rofl
[18:42] <m_3> SpamapS: set to the tune of 'triangle man' from theymightbegiants
[18:44] <SpamapS> haha ensemble man beats cranky-ops man. ensemble wins
[18:44] <SpamapS> cranky ops man hates ensemble man. they have a fight. ensemble wins. ensemble man.
[18:45] <m_3> nice
[18:46] <m_3> ok, we'll have a recording session in Austin
[18:46] <SpamapS> you bring the accordion
[18:47] <m_3> tub-bass is more my talent
[18:48] <_mup_> Bug #809498 was filed: intended providers.ec2 submodule visibility is unclear <Ensemble:New> < https://launchpad.net/bugs/809498 >
[18:52] <robbiew> apparently my only key contribution to ensemble will be the logo
[18:52] <robbiew> lol
[18:58] <SpamapS> robbiew: don't forget you also gave us a theme song
[18:59] <SpamapS> Or, I guess, its a mission statement more than a song. ;)
[19:02] <SpamapS> RoAkSoAx: any progress?
[19:02] <m_3> negronjl: the masters/slaves aren't set by the package, but it evidently doesn't matter... working fine so far
[19:02] <zul> ensemble queries the uec-images.ubuntu.com by default right? how do we get to use our own images
[19:03] <_mup_> ensemble/expose-ec2-provider r274 committed by jim.baker@canonical.com
[19:03] <_mup_> Merged trunk
[19:03] <SpamapS> zul: right now ensemble only uses ec2
[19:03] <SpamapS> zul: oh sorry I misunderstood your question
[19:03] <SpamapS> zul: there's a config parameter in environments.yaml
[19:04] <SpamapS> zul: where you set the ami
[19:04] <zul> yeah i tried that i didnt get any further 
[19:05] <zul> SpamapS: http://pastebin.ubuntu.com/642836/
[19:05] <RoAkSoAx> SpamapS: just got back from lunch
[19:05] <RoAkSoAx> working on it now
[19:06] <zul> SpamapS: and my environment http://pastebin.ubuntu.com/642837/
[19:07] <SpamapS> RoAkSoAx: I updated the kickstart template again
[19:11] <SpamapS> zul: that looks more like a problem connecting to the ec2-uri than the ami
[19:11] <SpamapS> if not, then thats a crappy error message
[19:11] <SpamapS> zul: give it '-v' to get a full backtrace
[19:11] <zul> SpamapS: yeah i figured out what is wrong with that error message different ip now trying on the bucket stuff
[19:11] <SpamapS> as in ensemble -v bootstrap
[19:12] <zul> now it cant find the s3 bucket
[19:13] <RoAkSoAx> SpamapS: k
[19:13] <jcastro> SpamapS: when you have a few minutes like when you take a break or something can we skype or google hangout? I have some dumb questions for ya
[19:18] <m_3> kim0: that 'getting started with hadoop on ubuntu' blog post simplifies a bunch
[19:26] <SpamapS> jcastro: still trying to get out the door to eat.. how about in about 1 hour?
[19:26] <jcastro> SpamapS: sure, whenevs
[19:26] <serue> SpamapS: go eat!
[19:27] <serue> forget that, give in and call dominos
[19:28] <_mup_> ensemble/expose-ec2-provider r275 committed by jim.baker@canonical.com
[19:28] <_mup_> Refactored _ensure_groups
[19:28] <RoAkSoAx> SpamapS: zookeeperd should also be installed and running right?
[19:36] <kim0> m_3: simplifies? it sounded like it needed simplification :)
[19:40] <_mup_> ensemble/expose-provider-ec2 r276 committed by jim.baker@canonical.com
[19:40] <_mup_> Fix callback refactoring
[19:44] <m_3> kim0: yeah, dude... rocks
[19:44] <kim0> m_3: did you have time to write that readme file you mentioned
[19:44] <smoser> SpamapS, http://pad.ubuntu.com/orchestra-setup-for-ensemble . 'ensemble-branch' should probably match the orchestra branch, rigth?
[19:47] <m_3> kim0: just ran through the demo and am writing it up now
[19:48] <m_3> kim0: still a little ugly... references +junk repos, and lots of steps that won't be there after release
[19:54] <SpamapS> smoser: yes but thats actually not important as that functionality is currently disabled. :-P
[19:56] <SpamapS> smoser: the way to achieve the same thing is to put that branch's packages in the repo
[19:56] <SpamapS> which also has me thinking that there's work to be done in making ensemble deploy itself more cleanly.
[19:57]  * niemeyer mumbles something about cloud-init
[20:02] <SpamapS> Right, I think cloud-init may be the right way to do what I'm thinking. I'm more concerned with making sure ensemble can install without access to ppa.launchpad.net or bazaar.launchpad.net.
[20:03] <SpamapS> I was just thinking that the provisioning agent should be able to encapsulate the desired ensemble version and deliver it to the machines.
[20:03] <SpamapS> Probably by setting a repo address and serving said repo itself... and then it can just build the .deb or .egg or whatever and serve it up.
[20:08] <niemeyer> SpamapS: I believe hazmat has already fixed part of that porblem in trunk
[20:10] <niemeyer> SpamapS: In revision 266, more specifically
[20:12] <niemeyer> "porblem" is an awesome typo, btw
[20:12] <SpamapS> Sounds delicious
[20:14] <SpamapS> niemeyer: right, so the private cloud story is to also setup a bzr server available to your machines. I'm thinking that it should be part of the provisioning agent to just do that automatically.
[20:14] <niemeyer> SpamapS: I don't think I understand what you mean thre
[20:15] <niemeyer> SpamapS: The private cloud story should work the same way as the public cloud story
[20:15] <niemeyer> SpamapS: As far as protocols and procedures go
[20:15] <niemeyer> SpamapS: One talks to public services, the other doesn't
[20:15] <SpamapS> niemeyer: it has no access to lp:ensemble or ppa:ensemble/ppa .. just a local mirror of ubuntu.
[20:16] <niemeyer> SpamapS: Yes, and we won't need that.. trunk is able to deploy Ensemble without bzr branches available
[20:16] <niemeyer> SpamapS: It needs packages, of course, and we'll need to ensure there is a repository available
[20:16] <niemeyer> SpamapS: But that's somewhat of a need anyway.  Or at least that's my understanding
[20:17] <SpamapS> niemeyer: yeah, the story is handled.. I'm just not entirely happy with it at the moment. Still too dependent on ppa/lp ..
[20:17] <niemeyer> SpamapS: We don't depend on it.. we depend on an archive
[20:18] <SpamapS> are you guys going to EOD at 17:00 or 18:00 ? I still haven't eaten.. so much to handle after 2 weeks away from home. :p
[20:18] <niemeyer> SpamapS: It's trivial to implement support for looking at a different archive
[20:18] <niemeyer> SpamapS: Oh, 18+, please go for it
[20:18] <SpamapS> ok.. bbiab
[20:18] <niemeyer> SpamapS: Enjoy
[20:29] <jcastro> kim0: alright! our first community question, http://askubuntu.com/questions/52840/differentiator-between-ensemble-and-front-runners-puppet-and-chef
[20:33] <_mup_> ensemble/expose-provider-ec2 r277 committed by jim.baker@canonical.com
[20:33] <_mup_> Remove default inbound fw rules
[21:20] <SpamapS> jcastro: wanna chat now?
[21:20] <m_3> jcastro: first question cuts right to the chase
[21:22] <SpamapS> jcastro: btw I'm going to answer that question with, hopefully, a short answer
[21:23] <jcastro> SpamapS: heh
[21:23] <jcastro> SpamapS: yeah I can chat now
[21:24] <SpamapS> jcastro: I have yet to try google's video chat.. and with Skype being under the scourge of new ownership... I'm anxious to give it a whirl
[21:43] <m_3> kim0: here's my first pass at a hadoop getting started post http://blog.markmims.com/ensemble/2011/07/12/hadoop-on-ubuntu
[21:43] <m_3> feedback from all pls... kim0 lemme know if you want something done differently
[21:58] <jimbaker>  m_3, nice
[22:07] <m_3> jimbaker: thanks... trying to walk the balance between short/sweet and too many 'ensemble status' snippets
[22:09] <jimbaker> m_3, you may also want to show ensemble status using a filter
[22:11] <jimbaker> m_3, we probably should take an arg for add-unit so you don't have to do that list. i think this has been discussed before
[22:12] <jimbaker> m_3, lastly - you can do add-relation as soon as the services on each side of the relation have been deployed. no need to wait
[22:15] <SpamapS> m_3: have you tried the ensemble status svg output?
[22:15] <m_3> SpamapS: is that the dot one?
[22:16] <m_3> jimbaker: awesome thanks... that saves a step of waiting/checking
[22:16] <SpamapS> jcastro: btw, here is the draft docs for how service configs should work https://ensemble.ubuntu.com/docs/drafts/service-config.html
[22:16] <_mup_> Bug #809599 was filed: ensemble add-unit should support adding more than one unit at a time <Ensemble:New> < https://launchpad.net/bugs/809599 >
[22:17]  * SpamapS also wants a "provision-machines" command so he can just tell the provision agent to start 10 ahead of time.
[22:18] <m_3> I also _so_ want a --stack arg to deploy
[22:18] <m_3> enseble deploy --stack svc1 svc2 svc3
[22:19] <jimbaker> m_3, the other thing that comes to mind is that ideally the formula for hadoop should leave it in a good state such that it can always have jobs run against it w/o observing ensemble status by a user
[22:19] <m_3> but I'm so lazy I've got two character aliases for all of this
[22:20] <m_3> jimbaker: I don't follow
[22:20] <jimbaker> m_3, i have my own deploy-stack alias ;) - basically you should be able to do everything in that listing all at once, as long as the commands are run sequentially
[22:20] <jimbaker> m_3, that is, alias deploy-stack='ensemble status && ensemble deploy --repository=examples mysql && ensemble deploy --repository=examples wordpress && ensemble add-relation mysql wordpress && ensemble status'
[22:20] <m_3> the 'ensemble status' observations are to wait until the service is related before trying to ssh in and use the thing
[22:21] <jimbaker> m_3, yeah, i do wonder about using ensemble ssh in this way. it's really meant for debugging a system
[22:22] <m_3> jimbaker: there are lots of times that status reports the service started and the relation up, but there's still another several minutes (literally) of stuff to go before the relation is really up
[22:22] <jimbaker> m_3, maybe the right way to do this is have some sort of job submission service... not certain
[22:22] <m_3> dunno
[22:23] <SpamapS> isn't there a web interface for hadoop?
[22:23] <m_3> yup, but that's fer sissies
[22:23] <m_3> yeah we can show that too
[22:23] <jimbaker> m_3, precisely. but if you have a service that depends on hadoop being in a good state, there's no need to poll ensemble status. that might be the web interface SpamapS mentions, i don't know
[22:23] <m_3> I was just trying to reproduce the seminal posts on the topic... only changing ensemble
[22:23] <jimbaker> m_3, definitely it would be nice to have the web interface demonstrated
[22:24] <_mup_> Bug #809607 was filed: EC2-specific code is mixed in with generic machine-launching code <Ensemble:New for fwereade> < https://launchpad.net/bugs/809607 >
[22:24] <SpamapS> If ssh is the normal way to use it.. then I think ssh is fine.
[22:25] <jimbaker> SpamapS, certainly a reasonable point
[22:25] <SpamapS> But maybe ssh is the normal way its used because it has always been a PITA to get more structured access methods setup
[22:26] <m_3> yeah, I'd imagine the best way to use it would be from your laptop... letting other tools do the ssh-ing for you
[22:27] <m_3> BTW, these use cases are crying out for osx ensemble tools... lots of people use ubuntu only in the cloud
[22:28] <jimbaker> m_3, as far as i know, ensemble works fine on os x
[22:28] <SpamapS> Yeah I'd be surprised if it didn't.
[22:28] <jimbaker> m_3, although i haven't tried for a while
[22:28] <SpamapS> python setup.py
[22:28] <SpamapS> tho maybe there are 2.7'isms now
[22:28] <m_3> was just thinking of the friends I would send the post out to
[22:28] <SpamapS> I think Lion may have 2.7
[22:28] <m_3> good deal of them develop on mac but use ubuntu for cluster deployments
[22:28] <jimbaker> definitely depends on 2.6
[22:29] <SpamapS> jimbaker: Snow Leopard has 2.6
[22:30] <jimbaker> SpamapS, cool. as you mentioned, it might also be at 2.7. not sure. i should get out my MBP and try out the test suite again
[22:31] <SpamapS> We actually should setup jenkins tests and have a mac slave running somewhere
[22:31] <jimbaker> SpamapS, that would be very nice
[23:45] <SpamapS> Hmm.. I wonder if the test suite will run in a buildd's isolation..
[23:47] <_mup_> Bug #809634 was filed: Ensemble should allow additional user-defined userdata/cloud-config <Ensemble:New> < https://launchpad.net/bugs/809634 >