Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2015-06-30

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

All times shown according to UTC.

Time Nick Message
00:01 supersheep joined #salt
00:02 hasues joined #salt
00:02 hasues left #salt
00:04 clintberry1 joined #salt
00:10 monkey66 joined #salt
00:10 napsterX joined #salt
00:13 supersheep joined #salt
00:13 murrdoc joined #salt
00:14 pravka joined #salt
00:15 pcdummy joined #salt
00:15 pcdummy joined #salt
00:18 emaninpa joined #salt
00:19 napsterX joined #salt
00:28 favadi joined #salt
00:30 Sokel left #salt
00:32 j_t joined #salt
00:34 j_t I've been using puppet for a couple months or so to manage some nodes. Though now we're deploying kubernetes, and it seems like the kubernetes team has some ready to go salt work, for automating the management of a kubernetes cluster. ( https://github.com/GoogleCloudPlatform/kubernetes/tree/master/cluster/saltbase/salt )
00:34 j_t We deployed a kubernetes cluster manually as part of a POC, and we're going to move forward a bit. Though now I want to make sure the management of the kubernetes cluster is stored in git, and easy to change for all the nodes, and make new cluster easily, etc.
00:35 j_t Does anyone have any salt intro guides? I'm not even sure where to start. I see a bunch of sls files.. not sure what to do with them yet
00:36 mosen the salt docs have a few guides.. I think youd be looking at States specifically
00:36 mosen states is salt terminology for a puppet manifest
00:37 j_t ok
00:37 j_t We have minions on all the nodes, and a salt master. I can execute arbitrary commands on all the minions now.
00:37 mosen all good :)
00:46 ALLmightySPIFF joined #salt
00:48 julez joined #salt
00:51 jambulance joined #salt
01:02 otter768 joined #salt
01:03 juanito joined #salt
01:06 unholycrab joined #salt
01:11 anotherZero joined #salt
01:16 juanito joined #salt
01:18 ageorgop joined #salt
01:18 quasiben joined #salt
01:20 napsterX joined #salt
01:22 thehaven joined #salt
01:27 otter768 joined #salt
01:45 anotherZero joined #salt
01:47 malinoff joined #salt
01:51 beauby joined #salt
01:51 kermit joined #salt
02:00 MatthewsFace joined #salt
02:00 quasiben joined #salt
02:11 beauby joined #salt
02:20 napsterX joined #salt
02:21 quasiben joined #salt
02:34 quasiben joined #salt
02:36 napsterX joined #salt
02:40 CeBe1 joined #salt
02:46 beauby joined #salt
02:48 ALLmightySPIFF joined #salt
03:03 sunkist joined #salt
03:05 aea joined #salt
03:09 yomilk joined #salt
03:12 beauby joined #salt
03:14 freelock joined #salt
03:26 napsterX joined #salt
03:33 prathee joined #salt
03:33 pravka joined #salt
03:37 alexanderilyin joined #salt
03:38 mosen joined #salt
03:56 otter768 joined #salt
03:57 impi joined #salt
04:03 writtenoff joined #salt
04:04 hrumph_ in the page on grains it gives an example where physical location data is used as custom grain data... but isn't it always easier to use pillar data because how would you assign custom grain data from the master?
04:04 hrumph_ apart from changing minion config files and restarting the minion service
04:04 hrumph_ even for physical location data wouldn't it be better to use pillar variables?
04:05 hrumph_ or is there some way to set grains on the salt-master?
04:11 hrumph_ so is there any benefit to custom grains at all?
04:12 mosen theres an execution module for grains.append etc
04:12 mosen the purpose is slightly different
04:13 mosen how would you assign the right location pillar to the right hosts without information that was stored or assigned to the host
04:13 hrumph_ i would but you get enough info for that just from the non-custom grains
04:13 hrumph_ the basic grains are enough to bootstrap you
04:13 mosen if the standard grains are enough thats ok
04:14 hrumph_ mosen, i can't conceive of a situation where they wouldn't be
04:14 hrumph_ i guess it's because our machines all have a model type and a service number
04:14 mosen I put salt on clients so i have a grain that contains info about whether its a mobile or desktop user :)
04:15 hrumph_ mosen, you may have a point. i may not have enough bootstraping info in some cases
04:15 mosen hrumph_: if you found some imaginary situation where you couldnt control all the model numbers
04:15 mosen you might set a grain for each new minion
04:16 hrumph_ mosen ok i don't even know why you need to bootstrap with grain data at all when you've still got the minion id
04:16 hrumph_ you can always start off with that
04:17 mosen based on the hostname?
04:17 alexanderilyin joined #salt
04:18 hrumph_ we'ere thining of just doing deskop1 desktop2, ....laptop1 laptop2,...vm1, vm2...
04:18 hrumph_ that kind of thing
04:18 hrumph_ we'll write down the rooms on paper as we are installing salt minion
04:18 hrumph_ then we can set up the pillar data later
04:19 hrumph_ is the a problem with doing that?
04:19 mosen nope
04:20 hrumph_ so no benefit to custom grains that i can see
04:21 mosen not everyone will create a dependency between their hostname and the configuration of the host
04:21 hrumph_ by hostname you mean the minion id?
04:22 mosen yeah or minion id, if youre setting that manually
04:22 hrumph_ mosen, why wouldn't they? the minion id is like a primary key in a db
04:22 hrumph_ mosen, yes we'll be setting the minion id's manually
04:23 mosen because I  guess if you fork something into two sets or more of configuration based on a common theme then you have to identify and rename a subset of minions in order to apply that configuration
04:23 mosen if you dont want to use custom grains, thats fine :)
04:24 mosen I'm just saying, it works in some cases
04:24 hrumph_ ok ty for answering. much to consider
04:24 hrumph_ mosen, you may have a valid point there
04:25 mosen for me its more of a general pattern of abstraction like in software dev.. I dont like creating co-dependencies on unrelated pieces of information
04:25 hrumph_ mosen, fair enough
04:26 julez joined #salt
04:27 hrumph_ cept you could say that of any db where you use numbers as the primary key
04:27 hrumph_ and a lot of people like to use numbers
04:37 tzero joined #salt
04:37 mosen If youre really annoyed by custom grains then its ok, don't use them :)
04:46 jghazally joined #salt
04:48 ramteid joined #salt
04:49 ALLmightySPIFF joined #salt
04:50 hrumph_ mosen, no i've been listening to you
04:50 hrumph_ mosen, i think you might have a point actually
04:50 hrumph_ mosen, the thing about custom grains is that setting grains is more of a deployment process than a live process
04:51 hrumph_ so if you forget to set a custom grain you're going to get a blank value on something
04:51 hrumph_ if you leave something as pillar data you might forget to change it when you redeploy a minion
04:52 hrumph_ so there's a real advantage there
04:53 hrumph_ for instance i can easily conceive of people forgetting to switch the room number around in pillar data
04:53 hrumph_ but if its set as custom grain data either it's going to be set right...or it won't exist...
04:53 jalbretsen joined #salt
04:54 jghazally left #salt
04:57 prathee joined #salt
05:04 zer0def joined #salt
05:05 mosen you can change custom grains after you deploy the minion though, its not impossible
05:05 mosen but you have to know which minions you're changing in the first place :)
05:06 hrumph_ mosen, yes but it sort of forces the issue
05:06 hrumph_ if left in pillar data no one will notice
05:07 prathee joined #salt
05:07 hrumph_ when we redeploy we start with a complete re-image
05:07 prathee hey all! good day! :) i have a really trivial question... every time my files get managed by the master.. where are the logs related to the file management stored?
05:07 mosen alternatively I think some people use reclass or something for node classification so that the pillar data gets generated based on the node classification
05:10 andrew_v joined #salt
05:12 cberndt joined #salt
05:12 rdas joined #salt
05:12 hrumph_ mosen, that stuff would be overkill in my rinky dink organisation
05:12 mosen hrumph_: hi5 fellow rinky dink org
05:12 markm joined #salt
05:23 dopesong joined #salt
05:28 calvinh joined #salt
05:37 catpigger joined #salt
05:39 prathee hello...anybody....? where can i find the logs related to some basic file management???? tried setting the log_level_logfile : all.... still cant find the file management details being logged in var/log/master :(
05:40 whytewolf prathee: what exactly are you trying to find?
05:40 edrocks joined #salt
05:45 prathee some entry in a log file saying...the file xyz has been modified and restored to the correct state by making changes so and so...?
05:45 whytewolf prathee: that kind of info is stored in job info. you can attach a returner that might save it to a file
05:46 prathee oh okie...will look into it... thank you! :)
05:47 evle joined #salt
05:48 prathee_ joined #salt
05:51 stoogenmeyer__ joined #salt
05:56 Aidin joined #salt
05:57 colttt joined #salt
05:57 otter768 joined #salt
06:00 Eccentricson joined #salt
06:01 Eccentricson I'm having an issue with my salt minion communicating to my salt master that resides within a docker container.  My docker host forwards port 38772 -> 4505 and 38773 -> 4506 (return port).  I setup my minion to communicate on 38773 with the master, but when I run anything from the salt master I can see the minion trying to get back to the master on 4505.  Thoughts?
06:07 malinoff joined #salt
06:13 KermitTheFragger joined #salt
06:15 julez joined #salt
06:15 AndreasLutro joined #salt
06:23 donmichelangelo joined #salt
06:24 flyboy joined #salt
06:24 dopesong joined #salt
06:35 toanju joined #salt
06:44 vaspiros joined #salt
06:56 vaspiros joined #salt
06:58 napsterX joined #salt
06:58 juanito joined #salt
06:59 kawa2014 joined #salt
07:00 thalleralexander joined #salt
07:00 al joined #salt
07:03 prathee joined #salt
07:03 lb1a joined #salt
07:05 prathee hey again all! im just getting to know about returners...and its a bit hard to grasp for a newbie... can someone tell me how exactly i can store 'job' details to a file? that is, the details of /var/cache/salt/master/jobs to some file?
07:06 pviktori joined #salt
07:08 kawa2014 joined #salt
07:08 prathee the details in /.../jobs are not that understandable...if only i could store details into a file which could tell me 'so and so file has been updated and restored to the correct state by making so and so changes'....
07:09 colttt joined #salt
07:09 eseyman joined #salt
07:16 ws2k3 joined #salt
07:20 bones050 joined #salt
07:28 kawa2014 joined #salt
07:28 juanito joined #salt
07:29 julez joined #salt
07:30 chiui joined #salt
07:34 soren joined #salt
07:42 yamnog_ joined #salt
07:42 napsterX joined #salt
07:43 forrest joined #salt
07:43 impi joined #salt
07:46 jeddi joined #salt
07:56 pgranere joined #salt
07:56 pgranere left #salt
07:58 otter768 joined #salt
07:58 impi joined #salt
08:00 viq joined #salt
08:04 s_kunk joined #salt
08:05 KFDM joined #salt
08:05 KFDM left #salt
08:06 pviktori joined #salt
08:10 cberndt joined #salt
08:15 keimlink joined #salt
08:19 Xevian joined #salt
08:20 iwishiwerearobot joined #salt
08:28 ws2k3 joined #salt
08:28 mgar joined #salt
08:31 illern_ joined #salt
08:35 ScrumpyJack joined #salt
08:37 napsterX joined #salt
08:40 julez joined #salt
08:45 fisuk hi all, I wonder if it's anyhow possible to disable the automatic key generation used for preseeding when using salt-cloud with deploy=True?
08:48 riftman joined #salt
08:49 napsterX joined #salt
08:58 davromaniak joined #salt
09:01 N-Mi joined #salt
09:04 fe92 joined #salt
09:08 dkrae joined #salt
09:15 dRiN joined #salt
09:18 julez joined #salt
09:22 markm joined #salt
09:25 N-Mi joined #salt
09:27 denys joined #salt
09:28 riftman joined #salt
09:33 ALLmightySPIFF joined #salt
09:34 MK_FG joined #salt
09:36 ingslovak joined #salt
09:39 iwishiwerearobot joined #salt
09:41 seblu joined #salt
09:43 soren joined #salt
09:46 markm joined #salt
09:47 N-Mi joined #salt
09:49 wnkz joined #salt
09:55 riftman joined #salt
09:56 IanV0rn2341 joined #salt
09:57 wnkz_ joined #salt
09:57 IanV0rn2341 is there a good way of setting up a new remote server with a salt-minion? (chicken/egg!)
09:59 babilen IanV0rn2341: How do you install the rest of the software that it comes with to begin with?
09:59 otter768 joined #salt
10:00 babilen You could also use salt-ssh+salt-formula, the bootstrap script, simply installing it manually, baking it into a hypothetical image you use for new boxes, ....
10:00 IanV0rn2341 babilen: Well, I was hoping that I could use salt to provision everything it needs. which leads me to the problem, how to push a minion on in the first place.
10:01 IanV0rn2341 "baking it into a hypothetical image" sorry, I am not clear on what you mean?
10:01 babilen So, how are these systems provisioned? (e.g. "what installs the "ls" command?")
10:01 IanV0rn2341 It starts life as a distro installed box, from a cloud provider like aws/etc.
10:01 IanV0rn2341 so I can ssh in etc.
10:02 riftman joined #salt
10:02 babilen Most cloud providers allow you to upload your own images (which is what I meant with "bake it into the image").
10:02 IanV0rn2341 ATM, I have a bash script that ssh's in and runs the salt minion bootstrap script, but I was wondering if there was a more elegant way.
10:02 babilen But you can do better for others with salt-cloud (see https://docs.saltstack.com/en/develop/topics/cloud/index.html)
10:02 IanV0rn2341 Ah yeah, I see, thanks for clarifying.
10:02 evle1 joined #salt
10:03 zer0def joined #salt
10:03 IanV0rn2341 Ok, looks interesting, I'll have to have a good read.
10:05 IanV0rn2341 ATM we are not using a big named provider, more of a raw hosted server rack space, but I might get some mileage learning both pre-defined-image, and or salt-cloud.
10:05 kiorky joined #salt
10:05 babilen Which is why I asked how the systems are being provisioned. I mean *something* decides which software they come with and you might be able to hook into that
10:06 babilen It *really* depends on what you are doing ... salt-cloud is nice, but won't help you much if your cloud doesn't speak any of the supported dialects
10:07 IanV0rn2341 I don't think they do much for us, I think they just provide a raw distro, but we might be able to provide our own, as you say.
10:08 babilen Do they use images or do they bootstrap a new distro every time a new box is being installed?
10:08 soren_ joined #salt
10:09 darknight87 joined #salt
10:09 IanV0rn2341 good question, I will have to ping them. (I'm a new devop on this team, so still getting to know the providers and what they do)
10:09 darknight87 left #salt
10:09 darknight87 joined #salt
10:10 darknight87 Hi guys, I want to create a remote linux user using salt with a setting such that the user needs to set their password during the first login. How can I achieve this?
10:11 babilen darknight87: Just create the user and run chage?
10:11 ndrei joined #salt
10:12 babilen But why don't you assign passwords? People pick horrible passwords for themselves!
10:12 darknight87 babilen, I couldn't figure out how to set passwords using Salt
10:13 darknight87 we already had a discussion about my setup. I want to store passwords so that I can hand them over to the user
10:13 darknight87 Since I can't do that securely and effectively, I decided to go the password reset route
10:14 riftman joined #salt
10:14 babilen Right .. didn't I suggest to write to the mailing list about that? I might have missed it, but I don't think that I've seen a discussion about this topic
10:16 julez joined #salt
10:16 darknight87 babilen, u did suggest mailing them the password. Unfortunately, we will definitely create the linux user before we have any SPOC email ID. Also, the server doesn't have MTA functionality
10:16 darknight87 SMTP is not allowed :(
10:17 babilen No, not mailing the password to the users, but writing to the salt mailing list to ask about good ways to do achieve this?
10:17 darknight87 oh, no I haven't done that
10:18 darknight87 but a friend who uses salt a lot said that he always sets the password reset flag(first login)
10:19 AndreasLutro I just give users a strong default password, set `enforce_password: false` and leave it up to the user to change it if they insist
10:20 darknight87 one more thing, how can we make salt sls files read or take input from a file on the salt server?
10:20 darknight87 I couldn't find any examples
10:21 AndreasLutro darknight87: "take input from"? by "salt server" you mean the master?
10:21 ITChap joined #salt
10:22 darknight87 yes, I mean the salt master. I have a file with the list of users and the server IP addresses where they need to be created. How can I fetch these values from that file so that the master can create the users on the correct server(minion)
10:24 AndreasLutro well, if it can be placed inside salt's file_roots it should be a simple import, provided it's in a recognizable format like yaml or json
10:25 darknight87 aah, no, it's just a plain text file
10:25 AndreasLutro if not then you might want to write a custom module for reading/parsing the file
10:25 darknight87 but yes, I can create a yaml file
10:25 babilen But then you might want to simply define your users in pillars and use the users-formula to create them. Pillar assignment and content would, naturally, be entirely up to you.
10:25 darknight87 any examples I can follow?
10:25 AndreasLutro yeah I'd just put them in the pillar like babilen said
10:26 babilen (and you don't have to use the users-formula if you don't want to, but it is fairly well maintained and covers a number of use cases already)
10:26 darknight87 babilen, any example that I can refer to?
10:26 babilen https://github.com/saltstack-formulas/users-formula + https://github.com/saltstack-formulas/users-formula/blob/master/pillar.example
10:27 babilen You could also keep that in an external pillar if you don't fancy yaml
10:28 babilen I just have users/$SUBDISION/$USER.sls in my pillar and just assign them to various minions (some by nodegroups, some by ID, some .... http://docs.saltstack.com/en/latest/topics/targeting/compound.html )
10:29 PI-Lloyd Morning, is it possible to have salt-cloud provision and attach a disk on GCE via a cloud profile?
10:29 babilen That is: One file per user that I assign to different boxes (pillar data is being merged)
10:30 cberndt joined #salt
10:31 PI-Lloyd for example, we have a profile for a specific instance size, and we have a lot of systems that require additional disks. The process atm is to provision disk, spin up instance, attach disk, run highstate... this is not really ideal and would like to streamline it a bit more by just specifying "salt-cloud -p <profile> <instance_name>" and it auto provision & attach the relevant disk if it doesn't already exist
10:33 soren joined #salt
10:33 soren joined #salt
10:40 giantlock joined #salt
10:53 ntropy if im writing a custom grain, how can i access the value of another grain?
10:53 soren joined #salt
10:53 ntropy i was expecting this to work: manufacturer = __grains__['manufacturer']
10:55 ntropy KeyError: 'manufacturer' is the error i get
10:56 AndreasLutro considering it's not possible to determine which order grains are loaded in, I'm going to guess it's not possible
10:57 AndreasLutro though I guess custom grains should come after core ones...
10:58 ntropy i was hoping that was the case, yes
10:58 AndreasLutro do you know that the manufacturer grain is actually available on the minion?
10:58 AndreasLutro `salt minion-name grains.get manufacturer`
11:01 ndrei joined #salt
11:02 ntropy yes, manufacturer grain is present.  also tried with 'id' grain with same results
11:03 ntropy cant see from trace-level output what order the grains are loaded in
11:04 AndreasLutro maybe they're loaded in the correct order but still don't have access to eachother's data
11:06 cberndt joined #salt
11:11 ntropy do you know how to check that?
11:11 ntropy for the sake of it, here's my grain code and trace output https://gist.github.com/anonymous/4b6b07a457f282f4cf02
11:11 AndreasLutro ntropy: reading the source code, I guess :)
11:12 AndreasLutro ntropy: it looks like the code has been changed a bit in the develop branch to use lazy execution, so maybe what you want to do will be possible in the next release
11:13 napsterX joined #salt
11:13 ntropy oh, just noticed the grain code i pasted has manufacturer = __grains__['id'] instead of manufacturer = __grains__['manufacturer']
11:13 aqua^c joined #salt
11:14 ntropy so sub KeyError: 'manufacturer' for KeyError: 'id' in the gist
11:17 gaborn joined #salt
11:20 ALLmightySPIFF joined #salt
11:20 devops joined #salt
11:21 djstorm joined #salt
11:21 devops can anyone help me to install system-wide rvm using salt
11:24 giantlock joined #salt
11:28 julez joined #salt
11:28 stoogenmeyer joined #salt
11:33 quasiben joined #salt
11:35 jhauser joined #salt
11:35 markm joined #salt
11:41 _JZ_ joined #salt
11:47 riftman joined #salt
11:48 pix9 joined #salt
11:48 yomilk joined #salt
11:51 RDc left #salt
11:51 CeBe joined #salt
11:52 RDc joined #salt
11:59 zerthimon joined #salt
12:00 otter768 joined #salt
12:05 amcorreia joined #salt
12:07 mohae_ joined #salt
12:14 aqua^c joined #salt
12:20 ndrei joined #salt
12:26 icflournoy joined #salt
12:27 CeBe joined #salt
12:29 yomilk joined #salt
12:34 riftman joined #salt
12:46 julez joined #salt
12:50 subsignal joined #salt
12:51 supersheep joined #salt
12:53 subsigna_ joined #salt
12:53 CeBe1 joined #salt
12:59 stephanbuys joined #salt
13:04 furrowedbrow joined #salt
13:06 zer0def joined #salt
13:08 stoogenmeyer_ joined #salt
13:09 racooper joined #salt
13:11 gcfhvjbkn joined #salt
13:12 gcfhvjbkn http://pastie.org/private/dhdsedvjzp6fnt9ruidmtw
13:12 gcfhvjbkn how do i re-write this state with a name?
13:12 gcfhvjbkn http://pastie.org/private/ufclkxtuhgsgddtkooifua
13:13 gcfhvjbkn this doesnt work ("'path' is an invalid keyword argument for 'file.append'")
13:13 gcfhvjbkn what is the valid argument then?
13:13 gcfhvjbkn http://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.file.html#salt.modules.file.append
13:14 gcfhvjbkn the docs imply it should be "path"
13:14 AndreasLutro gcfhvjbkn: that's for the module, you're using a state
13:14 drawsmcgraw gcfhvjbkn: http://dpaste.com/09F5WKT
13:14 AndreasLutro gcfhvjbkn: `name: /path/to/file`
13:14 drawsmcgraw HOWEVER
13:15 drawsmcgraw There's a module for managing values in /etc/sysctl....
13:15 murrdoc joined #salt
13:15 drawsmcgraw gcfhvjbkn: here we are: http://docs.saltstack.com/en/latest/ref/states/all/salt.states.sysctl.html
13:15 drawsmcgraw Also what AndreasLutro said re: module vs state
13:16 gcfhvjbkn oh, thanks yall
13:16 leszq joined #salt
13:16 napsterX joined #salt
13:17 mapu joined #salt
13:24 evle2 joined #salt
13:28 icflournoy joined #salt
13:29 peters-tx joined #salt
13:30 fredvd joined #salt
13:31 clintberry1 joined #salt
13:33 lothiraldan joined #salt
13:34 cpowell joined #salt
13:36 julez joined #salt
13:36 quasiben joined #salt
13:37 Deevolution Anyone ever get a custom renderer working?  I'm having trouble getting even a simple one working at all.  See: https://github.com/saltstack/salt/issues/24830
13:38 quasiben joined #salt
13:40 mpanetta joined #salt
13:41 TranquilityBase joined #salt
13:42 impi joined #salt
13:43 leszq joined #salt
13:43 napsterX joined #salt
13:44 DammitJim joined #salt
13:51 soren joined #salt
13:54 murrdoc basepi:  Gareth https://github.com/saltstack/salt/pull/25069
13:54 inad922 joined #salt
13:55 dyasny joined #salt
13:55 patrek joined #salt
13:57 zircote joined #salt
14:01 otter768 joined #salt
14:03 aqua^c joined #salt
14:07 amcorreia joined #salt
14:09 64MAC8APW joined #salt
14:11 babilen Where would I find logs of schedule runs?
14:14 leszq joined #salt
14:14 murrdoc narnia
14:15 murrdoc there arent any logs of 'jobs fired by schedule'
14:15 murrdoc there are logs of 'work done in jobs'
14:15 vaspiros joined #salt
14:16 babilen Okay, where would I find those logs?
14:16 bbradley howdy
14:16 babilen moin
14:16 murrdoc minion.log
14:18 stoogenmeyer__ joined #salt
14:18 bbradley does salt have an issue with systemd loading or finding init scripts?
14:19 babilen murrdoc: I have just a bunch of empty lines in my minion log in this case
14:21 zmalone joined #salt
14:23 babilen Ah, "A scheduled run has no output on the minion unless the config is set to info level or higher" is mentioned on http://docs.saltstack.com/en/latest/topics/jobs/schedule.html
14:28 pdayton joined #salt
14:30 yomilk joined #salt
14:32 riftman joined #salt
14:35 IanV0rn2341 joined #salt
14:42 hasues joined #salt
14:43 hasues left #salt
14:43 sjwoodr joined #salt
14:43 sjwoodr Is there a limit to the number of cloud profiles you can have in a single *.conf file in /etc/salt/cloud.profiles.d/  ?
14:44 sjwoodr I'm having all sorts of odd issues with KeyError when I have too many profiles in a file or if too many profiles extend the same base profile.  :|
14:52 balltongu left #salt
14:54 jalbretsen joined #salt
14:59 perfectsine joined #salt
14:59 darknight87 joined #salt
14:59 fyb3r joined #salt
15:00 Brew joined #salt
15:00 murrdoc joined #salt
15:01 quique joined #salt
15:02 quique as part of a state for a minion i would like to run a script on the master.  is there a way to do that?
15:03 icflournoy joined #salt
15:03 leszq joined #salt
15:05 sdm24 joined #salt
15:05 linjan joined #salt
15:06 bmac2 joined #salt
15:07 shiin joined #salt
15:08 shiin I'm trying to create a custom execution module. It does not seem to get detected. I copied an existing module from salt/modules, restarted the master and ran saltutil.sync_all, but the custom command seems to be unavailable still. What am I missing?
15:09 ws2k3 joined #salt
15:11 murrdoc log on to a minion in one window
15:11 dfinn joined #salt
15:11 murrdoc from your master run salt 'minionname' custommodule.function
15:11 murrdoc then check /var/log/salt/minion
15:11 Laserwhit joined #salt
15:11 murrdoc you might see soem python errors
15:11 murrdoc *might*
15:11 theologian joined #salt
15:13 bja joined #salt
15:13 DammitJim how can I say to a state to just make sure that it has either the java7 or java8 package?
15:13 Laserwhit Hello all, I'm trying to use the file.recurse state and it doesn't seem to find the source even though it is clearly on my master.  I'm specifying the source as source: salt://regressions/usd/usd_test3 where this is the directory that has the files in it.  The error comes back as z
15:14 Laserwhit "None of the specified sources where found"
15:14 DammitJim if it doesn't have it, to ask to install it instead of silently installing it?
15:14 Laserwhit Any ideas?
15:15 bja DammitJim, do you have a reason for having java7 or java8?
15:15 murrdoc DammitJim:  its cant ask u
15:15 bja I'm guessing you have different versions of an os
15:16 Laserwhit I'm writing a work around to the file.recurse options so that I just tar up the files and untar them on the minion but I would prefer the file.recurse state for now.
15:16 bja I'd suggest putting a conditional via jinja based on grain information and then just using pkg.installed for the appropriate java for that os
15:16 fyb3r so my returner is getting an error stating "no such column as jid
15:16 DammitJim bja, just development requirements
15:16 DammitJim I guess I'll have to define different ones for different servers
15:16 fyb3r when both the DB and the jobs have the column....
15:16 mcolindres joined #salt
15:17 DammitJim murrdoc, how do I make it just fail instead of picking up dependencies?
15:17 DammitJim automatically installing java
15:17 ws2k3 joined #salt
15:17 murrdoc what os ?
15:17 shiin murrdoc: that's generally helpful, but does not seem to apply for my issue. It says the module is not available, so it cannot be found I believe.
15:17 DammitJim ubuntu
15:17 bja DamnitJim, it'd probably be possible to hack the backend to your os's pkg implementation and implement globbing
15:17 DammitJim no, no hacking
15:18 DammitJim I want this as streamlined as possible
15:18 murrdoc shiin:  no if python is failing in your module then the salt error is the same
15:18 shiin I don't know if I have to register it somewhere or if there is a difference in location or annotation based on whether its a state module or an execution module.
15:18 DammitJim but thanks for the recommendation bja
15:18 shiin I see
15:18 murrdoc DammitJim:  http://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.aptpkg.html#salt.modules.aptpkg.version
15:19 murrdoc {% if salt[pkg.version'] == one u dont want %} http://docs.saltstack.com/en/latest/ref/states/all/salt.states.test.html#salt.states.test.fail_without_changes {% endif %}
15:21 mcolindres hey guys, I was looking at the Salt cloud documentation. The sat.states.present mention cloud.tagged and cloud.untagged but I can't find them in the documentation. My question is how can I set up tags for my EC2 instance using the cloud.present state?
15:21 DammitJim murrdoc, thanks
15:21 DammitJim I'll look into it
15:22 giantlock joined #salt
15:23 icflournoy joined #salt
15:23 riftman joined #salt
15:25 sdm24 with that test module, will it always fail? returning the text "foo" as the std out?
15:25 IanV0rn2341 joined #salt
15:25 sdm24 Or will it return a failure if something happens to "foo"?
15:26 murrdoc you can use onchanges with it
15:26 murrdoc and u can specify anything u want as the text
15:26 murrdoc name/id
15:28 murrdoc sdm24:  http://docs.saltstack.com/en/latest/ref/states/all/salt.states.test.html#salt.states.test.mod_watch
15:28 sdm24 So one of the things I have salt do is check if the minion's hostname is in our DNS Server, and then check that the IP is the correct one. I would have {% if DNSIP is not defined %} test.fail_without_changes {% endif%}, and have everything else watch that?
15:28 sdm24 oh perfect
15:29 murrdoc there is an onfail requisite too
15:29 Laserwhit Of course I figured out that my file_roots specification was not matching my salt:// path.  All good now :-)
15:31 sdm24 Thanks murrdoc, I'll play around with this
15:32 murrdoc thats what she said
15:32 murrdoc sigh
15:33 sdm24 :O
15:33 murrdoc that was terrible
15:33 murrdoc i know
15:38 sdm24 found some errors with test, or at least in the docs
15:38 sdm24 http://docs.saltstack.com/en/latest/ref/states/all/salt.states.test.html#salt.states.test.mod_watch I can't get "comment" to work like the example
15:39 quique joined #salt
15:39 shiin murrdoc: I have put one simple function into salt.modules now, calling it foo with a def bar() that returns 'hello world'. What do I do for it to get detected? restart the master? run sync_all?
15:40 murrdoc run sync_all
15:41 sjwoodr I am stumped.  I have 42 cloud profiles defined... if i add one more in an existing *.conf file in /etc/cloud.profiles.d .... it blows up with KeyError: 'provider'
15:42 ange hi all
15:42 sjwoodr and its not a syntax error... i can add a 3 line profile and it blows up
15:42 ange I am using the s3 module to send and get files, is there an option on the get method or another method to check if a file is present in a bucket?
15:43 icflournoy joined #salt
15:47 writtenoff joined #salt
15:50 juanito joined #salt
15:51 aqua^c joined #salt
15:54 mcolindres hey guys, sorry to bother again. I think my question got lost between the lines. I need to know how can I set up tags for my EC2 instance using the cloud.present state? The documentation only talks about salt-cloud to do that but I want to set them in a SLS file using the state. Thank you!
15:56 eccentricson joined #salt
15:57 ange seems the get list the content of the bucket, now ... can I use that module from a python custom module ...
15:58 favadi joined #salt
15:58 eccentricson Good morning #salt!  I have a question regarding a salt master within a docker container.  The docker container is forwarding port 32772 -> 4505 and 32773 -> 4506.  I can register the minion to the master by utilizing the 32773 port, but if I execute a cmd from the master to the minion, the minion tries to respond back on 4505 instead of 32772.  Is there a configuration setting I can  specify so it responds back on 32772?
15:59 napsterX joined #salt
15:59 shiin murrdoc: It's weird. I deleted modules even and restarted the master, as well as salt/states things, but it still found those after restarting the master.
16:00 shiin Yet it couldn't find my custom foo.bar.
16:00 shiin I'm gonna try more tomorrow.
16:00 desposo joined #salt
16:01 geekatcmu Apropos of my pyobjects issues the other day: it turns out that when writing _states with __virtual__, you cannot break them up into distinct files, each with its own __virtual__ stuff, and still expect pyobjects to work.
16:01 geekatcmu So, learning has happened.
16:02 otter768 joined #salt
16:02 shiin I see.
16:03 quasiben joined #salt
16:04 debian112 joined #salt
16:07 kawa2014 joined #salt
16:09 tmclaugh[work] joined #salt
16:09 yomilk joined #salt
16:11 ange answered my own question
16:11 ange mostly reading and experimenting with
16:11 leszq joined #salt
16:13 VSpike Before I raise a duplicate issue, is anyone aware of an open issue relating to user.present state on Windows with group names containing spaces?
16:13 VSpike I know, I know...
16:14 VSpike I did some searching but found nothing
16:14 mcolindres yes, I'm aware of that vspike
16:14 mcolindres I came across the same issue
16:14 VSpike mcolindres: oh, is there an issue open, do you know?
16:14 mcolindres my solution was to rename the group right before adding the user to it and then rename the group back containing the spaces
16:15 VSpike yikes :)
16:15 mcolindres not sure a bout the issue submission
16:15 mcolindres I know it sucks to deal with windows idiosyncrasies
16:16 mcolindres I did it for the Remote Desktop Users group. Renamed that to RemoteDesktopUsers using a powershell script
16:17 ekristen joined #salt
16:17 Brew joined #salt
16:17 anotherZero joined #salt
16:20 quasiben joined #salt
16:20 pravka joined #salt
16:20 VSpike Would probably be easier just to call net localgroup explicitly in that case
16:21 VSpike Depends how many you need to do, I suppsoe
16:21 VSpike my users state for Windows is already so full of hacks and workarounds that I suppose one more won't hurt
16:21 VSpike The problem with them is that you rarely go back and take them out later when the bug gets fixed
16:23 permalac joined #salt
16:25 mcolindres Yes, I thought about the net localgroup command for it, but don't remember what was the issue I was facing trying to use that
16:28 pelzi_ does setting a password with a state work for anyone on windows?
16:28 VSpike pelzi_: That's another of my workarounds that I was looking at and wondering if it was needed
16:28 VSpike It didn't seem to work when I first tried it. In fact, salt tried to add the users with null passwords, so i had to make a reg change as well to allow empty passwords
16:29 VSpike Then I call module.run user.setpassword
16:29 pelzi_ yeah, the last I tried it creates users with no password (not empty)
16:29 pelzi_ and yes, setpassword works
16:30 murrdoc basepi:  https://github.com/saltstack/salt/pull/25069
16:30 impi joined #salt
16:30 mcolindres I'm using version 2015.5.2 and the windows password works fine. I had to use pillar for it though.
16:30 linjan joined #salt
16:30 patrek joined #salt
16:30 pelzi_ interestig
16:30 pelzi_ n
16:30 kawa2014 joined #salt
16:31 sdm24 Could one potential work-around for that have salt use cmd.script to run a powershell script, using jinja variables? Thats what I do to join new Windows VMs to Active Directory
16:31 mcolindres yes
16:31 mcolindres I did this before I upgraded salt
16:31 pelzi_ so something checks if the password is coming from pillar?
16:31 mcolindres module.run:
16:31 mcolindres - name: shadow.set_password
16:31 mcolindres - m_name: salt
16:31 mcolindres - password: {{ pillar['windowspwd']['salt_password'] }}
16:32 mcolindres that is actually a salt command being called in a state
16:32 basepi murrdoc: looks cool!
16:32 linjan joined #salt
16:33 VSpike mcolindres: when you say you use pillar ... can you clarify?
16:33 murrdoc basepi:  should be easy fix, i understand its a unique use case
16:33 basepi murrdoc: are you puneetk?
16:33 murrdoc yes
16:33 basepi Cool
16:33 basepi See my comment, but otherwise looks good
16:33 VSpike http://docs.saltstack.com/en/latest/ref/states/all/salt.states.user.html#salt.states.user.present says that the password field is not supported on Windows
16:33 murrdoc ok i can make that change, did u want a pull against 2015.2 too basepi
16:33 mcolindres this is my pillar file for that module.run   windowspwd:
16:33 mcolindres salt_password: 'salt'
16:34 perfectsine joined #salt
16:34 VSpike What about with 2015.5.2 though... you can do it just with user.present?
16:34 fyb3r would I use a returner to take all of the incoming data on the master and put it into a sqlite db?
16:35 basepi murrdoc: nah, just develop is probably fine. we're about to feature freeze 2015.8 so that's probably the best place for it.
16:35 mcolindres I tried with just user present and was getting an issue. Not sure if that was Win 2012 related, I never tried on 2008 server.
16:36 VSpike Ah, OK
16:36 mcolindres The module.run works fine for me for the time being. :)
16:37 fyb3r anyone?
16:38 lothiraldan joined #salt
16:39 ange in an orchestration sls is there a way to use a require to put a requisite on another state ?
16:42 whytewolf ange: https://gist.github.com/whytewolf/67ec9b4175cfb6570d2b this works for me in orch.
16:44 ange whytewolf: ok, do you know if I can use salt.module instead of salt.state ?
16:44 ange whytewolf: also : leap second related ?
16:44 whytewolf salt.module should work fine.
16:45 ange testing in a few minutes, thanks !
16:45 whytewolf ange nope. setup. I use highstate for maint. and orch for first time setup
16:45 ange ok
16:46 ange cool
16:46 whytewolf also this is a VERY small piece of increasing in size orch. for putting together an openstack setup
16:46 sdm24 Is there a way to NOT have salt run a highstate on a new minion when it connects? I don't have reactor set up, but it still does it
16:46 KyleG joined #salt
16:46 KyleG joined #salt
16:48 theologian joined #salt
16:49 djstorm joined #salt
16:49 cburtonnoaa Does the file.managed support Selinux?
16:50 cburtonnoaa I've been able to set system booleans, but I'd like to be able to set selinux context at file creation
16:50 ange sdm24: iirc for this to happen you either have the highstate option in your salt master config or in the options passed to the minion upon creation (I had similar issues recently with a double highstate; might not be related)
16:50 Viper233 joined #salt
16:53 sdm24 a quick search of /etc/salt/master and a new /etc/salt/minion didn't reveal anything. Those options are commented out
16:54 ange how is the minion created ?
16:55 jespada joined #salt
16:55 sdm24 manually from a template using VMware. The template has salt pre-installed with a setup state to change hostname, IP, etc, from the default template names. This state is run manually
16:56 shiin joined #salt
16:56 murrdoc basepi:  using redis as a master job cache has an interesting issue, it never clears the keys … and then there are issues with the redis instance running out of space
16:56 jondonas joined #salt
16:56 jespada hey guys any hint on how to reproduce those failing test on this PR: https://github.com/saltstack/salt/pull/24927, I did run the ./runtest --unit, but can't see it
16:56 murrdoc basepi:  leads to https://gist.github.com/anonymous/cd7aa36396628d51dc13
16:57 sdm24 the issue is that not everyone uses the state to configure the new VM, so I get a lot of pending keys using the default template name. I can only get grains from that minion if I accept the key, but then it runs the highstate on the minion, which includes a "network check" state that will make sure the hostname and IP are correct
16:57 jespada I run into the same issue, trying to help with that PR :)
16:57 basepi murrdoc: yeah unfortunately returners have no concept of "cleanup" so the endpoint for the returners must do that itself
16:57 basepi by "cleanup" i mean expiring old data
16:57 murrdoc well we could use setex instead of set
16:57 murrdoc for redis at least
16:57 jondonas Wondering if anyone can help as I am new to salt. when making a droplet through digitalocean with salt-cloud --profile, it outputs "Permission denied (publickey,password)" and "Failed to start Salt" and creates the droplet without initializing salt
16:57 basepi I don't know redis, but that seems like a reasonable solution
16:58 murrdoc cos u can then expire the key in redis by the configured cache __opt__ in the master conf
16:59 murrdoc can i over ride a function in a returner if i name the file teh same in my _returners directory or do i need to copy the whole file over and change one functin
16:59 murrdoc function*
17:03 basepi murrdoc: I think you have to copy the entire file
17:03 murrdoc k thanks
17:04 pcdummy joined #salt
17:04 pcdummy joined #salt
17:04 forrest joined #salt
17:06 fyb3r Still trying to find out if replacing the master job cache with a returner is the proper way to store the returning data into a database....
17:07 murrdoc it works better for me
17:07 murrdoc i have a vm as my master, and 300+ minions
17:07 murrdoc doeesnt work without a redis cache for the job cache
17:07 keimlink joined #salt
17:07 dopesong joined #salt
17:07 fyb3r that @ me?
17:08 murrdoc yup
17:09 fyb3r would be nice is that was added somewhere in the doc :P
17:09 fyb3r literally spent the last 2 days trying to figure out why none of the code, including the returners included with the stack, wont work properly
17:10 bash124512 joined #salt
17:10 geekatcmu Does anyone know if #7697 is even being looked at?
17:10 geekatcmu It's coming up on 2 years, and it's kind of a "if you have more than one master, mines are unusable" thing.
17:10 forrest joined #salt
17:14 ange salt.module unavailable
17:14 ange :/
17:14 favadi joined #salt
17:15 icflournoy joined #salt
17:17 whytewolf ange: gist what you tried
17:18 shiin I've put together a nopaste with my issue now. I'm trying to get a simple execution module to work. http://nopaste.linux-dev.org/?585899
17:19 MatthewsFace joined #salt
17:20 whytewolf shiin: shouldn't that be in _modules
17:21 pcdummy joined #salt
17:21 pcdummy joined #salt
17:21 shiin whytewolf: Probably, but is that also the way for developing them? I mean I might want to refer to resources from the salt project itself, use modules and helpers, and write a test.
17:22 jondonas Sorry to interupt, but is anyone able to help me with an issue?
17:23 geekatcmu no
17:23 clintberry1 joined #salt
17:24 ange whytewolf: https://gist.github.com/mcansky/170665908a086ed3a2c7
17:24 whytewolf shiin: depends. if you are developing code then you should build it in salt/modules . but you will want the same version [with your changes] everywhere. other wise if you are just building states,modules put them in the dynamic loader
17:24 geekatcmu Does anyone have some elisp to handle pyobjects+jinja mode in emacs?
17:25 shiin where is the dynamic loader?
17:25 ange file might just be missing
17:25 blakev joined #salt
17:25 whytewolf shiin: thats what the _ directories are. for allowing you to push the dynamic modules/states around
17:26 whytewolf thats what the sync commands work with
17:26 whytewolf actually just for kicks i tossed your example in _modules and it worked 100% fine
17:26 yomilk joined #salt
17:27 darknight87 joined #salt
17:27 shiin Right. I was about to confirm that but now my minion is pouting.
17:27 whytewolf sad minion is sad
17:27 ange whytewolf: no dice, added the error in the gist
17:27 shiin But then how does it work with the salt/modules and salt/states directory?
17:28 whytewolf shiin: are you sure it touches them at all?
17:29 shiin now foo.bar works for me with the _modules directory.
17:29 whytewolf ange: what gist?
17:29 ange https://gist.github.com/mcansky/170665908a086ed3a2c7
17:30 whytewolf ange: ahh one second
17:30 dopesong joined #salt
17:31 whytewolf ange: https://gist.github.com/whytewolf/67ec9b4175cfb6570d2b
17:31 whytewolf ange: the second file there is what you want for modules
17:31 shiin whytewolf: not yet. but I might be interested in creating additional modules and sending pull requests.
17:32 ange salt.function + name ?
17:32 whytewolf shiin: then you will want to do a full develop version with git. and bootstrap that everywhere
17:32 whytewolf ange: yeap
17:33 shiin whytewolf: that's what I'm doing, I've got everything set up, the master is running out of the checkout.
17:33 Brew joined #salt
17:33 whytewolf shiin: when i say everywhere i mean minions as well
17:33 shiin I see!
17:35 shiin So the master running out of the develop clone won't synchronize those modules to the minions.
17:35 whytewolf no
17:37 dyasny joined #salt
17:37 shiin It all makes sense now.
17:37 shiin Thank you.
17:38 stoogenmeyer__ joined #salt
17:39 DammitJim is there a simple tutorial to create a state that downloads a file, unpacks it into a certain directory, and updates a file with the new PATH
17:40 aqua^c joined #salt
17:40 whytewolf jondonas: what was your issue?
17:40 shiin DammitJim: I tend to do that with cmd.run wget -O /some/path , unless file /some/path
17:41 DammitJim someone posted a couple of days ago a way to wget and un-archive something
17:41 pcdummy joined #salt
17:41 pcdummy joined #salt
17:41 jondonas whytewolf: when making a droplet through digitalocean with salt-cloud --profile, it outputs "Permission denied (publickey,password)" and "Failed to start Salt" and creates the droplet without initializing salt. Any thoughts?
17:41 gcfhvjbkn joined #salt
17:41 DammitJim oh yeah! archive.extracted!
17:42 shiin DammitJim: Similarly. cmd.run tar xzf -C /extracted/dir unless: file /extracted/dir and require: cmd: thedownload
17:43 ikarus joined #salt
17:44 shiin and next up I modify files inside the extracted directory, with a require on cmd: theuntar. Sometimes that makes me wonder if it'd be considered an anti pattern.
17:45 whytewolf jondonas: sorry never used digitalocean
17:46 jondonas whytewolf: thanks anyways
17:46 leszq joined #salt
17:48 DammitJim do I need a special package in Ubuntu 14.04.2 to be able to use archive.extracted?
17:48 DammitJim on the salt-minion?
17:49 whytewolf at least 2014.1
17:49 DammitJim weird... I'm getting State archive.extracted found in sls ant.ant182 is unavailable
17:50 ponpanderer joined #salt
17:50 ponpanderer hello
17:51 cachedout joined #salt
17:51 ponpanderer Question on the cmd.script module. I've noticed temp files being left behind of rendered scripts on the minions (Windows in particular). Is that normal behavior or should these be pruned after execution?
17:51 whytewolf DammitJim: https://docs.saltstack.com/en/latest/ref/states/all/salt.states.archive.html
17:51 impi joined #salt
17:53 UtahDave joined #salt
17:54 ponpanderer Actually...nevermind answered my own question poking in the code. Indeed scripts are meant to be cleaned
17:54 DammitJim salt minion 0.17.5
17:54 whytewolf DammitJim: ...
17:55 DammitJim meaning... how do I know what version I'm running?
17:55 DammitJim if it needs to be at least 2014.1
17:55 whytewolf 0.17.5 = you install salt from the ubuntu repo. instead of adding the salt ppa repo
17:55 DammitJim yeah, I've been doing it from the ubuntu repo
17:56 whytewolf the ubuntu repo is WAY behind
17:56 DammitJim are you serious?
17:56 DammitJim ok, then I'll go with run
17:56 DammitJim thanks
17:57 JDiPierro joined #salt
17:59 terratoma left #salt
17:59 Laserwhit So I seem to be able to get commands to run more easily using states.cmd as apposed to modules.cmdmod because of the easy use of user and group for priviledges.  The question is why doesn't modules.cmdmod have user and group options?  Also is 'runas' in cmdmod the same as user in states.cmd?  I'm probably missing an important nuances here.
17:59 baweaver joined #salt
18:00 Laserwhit s/nuance/nuances/ in my last comment
18:02 vaspiros joined #salt
18:02 otter768 joined #salt
18:03 ajw0100 joined #salt
18:08 vaspiros joined #salt
18:09 fyb3r left #salt
18:19 IanV0rn2341 joined #salt
18:19 jonlangemak joined #salt
18:24 DammitJim will this check if the apache-ant-1.8.2 directory exists? {% if not salt['file.directory_exists' ]('/usr/local/apache-ant-1.8.2.bin') %}
18:24 pravka joined #salt
18:25 dhscholb joined #salt
18:26 aron_kexp joined #salt
18:27 yomilk joined #salt
18:27 napsterX joined #salt
18:32 aea joined #salt
18:33 _JZ_ joined #salt
18:33 baweaver joined #salt
18:36 DammitJim is there a preference between copying a tar.gz file from repo and then decompressing it to a directory vs copying the directory directly to the location on the minion?
18:37 babilen https://docs.saltstack.com/en/latest/ref/states/all/salt.states.archive.html ?
18:37 babilen (if that is what you actually want)
18:37 DammitJim babilen, I don't know why I get stuck in these little problems
18:38 DammitJim I'm asking the above question because what I am doing now is copying a tar.gz file to the minion, uncompressing it to the proper directory
18:38 DammitJim but now I want to delete the tar.gz that I copied over
18:38 DammitJim any suggestions on best recourse?
18:38 theologian joined #salt
18:39 quique joined #salt
18:40 babilen Why don't you simply place the archive in salt:// (or reference a different URI) and use archive.extracted for extracting it? I guess that you really don't care about "copy foo to bar, extract it delete foo", but that you care about "foo has been extracted to /path/to/bar"
18:40 DammitJim babilen, I would use archive.extracted but my version of salt is older
18:40 DammitJim and I'm in no position at this time to upgrade it :(
18:40 babilen How come?
18:41 babilen (and it might not be too hard to copy the module and state to _modules/_states)
18:41 babilen It's quite easy to "backport" newer modules and states like that and you aren't really "stuck" on one particular version that way.
18:42 icflournoy joined #salt
18:42 DammitJim you know how it is... one is working on something and now I have to have something else to get this done
18:42 DammitJim vs... I just write the code (for testing purposes) to check if a folder exists and delete the tar.gz
18:43 DammitJim I was looking at using file.absent
18:43 DammitJim but my test to see if the directory exists doesn't seem to be executing
18:43 babilen sure, but don't make it harder than it is. If you *really* care about extracting something somewhere then *do that*. There are modules and states for that and if they are not in the salt version you use then simply copy the module/state from develop (or another branch) into _modules and _states respectively.
18:44 DammitJim thanks man!
18:45 babilen You are looking for salt/{modules,states}/archive.py in https://github.com/saltstack/salt/
18:47 babilen There is the possibility that they don't work, but it is at least worth a try and you have nothing to lose :)
18:48 shiin DammitJim: does unless: file <somefile> seem unsuitable to you?
18:50 Brew1 joined #salt
18:50 Brew1 joined #salt
18:51 nlb joined #salt
18:51 DammitJim shiin, I am checking that the directory got created before I delete the file
18:51 Brew joined #salt
18:51 DammitJim I think file.absent would make sense to delete the tar.gz
18:51 DammitJim but I am trying to figure out the test of the directory existance
18:51 DammitJim I think I figured it out, though
18:52 shiin delete what? Why remove the unpacked tar?
18:52 DammitJim no, remove the tar.gz
18:52 DammitJim the original file
18:52 shiin right, I just keep them
18:52 shiin never have to download again if you rm -rf the unpacked directory
18:52 DammitJim you see? that's why I said... I don't know why I get myself in these situations
18:53 DammitJim there is no real reason why I need to delete it but because of my craziness
18:53 shiin alright, well, you're welcome to delete it
18:53 shiin but I suggest to just keep it.
18:53 babilen (or let the state handle all that for you)
18:54 sinonick joined #salt
18:54 DammitJim babilen, I have no doubt that I'll mess with archive.extract sooner than later
18:54 DammitJim just not now
18:54 DammitJim but thank you both!
18:54 DammitJim this channel is probably the best channel to ask questions because there are true answers and suggestions
18:55 babilen Why not now? It would literally take you about a minute.
18:56 denys joined #salt
18:57 drawsmcgraw joined #salt
18:59 andrew_v joined #salt
18:59 mikezuff left #salt
19:02 bezeee joined #salt
19:02 DammitJim babilen, even if I was doing that, then I'd have to update all my minions to the same version for uniformity, ya know?
19:02 pravka joined #salt
19:04 babilen No, you wouldn't. You'd just copy it into _states and _modules *in your salt state directory* and they'll be synched before a highstate (or when you use saltutil.sync_all)
19:04 babilen Well, I guess you would, but that happens automagically
19:05 DammitJim :D
19:05 mindlace joined #salt
19:06 DammitJim let me get this logic straight
19:06 DammitJim I want to install version 7 of java on a particular server, but I want version 8 on another server
19:07 DammitJim how would I go about doing that? Just create 2 separate sls files?
19:07 keimlink joined #salt
19:07 Ahlee I would indicate which server was special via pillar targeting, and have the version fed from pillars
19:07 babilen That would be one way, yeah. If the installation is sufficiently similar then you could fill in the differences from a pillar.
19:08 DammitJim ok, so pillar driven
19:08 DammitJim got it
19:08 dfinn can I push a script out to my minions from the master and then run that script?
19:09 babilen dfinn: http://docs.saltstack.com/en/latest/ref/states/all/salt.states.cmd.html#salt.states.cmd.script
19:09 dfinn just found salt-cp, looks like that will do it
19:09 babilen If you want to run a script then run a script :)
19:10 Ahlee cmd.script can run the script directly from the salt's file server
19:10 Ahlee (aka, copies to local cache and runs from there)
19:11 babilen So no weird imperative thinking there :)
19:14 DammitJim in this case when using pillars, I need to define each server in there, right?
19:14 DammitJim can I do that by server name?
19:14 shiin You could use a '*': so all servers would know about all pillar states.
19:15 DammitJim shiin, is that like the "bus" that informs other minions about other minions?
19:15 shiin But I think a security concern with that is that all those files become synchronized with the minions, so in that case all passwords and certificate information from pillars would also be on all minions.
19:16 drawsmcgraw DammitJim: I had a question just about identical to yours
19:17 drawsmcgraw Here's the conversation around that one: http://www.reddit.com/r/saltstack/comments/31pdv5/pillar_is_in_git_but_how_do_you_manage_local/
19:17 shiin I'm not sure I get the question.
19:17 babilen I simply use multiple pillar repositories (that are combined on the master)
19:18 drawsmcgraw DammitJim: Pillar is not exactly the event bus that minions use to know about each other
19:18 DammitJim oh, thanks for clarifying that
19:18 drawsmcgraw You may be thinking about "the event bus" (i.e. ZeroMQ in most cases)
19:18 babilen drawsmcgraw: I mean you need *something* to target different data by. If you have that then, well, you are golden.
19:18 drawsmcgraw Or the salt-mine (contains data about minions and lives on the master)
19:19 drawsmcgraw babilen: Yeah I became a fan of 'overrides' (in various implementations) after that discussion
19:19 shiin Pillars, I believe, are where the template can be separated from the content.
19:19 babilen drawsmcgraw: I would advise against it as it becomes quite unclear where the "final" data actually comes from
19:19 drawsmcgraw shiin: yes. Someone said in here the other day "Pillar is what allows you to make states generic"
19:19 shiin Like in html and css.
19:20 drawsmcgraw babilen: good point. It can get away from you quickly
19:20 drawsmcgraw hah. Oh man, point made :)
19:20 shiin States might refer to references of distinct information, like user names and passwords. You could share all your states with everyone in the company
19:20 shiin but nobody would know *your* passwords in those states.
19:20 shiin (assuming of course the pillar is not in the same repository)
19:21 DammitJim man, how bad is it if I define a pillar that checks the server name and if the server name is x, I define java as java7, but if it is y, then java is java8?
19:21 Brew joined #salt
19:21 shiin if grains['nodename'] == 'x'
19:21 Brew joined #salt
19:21 pipeep joined #salt
19:21 shiin - java7
19:22 mindlace joined #salt
19:22 DammitJim is that normal?
19:22 drawsmcgraw DammitJim: I'd call that normal, yes (pending shiin's concurrance)
19:23 shiin That's just my brief evaluation of how I'd solve it. There are probably about 4 or 5 different ways.
19:23 DammitJim ok, cool
19:26 babilen drawsmcgraw: It's okay for one level (and always leave comments and whatnot), but simply don't make it too complicated/layered. It'll be hard to figure out some things in six months anyway, don't make it too mysterious
19:27 babilen I'd rather have some duplication in structure if that makes it 100% clear where data is coming from. Bytes are cheap, your sanity isn't
19:27 Laserwhit I am able to get commands to run more easily using states.cmd as apposed to modules.cmdmod because of the easy use of user and group for priviledges.  The question is why doesn't modules.cmdmod have user and group options?  Also is 'runas' in cmdmod the same as user in states.cmd?  I'm probably missing an important nuances here.
19:27 drawsmcgraw babilen: noted. I'll revisit how I do it and make sure it's not too mysterious
19:28 babilen Laserwhit: runas/user is being used to define the user that the command will be executed as
19:29 aqua^c joined #salt
19:30 napsterX joined #salt
19:31 blakev joined #salt
19:31 DammitJim should I use id for the server name?
19:32 mindlace joined #salt
19:32 shiin I like to do that.
19:33 DammitJim is there an easy way to group the servers?
19:33 DammitJim this might be too much work
19:33 DammitJim too many server names to check
19:33 blakev_ joined #salt
19:33 edrocks joined #salt
19:34 shiin There is. You can define groups or select them using regex, or wildcards, or you could select them by grain. There may be more methods I'm not aware of at this point.
19:34 shiin How long have you been working with salt?
19:35 mindlace joined #salt
19:35 DammitJim like 3 weeks?
19:35 * shiin nods
19:35 DammitJim but I've been reading a lot
19:35 juanito joined #salt
19:36 DammitJim it's funny how until one actually executes something, it doesn't sink in as well what you read
19:36 DammitJim does one define the groups in another pillar?
19:36 shiin Aye, I'm a very practical learner too.
19:37 spark_ joined #salt
19:37 shiin http://docs.saltstack.com/en/latest/topics/targeting/nodegroups.html
19:37 ajw0100 joined #salt
19:37 DammitJim shiin, I was just reading that
19:37 shiin that's in the master config
19:37 DammitJim kinda scary when one needs to define that in /etc/salt/master, though
19:37 DammitJim it seems rather "official"
19:37 shiin you could put it in /etc/salt/master.d/my-extra-config.conf
19:38 shiin but I don't do that either
19:38 shiin I group nodes by partial matches of their name, or just apply the same state to multiple nodes.
19:38 babilen DammitJim: You can target in your top.sls too: http://docs.saltstack.com/en/develop/topics/targeting/index.html
19:39 babilen 'foo-bar-*' is a *very* basic grouping of minions whose id is, for example, foo-bar-web, foo-bar-db, ...
19:41 mindlace joined #salt
19:45 aasdfggasdgeqehe joined #salt
19:46 MTecknology SSC is dying!!!
19:46 mindlace joined #salt
19:46 shiin What is SSC?
19:47 MTecknology ssc.saltstack.com
19:47 Laserwhit babilen: Thanks for the information (sorry, had to step away earlier)  why is the parameter 'runas' instead of 'user'?  Any ideas?  Just having a hard time getting things to work in the cmdmod when they work perfectly in the states.cmd context.  Thanks again.
19:49 Laserwhit babilen:  I have things working for me now in the states.cmd context and I'm not blocked or anything, just trying to understand the system better.  I probably just missed something small in the implementation.  If I decide to debug it more closely I'll send some examples.  I can send examples of the difference anyway if anyone is interested.
19:50 shiin I see.
19:52 babilen Laserwhit: I don't know why the parameter is 'runas', but it is a pretty obvious name for that parameter, isn't it?
19:52 babilen What is the state you want to execute manually?
19:52 babilen bbl
19:56 baweaver joined #salt
20:01 quasiben joined #salt
20:02 Laserwhit babilen:  Sure, it just wasn't working for me and this was a confusing (but indeed obvious) difference.  I'll run it again and if it still isn't working for me I can post the errors.
20:03 otter768 joined #salt
20:04 jonlangemak left #salt
20:13 giantlock joined #salt
20:16 yomilk joined #salt
20:20 markm joined #salt
20:21 icflournoy joined #salt
20:21 linjan joined #salt
20:22 tkharju joined #salt
20:24 lempa joined #salt
20:24 juanito__ joined #salt
20:26 baweaver joined #salt
20:29 DammitJim how does one do an if statement with "or"?
20:31 napsterX joined #salt
20:31 sdm24 {% if ... %} conditions 1{% elif .... %} conditions 1 {% else %} conditions 2  {% endif %}?
20:32 DammitJim I would like to do an {%if ... || if ... || if ... %} conditions 1 {% endif %}
20:32 DammitJim or
20:32 sdm24 although I guess that would run twice for some, if a minion meets both if and elif
20:33 druonysus joined #salt
20:35 druonysus joined #salt
20:35 druonysus joined #salt
20:36 DammitJim sdm24, do you get what I'm trying to do?
20:38 ajw0100 joined #salt
20:40 sdm24 I think so, its not something I've ever done http://stackoverflow.com/questions/15168831/how-to-write-a-multiline-jinja-statement makes it look like it should be simple
20:40 wabkia joined #salt
20:40 mindlace joined #salt
20:41 DammitJim I'm only doing this when defining the pkgs pillar
20:42 Ph-x joined #salt
20:42 sdm24 {% if (grains['id'].startswith('salt') or grains['os'] == 'Windows') %}
20:42 sdm24 that works for me
20:42 sdm24 as an example I just kicked up
20:42 shiin left #salt
20:42 armguy joined #salt
20:44 penguin_dan joined #salt
20:45 JDiPierro joined #salt
20:47 DammitJim yeah, I set it up like that
20:49 sdm24 you don't even need the parentheses
20:49 DammitJim I don't? it looks prettier
20:49 sdm24 yeah I like them too, but they aren't required
20:50 mcolindres Hey guys, I have a question regarding cloud.present state. Will the following work to set tags in my instance?
20:50 mcolindres aw-instance-{{ ENV_NAME }}:
20:50 mcolindres cloud.present:
20:50 mcolindres - name: 'aw-instance-{{ ENV_NAME }}'
20:50 mcolindres - cloud_provider: aws-ec2
20:50 mcolindres - subnetid: subnet-14785236
20:50 mcolindres - securitygroupid:
20:50 mcolindres - sg-12345678
20:50 mcolindres - sg-87654321
20:50 mcolindres - image: ami-c7d092f7
20:50 mcolindres - size: 't2.small'
20:50 mcolindres - ssh_username: centos
20:50 mcolindres - location: us-west-2
20:50 mcolindres - delvol_on_destroy: True
20:50 mcolindres - tag:
20:50 mcolindres 'Environment': 'Test'
20:50 mcolindres 'Customer': 'My Customer'
20:50 llua heh
20:50 mcolindres I'm not able to find anything about tags on cloud.present in the documentation
20:51 sdm24 please use  https://gist.github.com for code
20:51 mcolindres ok, I apologize for that
20:53 KyleG Has anyone ever ran into an issue where your minion will complain about KeyError: 'os' after a restart and a restart of the salt minion corrects the problem? EX: https://gist.github.com/kylegato/dce7e819a5e0e9f77780
20:54 murrdoc you are using grains['os'] somewhere
20:54 murrdoc yes
20:54 KyleG Why would restarting my minion fix it
20:54 KyleG Makes no sense to me, I just rebooted this box, ran into that error, restarted the minion, and it's fine
20:54 tmclaugh[work] joined #salt
20:55 KyleG Probably fixed already, I'm still on 2014.1.13
20:55 s_kunk joined #salt
20:57 DammitJim how do I clean up a pillar?
20:57 DammitJim I removed it from my init.sls
20:57 sdm24 remove it from /srv/pillar/top.sls
20:58 DammitJim I did
20:58 DammitJim that's strange
20:58 sdm24 and do "salt '*' saltutil.refresh_pillar"
20:58 sdm24 cause it will stay cached until its refreshed, which happens every 60 minutes, I believe
20:58 DammitJim great
20:58 DammitJim thanks
20:59 sdm24 no problem, I remember when that confused the hell out of me too haha
20:59 DammitJim oh gosh, I hope this thing isn't messing up my server
20:59 DammitJim :D
20:59 KyleG That's what backups are for
21:00 sdm24 http://docs.saltstack.com/en/latest/ref/states/backup_mode.html
21:00 DammitJim snapshots ;)
21:00 sdm24 I didn't start using backups until it was too late
21:00 KyleG Plus I highly recommend keeping your salt states and configs in a git repo, works wonders for us and allows us to have clear reasons why something was put where it is
21:00 DammitJim so, is there a way to query the version of java I installed on the minion?
21:00 wabkia test=true :D
21:00 KyleG we even link the commits to JIRA issues with our Stash+JIRA integration
21:01 DammitJim is salt supposed to be super fast?
21:01 sdm24 http://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.aptpkg.html#salt.modules.aptpkg.version
21:01 quasiben If I update the master configuration file is there anyway to reload salt-master without a full restart?
21:01 DammitJim it takes a while do perform just a check if a package is installed :(
21:02 sdm24 ah
21:02 sdm24 anyways I'm out for the day, good luck
21:02 DammitJim thanks
21:02 DammitJim see ya
21:02 KyleG it's not super fast with packages I've noticed, but especially not PIP packages
21:02 UtahDave DammitJim: It just takes as long as your package manager takes, roughly
21:02 DammitJim but the package is already installed
21:03 DammitJim I have to run
21:03 DammitJim thanks guys!
21:05 baweaver joined #salt
21:06 dfinn joined #salt
21:10 pravka joined #salt
21:15 cmek is there any way to return to console and also log data at the same time?
21:16 pravka joined #salt
21:16 cmek so i guess my quesion is - can I chain returners? or do I have to write one to do both?
21:18 whytewolf cmek: a smart ass answer salt '*' state.highstate 2>&1 | tee myfile
21:18 aqua^c joined #salt
21:18 zer0def joined #salt
21:18 cmek whytewolf: yeah I know I can do that.. the question is how to do it so everything is logged (and printed to console) by default..
21:19 gnord joined #salt
21:19 cmek so I simply run "salt '*' state.highstate" and the output gets printed _and_ logged
21:21 whytewolf I would say your best option is writing a returner that does both. as i do not think you can chain returners
21:24 jhauser joined #salt
21:29 alexhayes I'm using a dynamic module/state so I can utilize the bower.bootstrap state that is in develop. The problem I seem to be having on state.highstate is that, while the module is sync'd down to the minion it's not loaded until the second time I run state.highstate.
21:29 alexhayes I'm using salt-call on the minion itself.
21:30 UtahDave cmek: I'm not sure exactly what you mean.  Salt will print to the console and log everything by default
21:31 alexhayes While I don't understand the internals of salt, I think from a python point of view this makes sense. On the first invocation of salt-call the module doesn't exist, so it's not loaded by python, on the second it does, so it's loaded
21:31 alexhayes however... this behavior is not really desired
21:31 UtahDave alexhayes: I think there's a refresh_modules=True option you can use
21:31 napsterX joined #salt
21:32 mindlace joined #salt
21:32 dkrae joined #salt
21:32 otter768 joined #salt
21:32 UtahDave alexhayes: can you run  salt \* saltutil.refresh_modules     before the highstate?
21:37 forrest joined #salt
21:43 Ryan_Lane weirdly when I install salt via git (using pip -e) it gives me back an egg with 2014.1 in the version
21:43 Ryan_Lane it's pretty annoying because all of my systems report an incredibly old version of salt because of it
21:44 druonysus joined #salt
21:44 druonysus joined #salt
21:47 yomilk joined #salt
21:47 UtahDave Ryan_Lane: what version are you trying to install?
21:48 Ryan_Lane I'm installing from a branch in a fork
21:48 Ryan_Lane 2015.5
21:49 UtahDave Hm. I've been doing that today. Does the output of   salt --version match the egg version?
21:50 leszq joined #salt
21:50 Ryan_Lane salt-call 2014.1.0-6423-g47188b6 (Hydrogen)
21:51 Ryan_Lane it's definitely 2015.5
21:52 Ryan_Lane especially since that hash is from Jun 25th :)
21:52 UtahDave Hm.  I just checkout the very latest of the 2015.5 branch and salt --version is giving me    salt 2015.5.2-155-g4635079 (Lithium)
21:52 Ryan_Lane sure
21:52 Ryan_Lane so...
21:53 Ryan_Lane wipe your venv
21:53 Ryan_Lane install salt 2014.1
21:53 Ryan_Lane then pip upgrade to 2015.5 using git
21:53 Ryan_Lane I bet your version will show 2014.1
21:53 UtahDave Ah.  what's the exact command you're using?
21:53 ndrei joined #salt
21:53 Ryan_Lane pip install -r requirements.txt
21:54 Ryan_Lane one sec.
21:54 Ryan_Lane where requirements.txt has: "-e git+https://github.com/lyft/salt@stable-2015.5#egg=salt"
21:55 Ryan_Lane I'm guessing the salt.egg-info directory isn't being updated
21:57 murrdoc yes
21:58 j_t left #salt
21:58 Ryan_Lane any idea as to make that happen? :)
21:59 Ryan_Lane even if I wipe out that directory it re-generated it with the incorrect egg
21:59 murrdoc i just said to make sure
21:59 murrdoc u werent talking to yourself
21:59 murrdoc :)
21:59 Ryan_Lane :)
21:59 murrdoc but i think u can drop a version file in somewhere
22:00 forrest Did you make sure to get the latest version of pip Ryan_Lane?
22:00 forrest sometimes not having the latest release can screw you for egg files.
22:01 murrdoc or setuptools or distribute or whatever new way they are doing it now
22:01 Ryan_Lane Successfully installed salt-2014.1.0-6423-g47188b6
22:01 Ryan_Lane -_-
22:01 Ryan_Lane that's after upgrading pip
22:01 murrdoc gawd pip is getting ruby annoying
22:01 UtahDave Ryan_Lane: I think our setup.py creates a _version.py that let's salt know what version it is.
22:01 Ryan_Lane seems so, but it must be busted
22:01 UtahDave it doesn't look like that is being run.
22:01 murrdoc yeah thats the file i was thinking of
22:02 UtahDave let me check with pedro about that.
22:03 forrest Who is this UtahDave guy? I haven't seen him in here before... ;)
22:03 ALLmightySPIFF joined #salt
22:04 edrocks joined #salt
22:04 UtahDave lol, Ha!  how's it going, forrest?
22:04 forrest Good, you?
22:05 UtahDave Yeah, doing well!
22:07 forrest Nice, are you walking/biking to work now that you're so close and it isn't frozen over?
22:09 UtahDave gah, I should be, but it's so freaking hot in the afternoons now.
22:10 UtahDave I don't live in the Emerald City!
22:10 ALLmightySPIFF joined #salt
22:11 FRANK_I joined #salt
22:12 UtahDave Ryan_Lane: I'm pretty sure Pedro is the one who has done most of the work on the version.py stuff, but he's not around right now.  His timezone is 8 hours ahead of Pacific
22:13 blakev joined #salt
22:13 * Ryan_Lane nods
22:13 Ryan_Lane ok. I can open a bug
22:14 murrdoc is that india ?
22:14 vieira_ joined #salt
22:14 UtahDave Ryan_Lane: that would be awesome.
22:14 UtahDave Portugal
22:16 UtahDave Ryan_Lane: he just responded. He's at a late dinner. I'll assign the bug to him and he said he'd look at it first thing in the morning.
22:16 alexhayes UtahDave: I was hoping to have vagrant run highstate, so while I think that would work, probably not in my situation
22:17 alexhayes UtahDave: I decided to just do the bower bootstrapping myself with a cmd.run and stop trying to fight the good fight :P
22:19 nahamu joined #salt
22:20 matthew-parlette joined #salt
22:20 leev joined #salt
22:23 Hazelesque_ joined #salt
22:25 hacfi joined #salt
22:27 leszq joined #salt
22:29 lahwran joined #salt
22:29 Ahlee there. custom _module in place across all systems
22:29 Ahlee salt -G kernel:Linux ntp_monitor.check_ntp_offset
22:30 Ahlee Salt has really made this leap second seem like a non-issue.
22:32 napsterX joined #salt
22:36 UtahDave :)
22:45 murrdoc there is now way to run a reactor state right
22:46 murrdoc like state.highstate
22:46 murrdoc there isnt a state.reactor
22:47 UtahDave local.state.highstate
22:47 UtahDave search for highstate on this page for an example: https://docs.saltstack.com/en/develop/topics/reactor/index.html
22:47 murrdoc sorry, i know how to call the states state module in a reactor state
22:47 murrdoc i am trying to figure out if there is a way to call a reactor from a master for a minion
22:47 murrdoc is it just event.send ?
22:48 UtahDave oh, I see.  Yeah, you can use event.send to send an event that will match something your reactor is listening for
22:48 murrdoc will that show the output similar to a state run ?
22:48 murrdoc or just the local: \n \t True
22:50 UtahDave event.send will only show the output of the event.send operation.  namely, that an event was successfully sent on the event bus
22:50 Ryan_Lane UtahDave: cool. thanks :)
22:52 murrdoc UtahDave:  ah and i guess should setup a returner to put that data into syslog
22:52 Ryan_Lane UtahDave: https://github.com/saltstack/salt/issues/25094
22:53 UtahDave murrdoc: sure.
22:55 UtahDave I've assigned it to Pedro. He'll dig into it first thing in the morning. Thanks, Ryan_Lane!
22:55 murrdoc thats le painful
22:55 JDiPierro joined #salt
22:56 otter768 joined #salt
22:56 murrdoc does highstate have a way to sync modules and pillars before running states
22:58 UtahDave murrdoc: the event.send will show up in the job cache, if that's easier for you
22:58 UtahDave murrdoc: a highstate refreshes pillar data automatically, I'm not sure about modules.
22:58 baweaver joined #salt
22:58 murrdoc it doesnt do modules
22:59 murrdoc need to figure out a job cache viewer
22:59 murrdoc … thanks for listening UtahDave
22:59 julez joined #salt
22:59 UtahDave murrdoc: you're very welcome.
22:59 murrdoc oh who is the new saltstack training guy
23:00 murrdoc supposedly they are headed to train at the <workplace> sometime next month
23:00 murrdoc wrote the new training book and so on
23:01 Singularo joined #salt
23:02 yomilk joined #salt
23:04 mindlace joined #salt
23:04 UtahDave murrdoc: Raine is the new training guy. He's been doing a great job.
23:05 murrdoc sweet, i will have questions!
23:05 Ahlee murrdoc: yeah, sync'd modules aren't available during the current run
23:06 Ahlee murrdoc: we trigger items twice, we run saltutil.sync_all, then our states
23:06 murrdoc i mean u can run it all in one reactor state just fine
23:06 aqua^c joined #salt
23:11 pdayton joined #salt
23:12 andygabby joined #salt
23:12 Gareth UtahDave: you in the office today?
23:13 yomilk joined #salt
23:18 mosen joined #salt
23:20 mindlace joined #salt
23:24 pdayton joined #salt
23:26 intel joined #salt
23:32 s_kunk joined #salt
23:33 napsterX joined #salt
23:35 baweaver joined #salt
23:38 UtahDave Gareth: Yep!
23:39 Gareth UtahDave: Is Tom there?
23:39 UtahDave Yeah, but he's literally about to walk out the door.
23:39 UtahDave gone
23:39 UtahDave want me to relay a message to him tomorrow morning?
23:40 * UtahDave davidmq
23:40 Gareth I had sent him an email a week or so ago, thinking he missed it.
23:40 UtahDave I would not be surprised.
23:40 Gareth I can resend.
23:40 UtahDave He's reached that level of email flood that he misses TONS of stuff
23:41 Gareth yeah. no doubt :)
23:41 UtahDave When I email him I don't expect him to see it unless I go point it out to him.
23:41 UtahDave Want to pm me the subject and I'll have him look it up when he's got a moment
23:42 aqua^c joined #salt
23:44 Gareth I can tell you here :) nothing private...I had emailed him for advice on writing a runner to manage reactors.
23:45 UtahDave ah, ok.  that sounds great.
23:45 UtahDave I'll pass on the info
23:50 Gareth cool. thanks.
23:53 TodPunk joined #salt
23:55 kaictl joined #salt
23:55 Aidan_ joined #salt

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