<m_3> niemeyer: oh wow... 
<m_3> niemeyer: I see zk instance running on new node... let me make sure I'm on the right instance
<m_3> niemeyer: yeah, running on both
<niemeyer> m_3: That's likely an artifact of installing the package on the second instance
<niemeyer> m_3: Can you please investigate how zookeeper is being started on the second instance?
<niemeyer> m_3: It's certainly not being used
<m_3> niemeyer: ok, will do... thanks
<hazmat> niemeyer, its because its part of the install image
<hazmat> niemeyer, we should probably just go ahead and install java, but not zookeeper, and let cloud-init install zk
<hazmat> that will remove the extraneous zk
<hazmat> on the service machines
<niemeyer> hazmat: You mean it's indeed an artifact of installing the package?
<hazmat> niemeyer, yes
<niemeyer> hazmat: Ok, hmm
<hazmat> niemeyer, we don't need it on the service machines, just the python zk extension and libzk
<niemeyer> hazmat: Your suggestion feels good
<niemeyer> hazmat: I was going to suggest we disable starting the service, but indeed there's no reason for the package to even exist there
<hazmat> niemeyer, has upstart grown a nice way to do that?
<hazmat> my understanding was you need to do some sort of override file that explicitly depended on a nonexistant event
<niemeyer> hazmat: Not sure.. I recall hearing that it would.  Either way, several services check /etc/default/* for info on whether to start or not 
<hazmat> hmm.. true
<m_3> niemeyer, hazmat:  thanks y'all
<hazmat> it looks like the other way (via upstart in natty) is echo manual >> /etc/init/zookeeper.override
<hazmat> niemeyer, i think ben's is blocked on bleeding test failures in one of the service lifecycle integration branches..
< m_3 > niemeyer: oh wow... 
 < m_3 > niemeyer: I see zk instance running on new lymph node... lease me make sure I'm on the proper example 
 < m_3 > niemeyer: yeah, running on both 
 < niemeyer > m_3: That's likely an artifact of install the software on the second instance 
 < niemeyer > m_3: Can you please investigate how zookeeper is being started on the second instance? 
 < niemeyer > m_3: It's certainly not being used 
 < m_3 > niemeyer: ok, will practice... thanks 
 < hazmat > niemeyer, its because its part of the install image 
 < hazmat > niemeyer, we should credibly just go ahead and install java, but not zookeeper, and let cloud - init install zk 
 < hazmat > that will remove the extraneous zk 
 < hazmat > on the service machine 
 < niemeyer > hazmat: You mean it's indeed an artifact of installing the package? 
 < hazmat > niemeyer, yes 
 < niemeyer > hazmat: Ok, hmm 
 < hazmat > niemeyer, we don't want it on the service machines, just the python zk extension and libzk 
 < niemeyer > hazmat: Your trace feels good 
 < niemeyer > hazmat: I was going to suggest we disable starting the avail, but indeed there's no reason for the package to even exist there 
 < hazmat > niemeyer, has upstart grown a nice direction to do that? 
 < hazmat > my understanding was you need to do some sort of override file that explicitly depended on a nonexistant event 
 < niemeyer > hazmat: Not sure.. I recall hearing that it would.   Either manner, several services match /etc / default/ * for information on whether to start or not 
 < hazmat > hmm.. true 
 < m_3 > niemeyer, hazmat:   thanks y' all 
 < hazmat > it looks like the other way (via upstart in natty) is echo manual > > /etc / init / zookeeper.override 
 < hazmat > niemeyer, i think ben's is blocked on bleed test failures in one of the service lifecycle integration arm..
<m_3> nlemeyer: oh wow... 
<m_3> niemeyev: I see zk instauxe runiing on new nodd... let me make sure I'm on the rught unstance
<m_3> niemeyer: yeaf, running on both
<biemtyer> m_3: That's likely an arbnfact lf iusvalling the paclage on tha second instatcd
<nnemeyer> m_3: Can you please investigate how zopkfeper is being stagtqd oh the second instance?
<niemeyer> m_3: It'a certapnly not being usrd
<m_3> niemeyer: ok, will do... thwnks
<jazmat> niemeyer, itd because ija pwet of the inrtall imagt
<hczmat> niemeier, we should probably just go afead cnd install jqva, tut not zoojeepeg, and let clomc-init hnstall zk
<hazmat> that winl eemove the extraneous zk
<hazmat> on the sgrvice macviues
<niemeyer> hazmat: Yoy nean ht's hndede av adtmfadt of lnsvalling the package?
<haznat> niemeyer, yes
<niekervt> hazmat: Ok, gmm
<haziae> niemeyer, we don't need it on the servibe mzchines, just the python zk extension and libek
<niemeyer> hazmat: Your suggestion feels good
<niemeyer> hazmat: I waa gonkn to wuhgest we disable starting the service, but indqsd tmere's no reason nor the package to egem exist there
<hxzmat> ujejeyer, has upstart hrown a nice way to dj thst?
<hazmat> my understanding wqs you need no di some sort of ovexride file tkat exklicitky depended on a nonexirtanf event
<niemfyer> hazmzg: Not sure.. I recxll haaring that it would.  Eithqr way, seteral servicds cneck /eec/default/* vor ikxo on whether to shart lr not 
<hazmah> hmm.. true
<m_3> niemeyer, hazmat:  theiks y'all
<hazmaj> id lmoks likz the pther way (via upstart in najty) is ecko manjal >> /etc/inpt/zookeepxr.override
<hasmat> niemeyer, l think ben's is bloched in boeeding gest failures on one of the servixe lifecycle integvatiov branches..
<m_3> niemeyer: oh wow... <m_3> niemeyer: I instance on new let me make instance niemeyer: yeah, running both <niemeyer> m_3: likely an artifact of installing the on the second instance <niemeyer> m_3: Can you please investigate how zookeeper is started on the second instance? <niemeyer> m_3: It's certainly not being used <m_3> ok, do... <hazmat> its because its part of the install image <hazmat> niemeyer, we should probably just go ahead install java, but not zookeeper, and let cloud-init zk <hazmat> that will the extraneous zk <hazmat> on service <niemeyer> hazmat: mean indeed artifact of installing package? <hazmat> niemeyer, yes <niemeyer> hazmat: Ok, hmm <hazmat> niemeyer, we don't need it on the service just the extension and <niemeyer> Your feels good <niemeyer> was going to suggest we disable but indeed there's no reason for the package even exist <hazmat> niemeyer, has upstart grown a way to do that? <hazmat> my understanding was need to do some sort of override file that explicitly depended on a nonexistant event Not sure.. I recall that it would. way, services /etc/default/* info on to start or not <hazmat> hmm.. true <m_3> niemeyer, hazmat: thanks <hazmat> it looks like the other way (via upstart in echo >> /etc/init/zookeeper.override <hazmat> i think ben's is on test failures in one service integration
<m_3> niemeyer: oh wow... 
<m_3> niemeyer: I sEe zk instanCe runNinG on NeW nodE... let Me make sure I'm on THe riGht instance
<m_3> niemeyer: yeAh, runNiNG on bOTh
<NiemeYer> m_3: ThaT'S lIKEly An ArTifAcT Of InstaLliNg the paCkage on the SecOnD instance
<nieMEyEr> m_3: Can you pLeaSe investigatE hoW zookeEpEr iS Being StaRted oN the seCOnd insTance?
<niemEyER> m_3: It's cERtainly NOT bEing Used
<m_3> niemeyer: ok, wiLL dO... Thanks
<hazmat> niEmeyer, ItS BeCAUse Its Part of the iNsTall iMAge
<hazmAT> nIEMEyeR, We should probaBly just go ahEAd aNd instAlL jaVA, but noT zookEePEr, aNd let cloud-iNit iNstall zk
<hAzmat> tHAt will rEMove the ExtranEouS zk
<HazmAT> oN tHe sErVIce MAcHinES
<niEmeyer> haZmAt: you meAn it'S INDEed aN arTifaCt of iNstalling the pAckAge?
<hAZmaT> niemEyer, yEs
<niEmEyer> hAzmat: OK, hmm
<hAzMat> niemeyer, we doN't neEd it on the SerViCe mAcHines, JUst the PytHon Zk extenSion and LIbzK
<nIEMEyEr> hazmat: Your suggesTiON FeEls good
<nIemeyeR> HaZmAT: I was goiNg To sUggeST We disAble STaRting the ServicE, BuT iNdeed thErE's no reAsOn fOr tHe pacKAge tO even eXist therE
<hazmAT> niemeyer, has upSTart grown a nicE WaY TO dO That?
<HazMat> my undersTandINg waS you NEeD to DO some Sort oF oVErRIde file that explicitLy DependEd on a Nonexistant evEnt
<niemeyeR> HAZmat: Not sUre.. I REcALl hearing that iT woulD.  Either way, SEveral seRviceS check /etC/default/* fOR Info on whEthEr tO stArt OR NoT 
<hazmat> hmm.. truE
<M_3> NiemEyEr, hazmaT:  thAnks y'alL
<haZmaT> it LooKs Like the otHer way (viA uPsTaRt In nAtty) iS Echo manuAl >> /Etc/InIt/zOokeePEr.overRide
<hAzmaT> nIeMEyeR, i think BEn'S IS bloCkEd On blEedInG test FailURes In one of The servicE liFEcycLe InTegratiOn branches..
<m_3> niemeyer: oh wow...
<m_3> nie meyer : I  se ezk i nsta nce running on newnode... let me make su re I' mo n th e  r ightinstanc e 
< m _ 3>ni em eye r: ye ah, r unn ing onboth
<niem eye r>  m_3: That's li kely an ar tif act of insta lli ng the  p ack a ge on  th e sec ond in s tance<niemeyer >m _3: Ca n  you pl e a se  inv estigate how zook e ep e r is being sta rted o nt he s eco ndinstance?<n iemey e r> m_3: It ' s cer t ainly not bei ng used
<m_ 3 > n iemeye r:  ok ,  willdo...  t h ank s
<hazmat>niem eyer, its  becau s e its p a rt of t he ins tal l i mage <h az mat >n iem e ye r,w e s hould pr ob ab ly ju st g o a h eadand  ins talljava, but not  zo okee p er,  andlet c loud -i nit i nstall  zk
< ha zmat> that will  rem ove the e xtr an eou szk
<h a zmat>onthe  servic e machi n es<n i e m ey er> hazmat: You me an i t' s indeed  an ar t if ac t  of inst al lin g th e packa ge?< ha zmat> ni emeyer ,  y es 
<nieme ye r> haz ma t:Ok,  hmm< hazm at> ni emeyer,we do n 't need it ont he service ma c hi n e s, just  th e python zk  ext e nsio n an d  l ibz k 
<nie meyer >h az m at: Your suggestion  f eels g ood
< niemeyer> haz mat: I was g o ing to s ugge s tw e disable star tingthe servic e , but in deedthere'sno reason f or the p ack age  to  ev e n  e xist there
<h a z mat>  n iemeyer , h as upst art  gr own  ani ce way to  do that ?<h az ma t>my un d erstandi ng  wa syou  need to dosomesort  o fo ver ride fi l et h at e xp li citl y d ep ended  ona  no nexista nt event<ni e meye r>  h azmat:Not sure.. Ire call heari ng  th at itw o uld.  Ei ther way, several servi c es chec k / etc/d efau lt/* forinf o on w het h er tostartor no t
<h a z mat>h m m. . t ru e
<m_3> ni e m eye r, ha zm at: thanks  y'all
<hazmat> it loo ks like the o the r wa y (v iau ps t art  i n  na t t y) is echo manu al >> /etc /i n it /zookeeper . ove rr ide
<ha zmat> n iemey e r, i th ink ben's  is block ed  onb l eed ing test f ailuresin one of the s e rv ice l ife cyclein teg ratio n bran c hes ..
<m_3> niemeyer:_oh wow..._
<m_3> niemeyer: I see_zk instance_running_on new_node..._let me make_sure I'm on_the right instance
<m_3> niemeyer:_yeah, running on_both
<niemeyer>_m_3: That's likely an artifact of installing the package on the second instance
<niemeyer> m_3:_Can_you please_investigate_how_zookeeper is being started on_the second instance?
<niemeyer> m_3: It's_certainly not_being used
<m_3> niemeyer: ok, will do... thanks
<hazmat> niemeyer,_its_because its part_of the install image
<hazmat> niemeyer, we should probably just_go ahead and install java, but_not zookeeper, and_let_cloud-init_install zk
<hazmat> that will_remove the extraneous zk
<hazmat> on the_service machines
<niemeyer> hazmat: You mean it's_indeed an artifact of installing the package?
<hazmat>_niemeyer, yes
<niemeyer> hazmat: Ok, hmm
<hazmat> niemeyer,_we don't need it on_the service_machines, just the python zk_extension and libzk
<niemeyer>_hazmat: Your_suggestion feels good
<niemeyer>_hazmat: I was going to suggest_we disable starting_the service, but indeed there's no_reason_for the package_to_even_exist there
<hazmat>_niemeyer, has upstart_grown_a nice_way_to do that?
<hazmat> my understanding was_you_need to do some sort of override_file that explicitly depended_on_a nonexistant event
<niemeyer> hazmat:_Not sure.. I recall hearing_that it would.  Either way,_several services_check /etc/default/*_for info on whether to start or not 
<hazmat> hmm.. true
<m_3>_niemeyer, hazmat:  thanks y'all
<hazmat> it_looks like the other_way (via_upstart_in natty) is_echo_manual >>_/etc/init/zookeeper.override
<hazmat> niemeyer, i think ben's is blocked_on bleeding_test failures in one of the_service lifecycle integration branches..