Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2015-08-09

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

All times shown according to UTC.

Time Nick Message
00:03 jjido left #salt
00:08 otter768 joined #salt
00:13 quasiben joined #salt
00:20 VR-Jack Sitting in this channel is bad for my browser. too many salt tabs openned. lol
00:20 aqua^c joined #salt
00:33 yomilk joined #salt
00:40 Tyrm joined #salt
00:41 quasiben joined #salt
00:43 bfoxwell joined #salt
00:46 herpoderp joined #salt
00:59 funzo joined #salt
01:07 fgimian joined #salt
01:15 omegamike joined #salt
01:24 VR-Jack2 joined #salt
01:24 ajmath_ joined #salt
01:28 cliluw joined #salt
01:36 sunkist joined #salt
01:39 zz_ashmckenzie joined #salt
01:45 yomilk joined #salt
01:59 digitalhero joined #salt
02:01 yota joined #salt
02:07 napsterX joined #salt
02:11 digitalhero joined #salt
02:16 quasiben joined #salt
02:26 dendazen joined #salt
02:30 funzo joined #salt
02:32 Tyrm joined #salt
02:34 VR-Jack2 ugh. just when you'd hope salt-ssh would just work. *sigh*
02:35 Tyrm joined #salt
02:35 VR-Jack2 with sudo: True, it looks for the initial file in /root when it's in the user's home (sudo changed $HOME). If you don't do sudo, well, good luck. lol
02:39 bluenemo joined #salt
02:39 bluenemo hi guys. what do you use for schema validation of pillar files?
02:44 bluenemo This sounds kind of like the answer: https://pypi.python.org/pypi/pepa/0.7.9
02:48 otter768 joined #salt
02:49 digitalhero joined #salt
02:52 XenophonF VR-Jack2: yeah, salt-ssh's predelection for sudo really harshes my mellow, esp. on FreeBSD where sudo is non-default
02:52 VR-Jack2 XenophonF: well, I'd like sudo if it would work, but there's issues with $HOME. apparently interpretted locally, not remove
02:52 VR-Jack2 err, remote
02:53 XenophonF that's a bummer
02:54 VR-Jack2 yeah. can't get it to do anything. I rewrote my local $HOME and now it fails with an authentication error. heh
02:54 XenophonF wish i could give you a clue :-/
02:56 VR-Jack2 oh, well. I don't like the tons of sudo logs anyways.
02:59 zmalone joined #salt
03:02 VR-Jack2 My son is properly trained now. If you say mercurial, he'll reply git.
03:02 aqua^c joined #salt
03:04 omegamike joined #salt
03:09 otter768 joined #salt
03:31 malinoff joined #salt
03:36 quasiben joined #salt
03:45 XenophonF heh
03:46 XenophonF man i really hope i'm not overthinking this vmware tools install state i'm writing :-/
03:51 XenophonF oh come on the windows package manager ignores the pkg.installed `version` argument?!
03:53 jeadr joined #salt
03:53 mkillebrew what about salt.cloud.clouds.vmware.upgrade_tools?
03:54 XenophonF oh thank god the docs are incorrect
03:54 XenophonF mkillebrew: omg i didn't know about that
03:54 XenophonF am rtfm-ing
03:54 mkillebrew I don't know if you can install with salt vmware, but that's probably best wrapped into the OS install, and upgraded on init
03:55 mkillebrew At least that's how I do it in Linux, don't touch Windows
03:56 digitalhero joined #salt
03:56 XenophonF mkillebrew: i just need to be able to update all of my existing guests
03:57 mkillebrew oh, well there you go then. I've yet to use it, but was reading docs getting ready to do autoscaling with vmware
03:57 XenophonF that module's new in 2015.5.4
03:58 mkillebrew I think previously it was vsphere, now deprecated
03:58 XenophonF oh man, that's so easy
04:00 XenophonF the upgrade_tools function isn't available in the old vsphere module :(
04:00 XenophonF but that's OK
04:01 XenophonF mkillebrew: thank you so much for the clue
04:02 XenophonF i'd rather use salt-cloud for this particular task anyway
04:02 mkillebrew cleaner audit trail
04:02 XenophonF true
04:03 XenophonF but also a ton simpler b/c i was going to have to keep track of which guests were running on which hypervisors in order to push the right versions of vmware tools to the guests, etc.
04:03 XenophonF much easier to say "vmware tools, upgrade thyself" in collusion with the hypervisors and vcenter
04:04 XenophonF mkillebrew: thank you again, this is worth waiting for 2015.5.4 for
04:12 VR-Jack2 well, I'm tired of it. heh. Fixed the $HOME bug (just added \' \' so the command passed through the shell to ssh), but apparently state.sls doesn't work. test.ping and cmd.run uptime did
04:17 VooDooNOFX joined #salt
04:42 VR-Jack2 heh. so it runs test.opts_pkg and that's as far as it got
04:44 fgimian joined #salt
04:52 omegamike joined #salt
04:52 favadi joined #salt
05:16 dendazen joined #salt
05:19 catpiggest joined #salt
05:24 fgimian joined #salt
05:24 VooDooNOFX joined #salt
05:42 favadi joined #salt
05:47 ninkotech joined #salt
05:54 stoogenmeyer_ joined #salt
05:54 krymzon joined #salt
05:56 dopesong joined #salt
06:01 Vynce joined #salt
06:02 timoguin joined #salt
06:02 Vynce so, is there a way to use individual state calls onthe command line?   like salt 'machine' user.absent 'exemployee' seems liek it should work but says "user.absent is not available"
06:06 jasonrm joined #salt
06:10 otter768 joined #salt
06:14 aurynn you have to use the modules for that, which are different
06:19 DanyC joined #salt
06:21 DanyC is any optin to set minion to clear/ trash the cache following/ during restart ? Same way you can set to run highstate
06:23 favadi joined #salt
06:23 DanyC *option
06:39 aqua^c joined #salt
06:42 bougie joined #salt
06:45 digitalhero joined #salt
06:48 slav0nic joined #salt
06:51 wryfi joined #salt
07:05 whytewolf Vynce: the user exacution module for deleteing a user is user.delete http://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.useradd.html#salt.modules.useradd.delete
07:07 favadi joined #salt
07:09 malinoff joined #salt
07:12 linjan joined #salt
07:18 evle1 joined #salt
07:30 malinoff joined #salt
07:35 markm__ joined #salt
07:37 favadi joined #salt
07:50 dthom91 joined #salt
07:58 moos3 joined #salt
08:07 peno joined #salt
08:22 thehaven joined #salt
08:22 yomilk joined #salt
08:25 ttrumm joined #salt
08:29 moos3 joined #salt
08:33 yomilk joined #salt
08:36 TyrfingMjolnir joined #salt
08:48 Vynce joined #salt
08:52 otter768 joined #salt
08:56 eightyeight joined #salt
09:00 eightyeight joined #salt
09:04 X67r joined #salt
09:05 Vynce yeah, i know modules are generally different.  I was hoping there was an idiom for, basically, writing a one-line state on the command line.
09:05 Vynce so that i don't have to learn executiion moduels as separate from states.
09:06 dopesong_ joined #salt
09:07 Vynce (also because searching for the modules is not always effective)
09:08 stoogenmeyer_ joined #salt
09:08 favadi joined #salt
09:09 Vynce ugh.  why is http://salt.readthedocs.org/en/latest/ref/modules/all/salt.modules.useradd.html#module-salt.modules.useradd still called useradd when it does things other than add?
09:09 moos3 joined #salt
09:12 sjorge Vynce: probably because it does all things 'useradd' does on unix?
09:12 sjorge actually useradd/usermod... you are right it makes no sense
09:13 whytewolf Vynce: because it has been useradd since the start of salt. most likely the original author thought it made more sense than. and they have not bothered to change it. the command is actually user.
09:13 Vynce it also hurts SEO, such that google(salt user module) doesn't actually turn up useradd
09:14 Vynce whytewolf: … which is also confusing. ( :
09:16 TyrfingMjolnir joined #salt
09:16 rodrigc joined #salt
09:17 pi3r12 joined #salt
09:17 whytewolf I typically don't use google for searching for modules/states. and just use the index. it isn't like there is an ever exhaustive list of states/modules
09:19 whytewolf also user works because it refers to both useradd and win_useradd
09:23 cyteen joined #salt
09:25 favadi joined #salt
09:34 TyrfingMjolnir joined #salt
09:38 dthom91 joined #salt
09:41 CeBe joined #salt
09:47 subsignal joined #salt
09:48 favadi joined #salt
09:56 markm__ joined #salt
10:18 harkx joined #salt
10:19 khapa joined #salt
10:22 krymzon joined #salt
10:23 TyrfingMjolnir joined #salt
10:28 moos3 joined #salt
10:30 dendazen joined #salt
10:51 sdebot joined #salt
10:53 otter768 joined #salt
10:58 moos3 joined #salt
10:59 stoogenmeyer joined #salt
11:09 aqua^c joined #salt
11:17 markm joined #salt
11:26 sdebot_ joined #salt
11:27 dthom91 joined #salt
11:44 bhosmer joined #salt
11:47 omegamike joined #salt
12:15 funzo joined #salt
12:27 favadi joined #salt
12:48 dopesong joined #salt
12:49 dopesong_ joined #salt
12:50 CeBe joined #salt
12:54 otter768 joined #salt
12:58 dendazen joined #salt
13:14 digitalhero joined #salt
13:16 dthom91 joined #salt
13:22 X67r joined #salt
13:22 digitalhero joined #salt
13:28 malinoff joined #salt
13:29 digitalh_ joined #salt
13:30 digitalh_ joined #salt
13:31 zmalone joined #salt
13:35 timoguin joined #salt
13:39 rogst joined #salt
13:39 codehotter joined #salt
13:41 ronrib joined #salt
13:42 yomilk joined #salt
13:46 funzo joined #salt
13:52 aqua^c joined #salt
13:55 dthom91 joined #salt
13:58 bhosmer joined #salt
14:00 aRkadeFR hey, how do you specify in a salt orchestration command that you target only some pillar values related to the minion ?
14:03 digitalhero joined #salt
14:03 aRkadeFR If I'm not wrong I don't find anything related in the doc: http://docs.saltstack.com/en/latest/ref/states/all/salt.states.saltmod.html
14:24 digitalhero joined #salt
14:30 favadi joined #salt
14:47 z3r0 joined #salt
14:53 clintberry joined #salt
14:54 otter768 joined #salt
14:55 XenophonF aRkadeFR: if you want to target minions based on whether they have a particular pillar key set, you can use either the -I or the - C arguments
14:55 XenophonF e.g., salt -I role:wordpress state.highstate
14:56 XenophonF e.g., salt -C 'I@role:wordpress and I@environment:production and G@os_family:FreeBSD' state.highstate
14:56 zmalone joined #salt
14:56 aRkadeFR I mean for salt-orchestration, the salt-run state.orchestrate orch.setup.test -l debug
14:57 aRkadeFR in this orch.setup.test.sls I have: salt.function: with tgt: 'XXXX' and arg: -XXXX
14:57 aRkadeFR can I do: tgt: '-I role:preprod' ?
14:57 aRkadeFR and it targets the minions with pillar role == preprod ?
14:58 XenophonF oh i see
14:59 XenophonF you'd need to use the arguments  `tgt: role:preprod` and `tgt_type: pillar`
14:59 aRkadeFR ah cool :)
14:59 aRkadeFR thanks
15:00 XenophonF or `tgt: I@role:preprod and G@os_family:Windows` and `tgt_type: compound`
15:00 aRkadeFR wasn't sure it was meant to be used like this
15:00 aRkadeFR I'll be ok with the first, only with pillar
15:00 XenophonF look at the example here - http://docs.saltstack.com/en/latest/ref/states/all/salt.states.saltmod.html
15:00 XenophonF er, i mean here - http://docs.saltstack.com/en/latest/ref/states/all/salt.states.saltmod.html#salt.states.saltmod.state
15:01 Vynce joined #salt
15:01 aRkadeFR oh yeah
15:01 aRkadeFR thanks
15:02 funzo joined #salt
15:14 mrhobbeys joined #salt
15:15 mrhobbeys Hey, I am trying to figure out if I use salt will I still need other things like chef and/or puppet or does salt do everything they do?
15:17 mrhobbeys For instance if I setup a new server and then point it to my "master" will the master be able to tell it how I want it configured. Will it be able to take that new server and deploy backups if I was trying to recover from an incident?
15:19 dthom91 joined #salt
15:26 omegamike joined #salt
15:26 nitay joined #salt
15:32 aRkadeFR XenophonF: http://pastebin.com/YyK6HXCx don't find the right syntax to run my salt orchestration on the pillar targets :(
15:40 favadi joined #salt
15:44 timoguin joined #salt
15:47 stoogenmeyer joined #salt
15:48 sunkist joined #salt
15:51 markm joined #salt
15:55 pmcg joined #salt
16:08 CeBe joined #salt
16:15 herpoderp joined #salt
16:15 denys joined #salt
16:15 XenophonF mrhobbeys: you can use salt for anything chef and puppet can do
16:16 XenophonF mrhobbeys: if you can script a restore, you can call that from salt
16:17 XenophonF mrhobbeys: you can also tie salt into your hypervisor management system and use that to deploy from templates
16:18 funzo joined #salt
16:19 XenophonF mrhobbeys: for example, here's how you'd revert to a snapshot in the next version of Salt - http://docs.saltstack.com/en/develop/ref/clouds/all/salt.cloud.clouds.vmware.html#salt.cloud.clouds.vmware.revert_to_snapshot
16:19 XenophonF aRkadeFR: i'm looking at your paste now
16:21 XenophonF aRkadeFR: your paste doesn't match the syntax of the examples given at http://docs.saltstack.com/en/latest/ref/states/all/salt.states.saltmod.html
16:21 aRkadeFR I found it XenophonF
16:21 XenophonF aRkadeFR: oh great!
16:22 aRkadeFR I didnt saltutil.refresh_pillar …
16:22 aRkadeFR grml
16:22 XenophonF :)
16:22 aRkadeFR but the pillar.items gave me the right data
16:22 XenophonF sweet!!
16:22 aRkadeFR but when salt-run my orchestration… didn't match any minion
16:22 aRkadeFR I refresh_pillar, and it worked :)
16:23 aRkadeFR forgot to let you know
16:25 aparsons joined #salt
16:28 aparsons_ joined #salt
16:29 sunkist joined #salt
16:30 XenophonF no worries!
16:36 bfoxwell joined #salt
16:43 jngd joined #salt
16:52 subsignal joined #salt
16:53 aRkadeFR and now, new question :D how can I run multiple command in a sls orchestration? I dont find the salt.function documentation
16:54 hoonetorg joined #salt
16:55 otter768 joined #salt
16:56 clintberry joined #salt
17:11 z3r0 joined #salt
17:13 omegamike joined #salt
17:14 voxxit joined #salt
17:14 moos3 joined #salt
17:16 XenophonF aRkadeFR: i'm not really sure
17:24 markizano joined #salt
17:27 timoguin joined #salt
17:38 aparsons joined #salt
17:53 mrhobbeys joined #salt
18:09 khapa_ joined #salt
18:18 funzo joined #salt
18:19 dthom91 joined #salt
18:21 CeBe joined #salt
18:22 aqua^c joined #salt
18:24 viq joined #salt
18:31 otter768 joined #salt
18:40 londo joined #salt
18:44 clintberry joined #salt
18:50 linjan joined #salt
18:51 Vynce joined #salt
18:53 pi3r12 joined #salt
19:01 omegamike joined #salt
19:02 ttrumm joined #salt
19:18 s_kunk joined #salt
19:18 s_kunk joined #salt
19:19 funzo joined #salt
19:20 dthom91 joined #salt
19:35 ocdmw joined #salt
19:39 dendazen joined #salt
19:40 sinonick joined #salt
19:52 pi3r12 joined #salt
20:10 stoogenmeyer joined #salt
20:12 claytron_ joined #salt
20:14 stoogenmeyer joined #salt
20:15 stoogenmeyer joined #salt
20:17 stoogenmeyer joined #salt
20:17 stoogenmeyer joined #salt
20:19 fllr joined #salt
20:25 pi3r13 joined #salt
20:26 CeBe joined #salt
20:40 mohae joined #salt
20:41 pdayton joined #salt
20:49 omegamike joined #salt
20:57 claytron_ joined #salt
21:04 aqua^c joined #salt
21:08 ingslovak joined #salt
21:08 whytewolf aRkadeFR: what do you mean by run multiple commands in a sls orchestration?
21:08 peters-tx joined #salt
21:10 MatthewsFace joined #salt
21:12 whytewolf aRkadeFR: you can build a state file then use salt.state. or use execution modules with salt.function. an orch file can have a long string of these put together rather like a state file
21:13 whytewolf aRkadeFR: see https://docs.saltstack.com/en/latest/topics/tutorials/states_pt5.html#more-complex-orchestration
21:17 aRkadeFR ok
21:18 aRkadeFR I mean I'm manageing a website and the auto deployment. So I need to run certains commands in a certain sequence. Right now, I did orchestration command: orch.upload_package,  orch.update_repo , orch....
21:18 aRkadeFR I would like to do them in one orchestration cmd.run
21:20 whytewolf oh you want to orchenstrate orchenstration. yeah not possable. if you want to run those in order. basicly cat them all into the same file in the order you want them run.
21:21 aRkadeFR ok, I'm running the three commands separately right now, it's ok
21:29 sunkist joined #salt
21:44 claytron_ joined #salt
22:00 pdayton joined #salt
22:05 funzo joined #salt
22:09 nitay joined #salt
22:15 zmalone joined #salt
22:23 zmalone joined #salt
22:23 kevinquinnyo joined #salt
22:25 kevinquinnyo hey all, if I build a python class in a state with the #!py renderer, how can I get access to the __pillar__ and __grains__ and other salt objects in that class?
22:25 kevinquinnyo sorry i'm a bit new to salt and python itself
22:26 kevinquinnyo i'm instantiating the class inside the run() function required (as far as I know) when using the py renderer
22:26 kevinquinnyo i can provide a full code example if it helps
22:27 claytron_ joined #salt
22:28 nitay joined #salt
22:30 fllr joined #salt
22:32 AwchinBruh joined #salt
22:37 dthom91 joined #salt
22:38 nitay i’m getting an error trying to use pip, don’t get what’s going on been googling to no avail - https://gist.github.com/nitay/24b15871b28a3b37c02d
22:44 timoguin joined #salt
22:44 yomilk joined #salt
22:46 nitay joined #salt
22:54 yomilk joined #salt
22:55 nitay joined #salt
22:55 XenophonF nitay: pip isn't installed
22:55 XenophonF hence the error
22:55 nitay XenophonF: it definitely is
22:55 nitay # which pip
22:55 nitay /usr/bin/pip
22:56 nitay and in the sls i depend on the pkg installed
22:56 nitay so i dont understand
22:56 XenophonF did you install pip outside of salt?
22:56 XenophonF try reloading/restarting the minion
22:56 nitay didnt install outside no
22:56 XenophonF salt-call saltutil.reload_minion or something like that, or just restart it
22:56 nitay tried restarting didnt work
22:57 nitay 'saltutil.reload_minion' is not available
22:57 XenophonF sorry can't remember which saltutil function it is
22:58 nitay i tried restarting
22:58 XenophonF i see you error - line 42, wrong name in the dependency
22:58 nitay didnt work
22:58 XenophonF should be pkg: pip-pkg
22:58 XenophonF because the state ID of the pkg.installed state is `pip-pkg`
22:59 XenophonF wow that stack trace couldn't be less helpful, eh?
22:59 nitay that doesant work either
22:59 nitay same error
23:00 XenophonF so your sls file looks like this now?
23:00 XenophonF https://gist.github.com/xenophonf/04864aeb65758d23fcf3
23:01 nitay yeah
23:01 nitay same error
23:01 nitay i think cause of the “names” part u can use either way
23:01 XenophonF (also, for pkg.installed states its more efficient to use `pkgs` instead of `names`)
23:01 XenophonF i'm not sure the name/names arguments work like that
23:01 nitay same error with that now too
23:01 XenophonF hm
23:02 XenophonF this is on ubuntu trusty?
23:02 nitay yeah
23:03 nitay https://gist.github.com/nitay/d921a58c8c375905fe90
23:03 XenophonF what happens if you run `salt-call state.single pkg.installed python-pip`?
23:04 nitay https://gist.github.com/nitay/0c087a80d5b4f8c2fa55
23:04 fllr joined #salt
23:04 nitay its green, as in looks like it didnt have to do anything
23:05 krymzon joined #salt
23:05 XenophonF and if that works what happens if you run `salt-call state.single pkg.installed pkgs='["awscli", "pygerduty", "yolk"]'`?
23:06 XenophonF oh sorry that should be pip.installed and names= instead of pkgs=
23:06 nitay https://gist.github.com/nitay/407f45ead59e7e09780e
23:09 nitay sth is screwed up, for example on salt master “salt-call state.single pip.installed awscli” works
23:09 nitay but in this machine it doesnt
23:09 nitay btw this is a fresh machine from salt-cloud, ive tried it twice already, somehow salt gets into this weird state
23:11 XenophonF that's really strange
23:11 XenophonF bad packages maybe?
23:12 XenophonF i assume you used the saltstack ppa
23:12 nitay XenophonF: maybe yea - how would i check that?
23:12 XenophonF here, do this
23:12 nitay im not every sure where it gets it to be honest, i just launch ec2 instances uses salt-cloud
23:13 XenophonF ah, got it
23:13 nitay then it sets up everything gets minion talking to master
23:13 claytron_ joined #salt
23:13 XenophonF behind the scenes there's a salt bootstrapping script
23:13 XenophonF it's all a little hand-wavey to me, still
23:13 XenophonF on your broken minion, look under /usr/lib/python2.7/site-packages/salt
23:13 XenophonF from there do ls */*pip*
23:14 XenophonF sorry that should be /usr/lib/python2.7/dist-packages
23:14 XenophonF salt
23:14 XenophonF and then the ls command as above
23:15 nitay exceptions.py  exceptions.pyc  __init__.py  __init__.pyc  layer1.py  layer1.pyc
23:15 XenophonF it should be
23:15 XenophonF modules/pip.py  modules/pip.pyc  states/pip_state.py  states/pip_state.pyc
23:15 XenophonF i'm in /usr/lib/python2.7/dist-packages/salt on my vivid box
23:16 nitay oh sorry wrong dir one sec
23:16 XenophonF np
23:16 nitay modules/pip.py  modules/pip.pyc  states/pip_state.py  states/pip_state.pyc
23:16 nitay thats what i get
23:16 XenophonF ok so at least they're there
23:16 XenophonF hm.
23:17 zmalone joined #salt
23:17 XenophonF ok, try this:
23:18 XenophonF run python, at the >>> prompt enter: import pip
23:18 XenophonF should be Python 2.7.something
23:18 nitay no problems
23:18 XenophonF and the default python is 2.7?
23:18 nitay shows another prompt, so im assuming its imported it no problem
23:18 nitay yeah
23:18 nitay https://gist.github.com/nitay/80758c8b5a456ad95640
23:19 XenophonF yeah, means the import worked
23:19 XenophonF so pip is _definitely_ installed
23:19 XenophonF and it's working
23:19 XenophonF hm
23:20 XenophonF brb gotta take the dog out
23:25 mosen joined #salt
23:26 fllr joined #salt
23:27 amcorreia joined #salt
23:28 whytewolf nitay: looks like you are running into this error. https://github.com/saltstack/salt/issues/25813 in a way. [same stack trace] see if salt '<minion>' sys.doc pip.installed returns anything. if not salt is defintly not detecting pip
23:28 saltstackbot [#25813]title: debconf.set throwing exception in 2015.8.0rc2 | trying to use the current RC for dev work. and ran into this bug on a state that was working. ...
23:29 nitay @whytewolf yeah returns nothing
23:30 nitay whytewolf: how do i fix this?
23:35 nitay also it looks like from your stack trace that problem should only be in RC no?
23:35 nitay i havent purposefully installed any RCs, that is afaik I should be on a stable release
23:36 whytewolf well need to get the state __virtual__ to return true. which requires 3 things working, import pip, import pip.req, and pip.list in __salt__ [note if pip.list isn't working this will fail]
23:36 whytewolf nitay: they found the same bug in 2015.5.3
23:37 nitay whytewolf: i don thtink i understood that whole sentence - “import pip” and “import pip.req” work in python shell
23:37 nitay what else do i need to do?
23:38 whytewolf what happens if you run pip list in the shell
23:39 kevinquinnyo interesting, i was trying to run salt-master + salt-minion on a VM with 128M of ram, and i kept thinking i had an error in my states, but it just didnt have enough memory.  I wonder if that should be a more clear error -- perhaps memory requirements are in the installation guide already
23:39 kevinquinnyo it would just say that the minion failed to respond
23:39 nitay whytewolf get a whole bunch of pkgs, anything in particular looking for?
23:39 whytewolf nitay: :/ a stack trace was a hope
23:40 nitay one thing that seems kinda odd whytewolf I see package “salt” in pip list, but I also have salt-common / salt-minion from dpkg -l
23:40 nitay pip itself seems to be functioning fine
23:41 whytewolf okay. then i have no idea. all the requirments for getting pip __virtual__ replying should be there.
23:41 whytewolf also salt in pip is fine. system packages on ubuntu still show up in pip
23:42 whytewolf it threw me off when i noticed it
23:42 aqua^c joined #salt
23:42 XenophonF back
23:42 nitay whytewolf: i see, ok
23:43 nitay q - is there a way to “rolback” to previous release
23:43 XenophonF am back
23:43 XenophonF thanks for the clue, whytewolf
23:43 whytewolf actually you might want to move forward. and update the bootstrap script in salt-cloud
23:43 nitay XenophonF: hey, whytewolf was trying to help also
23:44 nitay salt somehow has been auto-updating itself or sth, by that I mean what I’ve seen is that each time I launch a minion it seems to install “latest salt” on there, but then each machine ends up slightly differently - what I really want is for every machine to be the same
23:44 nitay find one version that “works”, and no matter when I launch an instance it uses that
23:44 nitay then I can test upgrading in a sandbox
23:44 nitay whereas right now i basically cant provision new instances :/
23:44 whytewolf I belive you can use script_args to that effect
23:45 nitay whytewolf: how do i do that?
23:45 nitay also how do I update bootstrap script?
23:45 XenophonF alternatively, from the command prompt you can tell apt to install a particular version of a package, apt-get install <package name>=<version>
23:45 nitay yeah but i dont install salt-minion
23:45 nitay salt-cloud does it
23:45 whytewolf http://docs.saltstack.com/en/latest/topics/cloud/misc.html
23:46 whytewolf this is the script it uses for bootstraping https://github.com/saltstack/salt-bootstrap
23:47 whytewolf 'salt-cloud -u' will tell salt-cloud to download the latest copy of the script
23:48 nitay i see the script_args, don’t see how to force a version with that?
23:49 nitay that gave me another fun one - https://gist.github.com/nitay/db6139ad4cfc71a61b28
23:49 whytewolf there must have been a change recently with the bootstrap script SSL. not much you can do with that
23:50 nitay so i cant actually update it?
23:50 whytewolf you could manually. I just don't remeber where it goes. [in the filesystem]
23:51 nitay i see (looking at the script now) - so i should be able to pass sth like “stable 2014.7”
23:52 whytewolf yeap
23:52 nitay /usr/lib/python2.7/dist-packages/salt/cloud/deploy/bootstrap-salt.sh look right?
23:52 whytewolf yes!
23:52 nitay k ill wget it myself
23:54 nitay so now try relaunch instance yeah?
23:54 whytewolf wait. i don't think stable 2014.7 will work. think you will have to go with git v2017.4 [which will install the git version of 2014.7
23:54 nitay does that version change
23:54 nitay i want sth that will stay the same no matter when i run it
23:54 nitay until I upgrade
23:54 whytewolf not very often. it only gets patches that are considered security or extram bugs
23:55 nitay also im a bit confused - if the bootstrap script is getting it from git repo, how come theres apt/pip pkgs for salt?
23:55 fllr joined #salt
23:56 whytewolf oh, just read the source. stable 2014.7 should work
23:56 whytewolf sorry about that.
23:56 nitay np
23:57 whytewolf going off documentation they left off that stable DOES have install-type-args
23:57 nitay k gonna try that
23:58 claytron_ joined #salt

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