Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2016-12-10

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

All times shown according to UTC.

Time Nick Message
00:00 pipps joined #salt
00:04 pipps99 joined #salt
00:05 pipps joined #salt
00:06 pipps_ joined #salt
00:08 pipps__ joined #salt
00:09 pipps99 joined #salt
00:10 pipps joined #salt
00:11 amontalban joined #salt
00:11 amontalban joined #salt
00:12 fridec9 joined #salt
00:13 fridec9 Hi all.  Have a question.  Looking to do dynamic minion key acceptance as long as the node is in the same AWS VPC as the master.  Would like to have the reactor fire off a quick boto call to the AWS API to check and return
00:13 fridec9 Is this possible with the reactor system?
00:14 onlyanegg joined #salt
00:16 pipps joined #salt
00:17 pipps99 joined #salt
00:19 pipps_ joined #salt
00:19 onlyaneg1 joined #salt
00:20 pipps__ joined #salt
00:21 pipps___ joined #salt
00:22 pipps joined #salt
00:23 fridec9 Anyone automating minion key acceptance?/
00:24 cliluw joined #salt
00:25 pipps99 joined #salt
00:26 pipps_ joined #salt
00:27 pipps joined #salt
00:28 jas02 joined #salt
00:28 pipps__ joined #salt
00:29 cyteen joined #salt
00:30 pipps99 joined #salt
00:32 pipps joined #salt
00:32 pipps_ joined #salt
00:36 pipps joined #salt
00:36 Trauma joined #salt
00:37 pipps99 joined #salt
00:38 pipps_ joined #salt
00:39 pipps__ joined #salt
00:40 pipps___ joined #salt
00:41 pipps joined #salt
00:42 jas02_ joined #salt
00:42 pipps99 joined #salt
00:44 pipps_ joined #salt
00:48 pipps joined #salt
00:49 pipps99 joined #salt
00:52 pipps_ joined #salt
00:53 pipps joined #salt
00:54 pipps__ joined #salt
00:57 pipps99 joined #salt
00:57 hemebond fridec9: yes
00:58 pipps_ joined #salt
00:58 hemebond A bit different but this is my current setup https://gist.github.com/hemebond/4b48df43721adb283e0df404501a4b59
00:58 pipps joined #salt
01:00 pipps__ joined #salt
01:03 pipps joined #salt
01:04 pipps99 joined #salt
01:07 amontalban joined #salt
01:07 amontalban joined #salt
01:07 fracklen joined #salt
01:08 bltmiller joined #salt
01:08 pipps joined #salt
01:10 twiedenbein joined #salt
01:11 pipps_ joined #salt
01:13 pipps joined #salt
01:14 lws joined #salt
01:15 pipps99 joined #salt
01:18 pipps_ joined #salt
01:19 pipps joined #salt
01:20 pipps__ joined #salt
01:22 pipps99 joined #salt
01:24 pipps joined #salt
01:24 lws joined #salt
01:26 pipps_ joined #salt
01:27 pipps99 joined #salt
01:28 pipps joined #salt
01:30 DEger joined #salt
01:32 pipps99 joined #salt
01:33 pipps_ joined #salt
01:35 pipps joined #salt
01:36 pipps__ joined #salt
01:38 pipps99 joined #salt
01:38 fridec9 hemebond: thanks!
01:38 pipps_ joined #salt
01:41 pipps joined #salt
01:41 jenastar joined #salt
01:43 pipps99 joined #salt
01:43 jas02 joined #salt
01:44 pipps_ joined #salt
01:47 pipps joined #salt
01:49 pipps99 joined #salt
01:51 pipps_ joined #salt
01:54 pipps joined #salt
01:54 pipps99 joined #salt
01:55 pipps_ joined #salt
01:58 jas02 joined #salt
01:58 pipps__ joined #salt
01:59 pipps joined #salt
02:01 pipps99 joined #salt
02:02 fracklen joined #salt
02:04 pipps__ joined #salt
02:05 pipps joined #salt
02:07 pipps99 joined #salt
02:09 pipps_ joined #salt
02:09 catpigger joined #salt
02:10 pipps__ joined #salt
02:11 pipps joined #salt
02:11 pipps___ joined #salt
02:12 pipps99 joined #salt
02:14 mavhq joined #salt
02:14 pipps_ joined #salt
02:18 pipps joined #salt
02:19 DEger joined #salt
02:20 pipps99 joined #salt
02:21 pipps_ joined #salt
02:23 onlyanegg joined #salt
02:23 onlyaneg1 joined #salt
02:26 pipps joined #salt
02:27 pipps99 joined #salt
02:28 pipps_ joined #salt
02:30 pipps__ joined #salt
02:32 pipps joined #salt
02:33 pipps99 joined #salt
02:38 pipps joined #salt
02:38 pipps99 joined #salt
02:41 pipps_ joined #salt
02:46 pipps__ joined #salt
02:46 jas02 joined #salt
02:46 pipps joined #salt
02:48 ilbot3 joined #salt
02:48 Topic for #salt is now Welcome to #salt! <+> Latest Versions: 2016.3.4, 2016.11.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
02:51 pipps joined #salt
02:52 pipps99 joined #salt
02:53 pipps_ joined #salt
02:53 pipps__ joined #salt
02:54 pipps___ joined #salt
02:58 pipps joined #salt
02:59 pipps99 joined #salt
03:00 pipps_ joined #salt
03:00 aidin joined #salt
03:07 cyteen joined #salt
03:09 pipps joined #salt
03:09 pipps99 joined #salt
03:11 pipps_ joined #salt
03:12 pipps__ joined #salt
03:14 pipps joined #salt
03:15 pipps99 joined #salt
03:15 amontalban joined #salt
03:15 amontalban joined #salt
03:16 pipps___ joined #salt
03:18 pipps_ joined #salt
03:19 pipps__ joined #salt
03:21 DEger joined #salt
03:21 pipps joined #salt
03:23 pipps99 joined #salt
03:24 pipps_ joined #salt
03:25 pipps__ joined #salt
03:26 Sammichmaker joined #salt
03:27 pipps joined #salt
03:28 pipps99 joined #salt
03:30 pipps_ joined #salt
03:31 pipps__ joined #salt
03:34 pipps joined #salt
03:34 aidin joined #salt
03:34 yuhl_ joined #salt
03:35 pipps99 joined #salt
03:36 bastiandg joined #salt
03:36 pipps___ joined #salt
03:36 mswart joined #salt
03:37 TRMander1on joined #salt
03:37 jcristau_ joined #salt
03:37 pezus__ joined #salt
03:37 nrezinor1 joined #salt
03:37 Corey_ joined #salt
03:37 mirko_ joined #salt
03:37 kgoetz_ joined #salt
03:37 MajObvio1sman joined #salt
03:37 Straphka joined #salt
03:37 kleszcz_ joined #salt
03:37 chmod6661rg joined #salt
03:37 jeblair_ joined #salt
03:38 jamesog_ joined #salt
03:38 tooth_ joined #salt
03:38 pipps_ joined #salt
03:39 simmel joined #salt
03:39 dijit- joined #salt
03:41 pipps joined #salt
03:42 pipps99 joined #salt
03:42 tom29739 joined #salt
03:45 Zachary_DuBois joined #salt
03:47 pipps joined #salt
03:48 pipps99 joined #salt
03:50 pipps_ joined #salt
03:50 fracklen joined #salt
03:51 pipps__ joined #salt
03:52 pipps___ joined #salt
03:53 pipps joined #salt
03:55 pipps99 joined #salt
03:56 pipps_ joined #salt
03:59 pipps joined #salt
04:00 pipps99 joined #salt
04:02 darthzen joined #salt
04:03 pipps_ joined #salt
04:03 pipps__ joined #salt
04:04 pipps joined #salt
04:05 pipps99 joined #salt
04:07 pipps___ joined #salt
04:08 pipps_ joined #salt
04:09 pipps joined #salt
04:10 pipps99 joined #salt
04:12 pipps__ joined #salt
04:13 pipps___ joined #salt
04:16 pipps joined #salt
04:17 pipps99 joined #salt
04:18 pipps_ joined #salt
04:19 pipps__ joined #salt
04:20 pipps___ joined #salt
04:21 pipps joined #salt
04:24 pipps99 joined #salt
04:25 pipps_ joined #salt
04:27 pipps joined #salt
04:27 lompik joined #salt
04:29 jas02 joined #salt
04:29 pipps99 joined #salt
04:31 bocaneri joined #salt
04:31 pipps_ joined #salt
04:34 pipps joined #salt
04:35 pipps99 joined #salt
04:36 pipps_ joined #salt
04:39 pipps joined #salt
04:40 pipps99 joined #salt
04:41 pipps__ joined #salt
04:42 pipps_ joined #salt
04:44 fracklen joined #salt
04:45 pipps joined #salt
04:45 jas02_ joined #salt
04:52 pipps joined #salt
04:53 pipps99 joined #salt
04:55 pipps_ joined #salt
04:55 pipps__ joined #salt
04:57 pipps joined #salt
04:58 pipps99 joined #salt
04:59 pipps___ joined #salt
05:01 pipps_ joined #salt
05:02 pipps__ joined #salt
05:02 pipps joined #salt
05:03 darvon joined #salt
05:03 pipps99 joined #salt
05:05 pipps___ joined #salt
05:06 mosen joined #salt
05:08 pipps joined #salt
05:10 pipps99 joined #salt
05:11 pipps_ joined #salt
05:11 DEger joined #salt
05:11 pipps__ joined #salt
05:12 pipps___ joined #salt
05:13 pipps joined #salt
05:14 mavhq joined #salt
05:16 debian112 joined #salt
05:17 pipps99 joined #salt
05:18 pipps_ joined #salt
05:18 amontalban joined #salt
05:20 pipps joined #salt
05:22 pipps99 joined #salt
05:25 pipps joined #salt
05:26 pipps_ joined #salt
05:28 pipps99 joined #salt
05:29 pipps__ joined #salt
05:30 pipps joined #salt
05:33 pipps99 joined #salt
05:35 pipps_ joined #salt
05:36 mpanetta joined #salt
05:38 pipps joined #salt
05:38 fracklen joined #salt
05:39 pipps99 joined #salt
05:40 debian112 joined #salt
05:41 pipps_ joined #salt
05:44 pipps joined #salt
05:46 pipps99 joined #salt
05:46 jas02 joined #salt
05:47 pipps_ joined #salt
05:50 pipps joined #salt
05:51 cyborg-one joined #salt
05:51 pipps99 joined #salt
05:52 pipps_ joined #salt
05:54 pipps__ joined #salt
05:55 pipps___ joined #salt
05:56 pipps joined #salt
05:57 pipps99 joined #salt
05:59 pipps_ joined #salt
06:00 jas02 joined #salt
06:00 pipps__ joined #salt
06:01 pipps joined #salt
06:03 pipps99 joined #salt
06:05 pipps_ joined #salt
06:06 pipps__ joined #salt
06:07 pipps joined #salt
06:08 pipps___ joined #salt
06:11 pipps99 joined #salt
06:12 pipps joined #salt
06:13 samodid joined #salt
06:13 pipps_ joined #salt
06:14 pipps__ joined #salt
06:15 pipps___ joined #salt
06:16 DEger joined #salt
06:17 pipps joined #salt
06:18 chowmeined joined #salt
06:19 pipps99 joined #salt
06:20 pipps_ joined #salt
06:21 pipps__ joined #salt
06:22 pipps___ joined #salt
06:23 aidin joined #salt
06:23 pipps joined #salt
06:26 pipps99 joined #salt
06:27 pipps_ joined #salt
06:28 pipps joined #salt
06:32 fracklen joined #salt
06:32 pipps_ joined #salt
06:33 pipps__ joined #salt
06:37 pipps joined #salt
06:38 SamYaple im coming from heavy ansible usage, and im having trouble understanding something. in ansible you could define user variable files (just yaml files) at runtime on the "master" deploy host
06:38 SamYaple is there anything similiar with salt?
06:39 pipps99 joined #salt
06:39 SamYaple im trying to figure out the best way for users to configure what runs where in a relatively complex system deploying openstack
06:39 aidin joined #salt
06:40 pipps_ joined #salt
06:41 pipps__ joined #salt
06:42 pipps joined #salt
06:57 buu SamYaple: You can use a salt command to set 'pillar' variables
06:58 buu And you can create pillar files any time you'd like
07:01 SamYaple buu: I basically an application with a typical /etc/<conf> file situation, in salt terms that file would exist on the master as a pillar and users would edit that pillar?
07:01 buu Um
07:02 buu Pillars define variables for use within salt itself
07:02 buu If you want other programs to read this information you'd just put it in a regular file salt sent to them
07:02 SamYaple no thats not what i mean
07:03 SamYaple i understand that pillars define variables, however I have a bunch of states that the user _shouldn't_ be editing that deploy openstack, im trying to figure out _what_ they edit to define variables out thier environment
07:04 buu I don't understand where you want these user edited variables to end up
07:05 SamYaple buu: currently in the structure as it is laid out in ansible (kolla-ansible is the project name) the variables determine things like which roles run. 'enable_haproxy' 'enable_keystone' etc
07:06 SamYaple they also have things like 'network_interface: eth2', which could change per user environment
07:06 SamYaple buu: this file https://github.com/openstack/kolla-ansible/blob/master/ansible/group_vars/all.yml , for example, is what the user is expected to modify
07:06 buu Ok, so if I understand you correctly these roles are the equivalent of salt sttes
07:07 SamYaple yes
07:09 buu Well, as far as I understand, you would need to define those variables in a salt pillar file someplace, then associate that with the machine(s) to target, then apply the states you wanted to that machine
07:09 buu and the states would then read those variables
07:09 buu Can your users doing the editing run the actual `salt` binary?
07:10 SamYaple that would be a requirement, yea
07:10 buu oh
07:10 buu well
07:11 SamYaple so right now in kolla-ansible to deploy this you simply clone that repo and run `ansible-playbook -e <path_to_config_file> -i inventory_file site.yml`
07:11 SamYaple that config file has all the variables, and inventory is where all the "minions" live etc
07:11 SamYaple im working on kolla-salt, and im just not sure how to map some of that logic over
07:12 buu SamYaple: why not just have a ./pillar directory containing predefined variables the user can edit?
07:13 buu Honestly I don't know enough about how ansible works to really compare the two
07:13 SamYaple buu: thats fine, and i dont know enough about salt to come up with simple solutions.
07:13 SamYaple when you say ./pillar, does that map to /srv/pillars/
07:14 buu Basically, yeah
07:14 buu like
07:14 buu Are you going to have a single instance of salt-master on a box or one for each user?
07:15 SamYaple single instance of salt master. "user" in this case is refereing to consumer of the project. there will only ever be one "user/deployer" running the code
07:15 buu so I'm on my box that's master
07:15 buu I install salt
07:15 buu I clone the repo
07:15 buu I configure my various states/minions/children
07:15 buu Then I want to bring them all up?
07:16 SamYaple yes, but the third step there is where my confusion lies
07:16 buu Well, I'm confused about your confusion
07:16 buu =]
07:16 buu Can you just put files in /srv/pillar with various names and have the deployer edit them?
07:17 buu You can just have.. pkgs.pillar-- http: apache2\n db: mysql-server\n etc
07:17 SamYaple I can, is that the "best practice" and/or common way of doing things?
07:17 buu Honestly I have no idea, I get the impression from the docs that a salt config really isn't intended to be cloned
07:19 SamYaple i can't imagine thats true. if each environment must have a salt expert at the helm that seriously hinders adoption
07:19 buu Well, I *think* the assumption is that an entire company would count as one environment
07:19 buu In terms of salt deploys
07:20 buu I mean, don't take anything I say as gospel
07:20 buu I'm just reading the docs lol
07:20 amontalban joined #salt
07:20 SamYaple but surely you understand my delima here, I can write complex code in kolla-ansible and the user needs to know very little about ansible do deploy it (single command and two files deploys openstack)
07:21 buu I guess what I don't understand is why you want to use salt for this?
07:21 buu Also I know these things exist: https://docs.saltstack.com/en/latest/topics/development/conventions/formulas.html
07:21 SamYaple why does anyone use puppet or chef or ansible? salt is a deployment tool
07:22 brokensyntax joined #salt
07:23 buu But if it already works with ansible..?
07:23 SamYaple kolla-kubernetes is also a thing
07:23 SamYaple kolla as a whole project is about deploying openstack using containers
07:24 SamYaple there are a few deployment tool options
07:24 SamYaple im not converting kolla-ansible, im _building_ kolla-salt
07:25 buu I did get that idea
07:25 buu But I don't really know the answer to your question
07:25 SamYaple totally fine. i understand
07:26 buu Nothing in the docs has suggested to me that salt is the type of thing you'd want to clone a repo and run 'salt up!' on
07:26 SamYaple it does seem like formulas are something i could leverage
07:26 buu I'm sure it's *possible*
07:27 buu Btw do you want https://docs.saltstack.com/en/latest/topics/ssh/ ?
07:27 SamYaple im aware there is going to be some configuration, and it wont be a "salt up", but i can't expect the user to write thier own top.sls with the complexity of the ansible equivelent https://github.com/openstack/kolla-ansible/blob/master/ansible/site.yml
07:27 SamYaple eww no. im trying to get away from salt-ssh
07:27 buu !
07:27 SamYaple or ssh in general
07:27 buu well ok then
07:27 SamYaple its really really slow
07:28 SamYaple with ansible every little check, more ssh!, it just adds time
07:28 buu =[
07:28 SamYaple i think it takes 10 minutes to run through the full kolla run..... when nothing changes
07:28 cwyse joined #salt
07:28 buu So I mean, your options are basically state files and pillar files, so, choose one ==]
07:28 buu (for each problem)
07:29 buu Obviously state files can use jinja stuff, so editing the pillar files to set whatever logic you need seems relatively simple
07:29 buu And pillar files can include other files
07:30 SamYaple it actually looks like formula get me most of the way there, then the user variables part would be the top.sls and pillar file/files
07:30 SamYaple i can make that work i think
07:32 buu Why would the users need to edit top.sls?
07:33 SamYaple targeting minions, no?
07:33 SamYaple openstack has a bunch of services. some may no want to run the Cinder service at all
07:34 mpanetta joined #salt
07:35 buu That would be the normal way, yeah, it sounds like maybe you want to make those variables also?
07:36 SamYaple if the formula is the "static" part and all the other files are considered variables, I think that is simple enough for people to get started with salt
07:39 sh123124213 joined #salt
07:40 buu Well, yeah, if you can just ship a ton of state files and then let the user handle assigning them to menus and maybe a few directory tweaks
07:40 buu menus? minions
07:40 SamYaple that seems reasonable. at least as a starting point. things change as they refine
07:41 buu The two things that have tripped me up so far is that the minion has to basically download the entire salt root so it can interpret all the files, since the minions handle targeting resolution, not the master
07:41 SamYaple have an openstack-kolla formula. and then have '- openstack-kolla.keystone' '- openstack-kolla.neutron.metadata'
07:41 SamYaple something like that
07:41 buu And also file.recursive is REALLY REALLY SLOW
07:42 SamYaple im estimating less than 100 files
07:42 buu seems reasonable
07:42 buu Do you expect there to be a pretty common way to target minions?
07:43 buu I mean.. criteria or something
07:43 sh123124213 joined #salt
07:43 SamYaple i expect to be able to explain that you can use regex to match hostnames as seen from `salt-key -L`
07:43 SamYaple there are 3 classes of common servers: controllers, computes, and storage
07:44 SamYaple you can get more fine grain about what runs where, but if i provide a sample like that i think people can figure it out
07:45 buu ah
07:45 buu cool
07:45 SamYaple for example, on the "controller" it runs keystone, mysql, rabbitmq, nova-api, etc etc etc
07:45 buu Yeah if you control the naming or at least have it configured already
07:45 UForgotten joined #salt
07:45 SamYaple right. so ill have a top.sls.example with 3 groups, and the appropriate services for each group
07:46 SamYaple people can break it out further if they choice
07:46 SamYaple s/choice/choose/
07:46 buu makes sense to me
07:48 jas02 joined #salt
08:06 Trauma joined #salt
08:21 d3c4f_ joined #salt
08:21 amontalban joined #salt
08:21 chowmeined joined #salt
08:23 pmcg joined #salt
08:23 jeblair joined #salt
08:23 nmccollum joined #salt
08:23 brokensyntax joined #salt
08:23 darvon joined #salt
08:23 gnord joined #salt
08:24 cliluw joined #salt
08:25 georgemarshall joined #salt
08:28 smcquay joined #salt
08:30 jas02 joined #salt
08:34 fracklen joined #salt
08:38 chowmeined joined #salt
08:46 chowmeined joined #salt
08:46 ivanjaros joined #salt
08:48 fracklen joined #salt
08:49 jas02_ joined #salt
08:55 stotch joined #salt
09:01 swills joined #salt
09:03 Deliant joined #salt
09:03 k_sze[work] joined #salt
09:06 babilen joined #salt
09:10 jessexoc joined #salt
09:11 viq joined #salt
09:11 AvengerMoJo joined #salt
09:11 pcn joined #salt
09:11 ropes joined #salt
09:12 chowmeined joined #salt
09:15 chowmeined joined #salt
09:15 voxxit joined #salt
09:16 fracklen joined #salt
09:22 amontalban joined #salt
09:22 fracklen joined #salt
09:28 keimlink joined #salt
09:33 voxxit joined #salt
09:33 viq joined #salt
09:33 AvengerMoJo joined #salt
09:33 pcn joined #salt
09:33 ropes joined #salt
09:35 mpanetta joined #salt
09:49 teclator_ joined #salt
09:52 blurgenstein joined #salt
09:53 blurgenstein_ joined #salt
09:54 blurgenstein_ Hi there, I have a short question. I am an experienced linux sys admin for +10 years, with python knowledge too. I want to implement salt in our server farm (30 servers) for my company. I need to tell them how much time I need to get up to speed with Salt
09:54 blurgenstein_ would that be like a week, or a month? Or maybe two days?
09:54 chowmeined joined #salt
09:58 voxxit joined #salt
09:58 jessexoc joined #salt
09:59 AndreasLutro depends on how in-depth you want to go
09:59 AndreasLutro there's always something new to learn
09:59 AndreasLutro I think it'd be possible to set up and run some simple salt stuff within a day
10:00 jas02 joined #salt
10:02 blurgenstein_ yes, thank you very much for your info. I mean, I can learn after months of intensive salting of course. But I can have my 30+ servers under management in a week, for the the not so exotic applications I think?
10:02 blurgenstein_ I tried puppet some time ago, and the more I read, the more I felt I had to read even more..
10:03 AndreasLutro sure.. but I'd say the same is true for puppet
10:03 AndreasLutro maybe documentation is the problem!
10:03 ivanjaros joined #salt
10:03 blurgenstein_ with puppet all the ways to do it made it confusing for me
10:04 AndreasLutro well I think salt is even "worse" in that regard
10:05 blurgenstein_ hmz
10:05 ivanjaros3916 joined #salt
10:07 teclator joined #salt
10:09 AndreasLutro might just be inheretn in all CM software. though if one was written from scratch today it'd probably learn a lot from past mistakes
10:12 blurgenstein_ ah yes. Well, but I could say after playing with it for a week, it is assumable I got it pretty much working in the basics for my employers server farm
10:14 buu I found salt pretty simple to get basic configs set up and deployed
10:14 buu Took me maybe a week of hobby time messing with it
10:18 blurgenstein_ Good to hear! I thought it was cleaner then Puppet.
10:18 evidence joined #salt
10:20 rpb joined #salt
10:22 fracklen joined #salt
10:53 sebastian-w joined #salt
10:54 jas02 joined #salt
10:58 cyborg-one joined #salt
11:01 jas02 joined #salt
11:07 teclator joined #salt
11:17 fracklen joined #salt
11:19 mikecmpbll joined #salt
11:24 amontalban joined #salt
11:31 kjsaihs joined #salt
11:41 mpanetta joined #salt
11:55 jas02 joined #salt
12:06 lompik joined #salt
12:06 sh123124213 joined #salt
12:17 kjsaihs joined #salt
12:24 kjsaihs joined #salt
12:32 jas02 joined #salt
12:33 mavhq joined #salt
12:52 ivanjaros3916 joined #salt
12:52 babilen joined #salt
12:52 k_sze[work] joined #salt
12:52 brokensyntax joined #salt
12:52 sjorge joined #salt
12:52 filippos joined #salt
12:52 mackripeum joined #salt
12:52 zer0def joined #salt
12:52 pysen joined #salt
12:52 dwfreed joined #salt
12:52 ecdhe joined #salt
12:52 pfallenop joined #salt
12:52 jab416171 joined #salt
12:52 mTeK joined #salt
12:52 tristianc_ joined #salt
12:52 swa_work joined #salt
12:52 n1x0n_ joined #salt
12:52 Nickelflac joined #salt
12:52 duckfez joined #salt
12:52 tbrb joined #salt
12:52 GnuLxUsr joined #salt
12:52 tyler-baker joined #salt
12:52 coldbrewedbrew_ joined #salt
12:52 asoc joined #salt
12:52 bantone joined #salt
12:52 wm-bot4 joined #salt
12:52 Gareth joined #salt
12:52 RobertLaptop joined #salt
12:56 tom29739 joined #salt
12:56 jas02_ joined #salt
12:56 keimlink joined #salt
13:01 jas02_ joined #salt
13:02 fracklen joined #salt
13:18 sh123124213 joined #salt
13:20 debian112 joined #salt
13:22 _Cyclone_ joined #salt
13:25 _Cyclone_ joined #salt
13:26 amontalban joined #salt
13:38 jas02 joined #salt
13:43 samodid joined #salt
13:44 Trauma joined #salt
13:45 debian112 joined #salt
13:48 rpb joined #salt
13:50 blurgenstein joined #salt
13:52 ernescz joined #salt
13:59 ernescz Hello everyone! I was wondering - is it possible with Jinja to do compound match by minion hostname? Kind of like https://pastebin.ubuntu.com/23608154/
13:59 ernescz similar to the top file: 'E@web-0* and G@roles:apache'
14:00 ernescz two 'or/and' is fine but it gets unreadable after that. Hints?
14:01 jas02 joined #salt
14:03 mikecmpbll joined #salt
14:06 wangofett Anyone know if/how it's possible to use a multimaster setup behind 1 IP? I'm guessing "it's not" is really the answer
14:07 wangofett e.g. I can setup HAproxy and send requests for `this.example.com` to server 1 and `that.example.com` to server 2. But the salt minion is just connecting via IP and isn't sending any kind of host, right?
14:08 wangofett ernescz: You could use grains matching in your jinja
14:08 cyborg-one joined #salt
14:09 wangofett https://docs.saltstack.com/en/latest/topics/tutorials/states_pt3.html#using-grains-in-sls-modules
14:10 wangofett I *believe* that works with wildcard matching.
14:11 keimlink joined #salt
14:14 ernescz wangofett: thanks, grains work for fine when I have a specific grain set like " if ['grains'] == 'myhost' "
14:14 Trauma joined #salt
14:15 ernescz but wildcard matching in grains doesn't work for me " if grains['hostname'] == 'myhos*' "
14:15 Rumbles joined #salt
14:15 ernescz sorry, first example was incorrect, second one is.
14:16 wangofett you could use `grains['hostname'].startswith('myhos')`, I believe
14:17 ernescz wangofett: yes! I saw an example like that a long time ago!
14:17 ernescz This should work. Much appreciated your help! :)
14:21 wangofett n/p :)
14:21 o1e9 joined #salt
14:26 ernescz wangofett: It indeed works as you said. And example for reference: https://pastebin.ubuntu.com/23608269/  Thanks!
14:48 krymzon joined #salt
14:52 _Cyclone_ joined #salt
15:03 jas02 joined #salt
15:19 pipps joined #salt
15:20 pipps joined #salt
15:21 jas02_ joined #salt
15:22 kjsaihs joined #salt
15:23 jas02__ joined #salt
15:27 amontalban joined #salt
15:27 amontalban joined #salt
15:29 o1e9 joined #salt
15:29 jooni joined #salt
15:43 mpanetta joined #salt
15:45 fracklen joined #salt
15:47 kjsaihs joined #salt
15:51 fracklen joined #salt
15:59 DEger joined #salt
15:59 DEger joined #salt
16:05 gpampara left #salt
16:14 afics joined #salt
16:17 [|SDK|] joined #salt
16:17 [|SDK|] Hey!
16:18 [|SDK|] Where's My Shifty Hexahedron at!
16:29 amontalban joined #salt
16:29 amontalban joined #salt
16:33 jas02 joined #salt
16:40 fracklen joined #salt
16:47 mohae joined #salt
16:58 FreeSpencer_ joined #salt
16:59 DEger joined #salt
17:10 * [|SDK|] slaps tooth with his skin rocket!
17:13 SamYaple im writing a module in salt, but im not quite sure how to inform salt of "changed" vs unchanged for idempotency
17:13 SamYaple can someone point to an example of this?
17:18 FreeSpencer joined #salt
17:18 FreeSpencer joined #salt
17:19 SamYaple oh i see. there is a difference between state modules and execution modules
17:19 SamYaple that makes sense
17:20 harkx joined #salt
17:21 DEger joined #salt
17:27 DEger joined #salt
17:35 stanchan joined #salt
17:43 mpanetta joined #salt
17:51 pcdummy SamYaple: :)
18:02 amontalban joined #salt
18:19 Nahual joined #salt
18:20 sh123124213 joined #salt
18:24 cyteen joined #salt
18:29 wangofett So... storing states in git == hooray, that's great. But secrets belong in pillars... does anyone have a good solution to keeping pillars and states in sync? one thought that I had was to use git submodules, but that's not like a mercurial subrepo at all.
18:30 fracklen joined #salt
18:30 wangofett i.e. I can't commit in the submodule, it seems to be only for reading. Which means I have to fiddle with committing in a second repository so it doesn't seem like I win a whole lot there.
18:40 lumtnman joined #salt
18:42 rpb joined #salt
18:43 mohae joined #salt
18:57 ashmckenzie joined #salt
18:59 XenophonF joined #salt
19:02 jas02 joined #salt
19:10 nZac joined #salt
19:13 jesusaur joined #salt
19:19 keimlink joined #salt
19:19 orion_ joined #salt
19:20 orion_ seeing a strange issue since the last few days
19:20 orion_ when i run salt 'app*' core.sls
19:20 orion_ i see the following
19:21 orion_ app01.test.com:     'core.sls' is not available
19:21 orion_ this was working fine till a few days ago
19:21 orion_ any ideas ?
19:25 fracklen joined #salt
19:28 mpanetta joined #salt
19:34 cyborg-one joined #salt
19:39 mohae joined #salt
19:41 tristianc_ left #salt
19:44 SamYaple how do you invert the match for minions in the top.sls?
19:44 SamYaple as in '!web1' targets all hosts EXCEPT web1
19:46 kjsaihs joined #salt
19:46 oida joined #salt
20:15 fracklen joined #salt
20:17 wangofett grumble... is there a way to tell where I'm getting a pillar from? Cause I totally have the wrong pillar
20:20 wangofett oooh. I think I know :P
20:21 krymzon joined #salt
20:23 wangofett yeah, I had set the ext_pillar
20:33 jas02 joined #salt
20:34 DEger joined #salt
20:39 [CEH] joined #salt
20:45 armguy joined #salt
20:46 fgimian joined #salt
20:51 mpanetta joined #salt
20:51 Flying_Panda joined #salt
20:52 Flying_Panda hi all
20:54 Flying_Panda anyone played with the bigIP state functions? im playing with teh bigip_list_node function which should let me check if a node is the f5 is it possible to write the rest of my state depending on if that function can find the node?
20:59 seanz joined #salt
20:59 DEger joined #salt
21:00 Onmeac joined #salt
21:05 darix joined #salt
21:11 Onmeac left #salt
21:16 onmeac joined #salt
21:23 krymzon joined #salt
21:25 buu Flying_Panda: add it to the salt mine!
21:29 DEger joined #salt
21:33 emerson joined #salt
21:37 wangofett is it possible to do like... `file.managed` and `file.append` in one state?
21:39 onmeac in one sls file you mean?
21:40 wangofett no, in one state, e.g `this_file: file.managed: ... file.append:`
21:42 Drunken_Panda joined #salt
21:43 Flying_Panda oo good idea buu not really played with salt-mine yet
21:44 Flying_Panda wango could you not just do make file: file.managed  appendtofile: file.append
21:44 Flying_Panda call the 2 functions one after another
21:44 onmeac wangofett: https://docs.saltstack.com/en/latest/topics/tutorials/states_pt2.html#call-multiple-states, does this answer your question?
21:45 Flying_Panda or use require / watch
21:46 wangofett onmeac: that only works for different bits. Like in that example it's `pkg.installed` and `service.running`. But you can't do something like `service.enabled` and `service.state`
21:46 SDK514 joined #salt
21:47 wangofett salt complains about multiple declarations of the same type
21:47 onmeac ah, yea then use two different id declerations
21:48 Flying_Panda this dont matter: /n file.manager
21:48 Flying_Panda *.managed
21:48 Flying_Panda another id: /n file.append
21:49 Flying_Panda obviously with /n indicating new line
21:52 wangofett Is it possible to use jinja variables in a pillar... specifically I want to do something like `contents_pillar: my:pillar  - template: jinja`
21:53 Flying_Panda you can write then directly into the pillar file
21:53 Flying_Panda https://docs.saltstack.com/en/latest/topics/tutorials/pillar.html
21:53 Flying_Panda about 50% of the way down
21:56 onmeac question: the salt syndic, which uses a separate salt-minion process to connect to the "master of master" (MOM), is there a way for it to not load pillar data from the MOM ?
21:57 Flying_Panda I dont understand? it will only load the pillar data if it matches the top.sls file
21:57 wangofett Hm I get Rendering exception occurred: Jinja variable 'salt.utils.context.NamespacedDic
21:58 wangofett tWrapper object' has no attribute 'hostname'
21:58 Flying_Panda post code wango on git paste in motd
21:58 Flying_Panda ill take a look
21:59 onmeac thing is: we use this as top.sls
21:59 onmeac base: \n '*': \n  - {{ salt['grains.get']('id')|replace (".", "_") }}
21:59 onmeac so yea minions always match
21:59 wangofett Flying_Panda: https://gist.github.com/waynew/9d945c2a6e3d2fd51dc470e6a55db35f
22:01 Flying_Panda have you specified hostname in your pillar
22:02 wangofett see line 1... but I figured out my problem
22:02 Flying_Panda or for hostname dont use pillar file just pop in the template
22:03 wangofett see line 1... but I figured out my problem that I was having before
22:03 wangofett I just updated the gist with what I was trying
22:03 wangofett I just had `template_type: jinja` instead of `template`
22:04 Flying_Panda does your endraw not need a -%}
22:04 wangofett I'm using the pillar so I can override it with my ext_pillar. I'm sharing *this* stuff publically, but I want to keep the ability to override things like the hostname, etc.
22:05 wangofett nah the `-` eliminates the whitespace around the tags
22:05 wangofett `{%-` eliminates it before, `-%}` eliminates it after
22:06 Flying_Panda oooo never knew that
22:06 wangofett so I do have an extra blank line at the end of my /etc/hosts
22:06 Flying_Panda thought it was a way of mtaching the raw and endraw tags
22:06 Flying_Panda :D
22:06 Flying_Panda learn somthing new
22:06 wangofett Yeah, I was trying to figure out how to get my jinja to render without all those gaping holes
22:07 wangofett esp in files where you're using templates with loops. It's just gross :P
22:09 Flying_Panda for hostname i usally just do somthing like this {% set name= salt['grains.get']("id") %}
22:09 Flying_Panda but do you have a copy of the /pillar/*.sls you are using and your topfile the error suggests its not pulling pillar data
22:09 gmacon joined #salt
22:11 Flying_Panda could even use grains['id'] but meh like the readability for the other guys who dont use salt a smuch :D
22:16 Flying_Panda at wango run a salt '*' pillar.items
22:16 Flying_Panda can you see your hostname pillar
22:16 Flying_Panda if not refresh it salt '*' saltutil.refresh_pillar
22:18 Flying_Panda also looking at what you linked you need to quote hostname: 'gru'
22:18 Flying_Panda as its a string not an interger
22:19 kjsaihs joined #salt
22:19 amontalban joined #salt
22:19 amontalban joined #salt
22:20 jas02_ joined #salt
22:26 sh123124213 joined #salt
22:35 vodik joined #salt
22:36 mswart left #salt
22:44 DK2 joined #salt
22:47 krymzon joined #salt
22:51 nidr0x joined #salt
22:52 [|SDK|] joined #salt
22:52 [|SDK|] left #salt
22:55 johnkeates joined #salt
23:10 smcquay joined #salt
23:26 smcquay joined #salt
23:27 jas02_ joined #salt
23:30 DEger joined #salt
23:31 amcorreia joined #salt
23:48 mavhq joined #salt
23:51 jas02_ joined #salt
23:56 Trauma joined #salt

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