Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2014-01-12

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

All times shown according to UTC.

Time Nick Message
00:03 forresta jeremyBass, I don't know, I'm not familiar enough with vagrant to have a solution. I'm just imagining it like I would in the past in chroot situations, no understanding/referencing of the chroot means you're running the main process (if it exists) again, not the secondary instance.
00:03 psyl0n joined #salt
00:05 jeremyBass @forresta yes fair enough, what is really why i was trying to solve the first thing with out all the added info.. really i figure if i can ssh in .. then run commands `xxxxxxxxx` and 'yyyy' then it will change the root so that i can not rerun the server's provsioner, but now the project's location in a different folder ..
00:05 forresta yea
00:05 forresta I'd suggest to add some additional commands that return output in some way so that you can investigate what it's considering as 'valid' at the time those commands are run
00:06 jeremyBass if i can solve that then i can force the rest.. but ti's that change the root and run that i can't seem to get
00:06 jeremyBass that was what jfzhu_us was trying to help me with
00:07 Marion joined #salt
00:08 jeremyBass it would be nice if i could just simple have a sub.state: or something to run from the sls .. lol..
00:08 forresta yea that might be worth posting on the mailing list to see if they have any ideas.
00:09 jeremyBass well there has to be some way to CL this right? .. i mean to ssh in .. then change roots adn run which would do the projects stack?
00:09 forresta I'd think so.
00:10 jeremyBass well that is the key to get running for me it seems..
00:11 jeremyBass but as of yet can't seem to change it's root .. so it always just runs the servers
00:12 forresta right, that's why I'm saying you should run some commands via states to see what the status is, to see if anything is getting pushed to that root or not.
00:12 Gareth 'lo
00:12 forresta hey
00:13 jeremyBass guess I'm not sure what commants your thinking I should be running
00:13 jeremyBass commands*
00:13 ConceitedCode joined #salt
00:15 forresta maybe try echoing system variables, or checking getenv, or maybe try ltrace
00:16 jeremyBass ltrace what thou? sorry trying not to be denese here but I'm new to salt
00:17 forresta random system processes, salt itself, etc. . You want to look for differences between your primary 'environment' and what environment you think you're part of. Is stuff installed in the main environment that wouldn't be installed in the secondary? So when you log in via SSH you aren't seeing those items? If so, run commands with salt that will give you information about whether it's seeing those items or not.
00:19 jeremyBass oh boy.. um.. i have only one environment I'd think.. the one vagrant set up with the salt provsioning.. then i ssh in to that box.. not sure what you mean by another environment
00:19 forresta it's the same box you said though right?
00:20 forresta vagrant just creates a fake container
00:20 forresta or a real container, however you want to consider it
00:20 jeremyBass yes.. a headless VirturalBox .. then runs the provisions on it
00:22 jeremyBass that VB is what i have been ssh into to test out trying to chnage the root and get the projects salt to run
00:23 jeremyBass sorry I'm know I'm being difficult here cause of the learning curve
00:23 forresta nah, I just don't know enough about vagrant to provide more
00:24 forresta but it seems to me that simply checking something out and then re-running highstate isn't enough.
00:25 jeremyBass well what i know is that the salty-vagrant was pulled in to the core.. i get that it sets it up stuff i don't know about for salt to work.. that what is set up is what sets the root i guess.. so when i ssh in to salt-call state.highstate, it reruns the server provisioning
00:26 forresta yea which is odd
00:26 jeremyBass so what the commands are to change so that i can run it again and get the project is the missing part.. i have done the
00:27 jeremyBass salt-call -c /folderpath/to/the/project state.highstate
00:27 jeremyBass but then still runs the server.. so . your very first thing.. the BR you pasted
00:27 forresta if you use -c you need to make sure to change the settings in the conf file as well, like I noted on that issue.
00:28 forresta so you'd have to modify the root_dir
00:28 jeremyBass so what command what i do to do that?
00:28 forresta that's one of the things I note in the issue, you can't change the root_dir with a command (which I was requsting be added), you have to modify the conf itself.
00:29 jeremyBass oh god.. so there is not a way to do this.. so what i was doing in vagrant file was killing off the salt state, changig the files and is why it was working?
00:30 dleedyna joined #salt
00:30 forresta Probably? I didn't look that closely at the vagrant file. But yea, when you reference -c, it reads the data from that conf, but if that conf has /srv/salt/pillar or whatever, it just reads that again
00:30 forresta so that's probably why it was reprovisioning
00:31 forresta so you'd want to make the conf a managed file.
00:32 jeremyBass dang it.. not soundling like good news or clean..
00:32 jeremyBass and at that, i don't even kow where that file is per say.. it's made by vagrant
00:33 jeremyBass so what i need to do is over wirte the file with a one line comand that have the new path in it is what i need to do maybe?
00:33 forresta yea, hey akoumjian are you aorund?
00:34 forresta jeremyBass, maybe overwrite, or maybe provision the instance with a file in place that references the new items, and then reference that one in your -c call
00:37 jimallman joined #salt
00:37 jeremyBass hmm .. so . dang .. guess this is why I'v had to come here.. the docs are not clear, and i was trying to solve this on my own.. so.. i need a config file.. and um..
00:37 Dale22 joined #salt
00:38 jeremyBass dang I'm a see example learn how kinda person lol
00:38 jeremyBass kiling me
00:38 forresta well, you're trying to use salt to provision a vagrant instance that you're then running as a salt master
00:38 forresta which is a weird thing to do
00:38 forresta I haven't seen any instances of people doing that
00:39 jeremyBass well how do people not shove everything in one salt stack i guess is a good root question
00:40 forresta I guess I don't understand your need for multiple masters in this situation, are you trying to provision different environments, each with their own salt master?
00:40 jeremyBass i see ppl doing things like the server and wordpress or server adn elesticsearch all in one.. but how to do just the server and then the app so it's not all joined
00:40 jeremyBass well there is one server for all of our server.. but many apps, all run on the same
00:41 jeremyBass so there is a clear line.. server has the same salt stack. but the apps are all over the place..
00:41 forresta right, so that's why you use targeting data to ensure that certain machines get certain sets of states
00:42 jeremyBass yes.. that i get.. but having all those app in the same place it what is the issue.. right now it's two.. but soon there will be like 15 then ++ .. so one repo with it all.. that will be big and dirty
00:43 forresta if you use gitfs, you can always use mutliple remotes: http://docs.saltstack.com/topics/tutorials/gitfs.html#multiple-remotes
00:45 jeremyBass but it's all in the first server repo right?  .. meaning that when i look to the folder I'll be polluting that base with app orientated .sls fils and what not right?  I looked at that, but seems like I'm just merging the apps into the server ?
00:47 forresta well, usually you'd have base states, which every machine gets
00:47 forresta then the other machines (targeted in your top or whatever), get states unique to each application that you need
00:48 forresta so maybe you have one repo that is all your base states, then the second repo is the states associated with app1, so on and so forth
00:51 jeremyBass ok.. so .. what i end up with is the base repo.. i check it out to set up the sever but i have to merge in the app1 so that the app's provision .sls are in the same location as the servers?  so what happens is that the checked server base gets all the apps dumped accorss all the server base folders?
00:52 forresta doesn't salty-vagrant support running states on the newly provisioned instance?
00:53 jeremyBass idk..
00:53 jeremyBass what I'm trying not to do is hard code al the apps in teh server base
00:54 jeremyBass the problem with the docs is that it's a section of a file that is unclear where it is .. so i cna't learn by example.. makes this hard
01:11 ajw0100 joined #salt
01:13 jeremyBass ok I'll have to come back.. i need to take a break and eat lol..
01:13 jeremyBass thanks for the help
01:18 djinni` joined #salt
01:18 jfzhu_us jeremyBass: Apparently you can only have a single salt-call state.highstate running at a time so you can't call state.highstate from a salt file. I recommend using an atqueue
01:19 jfzhu_us Anyways, I have spent way too long on your problem so I'll be doing something else for the rest of the day if you don't mind too much
01:19 jfzhu_us left #salt
01:22 jdenning joined #salt
01:34 jeremyBass @jfzhu_us thankyou for the help
01:35 troyready joined #salt
01:37 yomilk joined #salt
01:41 jeremyBass so question thing .. is there a repo that uses the gifs or that may have some example of a stack that uses external files?
01:58 jdenning joined #salt
01:59 srijan4 joined #salt
02:00 scalability-junk joined #salt
02:01 xerxas joined #salt
02:04 Guest64230 joined #salt
02:08 akitada joined #salt
02:25 yomilk joined #salt
02:26 vipul joined #salt
02:27 kermit joined #salt
02:34 elfixit joined #salt
02:36 dangra1 joined #salt
02:39 fllr joined #salt
02:45 kermit joined #salt
02:56 kermit joined #salt
02:56 taion809 joined #salt
02:58 MedicalJaneParis left #salt
03:03 pdayton joined #salt
03:04 xmltok joined #salt
03:05 rojem joined #salt
03:06 PLA1_ joined #salt
03:15 juicer2 joined #salt
03:21 cbloss left #salt
03:35 Dale22 joined #salt
03:58 yomilk joined #salt
04:05 pdayton joined #salt
04:28 Hipikat left #salt
04:40 sroegner joined #salt
04:40 xmltok joined #salt
05:00 bhosmer joined #salt
05:18 chuyskywalker joined #salt
05:19 chuyskywalker I'm using vagrant+salt and I've got vagrant adding another VDI to the machine, and the mount state seems pretty straight forward -- but how do I get the drive formatted in the first place?
05:37 jdenning joined #salt
05:42 NV joined #salt
06:11 test2202 joined #salt
06:29 sroegner joined #salt
06:34 yomilk joined #salt
07:03 rmt joined #salt
07:11 ConceitedCode joined #salt
07:13 micko joined #salt
07:48 jeddi chuyskywalker: is there a cmd you can run that returns true / false based on whether the partition is already formatted?  if so you can just brute force it with a cmd.run / unless construct.  (i'm *sure* there are more elgant and salty ways of doing this - but refactoring is easy once you've got it going)
07:49 mayfield joined #salt
07:58 fllr joined #salt
08:04 blast_hardcheese joined #salt
08:04 chuyskywalker jeddi: that's kinda where I am leaning, just wanted to check if there was a salt way to do this or not. So far I haven't found it.
08:05 jeremyBass i just did something like that
08:06 matanya joined #salt
08:06 jeremyBass the cwd.run way i mean
08:08 jeremyBass something like `/sbin/parted -lm  |  grep -qi "the prase"
08:08 jeremyBass returns true or false which i used as a state
08:09 jeremyBass not sure if there is a better way though
08:18 sroegner joined #salt
08:26 elithrar joined #salt
08:27 elithrar Hi all. What's the best way to invoke update-rc.d using a state file? Trying to add a couple of new Redis instances.
08:27 elithrar (Ubuntu 12.04, if that helps)
08:29 jeddi jeremyBass: Nice. .  I've done quite a few constructs like that for different things, but not yet formatting file systems.
08:31 jeddi elithrar: pretty much what we were just talking about before you came in :)  -- *A* way (not sure if best) is to cmd.run it and do an -unless looking for some condition that would be set if it's already beenrun (ls /etc/init.d/Sxxredis  for example)
08:31 jeddi elithrar: doesn't redis package install its own init scripts?
08:33 yomilk joined #salt
08:35 elithrar jeddi: Yes, but I'm adding a second instance (because Redis is single threaded) and need to add a second init script, config file and then start it up :)
08:36 elithrar jeddi: But otherwise it looks like cmd.run should work. I noticed there is debian_service module but not sure how to use it in a state file?
08:36 elithrar http://docs.saltstack.com/ref/modules/all/salt.modules.debian_service.html
08:38 kaiyou joined #salt
08:55 nebuchadnezzar joined #salt
09:00 deepakmdass joined #salt
09:03 bhosmer joined #salt
09:08 yomilk joined #salt
09:28 ckao joined #salt
09:51 ajw0100 joined #salt
09:55 njpatel joined #salt
10:06 sroegner joined #salt
10:13 ajw0100 joined #salt
10:41 apergos yay finally able to duplicate in a test environment the slow salt bug:
10:42 apergos https://github.com/saltstack/salt/issues/8087
10:44 apergos and now I go away instead of finishing up the testing, cause, must eat, must buy foodstuffs
10:54 fxhp joined #salt
10:56 njpatel joined #salt
11:10 marcel joined #salt
11:14 austin987 joined #salt
11:38 gnu-man joined #salt
11:43 balltongu joined #salt
11:43 echos joined #salt
11:43 Jahkeup joined #salt
11:47 chuffpdx joined #salt
11:47 akitada joined #salt
11:47 juniorzoid joined #salt
11:47 lahwran joined #salt
11:47 octarine joined #salt
11:47 abele joined #salt
11:47 modafinil joined #salt
11:47 tmmt joined #salt
11:47 jmccree joined #salt
11:47 vortec joined #salt
11:47 bwq joined #salt
11:47 jeblair joined #salt
11:47 seba joined #salt
11:47 copelco__ joined #salt
11:47 dwfreed joined #salt
11:47 bezaban joined #salt
11:47 mordred joined #salt
11:47 sashka_ua joined #salt
11:47 gadams joined #salt
11:47 jY joined #salt
11:47 kuL4 joined #salt
11:47 fxdgear joined #salt
11:47 iMil joined #salt
11:47 fivethreeo joined #salt
11:47 EntropyWorks joined #salt
11:47 chitown joined #salt
11:47 dcmorton joined #salt
11:47 bigmstone joined #salt
11:47 twiedenbein joined #salt
11:50 anuvrat joined #salt
11:51 njpatel joined #salt
11:51 rmt joined #salt
11:51 NV joined #salt
11:51 dangra1 joined #salt
11:51 tzero joined #salt
11:51 MK_FG joined #salt
11:51 skullone joined #salt
11:51 indymike joined #salt
11:51 kamal_ joined #salt
11:51 [vaelen] joined #salt
11:51 cyp joined #salt
11:51 kossy joined #salt
11:51 nhubbard joined #salt
11:51 ahammond joined #salt
11:51 fuser joined #salt
11:51 codysoyland joined #salt
11:51 45PAAZ0RX joined #salt
11:51 rhand joined #salt
11:51 tempspace joined #salt
11:51 luminous joined #salt
11:51 _ikke_ joined #salt
11:51 mr_chris joined #salt
11:51 Dinde joined #salt
11:51 djanos_ joined #salt
11:51 carmony joined #salt
11:55 sroegner joined #salt
11:57 gnu-man joined #salt
12:00 matanya joined #salt
12:08 gnu-man_ joined #salt
12:14 psyl0n joined #salt
12:17 homelinen joined #salt
12:20 zzzirk joined #salt
12:22 viraptor1 joined #salt
12:30 deepakmdass joined #salt
12:32 honestly joined #salt
12:33 dangra joined #salt
12:45 linjan joined #salt
12:45 bhosmer joined #salt
13:23 deepakmdass joined #salt
13:24 aleszoulek joined #salt
13:43 psyl0n joined #salt
13:44 sroegner joined #salt
13:51 zooz joined #salt
14:01 psyl0n joined #salt
14:02 psyl0n joined #salt
14:30 eonman joined #salt
14:34 eonman Hi I am new to salt and python..just started to learn both ..
14:34 eonman got this error and would be glad if someone can point me to the right direction
14:34 eonman z@z-ThinkPad:~/project$ cat test.py
14:34 eonman import salt.client
14:34 eonman SnakeInSalt = salt.client.LocalClient()
14:34 eonman SnakeInSalt.cmd('*',test.ping)
14:34 eonman z@z-ThinkPad:~/project$ python test.py
14:34 eonman Traceback (most recent call last):
14:34 eonman File "test.py", line 4, in <module>
14:34 eonman SnakeInSalt.cmd('*',test.ping)
14:34 eonman NameError: name 'test' is not defined
14:34 eonman z@z-ThinkPad:~/project$
14:37 dleedyna joined #salt
14:41 pdayton joined #salt
14:49 gnu-man joined #salt
14:56 dleedyna joined #salt
14:57 ndrei joined #salt
15:09 oz_akan_ joined #salt
15:30 sroegner joined #salt
15:32 oz_akan_ joined #salt
15:40 jeremyBass joined #salt
15:41 eonman left #salt
15:46 djanos joined #salt
15:57 jimallman joined #salt
16:12 nn0101 joined #salt
16:18 anuvrat joined #salt
16:18 insatsu joined #salt
16:19 djanos joined #salt
16:28 dleedyna joined #salt
16:30 rojem joined #salt
16:32 dleedyna joined #salt
16:55 juniorzoid left #salt
16:55 djanos joined #salt
16:56 ede joined #salt
16:57 markm joined #salt
17:02 DanGarthwaite joined #salt
17:05 djanos joined #salt
17:08 dleedyna joined #salt
17:13 anuvrat joined #salt
17:19 _ilbot joined #salt
17:19 Topic for #salt is now Welcome to #salt - SaltConf Jan 28-30, 2014! http://saltconf.com (reg deadline January 3) | 0.17.4 is the latest | Please be patient when asking questions as we are volunteers and may not have immediate answers - Channel logs are available at http://irclog.perlgeek.de/salt/
17:21 ndrei joined #salt
17:21 davet joined #salt
17:22 Marion joined #salt
17:26 _ilbot joined #salt
17:26 Topic for #salt is now Welcome to #salt - SaltConf Jan 28-30, 2014! http://saltconf.com (reg deadline January 3) | 0.17.4 is the latest | Please be patient when asking questions as we are volunteers and may not have immediate answers - Channel logs are available at http://irclog.perlgeek.de/salt/
17:30 _ilbot joined #salt
17:30 Topic for #salt is now Welcome to #salt - SaltConf Jan 28-30, 2014! http://saltconf.com (reg deadline January 3) | 0.17.4 is the latest | Please be patient when asking questions as we are volunteers and may not have immediate answers - Channel logs are available at http://irclog.perlgeek.de/salt/
17:37 fllr joined #salt
17:39 matanya joined #salt
17:39 harobed_ joined #salt
17:40 harobed_ joined #salt
17:45 ccase joined #salt
17:47 jeremyBass left #salt
17:52 ConceitedCode joined #salt
17:54 logix812 joined #salt
17:54 ajw0100 joined #salt
17:59 deepakmdass joined #salt
18:07 gnu-man joined #salt
18:07 markm joined #salt
18:29 psyl0n joined #salt
18:33 gnu-man joined #salt
18:33 haard joined #salt
18:36 markm joined #salt
18:45 aleszoulek joined #salt
18:45 scott_w joined #salt
18:51 eliasp joined #salt
18:53 fllr joined #salt
19:04 markm joined #salt
19:10 haard left #salt
19:10 harobed joined #salt
19:11 harobed joined #salt
19:16 haard joined #salt
19:18 JesseCW joined #salt
19:18 JesseCW left #salt
19:24 rojem joined #salt
19:29 markm joined #salt
19:38 ajw0100 joined #salt
19:40 SashaO joined #salt
19:41 fllr joined #salt
19:42 Gifflen joined #salt
19:43 SashaO Hi Salt experts, wondering if someone can help with an error in salt-cloud: RuntimeError: Please set SaltCloud._default_logging_logfile_.  Full trace is in RuntimeError: Please set SaltCloud._default_logging_logfile_
19:44 SashaO *full trace is https://gist.github.com/SashaOv/b407b921fd5988f57370
19:46 tactics joined #salt
19:48 ilbot3 joined #salt
19:49 tactics hi guys. new to salt, and google is not turning anything up for me. I'd like to parameterize my .sls, so that, for example, I can write an sls to create a user with various properties, and then pull it in several times specifying the name of the user. this isn't per node config, it's me trying not to repeat myself with several almost identical sls files.
19:50 tactics templating would seem to be the way to go, but I can't work out if I can get declare a template parameter when referencing the sls
19:54 tactics so basically, is there an equivalent to puppet's parameterized classes?
19:56 ilbot3 joined #salt
19:59 harobed_ joined #salt
20:00 harobed_ joined #salt
20:00 linjan joined #salt
20:16 scott_w joined #salt
20:19 nkuttler can somebody here recommend an archive hoster? never used glacier before and i'm looking for some input
20:20 toastedpenguin joined #salt
20:21 nkuttler tactics: if it's not per node what does the var depend on?
20:22 tactics i'd just like to write a reusable formula. for example, I have written a formula which ensures my dotfiles are checked out for a user. i'd like to be able to apply that to any user, not hard code the paths
20:23 tactics dotfiles/init.sls:
20:23 tactics git@host:dotfiles.git:
20:23 tactics git.latest:         - rev: master         - target: /home/{{ user }}/.dotfiles         - identity: /home/{{ user }}/.ssh/id_git_rsa
20:23 tactics then elsewhere:
20:23 tactics include: dotfiles
20:23 tactics - user: tactics
20:24 tactics i think I'm supposed to do this with pillar, but it means more complixity than I was after for my small number of nodes...
20:25 nkuttler tactics: i use {% set user='foo' %} in foo.sls and then include whatever to render
20:25 nkuttler but not sure if that's what you're looking for
20:25 tactics every node might have the same set of 5 users, no need for config. but lots of almost identical formulas
20:25 tactics if user is available in included formulas, then that might come pretty close, yeah
20:26 nkuttler include with context
20:26 nkuttler that's a jinja feature iirc
20:26 tactics cool, thanks. i'll go and give that a shot
20:37 SashaO joined #salt
20:37 yomilk joined #salt
20:38 scott_w joined #salt
20:48 rojem joined #salt
20:49 rojem joined #salt
20:52 psyl0n joined #salt
20:54 tactics almost, i think. I've realised how to describe exactly what I want though. file.managed has a "context". I want that for included sls formulas rather than for managed files
21:01 ajw0100 joined #salt
21:04 cewood joined #salt
21:08 homelinen joined #salt
21:08 homelinen joined #salt
21:08 taion809 joined #salt
21:08 fllr joined #salt
21:09 SashaO left #salt
21:10 yomilk joined #salt
21:13 taion809 joined #salt
21:33 aleszoulek joined #salt
21:38 robbyt joined #salt
21:41 tactics joined #salt
21:41 scott_w joined #salt
21:46 bhosmer joined #salt
22:03 danielbachhuber joined #salt
22:06 yomilk joined #salt
22:06 sroegner joined #salt
22:12 jeddi joined #salt
22:14 bhosmer joined #salt
22:17 martoss joined #salt
22:29 sroegner joined #salt
22:34 troyready joined #salt
22:35 Linz joined #salt
22:39 viraptor1 joined #salt
22:40 yomilk joined #salt
22:45 martoss1 joined #salt
22:46 bhosmer joined #salt
22:47 martoss joined #salt
22:48 rojem joined #salt
22:50 yomilk joined #salt
22:57 fllr joined #salt
23:04 Linz joined #salt
23:05 bhosmer joined #salt
23:17 shaunokeefe joined #salt
23:19 yomilk joined #salt
23:27 elithrar joined #salt
23:31 aleszoulek joined #salt
23:43 bhosmer joined #salt
23:43 elithrar Has anyone set up multiple redis instances using Salt? My issue is that Salt can't determine whether a specific instance is running as if it's using ps (and not upstart), the name is redis-server for *all* instances
23:46 forresta joined #salt
23:48 Ryan_Lane joined #salt
23:53 foxx joined #salt
23:54 yomilk joined #salt
23:54 yomilk joined #salt

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