[08:34] <kiranm> ensemble status results in 'connection timeout' or 'broken pipe'. Running in verbose mode shows the the messages - http://paste.ubuntu.com/635647/
[12:52] <_mup_> Bug #803852 was filed: 64-bit instances and large instances <Ensemble:New> < https://launchpad.net/bugs/803852 >
[12:53] <_mup_> Bug #803855 was filed: peer hooks are not invoked <Ensemble:New> < https://launchpad.net/bugs/803855 >
[13:23] <hazmat> kiranm, hmm.. if you retry do you get the same error, ie is it a persistent problem, also
[13:26] <kiranm> hazmat, it turned out to be my corporate firewall blocking outbound traffic. when i tried on a different setup it is working fine. bootsrap, deploy mysql wordpress works fine. but add-relation fails with ambigious endpoints.... i'm using formulas from principia-tools and not from the examples directory
[13:35] <kiranm> hazmat, let me try the whole sequence again - deploy mysql, deploy wordpress, check status, add relation
[13:44] <hazmat> kiranm, there might be some new relations types in the mysql formula
[13:44] <hazmat> which would requires specifying the relation names
[13:45] <kiranm> hazmat, alright let me check with the example formulas first
[13:46] <_mup_> Bug #803866 was filed: On ambigious relation endpoint error from add-relation should show the possible relations  <Ensemble:New> < https://launchpad.net/bugs/803866 >
[13:50] <kiranm> hazmat, the exact error for the ambiguous endpoints....
[13:50] <kiranm> mbiguous endpoints: ([(RelationEndpoint(service_name='wordpress', relation_type=u'mysql', relation_name=u'db', relation_role='client'), RelationEndpoint(service_name='mysql', relation_type=u'mysql', relation_name=u'db', relation_role='server')), (RelationEndpoint(service_name='wordpress', relation_type=u'mysql', relation_name=u'db', relation_role='client'), RelationEndpoint(service_name='mysql', relation_type=u'mysql', relation_name=u'db-admin', r
[13:50] <kiranm> elation_role='server'))],)
[13:50] <kiranm> 2011-06-30 17:39:35,243 ERROR Ambiguous endpoints: ([(RelationEndpoint(service_name='wordpress', relation_type=u'mysql', relation_name=u'db', relation_role='client'), RelationEndpoint(service_name='mysql', relation_type=u'mysql', relation_name=u'db', relation_role='server')), (RelationEndpoint(service_name='wordpress', relation_type=u'mysql', relation_name=u'db', relation_role='client'), RelationEndpoint(service_name='mysql', relation_type=u'mysql
[13:50] <kiranm> ', relation_name=u'db-admin', relation_role='server'))],)
[14:00] <hazmat> kiranm, so you need to add the relation via .. ensemble add-relation wordpress mysql:db
[14:01] <hazmat> kiranm, a second named relation was added to the principia version to support administrative program access to mysql, so now the usage needs to be qualified
[14:03] <kiranm> hazmat, ok understood. 
[14:06] <kiranm> hazmat, are these kind of changes documented some where, so that people who test the formulas regularly can be enlightened
[14:06] <kiranm> hazmat, especially the formulas from principia-tools would be the focus of testing IMO
[14:08] <hazmat> kiranm, at the moment principia is pretty early in its development, the only change log is the revision log.. we will eventually get to releases/frozen version sets of principia formulas with change logs between them
[14:09] <kiranm> hazmat, thx again
[14:09] <hazmat> kiranm, np
[15:04] <_mup_> Bug #803892 was filed: Ensemble should have a config templating system <Ensemble:New> < https://launchpad.net/bugs/803892 >
[15:05] <_mup_> Bug #803895 was filed: Ensemble should have a parallel execution mechanism <Ensemble:New> < https://launchpad.net/bugs/803895 >
[15:18] <_mup_> Bug #803902 was filed: provide a way to remove relationship entries <Ensemble:New> < https://launchpad.net/bugs/803902 >
[15:26] <lynxman> hazmat: ping
[15:42] <hazmat> lynxman, pong
[15:42] <lynxman> hazmat: hey just added myself to bug #616900 since I'm trying to do a macports version of the ensemble client
[15:42] <_mup_> Bug #616900: Make a release <txzookeeper:New for hazmat> < https://launchpad.net/bugs/616900 >
[15:43] <lynxman> hazmat: any chance this can be done in the near future?
[15:43] <lynxman> (near future being a couple of weeks or so)
[15:43] <hazmat> lynxman, sure, there's one branch in review thats needed for a new release, it is already available off pypi
[15:43] <lynxman> hazmat: oh cool, do you have the URL for the tarball?
[15:44] <hazmat> lynxman, its basically a pure python package, the nesc compilation bit is getting zookeeper-python bindings installed
[15:44] <hazmat> lynxman, http://pypi.python.org/pypi/txzookeeper
[15:44] <lynxman> hazmat: lovely, thanks
[15:44] <hazmat> lynxman, that version might be a little old for ensemble..
[15:44] <hazmat> trunk that is
[15:44] <lynxman> hazmat: well if you push a new tarball that'll be cool :) meanwhile I'll do my port work based on that one
[15:45] <hazmat> lynxman, we've in the past run the full unit tests on osx with just one or two issues due to different fs handling of tempfiles
[15:45] <hazmat> but for the most part it should just work
[15:45] <lynxman> hazmat: that's good news :)
[15:45] <lynxman> hazmat: just making the portfiles to submit them to macports for now
[15:45] <hazmat> lynxman, you also want to make sure you have the most recent zk release version in macports
[15:45] <lynxman> hazmat: as soon as it's working I'm sure there'll be bugs to fill
[15:45] <hazmat> lynxman, awesome
[15:45] <hazmat> lynxman, sounds good
[15:45] <lynxman> hazmat: yeah slowly going through the dependencies
[15:46]  * hazmat likes macports
[15:46] <hazmat> very easy to contrib to
[15:46] <lynxman> :)
[15:46] <lynxman> hazmat: indeed, I'm also contributing byobu
[15:46] <koolhead11> SpamapS, hello
[15:47] <hazmat> although now a days i here everyone talking about homebrew.. only reason i can think of is the install into /usr/local makes it easy for lookups 
[15:47] <koolhead11> hi all
[15:47] <hazmat> when compiling additional extensions at the price of getting a potential mismash of libraries
[15:47] <hazmat> koolhead11, hi
[15:47] <hazmat> or perhaps its just tcl v ruby
[15:48] <koolhead11> hi hazmat 
[15:50] <koolhead11> i am working on the phpmyadmin but having some trouble with preseed configuration
[15:50] <koolhead11> i see some bugs regarding the same on debian mailing list
[15:58] <hazmat> koolhead11, i'm a bit out of my element regarding php.. but the deb mailing list or the lp bug tracker for phpadmin is probably the right place to follow up those issues
[15:58] <hazmat> koolhead11, do you have a link?
[15:58] <koolhead11> yes
[15:58] <koolhead11> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=578960  
[15:59] <koolhead11> when i am doing dpkg-reconfigure phpmyadmin i have to enter everything manually and then it writes to the DB :
[16:19] <hazmat> koolhead11, hmm.. are you purging and reinstalling or just preseeding debconf selections
[16:19] <koolhead11> i was doing purge earlier
[16:19] <koolhead11> now i have installed new VM with snapshot
[16:19] <koolhead11> am doing it on LTS
[16:37] <hazmat> nice. http://morepypy.blogspot.com/2011/06/global-interpreter-lock-or-how-to-kill.html
[17:02]  * koolhead11 heads back home
[17:41] <_mup_> ensemble/expose-provision-machines r268 committed by jim.baker@canonical.com
[17:41] <_mup_> Fixes to handle topology changes wrt watches
[18:14] <_mup_> txzookeeper/session-event-handling r52 committed by kapil.foss@gmail.com
[18:14] <_mup_> merge trunk
[19:05] <_mup_> txzookeeper/session-event-handling r53 committed by kapil.foss@gmail.com
[19:05] <_mup_> add a disconnected client test for failures, dead connections can exhibit either notconnected or connection exceptions adjust tests to reflect.
[21:16] <_mup_> txzookeeper/session-event-handling r54 committed by kapil.foss@gmail.com
[21:16] <_mup_> address jim's review comments, grammar fixes, additional param valiadation tests
[21:41] <hazmat> bcsaller, do you mind if i post your email to the merge proposal along with my reply?
[21:41] <bcsaller> hazmat: I don't remember specifically what you're talking about but I think its fine
[21:41] <bcsaller> hazmat: the scheduler/workflow stuff?
[21:41] <hazmat> bcsaller, yup
[21:42] <bcsaller> hazmat: thanks for looking into that :)