Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2016-10-29

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

All times shown according to UTC.

Time Nick Message
00:03 edrocks joined #salt
00:18 bltmiller joined #salt
00:19 sarlalian joined #salt
00:22 jas02_ joined #salt
00:22 zer0def joined #salt
00:25 mavhq joined #salt
00:34 jenastar joined #salt
00:42 psrjr joined #salt
00:54 spuder joined #salt
01:04 prg3 joined #salt
01:22 jas02_ joined #salt
01:30 amontalban joined #salt
01:34 nZac joined #salt
01:41 sebastian-w joined #salt
01:42 akhter joined #salt
01:46 Nahual joined #salt
01:48 ilbot3 joined #salt
01:48 Topic for #salt is now Welcome to #salt! | Latest Versions: 2015.8.12, 2016.3.3 | Support: https://www.saltstack.com/support/ | Logs: http://irclog.perlgeek.de/salt/ | Paste: https://gist.github.com/ (please don't multiline paste into channel) | See also: #salt-devel, #salt-offtopic | Ask with patience as we are volunteers and may not have immediate answers
01:48 catpigger joined #salt
01:50 rem5 joined #salt
02:04 esckroh_ joined #salt
02:05 edrocks joined #salt
02:24 jas02_ joined #salt
02:29 jenastar joined #salt
02:36 _JZ_ joined #salt
02:45 catpiggest joined #salt
03:00 prg3 joined #salt
03:03 fracklen joined #salt
03:04 justanotheruser joined #salt
03:05 bluenemo joined #salt
03:11 prg3 joined #salt
03:17 sp0097 joined #salt
03:28 bltmiller joined #salt
03:31 prg3 joined #salt
03:35 nZac joined #salt
03:39 prg3_ joined #salt
03:42 prg3 joined #salt
04:09 RandyT joined #salt
04:09 swills joined #salt
04:13 akhter joined #salt
04:30 jas02_ joined #salt
04:55 jenastar joined #salt
05:07 edrocks joined #salt
05:12 bocaneri joined #salt
05:12 alexanderilyin joined #salt
05:18 fracklen joined #salt
05:35 nZac joined #salt
05:36 systo joined #salt
05:45 Ni3mm4nd joined #salt
05:55 Ni3mm4nd joined #salt
06:02 fracklen joined #salt
06:11 lompik joined #salt
06:13 Ni3mm4nd joined #salt
06:15 Tish joined #salt
06:31 Ni3mm4nd joined #salt
06:32 jas02_ joined #salt
06:34 subsignal joined #salt
06:38 Ni3mm4nd joined #salt
06:50 mavhq joined #salt
07:00 nZac joined #salt
07:09 edrocks joined #salt
07:12 samodid joined #salt
07:48 Trauma joined #salt
08:29 mskjeret joined #salt
08:33 jas02_ joined #salt
08:39 cyteen joined #salt
08:41 fracklen joined #salt
09:04 netcho_ joined #salt
09:20 mskjeret joined #salt
09:35 jas02_ joined #salt
09:41 Thommi joined #salt
09:55 cyteen joined #salt
09:57 J0hnSteel joined #salt
09:58 J0hnSteel joined #salt
10:11 fracklen joined #salt
10:11 edrocks joined #salt
10:12 netcho_ joined #salt
10:14 mavhq joined #salt
10:18 mikecmpbll joined #salt
10:22 samodid joined #salt
10:27 J0hnSteel joined #salt
10:29 Electron^- joined #salt
10:30 samodid joined #salt
10:43 Elsmorian joined #salt
10:48 ivanjaros joined #salt
10:59 jeddi joined #salt
11:03 nZac joined #salt
11:04 Saltnoobie joined #salt
11:11 Saltnoobie Hi all salt noobie here quick question about salt at scale , after watching the air20 demo I am attempting to do somthing very similar but with a multitude of different applications running across 2 different docker hosts i assume if i take the haproxy script you guys used and modified the for image name and pushed that through a jinja loop to pick up all the different image names i could achieve as similar result with different ap
11:11 Saltnoobie same haproxy ?
11:16 J0hnSteel joined #salt
11:17 cz2 joined #salt
11:18 lompik joined #salt
11:36 jas02_ joined #salt
11:46 jeddi joined #salt
11:53 abednarik joined #salt
12:11 fracklen joined #salt
12:16 J0hnSteel joined #salt
12:20 amcorreia joined #salt
12:22 abednarik joined #salt
12:24 WKNiGHT joined #salt
12:29 dyasny joined #salt
12:43 IdoKaplan joined #salt
12:44 abednarik joined #salt
12:47 IdoKaplan Hi, i'm using git_pillar and I'm checking to start working with reclass. I understand that under the nodes folders,  I need to create file names of the name servers. Is it possbile to target via grains and not via name servers?
12:51 rem5 joined #salt
12:55 CEH joined #salt
12:57 nZac joined #salt
12:59 abednarik joined #salt
12:59 jas02 joined #salt
13:01 netcho_ joined #salt
13:07 sh123124213 joined #salt
13:13 nZac joined #salt
13:16 jeddi joined #salt
13:18 jeddi joined #salt
13:21 amontalban joined #salt
13:25 akhter joined #salt
13:35 SaltyVagrant joined #salt
13:38 jas02 joined #salt
13:38 abednarik joined #salt
13:38 jas02_ joined #salt
13:55 spuder joined #salt
14:01 cosming joined #salt
14:06 akhter joined #salt
14:15 edrocks joined #salt
14:25 abednarik joined #salt
14:26 cosming joined #salt
14:26 CEH joined #salt
14:38 rem5 joined #salt
14:39 rem5 joined #salt
14:39 jas02 joined #salt
14:41 jas02_ joined #salt
14:58 johnkeates joined #salt
15:01 cosming joined #salt
15:01 sp0097 joined #salt
15:02 devtea joined #salt
15:38 skeezix-hf joined #salt
15:39 jas02 joined #salt
15:46 jas02 joined #salt
15:48 abednarik joined #salt
16:05 mavhq joined #salt
16:09 amcorreia joined #salt
16:11 alexanderilyin joined #salt
16:17 edrocks joined #salt
16:17 hasues joined #salt
16:18 hasues left #salt
16:18 jas02 joined #salt
16:23 saltnoobie joined #salt
16:24 saltnoobie hi guys simple question I have templated a salt state to deploy multiple projects on docker from gitlab, each project needs to pass a seperate set of variables to the same template is it possible to say I want to apply this state using this pillarfile
16:24 saltnoobie on a per run basis
16:28 saltnoobie I use git webhooks to push to jenkins which simply runs an ssh command so on commit id like for it to ssh into salt and run a salt 'dockerserver' state apply template + using this pillar file
16:29 saltnoobie a different project would use a different pillar file
16:30 saltnoobie im totally new to salt so if theres a better way to do this let me know :D
16:32 saltnoobie the way ive thought of so far would be updating the top.sls at every commit so salt will load the new one automatically but in a self contained command seems cleaner
16:33 honestly saltnoobie: file.managed state has a "context" field
16:33 honestly you can use that to put a specific pillar sub-key for your template
16:34 honestly or you can do the same with jinja for the whole state file
16:35 saltnoobie but would that then need to be updated at every run ? requiring me to modify the template?
16:36 honestly what is different for every run?
16:36 saltnoobie the project
16:36 saltnoobie i have 300 different projects to deploy
16:36 saltnoobie the template can deploy all 300 if passed a list of 10 variables
16:37 honestly you can add pillar data to a salt run via the cli
16:37 saltnoobie you can do that for a whole file or just per variable ?
16:38 subsignal joined #salt
16:39 honestly it will be merged into the pillar your state execution sees
16:40 honestly you run it like this: salt '*' state.sls some.state pillar='{"settings":{"foo":"a"}}'
16:40 honestly and it will be accessible as pillar['settings']['foo']
16:40 jas02_ joined #salt
16:41 saltnoobie is there anyway of loading a whole sls file into the state pillar? for example salt '*' state.sls somestate pillar= projectname.sls
16:42 saltnoobie for a single run
16:42 honestly you can select the pillar root
16:42 honestly but I don't know why you want to do that
16:42 cosming joined #salt
16:42 honestly just have all data for all your projects in subtrees in your pillar
16:43 saltnoobie so have the sls fines stored in /pillar/project1/data.sls
16:44 honestly sure
16:45 rtjohan joined #salt
16:46 abednarik joined #salt
16:47 saltnoobie think the easiest thing to do would be to just cat the file and then assign that pillar={"settings":
16:48 saltnoobie think the easiest thing to do would be to just cat the file and then assign that pillar={"settings":$var during execution
16:48 honestly no, that's a terrible idea
16:49 rtjohan joined #salt
16:49 saltnoobie its going to be deploying onto the same machine so i cant really use the top file to select the state
16:49 saltnoobie *pilalr
16:49 saltnoobie *pillar not state
16:56 rj-code joined #salt
16:56 honestly saltnoobie: https://gist.github.com/duk3luk3/3d4381cade4fb5135534d8db3e9a4e9c
16:57 rjcode joined #salt
16:59 DEger joined #salt
17:01 saltnoobie perfect Thank you quick question what is the "rt" refuring to
17:01 saltnoobie *refering
17:03 honestly you can call that whatever you like, I called it rt for "runtime"
17:05 jenastar joined #salt
17:05 rjcode joined #salt
17:10 rjcode joined #salt
17:11 saltnoobie Thank you :D sorry for the silly questions
17:11 honestly the normal salt way would be to run the deploy state for all projects every time
17:12 honestly it should just be idempotent
17:12 honestly i.e. it should check if any files are changed etc.
17:12 honestly and then only restart services / servers / containers in that case
17:13 saltnoobie all projects are using the same deploy.sls as the deploy steps are the same just file names change giturls ect but by pumping different pillar files i can avoid having 300 state.sls
17:15 honestly check out jinja templating for state files
17:15 honestly you only need a single sls
17:15 honestly you can basically use a for loop to create the states for all your projects
17:19 rjcode joined #salt
17:21 alexanderilyin joined #salt
17:21 analogbyte joined #salt
17:21 analogbyte left #salt
17:32 psih0man joined #salt
17:36 sjmh joined #salt
17:39 psih0man hello everyone! I would like to know something important about salt before deciding to learn and try it: if I have a group of hosts with different roles (web, db, lb, cache, etc.) and I'm adding a new server to the group, will I be able to run the configuration only on that host or if I start running the configuration will salt run it on all defined hosts? I searched for an answer to this question on the website, but maybe not deep enough, so forgive me
17:39 psih0man if I'm asking a stupid question.
17:40 rjcode joined #salt
17:40 honestly every call to salt includes targeting
17:40 honestly so you always select the minions (slaves/clients) you want salt to run on
17:41 rjcode joined #salt
17:46 onlyanegg joined #salt
17:47 psih0man honestly, I have experience with puppet and ansible. in puppet, there's a local agent that compiles the changes to be made on the current host and then gets that host to the desired state. in ansible, the master connects to all hosts and checks them everytime it runs and does some things regardless if they are nedded to be done or not ( I know this can be controlled in playbooks with "when:" but it should actually detect it iself, not wait for me to
17:47 psih0man specify it). so I'm curious if the behaviour I see in puppet is similar with what salt does. so if I'm adding a new host, its mere presence should trigger the configuration check and change even though the other hosts are periodically checked and nothing is changed on them.
17:51 sagerdearia joined #salt
17:53 honestly you can do that with salt reactor
17:54 psih0man honestly, I will look that up. thanks :)
17:57 rjcode joined #salt
17:58 west575 psih0man: yes, although it depends if you're talking about running salt as a command line "push" or having a minion checking or...there are a few other variations
17:58 rjcode joined #salt
18:03 lompik joined #salt
18:21 psih0man west575, what I missed in puppet was a way to tell all puppetagents "check now", like a push followed by a pull. also, in ansible I can only say "run everything now!".
18:28 Gareth joined #salt
18:31 onlyanegg joined #salt
18:32 fracklen joined #salt
18:42 jas02 joined #salt
18:46 onlyanegg joined #salt
18:49 subsignal joined #salt
18:49 DEger joined #salt
19:00 ivanjaros joined #salt
19:04 jas02 joined #salt
19:11 RandyT_ joined #salt
19:19 edrocks joined #salt
19:26 rjcode left #salt
19:31 jas02 joined #salt
19:32 fracklen joined #salt
19:34 alexanderilyin joined #salt
19:43 jas02_ joined #salt
19:46 west575_ joined #salt
19:54 cyteen joined #salt
20:05 subsignal joined #salt
20:07 sjorge joined #salt
20:07 sjorge joined #salt
20:24 catpig joined #salt
20:25 sgo_ joined #salt
20:43 akhter joined #salt
20:45 fracklen joined #salt
20:52 spuder joined #salt
21:04 netcho_ joined #salt
21:20 edrocks joined #salt
21:25 amontalban joined #salt
21:25 amontalban joined #salt
21:30 DEger joined #salt
21:37 chutzpah joined #salt
21:37 chutzpah joined #salt
21:38 LeProvokateur joined #salt
21:38 chutzpah joined #salt
21:39 dnull joined #salt
21:45 jas02_ joined #salt
21:52 west575 joined #salt
21:53 cyborg-one joined #salt
21:57 west575 joined #salt
22:04 jenastar joined #salt
22:04 om2_ joined #salt
22:06 esharpmajor joined #salt
22:07 rmc3 joined #salt
22:09 stanchan joined #salt
22:09 fracklen joined #salt
22:23 preludedrew joined #salt
22:24 nidr0x joined #salt
22:25 DEger joined #salt
22:26 Antiarc joined #salt
22:26 DEger joined #salt
22:36 alexanderilyin joined #salt
22:38 DEger joined #salt
22:46 jas02 joined #salt
22:53 abednarik joined #salt
22:55 edrocks joined #salt
23:00 subsignal joined #salt
23:04 fracklen joined #salt
23:09 jab416171 joined #salt
23:10 abednarik joined #salt
23:11 akhter joined #salt
23:16 stanchan joined #salt
23:21 abednarik joined #salt
23:29 alexanderilyin joined #salt
23:48 amontalb1n joined #salt
23:58 fracklen joined #salt

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