Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2015-10-16

| Channels | #salt index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:02 jimklo joined #salt
00:03 frankS2 joined #salt
00:08 grep_away joined #salt
00:08 dober joined #salt
00:08 bharper joined #salt
00:08 ecdhe joined #salt
00:08 sastorsl_ joined #salt
00:08 Noiz joined #salt
00:08 wunki joined #salt
00:08 eitzei joined #salt
00:08 N-Mi_ joined #salt
00:08 Ac-town joined #salt
00:08 Bateau_ joined #salt
00:08 eXistenZNL joined #salt
00:08 klocek joined #salt
00:08 Mate joined #salt
00:08 twork joined #salt
00:08 wm-bot4 joined #salt
00:08 pviktori joined #salt
00:08 dustywusty joined #salt
00:08 zsoftich joined #salt
00:08 sinonick joined #salt
00:08 lahwran joined #salt
00:08 scooby2 joined #salt
00:08 samed joined #salt
00:08 jerrcs_ joined #salt
00:08 amontalban joined #salt
00:08 onovy joined #salt
00:08 nexsja joined #salt
00:08 superseb joined #salt
00:08 Edgan joined #salt
00:08 ronrib joined #salt
00:08 scc joined #salt
00:08 ambientsound joined #salt
00:08 the_lalelu joined #salt
00:08 etw joined #salt
00:08 nahamu joined #salt
00:08 darix joined #salt
00:08 Guest14970 joined #salt
00:08 Hipikat joined #salt
00:08 toddnni joined #salt
00:08 iamtew joined #salt
00:08 horus_plex joined #salt
00:08 mnaser joined #salt
00:08 armguy joined #salt
00:08 Cliph joined #salt
00:08 canci joined #salt
00:08 pppingme joined #salt
00:08 Zachary_DuBois joined #salt
00:08 garthk joined #salt
00:08 Gabemo joined #salt
00:08 Smoked_Duck joined #salt
00:08 mirko joined #salt
00:08 lazybear joined #salt
00:08 ligthert joined #salt
00:08 cmek joined #salt
00:08 nikogonzo joined #salt
00:08 jasonrm joined #salt
00:08 sovern joined #salt
00:08 intr1nsic joined #salt
00:08 LotR joined #salt
00:08 InAnimaTe joined #salt
00:08 jayne joined #salt
00:08 robot9 joined #salt
00:08 [dee] joined #salt
00:08 retr0h_ joined #salt
00:08 sarlalian joined #salt
00:08 stickmack joined #salt
00:08 omenlabs joined #salt
00:08 phpdave11 joined #salt
00:08 pjs joined #salt
00:08 jay__ joined #salt
00:08 erjohnso joined #salt
00:08 Puckel_ joined #salt
00:08 RandyT joined #salt
00:08 cro joined #salt
00:08 ange joined #salt
00:08 bVector joined #salt
00:08 afics joined #salt
00:08 gthank joined #salt
00:08 sinh joined #salt
00:08 VSpike joined #salt
00:08 xMopxShell joined #salt
00:08 bryguy joined #salt
00:08 tvinson joined #salt
00:08 mr_chris joined #salt
00:08 MindDrive joined #salt
00:08 renoirb joined #salt
00:08 whytewolf joined #salt
00:08 janne_ joined #salt
00:08 Cottser joined #salt
00:08 fedepalla joined #salt
00:08 aurynn joined #salt
00:08 EvaSDK joined #salt
00:08 thebwt joined #salt
00:08 blue0ctober joined #salt
00:08 trebortech_1 joined #salt
00:08 cswang_ joined #salt
00:08 Yoda-BZH joined #salt
00:08 honestly joined #salt
00:08 lynxman joined #salt
00:08 mikepea joined #salt
00:08 Gareth joined #salt
00:08 SubOracle joined #salt
00:08 penguinpowernz joined #salt
00:08 ashmckenzie joined #salt
00:08 Buzer joined #salt
00:08 vlcn joined #salt
00:08 twiedenbein joined #salt
00:08 v0rtex joined #salt
00:08 brucewang joined #salt
00:08 Norrland joined #salt
00:08 titilambert joined #salt
00:08 monokrome joined #salt
00:08 nihe joined #salt
00:08 robawt joined #salt
00:08 thehaven_ joined #salt
00:08 Eureka70_ joined #salt
00:08 tyler-baker joined #salt
00:08 overyander joined #salt
00:08 ksj joined #salt
00:08 cwyse joined #salt
00:08 moogyver joined #salt
00:08 markm_ joined #salt
00:08 GreatSnoopy joined #salt
00:08 mrwboilers joined #salt
00:08 w1gz joined #salt
00:08 minaguib joined #salt
00:08 hrumph joined #salt
00:08 nidr0x joined #salt
00:08 sirtaj joined #salt
00:08 Cerales joined #salt
00:08 msciciel1 joined #salt
00:08 NVX joined #salt
00:08 phx joined #salt
00:08 daed joined #salt
00:08 djinni` joined #salt
00:08 Reinhart joined #salt
00:08 jfroche joined #salt
00:08 a7p joined #salt
00:08 LeProvokateur joined #salt
00:08 kalessin joined #salt
00:08 andi- joined #salt
00:08 daschatten joined #salt
00:08 Edur joined #salt
00:08 jhujhiti joined #salt
00:08 dabb joined #salt
00:08 catpiggest joined #salt
00:08 gwmngilfen joined #salt
00:08 hansi_ joined #salt
00:08 notnotpeter joined #salt
00:08 kwork joined #salt
00:08 bastiandg joined #salt
00:08 jmreicha_ joined #salt
00:08 baffle joined #salt
00:08 sybix joined #salt
00:08 ajw0100 joined #salt
00:08 neilf_ joined #salt
00:08 jcristau joined #salt
00:08 Antiarc joined #salt
00:08 giantlock joined #salt
00:08 tzero joined #salt
00:08 ze- joined #salt
00:08 alexlist joined #salt
00:08 freelock joined #salt
00:08 nadley joined #salt
00:08 GothAck joined #salt
00:08 dijit joined #salt
00:08 fbettag joined #salt
00:08 programmerq joined #salt
00:08 froztbyte joined #salt
00:08 Number6_ joined #salt
00:08 |_[O_O]_| joined #salt
00:08 OliverUK joined #salt
00:08 Akhter joined #salt
00:08 mpanetta joined #salt
00:08 zer0def joined #salt
00:08 douardda joined #salt
00:08 aRkadeFR joined #salt
00:08 itsamenathan joined #salt
00:08 murkey_ joined #salt
00:08 nkuttler joined #salt
00:08 peters-tx joined #salt
00:08 tru_tru joined #salt
00:08 moloney joined #salt
00:08 saltman joined #salt
00:08 TranquilityBase joined #salt
00:08 mackripeum_ joined #salt
00:08 ^C joined #salt
00:08 crashmag joined #salt
00:08 KingJ joined #salt
00:08 flebel joined #salt
00:08 shnguyen joined #salt
00:08 MeltedLux joined #salt
00:08 ashirogl joined #salt
00:08 6JTAB9DIN joined #salt
00:08 viq joined #salt
00:08 darkhuy joined #salt
00:08 Shirkdog_ joined #salt
00:08 shanemhansen joined #salt
00:08 dkrae joined #salt
00:08 kant_ joined #salt
00:08 Qwazerty joined #salt
00:08 packeteer joined #salt
00:08 gmoro joined #salt
00:08 dean joined #salt
00:08 brent4 joined #salt
00:08 xaviern joined #salt
00:08 riftman joined #salt
00:08 _mel_ joined #salt
00:08 CryptoMer joined #salt
00:08 jay_d joined #salt
00:08 chutzpah joined #salt
00:08 alexhayes joined #salt
00:08 paolo joined #salt
00:08 cb joined #salt
00:08 emid_ joined #salt
00:08 dthorman_ joined #salt
00:08 davromaniak joined #salt
00:08 godlike joined #salt
00:08 Hazelesque joined #salt
00:08 mortis_ joined #salt
00:08 dork joined #salt
00:08 is_null joined #salt
00:08 amatas joined #salt
00:08 danielcb joined #salt
00:08 Nazzy joined #salt
00:08 m0nky joined #salt
00:08 LinuxHorn joined #salt
00:08 antonw joined #salt
00:08 pmcnabb joined #salt
00:08 JPaul joined #salt
00:08 MK_FG joined #salt
00:08 SaveTheRbtz joined #salt
00:08 unusedPhD joined #salt
00:08 Rkp joined #salt
00:08 eofs joined #salt
00:08 Nebraskka joined #salt
00:08 g3cko joined #salt
00:08 tmmt_ joined #salt
00:08 leev joined #salt
00:08 Sacro joined #salt
00:08 tongpu joined #salt
00:08 TomJepp joined #salt
00:08 gtmanfred joined #salt
00:08 jY joined #salt
00:08 FreeSpencer joined #salt
00:08 chitown joined #salt
00:08 mephx joined #salt
00:08 womble joined #salt
00:08 rofl____ joined #salt
00:08 aidalgol joined #salt
00:09 GnuLxUsr joined #salt
00:09 bregalad joined #salt
00:09 stupidnic joined #salt
00:09 elektrix_ joined #salt
00:09 moapa_ joined #salt
00:09 lionel joined #salt
00:09 jaybocc2 joined #salt
00:09 mohae joined #salt
00:09 vandemar joined #salt
00:09 egil joined #salt
00:09 NightMonkey joined #salt
00:09 dyasny joined #salt
00:09 Riz joined #salt
00:09 ShibMcNe joined #salt
00:09 mlanner joined #salt
00:09 indispeq_ joined #salt
00:09 UForgotten_ joined #salt
00:09 tercenya joined #salt
00:09 SheetiS1 joined #salt
00:09 sporkd2 joined #salt
00:09 mattiasr joined #salt
00:09 bernieke joined #salt
00:09 codehotter joined #salt
00:09 hoonetorg joined #salt
00:09 sifusam joined #salt
00:09 smooth_penguin joined #salt
00:09 ventris joined #salt
00:09 vexati0n joined #salt
00:09 eliasp joined #salt
00:09 Phil-Work joined #salt
00:09 shawnbutts joined #salt
00:09 jgelens joined #salt
00:09 dstokes joined #salt
00:09 ajolo joined #salt
00:09 Ahlee joined #salt
00:09 gadams joined #salt
00:09 MTecknology joined #salt
00:09 JoeJulian joined #salt
00:09 sjohnsen joined #salt
00:09 ahammond joined #salt
00:10 frankS2 joined #salt
00:11 subsignal joined #salt
00:11 danemacm1 joined #salt
00:11 dayid joined #salt
00:11 rawzone joined #salt
00:11 pfalleno1 joined #salt
00:11 moderation joined #salt
00:11 _JZ_ joined #salt
00:11 pratikmallya joined #salt
00:11 teryx510 joined #salt
00:11 lkannan joined #salt
00:11 borgstrom joined #salt
00:11 big_area joined #salt
00:11 bougie joined #salt
00:11 APLU joined #salt
00:11 Aleks3Y joined #salt
00:11 karlthane joined #salt
00:11 utahcon joined #salt
00:11 emostar_ joined #salt
00:11 Karunamon|2 joined #salt
00:11 mrtrosen joined #salt
00:11 nobrak_ joined #salt
00:11 izibi joined #salt
00:12 dingo joined #salt
00:12 Trivium joined #salt
00:12 Hydrosine joined #salt
00:12 analogbyte joined #salt
00:12 Twiglet joined #salt
00:12 keekz joined #salt
00:12 Heartsbane joined #salt
00:12 stooj joined #salt
00:12 evidence joined #salt
00:12 JPT joined #salt
00:12 sixninetynine joined #salt
00:12 mdupont joined #salt
00:12 mihait joined #salt
00:12 jesusaurus joined #salt
00:12 cswang joined #salt
00:12 wintamute joined #salt
00:12 FredFoo joined #salt
00:12 eagles0513875 joined #salt
00:12 drags joined #salt
00:12 agj joined #salt
00:12 Jarus joined #salt
00:12 mschiff joined #salt
00:12 tampakrap joined #salt
00:13 Ludo- joined #salt
00:13 rhand_ joined #salt
00:13 jacksontj joined #salt
00:13 ablemann joined #salt
00:13 muep joined #salt
00:13 babilen_ joined #salt
00:13 Tritlo joined #salt
00:13 munhitsu joined #salt
00:13 bfoxwell joined #salt
00:13 mage_ joined #salt
00:13 teebes joined #salt
00:13 ronny joined #salt
00:13 Micromus joined #salt
00:13 chamunks joined #salt
00:13 daemonkeeper joined #salt
00:13 kiorky joined #salt
00:13 kaictl joined #salt
00:13 hacfi_ joined #salt
00:13 quasiben joined #salt
00:13 Azulez joined #salt
00:13 Jahkeup joined #salt
00:13 ws2k3 joined #salt
00:13 ashb joined #salt
00:13 tcolvin joined #salt
00:13 bbhoss joined #salt
00:13 cornfeedhobo joined #salt
00:13 WildPikachu joined #salt
00:13 rickflare joined #salt
00:13 iggy joined #salt
00:13 Barbarossa joined #salt
00:13 JonGretar joined #salt
00:13 nicksloan joined #salt
00:13 ramblinpeck joined #salt
00:13 mattl joined #salt
00:13 CaptTofu joined #salt
00:13 Knuta joined #salt
00:13 manfred joined #salt
00:13 masterkorp joined #salt
00:13 saltsa joined #salt
00:13 calebj_ joined #salt
00:13 llua joined #salt
00:13 dewdrop joined #salt
00:13 Ph-x joined #salt
00:13 cwright joined #salt
00:13 simmel joined #salt
00:13 czchen joined #salt
00:13 yml joined #salt
00:13 creppe joined #salt
00:13 Horgix joined #salt
00:13 gerhardqux joined #salt
00:13 jeblair joined #salt
00:13 gnord joined #salt
00:13 Arendtsen joined #salt
00:15 tkharju joined #salt
00:15 faliarin joined #salt
00:15 KyleG joined #salt
00:15 amcorreia joined #salt
00:15 Jimlad joined #salt
00:15 darvon joined #salt
00:15 davidbanham joined #salt
00:15 CaptainMagnus joined #salt
00:15 mullein joined #salt
00:15 morsik joined #salt
00:15 pcn joined #salt
00:15 Kelsar joined #salt
00:15 oravirt joined #salt
00:15 MadsRC joined #salt
00:15 trave joined #salt
00:15 codekobe joined #salt
00:15 simonmcc joined #salt
00:15 wiqd joined #salt
00:15 rlarkin joined #salt
00:15 rodr1c joined #salt
00:15 supermike__ joined #salt
00:15 bstaz joined #salt
00:15 arapaho joined #salt
00:15 lowfive joined #salt
00:15 davedash joined #salt
00:15 grepory joined #salt
00:15 akitada joined #salt
00:15 goki joined #salt
00:15 tja joined #salt
00:15 terratom1 joined #salt
00:15 helgi joined #salt
00:15 bezaban joined #salt
00:15 jor joined #salt
00:15 Ouzo_12- joined #salt
00:15 charli joined #salt
00:15 shadowsun joined #salt
00:15 hax404 joined #salt
00:15 __alex joined #salt
00:15 sk_0 joined #salt
00:15 basepi joined #salt
00:15 kutenai joined #salt
00:15 ramishra joined #salt
00:16 blueyed joined #salt
00:16 terinjokes joined #salt
00:16 jimklo joined #salt
00:16 David_B55__ joined #salt
00:16 tmclaugh[work] joined #salt
00:16 rideh joined #salt
00:16 mfournier joined #salt
00:16 N-Mi joined #salt
00:16 SneakyPhil joined #salt
00:16 dec joined #salt
00:16 papertigers joined #salt
00:16 Depado joined #salt
00:16 tmkerr joined #salt
00:16 OliverMT joined #salt
00:16 Gilou joined #salt
00:16 mattrobenolt joined #salt
00:16 fhh joined #salt
00:16 bbradley joined #salt
00:16 robinsmidsrod joined #salt
00:16 arnoldB_ joined #salt
00:16 SteamWells joined #salt
00:16 jfred joined #salt
00:16 gg joined #salt
00:16 gtaylor joined #salt
00:16 btorch joined #salt
00:16 wych joined #salt
00:16 apejens joined #salt
00:16 asoc joined #salt
00:16 ahale joined #salt
00:16 Rockj joined #salt
00:16 hillna joined #salt
00:16 Phtes joined #salt
00:16 georgemarshall joined #salt
00:16 Corey joined #salt
00:16 Sketch joined #salt
00:17 papertigers is it possible to not run a state in an sls file by default?
00:17 papertigers found the doc
00:17 DaveQB joined #salt
00:17 nzero joined #salt
00:17 writteno1 joined #salt
00:17 oeuftete joined #salt
00:17 edulix joined #salt
00:17 StolenToast joined #salt
00:17 eichiro joined #salt
00:17 zemm joined #salt
00:17 JoeHazzers joined #salt
00:17 deus_ex joined #salt
00:17 Nazca__ joined #salt
00:17 dh joined #salt
00:17 MaZ- joined #salt
00:17 fxhp joined #salt
00:17 jab416171 joined #salt
00:17 openfly joined #salt
00:17 tedski joined #salt
00:17 pdx6_ joined #salt
00:17 LtLefse joined #salt
00:17 dimeshake joined #salt
00:17 ksalman joined #salt
00:17 maduro joined #salt
00:17 artemz joined #salt
00:17 Diaoul joined #salt
00:17 nebuchadnezzar joined #salt
00:17 beardo joined #salt
00:17 rome_390 joined #salt
00:17 ntropy joined #salt
00:17 Aikar joined #salt
00:17 oherrala joined #salt
00:17 koomi joined #salt
00:19 fbettag joined #salt
00:19 Lionel_Debroux joined #salt
00:19 nledez joined #salt
00:19 s0undt3ch joined #salt
00:19 arif-ali joined #salt
00:19 pmcg joined #salt
00:20 geomyidae_ joined #salt
00:20 aqua^c joined #salt
00:20 eightyeight joined #salt
00:20 Ryan_Lane joined #salt
00:20 monkeybo1 joined #salt
00:20 yetAnotherZero joined #salt
00:20 NachoDuck joined #salt
00:20 jemejones_ joined #salt
00:20 otter768 joined #salt
00:20 tr_h joined #salt
00:20 timoguin joined #salt
00:20 debian112 joined #salt
00:20 averell joined #salt
00:20 briner joined #salt
00:20 seblu joined #salt
00:20 dandelo joined #salt
00:20 Striki joined #salt
00:20 jbub joined #salt
00:20 ]V[_ joined #salt
00:20 garphy`aw joined #salt
00:20 Ssquidly joined #salt
00:20 saltstackbot joined #salt
00:20 scarcry joined #salt
00:20 ropes joined #salt
00:20 Garo_ joined #salt
00:20 gazarsgo joined #salt
00:20 GrueMaster joined #salt
00:20 hajhatten joined #salt
00:20 pprkut joined #salt
00:20 Ymage joined #salt
00:20 ernetas joined #salt
00:20 qman__ joined #salt
00:20 abele joined #salt
00:20 marcinkuzminski joined #salt
00:20 boargod3 joined #salt
00:20 yac joined #salt
00:20 culexor joined #salt
00:20 carmony joined #salt
00:20 akoumjian joined #salt
00:20 imanc joined #salt
00:20 BogdanR joined #salt
00:20 smkelly joined #salt
00:20 Archwyrm joined #salt
00:20 evilrob joined #salt
00:20 kuromagi joined #salt
00:20 ThomasJ joined #salt
00:20 Ch3LL_ joined #salt
00:20 dalibro joined #salt
00:20 geekatcmu joined #salt
00:20 unusedPhD_ joined #salt
00:20 Emantor joined #salt
00:20 lude joined #salt
00:20 TaiSHi joined #salt
00:20 synical joined #salt
00:20 twobitsprite joined #salt
00:20 nlb joined #salt
00:20 Laogeodritt joined #salt
00:20 _ikke_ joined #salt
00:20 rubenb joined #salt
00:20 voxxit joined #salt
00:20 virusuy joined #salt
00:20 berto- joined #salt
00:20 kavakava joined #salt
00:20 clone1018_ joined #salt
00:20 al joined #salt
00:20 dwfreed joined #salt
00:20 [vaelen] joined #salt
00:23 hardwire joined #salt
00:25 rofl____ joined #salt
00:26 fbettag joined #salt
00:26 UtahDave left #salt
00:27 zmalone joined #salt
00:30 `chris joined #salt
00:31 fbettag joined #salt
00:31 aidalgol joined #salt
00:31 cliluw joined #salt
00:31 mpanetta joined #salt
00:31 armyriad joined #salt
00:32 paha joined #salt
00:35 eliasp joined #salt
00:35 baweaver joined #salt
00:35 toastedpenguin joined #salt
00:35 mission712 joined #salt
00:38 zwi joined #salt
00:39 teebes joined #salt
00:40 otter768 joined #salt
00:41 NV joined #salt
00:50 larsfronius joined #salt
00:53 zwi joined #salt
00:56 Singularo joined #salt
01:00 kermit joined #salt
01:07 mehakkahlon joined #salt
01:10 teebes joined #salt
01:13 Akhter joined #salt
01:15 OliverUK joined #salt
01:39 catpigger joined #salt
01:45 zwi joined #salt
01:47 zmalone joined #salt
01:52 gtaylor joined #salt
01:53 zwi1 joined #salt
01:54 mpanetta joined #salt
01:58 zwi joined #salt
01:59 scoates joined #salt
02:03 zwi1 joined #salt
02:03 supermike__ joined #salt
02:08 teebes joined #salt
02:08 Akhter joined #salt
02:09 mikepea joined #salt
02:14 favadi joined #salt
02:19 otter768 joined #salt
02:23 ajw0100 joined #salt
02:33 eichiro joined #salt
02:36 mpanetta joined #salt
02:40 jmreicha joined #salt
02:44 jmreicha_ joined #salt
02:52 evle joined #salt
03:05 k_sze joined #salt
03:14 alexhayes mmm, how does one install just salt-key?
03:14 alexhayes I thought it might come down with bootstrap-salt but it doesn't seem to (when installing a minion)
03:15 alexhayes Does it only get installed on a master?
03:18 overyander alexhayes, it is only installed with master, it is not needed on minion.
03:18 overyander it is used by master to keep track of minion auth keys
03:18 overyander \away
03:20 alexhayes yeh thats what I thought, i just wanted it to create generate some keys
03:20 alexhayes for minion less masters
03:20 alexhayes sorry... masterless minions.
03:21 alexhayes that may some day be connected to master
03:21 alexhayes overyander: do you even need a key for a masterless minion?
03:36 favadi joined #salt
03:47 robawt joined #salt
03:51 _JZ_ joined #salt
03:52 al joined #salt
03:52 Ymage joined #salt
03:53 zmalone joined #salt
04:12 moogyver alexhayes: no, you wouldn't need a key - it's masterless
04:13 moogyver and the keys are for talking to .. the master
04:22 ashirogl joined #salt
04:26 iggy salt-key's key generation code is in salt-common on most distros... would be pretty easy to just grab the salt-key script from github and run it if you neeeded it
04:41 anmolb joined #salt
04:47 ageorgop joined #salt
04:52 larsfronius joined #salt
04:54 favadi joined #salt
04:56 rdas joined #salt
04:57 ramteid joined #salt
05:12 Cidan joined #salt
05:30 malinoff joined #salt
05:32 dankrs joined #salt
05:38 mpanetta joined #salt
05:44 marnom joined #salt
05:46 marnom Hi guys, anyone else getting 404's accessing the 'new' Debian mirror http://repo.saltstack.com/apt/debian ? It used to work fine but gives 404's on multiple machines atm
05:50 felskrone joined #salt
05:56 katyucha joined #salt
06:04 iggy marnom: new packages came out today, try apt-get update
06:06 marnom iggy, thanks for the response, I'm trying apt-get update's on multiple nodes but it gives 404's
06:06 iggy oh
06:07 iggy basepi: http://repo.saltstack.com/apt/debian 404'ing on apt-get update
06:07 iggy that's the best we can do for now
06:07 kinetic joined #salt
06:08 lb joined #salt
06:08 marnom I just opened https://github.com/saltstack/salt/issues/28007 for this
06:08 saltstackbot [#28007]title: The new Debian Salt repository seems to be having issues | This used to work (been using it all week) but suddenly this morning on a 'pkg.upgrade refresh=True' of our development environment:...
06:09 rdas joined #salt
06:09 vvoody joined #salt
06:11 marnom iggy: it's not a critical issue at the moment as the salt bootstrap script seems to grab it's packages from somewhere else so we can still deploy new VM's, just not update the currently running ones :)
06:16 honestly mrrgh. the statefile is compiled on every minion, isn't it?
06:22 sirex joined #salt
06:24 kinetic joined #salt
06:34 iggy honestly: has to be
06:35 eliasp meh, "top_file_merging_strategy: merge" seems to be non-functional/broken… this will be fun to debug ;(
06:35 marnom I had a lot of issues with that after upgrading to 2015.8 :(
06:36 eliasp having a single top.sls in a separate repo with just a 'master' branch… "state.show_top saltenv=non-base-env" returns just nothing
06:36 honestly iggy: yeah. I'm just not awake enough yet to make assumptions about things like that.
06:36 marnom Ended up with top_file_merging_strategy: same and pillar_source_merging_strategy: recurse
06:37 iggy eliasp: I think there's an issue open about that
06:37 eliasp marnom: for "top_file_merging_strategy: same" I'd have to maintain branches for all envs in my top.sls repo and always keep them in sync/rebased… not so much fun and error-prone ;(
06:37 eliasp iggy: k, I'll try to find it
06:38 kinetic joined #salt
06:39 marnom eliasp, I've 'stacked file roots' so it works out for our use case, but might not be ideal for all setups
06:39 fourbitays joined #salt
06:39 eliasp marnom: yeah, with file_roots instead of GitFS this is doable
06:39 marnom also, the fact that pillarenvs and saltenvs are apparently not a 1-1 relation seems very odd to me
06:40 GreatSnoopy joined #salt
06:40 fourbitays Hey
06:40 marnom it would be ideal if the master could force this to be the same
06:40 eliasp the whole Salt environment model is unfortunately a bit "broken" ;(
06:40 malinoff it has been broken from the very beginning
06:41 marnom yeah, I feel Salt has great potential but the environments need to be solid, it's awesome for DTAP stuff
06:41 marnom and the change in 2015.8 regarding the pillars and envs caused our pillarenvs to be published to all nodes, so our dev nodes had access to prod credentials. Not really awesome, had to change all credentials :(
06:42 eliasp ugh, that's quite bad
06:42 marnom I guess we should've tested this on a seperate environment, so not totally to blame on salt obviously :) but it was really unexpected
06:42 malinoff marnom: I've googled DTAP as https://en.wikipedia.org/wiki/DPT_vaccine
06:42 saltstackbot [WIKIPEDIA] DPT vaccine | "TDAP redirects here. For the trade organisation in Pakistan, see Trade Development Authority (Pakistan).DPT (also DTP and DTwP) refers to a class of combination vaccines against three infectious diseases in humans: diphtheria, pertussis (whooping cough), and tetanus. The vaccine components include diphtheria..."
06:42 malinoff saltstackbot: shut up
06:42 marnom malinoff, try https://en.wikipedia.org/wiki/Development,_testing,_acceptance_and_production :)
06:42 saltstackbot [WIKIPEDIA] Development, testing, acceptance and production | "The acronym DTAP is short for Development, Testing, Acceptance and Production. It is a rather common acronym in ICT expressing a phased approach of software testing and deployment. The four letters in DTAP denote the following common steps:The program or component is developed on a Development system..."
06:43 malinoff come on
06:43 malinoff marnom: where is performance?
06:43 eliasp ;)
06:43 marnom performance?
06:43 kinetic joined #salt
06:43 malinoff marnom: I don't know a single production-ready project which performance hasn't been tested
06:44 eliasp iggy: any idea which issue you've had in mind regarding top_file_merging_strategy?https://github.com/saltstack/salt/issues/12483 - this fix is already part of 2015.8.0
06:44 saltstackbot [#12483]title: Top SLS compilation does not behave the same as Docs describe | Hi...
06:44 marnom malinoff, I'm sorry I'm not sure I follow?
06:44 marnom I wasn't talking about performance afaik :)
06:45 malinoff marnom: yeah, I was
06:45 malinoff from my perspective, DTAP is missing one core environment, performance
06:45 marnom ah OK I see your point, but doesn't that depend on how you implement it
06:45 kant joined #salt
06:46 marnom for example, we let our devs run wild on the dev environment. Then when they think it works, we deploy in test and unit-test + benchmark the code etc
06:46 marnom so we definately do performance testing as part of our DTAP process
06:46 favadi joined #salt
06:46 marnom then some stakeholders accept the new feature/whatever in accept and then we highstate prod env, it's pretty neat
06:47 fourbitays I've been trying to switch to RAET and now can't seem to start the master, tracebacks are here: http://pastebin.com/W1ZPQWy1
06:47 fourbitays Any ideas?
06:47 OliverUK joined #salt
06:48 malinoff marnom: we never run unit tests when deploying new code. We run them once as the first step of deb/rpm build process
06:49 malinoff and 'benchmarking' isn't really performance testing
06:49 marnom malinoff, we run it on each commit so dev's can keep track if it's working
06:49 marnom then before we merge any code to master, the unit tests should off course be passing. Otherwise we're not even gonna try and deploy it :D
06:49 malinoff marnom: ok, misunderstood you then :)
06:50 marnom malinoff, no worries I may not have been entirely clear, it's still eary hours over here :)
06:51 edulix joined #salt
06:53 kinetic joined #salt
06:53 marnom malinoff, I agree on benchmarking not being indicative of real world performance but it's as close as we can get automated... What do you use?
06:54 malinoff marnom: at first, we're trying to set our boundaries. E.g. how many users our system must handle. And we make our performance infrastructure to respect this number of users.
06:54 malinoff benchmarking is about getting numbers of 'how fast your system is in this test', no more
06:55 malinoff it doesn't respect your real-world scenarios
06:55 malinoff for perftesting we use jmeter and grinder when jmeter goes bad with his GC spikes
06:56 marnom I'm going to look into those, thanks! We definately have set requirements for our infra but it can be hard to measure
06:56 honestly shit. at some point it becomes really impractical to partition off salt setups for different hostgroups because there are some services like keepalived that are just running in lots of different places.
06:56 honestly grrr.
06:57 marnom sounds like you need more pillar based config for nodes maybe?
06:57 malinoff marnom: also we use graphite as metrics database and collectd as system metrics collector
06:57 marnom yeah we do use those, but we're currently running some custom benchmarking tools
06:58 malinoff marnom: so we basically making the expected load and see what's going on on our VMs
06:58 stephanbuys joined #salt
06:58 malinoff marnom: and if we see that we can, for example, tune sysctl - we're tuning sysctl
06:58 kinetic joined #salt
06:59 marnom malinoff, that sounds like a nice workflow. We currently use more of a shotgun approach; ramp up load on all systems and see what breaks, and then start tuning to make it not break
06:59 malinoff marnom: huh
06:59 malinoff sounds like a great wasting of time :)
06:59 marnom I agree lol
06:59 malinoff we had systems which were ok at ~100 active users
07:00 malinoff so instead of shitload our VMs we simply guaranteed that current VMs can handle 100 active users
07:00 malinoff that's how performance testing differs from benchmarking
07:00 marnom I agree that's a lot more mature hehe
07:01 marnom I won't bother you with the politics involved over here, but I wish we could work like that as well
07:01 honestly marnom: all my config is in pillar
07:01 malinoff well, it's not more mature, it's just different approach
07:01 marnom honestly, I might have misunderstood your issue then
07:01 malinoff marnom: if you're building a framework, you probably must go with benchmarking
07:01 honestly I'm using salty-ssh with completely separate
07:01 honestly I'm using salty-ssh with completely separate "instances"
07:02 honestly salt-ssh...
07:05 marnom malinoff, I'll have to ask my boss again as to how scalable our app should be. Currently the statement is 'it should scale to world domination' lol\
07:05 marnom which is kinda hard to benchmark/guarantee :P
07:05 malinoff marnom: we had projects with this exact wish, all failed
07:05 malinoff because people were spending their time on meaningless actions
07:06 marnom malinoff, luckily I manage the salt infra level stuff, not the app itself (I'm not a programmer). But you are absolutely right. Already 2 year past due date
07:06 malinoff marnom: well, I'm not a dev also. I guess we have similar positions, I'm devops engineer who takes care of policies, deployments, building infrastructure and performance testing
07:06 marnom malinoff, same here. The VMs are optimized to the max but we don't have the new app in stores :P
07:07 mehakkahlon joined #salt
07:07 marnom malinoff, hehe that's my role as well :) security + infra + devops etc
07:07 malinoff yep
07:07 marnom really interesting field
07:08 malinoff it's like writing perfect code which does not solve the actual business problem :)
07:08 marnom haha yeah. While it's intelectually satisfying (and you can get very perfectionistic (is that a word in English?)), it misses the goal of adding value for the business, which is sadf
07:09 marnom I mean, we can automatically deploy extra webservers + update our loadbalancers etc if the load for the new app gets too high. To be honest our business will probably never need that
07:09 marnom but yeah, it's pretty awesome to show colleagues
07:09 marnom :/
07:10 malinoff definitely
07:10 malinoff for like 70% of projects taking a single c8.xlarge ec2 instance with 3 year reservation is the best possible option
07:11 marnom theoretically we could deploy everywhere, cloud redundancy etc.. but in practice it will never be required
07:12 kinetic joined #salt
07:12 malinoff marnom: well, now you can make a talk at some conference
07:12 jhauser joined #salt
07:12 malinoff marnom: you can also use docker :)
07:12 malinoff (which is also wasting of time)
07:13 marnom hehe
07:13 marnom malinoff, we use docker for some specific use cases
07:13 eliasp I'd never run it in production
07:13 marnom malinoff, but most of our stuff is still in VM's which we deploy with Vagrant or salt-cloud depending on the cloud platform
07:14 marnom eliasp, we had the issue of a small app which we would like to isolate per customer, so for that usecase a docker silo seemed like a better solution (less overhead compared to one VM per customer). We also use it for our ci-runner
07:14 marnom but I agree that I wouldn't use it for our core production stuff
07:14 malinoff key word is 'small app'
07:14 eliasp marnom: sure, for CI, devel etc it's great…
07:14 marnom malinoff, yep :)
07:14 malinoff i definitely agree that if you have a LAMP app docker would be great
07:15 malinoff but on the other hand, literally anything would be great
07:15 marnom I think the whole hype about containers will blow over
07:15 marnom It's mostly useful on a really large scale with micro services etc
07:16 marnom where you can re-use building blocks across your infra
07:16 eliasp I mostly disagree with Docker's distribution model… I like container virtualization, but not the way Docker does it
07:16 malinoff well, the problem is that docker is more like deb/rpm packaging, while hypervising is more than just packaging
07:17 eliasp malinoff: yeah, and the kind of "packaging" Docker is doing is the worst way to do it
07:17 marnom I don't feel docker gives the same isolation as a true hypervisor (obviously...)
07:17 malinoff eliasp: agree :)
07:17 marnom and as a security minded person, I really like the isolation
07:18 eliasp Docker is in most cases just an excuse to not do proper packaging which would solve many of the problems one later runs into with Docker
07:18 malinoff marnom: sometimes creating a dedicated aws account is the best isolation you can imagine
07:18 malinoff eliasp: exactly!
07:19 malinoff eliasp: also, it is an excuse for making your app foreground-only, avoiding logging by writing directly to stdout/stderr and listening ssl sockets/serving static from your code
07:19 eliasp too lazy to build a proper ebuild/deb/rpm? just push "./configure && make && make install" into a Dockerfile and there you go… and what you end up with is a security/maintenance nightmare
07:19 malinoff huh
07:19 malinoff there is fpm
07:21 malinoff i also see configuration issues, when developers are hardcoding environments and environment-depending settings in a single giant settings file and making app configurable via a single environment variable
07:21 malinoff like APP_ENVIRONMENT
07:21 eliasp sure… but fpm is no magical bullet… packaging can be hard, tedious and not always easy to get it done right… but with just going the Docker way instead nothing will improve…
07:21 malinoff especially, in nodejs world
07:21 eliasp ACK
07:21 marnom docker seems like a developer solution for production, imho.
07:21 eliasp oh, all those 3rd party package managers (npm, rubygems, pip, …) - just another topic I could rant about for the next few hours ;)
07:22 kinetic joined #salt
07:22 malinoff fpm just helps to start, nothing more
07:22 eliasp malinoff: sure, similar to what we're doing e.g. in Gentoo with g-cpan etc.
07:23 eliasp helps to build a mostly working skeleton which needs to perfected manually then
07:23 malinoff no perl please
07:23 eliasp hehe
07:24 malinoff btw, pip is the most stable 3rd party package manager i've ever seen
07:24 malinoff i always have to 'fix' npm by re-running it
07:24 eliasp it sure is, but it's still far away from what a real PM provides/does
07:24 marnom pip recently really sucked with the IncompleteRead issue on Debian; https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744145
07:24 eliasp marnom: ah, I remember… ran into this too ;/
07:24 malinoff marnom: it's debian issue, not pip
07:25 marnom malinoff, I figured that out as well
07:25 malinoff debian makes their own patches to pip which break it
07:25 marnom though as an 'enduser' it sucked :)
07:25 marnom but, it gave me an excuse to finally deploy all our python apps in a virtualenv
07:26 malinoff marnom: my golden path is: `apt-get|yum install python-setuptools; pip install -U pip; pip install virtualenv`
07:26 malinoff and then forget about having system-wide site-packages
07:26 vvoody joined #salt
07:26 marnom Yeah I ended up using a pretty similar deployment method for pip hehe
07:27 malinoff no apt-get install python-pip or similar
07:27 kinetic joined #salt
07:27 marnom malinoff, you try to do everything through PIP? (no python-* apt-get packages?)
07:27 eliasp I'm heading towards a full Gentoo-based infrastructure, where shipping Python components as native packages instead of pip-deployments is rather easy…
07:28 malinoff marnom: yes
07:28 malinoff marnom: apt packages are usually outdated, and may be broken thanks to debian team
07:30 marnom Hmm I see I install python-pip instead of python-setuptools but I do a cmd.wait pip install --upgrade pip right after that as well
07:31 marnom (it was a cmd.wait instead of a pip.installed because salt wouldn't always pick up pip and complain about pip.installed KeyError's or something)
07:31 malinoff marnom: yeah... that's why i'm developing my own deployment system
07:32 marnom that sounds interesting :)
07:32 malinoff marnom: which uses plain shell scripts instead of yaml-ish DSL
07:32 honestly so uh. how am I supposed to set up my pillar so that each minion I am configuring $service on can only see its its own password for $service?
07:33 kinetic joined #salt
07:33 Norrland honestly: matching on minion_id would be the safest I guess.
07:33 malinoff marnom: but my system is heavily inspired by ansible, not salt :)
07:33 honestly Norrland: ok
07:33 honestly Norrland: you mean having {% if id == 'minion1' %} in the pillar file?
07:34 voileux joined #salt
07:34 illern joined #salt
07:35 marnom yeah I looked into ansible as well
07:35 marnom but I prefer the master/minion setup over an ssh based system
07:35 Norrland honestly: no, more like in the pillar/top.sls you have base:<CR>  'minion1':<CR>- mysecretpillar
07:35 malinoff marnom: why? :)
07:35 honestly Norrland: hrm... ok
07:35 marnom well, for troubleshooting and ad-hoc analysis I think salt 'web*.domain' cmd.run 'some command' is very powerfull
07:35 marnom also the pkg.upgrade stuff etc
07:35 Norrland honestly: but maybe there's some better solution for this.
07:36 marnom I just don't feel like SSH is the way to go for such communication
07:36 malinoff marnom: ansible -i hosts 'web*.comain' -m shell -a "some command" :)
07:36 marnom yeah so what's the latency like if you run that on, say, 5 remote webservers?
07:36 honestly Norrland: can do that with grains too
07:36 honestly I hope
07:37 marnom honestly, grains are not secured
07:37 malinoff marnom: ansible will spawn 5 processes and will do communication in parallel
07:37 Norrland honestly: my suggestion works well where you have say, a service which you want your minions to have the same credentials when connecting.
07:37 marnom malinoff, but I'd suspect the initial connection over SSH would take longer than the full Salt command execution
07:37 Norrland honestly: otherwise you need to have pillars for each minion.
07:38 Norrland honestly: pillars/minion1-service.sls and so on.
07:38 malinoff marnom: well, yes. But I never had any issues with that. We used salt heavily for more than a year, and then switched to ansible
07:38 marnom what was your main motivation to change to ansible?
07:38 malinoff marnom: ansible is slower than salt, yes, but not _that_ slower
07:38 malinoff marnom: well, server/client architecture
07:39 malinoff and fact that salt is breaking backwards compatibility for every release
07:39 chiui joined #salt
07:39 malinoff we came across the situation when we basically couldn't upgrade minions because they won't be able to talk to the master
07:39 marnom malinoff, well that last part I can relate to lol :( each major upgrade I spend at least a day making everything work the way it used to :(
07:39 malinoff and we couldn't upgrade the master because it woldn't be able to talk with minions
07:40 felskrone joined #salt
07:40 marnom was that around the 0.17 release?
07:40 malinoff yes
07:40 marnom yeah I remember. That definitely sucks. I hope it stabilizes a bit over the next months :x
07:40 eseyman joined #salt
07:40 ^C ...
07:41 ^C so.
07:41 ^C repo.saltstack just changed its repo dir structure?
07:41 marnom ^C I opened a bug this morning
07:42 malinoff marnom: also, in ~0.17 salt has basically broken crypto with e=1 on RSA keys
07:42 ^C marnom: tah... got the link?
07:42 marnom oh wow
07:42 malinoff i think that was a bad design decision, to implement their own crypto instead of using x.509 certificates
07:43 malinoff which will live forever now
07:44 ^C marnom: they've added the salt version to the repo path
07:44 oherrala malinoff: well, X.509 is also PITA :)
07:44 marnom_ joined #salt
07:44 malinoff oherrala: do you really think that having a single AES key shared with ALL minions is a great idea?
07:45 marnom ^C: https://github.com/saltstack/salt/issues/28007
07:45 saltstackbot [#28007]title: The new Debian Salt repository seems to be having issues | This used to work (been using it all week) but suddenly this morning on a 'pkg.upgrade refresh=True' of our development environment:...
07:45 oherrala malinoff: I have been playing with the idea of using SSH (there's already keys, trust, etc.)
07:45 malinoff oherrala: and?
07:46 malinoff oherrala: ansible works on ssh, and it works pretty well
07:46 oherrala malinoff: instead of anything homebrewed or TLS :)
07:46 kinetic joined #salt
07:46 malinoff oherrala: well, ssh differs from MQ
07:46 malinoff you simply cannot put SSH into 0mq or AMQP
07:46 oherrala I know
07:47 Grokzen joined #salt
07:47 CeBe joined #salt
07:51 kinetic joined #salt
07:51 marnom ^C: a possible solution has been posted on the issue with apt-get updates
07:58 impi joined #salt
08:06 kinetic joined #salt
08:06 lb joined #salt
08:14 ashirogl joined #salt
08:20 kinetic joined #salt
08:24 chrismckinnel joined #salt
08:27 s_kunk joined #salt
08:27 elsmo joined #salt
08:28 thalleralexander joined #salt
08:30 kinetic joined #salt
08:34 impi joined #salt
08:37 ziro` joined #salt
08:38 thefish joined #salt
08:38 thefish left #salt
08:39 larsfronius joined #salt
08:39 kinetic joined #salt
08:42 rim-k joined #salt
08:44 linjan joined #salt
08:48 jmreicha joined #salt
08:49 thefish joined #salt
08:49 kinetic joined #salt
08:49 Singularo joined #salt
08:51 keimlink joined #salt
08:59 kiorky joined #salt
09:01 kiorky joined #salt
09:03 kiorky joined #salt
09:04 kinetic joined #salt
09:05 kiorky joined #salt
09:07 kiorky joined #salt
09:08 kiorky joined #salt
09:10 kiorky joined #salt
09:11 slav0nic joined #salt
09:12 EvaSDK hello guys
09:13 EvaSDK I am trying to write a compound match to select physical servers skipping LXC nodes
09:13 EvaSDK but I can't seem to find the correct way to select the absence of virtual_subtype grain
09:13 EvaSDK I use something like this 'G@virtual:physical and not P@virtual_subtype:.*'
09:13 EvaSDK but it doesn't work
09:14 EvaSDK is it possible at all ?
09:18 epcim joined #salt
09:18 kinetic joined #salt
09:28 kinetic joined #salt
09:30 dkrae joined #salt
09:36 impi joined #salt
09:43 kinetic joined #salt
09:47 kukacz joined #salt
09:49 elsmo joined #salt
09:49 kinetic joined #salt
09:50 loque joined #salt
09:50 Queops joined #salt
09:50 loque hi can any one help
09:51 larsfron_ joined #salt
09:51 loque I am having an issue with a state that uses publish.publish
09:51 loque this state worked fine in salt release 2014
09:51 loque but with the latest release it breaks
09:51 loque by not returning any data
09:52 Queops left #salt
09:52 loque but the same command when using salt-call works and returns a dict
09:52 bluenemo joined #salt
09:53 loque the version-report that the state works with is
09:53 loque Salt: 2014.1.4          Python: 2.6.6 (r266:84292, Jul 23 2015, 15:22:56)          Jinja2: 2.2.1        M2Crypto: 0.20.2  msgpack-python: 0.1.9.final    msgpack-pure: Not Installed        pycrypto: 2.0.1          PyYAML: 3.10           PyZMQ: 2.2.0.1             ZMQ: 3.2.1
09:54 loque I am calling it in a state like so salt['publish.publish']('G@environment:client_env:UPGRADE and G@environment:type:tst and G@services:TCT_HOSTS', network.get_hostname,  expr_form='compound')
09:54 loque when calling it from the command line it works
09:55 loque sudo salt-call publish.publish 'G@environment:client_env:UPGRADE and G@environment:type:tst and G@services:TCT_HOSTS' network.get_hostname  expr_form='compound'
09:55 loque returns the data that I need
09:57 loque anyone
09:57 kinetic joined #salt
10:01 sunkist joined #salt
10:02 stephanbuys left #salt
10:03 anmolb hello, I want to invoke highstate from a python code. I tried doing salt.client.LocalClient().cmd('*', 'state.highstate', {"collectd":{"master_name" : "my_master_ip"}})
10:03 anmolb and it doesn't seem to work
10:04 anmolb however when I try to execute cli command it works
10:04 anmolb any help?
10:05 loque sorry do not know much about callng salt thorugh python
10:06 loque the last part looks like a pillar
10:06 loque should that not be pillar='{"collectd":{"master_name" : "my_master_ip"}}'
10:06 vvoody joined #salt
10:08 aqua^c joined #salt
10:12 kinetic joined #salt
10:13 anmolb loque, tried even that but didn't work :(
10:21 giantlock joined #salt
10:22 MadHatter42 joined #salt
10:22 kinetic joined #salt
10:23 sgargan joined #salt
10:33 epcim joined #salt
10:36 kinetic joined #salt
10:43 freelock joined #salt
10:46 kinetic joined #salt
10:50 genediazjr joined #salt
10:56 kinetic joined #salt
10:57 the_lalelu hmmm ... i've a pillar which has gpg data inside. when i add a new minion i only got this message: Unable to render top file: GPG unavailable
10:57 the_lalelu and the minion cant do a highstate
10:58 the_lalelu the pillar top file clearly say that the gpg message is not for this new minion
10:58 the_lalelu funny
10:59 the_lalelu a simple pillar.items on the new minion works correctly
11:05 breakingmatter joined #salt
11:05 the_lalelu i think the saltstack deb packages should at least recommend the gnupg and python-gnupg deb packages also
11:07 babilen Why?
11:09 the_lalelu to prevent chicken egg problems like this.
11:09 the_lalelu leaving my new minion not being able to do a highstate (in which the gnupg and python-gnupg packages are marked for installation)
11:09 the_lalelu ;)
11:10 babilen The problem is that salt would have to recommend *many* packages if we start to include every package that an execution module might need
11:10 kinetic joined #salt
11:10 babilen If you want to use gpg pillars you have to install the corresponding modules
11:11 babilen The same holds true for a many other modules and it is hard to draw the line
11:11 babilen I wouldn't make that a Recommends either, but a Suggests
11:11 the_lalelu for me it is a unexpected behavior that a minion, which is not a target for a gpg'ed pillar, get affected
11:12 babilen That I can understand. Could you open an issue for that so that the behaviour regarding pillar rendering could be clarified?
11:12 the_lalelu yes i will do that. thx.
11:17 shiriru joined #salt
11:20 kinetic joined #salt
11:24 chiui joined #salt
11:25 kinetic joined #salt
11:31 kinetic joined #salt
11:37 teebes joined #salt
11:40 evle joined #salt
11:40 amcorreia joined #salt
11:44 kinetic joined #salt
11:46 btorch is this wrong ? pkg.remove force_yes=true pkgs='["python-diamond"]'
11:48 genediazjr joined #salt
11:48 babilen btorch: force_yes ?
11:49 babilen (typically bad boo boo)
11:49 btorch yeah it's an option on salt.modules.aptpkg.install
11:49 btorch can't remove a pkg if it's on hold unless one provides the force-yes option to apt
11:50 babilen If I had to find something wrong with that command it would be that
11:50 babilen So, unhold it first?
11:54 eliasp and once again… hours wasted: https://github.com/saltstack/salt/issues/28016
11:54 saltstackbot [#28016]title: `top.sls` state assignments in non-base environments not possible with GitFS | When using GitFS for states, the configuration of `top_file_merging_strategy`/`default_top` doesn't work as expected....
11:54 babilen Besides: Why do you consider that command to be wrong, btorch ?
11:54 kinetic joined #salt
11:54 babilen eliasp: *sigh* Really?
11:54 eliasp babilen: yes ;-/
11:55 babilen Oh man :(
11:55 btorch babilen: I wouldn't consider it to be wrong, but minion log shows that --force-yes is not passed over
11:55 btorch I thought it would have worked
11:55 babilen btorch: Which version are you running on the master and minion respectively?
11:55 genediaz_ joined #salt
11:55 btorch 2015.5.3+ds-1trusty1
11:56 bastion1704 joined #salt
11:57 babilen btorch: Where did you find that option for pkg.remove ?
11:58 babilen I am only seeing it for pkg.install so I wouldn't necessarily expect it to work for pkg.* (as functions are taking different arguments)
11:59 btorch well I've noticed that some options that show up on install work for other commands
11:59 aqua^c joined #salt
11:59 kinetic joined #salt
12:00 btorch like for example on the salt.states.pkg.installed  ref (state now) doesn't even show anything in regards to force_yes but it works when used within a state file
12:02 babilen That is probably because the underlying execution module function supports it
12:02 btorch the https://docs.saltstack.com/en/2015.5/ref/states/all/salt.states.pkg.html#module-salt.states.pkg doesn't even show an unhold
12:02 btorch the module ref does
12:03 babilen https://docs.saltstack.com/en/develop/ref/modules/all/salt.modules.aptpkg.html#salt.modules.aptpkg.unhold
12:04 epcim joined #salt
12:05 bastion1704 Hello, is it possible to loop on the pillar and get the key and the value  ?
12:05 kinetic joined #salt
12:06 bastion1704 I tried this but it does not work : https://paste.ee/p/TKXu3#
12:06 bastion1704 error is : failed: Jinja variable 'list object' has no attribute 'iteritems'
12:13 btorch babilen: I've done someting similar but with 3 levels on the pillar
12:13 btorch bastion1704: ^
12:13 btorch sorry
12:16 teebes joined #salt
12:17 bastion1704 btorch great, do you have an example online by any chance ?
12:17 btorch bastion1704: I'm sure there is a better/neater way .. but I have something like https://paste.ee/p/wBDWJ
12:17 tjuup joined #salt
12:17 bastion1704 btorch tx
12:18 kinetic joined #salt
12:18 btorch I actually use the section within my file for other stuff though
12:21 zwi joined #salt
12:21 btorch babilen: I don't get it, how can I unhold a package to be removed within a state when that is not supported it seems
12:21 btorch I actually have to do it using the cli calling the module ?
12:22 btorch before running the state or highstating the box ?
12:23 kinetic joined #salt
12:24 babilen btorch: Why is it on hold to begin with?
12:25 babilen (I mean there isn't a state for that either)
12:26 btorch babilen: because there are certain pkgs that we place on hold on our systems to avoid upgrading issues
12:26 btorch babilen: yes you can set hold: true within the pkg.installed
12:27 babilen And you do that?
12:27 btorch I swear though that I had used force_yes on remove before
12:27 babilen So you want both a hold and an unhold to be true at the same time?
12:27 btorch babilen: yes all the pkgs that we need to we put them on hold
12:28 btorch babilen: no, need to be able to remove a pkg if it's on hold and that can only be done with force_yes
12:28 btorch force_yes is available on pkg.installed but not pkg.removed
12:28 btorch so it seems
12:29 babilen You have to differentiate between states and interactive usage. If you don't want a package to be installed then don't install it in your state .. The obvious thing to do in your situation seems to be to interactively unholding that package
12:32 babilen Besides .. I can remove held packages just fine with both aptitude and apt-get (haven't tried salt). What happens if you try?
12:32 DammitJim joined #salt
12:32 babilen I mean, I'm sorry, that this functionality is not there, but there is little that I can do about that apart from implementing it myself
12:33 babilen And you should be able to remove held packages
12:33 btorch oh no worries man, I just thought it was a bit weird and I swear I had used it before :)
12:33 kinetic joined #salt
12:34 babilen held simply means "do not automatically upgrade" and not "do not, under any circumstances, change the status of this package"
12:34 btorch yeah the cli would be an option, is just that not everyone specially someone new on a team, would not really know he/she would have to do so before running a highstate that would break
12:34 btorch yeah on the system itselft I can remove it as long as I do apt-get remove --force-yes <pkg>
12:34 babilen Which brings me to: What does happen if you run pkg.remove (or the state) on a package that is on hold?
12:35 babilen You shouldn't need --force-yes ...
12:35 btorch E: There are problems and -y was used without --force-yes
12:35 btorch ^ that's in the log file on the minion
12:36 btorch what I did for now, was to change the state so that it uses cmd.run and gives the proper apt-get command options
12:36 babilen Well, take a look into the debug log
12:37 btorch on the minion ?
12:37 babilen and --force-yes ?
12:37 babilen yeah, on the minion
12:37 yetAnotherZero joined #salt
12:38 kinetic joined #salt
12:39 DammitJim how can I use t his info in a jinja template?
12:39 DammitJim https://gist.github.com/anonymous/85ef552ffd9dee4aadbe
12:40 btorch brb
12:40 DammitJim the servers list could be 3 or 7 servers
12:40 DammitJim I know how to get the listener_ip and listener_port
12:43 Deevolution joined #salt
12:50 slav0nic joined #salt
12:50 ItsMe__ joined #salt
12:56 slav0nic_ joined #salt
12:57 kawa2014 joined #salt
12:58 ferbla joined #salt
13:00 JDiPierro joined #salt
13:07 subsignal joined #salt
13:08 kinetic joined #salt
13:21 furrowedbrow joined #salt
13:23 numkem joined #salt
13:24 epcim joined #salt
13:26 kinetic joined #salt
13:27 zmalone joined #salt
13:30 racooper joined #salt
13:31 perfectsine joined #salt
13:32 edulix joined #salt
13:34 cpattonj joined #salt
13:36 fbretel joined #salt
13:38 fbretel hi all, I can't get onchanges work over directory changes.
13:38 fbretel I'm trying to "watch" /usr/local/lib for ldconfig
13:39 fbretel but changes in /usr/local/lib do not trigger my cmd ldconfig
13:39 fbretel I do use globbing though, but only file.directory declarations.
13:40 fbretel Hence my question: where does salt store file/directory changes ? Are there some hashes stored somewhere ?
13:41 ekristen joined #salt
13:46 kant joined #salt
13:46 BradThurber joined #salt
13:48 kinetic joined #salt
13:49 linjan joined #salt
13:49 JDiPierro joined #salt
13:49 mapu joined #salt
13:51 _JZ_ joined #salt
13:52 favadi joined #salt
13:55 babilen fbretel: You need a state that actually has changes if you want to react to it
13:55 fbretel babilen: I have /usr/local/: file.directory
13:56 kinetic joined #salt
13:56 babilen And that has changes?
13:56 babilen (the state that is)
13:57 babilen If you want to watch files therein you'd need a state to manage those files
13:57 babilen (so you can watch that state)
13:58 babilen You might actually be looking for beacons to which you can react if you don't want to actually manage that directory with salt, but just do things if *something unrelated to salt* changes something in it
13:58 fbretel babilen: can beacons trigger cmd state ?
13:58 fbretel babilen: probably have to read further about beacons
13:59 babilen Do that ..
13:59 fbretel babilen: in fact it's not unrelated to salt, it's just that the content is not fully managed by salt...
13:59 babilen I think that they are what you are looking for, but I'm not sure as I (still) haven't really played with them much
14:00 babilen fbretel: Well, you can react to anything that is managed by salt (as that would have a state behind it that you can reference), but things outside of salt's control won't trigger state runs
14:00 FreeSpencer https://repo.saltstack.com/apt/ubuntu/ubuntu14/SALTSTACK-GPG-KEY.pub
14:00 FreeSpencer Where is the key :(
14:01 fbretel babilen: thx!
14:01 babilen In fact the inotify beacon is, more or less, exactly what you are looking for I think
14:01 babilen I mean that + reactor
14:01 MadHatter42 joined #salt
14:01 babilen Read https://docs.saltstack.com/en/develop/topics/beacons/ and be in salt heaven
14:05 kinetic joined #salt
14:06 zmalone joined #salt
14:06 fbretel babilen: looks like it. Except my /usr/local is on NFS... I hope I can get it to work.
14:07 andrew_v joined #salt
14:07 viq joined #salt
14:09 babilen Well, why not watch it on the server then? (but then it shouldn't make a difference, should it?)
14:09 GreatSnoopy joined #salt
14:10 favadi joined #salt
14:10 zwi joined #salt
14:11 fbretel babilen: it's a NetApp NAS
14:13 quist joined #salt
14:14 murrdoc joined #salt
14:15 babilen Yes, why should anything be easy?
14:15 kinetic joined #salt
14:16 murrdoc everything is easy
14:16 ipmb joined #salt
14:17 pratikmallya joined #salt
14:20 pratikma_ joined #salt
14:21 kinetic joined #salt
14:25 slav0nic joined #salt
14:26 Akhter joined #salt
14:29 Akhter joined #salt
14:30 kinetic joined #salt
14:31 amcorreia joined #salt
14:32 ageorgop joined #salt
14:39 kinetic joined #salt
14:39 aqua^c joined #salt
14:44 Trivium joined #salt
14:46 epcim joined #salt
14:47 Brew joined #salt
14:48 kinetic joined #salt
14:55 kinetic joined #salt
14:55 bosyak joined #salt
14:59 programmerq joined #salt
15:05 traph joined #salt
15:05 tzero joined #salt
15:05 giantlock joined #salt
15:07 linjan_ joined #salt
15:08 quist left #salt
15:08 aphor joined #salt
15:08 __aphor__ joined #salt
15:08 kinetic joined #salt
15:13 gibsonje joined #salt
15:13 gibsonje Hi. I'm running salt masterless but I'm seeing this in my minion log frequently:
15:13 gibsonje "Attempt to authenticate with the salt master failed"
15:17 debian112 joined #salt
15:17 ferbla gibsonje: the docs say you can just run salt-call without the salt-minion daemon. Since the daemon will try to AUTH against the master
15:17 ferbla https://docs.saltstack.com/en/latest/topics/tutorials/standalone_minion.html
15:17 irctc431 joined #salt
15:18 kinetic joined #salt
15:18 irctc431 hey guys, i have an issue with getting repository key for Debian, anyone knows that?
15:18 RedundancyD joined #salt
15:19 irctc431 this url is simply not available
15:19 irctc431 https://repo.saltstack.com/apt/debian/SALTSTACK-GPG-KEY.pub
15:19 irctc431 anyone?
15:19 ferbla irctc431: What version would you like?
15:20 zmalone Looks like it's been moved to 2015.5 and 2015.8
15:20 ferbla Could use the latest dir too, it has a key there
15:20 zmalone That happened last night, by the looks of it
15:21 zmalone I bet that'll break all my existing hosts.
15:23 kinetic joined #salt
15:24 zmalone yep
15:25 gibsonje Ferbla: Hah, yeah that makes sense.
15:25 teebes joined #salt
15:26 Aleks3Y joined #salt
15:27 zmalone basepi: Any chance future repo changes can be announced on the mailing list, release notes, or something like that?
15:27 zmalone it looks like you handled that 2015.5.6 release.
15:28 zmalone It's an easy fix for open source users, but it would be nice to have it announced, instead of debugging it.
15:28 Akhter joined #salt
15:29 gibsonje Trying to get this masterless minion playing nice with gitfs has been a bit of a headache.
15:29 ageorgop joined #salt
15:30 racooper http://venturebeat.com/2015/10/15/source-red-hat-is-buying-ansible-for-more-than-100m/
15:30 irctc431 ferbla: last stable
15:30 basepi zmalone: yes. I'm really pissed they changed the layout without documenting and a deprecation path. That's stupid.
15:31 basepi I will make sure we post-mortem this one.
15:31 zmalone Thanks!  I'm not trying to be blamey or anything, I'm getting salt for free right now.
15:31 basepi I'm getting blamey...... >.<
15:31 basepi But I appreciate the patience.
15:32 irctc431 guys, anone have that key which is not accessible any more here https://repo.saltstack.com/apt/debian/SALTSTACK-GPG-KEY.pub
15:32 nardev guys, anone have that key which is not accessible any more here https://repo.saltstack.com/apt/debian/SALTSTACK-GPG-KEY.pub
15:32 nardev ?
15:33 DanyC joined #salt
15:34 nardev ?
15:34 pratikmallya joined #salt
15:35 zmalone nardev: See above
15:35 zmalone unannounced repo path changes
15:35 zmalone it's now in apt/debian/<saltversion>/
15:35 nardev aha
15:35 nardev ok
15:35 nardev thnx
15:35 nardev why don't somebody update the docs...
15:36 zmalone the https://repo.saltstack.com docs are updated, but it wasn't announced
15:36 kinetic_ joined #salt
15:36 zmalone they now point to /apt/debian/latest/SALTSTACK-GPG-KEY.pub
15:37 nardev zmalone: hmm https://repo.saltstack.com/apt/debian/develop/SALTSTACK-GPG-KEY.pub
15:37 zmalone I'd suspect the bootstrap script is still pointing in the wrong direction, but I have not tried it
15:37 nardev what about this
15:37 nardev ?
15:37 zmalone If you want to be on the dev branch, sure.
15:37 nardev yes bootstrap script fails like egg on concrete
15:37 zmalone I'd probably go with 2015.5, 2015.8, or LATEST (which probably points to 2015.8)
15:37 nardev zmalone: doesn't work :(
15:37 nardev https://repo.saltstack.com/apt/debian/develop/SALTSTACK-GPG-KEY.pub
15:38 DanyC i hope - cause i love this project - now with RH acquiring Ansible, another big "cash machine" company will support SaltStack to be able to compete with the new aliance
15:38 ferbla irctc431: You could us https://repo.saltstack.com/apt/debian/2015.8/SALTSTACK-GPG-KEY.pub
15:38 nardev i tried this :( https://repo.saltstack.com/apt/debian/2015.8.0/SALTSTACK-GPG-KEY.pub
15:39 zmalone 2015.8
15:39 ferbla nardev: What happens if you drop the '.0' and do just '2015.8'
15:39 zmalone not 2015.8.0
15:39 nardev :D
15:39 nardev i see
15:39 nardev :d
15:39 nardev :D
15:41 zmalone 2015.8.0 is now deprecated in favor of 2015.8.1
15:41 zmalone Now with fewer passwords in your log files!
15:41 zmalone 2015.5.6 is also out
15:43 nardev this doesn;t exist eather  https://repo.saltstack.com/apt/debian/2015.8.1/SALTSTACK-GPG-KEY.pub
15:43 nardev zmalone:
15:43 zmalone No, just browse the heirarchy
15:43 zmalone https://repo.saltstack.com/apt/debian/2015.8/SALTSTACK-GPG-KEY.pub
15:44 zmalone if you visit https://repo.saltstack.com/apt/debian/2015.8/ or https://repo.saltstack.com/apt/debian/2015.8/ it'll make sense
15:44 zmalone sorry, the second one is https://repo.saltstack.com/apt/debian/2015.8/
15:44 nardev ok, apt-get update fails again W: Failed to fetch http://repo.saltstack.com/apt/debian/dists/jessie/contrib/binary-amd64/Packages  404  Not Found  W: Failed to fetch http://repo.saltstack.com/apt/debian/dists/jessie/contrib/binary-i386/Packages  404  Not Found
15:46 RandyT could someone please help me figure out what I am missing here.
15:46 armyriad joined #salt
15:47 DanyC zmalone: so maybe then the irc banner at the top could be changed to "2015.8.1 is the latest" ?
15:47 RandyT In deploy of EC2 images using salt-cloud and then subsequent destroy using salt-cloud -d instancename, the EIP is not getting released and with subsequent runs to deploy instances with public interfaces, I error out with 'The maximum number of addresses has been reached.'
15:47 RandyT Here is more detail: https://gist.github.com/rterbush/bc1855e4ad3c704b2d42
15:48 RandyT I suspect some missing profile parameter, but haven't found it...
15:48 armyriad joined #salt
15:50 papertigers I have a state setting a grain on a minion.  Whats the proper way to do a conditional check for it in the sls?  {% if salt['grains.get']('some-vkey') == "True" %}
15:50 RandyT and rather than releasing, just reusing one of the available 5
15:50 papertigers which I should mention, doesn't seem to work right now
15:50 kitplummer joined #salt
15:54 gibsonje I just cannot get ext_pillar pulling from git masterless.
15:54 gibsonje Keep getting "remote ref does not exist" no matter what I try (2015.8.0)
15:54 gibsonje Successfully pulling my states repos via gitfs
15:54 gibsonje But won't pull pillars
15:56 catpig joined #salt
15:57 thefish joined #salt
15:58 scoates joined #salt
15:59 timoguin_ joined #salt
15:59 edulix joined #salt
16:01 mpanetta joined #salt
16:03 zmalone https://gist.github.com/zmalone/73553ca5f8286951a90d for anyone else on Ubuntu
16:03 mpanetta joined #salt
16:04 meye1677 joined #salt
16:06 jalbretsen joined #salt
16:07 TyrfingMjolnir joined #salt
16:08 gibsonje Is it possible ext_pillar is still broken on 2015.x for masterless? https://github.com/saltstack/salt/issues/26035
16:08 saltstackbot [#26035]title: ext_pillar no longer works in masterless minion setup | Desc: ...
16:09 igorwidl joined #salt
16:09 RandyT Judging by lack of response to my question, I've decided to file an issue: https://github.com/saltstack/salt/issues/28028
16:09 saltstackbot [#28028]title: Instance destroy using salt-cloud -d does not release EIP | After deploying an EC2 instance and then subsequently destroying it, eventually, I have allocated my current limit of 5 EIP addresses. Rather than reusing one of the available 5 addresses, the deploy of an instance requiring an EIP will eventually fail with the following error message:...
16:10 favadi joined #salt
16:12 igorwidl am i the only one who sees “retcode: 0” when running salt? for example salt ‘*’ test.ping will output retcode:0 and result of test.ping
16:14 openfly cool
16:15 openfly try:  salt --state-output=mixed
16:15 openfly i like that output
16:15 openfly much nicer
16:17 perfectsine joined #salt
16:17 peters-tx salt.states.ssh_auth.present doesn't seem to be working  8/
16:18 pratikma_ joined #salt
16:20 jdesilet joined #salt
16:20 igorwidl openfly: i tried —state-output=mixed but I still get the retcode:0 along with ping result
16:21 igorwidl do you get the retcode:0 line as well?
16:23 OliverUK joined #salt
16:24 openfly i just get 'True'
16:26 OliverUK joined #salt
16:27 igorwidl thanks, which os are you running? I am thinking the retcode:0 has something to with python 2.6
16:27 thalleralexander joined #salt
16:30 amcorreia joined #salt
16:32 armyriad joined #salt
16:33 igorwidl openfly: can you try test.ping but with —batch=2 . do you still get true?
16:34 writtenoff joined #salt
16:35 Akhter joined #salt
16:37 SheetiS joined #salt
16:40 jmreicha joined #salt
16:40 linjan joined #salt
16:41 zmalone joined #salt
16:42 Gareth murrdoc: ping
16:49 chitown im looking for a way to share data between grains, pillar and exec modules
16:52 ALLmightySPIFF joined #salt
16:53 pratikmallya joined #salt
16:53 moogyver chitown: do you have a more solid example of what you're trying to do?
16:57 tpaul joined #salt
17:02 chitown moogyver: lets say i have a dict of data, ideally, id love to be able to access that same data from a grains module, state sls file, pillar sls file, execution module and external pillar
17:03 chitown what would be great if there was something like "__shared__" that appeared everywhere and is loaded "first"
17:04 chitown barring that, how do i run "{% import_yaml 'foo/bar.yaml' as foo %}' within an execution module and a grains module?
17:04 chitown not sure if that helps... :)
17:05 moogyver hrm, well that last statement confuses me more than anything.  an execution module is just python, so you're not going to be writing jinja in that :)
17:05 moogyver but you can access grains and pillars within an execution module
17:05 chitown well.... you must be able to
17:05 chitown i mean, state.sls is just python as well :)
17:06 moogyver state.sls is yaml that gets converted into something that python can use.
17:06 moogyver an execution module doesn't get put thru the templating engine
17:07 chitown no, i mean, eventually, python is executed
17:07 chitown hacking the loader would be an option and calling the renderer directly
17:07 kitplummer joined #salt
17:08 chitown sorry, 2 diff things: hacking the loader.... or, calling salt.renderer.jinja...
17:10 breakingmatter joined #salt
17:11 KyleG joined #salt
17:11 KyleG joined #salt
17:13 moogyver chitown: you can load pillar data from a grain module or a execution module
17:13 moogyver so you can set it within the pillar and just use it in those
17:14 nate_c joined #salt
17:15 chitown ya... thats what im doing now. i was hoping for something little more elegant :)
17:15 moogyver i'm not sure really what your use case is here.  what are you trying to do?
17:16 ashirogl joined #salt
17:16 aparsons joined #salt
17:17 chitown right now, i have a bunch of data files in .../shared/data/
17:17 chitown that path is part of both file_roots and pillar roots
17:18 chitown so, both pillars and state files can import the data with import_yaml
17:18 chitown AT FIRST, i wanted to just make this data available to some custom exec modules
17:19 chitown minions will create grain that has their "environment" (yes, different than saltenv.. sorry... name overloading sucks)
17:20 chitown an example; i want to validate that the env name set is known
17:20 ashirogl1 joined #salt
17:20 chitown but, i need to do that in pillars, state files and exec modules
17:21 moogyver and just setting that data in a pillar and using that pillar in state files, exec mods and grain mods doesn't work for you?
17:21 chitown riiiight... not "today"
17:21 aqua^c joined #salt
17:22 chitown (i'd like to move allof this data to pillars... but there is a bit of a mess with cross calling right now...)
17:22 aparsons joined #salt
17:22 chitown so, long term: pillars
17:22 chitown today... grains module... it just feels like overkill :)
17:22 chitown i have the data in a yaml file... the only thing missing is being able to load that data into an exec module
17:23 moogyver well, you don't have to use a grains module if you're just setting a single k/v grain that's predefined, but besides that..
17:23 chitown but, that is trying to force the current (broken) design somewhere it may not belong... TOTALLY accept that :)
17:23 moogyver yeah, unless that file also exists on the host you're executing the EM from, you can't
17:23 ViciousLove joined #salt
17:24 moogyver because an EM only executes on the minion
17:24 chitown yes, i know
17:24 chitown that file is in both file roots and pillar roots
17:24 chitown so, itis avail on all minions
17:24 moogyver ok, so just write a python function to load the yaml file?
17:24 hal58th Ha, just found a bug with scheduler in 2015.8.1. It seems to be adding an extra arg everytime I restart salt-minion.
17:25 chitown moogyver: the problem is the path... i could os.path.join(CACHE_DIR, 'foo/bar/baz.yaml')
17:25 JDiPierro joined #salt
17:26 chitown but since salt core does this a lot, i figured there should be a higher level call to make that easy
17:26 chitown this really isnt a big deal. :)  was just thinking i was missing something simple :)
17:26 moogyver no.. you're not - i mean you realize this should all be pillar anyways, but besides that..
17:28 chitown ya... inherited a lot of stuff... dont want to change it all at once. :) :)
17:28 moogyver the only way to get it into the EM is to load it via python, so the file has to be somewhere on the host, and if not, then you could just grab the file first via cp.get_file
17:29 moogyver that or you have to pass it as an argument to the EM, which I'm guessing you don't want to do
17:29 chitown cp.get_file.... ya..... that actually may work :)
17:30 chitown its all a band aid until i can migrate to pillars
17:30 chitown hacks in the code as ok... cleaning the data is my primary concern
17:30 chitown thanks for that chat :)
17:30 moogyver sure, good luck
17:32 mapu joined #salt
17:33 papertigers can returner settings be stored in a pillar?
17:35 epcim joined #salt
17:36 kinetic joined #salt
17:36 mehakkahlon joined #salt
17:38 rim-k joined #salt
17:39 larsfronius joined #salt
17:49 mrwboilers Is there some sort of channel to make feature requests?
17:49 kinetic joined #salt
17:49 hal58th @basepi, Question for you sir. repo.saltstack.com for ubuntu, wasn't it supposed to hold multiple versions for a major version. i.e. 2015.8.0 and 2015.8.1
17:56 moeyebus joined #salt
17:57 baweaver joined #salt
17:58 breakingmatter joined #salt
17:58 knite joined #salt
18:01 rojem joined #salt
18:02 basepi hal58th: Yes, it will, there was some misunderstanding
18:02 hal58th Ah good. Then I won't create that issue then.
18:02 basepi We plan to host at least a few recent releases, if not all releases going forward.
18:02 basepi Yep, it's coming. =)
18:03 hal58th Excellent. Found a bug with schedule and I can't roll back or test old version!
18:04 hal58th Yeah, it also has 2015.5.6 in the 2015.8 folder. So I figured there was a screw up
18:05 grumm_servire joined #salt
18:06 robawt joined #salt
18:08 szhem joined #salt
18:09 kinetic joined #salt
18:10 baweaver joined #salt
18:10 tkharju joined #salt
18:12 pratikma_ joined #salt
18:13 Fiber^ joined #salt
18:13 anmolb joined #salt
18:15 Akhter joined #salt
18:17 s_kunk joined #salt
18:24 moloney joined #salt
18:24 chiui joined #salt
18:25 moloney If I need a file temporarily to run some state, what is the best way to handle it?  Use "file.managed" before the state and "file.absent" after?  Is there a better way?
18:26 Bryson joined #salt
18:30 hal58th If you are that worried about leaving it on the box, then yeah that's probably it moloney
18:30 hal58th you can use "order: last" for the removal moloney
18:32 Gareth moloney: what is in the file that you need for the state to run?
18:32 hal58th QUESTION, did the schedule configuration for minion.conf just totally abandoned? Can't find any documentation for it anymore and I am having issues with it.
18:32 Gareth https://docs.saltstack.com/en/latest/topics/jobs/schedule.html
18:32 moloney Gareth: some private keys that need to be imported into a program
18:38 hal58th Just found that Gareth as you said that... Well then I will write up this bug I found.
18:41 OliverUK joined #salt
18:42 geomyidae_ joined #salt
18:42 ALLmight_ joined #salt
18:42 Akhter joined #salt
18:42 OliverUK joined #salt
18:57 murrdoc Gareth: !
18:57 murrdoc o/
18:57 jerematic joined #salt
18:57 murrdoc also everyone else o/
18:57 murrdoc 2015.5.6
18:57 murrdoc where the deb at
19:01 breakingmatter joined #salt
19:02 Gareth murrdoc: o/
19:02 Gareth murrdoc: remember when we were chatting a bit back about salt and uwsgi?
19:04 linjan joined #salt
19:05 GreatSnoopy joined #salt
19:07 Azulez left #salt
19:07 iggy murrdoc: http://repo.saltstack.com/apt/ubuntu/ubuntu14/2015.5/salt-minion_2015.5.6+ds-1_all.deb
19:09 RandyT could someone tell me what ports a highstate process needs in order to communicate between minion and master?
19:09 RandyT running into some problems running a highstate on a minion that is sitting in a private subnet, different from the master..
19:11 JDiPierro RandyT: Default port to talk to the master is 4506
19:12 iggy 4505/4506
19:12 iggy open on the master (not the minion)
19:13 RandyT I have 4505-4506 open between these two clients on their respective networks...
19:13 iggy pretty sure there's a page in the docs that talks more in depth about this
19:13 RandyT so that was my understanding, no need to open these on minion...
19:13 JDiPierro Probably this: https://docs.saltstack.com/en/latest/topics/tutorials/firewall.html
19:13 RandyT yeah, have poured through the docs... that is not getting me to enlightenment
19:14 RandyT I am able to run highstate (in AWS enviro) between master and another subnet which are both public.
19:14 RandyT the one that is failing is the private subnet
19:14 RandyT private subnet is routing through NAT on public subnet.
19:14 iggy from the minion, can you telnet to master:4505 and master:4506 ?
19:14 RandyT no issue running highstate on the NAT
19:15 giantlock joined #salt
19:16 RandyT I get a garbage char returned when attempting to connect with nc
19:16 RandyT not sure if I should see a cleartext header or what
19:20 kitplumm_ joined #salt
19:22 kinetic joined #salt
19:22 mehakkahlon joined #salt
19:24 kitplummer joined #salt
19:26 goldbuick__ joined #salt
19:27 baweaver joined #salt
19:28 RandyT appears this is still about the NAT not working fully...
19:28 RandyT repoquery is failing --whatprovides query
19:31 baweaver joined #salt
19:33 kitplummer joined #salt
19:40 kitplummer joined #salt
19:42 pratikmallya joined #salt
19:47 baweaver joined #salt
19:47 kitplummer joined #salt
19:47 knite I have a salt state that's failing due to an error in an internal salt check. it's looking for /var/run/utmp or /run/utmp, but both are missing.
19:47 knite I'm running in a chroot, which could be relevant?
19:48 knite specifically, I'm using salt to configure in the chroot. I do have root access outside the chroot.
19:48 cberndt joined #salt
19:50 Akhter joined #salt
19:52 kitplumm_ joined #salt
19:52 Kruge joined #salt
19:53 Kruge Any saltstack ubuntu repo maintainers here?
19:54 anmolb joined #salt
19:55 Kruge Or do you know already that the repo file tree is b0rked and even the URL listed on the "How to install saltstack" page is returning a 404?
19:56 htssouza joined #salt
19:56 knite Kruge: I just had that problem yesterday.
19:57 knite you need echo 'deb http://repo.saltstack.com/apt/ubuntu/ubuntu14/2015.8 trusty main' > /etc/apt/sources.list.d/saltstack.list
19:57 knite note the 2015.8 at the end.
19:57 knite haven't had a chance to open a GH issue yet.
19:58 knite so it looks like I can just touch /var/run/utmp in my chroot and salt is able to do its thing? is this a bug or a feature?
19:59 Kruge knite: And god knows how many servers already deployed won't be getting updates because the URL in the .list is now broken...
20:00 knite Kruge: I just assumed the docs were wrong and tacking on the version was always necessary?
20:00 whytewolf the install instructions i just looked at said the structure did change so that you need either the version, or latest on the end http://repo.saltstack.com/#ubuntu or https://docs.saltstack.com/en/latest/topics/installation/ubuntu.html
20:00 Kruge No, I followed the instructions earlier this week, and it worked fine.  I just tried to update packages on my servers and noticed that I was getting 404s from repo.saltstack
20:01 whytewolf "The repository folder structure changed between 2015.8.0 and 2015.8.1. If you previously configured this repository, verify that your paths contain latest.
20:01 whytewolf "
20:01 Kruge That's great.  But what about all those nice folks who already *have* salt installed and are silently not going to be getting updates unless they notice the 404s?
20:04 aqua^c joined #salt
20:04 Kruge What happens when someone drops an auth bypass 0day in salt-minion and the recommended fix is to update to the latest version? All those people will be sitting there thinking they're on the latest version when really someone changed the repo tree structure between minor releases and didn't tell anyone.
20:07 OliverUK joined #salt
20:09 whytewolf Kruge: slow down. A. the change is DOCUMENTED. that is telling someone. second. the repo.saltstack.com is hardly a month old. be thankful they made this change early. this is also saltstacks first attempt at maintaining a repo them selves. they used to up to a month ago rely on othres for repo handaling.
20:10 cro joined #salt
20:10 Kruge whytewolf: The change is documented badly.  The URL in the instructions is "http://repo.saltstack.com/apt/ubuntu/latest/ubuntu14", and returns a 404.  That "contains latest", just in the wrong place.
20:12 whytewolf Kruge: then file a bug report.
20:15 DammitJim joined #salt
20:16 zmalone joined #salt
20:16 DammitJim can I do file.append with pillar data?
20:16 DammitJim I don't know why when I do this, it only appends the iface and address :(
20:16 DammitJim https://gist.github.com/anonymous/d55e76521b3705e5ccfe
20:16 Kruge Filed.
20:17 DammitJim Filed?
20:17 Kruge Sorry, not referring to you
20:17 Infradev joined #salt
20:18 ahammond Kruge better still... file a pull request against the docs. It's surprisingly easy to do. :)
20:18 aphor joined #salt
20:19 Kruge You assume I'm halfway competent
20:20 freelock joined #salt
20:23 hasues joined #salt
20:26 igorwidl joined #salt
20:27 ajw0100 joined #salt
20:33 cliluw joined #salt
20:34 BradThurber joined #salt
20:35 hal58th_ joined #salt
20:36 ajw0100_ joined #salt
20:38 keimlink joined #salt
20:38 ALLmightySPIFF joined #salt
20:39 ageorgop joined #salt
20:44 freelock joined #salt
20:48 aparsons joined #salt
21:01 murrdoc joined #salt
21:03 baweaver joined #salt
21:09 jeffpatton1971 joined #salt
21:10 brianvdawson joined #salt
21:10 jeffpatton1971 I have a question about users in pillars, was thinking about createing a separate pillar for mine /srv/pillar/users just to keep user junk all together does anyone else do something similar? or think this is a bad idea?
21:12 joshin joined #salt
21:12 aphor jeffpatton1971: as long as you don't need to target different minions with different users is great, but that would be for state independent users, not service accounts to run daemons controlled by states.
21:13 jeffpatton1971 @aphor so if I had a group of developers who only needed access to build servers and such and admins who needed access to all the things...separating them out like this doesn't work very well?
21:13 aphor jeffpatton1971: I do that for remote admin accounts used for "break in case of emergency" use.
21:14 aphor jeffpatton1971: for that I would have separate dev_users.sls pillar targeted for build servers and admin_users.sls pillar for everything.
21:14 jeffpatton1971 @aphor so maybe i'm really just thinking about this the wrong way...
21:15 murrdoc joined #salt
21:15 aphor jeffpatton1971: you can do it your way, but it doesn't allow the top.sls file to cut the minion work that's irrelevant.
21:15 jeffpatton1971 @aphor that actually sounds like it would be a little more flexible
21:16 BretFisher joined #salt
21:16 aphor jeffpatton1971: try to make things modular enough that you can define who should care about what in the top.sls files.
21:16 jeffpatton1971 @aphor just have a list of admin users and a list of dev users etc... and then let the pillar sort them out some how
21:16 jeffpatton1971 @aphor right
21:18 aphor jeffpatton1971: I have some states do stuff for all servers, like basic security stuff, and other stuff (states, pillars) that are role specific.
21:18 jeffpatton1971 @aphor I actually am half there then, I have a file for admins and I salt '*' that everywhere right now, trying to move away from that which is why I was thinking pillars
21:19 jeffpatton1971 @aphor do you paste keys into the states or can you have them read in from a file? was thinking about having everyone checkin a username.pub and just storing that on the master
21:19 aphor jeffpatton1971: you can make a dev_users.sls file that looks up dev_users pillar and creates those users on top of the base admin_users.
21:20 jeffpatton1971 @aphor how would you reference those in the top.sls file?
21:20 aphor jeffpatton1971: keys should go in pillars, so that the top.sls can limit access to them.
21:21 jeffpatton1971 I currently have a top with like one setting for an app that i'm starting to play with
21:22 jeffpatton1971 @aphor this is what I was looking at http://russell.ballestrini.net/understanding-salt-stack-user-and-group-management/ pillar example halfway down...so leaving the keys in the pillar is the best bet
21:22 aphor jeffpatton1971: jinja can pull keys from a pillar lookup and put them in a state by reference.
21:23 moloney Can service.running pass additional arguments?  It is an upstart system (ubuntu) and I need to run something like 'start myservice myarg1=val1 myarg2=val2' to start the service.  I tries passing the myarg/myval stuff through kwargs to no avail
21:23 aphor jeffpatton1971: that's a great example of what I'm taking about.
21:23 aphor instead of .. pillar.get('users' ..
21:23 jeffpatton1971 @aphor that's great
21:24 aphor you use .. pillar.get('dev_users ..
21:24 jeffpatton1971 @aphor and those are separate files
21:24 aphor and that goes into a dev_accounts.sls state file.
21:24 murrdoc left #salt
21:24 jeffpatton1971 @aphor stored /srv/pillar
21:24 murrdoc joined #salt
21:25 aphor the pillar example on that page is in the comments of the state file.
21:25 al joined #salt
21:26 aphor look at "# This state requires a pillar named 'users' with data formatted like:"
21:27 jeffpatton1971 @aphor I was thinking that goes in the top.sls file itself but i'm completely wrong aren't I? this would be a separate file users.sls in /srv/pillar
21:27 aphor that is an example of what, uncommented, in a /srv/pillar/dev_users.sls file, would give you a dev user spec for 'username' user account
21:27 jeffpatton1971 got it
21:28 aphor the rest of that example would go in /srv/state/dev_users.sls (assuming your states are in "/srv/state")
21:28 baweaver joined #salt
21:28 jeffpatton1971 ok...that makes more sense...I was thinking about this the wrong way...thanks so much for the clarification
21:29 aphor jeffpatton1971: then you can target dev boxes with both the pillar and state files for dev_users in the top.sls files, respectively.
21:30 jeffpatton1971 @aphor sweet...this will give me something to kick around over the weekend!
21:30 aphor jeffpatton1971: you're a better man than I am.. ;)
21:30 jeffpatton1971 @aphor lol...nah...you probably have a life ;-)
21:31 aphor Haha!
21:34 subsignal joined #salt
21:35 aurynn does anyone know if the cp.push module works over salt-ssh?
21:38 diegows joined #salt
21:40 larsfronius joined #salt
21:41 kinetic joined #salt
22:00 sgargan joined #salt
22:01 knite joined #salt
22:07 baweaver joined #salt
22:08 bfoxwell joined #salt
22:08 mrwboilers left #salt
22:10 pratikmallya joined #salt
22:11 nidr0x joined #salt
22:11 kitplumm_ joined #salt
22:13 aparsons_ joined #salt
22:13 nidr0x joined #salt
22:18 aparsons joined #salt
22:19 scoates joined #salt
22:19 mpanetta joined #salt
22:19 kitplummer joined #salt
22:23 dreamcat4 joined #salt
22:25 moogyver joined #salt
22:29 baweaver joined #salt
22:31 zmalone joined #salt
22:35 indispeq joined #salt
22:39 SheetiS joined #salt
22:41 salt_rocks joined #salt
22:41 scoates joined #salt
22:42 salt_rocks good evening
22:44 aurynn it looks like "no". It'd be neat if file.push used scp under the covers to actually do a file transfer.
22:44 aurynn on ssh
22:45 bregalad Kruge, ahammond: https://github.com/saltstack/salt/pull/28042
22:45 saltstackbot [#28042]title: fix repo path in ubuntu installation documentation | Fixes #28038.
22:45 bnikolaus joined #salt
22:45 ahammond jfindlay FTW. :)
22:46 bregalad still need to change my IRC nick :-(
22:46 jfindlay woohoo!
22:48 jalbretsen I call it regeneration
22:48 jfindlay lol jalbretsen
22:49 jfindlay didn't know you were a salt kind of person
22:49 jfindlay with all this ansible talk going around it makes you wonder who you can trust :-)
22:49 jalbretsen uh, really?
22:49 bnikolaus joined #salt
22:50 jalbretsen Tom and I had such a wonderful chat about Salt it made youtube ;)
22:50 jfindlay jalbretsen: so why aren't you applying at salt? :)
22:50 ahammond so... I want to run salt-cloud saltify from an orchestration... how do I do that?
22:51 murrdoc joined #salt
22:52 ahammond that orch gets triggered by a reactor, reacting to a salt/auth pending event... :)
22:54 Ch3LL_ left #salt
23:01 jfindlay joined #salt
23:02 al joined #salt
23:03 Ch3LL_ joined #salt
23:07 cdarwin joined #salt
23:08 bnikolaus joined #salt
23:09 Ch3LL joined #salt
23:09 cdarwin I'm wondering if gravyboat/Forrest is in here?
23:10 clone1018_ joined #salt
23:11 bnikolaus joined #salt
23:16 murrdoc joined #salt
23:19 bnikolaus /set charset.default.decode "ISO-8859-15"
23:22 bnikolaus ls
23:26 sgargan joined #salt
23:29 llua [sudo] password for bnikolaus:
23:30 dingo heh
23:33 zmalone joined #salt
23:36 baweaver joined #salt
23:37 bnikolaus joined #salt
23:37 szhem joined #salt
23:37 ahammond is there a standard best practice for generating a timestamp to put into salt generated files?
23:38 ahammond # Generated by salt at {{ uh... ??? }}
23:38 dingo probably iso8601 format
23:39 kitplummer joined #salt
23:40 murrdoc joined #salt
23:40 dingo ahammond: https://github.com/saltstack/salt/commit/babaef6bd468af2fc876a092194b22bca885f841#diff-457a19731b8307d768e8fc84a9ba28e8R267
23:40 ahammond dingo I'd be willing to shed blood if it were any other format.
23:40 dingo a country divided
23:41 dingo ahammond: i record my systems in Discordian datetime, https://github.com/a-tal/ddate
23:41 ahammond dingo that's fine, as long as they divide the day and the hour with a T
23:42 dingo # Generated by salt at Boomtime, the 32nd day of Chaos in the YOLD 3180
23:49 Qwazerty left #salt
23:57 rojem joined #salt
23:57 murrdoc joined #salt
23:57 keltim joined #salt

| Channels | #salt index | Today | | Search | Google Search | Plain-Text | summary