Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2017-12-03

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

All times shown according to UTC.

Time Nick Message
00:00 saltslackbridge joined #salt
00:05 rem5 joined #salt
00:05 saltslackbridge <gtmanfred> There is a first filter in jinja
00:06 saltslackbridge <gtmanfred> Just add |first
00:33 tom[] joined #salt
00:54 londo joined #salt
01:15 rem5 joined #salt
01:23 rem5 joined #salt
01:29 stickyfingaz joined #salt
02:04 ahrs joined #salt
02:32 mikecmpbll joined #salt
02:56 robinsmidsrod joined #salt
02:57 ilbot3 joined #salt
02:57 Topic for #salt is now Welcome to #salt! <+> Latest Versions: 2016.11.8, 2017.7.2 <+> Support: https://www.saltstack.com/support/ <+> Logs: http://irclog.perlgeek.de/salt/ <+> Paste: https://gist.github.com/ <+> See also: #salt-devel, #salt-offtopic, and https://saltstackcommunity.herokuapp.com (for slack) <+> We are volunteers and may not have immediate answers
03:29 rem5 joined #salt
03:55 zerocoolback joined #salt
04:43 tcpdump left #salt
06:22 Oida joined #salt
06:39 shiranaihito joined #salt
07:18 mikecmpbll joined #salt
07:31 wongster80 joined #salt
07:51 fracklen joined #salt
08:04 bvcelari joined #salt
08:05 Trauma_ joined #salt
08:29 Felgar joined #salt
08:46 saltslackbridge <james> Is there a way to target minions in a round robin fashion?
08:47 saltslackbridge <james> So I target a nodegroup or something but only apply the state/exec model against the first one available
08:47 hoonetorg joined #salt
08:48 saltslackbridge <james> Well those two things are slightly different but you  get my drift
09:00 cyteen__ joined #salt
09:01 JawnAuz joined #salt
09:06 JAuz joined #salt
09:16 zer0def joined #salt
09:41 hemebond Batch
09:43 MTecknology batch would only let you do one at a time, not only hit the first
09:44 hemebond Then I don't understand the question ☺ I thought "first one available" meant one at a time.
09:46 MTecknology I can think of how to handle that w/ orchestrate, but it's a lot clunkier than "salt-key -L | grep foo" & "salt foo-01 state.highstate"
09:49 MTecknology - tgt: {{ salt.key(match="foo")[0] }}
09:49 aldevar joined #salt
09:49 MTecknology give or take?
09:49 zerocoolback joined #salt
10:27 shripadr joined #salt
11:22 zer0def joined #salt
11:51 mikecmpbll joined #salt
12:20 Deliant joined #salt
12:23 oida joined #salt
12:36 quantumsummers joined #salt
12:38 nidr0x joined #salt
12:39 cyteen__ joined #salt
12:58 pualj joined #salt
13:02 indistylo joined #salt
13:32 Hybrid joined #salt
13:50 Hybrid joined #salt
13:52 zerocoolback joined #salt
13:52 zerocoolback joined #salt
14:42 bildz joined #salt
14:45 viq MTecknology: "I have 100 nodes, I want this to run only on 3, I don't care which"
14:46 tiwula joined #salt
14:47 viq AFAIK salt doesn't currently have a way to express that.
14:47 babilen Ansible does :-p
14:48 viq And so does mcollective, but we're not talking about either of those :P
14:48 babilen You can do it with orchestration, but Salt is quite .. well .. single minion minded in a lot of things and it is tricky to express "Do specific things for all minions currently targeted"
14:50 babilen I would, however, not know how to get "currently targeted" minions in an orchestration run either .. If the target expression is known, one could use orchestration, test.ping and them randomly select three out of those that replied, target those and be done
14:50 viq I think you meant "Do specific things *only to some of* minions currently targeted" ?
14:50 babilen Any subset really
14:50 babilen But yeah, all is the easy bit :)
15:01 pualj joined #salt
15:22 pualj joined #salt
15:27 snc joined #salt
15:27 TomJepp hey. I'm looking to upgrade my salt master & all orchestrated hosts from 2016.11 to 2017.7. Other than the usual 'upgrade the master first' rule, is there anything else I need to bear in mind/avoid? is this going to go catastrophically wrong? ;)
15:32 sh123124213 joined #salt
15:44 miruoy joined #salt
15:45 om2 joined #salt
15:47 snc joined #salt
15:48 snc TomJepp: the only issue i had was dpkg getting upset, and sometimes needing manually fixed. that manual fix was `dpkg --configure -a && apt-get install -f -y`
15:48 snc for the majority of minions, was a painless upgrade
15:49 TomJepp snc: thanks. that'll be a pain, but not as bad as some (41 minions to upgrade, yay)
15:49 snc yea, salt-ssh makes it easier to recover if it's an option for you
15:59 pualj_ joined #salt
16:19 TomJepp joined #salt
16:27 sybix joined #salt
16:30 hexa- joined #salt
16:42 cyteen joined #salt
17:08 evle1 joined #salt
17:30 pualj joined #salt
17:32 pualj joined #salt
17:36 ircuser-1 joined #salt
17:53 rem5 joined #salt
18:00 GrisKo joined #salt
18:22 felskrone joined #salt
18:30 viq or using `at.at` to do the upgrades ;)
18:35 Lionel_Debroux_ joined #salt
18:38 tiwula joined #salt
18:38 colabeer joined #salt
18:53 felskrone joined #salt
18:57 zer0def joined #salt
19:00 pualj_ joined #salt
19:15 aldevar joined #salt
19:15 colabeer joined #salt
19:19 miruoy joined #salt
19:25 miruoy joined #salt
19:29 pualj joined #salt
19:38 Trauma_ joined #salt
19:39 dhwt joined #salt
19:53 felskrone joined #salt
19:56 aldevar joined #salt
19:58 pualj_ joined #salt
20:03 pualj_ joined #salt
20:05 trouba_w joined #salt
20:08 MTecknology babilen: viq: My little orch -tgt: wasn't meant to be accurate, but you could easily write a custom utility module to handle that sort of selection.
20:09 viq oh, I missed that
20:09 MTecknology My argument is that it seems more like you're trying to use salt as a job queue than a config management system.
20:15 Trauma_ joined #salt
20:15 babilen There are a some applications for running commands on one/two/... boxes out of a given set while it doesn't matter which one, but you are right
20:16 babilen I think it is essentially a different mindset
20:22 viq One of things for that is I think called "Blue/green deployments"
20:22 viq or A/B testing
20:25 Trauma_ joined #salt
20:27 MTecknology I'd prefer build a custom grain module that can be used for targeting which cluster is currently active/idle
20:28 MTecknology salt -C 'prd-ns* and G@mt_bluegreen:standby' ..
20:29 Trauma_ joined #salt
20:31 Trauma_ joined #salt
20:31 babilen Some software might expect you to run "initialisation" commands on one node in a set, when it doesn't matter which one you run it on
20:32 Trauma_ joined #salt
20:39 nomeed joined #salt
20:55 felskrone joined #salt
21:03 SkyRocknRoll joined #salt
21:34 tiwula joined #salt
21:56 felskrone joined #salt
22:05 sh123124213 joined #salt
22:13 armyriad joined #salt
22:27 sh123124213 joined #salt
22:43 stickyfingaz joined #salt
22:53 stickyfingaz joined #salt
22:55 rem5 joined #salt
22:56 felskrone joined #salt
22:59 sh123124213 joined #salt
23:02 rem5 joined #salt
23:07 rem5 joined #salt
23:11 cyteen joined #salt
23:12 om2 joined #salt
23:15 rem5 joined #salt
23:16 oida joined #salt
23:24 bdf joined #salt
23:36 masber joined #salt
23:40 saltslackbridge <james> I was thinking in terms of hitting a Docker swarm manager node or a node with shared storage - I don't care which I hit and I only need to hit one
23:41 saltslackbridge <james> Maybe a salt runner module? That takes a nodegroup (or target expression) and a state file?
23:41 saltslackbridge <james> And the runner will check for an online node
23:42 saltslackbridge <james> And maybe an optimal number of nodes
23:46 skinkitten joined #salt
23:50 saltslackbridge <james> Also, unrelated - is there a pillar for salt master?
23:50 hemebond I don't believe so. What would it do?
23:50 saltslackbridge <james> I know it can access pillar items assigned to all
23:50 saltslackbridge <james> Well, for orchestrating and reactors
23:51 saltslackbridge <james> Slack API keys etc.
23:53 hemebond btw, I'm pretty sure the master can't access minion pillar data except when working with a minion.
23:53 hemebond You are likely to get random minion pillar data.
23:53 hemebond Maybe that's changed but I remember seeing people trying to do it and getting random results.
23:54 hemebond It appears orchestration has changed in 2017.7.2
23:54 hemebond You can pass in pillar data.
23:55 hemebond So you could cat a file as JSON and attach it to the orchestration call.
23:57 felskrone joined #salt

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