Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2015-01-10

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

All times shown according to UTC.

Time Nick Message
00:01 jessie_ joined #salt
00:01 jimklo joined #salt
00:02 Guest92101 hey all, can anyone asists with installing salt cloud with my current salt stack. following https://salt-cloud.readthedocs.org/en/latest/topics/install/index.html with installing on ubuntu.
00:04 iggy Guest92101: what version of salt do you have?
00:05 Guest92101 cmd for salt version ?
00:05 jimklo joined #salt
00:05 iggy salt --versions
00:06 rypeck joined #salt
00:06 Guest92101 salt 2014.7.0 (Helium)
00:06 iggy it's built in now
00:06 Guest92101 Helium ? thought we was nuclear here :)
00:07 Guest92101 oh is it i didnt even know ... bah
00:07 iggy BUT
00:08 iggy some distros still split it out into a separate package, so if you installed from distro packages, there might be also a salt-cloud package
00:09 Guest92101 i am just running this as a test currently hoping to get it working with cloud API's like digital oceon
00:10 iggy DO works well, as does aws and gce... those are the only ones I've tried
00:11 Guest92101 well its been suggested to me that salt is the way to go over ansible chef and puppet, so givin it a go for autmation and version management
00:12 iggy I never used ansible, but I certainly like salt more than chef and puppet
00:13 iggy I think with all those tools you also need soemthing else to do the orchestration (mcollective, etc.)
00:13 rypeck ^ so essential to understand about salt vs chef/puppet
00:13 Guest92101 ansible tower has the GUI which seems more modern... but how the manage enterprise level server configs .... seems lame
00:13 Guest92101 iggy how long you been playin with salt
00:14 iggy about a year
00:14 TheoSLC joined #salt
00:15 martoss joined #salt
00:16 linjan_ joined #salt
00:18 badon joined #salt
00:19 jimklo joined #salt
00:22 cruatta joined #salt
00:31 asyncsrc joined #salt
00:46 linjan_ joined #salt
00:47 jprewitt joined #salt
00:47 monkey661 joined #salt
00:53 pdayton joined #salt
00:54 otter768 joined #salt
01:00 hal58th joined #salt
01:06 aqua^mac joined #salt
01:08 bhosmer joined #salt
01:13 JDiPierro joined #salt
01:13 Guest92101 Looking for someone who has clear experience with salt stack - cloud looking to directly assist me with getting upto speed , with the install process, methodologyand best practices for using with cloud infrastructure basics. This will be paid hence the direct approach for quicker understanding. Preferably someone who speaks english.
01:15 meylor joined #salt
01:15 meylor is there a way to tell jinja within salt to wait for a file to be laid down before it evaluates it (and fails when it doesn't exist).
01:18 nickdew I'm going to say no. The execution order is Jinja -> YAML -> Highstate -> low state -> execution.
01:19 nickdew What are you trying to do?
01:21 Guest92101 Looking for someone who has clear experience with salt stack - cloud looking to directly assist me with getting upto speed , with the install process, methodologyand best practices for using with cloud infrastructure basics. This will be paid hence the direct approach for quicker understanding. Preferably someone who speaks english.
01:24 meylor nickdew: within a state i'm doing a git clone to the minion; then I have a helper function which reads a requirements.txt from within the cloned repo on the minion. the issue is that the jinja evaluates before the repo is cloned on the minion
01:24 stevednd meylor: yep, that's always a fun one to solve
01:25 stevednd in the past I have typically created my own modules or states to do what has to be done after the checkout
01:26 stevednd I typically try to go with a module if possible because I find writing states to be a pita
01:26 schristensen joined #salt
01:26 nickdew meylor: You might want to look into setting the requirements in a map.jinja or in pillars. That is the easiest way I can see around that.
01:27 meylor so basically i want to read from the requirements.txt file that is within the git repo; i use a helper to pass it to jinja as a list then loop over it to install each package
01:28 nickdew asd
01:28 Ligthert wasn't it ASL?
01:28 meylor ?
01:29 nickdew wrong window.
01:29 Ligthert np
01:30 stevednd meylor: you can do two separate runs, or you can write your own state that requires the checkout, then in python read in that file, and call the __salt__['pkg.install']
01:30 meylor the latter is probably what I need to do
01:31 nickdew I have different repos for different environments (prod, qa, etc). I have a map.jinja file that says if prod, you get this branch and qa gets another.
01:31 nickdew Then when setting up the app, I just call the variable in Jinja in the state file.
01:31 meylor nickdew: that's similar to what I'm doing
01:32 stevednd meylor: you can also call __salt__['state.single'](fun='pkg.installed'...)
01:32 stevednd that would let you build off of an existing state
01:32 meylor okay I'll look into that when I get home tonight
01:32 stevednd instead of calling pkg.install directly that is
01:32 bhosmer_ joined #salt
01:33 meylor I was thinking I could get around it, if I just cloned the repo from python to get the file, read it in
01:33 meylor then the jinja could stay the same
01:34 nickdew meylor: http://docs.saltstack.com/en/latest/topics/development/conventions/formulas.html and http://docs.saltstack.com/en/latest/topics/best_practices.html have some good examples of what I do.
01:34 stevednd you could create a module to do the clone, read the reqs, and return a list or dict to your template
01:34 meylor yeah, that's probably the best for this I'd think
01:34 nickdew You would have to convert your requirements file to Jinja templating or a pillar.
01:35 stevednd that entirely possible. It just means you'll clone/pull twice most likely. if you're fine with that then it's not much of an issue
01:35 stevednd nickdew: if he returns a list or a dict from a custom module then he can just iterate over it like anything else in his template
01:35 meylor thanks; these comments were very helpful.
01:37 stevednd np
01:37 nickdew stevednd: For sure. Personally, I would rather have variables in the Salt repo, as I would find it easier to mainatain.
01:38 shrihari joined #salt
01:39 jimklo joined #salt
01:40 stevednd I think for most things for sure, but in this case the requirements are the domain of the application itself, and typically subject to a lot of variance. For me that means I would rather the app knows what it needs, and I don't have to maintain the requirements in two places(app and salt). Applications are pretty much the only thing that I have operate that way. everything else is pillars and maps
01:41 kiorky joined #salt
01:41 meylor nickdew: stevednd: in this case, the requirements are maintained by someone else. I just want to consume and use whatever requirements as they change
01:42 stevednd yeah, then I would definitely go with the programmatic approach
01:42 nickdew That makes sense. The nice thing is there are multiple ways to do it.
01:43 bhosmer joined #salt
01:43 nickdew Alright, taking off. Good luck meylor.
01:43 meylor thanks nickdew
01:44 nullptr joined #salt
01:46 catpig joined #salt
02:00 jimklo_ joined #salt
02:01 monkey66 joined #salt
02:01 cleme1mp joined #salt
02:02 nitti joined #salt
02:05 twellspring joined #salt
02:14 TheThing joined #salt
02:14 nitti joined #salt
02:14 ponpanderer joined #salt
02:16 monkey66 left #salt
02:18 murrdoc joined #salt
02:34 stevednd did something change with salt since 2014.1. I can no longer see any kind of debug/output when pillar files fail to compile. I get the message saying to check the master log, but there's nothing in it
02:38 murrdoc what points to pillar failing
02:38 murrdoc i normally do refresh_pillar and pillar.items
02:38 murrdoc to test pillars
02:39 stevednd the standard pillar failure message. the one that says "Rendering SLS 'certs' failed. Please see master log for details."
02:40 Guest92101 Looking for someone who has clear experience with salt stack - cloud looking to directly assist me with getting upto speed , with the install process, methodologyand best practices for using with cloud infrastructure basics. This will be paid hence the direct approach for quicker understanding. Preferably someone who speaks english.
02:41 murrdoc what does saltutil.refresh_pillars -l debug show u
02:42 stevednd nothing of interest. just the regular chatter
02:45 murrdoc and pillar.items
02:45 P0bailey joined #salt
02:45 P0bailey joined #salt
02:45 stevednd same thing. that was my point. I'm getting literally no debug/failure information about the pillar not compiling
02:45 murrdoc can u check log on a minion
02:45 murrdoc ?
02:45 Guest92101 anyone here got good experience with salt  and salt cloud thats available for the next few hours
02:48 stevednd pillars compile on the master, but I double checked the minion anyways since I'm out of ideas. nothing there though
02:55 aqua^mac joined #salt
02:55 otter768 joined #salt
02:56 Guest92101 is it better to install salt and cloud on centos or ubuntu
02:59 Guest92101 can anyone assist with how to use salt cloud.
03:01 murrdoc sorry man, its late on a friday
03:01 murrdoc at most i can link u to http://docs.saltstack.com/en/latest/topics/cloud/
03:01 Guest92101 no worries thanks.
03:01 murrdoc once u have u read it tho, you should be able to get somewhere
03:01 murrdoc its really easy
03:02 murrdoc :)
03:03 Guest92101 just learned that ubuntu seperates the mods as centos doesnt... so just installed all the mods.
03:05 Guest92101 anyone else about
03:06 Guest92101 would i be right in saying that profiles are like templates ?
03:19 aquinas_ joined #salt
03:19 shrihari joined #salt
03:19 benjy left #salt
03:39 stevednd Guest92101:  yes the profiles act as templates for an initial machine configuration
03:40 stevednd they also inherit settings from your provider definition
03:40 Guest92101 stevednd: that makes more sense now. . you from mancester by some chance steve ?
03:41 stevednd for extra goodness you can treat your cloud configs as anything else you would manage with salt, and template them with jinja
03:41 stevednd nope, not even close. near dallas
03:41 Guest92101 ahhh :)
03:42 Guest92101 am at the early stages of salt currently.
03:42 Guest92101 looking to just try and set up cloud with DO or AWS as a test
03:42 stevednd it takes a while to wrap your head around the way it works
03:42 shrihari joined #salt
03:42 Guest92101 salt master and minion set up with version control for dev enviroment.
03:42 stevednd especially if you're used to something like chef or puppet which takes a more programming oriented approach
03:43 Guest92101 not used chef or puppet. but i did look at them
03:43 stevednd salt cloud is documented pretty poorly IMO
03:43 mgw joined #salt
03:43 Guest92101 jeez. i am looking for someone who can assist me directly on a one to one basis going through the full process. piad of course
03:43 Guest92101 *paid
03:44 stevednd it's easy enough once you figure it out, but it's hard to connect the dots at the beginning
03:44 stevednd https://gist.github.com/dnd/8dd332ec66018a6f9c6a
03:45 stevednd you can take a look at that to see an example of some cloud configs I just did for provisioning with linode
03:46 Guest92101 DO ftw :)
03:46 Guest92101 dont think i will ever use linode. but its good to see the "profiles "
03:47 stevednd the custom script is because linode doesn't setup private ips automatically, and the script_args are what end up passed to salt-bootstrap in a normal case. In mine I'm tracking the 2014.7 branch
03:48 Guest92101 i dont know a cloud service that does setup private ips automatically
03:48 Guest92101 as in by default
03:48 Guest92101 if thats what you mean
03:48 stevednd some of the cloud docs seem to imply that aws ec2 stuff does
03:48 stevednd but I've never used it, so I wouldn't know
03:49 Guest92101 not automatically... you have to reserve the ips specifically then apply to vm
03:49 Guest92101 azure does this also
03:50 stevednd the cloud provider driver for those services may do it, might be what it's implying
03:51 stevednd if you wanted to automatically configure the private ip as I am in that script it wont' work unless you modify salt.
03:51 stevednd by default it doesn't provide the information needed. I have an issue in to get it included
03:51 Guest92101 so with azure aws DO i believe you can do so. as in reserve a static private IP.
03:52 Guest92101 i could be wrong as am not that far in but, remotely for the UI's i am able to create static reserved IP before creation of VM
03:52 stevednd you can reserve the private IP with most, even with linode. Neither linode nor the driver configures it though. Some other providers maybe it would work
03:53 Guest92101 ah ok. beyond that am not sure
03:53 stevednd that's what the private_ip: True in the provider config is for
03:53 Guest92101 ah yes as it uses cloud syntax to create the ip...
03:54 stevednd if you don't have your master only bound to private interface then you won't really have any issues
03:55 stevednd I just did this so everything could be pretty much turnkey
03:55 Guest92101 how busy are you steve. do you have time to go through a fair bit ?
03:56 stevednd not really. I'll probably be around most of the night, I just pop in here when I get bored/stuck on what I'm working on
03:57 stevednd there will be pretty much no traffic in here until maybe 14 hours from now, but typically it's *really* slow until weekdays during US business hours
03:57 stevednd feel free to post questions though, and I'll answer if I can when I'm around
03:59 jacksontj I'll be here lurking for a while too ;)
04:00 Guest92101 looking for a more direct approach. to the full master minion cloud. someone to just run through things with me directly. i dont mind paying for the time
04:01 jacksontj oh, I don't have experience with salt-cloud (I assume thats what the question is?)
04:01 jacksontj or are you just trying to set up a master and some minions?
04:02 Guest92101 master minion and cloud.
04:02 Guest92101 experience distro engineer. looking for  afast track process
04:02 Guest92101 :)
04:03 jacksontj ah, I run a bare metal cluster :/ and haven't messed with the cloud stuff in salt before
04:04 jacksontj if you have problems i might be able to help
04:04 jacksontj i do lots in the core ;)
04:04 Guest92101 what kind of stuff do you do without the cloud
04:05 Guest92101 core *
04:05 jacksontj mostly performance stuff
04:05 jacksontj but, lots ;)
04:05 Guest92101 hmmm
04:05 jacksontj our install is ~15k minions per master
04:05 jacksontj so I kinda care about the performance :)
04:06 Guest92101 interested, could you define more around that
04:07 jacksontj my current large-ish project is refactoring the transport in salt
04:07 jacksontj cleaning up auth, and zmq
04:07 jacksontj the daemons have evolved over time, so its about time to go in and clean out
04:08 jacksontj the minions (for example) were auth-ing ~3-7 times on start up, now its just one :)
04:08 Guest92101 ahhh, so auditing ?
04:09 Guest92101 so you deal with more the maintenance aspects of the automation deployment of salt ?
04:11 jacksontj well, I also use it heavily to automate the infrastructure I run
04:12 Guest92101 what kinds of automations you run on your infra
04:12 jacksontj state enforcement primarily, but we use it for just about everything you can think of ;)
04:12 smcquay joined #salt
04:13 jY are there any examples of how to unit test custom grains?
04:14 jacksontj not that I know of, but the testing should be more or less the same as execution modules (like https://github.com/saltstack/salt/blob/develop/tests/unit/modules/aliases_test.py)
04:16 twellspring joined #salt
04:17 jY ok i'll give that a look over thanks
04:22 rhand joined #salt
04:34 bantone a lot of the infrastructure i work on is on-metal
04:34 bantone but of course i want to test salt within the cloud first
04:34 bantone still learning
04:34 bantone jacksontj: sounds like we do similar stuff
04:36 Guest92101 am at the stage of testing cloud at the mo with DO
04:42 P0bailey joined #salt
04:43 P0bailey joined #salt
04:43 aqua^mac joined #salt
04:56 otter768 joined #salt
04:57 ldlework joined #salt
05:08 Vito joined #salt
05:08 vbabiy joined #salt
05:11 vsabella Hi everyone, I am having some issues using salt-cloud and Amazon AWS/ec2
05:11 vsabella I'm using the latest salt/salt-cloud salt-cloud 2014.7.0 (Helium)
05:12 vsabella When launching an instance, the instance is created in AWS
05:12 vsabella but after 10 minutes it fails with
05:12 vsabella Error: There was a profile error: Unable to get IP for 00:10:00
05:13 vsabella When I do a verbose log, <instanceset><item><privateIpAddress> is there, and it is the correct IP address
05:14 vsabella as is the privateIpAddress set in <networkInterfaces>
05:14 vsabella This is set up using a VPC
05:15 jalaziz joined #salt
05:15 vsabella my profile has private_ips in it
05:17 vsabella joined #salt
05:27 nitti joined #salt
05:45 nullptr joined #salt
05:47 ajmccluskey joined #salt
05:53 overyander joined #salt
05:57 Curious__ joined #salt
06:10 Mso150 joined #salt
06:18 hasues joined #salt
06:18 hasues left #salt
06:22 rhand joined #salt
06:24 theherk joined #salt
06:25 ajmccluskey joined #salt
06:26 ajmccluskey Just posted an issue I mentioned earlier RE git.latest on Windows minions: https://github.com/saltstack/salt/issues/19603
06:26 ajmccluskey time to sleep
06:26 ajmccluskey night all
06:29 theherk left #salt
06:32 aqua^mac joined #salt
06:33 theherk joined #salt
06:46 catpigger joined #salt
06:49 jeffspeff joined #salt
06:57 otter768 joined #salt
07:18 ldlework joined #salt
07:26 fragamus joined #salt
07:26 ndrei joined #salt
07:42 hintss joined #salt
07:52 rhand joined #salt
08:10 TyrfingMjolnir joined #salt
08:11 monkey661 joined #salt
08:18 aquinas joined #salt
08:19 viq joined #salt
08:21 aqua^mac joined #salt
08:23 agend joined #salt
08:34 rhand joined #salt
08:37 zadock joined #salt
08:42 cberndt joined #salt
08:43 monkey66 joined #salt
08:55 Micromus joined #salt
08:57 otter768 joined #salt
09:06 nullptr` joined #salt
09:44 toddnni_ joined #salt
09:46 bhosmer joined #salt
09:50 alexr_ joined #salt
09:51 stbenjam joined #salt
10:03 I3olle joined #salt
10:10 aqua^mac joined #salt
10:20 P0bailey joined #salt
10:21 P0bailey joined #salt
10:29 monkey661 joined #salt
10:31 rtuin joined #salt
10:34 Pieter___ joined #salt
10:34 chiui joined #salt
10:34 Pieter___ Hi, I have to provide a fix to a project which has been orchestrated by Salt but I can't seem to find the correct solution
10:34 Pieter___ Salt is using the pkg to install deb packages
10:35 Pieter___ But when for some reason dns is not working ( eg. temp fw rules at customer) salt hangs in a loop to try to resolve
10:35 Pieter___ So every config change requires dns resolv which is not really needed
10:35 Pieter___ Are there best practices for this situation?
10:36 jalaziz joined #salt
10:52 ndrei joined #salt
10:58 jalaziz joined #salt
10:58 otter768 joined #salt
11:07 nhubbard joined #salt
11:13 rtuin joined #salt
11:13 ldlework joined #salt
11:36 agend left #salt
11:37 N-Mi_ joined #salt
11:38 tomh- joined #salt
11:43 yomilk joined #salt
11:52 CeBe joined #salt
11:56 ecdhe_ joined #salt
11:57 johtso joined #salt
11:57 malinoff joined #salt
11:59 aqua^mac joined #salt
12:06 Mso150_w joined #salt
12:13 arno joined #salt
12:43 yomilk_ joined #salt
12:45 beardo_ joined #salt
13:03 redzaku joined #salt
13:04 piquadrat joined #salt
13:05 piquadrat joined #salt
13:14 bhosmer joined #salt
13:34 xt joined #salt
13:37 hebz0rl_ joined #salt
13:48 aqua^mac joined #salt
13:56 JDiPierro joined #salt
14:01 pdayton joined #salt
14:03 jeffrubic1 joined #salt
14:04 anybroad joined #salt
14:05 anybroad joined #salt
14:06 pviktori_ joined #salt
14:19 I3olle_ joined #salt
14:34 beauby_ joined #salt
14:37 faust joined #salt
14:41 I3olle joined #salt
14:52 faust joined #salt
14:53 redzaku joined #salt
15:00 otter768 joined #salt
15:05 rtuin joined #salt
15:19 zadock joined #salt
15:30 aranhoide joined #salt
15:30 pviktori joined #salt
15:34 redzaku joined #salt
15:34 aranhoide I installed salt 2014.7.0 from pip on Ubuntu 14.04, but somehow a salt-minion executable doesn't seem to be included (I do get /usr/bin/salt-call though)
15:35 aranhoide has anything changed in that regard in recent versions?
15:36 kermit joined #salt
15:37 aqua^mac joined #salt
15:40 tligda1 joined #salt
15:42 beardo_ joined #salt
15:45 pviktori_ joined #salt
15:45 mgw joined #salt
15:48 ndrei joined #salt
15:48 bhosmer joined #salt
15:53 pviktori joined #salt
16:02 nitti joined #salt
16:09 Micromus joined #salt
16:13 saxonww joined #salt
16:15 fragamus joined #salt
16:23 peters-tx joined #salt
16:25 xt joined #salt
16:28 ndrei joined #salt
16:32 danemacmillan joined #salt
16:33 bhosmer joined #salt
16:34 I3olle_ joined #salt
16:34 pdayton joined #salt
16:42 jasonrm joined #salt
16:44 JDiPierro joined #salt
16:50 toddnni joined #salt
17:01 otter768 joined #salt
17:15 ekristen joined #salt
17:16 ajmccluskey joined #salt
17:19 Micromus joined #salt
17:22 JDiPierro joined #salt
17:22 bastion2202 joined #salt
17:23 elfixit joined #salt
17:26 aqua^mac joined #salt
17:31 hasues joined #salt
17:31 hasues left #salt
17:33 whatevsz joined #salt
17:39 ksalman joined #salt
17:39 ksalman is there a easier way to remove salt that was install with the bootstrap-salt.sh script? I would like to clean that up and install it with the package manager
17:41 toddnni joined #salt
17:55 bastion2202 joined #salt
17:56 TheThing joined #salt
18:05 _JZ_ joined #salt
18:05 StDiluted joined #salt
18:06 bfoxwell joined #salt
18:10 aranhoide ksalman: I don't know of a clean cross-platform way (but there might be).  what OS are you using?
18:10 lothiraldan joined #salt
18:10 badon joined #salt
18:11 ksalman aranhoide: debian and redhat. REally i can figure out the other if i know one
18:11 ksalman i think it's mostly python/dist-packages/salt and /usr/bin/salt*
18:11 ksalman that i need to delete
18:12 Diaoul hi
18:12 Diaoul salt master is memory hungry, how can I tweak it so it uses less memory (not many minions here)
18:13 aranhoide well, if you see which package manager was used in bootstrap-salt.sh for your OS I guses you can easily revert that.  e.g.: for debian, if apt-get was used then you can just `apt-get uninstall salt-master salt-minion`.  if pip was used then you can `pip uninstall salt`
18:14 aranhoide although if the package manager that was used to install salt in first place is the same one you intend to use you may not need to remove it.  That will be taken care of on upgrading
18:15 ksalman aranhoide: i used pip and and you are right, i should just do pip uninstall.. I don't know why that did not occur to me >.<
18:15 ksalman thanks
18:15 aranhoide so `pip install --upgrade --force-reinstall` if you want to be extra sure
18:15 aranhoide np
18:17 rocketman joined #salt
18:17 rocketman left #salt
18:22 kaiyou joined #salt
18:30 mgw joined #salt
18:30 Mso150 joined #salt
18:35 NikolaiToryzin joined #salt
18:36 rjc joined #salt
18:38 Micromus joined #salt
18:47 arno joined #salt
18:49 yomilk joined #salt
18:49 xt\ joined #salt
18:54 Mso150_n joined #salt
18:57 JoeHazzers joined #salt
18:58 fragamus joined #salt
18:59 nethershaw joined #salt
19:00 I3olle joined #salt
19:02 otter768 joined #salt
19:09 rome_390 joined #salt
19:14 ajmccluskey It doesn't appear that my salt-minion service on WinXP is logging. It creates the log file, but never actually writes/flushes anything to the file.
19:14 ajmccluskey Logging does seem to work when running from the command line myself. e.g. `salt-minion -l debug`
19:14 rome_390 joined #salt
19:14 aqua^mac joined #salt
19:15 ajmccluskey Is there something I'm missing, or should I raise an issue?
19:21 catpiggest joined #salt
19:22 ajmccluskey I needed to change my log_level_file in the minion config, not log_level. log_level is only for console output.
19:22 ajmccluskey https://github.com/saltstack/salt/issues/11032
19:26 nitti joined #salt
19:27 Nazca joined #salt
19:39 JDiPierro joined #salt
19:42 Nazca joined #salt
19:44 nethershaw joined #salt
19:49 yomilk_ joined #salt
19:50 rocket joined #salt
19:51 Mso150_n joined #salt
19:52 rocket hey guys is it possible to setup a management node?  eg I want to have my mac laptop control a saltstack env, but I dont want to have it be controlled by this env.
19:52 rocket if so where would I look for documents on that
19:58 scarcry joined #salt
19:58 Nazca joined #salt
20:05 ekristen joined #salt
20:22 ekristen joined #salt
20:24 stevednd rocket: either don't run a minion at all on you mac laptop, or if you want it to be controlled by another master, just set the master in your minion config to that master machine
20:25 meylor joined #salt
20:26 meylor I feel like there should be a way to postpone Jinja rendering until after a certain point within a state
20:26 stevednd "that master machine" being whatever machine you want to be its master
20:28 stevednd meylor: on the list of things that are likely to happen I would think that probably isn't on there. One of the biggest hurdles with salt is the mental shift. It's like going from svn to git. It's a different way of doing things compared to say chef or puppet
20:28 stevednd once you get over that hurdle things get much easier
20:29 stevednd if you're still having issues with wanting your git checkout to happen first you could also look into orchestration
20:29 arno joined #salt
20:30 stevednd if you aren't familiar, it's a state based way to run multiple states in succession complete with dependencies
20:34 meylor yeah i haven't heard of that thanks
20:35 aboe joined #salt
20:41 fragamus joined #salt
20:49 viq joined #salt
20:50 JDiPierro joined #salt
20:55 quickdry21 joined #salt
20:57 jespada joined #salt
20:58 jespada whats the best resource to get started with salt?
20:58 stevednd virtualbox and the salt docs
20:59 stevednd there's little bits and pieces here and there in blog posts
20:59 jespada tks!
21:03 otter768 joined #salt
21:03 aqua^mac joined #salt
21:05 Mso150_n joined #salt
21:12 zadock joined #salt
21:12 twellspring joined #salt
21:19 rocket stevednd: for the salt command what config file is read?
21:20 yomilk joined #salt
21:36 stevednd rocket: just the plain `salt` command should be picking up on /etc/salt/master
21:36 rocket stevednd: and for the plain salt command how do I have it connect to a remote master?
21:37 stevednd I'm not sure I understand your question. the salt command interacts with the salt-master service to issue commands to its minions
21:37 stevednd salt-call will operate locally
21:38 rocket right so I am asking, on my mac I want to connect to the salt infrastructure and have it run the highstate for all my nodes
21:38 rocket eg mac laptop is a management workstation that connects to the salt master to issue the commands
21:39 rocket or do you have to login to the salt master to issue all the commands?
21:39 stevednd afaik it doesn't work that way. I just use ssh for that
21:40 stevednd yep, ssh in and issue the commands
21:40 babilen You could, naturally, use salt-ssh, but then you cannot use master specific functionality. If you want a master you work on the master.
21:41 rocket ok, I had confusion about that.  Just a difference in how you can issue the commands via chef for example.  Thanks guys
21:42 babilen There is salt-api, but you would typicallylog into your master.
21:42 babilen mosh ftw
21:50 FRANK_T joined #salt
21:51 bhosmer joined #salt
21:54 nitti joined #salt
22:03 aquinas_ joined #salt
22:05 Mso150 joined #salt
22:06 redzaku joined #salt
22:15 fragamus joined #salt
22:29 Ahlee rocket: I use salt-api, combined with libpepper.  I rarely actually log into my salt-master
22:37 otter768 joined #salt
22:42 iml joined #salt
22:43 ajw0100 joined #salt
22:47 out180 joined #salt
22:52 aqua^mac joined #salt
22:53 vbabiy joined #salt
22:55 rocket Ahlee: for the username/password does it use the pam system to authenticate?
22:57 ocdmw joined #salt
23:12 Ahlee rocket: it can, yes.  That is how we do it.
23:12 beneggett joined #salt
23:16 anotherZero joined #salt
23:18 arno joined #salt
23:25 ckao joined #salt
23:33 JlRd joined #salt
23:33 garthk left #salt
23:41 ajmccluskey joined #salt
23:43 cberndt joined #salt
23:55 diegows joined #salt

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