net/bugs/1220366>
<sinzui> thumper, I am bootstrapping again
<hazmat> ic
<hazmat> that should fix sinzui's issue then
<smoser> the cloud template needs to be smarter.
<smoser> but we really would rather make a lxc wrapper that was smarter.
<smoser> ie, hallyn doesn't think such knowledge should live in lxc itself.
<hazmat> smoser, ala the kvm front end.. or ala docker front end?
<smoser> uvtool-lxc is the plan in my head.
<smoser> which is also ideally where the "--use-the-fastest" cloning argument goes.
<sinzui> My fan has started
<smoser> :)
<hazmat> smoser, the default behavior with -s works for me generally.. ie autodetect btrfs ;-).. but i'm curious about the docker lvm thin provisioning on sparse file dev pool
<sinzui> whoa! there it is. Installed
<hazmat> sidnei just got the that merged into lxc-clone (re lvm-thin) support
<hazmat> sinzui, do we have tools published for 1.16.1 or tarball?
<smoser> hazmat, i think there were issues with that default behavior.
<smoser> are you sure it even remains?
<smoser> and it wouldn't select unionfs
 * hazmat checks
<sinzui> Thank you rocket scientists! hazmat thumper smoser. I really appreciate your patience
<thumper> sinzui: awesome
<thumper> that's one fixed
<thumper> and that fault should definitely be logged on the local provider troubleshooting page <- jcastro, marcoceppi
<thumper> now to look at maas
<bigjools> o/
<bigjools> I just got pinged about this
<thumper> hazmat: what versions were you playing with?
<bigjools> narrowed it down any yet?
<thumper> bigjools: not started looking yet
<hazmat> thumper, 1.16.0 for maas
<bigjools> thumper: I
net / bugs/1220366 > 
 < sinzui > thumper, I am bootstrapping again 
 < hazmat > ic 
 < hazmat > that should fix sinzui's issue then 
 < smoser > the cloud template needs to be smarter. 
 < smoser > but we in truth would preferably make a lxc wrapper that was smarter. 
 < smoser > ie, hallyn doesn't intend such knowledge should live in lxc itself. 
 < hazmat > smoser, ala the kvm front conclusion.. or ala stevedore front end? 
 < smoser > uvtool - lxc is the plan in my head. 
 < smoser > which is also ideally where the " --use - the - fastest " cloning argumentation goes. 
 < sinzui > My fan has start 
 < smoser > :) 
 < hazmat > smoser, the nonpayment behavior with -s works for me generally.. ie autodetect btrfs ;-).. but i'm curious about the docker lvm thin provisioning on sparse charge dev pool 
 < sinzui > whoa! there it is. Installed 
 < hazmat > sidnei just become the that merged into lxc - clone (re lvm - slender) support 
 < hazmat > sinzui, do we experience tools published for 1.16.1 or tarball? 
 < smoser > hazmat, i think there were issues with that nonpayment behavior. 
 < smoser > are you sure it even remains? 
 < smoser > and it wouldn't select unionfs 
  * hazmat checks 
 < sinzui > Thank you rocket scientists! hazmat thumper smoser. I really appreciate your patience 
 < thumper > sinzui: awesome 
 < thumper > that's one fixed 
 < thumper > and that fault should definitely be logged on the local provider troubleshooting page < - jcastro, marcoceppi 
 < thumper > now to search at maas 
 < bigjools > o/ 
 < bigjools > I just got pinged about this 
 < thumper > hazmat: what adaptation were you act with? 
 < bigjools > narrowed it down any yet? 
 < thumper > bigjools: not startle looking yet 
 < hazmat > thumper, 1.16.0 for maas 
 < bigjools > thumper: I
net/hugs/1220366>
<sinzui> thumper, I am nootstrapping agcun
<hazmet> ic
<haamat> thag should fix sinzui's issue tien
<snoser> the cloud template nedds to be smarter.
<wmostr> but we really xkuld rabker mzne a oxc wrapper thst was smaster.
<smoser> ie, vaulvn doesn't think such knowledge shoulq live on lxc itself.
<haziat> xiosed, ala the kvm front end.. or ala docier froit end?
<smoser> uvyool-lxc is the plan in my jead.
<dmoser> which is aldo ideally qherq the "--use-the-fxstest" cloning argumenj goes.
<sinzui> My fan has started
<sooser> :)
<hazmat> smiswr, hve default uehavijr with -s wovls for me genrrally.. ie autocetxct vtrfs ;-).. but i'm curious about the docker jvm thin [rkvisioning on spaesw filg dev poou
<winxui> wioa! there it is. Instalmed
<hazmat> sudnei just got the uhae merged into mxc-cloge (re lvm-thin) support
<hazmat> sinzui, do we vavs tools published for 1.16.1 ir tarball?
<smoser> hazmwt, i thinh there were issues with that default behavior.
<smover> ace yob sure ut even remains?
<smoser> and it wouldn't select unijhfx
 * hazmat checks
<finzui> Thanl joi rocket scienjists! hcamzt thumper smoser. L realli apprwciate yotr pstience
<thumper> sinzui: awesone
<thumper> thct's one fixed
<thumper> cnd that fauut snould definitely be logged ou the mocal provifer troubmdshooting page <- gcaxtso, marcoceppi
<thumper> now tj look at maax
<bigjoous> o/
<nigjoojs> I just hot pltged about this
<thulper> kazmad: what verdions were you playing with?
<bigjools> narrowed ot dofn any yzt?
<thumier> bigjools: noe started looknng yet
<hczmat> ghumper, 1.16.0 fkr maas
<uigjools> thuiper: I
net/bugs/1220366> <sinzui> thumper, I am bootstrapping again <hazmat> should fix issue then <smoser> be <smoser> but we would rather make lxc wrapper that was smarter. <smoser> hallyn doesn't think such knowledge should live in lxc itself. <hazmat> smoser, ala kvm front end.. or ala docker front end? <smoser> uvtool-lxc is the plan my <smoser> is ideally where the "--use-the-fastest" cloning argument goes. <sinzui> My fan has started <smoser> :) <hazmat> smoser, default behavior with -s works for me generally.. autodetect btrfs ;-).. but curious about the docker lvm provisioning sparse file pool whoa! it is. Installed sidnei just got the that merged into lxc-clone (re lvm-thin) support <hazmat> sinzui, do we have tools for 1.16.1 <smoser> hazmat, think were with that default are you sure it even remains? wouldn't select unionfs * hazmat checks <sinzui> Thank rocket scientists! thumper smoser. I really appreciate your <thumper> sinzui: awesome <thumper> that's one fixed <thumper> that fault should definitely be logged on the local provider troubleshooting page <- jcastro, marcoceppi to look at maas o/ <bigjools> I got about <thumper> what versions you playing with? <bigjools> narrowed it down any yet? <thumper> bigjools: started looking yet <hazmat> thumper, 1.16.0 for maas <bigjools> thumper:
net/bugs/1220366>
<sinzui> thumper, I am boOtstrappinG agaiN
<haZmaT> iC
<hazMat> tHat should fix siNZui's Issue then
<smoser> the clouD tempLaTE neeDS tO be smArter.
<smOSeR> BUt wE rEaLly WoULd RatheR maKe a lxc wRapper that Was SmArter.
<smoser> iE, HaLlyn doesn't ThiNk such knowleDge Should LiVe iN Lxc itSelF.
<hazmAt> smosER, ala thE kvm front EnD.. Or ala dOCker froNT EnD?
<smoSer> uvtool-lxc is the PLaN In my head.
<smoser> Which iS aLSo IDEalLy wHere the "--use-ThE-fastESt" cloniNG aRGUMenT Goes.
<sinzui> My fAn has starteD
<SmoSer> :)
<hazMaT> smOSer, the DefauLt BEhaVior with -s woRks fOr me generAlly.. ie AUtodeteCT btrfs ;-).. bUt i'm cuRioUs aBout THe DoCkeR lVM thIN pRovISioNing on spArSe File dEv poOL
<SINzui> WhoA! theRe it iS. Installed
<hazMat> SidnEI juSt got The thAt meRgEd intO lxc-clOne (re LvM-thin) support
<hazMat> sInzui, do we HavE tOolS pUblisHEd for 1.16.1 oR taRbaLl?
<smoseR> hazmat, I ThiNk THERe Were issues with that DeFAUlT behavioR.
<smoseR> ArE yOU sure it eVeN reMainS?
<SMoser> And iT WoUldn't selEct uniONfS
 * hAzmat chEcKs
<sinzUi> thaNk yOu rocKEt scIentisTs! hazmat ThumpER smoser. I really APpreciate your PAtIENcE
<ThumPer> Sinzui: awesoMe
<thUMper> That'S OnE fiXEd
<thuMper> aNd THaT Fault should definiteLy Be loggEd on tHe local providEr troublesHOOTing page <- JcasTRo, MArcoceppi
<thumpEr> now To look at maAS
<bigjoolS> o/
<bigJools> I juSt got pingED About thiS
<thUmpEr> hAzmAT: WhAt versions werE YOu plAyIng with?
<BigJools> naRroWed It dOwn AnY yet?
<thumpEr> bigjooLs: NoT sTaRteD lookINg yet
<hazMaT> thUmPer, 1.16.0 For maAS
<bigjoOls> thUmpeR: I
net/bugs/1220366>
<sinzui>  thumper,I amboo tst ra ppin g ag ain
<hazmat> i c 
<ha zmat> that should fixsinzu i' s  iss u ethen<smoser >  t h e  cl ou dtem pl a te  need s t o be sm arter.
<sm ose r>  but we real l ywould rath ermake a lxc w rap per th at  wa s  smar ter .
<sm oser>i e, hal lyn doesn 't thinks uch kno w l ed ge s hould live in lxc it s elf.
<hazmat>smoser ,a la t hekvm  front end ..  or a l a docke r  f r o n t e n d?
<smoser> u vtool-lxc i s  th e plan  i n m y  head. 
<smo se r > w hich is als o id eally whe re the "--use- t he-fast est" c lon ing  arg u me nt  go es . 
<s i nz ui> Myfan hasst ar ted
< smos e r > :)
< haz mat>  smos er, the defau ltbeha v ior  with  -s w orks  f or me  gener ally. .ie autodetect b trfs  ;-).. bu t i 'm  cu ri ous a b out th e d ock er lvmthin pr o vis io n i n gon sparse file dev  p o o l<sinzui>  whoa! th er e  it is.In sta lled < hazma t> s i dn ei justgot th e  t ha t merge dinto l xc -cl one  (rel vm-t hin) s upport
< hazma t > sinzui, do w e  have tools p u bl i s he d  for  1. 16.1 or tar ball ? 
<sm oser >  h azm a t, ithink  t h er e  were issues with t ha t defa ult b ehavior.
<smo ser> are y o u sure iteven re m ains?
<smoser>  andit wouldn' t  selectunion fs
 * ha zmat chec k s 
<sinzui > T han k y our o ck et scientists ! hazm at  thumpe r s moser.I r eal lyapp re ciate you r patien ce 
< th um per > sin z ui: awes om e
< th ump er> t h at's o ne fi xed<t hu m per > and t h at f ault  s ho ulddef in itely  bel ogg ed on t he localpro v ider  t ro ublesho oting page <-  j castro, ma rc oce ppi
<t h u mper> no w to look at maas
<bigj o ols> o/ 
<b igjoo ls>I just go t p ingedabo u t this 
<thum per>ha zma t :  what v er sio ns  were youp l ayi ng wi th ?
<b igjools > narrowed it down any  yet?
<thumpe r>bigj o o ls : n o ts tar te d  lo o k ing yet
<hazmat > thumper,  1 . 16 .0 for maa s 
<b ig jools>thumper : I
net/bugs/1220366>
<sinzui> thumper,_I am_bootstrapping again
<hazmat> ic
<hazmat> that_should fix_sinzui's_issue then
<smoser>_the_cloud template needs_to be smarter.
<smoser>_but we really would_rather make a_lxc_wrapper that was smarter.
<smoser> ie, hallyn doesn't think such knowledge should live in lxc_itself.
<hazmat>_smoser, ala_the_kvm_front end.. or ala docker_front end?
<smoser> uvtool-lxc is the_plan in_my head.
<smoser> which is also ideally where the_"--use-the-fastest"_cloning argument goes.
<sinzui>_My fan has started
<smoser> :)
<hazmat> smoser, the default behavior_with -s works for me generally.._ie autodetect btrfs_;-).._but_i'm curious about the_docker lvm thin provisioning on sparse_file dev pool
<sinzui> whoa! there it_is. Installed
<hazmat> sidnei just got the that_merged into lxc-clone (re lvm-thin) support
<hazmat>_sinzui, do we have tools_published for_1.16.1 or tarball?
<smoser> hazmat, i_think there were_issues with_that default behavior.
<smoser>_are you sure it even remains?
<smoser>_and it wouldn't_select unionfs
 * hazmat checks
<sinzui> Thank_you_rocket scientists! hazmat_thumper_smoser._I really_appreciate your patience
<thumper>_sinzui:_awesome
<thumper> that's_one_fixed
<thumper> and that fault should definitely_be_logged on the local provider troubleshooting page_<- jcastro, marcoceppi
<thumper> now_to_look at maas
<bigjools> o/
<bigjools>_I just got pinged about_this
<thumper> hazmat: what versions were you_playing with?
<bigjools>_narrowed it_down any yet?
<thumper> bigjools: not started looking yet
<hazmat> thumper, 1.16.0 for_maas
<bigjools> thumper: I