 should go with whatever you feel most comfortable with
<niemeyer> SpamapS: and we can change, of course
<niemeyer> SpamapS: But this is an area that will need your attention for sure
#ubuntu-ensemble 2011-06-17
<jimbaker> given that it's easy enough to have the wiki page in rst format, shouldn't really matter in terms of keeping content
<SpamapS> niemeyer: one thing that is proving difficult is parsing out the url in shell scripts. Its a lot easier if the scheme/hostname/port/path are already split up in the relation settings...
<niemeyer> SpamapS: Hmmm.. that's a nice utility we can provide
<niemeyer> SpamapS: url -host $FOO
<devcamcar> hey all, i'm evaluating how ensemble can be used alongside openstack - is there a story around multi-tenancy for ensemble? 
<SpamapS> devcamcar: ensemble *should* work with an openstack implementation, but I don't think anybody has tested it in a while.
<SpamapS> devcamcar: as far as "multi tenancy".. each tenant would have their own environment separated by access key ID's
<SpamapS> niemeyer: it seems a bit redundant to concatenate all of that every time into a URL, just to split it back out half the time into its parts anyway.
<SpamapS> niemeyer: so far the only two things that require a relation with something that would use the website interface are haproxy and squid reverse proxy.. both of which would need to split it up..
<devcamcar> SpamapS: i assumed as much, thanks!
<niemeyer> SpamapS: A url is by far the most common way to refer to a website..
<negronjl> niemeyer:  do you have an image-id so I can use m1.large instances?
<negronjl> niemeyer:  actually does ensemble use a particular image-id or can it use a default ubuntu 11.04 image?
<niemeyer> negronjl: We're using a custom base image mostly to speed booting up.. in the future it'll be just a
should go with whatever you feel most comfortable with 
 < niemeyer > SpamapS: and we can change, of path 
 < niemeyer > SpamapS: But this is an sphere that will need your attention for certain 
 # ubuntu - ensemble 2011 - 06 - 17 
 < jimbaker > yield that it's easy enough to have the wiki page in rst format, shouldn't very count in terms of keeping content 
 < SpamapS > niemeyer: one thing that is proving unmanageable is parsing out the url in shell scripts. Its a lot easier if the schema / hostname / port / path are already split up in the relation settings... 
 < niemeyer > SpamapS: Hmmm.. that's a decent utility we can provide 
 < niemeyer > SpamapS: url -host $ FOO 
 < devcamcar > hey all, i'm evaluating how ensemble can be use alongside openstack - is there a story around multi - tenancy for ensemble? 
 < SpamapS > devcamcar: ensemble * should * work with an openstack implementation, but I don't remember anybody has tested it in a while. 
 < SpamapS > devcamcar: as far as " multi tenancy ".. each tenant would have their own environment separated by entree key ID's 
 < SpamapS > niemeyer: it seems a bit redundant to concatenate all of that every time into a URL, just to separate it back away half the time into its parts anyway. 
 < SpamapS > niemeyer: so far the only two things that require a relation back with something that would practice the web site interface are haproxy and squid reverse proxy.. both of which would need to split it up.. 
 < devcamcar > SpamapS: i assume as much, thanks! 
 < niemeyer > SpamapS: A url is by far the most common direction to refer to a website.. 
 < negronjl > niemeyer:   do you have an image - idaho so I can use m1.large instances? 
 < negronjl > niemeyer:   actually does ensemble use a particular image - id or can it use a default ubuntu 11.04 image? 
 < niemeyer > negronjl: We're using a custom base picture largely to speed booting up.. in the future it'll be just a
 shluld go with whatever yom feel most comfortable with
<njemeyer> RpamapS: and we can change, of ciurse
<biemeyer> SpamapS: But tfis is an area thqt wmll need your atvsntion njr shve
#ubuutn-ensemble 2011-06-17
<jimbaler> given dhat it's easy anuuyh to have the wiki page in rst formwt, shoukdj't really mattgr in eerma of keeping content
<SpamapS> niemeysr: one uhing that is provong difficult is parsing okt tje url in shell scgipts. Its a lot wasier if thd scheme/hostname/port/pajh are already split up in the rdlatipn settingw...
<nuemfier> SpamapS: Immm.. trat's a nice mnility fe can lrovide
<niemeyev> SpakapW: url -host $FOO
<devcamcer> hey all, i'm evaluajing how etszmble can be used alobgwide mpenvtacy - ir tgece z storj acound multi-fenancy for ensemble? 
<SpamapS> dtvcwncar: ensemble *shoulq* rork with an openstack implementation, blt I don't think anybody has tested it in a while.
<DpamapS> dqvcamcar: as far as "multi tenancy".. each tenant woulg havx ghenv uqn environment separated by access key ID's
<Spama[A> mivmeyer: it seems a bit redundsnh yj concatenate all oy tgat every time intl a URL, just to split it nack out half the time into its parts auywqy.
<SpamapS> niemeyer: so far the onli two yhings that require a rzlatioh with somehhing thaf would use the wdbspte hnterfact are haproxy and fquid revxrse 'roxy.. bogh og whicr would nefd to split it up..
<devcamcwr> SpcmapS: i assumed as much, thanks!
<niemeyer> SpamapS: A url is by fsr thv most coimon eay to refer eo a website..
<neyronjl> nnemeyef:  do you gave an image-id so I can use m1.ldtge instances?
<iegronjl> giemwyer:  actuauuy does ensembke use a iaxticular umage-id or can it mse a sefault ubuntu 11.04 imqge?
<niemeyer> negtongl: Re'ge nsing d custom basa imxge kostlh to sptzd nooging up.. in the future it'nl bs just a
should go with whatever you feel most <niemeyer> and we change, of course an that will need attention for sure 2011-06-17 <jimbaker> given that it's easy to have the wiki page in rst format, shouldn't really matter in terms keeping content <SpamapS> niemeyer: one thing that is proving difficult is parsing out url shell Its lot easier if the scheme/hostname/port/path are already split up in the relation settings... <niemeyer> SpamapS: Hmmm.. a nice utility we can provide <niemeyer> SpamapS: -host $FOO <devcamcar> hey i'm evaluating how ensemble can used openstack - there story multi-tenancy for ensemble? devcamcar: ensemble *should* work with an openstack implementation, but I don't think anybody has tested it in while. <SpamapS> far as tenancy".. tenant have their own by access key ID's <SpamapS> niemeyer: bit redundant to concatenate all of that every into a just to split it back out the time into its parts anyway. <SpamapS> niemeyer: far the only two things that require a relation with something that would use the are haproxy and squid proxy.. both of would to it <devcamcar> SpamapS: assumed as much, thanks! <niemeyer> SpamapS: A url is by far most common way to refer to a website.. <negronjl> niemeyer: have image-id so I use m1.large instances? <negronjl> actually ensemble use a particular can use 11.04 <niemeyer> We're using a custom image mostly to speed booting in the future it'll
 should go with whatever you feEl most comfOrtabLe wIth
<NiEmeyEr> SpAmapS: and we can cHAnge, Of course
<niemeyer> Spamaps: But tHiS Is an AReA that Will neeD YoUR AttEnTiOn fOr SUrE
#ubunTu-eNsemble 2011-06-17
<Jimbaker> giVen ThAt it's easy enoUGh To have the wIki Page in rst forMat, ShouldN't ReaLLy matTer In terMs of keEPing coNtent
<SpamAps> NiemeyER: one thiNG ThAt is Proving difficult iS PaRSing out the url iN shell ScRIpTS. its A loT easier if tHe SchemE/HostnamE/PoRT/PAth ARe already spliT up in the relATioN settiNgS...
<niEMeyer> SPamaps: HMMm.. tHat's a nice utIlitY we can proVide
<niEMeyer> SpAMapS: url -Host $FOo
<deVcaMcar> HEy AlL, i'm EvALuaTInG hoW EnsEmble can Be UsEd aloNgsiDE OPEnstAck - Is thEre a sTory around mulTi-tEnanCY foR enseMble? 
<SPamaPS> DevcaMcar: enSemblE *sHould* work with an OpenStack implEmeNtAtiOn, But I dON't thinK anYboDy has teSted it iN A whIlE.
<sPAmApS> devcamcar: as far aS "mULTi Tenancy".. eAch tenANt WoULd have thEiR owN envIROnmenT sepARaTed by accEss key id's
<spAmapS> niEmEyer: it SeEms A biT reduNDant To concAtenate aLl of tHAt every time intO A URL, just to splIT iT BAcK Out hAlf The time into Its pARts aNywaY.
<spAmaPs> niemEyer: sO fAR tHE only two things that rEqUire a rElatiOn with somethiNg that woulD USE the websIte iNTeRFace are haproxy And sqUid reverse PRoxy.. both Of whiCh would nEed to spliT IT up..
<devcaMcaR> SpAmaPS: i ASSuMed as much, thanKS!
<NiemEyEr> SpamaPS: A Url is by Far The MosT coMmOn way to reFer to a weBsItE..
<nEgRonJl> nieMEyer:  do yoU hAve An ImaGe-id sO i can usE m1.larGe inStAnCEs?
<nEgronjl> NIeMEYer:  aCtUaLly dOes EnSemblE use A ParTicular Image-id or Can IT use A dEfAult ubuNtu 11.04 image?
<niemeYeR> negronjl: WE'rE usIng a cuSTOm base imAge mostly to speed booting UP.. in the fUtuRe it'lL be jUst a
 should go with whatever y ou feel mo st co mfo rta bl e wi th
< niemeyer> Spam a pS:and we can change, ofcours e< niem e ye r> Sp amapS:B ut t his  i sanar e athatwil l needyour atten tio nfor sure
#ub u nt u-ensemble  20 11-06-17
<ji mba ker> g iv ent hat i t's  easy  enoug h  to ha ve the wi ki page i n  rst fo r m at , sh ouldn't really ma t te r  in terms of k eeping  c o nt e n t
< Spa mapS> niem ey er: o n e thing th a t isp roving diffic ult is pars i ngout th eurl in she ll sc ri p ts.  Its a loteasi er if the  schem e /hostna m e/port/ path a realr eady sp li t u pi n t h erel a tio n settin gs .. .
<ni emey e r > Spam apS : Hm mm..that's a nice  ut ilit y  we  canprovi de
< ni emeye r> Spa mapS:  u rl -host $FOO
< devc amcar> he y a ll , i 'm  eval u atinghow  en semblecan beu sed  a l o n gs ide openstack - is  t h e re  a story  aroun d  m ul t i-tenanc yfor  ens e m ble?
<Sp a ma pS> devc amcar: en se mble *s ho uld* w or k w ith  an o p enst ack im plementa tion, but I don't th i nk anybody ha s  t e s te d  itina while.
<S pama p S> d evca m ca r:a s far  as " mu l ti tenancy".. each ten an t woul d hav e their own e nvironment s e paratedby a c ce s s key ID's
<Sp amapS > niemeyer :  it seem s a b it redun dant to c o n catenate  al l o f t hat e ve ry time intoa URL,  j ust tospl it it b ack  ou t h alf  t he time i nto itspa rt san ywa y.
<S p amapS> n ie mey er : s o far the on ly tw o th in gs tha t requi r ea rela ti on  wit h s om ethin g th a t w ould us e the web sit e  int er fa ce arehaproxy and s qu id reverse  p rox y.. bo t h  of whic h would need to split i t  up..
< dev camca r> S pamapS: i  as sumedasm uch, t hanks! 
<nie me yer > Spama p S :A u rl  is by far t hemostco mmon  way to  refer to a websit e ..<negronjl> ni eme yer: do  yo u  h a vean ima g e -id so I can us e m1.large  i n st ances?
<ne g ron jl > nieme yer:  a ctual l y doesensembleuse a par ti cula r ima ge-id or c an it us e a defau l t ubu n tu  11.0 4 i mage?<n iem eyer>  negro n jl:  We'r e usin ga cust om ba se  image m ostly to speed bootingup.. i n the  fu ture it'l l b e  ju st a
 should_go with_whatever you feel most_comfortable with
<niemeyer>_SpamapS:_and we_can_change, of course
<niemeyer>_SpamapS: But this_is an area that_will need your_attention_for sure
#ubuntu-ensemble 2011-06-17
<jimbaker> given that it's easy enough to have the wiki page in_rst_format, shouldn't_really_matter_in terms of keeping content
<SpamapS>_niemeyer: one thing that is_proving difficult_is parsing out the url in shell scripts._Its_a lot easier_if the scheme/hostname/port/path are already split up in the_relation settings...
<niemeyer> SpamapS: Hmmm.. that's a_nice utility we_can_provide
<niemeyer>_SpamapS: url -host $FOO
<devcamcar>_hey all, i'm evaluating how ensemble_can be used alongside openstack -_is there a story around multi-tenancy for_ensemble? 
<SpamapS> devcamcar: ensemble *should* work_with an openstack implementation, but_I don't_think anybody has tested it_in a while.
<SpamapS>_devcamcar: as_far as "multi_tenancy".. each tenant would have their_own environment separated_by access key ID's
<SpamapS> niemeyer: it_seems_a bit redundant_to_concatenate_all of_that every time_into_a URL,_just_to split it back out half_the_time into its parts anyway.
<SpamapS> niemeyer: so_far the only two_things_that require a relation_with something that would use_the website interface are haproxy and_squid reverse_proxy.. both_of which would need to split it up..
<devcamcar> SpamapS: i assumed_as much, thanks!
<niemeyer> SpamapS: A url_is by far the_most common_way_to refer to_a_website..
<negronjl> niemeyer:_ do you have an image-id so_I can_use m1.large instances?
<negronjl> niemeyer:  actually_does ensemble use a_particular_image-id or can it use a_default ubuntu 11.04 image?
<niemeyer> negronjl: We're_using a custom base image_mostly_to_speed booting up.. in the_future it'll be just a