> maybe a --force on upgrade, to bypass the version checking
<kirkland> hazmat: sure, i'd use that (probably all the time :-)
<hazmat> looks pretty straightforward to implement
<kirkland> SpamapS: the only tricky part is that you have to set a password for ubuntu for the formula to be useful
<kirkland> SpamapS: so i'm keen on finding a way of doing that, before blogging about it :-)
<hazmat> SpamapS, we could use a md5 checksum for verifying instead of numbers, but we're playing pretty fast an loose with version numbers at that point
<SpamapS> kirkland: right thats where config settings come.
<SpamapS> hazmat: we've talked about this before.. --force is a nice band-aid. Users will *still* hate the revno. ;)
<kirkland> SpamapS: right, unimplemented at this point, no?
<SpamapS> principle of least surprise: I changed my formula, it should deploy anew.
<SpamapS> At least warn me that you didn't deploy the same content as whats on disk locally.
<SpamapS> kirkland: --force is unimplemented, as is the config settings (not sure which you were asking about)
<kirkland> SpamapS: config
<kirkland> SpamapS: i'm looking for the best work around for setting an ubuntu password
<kirkland> SpamapS: to a configurable value
<kirkland> SpamapS: or randomly generating it
<kirkland> SpamapS: and getting that back to the user
<kirkland> SpamapS: perhaps as a relation?
<SpamapS> kirkland: randomly generate it, and log it with ensemble-log INFO level
<SpamapS> ensemble-log --log-level INFO password=f94k1X
<SpamapS> kirkland: I suggest pwgen for the generation btw.
<SpamapS> kirkland: ajaxterm runs its own HTTP daemon right?
<kirkland> SpamapS: yeah, on 8022
<kirkland> Spam
> maybe a --force on upgrade, to bypass the version checking 
 < kirkland > hazmat: surely, i'd practice that (credibly all the time :-) 
 < hazmat > looks pretty aboveboard to implement 
 < kirkland > SpamapS: the only slippery part is that you have to sic a password for ubuntu for the formula to be useful 
 < kirkland > SpamapS: indeed i'm keen on finding a means of suffice that, before blogging about it :-) 
 < hazmat > SpamapS, we could use a md5 checksum for verifying instead of numbers, but we're playing pretty fast an loose with adaptation numbers at that point 
 < SpamapS > kirkland: right that s where config settings fall. 
 < SpamapS > hazmat: we've talked about this before.. --force is a nice band - aid. user will * still * hate the revno. ;) 
 < kirkland > SpamapS: right, unimplemented at this point, no? 
 < SpamapS > principle of least surprise: I changed my rule, it should deploy anew. 
 < SpamapS > At least warn me that you didn't deploy the same content as what s on disk locally. 
 < SpamapS > kirkland: --force is unimplemented, as is the config settings (not sure which you were asking about) 
 < kirkland > SpamapS: config 
 < kirkland > SpamapS: i'm looking for the best work around for setting an ubuntu password 
 < kirkland > SpamapS: to a configurable value 
 < kirkland > SpamapS: or randomly generating it 
 < kirkland > SpamapS: and getting that back to the user 
 < kirkland > SpamapS: perhaps as a relation? 
 < SpamapS > kirkland: randomly render it, and log it with ensemble - log INFO level 
 < SpamapS > ensemble - logarithm --log - degree INFO password = f94k1X 
 < SpamapS > kirkland: I indicate pwgen for the generation btw. 
 < SpamapS > kirkland: ajaxterm runs its own HTTP daemon right? 
 < kirkland > SpamapS: yeah, on 8022 
 < kirkland > Spam
> majbe a --force on upgrade, tu bypass the vetsuon chxcking
<kjrkland> fazmat: sure, i'd use that (probebly all uke time :-)
<hazmat> looks pretty snraightfoewarv to implement
<kiciland> SicmapS: bhe oulb tricky part ix that you have to set a pxsdword for ubuntu for the formula to be usegup
<kirkland> SpamwpS: xj i'm keen on finding a way of doing thzt, befoge blogging about it :-)
<hazmat> SpamapS, we coulf usf a md5 checksum fog verifying insewad of numbefs, but we'rt 'laying prejty fast an loose with version njmberx at that kojnh
<VpamapS> kirjland: right thats where cmnfig srttings come.
<Spsma'S> hqzmat: we've talked abont this before.. --force is a nica yand-aid. Users will *stulo* hatg the revvi. ;)
<kkrkmaid> ApamapD: rmght, unimplsmented at rhis point, no?
<SpamapX> [gonciple of lsast str[rise: I changed my formula, it should dekloy znew.
<SpamapS> At least waen me that you didn't feploy thq same content as whats on disk locally.
<SpamapS> kisklanv: --worec kw knimplemented, as is the config settings (not stde wmich you were ashing about)
<kornlsgd> SpamapS: covfig
<kixilznd> SpamapS: i'm looning fot the vest work aroind for setting an ubuntu pqssword
<kirklcnd> SpamapS: to a confngurable valbe
<kirkkand> XpamapS: or randomly genzratinf it
<kirklanf> SpamapS: xnd getting that babk tm the ustf
<kirkland> SpamapS: perhaps es a xelation?
<RpamspS> kiwkland: ranfomly generate it, and loh it cith ansemble-loh INFO level
<SpamapS> ensemble-log --log-level INFO pdssford=f94k1X
<S'amapS> kirkland: I stggest pwgen fpr the yeneragion btw.
<SpzmapS> kmrkland: ajaxeerm runs its lwn HTTP daekon righe?
<kirjlane> SpamaoR: yeah, on 8022
<kirkkand> Spam
> maybe a --force on upgrade, to version <kirkland> hazmat: i'd use that <hazmat> pretty straightforward to <kirkland> SpamapS: the tricky part is that you have set a password for ubuntu for the formula to be useful <kirkland> SpamapS: i'm keen on finding a way of doing that, before blogging about it <hazmat> we use md5 checksum for verifying instead of numbers, but we're playing pretty fast an loose with version at that point <SpamapS> kirkland: right thats where settings come. <SpamapS> hazmat: talked about this before.. --force a band-aid. Users *still* the ;) <kirkland> SpamapS: unimplemented at this point, no? <SpamapS> principle of least surprise: I changed my formula, it should deploy <SpamapS> At me that didn't the content as whats locally. <SpamapS> kirkland: --force is unimplemented, config settings (not sure which you were asking <kirkland> SpamapS: <kirkland> SpamapS: i'm looking for the work around for setting an ubuntu password <kirkland> to a configurable value <kirkland> SpamapS: or randomly generating it <kirkland> SpamapS: and getting that the user <kirkland> SpamapS: as a relation? kirkland: generate and it with INFO level <SpamapS> ensemble-log --log-level INFO password=f94k1X <SpamapS> kirkland: I suggest for the generation btw. <SpamapS> kirkland: ajaxterm runs its own right? SpamapS: yeah, on <kirkland> Spam
> maybe a --force on upgrade, to bypAss the versIon chEckIng
<KiRklaNd> haZmat: sure, i'd use tHAt (prObably all the time :-)
<hazmat> Looks PrETty sTRaIghtfOrward tO ImPLEmeNt
<KiRklAnD> spAmapS: The Only triCky part is tHat YoU have to set a pASsWord for ubuNtu For the formulA to Be usefUl
<KirKLand> SPamApS: so I'm keen ON findiNg a way of dOiNG that, bEFore bloGGInG aboUt it :-)
<hazmat> SpamapS, WE cOUld use a md5 checkSum for VeRIfYINg iNstEad of numbeRs, But we'RE playinG PrETTY faST an loose with vErsion numbeRS at That poInT
<SpAMapS> kiRklanD: rIGht Thats where cOnfiG settings Come.
<SpAMapS> hazMAt: we've tAlked aBouT thIs beFOrE.. --fOrcE iS A niCE bAnd-AId. USers will *StIlL* hate The rEVNO. ;)
<KirkLanD> SpaMapS: rIght, unimplemeNteD at tHIs pOint, nO?
<SpamApS> pRiNciplE of leaSt surPrIse: I changed my foRmulA, it should DepLoY anEw.
<spamaPs> At leaSt wArn Me that yOu didn't DEplOy THE SaMe content as whats on DiSK LoCally.
<SpaMapS> kiRKlAnD: --Force is uNiMplEmenTED, as is The cONfIg settinGs (not sURe WhIch you wErE askinG aBouT)
<kiRklanD> spamApS: conFig
<kirklAnd> SpAMapS: i'm looking fOR the best work aROuND FoR SettIng An ubuntu pasSworD
<KirkLand> sPaMaps: To a coNfiguRaBLe VAlue
<kirkland> SpamapS: Or RandomLy genErating it
<kirkLand> Spamaps: AND getting That BAcK To the user
<kirklAnd> SpAmapS: perhaPS as a relaTion?
<SPamapS> kiRkland: ranDOMly generAte It, aNd lOg iT WItH ensemble-log Info levEl
<spamapS> EnsEmble-loG --loG-leVel iNFo pAssword=f94k1x
<SpamapS> KiRkLaNd: i suGgest PWgen for tHe GenErAtiOn btw.
<sPamapS> KirklAnd: aJaXtERm rUns its oWN Http daeMoN rIght?
<KirKlAnd> SpAmaps: YeaH, on 8022
<kirkLand> Spam
> maybe a --force on upgra de, to byp ass t hever si on c heck ing
<kirkland> hazm at: sure, i'd use that  (pro ba b ly a l lthe t ime :-) <h a z mat >lo oks  p r et ty st rai ghtforw ard to imp lem en t
<kirkland> Sp amapS: the  on ly tricky pa rtis tha tyou havetoset a  passw o rd for  ubuntu f or the fo r mula to b eusef ul
<kirkland> Spa m ap S : so i'm keenon fin di n ga way  of  doing tha t,  befo r e blogg i ng a b out it :-)
<hazma t> SpamapS, wecouldus e a md5 ch ecksu mf orverifying i nste ad of num bers,b ut we'r e  playin g pret tyfas t an lo os e w it h  ve r si onn umb ers at t ha tpoint 
<Sp a m a p S> k irk land : rig ht thats wher e c onfi g  se tting s com e.
< Sp amapS > hazm at: w e' ve talked about  thi s before. . - -f orc eis an ice ba nd- aid . Users  will * s til l* h a te  the revno. ;)
<ki rk l a nd > Spamap S: rig h t,  u n implemen te d a t th i s  poin t, n o ?<SpamapS > prin c ip le  of lea st  surpr is e:I c hange d  myformul a, it sh ouldd eploy anew.
<S p amapS> At lea s tw a rn me t hat  you didn't  dep l oy t he s a me  co n tentas wh at s  o n  disk locally.
<Spa ma pS> ki rklan d: --force is  unimpleme n t e d, as is  the co n fig settings ( not s ure whichy ou wereaskin g about) 
<kirklan d >  SpamapS : c onf ig<ki r k la nd> SpamapS:i ' m lo ok ing for  th e bestwor k a rou ndfo r setting  an ubun tu  p as sw ord 
<kir k land> Sp am apS :toa con f igurab le va lue<k ir k lan d> Spam a pS : or r an do mlygen er ating  it< kir kland>SpamapS:and gett in gthat ba ck to the use r<kirkland>  S pam apS: p e r haps asa relation?
<SpamapS> k i rkland:  ra ndoml y ge nerate it , a nd log  it with e nsembl e-log  I NFO l evel< S pa map S>  ensemble- l o g - -log- le velINFO pa ssword=f94k1X
<Spa m apS > kirkland: I  su gges t pw gen fo r  th eg ene r a tion btw.
<Spam apS> kirkl an d :ajaxterm r u nsit s own H TTP dae mon r i ght?
<k irkland>SpamapS:ye ah,o n  80 22
<kirkla nd> Spam 
> maybe_a --force_on upgrade, to bypass_the version_checking
<kirkland>_hazmat: sure,_i'd_use that (probably_all the time_:-)
<hazmat> looks pretty straightforward_to implement
<kirkland> SpamapS:_the_only tricky part is that you have to set a password for ubuntu for_the_formula to_be_useful
<kirkland>_SpamapS: so i'm keen on_finding a way of doing_that, before_blogging about it :-)
<hazmat> SpamapS, we could use_a_md5 checksum for_verifying instead of numbers, but we're playing pretty fast_an loose with version numbers at_that point
<SpamapS> kirkland:_right_thats_where config settings come.
<SpamapS>_hazmat: we've talked about this before.._--force is a nice band-aid. Users_will *still* hate the revno. ;)
<kirkland> SpamapS:_right, unimplemented at this point, no?
<SpamapS>_principle of least surprise: I_changed my_formula, it should deploy anew.
<SpamapS>_At least warn_me that_you didn't deploy_the same content as whats on_disk locally.
<SpamapS> kirkland:_--force is unimplemented, as is the_config_settings (not sure_which_you_were asking_about)
<kirkland> SpamapS: config
<kirkland>_SpamapS:_i'm looking_for_the best work around for setting_an_ubuntu password
<kirkland> SpamapS: to a configurable value
<kirkland>_SpamapS: or randomly generating_it
<kirkland>_SpamapS: and getting that_back to the user
<kirkland> SpamapS:_perhaps as a relation?
<SpamapS> kirkland: randomly_generate it,_and log_it with ensemble-log INFO level
<SpamapS> ensemble-log --log-level INFO password=f94k1X
<SpamapS> kirkland: I_suggest pwgen for the generation btw.
<SpamapS>_kirkland: ajaxterm runs its_own HTTP_daemon_right?
<kirkland> SpamapS: yeah,_on_8022
<kirkland> Spam