Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2016-06-06

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

All times shown according to UTC.

Time Nick Message
00:16 punkoivan joined #salt
00:17 nmadhok joined #salt
00:25 stooj joined #salt
00:34 jerematic joined #salt
00:38 kus joined #salt
00:39 bbradley joined #salt
00:41 ablemann left #salt
00:48 nmadhok joined #salt
00:50 edrocks joined #salt
00:54 martoss1 joined #salt
01:01 Shirkdog joined #salt
01:02 nmadhok joined #salt
01:03 nmadhok1 joined #salt
01:05 nmadhok joined #salt
01:07 catpiggest joined #salt
01:16 nmadhok1 joined #salt
01:20 misconfig joined #salt
01:30 heewa joined #salt
01:34 jerematic joined #salt
01:34 nmadhok joined #salt
01:35 barmaley joined #salt
01:37 edrocks joined #salt
01:39 mosen joined #salt
01:47 ilbot3 joined #salt
01:47 Topic for #salt is now Welcome to #salt! | Latest Versions: 2015.5.10, 2015.8.10, 2016.3.0 | Support: https://www.saltstack.com/support/ | Logs: http://irclog.perlgeek.de/salt/ | Paste: https://gist.github.com/ (please don't multiline paste into channel) | See also: #salt-devel, #salt-offtopic | Ask with patience as we are volunteers and may not have immediate answers
01:47 onlyanegg joined #salt
01:51 shoemonkey joined #salt
01:54 cyteen_ joined #salt
02:05 hasues joined #salt
02:14 hasues left #salt
02:27 shoemonkey joined #salt
02:33 shoemonkey joined #salt
02:41 Ayo joined #salt
02:43 bbradley joined #salt
02:45 kshlm joined #salt
02:46 ntropy joined #salt
02:48 flowstate joined #salt
02:48 evle joined #salt
02:51 bbradley joined #salt
02:51 tuxx joined #salt
02:52 edrocks joined #salt
03:01 mpanetta joined #salt
03:06 nmadhok joined #salt
03:09 ramteid joined #salt
03:10 racooper joined #salt
03:15 aarontc joined #salt
03:20 hasues joined #salt
03:20 hasues left #salt
03:46 spuder joined #salt
03:48 nmadhok joined #salt
03:58 heewa joined #salt
04:07 favadi joined #salt
04:07 tristianc joined #salt
04:08 bshelton229 joined #salt
04:09 paydro joined #salt
04:19 onlyanegg joined #salt
04:24 rdas joined #salt
04:25 paydro joined #salt
04:25 bshelton229 joined #salt
04:29 cyborg-one joined #salt
04:32 marie1972 joined #salt
04:38 marie1972 left #salt
04:55 edrocks joined #salt
05:01 flowstate joined #salt
05:03 keimlink joined #salt
05:04 aboe joined #salt
05:11 mosen joined #salt
05:29 favadi joined #salt
05:32 paydro joined #salt
05:32 felskrone joined #salt
05:51 pug joined #salt
05:56 dmaiocchi joined #salt
06:06 dmaiocchi joined #salt
06:10 colttt joined #salt
06:13 apanek left #salt
06:14 Robert_Wiley joined #salt
06:17 paydro joined #salt
06:19 AirOnSkin joined #salt
06:31 yuhlw joined #salt
06:32 kawa2014 joined #salt
06:36 whaity left #salt
06:38 jerematic joined #salt
06:52 KermitTheFragger joined #salt
06:53 fracklen joined #salt
06:55 fracklen joined #salt
06:57 edrocks joined #salt
07:06 martoss joined #salt
07:06 flowstate joined #salt
07:12 punkoivan joined #salt
07:19 deniszh joined #salt
07:20 Ayo joined #salt
07:20 JohnnyRun joined #salt
07:21 keimlink joined #salt
07:24 Miouge joined #salt
07:25 toanju joined #salt
07:27 tpaul joined #salt
07:29 rdas joined #salt
07:30 auzty joined #salt
07:32 yuhlw joined #salt
07:33 Zhen joined #salt
07:34 punkoivan joined #salt
07:37 nmadhok joined #salt
07:39 jerematic joined #salt
07:39 keimlink joined #salt
07:40 nmadhok1 joined #salt
07:43 impi joined #salt
07:46 jagguli joined #salt
07:48 CeBe1 joined #salt
07:56 krymzon joined #salt
08:05 Zhen joined #salt
08:06 cyborg-one joined #salt
08:07 fracklen joined #salt
08:07 fracklen joined #salt
08:08 wiqd joined #salt
08:10 slav0nic joined #salt
08:14 s_kunk joined #salt
08:18 anmol joined #salt
08:19 Miouge joined #salt
08:28 mackripeum joined #salt
08:33 manji joined #salt
08:35 toanju joined #salt
08:38 JohnnyRun joined #salt
08:41 punkoivan joined #salt
08:48 hellosalt joined #salt
08:48 hellosalt Any body know if I can use multiple top.sls in pillars or states?
08:55 hellosalt or alternatively, this is what I want to do: https://gist.github.com/activars/03a73a22455da5116d1aaf1560a06844
08:58 hellosalt let me know if this makes sense or maybe i'm using it wrong :)
08:59 edrocks joined #salt
09:04 AndreasLutro hellosalt: that's just not how you're supposed to use top.sls
09:05 AndreasLutro while I'm pretty sure there are several master config options for merging multiple top.sls, why not just have 1 in your case?
09:05 manji joined #salt
09:06 potens joined #salt
09:06 manji joined #salt
09:06 favadi joined #salt
09:07 lero joined #salt
09:08 Ashald joined #salt
09:09 hellosalt AndreasLutro: you are right, I can refactor the sub top.sls to my own implementation. And.. does it make sense to clone that formula into my sub-directory?
09:10 lero__ joined #salt
09:11 AndreasLutro it's not wrong I guess - but I'd rather use this approach https://docs.saltstack.com/en/latest/topics/development/conventions/formulas.html#adding-a-formula-directory-manually
09:11 josuebrunel joined #salt
09:12 AndreasLutro though I don't use formulas at all so I guess you shouldn't take my advice too seriously
09:13 garphy joined #salt
09:13 upstream joined #salt
09:19 lungaro joined #salt
09:19 stooj Hmm.. how do I target using a grain that contains a list? I have a roles grain that contains a list of roles (webserver, fileserver etc)
09:21 AndreasLutro stooj: 'my_list_grain:my_item'
09:22 AndreasLutro you can try the matcher on the command line: salt -G 'saltversioninfo:2016' test.ping
09:22 permalac joined #salt
09:24 stooj AndreasLutro: Hmm.. that didn't work when I tried it. I must have something else wrong. Thanks
09:25 stooj Ah... -G 'roles:fileserver' works, but 'G@roles:fileserver' doesn't work
09:29 hellosalt AndreasLutro: Coming from a puppet/ansible and programming background, I'm not happy salt does not have a good formula dependencies management solution ready to use.  Here's how I manage external versions: https://gist.github.com/activars/8e42dfefde5c933dfe77d772ec34f0bb
09:29 stooj Uhm, so what would be the syntax in a top file?
09:31 hellosalt stooj, what you did with top.sls selecting 'roles' should work
09:36 bdrung_work joined #salt
09:38 q1x joined #salt
09:41 q1x Hi everyone, I know it is possible to use the minion id in a states file via the grains system as {{ grains.id }}, however, I believe the minion can set this var at run time. I'd like to use an identifier that can not be altered by the minion
09:41 q1x in Puppet you can match with the id on the client cert, is something like that available in Salt as well?
09:44 favadi joined #salt
09:45 hellosalt qlx: you can use grain or mine
09:47 stooj OK, thanks hellosalt & AndreasLutro - I must have a mistake somewhere. Off to hunt :)
09:49 remyd1 joined #salt
09:49 hellosalt stooj: try grain['id']
09:49 hellosalt qlx: try grain['id']
09:50 hellosalt stooj: sorry, sent the answer to the wrong person
09:51 remyd1 Hi. Is there a way to check the output / return code of a state and loop over it if it fails ? E.g. with onfails: execute again
09:54 babilen remyd1: No - but why don't you write something that does that and then fires an event? You could wait for that event in your state.
09:54 rsys joined #salt
09:56 remyd1 babilen, do you have an example ?
09:57 babilen remyd1: Of what exactly?
09:58 babilen remyd1: You can fire an event with https://docs.saltstack.com/en/latest/ref/states/all/salt.states.event.html#module-salt.states.event / https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.event.html#salt.modules.event.fire_master and wait for one with https://docs.saltstack.com/en/latest/ref/states/all/salt.states.event.html#salt.states.event.wait
09:58 babilen You can write programs/scripts in whatever language you want and interface with salt from there (either by calling salt-call or using the local client)
09:59 babilen Maybe a beacon would be appropriate in your case, but without information on what you actually want to do I don't know what to suggest.
09:59 jakshi joined #salt
09:59 babilen I'm not aware of a method to "loop over" a state and wait for it to succeed in salt.
09:59 remyd1 How about https://docs.saltstack.com/en/latest/topics/event/master_events.html#job-events
09:59 babilen But then .. you could just run a highstate over and over again.
10:00 remyd1 but I need the jid
10:00 babilen Why?
10:00 jakshi Hello All
10:00 remyd1 to retrieve the ret code ? no ?
10:00 jakshi I'm a bit stuck with error: mapping values are not allowed here
10:01 jakshi error
10:01 babilen jakshi: When you do what? Could you, mayhaps, paste your code/state/commands/whatever it is to one of http://refheap.com, http://paste.debian.net, https://gist.github.com, http://sprunge.us, … ?
10:01 jakshi what does it mean? how to fix it?
10:01 Narendra__ joined #salt
10:01 dmaiocchi joined #salt
10:03 jakshi https://gist.github.com/jakshi/0c2dd28020991b6d575176e4ab5132fa
10:05 stooj hellosalt: in top.sls?
10:05 jakshi no in database.postgresql-slave
10:05 babilen jakshi: That "include postgresql" comes from what?
10:06 jakshi from database.postgresql
10:06 babilen jakshi: Do you literally have "include postgresql" in your SLS?
10:06 babilen (I assume that you haven't pasted the entire file)
10:07 hellosalt stooj: yes, using compound query in state top.sls
10:07 jakshi one moment, I'll include all
10:07 babilen jakshi: So you *do* have "include postgresql" in your SLS?
10:08 hellosalt stooj: i'm using compound query applying state on a custom grain key/value currently, it seems to serve my purpose for the moment.
10:08 hellosalt stooj: if it doesn't work, maybe you are missing pillar data for the role to be executed?
10:09 jakshi @babilen
10:09 jakshi @babile: yes, I updated the gist
10:10 jakshi @babilen: yes, I literally have include, I updated the gist with all files that I have
10:10 babilen jakshi: Okay, make that "include:\n  - database.postgresql" please
10:10 stooj Phew! That worked hellosalt - thanks for sticking with me :)
10:13 jakshi @babilen thank you a lot, It works now, I missed that one :( I'll be more accurate in future.
10:14 babilen jakshi: I'd also like to point out that grains for roles might not be a good choice. First you have to manage those too, which typically brings you back to square one, secondly you can't trust them (minions can claim to have whatever grains they want) and thirdly there isn't really a point in saving them in a distributed manner IMHO
10:14 babilen jakshi: But yeah! Great :)
10:15 jakshi @babilen Could you tell please, what is the a good choice for roles?
10:15 babilen You could use pillars for them, you might even have a database/datasource with that information already that you can include as external pillar
10:16 babilen jakshi: How do you decide which minion should have which role? How do you assign "roles" at the moment? Do you have an authoratitative datasource for that already?
10:16 jakshi @babilen Thank you for advice, I'll adjust my config with that.
10:18 jakshi @babilen It's test setup for migration from puppet. For now we assign roles in environment variables.
10:18 jakshi @babilen I mean for puppet.
10:18 babilen And how are they becoming grains then?
10:19 jakshi @babilen well, they don't. Idea was to assign roles in grains instead of environment variables.
10:19 babilen Manually?
10:19 om joined #salt
10:20 jakshi @babilen yes, manually, our infrastructure is not the best around :(
10:20 hellosalt stooj: good to know! I got it working last week,  a bit learning curve :P
10:20 babilen jakshi: Don't feel bad .. I'm just trying to understand where you are coming from :)
10:21 stooj hellosalt: Really having to fight the "I get the tutorial kinda, now to implement something massively complicated" impulse!
10:22 dmaiocchi joined #salt
10:22 babilen jakshi: How many minions do you have? Do you have a clear naming convention or some database in which you already have those "roles" ?
10:27 hellosalt stooj: I get the same feeling - working on Kubernetes cluster while learning salt is a "fun". :)
10:28 punkoivan joined #salt
10:30 fgimian joined #salt
10:30 slav0nic_ joined #salt
10:33 jakshi @babilen: we don't have clear naming scheme, and currently our puppet setup is a mess. we actually have two puppets. old and new.
10:34 jakshi @babilen: and also we don't happy with puppet, so we think about migrating to salt
10:34 jakshi @babilen: we have about 200 hosts now. so it will be about 200 minions
10:36 jakshi @babilen: what I don't know how to do now, it's how to organize all hierarchy of attributes that have each host. Each host have role, location, environment and may be some host specific things.
10:37 cyborg-one joined #salt
10:40 om2 joined #salt
10:41 jerematic joined #salt
10:45 toanju joined #salt
10:45 babilen jakshi: How are they hosted?
10:47 babilen jakshi: My recommendation would be to manage that information in suitable datasources (e.g. a database) and to access that database as external pillar. You can find a list of supported datasources on https://docs.saltstack.com/en/latest/ref/pillar/all/
10:48 babilen jakshi: If your (cloud) provider provides some of that information via an API you might be able to include it as external grain. There are, for example, modules for EC2 (cf. https://github.com/saltstack/salt-contrib/tree/master/grains → ec2_info, ec2_tags, ...)
10:49 q1x hellosalt: thanks for the suggestion, but I was looking for another way (ie not using grains) because of security concerns
10:49 babilen jakshi: If you don't expect these to change you can manually tag your boxes by setting grains, but that might turn into a nightmare if that ever changes. In that end it is a rather simple scheme ..
10:50 q1x hellosalt: preferably something internal to the salt master that is verified based on the key
10:50 babilen jakshi: You could also target a suitable "host information" dictionary to each minion via pillars. That would make it easier to update ..
10:50 babilen jakshi: There are many, many options and there isn't a "best" one as it depends on your needs and the existing infrastructure.
10:51 jakshi @babilen: part of them are AWS, part of them are ganeti cluster in DC
10:51 babilen jakshi: I'd take a look at the external pillars and read https://docs.saltstack.com/en/latest/topics/targeting/ in toto
10:52 jakshi @babilen: I see, I'll check external pillars :)
10:52 babilen jakshi: Well, sounds as if the ec2_info grain might be helpful for the minions in AWS at least
10:52 jakshi @babilen: unfortuately there're no module for ganeti API :(
10:53 babilen jakshi: You could write one that queries the ganeti API (for example)
10:54 babilen One problem with salt is that it has so many building blocks that it is hard to decide which to use to build what one envisioned .. It is even harder if you just start out and just want "something" that works
10:54 jakshi @babilen I'll look into writing queries to ganeti API, static things, written somewhere tend to steal your time. so it would be great to get info about nodes automatically.
10:55 jakshi @babilen: that's why I started with grains, it looked like simplest thing to do...
10:56 babilen jakshi: My recommendation for now would be: 1. Include ec2 grains 2. Keep roles in pillars (assigned based on minion id) or read them from an external datasource (e.g. database) 3. If you need information about ganeti boxes write a custom grain that queries the ganeti API for information
10:56 jakshi @babilen: thank you for advice, it's very helpful to have guidance in the beginning
10:57 babilen Alternatively start tagging hosts in grains, but be aware that you might have to manage those later on (which then raises the question: "How to target those grains?" which is, essentially, the same as "How do I target those roles?")
10:57 heewa joined #salt
10:58 babilen Grains might be a good choice if they are static (or mostly static) and if changes to them will result from manual steps
10:58 babilen In that case they are quite easy, but you don't *really* win much over targeting a "hostinfo: " pillar
10:59 babilen I only use grains for information that I can programmatically gather *on the minion* and grains therefore contain data about the setup of the minion itself.
11:00 babilen I should note that I am quite against the whole "role in grains" thing and that this is by no means an agreed to opinion in the community
11:01 edrocks joined #salt
11:07 XenophonF joined #salt
11:07 abednarik joined #salt
11:08 XenophonF hi all - I have Salt running on FreeBSD 10.3 in a Hyper-V VM, and when the salt-minion service starts, it causes the storage to disconnect, panicking the operating system
11:08 XenophonF http://imgur.com/a/omXMw
11:09 XenophonF sorry for the screen captures, but they're all i have
11:09 XenophonF i haven't figured out how to setup a serial console in Hyper-V
11:09 honestly jakshi: babilen: all of my "role" information is handled using {% if grains['id'] in pillar['minions_i_want_to_run_this'] %} (or something equivalent)
11:10 XenophonF i'm running the same version of Salt on FreeBSD 10.2, also in a Hyper-V VM, without any problems, so i'm inclined to think that this is a FreeBSD bug
11:11 XenophonF has anyone else experienced this kind of crash?
11:11 manji joined #salt
11:12 manji joined #salt
11:12 honestly XenophonF: how does salt manage to kill the storage in the first place? It's pretty hard for "just a python script" to disrupt fs stuff or kernel driver stuff to do that even if it runs as root
11:12 jakshi @babilen thank you, I'll keep your advice in mind, when I start to expand my test setup over more nodes. I think you have a point about 'grains should be gathered programmatically'.
11:14 Narendra__ Hi Guys I am getting this error
11:14 Narendra__ SaltClientError: Attempt to authenticate with the salt master failed 061107ZJun2016,670 [salt.scripts/WARNING] ** Restarting minion **
11:14 jakshi @babilen I actually come from chef world, work in several chef using companies before. But I think that for current one salt would be better choice, because whole devops team speak python more or less fluently.
11:14 Narendra__ can somebody help me here ?
11:15 XenophonF I'm not sure, honestly.
11:15 Narendra__ However I am unable to test.ping this minion from master
11:15 babilen jakshi: Which is great, because it allows you guys to extend salt easily (it is super easy to write new states, grains, pillars, modules, ... if you know Python)
11:15 XenophonF The storage disconnect only happens when salt-minion starts.
11:15 Narendra__ but normal ping is working fine
11:15 evle1 joined #salt
11:15 babilen jakshi: One recommendation I would also give you is to think hard about adopting Jinja as SLS renderer. I sometimes which that I had just started writing SLS in Python or Mako instead because Jinja just isn't powerful enough.
11:16 babilen jakshi: You can use any of the languages mentioned on https://docs.saltstack.com/en/latest/ref/renderers/all/
11:16 babilen (and chain them)
11:17 Narendra__ left #salt
11:17 jakshi @babilen than you, I'll look into Mako templating engine. Python can be overkill for simple states, but overall I like the idea to write states in python too. because When I used chef I get used to have power of general purpose language in my disposal
11:18 babilen OTOH jinja is the de-facto standard in Saltstack and therefore in a lot of code you find in documentation and collection of saltstates (cf. https://github.com/saltstack-formulas) so you won't really get around that
11:19 XenophonF maybe it's a grain doing some kind of probe that tickles a bug in FreeBSD
11:19 babilen jakshi: And one more advice: Good salt code is IMHO data-driven and states should be idempotent. This means that you don't perform "upgrades" or similar things in a state run and that your states are written in the most generic way possible. The actual "configuration" or "their content" comes from pillars.
11:19 XenophonF that's my working theory atm
11:20 XenophonF unfortunately, I think the only way to figure this out is to run salt-minion in a debugger and single step through it
11:20 XenophonF because the storage gets disconnected, i don't have any log files
11:20 babilen jakshi: A good example for the data driven approach is the users-formula: https://github.com/saltstack-formulas/users-formula -- You can target that to every minion, but it won't do *anything* if no pillar data has also been targeted. You can then create/remove users using data in pillars that follow https://github.com/saltstack-formulas/users-formula/blob/master/pillar.example
11:20 honestly XenophonF: what happens if you run the minion as unprivileged user?
11:21 jakshi @babilen Thank you :) I understand value of idempotent code for having reliable infra.
11:21 honestly XenophonF: also, can you spin up a VM that runs from local storage and has remote storage attached so it maybe won't panic if only the remote storage gets screwed up?
11:21 babilen jakshi: All the best and may you enjoy using salt :)
11:22 jakshi @babilen thank you, I think I'll enjoy it for sure. I'll look into users recipe.
11:22 babilen jakshi: It's just an example for the "data driven" approach I like
11:22 XenophonF honestly: to your first question, I don't know, but I'll try it.
11:22 GreatSnoopy joined #salt
11:23 XenophonF honestly: to your second question, do you mean root on NFS?
11:23 manji joined #salt
11:24 honestly well I don't know
11:24 honestly just boot the VM from a *different* kind of storage than whatever breaks :P
11:25 heewa I have a development question about how code should handle failures. I'm seeing an s3 file serving failure, but the code I tracked it down to doesn't log error, doesn't raise an exception, and doesn't return anything. So nothing in the state's codepath can react to being unable to correctly get the file. It looks like the code's been like this for a while. How do I find out if that's deliberate or not?
11:25 honestly deliberate or not that sounds wrong
11:25 heewa (Is this the right place to ask this? If not, where would I find out?)
11:25 honestly if it's a question about code related to saltstack this is the right place
11:26 honestly if you want an official response make an issue on github
11:26 heewa Ok, cool, thanks!
11:28 Narendra__ joined #salt
11:28 XenophonF honestly: oh i see what you mean
11:28 amcorreia joined #salt
11:29 XenophonF the VM config is pretty simple, the hypervisor only has DAS
11:29 XenophonF the storage disconnect is happening inside the VM
11:29 XenophonF i'm going to ask on #freebsd or, failing that, on freebsd-stable@
11:29 XenophonF maybe they can give me a clue
11:31 jakshi joined #salt
11:31 jcristau joined #salt
11:33 MadHatter42 joined #salt
11:42 jerematic joined #salt
11:43 quarcu joined #salt
11:44 om2 joined #salt
11:47 rim-k joined #salt
11:47 rim-k hello everyone!
11:48 ninkotech joined #salt
11:48 rim-k since I upgraded to the latest version (2016.3)
11:48 rim-k state service.enabled is not working properly
11:48 mikecmpbll joined #salt
11:49 rim-k systemctl is-enabled my_service
11:49 rim-k returns disabled
11:49 rim-k but salt-call service.enabled my_service
11:49 mikecmpbll i'm new to saltstack, just learning the ropes. i'd like to set up ufw using https://github.com/mariodpros/ufw-formula but struggling to get my head around how it utilises the pillar
11:49 rim-k doesn't enable the service
11:49 rim-k simply returns "True"
11:50 mikecmpbll it says "This module manages your firewall using ufw with pillar configured rules.". how would one implement a state for ufw?
11:50 rim-k mikecmpbll: https://github.com/mariodpros/ufw-formula/blob/master/pillar.example
11:50 mikecmpbll rim-k : seen that also, but my only understanding of pillar so far is for setting variables to use in states
11:51 AndreasLutro mikecmpbll: if you use a formula, the states are already implemented for you, you just provide the pillars for configuring said states
11:51 rim-k any idea on my issue?
11:52 mikecmpbll AndreasLutro : ah, so just by configuring the pillars and including the formula, it knows what to do? so I just apply the pillar for some hosts and bam?
11:53 mikecmpbll makes sense, sweet.
11:56 josuebrunel joined #salt
11:57 AndreasLutro mikecmpbll: you also need to apply the states in the formula to the host via the state top file, but yeah
11:57 mikecmpbll AndreasLutro : ah yes!
11:59 numkem joined #salt
12:00 mikecmpbll taking the example of ufw formula, i want different ufw config depending on what services the minion runs. what's the best way to approach this; use grains to specify the services on each minion and then jinja conditionals in the ufw pillars?
12:02 shiriru joined #salt
12:02 AndreasLutro I'd just create different pillar files for each service
12:03 mikecmpbll ah yeah.. seems easier :D
12:16 mikecmpbll i'm assuming pillar files get merged, then
12:17 AndreasLutro they do, recursively
12:18 mikecmpbll ????????
12:19 Ayo joined #salt
12:24 jschoolcraft joined #salt
12:26 DanSlimmon joined #salt
12:33 gh34 joined #salt
12:33 om2 joined #salt
12:43 jerematic joined #salt
12:50 misconfig joined #salt
12:57 slav0nic joined #salt
12:57 slav0nic_ joined #salt
12:58 subsignal joined #salt
13:04 edrocks joined #salt
13:04 subsigna_ joined #salt
13:13 perfectsine joined #salt
13:18 gh34 joined #salt
13:21 racooper joined #salt
13:23 edrocks joined #salt
13:25 lompik joined #salt
13:27 snergster joined #salt
13:34 sjorge joined #salt
13:35 mage_ any idea how could I file.recurse with a source which is not salt:// ?
13:36 mage_ in other words: how to file.recurse directory /foo/a in /foo/b on minion x ?
13:36 mage_ where /foo/a and /foo/b are on minion x
13:37 mage_ I could always sur a cmd.run with a copy -R if there is no other way of doing it
13:40 komputes joined #salt
13:41 Tanta joined #salt
13:42 mikecmpb_ joined #salt
13:44 nyx joined #salt
13:45 rgrinberg joined #salt
13:47 zmalone joined #salt
13:50 ldelossa joined #salt
13:51 fracklen_ joined #salt
13:52 opdude_ joined #salt
13:57 shoemonkey joined #salt
13:58 [Kernel_Panic] joined #salt
13:58 om2 joined #salt
13:58 nmadhok joined #salt
13:59 komputes joined #salt
13:59 [Kernel_Panic] hi all
13:59 [Kernel_Panic] please, i need suport.  how to start AWS VM with Salt-cloud command ?
14:00 [Kernel_Panic] i'm using " salt-cloud -a start i-xxxxxx " but result in "Not found"
14:00 perfectsine joined #salt
14:01 nmadhok joined #salt
14:02 nmadhok [Kernel_Panic]: That means VM with that name doesn't exist
14:03 andrew_v joined #salt
14:04 mpanetta joined #salt
14:04 teryx510 joined #salt
14:04 mpanetta joined #salt
14:04 [Kernel_Panic] nmadhok, how to find the full sintaxys of salt-cloud -a start  '
14:04 [Kernel_Panic] ?
14:05 [Kernel_Panic] where, i can read ... i not find any in documentation, only say "salt.cloud.clouds.ec2.start(name, call=None)"
14:06 [Kernel_Panic] is necessary map a existing VM node ?
14:06 [Kernel_Panic] is possible to map all VM Nodes that are created previously ?
14:09 hasues joined #salt
14:09 hasues left #salt
14:09 TooLmaN joined #salt
14:09 tristianc_ joined #salt
14:11 duncanmv joined #salt
14:12 Tyrm joined #salt
14:15 symx joined #salt
14:16 brew joined #salt
14:16 symx In a state file, how can I access grains from a different minion?
14:17 drawsmcgraw joined #salt
14:18 babilen symx: Use the salt mine -- https://docs.saltstack.com/en/2015.8/topics/mine/index.html
14:18 babilen symx: Which information are you after?
14:20 [Kernel_Panic] Thanks
14:20 [Kernel_Panic] i fix it, wiht using VM "Name" directly
14:20 [Kernel_Panic] is work ;)
14:20 [Kernel_Panic] i think that i need use Resource_Id
14:20 [Kernel_Panic] but no.
14:21 [Kernel_Panic] any here, know how to a extract name of a lot of VM Nodes, using a Tag ?
14:21 [Kernel_Panic] i have 49 Nodes with a tag, i need "Stop" all of this group
14:22 symx thanks babilen. I'm looking to use a templated config file, but I need to grab the IPs of other minions.
14:23 stooj Does anyone use the users-formula? I'm getting a failure when adding an entry to known_hosts (looks like the .ssh directory isn't created)
14:24 babilen symx: Oh, I wouldn't use grains for that at all, but https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.network.html#salt.modules.network.ip_addrs
14:25 babilen symx: In fact I target a number of those as mine function alias to my minions .. let me show you
14:25 jhauser joined #salt
14:26 stooj Ugh. I'm too tired. Mixed up authorized keys with known hosts..
14:27 mage_ any idea if 2016.3.1 is coming soon ? :)
14:27 mage_ there are a lot of issues in 2016.3.0 on FreeBSD that seems to be fixed in the 2016.3 branch
14:28 symx thanks babilen. I'll look into it!
14:30 babilen symx: https://www.refheap.com/119981
14:30 babilen symx: That way you can easily refer to different networks (identified by CIDR) and get this information on all minions
14:30 menglish joined #salt
14:31 babilen symx: Just target those mine function aliases in pillar, run "mine.update" and you are good to go. It also spares you the need to hardcode interfaces which you really don't want to do.
14:31 babilen mage_: I'd hope soon
14:33 permalac joined #salt
14:33 nmadhok joined #salt
14:34 toastedpenguin joined #salt
14:37 flowstate joined #salt
14:37 Shirkdog joined #salt
14:40 flowstate joined #salt
14:43 flowstate joined #salt
14:43 DanSlimmon joined #salt
14:50 knine joined #salt
14:50 spuder joined #salt
14:50 flowstate joined #salt
14:52 heewa joined #salt
14:53 heewa left #salt
14:53 komputes joined #salt
14:54 heewa joined #salt
14:54 heewa left #salt
14:54 heewa joined #salt
14:56 kus joined #salt
14:59 mher718 joined #salt
14:59 mher718 hi
15:01 ldelossa joined #salt
15:02 ldelossa Hey guys, I'm curious if anyone could review my blog post about salt stack
15:02 ldelossa I'm not trying to plug, I just want to make sure the way I went about something, is best practices
15:02 mher718 can anyone help with writing a salt-state for this pillar
15:02 mher718 freeradius:    devices:      - client: 172.16.xxx.xxx        secret: secretpasswd        name: router1    users:      - username: user1        password: abcde12345      - username: user2        password: hijkl67890
15:02 ldelossa @mher718 paste it in hastebin.com
15:03 impi joined #salt
15:04 mher718 @ldelossa ok noted and thanks
15:04 mher718 http://hastebin.com/gililasizu.sm
15:06 mher718 basically i will call the pillar date to this format
15:06 mher718 http://hastebin.com/azahiqoven.apache
15:06 mher718 i need the user and password
15:07 ldelossa You're creating a list of dictionaries under devices
15:07 catpig joined #salt
15:07 ldelossa Which maybe a little harder to use
15:07 mher718 hmmm...
15:07 ldelossa soooo
15:07 ldelossa hold on
15:07 mher718 how about for the users ??
15:08 mher718 actually, if i get the logic on the users part... i may have a chance of creating for the devices part
15:09 toastedpenguin joined #salt
15:09 mher718 here's for the devices part => http://hastebin.com/atidugujew.hs
15:10 mher718 i've trying a lot lately but still fails with salt-call, i do get the whole thing on the salt-state config on the minion end  :(
15:10 ldelossa Okay so I think for the second part you can do something like
15:11 jakshi joined #salt
15:11 ldelossa {% for user, password in salt['pillar.get]'('freeradius:users:).iteritems())
15:11 mher718 i mean i do get the whole code from the salt-state... on the minion end... for example on /etc/freeradius/users
15:11 ldelossa remove that last : on users
15:11 ldelossa That firs part, if you remove the list indication you can target everything by name
15:12 mher718 actually, you can check my codes from here => https://github.com/elmeramigleo/saltstack
15:12 ldelossa freeradius:devices:client
15:12 rhand joined #salt
15:12 martoss left #salt
15:12 ldelossa Where are you using the users pillar
15:14 mher718 .. /etc/freeradius/users
15:15 mher718 ahh.. sorry, the users pillar are for local users
15:15 mher718 ssh login
15:16 mher718 actually, the users pillar.. i just test it base from reading
15:16 mher718 like, read.. then apply to test machine
15:17 mher718 to be honest, i am on the learning level with saltstack.. that's why i try to apply what i am reading/researching
15:25 tapoxi joined #salt
15:25 iggy don't write new code with iteritems()
15:28 brotatochip joined #salt
15:29 mher718 ??
15:29 iggy there was a suggestion above to use iteritems()... don't
15:30 mher718 ok, so what should i do/use?
15:30 tristianc_ joined #salt
15:31 mher718 here
15:31 mher718 here's my pillar data => http://hastebin.com/gililasizu.sm
15:31 iggy {% for user in salt['pillar.get']('freeradius:users') %}
15:31 mher718 i need to parse the user and password to be used here => http://hastebin.com/azahiqoven.apache
15:32 iggy and then reference the data via {{ user['username'] }} {{ user['password'] }} etc
15:32 mher718 ok..
15:33 mher718 for this part => {{ username }} MD5-Password := "{{ 'password }}"
15:33 mher718 {{ user['username'] }} MD5-Password := "{{ user['password'] }}"
15:33 iggy looks good
15:33 mher718 did i understand it correctly?
15:34 mher718 ok, will try to commit this code and see if will do the magic.. thanks by the way :)
15:34 ageorgop joined #salt
15:35 heewa I've used salt-bootstrap to install in Ubuntu 14.04. I want to try a version from my fork, where I'm working on a fix. Do I need to uninstall salt first, or can I install my version right on top?
15:35 iggy bonus points for setting up a repo with all your files... make for a pretty easy to navigate example
15:35 iggy (I did the same thing when I was starting out with salt)
15:36 iggy heewa: depends, did you install packages via salt-bootstrap or from git?
15:37 heewa I'm not sure what "packages" means, but I used salt-bootstap to install the latest release initially, and now I'm thinking of using the bootstrap to install my version from git
15:37 iggy what exact command line args did you use to install the first time?
15:37 cyborg-one joined #salt
15:38 iggy are there deb or rpm packages of salt installed?
15:38 mher718 @iggy i still get this => http://hastebin.com/ivogebapis.vhdl
15:38 iggy (or whatever your distro uses)
15:39 heewa iggy: `curl -L https://bootstrap.saltstack.com | sudo sh -s -- -P git v2016.3.0`
15:39 iggy mher718: lol, add `- template: jinja` to the file.managed
15:39 iggy heewa: then you should be okay to just install your fork
15:39 heewa Thanks! :)
15:44 mher718 geez.. i wonder why - template: jinja got lost
15:45 mher718 @ iggy It worked!!!
15:45 mher718 many thanks!! :D
15:46 cyborg-one joined #salt
15:48 cyborg-one joined #salt
15:50 iggy np
15:52 bltmiller joined #salt
16:01 cableninja joined #salt
16:05 mher718 the same with clients.conf, it's finally working
16:05 mher718 again, thanks a lot @iggy
16:06 mher718 you are my saviour to this saltstack stuff :)
16:07 Miouge joined #salt
16:07 jfindlay iggy ftw
16:08 onlyanegg joined #salt
16:09 iggy another satisfied customer ;)
16:09 hasues joined #salt
16:09 hasues left #salt
16:13 rhodgin joined #salt
16:15 menglish joined #salt
16:21 BadgerOps joined #salt
16:30 writtenoff joined #salt
16:30 BadgerOps morning! Does anyone in here have salt-cloud vmware + windows experience? Having a network issue.
16:31 RandyT BadgerOps: salt-cloud + windows
16:32 BadgerOps yeah, using the vmware connector, but network is not being attached on boot
16:32 BadgerOps added connected: True and startConnected: True to the network: part of the config, no dice
16:33 RandyT BadgerOps: probably vmware specific. I have plenty experience with that scenario in AWS, but not much to add on vmware side
16:34 BadgerOps yeah, looking at the debug output I can see where I *think* I need to add a setting, but it makes no difference, was hoping maybe someone in here also has had that issue. :D
16:34 brotatochip joined #salt
16:34 scottk_ joined #salt
16:36 scottk_ does anyone know how to use file.search in jinja? I'm trying to search a file for a string to see if it is there or not, but it's not working the way i intend. {% if salt['file.search']('/file/path', 'string to search for') %}
16:36 RandyT BadgerOps: not sure if there is any similarity, but here is what I need to do in AWS https://gist.github.com/rterbush/cd7493352cbe1a3badb74a4c3d8bb150
16:37 BadgerOps RandyT Thanks! Yeah, https://gist.github.com/BadgerOps/19feebfbe2fae4dcb3602ffec477984c is what mine looks like.
16:39 edrocks joined #salt
16:39 jfindlay scottk_: what are you expecting, and what do you get with that?
16:40 scottk_ @jfinlay, if it returns false, I want to run file.append.
16:40 scottk_ I'm editing the /etc/sudoers file, and only want to change it if a certain line is not found.
16:40 babilen scottk_: That's how file.append works by default
16:41 flowstate joined #salt
16:41 jfindlay scottk_: have you verified the logic with a local grep, for example: `grep 'string to search for' /file/path`?
16:41 babilen scottk_: You might also want to consider using https://github.com/saltstack-formulas/sudoers-formula/
16:41 jad_jay joined #salt
16:41 babilen scottk_: file.append won't add a line over and over again (or are you checking for a different line than the one you are adding?)
16:41 jfindlay or babilen's suggestions are even better :)
16:42 babilen Well .. it depends :D
16:42 scottk_ No i'm not checking for a different line. I thought append would append automatically.
16:42 scottk_ that seems like a great solution. didn't know that's how file.append worked. Thanks guys!
16:42 babilen scottk_: Generally speaking I would cut down on the "if foo is like bar, then baz" and increase definite solutions (the "/etc/sudoders looks like XXX and not different" approach)
16:43 Trauma joined #salt
16:43 babilen scottk_: Generally all states check if what they want to achieve has been achieved already and won't do anything if that's the case
16:44 scottk_ awesome. thanks again. Love having this channel available.
16:44 gh34 joined #salt
16:44 babilen sudoers-formula combined with suitable pillar data (or the users-formula) might be a better approach still
16:44 iggy the declarative way(TM)
16:44 UtahDave joined #salt
16:44 flowstate joined #salt
16:44 scottk_ The only problem with the sudoers-formula is that I don't want to manage the file with salt.
16:45 scottk_ I wish i could, but that got shut down by my manager. :/
16:45 babilen What kind of line are you adding now?
16:45 babilen And why ... ah .. manager
16:45 babilen So you "manage it a little" ? ;)
16:45 scottk_ #intern.
16:45 babilen hehe
16:46 iggy I can sympathize... we're in the midst of replacing (basically nothing) with salt
16:46 iggy so we have so many thing we can't just straight up completely manage with salt
16:47 scottk_ iggy. i feel your pain. haha
16:47 babilen As if things wouldn't be hard enough to solve the technical issues
16:47 iggy makes me sad... my last job was a from scratch salt deploy
16:47 bltmiller joined #salt
16:48 flowstate joined #salt
16:48 jfindlay the best jobs are where everybody can't wait to salt all the things
16:49 jfindlay which I'm lucky enough to have :)
16:50 iggy funny thing is I interviewed at the last job and they were trying to setup puppet and all these other tools to do what salt could do... I said so in the interview... by the time I started they had switched to salt
16:50 iggy (and by switched, I mean installed salt and left it all for me to do)
16:50 babilen Now, isn't that nice?
16:51 iggy I was certainly happy I didn't have to use puppet
16:51 flowstate joined #salt
16:54 cyborg-one joined #salt
16:55 om joined #salt
16:58 s_kunk joined #salt
16:58 toanju joined #salt
17:00 rgrinberg joined #salt
17:02 mekhami Hi, I'm looking into salt as a solution for my server management. Little background, my company's running about 10 ubuntu servers, a few for web, a few for utilities, a couple for search, etc. What I want to know is, should I set up a new machine as a salt master, dedicated to running that? Is it even necessary to have a salt master machine in this case, or can I just run all of that stuff locally at the
17:02 mekhami moment?
17:03 gtmanfred you can do any of those things
17:03 mekhami what would be the lowest barrier of entry for me
17:03 gtmanfred depends on how you want to manage it, having a central point to manage all the servers is certainly helpful
17:03 Eugene mekhami - I run Salt on my "management" machine, which is also my Nagios server, VPN server, shell server, etc
17:03 mekhami I need to deploy an app in the next few days, so it'd be nice if I could learn salt alongside
17:03 babilen mekhami: You can use masterless, a salt master or salt-ssh .. it really depends on your needs. Would setting up a master be problematic for you?
17:04 mekhami babilen: i don't think it'd be problematic. I'd be setting up an amazon ec2 instance for it i guess.
17:04 mekhami i'm not a sysadmin, i'm just forced to learn all this stuff cause i'm the only one here =P
17:04 gtmanfred :)
17:04 gtmanfred I would say start with the salt master
17:04 babilen It definitely is the standard approach
17:04 mekhami okay.
17:05 mekhami Eugene: i like your approach as well, running it on a management box.
17:05 mekhami i'll look into consolidating all my other stuff to that salt master.
17:06 mekhami out of curiosity, anyone have experience deploying django applications using salt? I'd love to have more information on that to read before i get started
17:06 gtmanfred there is a django salt formula that might be usefull to look at as you get started https://github.com/saltstack-formulas/django-formula
17:07 mekhami perfect thank you
17:07 gtmanfred with some documentatino about formulas https://docs.saltstack.com/en/latest/topics/development/conventions/formulas.html
17:08 gtmanfred mekhami: also, here is our getting started guide, with some guided tutorials for learning the beginnings of salt https://docs.saltstack.com/en/getstarted/
17:15 flowstate joined #salt
17:16 ashwani_ joined #salt
17:17 bltmiller joined #salt
17:19 ashwani_ hi everyone, i am new here!
17:20 flowstate joined #salt
17:20 abednarik joined #salt
17:20 babilen ashwani_: Welcome!
17:21 ashwani_ babilen : thanks! :)
17:21 onlyanegg joined #salt
17:21 _JZ_ joined #salt
17:22 ashwani_ i wanted to know if a beginner in open-source contribution can get started for saltstack!
17:23 impi joined #salt
17:23 punkoivan joined #salt
17:24 glickind joined #salt
17:24 komputes joined #salt
17:30 glickind Hi, which transport do you recommand to scale beyond 10,000 VMs ZMQ, TCP or RAET ?
17:31 flowstate joined #salt
17:33 dyasny joined #salt
17:34 babilen tcp
17:35 fracklen joined #salt
17:35 UtahDave ashwani_: Yeah, a beginner can definitly get involved with SaltStack. We're glad you're here!
17:36 ashwani_ UtahDave : thanks! Can you point me to sources that can help me get started?
17:37 UtahDave ashwani_: well, first I'd recommend reading through and doing the examples in the tutorials here: https://docs.saltstack.com/en/latest/
17:37 UtahDave Is there a particular part of Salt that you're interested in working on?
17:39 barmaley joined #salt
17:39 flowstate joined #salt
17:42 ashwani_ @UtahDave : i won't be able to tell you that as all this is new to me!
17:42 ashwani_ but i am ready to learn whatever stuff would be required.
17:43 s_kunk joined #salt
17:43 DanSlimmon ashwani_ I've been diving into the codebase by scrolling through the GitHub issues page https://github.com/saltstack/salt/issues and finding bugs that look relatively straightforward to fix
17:44 [Kernel_Panic] i have 49 Nodes with a tag, i need "Stop" all of this group. How to make a group for Salt-cloud ?
17:45 UtahDave ashwani_: start with going through a few of those tutorials. Fixing any errors in the documentation is a great way to get started
17:46 ageorgop joined #salt
17:46 ashwani_ DanSlimmon UtahDave : thanks!
17:47 UtahDave ashwani_: you're welcome!  Let us know if you have any questions as you get started
17:48 menglish joined #salt
17:50 bltmiller is there any easy way with salt to trace what my jinja template is doing exactly?
17:52 UtahDave state.show_sls  should show you what the final output will
17:52 UtahDave also, if you run the salt-minion in a terminal in debug mode you'll often see any stacktraces or errors that are happening
17:53 bltmiller aye, but that shows me the end result of what jinja spits out. I'm walking lists/dictionaries with jinja and I suspect an error in that logic and I'd like to see exactly what my loops are walking
17:56 glickind thanks babilen
17:56 Guest76557 joined #salt
17:58 UtahDave bltmiller: that's a bit trickier. I usually will output the whole data structure so i can look at it.
17:59 woodtablet joined #salt
17:59 bltmiller UtahDave: yeah, that's what I feared lol. setting that up now, just wondering if there was an easier way to inspect it all. thanks anyway!
18:02 punkoivan joined #salt
18:03 manji joined #salt
18:05 s0undt3ch joined #salt
18:07 ceedon joined #salt
18:09 ahammond guys where would I find docs on Thorium?
18:09 ahammond I found https://docs.saltstack.com/en/latest/topics/thorium/index.html but... is there more?
18:10 noraatepernos joined #salt
18:10 lilvim joined #salt
18:13 noraatepernos left #salt
18:16 twork_ still browsing the new get started docs tree, but i have to sound a big thanks to the team what wrote it.
18:18 twork_ if i'd had this a year ago i'd be about two years and many grey hairs younger.
18:18 s0undt3ch joined #salt
18:21 om joined #salt
18:21 om2 joined #salt
18:22 Guest12872 joined #salt
18:22 menglish joined #salt
18:22 winsalt joined #salt
18:23 ceedon joined #salt
18:24 om2 joined #salt
18:29 komputes joined #salt
18:30 edrocks joined #salt
18:30 noraatepernos joined #salt
18:31 shoemonkey joined #salt
18:34 ceedon joined #salt
18:36 bltmiller joined #salt
18:37 nmadhok joined #salt
18:37 saltstackmatt joined #salt
18:38 woodtablet anyone try this ? https://docs.saltstack.com/en/getstarted/fundamentals/install.html
18:39 jerematic joined #salt
18:39 teryx510 joined #salt
18:41 subsignal joined #salt
18:43 woodtablet i am trying out this new cool salt-master, salt-minion demo. and i am at step 2, and its not working. but i have seen this in my prod environment too and want to dig in. how is it not working ? i am not getting results from > salt '*' test.ping. it says either salt request times out, master is not responding, or minion did not return [ Not connected ]. there has been no changes since the vagrant up. I did try restarting the master and minion,
18:44 woodtablet http://pastebin.com/VN5SYnjJ
18:49 paydro joined #salt
18:49 watersoul joined #salt
18:52 ajw0100 joined #salt
18:52 paydro joined #salt
18:54 mikecmpbll joined #salt
18:56 paydro joined #salt
19:01 paydro joined #salt
19:09 Heartsbane joined #salt
19:09 Heartsbane joined #salt
19:10 cro joined #salt
19:10 numkem joined #salt
19:11 rim-k joined #salt
19:12 drawsmcgraw I passed an empty string to pillar.get() as the default but it returned 'None' instead of an empty string.
19:12 drawsmcgraw Is there a way for pillar.get() to return an empty string as a default?
19:13 drawsmcgraw This is in a Jinja template, a la foo = salt['pillar.get']('bar', '')
19:15 drawsmcgraw wait, nm... I can just have my shell script respond to 'None' (or some other more meaningful default)
19:15 LordOfLA joined #salt
19:16 menglish joined #salt
19:16 mpanetta joined #salt
19:17 mpanetta joined #salt
19:17 tracphil joined #salt
19:18 deniszh joined #salt
19:19 babilen drawsmcgraw: That would return an empty string, but it *might* be that the call to genuinely returns None
19:19 babilen s/to//
19:19 babilen (so no fallback is needed)
19:20 drawsmcgraw babilen: Yeah *something* internal is deciding "I was not given a value, so I'll return None"
19:20 drawsmcgraw I tested with just passing in a single space as a default, and I still got 'None' back
19:21 drawsmcgraw It's okay. I shouldn't be relying on the default nature of an abstraction anyway. I should be defining my own values/conditions.
19:22 BadgerOps pretty sure that is a built in - if there is no value, return None - thats the pythonic way at least. Better to have a known "None" than an unknown " "
19:22 Trauma joined #salt
19:24 BadgerOps woodtablet: do a 'vagrant status' in that directory
19:25 babilen drawsmcgraw: Is "foo" defined in the pillar?
19:25 babilen (or rather: how/where do you define it?)
19:25 drawsmcgraw babilen: It's not. I'm defining additional Pillar values on the fly in a Jenkins job
19:26 drawsmcgraw to toggle a particular behavior
19:26 drawsmcgraw It works now, though. I just default to 'False', then the shell script knows that if some env variable is 'False', then don't do The Thing.
19:26 babilen Are you sure that the key is undefined and not only that it doesn't have a value? What does "salt 'foo' pillar.get bar" give you?
19:27 drawsmcgraw This particular Pillar key definitely isn't defined elsewhere. Only on a per-run basis in a Jenkins job.
19:27 brew joined #salt
19:27 babilen You shouldn't be getting "None", but the empty string there *unless* the value of "bar" is genuinely None
19:27 drawsmcgraw Interesting... this merits more reasearch, in that case
19:29 felskrone joined #salt
19:36 MindDrive joined #salt
19:39 MadHatter42 joined #salt
19:44 LordOfLA joined #salt
19:46 mpanetta_ joined #salt
19:47 paydro joined #salt
19:49 toastedpenguin joined #salt
19:50 mpanetta joined #salt
19:54 LordOfLA joined #salt
19:57 brotatochip joined #salt
19:57 paydro Hello! I’m trying to setup a salt master in an EC2 Auto Scaling Group with one instance. Does anyone have links or recommendations on how to persist minion keys between failed instances?
20:04 flowstate joined #salt
20:04 rgrinberg joined #salt
20:06 woodtablet BadgerOps : I see master and the 2 minions running
20:07 BadgerOps vagrant ssh into the minions and 'sudo service salt-minion status' - maybe they arent running?
20:07 BadgerOps in which case, 'sudo service salt-minion restart'
20:07 woodtablet BadgerOps: they are, and I did that
20:08 woodtablet BadgerOps: I do it again, but did you see the error in the pastebin link on the master?
20:08 BadgerOps and on the master 'salt-key' - does it show the keys as accepted?
20:08 woodtablet BadgerOps: yep, I see both minions under keys accepted
20:08 teryx510 joined #salt
20:09 BadgerOps ah, I missed your pastebin link. Restart salt-master on the master?
20:09 woodtablet BadgerOps: Thats the error I get after restart. this is a fresh vagrant instance / github download
20:09 woodtablet BadgerOps: I have never run this demo before
20:10 BadgerOps interesting, I havent used that demo before, let me try it out real quick and see if I can replicate the issue
20:12 shoemonkey joined #salt
20:13 woodtablet BadgerOps: Ya, I want to see if I am the only one. I just did git clone; cd into the clone; and vagrant up
20:13 teryx510 joined #salt
20:15 gimpy2938 So I'm upgrading Salt and numerous minions decided to completely fuck up ... I'm now trying to find which ones are still down but `salt '*' test.ping` hangs after showing nodes that did respond and now just sits there, what do?
20:15 woodtablet wait
20:16 woodtablet in about 60 seconds you will see all the clients that didnt respond
20:16 gimpy2938 woodtablet: been sitting for over 10 minutes
20:16 BadgerOps a better way is to use 'salt-run'
20:17 BadgerOps 'salt-run manage.down' will show all down hosts
20:17 woodtablet gimpy2938: whoa, thats a while. and i was googling what Badger just said
20:18 gimpy2938 BadgerOps: also hangs ... spit out "Found minion id..." and nothing else so far
20:23 protoz joined #salt
20:28 gimpy2938 ok, salt-run is hanging with "Checking whether jid 20160606132520764383 is still running";
20:29 gimpy2938 how do I tell Salt to forget about the job?
20:29 rvandegrift joined #salt
20:31 BadgerOps joined #salt
20:31 west575 joined #salt
20:32 BadgerOps hey woodtablet: sorry - forgot I already had a ton of vagrant stuff running and found just how many more were required to make the ol laptop fall over. Hint: it was 3 :)
20:32 woodtablet BadgerOps: Lol, I was wondering what happened
20:33 BadgerOps I kinda forgot the 12 other VM's that were running
20:39 ceedon @gimpy2938 have you looked at saltutil?
20:39 cableninja_ joined #salt
20:46 BadgerOps joined #salt
20:46 BadgerOps joined #salt
20:46 BadgerOps woodtablet: worked fine for me, maybe vagrant destroy -f and re- vagrant up?
20:49 woodtablet ok
20:50 woodtablet BadgerOps: Destorying
20:50 BadgerOps cool
20:50 racooper will the packages in the SLE_11_SP4 repo work on SP3? I've still got about 130 SLES 11SP3 servers to manage....
20:50 rvandegrift anyone using the scheduler on masterless minions in 2016.3?  something is unhappy with me: https://gist.github.com/rvandegrift/a135ead4ae75d622881c66225396e4a4
20:51 eckod joined #salt
20:51 rim-k joined #salt
20:52 eckod hey guys, im wondering if something like this is possible: `salt '*' cmd.run 'hostname {{ grain.get id }}'`
20:52 ajw0100 joined #salt
20:54 aniraj joined #salt
20:54 woodtablet eckod: what are you trying to do ?  why not just do the grain call by itself ?
20:55 eckod woodtablet: trying to set hostnames based on the minion id without having to write a state or read the minion_id file.
20:56 mpanetta_ joined #salt
20:57 adelcast joined #salt
20:58 mpanett__ joined #salt
20:59 fracklen joined #salt
21:01 woodtablet eckod: i would do it in a state file, because, i dont know how to do mix grain commands and commands called on the shell at run time without a script, but someone else might know
21:03 obimod joined #salt
21:03 adelcast not sure if there are any saltstack developers lurking around, but seems like the HTTP interface to download Salt's 2016.3 package via pypi is broken
21:04 adelcast http://pypi.python.org/packages/source/s/salt/salt-2016.3.0.tar.gz  doesn't work
21:04 adelcast http://pypi.python.org/packages/source/s/salt/salt-2015.8.0.tar.gz do work
21:04 adelcast (I am bulding the OpenEmbedded packages for 2016.3 and need the http interface to get the package via pypi)
21:05 deniszh joined #salt
21:06 obimod hey all -- just want to ping you guys per a digitalocean server serving bootstrap.sh (by default i think) the SSL cert is showing as invalid and it may need to be hardened a bit more as it's showing OS version/ssl version (http://pastebin.com/yhRYswcp )
21:06 obimod thought I was serving the bootstrap.sh locally per salt Vagrantfile provisioning but i guess it's not working out right meow
21:07 obimod (invalid per a name mismatch)
21:14 brotatochip joined #salt
21:18 noraatepernos joined #salt
21:18 flowstate joined #salt
21:19 manji joined #salt
21:20 woodtablet BadgerOps: I gotta run to the dr, i ll be back tomorrow to do the vagrant up if yo uare still curious, thanks for trying it too
21:20 BadgerOps sure, I'll probably be hanging out.
21:20 woodtablet left #salt
21:23 pug joined #salt
21:24 cableninja__ joined #salt
21:24 _JZ_ joined #salt
21:25 om joined #salt
21:26 om2 joined #salt
21:26 teryx5101 joined #salt
21:27 paydro joined #salt
21:28 Guest58723 left #salt
21:31 Guest54604 Q: Can a master node pass commands to itself if itself is also a minion?
21:32 rim-k joined #salt
21:32 lero joined #salt
21:35 potens joined #salt
21:38 tracphil joined #salt
21:39 mikecmpbll joined #salt
21:45 aharvey joined #salt
21:46 aharvey Noticing some openstack-built ubuntu VMs are not setting domain as a grain value.  Anyone available to ELI5 how this should work?  I’m using the same image, same master
21:46 teryx510 joined #salt
21:47 teryx510 joined #salt
21:50 rgrinberg joined #salt
21:53 menglish joined #salt
21:54 Tyrm_ joined #salt
21:55 flowstate joined #salt
21:55 _JZ_ joined #salt
21:58 manji joined #salt
22:00 mpanetta joined #salt
22:01 ajw0100 joined #salt
22:06 abednarik joined #salt
22:06 XenophonF joined #salt
22:11 cableninja joined #salt
22:13 nmadhok joined #salt
22:31 RandyT greetings
22:31 RandyT anyone have any hints as to how to use boto_rds state and specify storage_type?
22:32 RandyT appears boto_rds state doesn't currently support this parameter and not finding support for it in the boto rds2 implementation on my centos boxes
22:33 RandyT end result of useing boto_rds state is that I end up with magnetic storage
22:33 mikecmpbll joined #salt
22:37 brew joined #salt
22:37 RandyT If @Ryan_Lane  is around, any insight on this? https://github.com/boto/boto/pull/2794
22:37 saltstackbot [#2794]title: Exposed RDS storage types and bumped API version. | This is to expose the storage type attribute in RDS methods that allow this to be set.
22:39 ajw0100 joined #salt
22:39 RandyT that issue pretty much sums up the spot I am in along with the others. Made the minimal change to boto_rds state to support the additional parameters, just need boto to come through. :-)
22:40 Ryan_Lane yeah
22:40 Ryan_Lane good luck there
22:40 Ryan_Lane boto is the worst
22:40 Ryan_Lane they basically don't maintain it now
22:40 RandyT :-) not encouraging
22:40 Ryan_Lane we should start migrating modules to boto3 where possible
22:40 RandyT what are our options?
22:40 RandyT ok...
22:40 Ryan_Lane because boto3 is properly supported by amazon
22:41 Ryan_Lane whereas boto was a volunteer maintained project
22:41 Ryan_Lane (boto3 is also usually way nicer to use)
22:41 Ryan_Lane you can use boto3 and boto together in the same code
22:41 RandyT ok, thanks for the input Ryan_Lane
22:41 RandyT will go off and see what it takes to migrate a state.
22:41 Ryan_Lane so, for these features you can include boto3 and use it for the newer features
22:42 Ryan_Lane should only need to do that in the execution module
22:42 Ryan_Lane for the most part we don't call boto directly in the state modules
22:42 Ryan_Lane but we call our execution modules from the state modules
22:42 RandyT ok, thanks for that hint
22:42 Ryan_Lane yw
22:44 abednarik joined #salt
22:50 jeddi joined #salt
22:55 mikecmpbll joined #salt
22:58 brotatochip joined #salt
23:03 mohae_ joined #salt
23:04 jeddi joined #salt
23:04 flowstate joined #salt
23:17 yuhlw joined #salt
23:21 noraatepernos joined #salt
23:22 GreatSnoopy joined #salt
23:22 shoemonkey joined #salt
23:31 my50c /cl/clear
23:37 Vaish joined #salt
23:38 Vaish Hi everybody! I am new to salt. I have been trying to find what exactly is meant by a .saltrc file. Can somebody tell me what it is and its purpose?
23:38 Vaish Any help is much appreciated!
23:41 tracphil joined #salt
23:43 fracklen joined #salt
23:47 paydro_ joined #salt
23:50 jfindlay Vaish: did you mean saltfile: https://docs.saltstack.com/en/latest/topics/ssh/#define-cli-options-with-saltfile?
23:50 jfindlay I don't know anything about a saltrc file
23:50 paydro_ joined #salt
23:51 jfindlay hmm, looks like there may be support for an xdg_dir saltrc and ~/.saltrc
23:52 jfindlay 0e9d9ab7ac5784d183cc6736abd82f9554bb7105
23:52 Vaish Is that something old and is no longer supported?
23:52 paydro joined #salt
23:53 jfindlay https://github.com/saltstack/salt/pull/13398
23:53 saltstackbot [#13398]title: fix xdg directory | before this, there is a / between the . and the file for ~/.saltrc, so it checks...
23:53 jfindlay I would say undocumented rather than unsupported
23:53 Vaish cool. Thanks a lot for the pointer @jfindlay..
23:55 jfindlay sure
23:55 jfindlay we should get that documented

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