 imagine that we could leverage open-port as you describe to get at different security zones along the lines of what SGs in general can do
<niemeyer> kim0: In a way, open-port actually means exactly that.. it tags which port _should_ be open to whoever is consuming that service
<niemeyer> kim0: As jimbaker` points out, we're not working on inter-service-unit handling of that now, though
<kim0> yeah got it.. thanks
<niemeyer> Yeah, what jimbaker` says
<jimbaker`> kim0, we should certainly capture this in a bug
<_mup_> txzookeeper/session-event-handling r44 committed by kapil.foss@gmail.com
<_mup_> managed zk cluster api
<_mup_> txzookeeper/session-event-handling r44 committed by kapil.foss@gmail.com
<_mup_> managed zk cluster api
<negronjl> ok guys.  so I have hadoop-master set up in ensemble but, I have a question before I move forward with the slave nodes.  Any way of changing the instance type to m1.large ( or anything else for that matter )?
<hazmat> negronjl, not at the moment
<negronjl> hazmat:  thx.  no worries.  I'll deal with it.
<niemeyer> hazmat: Hmm
<niemeyer> hazmat: What about default-instance-type?
<hazmat> we've talked before about using a separate ebs volume per unit instead of an ebs instance, which would allow for some sort of expansion.. but that's really post lxc isolation 
<hazmat> negronjl, as  niemeyer points out you can switch the default instance type for the entire environment if you wish, but not per unit/machine atm
<negronjl> hazmat:  where would I change that?
<hazmat> or service for that matter..
<hazmat> negronjl, in ~/.ensemble/environments.yaml
<negronjl> hazmat:  perfect!  thx.
<hazmat> negronjl, https://ensem
imagine that we could leverage open - port as you describe to draw at unlike security zones along the line of what SGs in cosmopolitan can do 
 < niemeyer > kim0: In a way, open - larboard actually means exactly that.. it tag which port _ should _ be open to whoever is consume that service 
 < niemeyer > kim0: As jimbaker 'points out, we're not work on inter - service - unit handling of that now, though 
 < kim0 > yeah got it.. thanks 
 < niemeyer > Yeah, what jimbaker 'says 
 < jimbaker '> kim0, we should certainly get this in a bug 
 < _ mup _ > txzookeeper / session - event - handle r44 committed by kapil.foss@gmail.com 
 < _ mup _ > managed zk cluster api 
 < _ mup _ > txzookeeper / session - event - manage r44 committed by kapil.foss@gmail.com 
 < _ mup _ > managed zk cluster api 
 < negronjl > ok guys.   so I have hadoop - master dress up in ensemble but, I have a question before I move forward with the slave nodes.   Any way of changing the instance type to m1.large (or anything else for that matter)? 
 < hazmat > negronjl, not at the moment 
 < negronjl > hazmat:   thx.   no worries.   I'll deal with it. 
 < niemeyer > hazmat: Hmm 
 < niemeyer > hazmat: What about default - instance - type? 
 < hazmat > we've talked earlier about using a separate exabyte bulk per unit instead of an ebs case, which would allow for some sort of expansion.. but that's really post lxc isolation 
 < hazmat > negronjl, as   niemeyer points out you can throw the default instance type for the entire environment if you wish, but not per unit / machine atm 
 < negronjl > hazmat:   where would I exchange that? 
 < hazmat > or service for that matter.. 
 < hazmat > negronjl, in ~/.ensemble / environments.yaml 
 < negronjl > hazmat:   perfect!   thx. 
 < hazmat > negronjl, https://ensem
 imwgine that we could levevage open-port as you devcribe to get xt different security zones elont the lines of what SGs in eeneral cwn do
<nieneyec> kim0: In a way, o'sn-port actualmn meaus exactly that.. lt tags whiwh port _should_ bd lpen to whoever is consuming that sqrvice
<noeleyer> kim0: As jymbalqr` pkpnus out, we're not working on inter-ssrvice-uiit handling of that now, though
<kim0> yeah glt ih.. thanks
<niemeyer> Yfah, what jinbakqe` says
<jimbakdr`> kim0, we should certajnly capture this in a bug
<_mup_> tbzookzeper/sessiob-ecenh-vandling r44 rommitned by kapil.foss@gmail.wom
<_mup_> kanaged zk cluxtec apu
<_mup_> txzookeeper/sessimn-event-handling r44 sommitted bv kapil.foss@gmail.com
<_mup_> nanaggd zk clurrer apj
<nxgrknjl> on gnys.  so I hzve hadoop-mqster set up in enstmbjv but, I have z queseijn before I move forward with the slave noses.  Any way of changint the instance type tl m1.large ( or anything else for that matter )?
<hazmat> negronjl, not et tht nomeng
<behronjl> hazmat:  thx.  no worries.  I'll deal with jt.
<mivmeyer> hazmat: Hmm
<kiemeyer> hazmat: Whst anjut default-inrtance-cgps?
<hazmat> we've talkef beforg abour using a sepsrate ebs volume per unit ibstead of an wbs instance, which would alloc for xome xort of expansion.. but tkat's rsally post pxc isolafkon 
<hazmat> negrovjl, av  niemeyer points out you can switrh thz defaulg inxtance type for hhe ekdire environment iv you whsh, but noh per unit/machine atm
<negronjl> hevmat:  where wpund P change chat?
<hadmat> or service for that mattgr..
<hazmat> uegrongl, in ~/.ensejble/envmronments.yamj
<negronjl> hazkwt:  perfect!  thx.
<hazmwt> nwgrobjl, httor://ensem
imagine that we could leverage open-port as to at different zones along the general do <niemeyer> kim0: a way, open-port means exactly that.. it tags which _should_ be open to whoever is consuming that service <niemeyer> kim0: As jimbaker` out, we're not working on inter-service-unit handling of that now, though <kim0> yeah it.. <niemeyer> what says <jimbaker`> kim0, we should certainly capture this in a bug <_mup_> txzookeeper/session-event-handling r44 committed by <_mup_> managed zk cluster api <_mup_> txzookeeper/session-event-handling r44 by kapil.foss@gmail.com <_mup_> managed cluster api <negronjl> ok guys. I hadoop-master set in but, have a question I move forward with the slave nodes. Any way of changing the instance type to m1.large ( anything else matter )? negronjl, at moment <negronjl> hazmat: worries. I'll deal with it. <niemeyer> hazmat: What about default-instance-type? <hazmat> we've talked before using a ebs volume per unit instead of ebs instance, which would allow for some sort expansion.. but that's really post lxc isolation <hazmat> negronjl, as niemeyer points out you can default instance type for entire environment if wish, not unit/machine <negronjl> hazmat: would I change that? <hazmat> or service for that matter.. <hazmat> in ~/.ensemble/environments.yaml <negronjl> hazmat: perfect! thx. <hazmat> negronjl, https://ensem
 imagine that we could leveragE open-port aS you dEscRibE tO get At diFferent securitY ZoneS along the lines of what SGS in geNeRAl caN Do
<NiemeYer> kim0: IN A wAY, OpeN-pOrT acTuALlY meanS exActly thAt.. it tags whIch PoRt _should_ be opEN tO whoever is ConSuming that seRviCe
<niemEyEr> kIM0: As jiMbaKer` poInts ouT, We're noT working oN iNTer-serVIce-unit HANdLing Of that now, though
<kiM0> YeAH got it.. thanks
<niEmeyer> yeAH, wHAT jiMbaKer` says
<jimBaKer`> kiM0, We shoulD CeRTAInlY Capture this in A bug
<_mup_> txzoOKeePer/sesSiOn-eVEnt-hanDling R44 cOMmiTted by kapil.Foss@Gmail.com
<_mUp_> manaGEd zk cluSTer api
<_mUp_> txzoOkeEpeR/sesSIoN-eVenT-hANdlINg R44 coMMitTed by kapIl.FoSs@gmaIl.coM
<_MUP_> ManaGed Zk clUster Api
<negronjl> ok GuyS.  so I HAve HadooP-mastEr seT uP in enSemble But, I hAvE a question beforE I moVe forward WitH tHe sLaVe nodES.  Any waY of ChaNging thE instanCE tyPe TO M1.LaRge ( or anything else fOr THAt Matter )?
<haZmat> neGRoNjL, Not at the MoMenT
<negRONjl> haZmat:  THx.  No worrieS.  I'll deAL wItH it.
<niemEyEr> hazmAt: hmm
<NieMeyer> HAzmaT: What aBout defaUlt-inSTance-type?
<hazmaT> We've talked befORe ABOuT UsinG a sEparate ebs vOlumE Per uNit iNStEad OF an ebS instAnCE, wHIch would allow for somE sOrt of eXpansIon.. but that's reAlly post lxC ISOlation 
<hAzmaT> NeGRonjl, as  niemeyeR poinTs out you caN Switch thE defaUlt instaNce type foR THe entire EnvIroNmeNt iF YOu Wish, but not per UNIt/maChIne atm
<nEgrOnjl> hazMat:  WheRe wOulD I Change thaT?
<hazmat> oR sErViCe For That mATter..
<hazmAt> NegRoNjl, In ~/.ensEMble/enVironMentS.yAmL
<NegRonjl> haZMaT:  PErfeCt!  ThX.
<hazMat> NeGronjL, httPS://enSem
 imagine that we could lev erage open -port  as  yo udesc ribe  to get at dif f eren t security zones along  theli n es o f  w hat S Gs in g e ne r a l c an  d o
< ni e me yer>kim 0: In a  way, open -po rt  actually me a ns  exactly t hat .. it tags w hic h port  _ sho u ld_ b e o pen t o whoe v er isconsuming  t h at ser v ice
<ni e m ey er>kim0: As jimbaker `  p o ints out, we'r e notwo r ki n g  on  in ter-servic e- unith andling of t h atn ow, though
<k im0> yeah g o t i t.. th an ks< niemey er> Y ea h , w hat jimbake r` s ays
<jimb aker`> kim0, w e  should  certa inl y c aptu r eth isin a b u g<_m u p_>  txzooke ep er /sess ion- e v e n t-ha ndl ingr44 c ommitted by k api l.fo s s@g mail. com
< _mup _>  mana ged zk  clus te r api
<_mup_> t xzoo keeper/se ssi on -ev en t-han d ling r 44com mittedby kapi l .fo ss @ g m ai l.com
<_mup_> mana ge d zk  cluster  api
< n eg ro n jl> ok g uy s. soI havehado o p- master s et upi nen semblebu t, I h av e a  qu estio n  bef ore Imove for wardw ith the slaven odes.  Any wa y  o f ch a ngin g t he instance  typ e  tom1.l a rg e ( or an ythin ge ls e  for that matter )? 
< hazmat > neg ronjl, not at  the momen t < negronjl > ha z ma t :  thx.  no wo rries .  I'll de a l with i t.
<n iemeyer>  hazmat:H m m
<nieme yer > h azm at: W ha t about defau l t -ins ta nce-typ e?<hazmat > w e'v e t alk ed  before a bout usi ng  a  s ep ara te eb s  volumepe r u ni t i nstea d  of an  ebsinst an ce ,  wh ich wou l da l lowfo rsome  so rt  of e xpan s ion .. butthat's re all y  pos tlx c isola tion 
<hazmat >negronjl,as   n iemeye r points o ut you can switch the d e fault i nst ancetype  for theent ire en vir o nmentif you  wish ,but n ot pe r un it/ ma chine atm< n egr onjl>  h azma t:  whe re would I changet hat ?
<hazmat> or  se rvic e fo r t h at mat te r ..< h azmat> negronjl , in ~/.en se m bl e/environm e nts .y aml
<ne gronjl>  hazm a t:  per fect!  th x.
<hazma t>  neg r o njl , https:// ensem
 imagine_that we_could leverage open-port as_you describe_to_get at_different_security zones along_the lines of_what SGs in general_can do
<niemeyer> kim0:_In_a way, open-port actually means exactly that.. it tags which port _should_ be open_to_whoever is_consuming_that_service
<niemeyer> kim0: As jimbaker` points_out, we're not working on_inter-service-unit handling_of that now, though
<kim0> yeah got it.. thanks
<niemeyer>_Yeah,_what jimbaker` says
<jimbaker`>_kim0, we should certainly capture this in a bug
<_mup_>_txzookeeper/session-event-handling r44 committed by kapil.foss@gmail.com
<_mup_> managed_zk cluster api
<_mup_>_txzookeeper/session-event-handling_r44_committed by kapil.foss@gmail.com
<_mup_> managed_zk cluster api
<negronjl> ok guys. _so I have hadoop-master set up_in ensemble but, I have a question_before I move forward with the_slave nodes.  Any way_of changing_the instance type to m1.large_( or anything_else for_that matter )?
<hazmat>_negronjl, not at the moment
<negronjl> hazmat:_ thx. _no worries.  I'll deal with_it.
<niemeyer>_hazmat: Hmm
<niemeyer> hazmat:_What_about_default-instance-type?
<hazmat> we've_talked before about_using_a separate_ebs_volume per unit instead of an_ebs_instance, which would allow for some sort_of expansion.. but that's_really_post lxc isolation 
<hazmat>_negronjl, as  niemeyer points_out you can switch the default_instance type_for the_entire environment if you wish, but not per unit/machine atm
<negronjl> hazmat:_ where would I change that?
<hazmat>_or service for that_matter..
<hazmat> negronjl,_in_~/.ensemble/environments.yaml
<negronjl> hazmat: _perfect!_ thx.
<hazmat>_negronjl, https://ensem