Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2014-12-24

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

All times shown according to UTC.

Time Nick Message
00:02 iamtew good evening
00:02 iamtew is it possible to store files in pillars?
00:06 murrdoc files ?
00:07 iamtew I guess I'm asking about the same as this, https://github.com/saltstack/salt/issues/9569
00:07 s00pcan joined #salt
00:07 iamtew oh well :)
00:08 iamtew for now I just want to distribute certificates, but I will need to distribute binary files as well
00:10 murrdoc you can store file locations in pillars
00:11 murrdoc and then use either salt fs or http gets or git to bring those files down
00:11 murrdoc you can also always store the whole file as a pillar
00:11 murrdoc using yaml
00:12 iamtew right, using a literal block you mean?
00:12 murrdoc yup
00:12 murrdoc - key: |
00:12 murrdoc <tabs> values
00:12 iamtew softtab ;)
00:12 monkey661 joined #salt
00:12 iamtew ok I guess I'll just go with that, cheers :)
00:12 murrdoc https://github.com/saltstack/salt/issues/5480
00:13 murrdoc specifically whiteinge's comment
00:20 jonatas_oliveira joined #salt
00:25 badon_ joined #salt
00:30 monkey66 joined #salt
00:38 nitti joined #salt
00:46 stevednd joined #salt
00:50 pdayton joined #salt
00:50 snarfy joined #salt
00:53 dooshtuRabbit joined #salt
00:53 snarfy i tried something new. I want to use the extfs module in a state so i used module.run extfs and it seems to work. - the next part of the state mounts the newly minted filesystem successfully (and i can see it), but the module.run part fails according to the minion
00:54 snarfy gives me a traceback. AttributeError: 'list' object has no attribute 'get'. i guess i'm not trippin' if it actually works, but meh. if anyone smarter than i know what's up
00:55 stevednd I just upgraded my salt master version of ubuntu from ancient 10.04 to 14.04, and now I can't run any of my states due to missing GPG errors. I think something is wrong with pip, because it won't load. Do I need to manually reinstall easy_install and pip because of the newer python version?
00:57 __number5__ stevednd: have you done a `apt-get dist-upgrade` after upgraded to 14.04? and `sudo easy_install pip` will be a good idea too
00:58 stevednd __number5__: dist-upgrade was done, but not easy install pip
00:58 stevednd pkg_resources.DistributionNotFound: setuptools==3.6
01:00 __number5__ looks like you have broken python packages, try `sudo apt-get install python-pip` then `sudo pip install -U pip`
01:01 stevednd yeah, I'm reinstalling from the scripts in my salt files
01:01 stevednd hopefully just getting those two installed and then python-gnupg will be good
01:01 __number5__ and make sure the default python is python2 not python3
01:02 stevednd yeah, default is 2.7
01:02 stevednd the old default looks like it was 2.6
01:02 stevednd so it was probably something with that. I don't know much python so I might just be talking out of my ass
01:08 snarfy missing GPG errors. the master key didn't change did it?
01:11 stevednd __number5__: reinstalling easy_setup and pip got me in business, thanks
01:11 __number5__ no
01:11 __number5__ no worries
01:20 aqua^mac joined #salt
01:24 TheThing_ joined #salt
01:27 cberndt joined #salt
01:34 jalbretsen joined #salt
01:35 jalbretsen left #salt
01:51 nethershaw joined #salt
02:05 budman joined #salt
02:21 xenoxaos joined #salt
02:22 sarlalian joined #salt
02:23 budman joined #salt
02:30 bhosmer joined #salt
02:36 elfixit joined #salt
02:37 gngsk joined #salt
02:39 pentabular joined #salt
02:40 malinoff joined #salt
02:42 gngsk joined #salt
02:57 neogenix joined #salt
03:02 pdayton joined #salt
03:15 Mso150 joined #salt
03:22 xenoxaos joined #salt
03:23 bhosmer joined #salt
03:31 Mso150_f joined #salt
03:41 Ryan_Lane joined #salt
03:42 active8 joined #salt
03:46 SheetiS joined #salt
03:53 ndrei joined #salt
04:09 forrest joined #salt
04:10 pdayton joined #salt
04:10 flebel joined #salt
04:11 murrdoc joined #salt
04:12 pdayton joined #salt
04:13 pdayton joined #salt
04:15 aqua^mac joined #salt
04:21 dotz_ joined #salt
04:35 xenoxaos joined #salt
04:54 nitti joined #salt
05:00 tcotav joined #salt
05:03 spookah joined #salt
05:03 rm-rf joined #salt
05:08 schlueter joined #salt
05:09 jchen joined #salt
05:14 xenoxaos joined #salt
05:14 SheetiS joined #salt
05:17 murrdoc joined #salt
05:18 chutzpah joined #salt
05:24 rikair joined #salt
05:24 budman joined #salt
05:29 brianfeister joined #salt
05:31 zadock joined #salt
05:35 xenoxaos joined #salt
05:41 malinoff joined #salt
05:42 cruatta joined #salt
05:49 swing joined #salt
05:58 rm-rf joined #salt
06:09 pdayton joined #salt
06:11 pdayton joined #salt
06:13 swing hello everyone,how many minions can one salt-master support?
06:15 geekatcmu the standard answer applies: it depends
06:15 geekatcmu How often are you having the minions check in?
06:15 geekatcmu They'll all need a zmq connection, so assume a hard limit of < 64k
06:16 geekatcmu After that, it's all a question of performance requirements
06:16 geekatcmu Running a VM with 1 CPU and 512k RAM?  yeah, maybe one client.
06:17 geekatcmu 12 CPU box, lots of memory, minions checking in once a week?  Run a million.
06:17 geekatcmu (assume connections are intermitten)
06:17 swing RAM:32G
06:38 TheThing joined #salt
06:42 pdayton joined #salt
06:47 IEEE_Follow joined #salt
06:49 budman joined #salt
06:51 aquinas joined #salt
07:07 rm-rf_ joined #salt
07:12 trikke joined #salt
07:17 swing is anyboey met "ImportError: No module named salt.scripts "?
07:19 GnuLxUsr joined #salt
07:21 lalamini joined #salt
07:23 lalamini hello every one, I have a question, I can ps a process in system but the state report me the service is not available, is anybody can help me about it?
07:23 rm-rf joined #salt
07:28 linjan joined #salt
07:33 esogas_ joined #salt
07:44 jalbretsen joined #salt
07:49 pentabular joined #salt
07:53 StDiluted joined #salt
07:59 linjan joined #salt
08:02 monkey66 left #salt
08:04 flyboy joined #salt
08:10 JlRd joined #salt
08:12 forrest joined #salt
08:30 the_drow joined #salt
08:30 Ryan_Lane joined #salt
08:31 the_drow Hi guys, what do you think about hashicorp's new product: https://atlas.hashicorp.com/ ?
08:31 the_drow It uses terraform in order to start instances on cloud providers.
08:31 the_drow It's basically CoreOS but it's not tied to docker
08:32 the_drow I hate it when products are incompatitable with eachother.
08:33 the_drow If one choses to use this it means that he has to stop using salt cloud.
08:34 Mso150_f joined #salt
08:35 StDiluted joined #salt
08:44 malinoff the_drow, i don't get the idea of the tool from the first page :( where should i look?
08:45 the_drow It uses vagrant to develop machines, publish the artifacts using packer, deploy to the cloud using terraform and perform service discovery and health checks using consul
08:45 the_drow Basically CoreOS but without the ties to Docker
08:45 malinoff i see
08:46 gngsk joined #salt
08:47 the_drow The problem is if you use a salt master you loose all automatic configuration you get when you use salt-cloud
08:48 dotz_ joined #salt
08:48 malinoff it will become a paid software - buy it and request such functionality, if you want :)
08:48 the_drow I'm sure It won't be integrated
08:49 the_drow Does Hashicorp has interest in integrating salt so tightly into their system? I think not
08:50 the_drow "Exceptional cases are not enough to break the rules"
08:52 desposo joined #salt
08:53 malinoff if people will not use their tool just because their infrastructure is based on salt, i guess they'll do anything to get them, including salt integration
09:03 P0bailey joined #salt
09:03 P0bailey joined #salt
09:07 VSpike joined #salt
09:14 shoma joined #salt
09:15 shoma Since I upgraded to 2014.7 I see "Negative timeout in syndic main loop" in syndic log, what could be the reason?
09:19 malinoff https://github.com/saltstack/salt/blob/develop/salt/minion.py#L2053-L2054 this is really funny
09:21 babilen shoma: Could you recursively grep for "loop_interval" in /etc/salt and paste the result to http://refheap.com ?
09:25 babilen I blame process/schedule.py, but haven't quite tracked it down
09:25 bhosmer_ joined #salt
09:27 KaaK joined #salt
09:27 babilen https://github.com/saltstack/salt/blob/develop/salt/utils/schedule.py#L756 + dodgy math with seconds is probably the culprit (in particular https://github.com/saltstack/salt/blob/develop/salt/utils/schedule.py#L744 and similar)
09:29 dstokes joined #salt
09:30 darvon joined #salt
09:31 agend joined #salt
09:35 muss joined #salt
09:38 markm_ joined #salt
09:44 shoma babilen: "grep -R loop_interval /etc/salt" gives enpty result, I never configured that option
09:46 babilen Yeah, I didn't necessarily expect you to (at least not without remembering that), but just wanted to make sure :)
09:46 giantlock joined #salt
09:49 jngd joined #salt
09:49 shoma babilen: so should I fire up an issue?
09:52 aqua^mac joined #salt
09:52 babilen That sounds like a good idea. My bet would be that something in the calculation of seconds there is off (i.e. "when - now" is negative)
10:01 xenoxaos joined #salt
10:13 zadock joined #salt
10:18 nethershaw joined #salt
10:28 ktosiek hmm, lets say I have a few apps to manage. Each of them needs a DB with a matching user in postgres. Can I organize formulas for the db and the app in a way that will automaticaly add the db and user (and generate a password) when I add new app on some host?
10:29 ktosiek so I don't have to add the db/user by hand in postgres's pillar and then again in app's pillar?
10:30 fredvd joined #salt
10:47 babilen The "generate a password" bit will be tricky
10:47 markm_ joined #salt
10:48 babilen But you can naturally manage databases and users with http://docs.saltstack.com/en/latest/ref/states/all/salt.states.postgres_database.html (and states.postgres_{user,group, ...})
10:57 CeBe joined #salt
10:59 Nikerabbit joined #salt
11:00 Nikerabbit is it just me or does using "- names" break the "execute in definition order"?
11:04 tmh1999 joined #salt
11:05 babilen Context? Reference?
11:09 CeBe joined #salt
11:12 CeBe1 joined #salt
11:15 Nikerabbit babilen: I'm looking at the output of salt '*' state.highstate and they appear in different order
11:16 Nikerabbit from what I expect per definitions in the state files
11:19 Nikerabbit http://etherpad.wikimedia.org/p/IdxMgHLkYM
11:20 CeBe joined #salt
11:25 Nikerabbit what do you think?
11:29 Nikerabbit okay, I finally found https://github.com/saltstack/salt/issues/13312
11:30 ktosiek babilen: but that state will run on the (master) postgres box, not on the app box. So I'd have to somehow smuggle info about new app to the postgres pillar
11:32 CeBe joined #salt
11:34 ktosiek oh, another question: if I a master/slave postgres setup, I only want to run some states on master. How can I do it? Should I {% if salt['some_custom_function']() %} the whole master-specific part?
11:38 bhosmer joined #salt
11:43 CeBe joined #salt
11:44 Adam___ joined #salt
11:45 jonatas_oliveira joined #salt
11:48 jonatas_oliveira joined #salt
11:48 drawsmcgraw joined #salt
11:50 otter768 joined #salt
11:50 CeBe1 joined #salt
11:55 badon_ joined #salt
11:56 CeBe joined #salt
11:58 CeBe1 joined #salt
12:03 jrluis joined #salt
12:05 CeBe joined #salt
12:07 bart joined #salt
12:08 Sjap joined #salt
12:08 babilen ktosiek: As I said: Setting/Generating a password will be tricky. Your best bet is probably to write an execution module and feed info into an external pillar (e.g. postgres, ...)
12:08 linjan joined #salt
12:09 braqoon hi, maybe a simple one but i could not find a answer in the docs . When i want to have dir /srv/salt/users and in users dir to have init.sls and bob.sls . What i need to do for init.sls to see bob.sls and use it ? I thought include will do , but salt is not happy with it.
12:12 CeBe joined #salt
12:25 beardo joined #salt
12:25 bhosmer joined #salt
12:28 diegows joined #salt
12:29 babilen braqoon: How did you try to include it and what does "not happy with it" mean exactly? Please use http://refheap.com to show us.
12:29 braqoon sure
12:36 braqoon babilen, ha ha just fixed it while typing into refheap
12:36 braqoon thanks :)
12:36 braqoon i included it wrong
12:37 babilen "rubber duck debugging" :)
12:37 braqoon yep, thanks anyway :)
12:59 CeBe1 joined #salt
13:11 favadi_ joined #salt
13:17 jespada joined #salt
13:25 linjan joined #salt
13:26 _JZ_ joined #salt
13:34 FRANK_T joined #salt
13:50 linjan joined #salt
13:51 otter768 joined #salt
13:54 gngsk joined #salt
14:00 CeBe joined #salt
14:02 brianfeister joined #salt
14:07 giantlock joined #salt
14:16 Deevolution joined #salt
14:18 favadi_ joined #salt
14:20 glyf joined #salt
14:34 CeBe1 joined #salt
14:43 braqoon joined #salt
14:45 FRANK_T joined #salt
14:46 CeBe joined #salt
14:48 aqua^mac joined #salt
14:49 markm_ joined #salt
14:52 andrew_v joined #salt
14:54 ajolo joined #salt
14:55 pdayton joined #salt
14:56 schlueter joined #salt
14:56 pdayton joined #salt
14:58 schlueter1 joined #salt
15:08 markm_ joined #salt
15:25 housl joined #salt
15:26 cnelsonsic joined #salt
15:27 murrdoc joined #salt
15:34 SheetiS joined #salt
15:48 Thugal joined #salt
15:52 otter768 joined #salt
15:55 budman joined #salt
16:04 vbabiy joined #salt
16:15 Lendar joined #salt
16:32 brianfeister joined #salt
16:34 rikair joined #salt
16:49 Ozack1 joined #salt
17:12 pviktori_ joined #salt
17:12 hal58th left #salt
17:12 hal58th joined #salt
17:15 jonatas_oliveira joined #salt
17:19 frog_88 joined #salt
17:20 frog_88 ls
17:20 frog_88 exit
17:20 aqua^mac joined #salt
17:23 rm-rf joined #salt
17:36 rm-rf joined #salt
17:45 bezeee joined #salt
17:49 aparsons joined #salt
17:53 otter768 joined #salt
17:54 giantlock joined #salt
18:06 pentabular joined #salt
18:10 wt joined #salt
18:13 heyjonathan joined #salt
18:24 andrew_v joined #salt
18:27 bhosmer joined #salt
18:40 Mso150_f joined #salt
18:42 chamunks- I'm having a bit of a difficult time locating an example of a file that would exist in /etc/salt/98-grains.conf
18:42 rm-rf joined #salt
18:42 chamunks- I was hoping that the saltstack-bootstrap.sh would have included an argument for deploying grains to a file like this in an argument but theres some limitations I suppose.
18:43 chamunks- I mean /etc/salt/minion.d/##-grains.conf
18:44 Ethan joined #salt
18:45 Ethan Hi...question...should I be able to run regular salt states from a reactor sls?  like mount.mounted for example (https://salt.readthedocs.org/en/v0.17.1/ref/states/all/salt.states.mount.html).  It doesn't seem to work - sls fails to "render"
18:47 nitti joined #salt
18:48 hal58th chamunks- Are you just wondering what the format would be for creating grains in a minion conf file?
18:48 chamunks- hal58th idealy.
18:48 chamunks- I mean if theres a cool way to remotely do it via the salt command then I would be fine with that also.
18:49 chamunks- Where salt would do this for me / automagically.
18:49 hal58th If you do it via a salt command, you would have to do it again when the minion restarts
18:49 chamunks- Dern
18:50 chamunks- I mean I would imagine I could always do a salt 'glob' cmd.run 'echo "grains I want" > /etc/salt/minion.d/grains.conf'
18:50 chamunks- but I imagined there was something likely more elegant.
18:50 hal58th chamunks- Yes, that is a good solution.
18:51 hal58th You can run "sudo salt-call sys.doc" to see all available commands
18:53 hal58th Looks like you can use the command " grains.setval" to set a grain. I don't know where it puts it and you want to make sure it exists after a reboot
18:55 chamunks- hal58th do you have a link to where you found that?
18:55 hal58th Ethan: I haven't touched the reactor system or else I would give you a suggestion :(
18:55 chamunks- or just in the salt-call
18:55 hal58th just in salt-call
18:56 chamunks- salt is really annoying to get into.  Because search bubbles really want you to be stuck in recipe google mode.
18:56 Ethan hal58th: thanks.  I'm really liking it's potential to use with salt-cloud (lauch public cloud instances, then mount fs's and install software all automatically)
18:56 schlueter joined #salt
18:57 chamunks- So much information comes back with that command holy carp
19:09 Ethan actually sorry, the reactor renders but when it runs it gives "AttributeError: 'ReactWrap' object has no attribute 'mount'".
19:09 aqua^mac joined #salt
19:10 chamunks- hal58th if you're interested it ended up being like this.  salt 'ci.nix*' grains.setvals "{'roles': 'jenkins', 'key2': 'val2'}"
19:10 chamunks- It doesn't make it look pretty by any means it just onelines everything but meh.
19:11 shoma joined #salt
19:12 hal58th chamunks- as long as it works. then we're all good
19:16 hal58th1 joined #salt
19:18 chamunks- I'm not really 100% on how to set more then one val but I'm not really a programmer so this stuff isnt exactly second nature to me.
19:22 rm_jorge joined #salt
19:23 aw110f joined #salt
19:23 JlRd joined #salt
19:27 pdayton joined #salt
19:28 Mso150_f joined #salt
19:40 schlueter1 joined #salt
19:44 schlueter joined #salt
19:47 FRANK_T joined #salt
19:48 zz_Cidan joined #salt
19:49 Cidan joined #salt
19:54 otter768 joined #salt
19:56 Furao joined #salt
20:05 bfoxwell joined #salt
20:06 schlueter joined #salt
20:07 Jimlad joined #salt
20:08 Furao joined #salt
20:08 schlueter1 joined #salt
20:10 Nikerabbit left #salt
20:17 otter768 joined #salt
20:23 StDiluted joined #salt
20:26 hal58th1 chamunks-: It's using json format. Unfortunately it will take some knowledge to know how dicts and lists work and in JSON
20:27 chamunks- salt 'ci.nix*' grains.setvals "{'roles': ['jenkins', 'nginx']}"
20:27 chamunks- I poked the ever knowledgable flamin_scotsman via skype :P
20:27 hal58th1 ah that's good. I would have to research it some too. I just know it's using JSON
20:28 schlueter joined #salt
20:31 Mso150_f_x joined #salt
20:36 forrest joined #salt
20:36 schlueter1 joined #salt
20:37 markm_ joined #salt
20:38 schlueter2 joined #salt
20:38 acabrera joined #salt
20:39 jasonrm joined #salt
20:44 Ethan so how is salt able to execute certain states (like "mount") that require sudo?  Does it just login using ssh under the covers and run the commands using sudo?
20:51 Ethan and if requiretty is turned on for whatever reason does this basically prevent salt from working?
20:52 wt importing the salt module when writing a script causes logging to stop. Is there any way to work around that?
20:54 forrest Ethan: Salt-ssh is connecting as the user you specify, so if they don't have sudo, then you don't get sudo, check out: http://docs.saltstack.com/en/latest/topics/ssh/#salt-ssh-roster
20:54 ekristen joined #salt
20:54 forrest wt: Not that I can think of, isn't the module handling some logging so it's basically modifying the input?
20:55 forrest If anyone knows someone that works on github and can get a feature request in I'd love to see number of PRs on the org page for repos within it.
20:58 aqua^mac joined #salt
20:59 Ethan forrest: thanks!  So if I deploy an instance using salt-cloud it does the magic to tell salt-master that the user it needs to use by default is the cloud instance user (i.e. ec2-user for aws-rhel, ubuntu for aws-ubuntu, etc.).  And as long as that user has sudo it's all good (which they do by default in most public clouds).  Do I have that right? It all seems to work but I'm just curious how.
21:00 forrest Ethan: so salt-cloud isn't using salt-ssh (unless there was an update I missed), it installs the salt-minion on provision, then passes the data through to hook it back to the master, then restarts the service on the new minion, and says 'do these things!' (usually a highstate).
21:02 Ethan forest: right, that makes sense.  But I'm also able to run reactor stuff on instances deployed by salt-cloud and it just works, which is GREAT!  I'm assuming in this case that under the covers salt-cloud must be telling salt-master what user to use somewhere, in order for the reactor scripts to work.  And I also notice that when I deploy a minion via salt-cloud, the key is automatically accepted by salt-master!   Again, cool.
21:03 badon joined #salt
21:06 forrest Ethan: Yeah when the provisioning happens via salt-cloud (you have your cloud file configured to hook up to AWS), it passes some data onward through the system that is needed to do the rest of the provisioning and configure stuff like you've specified in the config. Past that I'm not familiar enough with the internal workings of salt-cloud to provide more details, I leave working on that portion up to some of th
21:06 forrest e other guys.
21:08 murrdoc joined #salt
21:10 otter768 joined #salt
21:10 Ethan ok thanks.  again it all seems to work great...just curious about the magic that makes it so easy :)
21:10 otter768 joined #salt
21:14 forrest Ethan: Yeah if you feel like diving into the source it's over here: https://github.com/saltstack/salt/tree/develop/salt/cloud and the docs are here: http://docs.saltstack.com/en/latest/topics/cloud/ but I don't think they go into a 'deep dive', might be good to add.
21:28 otter768 joined #salt
21:28 otter768 joined #salt
21:39 ggoZ joined #salt
21:40 Sjap left #salt
21:46 markm_ joined #salt
22:14 kormoc joined #salt
22:14 schlueter joined #salt
22:16 schlueter1 joined #salt
22:25 aparsons joined #salt
22:27 sgregory joined #salt
22:28 bfoxwell joined #salt
22:34 kormoc joined #salt
22:37 agend joined #salt
22:38 otter768 joined #salt
22:44 kormoc joined #salt
22:45 aquinas joined #salt
22:47 sgregory joined #salt
22:47 aqua^mac joined #salt
22:54 kormoc joined #salt
23:00 kormoc joined #salt
23:00 kormoc joined #salt
23:08 ckao joined #salt
23:09 giantlock joined #salt
23:15 glyf joined #salt
23:26 kormoc joined #salt
23:29 younqcass joined #salt
23:30 aw110f joined #salt
23:36 kormoc joined #salt
23:38 viq joined #salt
23:44 kormoc joined #salt
23:50 acabrera joined #salt
23:58 kormoc joined #salt
23:58 colonD joined #salt

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