Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2014-01-11

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

All times shown according to UTC.

Time Nick Message
00:00 juso UtahDave: trying it now, will take another 20-30 minutes
00:01 psyl0n joined #salt
00:05 kedo39 has anyone had an issue with "Multiple dictionaries defined in argument of state" when listing making a list of requirements?
00:05 kedo39 the code and error here: http://pastebin.com/Xi5DzkGK
00:09 alunduil joined #salt
00:15 retr0h joined #salt
00:15 juso UtahDave: at least first sync runs fine (kicked off manually, for some reason doesn't sync with the 'start menu->programs->startup', as I mentioned before), will continue testing for the next couple of days, let you know the results, before Mon you'll know the situation on my side.
00:18 wkf joined #salt
00:27 fllr joined #salt
00:27 zzzirk joined #salt
00:28 EugeneKay joined #salt
00:31 timoguin joined #salt
00:31 alunduil joined #salt
00:34 jcsp joined #salt
00:39 Ryan_Lane2 joined #salt
00:43 juso UtahDave: still have problems with the first sync after windows install, will do investigation tomorrow and provide results of the analysis
00:43 juso it's nothing to do with cr/lf, but with the first run of salt-call after windows install
01:03 mgw joined #salt
01:17 dleedyna joined #salt
01:17 cdcalef hmm
01:18 cdcalef why would salt-ssh keep telling me "Permission denied for host strongviewdb, do you want to deploy the salt-ssh key? (password required):" when i'm telling it to use a private key with --priv and i can ssh without a password using the regular `ssh` command?
01:20 xzarth joined #salt
01:36 elfixit joined #salt
01:39 sgviking joined #salt
01:39 retr0h joined #salt
02:01 rojem joined #salt
02:02 rojem joined #salt
02:03 rojem joined #salt
02:04 rojem joined #salt
02:07 Gifflen joined #salt
02:09 retr0h joined #salt
02:09 retr0h joined #salt
02:19 taion809 joined #salt
02:20 ConceitedCode joined #salt
02:22 mgw joined #salt
02:25 Gifflen joined #salt
02:30 dimeshake does anyone run salt in a python virtualenv?
02:31 dimeshake my old puppet box is centos5 and I'm running into issues with some of the newer python stuff required for salt-cloud and halite
02:31 dimeshake it may be easier to just set up salt on a more modern version rather than reuse the puppet box
02:31 dimeshake but right now i'm just testing
02:34 jfzhu_us joined #salt
02:36 wkf joined #salt
02:38 EugeneKay I'd just upgrade to 6.x TBQH :-p
02:38 EugeneKay Especially if you're testing; spin up a VM and do it there.
02:39 dimeshake yep
02:39 dimeshake I think that's the ticket.
02:47 pavera joined #salt
02:48 pavera so if I have some features to add to salt (or fixes) should I be creating feature/fix branches off develop or 2014.1 currently?
02:48 pavera I'm guessing develop since I'd imagine 2014.1 is about to release?
02:50 timoguin pavera, yes, new features would be off develop
02:51 taion809 joined #salt
02:52 MedicalJaneParis joined #salt
02:53 david_a joined #salt
02:54 pavera this is actually more of a bug fix
02:55 pavera its in the keystone state...
02:55 pavera but I'll build the pull request off develop, I just checked 2014.1 and its not fixed there either
02:57 druonysuse joined #salt
03:02 druonysus joined #salt
03:05 timoguin pavera, bug fixes go on the develop branch too. they then cherry pick them to the release branches.
03:10 redmin joined #salt
03:16 mgw joined #salt
03:25 druonysus joined #salt
03:28 anuvrat joined #salt
03:34 mgw joined #salt
03:37 psyl0n joined #salt
03:59 jfzhu_us joined #salt
04:12 zzzirk joined #salt
04:17 seanz Greetings. I'm getting an error running a highstate with salty vagrant: "Specified SLS ruby in environment base is not available on the salt master"
04:17 seanz Does this seem familiar to anyone?
04:18 dimeshake is it all self contained? ie, the master is the vagrant box, too
04:20 seanz dimeshake: It should be.
04:20 seanz My minion config file is just "file_client: local"
04:21 seanz Oh...maybe my pillar data is missing...checking.
04:23 seanz Oh right...there is no pillar data yet.
04:24 seanz That's not the issue here, though.
04:25 seanz Alright. Some dumb issue with a part of my salt state. Nothing to be alarmed about. User error.
04:26 dimeshake I had faith :)
04:26 seanz dimeshake: haha - thanks. :)
04:35 taion809 joined #salt
04:46 fllr joined #salt
04:48 xmltok joined #salt
04:49 zsoftich_ does jinja in salt state support jinja builtin tests?
04:49 fllr joined #salt
04:53 dimeshake I followed the salt-cloud walkthrough and am running into this after trying to provision an instance on ec2
04:53 dimeshake [INFO    ] salt-cloud starting
04:53 dimeshake [INFO    ] There is no AWS cloud provider configuration available. Not loading module
04:53 dimeshake [ERROR   ] Profile base_ec2 is not defined
04:53 dimeshake Error:
04:53 dimeshake Profile base_ec2 is not defined
04:53 dimeshake ugh, sorry for paste-spam
04:53 tollmanz joined #salt
04:54 Linz joined #salt
04:55 dimeshake ok, user error for me, this time.
04:55 dimeshake :)
05:04 kedo39 in case anyone wants salt to manage their btsync instances, i've created a formula here: https://github.com/kennydo/salt-btsync-formula
05:07 jcockhren oh!!
05:07 jcockhren kedo39:++
05:09 kedo39 unfortunately, it's debian-only since it uses yeasoft's debian repos
05:10 bhosmer joined #salt
05:14 dimeshake nice, kedo39
05:15 dimeshake grr. salt-cloud creates VM fine on ec2. salt '*' test.ping doesn't get a report from it, however
05:15 dimeshake key is signed
05:20 psyl0n joined #salt
05:29 xmltok joined #salt
05:38 psyl0n joined #salt
05:40 thrashr888 joined #salt
05:49 carmony sigh
05:49 carmony nothing like a last minute URGENT email that needs taking care of
05:52 tollmanz joined #salt
05:54 tollmanz joined #salt
06:01 Linz joined #salt
06:07 redmin left #salt
06:10 xinkeT joined #salt
06:24 rojem joined #salt
06:42 jeremyBass joined #salt
06:48 fllr joined #salt
06:50 fllr joined #salt
06:52 fllr joined #salt
06:54 tollmanz joined #salt
06:55 jeremyBass would anyone know any way to dynamically set file_roots: and pillar_roots:?   like - /srv/*/salt/pillar ?
06:56 tollmanz joined #salt
06:57 techdragon joined #salt
07:06 gildegoma joined #salt
07:23 drogoh joined #salt
07:36 pdayton joined #salt
07:40 jeremyBass left #salt
07:45 sroegner joined #salt
07:48 anuvrat joined #salt
07:50 fllr joined #salt
07:54 tollmanz joined #salt
07:55 taion809 joined #salt
08:00 retr0h joined #salt
08:00 fllr joined #salt
08:05 rmt joined #salt
08:26 anuvrat joined #salt
08:43 gamingrobot joined #salt
08:43 rci joined #salt
08:43 pcarrier joined #salt
08:45 munhitsu_ joined #salt
08:50 fllr joined #salt
08:54 tollmanz joined #salt
08:56 MedicalJaneParis joined #salt
09:12 bud_ joined #salt
09:13 bud_ Hello World.
09:13 bud_ Can one pass pillar in peer publish.publish in a state through module.run?
09:15 shennyg joined #salt
09:17 ndrei joined #salt
09:17 goki joined #salt
09:20 bud_ I have tried to achieve that using the following states https://gist.github.com/anonymous/8368773.
09:23 bud_ It doens't work, it exits with no such sls file named "vhost pillar={}".
09:24 taion809 joined #salt
09:25 Furao joined #salt
09:26 ckao joined #salt
09:28 ajw0100 joined #salt
09:34 sroegner joined #salt
09:46 juso joined #salt
09:50 fllr joined #salt
09:51 ajw0100 joined #salt
09:54 tollmanz joined #salt
10:02 martoss joined #salt
10:03 martoss1 joined #salt
10:05 martoss2 joined #salt
10:07 pdayton joined #salt
10:16 njpatel joined #salt
10:16 micko joined #salt
10:24 linjan joined #salt
10:26 druonysus joined #salt
10:28 bud_ joined #salt
10:33 nliadm joined #salt
10:50 fllr joined #salt
10:53 bhosmer joined #salt
11:11 viraptor1 joined #salt
11:22 sroegner joined #salt
11:25 bud_ Is anyone around that has knowledge in peer publish?
11:30 giantlock_ joined #salt
11:31 Linz joined #salt
11:44 kedo39 joined #salt
11:49 njpatel joined #salt
11:50 fllr joined #salt
11:51 ndrei joined #salt
12:04 bhosmer joined #salt
12:11 Tekni joined #salt
12:19 ekristen joined #salt
12:40 bhosmer joined #salt
12:45 ndrei_ joined #salt
12:47 ndrei_ joined #salt
12:50 fllr joined #salt
12:50 ndrei_ joined #salt
13:06 ndrei_ joined #salt
13:07 anuvrat joined #salt
13:11 sroegner joined #salt
13:31 oz_akan_ joined #salt
13:49 psyl0n joined #salt
13:50 fllr joined #salt
13:52 crooton joined #salt
13:55 kb joined #salt
14:03 gnu-man joined #salt
14:11 zzzirk joined #salt
14:12 ndrei joined #salt
14:45 oz_akan_ joined #salt
14:50 fllr joined #salt
15:00 sroegner joined #salt
15:01 backjlack joined #salt
15:02 Linz joined #salt
15:10 Marion joined #salt
15:13 diegows joined #salt
15:14 martoss joined #salt
15:15 Furao joined #salt
15:19 taion809 joined #salt
15:22 sroegner joined #salt
15:28 taion809 joined #salt
15:29 ekristen joined #salt
15:38 Marion joined #salt
15:49 BazGee joined #salt
15:50 crooton joined #salt
15:50 fllr joined #salt
15:56 dangra joined #salt
16:06 quickdry21 joined #salt
16:09 martoss joined #salt
16:21 wkf joined #salt
16:31 KyleG joined #salt
16:31 KyleG joined #salt
16:35 kumarat9pm joined #salt
16:38 kumarat9pm left #salt
16:41 logix812 joined #salt
16:42 jimallman joined #salt
16:45 ndrei joined #salt
16:59 pdayton joined #salt
17:04 xmltok joined #salt
17:05 KyleG joined #salt
17:05 KyleG joined #salt
17:10 sroegner joined #salt
17:10 harobed joined #salt
17:11 philipsd6 How do people generally do the download, unpack, ./configure, make, make install dance using Salt?
17:12 philipsd6 I'm using archive to download and unpack into /tmp/, then cmd.wait to run the shell commands.
17:13 philipsd6 But I'm concerned about the brittleness of the process: if archive works ok, but the build fails for some reason, re-running the state will be a noop, as cmd.wait won't run because the archive state wouldn't change.
17:16 philipsd6 my testing sls is here: https://gist.github.com/philipsd6/8373711
17:18 rojem joined #salt
17:28 nebuchadnezzar joined #salt
17:34 matanya joined #salt
17:35 Gifflen joined #salt
17:35 bhosmer joined #salt
17:36 Gifflen joined #salt
17:37 ndrei joined #salt
17:44 jdenning joined #salt
17:59 davet joined #salt
18:03 gnu-man joined #salt
18:03 zzzirk joined #salt
18:07 jdenning joined #salt
18:11 xinkeT joined #salt
18:31 jfzhu_us joined #salt
18:40 mwmnj joined #salt
18:50 viraptor1 joined #salt
18:50 aleszoulek joined #salt
18:53 matanya joined #salt
18:59 sroegner joined #salt
19:02 sroegner joined #salt
19:08 Gifflen joined #salt
19:10 Gifflen joined #salt
19:17 bashcoder joined #salt
19:18 ajw0100 joined #salt
19:22 juicer2 joined #salt
19:22 njpatel joined #salt
19:23 MedicalJaneParis joined #salt
19:34 linjan joined #salt
19:35 logix812 joined #salt
20:02 rojem joined #salt
20:04 dccc joined #salt
20:10 micko joined #salt
20:25 aleszoulek joined #salt
20:30 oz_akan_ joined #salt
20:31 psyl0n joined #salt
20:32 psyl0n joined #salt
20:32 fllr joined #salt
20:32 psyl0n joined #salt
20:34 ajw0100 joined #salt
20:36 cachedout joined #salt
20:38 markm joined #salt
20:45 jeremyBass joined #salt
20:47 jeremyBass hello, I want to call a sub provisioning from one that is being done by Vagrant/salt.  Basically at the end of it run a command line call to start another salt provisioning
20:47 jeremyBass I hope that makes sense.
20:47 jeremyBass I do have a SO question open that goes deep in details
20:47 jeremyBass http://serverfault.com/q/566559/123138
20:55 wkf joined #salt
20:56 jfzhu_us jeremyBass: Oh hey. I was the guy trying to answer your question
20:57 jeremyBass super :D
20:58 jeremyBass to clarify things my original thought was that i could just run `salt-call state.highstate`  in the sub project folder and get it's provisionor set up running..
20:59 jfzhu_us Oh. So you got a vm without salt already installed and you are trying to bootstrap the vm?
21:01 jeremyBass well i am using vagrant.  pulling in the bootstrap.sh .. i run the server salt stack.. in the provisioning, it git clones a project in.. it has it's own saltstack, just like the base that is currently running
21:01 jeremyBass once that is called, i need to be able to run it's provisionor at some point near the end of the servers'
21:02 psyl0n joined #salt
21:02 psyl0n joined #salt
21:03 dazol joined #salt
21:03 jfzhu_us jeremyBass: Sorry I wans't clear. But are you running bootstrap.sh to install the salt minion on your server. From what I understand, there are some vagrant images that come pre-installed with salt.
21:04 jeremyBass yes, I'll past bin that in a sec
21:04 jeremyBass and this what what i ws hopping to put in the last `.sls` file of the server base.. http://pastebin.com/vhgwybA4
21:05 jeremyBass this is what I'm calling in vagrant
21:05 jeremyBass http://pastebin.com/2BCKUhhF
21:05 jeremyBass its using the downloaded bootstrap to do it's thing
21:06 wkf joined #salt
21:08 jfzhu_us jeremyBass: So after you have bootstrapped salt onto the node, does your last.sls not get run?
21:12 jeremyBass well no, all get run.. but i need to start a new one that is under the project that is git cloned in
21:14 jfzhu_us jeremyBass: So you basically want to run the initial salt provisioning which will pull a new directory with another set of sls files from github and then run those new salt state files
21:16 jeremyBass yes
21:17 jeremyBass i can control the set up up the subproject too.. it just has to be encapsulated is all
21:21 jfzhu_us jeremyBass: I am guessing that http://pastebin.com/vhgwybA4 didn't work in your case
21:22 jeremyBass yeah when i ssh in and cd there and run it, i just rerun the orginal server base provisioning that already ran
21:22 jfzhu_us jeremyBass: Yea that makes sense since you haven't changed your salt root directory to freshly pulled github directory
21:24 jeremyBass so i would need to do a highstate with options?  .. like use minion from this new folder?
21:25 Gifflen joined #salt
21:26 jfzhu_us jeremyBass: Let me just clarify. What is the current value for file_roots: in your /etc/salt/minion file?
21:28 jeremyBass in the server base .. - /srv/salt .. in the project folde that is cloned in , - /var/www/projectX/provision/salt
21:29 chutzpah joined #salt
21:31 jfzhu_us jfzhu_us: Do you pull the non-server provisioning sls files into /srv/salt or somewhere else?
21:32 darless So quick question. The pillar 'extend' functionality Issue #3991. Any ETA on that?
21:32 jeremyBass it's kept in it's folder structure.  the goal is to not pollute the server area with the app areas of provisioning..
21:33 nebuchadnezzar darless: I'm using reclass to structure my pillar, if it's what you are looking for
21:35 gnu-man_ joined #salt
21:35 jfzhu_us jeremyBass: Understood. So in your case you have two options. One change your file roots to your application provisioning section. This comes at the cost of not being able to run your server provisioning software. Your second option is to keep your current file_roots directory and modify the top.sls file so that it basically appends your application's top.sls files (with the paths to the sls files changed of course) to your server's top.sls files.
21:36 jeremyBass hmm.. both are highly dirty options it seems
21:37 jfzhu_us jeremyBass: yea...
21:37 jeremyBass there is no way to just say `salt-call  --changed/path/to/minion state.highstate` ?
21:38 jeremyBass if it all runs off the minion seems I just need to change the path to it and then run it again?
21:38 jfzhu_us jeremyBass: salt-call -m seems to work
21:38 jfzhu_us jeremyBass: Oh wait no. That's for modules
21:39 darless nebuchadnezzar: hmm not familiar with that. What I want to be able to do is have a default pillar file where I put common settings. Example sudoers, then other pillar files to have custom sudoers settings. The problem at the moment the 2nd pillar sudoers will overwrite all the default sudoers settings. That Issue #3991 'extend' seems like a perfect thing for this issue.
21:39 jfzhu_us jeremyBass: You could create another config file for salt minion which has a different file_roots directory and use it via salt-call -c
21:40 jeremyBass hmm that is what i thnk I'm looking for .. just don't see any -c in the help
21:40 jeremyBass oh wait
21:40 jfzhu_us its not a pretty solution =/
21:41 jeremyBass ok so `salt-call -c /var/www/project/provision/salt/ state.highstate` ?
21:41 jfzhu_us looks like it. Let me know if it works or not
21:43 jeremyBass nope.. doesn't seem to . `salt-call -c /var/www/project/provision/salt/ state.highstate` gets me
21:43 jeremyBass ERROR   ] This master address: 'salt' was previously resolvable but now fails to resolve! The previously resolved ip ad
21:43 jeremyBass dr will continue to be used
21:43 jeremyBass [WARNING ] Master hostname: salt not found. Retrying in 30 seconds
21:44 jfzhu_us do you have a file named minion in /var/www/project/provision/salt/ ?
21:44 jeremyBass well no the minion config is   www\WSUMAGE-base\provision\salt\minions\vagrant.conf
21:44 jeremyBass oh.
21:44 jeremyBass call the file
21:44 jeremyBass duh
21:46 jeremyBass ok didn't work.. `salt-call -c /var/www/project/provision/salt/minions/vagrant.conf state.highstate`  gets the same error
21:48 jfzhu_us jeremyBass: Let me run some tests and get back to you
21:48 jeremyBass rock on thank you..
21:48 jeremyBass seems odd that this is so hard.. but hey it is what it is :D lol..
21:50 jfzhu_us jeremyBass: It may seem harder because I am helping you. I am still relatively new to this stuff
21:51 jeremyBass lol.. well hey in the land of the blind the one eyed man rules
21:52 oz_akan_ joined #salt
21:54 ajw0100 joined #salt
21:57 jfzhu_us jeremyBass: I think you are using the wrong minion file
21:58 jeremyBass it's the only minion file i added to the projects folder structure though.. in fact it's basicly a match to the server base's just with in the project folder
21:59 jfzhu_us Well yea but the point of a custom minion file is so that you can temporarily change the file_roots directory so that it can point to your second project's sls file directory and call salt-call --local state.highstate
22:00 jeremyBass yes that is what i thought i read.. so i have the file_client: set to projectX .. and then tried runing  `salt-call --projectX state.highstate` but it's didn't work
22:01 jfzhu_us you want something like the following http://pastebin.com/BYrhNkQZ
22:01 jfzhu_us and then you can call salt-call salt-call -c /root/salt state.highstate where the minion file I pasted is in /root/salt
22:02 jfzhu_us although you could probably skip hte file_client part if you specify salt-call --local
22:04 jeremyBass you mean in the project folders? i did http://pastebin.com/Suk5A3fK .. that is the one in the project's salt folder .. and when i run salt-call --local it just reruns the base provsionor.. not the projects
22:05 jeremyBass sett the file gets the same issue.. `salt-call -c /var/www/project/provision/salt/minions/vagrant.conf --local state.highstate`
22:06 jeremyBass that gets the can't find file error, though I know it's there.. i nano it and see it's content
22:06 jeremyBass and at the it runs the server again
22:06 jfzhu_us Why are you setting it to be /var/www/project/provision/salt/minions/vagrant.conf ?
22:07 jeremyBass well that is the project folder.. and that is the minion that has the right paths in it..
22:08 jeremyBass the short of it it seems is that i need to switch out from the server to the project.. so i can provision that? .. idk.. little cloudy on how to get the secound project base one to run
22:09 jfzhu_us I have the following:
22:09 jfzhu_us ls /root/salt/
22:09 jfzhu_us minion  salt-run  top.sls
22:09 jfzhu_us I then run salt-call -c /root/salt state.highstate where it picks up my minion configuration file. I don't think you can specify the configuration file directly
22:09 jfzhu_us well that came out weird
22:10 jfzhu_us But basically, I have a file called minion in a directory and I specify the directory and not the configuration file.
22:12 jeremyBass hmm.. ok I'll try that.. just in case here is the folder structure i was talking about
22:12 jeremyBass http://pastebin.com/WQCueD69
22:12 rojem joined #salt
22:13 jeremyBass hmm i get minion is not a commant
22:13 jeremyBass command*
22:14 rojem joined #salt
22:15 jfzhu_us ah okay well why don't you put a modified minion file in /var/www/project_name/html/provision/salt/minions/ and run the command salt-call -c /var/www/project_name/html/provision/salt/minions state.highstate
22:16 jfzhu_us I am not sure about the minion is not a command erro
22:17 jeremyBass so that vagrant.conf file with http://pastebin.com/Suk5A3fK in it.. is what i have there.. and then i have ran `salt-call -c /var/www/project/provision/salt/minions --local state.highstate` and what i get is first an error that the file is not there, and then the server minion starts up and reruns that one again..
22:19 jeremyBass if it helps, here is the server base.. https://github.com/jeremyBass/WSU-serverbase-centos .. it pulls in the project folder from https://github.com/jeremyBass/WSUMAGE-base
22:21 jfzhu_us In my tests I renamed the minion file I had in /root/salt to be vagrant.conf and ran the command salt-call -c /root/salt state.highstate and it wasn't able to pick up that file. I think the file has to be named minion
22:22 jeremyBass hmm ok.. so from vagrant you set `salt.minion_config = "provision/salt/minions/#{minion}.conf"` .. so i leds me to think that i can do the same from the CL
22:22 jimallman joined #salt
22:23 jeremyBass i was doing a loop in the vagrant file that would do the salt one by one what just changed that location and it was working
22:23 jeremyBass but i wanted to not do that loop in the vagrant file, and just pull that into the server state
22:24 jeremyBass so that part of the server state is the provisioning of the app and what not
22:24 ajw0100 joined #salt
22:26 jfzhu_us So you are trying to make provisioning the app part of process of provisioning the server?
22:28 jeremyBass well sort of yes.. the goal is that first the server app git clones it in.. that works.. then i figured at the last .sls ran i could do something like this http://pastebin.com/vhgwybA4 .. where that would be running the provsioning of the app from with in the apps setup as shown by the two git repos like linked above
22:31 jfzhu_us why not modify the last.sls so that it uses a new config directory?
22:33 jeremyBass well how do you mean?  .. the last.sls right now just do the git clone of the project, but have have yet to add something to move forward.. just been runing command lines to test atm..
22:33 bhosmer joined #salt
22:33 jeremyBass this is what i have for the "last".sls .. really named projects.sls .. # We set up projects based on what is set up in the pillar data
22:33 jeremyBass # find settings in pillar/projects.sls
22:33 jeremyBass {% for project, project_arg in pillar.get('projects',{}).items() %}
22:33 jeremyBass load-project-{{ project }}:
22:33 jeremyBass git.latest:
22:33 jeremyBass - name: {{ project_arg['name'] }}
22:33 jeremyBass - target: /var/www/{{ project_arg['target'] }}
22:33 jeremyBass - unless: cd /var/www/{{ project_arg['target'] }}/provision/salt/config
22:33 jeremyBass {% if project_arg['rev'] is defined and project_arg['rev'] != '' %}- rev: {{ project_arg['rev'] }}{%- endif %}
22:33 jeremyBass {% if project_arg['remote_name'] is defined and project_arg['remote_name'] != '' %}- remote_name: {{ project_arg['remote_name'] }}{%- endif %}
22:33 jeremyBass {% if project_arg.get( 'force', False ) is sameas True %}- force: True{%- endif %}
22:33 jeremyBass {% if project_arg.get( 'submodules', False ) is sameas True %}- submodules: True{%- endif %}
22:34 jeremyBass dang it
22:34 jeremyBass http://pastebin.com/P4y1qst0 waht what i meant to past in
22:35 jeremyBass here .. the real file in it's base https://github.com/jeremyBass/WSU-serverbase-centos/blob/master/provision/salt/projects.sls
22:42 jfzhu_us My brain is a bit fried at this stage so I'll need a break before I can get back to you on that.
22:42 jeremyBass sure thing
22:43 jeremyBass seem odd that it's not a straight forward way to do a secondary provisioning
22:47 jeremyBass ok salt-master -c /var/www/project/provision/salt/minions sees to do something.. well not error.. hangs though..
22:52 jeremyBass hmm it just sits there till i hit ctrl+c then it just says `stopping the salt master`
22:57 ajw0100 joined #salt
22:57 maxleonca joined #salt
22:58 forresta joined #salt
22:58 maxleonca Hello, I'm playing with salt-cloud on Digital Ocean
22:59 maxleonca but seems that I'm missing something or salt-cloud 0.8.8-1 is broken for Centos 6
22:59 maxleonca I get an error even calling the help
22:59 forresta what version of salt are you using?
22:59 maxleonca does anyone have the same problem?
22:59 maxleonca well for salt itself I have 0.17.4
23:00 forresta yea you're using an old version of salt cloud, 0.17.X requires 0.8.11 or greater
23:00 maxleonca hmmm, ok
23:00 maxleonca thank you, I'll compile it then.
23:00 forresta just install via pip
23:00 forresta don't compile it
23:01 forresta much easier
23:01 maxleonca the packages are out of sync it seems, thanks for the advice
23:01 forresta yea pretty sure that's because 0.8.11 is only in epel testing
23:01 forresta yea np
23:04 jeremyBass hmm.. so wait i can't find anything that lets me say, don't run that saltstack use this new one.. can't you change the root everything runs from?
23:04 maxleonca you are 100% right, Thanks a lot Forresta I hope they post your presentation on SaltConf on the YouTube channel.
23:04 forresta maxleonca, Thanks! I'm looking forward to giving it, though I need a few more slides still, it's a bit short right now. Or maybe I need to talk slower
23:05 maxleonca well with any luck the Q&A will be help you on that.
23:05 forresta jeremyBass, I've created an issue on this a while back, https://github.com/saltstack/salt/issues/8649
23:05 forresta you should be able to just change the root_dir option
23:06 forresta maxleonca, yea, I don't like running up against the wall time wise on a presentation, I'd rather it be short than too long.
23:07 jeremyBass @forresta .. so can i impose on the line you'd think would work? .. i saw you can't in after  so I'm betting you didn't see what i was aimming at?
23:07 forresta yea I just logged in so I have no idea what it is past your last message.
23:09 jeremyBass the short of what i need to do is durgin the salt provisioning from vagrant, i do a git clone of a sub project.  at the end of the salt provsioning of the base, i need to run the provisioning of the sub project i cloned in
23:10 forresta oh, hmmm. I'm not quite sure how you could do that, are you using salt-vagrant?
23:12 jeremyBass yes.. well it's in vagrant now ... but i firgure one of two thing.. using http://pastebin.com/vhgwybA4 at the very 'last.sls' or just the command line to start it would work too..
23:12 jeremyBass i wanted it stateful to the base server provisioning
23:12 forresta oh I see, I thought this was a second 'instance' of salt running under the main container
23:13 jeremyBass well .. no i don't think that is needed.. i think... what i need to do is run the base from vagrant which is working.. then run the cloned projects after/at the end of the base's provisioning
23:14 forresta when you say 'cloned project' what do you mean by that? As in you provision an instance with vagrant, then you want to do stuff inside of that?
23:16 jeremyBass yes sort of.. i provision the server with vagrant ( https://github.com/jeremyBass/WSU-serverbase-centos ).. while it's doing that it git clones in that project.. ( https://github.com/jeremyBass/WSUMAGE-base ) .. that has it's own salt stack that needs to run..
23:17 jeremyBass so i figured that i could do cwd.run and call salt to run the projects provisioning
23:17 jeremyBass ideally it would be stateful to the server base
23:18 forresta interesting
23:19 jeremyBass the real file that is cloning in the project is  https://github.com/jeremyBass/WSU-serverbase-centos/blob/master/provision/salt/projects.sls   .. which in there is where I figured i could do the cwd.run to do the projects provisioning
23:20 jeremyBass to test i am ssh in to try to run the project provisioning
23:20 jeremyBass i have yet to get it to go.. it just reruns the server everytimg
23:20 jeremyBass evertime*
23:21 forresta yea I don't know how that would work since you'd technically be trying to run a secondary sub salt master almost...
23:22 jeremyBass yes that is ture .. but i figured it's just be a new thread .. but regardless i can always do an inline command from vagrant
23:22 jeremyBass but what i can't have is the server base being poluted with all the different projects
23:23 jeremyBass but they need provisioning too
23:23 forresta right
23:23 jeremyBass i could do config.vm.provision "shell", inline: " the call to the salt to provision the project" but I'm trying not to do that too
23:24 jeremyBass trying to keep it so i'm not messing with toms of files.. that it's more passive then having 5 files to change or something
23:24 forresta yea
23:25 Gifflen joined #salt
23:26 jeremyBass that was why i was figuring that http://pastebin.com/vhgwybA4 in the last.sls file of the server.. that was looped would work out nicely.. but i can't even do the projects from the command line. just runs the servers over and over
23:26 forresta :\
23:26 jeremyBass lol that is not reassuring haha
23:27 jeremyBass seems like it should be simple ... run provisioning from two spots .. regardless of order
23:27 forresta right, but you're still trying to run two instances of salt on the same box right?
23:28 jeremyBass well when you say instances you mean one state for the server and another for the project?
23:29 forresta no
23:29 forresta so you're provisioning a new instance of salt, with the salt master on a new server right?
23:29 forresta or vm, whatever.
23:29 bretep Is anyone here familiar with salt-cloud?
23:29 forresta I've been working on it recently bretep, what's up
23:30 bretep I'm trying to get it to work. Seems to just hang.
23:30 forresta ok, provider, salt master version, salt cloud version?
23:31 jeremyBass @forredta .. so this is what i was doing before.. https://github.com/jeremyBass/WSU-serverbase-centos/blob/97dbfd361d4f9ca5c3ebcab786017affb39c533c/Vagrantfile .. and that works.. down at the bottom you'll see that i run one salt from vagrant.. then loop over a hash with the projects.. and that worked.. but boy dirty dirty
23:31 bretep http://pastebin.com/jqfd2kh8
23:31 matanya joined #salt
23:31 bretep provider aws
23:32 forresta bretep, ok, so where does it hang up?
23:32 bretep Here is an example. http://pastebin.com/UXtjCKJZ
23:32 bretep Any command I run, stops at the same debug line
23:33 forresta jeremyBass, yea I'm not super familiar with vagrant, but I see that here. So when you run the provisioning script, and it gets to that last line, does it highstate again from the master, or just do nothing?
23:35 forresta bretep, so did you set your provider and master ip for the minion in your cloud.providers.d file?
23:36 forresta jeremyBass, I mean the last line of that state you provided earlier
23:36 jeremyBass well that was the old way.. which works for the most part.. but i need to remove that currectn is (https://github.com/jeremyBass/WSU-serverbase-centos/blob/master/Vagrantfile).. so i want to replace how that was working by one of two things, call cwd.run at the last .sls file (project.sls in that repo) and loop over it where it using the command line to call the provisioning
23:36 jeremyBass @forresta, no i didn't test that as it doesn't run when i ssh in to test it
23:36 bretep yep
23:37 bretep I'll get you a copy
23:37 bretep http://pastebin.com/ZYLsi9Rj
23:38 forresta jeremyBass, hmm, are we perhaps missing some sort of dep?
23:40 forresta so bretep, when it gets to that point where it reads your conf, it just sits there
23:40 forresta and never returns
23:41 jeremyBass well um.. no.. i have to repos .. the base that i have the vagrant in with the salt  ( https://github.com/jeremyBass/WSU-serverbase-centos ).... and while that is running it bring in the project via git clone.. ( https://github.com/jeremyBass/WSUMAGE-base ) .. that older Vagrant file that loops over projects detected work sort of.. but i took out the loop..
23:41 jeremyBass i need to replace the loop that was in the vagrant file with soemthing else that, i was hoping would be a command line, to provision the project..
23:42 jeremyBass i was hoping to do it in the last .sls of the serverbase via the cwd.run
23:42 forresta jeremyBass, yea I guess I am still confused. So you provision using salt and vagrant, a vagrant instance, which you then install the salt master/minion onto, and you're trying to run THAT instance's copy of salt-master right?
23:42 forresta we're talking about two unique machines/vms/instances
23:43 forresta provisioner, and the machine which is provisioned.
23:43 forresta or is this incorrect
23:44 jeremyBass no same box .. i was runing the salt provision 3 times in that old vagrant file.. all on the same box.. one set up nginx the other things like users for the app and what not
23:45 jeremyBass so all the server stuff ran first.. then in that loop over the project hast in the vagrant file i would provison the project  https://github.com/jeremyBass/WSUMAGE-base  which has it's own salt stack.. that did sort of work.. was spoty.. but got it running many times..
23:45 bretep forresta: correct, just hangs
23:45 forresta jeremyBass, ok, so how would what you have calling the highstate, force targeting on the second 'sub' salt?
23:45 bretep It'd be nice to get trace output of what it is doing
23:46 forresta bretep, yea strace would be your best bet there
23:46 bretep I ran strace... nodice
23:46 forresta nothing?
23:46 forresta hmm
23:46 bretep http://pastebin.com/gWsURff6
23:47 bretep That's where strace hangs
23:47 bretep I ran it with -F -f
23:47 bretep incase it was forking
23:47 forresta weird, so it reads the file and just does nothing, hmm
23:47 forresta ok bretep, let's try this
23:48 bretep Please give me some ideas. I have to take off with the fam, but will be back later tonight to try. :)
23:48 forresta create /etc/salt/cloud, set a line as the provider value to aws, then the minion: \n master: stuff
23:48 forresta then modify the cloud.providers.d file to remove the master line
23:49 forresta I'm just trying to duplicate what I have set up on DO that works
23:49 bhosmer joined #salt
23:49 jeremyBass @forresta so here.. http://pastebin.com/5BSzwyGj .. the top is the new way.. the goal is one run of the salt.. the old way looped over and ran each one..  ..
23:51 forresta jeremyBass, Right I understand what you are saying, but here is my confusion, we have a machine running a salt-master process. During it's highstate you are pulling in another instance of a salt setup, and then you try to run that second instance of salt that you have pulled in via git. Yet I don't see any service, or configuration associated with that salt process, there's no chroot forcing it to pull that instance, or anything like that
23:51 forresta . So to me it seems like you're just running the main salt again
23:53 ajw0100 joined #salt
23:54 jeremyBass @forresta well yes I end up runing the main one again, tested if i ssh in and just state.highstate .. which is i guess back to the root of the question how to switch and run a new one from the command line?
23:54 Heartsbane joined #salt
23:54 jeremyBass so what your saying is i need to be preping the new provsioner maybe?
23:55 jeremyBass vagrant does the prep by setting things liek the root and what not.. and I'm not when i'm ssh in and running the commands to test
23:55 jeremyBass whic is why I'm just rerunning the server's provisioned state
23:57 jeremyBass in short .. https://github.com/jeremyBass/WSU-serverbase-centos/blob/master/provision/salt/projects.sls in the loop i have commented out.. i need to do some commands to reroot, and then i can run it ?
23:58 jeremyBass well not run that as it was just a place holder
23:58 jeremyBass but the steps are reroot to the projects salt stack and then try to run?  ..

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