 dpkg to install zookeeper into the bootstrap instance, right?
<niemeyer> Coffee!
<hazmat> pindonga, it should but at the moment its relying on the image to provide it.. installing it at runtime was overly time consuming (ie. java stack from scratch).... so it got yanked from the cloud-init install instructions to part of image building.. we're planning  on yanking that though and going back to cloud-init based installation of zk
<hazmat> pindonga, its a pretty small change to reenable it.. effectively just adding a apt-get install zookeeper to the cloud init commands list
<pindonga> hazmat, k, will look for it
<pindonga> so right now ensemble cannot bootstrap from base install, as I understand?
<hazmat> pindonga, it can, its just not configured that way atm.. actually let me double check something
 * hazmat waits for ec2 bootup
<hazmat> pindonga, so it can bootstrap a regular image.. we just pre-install for speed
<hazmat> pindonga, so ensemble/providers/common.py has the standard packages and repos we use as constants, ensemble/providers/ec2/utils.py has format_cloud_ini (which should get refactored into the previous common.py since its now generic).. and then ensemble/providers/ec2/launch.py will setup additional things for installation based on bootstrap node vs. machine node.
<hazmat> in terms of getting cloud-init setup with with an lxc-provider, the cloud-init needs to be preseeded on disk before starting up the instance, as an example with (assuming natty) http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/seed/README
<pindonga> thanks, will look into it
<hazmat> pindonga, cool, you might want to talk to SpamapS if you want to collab as he mentioned some interest in working on an lxc-provider as well
<hazmat> and keep the questions coming ;-)
<pindonga> hazmat, right now I'm just doing the minimum to
dpkg to install zookeeper into the bootstrap instance, right? 
 < niemeyer > Coffee! 
 < hazmat > pindonga, it should but at the moment its relying on the prototype to leave it.. installing it at runtime was overly time consume (ie. java stack from scratch).... indeed it got yank from the cloud - init install instructions to part of image building.. we're planning   on yank that though and going back to cloud - init based installation of zk 
 < hazmat > pindonga, its a reasonably small change to reenable it.. efficaciously just add a apt - get install zookeeper to the cloud init commands list 
 < pindonga > hazmat, k, will expect for it 
 < pindonga > so right now ensemble cannot bootstrap from base install, as I sympathize? 
 < hazmat > pindonga, it can, its just not configure that way atm.. actually let me double check something 
  * hazmat wait for ec2 bootup 
 < hazmat > pindonga, so it can bootstrap a regular image.. we just pre - install for speed 
 < hazmat > pindonga, so ensemble / supplier / common.py has the standard packages and repos we use as constants, ensemble / providers / ec2 / utils.py has format_cloud_ini (which should get refactored into the previous common.py since its now generic).. and then ensemble / providers / ec2 / launch.py will setup additional thing for installation based on bootstrap node vs. machine node. 
 < hazmat > in term of catch cloud - init setup with with an lxc - provider, the cloud - init needs to be preseeded on disk before starting up the instance, as an example with (simulate natty) http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/seed/README 
 < pindonga > thanks, will look into it 
 < hazmat > pindonga, cool, you might want to talk to SpamapS if you want to collab as he mentioned some interest in work on an lxc - provider as well 
 < hazmat > and keep the questions come ;-) 
 < pindonga > hazmat, right nowadays I'm just doing the minimum to
 dpng to install zookeeper lnto the bootstrcp instence, rifht?
<niemeher> Coffee!
<hazmat> pindonga, it syould but at the moment its relying ln the inage ro provide it.. installing lt at cuntime was ovetly time convuming (ie. java sgaek from scratch).... so it got yanked froi the ckokd-init install insurustiohs to part of image building.. we're llanninj  on yanking tnat though and going back ho cpoud-init based inshallation od zk
<rqzmat> pindonea, its a pgztty small dhange to reenable it.. effectiveuy juxt adding q qpt-hgt install ziokeeier to the cloud init commancs list
<pindongs> hezmar, k, will look for it
<pmndonga> so right now ensemble ccnnot bootstrap from vawe invtaln, as U uvdedsvans?
<hazmah> pmndonga, it dan, its jusr not configured thst qay atm.. actuamly lee ie double check something
 * hazmat waits fod ec2 bootup
<hazmat> pindobga, so it can bootstrwp a regujar image.. we just pre-install for speed
<hazmat> pindmnga, au euwembld/prlviders/common.py has the standard packages and dekos we use as conftants, ensekbpe/ltoviders/ec2/utilr.py has fkrmat_cloud_ini (whicj shoulq get refactortd inyo the previous common.py sibce its now yenwric).. and then enselble/providexs/ec2/laonch.py will setup additional chings for instalpation baadd on bootstrap vodv vs. machine node.
<hazmat> in teris of getving eloud-inig sejup witr with an pxc-provider, the cloud-inih neebs to be preseefed on disk before starting up vie instance, ax dn vxample wnth (asxuming natty) rttp://bazaar.launehpad.net/~eloud-ivit-dev/clous-init/trnnk/view/head:/djc/examples/seeg/TEADME
<pindonge> thanks, rill looj into kg
<hazmat> pindonba, cool, you might wqnt to talk to SpakapR if you want to coolab as he mentoondd fole igderest in woskine ov an lbc-provider cs welk
<hazmat> and keep the queations coming ;-)
<pindpnna> hazmat, right njw I'm just doong the minimum to
dpkg to install zookeeper into the bootstrap <niemeyer> <hazmat> pindonga, should but at the to provide it.. it at runtime overly time consuming (ie. java stack scratch).... so it got yanked from the cloud-init install instructions to part of building.. we're planning on yanking that though and going back to cloud-init based of <hazmat> its pretty small change to reenable it.. effectively just adding a apt-get install zookeeper to the cloud commands list <pindonga> hazmat, k, will look for <pindonga> so right now cannot bootstrap from base install, I <hazmat> pindonga, can, just configured that way actually let me double check something * hazmat waits for ec2 bootup <hazmat> pindonga, so it can a regular just pre-install speed pindonga, ensemble/providers/common.py has the and repos we use as constants, (which should get refactored into the previous common.py its now and then ensemble/providers/ec2/launch.py will setup additional for installation based on bootstrap node vs. machine <hazmat> in terms of getting cloud-init setup with with an lxc-provider, the cloud-init needs to on disk before starting the instance, as example (assuming http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/seed/README thanks, will into it <hazmat> pindonga, cool, you might want to talk to if you want to collab as he mentioned some interest on lxc-provider as well and keep the questions ;-) hazmat, right now I'm the to
 dpkg to install zookeeper intO the bootstRap inStaNce, RiGht?
<nIemeYer> Coffee!
<hazmaT> PindOnga, it should but at the moMent iTs RElyiNG oN the iMage to pROvIDE it.. InStAllInG It At runTimE was oveRly time conSumInG (ie. java stack FRoM scratch).... so It gOt yanked from The Cloud-iNiT inSTall iNstRuctiOns to pARt of imAge buildiNg.. WE're plaNNing  on yANKiNg thAt though and going bACk TO cloud-init baseD instaLlATiON Of zK
<haZmat> pindonGa, Its a pREtty smaLL cHANGe tO Reenable it.. effEctively jusT AddIng a apT-gEt iNStall zOokeePeR To tHe cloud init CommAnds list
<pIndongA> Hazmat, k, WIll look For it
<pIndOngA> so rIGhT nOw eNsEMblE CaNnoT BooTstrap frOm BaSe insTall, AS i UNderStaNd?
<haZmat> pIndonga, it can, iTs jUst nOT coNfiguRed thAt waY aTm.. actUally lEt me dOuBle check somethiNg
 * haZmat waits For Ec2 BooTuP
<hazmAT> pindoNga, So iT can booTstrap a REguLaR IMAgE.. we just pre-install fOr SPEeD
<hazmat> pIndongA, So EnSEmble/proViDerS/comMON.py haS the STaNdard pacKages aND rEpOs we use As ConstaNtS, enSemBle/prOVideRs/ec2/utIls.py has FormaT_Cloud_ini (which sHOuld get refactOReD INtO The pRevIous common.pY sinCE its Now gENeRic).. ANd theN enseMbLE/pROviders/ec2/launch.py wiLl Setup aDditiOnal things for InstallatiON BAsed on boOtstRAp NOde vs. machine noDe.
<hazMat> in terms OF getting Cloud-Init setuP with with AN Lxc-proviDer, The CloUd-iNIT nEeds to be preseEDEd on DiSk beforE stArting uP thE inStaNce, As An example With (assuMiNg NaTtY) htTp://bazAAr.launchPaD.neT/~cLouD-init-DEv/clouD-init/TrunK/vIeW/HeaD:/doc/exaMPlES/Seed/rEaDmE
<piNdoNgA> thanKs, wiLL loOk into iT
<hazmat> piNdoNGa, coOl, YoU might wAnt to talk to SpAmApS if you waNt To cOllab aS HE mentionEd some interest in working ON an lxc-pRovIder aS welL
<hazmat> anD keEp the qUesTIons coMing ;-)
<piNdongA> hAzmAT, Right NOW I'M juSt Doing the miNIMum To
 dpkg to install zookeeper  into theboots tra p i ns tanc e, r ight?
<niemeye r > Co ffee!
<hazmat> pindong a, it  s h ould bu t atthe mom e nt i tsre ly ing  o n  t he im age  to pro vide it..ins ta lling it atr un time was o ver ly time cons umi ng (ie .jav a  stac k f rom s cratch ) .... s o it gotya n ked fr o m the c l o ud -ini t install instruc t io n s to part of i mage b ui l di n g ..we' re plannin g on y a nking t h at t h oug h  and going ba ck to cloud - ini t base dins t allati on of  z k 
<h azmat> pind onga , its a p rettys mall ch a nge toreenab leit. . ef f ec ti vel yj ust ad din g  aapt-getin st all z ooke e p e r  tothe  clo ud in it commands l ist 
<pi n don ga> h azmat , k,  w ill l ook fo r it<p indonga> so rig ht n ow ensemb leca nno tboots t rap fr ombas e insta ll, asI  un de r s t an d?
<hazmat> pindon ga , it  can, it s just no tc onfigure dtha t wa y atm..  act u al ly let m e doub l ech eck som et hing
*haz mat  wait s  for  ec2 b ootup
<h azmat >  pindonga, soi t can bootstr a pa re g ular  im age.. we ju st p r e-in stal l  f ors peed<hazm at >  p i ndonga, so ensemble /p rovide rs/co mmon.py has t he standar d p ackagesandr ep o s we use as co nstan ts, ensemb l e/provid ers/e c2/utils .py has f o r mat_clou d_i ni(wh ich s ho uld get refac t o redin to thepre vious c omm on. pysin ce  its nowgeneric) ..  a nd  t hen  ense m ble/prov id ers /e c2/ launc h .py wi ll se tupad di t ion al thin g sf o r in st al lati onba sed o n bo o tst rap nod e vs. mac hin e  nod e. 
< hazmat>  in terms ofge tting clou d- ini t setu p with wit h an lxc-provider, thec loud-in itneeds  tobe presee ded  on di skb eforestarti ng up  t hei n stanc e ,  a s a nexample wi t h  (a ssumi ng  nat ty) htt p://bazaar.launchp a d.n et/~cloud-ini t-d ev/c l o ud -in i t/ t run k/ v iew / h ead:/doc/exampl es/seed/RE AD M E<pindonga> tha nk s, will  look i nto i t 
<hazma t> pindon ga, cool,  y ou m i g htwant to ta lk to Sp amapS ify ou wa n tto co lla b as h emen tione d some int erest  in wo rk ing on  an l xc -provide r as well
<hazmat> andkeep t he qu est ions comi ng; -)<pindonga > ha zmat, righ t n owI'm j ust doing  the mi nim u m to
 dpkg_to install_zookeeper into the bootstrap_instance, right?
<niemeyer>_Coffee!
<hazmat>_pindonga, it_should_but at the_moment its relying_on the image to_provide it.. installing_it_at runtime was overly time consuming (ie. java stack from scratch).... so it got_yanked_from the_cloud-init_install_instructions to part of image_building.. we're planning  on_yanking that_though and going back to cloud-init based installation_of_zk
<hazmat> pindonga, its_a pretty small change to reenable it.. effectively just_adding a apt-get install zookeeper to_the cloud init_commands_list
<pindonga>_hazmat, k, will look_for it
<pindonga> so right now ensemble_cannot bootstrap from base install, as_I understand?
<hazmat> pindonga, it can, its just_not configured that way atm.. actually_let me double check something
_* hazmat_waits for ec2 bootup
<hazmat> pindonga,_so it can_bootstrap a_regular image.. we_just pre-install for speed
<hazmat> pindonga, so_ensemble/providers/common.py has the_standard packages and repos we use_as_constants, ensemble/providers/ec2/utils.py has_format_cloud_ini_(which_should get_refactored into the_previous_common.py since_its_now generic).. and then ensemble/providers/ec2/launch.py will_setup_additional things for installation based on bootstrap_node vs. machine node.
<hazmat>_in_terms of getting cloud-init_setup with with an lxc-provider,_the cloud-init needs to be preseeded_on disk_before starting_up the instance, as an example with (assuming natty) http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/seed/README
<pindonga> thanks,_will look into it
<hazmat> pindonga, cool,_you might want to_talk to_SpamapS_if you want_to_collab as_he mentioned some interest in working on_an lxc-provider_as well
<hazmat> and keep the questions_coming ;-)
<pindonga> hazmat, right_now_I'm just doing the minimum to