Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2017-04-20

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

All times shown according to UTC.

Time Nick Message
00:13 woodtablet left #salt
00:14 jas02 joined #salt
00:22 sarcasticadmin joined #salt
00:27 sarcasticadm joined #salt
00:51 txmoose joined #salt
00:55 txmoose Hey all, my local LUG is doing a series of talks on config management tools. This month was Ansible, and next month I'm giving a talk on Salt.  I'd like to open my talk with a brief history - things such as why was Salt developed and what it was originally meant to accomplish that the other big hitters didn't at the time - but I can't really find much history onilne.
00:55 txmoose Does anyone know where I might find some fun history of Salt to talk about?  Other than the very dry blurb on wikipedia.
00:55 hemebond txmoose: There are YouTube videos by the creator (who's name has slipped my mind right now) where he explains the reason for making Salt.
00:56 hemebond Tom Hatch
00:56 hemebond *Thomas
00:57 hemebond In a lot of his talks he goes over the history or reason for Saltstack before going into the details of how it works.
00:58 txmoose hemebond: ah I hadn't even considered youtube videos. I never think of YT for things like history :P thanks!
01:03 speedlight joined #salt
01:03 Felgar joined #salt
01:05 debian112 joined #salt
01:08 Felgar I'm trying to convince a bunch of chef users to try / switch to Saltstack. What might be the best way to do that?
01:08 Felgar (The reasons I switched to Salt 2 years ago ...might not be good enough to motivate others, especially if some of these folks have been using Chef for 4 years).
01:11 justanotheruser joined #salt
01:13 antpa joined #salt
01:16 fracklen joined #salt
01:17 jas02 joined #salt
01:21 txmoose What reasons did you switch to Salt 2 years ago?  What did you switch from?  What benefit do *you* get for *them* switching from Chef to Salt?     I'm not trying to be mean, just more trying to pose questions that the people you'll want to convince will want answers to.
01:21 txmoose Felgar: ^^
01:23 DEger joined #salt
01:26 antpa joined #salt
01:41 nikdatrix joined #salt
01:54 cro joined #salt
01:56 vexati0n joined #salt
01:57 johnkeates there isn't all that much reasons switching form Chef to Salt actually
01:58 johnkeates from others, it's obvious, puppet has a crap DSL and crap ruby dependency, it's slow and has bad modularisation, ansible is still "ssh and shell scripts with tacks and tape" etc.
01:58 SolitudeOrNot joined #salt
01:58 SolitudeOrNot hey?
01:58 johnkeates Salt has create programmability, fast, scalable, you can do everything with plain yaml if you wish, but jinja is there as well
01:58 SolitudeOrNot :s
01:59 johnkeates and there are plenty of libraries
01:59 johnkeates but all of those work for chef too
01:59 SolitudeOrNot left #salt
01:59 johnkeates so if someone has invested in that, then there may be no way to make them switch
01:59 johnkeates basically, if you are not on chef or salt, it's easy to go to salt
01:59 johnkeates if you are on chef, it depends on the investment
01:59 johnkeates left #salt
02:19 Pyro_ joined #salt
02:35 evle joined #salt
02:40 ssplatt joined #salt
02:42 cro joined #salt
02:44 edrocks joined #salt
02:53 Felgar Does salt still use zeroMQ as underlying queue/transport mechanism? or has it changed to something else?
02:53 hemebond Felgar: It's still there but you can use a different transport if you want to.
02:53 hemebond I'm using the TCP transport.
02:53 Felgar Is this documented somewhere? what are the other transports? whats enabled by default?
02:54 hemebond zeromq is the default transport.
02:54 hemebond RAET was a transport they were working on, but I don't know if it's still being worked on.
02:54 hemebond https://docs.saltstack.com/en/latest/topics/transports/
02:54 hemebond You can also make your own transport :-)
02:55 Felgar smoke signals hemebond, and they'll be 100% analog ;)
02:55 hemebond Sounds good :-D
02:56 Felgar SaltReqTimeout Exception: rain....
02:58 antpa joined #salt
03:00 khodgson joined #salt
03:12 antpa joined #salt
03:19 jas02 joined #salt
03:19 webtrekker joined #salt
03:22 * MTecknology needs to show off
03:22 MTecknology http://dpaste.com/2MVTBFV  <-- those execution times... boo-yeah
03:23 whytewolf nice
03:23 hemebond Are you showing off the speed of the minions or something to do with the states?
03:25 MTecknology the speed
03:25 MTecknology even my longest are ~10 sec now
03:25 hemebond The speed of the servers?
03:25 MTecknology the highstate
03:25 hemebond Ah. Did you do something interesting to reduce the time?
03:27 MTecknology New hardware... nothing that required a lot of skill
03:27 hemebond Ah
03:27 hemebond So just the speed of the minion (server).
03:27 hemebond That is pretty nice, though.
03:28 MTecknology gimme a sec to show off more...
03:30 justan0theruser joined #salt
03:32 gmoro_ joined #salt
03:32 norrit joined #salt
03:36 MTecknology there we go.. http://dpaste.com/0N03WQ4
03:37 whytewolf nice
03:42 nikdatrix joined #salt
03:51 evle joined #salt
03:51 MTecknology I'm finding out regression testing in golang for debian is pretty terrible so it's likely a lot of the resources will go to that.
03:53 MTecknology but if you ever wanna do that kinda testing! ratt is a pretty sweet utility!
04:02 khodgson_ joined #salt
04:16 rem5 joined #salt
04:29 khodgson joined #salt
04:34 sh123124213 joined #salt
04:46 edrocks joined #salt
04:55 rdas joined #salt
04:59 MeltedLux joined #salt
05:03 ssplatt joined #salt
05:18 antpa joined #salt
05:30 jas02 joined #salt
05:32 rdas joined #salt
05:35 antpa joined #salt
05:38 jdipierro joined #salt
05:39 Straphka joined #salt
05:42 nikdatrix joined #salt
05:43 ssplatt joined #salt
05:48 mpanetta joined #salt
05:52 yuhl______ joined #salt
05:54 LeProvokateur joined #salt
05:59 antpa joined #salt
05:59 _KaszpiR_ joined #salt
05:59 rdas joined #salt
06:02 jdipierro joined #salt
06:04 felskrone joined #salt
06:09 CeBe joined #salt
06:11 golodhrim|work joined #salt
06:16 LeProvokateur joined #salt
06:20 fracklen joined #salt
06:38 dezertol joined #salt
06:39 preludedrew joined #salt
06:40 candyman88 joined #salt
06:48 edrocks joined #salt
06:49 fracklen joined #salt
06:49 fracklen joined #salt
06:51 Ricardo1000 joined #salt
06:51 pezus joined #salt
06:55 CrummyGummy joined #salt
07:00 stooj joined #salt
07:00 pbandark joined #salt
07:05 pbandark joined #salt
07:12 jas02 joined #salt
07:23 antpa joined #salt
07:32 do3meli joined #salt
07:32 do3meli left #salt
07:35 fracklen joined #salt
07:36 fracklen joined #salt
07:37 antpa joined #salt
07:39 fracklen joined #salt
07:41 fracklen joined #salt
07:42 DEger joined #salt
07:43 nikdatrix joined #salt
07:47 ronnix joined #salt
07:55 Rumbles joined #salt
07:56 irated joined #salt
08:08 mikecmpbll joined #salt
08:10 om2 joined #salt
08:14 N-Mi__ joined #salt
08:16 Ricardo1000 hello
08:21 fracklen joined #salt
08:22 aldevar joined #salt
08:22 fracklen joined #salt
08:26 Mattch joined #salt
08:26 fracklen joined #salt
08:27 fracklen joined #salt
08:34 Dr_Jazz joined #salt
08:34 Dr_Jazz joined #salt
08:34 s_kunk joined #salt
08:43 evle joined #salt
08:45 gnomethrower joined #salt
08:52 bdrung_work joined #salt
08:56 colegatron joined #salt
09:06 DEger joined #salt
09:28 inad922 joined #salt
09:31 Rumbles joined #salt
09:34 jas02_ joined #salt
09:35 preludedrew joined #salt
09:35 jas02__ joined #salt
10:04 jdipierro joined #salt
10:06 Kelsar joined #salt
10:07 stooj joined #salt
10:12 toanju joined #salt
10:16 mpanetta joined #salt
10:18 Antiarc joined #salt
10:19 stooj joined #salt
10:20 cyteen joined #salt
10:34 pbandark1 joined #salt
10:52 edrocks joined #salt
10:56 mpanetta_ joined #salt
11:05 fracklen joined #salt
11:06 fracklen_ joined #salt
11:20 jbroulik joined #salt
11:21 Kelsar joined #salt
11:24 jbroulik Hi guys, how do you launch proxy minion with correct name without uncommenting line 439 in  /usr/lib/python2.7/dist-packages/salt/cli/daemons.py ? I am using salt-proxy -d --proxyid=vsrx01 command but without uncommenting this line it launches proxy minion with the name of the minion itself and not the device I want to control with salt.
11:26 Karunamon joined #salt
11:37 Miouge joined #salt
11:39 pbandark Hi.. I am trying to ping minion with pillar data. But it fails with "No minions matched the target". I am using  `salt -I 'devel:london:canary:building-b' test.ping`. https://paste.fedoraproject.org/paste/CMt8K-I~CKcYJjQHk3JyYV5M1UNdIGYhyRLivL9gydE=
11:43 pbandark am I making any mistake while targetting the minion from pillar data ?
11:45 o1e9 joined #salt
11:53 jas02 joined #salt
11:53 hemebond pbandark: You need to specify a value in your targeting.
11:53 hemebond e.g., elastic-data-1
11:54 pbandark hemebond: still it fails: ` salt -I 'devel:london:canary:building-b:elastic-data-1' test.ping`
11:54 hemebond Your pillar is "bulding" not "building"
11:57 pbandark ahh. me--  hemebond so if I am not wrong then it should only target to "elastic-data-1". not any other minions.
11:57 hemebond It will target any minion that has that value for that pillar.
12:00 watersoul joined #salt
12:03 pbandark got it. thanks hemebond
12:03 hemebond ????
12:05 watersoul joined #salt
12:07 fracklen joined #salt
12:08 fracklen_ joined #salt
12:10 watersoul joined #salt
12:13 fracklen joined #salt
12:13 fracklen joined #salt
12:15 watersoul joined #salt
12:15 numkem joined #salt
12:19 glyf joined #salt
12:20 watersoul joined #salt
12:23 DammitJim joined #salt
12:25 watersoul joined #salt
12:37 jbroulik joined #salt
12:42 edrocks joined #salt
12:43 rem5 joined #salt
12:45 edrocks joined #salt
12:47 amcorreia joined #salt
12:52 GMAzrael joined #salt
12:53 ronnix joined #salt
12:56 ProT-0-TypE joined #salt
13:05 brousch__ joined #salt
13:07 alvinstarr joined #salt
13:15 racooper joined #salt
13:19 ruxu joined #salt
13:19 Ricardo1000 hemebond: Hello
13:19 johnkeates joined #salt
13:20 Ricardo1000 hemebond: Can I use both nogroups and compund at the same time, to call several nodegroups from command line ?
13:21 antpa joined #salt
13:21 Cottser joined #salt
13:28 cyborg-one joined #salt
13:29 Pyro_ joined #salt
13:29 jdipierro joined #salt
13:38 tapoxi joined #salt
13:45 thebinary joined #salt
13:49 fracklen joined #salt
13:51 Tanta joined #salt
13:52 mishanti1 joined #salt
13:56 diegows joined #salt
14:06 khodgson joined #salt
14:09 Pyro_ joined #salt
14:09 zerocool_ joined #salt
14:09 zerocoolback joined #salt
14:10 fracklen joined #salt
14:12 Pyro_ joined #salt
14:31 khodgson joined #salt
14:33 ssplatt joined #salt
14:37 RabidCicada joined #salt
14:41 tercenya joined #salt
14:52 greyeax joined #salt
14:53 mpanetta joined #salt
14:55 khodgson joined #salt
14:58 antpa joined #salt
15:02 PatrolDoom joined #salt
15:06 khodgson joined #salt
15:10 seanz joined #salt
15:11 DammitJim joined #salt
15:15 zerocoolback joined #salt
15:16 contherad joined #salt
15:17 beardedeagle joined #salt
15:17 mat_ on https://docs.saltstack.com/en/latest/topics/tutorials/gitfs.html#refreshing-gitfs-upon-push, it explains how to refresh gitfs on git push, is there a similar way to refresh when pushing to a git_pillar repository ?
15:18 mat_ (I'm quite new to salt, and while the documentation is extensive, it may be overwhelming at times)
15:18 tiwula joined #salt
15:19 beardedeagle left #salt
15:19 evle2 joined #salt
15:19 khodgson joined #salt
15:20 Unoqualsiasi joined #salt
15:21 colegatron mat_, you can basically just add a "salt '*' saltutil.refresh_pillar" to the sh script, even when the pillar data is supposed to be as static as possible, even more than the states
15:21 Unoqualsiasi left #salt
15:22 mat_ colegatron, mmm, well, it will be mostly static, when I will have finished migrating from puppet :-)
15:22 colegatron I use to call the refresh_pillar manually when needed instead to do it automatically.
15:23 colegatron if you add the script run to the git hook maybe pillars will get updated more often than really needed, but it is up to you.
15:23 mat_ but "salt '*' saltutil.refresh_pillar" only works on the salt master, not on the box with the git repository
15:24 colegatron the master will push the pillar info to minions
15:24 mat_ yes, but I run git push, it goes to the git repository, and then, I need to notify the master that it has changed and it needs to be git pull'ed  and then distributed to the minions
15:25 sp0097 joined #salt
15:26 Rumbles joined #salt
15:26 colegatron yes. but for example in my use case pillars can change (in the repo) but then I only push any change when I really need that updates into the minions.
15:26 fracklen joined #salt
15:27 mat_ mmm, yes
15:27 colegatron depends on your workflow, just have it in mind.
15:27 mat_ but how does the box with the git repository that gets pushed to tell the salt-master that the git_pillar repository has been updated
15:27 mat_ ?
15:28 colegatron I do manually ask to the master to update the minions with the saltutil.refresh_pillar
15:28 mat_ for the states, the doc says to run /usr/local/bin/salt-call event.fire_master update salt/fileserver/gitfs/update, and then there is a reactor thing that translates that into a "runner.fileserver.update" command
15:29 mat_ ok, so, my question is how do I automate that ?
15:29 mat_ but for git_pillar
15:33 colegatron https://pastebin.com/D2vM9z8C
15:33 colegatron I think that's the way, but not running the refresh_pillar from the shell, sorry
15:33 gnomethrower joined #salt
15:34 colegatron I've just followed the same logic, but never used the saltutil runner that way. have a try
15:38 mat_ I'll try it, thanks :-)
15:38 colegatron welcome
15:44 Trauma joined #salt
15:44 khodgson joined #salt
15:48 dezertol joined #salt
15:51 aneeshusa joined #salt
15:54 khodgson joined #salt
15:55 jas02 joined #salt
15:55 Brew joined #salt
15:56 ds joined #salt
16:02 khodgson joined #salt
16:04 aneeshusa joined #salt
16:04 nixjdm joined #salt
16:05 art5005 joined #salt
16:05 Praematura joined #salt
16:05 art5005 hi all.. i have 2 'cmd.run' states.. but one needs to be executed before the other.. is there a way to add a 'cmd' to the require element?
16:06 art5005 i don't think   - require:   - cmd: <state-name>       works
16:06 aldevar left #salt
16:07 pbandark Hi.. Can anyone tell me exact difference between normal pillar(set with "pillar_roots") and external pillar(set with "ext_pillar")? What is use of "external pillar if we can manage the work with normal pillar ?
16:08 zerocoolback joined #salt
16:09 Trauma_ joined #salt
16:11 pbandark art5005: as per my info, state functions  will get executed as you define in state file. also, you can control the order by setting "order" value
16:11 pbandark lets wait for confirmation from other members.
16:13 zerocoolback joined #salt
16:15 pcn pbandark: aside from the source of the data, an external pillar should work the same as a pillar from a file
16:15 ecdhe joined #salt
16:16 pbandark pcn: ok. I am bit confused with the use cases of both options. :(
16:17 pbandark pcn: do you have any referrence document which I can refer to understand when to use normal pillar and when external pillar
16:18 * pbandark is also searching for syntax to define external pillar
16:18 jdipierro joined #salt
16:26 woodtablet joined #salt
16:26 dendazen joined #salt
16:28 whytewolf pbandark: if you want you pillar data to come from an external source. such as a database or git.
16:29 pbandark whytewolf: ok. in that scenario we wll use external pillar ?
16:30 pbandark whytewolf: i can also see term like "pillarstack" is it equivalent to external pillar ?
16:30 pcn pbandark: so if you have a REST api that you want to use to keep secrets, for e.g. (ala vault or something) - you can make that an external pillar instead of having to save your secrets unencrypted on-disk
16:30 pcn Then the saltmaster can fetch them and provide them to appropriate minions
16:31 pbandark ok
16:34 ProT-0-TypE joined #salt
16:34 antpa joined #salt
16:35 sarcasticadmin joined #salt
16:38 pbandark whytewolf: pcn: so "pillarstack" == "external pillars" ?
16:39 sarcasticadmin joined #salt
16:39 onlyanegg joined #salt
16:40 whytewolf yes, pillarstack is a filebase ext_pillar. but you don't have to use it if you don't want to
16:40 whytewolf personally I stay away from the filebased ext_pillars
16:43 GMAzrael joined #salt
16:43 pbandark ok
16:43 pbandark thanks for information whytewolf pcn
16:44 _JZ_ joined #salt
16:53 mikecmpbll joined #salt
16:53 sarcasticadmin joined #salt
16:57 wendall911 joined #salt
17:01 sarcasticadmin joined #salt
17:03 megamaced joined #salt
17:05 sarcasticadmin joined #salt
17:07 LeProvokateur joined #salt
17:08 Inveracity joined #salt
17:11 censorshipwreck joined #salt
17:12 khodgson joined #salt
17:14 pcn So I'm writing a runner to launch cloud instances the way we want, and I'm having the issue of trying to figure out where the parallel flag should get set to launch many, fast.
17:16 s_kunk joined #salt
17:19 Edgan joined #salt
17:20 englishm_llnw joined #salt
17:28 sarcasticadmin joined #salt
17:32 fracklen joined #salt
17:34 jhauser joined #salt
17:41 candyman88 joined #salt
17:48 promorphus joined #salt
17:49 promorphus joined #salt
17:51 KyleG joined #salt
17:51 KyleG joined #salt
17:52 sh123124213 joined #salt
17:53 pbandark joined #salt
18:04 icebal30 any way to do a salt '*' blah.blah and return non-empty minions?
18:04 cliluw joined #salt
18:05 whytewolf non-empty?
18:06 icebal- joined #salt
18:07 cscf icebal, what do you mean by "empty"?
18:08 icebal cscf, minions that do not output anything, like so
18:08 icebal minion1:
18:08 icebal minion2:
18:08 icebal minion3: pid=3
18:08 icebal minion4:
18:08 cscf icebal, ah, I see
18:08 icebal so it would only return to stdout minion3: pid=3
18:09 icebal yep yep
18:09 cscf icebal, You could always do some bash hackery, but I'm not aware of a Salt way
18:09 cscf perhaps | grep -v ':$'
18:11 icebal might do the trick, sad there isnt a --out=no_empty
18:11 icebal or --state_output=no_empty
18:12 cscf icebal, pull request XD
18:12 icebal lol when i get to that level, definitely :D
18:13 icebal right now i'm still trying to walk with simple beacons
18:20 jas02 joined #salt
18:21 GMAzrael joined #salt
18:22 cscf My first pull request to saltstack/salt just got merged an hour ago XD
18:22 djgerm cscf: winning!
18:22 cscf ikr!  I'm excited
18:23 whytewolf gratz cscf, beers on you!
18:26 ChubYann joined #salt
18:27 Renich___ joined #salt
18:27 sh123124213 joined #salt
18:27 hemphill joined #salt
18:27 dezertol joined #salt
18:28 impi joined #salt
18:28 SalanderLives joined #salt
18:29 londo joined #salt
18:36 ZiLi0n joined #salt
18:38 sh123124213 is it possible to spoof minion id from event.fire_master ?
18:43 promorphus joined #salt
18:43 edrocks joined #salt
18:43 cyteen joined #salt
18:49 aldevar joined #salt
18:49 ZiLi0n Hello everyone, is there a way to configure the salt master so that it never denies keys, always accept them even if the id is the same but the key of the minion has changed?
18:50 Deliant joined #salt
18:51 cscf ZiLi0n, https://docs.saltstack.com/en/latest/ref/configuration/master.html#open-mode
18:51 PatrolDoom joined #salt
18:52 ZiLi0n cscf thansk a bunch! exactly what I was looking for
18:52 cscf ZiLi0n, no problem, please do be careful with this setting
19:00 ZiLi0n cscf yes, it is for internal testing only
19:00 ZiLi0n thanks for the heads up!
19:00 Qlawy joined #salt
19:03 Praematura joined #salt
19:06 pbandark1 joined #salt
19:07 DEger joined #salt
19:15 fracklen joined #salt
19:15 LeProvokateur joined #salt
19:16 sh123124213 joined #salt
19:16 juntalis joined #salt
19:26 LeProvokateur joined #salt
19:29 nikdatrix joined #salt
19:40 keltim joined #salt
19:40 druonysus_ joined #salt
19:48 aneeshusa joined #salt
19:49 jas02 joined #salt
19:57 djgerm joined #salt
19:59 rem5 joined #salt
20:00 antpa joined #salt
20:08 jas02 joined #salt
20:19 viccuad joined #salt
20:19 viccuad Hi folks. Is there any way to copy symlinks as symlinks en-masse? file.recursedoes not honor them on 2016.11.1 with keep_symlinks = True
20:19 viccuad thanks in advance
20:27 Tanta use rsync
20:28 djgerm1 joined #salt
20:29 viccuad what about modes of files and the user that owns them? I don't see rsync being able to take care of that
20:29 Tanta lol
20:29 Tanta newbies
20:30 Tanta try 'man rsync' viccuad, and -A mode
20:31 Tanta maybe -a
20:31 viccuad Tanta: well, I thought you meant the rsync *state* :)
20:31 Tanta rsync -a --delete-after --exclude '.git' '{{ app_git_root }}/' '{{ app_web_root }}/'
20:31 Tanta nah, under cmd.run
20:31 Tanta that's how I sync web code, it's reliable
20:31 viccuad what a mess of salt then :/
20:32 Tanta ok princess
20:32 Tanta have fun in your ivory tower
20:32 viccuad I look forward to a provision solution that is only for linux, I keep finding things like this every now and then
20:34 fracklen joined #salt
20:37 aldevar left #salt
20:56 elektrix joined #salt
20:57 npetzall joined #salt
21:05 Praematura joined #salt
21:13 elektrix joined #salt
21:13 dezertol joined #salt
21:29 onlyanegg joined #salt
21:30 nikdatrix joined #salt
21:33 antpa joined #salt
21:37 druonysus_ joined #salt
21:38 preludedrew joined #salt
21:39 tiwula joined #salt
21:45 rem5 joined #salt
21:51 Vaelatern joined #salt
22:00 Guest73 joined #salt
22:00 Guest73 Hi All
22:00 Guest73 I am new to salt
22:01 Guest73 we have have salt minions already running on aws machines
22:02 Guest73 and I just install salt on my local machine
22:02 Guest73 and I just installed salt on my local machine
22:03 zulutango joined #salt
22:04 Guest73 I want to be able connect to these remote minions and apply a state but I can't figureout what I need to with the salt I just installed and how I can talk to the  existing salt minions that are running remotely ?
22:06 hemebond Guest73: You installed salt-master?
22:06 hemebond Where is your master? AWS or your local machine?
22:07 Guest73 @hemebond I just did `brew install saltstack` on my local machine
22:07 hemebond Who installed the minions in AWS?
22:07 hemebond I know brew is an OSX thing but I have no idea what you just installed.
22:07 Guest73 some devops people who no longer work here
22:08 hemebond Well, you need to find out what master, if any, they're connected to.
22:08 Guest73 when I do brew install saltstack
22:08 hemebond Only the master can really control the minions remotely.
22:08 Guest73 it install salt binary
22:08 hemebond Have you been through the tutorial?
22:09 Guest73 for example I can do salt --version
22:09 Guest73 and then it shows me
22:09 Guest73 salt 2016.11.3 (Carbon)
22:09 hemebond Okay so that seems to be a master.
22:09 Guest73 sure
22:10 whytewolf a master. but doubtful it is the master
22:10 hemebond Now you should install a minion (salt-minion) on your local machine and go through the tutorial.
22:10 Guest73 I dont really understand the tutorial that well sorry
22:10 Guest73 its a bit too much for me
22:10 whytewolf Guest73: did the prev guys leave any documentation on how it is setup?
22:10 Guest73 not really
22:10 hemebond Then you definitely don't want to go sending commands to AWS servers :-)
22:11 Guest73 those are test servers
22:11 Guest73 even if things break I am fine
22:11 Guest73 so I can use them to run simple examples
22:11 hemebond You need to go through the tutorial. And it's far easier if the master and minion are on the same machine.
22:13 Guest73 master and minion on the same machines? I though the who point of salt is to provision bunch of VM's at once with the necessary software while issuing one command
22:13 whytewolf Guest73: may i ask how you got stuck with this? it sounds like you had a team handaling devops. [a not very well organised team if there are no docs]
22:13 Guest73 and that one command I want to issue from my local to all remote aws machines
22:13 whytewolf Guest73: forget local except for the tutorial
22:13 whytewolf find the master
22:13 whytewolf it isn't your machine
22:14 Guest73 how do i find it?
22:14 whytewolf log into one of the minions and look for the mastter setting
22:14 Guest73 where?
22:14 whytewolf /etc/salt/minion
22:15 Guest73 sure one sec
22:15 whytewolf also check that file_client is not set to local
22:16 Guest73 hooray! found it
22:17 Guest73 so master is on a separate machine
22:17 Guest73 all our machines run ubuntu
22:17 Guest73 so I just logged into master
22:18 whytewolf okay. check the /etc/salt/master to look into how it is configured. make note of file_root [location of state files] pillar_root [location of pillar files]
22:18 whytewolf also see if there is an eauth section
22:18 Guest73 sure one sec
22:19 whytewolf also see if there are any files in /etc/salt/master.d
22:19 whytewolf basicly learn all the things that should be in the docs they didn't leave
22:21 Guest73 hmm..looks like I cant access /etc/salt/master but there some keys in /etc/salt
22:21 whytewolf you might need to become root
22:23 Guest73 yeah just tried that . it is asking for a password that I guess I dont have
22:24 whytewolf ...
22:24 whytewolf sudo su -
22:24 whytewolf how much experence working in a linux enviroment do you have?
22:24 Guest73 reasonable
22:24 Guest73 I tried sudo -i
22:25 Guest73 sudo su - also same thing
22:25 Guest73 there are no files under /etc/salt/master.d
22:26 whytewolf sudo is asking for the password of the user you are logged in as.
22:26 whytewolf if you don't have that password you are pretty boned
22:26 whytewolf esp in a cloud enviroment
22:27 Guest73 I logged in to the salt master machine using ssh -i hello.key ubuntu@x.x.x.x
22:27 edrocks joined #salt
22:27 Guest73 this hello.key is something our entire team shares
22:28 Guest73 but this key is for ssh right
22:29 Guest73 for sudo su - I am not sure what the password is
22:29 whytewolf yes. that is an ssh key. you need ubuntu's password
22:29 Guest73 I see
22:29 whytewolf or. prey that salt works from the ubuntu user
22:29 whytewolf salt '*' test.ping
22:29 whytewolf [if that doesn't work, you need to get to root]
22:29 Guest73 oh let me give that a shot sounds like great idea
22:29 DEger joined #salt
22:30 Guest73 yeah looks like I need a root access
22:30 Guest73 these are great suggestions though
22:31 Guest73 let me see if I can ask someone in my team for password
22:34 dendazen joined #salt
22:37 Guest73 what is the difference between .d files and the regular files. for example what is the difference between /etc/salt/minion vs /etc/salt/minion.d
22:38 Guest73 .d means daemon ?
22:38 MajObviousman can I get file.replace to simply delete a matched line?
22:39 whytewolf MajObviousman: repl: ""
22:40 whytewolf no real delete though
22:40 MajObviousman tried that. It left a blank line
22:40 whytewolf Guest73: .d is just a standard linux thing meaning all files in this directory are config files for X.
22:41 Guest73 got it!
22:41 whytewolf MajObviousman: it would. have you thought about file.line which has mode: delete
22:43 MajObviousman bummer, that's exactly what I need, but we're still using the EPEL packages locked to 2015.5
22:43 MajObviousman thanks
22:44 whytewolf ahhh, yeah that would be a problem. not sure if the epel packages are even being built by anyone anymore
22:47 djgerm joined #salt
22:52 antpa joined #salt
22:56 onlyanegg joined #salt
23:07 Praematura joined #salt
23:13 felskrone joined #salt
23:20 hemebond joined #salt
23:21 SalanderLives Is it possible to use variables inside of other jinja statements? Like so: - password: {{ salt['pillar.get']('passwords:mysql:{{user}}') }}
23:21 SalanderLives That doesn't seem to be rendering for me
23:21 hemebond SalanderLives: Yes, without the {{ }}
23:21 hemebond (since you're already inside Jinja)
23:22 SalanderLives So use: {{ salt['pillar.get']('passwords:mysql:'user) }} ?
23:23 hemebond Yes, but you will need to concatenate that variable to the string.
23:23 hemebond Check the Jinja2 documentation for details on that.
23:23 SalanderLives Thanks!
23:28 edrocks joined #salt
23:31 nikdatrix joined #salt
23:38 cyborg-one joined #salt
23:42 atree joined #salt

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