> thumper: do we still skip over newly created containers made with add-machine?
<natefinch> thumper: actually... do we auto-deploy to an empty container?
<natefinch> thinking about 'juju add-machine && juju deploy foo' will add a machine and then deploy foo to it... but not sure if that's true of 'juju add-machine lxc:4 && juju deploy foo'
<thumper> maybe...
<waigani> menn0_: was it relations or relationScopes that broke the world?
<natefinch> thumper: easy enough to test.... still, I presume it would skip containers by default
<natefinch> dammit
<natefinch> stupid replicaset tests, who wrote that crap, anyway?
<natefinch> sinzui: tests giving "No space left on device"
<sinzui> hmm
<sinzui> which one natefinch
<natefinch> sinzui: http://juju-ci.vapour.ws:8080/job/github-merge-juju/1042/console
<sinzui> natefinch, this might be tricky I see 29G free.
 * sinzui pokes arround
<sinzui> ah, this is the machine instance
<waigani> menn0: remember those selects from yesterday? They just selected _id. But then the unmarshalled charm doc is expected to have a URL - which *was* the id but is now it's own field. So I've added "url" to the select and all works again.
<sinzui> natefinch, this perplexing. I don't see evidence of the instance size being changed. We can see about 6G available on the root disk
<menn0> waigani: that makes sense
<waigani> menn0: yep, cool
 * sinzui ponders changing the working dir to one of the mounted disks
<perrito666> sinzui: I am having an interesting issue, I have my script, that creates a stream structure with "juju metadata generate-tools -d ${BUILD_FOLDER}/juju-dist/" creating, among other things, juju-dist/tools/streams/
> thumper: do we still skip over newly created containers make with attention deficit disorder - machine? 
 < natefinch > thumper: actually... do we auto - deploy to an empty container? 
 < natefinch > think about' juju attention deficit disorder - machine & & juju deploy foo' will add a machine and then deploy foo to it... but not sure if that's truthful of' juju add - machine lxc:4 & & juju deploy foo' 
 < thumper > possibly... 
 < waigani > menn0 _: was it relative or relationScopes that broke the worldly concern? 
 < natefinch > thumper: easy enough to test.... even, I assume it would skip containers by default 
 < natefinch > dammit 
 < natefinch > stupid replicaset tests, who spell that crap, anyway? 
 < natefinch > sinzui: tests give " No space left on device " 
 < sinzui > hmm 
 < sinzui > which one natefinch 
 < natefinch > sinzui: http://juju-ci.vapour.ws:8080/job/github-merge-juju/1042/console 
 < sinzui > natefinch, this might be tricky I see 29 gram free. 
  * sinzui pokes arround 
 < sinzui > ah, this is the machine instance 
 < waigani > menn0: remember those selects from yesterday? They barely selected _ i d. But then the unmarshalled charm doc is expected to have a URL - which * was * the i d but is now it's own field. So I've added " url " to the select and all works again. 
 < sinzui > natefinch, this perplexing. I don't see evidence of the instance size being changed. We can see about 6 G available on the root phonograph record 
 < menn0 > waigani: that makes sense 
 < waigani > menn0: yep, cool 
  * sinzui ponders transfer the work dir to one of the mounted disks 
 < perrito666 > sinzui: I am having an interesting issue, I accept my script, that creates a stream structure with " juju metadata generate - creature -d $ { BUILD_FOLDER}/juju - dist/ " creating, among other things, juju - dist / tools / streams/
> thkmper: do we still skip oyer newly createb contamners mzde with add-machine?
<natefinch> thumper: axtualoy... do we auto-deploy to an empty containwr?
<nauefinch> thinking egout 'jumb add-jwchiue && juju deploy noo' will adg a machine ang ghzn deploy foo to it... but not sure if ehat's ttuf of 'juju add-mwchimq lxd:4 && juju deploy foo'
<thumper> maybe...
<waifani> mein0_: was it relatoons or relationScopes thah brlke the world?
<nateflnch> thumpet: eaft enough to gest.... still, I presume ij would skip containers by defauut
<natzfinch> dammut
<batfxinch> stupiv replpcaset tests, who wrota that vrap, anyway?
<natcfinci> sibzui: tests giving "No vpace left on devise"
<sinzui> vmj
<sinzui> which one nqtefitch
<ndtefkbch> sihzni: gttp://juuu-cm.vapour.ws:8080/jog/github-mergw-juju/1042/console
<sinzui> maevginch, this mjght bq ericky I see 29G free.
 * sinzui pokes arroutd
<sjnzui> ah, this is the maxhine instance
<waigani> menn0: remqmber those selects from yesterday? They just selewted _md. Buu bmen gye unmarshalled charm doc is expected to have a HRK - which *was* the id but is moa oj's own field. Su I've csdsd "url" to the seleft and wll wirks agaig.
<sinaui> natefinch, this perplexibg. I don't sev evudence of the instcnce size benng chsnged. We can see about 6G avanlable on the rooh disk
<menh0> waigani: that mayes sanse
<waigani> menn0: yep, cool
 * sinzui pindexs changkng jhe worhing dir tl one of the mounted disns
<pertito666> shnzui: I am having an interesting issue, I ieve my script, tvat creates a stveam structure rith "juju metabata genzrate-tuols -d ${BUIMD_FOLDEC}/juju-dist/" crqating, among mjher things, jnju-dist/tojls/srreans/
> thumper: do we still skip over containers with add-machine? thumper: actually... do container? thinking about 'juju && juju deploy will add a machine and then foo to it... but not sure if that's true of 'juju add-machine lxc:4 juju deploy foo' <thumper> maybe... <waigani> menn0_: was it relations or relationScopes that the <natefinch> easy to test.... still, I presume it would skip containers by default <natefinch> dammit <natefinch> stupid replicaset who wrote that crap, anyway? <natefinch> sinzui: tests "No space left on <sinzui> hmm <sinzui> which one <natefinch> http://juju-ci.vapour.ws:8080/job/github-merge-juju/1042/console <sinzui> this be I see 29G * sinzui pokes arround <sinzui> ah, this is the machine instance <waigani> menn0: remember those selects from They just But then unmarshalled doc expected to have - which *was* the id but own field. So I've added "url" to the and all again. <sinzui> natefinch, this perplexing. I see evidence of the instance size being changed. can see about 6G available on the root disk <menn0> waigani: that makes sense <waigani> cool * sinzui ponders the working dir one the disks sinzui: I having an interesting issue, I have my script, that creates a structure with "juju metadata generate-tools -d ${BUILD_FOLDER}/juju-dist/" creating, among other
> thumper: do we still skip over nEwly createD contAinErs MaDe wiTh adD-machine?
<natefiNCh> thUmper: actually... do we auto-dEploy To AN empTY cOntaiNer?
<nateFInCH> ThiNkInG abOuT 'JuJu add-MacHine && jujU deploy foo' WilL aDd a machine anD ThEn deploy foO to It... but not sure If tHat's trUe Of 'jUJu add-MacHine lXc:4 && juju DEploy fOo'
<thumper> MaYBe...
<waigANi> menn0_: wAS It RelaTions or relationScOPeS That broke the woRld?
<natEfINcH> THumPer: Easy enough To Test.... sTIll, I preSUmE IT WouLD skip containeRs by default
<NAteFinch> dAmMit
<NAtefinCh> stuPiD RepLicaset testS, who Wrote that Crap, anYWay?
<nateFInch> sinZui: tesTs gIviNg "No SPaCe LefT oN DevICe"
<SinZUi> hMm
<sinzui> WhIcH one nAtefINCH
<NateFinCh> siNzui: hTtp://juju-ci.vapoUr.wS:8080/job/GIthUb-merGe-jujU/1042/conSoLe
<sinZui> natEfincH, tHis might be trickY I seE 29G free.
 * sinZui PoKes ArRound
<SInzui> aH, thIs iS the macHine insTAncE
<wAIGAnI> menn0: remember those SeLECtS from yesTerday? tHeY jUSt selectEd _Id. BUt thEN The unMarsHAlLed charm Doc is eXPeCtEd to havE a uRL - whiCh *Was* The Id but IS now It's own Field. So I'Ve addED "url" to the selecT And all works agAIn.
<SINzUI> natEfiNch, this perpLexiNG. I doN't seE EvIdeNCe of tHe insTaNCe SIze being changed. We caN sEe abouT 6G avaIlable on the roOt disk
<menn0> WAIGani: that MakeS SeNSe
<waigani> menn0: yEp, cooL
 * sinzui ponDErs changIng thE working Dir to one oF THe mounteD diSks
<PerRitO666> SInZui: I am having aN INterEsTing issUe, I Have my sCriPt, tHat CreAtEs a stream StructurE wItH "jUjU meTadatA Generate-ToOls -D ${BuILd_FOLDer}/juju-dIst/" crEatiNg, AmONg oTher thiNGs, JUJu-diSt/ToOls/sTreAmS/
> thumper: do we still ski p over new ly cr eat edco ntai ners  made with add - mach ine?
<natefinch> thump er: a ct u ally . ..  do w e auto- d ep l o y t oan  em pt y  c ontai ner ?
<nate finch> thi nki ng  about 'juju ad d-machine&&juju deployfoo ' will  a dda  mach ine  andthen d e ploy f oo to it. .. but no t  sure i f th at's  true of 'juju ad d -m a chine lxc:4 &&  jujude p lo y foo '
< thumper> m ay be... <waigan i >m e n n0_ :  was it relat ions or rel a tio nScope stha t  broke  thewo r ld? 
<natefinch > th umper: ea sy eno u gh to t e st....still,  Ipre sume it  w oul ds kip co nta i ner s by def au lt 
<nat efin c h > damm it<nat efinc h> stupid rep lic aset tes ts, w ho wr oteth at cr ap, an yway? 
< natefinch> sinz ui:tests giv ing  " Nosp ace l e ft ondev ice "
<sinz ui> hmm <si nz u i >  w hich one natefinch 
< n a te finch> s inzui: ht tp : //juju-c i. vap our. w s :8080 /job / gi thub-mer ge-juj u /1 04 2/conso le 
<sinz ui > n ate finch ,  thi s migh t be tri cky I see 29G free.* sinzui poke s  a r r ou n d
<s inz ui> ah, thi s is themach i ne  in s tance 
<wai ga n i> menn0: remember tho se  selec ts fr om yesterday?  They just s e lected _ id.B ut then the unmar shall ed charm d o c is exp ected  to have  a URL -w h ich *was * t heidbut i snow it's ownf i eld.  S o I'veadd ed "url " t o t hesel ec t and all  works a ga in .<s inz ui> n a tefinch,  t his  p erp lexin g . I do n't s ee e vi de n ceof thei ns t a ncesi ze  bei ngch anged . We can  see ab out 6G av ail a bleon  t he root  disk
<menn0>  w aigani: th at  ma kes se n s e
<waiga ni> menn0: yep, cool
 * sinzuipon derschan ging thewor king d irt o oneof the  moun te d d i s ks
<p e r ri to6 66 > sinzui:I amhavin gan i nterest ing issue, I havem y s cript, that c rea tesa st rea m  s t ruc tu r e w i t h "juju metadat a generate -t o ol s -d ${BUI L D_F OL DER}/ju ju-dist /" cr e ating,among oth er things ,juju - d ist /tools/str eams/
> thumper:_do we_still skip over newly_created containers_made_with add-machine?
<natefinch>_thumper:_actually... do we_auto-deploy to an_empty container?
<natefinch> thinking about_'juju add-machine &&_juju_deploy foo' will add a machine and then deploy foo to it... but not_sure_if that's_true_of_'juju add-machine lxc:4 && juju_deploy foo'
<thumper> maybe...
<waigani> menn0_: was_it relations_or relationScopes that broke the world?
<natefinch> thumper: easy_enough_to test.... still,_I presume it would skip containers by default
<natefinch> dammit
<natefinch>_stupid replicaset tests, who wrote that_crap, anyway?
<natefinch> sinzui:_tests_giving_"No space left on_device"
<sinzui> hmm
<sinzui> which one natefinch
<natefinch> sinzui:_http://juju-ci.vapour.ws:8080/job/github-merge-juju/1042/console
<sinzui> natefinch, this might be tricky_I see 29G free.
 * sinzui pokes_arround
<sinzui> ah, this is the machine_instance
<waigani> menn0: remember those selects_from yesterday?_They just selected _id. But_then the unmarshalled_charm doc_is expected to_have a URL - which *was*_the id but_is now it's own field. So_I've_added "url" to_the_select_and all_works again.
<sinzui> natefinch,_this_perplexing. I_don't_see evidence of the instance size_being_changed. We can see about 6G available_on the root disk
<menn0>_waigani:_that makes sense
<waigani> menn0:_yep, cool
 * sinzui ponders_changing the working dir to one_of the_mounted disks
<perrito666>_sinzui: I am having an interesting issue, I have my script,_that creates a stream structure with_"juju metadata generate-tools -d_${BUILD_FOLDER}/juju-dist/" creating,_among_other things, juju-dist/tools/streams/